Develop Bugs

help phone wont boot into recovery and system after using blankflash

so i was flashing a nougat 7.0 update on moto z play and then all of a sudden my phone wouldnt even power on the screen was all black so i decided to use blank flash. Blank flash did take me to the bootloader but even when trying to boot to recovery and system it wont work.
help plz.

Jaderalves said:
In Device Manager how is it listed? Fastboot Android S
Click to expand...
Click to collapse
what do you mean

Jaderalves said:
In Device Manager how is it listed? Fastboot Android S
Click to expand...
Click to collapse
is their any ways for me to access recovery and my device because at the moment I'm just stuck on the fast boot screen if so please tell me btw thanks for replying.

ahmed12389 said:
is their any ways for me to access recovery and my device because at the moment I'm just stuck on the fast boot screen if so please tell me btw thanks for replying.
Click to expand...
Click to collapse
Do you see the device listed in Windows?

Flashqueen said:
Do you see the device listed in Windows?
Click to expand...
Click to collapse
yes I can see it

Flashqueen said:
Do you see the device listed in Windows?
Click to expand...
Click to collapse
what do you suggest I do

ahmed12389 said:
what do you suggest I do
Click to expand...
Click to collapse
Have you flashed the stock ROM onto your device? What bootloader version or stock ROM build did you have before you flashed the stock 7.0 build and took the update?
Downgrading to older stock firmware and then attempting to update is generally what caused that hard brick. If you can let us know what device/territory you had, we can try to point you to the right firmware to flash.

echo92 said:
Have you flashed the stock ROM onto your device? What bootloader version or stock ROM build did you have before you flashed the stock 7.0 build and took the update?
Downgrading to older stock firmware and then attempting to update is generally what caused that hard brick. If you can let us know what device/territory you had, we can try to point you to the right firmware to flash.
Click to expand...
Click to collapse
Yes I have flashed stock firmware on my device I remember downgrading to marshmallow then updating back to nougat then my device fully shut down it was all black. After this incident, i did what you would normally do and that was to use blank flash to at least get the bootloader back, as I did get the bootloader I could not use the boot options such as recovery mode. so I am basically stuck on the bootloader and can do nothing. My device is an addison XT1635-02 and before I flashed nougat ota I had the marshmallow December security update.

echo92 said:
Have you flashed the stock ROM onto your device? What bootloader version or stock ROM build did you have before you flashed the stock 7.0 build and took the update?
Downgrading to older stock firmware and then attempting to update is generally what caused that hard brick. If you can let us know what device/territory you had, we can try to point you to the right firmware to flash.
Click to expand...
Click to collapse
I also believe my device is hard bricked as I cant access boot options at all it just keeps boot looping once I try to access a boot option. also is it normal for my bootloader to say that my software status is modified because I think after you flash blank flash your software status modified. finally, I have been trying to flash stock firmware but for some reason, gpt and bootloader.img always fail to flash. Thanks for the reply I hope you can help.

echo92 said:
Have you flashed the stock ROM onto your device? What bootloader version or stock ROM build did you have before you flashed the stock 7.0 build and took the update?
Downgrading to older stock firmware and then attempting to update is generally what caused that hard brick. If you can let us know what device/territory you had, we can try to point you to the right firmware to flash.
Click to expand...
Click to collapse
this is a dumb question but do you think that it is possible to get out of a hard brick without sending it to a moto service center.

ahmed12389 said:
this is a dumb question but do you think that it is possible to get out of a hard brick without sending it to a moto service center.
Click to expand...
Click to collapse
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.

echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
ok the thing is I am certain I used the wrong blank flash zip therefore meaning that I flashed the wrong things this is probably why I'm boot looping do you have any idea how to revert the changes of blank flash so I can flash the propper blank flash. Is their even any blank flash for Moto z play anyways

echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
I was flashing the July security patch stock firmware and it's giving me these errors

echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
if i flash that stock frimware it takes straight to 7.1.1 is that correct

echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
is blank flash universal and works for all version and models for Motorola phone or is their specific ones because if their is I might have used the wrong one

ahmed12389 said:
is blank flash universal and works for all version and models for Motorola phone or is their specific ones because if their is I might have used the wrong one
Click to expand...
Click to collapse
As far as I know, blankflashes are CPU specific, and may also be device specific, though we've had some success using a Moto Z2 play blankflash to rescue Moto Z Play devices that are hard bricked. There's some more info here https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page19 and here https://forum.xda-developers.com/showpost.php?p=73474192&postcount=249
Which blank flash did you use? Also, which July security patch firmware are you flashing? sounds like your need 7.0 or 7.1.1 firmware to proceed. That firmware link would take you up to 7.1.1, yes, but I would advise not to downgrade in future.
Also, please edit your posts rather than making new replies. I understand you're wanting to get your device fixed without paying a lot of money to fix it, give us time to respond.

echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
I just checked its all good i was using the right one. it appears that if you use blank flash, in general, it will modify your software status. I will flash that stock rom I just hope it would work and yes i was flashing the july marshmallow 6.0.1 update and it had no effect on my phone what so ever lets hope this 7.1.1 does. also sorry for all these replies I am in desperate need for my phone and I'm not thinking straight

ahmed12389 said:
I just checked its all good i was using the right one. it appears that if you use blank flash, in general, it will modify your software status. I will flash that stock rom I just hope it would work and yes i was flashing the july marshmallow 6.0.1 update and it had no effect on my phone what so ever lets hope this 7.1.1 does. also sorry for all these replies I am in desperate need for my phone and I'm not thinking straight
Click to expand...
Click to collapse
If your device was ever on stock Nougat (7.0 or 7.1.1), then flashing that marshmallow ROM won't likely work in repairing your bootloader. You need a firmware that is the same or newer than the latest firmware your device had. Downgrading stock firmware does not usually downgrade your bootloader, hence the corruption and need to have same or newer firmware to repair. Your bootloader would otherwise reject old firmware via preflash validation errors.
Hopefully the 7.1.1 firmware will help fix things. You will lose data however in the process of flashing your device, so hopefully you have backups.

echo92 said:
As far as I know, blankflashes are CPU specific, and may also be device specific, though we've had some success using a Moto Z2 play blankflash to rescue Moto Z Play devices that are hard bricked. There's some more info here https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page19 and here https://forum.xda-developers.com/showpost.php?p=73474192&postcount=249
Which blank flash did you use? Also, which July security patch firmware are you flashing? sounds like your need 7.0 or 7.1.1 firmware to proceed. That firmware link would take you up to 7.1.1, yes, but I would advise not to downgrade in future.
Also, please edit your posts rather than making new replies. I understand you're wanting to get your device fixed without paying a lot of money to fix it, give us time to respond.
Click to expand...
Click to collapse
oh my freaking god you fixed it!!! you are literraly my idol thanks to you i dont need to take it to service from now on I'm never flashing again. but thank you very much you fixed my phone you absolute legend.

ahmed12389 said:
what do you mean
Click to expand...
Click to collapse
how is it recognized by the PC in device manager?

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

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

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

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

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

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

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

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

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

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

Xt1766 how to get working apn
Will anyone confirm

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

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

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

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

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

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

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

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

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

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

dload method stuck at 5%

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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 hard/soft bricked

I tried downgrading my Moto G30 from Android 12 to Android 11 using an available stock ROM I found on the internet. At first, I faced some problems and a soft brick, but finally, I was able to flash and boot it correctly. Then, knowing that the ROM flashed was "stock," I decided to relock the bootloader, which was a mistake. After rebooting, I got the message "No valid operating system could be found. The device will not boot."
I spent the whole day trying to figure out how to get it working again. The main problem here is that I relocked the bootloader and can't get to the OS again to enable the option in developer settings to re-unlock it and flash another ROM. I tried using RSA (LMSA) to restore it, but it refuses, and I think it gets the same error that won't let me flash anything to the phone.
During my research, I found that one possible solution is to boot in EDL mode and flash everything again, but I don't want to open my phone and do weird things to get into that mode. Hopefully, there's another solution or another way to get into EDL.
If you have any information that could help me solve this, please comment.

I had the same problem with mine. The thing is, i tried to flash a blank-flash image but it wont go. I think its to early to downgrade your Moto G30, but you can try to flash the stock image in EDL Mode by opening your Motorola. Also you might need to send it to Motorola. Sorry
In the image you have the EDL Test Point you must brick.

But also you can try
fastboot reboot edl
Click to expand...
Click to collapse
or
reboot edl
Click to expand...
Click to collapse

U_ShowcaseDev said:
But also you can try
or
Click to expand...
Click to collapse
I've already tried several combinations of that command with no success.

aldoo9 said:
I've already tried several combinations of that command with no success.
Click to expand...
Click to collapse
Sorry I think your Motorola is Dead.

U_ShowcaseDev said:
I had the same problem with mine. The thing is, i tried to flash a blank-flash image but it wont go. I think its to early to downgrade your Moto G30, but you can try to flash the stock image in EDL Mode by opening your Motorola. Also you might need to send it to Motorola. Sorry
In the image you have the EDL Test Point you must brick.
Click to expand...
Click to collapse
Hello again! Do you know how to flash the stock rom in EDL mode? I've found some tutorials but the files required are not available in the stock rom files to do so.

aldoo9 said:
Hello again! Do you know how to flash the stock rom in EDL mode? I've found some tutorials but the files required are not available in the stock rom files to do so.
Click to expand...
Click to collapse
Please send me a Link.

aldoo9 said:
Hello again! Do you know how to flash the stock rom in EDL mode? I've found some tutorials but the files required are not available in the stock rom files to do so.
Click to expand...
Click to collapse
Don't you need to just blankflash it in EDL?
And yes you most likely need to open it.
For the Blankflash you need to download Lenovo Rescue and Smart Assistant (since lenovo produces moto phones). What this does it installs the correct drivers for your phone.
And the files can be found here : https://mirrors.lolinet.com/firmware/motorola/caprip/blankflash/
Good luck and as always, do your own research!
Edit: https://forum.xda-developers.com/t/hard-brick-moto-g30.4397117/page-2 this thread has more info.

KAN7A said:
Don't you need to just blankflash it in EDL?
And yes you most likely need to open it.
For the Blankflash you need to download Lenovo Rescue and Smart Assistant (since lenovo produces moto phones). What this does it installs the correct drivers for your phone.
And the files can be found here : https://mirrors.lolinet.com/firmware/motorola/caprip/blankflash/
Good luck and as always, do your own research!
Edit: https://forum.xda-developers.com/t/hard-brick-moto-g30.4397117/page-2 this thread has more info.
Click to expand...
Click to collapse
I tried one, but it doesn't work. The Bootloader keeps locked.

U_ShowcaseDev said:
I tried one, but it doesn't work. The Bootloader keeps locked.
Click to expand...
Click to collapse
Isn't the point to flash the stock ROM, not to unlock the bootloader?

Yes, you right. But how???

KAN7A said:
Isn't the point to flash the stock ROM, not to unlock the bootloader?
Click to expand...
Click to collapse
I saw, that you can flash a .xml Stock Firmware FIle. But i dont find anyone that work...

U_ShowcaseDev said:
I saw, that you can flash a .xml Stock Firmware FIle. But i dont find anyone that work...
Click to expand...
Click to collapse
I think you can flash with Lenovo Rescue and Smart Assistant or manually, the XML is to flash automatically, you can flash manually each image.
If you cant maybe there is an error along the way.
I might look into this later. I would lock my bootloader to test but i dont have a backup.

KAN7A said:
I think you can flash with Lenovo Rescue and Smart Assistant or manually, the XML is to flash automatically, you can flash manually each image.
If you cant maybe there is an error along the way.
I might look into this later. I would lock my bootloader to test but i dont have a backup.
Click to expand...
Click to collapse
That can be the end to your phone. But, if you have a test phone that would be excellent.

KAN7A said:
I think you can flash with Lenovo Rescue and Smart Assistant or manually, the XML is to flash automatically, you can flash manually each image.
If you cant maybe there is an error along the way.
I might look into this later. I would lock my bootloader to test but i dont have a backup.
Click to expand...
Click to collapse
Lenove RSA doesn't work. I tried it. When the Bootloader is unlocked it work. When the Bootloader is locked it wont work.

U_ShowcaseDev said:
Lenove RSA doesn't work. I tried it. When the Bootloader is unlocked it work. When the Bootloader is locked it wont work.
Click to expand...
Click to collapse
I dont have a test device right now so i cant test myself, anything I say might be wrong.
This might be a complete brick because of the downgrade from what I've read.
There is little info on the forum about this issue so I don't want to make wrong suggestions until i can test.

Yes, unfortunately, there is still little information about the Moto G30. But I hope that there will be more information and solutions in the future.

U_ShowcaseDev said:
Yes, unfortunately, there is still little information about the Moto G30. But I hope that there will be more information and solutions in the future.
Click to expand...
Click to collapse
Maybe you can help me with some info i am interested in.
1.You have booted into EDL using Short Pin method
2.You have used blankflash successfully
3.Then you try to flash manually and got Permission Denied?
For both Android 11 Stock ROM and Android 12 Stock Rom?
EDIT: Is the back of the phone glued? Or just clamps so you can put it back with no glue?
Since i want to test this soon hopefully.

KAN7A said:
Maybe you can help me with some info i am interested in.
1.You have booted into EDL using Short Pin method
2.You have used blankflash successfully
3.Then you try to flash manually and got Permission Denied?
For both Android 11 Stock ROM and Android 12 Stock Rom?
EDIT: Is the back of the phone glued? Or just clamps so you can put it back with no glue?
Since i want to test this soon hopefully.
Click to expand...
Click to collapse
1. Yes
2. I used a blankflash successfully.
3. Then in fastboot tried to flash the android 11 stock and after it failed the android 12 stock image. Also i tried the RSA varient. Both will not work.
The back is clicked in place. There are two stickers on the phone. Two white ones, One on the top left corner and one on the bottom of the phone.
But careful when you open the back. The screws are well screwed and the cap over the motherboard is slightly stuck. Maybe this will help you: Dissasembly Moto G30 YouTube

@U_ShowcaseDev Thank you so much! This is exactly what i wanted to know!