Develop Bugs

LG G4 H815 stuck, download mode only, no adb

Hello hello,
I unlocked bootloader, installed TWRP 2.8.7.0 (adb -> fastboot method) and then I flashed SuperSU 2.46 zip. After reboot from TWRP my phone stuck.
I can't access TWRP or i don't know how to…
System isn't starting BUT sometimes after few minutes of seeing LG logo i see standard wallpaper and suddenly animation freezes. That's all.
When i go to recovery mode (voldown+power, release power and press power again) I can "do" factory reset. I choose 2xYES and i see green android. Then phone is restarting but i should enter to TWRP, right?
I tried to flash stock system (kdz, tot, dz) via:
- LG Flash Tool 2014
- LG Flash Tool 1.8.6.527
- LGUP
- LG Bridge
but nothing…
My phone PID and IMEI is null :/ (and "CUMSS" to :?)
I tried fix that with QPST (2 different versions) but in device manager my phone is only detected as COM port. No "Android Device". I can't read and write anything…
adb isn't working
I tried all USB 2.0 ports, different drivers, roms (even not for 815), dlls.
I fought 3 days and still have brick, not smartphone
I have only download mode working.
I can send commands to com port (Send_Command.exe) but sometimes nothing happen, sometimes i see "fail" after sent command.
Any ideas? Can I install recovery through download mode? Or maybe somebody know how to send files to phone in download mode but without adb?
I had stock rom MM V20L. What else you need to know?
Thanks for any suggestions, sorry for chaos in post and my english.

After trying different roms in different programs with 3 versions of dlls and different drivers…
I found solution: just reinstalled .NET Framework and then finally i flashed by LGUP (refurbish, v20L, kdz, dll 0.0.3.23)!
Welcome back H815

2 0 said:
After trying different roms in different programs with 3 versions of dlls and different drivers…
I found solution: just reinstalled .NET Framework and then finally i flashed by LGUP (refurbish, v20L, kdz, dll 0.0.3.23)!
Welcome back H815
Click to expand...
Click to collapse
where did you founf v20L kdz i need it because my phone wont flash any kdz i think its to prevent downgrades

https://lg-firmwares.com/lg-h815-firmwares/

Try some from skdubg's link. This is probable the same as mine
PLS Europe PL/Poland H81520l_00_0928.kdz 1.68 G 2016-11-25
Click to expand...
Click to collapse
download-file/?fileId=4325 I can't post links
This is MD5 of my file 8f685baf42869c50ec5f1b7770aa3957 *H81520l_00_0928.kdz
If you still can't flash then i will upload my kdz somewhere. GL

LG G4 Model F500L Stuck on download mode After Downgrade
Hi
i have a problem with my LG G4 Model F500L i try to downgrade from Marsmallow to Lolilpop By Flashing with LGUP Tool when i flash it. it error at 16% boot fail. So i disconnect USB and pull out battery and when i turn on it stuck on download mode.. i have try to flash with any firmware and any LG Tools but it's still fail at writing boot step i had try with Optopus box but it's still fail at wrting boot fail what is the problem . i need help now.... i just bought my phone for a week. Thanks for your helping ....

Moto G5 Cedric - Repair Imei = 0

After being in a LineageOS ROM, I decided to reinstall the Stock Firmware od Moto G5 Cedric through ADB, but after that the phone signal was lost, and both IMEI appear in 0, Has anyone else had that problem, or know the solution?

Which cedric variant do you have and which firmware did you flash?

I had the same problem. Don't worry, it is recoverable.
Try this:
https://forum.xda-developers.com/g5/how-to/recovering-2g-3g-set-radio-band-to-usa-t3668767
Primarily, from bootloader:
Code:
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache

JhonMii said:
After being in a LineageOS ROM, I decided to reinstall the Stock Firmware od Moto G5 Cedric through ADB, but after that the phone signal was lost, and both IMEI appear in 0, Has anyone else had that problem, or know the solution?
Click to expand...
Click to collapse
if you installed this rom https://forum.xda-developers.com/g5/development/rom-lineageos-15-1-t3722188
1. install TWRP recovery x64 and flash said room
2. start the device
3. Turn off the device and boot into bootloader
4. Flash the stock rom by removing these linens:
fastboot erase modemst1
fastboot erase modemst2
5. Start the device and the imei is fixed

The rom is LineageOS 14.1 , and if I go back to the same rom, the imei do not come out
valithria said:
if you installed this rom https://forum.xda-developers.com/g5/development/rom-lineageos-15-1-t3722188
1. install TWRP recovery x64 and flash said room
2. start the device
3. Turn off the device and boot into bootloader
4. Flash the stock rom by removing these linens:
fastboot erase modemst1
fastboot erase modemst2
5. Start the device and the imei is fixed
Click to expand...
Click to collapse

thanks but it has not helped me, it has not helped me to reinstall the original firmware, no matter how hard I try
claviger said:
I had the same problem. Don't worry, it is recoverable.
Try this:
https://forum.xda-developers.com/g5/how-to/recovering-2g-3g-set-radio-band-to-usa-t3668767
Primarily, from bootloader:
Code:
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
Click to expand...
Click to collapse

My Moto is G5 Cedric XT1671
This last version:
https://mirrors.lolinet.com/firmware/moto/cedric/official/RETAIL/
Exanneon said:
Which cedric variant do you have and which firmware did you flash?
Click to expand...
Click to collapse

Even I have same problem to the date. My solution is same as @valithria.
I flash Pixel Experience ROM via twrp and boot to system.
Check for IMEI number. ( code 06 ).
Go back to bootloader and start fastboot.
Skip erase modest1 and modemst2.
Continue with remaining commands and reboot.
You will have your IMEI number back.
Device: Moto G5 Cedric xt1677

valithria said:
if you installed this rom https://forum.xda-developers.com/g5/development/rom-lineageos-15-1-t3722188
1. install TWRP recovery x64 and flash said room
2. start the device
3. Turn off the device and boot into bootloader
4. Flash the stock rom by removing these linens:
fastboot erase modemst1
fastboot erase modemst2
5. Start the device and the imei is fixed
Click to expand...
Click to collapse
I retrieved my IMEI using this indication, I am with the stock (Cedric) with the bootloader locked, with both IMEI working.
Thank you very much.
Device Moto G5 Cedric XT1672

blaze_me said:
Even I have same problem to the date. My solution is same as @valithria.
I flash Pixel Experience ROM via twrp and boot to system.
Check for IMEI number. ( code 06 ).
Go back to bootloader and start fastboot.
Skip erase modest1 and modemst2.
Continue with remaining commands and reboot.
You will have your IMEI number back.
Device: Moto G5 Cedric xt1677
Click to expand...
Click to collapse
I was also having the same problem and thanks to this tip, I got my IMEI back in stock. Thank you. Now how do I back up the IMEI? I have already found several tutorials on the internet and none have served my Cedric

I guess we can't. For Qualcomm we can't however, mtk board is supported to backup

EMPTY

Thank you very much, I work perfectly
blaze_me said:
Even I have same problem to the date. My solution is same as @valithria.
I flash Pixel Experience ROM via twrp and boot to system.
Check for IMEI number. ( code 06 ).
Go back to bootloader and start fastboot.
Skip erase modest1 and modemst2.
Continue with remaining commands and reboot.
You will have your IMEI number back.
Device: Moto G5 Cedric xt1677
Click to expand...
Click to collapse

JhonMii said:
Thank you very much, I work perfectly
Click to expand...
Click to collapse
After recovering the IMEi from my mobile phone, the mobile data does not connect more like 4g, is someone having a similar problem?

This is like asking how to back up the bootloader in a specific state, you can't, if you ever lose the imei again, follow blaze_me's steps.

Exanneon said:
This is like asking how to back up the bootloader in a specific state, you can't, if you ever lose the imei again, follow blaze_me's steps.
Click to expand...
Click to collapse
I did the blaze_me steps, and got retrieved IMEI from the smartphone. But the mobile data network now does not start as 4G, it only connects like 3G. Sorry for my bad English.

Are you running stock firmware? If this is so then I suggest trying a custom rom and see if that fixes it.

jmsckakaroto said:
I did the blaze_me steps, and got retrieved IMEI from the smartphone. But the mobile data network now does not start as 4G, it only connects like 3G. Sorry for my bad English.
Click to expand...
Click to collapse
I also have the same problem on any ROM.

jmsckakaroto said:
After recovering the IMEi from my mobile phone, the mobile data does not connect more like 4g, is someone having a similar problem?
Click to expand...
Click to collapse
I'm also having the same problem. I think the problem with the 4G is due to the Oreo modem, which remains in the Nougat system, has an error or is not compatible. It's just a guess.
If I'm not mistaken, I was also with Custom, in my case at PixelExperience (Oreo 64bits).
Eu também estou tendo o mesmo problema. Acho que o problema com o 4G é devido ao modem Oreo, que permanece no sistema Nougat, possui algum bug ou não é compatível. É apenas um palpite.
Se não me engano, estava assim também com a Custom, no meu caso a PixelExperience.

guiperriraz said:
I'm also having the same problem. I think the problem with the 4G is due to the Oreo modem, which remains in the Nougat system, has an error or is not compatible. It's just a guess.
If I'm not mistaken, I was also with Custom, in my case at PixelExperience (Oreo 64bits).
Eu também estou tendo o mesmo problema. Acho que o problema com o 4G é devido ao modem Oreo, que permanece no sistema Nougat, possui algum bug ou não é compatível. É apenas um palpite.
Se não me engano, estava assim também com a Custom, no meu caso a PixelExperience.
Click to expand...
Click to collapse
Maybe if we get a method to backup the IMEI, we could execute the command '' fastboot erase modemst '' and after that, restore the IMEI with the backup. With this the IMEI might come back with the 4G working.
Of course I'm counting on a possibility of the modemst not being without backup.

T-Mobile OnePlus 7T Internat'l ROM Version Conversion – Guaranteed Method That Works If All Else Fails

If you purchased a OnePlus 7T which went on sale recently, but still aren't able to replace the T-Mobile firmware with the internat'l variant then you're in luck. I came across a few guides which were a smoking gun, but I was never fully able to get it to work successfully and "failed miserably". And a few posts I read helped spur some ideas and inspired me to think outside the box in order to come up with a much more predictable viable solution here. Throughout this guide, I have linked the page or post based on information I gathered to put this guide together in order to credit that person instead of having to name drop them individually. The instructions given were made with the expectation that you already have the bootloader unlocked and installed the necessary drivers with adb setup. I followed this guide here as point of reference which I think could be potentially bypassed by using this method instead to completely streamline the process. Best of all, I spent 15 hours yesterday trying to figure this out so hopefully you won't have to go through what I did. NOW LET'S BEGIN!!!
FLASH OPERATIONS
I. Just to give a little background for those of you who followed the guide I referenced, whenever I attempted to flash the 10.0.13-GLOBAL fastboot rom it would display the error message "Flashing is not allowed for Critical Partitions" multiple times then auto reboot T-Mobile logo splash screen, indicating that the process failed.
At this point, hold Vol Up + Power till the device shuts down and boot into fastboot.
On the PC, download the All In One v2.0.1.3 tool.
Download 10.0.3-HD65AA-OnePlus7TOxygen_14.I.05_OTA_005_all_1909252229_1be2cbaa2-FASTBOOT.zip or from here.
Open All In One v2.0.1.3 –> Flash Factory Images –> Browse directory for the fastboot rom –> check off "Wipe all data" and "Reboot after flash" –> Flash Rom.
During flash process, it will reboot once, NOT into fastboot, but stock recovery menu (FastbootD), and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.3HD65AA rom image.
II. Download and extract "10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT.zip" into a folder called "adb" in the root of the C: drive.
III. While the phone is turned on, we must boot into FastbootD. The fastbootD screen has the OnePlus logo centered at the top with 3 language choices. Run "cmd" as admin and type:
Code:
adb reboot bootloader
fastboot reboot fastboot
IV. Enter this command to check what version of Fastboot you've booted into:
Code:
fastboot getvar is-userspace
"Yes" means you're in FastbootD.
V. To flash the "10.0.13-GLOBAL" fastboot rom, run the bat script by entering these commands:
Code:
cd C:/adb
flash-all.bat
During flash process, it will reboot once into FastbootD again (stock recovery menu) and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.13HD65AA rom image.
Take the opportunity to perform a system update to Oxygen OS 10.0.15.HD65AA.
Enable developer mode: Go to Settings –> About phone (at bottom) –> tap Build number (towards right) until it says Developer Mode is enabled.
Go to Developer Options –> Enable USB Debugging and "allow". Go to "Default USB configuration" and change it to "File Transfer".
ROOT THE DEVICE
VI. Download and copy magisk_patched 10.0.8 international (global) into the ADB folder. Rename it to "modded-boot.img". Flash the modded-boot.img file to achieve temporary root. While the phone is turned on, in cmd type:
Code:
adb reboot bootloader
cd C:/adb
fastboot boot modded-boot.img
The device will reboot on its own once the process has completed.
VII. Download Magisk Manager and copy it to the phone's internal storage and use the native "Files" app to install the apk.
Launch Magisk Manager. Click "Cancel" on the "Requires Additional Setup" message.
Update "Manager" if using an outdated apk. Update "Magisk" via Direct Install and Reboot.
After the reboot, the device will retain root which can be verified using apps like Root Checker in the Play Store.
Someone who hasn't already tried converting their stock T-Mobile firmware to the OnePlus Internat'l firmware variant and is interested enough to follow these steps, please update me with your results after going through the process to confirm it was successful, I would greatly appreciate it.
If you have any helpful suggestions that could offer more insight or if there seems to be any holes or missing explanations within my instructions missing feel free to comment.
Kudos to @mauronofrio, without his tools none of this would be possible

I'm trying all different guides to do this to my 7T.
After this step:
Open All In One v2.0.1.3 –> Flash Factory Images –> Browse directory for the fastboot rom –> check off "Wipe all data" and "Reboot after flash" –> Flash Rom.
During flash process, it will reboot once, NOT into fastboot, but stock recovery menu (FastbootD), and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.3HD65AA rom image.
The phone just botted on T-Mobile rom... what should I do?

dimelus said:
I'm trying all different guides to do this to my 7T.
After this step:
Open All In One v2.0.1.3 –> Flash Factory Images –> Browse directory for the fastboot rom –> check off "Wipe all data" and "Reboot after flash" –> Flash Rom.
During flash process, it will reboot once, NOT into fastboot, but stock recovery menu (FastbootD), and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.3HD65AA rom image.
The phone just botted on T-Mobile rom... what should I do?
Click to expand...
Click to collapse
Okay, so this was MY experience. I did the MSM tool thing then started flashing the Global ROM. My phone did the same thing, and I panicked BUT my phone eventually booted into T-mobile's software. All I did was mash all three buttons to get back to the bootloader and flashed the Global firmware and it worked.

draymond1987 said:
Okay, so this was MY experience. I did the MSM tool thing then started flashing the Global ROM. My phone did the same thing, and I panicked BUT my phone eventually booted into T-mobile's software. All I did was mash all three buttons to get back to the bootloader and flashed the Global firmware and it worked.
Click to expand...
Click to collapse
But did you setup the phone, activated usb debug again? or you just power it off and go vol+/power to enter in recovery?

dimelus said:
But did you setup the phone, activated usb debug again? or you just power it off and go vol+/power to enter in recovery?
Click to expand...
Click to collapse
I immediately went back to the bootloader. I didn't set up the phone.
Also, power down + vol down. You'll get into the Chinese recovery. Then select the options to get into fastboot

draymond1987 said:
I immediately went back to the bootloader. I didn't set up the phone.
Also, power down + vol down. You'll get into the Chinese recovery. Then select the options to get into fastboot
Click to expand...
Click to collapse
Did u have errors when flashing like:
FLASHING IS NOT ALLOWED FOR CRITICAL PARTITIONS?
I just did what you said, power vol down and went again into the fastboot.
But there are some errors happing atm

dimelus said:
Did u have errors when flashing like:
FLASHING IS NOT ALLOWED FOR CRITICAL PARTITIONS?
I just did what you said, power vol down and went again into the fastboot.
But there are some errors happing atm
Click to expand...
Click to collapse
What I would do, and it's silly but could work. Go back into fastboot and issue the "
fastboot flashing unlock_critical" command, again. I know this happened to me too because I had these errors and I just tried, out of desperation. I dunno if it's because the phone is on the T-mobile software, that it freaks out like that, question mark?

dimelus said:
I'm trying all different guides to do this to my 7T.
After this step:
Open All In One v2.0.1.3 –> Flash Factory Images –> Browse directory for the fastboot rom –> check off "Wipe all data" and "Reboot after flash" –> Flash Rom.
During flash process, it will reboot once, NOT into fastboot, but stock recovery menu (FastbootD), and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.3HD65AA rom image.
The phone just botted on T-Mobile rom... what should I do?
Click to expand...
Click to collapse
Did you not flash 10.0.3HD65AA rom image which is step "I."? If you go out of step and not follow the instructions as they're laid out then of course you're going to have problems.

urbanman2004 said:
If you purchased a OnePlus 7T which went on sale recently, but still aren't able to replace the T-Mobile firmware with the internat'l variant then you're in luck. I came across a few guides which were a smoking gun, but I was never fully able to get it to work successfully and "failed miserably". And a few posts I read helped spur some ideas and inspired me to think outside the box in order to come up with a much more predictable viable solution here. Throughout this guide, I have linked the page or post based on information I gathered to put this guide together in order to credit that person instead of having to name drop them individually. The instructions given were made with the expectation that you already have the bootloader unlocked and installed the necessary drivers with adb setup. I followed this guide here as point of reference which I think could be potentially bypassed by using this method instead to completely streamline the process. Best of all, I spent 15 hours yesterday trying to figure this out so hopefully you won't have to go through what I did. NOW LET'S BEGIN!!!
FLASH OPERATIONS
I. Just to give a little background for those of you who followed the guide I referenced, whenever I attempted to flash the 10.0.13-GLOBAL fastboot rom it would display the error message "Flashing is not allowed for Critical Partitions" multiple times then auto reboot T-Mobile logo splash screen, indicating that the process failed.
At this point, hold Vol Up + Power till the device shuts down and boot into fastboot.
On the PC, download the All In One v2.0.1.3 tool.
Download 10.0.3-HD65AA-OnePlus7TOxygen_14.I.05_OTA_005_all_1909252229_1be2cbaa2-FASTBOOT.zip or from here.
Open All In One v2.0.1.3 –> Flash Factory Images –> Browse directory for the fastboot rom –> check off "Wipe all data" and "Reboot after flash" –> Flash Rom.
During flash process, it will reboot once, NOT into fastboot, but stock recovery menu (FastbootD), and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.3HD65AA rom image.
II. Download and extract "10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT.zip" into a folder called "adb" in the root of the C: drive.
III. While the phone is turned on, we must boot into FastbootD. The fastbootD screen has the OnePlus logo centered at the top with 3 language choices. Run "cmd" as admin and type:
Code:
adb reboot bootloader
fastboot reboot fastboot
IV. Enter this command to check what version of Fastboot you've booted into:
Code:
fastboot getvar is-userspace
"Yes" means you're in FastbootD.
V. To flash the "10.0.13-GLOBAL" fastboot rom, run the bat script by entering these commands:
Code:
cd C:/adb
flash-all.bat
During flash process, it will reboot once into FastbootD again (stock recovery menu) and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.13HD65AA rom image.
Take the opportunity to perform a system update to Oxygen OS 10.0.15.HD65AA.
Enable developer mode: Go to Settings –> About phone (at bottom) –> tap Build number (towards right) until it says Developer Mode is enabled.
Go to Developer Options –> Enable USB Debugging and "allow". Go to "Default USB configuration" and change it to "File Transfer".
ROOT THE DEVICE
VI. Download and copy magisk_patched 10.0.8 international (global) into the ADB folder. Rename it to "modded-boot.img". Flash the modded-boot.img file to achieve temporary root. While the phone is turned on, in cmd type:
Code:
adb reboot bootloader
cd C:/adb
fastboot boot modded-boot.img
The device will reboot on its own once the process has completed.
VII. Download Magisk Manager and copy it to the phone's internal storage and use the native "Files" app to install the apk.
Launch Magisk Manager. Click "Cancel" on the "Requires Additional Setup" message.
Update "Manager" if using an outdated apk. Update "Magisk" via Direct Install and Reboot.
After the reboot, the device will retain root which can be verified using apps like Root Checker in the Play Store.
Someone who hasn't already tried converting their stock T-Mobile firmware to the OnePlus Internat'l firmware variant and is interested enough to follow these steps, please update me with your results after going through the process to confirm it was successful, I would greatly appreciate it.
If you have any helpful suggestions that could offer more insight or if there seems to be any holes or missing explanations within my instructions missing feel free to comment.
Kudos to @mauronofrio, without his tools none of this would be possible
Click to expand...
Click to collapse
Thanks for your guide lines.. I am a very newby yet 71 years old.. been messing with hardware and software since 1984, always learning. new to Flashing Rom's , I converted two 6T's and 3 7T from TMO to 1+, the third 7T gave me a fit, because I purchased from someone who didn't tell me that someone had tried to convert to dual sim and I had a hard time to solve the issue.. Two things,, for everyone trying to do this.. Branded to Global or Dual Sim, One You have to have the Correct Drivers for Windows for the ADB and Fastboot.. and it has to be setup correctly.. as for some drivers that are signature issue for windows, and you have exclamation mark because of signatures, as for Win10,
restart your windows with Shift key held down and select restart, when it boots into blue screen select "troubleshoot"
from that select " Startup blue secreen. " after that Select Item #7 which is to forces Windows to ignore Signature error reporting. select Start , then go on with your process for Brand to dual sim or Global, etc..
THANK YOU for Your Information and Procedure Steps to Convert from Branded to Dual / Global, etc.. made it very less time consuming...Appreciate You and All those who have given Good Guidance - Thank You

does this method unlock the sim card?

goggolar said:
does this method unlock the sim card?
Click to expand...
Click to collapse
No, you have a completely separate issue. The OnePlus 7T device I purchased already had an unlocked sim card. You need to refer to your phone carrier who provides you service.

It needs the bootloader unlocked?

SBruno said:
It needs the bootloader unlocked?
Click to expand...
Click to collapse
Yep

CaptRicXT912 said:
Gracias por sus lineamientos .. Soy muy nuevo por 71 años .. he estado jugando con hardware y software desde 1984, siempre aprendiendo. nuevo en Flashing Rom's, convertí dos 6T y 3 7T de TMO a 1+, el tercer 7T me encajó, porque le compré a alguien que no me dijo que alguien había intentado convertir a dual sim y tenía un Es difícil resolver el problema. Dos cosas, para todos los que intentan hacer esto. Con la marca Global o Dual Sim, una Debe tener los controladores correctos para Windows para ADB y Fastboot ... y debe estar configurado correctamente ... como para algunos controladores que son un problema de firma para Windows, y tiene un signo de exclamación debido a las firmas, como para Win10,
reinicie sus ventanas con la tecla Shift presionada y seleccione reiniciar, cuando se inicie en la pantalla azul, seleccione "solucionar problemas"
a partir de ahí, seleccione "Pantalla azul de inicio". Después, seleccione el elemento n. ° 7, que obligará a Windows a ignorar el informe de errores de firma. seleccione Inicio, luego continúe con su proceso de Marca a SIM dual o Global, etc.
GRACIAS por su información y procedimiento Los pasos para convertir de marca a dual / global, etc. hicieron que consumiera mucho menos tiempo ... Le agradezco a usted y a todos los que han dado una buena orientación - Gracias
Click to expand...
Click to collapse
seria de mucha ayuda si usted o alguien me ayudara en este problema estoy atascado en la version de android 10 de t-mobile la computadora no reconoce el dispositivo almenos que lo reinicie de fabrica, en modo fastboot no lo reconoce y estoy desesperado soy nuevo en esto

Excellent work, it did the job for mine. Followed your procedure and a couple of interpretations to get through it to the end.
Thank You for the help!

This worked for me, I wasn't even trying to convert my phone.. just restore a soft brick turned semi-hardbrick.
I haven't done android modding since my Zuk Z1! Previously I had modded my Galaxy s3, some LG [it was the one with RGB home button, man I miss that], and Z1. ​​Yesterday I decided I was finally ready to mod my oneplus 7t [hd1907] after 2 years of ownership. Bootloader unlock, Rooted, modded some things, and then Sound wouldn't play in the speakers, wifi dead, hotspot dead, amongst other broken features. Trouble is, I wasn't thinking like I used to and didn't have my img files backed up. All I wanted to do was revert back to the stock firmware.. but I ended up in a softbrick somehow. I can't find tmo op7t firmware anywhere online.. I was going to try flashing it with adb.​​Well I came across your guide here, and when all hope was lost I thought I might as well give it a try.. and it worked! Now instead I'm on international software! Even better than just recovering stock! Well youtube is throwing a connection error but I am hoping it just means I need to update my gapps.. Thank you very much this helped me recover my phone..
dimelus said:
Did u have errors when flashing like:
FLASHING IS NOT ALLOWED FOR CRITICAL PARTITIONS?
I just did what you said, power vol down and went again into the fastboot.
But there are some errors happing atm
Click to expand...
Click to collapse
I actually had "FLASHING IS NOT ALLOWED FOR CRITICAL PARTITIONS" on the first flash as well, and it never booted properly either. On the second flash I was getting "Invalid sparse file format at header magic".. However in the end of the process my phone was working.
I'm going to update gapps and update firmware to the latest OTA now, which popped up in the notifications already! Thanks again Urbanman.
Edit: "some LG [it was the one with RGB home button, man I miss that]" I checked my post history it was LG optimus G pro.

I now have the latest firmware for t-mobile 11.0.1.11. With the help of your method, can I flash the global firmware? Or do I need to first somehow lower the firmware version from t-mobile?

k.stahanov73 said:
I now have the latest firmware for t-mobile 11.0.1.11. With the help of your method, can I flash the global firmware? Or do I need to first somehow lower the firmware version from t-mobile?
Click to expand...
Click to collapse
Superboy58 msmtool will get u global oos10, then ota to 11.0.9.1 or oos12 global

HueyT said:
Superboy58 msmtool получит u global oos10, затем ota на 11.0.9.1 или oos12 global
Click to expand...
Click to collapse
I can not flash through msm .. at the fastboot stage after a reboot I ALWAYS boot into the old system !! always! already made 50 attempts and changed the cords and ports and no use!

Maybe it's because I have Windows 7?

Help me with the custom rom :(

Hello, first of all I want to apologize for any grammatical mistake since I do not speak English and this text was translated through a web page. Let's start, for a long time I came with emotions to try custom roms on my device (motorola moto g7 play ((XT1952-2)), I decided to try the lineageOs and to my surprise I managed to make it work, but I did not have the Gapps so I wore To investigate to install them, after investigating, I tried to install them but everything went wrong, very bad, the cell phone had been soft bricked and I was about 5 hours trying to solve it since the bootloader had been blocked and there was no way to install ANYTHING, After solving it, I found that I cannot install LineageOS in any way, I spent about 4 hours testing and it always throws me an error and this affects the entire device since I have to use the Motorola assistant on every failed occasion ( Rescue and Smart Assistant), I attach one of the problems that I get when trying to install the OS. I hope a prompt solution, thank you very much
Instalando archivo zip
Buscando archivo digest...
Step 1/2
Error applying update: 28 (ErrorCode::kDownloadOperationExecutionError)
Proceso Updater terminó con ERROR : 1
Error instalando archivo zip
Actualizando detalles de la particion
I tried in all the ways I could but did not reach any solution, I only use the stock motorola firmware, but the fact of installing a custom rom rejects it anyway.

ulisesgomez23 said:
Hello, first of all I want to apologize for any grammatical mistake since I do not speak English and this text was translated through a web page. Let's start, for a long time I came with emotions to try custom roms on my device (motorola moto g7 play ((XT1952-2)), I decided to try the lineageOs and to my surprise I managed to make it work, but I did not have the Gapps so I wore To investigate to install them, after investigating, I tried to install them but everything went wrong, very bad, the cell phone had been soft bricked and I was about 5 hours trying to solve it since the bootloader had been blocked and there was no way to install ANYTHING, After solving it, I found that I cannot install LineageOS in any way, I spent about 4 hours testing and it always throws me an error and this affects the entire device since I have to use the Motorola assistant on every failed occasion ( Rescue and Smart Assistant), I attach one of the problems that I get when trying to install the OS. I hope a prompt solution, thank you very much
Instalando archivo zip
Buscando archivo digest...
Step 1/2
Error applying update: 28 (ErrorCode::kDownloadOperationExecutionError)
Proceso Updater terminó con ERROR : 1
Error instalando archivo zip
Actualizando detalles de la particion
I tried in all the ways I could but did not reach any solution, I only use the stock motorola firmware, but the fact of installing a custom rom rejects it anyway.
Click to expand...
Click to collapse
Which recovery are you using? Twrp, or Lineage? it's not stock is it?

i use Twrp
Yes, I know about that application, I always use it when the phone throws me an error.
Let me explain, I have the bootloader unlocked so I connect the cell phone to the pc in fastboot mode and with a terminal I run "fastboot set_active a" to activate slot a, after this I use "fastboot boot <here I put the address where it is located the twrp recovery> "once started I go to wipe and delete dalvik, cache, data, and system, and after all this I go to install and look for my LineageOS.zip file and I proceed to install it, as soon as the installation begins, when the bar progress is 25%, the operation is canceled and I get the error that I mentioned before (Installing zip file
Searching for digest file ...
Step 1/2
Error applying update: 28 (ErrorCode :: kDownloadOperationExecutionError)
Updater process ended with ERROR: 1
Error installing zip file
Updating partition details)
After this the cell phone is without operating system so I have to use the motorola application (Rescue and Smart Assistant) to be able to recover my phone.
I want to clarify that the phone the first time I perform the steps everything worked perfectly, LineageOS was installed but when I turned it on first I got a black screen that said N / A and after a few seconds I started LineageOS, this I understand what happened due to that the OS was installed in slot b, but I have no idea, I can no longer flash any rom since it always gives me an error and there is nothing to solve it

Question poco f3 preso no recovery mode.

<Moderator Edit>: English translation added to the top.
My poco f3 was stuck in recovery mode, it has two options: "TRy Again" and "factory data resett", but it doesn't work back to the same screen.
Original:
Meu poco f3 ficou preso no modo recovery, tem duas opções: "TRy Again" e "factory data resett", porém não funciona volta pra mesma tela.

Israel F3 said:
<Moderator Edit>: English translation added to the top.
My poco f3 was stuck in recovery mode, it has two options: "TRy Again" and "factory data resett", but it doesn't work back to the same screen.
Original:
Meu poco f3 ficou preso no modo recovery, tem duas opções: "TRy Again" e "factory data resett", porém não funciona volta pra mesma tela.
Click to expand...
Click to collapse
I'm not sure what you've done to it. Have you unlocked the bootloader and flashed custom ROM or recovery?
With what you said I would say boot into fastboot mode and flash stock firmware with XiaoMiFlash tool.

I seen your message in my notifications and figured no one would answer you because that's how it goes so I figured well he's probably freaking out thinking he broke his phone. If you have done anything to change something like flashing roms or root let me know either way it's probably fixable.
Just don't try to get into EDL mode that's not needed and make sure no one tells you to type adb commands to erase anything people think it's funny to tell people how to erase bootloader and totally hard brick a device.