Develop Bugs

LG G Pro E988 stuck on the Logo screen

I have just flash the custom 5.0.2 ROM using philz touch 6.48.4.
After I flashed the ROM, I reboot to the philz recovery and flashed back to cwm 6.0.4.8.
However, the device stuck on the LG logo screen.
I have try to enter Download mode/Emergence mode/Hard reset mode/Recovery, but all of them I cannot go into.
Please help! Thank you for your helping!!

pchuen said:
I have just flash the custom 5.0.2 ROM using philz touch 6.48.4.
After I flashed the ROM, I reboot to the philz recovery and flashed back to cwm 6.0.4.8.
However, the device stuck on the LG logo screen.
I have try to enter Download mode/Emergence mode/Hard reset mode/Recovery, but all of them I cannot go into.
Please help! Thank you for your helping!!
Click to expand...
Click to collapse
Your boot loader is broken. Gonna have to get to the down load mode and reinstall either the or the stock. You can probably flash the recovery with .IMG file with lg flashing tool. Nerdy blond's twrp is one of those files that you can use. You can even try installing it first with the adb shell command, you can get the instructions at the same place where you download.
http://forum.xda-developers.com/showthread.php?t=3144369

hawkwind212 said:
Your boot loader is broken. Gonna have to get to the down load mode and reinstall either the or the stock. You can probably flash the recovery with .IMG file with lg flashing tool. Nerdy blond's twrp is one of those files that you can use. You can even try installing it first with the adb shell command, you can get the instructions at the same place where you download.
http://forum.xda-developers.com/showthread.php?t=3144369
Click to expand...
Click to collapse
Thank you for replying.
I cannot do anythings since I cannot enter into download mode.
I pressed volume key + and - and insert the usb cable to computer. There is nothing happened, computer dose not show the devices attached and the phone stay in the LG logo screen.
Also, I cannot use adb commands to force the phone enters into download mode as it shows nothings under "List of devices".
Is there any methods I can go into the download mode???
Thank you!

pchuen said:
Thank you for replying.
I cannot do anythings since I cannot enter into download mode.
I pressed volume key + and - and insert the usb cable to computer. There is nothing happened, computer dose not show the devices attached and the phone stay in the LG logo screen.
Also, I cannot use adb commands to force the phone enters into download mode as it shows nothings under "List of devices".
Is there any methods I can go into the download mode???
Thank you!
Click to expand...
Click to collapse
If your phone shows LG start screen, it should go into Download mode. I had similar problem few days ago while I was testing some kernel patches, it just froze on the LG screen. Solution was to unplug it, remove it's battery, SIM & SD (you don't have to remove SIM & SD, I just work that way) , make sure it's off, return battery back, press Vol + & Vol - at the same time and plug-in the USB cable.
Before that, make sure you have installed LG Unified driver (can be obtained via LG's software from support site), because without that Windows won't recognise your device.
After that, once you make your phone usable with Freegee/whatever you use to install initial recovery, flash official TWRP, because others are too old - that Philz CWM is old but still working with Lollipop but not work good and is tends to lock itself into a bootloop if you use hardware keys to enter; that other one, from GPRO_recovery APK is not supported and not working well (for me since day one), so it should be replaced as soon as possible.
Also, I can suggest you to flash your phone from stock 4.1 (not KitKat), root, flash recovery via freegee and after reboot update to latest official TWRP via Flashify.

hawkwind212 said:
Your boot loader is broken. Gonna have to get to the down load mode and reinstall either the or the stock. You can probably flash the recovery with .IMG file with lg flashing tool. Nerdy blond's twrp is one of those files that you can use. You can even try installing it first with the adb shell command, you can get the instructions at the same place where you download.
http://forum.xda-developers.com/showthread.php?t=3144369
Click to expand...
Click to collapse
ShadySquirrel said:
If your phone shows LG start screen, it should go into Download mode. I had similar problem few days ago while I was testing some kernel patches, it just froze on the LG screen. Solution was to unplug it, remove it's battery, SIM & SD (you don't have to remove SIM & SD, I just work that way) , make sure it's off, return battery back, press Vol + & Vol - at the same time and plug-in the USB cable.
Before that, make sure you have installed LG Unified driver (can be obtained via LG's software from support site), because without that Windows won't recognise your device.
After that, once you make your phone usable with Freegee/whatever you use to install initial recovery, flash official TWRP, because others are too old - that Philz CWM is old but still working with Lollipop but not work good and is tends to lock itself into a bootloop if you use hardware keys to enter; that other one, from GPRO_recovery APK is not supported and not working well (for me since day one), so it should be replaced as soon as possible.
Also, I can suggest you to flash your phone from stock 4.1 (not KitKat), root, flash recovery via freegee and after reboot update to latest official TWRP via Flashify.
Click to expand...
Click to collapse
Thank you for your detail reply.
I have tried to reinstall the LG driver and try to enter download mode again.
The screen is still stuck on LG logo and I cannot find the device in hardware manager (cannot recognize it).
I cannot do anythings until it can recognize it.
(Is it the bootloader is broken? and can I fix it?)
Thank you very much and waiting for your reply soon.:good:

pchuen said:
Thank you for your detail reply.
I have tried to reinstall the LG driver and try to enter download mode again.
The screen is still stuck on LG logo and I cannot find the device in hardware manager (cannot recognize it).
I cannot do anythings until it can recognize it.
(Is it the bootloader is broken? and can I fix it?)
Thank you very much and waiting for your reply soon.:good:
Click to expand...
Click to collapse
Which version of Windows are you using? It should be displayed under Serial ports in Device manager (named something like LGE Serial device) and LGFlashTool should recognise it immediately. I can't make you a screenshot/check for real name because I'm running Linux right now and can't reboot.
Also, try with another cable/port, remove all other android drivers you may have (Samsung's, Google's...) and disable antivirus.

ShadySquirrel said:
Which version of Windows are you using? It should be displayed under Serial ports in Device manager (named something like LGE Serial device) and LGFlashTool should recognise it immediately. I can't make you a screenshot/check for real name because I'm running Linux right now and can't reboot.
Also, try with another cable/port, remove all other android drivers you may have (Samsung's, Google's...) and disable antivirus.
Click to expand...
Click to collapse
It does not work on Windows 7 and XP.
I did not find any LGE XXX under Serial ports part.
Thank you!

pchuen said:
It does not work on Windows 7 and XP.
I did not find any LGE XXX under Serial ports part.
Thank you!
Click to expand...
Click to collapse
Hm.... Phone shows that it have entered download mode? Black screen, centered gray message and "DOWNLOAD MODE" red text?

ShadySquirrel said:
Hm.... Phone shows that it have entered download mode? Black screen, centered gray message and "DOWNLOAD MODE" red text?
Click to expand...
Click to collapse
No... nothing happens, just showing LG logo...

pchuen said:
No... nothing happens, just showing LG logo...
Click to expand...
Click to collapse
OK, it doesn't enter download mode. So, step by step:
- remove battery and leave it for 15-30 seconds, return battery
- press Vol+ and Vol- at the same time and keep them pressed,
- plug USB cable in while keys are pressed
It should immediately put you into download mode, with no LG screen, just black screen with gray box and red text I've described to you.

ShadySquirrel said:
OK, it doesn't enter download mode. So, step by step:
- remove battery and leave it for 15-30 seconds,
- press Vol+ and Vol- at the same time and keep them pressed,
- plug USB cable in while keys are pressed
It should immediately put you into download mode, with no LG screen, just black screen with gray box and red text I've described to you.
Click to expand...
Click to collapse
I understand what download mode screen is.
I followed your methods, bur I still cannot enter it and the computer cannot recognize that.
Sorry for disturbing :crying:

pchuen said:
I understand what download mode screen is.
I followed your methods, bur I still cannot enter it and the computer cannot recognize that.
Sorry for disturbing :crying:
Click to expand...
Click to collapse
So, whatever you try to do, phone just shows LG logo, not even a message in an upper left corner?
I'm running out of ideas. I have exact same variant (E988) but only time it didn't want to enter download mode this way was when cable I was using was broken...

ShadySquirrel said:
So, whatever you try to do, phone just shows LG logo, not even a message in an upper left corner?
I'm running out of ideas. I have exact same variant (E988) but only time it didn't want to enter download mode this way was when cable I was using was broken...
Click to expand...
Click to collapse
I have changed the cable, but it is the same.

screwed my memory i think - not hard bricked but what is this? cant boot

after trying unsucessfully many times to get LVM to work I decided to go back to stock oppo recovery. I saw an option to unify memory in the oppo recovery and clicked that. My screen flashed for 30min with no reboot. I shut it down. This could have where it went wrong.
Now I cant boot into any recovery. Just stays stuck on the oppo logo. i DO have fastboot mode though and I CAN execute commands via the terminal/cmd prompt using adb/fastboot.
If I flash twrp, i can see it tries to boot into twrp with a blue flash of a screen but immediately it goes back to the oppo logo and stays there forever.
If I flash oppo recovery again, i can see it tries to go into oppo recovery but then the screen starts flashing bits and pieces of what I can make out as the oppo recovery.
Tried the unbrick method. I assume my memory is messed up because i tried to unify memory via the oppo recovery? I cant seem to do the unbrick method here: http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067. Tried it with win10 on test mode and cant get his specific driver names to work/show up. Shows up on mine as Marshall London boot loader or Android bootloader.
Also used the repartition tool repair scripts: http://community.oppo.com/en/forum.php?mod=viewthread&tid=20271&extra=. That did nothing. Black screen for about 1hr. Still have fastboot right now though. Still doing the same thing.
Any way to solve this? Thanks in advance to the pros at XDA!

THIS WORKED!! It took me very long to figure this out!!
http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra=&page=1
For that tutorial i had to deviate from the instructions ironically, if i held down power + up, it would take me to fastboot and i could NOT install the right drivers and it would come up as Marshall London Device (windows 10 with TESTSIGNING turned on). All I had to do was just plug into usb and NOT press or hold any buttons on the phone. Then it showed up as QHSUSB_BULK in device manager and I can proceed with this tutorial.

My XIAOMI MI A2 went to 0% and now it has a bootloop android one

I was playing normally the phone discharged turned off, and when I connect it only shows the android one screen over and over, the led that shows that it's charging doesn't turns on, I have nothing weird installed, didn't even knew about fastboot or roms, or anything like that until 15 minutes ago, so the fastboot options are not and cannot be activated, does it have a solution? do I just let it be connected for a few hours and try again, or what, i'm a noob on this matters so I don't know what to do. Thanks

maybe try holding vol down and power for 10 or more seconds. it should vibrate. it reboots and shows fastboot icon, you can flash stock rom again, let us know

loop4444 said:
maybe try holding vol down and power for 10 or more seconds. it should vibrate. it reboots and shows fastboot icon, you can flash stock rom again, let us know
Click to expand...
Click to collapse
The fastboot screen shows, but I can't do anything, and if I connect it to my PC after watching somethings like going to CMD and trying some commands the console doesn't even recognize those commands, maybe I have to install something for it to read it? I don't know, if this helps in anyway, I appreciate it.

M4N4GM said:
The fastboot screen shows, but I can't do anything, and if I connect it to my PC after watching somethings like going to CMD and trying some commands the console doesn't even recognize those commands, maybe I have to install something for it to read it? I don't know, if this helps in anyway, I appreciate it.
Click to expand...
Click to collapse
connect phone in fastboot mode and flash stock rom trough MiFlash, but remember to take backup of internal memory. I'll release all except external sd.

pawelik said:
connect phone in fastboot mode and flash stock rom trough MiFlash, but remember to take backup of internal memory. I'll release all except external sd.
Click to expand...
Click to collapse
Can you do the backup even if the phone can't start? does de MiFlash has that option? and thanks i'll try

M4N4GM said:
Can you do the backup even if the phone can't start? does de MiFlash has that option? and thanks i'll try
Click to expand...
Click to collapse
It seems that you didn´t enable USB debugging before, maybe? Did you solve it?

SubwayChamp said:
It seems that you didn´t enable USB debugging before, maybe? Did you solve it?
Click to expand...
Click to collapse
No I didn't enable the USB debugging, and no I haven't been able to do it, the mi flash program needs extra installations but always sends an error message and closes, I really don't know how to do this kind of things, I tried with a program called MiFlash Unlock, but it needs a Xiaomi account connected with the number and I don't have one, I really don't know what to do from here, plus I've read that I need the rom to install and don't know where can I find it and which one is the one that I need to install.
Once again thanks and if someone can help me further than this is appreciated

M4N4GM said:
No I didn't enable the USB debugging, and no I haven't been able to do it, the mi flash program needs extra installations but always sends an error message and closes, I really don't know how to do this kind of things, I tried with a program called MiFlash Unlock, but it needs a Xiaomi account connected with the number and I don't have one, I really don't know what to do from here, plus I've read that I need the rom to install and don't know where can I find it and which one is the one that I need to install.
Once again thanks and if someone can help me further than this is appreciated
Click to expand...
Click to collapse
Anyway you can't do many things although you should have enabled USB debugging atleast you decided to unlock device but fastboot is (almost) useless for device with locked boatloader.
The first thing I do no matter I don't think to root or modify my device is enabling USB debugging just to have more options to recover from an eventual brick.
Now try to do the next before to go to the other option; try to enter to recovery from device off, using volume up + power for some seconds then format/factory reset and let us know what happened.

SubwayChamp said:
Anyway you can't do many things although you should have enabled USB debugging atleast you decided to unlock device but fastboot is (almost) useless for device with locked boatloader.
The first thing I do no matter I don't think to root or modify my device is enabling USB debugging just to have more options to recover from an eventual brick.
Now try to do the next before to go to the other option; try to enter to recovery from device off, using volume up + power for some seconds then format/factory reset and let us know what happened.
Click to expand...
Click to collapse
That option didn't work, volume up + power just tried to start the phone

M4N4GM said:
That option didn't work, volume up + power just tried to start the phone
Click to expand...
Click to collapse
Ok, I supposed it, some partitions get corrupted while device fails to reboot.
Your last solution is using EDL mode, you will find many tutorials on YouTube to put device in this mode using test point method, then flashing the official stock rom through MiFlash tool.
To take in account MiFlash tool doesn´t work while in fastboot mode on devices with locked bootloaders so you have to use it in EDL (Emergency DownLoad) mode, no other workaround known on that. (for this model)
As reference I´ll put the basis of the links that you need to take a look in:
- Test Point method:
https://www.google.com/url?sa=t&rct...=XzknDcBovWw&usg=AOvVaw3gCAHutdqhO0Ukszyz-XJ-
- Drivers for unbrick qualcomm devices:
https://gsmusbdrivers.com/download/qualcomm-hs-usb-qdloader-9008-driver-64-bit-windows/
- Xiaomi Flash Tool:
https://xiaomiflashtool.com/download/xiaomi-flash-tool-20181115
- Fastboot images, you can use the latest:
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871

SubwayChamp said:
Ok, I supposed it, some partitions get corrupted while device fails to reboot.
Your last solution is using EDL mode, you will find many tutorials on YouTube to put device in this mode using test point method, then flashing the official stock rom through MiFlash tool.
To take in account MiFlash tool doesn´t work while in fastboot mode on devices with locked bootloaders so you have to use it in EDL (Emergency DownLoad) mode, no other workaround known on that. (for this model)
As reference I´ll put the basis of the links that you need to take a look in:
- Test Point method:
https://www.google.com/url?sa=t&rct...=XzknDcBovWw&usg=AOvVaw3gCAHutdqhO0Ukszyz-XJ-
- Drivers for unbrick qualcomm devices:
https://gsmusbdrivers.com/download/qualcomm-hs-usb-qdloader-9008-driver-64-bit-windows/
- Xiaomi Flash Tool:
https://xiaomiflashtool.com/download/xiaomi-flash-tool-20181115
- Fastboot images, you can use the latest:
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Click to expand...
Click to collapse
Thanks i'll try if it works

SubwayChamp said:
Ok, I supposed it, some partitions get corrupted while device fails to reboot.
Your last solution is using EDL mode, you will find many tutorials on YouTube to put device in this mode using test point method, then flashing the official stock rom through MiFlash tool.
To take in account MiFlash tool doesn´t work while in fastboot mode on devices with locked bootloaders so you have to use it in EDL (Emergency DownLoad) mode, no other workaround known on that. (for this model)
As reference I´ll put the basis of the links that you need to take a look in:
- Test Point method:
https://www.google.com/url?sa=t&rct...=XzknDcBovWw&usg=AOvVaw3gCAHutdqhO0Ukszyz-XJ-
- Drivers for unbrick qualcomm devices:
https://gsmusbdrivers.com/download/qualcomm-hs-usb-qdloader-9008-driver-64-bit-windows/
- Xiaomi Flash Tool:
https://xiaomiflashtool.com/download/xiaomi-flash-tool-20181115
- Fastboot images, you can use the latest:
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Click to expand...
Click to collapse
You should try the official and safer fastboot image.
http://c.mi.com/oc/miuidownload/detail?device=1700353

Little Hill said:
You should try the official and safer fastboot image.
http://c.mi.com/oc/miuidownload/detail?device=1700353
Click to expand...
Click to collapse
Wrongly quoted.

Midway

The guy that I'm helping fix his phone had was successful in flash the abl files now it's in a boot loop. I'm trying to connect to LG up to flash the firmware but I can't have the computer recognize the phone. I've used pretty much every variation of lg up and LG flash tool and the computer is not recognizing the phone in download mode. Any ideas or suggestions anyone? I think I have downloaded and installed all the visual c++ distributable files. Even in device manager I change the com to com 41

Rootmaster906 said:
The guy that I'm helping fix his phone had was successful in flash the abl files now it's in a boot loop. I'm trying to connect to LG up to flash the firmware but I can't have the computer recognize the phone. I've used pretty much every variation of lg up and LG flash tool and the computer is not recognizing the phone in download mode. Any ideas or suggestions anyone? I think I have downloaded and installed all the visual c++ distributable files. Even in device manager I change the com to com 41
Click to expand...
Click to collapse
Instead of doing what you're doing, do the hard factory reset button combination, if you've installed a custom recovery.

Keno_I said:
Instead of doing what you're doing, do the hard factory reset button combination, if you've installed a custom recovery.
Click to expand...
Click to collapse
I can't. I can't access recovery or fastboot. I changed the active slot to a different one due to the fact I could not access download mode. And when I had the other slot active, it would boot to stock recovery and just hang. Then it bootloped again. I did the power button then volume up to enter recovery, but it looped.

Sorta/Kinda Brick After Attempted TWRP Install - Moto G7 Play 1952-4

Ok, so I’ve run myself off the road into a deep hole and am hoping someone can help me climb out and get back onto the correct path.
I have a Motorola Moto G7 Play 1952-4 (channel). My goal is to install TWRP, and LineageOS 18.1 with GAPPS. Root is not important at the moment.
Here’s what I did:
After successfully unlocking the bootloader (thank you Motorola), I downloaded TWRP for Chanel from the TWRP.me site. My plan was to first install TWRP, then use TWRP’s install feature for LoS 18.1 and the GAPPS.
To install TWRP recovery, I followed the instructions on the TWRP site. After starting the ADB server on my Windows 10 PC and booting the phone into the stock recovery, I used “adb boot twrp-3.5.2_10-0-channel.img” to temporarily boot into TWRP recovery. I then used ADB to push TWRP.zip onto the internal SDCARD. I used TWRP’s install feature to install "twrp-installer-3.5.2_10-0-channel.zip", presumably to both slots. To the best of my memory, everything completed correctly.
BUT . . . when I powered down the phone and attempted to boot into recovery, all I got was a black screen with a small N/A in the upper left corner instead of the familiar TWRP screens. After a while, the phone booted itself into the stock U.S. Cellular Android 10 (Hell Oh - Moe Toe). I've done several power-off/power-on cycles to no avail. I am able to get to and use the stock OS.
So, like TWRP.me suggests, I figured I’d just flash it back to stock and start over. Um, nope. I can Vol-DN/Power to the bootloader menu, but “adb devices” doesn’t see the phone, preventing me from flashing anything. USB Debugging is enabled and the phone says "USB Transfer Mode: Connected". “adb devices” sees the phone while Android 10 is running, but as soon as I boot into recovery, the phone “disappears” from ADB.
The only other thing I could think to do was to use the “Rescue” function in the Lenovo/Motorola Smart Assistant. While ADB can’t see the phone, LMSC sees it just fine and I was able to rescue/reinstall the stock OS successfully, or so LMSC said. Unfortunately, LMSC doesn’t seem to fix whatever is wrong with the recovery. Interestingly, “N/A” no longer appears after Vol-DN/Power and select Recovery Mode, the black screen now says “bad key”, followed a little while later by the Android logo with a “!” in the middle of the screen and “No command” below it.
And that’s the hole I now reside in. Despite considerable searching/reading here at XDA, I'm at a total loss for what to do next.
SOOOO, I’m hoping someone can help me:
1. Fix the N/A black screen
2. Get into a mode that ADB can see
3. Properly install TWRP
Thank you in advance,
Tenaya

Did you flash the copy-partitions.zip while in TWRP?
Maybe you could borrow some ideas from the official install instructions for LineageOS.
Install LineageOS on channel | LineageOS Wiki
wiki.lineageos.org
I had some strange intermittent USB connectivity issues with a few Moto G7 Plus devices with my main laptop, but was fine connecting on a 12 year old desktop computer. So perhaps you could check to see if adb connects on another machine. Only other idea I have is to somehow flash back to stock again with fastboot.
[Guide][Channel][Stock]Moto g7 play Factory Firmware Images
Moto g7 play Android 9 and 10 Factory Firmware Stock Images Info Updated on 23-11-2020 Hi there. I have found the moto g7 play stock images mirrored in lolinet servers for Android 9, and from motorola servers for Android 10. Go and download...
forum.xda-developers.com

zpunout,
Thank you for your response.
zpunout said:
Did you flash the copy-partitions.zip while in TWRP?
Click to expand...
Click to collapse
No, I didn't know I needed to; nothing about that is mentioned by TWRP.me.
This is unknown territory for me, but your question sparks a thought for me. I wonder if 1) The stock recovery is in the "other" slot, and 2) there is some way to boot from it. That could be a way to sidestep the ADB devices problem I'm having?
zpunout said:
So perhaps you could check to see if adb connects on another machine.
Click to expand...
Click to collapse
At the moment, I have no way to do that. I don't think the USB connection is the culprit, ADB "sees" the phone just fine while the phone is in the stock OS, just not in recovery (EDL?.
zpunout said:
Only other idea I have is to somehow flash back to stock again with fastboot.
Click to expand...
Click to collapse
That's my current plan, but FASTBOOT won't flash anything while ADB devices won't/can't see the phone. I'm hoping someone has a workaround of some sort for that.
Tenaya

Hi, first of all lets set some things straight, you are experiencing a Boot Loop, in other words a software brick. (Soft Brick) now luckily these are fairly simple to fix. Sorry to break it to you but the N/A Screen won't disappear, that used to be the Blue/Yellow Motorola Splash Screen, but since you unlocked your phone it'll only show N/A but thats okay there are tools that can help you customize this and change it later on.
Now why is it on a boot loop you may ask, well that is because there is no more operating system to load in. But worry not, try to get into your bootloader, and try to connect adb through there.
Tenaya43 said:
Ok, so I’ve run myself off the road into a deep hole and am hoping someone can help me climb out and get back onto the correct path.
I have a Motorola Moto G7 Play 1952-4 (channel). My goal is to install TWRP, and LineageOS 18.1 with GAPPS. Root is not important at the moment.
Here’s what I did:
After successfully unlocking the bootloader (thank you Motorola), I downloaded TWRP for Chanel from the TWRP.me site. My plan was to first install TWRP, then use TWRP’s install feature for LoS 18.1 and the GAPPS.
To install TWRP recovery, I followed the instructions on the TWRP site. After starting the ADB server on my Windows 10 PC and booting the phone into the stock recovery, I used “adb boot twrp-3.5.2_10-0-channel.img” to temporarily boot into TWRP recovery. I then used ADB to push TWRP.zip onto the internal SDCARD. I used TWRP’s install feature to install "twrp-installer-3.5.2_10-0-channel.zip", presumably to both slots. To the best of my memory, everything completed correctly.
BUT . . . when I powered down the phone and attempted to boot into recovery, all I got was a black screen with a small N/A in the upper left corner instead of the familiar TWRP screens. After a while, the phone booted itself into the stock U.S. Cellular Android 10 (Hell Oh - Moe Toe). I've done several power-off/power-on cycles to no avail. I am able to get to and use the stock OS.
So, like TWRP.me suggests, I figured I’d just flash it back to stock and start over. Um, nope. I can Vol-DN/Power to the bootloader menu, but “adb devices” doesn’t see the phone, preventing me from flashing anything. USB Debugging is enabled and the phone says "USB Transfer Mode: Connected". “adb devices” sees the phone while Android 10 is running, but as soon as I boot into recovery, the phone “disappears” from ADB.
The only other thing I could think to do was to use the “Rescue” function in the Lenovo/Motorola Smart Assistant. While ADB can’t see the phone, LMSC sees it just fine and I was able to rescue/reinstall the stock OS successfully, or so LMSC said. Unfortunately, LMSC doesn’t seem to fix whatever is wrong with the recovery. Interestingly, “N/A” no longer appears after Vol-DN/Power and select Recovery Mode, the black screen now says “bad key”, followed a little while later by the Android logo with a “!” in the middle of the screen and “No command” below it.
And that’s the hole I now reside in. Despite considerable searching/reading here at XDA, I'm at a total loss for what to do next.
SOOOO, I’m hoping someone can help me:
1. Fix the N/A black screen
2. Get into a mode that ADB can see
3. Properly install TWRP
Thank you in advance,
Tenaya
Click to expand...
Click to collapse

HellxDo,
Thanks for the reply.
After I used LSMC to "rescue" the phone, it stopped displaying N/A" and began showing "Bad key". Different, but not better.
HellxDo said:
Now why is it on a boot loop you may ask, well that is because there is no more operating system to load in.
Click to expand...
Click to collapse
Hmmm . . . The phone currently boots into the stock rom (U.S. Cellular Android 10) if I wait a while after "Bad key" displays. If there's no more OS to load in, how do it do dat?
HellxDo said:
But worry not, try to get into your bootloader, and try to connect adb through there.
Click to expand...
Click to collapse
My (limited) understanding is that the only way to "get into" my bootloader was with the Vol-DN/PWR button combination. When I do that , I get the bootloader menu, but ADB doesn't/can't see the phone - nothing is listed when I run ADB devices and fastboot won't/can't flash anything.
Is there a different/better way to get into my bootloader?
Tenaya

And the adventure continues. Here's some more information.
While continuing to research this, I was wondering if there was another way to boot the phone into EDL mode and Google found some instructions at thecustomdroid.com for using ADB to boot the phone into EDL. I booted the phone to the stock OS and used the command adb reboot edl. The phone immediately went blank, followed shortly by the "bad key" message. After a while it again booted into the stock rom.
I still cannot use fastboot because it doesn't/can't see the phone.
I have also discovered that if i use VOL-UP/PWR, the phone boots directly to "bad key", followed by the stock rom. Another dead end.
I also used LMSC to "Rescue" the phone again and learned several things:
While LMSC is running, it boots the phone into the bootloader menu and begins to flash. If I do adb devices while LMSC is flashing, the phone STILL doesn't appear in the list.
LMSC definitely flashed the stock OS - when the phone rebooted, it was back to the stock OS Android start screen as if it had never been configured.
There is still no recovery and I still can't flash anything.
LMSC is somehow able to flash without a recovery present.
Anyone have any other ideas?
Tenaya

Tenaya43 said:
And the adventure continues. Here's some more information.
While continuing to research this, I was wondering if there was another way to boot the phone into EDL mode and Google found some instructions at thecustomdroid.com for using ADB to boot the phone into EDL. I booted the phone to the stock OS and used the command adb reboot edl. The phone immediately went blank, followed shortly by the "bad key" message. After a while it again booted into the stock rom.
I still cannot use fastboot because it doesn't/can't see the phone.
I have also discovered that if i use VOL-UP/PWR, the phone boots directly to "bad key", followed by the stock rom. Another dead end.
I also used LMSC to "Rescue" the phone again and learned several things:
While LMSC is running, it boots the phone into the bootloader menu and begins to flash. If I do adb devices while LMSC is flashing, the phone STILL doesn't appear in the list.
LMSC definitely flashed the stock OS - when the phone rebooted, it was back to the stock OS Android start screen as if it had never been configured.
There is still no recovery and I still can't flash anything.
LMSC is somehow able to flash without a recovery present.
Anyone have any other ideas?
Tenaya
Click to expand...
Click to collapse
If "fastboot devices" can't see your device while in bootloader mode, that could be the same issue I had relating to your USB compatibility with your computer. Try to borrow someone else's computer, install "platform-tools" to see if the "fastboot devices" command works.
If that works, next see if the command "fastboot getvar all" works. You should get many lines of info come up. If it gets stuck after a couple of lines, then the symptoms are the same as what I had. I have a bunch of really old laptops and a desktop sitting around with platform-tools just for this issue. I have heard others say that plugging the phone in via a USB hub sometimes gets fastboot to connect properly, but I haven't had success yet.

OK, some progress.
I found this:
[GUIDE][TOOL] Reboot to EDL mode from FASTBOOT! No More "Test Point Method"! [kenzo]
kenzo has graciously hacked fastboot.exe to force the phone into EDL mode. Using that, the phone booted into EDL and fastboot devices can now "see" the phone. Thank you kenzo.
BTW, kenzo's fastboot-edl isn't G7 Play specific, it was originally for the Xiaomi Redme Note 3 and seems to work for some other Android phones as well.
I'm still working on getting TWRP and LoS installed, but at least fastboot can talk to the phone.
zpunout said:
I have heard others say that plugging the phone in via a USB hub sometimes gets fastboot to connect properly
Click to expand...
Click to collapse
I also had no luck with a USB hub.
I haven't tried another computer yet; I'm going to see what I can accomplish with fastboot-edl.
Tenaya

fastboot oem blankflash