Develop Bugs

Real OFFICIAL STOCK ROM for XT1625/XT1642 (Moto G4/G4 Plus)

Hi,
Everybody is looking for official stock roms for Moto G4/G4 Plus *AWAY* from Motorola support, which looked to me like kind of weird but I now know why: people are looking for stock roms that will allow them over the air upgrades. If you have a developer edition or a moto with unlocked bootloader, Moto's own roms are flashable and *COMPLETELY WORKING*
motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Go to above URL, quick login using G+, follow instructions to get to the download list. The listed download for XT1625 will also work just fine for XT1642.
Or, you can just use this direct link: motorola-global-portal.custhelp.com/cc/ajaxCustom/getBootFile/fileName/ib65qpz53y
may also require login.
******** VERY IMPORTANT ************
Everybody lists fastboot utility commands with which you restore a Moto stock rom. They do not tell these severe warnings:
- Never flash a gpt.bin file unless you really absolutely ultimately intentionally and knowingly NEED TO. Why? in 99.9% of the cases it is useless to your phone and your needs and all it will do is deprive you the ability to downgrade to an earlier version or flash an older boot file, system file, ...etc. You get the picture. BTW, gpt.bin is only a partition image containing Moto's partition table scheme, with versioning for downgrade prevention. Keep away from it. It is pure EVIL.
IF YOU SEE gpt.bin FILE, DELETE IT WITHOUT HESITATION.
- Our second vanity: bootloader.img or bootloader.bin or anything that spells BOOTLOADER. EVIL. DELETE IT. It will 99.9% only mess up your cellular capability and render your phone without voice calls, with out SMS and without 2G/3G/4G; no data whatsoever. It will convert your phone into a 5.5 inch SIM-less tablet. It will KILL YOUR SIM SLOTS.
Instruction are on the first link, but anyway, here we go:
To flash, put the phone in fastboot mode:
1. Power OFF your device
2. Then Power ON + Volume Down Alternatively, you can reboot into fastboot mode if you have adb...
adb reboot bootloader.
Next flash the images using fastboot:
Code:
"DELETED COMMAND HERE WAS SUPPOSED TO FLASH THE GPT.BIN. NEVER DO IT"
"DELETED COMMAND HERE WAS SUPPOSED TO FLASH THE BOOTLOADER. NEVER DO IT"
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
enjoy

****removed****

MK+2017 said:
****removed****
Click to expand...
Click to collapse
I would like back to MM from Nougat on XT1642. This firmware comes from a trusted source, but have you tried this firmware, no problems after flashing? Do I have to have an unlocked bootloader ?

kkamelot said:
I would like back to MM from Nougat on XT1642. This firmware comes from a trusted source, but have you tried this firmware, no problems after flashing? Do I have to have an unlocked bootloader ?
Click to expand...
Click to collapse
if you have not unlocked boot-loader you are covered by warranty and I advise you keep it that way. Motorola is a BI***.
if you really can't live without older stock, go to moto service and ask them to do it for you. should not cost you much, if any.
if what you hate is stock firmware, you can unlock bootloader, get warranty off, and flash LinageOS. Stable enough although still in nightly builds (successor of CyanogenMod)
hope that helps.
PS1: what you would fear the most is lose your SIM slot, happens a lot. Be safe!
PS2: asking if I tried it yes, I did. it worked. but I was on 6.0.1 at the time. do not take risk.
PS3: Motorola is a *****. DON'T MESS WITH IT.

MK+2017 said:
if you have not unlocked boot-loader you are covered by warranty and I advise you keep it that way. Motorola is a BI***.
if you really can't live without older stock, go to moto service and ask them to do it for you. should not cost you much, if any.
if what you hate is stock firmware, you can unlock bootloader, get warranty off, and flash LinageOS. Stable enough although still in nightly builds (successor of CyanogenMod)
hope that helps.
PS1: what you would fear the most is lose your SIM slot, happens a lot. Be safe!
PS2: asking if I tried it yes, I did. it worked. but I was on 6.0.1 at the time. do not take risk.
PS3: Motorola is a *****. DON'T MESS WITH IT.
Click to expand...
Click to collapse
Thank you for your answer !
I have one more question, is there way (like in nexus) to back to original software (Nougat can be) after changing OS or make a modifications?

kkamelot said:
Thank you for your answer !
I have one more question, is there way (like in nexus) to back to original software (Nougat can be) after changing OS or make a modifications?
Click to expand...
Click to collapse
There is, but if you are not good with command line, think twice. Check here: https://forum.xda-developers.com/moto-g4-plus/help/complete-partition-backup-script-xt1644-t3608408
you would typically use that alongside full TWRP backup.
I can assure you nothing will go wrong if you jump straight to LineageOS, it might only go wrong if you take the bad decision of going back to stock. The dd images would give you solid backup, though.
In case you lose your sim slot, you can use help from here: https://forum.xda-developers.com/showpost.php?p=72343095&postcount=101
I intuitively contributed to that solution Giving is taking!
Thank you @m.sawastik and @givitago

MK+2017 said:
There is, but if you are not good with command line, think twice. Check here: https://forum.xda-developers.com/moto-g4-plus/help/complete-partition-backup-script-xt1644-t3608408
you would typically use that alongside full TWRP backup.
I can assure you nothing will go wrong if you jump straight to LineageOS, it might only go wrong if you take the bad decision of going back to stock. The dd images would give you solid backup, though.
In case you lose your sim slot, you can use help from here: https://forum.xda-developers.com/showpost.php?p=72343095&postcount=101
I intuitively contributed to that solution 😊Giving is taking!
Thank you @m.sawastik and @givitago
Click to expand...
Click to collapse
I would also be happy to assist you if you want to jump to LineageOS. I won't assist you with dd backup, just because you need to take that responsibility on your own

My XT1625 is already on Lineage OS Andriod N. However, I feel like the cellular reception and thus battery life has been worse versus stock.
I wanted to flash only the latest baseband from the latest stock Andriod N but your Moto link only has 6.0.1 for XT1625.
What gives- I thought Motorola already updated the G4 to 7.0?

Will OTAs work with this?
Will OTAs work with these?

If I just want to upgrade my modem/baseband and then go back to LOS, do I just need to type "fastboot flash modem NON-HLOS.bin" or do I need to make a full install?

it works for moto g4 t1625 amazon version?? compilation number npj25.93-14.5 ?????? i answer this because in the web site motorola its appear the moto g4 rom xt1625 build MPJ24.139-64

Works!
I just want to say that I had a Moto G4 Plus (XT1642) that had no SIM recognition, no IMEI, no Wifi, and thanks to the instructions at the top of this thread, I now have it all.
I spent the whole day trying all sorts of things. Now it finally works!
Thanks!

How do I flash?
Hi friend, sorry but my English is not good.
My phone will receive nougat via OTA?

Something has broken my sound notifications
When I try this procedure I get a lot of these errors against some of the commands
(bootloader) Image aboot failed validation
(bootloader) Preflash validation failed
(bootloader) will fail: flash:aboot
FAILED (remote failure)
And now sounds that accompany any notifications from any applications fail to make any sound. Vibrate does initiate.

I am trying to find a way to enable hotspot on my ATT Moto G4 plus, if I flash this rom can anyone confirm it will unlock this feature? Torn between flashing or just going in to kernel and make change for this feature, any advice appreciated..

how to restore the sim slot after flash( i have no service)
i had frp, and after remove it with 3rd party tool i flash new rom.
now i have no service(but it detect the sim), there is any way to restore the sim slot?
i flashed the original rom from motorola site and it didnt help.
i flash the lineage OS and it didnt helped.
thanks

ggc201 said:
there is any way to restore the sim slot?
Click to expand...
Click to collapse
I've been searching for a fix for a few months now, whenever I get free time. Most threads about the subject die and aren't revisited. Someone will inevitably come to this page on a Google search wondering like us. I haven't found anything that will help and so I'm calling it quits. This phone is so outdated it would be better suited to find a deal somewhere else.

Thanks... can't find the button.
I have the xt1625 amz channel version and the: XT1625-XT1644_ATHENE-RETUS_6.0.1_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip > provided enhanced LTE whereas the official OS did not support. I can actually do sh** on my phone without hanging up.
I want you and yours to be blessed forever and great post.
Bootloader is unlocked but somehow it is stuck between root and no root. Will figure it out....
Again... thanks... this is a big deal for me. :good:

non-developer edition?
If you have a developer edition or a moto with unlocked bootloader, Moto's own roms are flashable and *COMPLETELY WORKING*
Click to expand...
Click to collapse
Can anyone attest to having successfully flashed an unlocked non-developer edition G4 with this ROM? Motorola clearly warns against doing this:
IMPORTANT! Do not use these images/packages on non-developer edition devices or on devices with a locked bootloader.
Click to expand...
Click to collapse
(sorry, I'm a new member so I'm not allowed to include a link)

[BRICKED]Need help to revive my P2a42

Hey guys
It all started with an OEM unlock and wanting to have Nougat update after flashing TWRP. Mobile network stopped working after flashing Nougat update ROM. Trying to fix that ended up with a hard brick (That's right. Only response I get from the phone is notification LED and Vibration)
Have been trying to fix it for past two weeks and all were dead ends. QFIL, QcomDloader and MI flash tool are some of the tools I have tried and given up. What left is MB swap. Need to be back to India in order to do it economically. Here in UK, I can get a new phone for the money to fix this one.
Do you guys know any ways I can try? Is there a firehose programmer available for P2a42's chipset? I have factory image for P2 with me (P2a42_S232_170320_ROW_fastboot).
ADB and fastboot are not recognising the phone. Device manager recognises it as Qualcomm HS-USB QLoader 9008 (COMX), value for X changes.
Below is the log for MI Flash tool.
[0.15 COM4]:[COM4]:start flash.
[2.18 COM4]:cannot receive hello packet,MiFlash is trying to reset status!
[4.77 COM4]:cannot receive hello packet,MiFlash is trying to reset status!
[7.27 COM4]:try to reset status.
[8.46 COM4]:write time out try agian 96
[9.97 COM4]:write time out try agian 97
[11.47 COM4]:write time out try agian 98
[13.00 COM4]:write time out try agian 99
[14.51 COM4]:write time out try agian 100
[15.13 COM4]:error:The write timed out.
[15.14 COM4]:error:The write timed out.
Any help is much appreciated. If you can't help, better not answer, as the admin says.

Did you get the firehouse file for flashing?
I have the same issue.

sisqin1 said:
Did you get the firehouse file for flashing?
I have the same issue.
Click to expand...
Click to collapse
Nope. I tried the firehose for P1. But not working. Can someone with a working P2 take a download and share? I know at least 3 people having the same issue.

Ronin1986 said:
Nope. I tried the firehose for P1. But not working. Can someone with a working P2 take a download and share? I know at least 3 people having the same issue.
Click to expand...
Click to collapse
It depends as how far you are bricked guys.
Are you able to enter fastboot?
Does the Lenovo P2 enter fastboot by itself?
You can use the factory images using fastboot to restore functionality.
I haven't come across a firehose for the Lenovo P2.
Usually those firehose flashers are signed to match the device's signature.
Unless someone leaks it somehow. I don't see how Mi-Flasher or QPST can work.
Both require the proper signed firehose.

celoxocis said:
It depends as how far you are bricked guys.
Are you able to enter fastboot?
Does the Lenovo P2 enter fastboot by itself?
You can use the factory images using fastboot to restore functionality.
I haven't come across a firehose for the Lenovo P2.
Usually those firehose flashers are signed to match the device's signature.
Unless someone leaks it somehow. I don't see how Mi-Flasher or QPST can work.
Both require the proper signed firehose.
Click to expand...
Click to collapse
From what I read, I think he is unable to access fastboot. So fastboot restore won't work

Siva Mk said:
From what I read, I think he is unable to access fastboot. So fastboot restore won't work
Click to expand...
Click to collapse
to my knowledge. previous firehose's weren't signed. you could use them from other devices with the same chipset.
i know that the SD820's uses a signed firehose. my main phone is as SD820. as the SD625 is from the same chipset-series (QC 2016).
they have added that "security feature" to prevent what was possible in the past.
in the old chipsets i would have recommend by try looking for a firehose that was successfully used on a device with the same chipset.
google search term would be "prog_emmc_firehose_8953" but as they are all signed now. the best hope would be:
A: wait for a leak for an EDL factory flasher. the chinese will probably leak one for the P2c72, it's just a matter of time.
B: try third party solutions such as this
remember we already have factory images. that can be flashed. currently only by fastboot.
those packages already contain the critical parts like: rawprogram0.xml and the images itself
all that is required is the proper signed firehose.

I am able to enter fastboot mode and also able to downgrade / upgrade from MM to N.
But the issue is with the modem, i am unable to make or receive any calls.
The carrier name shows up but there is no connectivity.

celoxocis said:
to my knowledge. previous firehose's weren't signed. you could use them from other devices with the same chipset.
i know that the SD820's uses a signed firehose. my main phone is as SD820. as the SD625 is from the same chipset-series (QC 2016).
they have added that "security feature" to prevent what was possible in the past.
in the old chipsets i would have recommend by try looking for a firehose that was successfully used on a device with the same chipset.
google search term would be "prog_emmc_firehose_8953" but as they are all signed now. the best hope would be:
A: wait for a leak for an EDL factory flasher. the chinese will probably leak one for the P2c72, it's just a matter of time.
B: try third party solutions such as this
remember we already have factory images. that can be flashed. currently only by fastboot.
those packages already contain the critical parts like: rawprogram0.xml and the images itself
all that is required is the proper signed firehose.
Click to expand...
Click to collapse
So if i have a P2c72 and yet the model say P2a42 in About Phone.. should i wait a certain time before unlocking my Leno device? I have exp. unlocking and using fastboot to do the neccesary for applying TWRP, and rooting.

Wmateria said:
So if i have a P2c72 and yet the model say P2a42 in About Phone.. should i wait a certain time before unlocking my Leno device? I have exp. unlocking and using fastboot to do the neccesary for applying TWRP, and rooting.
Click to expand...
Click to collapse
If you're asking about the 14 days wait then yes
---------- Post added at 03:53 AM ---------- Previous post was at 03:50 AM ----------
celoxocis said:
to my knowledge. previous firehose's weren't signed. you could use them from other devices with the same chipset.
i know that the SD820's uses a signed firehose. my main phone is as SD820. as the SD625 is from the same chipset-series (QC 2016).
they have added that "security feature" to prevent what was possible in the past.
in the old chipsets i would have recommend by try looking for a firehose that was successfully used on a device with the same chipset.
google search term would be "prog_emmc_firehose_8953" but as they are all signed now. the best hope would be:
A: wait for a leak for an EDL factory flasher. the chinese will probably leak one for the P2c72, it's just a matter of time.
B: try third party solutions such as this
remember we already have factory images. that can be flashed. currently only by fastboot.
those packages already contain the critical parts like: rawprogram0.xml and the images itself
all that is required is the proper signed firehose.
Click to expand...
Click to collapse
The firehose you mentioned is similar to that if Redmi note 3(I think). In that case miflash should work. Further more the XML file name maybe same but the file content maybe different. Don't have much knowledge on this. But have used all these.

No i'm asking is it safe to go through all that process.. cause it seems multiple people had had problems unlocking and flashing and end up bricking their phones. Oh and which TWRP to flash via ADB the 3.0.3-0 or the 3.1.0-3? I see that the 3.0.3.0 does not conform with the P2c72.. am trying to flash Lineage 13 that's why i ask about the 3.0.3-0.

Wmateria said:
No i'm asking is it safe to go through all that process.. cause it seems multiple people had had problems unlocking and flashing and end up bricking their phones. Oh and which TWRP to flash via ADB the 3.0.3-0 or the 3.1.0-3? I see that the 3.0.3.0 does not conform with the P2c72.. am trying to flash Lineage 13 that's why i ask about the 3.0.3-0.
Click to expand...
Click to collapse
I personally found TWRP bit too powerful. Be sure to read how to's and do's and don'ts before doing anything. One misstep, your device is bricked.

sisqin1 said:
I am able to enter fastboot mode and also able to downgrade / upgrade from MM to N.
But the issue is with the modem, i am unable to make or receive any calls.
The carrier name shows up but there is no connectivity.
Click to expand...
Click to collapse
I can't remember out of my head but I think the NON-HLOS.bin is included in the factory image package. It would be the one responsible for the modem.
Before you replace the partition make sure your device is the P2a42 or P2C72 and use appropriate modem image. You can't simply exchange them.
If exchanged wrongly. It could end up in:
A: bootloop
B: what you are describing. Unable to connect to a network.
My official TWRP can be used to flash that partition without entering fastboot.
Simply rename that .bin into *.img and select "install" browse the folder located and select "flash image". Select the image and select the modem partition, boot into system.
---------- Post added at 08:42 AM ---------- Previous post was at 08:32 AM ----------
Wmateria said:
So if i have a P2c72 and yet the model say P2a42 in About Phone.. should i wait a certain time before unlocking my Leno device? I have exp. unlocking and using fastboot to do the neccesary for applying TWRP, and rooting.
Click to expand...
Click to collapse
Sounds to me like you have one of those P2C72 which were flashed using the fastboot factory flasher with the P2a42 images. Leaving out the modem partition to make it multilingual. That Chinese shops, like to do to sell the Chinese version on the international market.
To answer your question, it depends all what your target is.
If you simply want to upgrade to stock Nougat.
You don't need to unlock the Bootloader.
As the fastboot factory flasher images are signed.
If you want root. That's another story.
Dump me your partition table details and I will see to build an TWRP that works for the P2C72.
I haven't read yet through all the threads and I'm not sure if the P2a42 TWRP works the P2c72.
It was probably already tested by users and
It should work but I think I saw at least one discrepancy in partition sizes when comparing the rawprogram0.xml file of both devices.
---------- Post added at 08:47 AM ---------- Previous post was at 08:42 AM ----------
Siva Mk said:
If you're asking about the 14 days wait then yes
---------- Post added at 03:53 AM ---------- Previous post was at 03:50 AM ----------
The firehose you mentioned is similar to that if Redmi note 3(I think). In that case miflash should work. Further more the XML file name maybe same but the file content maybe different. Don't have much knowledge on this. But have used all these.
Click to expand...
Click to collapse
I think you meant Redmi Note 4(x) codename mido. But like said above. To my knowledge the big change in the firehose's is they are all signed now.
I'm thinking it's due to the Chinese shops doing what I explained above and the company asking Snapdragon a way to prevent it. And we have what we have to today, signed firehose's that can only be used with the appropriate devices.
---------- Post added at 08:50 AM ---------- Previous post was at 08:47 AM ----------
Wmateria said:
No i'm asking is it safe to go through all that process.. cause it seems multiple people had had problems unlocking and flashing and end up bricking their phones. Oh and which TWRP to flash via ADB the 3.0.3-0 or the 3.1.0-3? I see that the 3.0.3.0 does not conform with the P2c72.. am trying to flash Lineage 13 that's why i ask about the 3.0.3-0.
Click to expand...
Click to collapse
Every TWRP outside my official TWRP thread is not based and compiled on sources but was "ported". Which introduces unknown issues. Stick with the TWRP's I made available. But like said. Dump me your partition table and in spare time I will build an P2C72 TWRP.

Hi celoxocis
Thank you for helping out!
My device is P2a42.
I have the NON-HLOS.bin which is included in the firmware file.
Just so i understand it correctly.
1) Update the TWRP recovery from https://forum.xda-developers.com/le...covery-unofficial-twrp-lenovo-p2-3-0-t3533659.
2) Rename the NON-HLOS.bin to NON-HLOS.img.
3) Flash it by using the "flash image" section.
4) Select the modem partation and boot into system.
I have an an Unlocked bootloader, when i tried previously to flash from fastboot using " fastboot flash modem NON-HLOS.bin " i used to get an error
writing 'modem'...
FAILED (remote: Do not allow to flash Bootloader image on Unlock device)
Would TWRP work flashing to modem partation?
celoxocis said:
I can't remember out of my head but I think the NON-HLOS.bin is included in the factory image package. It would be the one responsible for the modem.
Before you replace the partition make sure your device is the P2a42 or P2C72 and use appropriate modem image. You can't simply exchange them.
If exchanged wrongly. It could end up in:
A: bootloop
B: what you are describing. Unable to connect to a network.
My official TWRP can be used to flash that partition without entering fastboot.
Simply rename that .bin into *.img and select "install" browse the folder located and select "flash image". Select the image and select the modem partition, boot into system.
Click to expand...
Click to collapse

sisqin1 said:
Hi celoxocis
Thank you for helping out!
My device is P2a42.
I have the NON-HLOS.bin which is included in the firmware file.
Click to expand...
Click to collapse
That is correct.
However make sure your device is an P2c72 and use the proper NON-HLOS.bin file.
Best way would be to find the stock rom for the P2c72 and extract the zip file containing the right NON-HLOS.bin file.
As i stated I'm not sure the fastboot factory flasher package containts the NON-HLOS.bin file for the P2c72 its probably the one for the P2a42.

Thank you celoxocis,
My device is P2a42 which i have not changed or altered, do i still need to find the NON-HLOS.bin for P2c72 and flash it.
Or do i flash the NON-HLOS.bin for P2a42.
celoxocis said:
That is correct.
However make sure your device is an P2c72 and use the proper NON-HLOS.bin file.
Best way would be to find the stock rom for the P2c72 and extract the zip file containing the right NON-HLOS.bin file.
As i stated I'm not sure the fastboot factory flasher package containts the NON-HLOS.bin file for the P2c72 its probably the one for the P2a42.
Click to expand...
Click to collapse

sisqin1 said:
Thank you celoxocis,
My device is P2a42 which i have not changed or altered, do i still need to find the NON-HLOS.bin for P2c72 and flash it.
Or do i flash the NON-HLOS.bin for P2a42.
Click to expand...
Click to collapse
If you haven't changed and altered anything. Then there is no need to flash the modem partition.
The whole topic is about reviving a device?

I had used these commands and i was not able to make or receive calls.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
I will try flashing the image and report back.
celoxocis said:
If you haven't changed and altered anything. Then there is no need to flash the modem partition.
The whole topic is about reviving a device?
Click to expand...
Click to collapse

sisqin1 said:
I had used these commands and i was not able to make or receive calls.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
I will try flashing the image and report back.
Click to expand...
Click to collapse
I thought you said you didn't alter the device?
What's the sources of that NON-HLOS you flashed?
Make sure it is the right one.
It's simple.
P2A42 device must match NON-HLOS for P2a42
P2C72 device must match NON-HLOS for P2C72
You can NOT exchange them.

By alter I meant changing / flashing different firmware.
I have only unlocked the bootloader and downgraded to MM.
That's when I lost the network connectivity.
I ran the commands above to see if it resolves the issue and it did not.
I have the NON-HLOS for P2a42 which I downloaded. Bi when I try to flash using fast boot I get error.

Well, the only person i asked at the time that succesfully flashed roms was @Billytromp.. when he first attempted to flash DU Rom.. it didn't work and the LED flashed blue.. and then when flashed LOS 13.. it took 2 attempts for it to finally work. Um.. i dont think i can give you what you are asking since i have not dared to unlock and root my phone. Perhaps ask him since he is the only person i knew that has a P2c72.

hard bricked, need blankflash for z2 force

hello guys, my T-mobile z2force was bricked now, and when I connect to my pc , it only show it is qcom 9008, seems that I need blankflash to save my phone , so does anyone who can find it, please help me , thx .

18712886438 said:
hello guys, my T-mobile z2force was bricked now, and when I connect to my pc , it only show it is qcom 9008, seems that I need blankflash to save my phone , so does anyone who can find it, please help me , thx .
Click to expand...
Click to collapse
Can I ask how this happened?
On Moto Z we opened a very useful thread listing all dangerous operations to avoid others doing same errors/operations... :fingers-crossed:

enetec said:
Can I ask how this happened?
On Moto Z we opened a very useful thread listing all dangerous operations to avoid others doing same errors/operations... :fingers-crossed:
Click to expand...
Click to collapse
I did something wrong with some partitions like tz, and then it goes to 9008 now, can u give me the link for the thread?

18712886438 said:
I did something wrong with some partitions like tz, and then it goes to 9008 now, can u give me the link for the thread?
Click to expand...
Click to collapse
This is the thread about "brick experiences": https://forum.xda-developers.com/moto-z/how-to/how-bricked-share-experiences-t3515167
and this are about blankflash: https://forum.xda-developers.com/moto-z/how-to/guide-how-to-unbrick-moto-z-hardbricked-t3590133 and https://forum.xda-developers.com/moto-z/help/moto-z-bricked-qdloader9008-t3524448
PLEASE NOTE they are for Moto Z & not for Z2 Force, but maybe you could still find something useful...

enetec said:
This is the thread about "brick experiences": https://forum.xda-developers.com/moto-z/how-to/how-bricked-share-experiences-t3515167
and this are about blankflash: https://forum.xda-developers.com/moto-z/how-to/guide-how-to-unbrick-moto-z-hardbricked-t3590133 and https://forum.xda-developers.com/moto-z/help/moto-z-bricked-qdloader9008-t3524448
PLEASE NOTE they are for Moto Z & not for Z2 Force, but maybe you could fstill fnd something useful...
Click to expand...
Click to collapse
yes, thx

guys i tried blank flash oreo on mine bricked tmobile moto z2 force and it isnt working, any help would be great on this , thanks.. and also i have tried many blank flashes some for even other moto phone models none worked so far.. one or two of them got really close the oreo one did but failed at last part... tried about hundred times and yes i even tried holding down power and volume button with no success it didnt work it did though recognize the phone but still failed trying to boot or flash it though... seems to me it needs either up to date or just different blank flash it seems, but i dont know that for sure...

SmartPhoneDeveloper said:
guys i tried blank flash oreo on mine bricked tmobile moto z2 force and it isnt working, any help would be great on this , thanks.. and also i have tried many blank flashes some for even other moto phone models none worked so far.. one or two of them got really close the oreo one did but failed at last part... tried about hundred times and yes i even tried holding down power and volume button with no success it didnt work it did though recognize the phone but still failed trying to boot or flash it though... seems to me it needs either up to date or just different blank flash it seems, but i dont know that for sure...
Click to expand...
Click to collapse
I started a thread literally 2 threads down from yours on how to fix this lol.https://forum.xda-developers.com/z2-force/help/gotta-super-slim-brick-t3798403

bricked moto z2 force tmobile
mookiexl said:
I started a thread literally 2 threads down from yours on how to fix this lol.https://forum.xda-developers.com/z2-force/help/gotta-super-slim-brick-t3798403
Click to expand...
Click to collapse
tried both them files, the first one seems to almost work but says failed to read file after it says waiting to read firehose or something like that during the process, i can post the pics of what it says but need to know how to post them?...
---------- Post added at 04:17 PM ---------- Previous post was at 03:51 PM ----------
mookiexl said:
I started a thread literally 2 threads down from yours on how to fix this lol.https://forum.xda-developers.com/z2-force/help/gotta-super-slim-brick-t3798403
Click to expand...
Click to collapse
these are what it says on pics hope pics can be viewed??.. let me know thanks..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

SmartPhoneDeveloper said:
tried both them files, the first one seems to almost work but says failed to read file after it says waiting to read firehose or something like that during the process, i can post the pics of what it says but need to know how to post them?...
---------- Post added at 04:17 PM ---------- Previous post was at 03:51 PM ----------
these are what it says on pics hope pics can be viewed??.. let me know thanks..
Click to expand...
Click to collapse
Steps I also did uninstalled Motorola drivers and Disable Driver Signature Enforcement(google it). From reading different unbrick scenarios it seems that the desktop may need the perfect operating environment to run the commands of the blank flash.

FINALLY UNBRICKED moto z2 force tmobile !!
:highfive:
mookiexl said:
Steps I also did uninstalled Motorola drivers and Disable Driver Signature Enforcement(google it). From reading different unbrick scenarios it seems that the desktop may need the perfect operating environment to run the commands of the blank flash.
Click to expand...
Click to collapse
gonna try your steps just sec...
---------- Post added at 06:46 AM ---------- Previous post was at 05:58 AM ----------
mookiexl said:
Steps I also did uninstalled Motorola drivers and Disable Driver Signature Enforcement(google it). From reading different unbrick scenarios it seems that the desktop may need the perfect operating environment to run the commands of the blank flash.
Click to expand...
Click to collapse
your awesome mookiexl a genius mate!!, you saved my new z2 force thank gosh
thought it would be never working again , your steps worked exactly as you said..
guys if anyone gets in a tight position like i was and has a moto z2 force tmobile -(xt1789-04 model)- and flashed TWRP then tried to open slot b and then bricked your moto z2 force and now it wont boot just black screen , follow mookiexl steps it works great..
1: uninstall all moto drivers -(dont restart pc yet)
2: Disable Driver Enforcement in pc settings-(google it)
3: then after pc restart now in desktop screen connect phone to pc with usb
then click blank-flash.. there could be something i left out but i dont think i did
let me know if i missed something guys, and as always thank you so much!!..
btw mookixl, here are my results to show it finally flashed properly after you told me to proceed to next step(s) uninstall moto drivers and then disable driver enforcement then try again..

SmartPhoneDeveloper said:
:highfive:
gonna try your steps just sec...
---------- Post added at 06:46 AM ---------- Previous post was at 05:58 AM ----------
your awesome mookiexl a genius mate!!, you saved my new z2 force thank gosh
thought it would be never working again , your steps worked exactly as you said..
guys if anyone gets in a tight position like i was and has a moto z2 force tmobile -(xt1789-04 model)- and flashed TWRP then tried to open slot b and then bricked your moto z2 force and now it wont boot just black screen , follow mookiexl steps it works great..
1: uninstall all moto drivers -(dont restart pc yet)
2: Disable Driver Enforcement in pc settings-(google it)
3: then after pc restart now in desktop screen connect phone to pc with usb
then click blank-flash.. there could be something i left out but i dont think i did
let me know if i missed something guys, and as always thank you so much!!..
btw mookixl, here are my results to show it finally flashed properly after you told me to proceed to next step(s) uninstall moto drivers and then disable driver enforcement then try again..
Click to expand...
Click to collapse
Hell yeahz brother. Glad to be of assistance because I couldn't get any lol.

mookiexl said:
Hell yeahz brother. Glad to be of assistance because I couldn't get any lol.
Click to expand...
Click to collapse
sorry to hear that brother and i really appreciate your help of this matter so far,
but there are other issues now:
okay, guys there's alot of issue(s) going on with our device
and yes i know as we all do these are the risks we undertake
by unlocking our bootloader blah blah blah.. lol
anyways heres whats going on with mine okay
so much confusion and not really where to start, okay first off- what i did
is this:
i unlocked my bootloader on my moto z2 force tmobile-(xt1789-04), ]
did a flash boot twrp img it worked and all
and then read somewhere by a xda member on
one of the forums on said to try to go into or open
slot b on our moto z2 force and okay i did that and BAM! guess what!!..
it of course bricked my phone , this is where the fun began-(not really),
1: finally was able to unbrick it using a blank flash method one
believe it was an nougat blank flash one, and then when it got to the bootloader
i noticed it was a verizon bootloader smack dead on top.. i WAS SHOCKED!!
because we all know how verizon does our phones -locks the bootloader and stuff
verizon anything is the last thing i want to see on my device!!, one
i want to know how to get this off if possible and second
also been noticing that every time i try to
flash roms when phone boots up it just keeps going into bootloops
and also every since my device bricked and
i unbricked it it hasnt been same since because
it has verizon bootloader on it and two when i start
it up phone boots really fast now too fast and also
it doesnt vibrate no more like it used to before intially bricking it..
also anyone remembers or knows of motrola rom flashing and stuff
knows that there are some you can flash a global or usa unlocked version
of that rom and then it makes it fully global unlocked without
asking for a sim unlock code.. well i was in for a shocker , i thought
i was going to be do this with our motoz2 force turns out i not only
cant do this far as i know yet.. and two it seems alot more complicated
of the flashing methods to get stuff working properly must be
due to the dual partitions or something unless im just doing the flashall thing
wrong?.. and the flashall methods i read somewhere on one of the forums
where they was talking about the flashall* method and i tried
one of the oreoflashall methods but i noticed that
the *.bat* file it doesnt include the sparschunk files??.. are they needed!?..,
and if not needed then what exactly are they for because i have the tmobile
version and the sparschunk files are in there along with all other flash
files thats noted inside of the orginal flashfile.xml... any help guys would
be appreciated!!.. because as of the moment for over 5 days now im still stuck on
bootloader because i tried everything i can think of and its a no go
but i believe my flashing methods must be wrong or something...

In the moto unbricking forum it is mentioned that sometimes trying to go back to stock after a brick is troublesome. They suggest flashing a custom rom after unbricking then flashing an official stock. The reason it bootloops after flashing is probably because you didn't fastboot -w
I would flash AOSiP, and make sure you use the prep zip for TMO and follow the guide to the 'T' The prep zip will make sure you have an oreo base on both slots so it doesn't fall over on itself. If all is well and you get AOSiP up and going and you feel like returning to stock. Just go here and follow this guide.

UNBRICKED , but stuck in bootloader and now showing verizon bootloader!!
41rw4lk said:
In the moto unbricking forum it is mentioned that sometimes trying to go back to stock after a brick is troublesome. They suggest flashing a custom rom after unbricking then flashing an official stock. The reason it bootloops after flashing is probably because you didn't fastboot -w
I would flash AOSiP, and make sure you use the prep zip for TMO and follow the guide to the 'T' The prep zip will make sure you have an oreo base on both slots so it doesn't fall over on itself. If all is well and you get AOSiP up and going and you feel like returning to stock. Just go here and follow this guide.
Click to expand...
Click to collapse
okay will try, but note: i have tried this prior to bricking before,but that was before my bricking, it was throwing me a error 255 whatever that is, matter of fact never could get any custom rom working but also i do have an additional working perfect order untouched motoz2 force as well if that makes a difference couldnt i just use the twrp backup of the original to flash back the original rom?.. my original bootloader was oreo firmware also if that helps with these problems im having?... and also whats prep-zip?.
never heard that method?.. is that mean flashing via twrp custom recovery?..
and thanks for the help i really appreciate this bro... and also if you read the part where i said these problems trying to flash anything was having same ones even before bricking
my device,.. it just giving me more issues in a sense now...

SmartPhoneDeveloper said:
okay will try, but note: i have tried this prior to bricking before,but that was before my bricking, it was throwing me a error 255 whatever that is, matter of fact never could get any custom rom working but also i do have an additional working perfect order untouched motoz2 force as well if that makes a difference couldnt i just use the twrp backup of the original to flash back the original rom?.. my original bootloader was oreo firmware also if that helps with these problems im having?... and also whats prep-zip?.
never heard that method?.. is that mean flashing via twrp custom recovery?..
and thanks for the help i really appreciate this bro... and also if you read the part where i said these problems trying to flash anything was having same ones even before bricking
my device,.. it just giving me more issues in a sense now...
Click to expand...
Click to collapse
Twrp and backups for our phone at least isn't solid, maybe to restore some data, but other than that there have been issues. The prep zip, that's what I call it at least is in the 2nd comment in the AOSiP thread. It's a base package that flashes to both slots, its intent was to prevent trouble should Nougat be on the other slot. Either way, I would flash it. It is flashed via a flashall.bat inside the zip, no need for twrp yet. Just follow the guide in the OP of the AOSiP thread. That should at least get AOSiP up and running. If you don't like it, or if things are off and you want to return to stock, just follow the guide in the return to stock guide. Don't worry about anything else right at the moment, just AOSiP. If you have trouble, post it.

trying aosip custom rom now on bootloader stuck motoz2 force
41rw4lk said:
Twrp and backups for our phone at least isn't solid, maybe to restore some data, but other than that there have been issues. The prep zip, that's what I call it at least is in the 2nd comment in the AOSiP thread. It's a base package that flashes to both slots, its intent was to prevent trouble should Nougat be on the other slot. Either way, I would flash it. It is flashed via a flashall.bat inside the zip, no need for twrp yet. Just follow the guide in the OP of the AOSiP thread. That should at least get AOSiP up and running. If you don't like it, or if things are off and you want to return to stock, just follow the guide in the return to stock guide. Don't worry about anything else right at the moment, just AOSiP. If you have trouble, post it.
Click to expand...
Click to collapse
okay will do, and thanks for help on this matter mate, im trying it now but
also i forgot to mention on how to flash properly twrp on our device?..
as i couldnt even get twrp to boot up now but it will flash on fastboot at least it shows it flashing and stuff, but when it goes to restart on boot up
it just keeps restarting bootloop, also i think i may be flashing it wrong or something and is moto drivers needed or not?..

SmartPhoneDeveloper said:
okay will do, and thanks for help on this matter mate, im trying it now but
also i forgot to mention on how to flash properly twrp on our device?..
as i couldnt even get twrp to boot up now but it will flash on fastboot at least it shows it flashing and stuff, but when it goes to restart on boot up
it just keeps restarting bootloop, also i think i may be flashing it wrong or something and is moto drivers needed or not?..
Click to expand...
Click to collapse
Make sure you're using the 3.2.1-1.img and 3.2.1-1.zip from here
Follow the AOSiP guide and when it's time to BOOT twrp just
Code:
fastboot boot (drag n drop twrp.IMG here)
Once booted into twrp, flash the twrp.ZIP after the install do a reboot to recovery inside twrp to reboot back into it and follow along in the guide.
You can't flash twrp through fastboot with our phone because technically it doesn't have a recovery partition, it's built into boot. So just follow what I posted which is what the AOSiP guide says as well.

SmartPhoneDeveloper said:
sorry to hear that brother and i really appreciate your help of this matter so far,
but there are other issues now:
okay, guys there's alot of issue(s) going on with our device
and yes i know as we all do these are the risks we undertake
by unlocking our bootloader blah blah blah.. lol
anyways heres whats going on with mine okay
so much confusion and not really where to start, okay first off- what i did
is this:
i unlocked my bootloader on my moto z2 force tmobile-(xt1789-04), ]
did a flash boot twrp img it worked and all
and then read somewhere by a xda member on
one of the forums on said to try to go into or open
slot b on our moto z2 force and okay i did that and BAM! guess what!!..
it of course bricked my phone , this is where the fun began-(not really),
1: finally was able to unbrick it using a blank flash method one
believe it was an nougat blank flash one, and then when it got to the bootloader
i noticed it was a verizon bootloader smack dead on top.. i WAS SHOCKED!!
because we all know how verizon does our phones -locks the bootloader and stuff
verizon anything is the last thing i want to see on my device!!, one
i want to know how to get this off if possible and second
also been noticing that every time i try to
flash roms when phone boots up it just keeps going into bootloops
and also every since my device bricked and
i unbricked it it hasnt been same since because
it has verizon bootloader on it and two when i start
it up phone boots really fast now too fast and also
it doesnt vibrate no more like it used to before intially bricking it..
also anyone remembers or knows of motrola rom flashing and stuff
knows that there are some you can flash a global or usa unlocked version
of that rom and then it makes it fully global unlocked without
asking for a sim unlock code.. well i was in for a shocker , i thought
i was going to be do this with our motoz2 force turns out i not only
cant do this far as i know yet.. and two it seems alot more complicated
of the flashing methods to get stuff working properly must be
due to the dual partitions or something unless im just doing the flashall thing
wrong?.. and the flashall methods i read somewhere on one of the forums
where they was talking about the flashall* method and i tried
one of the oreoflashall methods but i noticed that
the *.bat* file it doesnt include the sparschunk files??.. are they needed!?..,
and if not needed then what exactly are they for because i have the tmobile
version and the sparschunk files are in there along with all other flash
files thats noted inside of the orginal flashfile.xml... any help guys would
be appreciated!!.. because as of the moment for over 5 days now im still stuck on
bootloader because i tried everything i can think of and its a no go
but i believe my flashing methods must be wrong or something...
Click to expand...
Click to collapse
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783 Follow guide. New T-Mobile firmware is linked and official from the Motorola firmware Team. The new update was released two days ago in flash all format. There is a utilities zip you can use to flash with. Just follow OP and download from second post. You'll be golden and back to stock.

UNBRICKED , but stuck in bootloader, trying other methods thanks to members!
41rw4lk said:
Make sure you're using the 3.2.1-1.img and 3.2.1-1.zip from here
Follow the AOSiP guide and when it's time to BOOT twrp just
Code:
fastboot boot (drag n drop twrp.IMG here)
Once booted into twrp, flash the twrp.ZIP after the install do a reboot to recovery inside twrp to reboot back into it and follow along in the guide.
You can't flash twrp through fastboot with our phone because technically it doesn't have a recovery partition, it's built into boot. So just follow what I posted which is what the AOSiP guide says as well.
Click to expand...
Click to collapse
going to try these methods so far i believe i was using older methods that was non-relevant or was maybe outdated for this, i was originally on oreo firmware before i flashed anything, it was oreo stock on mine as i heard some have 7.1.1 stock or so.. so maybe i just need to try flash oreo firmware since that was originally the firmware on mine?.. and also i really appreciate the help on this guys.. trying it now just sec.. i tried also to flash stock nougat firmware but no success?.., can we not downgrade as i was reading on some post about z2 force our phones and they said you could downgrade, but like i said maybe just my flash methods or .bat files are wrong or so?.. also btw i read somewhere that people that was on oreo firmware couldnt do a flashall method or something like that anyone can either confirm this or wrong it?....
---------- Post added at 11:05 AM ---------- Previous post was at 10:44 AM ----------
Uzephi said:
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783 Follow guide. New T-Mobile firmware is linked and official from the Motorola firmware Team. The new update was released two days ago in flash all format. There is a utilities zip you can use to flash with. Just follow OP and download from second post. You'll be golden and back to stock.
Click to expand...
Click to collapse
going to try this now mate, and thanks for all the help guys mookiexl, airwalk, and Uzephi on this matter for our great device, oh by the way guys i have been working on some things for our device for while now, while trying to get out of bootloader , while i was waiting to do a stock recover and such , but no worries i need some testers on this matter i tried two of them to see and they did seem to show on screen and no crashes or nothing so far, so it seems it's okay so far ..-(i have three variants of this splash screen to remove unlocked screen for replacing it because it can be kinda of pesky to some) - the commands are fastboot flash logo_a (the logo.bin here)..
EDIT!:
DISCLAIMER!!:
They do indeed work, But as i said-- I MANUALLY FLASHED THEM!-- THEY WORKED FOR ME NO PROBLEMS, BUT IF ON DIFFERENT FIRMWARE
PLEASE TEST AND LET ME KNOW I WASNT ON CUSTOM FIRMWARE SO ANY OTHERS ON THEM LET ME or other experienced members on this matter KNOW AND TRY TO SEE IF WORKS I WAS JUST ON BOOTLOADER AND IT WORKED SO FAR I TRIED ALL THREE VARIANTS...
links are below at the --BOTTOM OF THE POST-- also i almost forgot i ALSO INCLUDED TWRP RECOVERY FLASHABLE ZIP(s) file(s) for the logo boot splash screens for anyone only wanting to flash or has issues with fastboot for whatever reason to flash them in twrp instead they should work but if any issue(s) let us know thanks!!..
the way i did this was below, it worked for me both ways as well as in just:
**fastboot flash logo logo.bin** -(without quotes) also i did try it worked but as i say it may be different depending on if your either nougat or oreo users..
(guys side note!!: not 100% sure if logo_a and logo_b may be needed -(this is why i said i need some testers, so please be easy on me, im still learning myself, i did make these from scratch)
commands are:
fastboot flash logo_a (logo.bin here)
fastboot flash logo_b (logo.bin here)
note#2!: i heard somewhere on a xda post that oreo users may or may not be able to do a flashall method, this is why i say do it manually, correct me as needed please!, because as i said im learning myself in the process , but i learn really fast so no worries!
oreo users: to be safe side of things, do command below manually:
fastboot flash logo_a (logo.bin here)
fastboot flash logo_b (logo.bin here)
check out and see if you guys like the logo boot screen pics of ones i made
if no one likes these then i will happily remove them, and as always thanks guys for all the help with me on these matter(s)...
and also i have another question too about something -(this is seperate upon these things )-one more thing its about Sparsechunk files** as i noticed in our flashall.bat files thats provided from others, its not in there i have tmobile version of our variant and it does have sparsechunk files in there 0-3 of them check out my file flashall_main.bat file please someone and just right click this one i made by scratch and been using maybe reason why it hasnt been working for me and go to option 8 is what i been using for flashall.bat method- for the flashall method to flash on our motoz2 force, and let me know if its correct or no, also btw you know how its have dual partition on our device now, well i need to know of my flashll-main.bat file i will provide below in link if its right on the flashall methods on how to flash it on our device, notice thats theres system_a system_b but in sparsechunk files its like this below:
this is my part of it in my file(s) of my flashall-main.bat file:
option 8 only!!! as i noted others dont pay no attention to them was done for other model(s)
nash i made for option 8 on menu of this flashall
but i need help to see if it was done right
need to know if sparsechunk file(s) since its orginally system_b.img
would it need to be like system_a system_b then or like this:
_a _a
_a _b
_b _a
_b _b
????? see what i mean since we have dual partitions but since it is originally system_b
as i was saying i may not need to change it thats why im asking and as always thanks guys for this help
________________________________________________________
:flashStockR-ORIG-Custom#1-2-FLASHFILE.XML
cls
echo.
echo You will flash a Stock or Custom Stock Rom
echo The Stock or Custom Stock Rom Folder needs Used or Could Be Set within your ADB-Folder or Outside of ADB-Folder As Well Either Should Be Fine
echo.
pause
echo.
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader_a bootloader.img
fastboot flash bootloader_b bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash modem_b NON-HLOS.bin
fastboot flash fsg_b fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth_a BTFM.bin
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system_b.img_sparsechunk.0
fastboot flash system_a system_b.img_sparsechunk.1
fastboot flash system_a system_b.img_sparsechunk.2
fastboot flash system_a system_b.img_sparsechunk.3
fastboot flash oem_a oem.img
fastboot flash bluetooth_b BTFM.bin
fastboot flash dsp_b adspso.bin
fastboot flash logo_b logo.bin
fastboot flash boot_b boot.img
fastboot flash system_b system.img_sparsechunk.0
fastboot flash system_b system.img_sparsechunk.1
fastboot flash system_b system.img_sparsechunk.2
fastboot flash system_b system.img_sparsechunk.3
fastboot flash system_b system.img_sparsechunk.4
fastboot flash system_b system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash system_b system_b.img_sparsechunk.3
fastboot flash oem_b oem.img
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot -w
fastboot --set-active=other
fastboot reboot-bootloader
echo.
echo Done!
pause>nul
cls
goto menu
________________________________________________________

This worked, Disabling driver enforcement and uninstall Motorola drivers via programs and features! THANKS!!

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?

Question [Question] Who has rooted TMOBILE 9Pro Stock ROM

I understand I can convert to EU.... However, I don't wish to do that. I just want to root my stock TMOBILE ROM.
My sim is unlocked and I have the unlock.bin from OnePlus for my phone. For anyone who has rooted TMOBILE stock ROM, which boot.img did you patch? I've read that AA boot image can work, but no firsthand accounts confirming this.
Ideally, I'd like to use my own boot.img but I can't find a tutorial or guide anywhere advising how to obtain my boot.img without root.
Thanks!

use AA boot img, but recommend unlocking Bootloader and backing up your tmo modem a/b imgs

How to guide
[TMO] 9 PRO MODEM RETENTION/DATA FIX
----- With the release of OOS13, the modem issue no longer exist. Thank you all for the support & help with this unfortunate issue, we had to endure.... ----- EXPLICITLY FOR TMOBILE 9 PRO (I'm not responsible for your failure to read or...
forum.xda-developers.com

Use partitions backup (app) to backup the existing TMO Firmware first and copy your files to a pc before you do anything. As with any flashing you run the risk of wiping your info and stored files..

galaxyuser88 said:
Use partition magic to backup the existing TMO Firmware first and copy your files to a pc before you do anything. As with any flashing you run the risk of wiping your info and stored files..
Click to expand...
Click to collapse
What is partition magic? An app? Software?

Pain-N-Panic said:
What is partition magic? An app? Software?
Click to expand...
Click to collapse
Sorry meant to say partitions backup. Which is an app.
Partitions Backup & Restore - Apps on Google Play
Backup your important partitions to avoid any data or IMEI corruption
play.google.com

Thank you... unfortunately partition backup requires root. So I can't back anything up until I unlock and root....which using the AA boot image to root kinda freaks me out

Pain-N-Panic said:
Thank you... unfortunately partition backup requires root. So I can't back anything up until I unlock and root....which using the AA boot image to root kinda freaks me out
Click to expand...
Click to collapse
It is understandable to be freaked out,. But if you follow the direction letter for letter then you should be fine.
Also good rule of thumb is make sure you have all the drivers and software loaded on your pc, then make sure your pc and phone can talk in adb and fastboot before you start to flash your phone.
I have rooted my stock tmo rom with aa and all good. Of course I went even further and installed the EU version on my tmo bought 9Pro..

galaxyuser88 said:
It is understandable to be freaked out,. But if you follow the direction letter for letter then you should be fine.
Also good rule of thumb is make sure you have all the drivers and software loaded on your pc, then make sure your pc and phone can talk in adb and fastboot before you start to flash your phone.
I have rooted my stock tmo rom with aa and all good. Of course I went even further and installed the EU version on my tmo bought 9Pro..
Click to expand...
Click to collapse
Yep, confirmed, 9pro and my computer can talk. The whole MSM thing is what is worrying me. In the MSM tool, it says it is the TMO -EU MSM. So, once it does it's thing and flashes it all, it should wipe the phone, it would be on the EU rom?
From there, I would need to follow the steps, unlock BL, flash modems, and then download oxygen updater to be able to locally download updates and install?