Database Develop

[Q] From FRF91 to european vodafone FRF91

Hi, I am now on FRF91. And I would like to move to the european vodafone version which came out a little later.
I initially had a EPF30 vodafone rom and flashed it to the US FRF91 a couple of months ago using the XDA guide "EPE54B (new N1- AT&T) -> FRF50 -> FRF83 & beyond (hopefully) in 20 minutes". I can't post the link here because I am a new user and am not allowed to post links, but the steps were:
-Initial setup
-Unlock bootloader
-Install (flash) recovery
-Rooting
-INSTALL FRF50 with Radio
-FRF50 -> FRF83
I think that by updating from FRF83 to FRF91 I lost root access.
How would I now install the the european FRF91 rom? I tried putting this file:"6f7c048b246c.OTA_Passion_Vodafone_Generic_2.15.151.5_R_FRF91-1.14.1700.1_EPF30_release_signed.zip" (42mb) on my sd card and renaming it to update.zip and then flashing it, but I got a verification error. Do I need to follow the rooting steps again? or do I need another rom file?
I would appreciate any advice.
Thanks!

Out of interest, why do you want to? All it means for you is you'll get OTA updates about a month and half later than the rest of us.
Anyhow, what you have to do is download this: http://shipped-roms.com/shipped/Pas...on_VF_2.15.151.5_R_FRF91_MFG_Shipment_ROM.zip
Rename it to PASSIMG.zip and copy it to the root of your SD card. Power off the phone, hold Vol- and power it on. It'll boot into the bootloader, find the file and ask if you wish to install it.
DOING THIS WILL WIPE YOUR PHONE

Thanks.
I tried doing the 2.2.1 OTA update, but i got an assertion error somewhere during verification. And putting the update on my SD card i also got a verification error (a different one). I was hoping that maybe I could update to 2.2.1 from the european FRF91. Do you know an easier way to perform the update?

Unfortunately the Vodafone version of FRF91 isn't compatible with FRG83, so you'd be no better off.
You can get FRF91 direct from HTC, which I assume is the 'original' one: http://developer.htc.com/ and start again.
It's called "Nexus One FRF91 system image"
Do you have a custom recovery installed? Updates don't get on with them.

The FRF91 I have now is also the original one. And yes, I have Amon_RA's recovery img installed. Does that mean I can't get 2.2.1 on my phone?

Yes.
You need either stock recovery, or a recovery that doesn't check signatures, like RA 1.8.0.x or ClockworkMod.

Ok, but can I still use the method you described in your first post (Rename it to PASSIMG.zip etc.)? And just wait until there is a full 2.2.1 rom instead of the 2.2.1 update files?

Yes you could do that, seems kinda pointless though when it takes 10 seconds to switch to a compatible recovery

Oh ok
So I could just download the latest amon ra recovery and follow the same steps I followed the first time:
INSTALL(FLASH) RECOVERY
1) Download the latest Amon_RA's recovery img from here
2) move it to "C:\android-sdk-windows\tools" .
3) On your computer open a command window. 'start -> Run -> type 'cmd' -> hit 'ENTER'.
4) On the command screen: Type "cd c\" ; Hit 'ENTER' key
5) Then Type: "cd C:\android-sdk-windows\tools" ; Hit 'ENTER' key
6) On you computer's command window -- Type: fastboot devices and make sure your device's number is showing up.
7) On you computer's command window -- Type: fastboot flash recovery recovery-RA-nexus-v1.7.0.img
8) It should say: sending 'recovery' (3962 KB)... OKAY . . . . . writing 'recovery'... OKAY This should take a few seconds.
9) If flashing the recovery was successful, use the menu options to boot directly into recovery, or restart your phone normally.(without going to the bootloader screen).

Yes, although get v1.8.0.1, not v1.7.0

Rusty! said:
Yes, although get v1.8.0.1, not v1.7.0
Click to expand...
Click to collapse
Ah right, I meant 1.8.0.1. I just copy pasted the old tutorial. I don't need root for this right? Sorry for all the questions but I'm scared of destroying my phone.

Nope, no root as you've unlocked the bootloader.

Ok thanks alot! I'm gonna try it tonight and I'll post the result
EDIT: It works! Couldn't get the amon ra recovery installed (it just got stuck on "sending recovery"), so I installed clockworkmod instead, using the rommanager. (I had to root first using the 1click root app). But after that the update to 2.2.1 by placing the update.zip on the sd card worked fine. Thanks again for the advice Rusty!

Help! OTA - Rebooting

I got a message on my XT1053 Dev that there's a system update. (I'm running stock) I let it download, and then it wanted to reboot. Ok, but it came up in TWRP. I tried rebooting from TWRP every way, but it would not go into maintenance so it could flash the new firmware.
Now whenever I boot it normally, it comes up, and then immediately shuts down, I guess because it wants to upgrade.
What is wrong with this thing?

Quantumstate said:
I got a message on my XT1053 Dev that there's a system update. (I'm running stock) I let it download, and then it wanted to reboot. Ok, but it came up in TWRP. I tried rebooting from TWRP every way, but it would not go into maintenance so it could flash the new firmware.
Now whenever I boot it normally, it comes up, and then immediately shuts down, I guess because it wants to upgrade.
What is wrong with this thing?
Click to expand...
Click to collapse
You must be on stock recovery in order to OTA update. Try going into adb and flashing back to stock recovery and it should work.
Make sure you have mfastboot set up and working, if you need the file respond to this post and I can supply it for you.
Download the stock recovery from here (and make sure it's in your "android" folder)
Boot your phone into fastboot with
adb reboot bootloader
Click to expand...
Click to collapse
-OR-
While the phone is off, hold the PWR button and the Volume Down buttons at the same time for ~5 seconds. Release the PWR button ONLY and continue holding Volume Down until you see the fastboot screen.
Next
Then in adb on your computer perform:
mfastboot flash recovery *filename*
mfastboot reboot
Click to expand...
Click to collapse
When it reboots into the OS it should try to install the update again, like you said it was doing. When it reboots it should update correctly via stock recovery.
Emphasis on should. I can't guaruntee this will work but this is based on my prior knowledge and experience. Good luck and report back with success/problems!

Quantumstate said:
I got a message on my XT1053 Dev that there's a system update. (I'm running stock) I let it download, and then it wanted to reboot. Ok, but it came up in TWRP. I tried rebooting from TWRP every way, but it would not go into maintenance so it could flash the new firmware.
Now whenever I boot it normally, it comes up, and then immediately shuts down, I guess because it wants to upgrade.
What is wrong with this thing?
Click to expand...
Click to collapse
There's nothing wrong with this thing....
All of the guides here exist for a reason. One responsibility you have once you have decided to root your device or install custom recovery, is that when a new OTA comes out, you must check back here at XDA to see what the procedure for installing it is.
All of the guides here tell you that you MUST have stock recovery in order to accept any updates.
Here's how you will fix it:
Boot into TWRP. Clear your cache. This will prevent the constant reboots.
Now, use fastboot to flash back the stock recovery. You will need to download the 4.4.2 SBF for your XT1053 from here: http://sbf.droid-developers.org/phone.php?device=0
Extract the archive. You only need one file: recovery.img
You should already have the android SDK installed since you unlocked your BL and flashed TWRP. Use fastboot to flash the stock recovery:
fastboot flash recovery recovery.img
Now you can accept the OTA from your phone. You may need to go to Settings > About Phone > System Updates and re-download it.
The OTA should now successfully install (assuming you aren't using Xposed or made any other modifications).
Now, you can flash TWRP recovery back. Let us know how it works out for you...

Thanks, but the update was unsuccessful.
I seem to remember that the update checks existing files, and if one has the wrong CRC it fails. Well I'm stock but rooted. It is a develoepr's phone and there is no developer's image on those sites.

Quantumstate said:
Thanks, but the update was unsuccessful.
I seem to remember that the update checks existing files, and if one has the wrong CRC it fails. Well I'm stock but rooted. It is a develoepr's phone and there is no developer's image on those sites.
Click to expand...
Click to collapse
The GSM Developer edition uses the SAME exact software as the T-Mobile version. The T-Mobile variant has zero bloat, and no carrier branding. The only difference between the two is that you don't lose your warranty when you unlock the GSM Dev edition.
You're looking for the XT1053 T-Mobile SBF
http://sbf.droid-developers.org/phone.php?device=0

Quantumstate said:
Thanks, but the update was unsuccessful.
I seem to remember that the update checks existing files, and if one has the wrong CRC it fails. Well I'm stock but rooted. It is a develoepr's phone and there is no developer's image on those sites.
Click to expand...
Click to collapse
I always seem to have something in /system that messes with the ota update. In addition to flashing stock recovery to replace twrp, I also flash system.img (with mfastboot only) from the same sbf as you get the recovery.img. Then the ota goes through without a hitch.

Still Errors at the robot with spinning diamond heart, even with TMO_RETAIL_XT1053_4.4.2-KXA20.16-1.25_MR3_CFC.xml/recovery.img.
Looking around it seems that here are some rules. I think I'm violating #2: "Inside the OTA is a manifest file. It contains a list of files and their check sums it expects to be on your phone. If the files are missing, or the check sum for a particular file doesn't match (because you've replaced or altered the file), the OTA will fall." I've removed most of the G**gle junk since I don't trust them.
So if this is what they require, Hell with them. If it were possible to put multiboot on the Moto X I would have done it a long time ago. Maybe I can apply this OTA update in some other way? Without going through their rinky-dink tests?

Quantumstate said:
Still Errors at the robot with spinning diamond heart, even with TMO_RETAIL_XT1053_4.4.2-KXA20.16-1.25_MR3_CFC.xml/recovery.img.
Looking around it seems that here are some rules. I think I'm violating #2: "Inside the OTA is a manifest file. It contains a list of files and their check sums it expects to be on your phone. If the files are missing, or the check sum for a particular file doesn't match (because you've replaced or altered the file), the OTA will fall." I've removed most of the G**gle junk since I don't trust them.
So if this is what they require, Hell with them. If it were possible to put multiboot on the Moto X I would have done it a long time ago. Maybe I can apply this OTA update in some other way? Without going through their rinky-dink tests?
Click to expand...
Click to collapse
You are correct on the manifest.
Instead, just flash the entire stock SBF (TMO_RETAIL_XT1053_4.4.2-KXA20.16-1.25). The manual method is easiest.
Or you could just flash the system.img as the earlier poster suggested.
This will revert to stock, and you will have to reinstall your apps, but the OTA WILL work afterwards. You really should consider just 'freezing' the google apps instead of removing them this time...
The only other way you will be able to install the OTA is to put all the gapps back on...but I doubt you made a backup, right?
mfastboot flash system system.img
that should be all you need (beside stock recovery, of course). Then take the update, and finally do whatever mods you want remembering that you will HAVE to un-do the mods to be able to accept future OTAs without returning to 100% stock again.
Good Luck

Flashing system.img will not require you to reinstall your downloaded apps, just apps you installed as system apps via root access. Downloaded apps are in the /data/app partition that is not affected by a system.img flash.

I finally went this route. I'm not putting up with their OTA requirements; I'll get the upgrade without them. Although, that 4.3 sure has alot of G**gle and Motorola bloatware to remove.
With Xposed, GravityBox (and other modules) I now have the flexibility I was looking for.
Now all I need is a better dialer than the crappy G**gle one, and secure SMS.

[Q] Rooted/Unlocked but can't update to 4.2 to 4.3! [XT1058]

Ok guys, so here's what's happening with my Device XT1058. I literally can't install it!
When I try to return to stock and put the first one code that says "fastboot flash partition gpt.bin", it says:
<bootloader> variable not supported!
error: cannot load 'gpt.bin'.
2- When I try to do it by the RSDLite trying to load the 4.2 stock in there is says: "Error check input file. Either XML format is wrong or image files associated with it are missing"
I really don't know what's going on. Ive seen a video with the same model/device as mine and it went perfectly the ROOT/UNLOCKING BOOTLOADER. I did everything as it says on the video but it comes to update the android, I just cant proceed it.
My firmware operator is: Oi. From Brazil.
--
When I try to put the 4.4.3 in the Internal Storage:
1- Trying to install it from "System Updates" just doesn't work. Pops up the same old image as always "Your system is up to date, option: OK"
Then I try to do it manually by going to the Internal Storage in the phone, the zip file appears but I can't click on it.
Can someone help me to fix this problem ? Thanks!
OBS: I DID Install the BOOTLOADER and ROOT my phone perfectly as long as I can use it as a developer. But can't install either 4.2/4.3 rom in any ways I did as I explained it on the top.

Liooh said:
Ok guys, so here's what's happening with my Device XT1058. I literally can't install it!
When I try to return to stock and put the first one code that says "fastboot flash partition gpt.bin", it says:
<bootloader> variable not supported!
error: cannot load 'gpt.bin'.
2- When I try to do it by the RSDLite trying to load the 4.2 stock in there is says: "Error check input file. Either XML format is wrong or image files associated with it are missing"
I really don't know what's going on. Ive seen a video with the same model/device as mine and it went perfectly the ROOT/UNLOCKING BOOTLOADER. I did everything as it says on the video but it comes to update the android, I just cant proceed it.
My firmware operator is: Oi. From Brazil.
--
When I try to put the 4.4.3 in the Internal Storage:
1- Trying to install it from "System Updates" just doesn't work. Pops up the same old image as always "Your system is up to date, option: OK"
Then I try to do it manually by going to the Internal Storage in the phone, the zip file appears but I can't click on it.
Can someone help me to fix this problem ? Thanks!
OBS: I DID Install the BOOTLOADER and ROOT my phone perfectly as long as I can use it as a developer. But can't install either 4.2/4.3 rom in any ways I did as I explained it on the top.
Click to expand...
Click to collapse
You appear to be going about this wrong. You don't put the SBF files on the phone itself...you put them on your PC, in the same folder that fastboot and mfastboot are located.
The error you are receiving "error: cannot load gpt.bin" indicated that the file you are trying to flash is NOT in the same folder as fastboot/mfastboot.
Additionally, there is no "4.2" or "4.3" for the Moto X. There is 4.2.2, 4.4, 4.4.2, and now 4.4.3 (which may or may not have been released for your carrier yet).
Can you explain exactly what you are doing? Where did you get the SBF file to flash back to stock? Did you extract the archive? And make sure you are using the correct firmware for YOUR carrier. We don't like to support people who try to flash other carrier's ROMS to their phone. This can cause issues.

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.