Database Develop

[Q] Update with open bootloader and TWRP

Hi!
Soon we can expect some update to P9. Can I update in the future through OTA with open bootloader and root?

Yes, just flash stock recovery, make update and flash twrp back.

Thanks, where can we find original recovery? any idea?

Jostian said:
Thanks, where can we find original recovery? any idea?
Click to expand...
Click to collapse
you can flash it with the SRK Tool: http://forum.xda-developers.com/p9/development/tool-srk-tool-huawei-bootloader-root-t3374068
Edit: stock recovery also included in this pack: http://forum.xda-developers.com/p9/how-to/guide-root-huawei-p9-t3367800

Extra info, i have updated today:
Once you have flashed back original recovery you can begin update. But it is going to fail. Your phone first downloading a small update package (mine was 175mb) but since there were some changes due to root it failed immediately. You phone restarts and is downloading the full update package (~1.7gb). That is going to be OK.
You have to reflash TWRP and reflash root zip in order to have root.

so no issues with xposed when upgrading?

clouds5 said:
so no issues with xposed when upgrading?
Click to expand...
Click to collapse
I think only if you have systemless xposed installed...

smohanv said:
I think only if you have systemless xposed installed...
Click to expand...
Click to collapse
I have the custom one from Wanam that keeps the huawei theming engine intact. Is that systemless?

clouds5 said:
I have the custom one from Wanam that keeps the huawei theming engine intact. Is that systemless?
Click to expand...
Click to collapse
Yes. It is systemless. If you have both systemless root (SuperSU 2.62 and after) and systemless xposed, update should not be an issue.

I flashed stock recovery, update failed. now i can't download the update again. (rooted with supersu v2.76 and xposed by wanam)

TheFusi0n said:
I flashed stock recovery, update failed. now i can't download the update again. (rooted with supersu v2.76 and xposed by wanam)
Click to expand...
Click to collapse
same for me.

hi
same for me ( recovery stock - uninstall supersu with unsu.zip )
any idea
edit: same problem after restoring backup twrp no ota available
Edit2: i should restore p9 with dload b136 ( full wipe and relock bootloader ) and after made the ota update and restore backup

scedric57 said:
hi
same for me ( recovery stock - uninstall supersu with unsu.zip )
any idea
edit: same problem after restoring backup twrp no ota available
Edit2: i should restore p9 with dload b136 ( full wipe and relock bootloader ) and after made the ota update and restore backup
Click to expand...
Click to collapse
so it worked for you after resetting the phone? The status of your bootloader should have no impact on OTA from what I've seen.

Hi when you reflash with the firmware b136 by dload the phone do itself a full wipe and relock the boot loader
After the ota b166 was made fine

scedric57 said:
Hi when you reflash with the firmware b136 by dload the phone do itself a full wipe and relock the boot loader
After the ota b166 was made fine
Click to expand...
Click to collapse
thx, at least there is a way not prepared to go through all that though. I just realized I still have the update files on my phone (under \Internal storage\HwOUC\54265), there are two files: update.zip (381 mb) and update_data_hw_eu.zip (84 mb).
All I have to do is start up the update process again, as the files are still there. I tried moving these to dload folder on the sd card, packed, unpacked etc nothing seems to make it work so far. If I copy just the update.app from inside the update.zip the update process works but nothing changes, still on B136.

Yeah, holding back here for the moment, until we have a clear idea on how to update. I'm not needing b166 that much, that I have to jump through all those hoops, reset, wipe etc. just for the update.

How can i flash the stock recovery, tryed with STK Tool got an failed . (Command not allowed)
Ok, Recovery should now installed, but, when i press all 3 Buttons i got EMUI "Download latest version and recovery" "Reboot" and "Shutdown" When i click Download.... he cant download any files, wifi is working!
But it didnt install the Update.APP from the dload Folder. (B166)
I am at the Moment on B136

aliensmille said:
How can i flash the stock recovery, tryed with STK Tool got an failed . (Command not allowed)
Ok, Recovery should now installed, but, when i press all 3 Buttons i got EMUI "Download latest version and recovery" "Reboot" and "Shutdown" When i click Download.... he cant download any files, wifi is working!
But it didnt install the Update.APP from the dload Folder. (B166)
I am at the Moment on B136
Click to expand...
Click to collapse
Not exactly understanding what you are asking. For some reason moving the update.app from B166 in the dload folder is not working for this update. So at this moment there is no way to manually update.
If your OTA update failed and/or you don't get the update notification anymore there is only one way to get B166 at the moment: Flash full stock B136 (dload method), which does a factory reset and reverts everything back to stock, then you will get the update notification back and the update will work, even with unlocked bootloader.

I tried to install B162, that doesn't work with dload. My Bootloader is still unlocked, stock recovery is now installed, still rooted.
Should I try to install b136 and try to get the update?

I need L19C432B136, have someone an link for me, cant find this ROM

Device failed verification P9

There is an update on my phone and when i click on it to update it reboots and says in red, your device failed verification, no my phone was on version c900b136, as far as i was led to believe this was a corrupt version, so i have managed to get it back to c432b136, and there is an update and it fails on reboot what have i done and how do i fix this??
Thanks in advance :good:

swannyboy83 said:
There is an update on my phone and when i click on it to update it reboots and says in red, your device failed verification, no my phone was on version c900b136, as far as i was led to believe this was a corrupt version, so i have managed to get it back to c432b136, and there is an update and it fails on reboot what have i done and how do i fix this??
Thanks in advance :good:
Click to expand...
Click to collapse
try updating the full package thru firmware finder dns method, you should be able to get the update.

I have the same issue. Whatever method (3 buttons, TWRP, Huawei updater + HiSuite), I can not update. Only B386 can install nothing else.
I've tried a lots of package, even the FullOTA-MF-PV. Nothing nothing works.
I've tried to rollback to MM, no luck. B182, B360, B383, B390 no luck either. Going crazy...
Hopefully, I can reinstall B386 works fairly ok with some random crashes.

Now it comes up with update failed after reboot, that's doing it via the 3 button option, I was told that the bootloader was unlocked I don't know how to lock it

I'm in the same situation : I can't relock the bootloader using SRKTool. I can't flash most of update.zip, only B386 works so so....Really annoyed.
---------- Post added at 08:29 PM ---------- Previous post was at 07:32 PM ----------
Whatever method I use (dload, twrp, proxy updater even eRecovery), my package fail verification.
What can I do ? Seems something is broken with my phone...

Yeah so I've tried it again, restoring the phone first and it's still coming up with the same issue, I've unlocked the bootloader and (I assume that it needs locked again that's where the problem started) but I don't know how to go about this, as I said when you try and update it, its all in red saying the device is unsafe

swannyboy83, try this, it did work for me:
- When you turn on your phone, its all red saying "Verification Failed".
Try using Firmware Finder to download EVA-L09C109B132, unzip it, copy UPDATE.APP in the dload folder of the external sd card.
Turn off phone. Power button and keep + / - button.
It will install EVA-L09C109B132. Using recovery, try factory reset. Boot.
I see L09C432B132.
Now in the dload folder, replace UPDATE.APP by UPDATE.APP from B136.
Turn off phone. Power button and keep + / - button.
It will install L09C432B136.
Boot
Setup wifi.
Update now see B166.
==> But it ends up by Software installed failed for me.
At least, I have a usable phone...

just flash the stock recovery ( nougat or mm )
then relock the bootloader
then update the firmware reflash current or upgrade rom
the system will fulfill the missing files
dont forget to reset factory and back up before proceeding
goodluck

Hi vinfrix,
Done that : Stock recovery and bootloader relocked. But I can't reinstall the rom, whatever method, I have an error... Something corrupted in the phone I guess...

XavierP56 said:
Hi vinfrix,
Done that : Stock recovery and bootloader relocked. But I can't reinstall the rom, whatever method, I have an error... Something corrupted in the phone I guess...
Click to expand...
Click to collapse
Thats what i am getting, as you said at least i have a usable phone but would be nice to get the update :good:

Was there any fix until now??

Send your phone to official Huawei Centers in your area, their IT technicians will do the job

swannyboy83 said:
Thats what i am getting, as you said at least i have a usable phone but would be nice to get the update :good:
Click to expand...
Click to collapse
Why don't you update to Nougat, rebrand and then update to Oreo + network patch?

Problems with Honor 5C/7 Lite/Nem-L21, bootloop and more

Hi
I have searched through just about every thread and tried just about every trick in the book to make my Honor 5c/7 Lite/NEM-L21 to work again but nothing works for my problem. I'll try to describe what I did, what I have tried and what I am able to do with it.
What I did
Unlocked bootloader the official way with code from Huawei.
Flashed twrp recovery
Installed SuperSU from twrp and rooted the phone
Tried to install some custom roms and some stock roms, eventually I tried to install something that apparently wasn't for my specific model and twrp started to throw errors at me
The main error whenever I tried to do something in twrp was "can't mount /cust.." and some more error message which I can't remember
After that I tried to reboot my phone and hoping that it would somehow heal magically, which, of course, it didn't
What I did not do
Take a backup before I started to mess with my phone, stupid, yes I know, but tell me if you have to
What I am still able to do
E-recovery: can boot into E-recovery and connect to wifi and search for package info but then it fails with an error message stating that something is wrong with the package
Stock recovery dload method: Starting to install the package but halts at 5% and then the phone reboots and boots with error stating that I should update again, not sure about what package is loading since I think I have a dload folder both on the internal and the external sd card, but I cant see the internal sd card anywhere (loading the external sd card through another phone)
Fastboot: can boot into fastboot with volume- and power button and do almost all the fastboot commands, but adb does not detect my phone.
What I have tried
Googled, looking here and searching deep inside myself for answers (without any luck, needles to say)
Tried downloading a stock rom NEM-L21***B132, Android 6.x Emui 4.1 and extracting boot.img, system.img, recovery.img and cust.img and while boot and recovery flashes fine with this extracted images everything goes ape**** when trying to flash cust and system, with cust I get a partition error while writing and with system I get a sparse flash write failure, I have no idea why this rom fails while I'm able to flash above mentioned files perfectly fine with a stock nougat rom (Nougat is the reason I started this adventure to begin with). When I flashed all the files fine and try to dload the whole update.app I get nowhere anyway, just a bootloop.
Tried to erase and reformat cust and system but when I try that in fastboot I get a remote: command not allowed.
Tried to flash twrp recovery and the flashing succeeds but I cant boot into it, tried several different versions designed for both 'nougat and marshmallow.
What I need
Someone to point me in the right direction because I am totally lost and almost going crazy after trying everything.
All the help and tips I can get from you guys is much appreciated, I'm willing to try everything you throw at me and answer any questions regarding my issue!
Thanks in advance, Jeremias

dload method, use B100 package.

thelous said:
dload method, use B100 package.
Click to expand...
Click to collapse
Thanks for your fast reply, I do have a few questions for you:
1. Do you have any idea where I can find the B100 package? Tried googling but no luck so far, lowest I can find i B130.
2. Should I just put it on the external SD card and try to get it to update or do I need to extract the *.img and flash them in?
3. Could it be a problem that I might have a dload folder on the internal SD card with a different package?
Thanks again.

jerre84 said:
Thanks for your fast reply, I do have a few questions for you:
1. Do you have any idea where I can find the B100 package? Tried googling but no luck so far, lowest I can find i B130.
2. Should I just put it on the external SD card and try to get it to update or do I need to extract the *.img and flash them in?
3. Could it be a problem that I might have a dload folder on the internal SD card with a different package?
Thanks again.
Click to expand...
Click to collapse
i think somewhere in xda theres B100. all you need is update.app file in dload folder on external SD card (recovery wonr read internal memory since it could be corrupted etc...)

thelous said:
i think somewhere in xda theres B100. all you need is update.app file in dload folder on external SD card (recovery wonr read internal memory since it could be corrupted etc...)
Click to expand...
Click to collapse
Found it, crossing my fingers that it will work this time.

Unfortunately I can't get it to update with the B100 package and the dload method. I can start the stock recovery and the update starts but it freezes at 5% and then the phone reboots with no error message and the bootloop continues.
Any more ideas?

Still no luck for me, anyone got any ideas?

jerre84 said:
Still no luck for me, anyone got any ideas?
Click to expand...
Click to collapse
what was your phone build number before all these? EMUI 4 or 5?

shashank1320 said:
what was your phone build number before all these? EMUI 4 or 5?
Click to expand...
Click to collapse
It was EMUI 4. The reason for all this was that I could not get the Nougat-update in any way.
I think that I might be on EMUI 5 now because I can't get the stock recovery from the B100/B132 package to boot but when I flash the recovery from B351 or similar it can boot but I'm, still not able to get any update to work.

jerre84 said:
It was EMUI 4. The reason for all this was that I could not get the Nougat-update in any way.
I think that I might be on EMUI 5 now because I can't get the stock recovery from the B100/B132 package to boot but when I flash the recovery from B351 or similar it can boot but I'm, still not able to get any update to work.
Click to expand...
Click to collapse
I had same issue on mine. I updated to nougat manually with few bugs and then flashed custom arsenic ROM

Bricked Honor 5c NEM-L51 ?

Hi, I think i've kinda bricked my honor 5C (nem-l51), and I really need help :
A few years ago I rooted my phone to make otg work.
It worked a little while, but then a system update came up, could not update because of the twrp, so I tried to unroot it (from supersu) to do the update, and the twrp stayed after the unroot.
I stayed with the phone like this, twrp installed and update pending (still trying to install the update from time to time) and then I had to use OTG again and tried to re-root my phone.
I tried to flash the supersu files I used the first time, but, even when the flashing worked, I couldn't see the supersu app on the phone, still unrooted.
Then I tried to change the twrp (via fastboot) and I realised that I couldn't : I get the "command not allowed" failure when the recovery should get written. I tried with numerous twrp versions, and stock recovery.
So my twrp right now is the twrp-3.1.1-0-venus "OpenKirin edition" one.
The phone says it's unlocked and the frp is locked, but I can't remember if it was already the case or not when I first rooted.
I unfortunately don't have anymore the bootloader unlock code that huawai gave me originally. I have no idea how to get it again, to try to re-lock/unlock the bootloader.
Back then when I first rooted my phone, I made a back up, so I tried to restore that back up. It failed, first with "cannot wipe the cust partition". Then I tried to restore without restoring the cust partition, and I got "extracttarfork() process ended with error 255" while the system was restoring.
After that, the phone wouldn't boot into android anymore. It would be stuck at the unlocked bootloader warning message and then reboot after a few minutes.
So, lastly, I tried to install the unofficial lineageOS port from here : https://forum.xda-developers.com/honor-5c/development/rom-lineageos-14-1-honor-5c-t3713911 with my twrp.
The installation went well, but the phone is stuck while first booting in lineageOS (I let it overnight, restarted it, re-installed it, tried with the first release, nothing).
TL;DR: My phone isn't booting and I can't flash any new recovery.
Please, help me to get my phone working again

Give me the
old build number on emui
Update build you received..
Twrp working?
Fastboot?
Erecovery?

I got access to erecovery, even if the "download latest version and recovery" doesn't work. (erecovery connects to wifi, and the first thing it tries to check/download fails)
I can boot into fastboot but can't flash recovery from there because of the command not allowed problem.
I can boot into twrp, but the back up I tried to restore and the lineageos rom I tried to install both failed, so maybe the twrp has a problem?
I'm sorry I'm not sure about the build number, I'm pretty sure I was on EMUI 5.0 and android 7.x, and I think I remember comparing current build number vs the update, and it was something like B350 or B351 for the current, and B355 or B375 for the update.
I've found this in my backup file 'recovery.log' ro.omni.version=6.0.1-20160703-nemo-HOMEMADE and ro.build.id=MOB30M . So, that mean that I had android 6.x when I did the backup, way back at the beginning.
I thought the update never got installed because each time the phone would reboot to complete installation, it would reboot into twrp. But I've still updated from android 6 to android 7 somehow ?

NEM-L51C432 or NEM-L51C10 ?

NEM-L51C432 and I'm sure of that ^^

Zhyrclew said:
NEM-L51C432 and I'm sure of that ^^
Click to expand...
Click to collapse
Flash this via twrp
http://update.hicloud.com:8180/TDS/...-L51_hw_eu/update_data_full_NEM-L51_hw_eu.zip
Once done, boot to twrp and flash this
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1581/g104/v82938/f1/full/update.zip
Reboot.
If you are unable to flash the 2nd link then just use the dload method to flash this. If you are not aware of dload method, link is given in my signature.
Note, this 2nd firmware will replace your twrp with stock recovery. You should boot to b350 version and it will be full stock. Reason for flashing data file first is it doesn't replace the recovery to stock but just flashes your data, settings, apps. And 2nd link is main full firmware which will replace your boot, recovery, vendor everything and should boot.
Good luck

I flashed the first one, no error.
The second one had multiple errors :
"[...]
write radio image...
32k crc checked failure
E:unknown command [errno]
update_huawai_pkg_from_ota_zip: update package from zip failed
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/update.zip'
Updating partition details...
...done
"
So I tried the dload method, and the installation started and ended at 5% with this error :
"Software install failed!
Incompatibility with current version.
Please download the correct update package."
I guess it's because I couldn't tell you the exact build number, I'm sorry for not taking note of it.
If there is a way for me to get the build number despite the status of the phone, i'm ready to do it.
If not, I'm ready to try as many versions as it takes to find the good one.
PS: I've still access to the twrp, thank god ! That was my biggest fear, because I can't flash any recovery in the current state.

Zhyrclew said:
I flashed the first one, no error.
The second one had multiple errors :
"[...]
write radio image...
32k crc checked failure
E:unknown command [errno]
update_huawai_pkg_from_ota_zip: update package from zip failed
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/update.zip'
Updating partition details...
...done
"
So I tried the dload method, and the installation started and ended at 5% with this error :
"Software install failed!
Incompatibility with current version.
Please download the correct update package."
I guess it's because I couldn't tell you the exact build number, I'm sorry for not taking note of it.
If there is a way for me to get the build number despite the status of the phone, i'm ready to do it.
If not, I'm ready to try as many versions as it takes to find the good one.
PS: I've still access to the twrp, thank god ! That was my biggest fear, because I can't flash any recovery in the current state.
Click to expand...
Click to collapse
You may try other higher versions like 360, 370 etc and see your luck. Twrp will be replaced only if the installation os successful for the main firmware. Its just a trial and error for you now but I am 99% sure you should be able to revive the phone via dload method

Thank you, it's reassuring. I will not give up until I test all the versions ^^
Could you help me a little bit to find other versions, please ? The only place I know where there is update packages for my phone is there : https://forum.xda-developers.com/ho...lota-upgrade-packages-models-nem-l51-t3473110 and there is only two versions.

Zhyrclew said:
Thank you, it's reassuring. I will not give up until I test all the versions ^^
Could you help me a little bit to find other versions, please ? The only place I know where there is update packages for my phone is there : https://forum.xda-developers.com/ho...lota-upgrade-packages-models-nem-l51-t3473110 and there is only two versions.
Click to expand...
Click to collapse
Firmware finder website

Wow, thank you, I downloaded the firmware finder software, it has everything.
Should I flash the firmware in two steps like you first made me, or should I just try with only the dload method with the fullOTA firmware ?

Zhyrclew said:
Wow, thank you, I downloaded the firmware finder software, it has everything.
Should I flash the firmware in two steps like you first made me, or should I just try with only the dload method with the fullOTA firmware ?
Click to expand...
Click to collapse
Check dload guide in my signature. You can follow that now. Good luck

I tried b355, b361, b375, b377, nothing changes, same error.
I noticed that I have something related to an update in my sd card AND internal storage->HwOUC->140783->( update.zip[1.32GB], update_data_full_public.zip[344MB], update_full_NEM-L51_hw_eu.zip[412MB] )
I don't know whether these files were there before I did all these attempted updates.
Could it be that my phone is not trying to install the files I put in sdcard->dload, because he finds these files in the internal memory first, and each time try to install these ?
Should I delete them, move them, unzip them in dload folder ?

Zhyrclew said:
I tried b355, b361, b375, b377, nothing changes, same error.
I noticed that I have something related to an update in my sd card AND internal storage->HwOUC->140783->( update.zip[1.32GB], update_data_full_public.zip[344MB], update_full_NEM-L51_hw_eu.zip[412MB] )
I don't know whether these files were there before I did all these attempted updates.
Could it be that my phone is not trying to install the files I put in sdcard->dload, because he finds these files in the internal memory first, and each time try to install these ?
Should I delete them, move them, unzip them in dload folder ?
Click to expand...
Click to collapse
Copy them on PC and then try dload of files you downloaded from Firmware finder website.
These are files your phone downloaded for OTA update but as you were on twrp, they never installed it amd stays there

I copied the updates my phone downloaded on PC and then deleted them both on internal storage and sd card.
Then I tried dload method with b355,b375&b377 from firmware finder, and also with the update.zip I found in the updates my phone downloaded.
Nothing worked, all of them got the error "Incompatibility with current version. Please download the correct update package."
Should I try even more firmware versions, or should I try something else ?
Btw, I noticed my phone, when connected to my PC, is labeled as huawei-P9-lite, and I don't think it was always like that, but it's probably just because the twrp-3.1.1-0-venus.img is originally for the P9 lite.

I came accross this thread, where somebody recommends to flash stuff from fastboot.
I have not tried it yet, I only tried to flash recovery from fastboot, and it is failing with the "command not allowed". But maybe I could try to flash some other things ? Any advice ?
For now, despite all my attempts to install stock OTA via dload method, the phone is still trying to boot into lineageOS, and failing.

I came across the "current" firmware version with a check with DC-unlocker : "NEM-L51C432B120"
So I downloaded full OTA firmware b120 on firmware finder software, and the dload method worked !
The installation went well, and after a few minutes of the first boot, I got into phone configuration.
I have one last problem, though : the phone configuration is looping.
There is only 4 languages to choose, so I have to choose english(US), then there is a weird list of countries, none in the EU, where I feel i have to choose united states, then after some steps I have to register to huawei ID thing.
If I try to skip it, it loops to the language selection.
If I try to log in to my original account, it says "device not supported for your location" and then loops to languages. (my original account is in french/France)
If I try to create a new account with new address mail, it works but then at the end says again that "device not supported for your location" and then loops to languages.
I tried with other countries it still loops.
The other languages seems to be Chinese and Japanese, but the configuration is looping too if I choose them.
I tried with/without sim, with/without wifi connected...

Dload the next firmware now and see if it works. Then set the phone

I downloaded and installed with dload method (by removing sd card and copying directly on it the files, because I don't know how to have access to the phone internal & external memory now) the next firmware (b130 version)
The phone booted, it launched a "system optimization" that was a few minutes long, and then the EMUI configuration poped up and looped through language selection, region(country), wifi connection (successful), terms and conditions, and WLAN+(switch between wlan and mobile data automatically).
I feel like the phone is working, the notification led is even blinking when I receive sms, but I have access to nothing because of this damned configuration.
Note: the connection to huawei ID isn't prompted again in the loop once I log in, from the original or the new account. In order to be prompted again to log in to the huawei ID, I have to go to erecovery and reset to factory the phone.

OTA Failed - Recovery Mode Not Detected Need Assistance

I need assistance as the title says. First up my bootloader is not unlockable, (believe me I've tried) and here is my situation. I cannot flash the next OTA, because of failed error in recovery upon trying to install. There is no full firmware to reflash the device, only an OTA that I obtained (and yes it is completely for my phone model) (XT1925DL). I would sideload the OTA or apply it from sdcard in the recovery, however the device is not detected on Windows via adb or on linux, after hitting the sideload zip option, and Sdcard cannot mount. I get (sdcard failed to mount, E: installation aborted in recovery). If someone knows an option to maybe allow me to use the OTA file to repatch the system, without having to resort to the recovery mode, or adb sideload option, it would be appreciated if you could help.

hydroman202 said:
I need assistance as the title says. First up my bootloader is not unlockable, (believe me I've tried) and here is my situation. I cannot flash the next OTA, because of failed error in recovery upon trying to install. There is no full firmware to reflash the device, only an OTA that I obtained (and yes it is completely for my phone model) (XT1925DL). I would sideload the OTA or apply it from sdcard in the recovery, however the device is not detected on Windows via adb or on linux, after hitting the sideload zip option, and Sdcard cannot mount. I get (sdcard failed to mount, E: installation aborted in recovery). If someone knows an option to maybe allow me to use the OTA file to repatch the system, without having to resort to the recovery mode, or adb sideload option, it would be appreciated if you could help.
Click to expand...
Click to collapse
Is it a TracFone? You're probably going to have to flash in Fastboot.
Download the most recent firmware here:
https://mirrors.lolinet.com/firmware/moto/ali/official/TRAC/
And use this guide to flash:
https://forum.xda-developers.com/moto-g6/how-to/guide-faster-updated-guide-to-root-t3914228

Ragarianok said:
Is it a TracFone? You're probably going to have to flash in Fastboot.
Download the most recent firmware here:
https://mirrors.lolinet.com/firmware/moto/ali/official/TRAC/
And use this guide to flash:
https://forum.xda-developers.com/moto-g6/how-to/guide-faster-updated-guide-to-root-t3914228
Click to expand...
Click to collapse
I appreciate the response. Unfortunately that site is not up to date with the TracFone firmware. The latest official one I have. And I can't flash it unfortunately because I'm on a newer firmware and it throws security downgrade errors when I try. If I could figure out how to get recovery mode to show up on my pc I would be ok.... Then I would be able to apply the OTA I need for the next one to complete successfully.

hydroman202 said:
I appreciate the response. Unfortunately that site is not up to date with the TracFone firmware. The latest official one I have. And I can't flash it unfortunately because I'm on a newer firmware and it throws security downgrade errors when I try. If I could figure out how to get recovery mode to show up on my pc I would be ok.... Then I would be able to apply the OTA I need for the next one to complete successfully.
Click to expand...
Click to collapse
Have you tried to run those Fastboot commands without:
Code:
[I]fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img[/I]
Should work if you exclude those two; that's what I did to downgrade from Pie back to Oreo.
You could also try Lenovo Moto Smart Assistant.

I just realized that I totally misread your original post and, man, I feel like a total dummy.
Is the OTA currently on the root of your phone's internal storage?
If it's an actual update.zip file and it's in the root of your internal storage, you could try going into Settings/Apps & notifications/Apps info (tap the down arrow and select Show system)/Moto Update Services and make sure that Storage permission is toggled on. After that, try to perform an update.
I had a similar error when trying to sideload with ABD and update from SD in recovery, but it turned out that I was trying to update using full firmware.
Can you link the update file you have?

Ragarianok said:
I just realized that I totally misread your original post and, man, I feel like a total dummy.
Is the OTA currently on the root of your phone's internal storage?
If it's an actual update.zip file and it's in the root of your internal storage, you could try going into Settings/Apps & notifications/Apps info (tap the down arrow and select Show system)/Moto Update Services and make sure that Storage permission is toggled on. After that, try to perform an update.
I had a similar error when trying to sideload with ABD and update from SD in recovery, but it turned out that I was trying to update using full firmware.
Can you link the update file you have?
Click to expand...
Click to collapse
Unfortunately I cannot not link it but the file size of the ota is roughly 1.47 GB. And the ota was a upgrade to pie. I'm still on that one. Needing to reflash it so I can correct a partition issue. That's preventing the next ota from succeeding. The reason the next one doesn't succeed is because it checks the modem partition and it unfortunately fails to verify it because I accidentally flashed the wrong one. The ota should patch the modem in the device now I'm thinking because the modem that is currently on the device is the one before the ota arrived. All other partitions are the ones meant for the current firmware.

hydroman202 said:
Unfortunately I cannot not link it but the file size of the ota is roughly 1.47 GB. And the ota was a upgrade to pie. I'm still on that one. Needing to reflash it so I can correct a partition issue. That's preventing the next ota from succeeding. The reason the next one doesn't succeed is because it checks the modem partition and it unfortunately fails to verify it because I accidentally flashed the wrong one. The ota should patch the modem in the device now I'm thinking because the modem that is currently on the device is the one before the ota arrived. All other partitions are the ones meant for the current firmware.
Click to expand...
Click to collapse
Hm.
You could try to use the Lenovo Moto Smart Assistant. It has a Rescue option that returns the phone to stock firmware. It also has an Upgrade option; I've tried it but there aren't any updates for my phone. You could Rescuing and then Upgrading. Or you could Rescue and then try the OTA again.
The only downside is that everything on your phone's internal storage will be erased.