Database Users

[Answers] Solutions to Common Problems - Look Here Before Posting in Q&A

The purpose of this thread is to hopefully limit the number of repeat questions / calls for help in Q&A.
(if I see one more request to help fix a boot loop I'm going to strangle someone! )
The first place you should always look for information is the Beginners Guide. Tons of good stuff there.
If anyone has any additional helpful information, post below and I will add it to the OP.
If you find that any of the links are broken, please let me know so I can fix them.
If files are not available at the linked resource, they are available at the bottom of this post.
And always remember xda rule #1:
"Search before posting: Use one of our search functions before posting, whether you have a question or something new to share, it's very likely someone already asked that question or shared that news."
ADB not connecting to / can't find device:
Check to make sure you have the correct drivers installed on your PC.
Try disconnecting then reconnecting USB cable from PC.
On your PC open task manager, kill all instances of adb.exe, then start again.
Battery won't charge to 100%
1) Pull battery while charging
2) Wait for the question mark, then replace battery
3) Let battery charge for 1-2 hours
4) Wipe battery stats in CWM
Or try ravilov's Battery Fix app.
Battery too Low to Recover from Problem
Charge your battery with a wall charger, or use a USB cable.
Boot Loop
1) Pull battery
2) Replace battery while holding the volume down button
3) Use volume down to navigate to either recovery or fastboot, then press volume up
Once in:
Recovery - restore your backup or re-flash ROM
Fastboot - flash newer version of recovery or re-flash ROM
Fastboot Information
See post #2
Hard Brick
Consider using your device as a paperweight or doorstop. (or donate it to a dev)
Maybe if you are really lucky, something here might help.
Ram Low After Bootloader Unlock
Ramfix
Recovery Not Working (Just Rooted & Unlocked Bootloader)
You most likely followed a guide or used an automated tool with an outdated version of recovery.
Download the most recent version of CWM, then flash with fastboot (see post #3).
Return to Stock
The best and safest way to return to stock is by restoring the nandroid backup you made when you first installed CWM.
The next best way to return to stock is by flashing a fruit cake with CWM. Fruitcakes can be found here, and at the two links on the bottom of this post. There are some international fruit cakes available at the Atrix Reboot Project.
The third option is to fastboot flash a boot and system image (see post #4) from a fruit cake (links below). Or, fastboot flash a stock nandroid backup.
The least safe and least desirable method is to flash an sbf. This should only be used as a last resort (see entry for Hard Brick).
Rooting
The easiest way to root: Link
The way that you will learn something: Link1 Link2
There is not an established method for rooting the newest OTA (4.5.145). Exiting methods are hit or miss.
Sleep of Death (SOD)
Some users have had success with doubling the minimum CPU clock speed.
With CM7/9/10 you can adjust the clock speed in settings. Otherwise, try SetCPU.
This problem is not well understood, and usually the only real cure is returning to stock.
Soft Brick (Failed to boot XXXX)
Read this post, install software (Iinked below), select option 3.
Soft Keys not Working
Try Button Savior from the Play Store
Touchscreen - Dead Spot Quick Fix
Link
Touchscreen Replacement
Link
YouTube Video
_______________________________
Information Resources:
Atrix 4G Information Repository
_______________________________
File Resources:
A lot of the links in this forum are dead. But thanks to SamCripp and Zeljko1234, many of the files can be found below.
Atrix Reboot Project
[Fruit Cakes] Kernel, Unlock - Backup links
_______________________________
Downloads:
My AFH Atrix Folder
_______________________________

Setting up fastboot and ADB
Useful fastboot info and commands: Link1 Link2
1) Download and install 7Zip
2) Download and extract attached fastboot & ADB file
3) Download and install Motorola drivers
4) Create a new folder on your hard drive named "Android" (c:\Android)
5) Place all contents of the fastboot & ADB folder (5 files) in "Android" folder
6) Attach your phone to the PC via USB (use a port closest to the power supply)
7) In the USB settings make sure USB Mass Storage is selected
8) Reboot phone while holding volume down until you see "fastboot"
9) Press volume up to initiate fastboot
10) On your PC click the Start menu, then in the search box type "cmd"
11) In the command prompt type the following commands (no quotes, hit enter after each command)
11a) "cd c:/android"
11b) "fastboot devices"
If fastboot is working properly you should see something that looks like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Me>cd c:/android
c:\Android>fastboot devices
TA20703SX9 fastboot
c:\Android>

Flashing recovery with fastboot
1) Set up fastboot as described in post #2
2) Download the most recent CWM available Link
3) Place recovery image in c:\Android
4) Type the following commands (no quotes, hit enter after each command)
4a) "fastboot flash recovery recovery-clockwork-5.0.2.0-olympus.img" (note: the name of your recovery image may be different)
4b) "fastboot reboot"
If everything was successful, you should see something like this:
Code:
c:\Android>fastboot flash recovery recovery-clockwork-5.0.2.0-olympus.img
sending 'recovery' (4824 KB)... OKAY [ 0.575s]
writing 'recovery'... OKAY [ 0.592s]
finished. total time: 1.169s
c:\Android>fastboot reboot
rebooting...
finished. total time: 0.002s
c:\Android>

Fastboot flashing boot and system images - Returning to Stock
1) Set up fastboot as described in post #2
2) Download one set of boot and system images from post #1, or unzip a fruit cake and use those images.
3) Place boot and system images in c:\Android
4) Type the following command (no quotes, hit enter after each command)
4a) "fastboot erase cache"
4b) "fastboot erase userdata"
4c) "fastboot flash boot boot.img"
4d) "moto-fastboot flash system system.img"
4e) "fastboot reboot"
If successful, you should see something like this:
(Note: If you forget to use moto-fastboot to flash the system image (like I did), you will see the "INFOImage too big" error.)
Code:
c:\Android>fastboot erase cache
erasing 'cache'... OKAY [ 2.073s]
finished. total time: 2.073s
c:\Android>fastboot erase userdata
erasing 'userdata'... OKAY [ 5.393s]
finished. total time: 5.394s
c:\Android>fastboot flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 0.979s]
writing 'boot'... OKAY [ 0.610s]
finished. total time: 1.591s
c:\Android>fastboot flash system system.img
sending 'system' (327680 KB)... INFOImage is too big, use 0x10000000 bytes chunks
FAILED (remote: (00000006))
finished. total time: 0.001s
c:\Android>moto-fastboot flash system system.img
sending 'system' (262144 KB)... OKAY [ 29.155s]
writing 'system'... OKAY [ 13.965s]
sending 'system' (65536 KB)... OKAY [ 7.582s]
writing 'system'... OKAY [ 3.442s]
c:\Android>fastboot reboot
rebooting...
finished. total time: 0.010s
c:\Android>

Miscellaneous
All:
Set up fastboot as described in post#2
Place .img in c:\Android
Fastboot flash radio
fastboot flash radio radio.img
fastboot reboot
Fastboot flash boot logo
fastboot flash logo logo.bin
fastboot reboot

Reserved 3

Reserved.

Thank you so much for sharing these with us!!!!!:good:

Awesome post!

a lot of useful information =) this help me a lot

Excellent compilation !!
This is a one stop thread for those Atrix owners looking to get their doubts and queries about the bootloader unlocking procedure answered comprehensively. It sure did that for me!!

In Atrics (CM9) - 14/11/12, every time the super user privileges to provide a program, get the reboots when the screen turns off. The super user is already updated and nothing!

freezerj said:
In Atrics (CM9) - 14/11/12, every time the super user privileges to provide a program, get the reboots when the screen turns off. The super user is already updated and nothing!
Click to expand...
Click to collapse
Reinstall the rom
Enviado desde mi MB860 usando Tapatalk 2

HDMI Problem
hello guys, sorry if i didn't follow rules, but maybe some1 can answer me.
i have HDMI mirroring problem. when i attach phone on Lapdock, it says No Signal, Input : HDMI.
any solutions?

I'm using a jb custom rom and the 3g sometimes turns itself on without me initiating it! Any ideas?
Spilled from my Atrix4g utilizing Tapatalk

This is not a help thread.
Questions go in Q&A.
Please keep the discussion relevant to info in the OP.
Thanks!

Incoming Calls no contact Names
I have recently installed miui android version 4.1.2(MIUI 2.12.7)
However I everytime i get a call, the caller's name is not shown and instead i get to see only the number in the format +254722XXXXXX!! This despite having saved the contacts name and number in my google account which is synced. Im using a motorola Atrix (MB860),Carrier is Airtel Kenya
thanks in advance for any help

In case of infinite loop - Alternative method
Yeah,
I tried another method that worked like a charm for me :
- Start in fastboot mode (maintain power + volume down --> repeat down to choose fastboot --> validate with up volume)
- On your computer, open "cmd" command (windows + R --> CMD)
- Type : "fastboot -w" this command will erase user data
- Type : "fastboot reboot"
That is all.

Amazon Moto G4 bootloaders can't be unlocked?

I've followed a couple tutorials of that explain how to unlock Motorola's Moto G4 bootloader. This seems to be the "official" one from Motorola:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
I copied part of it up to where I get stuck. Here it is:
Put your device in fastboot mode (power off, then press the power and volume down buttons simultaneously).
On your desktop, open a command prompt or terminal, and go to the directory where you installed the Android SDK tools (or make sure fastboot is in your $PATH)
At the prompt, type $ fastboot oem get_unlock_data
The returned string will be used to retrieve your unlock key.
Example: On a Windows Desktop, the returned string format would be $ fastboot oem get_unlock_data
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
****************************************
OK, so I just bought a Moto G4 for $125 on Amazon's prime day. This means that it has ads on the lock screen. I'm OK with that. But I think they also made the locked bootloader unlocakble as 3 times I've gotten this from a Windows machine in ADB mode:
(bootloader) Unlock data:
(bootloader) 3A45210407248602#
(bootloader) 5A59323233433246534C004D6F746F2047200000#
(bootloader) 1095EFAB6000EDC14660539C503A04F7900B9A01#
(bootloader) 9F93C800000000000000000000000000
There should be numbers in that first Bootloader line and then Motorola says:
You're device does not qualify for bootloader unlocking.
Has anybody else had this happen? This is my second time doing this to a Motorola phone and the Moto g2 was a snap! I was hoping to install a custom recovery like TWRP so I could get a nandroid backup while everything is new
Marty

LinuxHippy said:
You're device does not qualify for bootloader unlocking.
Has anybody else had this happen? This is my second time doing this to a Motorola phone and the Moto g2 was a snap! I was hoping to install a custom recovery like TWRP so I could get a nandroid backup while everything is new
Marty
Click to expand...
Click to collapse
A Lot of us have already unlocked our bootloader

Rempala said:
A Lot of us have already unlocked our bootloader
Click to expand...
Click to collapse
Do u have the Amazon moto g4?

I do and I unlocked my bootloader and rooted the phone already.

Yes I have the Amazon G4

Well, these posts gave me hope that I was repeating the same mistake and I was. Forth time worked to unlock the BL. I was deleting the # signs at the end of each line. That was the mistake. It should be this from 4 lines:
3A45210407248602#5A59323233433246534C004D6F746F2047200000#1095EFAB6000EDC14660539C503A04F7900B9A01#9F93C800000000000000000000000000
Now I'm trying to boot into the TWRP image I flashed with fastboot and fastboot gave me errors about it not being signed so I'm not sure it worked. Where are people here getting the Moto g4 TWRP images? I went here:
https://www.androidfilehost.com/?w=...23bf15e9165ccc3b437c48af2047195d3fae863dca817

This is what I get when I try to flash TWRP now and then reboot into it with adb:
C:\Users\Huntz\Downloads>fastboot devices
ZY223C2FSL fastboot
C:\Users\Huntz\Downloads>fastboot flash recovery twrp_athene_20160526.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (12498 KB)...
OKAY [ 0.398s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.344s]
finished. total time: 0.746s
C:\Users\Huntz\Downloads>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: no devices/emulators found

Just FYI, Motorola's bootloader unlock website has a webtool that you can use to clean the output of get_unlock_data, so you'll only get the relevant info. Copy-paste the raw code into the tool, hit clean, copy paste the output into the unlock code line on the website, submit.
Regarding TWRP, yes I think everyone gets that "Image not signed or corrupt" message. Also, you can't "adb reboot recovery" from fastboot. Just flash it via fastboot, reboot into fastboot, then go into recovery.

Maybe it did install twrp OK since it still boots into the original stock ROM OK. How do u get into twrp with the buttons on the phone?

LinuxHippy said:
Maybe it did install twrp OK since it still boots into the original stock ROM OK. How do u get into twrp with the buttons on the phone?
Click to expand...
Click to collapse
Boot into fastboot (press and hold power + volume down, let go when the bootloader screen shows up), press down on the volume rocker twice, and it'll say "recovery mode" on the screen. Press power once and it'll boot into TWRP.

Something's wrong then. I get to the fastboot screen OK but when I go into recovery it says your device has been unlocked and can't be trusted. It will reboot in 5 sec and then I see a dead robot.
EDIT
it does boot OK into the stock ROM from there if u do nothing for a minute or two or if u just hold in power button for 15 secs to get a black screen and then release the button and hold it 4 secs to get a normal boot

Sounds like TWRP didn't flash correctly, or maybe was a bad download (can download directly from TWRP's website here: https://dl.twrp.me/athene/). Reboot back into fastboot and try flashing TWRP again (you might also want to try renaming it to recovery.img, so the flashing command would be "fastboot flash recovery recovery.img").

I'll try again later today-hopefully it works and thanks for the link
I'm gonna try doing adb in Linux too.

xtermmin said:
Sounds like TWRP didn't flash correctly, or maybe was a bad download (can download directly from TWRP's website here: https://dl.twrp.me/athene/). Reboot back into fastboot and try flashing TWRP again (you might also want to try renaming it to recovery.img, so the flashing command would be "fastboot flash recovery recovery.img").
Click to expand...
Click to collapse
When u reboot now, do u get a 5 second delay screen that says your device has been unlocked and can't be trusted?
Marty

LinuxHippy said:
When u reboot now, do u get a 5 second delay screen that says your device has been unlocked and can't be trusted?
Marty
Click to expand...
Click to collapse
Yes, that is normal for devices with unlocked bootloaders. You can get rid of it by rebooting into fastboot and following this guide: http://forum.xda-developers.com/showpost.php?p=67031810&postcount=5
(if you don't have mfastboot, you can use plain-old fastboot as well)

I'm puzzled-the md5 on twrp was right and I unlocked the BL OK. I'll try it in Linux later and see if it takes.

Might be worth trying another USB port or even another cable. Some people have issues when trying to flash things on a USB 2.0 phone plugged into a USB 3.0 port.

About how much time should it take to flash twrp? I don't think it even flashed anything yesterday because it was too quick.

LinuxHippy said:
About how much time should it take to flash twrp? I don't think it even flashed anything yesterday because it was too quick.
Click to expand...
Click to collapse
It is almost instantaneous. As for the booting into recovery and seeing the dead robot, that is probably due to the fact that the phone tries to re-write the recovery when you reboot automatically. Just flash the twrp.img, and then go to recovery from the bootloader without rebooting and you will be fine; just make sure you have whatever you want to flash (e.g. supersu) on your device storage when you get there.

Sounds like a plan! What's the md5 on the supersu file?

Looking for HTC Desire 820n Stock MM ROM Single sim

Hello Guys. I looking for Looking for HTC Desire 820n Stock Marshmallow ROM. I downloaded one from this forum, but it doesn't work, dunno why. Could you help me?
A51_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-01.01.010_U10305041_08.01.50512
OS-2.10.401.4
eMMC-boot 2048 OC
TWRP ver. 2.8
Already I using Tomal's Discovery v2.00
Thx for help.

Hello!
Here it is:
https://mega.nz/#!h1ghSaBA!gE3Sfsfcebdk0tyStLe5VFhYOfUia0gcvLkiV2zShRE
But i recommend you to do OTA update to Marshmallow
If you want to do that:
1) Download Stock Recovery: https://mega.nz/#!UkJRGKRB!nAPzWOobSYsVxTTrF5e0xtZVIL-5Mxh6nrVW84B-dVo
2) Download Lollipop RUU: https://mega.nz/#!F9QVgIZD!QopXqw1IPYhoo540nJn77vzJIanIanSeM6APMaoc1vc
3) Lock bootloader
4) Place Lollipop RUU to SD Card and rename file to 0PFJIMG.zip
5) Do OTA Update to Marshmallow
Cheers!

Ty so much man, I'll check this soon

Could you tell me two things: How to lock bootloader and how can I install stock recovery? Sorry for my knowledge ;__;

To install stock recovery:
1) Reboot to bootloader (Turn off phone, then press volume down and Power Button)
2)Click "Fastboot" (Just press Power Button)
3)Connect phone to PC
4)Install ADB 15 seconds installer (Google It! ?)
5)After instalation go to C:/ADB folder then press shift and right mouse Button then click "Open Command prompt)
6)Download stock recovery image (from #1 post)
7)Place it to C:/ADB folder
8)In command prompt type "Fastboot flash recovery (filename)"
To lock bootloader:
1)After installing stock recovery type In Command prompt: "Fastboot oem lock"
Cheers!

I've got sth like this after I typed a command in cmd:
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 7758080 is not a multiple of the block size 4096
sending sparse 'recovery' (14703 KB)...
error: write_sparse_skip_chunk: don't care size 7758080 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 7758080 is not a multiple of the block size 4096
OKAY [ 1.694s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.704s

This is fixed ADB for this device: https://yadi.sk/d/v5Yp8iAtuHdQE
Download and replace all files In C:/ADB folder
And try again!

Thanks man for help! But this is something like hydra head- one problem solved, and we gain two new problems. Now rebooting phone to ROM is not available, stucked on bootloader. However, when I try to go into recovery i have this:http://obrazki.elektroda.pl/6530102200_1432399738.jpg

To enter stock recovery launch It then press Power and volume up Button
P.s are you from Poland?

Do you mean to click "Recovery" in bootloader and next hold vol up and power button? Doesnt working, still this same image ;/
Yes, I'm from Poland

Just keep pressing buttons randomly
######
Ja też jestem z Polski

Priv then
________
Masz piwo u mnie

HI, would you please give new links to the same files, these are dead already - my phone got bricked after system update tried. (it was rooted, but no more) - there is no OS now : ) it`s exactly the same model as the one metnioned above. It will be much appreciated, really!

Hello. Pleaze i née thé ruu for htc desire 820n. Thanks

Could someone throw again mega.co files as expired?

Hello!
MEGA has removed my files (don't know why)
Stock recovery: https://yadi.sk/d/v5Yp8iAtuHdQE
Lollipop RUU: https://yadi.sk/d/KYcWwUH4raUxm
Marshmallow RUU: https://yadi.sk/d/lWwMzPdNuHc3X
Cheers!

I started uploading 0PFJIMG.zip, after a while the phone is switched off and started flashing orange LED. The phone was connected to the computer. After disconnecting the phone can not start. Once reconnected to the computer is still flashing orange flashes. What should I do? Key combinations do not work

Fr4gMovi3 said:
To install stock recovery:
1) Reboot to bootloader (Turn off phone, then press volume down and Power Button)
2)Click "Fastboot" (Just press Power Button)
3)Connect phone to PC
4)Install ADB 15 seconds installer (Google It! ��)
5)After instalation go to C:/ADB folder then press shift and right mouse Button then click "Open Command prompt)
6)Download stock recovery image (from #1 post)
7)Place it to C:/ADB folder
8)In command prompt type "Fastboot flash recovery (filename)"
To lock bootloader:
1)After installing stock recovery type In Command prompt: "Fastboot oem lock"
Cheers!
Click to expand...
Click to collapse
my bootloader doesn't lock. how to lock?

domell98 said:
I started uploading 0PFJIMG.zip, after a while the phone is switched off and started flashing orange LED. The phone was connected to the computer. After disconnecting the phone can not start. Once reconnected to the computer is still flashing orange flashes. What should I do? Key combinations do not work
Click to expand...
Click to collapse
I don't know... But you should place this file in sd card... Try launch bootloader and flash TWRP recovery and then push file to SD Card....

HELP!!!!!
i need official stock rom of htc Desire 820n(single sim)...its urgent
A51_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
radio-01.01.010_U10305041_08.01.41222_2
OS-1.29.401.5
eMMC-boot 2048 MB oc

Help~ US LEX727, fastboot oem unlock-go failed after TWRP restore

A brand new LE Pro 3, LEX 727.
EUI Version 5.8.021S
This is what I did:
Enable the Developer Option. Enable OEM Unlocking and USB Debugging
boot phone to fastboot mode, then connect to PC.
> fastboot oem unlock-go
> fastboot format userdata
> fastboot boot twrp-3.2.1-0-zl1.img
The phone enter TWRP, then in TWRP, I did
(1) backup,
(2) wipe (advanced wipe, select system, data, dalvik/ART cache, cache)
(3) Restore using backup created in step 1
After restore and reboot, the phone back to original.
Then I did:
1. Enable the Developer Option.
2. Enable OEM Unlocking and USB Debugging
3. ReBoot Phone to fastboot mode (Volume Down + Power button) and connect to PC.
4. fastboot oem unlock-go
Weird, this time it failed:
C:\adb>fastboot oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.006s
How can this happen? How to fix it???
Thanks!

rogerxda2018 said:
A brand new LE Pro 3, LEX 727.
EUI Version 5.8.021S
This is what I did:
Enable the Developer Option. Enable OEM Unlocking and USB Debugging
boot phone to fastboot mode, then connect to PC.
> fastboot oem unlock-go
> fastboot format userdata
> fastboot boot twrp-3.2.1-0-zl1.img
The phone enter TWRP, then in TWRP, I did
(1) backup,
(2) wipe (advanced wipe, select system, data, dalvik/ART cache, cache)
(3) Restore using backup created in step 1
After restore and reboot, the phone back to original.
Then I did:
1. Enable the Developer Option.
2. Enable OEM Unlocking and USB Debugging
3. ReBoot Phone to fastboot mode (Volume Down + Power button) and connect to PC.
4. fastboot oem unlock-go
Weird, this time it failed:
C:\adb>fastboot oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.006s
How can this happen? How to fix it???
Thanks!
Click to expand...
Click to collapse
Roger, I thought that I messaged you earlier but I see that it wasn't posted. I just answered your PM
So check your messages
Edit: It failed, because you restored the locked emmc_appsboot.mbn
after you prepare the phone for unlocking the bootloader, make sure that you remove any passwords, this way you will not have any storage encryption issues.
---------- Post added at 12:19 AM ---------- Previous post was at 12:17 AM ----------
tsongming said:
Roger, I thought that I messaged you earlier but I see that it wasn't posted. I just answered your PM
So check your messages
Click to expand...
Click to collapse
This is message 2.
The Pie Rom that you choose is a bad choice > It's not longer supported. We can talk on the phone if your timezone is close to mine . For me its 11:30pm Est.
I will be awake for about another hour. Otherwise, I can help you tomorrow. If you get this message tonight, message me ASAP
Next: Here is a link with the essential steps ( some of which you have found)
https://forum.xda-developers.com/showpost.php?p=75009966
Your Rom is an Alpha build. If You want Android 9.0 Pie > choose something recent such as Lineage 16.0, or AICP 14 These are great Roms and the developers currently have working Le Pro 3's.
If you still want or need help, I can help you on the phone or maybe use Team-Viewer.
Have these things ready
Your Rom of Choice
Recent Gapps ( Ex: open_gapps-arm64-9.0-nano) Here: https://opengapps.org/
TWRP : ( This One twrp-3.2.3-1-zl1 : https://dl.twrp.me/zl1 )
Magisk 17.3 ( https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)

Thank you!!! I sent you a PM, I will download the software you mentioned before we connect.
tsongming said:
Roger, I thought that I messaged you earlier but I see that it wasn't posted. I just answered your PM
So check your messages
Edit: It failed, because you restored the locked emmc_appsboot.mbn
after you prepare the phone for unlocking the bootloader, make sure that you remove any passwords, this way you will not have any storage encryption issues.
---------- Post added at 12:19 AM ---------- Previous post was at 12:17 AM ----------
This is message 2.
The Pie Rom that you choose is a bad choice > It's not longer supported. We can talk on the phone if your timezone is close to mine . For me its 11:30pm Est.
I will be awake for about another hour. Otherwise, I can help you tomorrow. If you get this message tonight, message me ASAP
Next: Here is a link with the essential steps ( some of which you have found)
https://forum.xda-developers.com/showpost.php?p=75009966
Your Rom is an Alpha build. If You want Android 9.0 Pie > choose something recent such as Lineage 16.0, or AICP 14 These are great Roms and the developers currently have working Le Pro 3's.
If you still want or need help, I can help you on the phone or maybe use Team-Viewer.
Have these things ready
Your Rom of Choice
Recent Gapps ( Ex: open_gapps-arm64-9.0-nano) Here: https://opengapps.org/
TWRP : ( This One twrp-3.2.3-1-zl1 : https://dl.twrp.me/zl1 )
Magisk 17.3 ( https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
Click to expand...
Click to collapse

Moto G7 Soft brick

I was asked yesterday to install LineageOS on someone's phone. It's been a few years, and I screwed some stuff up and now I need help. I'll go through what I did first and then I'll go through my current problems.
Enabled USB debugging and OEM unlock in the phone's settings.
Used ADB to reboot ot bootloader (adb reboot bootloader)
Verified the device's existence with adb.
Used Motorola's website to unlock the phone's bootloader. Process went fine.
Restarted the phone. Got the message that the bootloader was unlocked.
Went back to developer settings to re-enable USB debugging.
Rebooted to fastboot.
Typed in "fastboot flash boot twrp.img" (the file name was longer, but I'll abbreviate for the sake of brevity).
Wiped data.
Formatted data
Now, this is where the problems started. With the data formatted, I couldn't sideload anything, mounting didn't work, and the TWRP file manager showed literally nothing on the phone. No file system or anything, it looked like. This was done on a Linux computer (which also turned two of my MicroSD cards into read only. Thanks Fedora.
Anyway, I figured I should go back to fastboot to fix things. This was probably a mistake, because now I can't do anything. I can't flash TWRP, I can't boot into it, nothing. For example, when I type in
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
I get this:
(bootloader) is-logical:recovery: not found
Sending 'recovery' (27096 KB) OKAY [ 0.802s]
Writing 'recovery' (bootloader) Invalid partition name recovery
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
I Googled around. Some people said I might need to flash partitions from gpt.bin, but that didn't work either. Every time, I get "invalid partition name xxx."
What can I do?
Thanks you in advance.