Database Info

What did I do to my phone? Please help.

On a mac here. I think I got a bit over my head here with the 2.20 root. I did all of the bootloader unlocking successfully, installed TWRP, and then downloaded CM10, and flashed the boot.img.
Now when trying to boot the phone I get stock on the screen with "This Build is for development only."
I can get into recovery, but don't really know what to do from there. I'm trying to mount, but can't get the computer to recognize the device. Tried a factory reset and it failed. I'm not quite bricked, but sort of stuck and don't know what to do. I'd love to get CM10 working, but at least I want to be able to use my phone.
I'm pretty new to Android so sorry for newbishness.
Thanks anyone for your help.

Just to add, I'm getting the message "no OS installed" when trying to reboot in recovery.

ul49 said:
On a mac here. I think I got a bit over my head here with the 2.20 root. I did all of the bootloader unlocking successfully, installed TWRP, and then downloaded CM10, and flashed the boot.img.
Now when trying to boot the phone I get stock on the screen with "This Build is for development only."
I can get into recovery, but don't really know what to do from there. I'm trying to mount, but can't get the computer to recognize the device. Tried a factory reset and it failed. I'm not quite bricked, but sort of stuck and don't know what to do. I'd love to get CM10 working, but at least I want to be able to use my phone.
I'm pretty new to Android so sorry for newbishness.
Thanks anyone for your help.
Click to expand...
Click to collapse
Did you flash the boot.img first, then the ROM?
Can you wipe System?

Sorry, what's the difference betwwen boot.img and the rom itself? I only flashed boot.img. I did wipe the system.

ul49 said:
Sorry, what's the difference betwwen boot.img and the rom itself? I only flashed boot.img. I did wipe the system.
Click to expand...
Click to collapse
The boot.img has the kernel in it. If you didn't flash the CM10.zip you have no operating system.
Wipe System, and Factory Reset
Flash boot.img
Flash the CM10.zip, flash google apps, and you should be good after that

Now flash the rom zip from recovery (twrp)
Sent from a slithery smooth phone!

So to flash the zip file for the ROM and gapps, I just enter fastboot flash boot 'rom.zip' or 'gapps.zip'?
Also, what do I do after I've flashed them?
Thanks so much for your help

ul49 said:
So to flash the zip file for the ROM and gapps, I just enter fastboot flash boot 'rom.zip' or 'gapps.zip'?
Also, what do I do after I've flashed them?
Thanks so much for your help
Click to expand...
Click to collapse
no,you flash the boot.img in fastboot, and then you flash the rom.zip and gapps.zip from recovery (twrp)

ul49 said:
So to flash the zip file for the ROM and gapps, I just enter fastboot flash boot 'rom.zip' or 'gapps.zip'?
Also, what do I do after I've flashed them?
Thanks so much for your help
Click to expand...
Click to collapse
No, do a clean wipe.
boot your phone into fastboot
download the fastboot files http://www.mediafire.com/?4dx982z93w8z7wk and extract them to your desktop
on your computer, open up cmd and type
cd desktop
cd foldername (the folder that has fastboot.exe)
fastboot flash boot boot.img
reboot into recovery
flash CM10, flash gapps, reboot

I see. The problem is that I seem to be unable to mount my phone and sd card through recovery.

Trying to push the zips using adb using './adb push cm10.zip/sdcard' but when I enter this command in terminal it seems to just reload adb, and not push the file.

ul49 said:
Trying to push the zips using adb using './adb push cm10.zip/sdcard' but when I enter this command in terminal it seems to just reload adb, and not push the file.
Click to expand...
Click to collapse
I think you are typing the command wrong
./adb push file /destination
or ./adb push cm10.zip /mnt/sdcard
./adb push cm10.zip /sdcard
whatever the mount point is for the sdcard

Tried that too. It just reloads the opening adb dialogue.

ul49 said:
Tried that too. It just reloads the opening adb dialogue.
Click to expand...
Click to collapse
does ./adb devices return your phone as connected?

Well, now it doesn't. Instead of reloading the adb dialogue now, when I try the push command it says device not found. Just came out of nowhere. How do I make it recognize the phone again?
Thanks for bearing with me here. I think I'm really close.

ul49 said:
Well, now it doesn't. Instead of reloading the adb dialogue now, when I try the push command it says device not found. Just came out of nowhere. How do I make it recognize the phone again?
Thanks for bearing with me here. I think I'm really close.
Click to expand...
Click to collapse
I'm not familiar with OS X and android, are there any specific drivers you may need to install?
Are you in your bootloader or recovery?

All necessary drivers were installed. The device was being recognized before, but for some reason isn't now. I'm stuck on the "This build is for development purposes only" screen now since I can't get into recovery or bootloader using adb now since the device isn't recognized...

Ok, I'm connected again somehow. Now just trying to figure out this pushing issue. Entered this command './adb push /android/cm10.zip /sdcard and it looked like it was working then said "failed to copy to /sdcard"

ul49 said:
Ok, I'm connected again somehow. Now just trying to figure out this pushing issue. Entered this command './adb push /android/cm10.zip /sdcard and it looked like it was working then said "failed to copy to /sdcard"
Click to expand...
Click to collapse
because it is probably at /mnt/sdcard

Successfully pushed the files. Of course, I've hit another problem. Trying to install the ROM through TWRP and it's failing. Same with Gapps. I'm seeing "unable to mount /sdcard" and unable to mount storage. I've already cleared cache, wiped system, factory reset/

[Q] Help - Rooting gone wrong

So I got the HTC One s and try to root it with the following instruction: http://forum.xda-developers.com/showthread.php?t=1583427&__utma=248941774.997411949.1390324490.1394471756.1396118873.6&__utmb=248941774.2.10.1396118873&__utmc=248941774&__utmx=-&__utmz=248941774.1394471756.5.2.utmcsr=feedburner|utmccn=Feed:%20xda-developers/ShsH%20(xda-developers)|utmcmd=feed&__utmv=-&__utmk=25799614
As I thought that Step 3 was only there to install the Superuser.apk i just skipped it (mistake no. 1) and wiped the whole thing (without making a backup --> mistake no. 2) and tried to install the Maximus HD Rom which as I am still S-On of course didnt work. So I wiped again but really careless and made mistake no. 3: wiping the whole thing instead of just a few partitions like system, cache,....
So now I have my device S-On, theres really nothing on it exept TWRP but there (and in other recoverys I tried) the USB mout doesnt work so I cant get a new rom on it So I tried to push it through fastboot but I cant find a fitting command.
Any advice what I can do to either get the USB work in the recoverys or push it through fastboot and which rom works without S-Off?
If you need further infos Id like to give those!

Akkordinator said:
So I got the HTC One s and try to root it with the following instruction: http://forum.xda-developers.com/showthread.php?t=1583427&__utma=248941774.997411949.1390324490.1394471756.1396118873.6&__utmb=248941774.2.10.1396118873&__utmc=248941774&__utmx=-&__utmz=248941774.1394471756.5.2.utmcsr=feedburner|utmccn=Feed:%20xda-developers/ShsH%20(xda-developers)|utmcmd=feed&__utmv=-&__utmk=25799614
As I thought that Step 3 was only there to install the Superuser.apk i just skipped it (mistake no. 1) and wiped the whole thing (without making a backup --> mistake no. 2) and tried to install the Maximus HD Rom which as I am still S-On of course didnt work. So I wiped again but really careless and made mistake no. 3: wiping the whole thing instead of just a few partitions like system, cache,....
So now I have my device S-On, theres really nothing on it exept TWRP but there (and in other recoverys I tried) the USB mout doesnt work so I cant get a new rom on it So I tried to push it through fastboot but I cant find a fitting command.
Any advice what I can do to either get the USB work in the recoverys or push it through fastboot and which rom works without S-Off?
If you need further infos Id like to give those!
Click to expand...
Click to collapse
TWRP has ADB Sideload feature. Means you can flash zips using adb. Of course you can flash a roms this but keep in mind you have to flash the kernel (boot.img) manually immediately after flashing the rom.zip. When flashed Rom.zip by using ADB sideload method make SURE that you direct go into fastboot mode and flash the kernel (fastboot flash boot boot.img) (you can extract the boot.img from your rom.zip)
May be a compatible rom this time? But you're lucky -> Infact you already deleted everything you won't have to perform a wipe before flashing lol

LS.xD said:
Of course you can flash a roms
Click to expand...
Click to collapse
Ok, but I dont know with which command (fastboot flash what? or adb?)

You can use adb sideload as followed:
Start TWRP -> advanced -> ADB sideload + swipe to activate it. Connect your phone to the computer. Open "CMD Commandline" and type "adb sideload ROMNAME.zip"
Of course "ROMNAME" has to match the zip you want to flash. Thats it
In twrp go to "REBOOT" -> "fastboot"
When fastboot usb is ready use CMD commandline again and type "fastboot flash boot boot.img"
Then you can boot android

I whished I could. As I start ADB sideload it keeps doing nothing at all until I abort it. What I think is important to know is that it is then:
"E:Unable to mout '/internal_sd'
E:Unable to mount storage.", which I think is the problem.

Flash Stock recovery And perform "factory Reset + clear storage" that will fix your storage. Then flash twrp Version 2.7 again and do what I suggested to flash the Rom
Sent from my beloved HTC One S using (most time buggy) Tapatalk

Did the exact thing which removes the mounting error, but this has no effect on the sideload (or usb mount). Still not working.

Akkordinator said:
Did the exact thing which removes the mounting error, but this has no effect on the sideload (or usb mount). Still not working.
Click to expand...
Click to collapse
Can you acces your sdcard by twrp? Lot of poeple here has sd card bug yet and it was fixed everytime.
You're facing sdcard bug.
This is how to solve:
1. Flash stock recovery
2. reboot to bootloader and perform "factory reset + clear storage" (While in bootloader NOT in recovery)
3. Flash custom recovery again
4. Reboot recovery - mount usb storage - copy ROM.zip to sdcard // adb sideload rom
7. NOW boot android (Not at any time before! Even there is no system installed)
Please just repeat it.

LS.xD said:
Can you acces your sdcard by twrp? Lot of poeple here has sd card bug yet and it was fixed everytime.
Click to expand...
Click to collapse
I can acces it in TWRP (of course only a TWRP folder in it). Tried the repeating progress over and over but nothing changes. And USB-OTG isnt able to mount.
Thanks for your patient help!

Akkordinator said:
I can acces it in TWRP (of course only a TWRP folder in it). Tried the repeating progress over and over but nothing changes. And USB-OTG isnt able to mount.
Thanks for your patient help!
Click to expand...
Click to collapse
In case you can acces the storage in twrp its related to windows or drivers. What windows version you are running?

LS.xD said:
In case you can acces the storage in twrp its related to windows or drivers. What windows version you are running?
Click to expand...
Click to collapse
It was windows! Tried it on the other computer with win7 instead of 8.1 and I finally got a connection!
Thanks so much!!!

No OS... TWRP won't display files on otg/sd

I had a bit of a problem with CM and it kept saying trebuchet had stopped working. (This is after the phone had been running fine for a whole year with CM. Then the phone kept restarting and saying trebuchet had stopped working and it would constantly restart until it calmed down. I decided to install and alternative launcher but the problem didn't totally go.
Thereafter I decided to delete trebuchet from root and boom the phone never calmed down and kept restarting. Eventually I tried restoring factor settings and it says now that there's no OS.
I had TWRP installed before but now when I've tried to install the latest one, it doesn't show any files on the OTG. I've put twrp on the SD along with a rom as well but nothing shows at all.
Can someone help in simple terms?

emmpii said:
I had a bit of a problem with CM and it kept saying trebuchet had stopped working. (This is after the phone had been running fine for a whole year with CM. Then the phone kept restarting and saying trebuchet had stopped working and it would constantly restart until it calmed down. I decided to install and alternative launcher but the problem didn't totally go.
Thereafter I decided to delete trebuchet from root and boom the phone never calmed down and kept restarting. Eventually I tried restoring factor settings and it says now that there's no OS.
I had TWRP installed before but now when I've tried to install the latest one, it doesn't show any files on the OTG. I've put twrp on the SD along with a rom as well but nothing shows at all.
Can someone help in simple terms?
Click to expand...
Click to collapse
Use adb commands to flash TWRP (Put your TWRP image in the same folder on your pc as your adb and enter each command separately):
adb reboot bootloader
fastboot flash recovery twrp.img (latest version is 3.1.1-0-peregrine, remame it to twrp.img - if that doesn't work rename twrp to recovery.img and try that).
fastboot reboot
If that works, restore you last known good working backup or try re-installing your stock rom.

sdembiske said:
Use adb commands to flash TWRP (Put your TWRP image in the same folder on your pc as your adb and enter each command separately):
adb reboot bootloader
fastboot flash recovery twrp.img (latest version is 3.1.1-0-peregrine, remame it to twrp.img - if that doesn't work rename twrp to recovery.img and try that).
fastboot reboot
If that works, restore you last known good working backup or try re-installing your stock rom.
Click to expand...
Click to collapse
I've installed fastboot onto my PC. Now i'm trying the adb commands but my phone isn't showing up
Tried a new cable.. so far it's started to recognise. I'll update this if theres news.
*adb command doesn't work... says no devices. Fastboot seems to work

ive managed to get the latest twrp on.. now I cant seem to adb sideload the rom nor does it show via otg.. ADB sideload disconnects and says invalid zip file

emmpii said:
I've installed fastboot onto my PC. Now i'm trying the adb commands but my phone isn't showing up
Tried a new cable.. so far it's started to recognise. I'll update this if theres news.
*adb command doesn't work... says no devices. Fastboot seems to work
Click to expand...
Click to collapse
Install or re-install your Motorola Device Manager on your pc from this link: https://mobilesupport.lenovo.com/us/en/solution/MS88481
Check in your pc Device Manager to see if your device is connected and recognized properly when you plug in the USB cable.
In the folder where your adb and fastboot files are, open a command prompt and enter adb devices to see if the phone is recognized now in adb. If it is, proceed as suggested earlier.

sdembiske said:
Install or re-install your Motorola Device Manager on your pc from this link: https://mobilesupport.lenovo.com/us/en/solution/MS88481
Check in your pc Device Manager to see if your device is connected and recognized properly when you plug in the USB cable.
In the folder where your adb and fastboot files are, open a command prompt and enter adb devices to see if the phone is recognized now in adb. If it is, proceed as suggested earlier.
Click to expand...
Click to collapse
shows up in device manager as android usb device, Still not showing on adb

I managed to get the device to finally track on with adb. It tracks fine now. However I can't seem to flash a rom on regardless of whether its OTG or sideload...

emmpii said:
shows up in device manager as android usb device, Still not showing on adb
Click to expand...
Click to collapse
Go to this link (https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816) and download the correct untouched rom for your phone model and transfer it to your sd card or internal memory.
Then try this command: fastboot boot recovery.img or fastboot boot twrp.img
and follow the directions exactly in the op in that thread to flash the rom.

sdembiske said:
Try this command: fastboot boot recovery.img or fastboot boot twrp.img
Go to this link (https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816) and download the correct untouched rom for your phone model and transfer it to your sd card or internal memory.
Then try this command: fastboot boot recovery.img or fastboot boot twrp.img
and follow the directions exactly in the op in that thread to flash the rom.
Click to expand...
Click to collapse
Absolutely no idea how but I managed to get one of the CM roms sideloaded and even though when i chose to reboot it said no OS. I've got it going, however I've forgotten to put gapps on so I'll try that now. Later on I'll try sideload stock rom or something and see how that goes. Thanks for the help so far! :good:

emmpii said:
Absolutely no idea how but I managed to get one of the CM roms sideloaded and even though when i chose to reboot it said no OS. I've got it going, however I've forgotten to put gapps on so I'll try that now. Later on I'll try sideload stock rom or something and see how that goes. Thanks for the help so far! :good:
Click to expand...
Click to collapse
The problem with CM roms is they're not really being updated anymore - just one of the problems I have with a lot of custom roms besides the bugs, etc., etc.
If you're hell bent on a custom rom, I would check out this one: [ROM][OFFICIAL][Peregrine][7.X] LineageOS 14.1 at https://forum.xda-developers.com/moto-g/4g-development/rom-cyanogenmod-14-0-t3469103
Lineage is the new go-to from CM. I personally would go back to stock first, however, to ensure everything is restored properly before installing it.
It's being updated regularly currently.

I just had a old CM rom downloaded from before hence I went to that lol. I'm trying lineage for now but I've also downloads the stock ROM. Whatever will keep the phone going

[Q] Google OG Pixel problems soft bricked

Hello everyone,
I have an OG Pixel 5'', the stock Android was 7.1.2 and I updated it to Android 8.1 Oreo. Bootloader is unlocked, and I am able to install a TWRP 3.2.1-0 no problems. Phone at the time worked well. Now I have tried to flash an ElementalX Kernel on my device. This worked and I managed to boot. However, a message "There is an internal problem with your device, please contact the manufacturer". There is a thread to fix this and I should have done my research better.
Anyway, I went into TWRP and did a complete wipe of the phone, thinking that I could have just boot into TWRP again and copy the stock flashable zips to reflash the ROM.
It turns out that:
a) TWRP doesnt work. I.e when I got into fastboot mode (Power + Volume Down) and selected Recovery, the phone flashed to screen with Google image and then flashed back into the one with the green Android.
b) I managed to boot twrp via fastboot from my computer. So I booted into fastboot mode, and then on my computer, did: fastboot boot <twrp3.2.1.zip>. This worked and I managed to get into TWRP again. However, I cannot transfer file to flash. I.e when the phone showed up on my computer in TWRP, I cannot drag and drop anything into mounted folder.
I have tried the following to get stock ROM from this website: https://developers.google.com/android/images
a) I decided to look at ADB Sideload. So from the above website, I downloaded the zip files under Full OTA Images and then in TWRP, I went into Advance and chose ADB SIdeload. On my computer, I did "adb sideload name_of_zip_file_downloaded". The process started but ended very quickly, the finished time was 0.00 second, which means that nothing happened. Clearly, TWRP console showed that it is unable to mount /data and other folders. I guess the reason is that I am running a "live" TWRP? I checked by going back to TWRP mainscreen and tried to mount. However, all hard drives show 0MB (OTA USB and the main drive).
b) I used factory images approach by downloading zip from the same website, but this time under Factory Images. For this one, I unzip the files to a separate folder. Then I did flash-all.sh script but it said that my fastboot is too old.
So... to fix fastboot, I tried: (I am on Ubuntu 16.04.02)
a) Remove whole android fastboot with sudo apt-get remove, then reinstalled => Did not work. Still fastboot is too old
b) Download entire Android SDK from here: https://developer.android.com/studio/install.html. Fastboot still didnt work
c) From the Android Studio website, I tried to download just the command line tools. However, I could not find the folder with fastboot in it. A Google search shows that the fastboot and adb should be in platform-tools folder. Couldnt find any
Once again, I apologize for a very very long thread (It's 5am and I am trying to figure this thing out). Please, let me know if you guys can offer any help. Any help is greatly appreciated. FYI, I am coming from a Moto Z Play, and if things happen I would just boot into TWRP and copy the zip over. Clearly, this is not the case. This is my 1st Pixel as well.
Please let me know and thank you very very much.

Installing ex messes with the boot.IMG you need to reflash twrp after. Also don't manually flash stock zips that doesn't even make any sense. Download the latest android sdk or base platform tools then get the latest factory image and extract it into platform tools. Then go into fastboot and manually flash the official factory image

To use fastboot on ubuntu you have to put sudo infront of the command: sudo fastboot ........, Because of a permissions thing.
Sent from my Google Pixel using XDA Labs

Thank you everyone. I have managed to reflash the OS. Gonna stay with stock kernel

maxwell0312 said:
Thank you everyone. I have managed to reflash the OS. Gonna stay with stock kernel
Click to expand...
Click to collapse
I personally recommend using a custom kernel just make sure to follow the OP exactly. As the kernel and twrp are usually stored in the boot.img together and the kernel overwrites the boot.img the problem was likely that you just did things in the wrong order which would cause twrp to be removed. Typically the order of installing custom stuff from stock goes this way: flash_all to restore stock boot.img, boot twrp, factory wipe, flash rom, flash twrp, boot rom, reboot into recovery, flash kernel, flash twrp, reboot system, reboot recovery, flash magisk. Some rooms vary as they may require you to do things like flash a vendor img or delete the vendor overlay folder(always follow OP).

Flashed TWRP. ADB reboot recovery boots to TWRP, but when using vol/pwr keys, boots to stock recovery instead of TWRP.

Having problems booting into TWRP recovery by using power/volume keys on phone.
I managed to get the bootloader unlocked, so I am now free to load custom roms. Well, sort of. I rooted the system, and tried to install TWRP from the playstore. When I got to the part about flashing recovery with the TWRP image, it says Flash failed.
So, I went back to using adb and fastboot. I used "flashboot flash recovery TWRPfilename". That worked. Then "adb reboot recovery" took me to TWRP. So far, so good. When I shut down the phone and use the power/volume keys to boot into recovery, I get the stock rom recovery, not TWRP. If I connect the usb cable and use "adb reboot recovery" I get TWRP recovery.
What is going on here? Anybody who has a clue, please share your thought of the problem and/or possible fixes.
One more tidbit of info. I tried flashing TWRP (installed from the playstore) several times. At first all I got was Flash Failed. Now (for no apparent reason) it was able to flash the TWRP file. So I thought I'd test it out. No change. Still can't boot into recovery by using vol-and pwr. Still takes me to stock rom recovery. But (same as before) adb reboot recovery takes me right to TWRP, and it's working fine. So, I have a way to boot into TWRP, but it requires me to have a computer and usb cable available. I'd like to boot into TWRP using the phone keys.
I am not doing any data wipes, formatting, changing permissions, etc. . Anybody have any experience with this problem, or any thoughts on how to fix it????
BTW, this is for an LG K7 MS330m1.

BigZ1 said:
Having problems booting into TWRP recovery by using power/volume keys on phone.
I managed to get the bootloader unlocked, so I am now free to load custom roms. Well, sort of. I rooted the system, and tried to install TWRP from the playstore. When I got to the part about flashing recovery with the TWRP image, it says Flash failed.
So, I went back to using adb and fastboot. I used "flashboot flash recovery TWRPfilename". That worked. Then "adb reboot recovery" took me to TWRP. So far, so good. When I shut down the phone and use the power/volume keys to boot into recovery, I get the stock rom recovery, not TWRP. If I connect the usb cable and use "adb reboot recovery" I get TWRP recovery.
What is going on here? Anybody who has a clue, please share your thought of the problem and/or possible fixes.
One more tidbit of info. I tried flashing TWRP (installed from the playstore) several times. At first all I got was Flash Failed. Now (for no apparent reason) it was able to flash the TWRP file. So I thought I'd test it out. No change. Still can't boot into recovery by using vol-and pwr. Still takes me to stock rom recovery. But (same as before) adb reboot recovery takes me right to TWRP, and it's working fine. So, I have a way to boot into TWRP, but it requires me to have a computer and usb cable available. I'd like to boot into TWRP using the phone keys.
I am not doing any data wipes, formatting, changing permissions, etc. . Anybody have any experience with this problem, or any thoughts on how to fix it????
BTW, this is for an LG K7 MS330m1.
Click to expand...
Click to collapse
Your device might be an A/B partition device, your OS that you're using and stock recovery may be installed in one of those partitions and TWRP may be installed in the other. This may be causing the stock recovery to boot with the buttons and TWRP may be booting because it is responding to adb in a way that stock recovery does not.
How to fix? Not sure, but, if your device is rooted, you can install a Terminal Emulator app then open the app when you want to boot into recovery and type the following commands:
su (press enter, grant superuser if prompted)
Then type:
reboot recovery (press enter)
Terminal emulator works almost exactly like ADBshell and can run the same commands as ADB shell, you just have to remove the "adb" and "adbshell" part of the commands. In the example above, the comnand in adb would be "adb reboot recovery" but in Terminal Emulator, it is just "reboot recovery". The same would be true for any command that begins with "adb" or "adbshell". You can also try running any other adb or adbshell commands that you might need in the same way in Terminal emulator directly from within the device instead of having to use a PC to run them. You can also flash TWRP(or any other partition/.img) using Terminal emulator by using dd commands to put whatever .img you need/want into any partition that you want. But, you must specifically identify exactly which partition the .img is supposed to be in, if you flash the wrong .img to the wrong partition, it will brick the device. You absolutely MUST use the correct .img and you absolutely MUST flash it to the correct partition.
Or, if your device actually is an A/B device, try seeing if you can identify which partition is which and which one your currently installed operating system is installed in and which partition the stock recovery is installed in then see if you can flash TWRP onto the partition where your stock recovery is installed then try booting into it using the buttons, do not boot into system before booting into TWRP, using the buttons, after flashing TWRP, immediately power the device off then try using the button combo to boot into TWRP.

Thank You Droidriven. You have provided enough info for a reasonable work around.
BTW, I didn't understand what you meant by "I DO NOT PROVIDE HELP IN PM" Would you please explain that? What is PM? If I am doing something wrong in my post, let me know, as that is not my intent.
Using a terminal emulator and using superuser commands does indeed work, to boot directly into TWRP. So, after trying the terminal emulator, I installed an app from Google Play Store called Simply Reboot. It will boot directly into TWRP, no problem!
I don't think I have an A/B partition device. The LG K7 was introduced in 2016, so it's pretty old. I've tried searching the internet, but I can't find any reference to A/B partitions on it. If you have any ideas how I could find out for sure, please let me know.
I have another theory, and would appreciate feedback from you, or others reading this post. I remember watching some youtube video on custom recovery, where they talked about two different ways to control what happens when you use the phone keys to boot into recovery. One is to load an image into the recovery partition. The other is to modify the boot image so that the boot process points to another partition that has the stock recovery image. I might not have that 100% as I am no expert on this stuff. Anyway, maybe somebody can comment on this.
One last thing. Now that I have a terminal emulator, and am only marginally proficient in Linux commands, can anybody suggest what commands I would use to try and figure out where the TWRP image got loaded, vs. where the stock recovery image is located?
Once again, Thanks for all the help!!!!!!