Develop Bugs

How To Get Working Apn + Hotspot After Upgrade to NCQ26.69-64+ or With SPerry XT1766.

You Need From firmware.center / firmware / Motorola / Moto%20E4 / Stock / XT1766 /
SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Which Is Not For The XT1766 if You Flash This You Will Loose The Baseband And SoftBrick The Phone .
And From firmware.center / firmware / Motorola / Moto%20E4 / Stock / XT1766 /
XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip This One Have The Ratio And Modem And FsG images Of Your Phone Thats Why We Need It .
Lets Begin , if You Have This Phone You Had Noticed That After Upgrade To The Last Version The Ability To Add Apn And Modify Them And The Hotspot Wont Work Any More This Is Because The Locked Everything Up For No Reason Well Money Is the Reason , We need to Extract XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip in a folder and SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
in other folder , you must know your way to flash servicefile.xml on linux or windows no details here and bootloader unlocked , well that is easy , now we have to put the files : the 2 OEM files , the 4 System Files , boot.img ,
{{{ bootloader "NO NEED" This Work Before Just Because v48 and v56 have the same bootloader version }}} , recovey.img from SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip inside the folder that have the XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip firmware and replace those files , optional for rooting you can replace recovery.img with the Squid2 TWRP recovery.img file and The boot.img Patched Fixed F2FS kernel which is based in the stock firmware kernel sources that we are going to flash here and then flash supersu inside twrp , Well Thats It after Flashing This Downgrade Custom stock you will have back the ability to ADD apn's Again And Use The Hotspot included in the Stock Firmware , Cheers , Thanks To All The People Involved in the development for Perry Moto E4 Thanks Everybody i hope this help somebody with the XT1766. :laugh:
EDIT HELLO
Things Have Changed Dont Try To Downgrade Bootloader or The Phone Will Get Hard Bricked , Why well bootloader versions on new firmwares have been upgraded please check all the information on the Bootloader/Fastboot
MODE Of The Phone Which Version You Have , Now For Example If You Are On Version NCQS26.69-64-5 you will need SPERRY_SPRINT_NCQS26.69-64-5_cid50_XT1766-SS_7.1.1_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml full package then extract and now you will need SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml extract it too , Now Just Move The 2 Oems Images And 4 System Images And Boot Image To SPERRY_SPRINT_NCQS26.69-64-5_cid50_XT1766-SS_7.1.1_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml Folder Next Look for RSD_Lite_Motorola_XML_To_Batch_Script on Google Download it And Watch The Video Of Rootjunky on how to use it. Very Simple Wish All Of You Luck And im Not Responsible Of Any Damage Of Your Phone Use This Guide On Your Own Terms.

ozmage said:
You Need From firmware.center / firmware / Motorola / Moto%20E4 / Stock / XT1766 /
SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Which Is Not For The XT1766 if You Flash This You Will Loose The Baseband And SoftBrick The Phone .
And From firmware.center / firmware / Motorola / Moto%20E4 / Stock / XT1766 /
XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip This One Have The Ratio And Modem And FsG images Of Your Phone Thats Why We Need It .
Lets Begin , if You Have This Phone You Had Noticed That After Upgrade To The Last Version The Ability To Add Apn And Modify Them And The Hotspot Wont Work Any More This Is Because The Locked Everything Up For No Reason Well Money Is the Reason , We need to Extract XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip in a folder and SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
in other folder , you must know your way to flash servicefile.xml on linux or windows no details here and bootloader unlocked , well that is easy , now we have to put the files : the 2 OEM files , the 4 System Files , boot.img , bootloader , recovey.img from SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip inside the folder that have the XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip firmware and replace those files , optional for rooting you can replace recovery.img with the Squid2 TWRP recovery.img file and The boot.img Patched Fixed F2FS kernel which is based in the stock firmware kernel sources that we are going to flash here and then flash supersu inside twrp , Well Thats It after Flashing This Downgrade Custom stock you will have back the ability to ADD apn's Again And Use The Hotspot included in the Stock Firmware , Cheers , Thanks To All The People Involved in the development for Perry Moto E4 Thanks Everybody i hope this help somebody with the XT1766. :laugh:
Click to expand...
Click to collapse
I flashed the Sprint firmware and had data working on my XT1766 after it got it's carrier update, the Sprint firmware does not soft brick the phone as I flashed it and can confirm it doesn't soft brick it, so you are incorrect in saying that.

I'm not sure if I did something wrong but after trying this, my phone kept saying, "phone stopped working". I had backed up my phone so I restored it. Any ideas on what might have happened?

dlinderaz said:
I'm not sure if I did something wrong but after trying this, my phone kept saying, "phone stopped working". I had backed up my phone so I restored it. Any ideas on what might have happened?
Click to expand...
Click to collapse
Yeah, don't try to restore system apps. Phone app has some quirks, it's in oem. There are oem hide xml files and so on. Why try to restore phone?

madbat99 said:
Yeah, don't try to restore system apps. Phone app has some quirks, it's in oem. There are oem hide xml files and so on. Why try to restore phone?
Click to expand...
Click to collapse
I restored the entire thing after flashed the indicated files causing the error message.

dlinderaz said:
I restored the entire thing after flashed the indicated files causing the error message.
Click to expand...
Click to collapse
Oh, I never tried this method. I used rsd lite to flash the firmware (the one op says will brick you, it didn't by the way). After flashing new firmware I restored only data, nothing system or boot related, and have had no issues.

madbat99 said:
Oh, I never tried this method. I used rsd lite to flash the firmware (the one op says will brick you, it didn't by the way). After flashing new firmware I restored only data, nothing system or boot related, and have had no issues.
Click to expand...
Click to collapse
Thank you so much for the info. I'll give that a try tomorrow. I appreciate your time and help.

dlinderaz said:
Thank you so much for the info. I'll give that a try tomorrow. I appreciate your time and help.
Click to expand...
Click to collapse
Keep in mind I have the virgin mobile version (sprint xt1766). Don't know which one you have. Some have had trouble with rsdlite on Windows 10, it worked fine for me though.
I used rsdlite from here
The newest one, 6.2.4 I think

Apn Xt1766
I just want to add apn and want to use hot spot again
As the phone is updated on latest build ..
I don't want the root access..
What's should I try then from previous build , can anyone
Guide me easy steps plz.

Xt1766 how to get working apn
Will anyone confirm

danishamini.saifi said:
Will anyone confirm
Click to expand...
Click to collapse
The steps are there. Just don't use the root part if you don't want root. Once you switch the files, flash the service file.xml with rsdlite.

madbat99 said:
The steps are there. Just don't use the root part if you don't want root. Once you switch the files, flash the service file.xml with rsdlite.
Click to expand...
Click to collapse
Thanks, ill try and share the result.

I've tested it.. It worked for me but there is an issue
With this method occurred as well..
While Turing on the phone " BAD KEY" msg pops up on
Black display for 4-5 seconds and then mobile shows Motorola logo...
Now what is suppose to be done to get rid off BAD KEY msg.

danishamini.saifi said:
I've tested it.. It worked for me but there is an issue
With this method occurred as well..
While Turing on the phone " BAD KEY" msg pops up on
Black display for 4-5 seconds and then mobile shows Motorola logo...
Now what is suppose to be done to get rid off BAD KEY msg.
Click to expand...
Click to collapse
That's normal if you unlock the bootloader. Flash the no verity opt encrypt, or magisk, and it will change from bad key to n/a. But there will always be a message if you unlock the bootloader.
I know you said you don't need root, so that bad key message is there to stay.

madbat99 said:
That's normal if you unlock the bootloader. Flash the no verity opt encrypt, or magisk, and it will change from bad key to n/a. But there will always be a message if you unlock the bootloader.
I know you said you don't need root, so that bad key message is there to stay.
Click to expand...
Click to collapse
oh... i got it, thanks...
just one thing more please, if i go towards rooting the phone as well, will this be removed or N/A or something will be there?

danishamini.saifi said:
oh... i got it, thanks...
just one thing more please, if i go towards rooting the phone as well, will this be removed or N/A or something will be there?
Click to expand...
Click to collapse
N/A will be there. But you can flash a new boot logo to kinda hide it. Instead of a black screen, any logo you want, maybe with a white strip at the top to hide it. I'll get you a link.
Here are some good ones. https://forum.xda-developers.com/mo...om-boot-logos-converted-t3759320/post75787882
And here is the guide to make your own
https://forum.xda-developers.com/moto-e4/how-to/replace-n-boot-image-t3687212/post74118155

@madbat99
Everything you shared was perfect I made my own logo to hide bad key apn working ..
Now I want to have thebroot access in my phone XT1766..
TWRP IS ALREADY ISTALLED ON THE PHONE AS I AM FLASHING LOGOS..
WHAT SHOULD I INSTALLED TO GET ROOT ACCESS ..
SUPER USER ETC.. PLZ SHARE WITH ME..
and the main reason to have the root access is, I want to block or disable OTA update ..
Plz confirm, how will it be possible ..as I downgraded to get working APN But phone updated again now.
I want the phone to be stopped from being updated..
Plz help me out fixing this..
Thanks

danishamini.saifi said:
@madbat99
Everything you shared was perfect I made my own logo to hide bad key apn working ..
Now I want to have thebroot access in my phone XT1766..
TWRP IS ALREADY ISTALLED ON THE PHONE AS I AM FLASHING LOGOS..
WHAT SHOULD I INSTALLED TO GET ROOT ACCESS ..
SUPER USER ETC.. PLZ SHARE WITH ME..
and the main reason to have the root access is, I want to block or disable OTA update ..
Plz confirm, how will it be possible ..as I downgraded to get working APN But phone updated again now.
I want the phone to be stopped from being updated..
Plz help me out fixing this..
Thanks
Click to expand...
Click to collapse
Just don't accept the update. You can root by flashing magisk. You will still receive update notification. You'll need to disable the moto update app. I forget which one exactly. But your phone shouldn't be able to do ota updates once you are rooted with twrp installed. The update will fail.
here is the root thread.

madbat99 said:
Just don't accept the update. You can root by flashing magisk. You will still receive update notification. You'll need to disable the moto update app. I forget which one exactly. But your phone shouldn't be able to do ota updates once you are rooted with twrp installed. The update will fail.
here is the root thread.
Click to expand...
Click to collapse
Thank you. I wish I had known this. I had to flash the stock recovery, etc for the updates to work. A little bit of an unnecessary hastle.

dlinderaz said:
Thank you. I wish I had known this. I had to flash the stock recovery, etc for the updates to work. A little bit of an unnecessary hastle.
Click to expand...
Click to collapse
Ota updates will likely always fail if you have twrp, or have modified the system in any way. The ota performs many checks (assert props) to see if the system is clean. If any asserts fail, the ota will fail. Even restoring the stock recovery doesn't guarantee the ota will work.

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).

0 IMEI after Pie on XT-1789-03 Sprint

I have lost IMEI number after flashing Pie. On my Sprint Moto Z2 Force. Signal bar has turned grey and IMEI is showing as zero.
Wifi is working
Bluetooth is working
Barcodes in bootloader mode is showing some different IMEI no.
Downgrade to Stock Oreo or Naugat
If I downgrade to stock Oreo then I lost all wifi, sim and Bluetooth. Also no baseband found in bootloader.
Will appreciate if someone can help.
Thanks in advance.

If you have already flashed Pie Rom (including bl、 baseband), you will not be able to return to Oreo

Hello.
I am trying to research the imei bricks on Sprint models after Verizon pie update. In short, everything we understand says this should not be happening, and yet it is.
Can you, for research purposes, describe the state of your device when you applied the update? Was it running full verizon firmware down to the bl, modem, and gpt? I may have an experimental fix but I need to gather more info about the bricks.
Also, it is impetative that you don't flash any further modems for my fix to have a good chance to work. Thanks.

Thanks for the message,
The device working fine, very super smooth and I can feel the difference.
The only think which is not working is cell phone and it's because of 0 IMEI number, currently I am on pie retail version (NASH_RETAIL_9.0_PPX29.159-19_subsidy-default_regulatary-DEFAULT_CFC.xml) downloaded from mirrors lolinet com / firmware / Moto / Nash / retail
Pls let me know if you want more info.
Thanks in advance.

hqureshi said:
Thanks for the message,
The device working fine, very super smooth and I can feel the difference.
The only think which is not working is cell phone and it's because of 0 IMEI number, currently I am on pie retail version (NASH_RETAIL_9.0_PPX29.159-19_subsidy-default_regulatary-DEFAULT_CFC.xml) downloaded from mirrors lolinet com / firmware / Moto / Nash / retail
Pls let me know if you want more info.
Thanks in advance.
Click to expand...
Click to collapse
What firmware did you flash from? Stock? Do you have an unlocked bootloader?
If yes to all the above, I can give you some experimental things to try.

Yes to all and bootloader is unlocked.
btw i have flashed firmware in this order
1. i flashed NASH_PPX29.159_19_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml
then
2. XT1789-06_NASH_RETIN_9.0_PPX29.159-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
and now on
3. NASH_RETAIL_9.0_PPX29.159-19_subsidy-default_regulatary-DEFAULT_CFC.xml

That's not ideal (the additional flashes) but what I have is still worth a try and you have nothing to lose.
The first thing we need is to boot twrp on the device using fastboot (get the latest .img here and fastboot boot twrp.img it). Once in twrp, immediately reboot to "EDL."
https://dl.twrp.me/nash/
Get drivers for qualcomm 9008 mode device if needed (should show in Windows device manager under "ports"):
https://androidfilehost.com/?fid=11410963190603862036
Then get the nougat blankflash here:
https://mirrors.lolinet.com/firmware/moto/nash/blankflash/blankflash_from_NDX26.183-15_17.zip
Extract and run the cmd inside. You may need to try a few times, on different usb ports. I heard usb 2.0 works best.
If it succeeeds, try flashing your stock firmware and see if imei is back.
Good luck. This is a real stretch but it just might work...
PS: This does have potential to completely brick your device. Please keep that in mind and weigh your options.

I have tried as per instruction but still getting the "baseband not found" status on all stock oreo & nougat firmwares. So when I flash Pie retail I get wifi and Bluetooth back with 0 IMEI status. so the situation is the same.
BTW I have read somewhere the 0 IMEI issue is related persist file/folder/. I may be able to share reference link of that discussion in a while. (Link of discussion)
Let me know if you want me to test anything else. Thanks again for your time. best

hqureshi said:
I have tried as per instruction but still getting the "baseband not found" status on all stock oreo & nougat firmwares. So when I flash Pie retail I get wifi and Bluetooth back with 0 IMEI status. so the situation is the same.
BTW I have read somewhere the 0 IMEI issue is related persist file/folder/. I may be able to share reference link of that discussion in a while. (Link of discussion)
Let me know if you want me to test anything else. Thanks again for your time. best
Click to expand...
Click to collapse
That's really odd. Sorry, I have nothing right now for you but will look into this as best I can.

Thanks, btw whenever i flash stock nougat i am getting verification failed error during flashing of bootloader.img

EDL
R-T-B said:
That's not ideal (the additional flashes) but what I have is still worth a try and you have nothing to lose.
The first thing we need is to boot twrp on the device using fastboot (get the latest .img here and fastboot boot twrp.img it). Once in twrp, immediately reboot to "EDL."
https://dl.twrp.me/nash/
Get drivers for qualcomm 9008 mode device if needed (should show in Windows device manager under "ports"):
https://androidfilehost.com/?fid=11410963190603862036
Then get the nougat blankflash here:
https://mirrors.lolinet.com/firmware/moto/nash/blankflash/blankflash_from_NDX26.183-15_17.zip
Extract and run the cmd inside. You may need to try a few times, on different usb ports. I heard usb 2.0 works best.
If it succeeeds, try flashing your stock firmware and see if imei is back.
Good luck. This is a real stretch but it just might work...
PS: This does have potential to completely brick your device. Please keep that in mind and weigh your options.
Click to expand...
Click to collapse
I can see the qualcomm device in twrp on my device manager. how to i get to edl mode. there is no reboot edl option in twrp. do i command fastboot reboot edl when device in twrp screen? when i run the qboot blank-flash it says wating for device

Please use latest TWRP from here https://dl.twrp.me/nash/ load it using fastboot and the in TWRP click reboot and select EDL.
Let me know if you face any issue.

i'm on the same boat
no celluler, no IMEI
wifi and bluetooth working

Everyone keeps trying to flash pie firmware that isn't for their variant and this is the result, no baseband. Plus once you upgrade to a pie modem, you can't go back to an oreo modem. Maybe something will come along and remedy that, that's a big maybe too. The devs are trying to find a solution, but there just might not be one. You can't blankflash your way out of it, and if you're not careful you can brick your phone for real. Not 9008 brick, paperweight. Not trying to be an ass, just trying to warn others. If it isn't pie for your phone, don't flash it.

Blankflash doesn't work anyways.
Stand by we are working on another fix.

R-T-B said:
Blankflash doesn't work anyways.
Stand by we are working on another fix.
Click to expand...
Click to collapse
Let me know if you need this fastboot_nash_verizon_oem_vzw_user_9_PCX29.159-21_10d9a_release-keys-cid2_vzw.tar.gz. I have got it from @oslov a member of discord.
I have tried this in this sequence but still zero IMEI.
1. Nougat Blank flash
2. Flashed Stock Verizon Oreo and then staying in bootloader mode I flashed above Pie Update using Flash-All batch file.
Phone successfully booted with Verizon sim activation warning but IMEI was 0.
I thought I should update you guys.
Thanks

Oslov is my discord nick.
Confusing I know, lol.
Be careful with that file, we don't fully understand it yet. I gave it to you because, how much worse off can you be really?

R-T-B said:
Oslov is my discord nick.
Confusing I know, lol.
Be careful with that file, we don't fully understand it yet. I gave it to you because, how much worse off can you be really?
Click to expand...
Click to collapse
Lol. Wow!
Thanks again for doing this. Best

un1ocked said:
i'm on the same boat
no celluler, no IMEI
wifi and bluetooth working
Click to expand...
Click to collapse
Have restored IMEI # with the help of @oslov, We will share the solution in a while.

hqureshi said:
I have lost IMEI number after flashing Pie. On my Sprint Moto Z2 Force. Signal bar has turned grey and IMEI is showing as zero.
Wifi is working
Bluetooth is working
Barcodes in bootloader mode is showing some different IMEI no.
Downgrade to Stock Oreo or Naugat
If I downgrade to stock Oreo then I lost all wifi, sim and Bluetooth. Also no baseband found in bootloader.
Will appreciate if someone can help.
Thanks in advance.
Click to expand...
Click to collapse
I have resolved the 0 IMEI issue with the help of R-T-B, by doing undo Sim/network Unlock. changing CHMOD of id_00 to 0770
so now I am facing sim/network locked,
So whenever i unlock the sim/network lock i get 0 IMEI issue.
I will appreciate if someone now can help me to unlock SIM/network lock while keeping IMEI
I am currently on Retail pie with Sim/Network Locked. Phone Model is Sprint XT1789-03, dual sim enabled

Can I upgrade to Android Pie? XT 1706-06 64 GB 4 RAM

This is my question. I'm currently on ATTMX channel, but, my carrier has being saying in lot of forums AT&T México, that we are not being updated to Android Pie, due to end of cycle. I already found that:
https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
Is where you can find the update already in Stock format. My Albus is under OPSS27.76-12-25-15-2-4. But that's my question if not, I'm just leaving already the phone, wasn't all that worth it after all, but if I can update it, would be awesome for a second hand move.
Any kind of help, or comment, would be awesome. Thanks.

Vesaniaheim said:
This is my question. I'm currently on ATTMX channel, but, my carrier has being saying in lot of forums AT&T México, that we are not being updated to Android Pie, due to end of cycle. I already found that:
https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
Is where you can find the update already in Stock format. My Albus is under OPSS27.76-12-25-15-2-4. But that's my question if not, I'm just leaving already the phone, wasn't all that worth it after all, but if I can update it, would be awesome for a second hand move.
Any kind of help, or comment, would be awesome. Thanks.
Click to expand...
Click to collapse
In theory, it is possible to update.
My device is RETAR channel. And I updated using this file from the RETAIL channel.
Sorry if my English is not good: D

I also have a xt1706 from att mx, i used the method in this post https://forum.xda-developers.com/z2-play/how-to/download-z2-play-pie-ota-t3977367 but i had to install first the stock rom for retail moddel, exactly the ALBUS_RETAIL_8.0.0_OPSS27.76-12-25-23_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip, after that i copied the ota file from the post above to internal storage, searched on my system apps for motorola update services, give it storage permissions, reboot phone and when it booted the OTA appeared, so i just installed the OTA and rebooted, everything is working fine, a lot better than oreo stock or other pie based roms. the only issue i had was with Netflix, i can't install from play store due the phone showing on search for updates that system integrity is at risk.
What i'm trying to do now to solve that is to install the retail version of pie from this https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/ In the past i've installed some retail version from this web and everything worked fine so i hope installing the retail pie stock everything will work fine, speacially with netflix xD maybe i'll root because i need to record calls and none of the record callers are working fine because of the compatibility with pie, the only working method is with root.
I will update this if my attempt to install the retail version of pie and/or rooting is successful

Vesaniaheim said:
This is my question. I'm currently on ATTMX channel, but, my carrier has being saying in lot of forums AT&T México, that we are not being updated to Android Pie, due to end of cycle. I already found that:
https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
Is where you can find the update already in Stock format. My Albus is under OPSS27.76-12-25-15-2-4. But that's my question if not, I'm just leaving already the phone, wasn't all that worth it after all, but if I can update it, would be awesome for a second hand move.
Any kind of help, or comment, would be awesome. Thanks.
Click to expand...
Click to collapse
I have the XT1710-06 AMXMX Channel (not the ATTMX) with bootloader unlocked and rooted with Magisk. I upgraded to Pie using the retail version firmware from the page you mention.
1.- First I was on this stock Oreo version for my phone: XT1710-06_ALBUS_AMXMX_8.0.0_OPSS27.76-12-25-15-2-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
2.- Then I installed the retail Oreo ALBUS_RETAIL_8.0.0_OPSS27.76-12-25-23_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip to check if everything was working fine
3.- And finally I installed Pie with this firmware: ALBUS_RETAIL_9.0_PPS29.133-30_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Maybe I could skiped the step 2, I'm not sure.
I had an issue with my SD Card because system said it was damaged and I had to format it like 2 or 3 times. This happened randomly when I restarted the phone. Now all is working fine.
irvingagm said:
What i'm trying to do now to solve that is to install the retail version of pie from this https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/ In the past i've installed some retail version from this web and everything worked fine so i hope installing the retail pie stock everything will work fine, speacially with netflix xD maybe i'll root because i need to record calls and none of the record callers are working fine because of the compatibility with pie, the only working method is with root.
I will update this if my attempt to install the retail version of pie and/or rooting is successful
Click to expand...
Click to collapse
The thing with Netflix will be solved once you rooted your phone with Magisk.

̶Y̶e̶s̶ ̶y̶o̶u̶ ̶c̶a̶n̶,̶ ̶b̶u̶t̶ ̶a̶t̶ ̶l̶e̶a̶s̶t̶ ̶m̶y̶ ̶X̶T̶1̶7̶1̶0̶-̶0̶6̶ ̶h̶a̶s̶ ̶i̶s̶s̶u̶e̶s̶ ̶r̶e̶c̶o̶g̶n̶i̶z̶i̶n̶g̶ ̶t̶h̶e̶ ̶U̶S̶B̶ ̶c̶o̶n̶n̶e̶c̶t̶i̶o̶n̶ ̶o̶n̶ ̶P̶C̶.̶ ̶I̶ ̶h̶a̶v̶e̶ ̶t̶e̶s̶t̶e̶d̶ ̶m̶a̶n̶y̶ ̶c̶u̶s̶t̶o̶m̶ ̶R̶O̶M̶'̶s̶,̶ ̶A̶O̶S̶P̶,̶ ̶A̶E̶X̶,̶ ̶L̶i̶n̶e̶a̶g̶e̶ ̶O̶S̶ ̶f̶o̶r̶ ̶8̶.̶1̶,̶ ̶9̶ ̶a̶n̶d̶ ̶1̶0̶ ̶a̶n̶d̶ ̶e̶v̶e̶r̶y̶ ̶s̶i̶n̶g̶l̶e̶ ̶o̶n̶e̶ ̶o̶f̶ ̶t̶h̶e̶m̶ ̶g̶e̶t̶s̶ ̶t̶h̶e̶ ̶U̶S̶B̶ ̶c̶o̶n̶n̶e̶c̶t̶i̶o̶n̶ ̶w̶o̶r̶k̶i̶n̶g̶ ̶p̶r̶o̶p̶e̶r̶l̶y̶,̶ ̶h̶o̶w̶e̶v̶e̶r̶,̶ ̶a̶l̶s̶o̶ ̶e̶v̶e̶r̶y̶ ̶s̶i̶n̶g̶l̶e̶ ̶o̶n̶e̶ ̶o̶f̶ ̶t̶h̶o̶s̶e̶ ̶c̶u̶s̶t̶o̶m̶ ̶R̶O̶M̶s̶ ̶h̶a̶s̶ ̶i̶s̶s̶u̶e̶s̶ ̶w̶i̶t̶h̶ ̶t̶h̶e̶ ̶S̶p̶e̶a̶k̶e̶r̶s̶,̶ ̶s̶p̶e̶c̶i̶a̶l̶l̶y̶ ̶w̶h̶e̶n̶ ̶t̶h̶e̶r̶e̶ ̶i̶s̶ ̶a̶n̶ ̶o̶n̶g̶o̶i̶n̶g̶ ̶c̶a̶l̶l̶ ̶i̶t̶ ̶d̶i̶s̶t̶o̶r̶t̶s̶ ̶t̶h̶e̶ ̶a̶u̶d̶i̶o̶ ̶s̶o̶ ̶m̶u̶c̶h̶ ̶i̶t̶ ̶i̶s̶ ̶i̶m̶p̶o̶s̶s̶i̶b̶l̶e̶ ̶t̶o̶ ̶u̶s̶e̶ ̶t̶h̶e̶ ̶p̶h̶o̶n̶e̶ ̶d̶a̶i̶l̶y̶ ̶f̶o̶r̶ ̶c̶a̶l̶l̶s̶,̶ ̶w̶h̶i̶c̶h̶ ̶i̶n̶t̶e̶r̶e̶s̶t̶i̶n̶g̶l̶y̶ ̶t̶h̶i̶s̶ ̶i̶s̶s̶u̶e̶ ̶d̶o̶e̶s̶ ̶n̶o̶t̶ ̶h̶a̶p̶p̶e̶n̶ ̶o̶n̶ ̶S̶t̶o̶c̶k̶ ̶R̶O̶M̶.̶ ̶H̶a̶s̶ ̶a̶n̶y̶o̶n̶e̶ ̶h̶a̶d̶ ̶t̶h̶i̶s̶ ̶p̶r̶o̶b̶l̶e̶m̶?̶
EDIT: Actually the USB connection issue is caused by a bad guide that lacks some commands. This guide gets everything right without any issues.
https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-flash-update-stock-rom-t3838213
EDIT2: The audio issue only affects users who have upgraded to Stock Pie. This ROM's modem file causes distortion on audio during calls and must be avoided during the upgrading process. To fix the audio issue simply flash the modem file from Stock Android Oreo.

I'm currently on OPSS27.76-12-25-15-2-4
Can i upgrade directly to PPS29.133-30
Or do i need to flash them one by one (That would be annoying and nonsensical).
Please confirm.

Yes, you can.
AndroidManager said:
I'm currently on OPSS27.76-12-25-15-2-4
Can i upgrade directly to PPS29.133-30
Or do i need to flash them one by one (That would be annoying and nonsensical).
Please confirm.
Click to expand...
Click to collapse
I actually fixed the USB connection issue, it was actually caused by a bad installation (one of those flashing adb guides has missing commands needed for proper USB mode to function properly), this is NOT ROM issue as the missing commands will cause the USB connection to fail whether it is Nougat, Oreo or Pie.
Follow this guide. https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-flash-update-stock-rom-t3838213
But keep in mind one thing.
Avoid flashing the modem file NON-HLOS.bin because it is known the modem file from Stock Pie causes audio issues on Custom ROMs. This will be helpful later if you decide to flash Custom ROMs into it.

Ok. One more thing. My phone model is xt1710-06. That ROM is compatible with it right? Please reply soon, as I'm about to flash it.
leodexe said:
I actually fixed the USB connection issue, it was actually caused by a bad installation (one of those flashing adb guides has missing commands needed for proper USB mode to function properly), this is NOT ROM issue as the missing commands will cause the USB connection to fail whether it is Nougat, Oreo or Pie.
Follow this guide. https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-flash-update-stock-rom-t3838213
But keep in mind one thing.
Avoid flashing the modem file NON-HLOS.bin because it is known the modem file from Stock Pie causes audio issues on Custom ROMs. This will be helpful later if you decide to flash Custom ROMs into it.
Click to expand...
Click to collapse

yes
AndroidManager said:
Ok. One more thing. My phone model is xt1710-06. That ROM is compatible with it right? Please reply soon, as I'm about to flash it.
Click to expand...
Click to collapse
Do you speak spanish by any chance? I also have that model and that one comes from Spanish Providers for Latin America. I had some issues earlier because of some inaccuracies and other stuff I wasn't aware like the modem thing from Stock Android 9 distorting audio during calls. Now I got everything working properly and flashed Custom ROM AEX (you need Treble TWRP to flash custom ROMs) with working audio without problems.

I tried the internal storage method, but nothing happened. Then i tried the ADB method, which also failed (invalid signature). I'm gonna try to update to OPSS27.76-12-25-23 first, if that works, then I'll attempt to upgrade to PPS29.133-30 again.
In any case, it's very annoying. Let's hope it works though.
Once I'm done with that, I have to waste more time on rooting it, then enabling Camera2 API & Wireless display...

I tried the internal storage method, but nothing happened. Then i tried the ADB method, which also failed (invalid signature). I'm gonna try to update to OPSS27.76-12-25-23 first, if that works, then I'll attempt to upgrade to PPS29.133-30 again.
In any case, it's very annoying. Let's hope it works though.
Once I'm done with that, I have to waste more time on rooting it, then enabling Camera2 API & Wireless display...

Are you using fastboot or mfastboot? And you are using up to date adb?

Didn't work. Invalid signature again. :/
Screw this. I'm gonna unlock bootloader, then root the phone, then flash Pie ROM through RSDlite. If even that fails, then screw Pie. I'll stay on Oreo.

AndroidManager said:
I tried the internal storage method, but nothing happened.
Click to expand...
Click to collapse
Sometimes this method works, sometimes may not work.
AndroidManager said:
Then i tried the ADB method, which also failed (invalid signature). I'm gonna try to update to OPSS27.76-12-25-23 first, if that works, then I'll attempt to upgrade to PPS29.133-30 again.
Click to expand...
Click to collapse
You need bootloader unlocked for this process.
felipecassiors said:
Your bootloader must be unlocked.
Click to expand...
Click to collapse
JulioCeesarC said:
I recomend bootloader unlocked for this process
Click to expand...
Click to collapse
HTCDevil said:
Bootloader unlocked but without root
Click to expand...
Click to collapse

RSDLite didn't work either. It was not able to detect my device at all, so i couldn't proceed flashing this way.
Then i followed this video: https://www.youtube.com/watch?v=n57v9r2jysw
It's basically the same as the ADB method, except he extracts the ZIP file & uses individual commands to flash all items. I tried his method, and it worked wonders. I'm on Pie ROM now, it's all good.

AndroidManager said:
RSDLite didn't work either. It was not able to detect my device at all, so i couldn't proceed flashing this way.
Click to expand...
Click to collapse
RSD Lite isn't recommended as it can screw up your basebands getting a phone with no signal whatsoever. The standard ADB fastboot is recommended over everything else.
AndroidManager said:
Then i followed this video: https://www.youtube.com/watch?v=n57v9r2jysw
Click to expand...
Click to collapse
In 1:30 of the video, the following commands are missing:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
Without these commands, the USB and MTP Mode of the phone will never work. This is true for the XT-1710-06, and probably true for all other variants. Besides, it will do a heavier installation, meaning it will install all the OEM stuff that will eat space, resources and you will not probably use anyways.
AndroidManager said:
It's basically the same as the ADB method, except he extracts the ZIP file & uses individual commands to flash all items. I tried his method, and it worked wonders. I'm on Pie ROM now, it's all good.
Click to expand...
Click to collapse
Yes, it is, in fact, it is the exact same method as the standard ADB fastboot flash, because you need to extract the zip file anyways. But this video is mostly based on @JulioCeesarC's guide, which specifically lacks these three commands which are needed for a proper correct installation.
A better guide for flashing/updating Z2P to Pie 9.0 is this one: https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-flash-update-stock-rom-t3838213
The first statement in this guide is that YOUR BOOTLOADER must be unlocked for this process. This will become useful later if something goes wrong. As a locked bootloader can render the phone completely bricked if something goes wrong during the process. You were so LUCKY because your locked bootloader refused to flash the update. Otherwise you could end with a dead unrecoverable phone.
However, all of these guides in XDA forgets another important REQUIRED step:
If you upgrade to Stock Pie, and you decide to flash a Custom ROM later, you will have audio issues during calls. This is caused by the Stock Pie's faulty modem file (NON-HLOS.bin), the good thing is that the Stock Oreo's modem file works flawlessly and must be skipped during the upgrading/flashing process.
If you wanted a Spanish guide, then all you had to do is just ask for one. There might be more spanish users that don't quite understand english very well and might mess up with this trivial process. I will make a Spanish guide to help them and avoid more conflicts and unwanted bricks. I know all this through proper testing with trial and error.

Hey. I just tried plugging USB, and it is working fine. Even File transfer mode is working fine... I have not noticed any issues so far. So I'm gonna keep it as is without reflashing the ROM with those additional commands. If i encounter an issue later, i will consider your suggestion.
BTW, Now i am running Pie & have an unlocked bootloader. Please tell me the proper way to root the phone. I tried rooting before with TWRP & Magisk, but the phone went to bootloop. I then had to reflash the Pie ROM with ADB method to get it working again. I think the problem has to do with DM-Integrity & Encryption, but I've already wasted hours getting Pie to run on it, and don't want to waste more hours trying to root it. So a quick and easy working guide would be useful.
Also, i don't intend to install any custom ROMs on it. I just have to root it so i can enable Camera2 API (disabled on my variant), and enable wifi display (disabled by default on most AOSP based ROMs, including mine).
BTW, I don't understand spanish. I was looking for guides and found that video. I enabled english subtitles & understood enough to give it a shot. I have some experience with flashing & rooting in the past, so i can understand these concepts and methods.

Well, i followed this thread: https://forum.xda-developers.com/z2-play/development/twrp-3-2-0-0-moto-z2-play-albus-t3715660
And was able to root my phone without bootlooping. All is well for now. Now i will enable Wifi Display & Camera2 API. Once those are done. I'll have peace at last.
---------- Post added at 01:47 AM ---------- Previous post was at 01:27 AM ----------
Just successfully enabled wireless display (persist.debug.wfd.enable=1) & camera2 API (persist.camera.HAL3.enabled=1) within build.prop
Both are working as intended. I have succeeded in doing everything i desired to do. It only took a bunch of hours & a headache...
But thanks a lot to "leodexe" for helping me out. You're cool, friend!

AndroidManager said:
Hey. I just tried plugging USB, and it is working fine. Even File transfer mode is working fine... I have not noticed any issues so far. So I'm gonna keep it as is without reflashing the ROM with those additional commands. If i encounter an issue later, i will consider your suggestion.
Click to expand...
Click to collapse
Oh, mine is XT1710-06 and it had issues with the USB mode, I figured out it was because of the missing OEM commands, I tested several times flashing without these and the USB connection would never work, after a simple flash with all the commands it started to work again, so if yours worked without these then maybe it's a thing of luck. But keep in mind that without the OEM commands there will be more installed stuff, I prefer to include the OEM commands to remove all the bloatware, so the user can decide which thing to install later.
AndroidManager said:
BTW, I don't understand spanish. I was looking for guides and found that video. I enabled english subtitles & understood enough to give it a shot. I have some experience with flashing & rooting in the past, so i can understand these concepts and methods.
Click to expand...
Click to collapse
I am doing a spanish guide anyways, so spanish users can properly do the upgrade process without messing everything.
AndroidManager said:
I have succeeded in doing everything i desired to do. It only took a bunch of hours & a headache...
Click to expand...
Click to collapse
Same feeling bro, it took me a few nights and lots of headaches to get things working after upgrading.
AndroidManager said:
But thanks a lot to "leodexe" for helping me out. You're cool, friend!
Click to expand...
Click to collapse
Hey, thanks, no problem, the first time I arrived at this forum I had no clue how to do most things, so I'm here to help anyone whenever I can. Keep up the good work!

MODEM went crazy after upgrading MIUI to [Global 10.3.5.0] from [China 9.6.12]

Hi, I'm begging you all for help.
Please, even if you don't know the answer, share any sort of advice.
I'm not a newbie (25+ years story of Unix/Reversing), but I know nothing about radio.
Here's a list of symptoms:
1) Sometimes the WIFI MAC Address comes up as 02:00:00:00:00:00 and IMEI isn't available, then they both magically come up (without rebooting, after the SIM Is read - see n. 2)
2) It keeps powering ON & OFF the SIM and switching between Connected , No Signal , Emergency. Sometimes taking the SIM out & back in helps. Selecting the Preferred Network Type from the modem debug screen keeps it connected for long periods.
3) It won't search for alternative networks to Register Manually
3) IMS Registration is showing as Not Registered always, even while it's connected: Voice + Data (?!?)
4) From the Debug Info only 1 cell appears as SRV = R+N and has a CELL ID, so it seems it connects only to 1 cell at a time.
I can't post screenshots as I lost my old username here, so I signed-up again.
Nothing works, it was a new phone. I wanna die.
Thank you all for your help.
Thanks.

I have problems with modem and camera wgen updating ta android 9.
I would recomend you to rollback to 10.2.1.0
I would use this method
1. Backup your media files to your computer
2. Unlock bootloader
3. Download fastboot china version of 10.2.1.0 and Flash it with mi flash (choose wipe but dont lock!)
4. Flash orange fox twrp with fastboot
5 wipe all partitions exvept internal storage with orangefox
6. Download 10.2.1.0 from xiaomi.eu and flash it with orangefox
Tell me is you want direct links to all files that you need.
If you still have problems after downgrading I can prove my persist and modem files
Good luck

eliaztheone said:
I would recomend you to rollback to 10.2.1.0
Click to expand...
Click to collapse
@eliaztheone thank you for your reply and your offer about the files, I'll take it if necessary.
Just one question: won't that trigger Anti-Rollback ?
(I don't need to stay on MIUI: do I have other options?)

DoYouWantFriesWithThat said:
@eliaztheone thank you for your reply and your offer about the files, I'll take it if necessary.
Just one question: won't that trigger Anti-Rollback ?
(I don't need to stay on MIUI: do I have other options?)
Click to expand...
Click to collapse
Your anti rollback is already triggered on 4. Thats the arb value on 10.2 too. As long as you dont flash older miui 9 firmware you should be ok...

eliaztheone said:
Your anti rollback is already triggered on 4. Thats the arb value on 10.2 too. As long as you dont flash older miui 9 firmware you should be ok...
Click to expand...
Click to collapse
The roll-back went well but the phone is still unstable.
I'm not sure why: did the Persist get corrupted? Or the EFS partition? I have some backups but I'm not sure what to do.
Can you provide the files that you mentioned, or maybe some pointers?
What could be wrong with the phone?
Thanks a lot @eliaztheone

DoYouWantFriesWithThat said:
The roll-back went well but the phone is still unstable.
I'm not sure why: did the Persist get corrupted? Or the EFS partition? I have some backups but I'm not sure what to do.
Can you provide the files that you mentioned, or maybe some pointers?
What could be wrong with the phone?
Thanks a lot @eliaztheone
Click to expand...
Click to collapse
I can give you my efs and persist backup if you want? Then you can use partitions backup and restorev from playstore.
You need to be rooted with magisk to restore
Are you on the xiaomi.eu version of 10.2.1.0 and is it the 8.1 version or 9.0?

eliaztheone said:
I can give you my efs and persist backup if you want? Then you can use partitions backup and restorev from playstore.
You need to be rooted with magisk to restore
Are you on the xiaomi.eu version of 10.2.1.0 and is it the 8.1 version or 9.0?
Click to expand...
Click to collapse
I am on Xiaomi.eu 10.2 with Android 9 now, as you suggested. Rooted & with Magisk.
I have backups of my old PERSIST from the China 9.x ROM. Should I flash that (or do I risk bricking) ?
I was reading on persist.img and I don't understand one thing: if it's different for every phone, why there's a persist.img in every Fastboot ROM ?
EDIT: I flashed my old Persists (tried various ones), and the problem.....persists! :') lol
So I'm back to my most recent Persist and still in need for help.
PS: if it helps for a diagnosis, any time the modem resets the SIM it dumps a lot of logs in /ramdump

DoYouWantFriesWithThat said:
I am on Xiaomi.eu 10.2 with Android 9 now, as you suggested. Rooted & with Magisk.
I have backups of my old PERSIST from the China 9.x ROM. Should I flash that (or do I risk bricking) ?
I was reading on persist.img and I don't understand one thing: if it's different for every phone, why there's a persist.img in every Fastboot ROM ?
EDIT: I flashed my old Persists (tried various ones), and the problem.....persists! :') lol
So I'm back to my most recent Persist and still in need for help.
PS: if it helps for a diagnosis, any time the modem resets the SIM it dumps a lot of logs in /ramdump
Click to expand...
Click to collapse
Sorry I was not clear with my guide.. You needed to flash the android 8.1 version of 10.2.1.0 . I guess that wont help either but maybe so try it..
Try it and if it does not work. I will make backup of my persist and efs and modem and send them to you and after that u need to change to your imei numbers with qualcom app..

eliaztheone said:
Sorry I was not clear with my guide.. You needed to flash the android 8.1 version of 10.2.1.0 . I guess that wont help either but maybe so try it..
Try it and if it does not work. I will make backup of my persist and efs and modem and send them to you and after that u need to change to your imei numbers with qualcom app..
Click to expand...
Click to collapse
I tried it following this guide to restore the Persist partition (https://forum.xda-developers.com/xi...guide-restoring-persist-partition-to-t3906424 - via Fastboot, not EDL) , and right after flashing the SIM was working fine on 4G/LTE and the phone didn't present any problems.
Then I opened up Google-Maps and gave it permission to read the GPS and it went crazy: not reading the SIM anymore, rebooting, etc. And turning GPS off now won't help. So I guess the problem is with the Modem and the fact that it connects to only 1 Cell - no idea why.
@eliaztheone

eliaztheone said:
Sorry I was not clear with my guide.. You needed to flash the android 8.1 version of 10.2.1.0 . I guess that wont help either but maybe so try it..
Try it and if it does not work. I will make backup of my persist and efs and modem and send them to you and after that u need to change to your imei numbers with qualcom app..
Click to expand...
Click to collapse
I am on 10.2.1.0 - Android 8.1 now. In addition to what you suggested I restored the persist.img via Fastboot (not EDL) following this guide on XDA .
Right after flashing the phone didn't present any problems (SIM/4G was working without hiccups). As I opened up Google-Maps and gave it permission to read the GPS it went crazy: not reading the SIM anymore, rebooting, etc. Turning GPS off now won't help, it constantly reboots - I have to use Airplane Mode.
So I guess the problem is still in the Modem. Maybe it's the fact that it connects to only 1 Cell, apparently.
@eliaztheone if you can provide the files I'll try one last time. Thank you.

I will upload them tonight hopefully. You need to be on 10.2.1.0 oreo xiaomi.eu version.
You also need to be rooted with magisk so you can restore them with partition backup and restore
---------- Post added at 07:33 PM ---------- Previous post was at 07:28 PM ----------
Did you try to flash modem_fix_ysl.zip? It resets the modem.img and modemst1.img and modemst2.img

Take your time, thank you.
While inspecting the ramdump I noticed the following:
[ 21.864464] [c:1] [p:<003975, android.vending>] Fatal error on the modem.
[ 21.864522] [c:1] [p:<003975, android.vending>] modem subsystem failure reason: rflm_diag_error.cc:361:[email protected]_qlnk.cpp:1090 [9,3] RF stuck in QLINK start s.
[ 21.864530] [c:1] [p:<003975, android.vending>] subsys-restart: subsystem_restart_dev(): Restart sequence requested for modem, restart_level = RELATED.​
There's many SELinux odd log entries too, not sure if that's normal. When I disabled SELinux from the terminal the 4G immediately picked up...totally weird
eliaztheone said:
[/COLOR]Did you try to flash modem_fix_ysl.zip? It resets the modem.img and modemst1.img and modemst2.img
Click to expand...
Click to collapse
I'll try to flash it, thank you.
I am on 10.2.1.0 oreo xiaomi.eu. Do you think it makes sense to try a custom ROM ?
Thank you.
EDIT:
- I flashed modem_fix_ysl.zip but it didn't have any effect.
- I find the ramdumps from the china ROM much cleaner and errorless than the Xiaomi.eu ROM, just saying

I have sent you a pm

Have you guys found a solution? I have the exactly same problem on Mi Max 3 4/64Gb version. I'm on MIUI Global Stable 10.3.5.0. I was on China stable and had issues,so i flashed Global Stable fastboot rom using Mi Flash Tool(flash all option),and It doesn't solve the problem.I have unlocked bootloader,and no previous system backup.
Also i tried flashing NON-HLOS.bin file from Global Stable fastboot ROM using command : fastboot flash modem NON-HLOS.bin
Also i tried something that worked on my old redmi 4,after NON-HLOS.bin flash,executed fastboot commands :
fastboot erase modemst1 and modemst2,but no luck because of "partition is write protected" error.
Have you found what's the cause of this problem?Is it hardware?Is it corrupted modem files?Will custom rom solve it? Please, any help,any suggestion will be appreciated. I'll try everything to fix it. Thank you in advance.

@ghost baby
I tried the following:
- reflashing Global ROM
- flashing Xiaomi.eu ROM as per instructions of of Eliaztheone
- restoring a backup of old China ROM
- reflashing China ROM
- analyzing the ramdumps (memory dumps & system/radio-modem logs)
- EDL flashing (with `fastboot oem edl` - not with the deep-flash cable)
All the reflashes included overwriting the EFS (modemst1/2) & PERSIST partitions, automatically (in bulk) or manually, taken from various sources including those that Eliaztheone kindly sent to me. The EDL flashing didn't work because I had no authorization on my Xiaomi account (I've tried all combinations of SDR programmers & old versions of MiFlash - none works) so I've then tried to get a remote authorization, also without success: the guy from UNBRICK.RU told me that Xiaomi revoked all authorizations lately to push out of business the remote-auth-flashers.
From my understanding of the ramdumps the problem seems to be an internal modem fault. Since ARB wasn't triggered when I rolled back to China ROM, I suspect that the fault is a hardware (or very low-level SW) software in the radio modem, and so it can be maybe fixed only by EDL flashing.
That's why I resorted to finding a local authorized service center this week. But I have to see how much money they ask me: if they ask too much I might as well buy a new OPPO or REALME phone, which are cheap & open (at least more than ****ty Xiaomi). If the service center pisses me off you'll see the result in the news.
Support the right to repair movement.
I hope this helps.

DoYouWantFriesWithThat said:
@ghost baby
I tried the following:
- reflashing Global ROM
- flashing Xiaomi.eu ROM as per instructions of of Eliaztheone
- restoring a backup of old China ROM
- reflashing China ROM
- analyzing the ramdumps (memory dumps & system/radio-modem logs)
- EDL flashing (with `fastboot oem edl` - not with the deep-flash cable)
All the reflashes included overwriting the EFS (modemst1/2) & PERSIST partitions, automatically (in bulk) or manually, taken from various sources including those that Eliaztheone kindly sent to me. The EDL flashing didn't work because I had no authorization on my Xiaomi account (I've tried all combinations of SDR programmers & old versions of MiFlash - none works) so I've then tried to get a remote authorization, also without success: the guy from UNBRICK.RU told me that Xiaomi revoked all authorizations lately to push out of business the remote-auth-flashers.
From my understanding of the ramdumps the problem seems to be an internal modem fault. Since ARB wasn't triggered when I rolled back to China ROM, I suspect that the fault is a hardware (or very low-level SW) software in the radio modem, and so it can be maybe fixed only by EDL flashing.
That's why I resorted to finding a local authorized service center this week. But I have to see how much money they ask me: if they ask too much I might as well buy a new OPPO or REALME phone, which are cheap & open (at least more than ****ty Xiaomi). If the service center pisses me off you'll see the result in the news.
Support the right to repair movement.
I hope this helps.
Click to expand...
Click to collapse
Thank you man, I'll try everything you said tommorow. The device hardware is awesome,and i really want to support xiaomi,only if they had solution for this problem. Also i think keeping ARB on unlocked bootloader is a bad decision,it really makes this whole process harder.
I'm hoping you get you phone fixed and looking forward to see how this will end.
Thanks for helping me man.
(Sorry for bad English)
---------- Post added at 10:35 PM ---------- Previous post was at 10:33 PM ----------
Maybe someone's QCN file can help us?

DoYouWantFriesWithThat said:
@ghost baby
I tried the following:
- reflashing Global ROM
- flashing Xiaomi.eu ROM as per instructions of of Eliaztheone
- restoring a backup of old China ROM
- reflashing China ROM
- analyzing the ramdumps (memory dumps & system/radio-modem logs)
- EDL flashing (with `fastboot oem edl` - not with the deep-flash cable)
All the reflashes included overwriting the EFS (modemst1/2) & PERSIST partitions, automatically (in bulk) or manually, taken from various sources including those that Eliaztheone kindly sent to me. The EDL flashing didn't work because I had no authorization on my Xiaomi account (I've tried all combinations of SDR programmers & old versions of MiFlash - none works) so I've then tried to get a remote authorization, also without success: the guy from UNBRICK.RU told me that Xiaomi revoked all authorizations lately to push out of business the remote-auth-flashers.
From my understanding of the ramdumps the problem seems to be an internal modem fault. Since ARB wasn't triggered when I rolled back to China ROM, I suspect that the fault is a hardware (or very low-level SW) software in the radio modem, and so it can be maybe fixed only by EDL flashing.
That's why I resorted to finding a local authorized service center this week. But I have to see how much money they ask me: if they ask too much I might as well buy a new OPPO or REALME phone, which are cheap & open (at least more than ****ty Xiaomi). If the service center pisses me off you'll see the result in the news.
Support the right to repair movement.
I hope this helps.
Click to expand...
Click to collapse
Maybe someone's QCN file can help us?[/QUOTE]
All authorizations has been locked down for a while now, learned that the hard way during in the early days of ARB4 and i tried to flash a stable rom with a lower ARB number and my phone bricked. IThen i found someone to flash a beta rom by remote with authroization; costed me 15 USD. EDL flash was the only way if you still have fastboot. I worked with the service guy because he also wants to figure out the problem also. After bricking my device 4 times, I got the right recovery to use and then TWRP Recovery worked for the 4GB version. I got the 6GB version also and the people who sold me the phone had already unlocked the bootloader, I had to double check to see using command prompt. The i flashed the Recovery i was given to by a user on the AOSiP thread, thinks its Page 7, its a TWRP CN Recovery.. and it worked in both devices.

@Wmateria can you give me the contact of this person who gave you the remote Auth ?
I just phoned Xiaomi and they told me that Xiaomi's warranty is only valid at national level (read: each european country collects phones sold on its territory, and sends them to specific labs).
Wmateria said:
Maybe someone's QCN file can help us?
Click to expand...
Click to collapse
The QCN won't help cause we can't access EDL anyway even via QFIL.
If anyone has a contact for remote Auth, I'd appreciate if he/she could share it.
Thanks.

DoYouWantFriesWithThat said:
@Wmateria can you give me the contact of this person who gave you the remote Auth ?
I just phoned Xiaomi and they told me that Xiaomi's warranty is only valid at national level (read: each european country collects phones sold on its territory, and sends them to specific labs).
The QCN won't help cause we can't access EDL anyway even via QFIL.
If anyone has a contact for remote Auth, I'd appreciate if he/she could share it.
Thanks.
Click to expand...
Click to collapse
I found some article that shows how to flash QCN file form DIAG mode,and how to enter that mode. I'll try and keep you updated.

Wmateria said:
Maybe someone's QCN file can help us?
Click to expand...
Click to collapse
All authorizations has been locked down for a while now, learned that the hard way during in the early days of ARB4 and i tried to flash a stable rom with a lower ARB number and my phone bricked. IThen i found someone to flash a beta rom by remote with authroization; costed me 15 USD. EDL flash was the only way if you still have fastboot. I worked with the service guy because he also wants to figure out the problem also. After bricking my device 4 times, I got the right recovery to use and then TWRP Recovery worked for the 4GB version. I got the 6GB version also and the people who sold me the phone had already unlocked the bootloader, I had to double check to see using command prompt. The i flashed the Recovery i was given to by a user on the AOSiP thread, thinks its Page 7, its a TWRP CN Recovery.. and it worked in both devices.[/QUOTE]
Did EDL flash solved the problem?