Develop Bugs

dload method stuck at 5%

Hi,
My phone is stuck at boot
error boot.img
keeps rebooting, unable to boot to recovery (can only access erecovery)
bootloader unlocked, frp locked
I tried using dload method to flash stock firmware but each time installation fails at 5% and I am not getting anywhere with it.
MODEL - BND-AL10
How can i recover my phone from this state? Please help!

lalitkhokhar said:
Hi,
My phone is stuck at boot
error boot.img
keeps rebooting, unable to boot to recovery (can only access erecovery)
bootloader unlocked, frp locked
I tried using dload method to flash stock firmware but each time installation fails at 5% and I am not getting anywhere with it.
MODEL - BND-AL10
How can i recover my phone from this state? Please help!
Click to expand...
Click to collapse
They did something different for dload on this phone.
It needs special firmware to dload
We found that service firmware for l21c432 will get the phone working again, then use hwota to restore correct region firmware

mrmazak said:
They did something different for dload on this phone.
It needs special firmware to dload
We found that service firmware for l21c432 will get the phone working again, then use hwota to restore correct region firmware
Click to expand...
Click to collapse
what is hwota?
will i need to keep all files in dload folder or just the update.app?
is service firmware same as the full ota which is found on Firmware finder?
and there are two type of full ota FullOTA-MF and FullOTA-MF-PV which one should i download

lalitkhokhar said:
what is hwota?
will i need to keep all files in dload folder or just the update.app?
is service firmware same as the full ota which is found on Firmware finder?
and there are two type of full ota FullOTA-MF and FullOTA-MF-PV which one should i download
Click to expand...
Click to collapse
Service rom is different then fullOTA.
From the screenshot you have . The fullota-mf-pv examples are Oreo and the ones without the pv are nougat.
This separation is not allways Oreo/ nougat, but only in your example.
HWOTA is a method to force install fullOTA files that uses a modified stock recovery that bypasses version verifications.
Here is link.--( there is other hwota too. One that has more batch file script and incorporate bootloader unlock and device rebranding. )
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
And service rom was found on rusian site 4pda.
The file download there has reached a download limit and forces you to sign up for a Yandex account. I copied the service rom to Android file host.
Service rom BND-L21C432
https://www.androidfilehost.com/?fid=11050483647474828964
1. Unzip download
2. copy the dload folder to root of sdcard
3. power on phone holding all three buttons
4. After phone finishes and reboots, unlock frp and bootloader, if needed
5. Use Huru or HWOTA to flash correct firmware for your model/ region.

mrmazak said:
Service rom is different then fullOTA.
From the screenshot you have . The fullota-mf-pv examples are Oreo and the ones without the pv are nougat.
This separation is not allways Oreo/ nougat, but only in your example.
HWOTA is a method to force install fullOTA files that uses a modified stock recovery that bypasses version verifications.
Here is link.--( there is other hwota too. One that has more batch file script and incorporate bootloader unlock and device rebranding. )
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
And service rom was found on rusian site 4pda.
The file download there has reached a download limit and forces you to sign up for a Yandex account. I copied the service rom to Android file host.
Service rom BND-L21C432
https://www.androidfilehost.com/?fid=11050483647474828964
1. Unzip download
2. copy the dload folder to root of sdcard
3. power on phone holding all three buttons
4. After phone finishes and reboots, unlock frp and bootloader, if needed
5. Use Huru or HWOTA to flash correct firmware for your model/ region.
Click to expand...
Click to collapse
thank you! I will try this.

@mrmazak Thank you very much! L21 firmware worked and I am running it without any issue.
What difference does it make as now I am using BND-L21 firmware instead of BND-AL10?
Acc. to me this Rom is better as there are very few bloatware installed as compared to AL10 and everything seems to work fine.
In About Phone only things changed are-
Build number
Baseband Version
Model and imei are same as before.
Does i really need to install AL-10 firmware again?

lalitkhokhar said:
@mrmazak Thank you very much! L21 firmware worked and I am running it without any issue.
What difference does it make as now I am using BND-L21 firmware instead of BND-AL10?
Acc. to me this Rom is better as there are very few bloatware installed as compared to AL10 and everything seems to work fine.
In About Phone only things changed are-
Build number
Baseband Version
Model and imei are same as before.
Does i really need to install AL-10 firmware again?
Click to expand...
Click to collapse
As long as the phone is working normally, I think you should be fine . But further updates will , of course, need to be manually done . Like this install was.

mrmazak said:
Service rom is different then fullOTA.
From the screenshot you have . The fullota-mf-pv examples are Oreo and the ones without the pv are nougat.
This separation is not allways Oreo/ nougat, but only in your example.
HWOTA is a method to force install fullOTA files that uses a modified stock recovery that bypasses version verifications.
Here is link.--( there is other hwota too. One that has more batch file script and incorporate bootloader unlock and device rebranding. )
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
And service rom was found on rusian site 4pda.
The file download there has reached a download limit and forces you to sign up for a Yandex account. I copied the service rom to Android file host.
Service rom BND-L21C432
https://www.androidfilehost.com/?fid=11050483647474828964
1. Unzip download
2. copy the dload folder to root of sdcard
3. power on phone holding all three buttons
4. After phone finishes and reboots, unlock frp and bootloader, if needed
5. Use Huru or HWOTA to flash correct firmware for your model/ region.
Click to expand...
Click to collapse
Restored my phone using the service firmware but the "OEM Unlock" option in the Developer Options is completely missing. Is there a fix for this?

XandeR180 said:
Restored my phone using the service firmware but the "OEM Unlock" option in the Developer Options is completely missing. Is there a fix for this?
Click to expand...
Click to collapse
Never saw that before, unless your phone in C00 or C01 (China region)
Try factory reset?
Then skip wifi and Google account, but set a lock screen pin or pattern. See if that helps.
Then share screenshot of "about phone". Block out imei number though.
Also which service ROM did you use. How did you use it. Did you change method from as described, did it flash both parts? The update and hw_update?

mrmazak said:
Never saw that before, unless your phone in C00 or C01 (China region)
Try factory reset?
Then skip wifi and Google account, but set a lock screen pin or pattern. See if that helps.
Then share screenshot of "about phone". Block out imei number though.
Also which service ROM did you use. How did you use it. Did you change method from as described, did it flash both parts? The update and hw_update?
Click to expand...
Click to collapse
Actually, my phone is a BND-L34 (Mate SE)
Performed a factory reset 3 times. Third time I set up a pattern but the option still hasn't appeared.
I used the ROM in the link you provided in your previous post (had no idea there were any others, as I haven't been able to find anything else).
Didn't change anything. Extracted the dload folder to my external SD card, powered on while holding all three buttons and the update itself went just fine. Also I'm not sure how to tell whether or not it flashed both parts.
Everything else SEEMS to be working. Haven't poked around or anything, nor have I tried my SIM card. However the only issue I'm coming across (that I actually care about at the moment) is the inability to enable OEM unlocking (not grayed out or anything. It's just completely missing).
Pictures below.

XandeR180 said:
Actually, my phone is a BND-L34 (Mate SE)
Performed a factory reset 3 times. Third time I set up a pattern but the option still hasn't appeared.
I used the ROM in the link you provided in your previous post (had no idea there were any others, as I haven't been able to find anything else).
Didn't change anything. Extracted the dload folder to my external SD card, powered on while holding all three buttons and the update itself went just fine. Also I'm not sure how to tell whether or not it flashed both parts.
Everything else SEEMS to be working. Haven't poked around or anything, nor have I tried my SIM card. However the only issue I'm coming across (that I actually care about at the moment) is the inability to enable OEM unlocking (not grayed out or anything. It's just completely missing).
Pictures below.
Click to expand...
Click to collapse
The system number ending in .046 is clue that the second part of service ROM did not load.
Before worrying about the oem toggle too much. Does the boooader screen show frp locked?

mrmazak said:
The system number ending in .046 is clue that the second part of service ROM did not load.
Before worrying about the oem toggle too much. Does the boooader screen show frp locked?
Click to expand...
Click to collapse
Nope. It just says "PHONE locked". Weird, I could've sworn it said frp locked the first time I went into fastboot

XandeR180 said:
Nope. It just says "PHONE locked". Weird, I could've sworn it said frp locked the first time I went into fastboot
Click to expand...
Click to collapse
Alright, oem unlock should work.
Then after the reset and boot up , back to fastboot to flash TWRP.
Then use hwota, and best to go with probably b330,

mrmazak said:
Alright, oem unlock should work.
Then after the reset and boot up , back to fastboot to flash TWRP.
Then use hwota, and best to go with probably b330,
Click to expand...
Click to collapse
WOW it actually worked!! I'm amazed that it was that simple. Thank you so much. I'll follow your HWOTA guide and keep you posted if anything goes wrong :good:

XandeR180 said:
WOW it actually worked!! I'm amazed that it was that simple. Thank you so much. I'll follow your HWOTA guide and keep you posted if anything goes wrong :good:
Click to expand...
Click to collapse
I did see one time the issue with unknown model and strange build number. And hwota did not help going from emui 8 to emui 8. But downgradeing from emui 8 to emui 5 fixed it. Then update back to 8 went normal

mrmazak said:
I did see one time the issue with unknown model and strange build number. And hwota did not help going from emui 8 to emui 8. But downgradeing from emui 8 to emui 5 fixed it. Then update back to 8 went normal
Click to expand...
Click to collapse
Actually, installing the update files for emui 8 while on emui 8 worked perfectly! At least I think. Everything looks normal so far, even the model number and build number

XandeR180 said:
Actually, installing the update files for emui 8 while on emui 8 worked perfectly! At least I think. Everything looks normal so far, even the model number and build number
Click to expand...
Click to collapse
Sounds good.
So now let me ask what was the issue you had to recover from. And I assume you had the unlock code already?
I ask because yesterday I was helping someone , also with mate se. They are trying to get uock code from DC unlock, but need to downgrade first. I had guided a downgrade this way before to get unlock codes , and it went just fine. But when you had the unknown model number, it makes me wonder what caused it, and of it could be avoided for the guy I'm helping now.

mrmazak said:
Sounds good.
So now let me ask what was the issue you had to recover from. And I assume you had the unlock code already?
I ask because yesterday I was helping someone , also with mate se. They are trying to get uock code from DC unlock, but need to downgrade first. I had guided a downgrade this way before to get unlock codes , and it went just fine. But when you had the unknown model number, it makes me wonder what caused it, and of it could be avoided for the guy I'm helping now.
Click to expand...
Click to collapse
As much as I would love to help, I really don't know what caused the unknown model number.
The reason I needed to restore my phone was because I had originally gotten the Oreo update through firmware finder because I never officially got the OTA (even though my IMEI was approved according to FF). The update seemed to have worked alright but one day my camera suddenly stopped functioning completely. Reboot didn't fix it. So I decided to factory reset it but that only ended in a bootloop.
I could have used TWRP to fix it but for some reason it would not boot into TWRP, so I opted for triggering an OTA installation through stock recovery but that didn't work (this was before I knew of the service ROM). So then I tried reflashing TWRP but I couldn't because I forgot to enable USB debugging. I knew I was done for at that point. And stupid me added to the problem by relocking the bootloader (I don't remember why I decided to do that).
So I hadn't touched the thing in months up until today to see if there was any new methods for restoring a bricked device. That's when I found some threads pointing towards a service ROM. And here I am.
Sorry that I couldn't provide any specific details. Some things I just forgot and some things I don't even know the cause of (like the camera malfunctioning and the bootloop after factory resetting).

Bricked device? Tried to downgrade to oreo help?

Hello, I tried downgrading today to oreo (from official version of pie) because I wanted to root and flash resuruction remix rom. I unlocked my bootloader and then I installed android oreo from the website for pixel 2 xl, copied the files into the adb directory and ran the "flash-all" batch file. But now my device is stuck at the google screen with the unlcoked lock image, before this screen it says that my device is corrupt. How can I solve this issue and go back to oreo?
Thanks

abdane said:
Hello, I tried downgrading today to oreo (from official version of pie) because I wanted to root and flash resuruction remix rom. I unlocked my bootloader and then I installed android oreo from the website for pixel 2 xl, copied the files into the adb directory and ran the "flash-all" batch file. But now my device is stuck at the google screen with the unlcoked lock image, before this screen it says that my device is corrupt. How can I solve this issue and go back to oreo?
Thanks
Click to expand...
Click to collapse
Please list your exact steps trying to flash back to Oreo.
Unless I am mistaken (it does happen) I was under the impression flashing the 8.1 factory image was all that's needed to return to stock Oreo.
List your steps/process (and files used) and let's see if someone can't help you out.

Initially, I unlocked my bootloader and data was wiped, then I installed android 8.1 (the recommended version from resuruction remix rom forum) and extracted the files into the directory of adb, then I ran "flash-all" and it was running, then at the end it showed a fail error and now my device is not booting up, I can only access fastboot mode

abdane said:
Hello, I tried downgrading today to oreo (from official version of pie) because I wanted to root and flash resuruction remix rom. I unlocked my bootloader and then I installed android oreo from the website for pixel 2 xl, copied the files into the adb directory and ran the "flash-all" batch file. But now my device is stuck at the google screen with the unlcoked lock image, before this screen it says that my device is corrupt. How can I solve this issue and go back to oreo?
Thanks
Click to expand...
Click to collapse
Could be your Android PlatformTools are out of date?

abdane said:
Initially, I unlocked my bootloader and data was wiped, then I installed android 8.1 (the recommended version from resuruction remix rom forum) and extracted the files into the directory of adb, then I ran "flash-all" and it was running, then at the end it showed a fail error and now my device is not booting up, I can only access fastboot mode
Click to expand...
Click to collapse
If I am reading your steps right...
My suggestion is flash vanilla Oreo.
I wouldnt be surprised of there is some parition structure change that the Modded ROM is screwing up.
get back to vanilla
Mod after being stabel

parakleet said:
If I am reading your steps right...
My suggestion is flash vanilla Oreo.
I wouldnt be surprised of there is some parition structure change that the Modded ROM is screwing up.
get back to vanilla
Mod after being stabel
Click to expand...
Click to collapse
Im sorry, what do you mean by vanilla oreo? You mean the very first oreo ROM?

parakleet said:
If I am reading your steps right...
My suggestion is flash vanilla Oreo.
I wouldnt be surprised of there is some parition structure change that the Modded ROM is screwing up.
get back to vanilla
Mod after being stabel
Click to expand...
Click to collapse
abdane said:
Im sorry, what do you mean by vanilla oreo? You mean the very first oreo ROM?
Click to expand...
Click to collapse
I think the suggestion is that you flash the stock factory 8.1 image found on the Google site (the link to it is in my 9x and 8x links in my sig).
I agree with this.
Fastboot the factory 8.1 image using the flash-all, leave the -w in so you wipe any fragments, and you should have a brand new, fresh start.

Az Biker said:
I think the suggestion is that you flash the stock factory 8.1 image found on the Google site (the link to it is in my 9x and 8x links in my sig).
I agree with this.
Fastboot the factory 8.1 image using the flash-all, leave the -w in so you wipe any fragments, and you should have a brand new, fresh start.
Click to expand...
Click to collapse
I think I confused you guys, sorry, what i did is that I flashed the STOCK version of 8.1 Oreo, I wanted to downgrade from pie. I installed the official one from google and ran the "flash-all" command and failed at vendor_b

michaelbsheldon said:
Could be your Android PlatformTools are out of date?
Click to expand...
Click to collapse
I just uninstalled it, installed the latest version and still not working :/

I am trying to fastboot the files separately: bootloader, boot, radio, system and vendor images. They all pass except for the vendor image, it always fails there (Data write failure unknown error). Any help?

abdane said:
I just uninstalled it, installed the latest version and still not working :/
Click to expand...
Click to collapse
If you are for sure unlocked and critical unlocked, next step is to unzip everything in the Google factory image (about 25 files), then
use this with instructions listed: https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
It's fixed things for me several times when I just could not get results with flash-all.bat.

Alright, wow finally I got it to work. THe issue was either the cable or the port, I was using the originisl type-c to type c cable, tried my old LG G5 typeA to type c and worked fine, wow. Thanks for the help everyone!!! Phone is back and alive

abdane said:
Alright, wow finally I got it to work. THe issue was either the cable or the port, I was using the originisl type-c to type c cable, tried my old LG G5 typeA to type c and worked fine, wow. Thanks for the help everyone!!! Phone is back and alive
Click to expand...
Click to collapse
I thought you already read over my 8x or 9x guides, or I would've mentioned that in the first place
8x Guide:
-have a 2.0 USB in case your 3.0 USB doesn't work properly
-Reboot PC, change between 2.0 and 3.0 cables, and change USB ports if having trouble using fastboot
9x Guide:
*Unlocked bootloader and Critical_unlock completed.
*Latest SDK Tools found here
*USB 2.0 & 3.0 cables available (trust me)

hi dude, I have the same problem with you , have you solved yet?
after flash the factory image android o , it shows device corrupt..

Az Biker said:
I thought you already read over my 8x or 9x guides, or I would've mentioned that in the first place
8x Guide:
-have a 2.0 USB in case your 3.0 USB doesn't work properly
-Reboot PC, change between 2.0 and 3.0 cables, and change USB ports if having trouble using fastboot
9x Guide:
*Unlocked bootloader and Critical_unlock completed.
*Latest SDK Tools found here
*USB 2.0 & 3.0 cables available (trust me)
Click to expand...
Click to collapse
This exact info should be a sticky on every single thread!!

CyberpodS2 said:
This exact info should be a sticky on every single thread!!
Click to expand...
Click to collapse
I just created a "troubleshooting thread" for this situation in the 2 XL guides section
Link in my sig.
Should be much easier to point people to these steps before we spend two pages trying to help out just to find out it was a USB cable, or old SDK tools

Ble_Ale said:
hi dude, I have the same problem with you , have you solved yet?
after flash the factory image android o , it shows device corrupt..
Click to expand...
Click to collapse
I've had this happened a couple of times no Rhyme or Reason the only way out of it is to flash The Flash all with the -w. I believe it has something to do with Googles security.
Edit. I take that back I've switched to the other slot before and restored a backup and gotten out of it if that other slot isn't corrupt

I thought Android Pie has a mandatory "Anti Roll back" feature that prevents going back to Android Oreo?
That is not true then?!

samteeee said:
I thought Android Pie has a mandatory "Anti Roll back" feature that prevents going back to Android Oreo?
That is not true then?!
Click to expand...
Click to collapse
unless you do fastboot flashing unlock and fastboot flashing unlock_critical it is not possible to roll back.
if you do both above you can over-write the critical partitions allowing the roll-back.
the general population would not be doing these, so in essence they do block rolling back to earlier versions, but in a disaster situation it can be done.

uicnren said:
unless you do fastboot flashing unlock and fastboot flashing unlock_critical it is not possible to roll back.
if you do both above you can over-write the critical partitions allowing the roll-back.
the general population would not be doing these, so in essence they do block rolling back to earlier versions, but in a disaster situation it can be done.
Click to expand...
Click to collapse
Got it. Thanks for the explanation.

[ROM] ZTE Axon M Stock Firmware/Firehose

EDL Stock Firmware
Nougat AT&T Z999 B30
Nougat AT&T Z999 B37
Oreo China Z999 2.1
Oreo NTT DoCoMo Z-01K B32
SD Stock Firmware
Nougat Russia Z999 1.1
Oreo China Z999 1.11
Nougat China Z999 1.11 Fallback Pack
Oreo China Z999 2.10
Firehose files
AT&T Z999 Firehose (Extract with 7zip) Might work with the China Z999 but unknown
NTT DoCoMo Z-01K Firehose (Extract with 7zip)
TIM Z999 Firehose (Extract with 7zip)
Incomplete pre-production firmware (Do not use)
P996A26V1.0.0B07
P996A25V1.0.0B20
Here is a step by step guide on how to flash the stock rom with QFIL and by extension any image.
Download and install the Qualcomm drivers from here
Download the firmware and firehose from above
Extract the firmware to a folder that you can easily access them from like your desktop
Download and install QPST from here
Open the QFIL application (Find it in your start menu)
In the "Select Build Type" field select Flat Build
In the "Select Programmer" field navigate to the folder you extracted the firmware and support files to and select the prog_ufs_firehose_8996_ddr.elf file
Select the "Load XML" button and navigate to the folder you extracted the firmware and support files to and select the rawprogram0.xml and then the patch0.xml when prompted.
Plug in your phone
Run the following adb command "adb reboot edl" (Now the screen should be blank but the led light should be red)
If the text at the top of the QFIL application says "No Port Available" click the "Select Port..." option and pick your device. If your device isn't showing up there you didn't install the drivers properly.
Click the Download Button to begin flashing your device

Mine just in case

Thank u!! Just finding where I can update my att version firmware. I am still on b22. No OTA available. So sad...
Thx for sharing!!

my phone has been unlocked. will it be locked again after flashing??
your advice appreciated......

alhtc said:
my phone has been unlocked. will it be locked again after flashing??
your advice appreciated......
Click to expand...
Click to collapse
I am assuming you mean sim unlocked, if so I haven't ever seen it be relocked by flashing the device back to stock. But I can't be 100% for this device.

i followed up to no.9 Plug in your phone
but nothing happened...
shall i boot in bootloader mode?
i boot to recovery but after choosing bootloader mode, the phone just reboot and go into android...
---------- Post added at 02:03 PM ---------- Previous post was at 01:43 PM ----------
i also tried factory test mode. and the phone can be identified in QFIL
when i run adb command "adb reboot edl",
it shows:
* daemon not running. starting it now *
CreateProcess failure, error 2
* failed to start daemon *
error: cannot connect to daemon

Thank you!!
Thank you so much for your huge contribution!!
This opens a door to many possibilities!
Once again, thank you!

alhtc said:
i followed up to no.9 Plug in your phone
but nothing happened...
shall i boot in bootloader mode?
i boot to recovery but after choosing bootloader mode, the phone just reboot and go into android...
---------- Post added at 02:03 PM ---------- Previous post was at 01:43 PM ----------
i also tried factory test mode. and the phone can be identified in QFIL
when i run adb command "adb reboot edl",
it shows:
* daemon not running. starting it now *
CreateProcess failure, error 2
* failed to start daemon *
error: cannot connect to daemon
Click to expand...
Click to collapse
Plugging in your phone isn't meant to do anything itself you need a working adb install so you can then do adb reboot edl to get into the proper mode. Ftm is not the proper mode.

deadman96385 said:
Plugging in your phone isn't meant to do anything itself you need a working adb install so you can then do adb reboot edl to get into the proper mode. Ftm is not the proper mode.
Click to expand...
Click to collapse
thank u for the reply!
can you give more hint on how to do a working adb install??
i have tried some methods but seems doesn't work...
i also tried to enter EDL by pressing vol + & - and power button. and try download the firmware but failed too.

have been trying different version of adb driver...
usb debugging unlocked.
different type C cable.
different PC.
but still having the following results:
* daemon not running. starting it now *
CreateProcess failure, error 2
* failed to start daemon *
error: cannot connect to daemon
really want to update the Axon M to make it usable again. it's laggy and poor camera in this early firmware.

Can I ask a stupid question?
Can I install firmware update by SD card? I see the option but I don't have the resources....

can flash china rom to japan phone ??, last time i can flash att rom to china phone but signal bad and lost 1 sim

Alright so I'm not sure what I'm doing wrong. I keep getting various errors such as; Expecting SAHARA_END_TRANSFER but found: 0, didn't revive hello packet, or rx_data:247 Error occurred while reading from COM port. The error is just different based on what application. I've tried QFIL, the ZPST in your MEGA folder, MiFlash, and a modified version of the Axon 7 EDL tool. All give errors, unless I use my Axon 7 witch I am able to fully control in EDL mode. I think the basic problem is my Axon M can't be accessed, and I'm not sure what I'm doing wrong there. Any advice?

AT&T AXON M update issue
Hello Deadman 96385 thank you for your guidance . I have been looking for info to update my axon m (att version) and i downloaded all files and drivers that you provided. The first issue is one of the drivers which is this ZTE_V889F_V880G_V955_A2_Drivers . I extracted zip file and installed other drivers but i couldn't install this driver ZTE_V889F_V880G_V955_A2_Drivers . I believe i'm doing something wrong or i miss something. One another issue is after step 8 . Should i go into FTM mode to start process ? Adb gives an error such as deamon not started or running etc.. For sure we missed something . Can you explain this part a bit detailed if you have some time ? I will be appreciated if you can guide us in this part.
Thank you
Have a nice day

Thanks for the huge contribution. Is it possible to flash Chinese ROM on the AT&T phone. thanks

Please somebody help me to beat that " sahara fail " . Trying to update ZTE axon m (at&t z999). I installed all necessary drivers and files. QPST as well and still getting sahara error. Sahara failed , sahara failed , sahara failed . My phone is going to explode soon. Booted phone maybe 100 times to edl mode . everything is fine but that sahara ruins everything. I cannot update the phone. Windows 10 64 bit installed all drivers provided by developers but cannot flash rom. I have done research but there was no specific info regarding that getting" sahara fail error ". I just do not understand where did i go wrong ? if there is anyone who can help with this ???
Thank you

wta
which firmware should i download ?
the sd ones ? or the edl ones ?
just to be sure, if u have the time pls read my explanation, and pls tell me if I'm doing right or wrong (while I'm downloading the firmware files about 2 hours)
I just got at&t zte axon m (I live in indonesia)
it's unlocked (I could use my simcard to phone, and edge is working)
but I want to use 4G and tethering (which not working atm), and at&t messages backup & sync often nags me to put at&t number when I'm doing anything like changing the setting, etc.
so I think I want to upgrade the phone to oreo with chinese (would this remove that annoying at&t messages backup & sync) and hopefully makes my 4G and tethering working (if not then as long as my call working like now then it's ok too) and hopefully the battery would be better (read that oreo battery management is far better than nougat).
I would prefer to use cn 2.2 firmware as it has got the google play back (from what I read cn 2.1 remove the google play ?), but can't find it anywhere, and ur guide here seems to be the most detailed one. so I think I would gamble with cn 2.1 firmware (that maybe would let me update from setting to cn 2.2 ?)
what do u think ? would this work ?
if not pls warn me right away
thx in advance
oh and 1 more think. which firehose file should I use ? for now I downloaded the at&t one. or should I use the other ?
edited again :
found my answer.
so there was someone already trying and break his zte axon m. phew, I almost got to the last step, and was just trying to find how to boot into edl mode and found this :
https://forum.xda-developers.com/axon-m/help/bricked-edl-mode-t3844487

Hello myfire888 , according to my knowledge you cannot flash custom roms or custom recoveries to AT&T devices unless you unlock their bootloaders. I have an AT&T AXON M as well . I got it a month ago and it is 4G/LTE support. Phone is good but as i said we cannot flash custom roms on AT&T devices or unlock bootloaders. I've done a research and there is no way to unlock bootloaders of at&t devices(thsi is what i know so far, maybe there are some people who can do it but not me ). I have a galaxy S7 EDGE AT&T and it is the same like axon m. You need updates from AT&T only . Recently i found AT&T 's updates from xda but i was unable to flash the rom. I installed every drivers and other files and got a sahara error failed many times. I will not buy AT&T devices anymore. They work good but we cannot flash custom roms or recovery . We are lucky that some developers upload these updates on XDA otherwise it is really hard to find them. AT&T does not provide their update on their website. That sucks.
Good luck friend

galaxys2ci said:
Hello myfire888 , according to my knowledge you cannot flash custom roms or custom recoveries to AT&T devices unless you unlock their bootloaders. I have an AT&T AXON M as well . I got it a month ago and it is 4G/LTE support. Phone is good but as i said we cannot flash custom roms on AT&T devices or unlock bootloaders. I've done a research and there is no way to unlock bootloaders of at&t devices(thsi is what i know so far, maybe there are some people who can do it but not me ). I have a galaxy S7 EDGE AT&T and it is the same like axon m. You need updates from AT&T only . Recently i found AT&T 's updates from xda but i was unable to flash the rom. I installed every drivers and other files and got a sahara error failed many times. I will not buy AT&T devices anymore. They work good but we cannot flash custom roms or recovery . We are lucky that some developers upload these updates on XDA otherwise it is really hard to find them. AT&T does not provide their update on their website. That sucks.
Good luck friend
Click to expand...
Click to collapse
phew luckily I havent proceed through the flash yet, or I'll have another brick in my house.
u live in us ? use at&t ? because mine should support 4G/LTE too but only 2G run, and no tethering (well tethering would be useless too even if it can with only 2G)
can't find any chinese axon m on ebay too, so i just bought the at&t unlocked one.
this phone is near perfect, and I'd like to say "who needs huawei mate x and samsung galaxy fold when u have zte axon m" haha
oh well, I have use plan B and using mifi for now. it just not feels good to bring another extra modem.

i'm not living in us but i got the phone from somebody who brought this phone from us . it's sim unlocked not bootloader thats why we cannot flash custom roms. I have the update but i cannot flash it . ZTE is complicated phone to update . i have a samsung at&t and i update without an issue . samsung is easy to update. Before you update your phone do a research regarding your phone's model. Your phone should support 4G / LTE . Did you check network settings ? Mobile networks or network settings . it should say 2G/3G/4G etc.. check it. I cannot find any tutorial or solution to flash update on axon m unfortunately. I downloaded every single drivers but still can't flash it .

all about official firmware and where to find it

This wil be a list of firmware sources and a bit of explanation in different firmware versions and builds. This information has been gathered over the past few weeks, mainly by helping others to find the proper stock roms.
First of all, there seem to be multiple regions that have different firmware’s, and there seem to be different software channels per region or per region per provider. ( for instance vfeu vs reteu )
The phone model is XT2041-X where the X can stand for 1 to 4
The development name / moto name is called: Sofiar ( XT2041-1/3)
the development name for the US name is: Sofia ( xt2041-4 )
The easiest way to find the proper firmware would be via the Lenovo rescue and smart assistant ( LMSA)
you can download it from here: https://download.lenovo.com/consumer/mobiles/rescue_and_smart_v5.0.0.25_setup.exe
Since a few days support has been added to rescue the g8 power
you can download the current firmware for your device via the rescue page.
Manual selection of firmware sources:
So far, every source on the internet points to the lolinet mirror
see https://mirrors.lolinet.com/firmware/moto/sofiar/official/
US version: https://mirrors.lolinet.com/firmware/moto/sofia/official/
a 2nd source would be the moto updates tracker, but I expect that everything you find here Will appear on lolinet
US: https://t.me/s/MotoUpdatesTracker?q=#sofia
The rest of the world: https://t.me/s/MotoUpdatesTracker?q=#sofiar
so far I have not been able to find any other sources. I hope this helps a bit in downloading / finding the stock firmware for your phone.
If you find any other / better source, please let me know, I'll add it to this first post.

Thanks
I successfully updated mine and regained root.
I will post manual update guide later.
A side note: the following must be flashed in fastbootd (fastboot reboot fastbootd or adb reboot fastboot)
boot.img, recovery.img, vbmeta.img, super, dtbo.img

@mingkee Pls can you share manual update guide? THX

endva3 said:
@mingkee Pls can you share manual update guide? THX
Click to expand...
Click to collapse
There's a simple method using LMSA rescue method, but make sure you backup your phone because your phone will be wiped during the process.

Hi, I'm running into a little problem. I used the lolinet link to download the factory ROM for my Moto G Power (Best Buy unlocked, on Verizon). I downloaded the sofia VZW factory ROM first (thinking because I'm on Verizon). I used Magisk to patch the boot.img and fastbooted it. After reboot, I lost the touch screen and cell service -- could not unlock the phone. So I thought no big deal, I'll just reflash the unpatched boot.img from the sofia retus ROM this time. However, I still do not have touch screen. Does anyone have the factory boot.img for QPM30.80.50-1 that originally came with this G Power? Thanks in advance.

quangtran1 said:
Hi, I'm running into a little problem. I used the lolinet link to download the factory ROM for my Moto G Power (Best Buy unlocked, on Verizon). I downloaded the sofia VZW factory ROM first (thinking because I'm on Verizon). I used Magisk to patch the boot.img and fastbooted it. After reboot, I lost the touch screen and cell service -- could not unlock the phone. So I thought no big deal, I'll just reflash the unpatched boot.img from the sofia retus ROM this time. However, I still do not have touch screen. Does anyone have the factory boot.img for QPM30.80.50-1 that originally came with this G Power? Thanks in advance.
Click to expand...
Click to collapse
You may have patched unmatched build number.
Solution: flash full ROM
LMSA rescue is the simplest method but it will wipe the phone

Thanks! That was what I ended up doing.

Is it possible to change fw xt2041-3 (PAHF0004PL) to XT2041-3 (PAHF0006GB)? I'm on the PL version (andoid security January 2020) and the GB version is May 2020. If possible, the bootloader must be unlocked? Can it be changed via any tool (mototool) or via adb commands?

Anyone have the boot.img for QPMS30.80-51-3?
I cant download the latest May update from their server. Some reason the link to download expired a few days after. So if anyone has another link or can just hook it up with the boot.img please
I couldnt get it with the rescue app either it was a lower version.
EDIT
Found it here
https://forum.xda-developers.com/showpost.php?p=82865201&postcount=73

Some lessons learned
pjottrr said:
The easiest way to find the proper firmware would be via the Lenovo rescue and smart assistant ( LMSA)
you can download it from here: https://download.lenovo.com/consumer/mobiles/rescue_and_smart_v5.0.0.25_setup.exe
Since a few days support has been added to rescue the g8 power
you can download the current firmware for your device via the rescue page.
Click to expand...
Click to collapse
In my case, you in fact cannot exactly download the "current" firmware via the rescue page - the phone's updater app thinks QPM30.80-51-3 is the latest version, but the rescue app installs the newer QPM30.80-109. Both are 5/1/2020 security patch level, but the boot.img files are most certainly not interchangeable.
I ended up in a bootloop which I had to rescue the phone to escape. I'd advise anyone wanting to root this phone to just rescue it first.
Also it's essential that you install the Motorola Device Manager/USB drivers in addition to LRSA, otherwise LRSA will incorrectly insist your phone is not in fastboot flash mode if you have to resort to rescuing from fastboot mode.
Finally, the rescue process will not work from a Windows VM under KVM, whether you have the USB device redirected or shared with the host. You need Windows running on bare metal.
Hope this saves someone the hours of annoyance I just went through trying to unbrick the damn thing.

Can jump from a carrier Rom to a unlocked version? And if yes, what's the unlocked phone rom? Cause I only see carrier versions.

Mikael1013 said:
Can jump from a carrier Rom to a unlocked version? And if yes, what's the unlocked phone rom? Cause I only see carrier versions.
Click to expand...
Click to collapse
Switching from a carrier rom to an unlocked version won't SIM unlock a phone (at least not to my knowledge), if that's your objective. But if you're looking to switch the retail flavor rom, try RETUS, specifically XT2041-4_SOFIA_RETUS_10_QPM30.80-13-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip.

rlrevell said:
In my case, you in fact cannot exactly download the "current" firmware via the rescue page - the phone's updater app thinks QPM30.80-51-3 is the latest version, but the rescue app installs the newer QPM30.80-109. Both are 5/1/2020 security patch level, but the boot.img files are most certainly not interchangeable.
I ended up in a bootloop which I had to rescue the phone to escape. I'd advise anyone wanting to root this phone to just rescue it first.
Also it's essential that you install the Motorola Device Manager/USB drivers in addition to LRSA, otherwise LRSA will incorrectly insist your phone is not in fastboot flash mode if you have to resort to rescuing from fastboot mode.
Finally, the rescue process will not work from a Windows VM under KVM, whether you have the USB device redirected or shared with the host. You need Windows running on bare metal.
Hope this saves someone the hours of annoyance I just went through trying to unbrick the damn thing.
Click to expand...
Click to collapse
Also a good word of advice before flashing a boot.bin
run the command
fastboot boot boot.bin
or whatever your boot.bin is called
Then you can test your patched file before patching it. Also even better once you get into Android you can open MAGISK and use direct install

TNS201 said:
Also a good word of advice before flashing a boot.bin
run the command
fastboot boot boot.bin
or whatever your boot.bin is called
Then you can test your patched file before patching it. Also even better once you get into Android you can open MAGISK and use direct install
Click to expand...
Click to collapse
I've never actually had this work on any device I've tried to root. Command not implemented or some such error was always the result. Does it work for you on this device?

The download link for the latest Google Fi firmware works again if anyone wants to grab it before it expires...again heh.
SOFIA_RETAIL_QPMS30.80-51-3

CodyF86 said:
The download link for the latest Google Fi firmware works again if anyone wants to grab it before it expires...again heh.
SOFIA_RETAIL_QPMS30.80-51-3
Click to expand...
Click to collapse
Do you have stock boot IMG by any chance? Thx in advance

freddienuxx said:
Do you have stock boot IMG by any chance? Thx in advance
Click to expand...
Click to collapse
sofia_80-51-3boot.img

CodyF86 said:
sofia_80-51-3boot.img
Click to expand...
Click to collapse
Thx man

rlrevell said:
I've never actually had this work on any device I've tried to root. Command not implemented or some such error was always the result. Does it work for you on this device?
Click to expand...
Click to collapse
yea when you are in bootloader with phone attached to the PC it should work
It worked on my pixel 2 xl and this phone

Does anybody have this file available? (Sorry for the spaces, I can't post a link...). The download link has expired.
t.me /motoupdatestracker/ 2752
filename: SOFIA_RETAIL_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
What's the difference between that and RETUS on lolinet? Is there any? Reason I'm asking is that I don't have any radios after that OTA (Google Fi) and flashing the boot.img from RETUS QPMS-30.80-51-5.

Sony Xperia XA1 - Bootloop after twrp misuse

Hello, i'm writing this post because i'm a noob on mobiles and i need some assistence in this scenario.
I have a xa1 that was stopped at home because it had terrible calibration problems. This year i remembered to root and flash this mobile, maybe it was the build that was having some compatibility issues.
For now i have successfully unlocked the bootloader but when doing an instructon installing the twrp program on the device, i may have done something wrong.
From what i understand, twrp is a backup/recovery user gui to make some actions easier.
i think i ****ed up and now the phone is on bootloop and i cant even go into recovery mode.
i did not move the twrp.img to the folder i was working on and still pressed enter on the "fastboot boot twrp.img" step.
I understand that i may have told the phone "hey use this img that doesnt exist" and now its standarized to launch from that img i told him? is that it?
I have adb and fastboot installed. I had them both recognizing the device, no problem until i did that step earlier, and now adb doesnt recognize the device anymore. I thought i could maybe get the standart boot.img(if that even exists) from some forum but this is getting waaay hairier that i thought.

Don't worry, it normal that the phone has bootloop after unlocked. You should flash stock rom again via Flashtool, for the firmware you could still download it from xperiafirm I guess, after reflash the stock rom your device will work just fine and you could download my twrp here which I build for XA1 Plus but a friend of mine have it working on XA1 Ultra just fine, if you need any more help on TWRP just DM me or ask in my thread

Hari Nguyen said:
Don't worry, it normal that the phone has bootloop after unlocked. You should flash stock rom again via Flashtool, for the firmware you could still download it from xperiafirm I guess, after reflash the stock rom your device will work just fine and you could download my twrp here which I build for XA1 Plus but a friend of mine have it working on XA1 Ultra just fine, if you need any more help on TWRP just DM me or ask in my thread
Click to expand...
Click to collapse
which firmware do i select and download? i bought the phone via amazon, from the uk, should i use the firmware of the language i want or the original from the fabric? does that even make a difference? im sorry, im a noob at android systems xD

Learn it at Xperia Firm thread, my country might vary from your (like network operator or what not) for that you need to do your own research to know which one to download, in my country all I need it go and download firmware that made for vietnam and done, it already come with multiple languages