Related
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.
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?
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
Hey guys I have a problem with my LG G3 D855 model stucked at bootloop.
The deal is that I already tried to short two pins on motherboard and do qualcomm flash with LG BoardDiag tool.
Everithung went well AP pass, EMMC pass and SDRAM pass, all good.
Succesfuly restore all boot images and yet still stuck at bootloop, no download mode and no recovery mode.
I used this TOT file LGD855AT-00-V10e-EUR-XX-JUL-08-2014-16G+0.tot I guess that's the right one.
Tried with both DoardDiag 2.99a and 3.99c. But still with no luck.
My system is Windows 10 64bit, Qualcomm 64 bit version used in Windows test mode.
I followed couple of xda tutorials, and all went fine till the end, without beign able to go into Download Mode.
Any suggestions? Does anybody saw this kind of case?
The only suggestion I can offer is to try a newer firmware. (E.g. V10l) You should be able to extract the newer images from the kdz and use the partition table from the V10e tot, since the sizes don't change.
I had a similar problem when I downgraded to that V10e tot on a replacement board with exchanged eMMC-chip. Got a bootloop and eventually ended up in fastboot, since the kernel obviously could not deal with that type of chip.
If you also end up in fastboot once, you can try a tethered boot to a newer laf (download mode) image to be able to flash with LGUP.
macgyver77 said:
The only suggestion I can offer is to try a newer firmware. (E.g. V10l) You should be able to extract the newer images from the kdz and use the partition table from the V10e tot, since the sizes don't change.
I had a similar problem when I downgraded to that V10e tot on a replacement board with exchanged eMMC-chip. Got a bootloop and eventually ended up in fastboot, since the kernel obviously could not deal with that type of chip.
If you also end up in fastboot once, you can try a tethered boot to a newer laf (download mode) image to be able to flash with LGUP.
Click to expand...
Click to collapse
Hey @macgyver77,
Thanks for you answer
I can only do a flash with BoardDiag Tool, shorting two pins directly on motherboard. But still stuck at bootloop.
I made one mistake telling that I don't have recovery mode. I have it, but it's useless, because when I press factroy reset, it starts and reboots into bootloop again, every time.
So, if I extract KDZ I only get extensions .bin, but with BoardDiag I need extension .mbn.
Did you mean to extract KDZ and use primaryGPT from V10l to V10E TOT or the opposite?
And how to convert from .bin to .mbn or the other way arround?
I can not go into DL mode or ADB mode or FASTBOOT mode.
I don't know what caused this problem for you or why you had to use BoardDiag in the first place, but after I downgraded to V10e (successful flash using LGUP) I saw almost the same behaviour: Bootloops on normal boots, bootloops when trying to get to download mode, recovery apparently worked and cleared data (android robot logo shortly visible), but no effect on bootloops. However, after letting the device bootloop for several times, I eventually ended up in fastboot mode sometimes.
When you try to go to download mode, do you see the "Download mode loading" logo (similar to left picture here: https://lgaristo.com/lg-aristo-ms210-download-mode-recovery-mode-safe-mode/) briefly before the device bootloops?
From what I can see the "mbn" files BoardDiag extracts from the tot file are the same files that the "LG Firmware Extractor" saves as "bin" files, so it should be possible to exchange the files just by renaming. (Compare results from extracting V10e tot with both programs in pics below.)
I never actually had to use Boarddiag to recover, but my idea would have been to flash images from a newer firmware kdz (V10l) with it. However, I saw that the "aboot.img" sizes are different (V10e: 1.5 MB, V10l: 2.0 MB), so I'm not sure about that, because the partition layout may have changed between those versions. My next idea would have been to flash the V10e files using boarddiag, with just the laf partition exchanged to the V10l version. Maybe that would allow to get download mode to work. The "laf.mbn" file I attach here is the partition image from V10l - same size as the V10e image.
macgyver77 said:
I don't know what caused this problem for you or why you had to use BoardDiag in the first place, but after I downgraded to V10e (successful flash using LGUP) I saw almost the same behaviour: Bootloops on normal boots, bootloops when trying to get to download mode, recovery apparently worked and cleared data (android robot logo shortly visible), but no effect on bootloops. However, after letting the device bootloop for several times, I eventually ended up in fastboot mode sometimes.
When you try to go to download mode, do you see the "Download mode loading" logo (similar to left picture here: https://lgaristo.com/lg-aristo-ms210-download-mode-recovery-mode-safe-mode/) briefly before the device bootloops?
From what I can see the "mbn" files BoardDiag extracts from the tot file are the same files that the "LG Firmware Extractor" saves as "bin" files, so it should be possible to exchange the files just by renaming. (Compare results from extracting V10e tot with both programs in pics below.)
I never actually had to use Boarddiag to recover, but my idea would have been to flash images from a newer firmware kdz (V10l) with it. However, I saw that the "aboot.img" sizes are different (V10e: 1.5 MB, V10l: 2.0 MB), so I'm not sure about that, because the partition layout may have changed between those versions. My next idea would have been to flash the V10e files using boarddiag, with just the laf partition exchanged to the V10l version. Maybe that would allow to get download mode to work. The "laf.mbn" file I attach here is the partition image from V10l - same size as the V10e image.
Click to expand...
Click to collapse
I had to use BoardDiag because that's how it's only possible for me to do a flash, because I can go into Download Mode.
When I want to go into DL mode, first show LG logo and then reboots into bootloop. And if I let phone to do a couple of loops phone become very hot under the power button because of the chips.
I tried your method but still the same. I even tried with Marshmellow 6.0. I extracted all files and rename it to .mbn and flash all the nessesery files. And same bootloops.
The Only thing I can think of is to try a new battery. I saw some people on the net with the bootloops, and when they replace old battery with the new one bootloops stops and phone runs normaly.
But the problem is I don't want to buy new battery to find out that it's not the problem
Maybe I can go to some service if they have working battery to try that way, I don't know. Will see.
@macgyver77 thanks a lot for the suggestions
estou com mesmo problema, comprei uma placa lg g3 d855 32gb aliexpless,
versão KVT49L.D85510o 4.4 kk, tentei atualizar para Global D85530B_00_1217 pelo LGflashTool2014 não instala, tentei outras versões de rom d855 e nada, ai tentei pelo LGUP a rom LGD855AT-00-V10e-EUR-XX-JUL-08-2014-32G+0, aconteceu isso, loop infinito, não entra em modo download e nem modo recovery,
fiz procedimento pelo BoardDiag 2.99, só consegui extrair a rom LGD855AT-00-V10e-EUR-XX-JUL-08-2014-32G+0, as outras da erro ao extrair , fiz tudo como no como descrito pelo nenadlalos83, consigo entrar modo download, só que não consigo instalar nenhuma rom pelo LGflashTool2014, para 2% antes de instalar,
pelo LGUP consigo instalar as rom LGD855AT-00-V10b-HKG\TWN\EUR, todas instalam mas loop infinito...
alguma idéia possa fazer pra corrigir?
também não achei a rom que veio nele pra download (D85510o 4.4)
só achei essa mas parece instalar pelo twrp, não consigo entra recovery
D85510o.zip | ROM by Xi0N83 for G3 - Android File Hosti have the same problem, i bought a lg g3 d855 32gb aliexpless card,
version KVT49L.D85510o 4.4 kk, I tried to update to Global D85530B_00_1217 through LGflashTool2014 it does not install, I tried other versions of rom d855 and nothing, then I tried through LGUP the rom LGD855AT-00-V10e-EUR-XX-JUL-08-2014-32G+ 0, this happened, infinite loop, does not enter download mode or recovery mode,
I did the procedure through BoardDiag 2.99, I was only able to extract the rom LGD855AT-00-V10e-EUR-XX-JUL-08-2014-32G+0, the others gave an error when extracting, I did everything as described by nenadlalos83, I can enter mode download, only I can't install any rom by LGflashTool2014, to 2% before installing,
by LGUP I can install the roms LGD855AT-00-V10b-HKG\TWN\EUR, they all install but infinite loop...
Any ideas I can do to fix it?
I also couldn't find the rom that came with it for download (D85510o 4.4)
I just found this one but it seems to install through twrp, I can't enter recovery
D85510o.zip | ROM by Xi0N83 for G3 - Android File Host
Heya guys,
I did get TWRP + LineageOS 18.1 working on this tablet a few months ago, and have been enjoying it (along with Magisk + google apps).
I had to use Odin, since no other method worked - but I had to borrow a laptop for that (since I don't use Windows, and the Linux apps didn't work at all).
Since LineageOS 19.1 was released, I thought I would give the upgrade a try, and also the backup + restore method a try for TWRP (must be tried + tested right? .. Or so I thought).
So, I get a USB drive, exfat formatted, double the size of the internal storage.
I backup all partitions except for "Dtbo", "cache", "EFS" (so all the stuff that might be touched by a potential patching I wanted backed up)..
Data, I also renamed the "media" to "mediabak" and backed that up - so that I wouldn't lose any media files either.
I then "install"ed the LineageOS 19.1 zip file using the TWRP "install" button.... Cleared the cache, aaaaand got the LineageOS boot animation and then just continual reboot...
5 reboots later, I boot into TWRP: "no worries - I shall restore from my backups!" I say to myself.
I restore everything except the "data" partition, thinking "it's OK, it's only data and it'll save me time restoring that"
... NOPE! - reboot and now I just get continual reboots but no boot animation.
"Maybe I need to wipe them before hand?" - so I select to wipe the partitions (vendor, system, cache, ...).. Only data+recovery not being wiped.
Restore
.... NOPE!
"Let's try data - maybe there's something funny in there?"
.... NOPE! - and what's worse, I get a tar extraction error (255) - probably due to the fact the partition isn't encrypted (as a guess) - I found a webpage showing the "data" files in the backups are only tar files, and on my laptop they show as OK except for having some missing "TWRP.security.encrypt" and something about a missing equals sign on the extended metadata (so I think the data is all intact, so I can probably transfer / extract it after I get the tablet back).
"Let's just try to re-install LineageOS 18.1 from the images... Wipe system, grab the image from the net, use TWRP to 'install' the image"
.... NOPE! - still stuck with a boot loop.
Why will TWRP not install the OS properly?
How can I trust TWRP after this, with no ability to restore things?
What am I missing here, since there's no logs or errors for me to check I'm flying blind here and fairly annoyed at the fact that something so simple (essentially extracting files and running a few scripts for a 'normal' upgrade run) is failing so hard.
... Can anyone point me in the right direction?
--
Paul_one
*UPDATE*
So, I've got a semi-update:
I' was able to use Odin again to flash stock ROM, then re-flash vbmeta.tar, then re-flash recovery, then re-flash lineageOS 19.1
19.1 looks AWEFUL on first boot, nowhere near as 'refined' as 18.1 (using a scroll window center aligned makes me thing of old HTML from the late 90s before CSS).
Anyway, so I am able to boot into LineageOS 19.1 .. If I restore the "system_image" and wipe the data partition (clicking the 'wipe data' button) it allows me to also boot into 18.1 .. GREAT ....
...Except...
I still cannot restore the data partition using TWRP.
Still errors with a "extractTarFork()" error, code 255 .
The tars look "fine" on my Linux machine, and extract with only missing extended metadata errors.
I wrote a script to extract the tar files and run it in the TWRP terminal - it errors about file duplicates (no metadata errors).
I see that this is actually due to a character length limit on the filenames.
One sub-directory it tries to extract (sessions) is shortened (to 'session') and all files within it are extracted as the new shortened directory name... Meaning that it tries to delete a file (which it cannot since it's a directory) and write the file (which it cannot since the directory exists with that name)!
How is this possible when ALL android pathnames are disgustingly long. How has this not been seen before and why is this so cr*p?
There's 2 other 'tar' files (sym-links to 'toybox' - which I assume is a busybox clone) which are a different size to the normal one in the PATH... So I'm going to try those, but I'm a little lost as to how effective this will be, and I'm AMAZED that these errors aren't coming up on any google search since it seems it's broken from the foundational commands!
... How this ever backed up 'correctly' in the first place I will never know - but I'll never trust TWRP to 'backup' my data partition again..
--
Paul_one
Further update:
I progressed with the boot of the system to include a user account and put a decryption pattern on.
After rebooting, ensuring the "wiping" method was "rm -fr" in the settings, I was able to restore from the TWRP data backup.
I then have been able to copy the contents of the old /data/media directory into the new one.
... yet again: however....
The boot of the OS now is stuck on "tablet is starting", with no progress, no change, nothing.
I've tried another restore of the system_image but that hasn't changed anything.
I'll leave it going, just incase it's like a "restorecon" and all the files are being 'corrected' (which could understandably take a long time)... But isn't tarused to stop this sort of b**ks from happening?
This is the worst experience of "backup" I have had in over 20 years!!
If I had known the backup + restore mechanism wasn't actually tested I would have performed my own "dd" to stop any of this.
Hopefully this will be a warning for anyone else trying to use TWRP for 'backup' of actual data and people can make a much better choice going forward.
--
Paul_one
Another update:
So, I am attempting to check through various differences between a "clean" /data, and the /data that's restored and doesn't let the UI come up fully.
I thought "logcat" might be able to point me in the right direction (error message about "Unable to find com.android.systemui")... But it's not exactly helping me out with the mass of other minor errors etc.
I was able to get a tiny bit further by renaming the "/data/app" directory, so I'm now prompted for the pattern to decrypt/log in ... But the "tablet is starting" pops up after (as if the setup wizard is completing or something).
Pressing home does nothing. I can pull down the status bar to access things in there - but the "home" isn't coming up properly.
So, now it's just a long journey of trial+error to try and find the problematic files/directories.
--
Paul_one
[ROM][OFFICIAL][gts4lv|gts4lvwifi][12] LineageOS 19
LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project, with...
forum.xda-developers.com
The difference between 18.1&TWRP and 19.1&TWRP is inability of TWRP to decrypt /data/media were TWRP directory locates. So once installed, 19.1 makes backup/recovery functions of TWRP inoperable since TWRP cannot nor decrypt nor find encrypted /data/media/TWRP. You can make sure of that with the file manager while in TWRP, seeing abracadabra instead of directory names in /data/media, which is an alias path to /storage/emulated/0 (0 stands for user0), where Download, TWRP etc locates.
The only thing You can do with TWRP when 19.1 installed is to whipe System and FORMAT Data.
Then, wifhout leaving TWRP, You can INSTALL, not RECOVER, prepared on external SD 18.1 zip. You can't recover since You can't create /data structure by means of TWRP, but installation of 18.1 can. Then reboot into system, scip all settings and reboot to TWRP. Now You can recover to previously saved 18.1 BACKUP.
vpn560 said:
The only thing You can do with TWRP when 19.1 installed is to whipe System and FORMAT Data.
Then, wifhout leaving TWRP, You can INSTALL, not RECOVER, prepared on external SD 18.1 zip. You can't recover since You can't create /data structure by means of TWRP, but installation of 18.1 can. Then reboot into system, scip all settings and reboot to TWRP. Now You can recover to previously saved 18.1 BACKUP.
Click to expand...
Click to collapse
That's unfortunate. I only discovered this now after upgrading from 18.1 to 19.1 four days ago....and then tried doing a backup through TWRP....which threw up a 255 fork error....
Wondering if a fix will be included with the next vewrsion....twrp-installer-3.6.1_9-0-lake.zip....
Is there any other backup/recovery through recovery you can recommend?
Bonjour,
j'ai installé lineageos 19.1 (20221025) avec TWRP (3-5-1) sur mon oneplus 5T
tout est OK
Mais lors des mises à jour proposées par le telephone (>paramètres>systeme>gestionnaire de mises à jour) le tel redemarre en bootloops sur le logo lineage ???
Réinstallation de linéage mais en faisant un wipe paramètres usine et installation de TWRP (3-7-0)
= tout fonctionne paraitement (les mises à jour de la branche également)
Si ça peut servir....
djimel said:
Bonjour,
j'ai installé lineageos 19.1 (20221025) avec TWRP (3-5-1) sur mon oneplus 5T
tout est OK
Mais lors des mises à jour proposées par le telephone (>paramètres>systeme>gestionnaire de mises à jour) le tel redemarre en bootloops sur le logo lineage ???
Réinstallation de linéage mais en faisant un wipe paramètres usine et installation de TWRP (3-7-0)
= tout fonctionne paraitement (les mises à jour de la branche également)
Si ça peut servir....
Click to expand...
Click to collapse
- English Plesse
- wrong forum ; this is for Samsung Tab S5e, not Oneplus..