Develop Bugs

Addison_Row_Cust

Bought my Z Play used and have been really enjoying it! Phone came with TWRP + Root. After the November update came out, I flashed everything except baseband and modem, since I didn't want to lose my imei and couldn't find factory images for my device. I'd really like to flash back to 100% stock so I can relock my bootloader, use Android pay, and accept the upcoming nougat update once it arrives.
Looked through all of the factory images I could find on XDA and did a lot of googling, no luck.

Same situation as you are. I can't find that specific ROM.

Lenovo have not released signed images that you can flash and lock your bootloader with. Your device will always have the software flag : modified in the bootloader. Your best option for Android pay is for Alberto97 to include the SafetyNet kernel flag in LOS 14.1

Really_Rekt said:
Lenovo have not released signed images that you can flash and lock your bootloader with. Your device will always have the software flag : modified in the bootloader. Your best option for Android pay is for Alberto97 to include the SafetyNet kernel flag in LOS 14.1
Click to expand...
Click to collapse
Really, I care more about being able to take the upcoming nougat OTA, but this is good info, thank you!

xxBrun0xx said:
Really, I care more about being able to take the upcoming nougat OTA, but this is good info, thank you!
Click to expand...
Click to collapse
If I'm not mistaken, you should still be able to take upcoming OTA's even with an unlocked bootloader.
As long as you have stock recovery + un-root, you should be good in theory.

luciddreamin92 said:
If I'm not mistaken, you should still be able to take upcoming OTA's even with an unlocked bootloader.
As long as you have stock recovery + un-root, you should be good in theory.
Click to expand...
Click to collapse
True, but my baseband currently doesn't match anything else. To get to the November update, I flashed everything except modem from the latest USA factory ROM. Guess I can just do the same thing once someone posts images for nougat.

xxBrun0xx said:
True, but my baseband currently doesn't match anything else. To get to the November update, I flashed everything except modem from the latest USA factory ROM. Guess I can just do the same thing once someone posts images for nougat.
Click to expand...
Click to collapse
Hey guys, to prevent the loss of your precious data (apks, settings and etc), and "enable" ota on your devices, go to Twrp, wipe System, cache and dalvik cache.
After this, flash the firmware of your device via fastboot with the commands above:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
After that, your phone should be able to install ota's.
Cheers!

W3ND31 said:
Hey guys, to prevent the loss of your precious data (apks, settings and etc), and "enable" ota on your devices, go to Twrp, wipe System, cache and dalvik cache.
After this, flash the firmware of your device via fastboot with the commands above:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
After that, your phone should be able to install ota's.
Cheers!
Click to expand...
Click to collapse
Only if there is a factory image available for your device. Otherwise the OTA is going to brick your phone (OTA updates bootloader and modem, wrong modem will break radios, not sure if bootloader is region specific? If so, taking out of region OTA would hard brick you.)

xxBrun0xx said:
Only if there is a factory image available for your device. Otherwise the OTA is going to brick your phone (OTA updates bootloader and modem, wrong modem will break radios, not sure if bootloader is region specific? If so, taking out of region OTA would hard brick you.)
Click to expand...
Click to collapse
Nice addon!
Thx!

Update to this: spoke with a Level 2 Motorola Representative over the weekend. He did not seem to know anything about fastboot or TWRP or bootloader unlock vs sim unlock. I was pretty disappointed, Moto support has been excellent in past experience. He looked up the device by IMEI and told me it was unlocked US version, but had no idea what I was asking after almost an hour of explanation. The Level 1 tech I spoke to spoke pretty broken english. It's possible the baseband for RETUS is ROW_CUST, but I'm not brave enough to try flashing modem and boot.img.
If you're in the same boat, I'd recommend waiting until someone with a RETUS can confirm their baseband.

xxBrun0xx said:
Update to this: spoke with a Level 2 Motorola Representative over the weekend. He did not seem to know anything about fastboot or TWRP or bootloader unlock vs sim unlock. I was pretty disappointed, Moto support has been excellent in past experience. He looked up the device by IMEI and told me it was unlocked US version, but had no idea what I was asking after almost an hour of explanation. The Level 1 tech I spoke to spoke pretty broken english. It's possible the baseband for RETUS is ROW_CUST, but I'm not brave enough to try flashing modem and boot.img.
If you're in the same boat, I'd recommend waiting until someone with a RETUS can confirm their baseband.
Click to expand...
Click to collapse
I would avoid at all cost flashing any modem, bootloader or baseband related bin file. You can freely flash the sparse chunks and boot.img to your heart's content.
Sent from my XT1635-02 using XDA-Developers Legacy app

xxBrun0xx said:
Update to this: spoke with a Level 2 Motorola Representative over the weekend. He did not seem to know anything about fastboot or TWRP or bootloader unlock vs sim unlock. I was pretty disappointed, Moto support has been excellent in past experience. He looked up the device by IMEI and told me it was unlocked US version, but had no idea what I was asking after almost an hour of explanation. The Level 1 tech I spoke to spoke pretty broken english. It's possible the baseband for RETUS is ROW_CUST, but I'm not brave enough to try flashing modem and boot.img.
If you're in the same boat, I'd recommend waiting until someone with a RETUS can confirm their baseband.
Click to expand...
Click to collapse
I'm on RETUS. Baseband is Addison_RETUS_Cust. No ROW.

dandrumheller said:
I'm on RETUS. Baseband is Addison_RETUS_Cust. No ROW.
Click to expand...
Click to collapse
The plot thickens

How to get back to original STOCK ROM?

Hello,
i am currently running Dedrak Essential 1.3.0 which is a kind of 7.0 Stock ROM. But i want to get the orginal Moto-Stock. How to get that? I know there ist a Service Image of 6.0 and i had to do some fastboot/mfastboot actions. But i am not really sure if would this work or brick my device.
Can anyone give me an advice?
thanks
Peter

Just use RSD lite and flash original FW for youe device.
Here you can get 7.1.1 fully stock ROM (retin or retus - I don`t sure)
I flash it to my XT1635-03 and it works just perfect.
P.S. If you have issues with RSD flashing - just use fastboot with the next commands:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot reboot

acutally i need reteu. Well i will look for it.
Thanks so far

Keep in mind if you already upgraded your bootloader from the official July Patch and patch you'll hard brick your Moto Z play if you upgrade and downgrade. I'd advise you to flash the ROM and not the actual firmware.

i dont have that july patch. Dedrak was still on January.... so its 7.0 and it this was also the las official update i got changed to dedrak.
So it should work.

Dchoi229 said:
Keep in mind if you already upgraded your bootloader from the official July Patch and patch you'll hard brick your Moto Z play if you upgrade and downgrade. I'd advise you to flash the ROM and not the actual firmware.
Click to expand...
Click to collapse
Please explain a little bit more how is it possible. As far as I understand it should be as following
When I get phone from store it will look like:
Code:
F1: STOCK FIRMWARE V.1
F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1
┗━━━ BOOT ━━━┛┗━━━━ RECOVERY ━━━━┛┗━━━━━━━━━━━ SYSTEM ━━━━━━━━━━━┛
When I get OTA update it will look something like:
Code:
F1: STOCK FIRMWARE V.1
O2: OTA UPDATE V.2
F1O2F1O2O2O2O2F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1O2O2O2O2F1F1O2O2O2O2F1F1F1F1F1
┗━━━ BOOT ━━━┛┗━━━━ RECOVERY ━━━━┛┗━━━━━━━━━━━ SYSTEM ━━━━━━━━━━━┛
Then I downgrade via fastboot and it should look like:
Code:
F1: STOCK FIRMWARE V.1
F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1
┗━━━ BOOT ━━━┛┗━━━━ RECOVERY ━━━━┛┗━━━━━━━━━━━ SYSTEM ━━━━━━━━━━━┛
Why hardbrick?

Zixione said:
Please explain a little bit more how is it possible. As far as I understand it should be as following
When I get phone from store it will look like:
Code:
F1: STOCK FIRMWARE V.1
F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1
┗━━━ BOOT ━━━┛┗━━━━ RECOVERY ━━━━┛┗━━━━━━━━━━━ SYSTEM ━━━━━━━━━━━┛
When I get OTA update it will look something like:
Code:
F1: STOCK FIRMWARE V.1
O2: OTA UPDATE V.2
F1O2F1O2O2O2O2F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1O2O2O2O2F1F1O2O2O2O2F1F1F1F1F1
┗━━━ BOOT ━━━┛┗━━━━ RECOVERY ━━━━┛┗━━━━━━━━━━━ SYSTEM ━━━━━━━━━━━┛
Then I downgrade via fastboot and it should look like:
Code:
F1: STOCK FIRMWARE V.1
F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1
┗━━━ BOOT ━━━┛┗━━━━ RECOVERY ━━━━┛┗━━━━━━━━━━━ SYSTEM ━━━━━━━━━━━┛
Why hardbrick?
Click to expand...
Click to collapse
I honestly can't give you a solid answer. If you look at other threads you can find out why. It definitely has something to do with the bootloader.

Dchoi229 said:
I honestly can't give you a solid answer. If you look at other threads you can find out why. It definitely has something to do with the bootloader.
Click to expand...
Click to collapse
Every other thread (that I found) just states as axiom - "downgrading will hardbrick" without clarification - why. But wouldn't
Code:
fastboot flash bootloader bootloader.img
solve all that "bootloader related stuff"?

Zixione said:
Every other thread (that I found) just states as axiom - "downgrading will hardbrick" without clarification - why. But wouldn't
Code:
fastboot flash bootloader bootloader.img
solve all that "bootloader related stuff"?
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492

Dchoi229 said:
https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492
Click to expand...
Click to collapse
Already seen this. The only useful bits of info about downgrading\bricking cause is, again, just statement, that "some updates/flash packages do not allow downgrading", but again without much clarification how exactly some data, sent to flash memory, will block itself from being written:
The thing with failing updates/flash packages is that they usually fail because they do not allow downgrading - even if they allow downgrading of some sort (e.g. OS), they may limit downgrading the second stage bootloader, the signed GPT (partitioning table) etc.
Click to expand...
Click to collapse
Many thanx, anyway !:good: I just need deeper explanation, will search onward myself.

Zixione said:
Already seen this. The only useful bits of info about downgrading\bricking cause is, again, just statement, that "some updates/flash packages do not allow downgrading", but again without much clarification how exactly some data, sent to flash memory, will block itself from being written:
Many thanx, anyway !:good: I just need deeper explanation, will search onward myself.
Click to expand...
Click to collapse
yea.. sorry I'm not much of a developer. You can definitely look inside that thread and see that there are deeper explanations. I believe after a certain update (april security patch i believe) the bootloader is upgraded and when downgrading to a official firmware (MM 6.0.1) the updated bootloader will not work correctly and hard brick the Moto z play. I dont play with the bootloader anymore after hearing of this. Your best option is just to flash stock roms. Best of luck to you my friend. :good:

I am in a similar position wanted to go back to stock deodexed N but I can't because it is rooted with super su and I want to root with magisk which is not possible. Or I think as much anyway.

Zixione said:
Please explain a little bit more how is it possible. As far as I understand it should be as following
When I get phone from store it will look like:
<snip>
Why hardbrick?
Click to expand...
Click to collapse
As I understand it, the hardbrick comes not when you downgrade, but when you use OTA updates to upgrade your device. The likely reason for this appears to be that the OTA only verifies your system version and whether the system, OEM and other partitions are of the same patch level. It does not necessarily check whether your bootloader and GPT are matching your system before patching. Also, downgrading may not downgrade your bootloader (and sometimes doesn't, where it's blocked by a 'security downgrade' warning), leaving you with a mismatched system. Looking through the OTA scripts for the Moto G4 updates, for example, the checks are mainly: is this the correct build to flash over, and are the system partitions unmodified? If yes to both, then it proceeds to flash and then copies over the bootloader files for that OTA. I've not seen an OTA check to verify your bootloader is of the correct patch level (if someone knows better, feel free to correct me).
To use your illustration:
Code:
F1: STOCK FIRMWARE [B]V.2[/B]
O2: OTA UPDATE V.3
F1O3F1O3O3O3O3F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1O3O3O3O3F1F1O3O3O3O3F1F1F1F1F1
┗━━━ BOOT ━━━┛┗━━━━ RECOVERY ━━━━┛┗━━━━━━━━━━━ SYSTEM ━━━━━━━━━━━┛
This is after the OTA update to V3, taken after the OTA to V2. We assume that boot is the bootloader (the secondary bootloader, including the TrustZone and other bootloader partitions), and system includes the kernel and other system components.
If you downgrade to V1 from V3:
Code:
F1: STOCK FIRMWARE V.1
F1O3F1O3O3O3O3F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1
┗━━━ BOOT ━━━┛┗━━━━ RECOVERY ━━━━┛┗━━━━━━━━━━━ SYSTEM ━━━━━━━━━━━┛
You'll notice your bootloader has not downgraded (which can occur in fastboot), since the bootloader blocks you from downgrading your bootloader, especially in the newer stock firmwares. You'll also notice that your system is V1 though. Thus, though your system is V1, your bootloader is V3.
If you take an OTA update to V2, therefore, the OTA appears to look at your system, think your device is all V1 (including your bootloader), and proceed to patch to V2. Of course, as your bootloader is V3, then there is a high likelihood of the V2 OTA corrupting your V3 bootloader, leading to a hard brick.
We've seen this with the Moto Z Play (from the 7.1.1 to 7.0), Moto G4/Plus (downgrading from the June 2017 patch), and other Moto devices. Though this behaviour isn't restricted to Moto devices, it seems to more prevalent after the April/May/June 2017 stock patch updates (possibly to stop you reopening the Motorola bootloader vulnerability?). Thus, as others have suggested, do not downgrade if you can, or be careful and do not flash OTA updates. Try to flash the same stock ROM as what was on your device previously.
Hope that explains things a little more clearly.

Whenever I try use any command on fastboot, i get this message
Code:
(bootloader) slot-count : not found
(bootloader) slot-suffixes : not found
(bootloader) slot-suffixes : not found

RoboticBuddy said:
Whenever I try use any command on fastboot, i get this message
Code:
(bootloader) slot-count : not found
(bootloader) slot-suffixes : not found
(bootloader) slot-suffixes : not found
Click to expand...
Click to collapse
I think those messages are normal, as the Moto Z Play doesn't appear to have the A/B partition system found on the Pixel. Thus, those messages are more informational as there's no separate slot to flash to.

echo92 said:
I think those messages are normal, as the Moto Z Play doesn't appear to have the A/B partition system found on the Pixel. Thus, those messages are more informational as there's no separate slot to flash to.
Click to expand...
Click to collapse
Now I'm getting that I cannot write to /data.

echo92 said:
As I understand it, the hardbrick comes not when you downgrade, but when you use OTA updates to upgrade your device.
[snip]
Hope that explains things a little more clearly.
Click to expand...
Click to collapse
Your explanation adds up missing bits and makes everything much more clear to me. Thank you very much!

im not much of a programmer or anything but I can tell you this. my MZP was down for a month due to this. I was on 7.0 custom rom I think either on the april or January patch, wanted the ota for 7.1, sooooooo I figured I would just downgrade to 6 and accept the ota....... Well that was not wise. If I recall upgrading changed the bootloader which is not able to be downgraded so there was a mismatch and the phone could not boot itself to anything. I would advise double and triple checking the threads. before you hard brick. Luckily for that particular problem there is now a method to recover it. just wanted to give you as much info as possible

Zixione said:
Please explain a little bit more how is it possible. As far as I understand it should be as following
When I get phone from store it will look like:
Code:
F1: STOCK FIRMWARE V.1
F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1
┗━━━ BOOT ━━━┛┗━━━━ RECOVERY ━━━━┛┗━━━━━━━━━━━ SYSTEM ━━━━━━━━━━━┛
When I get OTA update it will look something like:
Code:
F1: STOCK FIRMWARE V.1
O2: OTA UPDATE V.2
F1O2F1O2O2O2O2F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1O2O2O2O2F1F1O2O2O2O2F1F1F1F1F1
┗━━━ BOOT ━━━┛┗━━━━ RECOVERY ━━━━┛┗━━━━━━━━━━━ SYSTEM ━━━━━━━━━━━┛
Then I downgrade via fastboot and it should look like:
Code:
F1: STOCK FIRMWARE V.1
F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1
┗━━━ BOOT ━━━┛┗━━━━ RECOVERY ━━━━┛┗━━━━━━━━━━━ SYSTEM ━━━━━━━━━━━┛
Why hardbrick?
Click to expand...
Click to collapse
Where did you get these hex values so I can check my own?

These values are just part of schematic illustration (as a version numbers are) and doesn't meant to have any meaningful sense.

Wifi not turning on other than marshmallow firmware

I'm facing a weird problem with my wifi on nexus5x
I can only open/access wifi on just marshmallow 6.0.1 firmware which is MTC20K
I tried flashing around 6 different stock firmwares including the latest 4 oreo firmwares. On every firmware other than mtc20k i can't turn on wifi.
Any way to fix this on oreo or nougat?
Any one else having this issue?
Note : i have fixed BLOD. Is that the reason for this?

I don't think so you probably have bad vendor.img

kastik4 said:
I don't think so you probably have bad vendor.img
Click to expand...
Click to collapse
I tried flashing stock firmware via fastboot which includes vendor image right?

Hassan_Elyas said:
I tried flashing stock firmware via fastboot which includes vendor image right?
Click to expand...
Click to collapse
it does include vendor img but depends if it gets flashed you can try flashing it manually. Extract the vendor img from the zip and move it to the folder you have fastboot "installed" and flash it with the command fastboot flash vendor vendor.img if that doesn't help either maybe its because you're radio img doesn't match the firmware you have and you can re flash it with with the command fastboot flash radio radio-bullhead-yourfirmware'sradio.img you need to extract that to the fastboot folder too

kastik4 said:
it does include vendor img but depends if it gets flashed you can try flashing it manually. Extract the vendor img from the zip and move it to the folder you have fastboot "installed" and flash it with the command fastboot flash vendor vendor.img if that doesn't help either maybe its because you're radio img doesn't match the firmware you have and you can re flash it with with the command fastboot flash radio radio-bullhead-yourfirmware'sradio.img you need to extract that to the fastboot folder too
Click to expand...
Click to collapse
Will try tonight. Thanks.

did it work? i have the same issue

Didn't work for me I'm running 8.1 Oreo with June security patches. Also my MAC address is weird 02:00:00:00:00:00 never seen one like this.

Did you do a full firmware flash, or just boot and system?

Calling not working in all custom roms [solved]

I have tried several custom roms (Oreo 8.1) like jaguar and AEX and calling is not working. It seems like the phone cannot connect to 3G.
4G is working.
In the stock rom everything is working.
My baseband version is 1.7.X as the roms requires.
I have used sim slot 1 and 2 without any luck.
I make a clean flash when i change rom.
Any suggestions on how to get calling working?

Flash stock zui 2.5 with qifl. It will work as I was having the same problem.

andreas951207 said:
I have tried several custom roms (Oreo 8.1) like jaguar and AEX and calling is not working. It seems like the phone cannot connect to 3G.
4G is working.
In the stock rom everything is working.
My baseband version is 1.7.X as the roms requires.
I have used sim slot 1 and 2 without any luck.
I make a clean flash when i change rom.
Any suggestions on how to get calling working?
Click to expand...
Click to collapse
Your baseband must be corrupted, flash 1.70 baseband.

cannot delete this comment?

ChetanLokhande said:
Your baseband must be corrupted, flash 1.70 baseband.
Click to expand...
Click to collapse
that did not work

AmaanRaza said:
Flash stock zui 2.5 with qifl. It will work as I was having the same problem.
Click to expand...
Click to collapse
Downgrade to 2.5 and then directly flash the custom ROM? Or should i update to latest zui oreo first?

andreas951207 said:
Downgrade to 2.5 and then directly flash the custom ROM? Or should i update to latest zui oreo first?
Click to expand...
Click to collapse
I think,
1. QFIL 1.9
2. Test if call working
3. Flash 3.5
4. OTA to latest
5. Unlock bootloader + TWRP
6. Flash Custom ROM
7. Test call now.

andreas951207 said:
Downgrade to 2.5 and then directly flash the custom ROM? Or should i update to latest zui oreo first?
Click to expand...
Click to collapse
Flash 2.5 through qifl then test if calls are working. If they are, then go back to custom roms. If they are not, update to 3.5.

andreas951207 said:
that did not work
Click to expand...
Click to collapse
Check if your efs partition is is fine. If it is corrupted then you have flash the xqcn file by editing it for your IMEI, there is one thread on that go through it.

Thank you for the help everyone. I found the solution after a long time.
Type this in fastboot:
fastboot -i 0x2b4c erase modemst1
fastboot -i 0x2b4c erase modemst2
fastboot -i 0x2b4c reboot

andreas951207 said:
Thank you for the help everyone. I found the solution after a long time.
Type this in fastboot:
fastboot -i 0x2b4c erase modemst1
fastboot -i 0x2b4c erase modemst2
fastboot -i 0x2b4c reboot
Click to expand...
Click to collapse
Did it worked I'm using a santoni,
For me the issue is that I cannot call a person perfectly (like my voice cuts everytime, and the other person can't hear all the words I spoke)
Will it be useful for that

How to flash custom roms from Fastboot? SEMI-BRICKED

Hi all! I recently got a XIAOMI MI A2 LITE and I messed it up. Now it goes only on fastboot and when i try to flash recovery it says PARTITION TABLE DOES NOT EXIST. I am guessing my only chance to get the phone back is by flashing the whole system through Fastboot. Can you guys help me ? I did not do any system back stupidly. can anyone send me the gpt bin file to flash the partition? Or other solutions....

Flash stock rom with XiaoMiFlash, unlock bootloader, flash TWRP and go to flash the rom

leechgid said:
Flash stock rom with XiaoMiFlash, unlock bootloader, flash TWRP and go to flash the rom
Click to expand...
Click to collapse
Thanks. I downloaded the images, however i do not have windows but only macbook and i do not know how to use the command to flash all the files at once.

https://forum.xda-developers.com/mi...oot-images-t3824871/post79316028#post79316028