Database Develop

How to unbrick hard bricked MOTO G 2nd Gen (xt1068)

My phone is totally bricked not even opening in bootloader. It's only recognized by pc as "qhsusb_bulk". so I signed my phone with "Riff BOX JTAG drivers Driver Signature Enforcement Overrider". after this my phone is recognized as "Qualcomm HS-USB QLoader 9008" under Ports (COM & LPT). Then I extract Motorola qboot utility and then run blank-flash.bat file after that this is showing (flashing singleimageFAILED (blank-flash:sdl-transfer-image:sdl-hello:error sending packet).
maybe that singleimage.bin file is problematic.
So I need correct blank-flash file for my phone.
Help me guys. thanks in advance.

deleted. Reason : OP edited.

sagar846 said:
Have you tried giving it CPR? (jk)
Just reflash stock firmware.
Link : Click Here
Click to expand...
Click to collapse
edit..

zman01 said:
Very useful post.. Did you read the OP or you're just guessing here?
Click to expand...
Click to collapse
Op edited post. Before there was only hard brick problem given (when I posted).

Well, there is a good chance that you can't do anything about it. But, give as some info about what you did to it, what was the last version of Android or Rom on it, and so on.

Addy K said:
My phone is totally bricked not even opening in bootloader. It's only recognized by pc as "qhsusb_bulk". so I signed my phone with "Riff BOX JTAG drivers Driver Signature Enforcement Overrider". after this my phone is recognized as "Qualcomm HS-USB QLoader 9008" under Ports (COM & LPT). Then I extract Motorola qboot utility and then run blank-flash.bat file after that this is showing (flashing singleimageFAILED (blank-flash:sdl-transfer-image:sdl-hello:error sending packet).
maybe that singleimage.bin file is problematic.
So I need correct blank-flash file for my phone.
Help me guys. thanks in advance.
Click to expand...
Click to collapse
I get the same place in my moto g 2014 xt1069. Do i have any chance to create a blackflash from original lollipop ROM?
EDIT: blankflash*

marcoslucianops said:
I get the same place in my moto g 2014 xt1069. Do i have any chance to create a blackflash from original lollipop ROM?
Click to expand...
Click to collapse
Nope, you don't have any

Addy K said:
...
Click to expand...
Click to collapse
Can you give me the files you used?

Well this guide might work for you guys. Its for the moto g1 but everything used in the guide is kind of the same for all moto devices except the firmware. Don't forget to download the correct firmware for your phone :
Click Here

sagar846 said:
Well this guide might work for you guys. Its for the moto g1 but everything used in the guide is kind of the same for all moto devices except the firmware. Don't forget to download the correct firmware for your phone :
Click Here
Click to expand...
Click to collapse
This won't work, ^^ the "blank flash" in the tutorial you've sent us, is only for the Moto G 1st gen, i've already tried it ^^ this is not compatible :/
This is why we need the blank flash for the Moto G 2014, then this tuto will work ^^

Miiick3y said:
This won't work, ^^ the "blank flash" in the tutorial you've sent us, is only for the Moto G 1st gen, i've already tried it ^^ this is not compatible :/
This is why we need the blank flash for the Moto G 2014, then this tuto will work ^^
Click to expand...
Click to collapse
Check the firmware download link again (file factory). There are 5+ pages. Find the right firmware for your phone (Itll be labelled TITAN CFL blah blah)
Flash it.
Direct link : Click Here

sagar846 said:
Check the firmware download link again (file factory). There are 5+ pages. Find the right firmware for your phone (Itll be labelled TITAN CFL blah blah)
Flash it.
Direct link : Click Here
Click to expand...
Click to collapse
Thanks for help, but i can't flash anything, my phone is only recognized on my pc as a qualcomm communication port ^^

Addy K said:
My phone is totally bricked not even opening in bootloader. It's only recognized by pc as "qhsusb_bulk". so I signed my phone with "Riff BOX JTAG drivers Driver Signature Enforcement Overrider". after this my phone is recognized as "Qualcomm HS-USB QLoader 9008" under Ports (COM & LPT). Then I extract Motorola qboot utility and then run blank-flash.bat file after that this is showing (flashing singleimageFAILED (blank-flash:sdl-transfer-image:sdl-hello:error sending packet).
maybe that singleimage.bin file is problematic.
So I need correct blank-flash file for my phone.
Help me guys. thanks in advance.
Click to expand...
Click to collapse
@Andy K
Found the reason why it didn't work. That is because that method is used to rescue Qualcomm Snapdragon devices. Our device is Qualcomm based so yeah. Here's a kinda detailed explanation
Owners of Qualcomm based LG’s, HTC’s, Samsung’s, Sony’s and Motorola’s, im afraid this tool is not suitable for you, because those liers mostly have chosen not to use default options of this platform, they dont (cant) want us to rescue our phones so easly, what would have happened to their service centers all around the world then ? They need to change “The Motherboard” in spite of the ability to fix this problem so easly to earn more and more and more money.
Site Link : Click Here

I was on stock Marshmallow 6.0 rom. Then I flashed stock Lollipop 5.0.2 rom in my phone and then I was updating my phone to new stagefright patch but after switch off my phone didn't turn on again.

My last android version was Marshmallow 6.0. I downgraded my phone to Lollipop 5.0.2 and tried to update latest stagefright patch from system update. But after switched off my phone never turn on again. Whenever I connect my phone to the charger it's shows nothing but white led light for 10 seconds. And my phone recognised by my PC as "qshusb_bulk".

Need Moto G 2nd Gen "blankflash image" to flash new bootloader.
As the bootloader of my phone has been collapsed so I need to flash a new bootloader to my phone to relive. But I don't have the right file. And I don't think there is any blankflash image of my phone (XT1068) is available on the net. So I just need to know that is there any way to extract these file from Stock ROM?

Addy K said:
As the bootloader of my phone has been collapsed so I need to flash a new bootloader to my phone to relive. But I don't have the right file. And I don't think there is any blankflash image of my phone (XT1068) is available on the net. So I just need to know that is there any way to extract these file from Stock ROM?
Click to expand...
Click to collapse
No there is no way. I think they already got 5.0 singleimage, but the problem is with programmer.mbn. Without motorola signature it won't flash the bootloader..

still no hope...

Do you have 5.0 or 6.0 singleimage file?

am stuck in the same position. the company has to come up with the new bootloader file. or upload the xt1068 bootloader. one method is throught riff jtag . but very few repair guys have that box. in mumbai they charge 1000-1500rs to repair such phones

Bricked - EDL Mode only

I have the AT&T version and I bricked it by attempting to flash CN 2.1. I knew the risks and its not a huge deal, but I was wondering if anyone has had any success unbricking this phone with miflash or qfil? I cannot seem to find a programmer that will flash this thing correctly. Most of them just reboot EDL mode immediately. I found one MSM8996 .elf programmer that at least hangs for a minute before failing, but thats about it.

loudog3114 said:
I have the AT&T version and I bricked it by attempting to flash CN 2.1. I knew the risks and its not a huge deal, but I was wondering if anyone has had any success unbricking this phone with miflash or qfil? I cannot seem to find a programmer that will flash this thing correctly. Most of them just reboot EDL mode immediately. I found one MSM8996 .elf programmer that at least hangs for a minute before failing, but thats about it.
Click to expand...
Click to collapse
the same problem bro, bricked after flashing CN firmware we need some one who downloading firmware for QPST

I am giving the uni Android tool a go. It cost me 50 bucks but allegedly they support the phone in the next release. I'll let you know what happens.

loudog3114 said:
I am giving the uni Android tool a go. It cost me 50 bucks but allegedly they support the phone in the next release. I'll let you know what happens.
Click to expand...
Click to collapse
Has the brother ROOT research been successful?

I got at&t zte axon m too (unlock cause I can use my simcard to phone and edge) and was trying to flash to cn 2.1
luckily I found this thread before the last step.
I would postpone for now, and just use whatever the phone can use, though I still sour from cannot use 4G, cannot tethering and at&t message backup & sync always pestering me to put at&t number (which I dont have cause I dont stay in us)

release unbrick tool
//forum.gsmhosting.com/vbb/f1019/zte-axon-z999-unbrick-done-flashing-uat-version-22-01-a-2590411/
uni-android tool released unbrick tool for ATT AXON M
i have bricked phone because update chinese rom on ATT AXON M
i paid for uat, wait 8 months, finally they did it
now supported flashing JUST ORIGINAL ROMS because axon m's bootloader not unlocked

docount said:
//forum.gsmhosting.com/vbb/f1019/zte-axon-z999-unbrick-done-flashing-uat-version-22-01-a-2590411/
uni-android tool released unbrick tool for ATT AXON M
i have bricked phone because update chinese rom on ATT AXON M
i paid for uat, wait 8 months, finally they did it
now supported flashing JUST ORIGINAL ROMS because axon m's bootloader not unlocked
Click to expand...
Click to collapse
i Can Comfirm this works ive done my self too cost a bit but phone is back to life!

Please can someone help with mine too I have the same problem after update ota by sdcard my phone is dead I want to bring it alive again axon m z999 at&t please help brother

nv data corrupted

Hi,
After trying to flash I was like you can see in the image "nv data corrupted", does anyone know how to solve it?

sk3lt said:
Hi,
After trying to flash I was like you can see in the image "nv data corrupted", does anyone know how to solve it?
Click to expand...
Click to collapse
"Trying to flash" , what exactly did you flash ?
How do you flash it ?
Why dont you flash TWRP followed by ROM of any choice ?
NV normally contained in EFS partition, which can be backed up and flash from TWRP and QPST.
But again, your description is far from clear for us to help you.

otonieru said:
"Trying to flash" , what exactly did you flash ?
How do you flash it ?
Why dont you flash TWRP followed by ROM of any choice ?
NV normally contained in EFS partition, which can be backed up and flash from TWRP and QPST.
But again, your description is far from clear for us to help you.
Click to expand...
Click to collapse
I already flashed with twrp and miflash with stock rom and xiaomi.eu the flash is finished successfully but the nv data corrupted always comes back. Any idea how can I solve this?

sk3lt said:
I already flashed with twrp and miflash with stock rom and xiaomi.eu the flash is finished successfully but the nv data corrupted always comes back. Any idea how can I solve this?
Click to expand...
Click to collapse
When you flash using TWRP, did you actually managed to boot into system ? Or it stuck in recovery ?
Where did the nv corrupted notification appear when u were using TWRP ?
Prior to facing this issue, what you actually did ? I mean, did this phone work before ? Before you start getting this error, what you did, what you install, what you flash, what you delete ? Or did it just suddenly happen with nothing modified ?

otonieru said:
When you flash using TWRP, did you actually managed to boot into system ? Or it stuck in recovery ?
Where did the nv corrupted notification appear when u were using TWRP ?
Prior to facing this issue, what you actually did ? I mean, did this phone work before ? Before you start getting this error, what you did, what you install, what you flash, what you delete ? Or did it just suddenly happen with nothing modified ?
Click to expand...
Click to collapse
Boot up to the Android logo and then return to recovery.
I flashed a room and lost the imei, I tried to recover with a qcn I found but I must have done something wrong.

sk3lt said:
Boot up to the Android logo and then return to recovery.
I flashed a room and lost the imei, I tried to recover with a qcn I found but I must have done something wrong.
Click to expand...
Click to collapse
You gonna need to ask someone to backup their QCN, take out the imei info, give it to you, and flash it using QPST.

otonieru said:
You gonna need to ask someone to backup their QCN, take out the imei info, give it to you, and flash it using QPST.
Click to expand...
Click to collapse
I can't use qpst, because I can't activate usbdebug and the diag port.
Is it possible to give me a hand?

sk3lt said:
I can't use qpst, because I can't activate usbdebug and the diag port.
Is it possible to give me a hand?
Click to expand...
Click to collapse
This is absolutely not a issue, that requires using Qpst
You simply need to wipe data and follow the on screen prompts. (You will lose all data on your phone.) However the phone will work again.

tsongming said:
This is absolutely not a issue, that requires using Qpst
You simply need to wipe data and follow the on screen prompts. (You will lose all data on your phone.) However the phone will work again.
Click to expand...
Click to collapse
I flashed an altered rom, without success I got a brick I'm without recovery and without fastboot I just have a black screen and it's only recognized by the PC in 9008 mode, you have any idea how I can solve it?

sk3lt said:
I flashed an altered rom, without success I got a brick I'm without recovery and without fastboot I just have a black screen and it's only recognized by the PC in 9008 mode, you have any idea how I can solve it?
Click to expand...
Click to collapse
Sorry that you are having these issues, But my comment was based on the photo that was posted on the OP. Typically formatting is the resolution. If you no longer have that screen available, you should contact an authorised repair center to fix it for you.
Otherwise If the phone is bound to your account, you could try what is listed here: https://www.mobilerdx.com/2019/02/xiaomi-mi-8-test-point-boot-xiaomi-mi-8-into-edl-9008-mode.html
Scams or Actual Fixes?
I have recently read about supposed hacks that according to a couple of Chinese BBS sites, has worked for some that require buying a specialised Jtag programming tool which cost about $60, that you use along with altered versions of following files: prog_emmc_firehose_8909.mbn.elf, mi8 persist image, rawprogram0, frp and a patch file. All of which that can all be obtained from here: https://romprovider.com/2019/09/mi-account-remove-xiaomi/ ( UMT Download)
Supposedly Chimera is another option: https://chimeratool.com/en/docs Again I have not used any of these tools with the mi8, I am merely sharing what I read about recently.
By the time you have spent the money acquiring the tools, it seems that you are better off just mailing the phone off to be repaired by an official repair center. Here is a web page that provides a list of official repair centers : https://www.pinoytechnoguide.com/2014/06/xiaomi-service-centers.html
Good Luck and try anything mentioned above at your own risk.
Edit: Have you tried the Flashall.bat method?
That should work since you are seeing the com port.

tsongming said:
This is absolutely not a issue, that requires using Qpst
You simply need to wipe data and follow the on screen prompts. (You will lose all data on your phone.) However the phone will work again.
Click to expand...
Click to collapse
tsongming said:
Sorry that you are having these issues, But my comment was based on the photo that was posted on the OP. Typically formatting is the resolution. If you no longer have that screen available, you should contact an authorised repair center to fix it for you.
Otherwise If the phone is bound to your account, you could try what is listed here: https://www.mobilerdx.com/2019/02/xiaomi-mi-8-test-point-boot-xiaomi-mi-8-into-edl-9008-mode.html
Scams or Actual Fixes?
I have recently read about supposed hacks that according to a couple of Chinese BBS sites, has worked for some that require buying a specialised Jtag programming tool which cost about $60, that you use along with altered versions of following files: prog_emmc_firehose_8909.mbn.elf, mi8 persist image, rawprogram0, frp and a patch file. All of which that can all be obtained from here: https://romprovider.com/2019/09/mi-account-remove-xiaomi/ ( UMT Download)
Supposedly Chimera is another option: https://chimeratool.com/en/docs Again I have not used any of these tools with the mi8, I am merely sharing what I read about recently.
By the time you have spent the money acquiring the tools, it seems that you are better off just mailing the phone off to be repaired by an official repair center. Here is a web page that provides a list of official repair centers : https://www.pinoytechnoguide.com/2014/06/xiaomi-service-centers.html
Good Luck and try anything mentioned above at your own risk.
Edit: Have you tried the Flashall.bat method?
That should work since you are seeing the com port.
Click to expand...
Click to collapse
Hello, thank you for your answer, the mother is not linked to my account I disconnected to do the experiments. in my country i don't have a xiaomi assistance center, i get the error missmatching image and device.
There is no other way to unbrick without buying these tools so expensive that you mentioned

sk3lt said:
Hello, thank you for your answer, the mother is not linked to my account I disconnected to do the experiments. in my country i don't have a xiaomi assistance center, i get the error missmatching image and device.
There is no other way to unbrick without buying these tools so expensive that you mentioned
Click to expand...
Click to collapse
use testpoint method, and flash it using QFIL.

otonieru said:
use testpoint method, and flash it using QFIL.
Click to expand...
Click to collapse
I always get this error.
I already managed to unbrick with a firmware eng eng.
but then when flash with stock rom stays the same again nv data corrupted.
Any solution to solve this nv data corrupted?

sk3lt said:
I always get this error.
I already managed to unbrick with a firmware eng eng.
but then when flash with stock rom stays the same again nv data corrupted.
Any solution to solve this nv data corrupted?
Click to expand...
Click to collapse
root cause of your issue is that you play with wrong qcn and messed up the nv,
wince you cant plugged to qpst, you need someone to make EFS backup for you torestore from twrp

You can restore phones imei if your bootloader is unlocked but only 2nd sim slot will work

How can I do this? Can you help me please?

jokerm90 said:
You can restore phones imei if your bootloader is unlocked but only 2nd sim slot will work
Click to expand...
Click to collapse
How can I do this? Can you help me please?

Dear All,
While trying to install MIUI 12 Beta , I Lost my IMEI
Installed ENG Firmware which allowed my to edit the IMEI using the Maui META ver 10.1816.0.01 but due to corrupted NV Data the phone isn't booting
Anyone can backup and share the NV Data file ?! i found one online but unfortunately it has a password and can't unrar it.
Your support is much appreciated to guide throw fixing this issue.

sk3lt said:
How can I do this? Can you help me please?
Click to expand...
Click to collapse
You need backup EFS and Modem via TWRP first(better with OrangeFox). After you need Magisk first and some manipulation with QCN file via QPST. I will write it later
MohamedYousri said:
Dear All,
While trying to install MIUI 12 Beta , I Lost my IMEI
Installed ENG Firmware which allowed my to edit the IMEI using the Maui META ver 10.1816.0.01 but due to corrupted NV Data the phone isn't booting
Anyone can backup and share the NV Data file ?! i found one online but unfortunately it has a password and can't unrar it.
Your support is much appreciated to guide throw fixing this issue.
Click to expand...
Click to collapse
Maui Meta is for MTK cpu phones. You need QPST

Note 8 Pro is MTK Device

Unlock ANY Pixel from Carrier

____________________________________________________
UPDATE AS OF 16 OF MAY 2023:
The security patch of December of 2022 fixed the patch, so it doesn't work on this version and newer ones.
The project is still alive and I am working to get the exploit to work on newer version, but for now haven't found any.
However due to the complex nature of the project and that I have little free time, expect this to take sometime until a new exploit is available.
If anyone has any ideas or suggestions please let me know! Any help is welcome
____________________________________________________
Hey everybody!
So recently I bought a Google Pixel 4 XL. The thing is that in Europe they are too expensive compared to the US, so I bought one that was from AT&T(used of course). However is that I need to use my SIM on the phone, but of course, the phone refused to allow me to use my SIM from Spain. ⛔️
So after hours of research, I found a way to unlock it. Here are the steps:
1. Remove your SIM card if it is on the phone
2. Do a factory reset
3. Do OFFLINE SETUP. Also, DON'T PUT ANY PASSWORD OR ANY TYPE OF SCREEN LOCK
4. Once you are on the main screen, enable USB Debugging.
5. Connect the phone to the computer (I assume you already have the USB drivers, platform-tools downloaded and knowledge on how to use ADB commands. If you don't have the SDK downloaded, head to this link and follow the instructions)
6. Inside the platform-tools folder, open a terminal window and run "adb shell"(on mac, once you are on the directory you have to run "./adb shell") and then "pm uninstall -k --user 0 com.google.android.apps.work.oobconfig" (run them without quotes)
After this, you can already connect the phone to the internet and put your SIM in.
This didn't unlock the phone though . What we have just done is this:
When we connect the phone to the internet, it verifies if it should lock the SIM or not. So we did a setup without internet, so the phone can't do that. After that, we uninstall the package responsible for doing this.
So when we connect it to the internet, it won't check the SIM lock
However, the bootloader is still locked and grey out. This is because this app is responsible to grey or not the bootloader switch. If it is from a carrier, the package will disable the switch, and if not you will have the ability to unlock it. As we kill the app before it could do its job, the bootloader will be waiting until the package gives its answer.
Special thanks to this Jorge Cortés to make this post possible.
If you find the post useful, consider buying me a cup of coffee please with Revolut.

If anyone has problems/doubts please let me know!

Esim is unlocked as well?

Didn't try but should work, as the phone never check if it is from a carrier or not.

#mcl said:
Didn't try but should work, as the phone never check if it is from a carrier or not.
Click to expand...
Click to collapse
On another post someaone said esim is working on pixel 4 verizon unlocked trought this steps. So as you say, it works.
Thanks

Danny17va said:
On another post someaone said esim is working on pixel 4 verizon unlocked trought this steps. So as you say, it works.
Thanks
Click to expand...
Click to collapse
No problem. Just for curiosity, who did the test on unlocked Verizon Pixel?

Is there any work around to unlock to bootloader too??

Daniyal48 said:
Is there any work around to unlock to bootloader too??
Click to expand...
Click to collapse
Hey,
I am working on that. As it turns out there is a way to flash firmware to any device with a Qualcomm chip, even if the bootloader os locked. It's called EDL mode. This mode was designed to force flash firmware in bricked devices that can't use fastboot or adb.
I already find the app I need to flash, actually there a a lot of different ones( I chose QPST) but it needs some strange files that I didn't find yet, and it won't allow em to use the google firmware neither .
So when I find those files I will write a detailed guide on how to unlock the bootloader , but for now I only know how to use any SIM on a locked Pixel device.

#mcl said:
Hey,
I am working on that. As it turns out there is a way to flash firmware to any device with a Qualcomm chip, even if the bootloader os locked. It's called EDL mode. This mode was designed to force flash firmware in bricked devices that can't use fastboot or adb.
I already find the app I need to flash, actually there a a lot of different ones( I chose QPST) but it needs some strange files that I didn't find yet, and it won't allow em to use the google firmware neither .
So when I find those files I will write a detailed guide on how to unlock the bootloader , but for now I only know how to use any SIM on a locked Pixel device.
Click to expand...
Click to collapse
I have tried the same on a OnePlus device but they have MSM Tool to thet let you work in edl mode but I haven't found any tool for Pixel devices yet

Daniyal48 said:
I have tried the same on a OnePlus device but they have MSM Tool to thet let you work in edl mode but I haven't found any tool for Pixel devices yet
Click to expand...
Click to collapse
yeah unlike Oneplus Google didn't release any software designed specifically to the Pixel lineup, so you have to use the generic Qualcomm tools.

#mcl said:
yeah unlike Oneplus Google didn't release any software designed specifically to the Pixel lineup, so you have to use the generic Qualcomm tools.
Click to expand...
Click to collapse
Can you name other generic Qualcomm tools so I can experiment with them??

Yeah of course, there is QFIL also and some others that aren't official. I downloaded them from Androidmtk website.
With this link you go to the qpst download and use instructions section of their webpage. At the bottom you will find similar programs, but I didn't get to try them. You can try them, but make sure they are for Qualcomm Chipset, because some of them are for mediatek phones.

#mcl said:
Yeah of course, there is QFIL also and some others that aren't official. I downloaded them from Androidmtk website.
With this link you go to the qpst download and use instructions section of their webpage. At the bottom you will find similar programs, but I didn't get to try them. You can try them, but make sure they are for Qualcomm Chipset, because some of them are for mediatek phones.
Click to expand...
Click to collapse
Okay thank you I hope i find a solution with this

Daniyal48 said:
Okay thank you I hope i find a solution with this
Click to expand...
Click to collapse
No problem, good luck researching .
I will keep searching as well to see if I can find those files

#mcl said:
No problem, good luck researching .
I will keep searching as well to see if I can find those files
Click to expand...
Click to collapse
If you find any files please also send them to me. Can we use a working Device to get these files from. Like we extract these files for a normal pixel 4 xl and then flash it to ours?

Daniyal48 said:
If you find any files please also send them to me. Can we use a working Device to get these files from. Like we extract these files for a normal pixel 4 xl and then flash it to ours?
Click to expand...
Click to collapse
Of course, if I find them I will make them available for anyone .
Yes in theory you can extract this files from your phon, however as mine is locked I need them from an unlocked pixel I suppose, but I didn't try to extract the files from my home and the flash them again, it could work. In the QPST you even have a section to that, it's a backup I Believe but not sure about the name.
If you try and it works let me know!

#mcl said:
Of course, if I find them I will make them available for anyone .
Yes in theory you can extract this files from your phon, however as mine is locked I need them from an unlocked pixel I suppose, but I didn't try to extract the files from my home and the flash them again, it could work. In the QPST you even have a section to that, it's a backup I Believe but not sure about the name.
If you try and it works let me know!
Click to expand...
Click to collapse
Yes I am also looking for an unlock Pixel 4 XL if I find one I will try extracting these files and post it somewhere on the internet so anyone can access it

Yeah that is a way, but I was thinking that maybe these files are inside of the IMG files of the firmware from Google, and that firmware isn't lock , so if anyone manage to find those files there you wouldn't need to buy another pixel to extract the firmware.
I also think that in reality you don't need the firmware but rather some files for your Qualcomm Chipset to get the Sahara protocol working and I believe later on you flash the firmware, however I am not sure about that as I didn't try it.
I think this because you can find some Qualcomm snapdragon 855 programmer files (which had the extension we need), so they may be basic files that activates the Sahara protocol (which is the one used when the phone is in this mode) and only after I believe you can flash the firmware using some commands.
I would like to try out this but I can't as it could brick my phone and I don't have other to use, and I don't have any other pixel, this is my first and only Pixel ever.
So if you have an older pixel and you want you could try this theory...

#mcl said:
Yeah that is a way, but I was thinking that maybe these files are inside of the IMG files of the firmware from Google, and that firmware isn't lock , so if anyone manage to find those files there you wouldn't need to buy another pixel to extract the firmware.
I also think that in reality you don't need the firmware but rather some files for your Qualcomm Chipset to get the Sahara protocol working and I believe later on you flash the firmware, however I am not sure about that as I didn't try it.
I think this because you can find some Qualcomm snapdragon 855 programmer files (which had the extension we need), so they may be basic files that activates the Sahara protocol (which is the one used when the phone is in this mode) and only after I believe you can flash the firmware using some commands.
I would like to try out this but I can't as it could brick my phone and I don't have other to use, and I don't have any other pixel, this is my first and only Pixel ever.
So if you have an older pixel and you want you could try this theory...
Click to expand...
Click to collapse
I have Pixel 2 XL but it doesn't boot into EDL i tried fastboot commands and also abd commands but it doesn't even go there...I have Pixel 3 XL on the way I will try on that but that is already unlocked

#mcl said:
Yeah that is a way, but I was thinking that maybe these files are inside of the IMG files of the firmware from Google, and that firmware isn't lock , so if anyone manage to find those files there you wouldn't need to buy another pixel to extract the firmware.
I also think that in reality you don't need the firmware but rather some files for your Qualcomm Chipset to get the Sahara protocol working and I believe later on you flash the firmware, however I am not sure about that as I didn't try it.
I think this because you can find some Qualcomm snapdragon 855 programmer files (which had the extension we need), so they may be basic files that activates the Sahara protocol (which is the one used when the phone is in this mode) and only after I believe you can flash the firmware using some commands.
I would like to try out this but I can't as it could brick my phone and I don't have other to use, and I don't have any other pixel, this is my first and only Pixel ever.
So if you have an older pixel and you want you could try this theory...
Click to expand...
Click to collapse
Mbn Files from Pixel 4 Request
As title states, I am looking for the mbn files from the pixel 4. I downloaded the modem partition and could not seem to extract it and thought someone that owns a pixel 4 might have better luck than me. Thanks! The directory might be...
forum.xda-developers.com
Are these files related to our issue

Redmi Note 9 - How do I restore my IMEI? I don't have a backup of my nvram/nvdata but I have the numbers.

How do I write IMEI along with baseband version back to my phone? I really don't want to risk bricking it again, that's enough stress for me in the past two days
I heard that I can only flash IMEI 2 back to it, and if I want flashing IMEI 1 as well I'd need to install a custom rom on the phone. So if that's a solution I'd love if someone could help me with it. MIUI 13 is slow and laggy af (which is the reason I bricked the phone in the first place, to install a better ROM).
But here's something, when I flash the phone's firmware through fastboot, issues start to rise (as per my experience with it so far), but through SP Flash Tool, it's alright. So I'd love to know if installing custom ROMs using the tool would be alright, if not then if recovery is required or if fastboot is fit for the job. If that's an issue I'd love if someone could give me advice when it comes to it.
Old post 1: (not my current situation)
"Long story short, I bricked the phone and after months, I've finally been able to repair it (downgraded from MIUI 13 to MIUI 11), but I lost my IMEI. I have the phone's two IMEI numbers, but I could not find any tool to help me write it to the phone. Either that, or I don't know whether the phone should be turned on or off, or if there's any special mode that's required for that matter.
Help would really be appreciated."
Old post 2:
"It happened after manually installing engineering ROM on it, now I can only doubt it's BROM mode that's working and nothing else, but I'm not sure. SP Flash Tool doesn't want to work with the phone since I want to flash the stock rom back. I really need help please."

YLTN said:
Long story short, I bricked the phone and after months, I've finally been able to repair it (downgraded from MIUI 13 to MIUI 11), but I lost my IMEI. I have the phone's two IMEI numbers, but I could not find any tool to help me write it to the phone. Either that, or I don't know whether the phone should be turned on or off, or if there's any special mode that's required for that matter.
Help would really be appreciated.
Click to expand...
Click to collapse
Install Engineering ROM and then write imei using available tools.

mvikrant97 said:
Install Engineering ROM and then write imei using available tools.
Click to expand...
Click to collapse
I fear that if I install the ROM, the phone might brick again

YLTN said:
I fear that if I install the ROM, the phone might brick again
Click to expand...
Click to collapse
Why?

mvikrant97 said:
Why?
Click to expand...
Click to collapse
The reason why my phone broke in the first place was due to flashing a misc.bin file after following a YouTube tutorial. It was part of a process to download twrp on the phone unofficially. Since then I started looking for ways to fix it until I finally found a post that had to do with fixing nvdata corruption (which was the error I had prior to fixing the phone) which helped.
So yeah, I don't think I can trust flashing ROMs on my phone as much as before, but I'll still try the engineering ROM thing.

mvikrant97 said:
Why?
Click to expand...
Click to collapse
So um...it bricked. This time worse than before. It doesn't turn on at all no matter how long I press the power button. It was after I manually flashed eng rom.

YLTN said:
So um...it bricked. This time worse than before. It doesn't turn on at all no matter how long I press the power button. It was after I manually flashed eng rom.
Click to expand...
Click to collapse
Does it shows up in device manager?

mvikrant97 said:
Does it shows up in device manager?
Click to expand...
Click to collapse
Yep, it doesn't show up as it's name or "Android", it shows up as MediaTek USB Port (COM3), that's why I doubted it to be in BROM mode.

YLTN said:
Yep, it doesn't show up as it's name or "Android", it shows up as MediaTek USB Port (COM3), that's why I doubted it to be in BROM mode.
Click to expand...
Click to collapse
By the way, after trying to connect to it using mtkclient, I got this error:
DeviceClass - [LIB]: ←[31mCouldn't get device configuration.←[0m

YLTN said:
By the way, after trying to connect to it using mtkclient, I got this error:
DeviceClass - [LIB]: ←[31mCouldn't get device configuration.←[0m
Click to expand...
Click to collapse
Hold on, it worked now for some reason when I disconnected the battery, but it keeps connecting and disconnecting so that's an issue.
I'll try to reconnect the battery and see.

YLTN said:
Hold on, it worked now for some reason when I disconnected the battery, but it keeps connecting and disconnecting so that's an issue.
I'll try to reconnect the battery and see.
Click to expand...
Click to collapse
Please install LIB USB drivers.
Visit this tutorial here on xda

mvikrant97 said:
Please install LIB USB drivers.
Visit this tutorial here on xda
Click to expand...
Click to collapse
Bro, thank you so much, the phone's unbricked now. I couldn't believe my eyes
But for now, is there any solution for the IMEI problem?

YLTN said:
Bro, thank you so much, the phone's unbricked now. I couldn't believe my eyes
But for now, is there any solution for the IMEI problem?
Click to expand...
Click to collapse
I always recommend a NV Backup before messing up with your own device, that's all I know.
Download the file attached here but remember you can fix only second IMEI using this method. Please don't try to fix both IMEI or NV Data will be corrupted again.
Video Tutorial to Follow Video Tutorial

mvikrant97 said:
I always recommend a NV Backup before messing up with your own device, that's all I know.
Download the file attached here but remember you can fix only second IMEI using this method. Please don't try to fix both IMEI or NV Data will be corrupted again.
Video Tutorial to Follow Video Tutorial
Click to expand...
Click to collapse
The guy in the video is using MIUI 12, I have MIUI 13. I don't know if that's an issue but someone in the comments said something about MIUI or so. I'm not a professional but many times when I see tutorials they're very specific with the MIUI version.
Also, I'm not sure how to back up nv data, do I use mtkclient or is it somewhere in the attachment you sent me?
And one more thing, my phone's baseband version is unknown, could that affect the process?

YLTN said:
The guy in the video is using MIUI 12, I have MIUI 13. I don't know if that's an issue but someone in the comments said something about MIUI or so. I'm not a professional but many times when I see tutorials they're very specific with the MIUI version.
Also, I'm not sure how to back up nv data, do I use mtkclient or is it somewhere in the attachment you sent me?
And one more thing, my phone's baseband version is unknown, could that affect the process?
Click to expand...
Click to collapse
You don't need the backup anymore and you can follow the tutorial in the video irrespective of the MIUI version you have.
I have also attached the files that are used in the video.

mvikrant97 said:
You don't need the backup anymore and you can follow the tutorial in the video irrespective of the MIUI version you have.
I have also attached the files that are used in the video.
Click to expand...
Click to collapse
Alright then, I'll follow the steps and tell you the results once I'm done.

mvikrant97 said:
You don't need the backup anymore and you can follow the tutorial in the video irrespective of the MIUI version you have.
I have also attached the files that are used in the video.
Click to expand...
Click to collapse
The phone keeps rebooting when connecting it to Maui META. Like it shows META MODE at the bottom of the screen but then it turns off. Now it's bootlooping. I guess I'll have to flash MIUI on it again. At least I still have access to fastboot and recovery.
Update: NV Data corrupted after flashing MIUI, but I got a solution that hopefully works.
Update 2: After flashing MIUI 11 (along with some other nvdata and nvram files, i think they're just empty), it works now and the error is gone. But as I said IMEI issue's still there. Maybe I would need engineering ROM for this one? Although it bricked my phone before.
Also, the phone started bootlooping before attempting the Maui META thing, so maybe it's either the manual formatting of partitions or the files I flashed on it.

YLTN said:
The phone keeps rebooting when connecting it to Maui META. Like it shows META MODE at the bottom of the screen but then it turns off. Now it's bootlooping. I guess I'll have to flash MIUI on it again. At least I still have access to fastboot and recovery.
Update: NV Data corrupted after flashing MIUI, but I got a solution that hopefully works.
Update 2: After flashing MIUI 11 (along with some other nvdata and nvram files, i think they're just empty), it works now and the error is gone. But as I said IMEI issue's still there. Maybe I would need engineering ROM for this one? Although it bricked my phone before.
Also, the phone started bootlooping before attempting the Maui META thing, so maybe it's either the manual formatting of partitions or the files I flashed on it.
Click to expand...
Click to collapse
Try flashing the ENG rom and try fixing your IMEI

mvikrant97 said:
Try flashing the ENG rom and try fixing your IMEI
Click to expand...
Click to collapse
So I ran into another issue. it tells me I need "exaid-verified.img" and that verified boot is enabled, which is not present in the ENG ROM folder.

mvikrant97 said:
Try flashing the ENG rom and try fixing your IMEI
Click to expand...
Click to collapse
Btw one more thing, I can update my phone right? Like, it won't break my phone? I'm good with MIUI 11 but I wonder if updating it would fix baseband version.