Database Info

[ROM] ZTE Visible R2 Stock firmware

Here is the stock firmware including the firehose needed to flash it
B10 Firmware
Here
B12 Firmware
Here
ZPI file for ZTE SalesMultiDL tool
Here
Here is a step by step guide on how to flash the stock rom with QFIL and by extension any image.
Download and install the Qualcomm drivers from here
Download the firmware from above
Extract the firmware to a folder that you can easily access them from like your desktop
Download and install QPST from here
Open the QFIL application (Find it in your start menu)
In the "Select Build Type" field select Flat Build
In the "Select Programmer" field navigate to the folder you extracted the firmware and support files to and select the prog_emmc_firehose_8917.mbn file
Select the "Load XML" button and navigate to the folder you extracted the firmware and support files to and select the rawprogram0.xml and then the patch0.xml when prompted.
Plug in your tablet
Run the following adb command "adb reboot edl" (Now the screen should be blank but the led light should be red)
If the text at the top of the QFIL application says "No Port Available" click the "Select Port..." option and pick your device. If your device isn't showing up there you didn't install the drivers properly.
Click the Download Button to begin flashing your device

Here is the Stock wallpapers in case anyone wants them
https://www.androidfilehost.com/?fid=1395089523397903558

I just got this device a couple days ago and was hoping I could use PDANet/Foxfi to connect more than one device at a time to wifi hotspot but they've evidently blocked the apps.. Do you have any insight to that?

pegb856 said:
I just got this device a couple days ago and was hoping I could use PDANet/Foxfi to connect more than one device at a time to wifi hotspot but they've evidently blocked the apps.. Do you have any insight to that?
Click to expand...
Click to collapse
I don't own this device sadly just grabbed the firmware for a friend of mine and posted it here in case anyone in the future wants it.

deadman96385 said:
I don't own this device sadly just grabbed the firmware for a friend of mine and posted it here in case anyone in the future wants it.
Click to expand...
Click to collapse
Ok thank you for the reply.

deadman96385 said:
I don't own this device sadly just grabbed the firmware for a friend of mine and posted it here in case anyone in the future wants it.
Click to expand...
Click to collapse
If you WANT to own this device it's currently $19 out the door on visible.com. No Trade required.
https://slickdeals.net/f/13221781-visible-r2-is-now-19-without-service-or-trade-in-requred

I'm gonna see if I can flash Chinese firmware to unlock the bands

Bowsa2511 said:
I'm gonna see if I can flash Chinese firmware to unlock the bands
Click to expand...
Click to collapse
Good Luck finding the A0722 firmware (that's the model androidpolice thinks this is a renamed version of).

famewolf said:
Good Luck finding the A0722 firmware (that's the model androidpolice thinks this is a renamed version of).
Click to expand...
Click to collapse
https://imgur.com/yOe0vIx

Your elite google-fu obviously exceeded my own. Please make that sharable if you can....megaupload.nz would hold it and is free.

famewolf said:
Your elite google-fu obviously exceeded my own. Please make that sharable if you can....megaupload.nz would hold it and is free.
Click to expand...
Click to collapse
https://mega.nz/#!aRo0CaBA!nm37c3V11tr2260V23wIxb4yZufD5-_f6gID8i3HjSY
Let me know if it's helpful

DISREGARD. Looks like out of date info.

Any of you able to get fastboot working on it? ADB works, but my fastboot doesn't detect the phone.

Nice looking out, just ordered one.

Using one of the hidden activities app from the play store. There is an option to change from LTE to 2G/3G/4G under one of the phone settings. But calling still did not work with either AT&T or T-Mobile.

famewolf said:
Good Luck finding the A0722 firmware (that's the model androidpolice thinks this is a renamed version of).
Click to expand...
Click to collapse
Just a heads-up: even if you found the files for the A0722, you'd brick your R2 if you managed to flash them. The chassis and screen seem to be the same, but they're completely different specs-wise. Given that the A0722 has a different SoC and an eMMC chip 2-4x larger, I doubt you'd get real far in the flashing process in the first place.

FEGuy said:
Just a heads-up: even if you found the files for the A0722, you'd brick your R2 if you managed to flash them. The chassis and screen seem to be the same, but they're completely different specs-wise. Given that the A0722 has a different SoC and an eMMC chip 2-4x larger, I doubt you'd get real far in the flashing process in the first place.
Click to expand...
Click to collapse
In my case my main goal was to use it and the factory software to learn about mbn files. I've dealt with LG's TOT and KDZ files but not the mbn's. Thanks for giving folks the warning though.

Would it be possible for someone to grab the download URL for whatever OTA update is available for the device? I don't think it's anything major but I'd like to poke around at it; the firmware uploaded here seems to be from launch.

FEGuy said:
Would it be possible for someone to grab the download URL for whatever OTA update is available for the device? I don't think it's anything major but I'd like to poke around at it; the firmware uploaded here seems to be from launch.
Click to expand...
Click to collapse
I've got a logcat recorder queued up to be installed and will try to grab an url by starting the download. If that fails there are a couple of alternatives....someone who has DONE the upgrade could rip the rom and make it available if @deadman96385 can point to some instructions on how to rip the rom.
Also you can always let your own upgrade occur because he's already provided the original software and QFIL which would let you restore to original factory and get the update again.
As a last resort I can grab the log from my ROUTER that the phone is connected to and try to get the url that way which I've had to do with SOME devices.

I'll probably end up taking the OTA again anyways as I've been messing around with the firmware from the first post. Honestly, I'd really recommend staying away from flashing it without a good reason. Even when the flasher works, either the logging and/or the flasher hangs and it's close to impossible to tell which without unplugging your phone. If a partial flash leaves you in a state where you can't get to ADB to boot to EDL mode, you'll have to boot into diagnostics mode, use a piece of Chinese software to boot from there back to EDL, and within five seconds or so, close that software and start the flashing process from QFIL before the com port stops responding to requests, leaving you to reboot the phone and start again.
I've been trying to get non-LTE networks and calling working, but it's entirely impossible to tell whether my tweaks are having unintended side effects or if the flashing just crapped out partway through, even when I'm just flashing single partitions.

Redmi Note 6 Pro Unbrick in EDL Mode - I Need Help!

Hi everyone,
I seriously need some advices since I can't manage to solve my problem.
BEFORE YOU READ:
A month has passed, and I couldn't manage to recover my phone. I decided to buy a brand new phone for my brother.
The thread is going to stay there, since I hope it could be useful for people luckier than myself
The Problem:
My brother found his phone (the Redmi Note 6 Pro) turned off.
He wasn't able to turn it on.
I could manage to wake it up by pressing volume-up + power
very strangely, it directly turned into the OS (and not into the TWRP)
"but ok, at least it turned on" I thought
After only a few minutes, the phone suddenly turned off and from there my journey started to became a p**p
I'm not able to enter into recovery, and I'm not able to enter into fastboot neither.
I realized that the phone is fu--- ehmm I mean bricked. The funny thing is that we haven't done anything strange.
Some useful informations:
latest TWRP was installed
I was on the latest Pixel Experience Extended ROM (Android 11)
No custom kernel (I kept the kernel included in the PEE ROM)
No Root
What I tried:
Since it was impossible to do anything, I followed some guides (found here and on Youtube as well) and I opened my phone (if I'm lucky, I haven't destroyed anything ---- YET ).
I managed to enter in EDL mode
my Windows PC is able to recognize it on the COM / LPT ports as Qualcomm HS-USB QDLoader 9008
I downloaded the Mi Flash Tool
I downloaded the Boot Firmware and the two special files (prog_emmc_firehose_Sdm660_ddr.elf and prog_emmc_firehose_Sdm660_lite.elf) following this video link (please don't blame me, but I haven't found anything here)
I put the files inside the image folder
I tried to flash the firmware via Mi Flash but I got a funny error: "cannot receive hello packet"
Thinking that I was doing something wrong, I downloaded the latest Mi Flash Tool but nothing
I downloaded the latest tulip global image but nothing
I authenticated with the mi account into the tool (technically it shouldn't be needed) and... guess what? nothing.
I'm totally out of ideas. Of course I tried to reconnect the phone multiple times (shortening the two pins every time). I also tried to disconnect the battery and going USB-power-only.
Every time I get the "cannot receive hello packet" error, and suddenly the procedure fails saying "Riferimento ad un oggetto non impostato su un'istanza di un oggetto" (italian, that means "Object reference not set to an instance of an object").
EDIT: this error is also listed as "Null Reference Exception" (since it seems to be caused by the following exception: "System.NullReferenceException" - as you can read in the log I included)
Any ideas? What else can I try? Have I done anything wrong?
This never happened me before in almost 10 years of flashing. And, you know what? I just learned how to destr--- ehm open a phone! (...I used the little metal tab inside a Monster Energy can as tool *coff coff* -- C Y B E R P U N K)
Thanks to everyone that will try to help me. Every suggestion is appreciated*
*but please don't suggest me a trash can
Mi Flash Log:
Spoiler: Mi Flash Log
[15:18:15 COM6]:MiFlash 2020.3.14.0
[15:18:15 COM6]:vboytest index:6
[15:18:15 COM6]:flash in thread name:COM6,id:15
[15:18:15 COM6]:sw in images
[15:18:15 COM6]:flash in thread name:COM6,id:15
[15:18:15 COM6]:vboytest do open :
[15:18:15 COM6]: serial port COM6 opend successfully
[15:18:15 COM6]:[COM6]:start flash.
[15:18:16 COM6]:cannot receive hello packet,MiFlash is trying to reset status!
[15:18:17 COM6]:try to reset status.
[15:18:17 COM6]:Switch mode back
[15:18:17 COM6]:cannot receive hello packet,MiFlash is trying to reset status!
[15:18:17 COM6]:System.NullReferenceException: Riferimento a un oggetto non impostato su un'istanza di oggetto.
in XiaoMiFlash.code.bl.SerialPortDevice.SaharaDownloadProgrammer(Int32 programmertype)
in XiaoMiFlash.code.bl.SerialPortDevice.XiaomiFlash() in XiaoMiFlash.code.bl.SerialPortDevice.SaharaDownloadProgrammer(Int32 programmertype)
in XiaoMiFlash.code.bl.SerialPortDevice.XiaomiFlash()
[15:18:17 COM6]:no provision exit:COM6
[15:18:17 COM6]:flashSuccess False
[15:18:17 COM6]:isFactory False CheckCPUID False
[15:18:18 COM6]:before:flashSuccess is False set IsUpdate:True set IsDone True
[15:18:18 COM6]:after:flashSuccess is False set IsUpdate:false set IsDone true

Little Update:
tried to disable windows' driver signature: same issue
tried to disconnect the phone display (seems weird, but why not giving it a chance): same issue.
I also downloaded Mi Flash Pro, which should work even without an authorized Mi account. But I get the same damn error.

Disperate up. You guys are my last hope.

Hello @Gh_Racer I got the exact same problem. Found my phone turned off 2 days ago, when I tried to turn it on the miui logo appeared. turned off and that was it. Not been able to turn it on after that. Did u by any chance fix the problem? Thanks!

fawziX said:
Hello @Gh_Racer I got the exact same problem. Found my phone turned off 2 days ago, when I tried to turn it on the miui logo appeared. turned off and that was it. Not been able to turn it on after that. Did u by any chance fix the problem? Thanks!
Click to expand...
Click to collapse
Damn, really? That's pretty disappointing. These cases are becoming suspicious... maybe that could be some kind of programmed obsolescence(?)
Just for curiosity: were you on stock MIUI or did you have any kind of modifications?
Unfortunately, I couldn't manage to do anything so far.
I loaned my old OnePlus 5T to my brother for now and I think that we'll buy a Redmi Note 10 as soon it will became available in our country. Of course I'm still here for any kind of suggestion until then.

Gh_Racer said:
Damn, really? That's pretty disappointing. These cases are becoming suspicious... maybe that could be some kind of programmed obsolescence(?)
Just for curiosity: were you on stock MIUI or did you have any kind of modifications?
Unfortunately, I couldn't manage to do anything so far.
I loaned my old OnePlus 5T to my brother for now and I think that we'll buy a Redmi Note 10 as soon it will became available in our country. Of course I'm still here for any kind of suggestion until then.
Click to expand...
Click to collapse
I was on the official MIUI, I didn't do any kind of modifications to the phone. I found it also weird that we have the same problem around the same time. Maybe it's related to an automatic update? mine was like that when I woke up in the morning the day before it was in perfect condition. Let me know if u manage to somehow fix it and I'll let u know if i get it working. (btw I also ordered a new XIAOMI phone red note 9 pro lol)

fawziX said:
I was on the official MIUI, I didn't do any kind of modifications to the phone. I found it also weird that we have the same problem around the same time. Maybe it's related to an automatic update? mine was like that when I woke up in the morning the day before it was in perfect condition. Let me know if u manage to somehow fix it and I'll let u know if i get it working. (btw I also ordered a new XIAOMI phone red note 9 pro lol)
Click to expand...
Click to collapse
I was on a custom ROM, as I said in my original post, so I won't point my finger to an automatic update. Maybe, maybe, some google-thing update? But I'm really sceptical that it would even be possible to hard brick a device in this way.
That's really weird, anyway.
Ps. Have you tried to open the phone and flash the fastboot + ROM in EDL mode?

I have not tried it yet. Do u have some links or tutorials on how to do this? I just received the kit to open the phone. I thought at first it might be a battery problem since the phone doesn't seem to charge at all when I plug it in electricity.

fawziX said:
I have not tried it yet. Do u have some links or tutorials on how to do this? I just received the kit to open the phone. I thought at first it might be a battery problem since the phone doesn't seem to charge at all when I plug it in electricity.
Click to expand...
Click to collapse
Here are some videos I followed. Do it at your own risk.
Phone Open + EDL Test Points *
Mi Flash Procedure in EDL Mode**
if the phone is not recognized as Qualcomm HS-USB QDLoader 9008, you need to install the drivers
This should work for both locked and unlocked bootloader devices, if I'm not wrong.
Here's another useful and complete guide.
This guide is not for the Redmi Note 6 Pro, so don't use the provided ROM and fastboot. Just follow the procedure, that it's the same for every Xiaomi phone.
* I don't know what kind of nails that guy has lol Keep in mind that you have to heat the phone up with an hair dryer in order to be able to work with the tools (the body is pretty tight).
In the video is not clear, but the phone has two slots: the first one is made for replacing the screen, and the second is made for taking apart the back cover. Pay attention to this (I didn't know this detail, and I took apart my screen during the first attempt).
** During the flash procedure, I get the error I mentioned in my original post. I'm not sure if it's related to having an un-authorized Mi account or whatsoever, I haven't found any clear confirmation about that.

Gh_Racer said:
Here are some videos I followed. Do it at your own risk.
Phone Open + EDL Test Points *
Mi Flash Procedure in EDL Mode**
if the phone is not recognized as Qualcomm HS-USB QDLoader 9008, you need to install the drivers
This should work for both locked and unlocked bootloader devices, if I'm not wrong.
Here's another useful and complete guide.
This guide is not for the Redmi Note 6 Pro, so don't use the provided ROM and fastboot. Just follow the procedure, that it's the same for every Xiaomi phone.
* I don't know what kind of nails that guy has lol Keep in mind that you have to heat the phone up with an hair dryer in order to be able to work with the tools (the body is pretty tight).
In the video is not clear, but the phone has two slots: the first one is made for replacing the screen, and the second is made for taking apart the back cover. Pay attention to this (I didn't know this detail, and I took apart my screen during the first attempt).
** During the flash procedure, I get the error I mentioned in my original post. I'm not sure if it's related to having an un-authorized Mi account or whatsoever, I haven't found any clear confirmation about that.
Click to expand...
Click to collapse
Thank you for the infos! I'll try to do this when I have some free time in the coming days and I'll let you know if I have any success.

fawziX said:
Thank you for the infos! I'll try to do this when I have some free time in the coming days and I'll let you know if I have any success.
Click to expand...
Click to collapse
I hope you'll be able to do something. Please update me in that case! Good luck.

Gh_Racer said:
I hope you'll be able to do something. Please update me in that case! Good luck.
Click to expand...
Click to collapse
Hello here I'm again. Maybe you can help me with one more thing. I'm trying to flash it but i get a weird xml error when trying.
Can u link to me the .elf files you used? The link in the video is broken. Thanks again!

fawziX said:
Hello here I'm again. Maybe you can help me with one more thing. I'm trying to flash it but i get a weird xml error when trying.
Can u link to me the .elf files you used? The link in the video is broken. Thanks again!
Click to expand...
Click to collapse
Btw I also had the hello packet problem. But if u remove the usb cable from PC and then attach it again and refresh it dissapears but then after some time I have the weird xml error (resdump: <?xmlversion="1.0".........)

fawziX said:
Hello here I'm again. Maybe you can help me with one more thing. I'm trying to flash it but i get a weird xml error when trying.
Can u link to me the .elf files you used? The link in the video is broken. Thanks again!
Click to expand...
Click to collapse
I need to search for them, since I downloaded things from a lot of different sources (I also deleted the one I downloade, since I did lost my hopes). I’ll update you in case I’ll be able to find them.

fawziX said:
Btw I also had the hello packet problem. But if u remove the usb cable from PC and then attach it again and refresh it dissapears but then after some time I have the weird xml error (resdump: <?xmlversion="1.0".........)
Click to expand...
Click to collapse
So, exactly, what did you do? You unplugged the cable and attached it again shortening the two test pins? Or you simply attached it without doing anything special?
I wasn’t able to solve the hello packet error.
I don’t know what the xml error is related to, since I couldn’t manage to communicate with the phone. I have no suggestions for this, I’m sorry.

Hi everyone...
Two days ago my Note 6 Pro woke up the same and after doing everything described above and even being able to successfully flash via EDL,
it remains the same and without changes.
I explain...
It turns on and stays in the MI logo, when trying to enter the recovery it stays in the TWRP home screen and only allows to enter the FASTBOOT that is unlocked but when trying to flash from MiFlash it gives an error as when I try directly from. bat file so I decided to try for EDL and it threw the xml error (resdump: <? xmlversion = "1.0" .........), I did some research and it turns out due to "prog_emmc_firehose_Sdm660_ddr.elf" and "prog_emmc_firehose_Sdm660_lite.elf" in "images folder" to firmware uncompress files, and I replaced them with others that allowed the flash to continue and finish successfully, but to my surprise, when restarting the device, everything continued without any change...
Until this moment I do not find any information that can help with this unfortunately.
I just hope that some of the "Great GURUS" in the forum can help and provide some solution... If it exists.

fawziX said:
Hello here I'm again. Maybe you can help me with one more thing. I'm trying to flash it but i get a weird xml error when trying.
Can u link to me the .elf files you used? The link in the video is broken. Thanks again!
Click to expand...
Click to collapse
Tenho o redmi note 6 pro bloqueado no modo edl gostaria de saber se alguém tem como ajudar
MOD EDIT: Please post only in English according to the FORUM RULES or at least add an English translation below your foreign language(Google translator for example), translation added below:
I have the redmi note 6 pro locked in edl mode I wonder if anyone has how to help

Hi everyone, I’m sorry for having not replied yet.
As I wrote in my main post, I haven’t managed to recover my phone so far, so we decided to buy a brand new phone.
I hope you’ll be luckier than me.

Hi all, in order to flash your phone you will need authorized account normally, but if you try to flash stock firmware with Mi Flash tool and QFill you will face errors and errors.
What I recommend you is to re-flash full fastboot firmware the same version what you had on your phone or the latest stable fastboot firmware which you can get here:
Oreo Android 8 OEKMIXM
Pie Android 9 PEKMIXM
Latest version:
https://bigota.d.miui.com/V12.0.1.0.PEKMIXM/tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global_ac26982758.tgz
All versions:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Once you download firmware open it with 7-Zip archive tool, and again open firmware inside 7-Zip until you see normal folder with the name of firmware for example "tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global" and extract to desktop.
Once is Finish dowload this bypass auth files.
File with out Login
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Now copy those two files:
prog_emmc_firehose_Sdm660_ddr.elf
prog_emmc_firehose_Sdm660_lite.elf
and replace those two files inside firmware that you extracted before on Desktop for example:
"C:\Users\YOUR_PC_USER_NAME\Desktop\tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global\images"
Next step is to use correct MiFlash tool which you can download here:
Working Mi Flash Tool:
MiFlash20160401.zip | by firmwarefile.com for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Now, load firmware inside Mi Flash tool:
for example:
"C:\Users\YOUR_PC_USER_NAME\Desktop\tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global"
Next is to remove battery cover carefully because you can damage fingerprint flat cable!or use special edl cable if you don't wanna to open your device.
- Disconect battery
- short those test point pins
https://1.bp.blogspot.com/-C8bU7S6nAaI/Xqrd_PdvLXI/AAAAAAAAaLA/PK_E4oI_qPcJhBnSwlbQ0sr5J_9Ti2ycQCNcBGAsYHQ/s1600/21-14-47-images.jpg
-Plug the usb cable while you are holding those pins, once you got your device detected in Qdowloader 9008 mode relese short from test points.
Now click on Reflash on MiFlash tool and you will see your device is detected, now click on Flash and wait (it can take some time to finish). If you got error just unpplug the phone from PC and try again.
FOR FLASH OPTION:
You can check FLASH All or Flash all except storage
Once you successfully flashed your device, unplug device from your pc, plug battery back and power up your device to see if it's working or not.
The pay part if that doesn't work is reprograming or replacing emmc chip with ufi tool or something like that...
Good luck

Teddy Lo said:
Hi all, in order to flash your phone you will need authorized account normally, but if you try to flash stock firmware with Mi Flash tool and QFill you will face errors and errors.
What I recommend you is to re-flash full fastboot firmware the same version what you had on your phone or the latest stable fastboot firmware which you can get here:
Oreo Android 8 OEKMIXM
Pie Android 9 PEKMIXM
Latest version:
https://bigota.d.miui.com/V12.0.1.0.PEKMIXM/tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global_ac26982758.tgz
All versions:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Once you download firmware open it with 7-Zip archive tool, and again open firmware inside 7-Zip until you see normal folder with the name of firmware for example "tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global" and extract to desktop.
Once is Finish dowload this bypass auth files.
File with out Login
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Now copy those two files:
prog_emmc_firehose_Sdm660_ddr.elf
prog_emmc_firehose_Sdm660_lite.elf
and replace those two files inside firmware that you extracted before on Desktop for example:
"C:\Users\YOUR_PC_USER_NAME\Desktop\tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global\images"
Next step is to use correct MiFlash tool which you can download here:
Working Mi Flash Tool:
MiFlash20160401.zip | by firmwarefile.com for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Now, load firmware inside Mi Flash tool:
for example:
"C:\Users\YOUR_PC_USER_NAME\Desktop\tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global"
Next is to remove battery cover carefully because you can damage fingerprint flat cable!or use special edl cable if you don't wanna to open your device.
- Disconect battery
- short those test point pins
https://1.bp.blogspot.com/-C8bU7S6nAaI/Xqrd_PdvLXI/AAAAAAAAaLA/PK_E4oI_qPcJhBnSwlbQ0sr5J_9Ti2ycQCNcBGAsYHQ/s1600/21-14-47-images.jpg
-Plug the usb cable while you are holding those pins, once you got your device detected in Qdowloader 9008 mode relese short from test points.
Now click on Reflash on MiFlash tool and you will see your device is detected, now click on Flash and wait (it can take some time to finish). If you got error just unpplug the phone from PC and try again.
FOR FLASH OPTION:
You can check FLASH All or Flash all except storage
Once you successfully flashed your device, unplug device from your pc, plug battery back and power up your device to see if it's working or not.
The pay part if that doesn't work is reprograming or replacing emmc chip with ufi tool or something like that...
Good luck
Click to expand...
Click to collapse
I followed all the steps without any issues, since they were the same as I tried the last time, but a wanted to give a try to the files you linked me.
But... Unfortunately, I always get the same error. Probably, as you correctly pointed, that's an hw fault and there's nothing we can do.
I hope that someone will be luckier than me! I lost my hopes. RIP Redmi Note 6 Pro.

[CLOSED] Delete Thread.

Due to the disrespect of certain members I will no longer share the tutorials.

Wait does this mean you finally got my script to work?

lebigmac said:
Wait does this mean you finally got my script to work?
How about a little feedback in my project thread? Is that too much to ask for?
Did the latest fix work for you or not? Hello?
Click to expand...
Click to collapse
I said you were working on it. LOL. If it worked I'd be writing a Guide for that!

Make sure boot.img matched with the phone build number, or the phone may get bootloop.
Moto One Ace is one of the easiest phone to root

mingkee said:
Make sure boot.img matched with the phone build number, or the phone may get bootloop.
Moto One Ace is one of the easiest phone to root
Click to expand...
Click to collapse
Exactly. Definitely made a note of that in the guide since that is why the frozen touchscreen issue happens.

Articul8Madness said:
.This tutorial is for people like me than ran into problems rooting the Moto One 5G Ace XT2113 (MetroPCS Qualcomm Variant) running on stock Android 10. I got this phone literally last week brand new in the box. This is a hand holding guide for the Noobs that really are intimidated by rooting their device.
Follow the following at your own risk! I am not responsible for any mishaps with your devices.
I want to thank @mingkee and @sd_shadow for pointing me in the right direction. And for the rest of the contributors that I took bits and pieces from that helped me figure out rooting this; I did achieve root out the starting gate but initially lost touchscreen functionality. The issue was that you have to use the boot.img of your firmware to patch into Magisk; if you do this with your phone out the box you really don't know which firmware was used and that is where the bungle happens. This will clear up all those potential freakout moments.
Thanks to Android 10 being System As Root with all these new super partitions running amuck, you cannot get Write access in the actual system files. So even when you achieve root, you can't do much. @lebigmac is working on that as we speak. Drop by his thread on R/W access and beta test his script so he can get more knowledge about how our phone works.
Introduction/Preparation
First, go and prepare by READING EVERYTHING. Very important. This is the Qualcomm variant and NOT the Mediatek variant. Flashing does make a difference between the two. Last thing you want to do is brick the device because you flashed the wrong firmware to the wrong processor, or you flashed other software for the other similiar Moto One 5G and it bricked.
Second, unlock the bootloader. All T-Mobile and their subsidiary variants can be unlocked by Motorola as well as International and Motorola factory variants; go to their bootloader official unlock site and follow their instructions, it's easy peasy. If you do it in firefox it may not go to the third step page and hang on the page where you put the long code in (follow instructions on page to get the unlock code you'll see what I'm talking about). It is HIGHLY ADVISABLE to do this in Waterfox or Chrome (I used Waterfox). And yes, you may have to request the code 3x to get it to send to your email depending on their server traffic. When you get it, follow Motorola's instructions for unlocking the bootloader in fastboot. It will show you that the bootloader is unlocked.
Verizon and ATT Variants CANNOT BE BOOTLOADER UNLOADER UNLOCKED.
***NOTES SO YOU DON'T FREAK OUT***
1. I did NOT see the motorola post screen telling me it was unlocked. I had to find this in fastboot's menu.
2. The only way to restore the phone if something goes wrong is by flashing it via fastboot. The way to get to fastboot is turn the phone off and press Volume Down and Power. The Motorola tool will NOT work. That's normal.
3. You will see a cute message that you've unlocked the bootloader and that the phone software integrity is compromised when you boot the phone up every single time after the bootloader unlock. It will also say press the power button to pause. This is normal. Give it a minute, you havent broke it.
4. OEM Unlocking should already be activated and greyed out in the Developer Options once the bootloader is unlocked; you can't access it anymore.
Files
You will need an SD card for root. You will also need other apks to successfully help you pull off root ready to install. Pull ALL the necessary files you will need.
1. Get Minimal ADB and Fastboot (it's easier).
2. Download the Motorola Drivers from their site if yo don't already have them (if you run into problems you will have to uninstall and reinstall them through their utility which is found on PC here: C:\Program Files\Common Files\Motorola Shared\Mobile Drivers
3. Cpu-Z.apk (Very important, its hard to know your hardware without this).
4. Magisk v22.0.apk (They no longer have a separate Magisk Manager)
5. Root Explorer.apk (This software helps navigation better but you can use any Explorer of your choice).
6. Root Checker.apk
7. Stock Firmware XT2113-3_KIEV_RETEU_10_QZK30.Q4-40-62_subsidy-DEFAULT_regulatory-XT2113-3-EU-SAR_CFC.xml (This is important if you mess up the boot image trying to root). You can get the firmware of your choice at Motorola Official Firmware For Kiev.
8. Patience (and a good movie keeping you going).
As of now this device as no TWRP, so you have to do this the old fashioned way to root. And just so you know, I used Windows 7 for all of this.
Pre-Rooting
1. Make sure the phone is fully charged.
2. Make sure your sim card is REMOVED from the phone. Everytime you wipe the phone or do anything messing with the boot image the phone resets itself to factory settings, and tries to push an update. Just take the silver key thing and pop it out. You will have to push it back in and out in a second, but start with it out.
3. Make sure your wifi is OFF.
4. Make sure your SD is in and mountable and all files you need are on the card.
5. Make sure you Save boot.img to your SD Card from your firmware files. This is very important for root.
6. Make sure your developer options are activated.
7. Make sure your USB debugging is enabled AND you've given permissions for your computer to have administrative access with it enabled (more on this below).
8. Make sure to check CPU-Z for your hardware specs so you download the right files for the phone and avoid potential problems.
9. Make sure you manually set USB to Transfer files (no other option will work and by default its set to Charge this Device).
10. Make sure you have the STOCK CABLE that comes with the phone. Like most Motorolas this model is funky about using other cables.
11. Make sure you back up all your calls, texts, pics, etc. Flashing the firmware is the ultimate factory reset and you will lose all your files on the phone. SMS Restore is a good software to backup Calls and Text logs and it supports keeping MMS.
12. Make sure you have the internet. It is necessary for some steps.
Rooting
1. Make sure all the firmware files are extracted into your Minimal ADB and Fastboot folder (or whatever ADB folder you're using for this).
2. Open FlashFile.xml in Notepad. This is located among the firmware files you put in the Minimal ADB and Fastboot folder.
3. Cut, copy, and paste everything from the FlashFile that is shown and then paste it in an online Flash file Converter. I used Online Flash File Converter here.
4. Convert the text by pressing the bar below where you pasted the text. It may be in Spanish or Portuguese but is should say something like Cerar Commandos.
5. Copy the text by hitting the two pieces of paper icon in the corner after it's converted. Or just cut copy and paste manually.
6. Turn the phone completely OFF.
7. Plug your phone via USB cable into the computer.
8. Press Volume Down and Power to boot into fastboot mode. Do not use "adb reboot bootloader" as that command may or may not work and hang at "waiting for device" (it was iffy for me and it knocked off USB permissions BADLY).
9. Open up Minimal ADB and Fastboot (Make sure you don't have it set to open this as an administrator, it messes with permissions) Make sure your firmware files are in the Minimal ADB directory or it won't work.
10. Paste the contents of the flashfile converter into Minimal ADB and Fastboot. This should start the process of the flashing.
11. When the entire flash is complete, boot the phone and disconnect phone from the computer. Ignore the bootloader unlock error.
12. Wait. Sometimes this takes up to 3-5 minutes on a new flash. You should see the boot animation of Motorola.
13. Push your Sim Card back into the phone.
14. Start setting up your device on the screen. Sim Card must be in or it will give you a message your phone is Network Locked.
15. Once you make it to the Wifi Setup screen take the Sim back OUT the phone. Do not connect to Wifi.
16. Once you are done with setup, go to Settings>About phone.
17. Go all the way down to Build Number and press it until you unlock Developer Options.
18. Go to Settings>System>Advanced>Developer Options. Advanced is a pull down tab that will reveal Developer Options.
19. Disable Automatic System Updates. I know this is hard for some people, but a forced OTA update may cause problems and prohibit root.
20. Enable USB Debugging. Disable Verify bytecode of debuggable apps. Disable Verify apps over USB if it is highlighted. Exit.
21. Put your SD/Sim card back into the phone.
22. Go to the Files folder and install Magisk first, then Root Explorer and Root Checker.
23. Open Magisk. You will see Magisk and App. Hit Install by Magisk (a fingerprint looking icon is to its left).
24. Allow Magisk to access photos, media, and files if it asks.
25. Select option "Select and Patch A File."
26. It will take you to a screen where you can select your explorer to navigate to your SD card where you saved the boot.img. Go there and select it.
27. Magisk will save it as magisk_patched.img. Once you get it patched, find where it saved, make sure it's on your SD card and then turn off the phone.
28. Plug your phone via USB cable into the computer.
29. Press Volume Down and Power to boot into fastboot mode.
30. Open up a fresh Minimal ADB and Fastboot (Make sure you don't have it set to open this as an administrator, it messes with permissions) Make sure you transfer the magisk_patched.img that Magisk patched off your SD card into this folder.
31. Rename your original boot.img to "boot.img original" or whatever distinct name you want to give it in your Minimal ADB and Fastboot folder.
32. Rename your magisk_patched.img to boot.img.
33. In Minimal ADB and Fastboot type "fastboot flash boot boot.img" and hit enter.
34. If all goes well it should flash to the partition before it says done and in how many seconds.
35. When it is done, reboot phone by selecting START (keep pressing volume rockers until you see it, then press the power button).
36. Wait for the bootloader cannot be trusted screen to pass (may take a minute) and wait for the Hello Moto opening.
37. Open Root Checker and confirm root. You can uninstall it after confirmation if you like.
38. Open Root Explorer. A prompt asking you to grant permission should pop up.
Congrats. You should be rooted now.
***NOTES SO YOU DON'T FREAK OUT***
1. Do NOT flash someone else's patched boot image. It WILL NOT WORK. Do the work, find your firmware, and patch the boot image yourself. You're asking for bootloop hell if you do as your boot.img that Magisk patches needs to match that particular firmware you used.
2. While it hasn't happened to me, You may have followed everything perfect and it still bootlooped. Save yourself the frustration and just flash it over. See the next section on the proper way to flash so you don't lose your baseband, IMEI, or any other important stuff.
3. While you won't lose anything just flashing boot.img, you will lose everything having to flash ALL the firmware over. Keep backups of all your important stuff.
****Notes on Flashing The Stock Firmware if you have to****
In the event you bootloop and have to start from scratch, follow my guide on restoring the firmware on the phone. And don't worry - it won't relock the bootloader. You can find my guide here: The Complete Noob Guide to Flashing via Fastboot MetroPCS Moto One 5G Ace XT2113 [Qualcomm Version]
Hope this helps my fellow TMobile and subdiary acolytes and othoers. I have flashed and reflashed my phone with different variant roms trying to force Write status and beta testing scripts for @lebigmac on our device so it's pretty straightforward now.
I will try and answer questions if I can or point you in the right direction.
Click to expand...
Click to collapse
Question I keep seeing you have to use adb to fix if messed up, sorry not a question yet but that's wrong. When I did it I think I mixed up my moto g stylus boot.img and got a boot loop. I flashed stock boot.img and it came up with a screen saying Android os was corrupted try to reboot if didn't work factory reset is needed. Rebooted popped up again hit factory reset and the phone did it for me. Not sure if you knew that, question tho lol sorry, can I patch boot img with magisk and flash to a phone that's not fresh from a factory reset

bobbyp1086 said:
Question I keep seeing you have to use adb to fix if messed up, sorry not a question yet but that's wrong. When I did it I think I mixed up my moto g stylus boot.img and got a boot loop. I flashed stock boot.img and it came up with a screen saying Android os was corrupted try to reboot if didn't work factory reset is needed. Rebooted popped up again hit factory reset and the phone did it for me. Not sure if you knew that, question tho lol sorry, can I patch boot img with magisk and flash to a phone that's not fresh from a factory reset
Click to expand...
Click to collapse
Well, when I rooted the 1st time I got a frozen touchscreen as I didn't have the correct Firmware (as the phone's firmware out of the box auto updated and the firmware that was available did not match its peripherals). So my phone lost ALL TOUCH ability. The way I explain in this guide is what worked for me, as the LHSA tool doesn't help at that stage. And honestly, I think adb is better and more familiar to most Moto folks that have had several devices and got root on them.
If you mixed up your Moto G Stylus boot.img, all you have to do is try and reflash your firmware boot.img and flash it (or if you have root your patched boot.img). I've flashed this phone almost 70 times in 9 days and I normally do not reflash my boot.img as its already patched to the firmware and I'm just starting from scratch. However, I wouldn't advise that on recovery.img that went wrong, just saying. The phone will force a factory reset.
I don't recommend a factory reset for flashing if you're trying to get root. It's best to compile all the files in ADB to make sure they're taking together, and not going after the fact. There is no shutting off DM-Verity at this time, especially without TWRP and a patch for it, and this model is a bit funky about added flashing with this new Dynamic Partition crap.

Articul8Madness said:
Well, when I rooted the 1st time I got a frozen touchscreen as I didn't have the correct Firmware (as the phone's firmware out of the box auto updated and the firmware that was available did not match its peripherals). So my phone lost ALL TOUCH ability. The way I explain in this guide is what worked for me, as the LHSA tool doesn't help at that stage. And honestly, I think adb is better and more familiar to most Moto folks that have had several devices and got root on them.
If you mixed up your Moto G Stylus boot.img, all you have to do is try and reflash your firmware boot.img and flash it (or if you have root your patched boot.img). I've flashed this phone almost 70 times in 9 days and I normally do not reflash my boot.img as its already patched to the firmware and I'm just starting from scratch. However, I wouldn't advise that on recovery.img that went wrong, just saying. The phone will force a factory reset.
I don't recommend a factory reset for flashing if you're trying to get root. It's best to compile all the files in ADB to make sure they're taking together, and not going after the fact. There is no shutting off DM-Verity at this time, especially without TWRP and a patch for it, and this model is a bit funky about added flashing with this new Dynamic Partition crap.
Click to expand...
Click to collapse
That's what mine did, I flashed stock boot, is corrupted my phone says and forced reset, I'm newish to moto, Samsung for many years, had to ditch them tho lol.
I appreciate the help and hope I didn't come across as arguing, more like clarifying. I too prefer adb over anything, only get the rom from tool. Again thanks for info.

bobbyp1086 said:
That's what mine did, I flashed stock boot, is corrupted my phone says and forced reset, I'm newish to moto, Samsung for many years, had to ditch them tho lol.
I appreciate the help and hope I didn't come across as arguing, more like clarifying. I too prefer adb over anything, only get the rom from tool. Again thanks for info.
Click to expand...
Click to collapse
If your bootloader is unlocked the only way you should have gotten the corruption is if you flashed an incompatible firmware. Mine came with MetroPCS but I've flashed RETUS and RETEU well. I'd stray from any VZW or ATT software just because you can't trust their firmware won't lock down the bootloader.
Or maybe the software just didn't download well. Try re-downloading it . I've had a bad download mess up a flash before.

I think it's cause 1 magisk wasn't installed and 2i used a different phone to patch

bobbyp1086 said:
I think it's cause 1 magisk wasn't installed and 2i used a different phone to patch
Click to expand...
Click to collapse
You have to install Magisk and patch on the phone in question since it's looking for that firmware and that phone's peripherals. You can't use another phone - that's a no no. This ain't Gingerbread, lol.

Articul8Madness said:
You have to install Magisk and patch on the phone in question since it's looking for that firmware and that phone's peripherals. You can't use another phone - that's a no no. This ain't Gingerbread, lol.
Click to expand...
Click to collapse
I'm fairly new to magisk, just recently in past year or so stopped using supersu. Not by choice lol but upgraded my note 4 lmao. So as far as the script for read and write, never flashed and after I got magisk, no modules only su permissions, fx did mount /
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and fix file permissions, it's in settings

bobbyp1086 said:
I'm fairly new to magisk, just recently in past year or so stopped using supersu. Not by choice lol but upgraded my note 4 lmao. So as far as the script for read and write, never flashed and after I got magisk, no modules only su permissions, fx did mount /View attachment 5279427View attachment 5279429View attachment 5279431View attachment 5279433 and fix file permissions, it's in settings
Click to expand...
Click to collapse
Having Root on this device is not going to magically fix the fact that Android 10 on ALL DEVICES is READ ONLY. You will have to go to @lebigmac or @munjeni and try their R/W mount scripts to get true root access. Munjeni's V2 worked for me. He's on V7 now. LeBigMac has been hard at work trying to get us up and running with his script, but we have Super partitions AND A/B. So it's taking some time.

Articul8Madness said:
Having Root on this device is not going to magically fix the fact that Android 10 on ALL DEVICES is READ ONLY. You will have to go to @lebigmac or @munjeni and try their R/W mount scripts to get true root access. Munjeni's V2 worked for me. He's on V7 now. LeBigMac has been hard at work trying to get us up and running with his script, but we have Super partitions AND A/B. So it's taking some time.
Click to expand...
Click to collapse
I am not familiar with either but take it that's it's not an easy task. Should I run v2 or v7 then? Moto one g ace metro.
I was fooled by the trickery, I thought something seemed off with the root on modern phone's.

I just bought a new Moto One 5G ace and was wondering where I can find the stock T-Mobile Firmware variants to prevent bricking?

I successfully rooted it with Magisk patched and ready to go. Unfortunately for the time being the phone won't bypass safety net even with MagiskHide. It just won't work but I'm really happy this phone can be unlocked

bobbyp1086 said:
I am not familiar with either but take it that's it's not an easy task. Should I run v2 or v7 then? Moto one g ace metro.
I was fooled by the trickery, I thought something seemed off with the root on modern phone's.
Click to expand...
Click to collapse
Android 10 is very challenging. It is easy to root but it is a trickable root with a false sense of root since Google locked all Android 10 and newer as Read Only on the System with this super partition crap trying to be Apple.

Skel40 said:
I just bought a new Moto One 5G ace and was wondering where I can find the stock T-Mobile Firmware variants to prevent bricking?
Click to expand...
Click to collapse
Check my guide. I posted link to where the repository is.

Skel40 said:
I successfully rooted it with Magisk patched and ready to go. Unfortunately for the time being the phone won't bypass safety net even with MagiskHide. It just won't work but I'm really happy this phone can be unlocked
Click to expand...
Click to collapse
You will not pass safety net because you've rooted it and Android 10 will block it. It isn't necessary, especially if you delete all Google stuff and their tracking Covid crap.

Articul8Madness said:
Having Root on this device is not going to magically fix the fact that Android 10 on ALL DEVICES is READ ONLY. You will have to go to @lebigmac or @munjeni and try their R/W mount scripts to get true root access. Munjeni's V2 worked for me. He's on V7 now. LeBigMac has been hard at work trying to get us up and running with his script, but we have Super partitions AND A/B. So it's taking some time.
Click to expand...
Click to collapse
Hi @Articul8Madness. Thanks for mentioning me
There's a Motorola user who recently got my script to work using the troubleshooting repair script that I posted here
It turns out the lpmake arguments that are auto-generated by the original script were flawless and were not the root cause of the unidentified lpmake error that some Motorola users were experiencing at the end of the original script. According to @Xiaoleng the error was most likely caused by some kind of new Motorola security feature that prevents the terminal command from executing if the arguments are too long. Go figure.
And he was even able to fastboot flash the super_fixed.bin in one piece without having to first split it up into chunks. That's a huge surprise to me. I always thought Motorola users can only fastboot flash super sparsechunks?!
Please feel free to give it a try and report back your results. Thanks. Good luck!

How To Guide Safely convert regions (includes T-Mobile) as well as restore the ability to use OOS12 after using Indian MSM to recover from a brick (Windows only)

It seems lots of us have had to use the India 9 Pro MSM to recover our devices and in the process, we lose the ability to go back to OOS12 or ROMs based on that firmware because the touchscreen stops working and also trying to convert T-Mobile variants, the fastboot scripts are just bricking them. Well I found a fix for these issues. Those who just want to convert can skip the MSM Tool process and get right to the conversion process as long as they're already running OOS11.
First thing is first, you need to be on OOS11. If you have a T-Mobile variant and you have flashed it with India firmware, you have to use a modded T-Mobile MSM: https://forum.xda-developers.com/t/...ariant-flashing-as-well.4454357/post-87050821
If you have a T-Mobile variant that hasn't used the Indian 9 Pro MSM Tool, is on OOS12, and you're just wanting to convert, you need this tool: https://forum.xda-developers.com/t/oneplus-9-11-2-22-2-t-mobile-msm-download-tool.4276119/
If you have a global variant or a global variant that has been flashed with Indian firmware, you can use this MSM (choose O2 for global or India for India in the Target dropdown, check Sha256, uncheck use lite firehose, it's a multi-target MSM Tool): https://mega.nz/file/ZWtGxTSb#UZ6aSOR2UTYrCao2fQNJ1IN5LSxPNBOxzel1kihnnJs
If you don't know how to use the MSM Tool, there are other guides around here, that's outside of the scope of this post.
Once you are back on OOS11, unlock the bootloader. We also need USB debugging enabled.
Now we need a tool called Fastboot Enhance. This wonderful tool allows you to directly flash OTAs from fastbootd and it doesn't have the same brick risk that flashing with fastboot scripts does.
Download it and unzip it somewhere.
Next we need the OOS11 global downgrade package (or whatever region you are wanting to switch to, global is recommended for T-Mobile variants) from here: https://forum.xda-developers.com/t/oneplus-9-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4254579/
Fire up command prompt in the folder you have your platform tools and run:
adb reboot fastboot (if you do adb reboot bootloader you will then need to type fastboot reboot fastboot to get to fastbootd)
This will take you into fastbootd. It will have a screen that has three different languages to choose from on it. Go ahead and fire up Fastboot Enhance now.
It may take a few seconds for the app to recognize the device but when you see it in the list, double-click it to get to the main screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Check that it says that the device is in fastbootd. Now we just need to click Flash Payload.bin and choose the OTA we downloaded earlier (we don't even need to extract the zip, the app does that for us). If it pops up with an unrecognized partitions error, you're either not in fastbootd, you didn't MSM back to stock (you cannot do this with a custom recovery), or you grabbed an OOS12 OTA. Do not continue and check that everything is correct otherwise you will brick and have to start all over with the MSM Tool. Likewise, if it pops up an alert about cow partitions, don't continue. Go to the partitions screen and search for cow and delete them all.
Once it's done, boot the device, factory reset it in the settings (this is mandatory as Fastboot Enhance does not erase the device like a normal downgrade would do and this can cause problems), set it back up, and then do the OTA process to get back to where you want to go.

Hey bud. So I ended up having too india again. After flashing nameless, it locked up completely. I followed along, but maybe I made a mistake around this point?
Once I was able to boot into India, i just used another msmtoolkit, this successfully converted my Pro to the proper OP 9 5g (the cutout for the cam was aligned so it worked) and i was now on 11.2.10.10
i then let the phone just OTA itself to Android 12.1 c.48
this is when i attempted to get into the latest nameless ROM that requires us to go from OOS 11 based system for the tom to A12.
did i mess up? Should i have flashed 12.1 again?
because the additional flash requirements were fairly straight forward. .
i unlocked the bootloader and then re-enabled /adb debugging the 12.1 and rebooted to bootloader
i flashed the 3 images i extracted from the payload of the latest 12.1 nameless zip and flashed them
fastboot flash boot boot.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
Click to expand...
Click to collapse
while in the same fastboot, i selected recovery boot. i was in the lineage recovery system, this is where i formatted and sideloaded in the same session
when i rebooted i was qualcom killed. could sitll fastboot but nothing would take so i just started over. i am now on my 2nd toolkit flash (india-pro to non-pro global.
i may just stick with the latest release that doesnt require 12. it doesnt help that im 2 days no sleep (unrelated but not helping) but even saying that, i feel i had most of what was required done, but im a big dummy so who knows
youre knowledge is sexy

THANK YOU SIR, true gentleman. Your post I guess was the only one convincing enough that it was finally brushed through the beta testing phase enough that it would be worth trying. No real risk here considering its just using that awesome tool you mentioned in the post, which i've never heard of. will be using for now on. Dunno about any testing with this method so i thought i would owe the community my post. i saw the sahara error post not too long ago talking about a fix with no testing yet xD that made me laugh honestly. But yeah my phone is now converted global through payload.bin flash in fastbootd. Tmo Variant had me & my girls phone networked unlocked through the one guy that was doing it for free on here a while back.. then applied for unlock code and did it officially, never tried to convert due to brick concerns, so i had the easy route through the methods involved in this post, considering i was still on oos 11 with bootloader unlocked when reading this. anyways, i think its safe to say its fixed pretty hyped to flash roms now and not get bootlooped and excited to see where this variant is gonna go! thanks again mate.

applyscience said:
Hey bud. So I ended up having too india again. After flashing nameless, it locked up completely. I followed along, but maybe I made a mistake around this point?
Once I was able to boot into India, i just used another msmtoolkit, this successfully converted my Pro to the proper OP 9 5g (the cutout for the cam was aligned so it worked) and i was now on 11.2.10.10
i then let the phone just OTA itself to Android 12.1 c.48
this is when i attempted to get into the latest nameless ROM that requires us to go from OOS 11 based system for the tom to A12.
did i mess up? Should i have flashed 12.1 again?
because the additional flash requirements were fairly straight forward. .
i unlocked the bootloader and then re-enabled /adb debugging the 12.1 and rebooted to bootloader
i flashed the 3 images i extracted from the payload of the latest 12.1 nameless zip and flashed them
while in the same fastboot, i selected recovery boot. i was in the lineage recovery system, this is where i formatted and sideloaded in the same session
when i rebooted i was qualcom killed. could sitll fastboot but nothing would take so i just started over. i am now on my 2nd toolkit flash (india-pro to non-pro global.
i may just stick with the latest release that doesnt require 12. it doesnt help that im 2 days no sleep (unrelated but not helping) but even saying that, i feel i had most of what was required done, but im a big dummy so who knows
youre knowledge is sexy
Click to expand...
Click to collapse
Did you use the copy partitions zip? You will brick if you don't do that after a MSM.
Process is:
MSM
Upgrade to C.48
Extract boot, dtbo, and vendor_boot from ROM
Fastboot flash dtbo, vendor_boot, and boot in that order
Reboot to recovery
Factory reset
Run copy partitions script
Reboot recovery
Flash ROM
Reboot
It shouldn't brick if you follow that process exactly.
zacattackkc said:
THANK YOU SIR, true gentleman. Your post I guess was the only one convincing enough that it was finally brushed through the beta testing phase enough that it would be worth trying. No real risk here considering its just using that awesome tool you mentioned in the post, which i've never heard of. will be using for now on. Dunno about any testing with this method so i thought i would owe the community my post. i saw the sahara error post not too long ago talking about a fix with no testing yet xD that made me laugh honestly. But yeah my phone is now converted global through payload.bin flash in fastbootd. Tmo Variant had me & my girls phone networked unlocked through the one guy that was doing it for free on here a while back.. then applied for unlock code and did it officially, never tried to convert due to brick concerns, so i had the easy route through the methods involved in this post, considering i was still on oos 11 with bootloader unlocked when reading this. anyways, i think its safe to say its fixed pretty hyped to flash roms now and not get bootlooped and excited to see where this variant is gonna go! thanks again mate.
Click to expand...
Click to collapse
Awesome, glad that it worked for you! There were two other testers before you as well as myself that have confirmed this method works, I guess I should have put that in the post. Thanks for being a guinea pig

question; so now that i did it through advanced boot app, does that mean my phone is officially seen as a global one? can i use global regular msm? can i use fastboot payload files for global, ect?

zacattackkc said:
question; so now that i did it through advanced boot app, does that mean my phone is officially seen as a global one? can i use global regular msm? can i use fastboot payload files for global, ect?
Click to expand...
Click to collapse
So your phone will be seen as global by OTAs but not the MSM. You would have to use a modded MSM Tool that flashes global firmware while targeting your device model.

EtherealRemnant said:
So your phone will be seen as global by OTAs but not the MSM. You would have to use a modded MSM Tool that flashes global firmware while targeting your device model.
Click to expand...
Click to collapse
damn.. that seems to be the culprit of everyone's hard brick.. so what about fastboot flashing oem software for global? I'm guessing that's not a problem because otas are of similar format, but just in a smaller package because it's adding only the updated parts instead of the full ROM.. and is this enhanced fastboot app an alternative to using msmtool and then unlocking bootloader and then flashing custom roms? kinda seems like it would be. and as a matter of fact after using the enhanced fastboot tool I went ahead and put it into fastbootd and flashed payload and it wouldn't boot at first. The app itself gave me an error regarding some cow partitions (really strange and very new concept for me) and told me that I could possibly fix everything if I deleted the cow partitions so I did and then formatted data and it booted into nameless AOSP. This might be the new way to flash custom roms due to the simple fact that it's way quicker than having to use NSM tool and then unlock bootloader and then do all the intricate flashing custom ROM parts. Just put in a fast boot d and flash just always have to make sure you format data afterwards to decrypt. This hasn't been fully tested at least not that I'm aware of

zacattackkc said:
damn.. that seems to be the culprit of everyone's hard brick.. so what about fastboot flashing oem software for global? I'm guessing that's not a problem because otas are of similar format, but just in a smaller package because it's adding only the updated parts instead of the full ROM.. and is this enhanced fastboot app an alternative to using msmtool and then unlocking bootloader and then flashing custom roms? kinda seems like it would be. and as a matter of fact after using the enhanced fastboot tool I went ahead and put it into fastbootd and flashed payload and it wouldn't boot at first. The app itself gave me an error regarding some cow partitions (really strange and very new concept for me) and told me that I could possibly fix everything if I deleted the cow partitions so I did and then formatted data and it booted into nameless AOSP. This might be the new way to flash custom roms due to the simple fact that it's way quicker than having to use NSM tool and then unlock bootloader and then do all the intricate flashing custom ROM parts. Just put in a fast boot d and flash just always have to make sure you format data afterwards to decrypt. This hasn't been fully tested at least not that I'm aware of
Click to expand...
Click to collapse
So honestly I haven't wanted to mess with it too much because it's such a chore to MSM and set everything back up. I can confirm the conversion works as long as you don't ignore any errors and continue (as you found out yourself with the cow files) but as for switching between custom ROMs, fastbootd is part of the custom recovery that we use to flash these ROMs and I don't know if it's possible to get a full flash using that custom recovery. When I tried to use an OOS12 OTA to skip having to use the MSM Tool to go back to stock, I got a partitions error and it rebooted to fastboot. Upon trying to flash the stock boot, dtbo, and vendor_boot, it bricked. I decided it was more important to figure out how to help people with their initial conversion process and I was frustrated because this particular brick was refusing to go into edl until I putzed around with the phone for a few minutes and managed to get it. It just isn't worth me possibly having an unrecoverable brick so I didn't mess with it any further.
In theory though, moving between custom ROMs using the same base firmware should be fine. People will have to test and find out.

EtherealRemnant said:
So honestly I haven't wanted to mess with it too much because it's such a chore to MSM and set everything back up. I can confirm the conversion works as long as you don't ignore any errors and continue (as you found out yourself with the cow files) but as for switching between custom ROMs, fastbootd is part of the custom recovery that we use to flash these ROMs and I don't know if it's possible to get a full flash using that custom recovery. When I tried to use an OOS12 OTA to skip having to use the MSM Tool to go back to stock, I got a partitions error and it rebooted to fastboot. Upon trying to flash the stock boot, dtbo, and vendor_boot, it bricked. I decided it was more important to figure out how to help people with their initial conversion process and I was frustrated because this particular brick was refusing to go into edl until I putzed around with the phone for a few minutes and managed to get it. It just isn't worth me possibly having an unrecoverable brick so I didn't mess with it any further.
In theory though, moving between custom ROMs using the same base firmware should be fine. People will have to test and find out.
Click to expand...
Click to collapse
ive been playing with them for the last 20 hours almost nonstop. im back to being tmobile but no msm tool (yet) will work with it. I tried almost every tmobile msm and a plethora of others have yet to work with it since. i also cant get my unlock_code.bin to work since i think somehow the code dont match with the region that it was applied with was. so i cant unlock my bootloader to get any conversion scripts or flashing commands to work. fastbootenhanced doesn't work either. i dont know what to do, please help me cuz i goofed hard as hell somewhere.

YourLocalDund33 said:
ive been playing with them for the last 20 hours almost nonstop. im back to being tmobile but no msm tool (yet) will work with it. I tried almost every tmobile msm and a plethora of others have yet to work with it since. i also cant get my unlock_code.bin to work since i think somehow the code dont match with the region that it was applied with was. so i cant unlock my bootloader to get any conversion scripts or flashing commands to work. fastbootenhanced doesn't work either. i dont know what to do, please help me cuz i goofed hard as hell somewhere.
Click to expand...
Click to collapse
Is the MSM saying device not match image, is it an unsupported target TMO error, what's the error?

EtherealRemnant said:
Is the MSM saying device not match image, is it an unsupported target TMO error, what's the error?
Click to expand...
Click to collapse
the msm is saying its a device mismatch and it thinks its the Indian variant but everything else is T-Mobile (stock), sorry about the late reply, its a holiday for me here.
Edit: I am Android version 12 now on T-Mobile, but I trying to get back to global rooted if that helps any with where I'm wanting to go with it
Edit 2: when I tried to use the multi msm tool provides I couldn't get O2 to show as an option anywhere, only Indian again.

YourLocalDund33 said:
the msm is saying its a device mismatch and it thinks its the Indian variant but everything else is T-Mobile (stock), sorry about the late reply, its a holiday for me here.
Edit: I am Android version 12 now on T-Mobile, but I trying to get back to global rooted if that helps any with where I'm wanting to go with it
Edit 2: when I tried to use the multi msm tool provides I couldn't get O2 to show as an option anywhere, only Indian again.
Click to expand...
Click to collapse
If it thinks it's an Indian variant, you use my modded MSM and select India for the target.

I recovered my bricked LE2110 from Oneplus 9 pro Indian msm tools and I wish to restore it to Oneplus 9 global rom. I try to use the "Fastboot enhance (version 1.3)" to flash the payload.bin into my LE2110, but I cannot find any "lfash" button ! The only button I can see is "Extract Image", am I missing something ? I try local upgrade but it cannot find the firmware file ! Please help !

EtherealRemnant said:
If it thinks it's an Indian variant, you use my modded MSM and select India for the target.
Click to expand...
Click to collapse
Thats why i edited my post, I tried to use the modded tool but it only gives the option for the indian variant. the 02 option is not there boss.

YourLocalDund33 said:
Thats why i edited my post, I tried to use the modded tool but it only gives the option for the indian variant. the 02 option is not there boss.
Click to expand...
Click to collapse
Which mod are you using? There have been a bunch posted in this forum.

EtherealRemnant said:
Which mod are you using? There have been a bunch posted in this forum.
Click to expand...
Click to collapse
the one from the op. its the one thats said its multi support for indian and global

YourLocalDund33 said:
the one from the op. its the one thats said its multi support for indian and global
Click to expand...
Click to collapse
Try this one.
3.56 GB file on MEGA
mega.nz
That one is also multi target. Both of these have been tested, I don't know why it's not working for you. You can also try not selecting a target and see what happens, I have found I don't always need to select the target if my device firmware hasn't been too corrupted.
Beware that with this one, you can't unlock the bootloader until after you go to OOS12 because OnePlus bugged the erase script on 11.2.10.10.

EtherealRemnant said:
Try this one.
3.56 GB file on MEGA
mega.nz
That one is also multi target. Both of these have been tested, I don't know why it's not working for you. You can also try not selecting a target and see what happens, I have found I don't always need to select the target if my device firmware hasn't been too corrupted.
Beware that with this one, you can't unlock the bootloader until after you go to OOS12 because OnePlus bugged the erase script on 11.2.10.10.
Click to expand...
Click to collapse
I'm already OOS12. still couldn't unlock bootloader. I was on chat with Oneplus support for an hour or so just a few minutes ago. They were a little slow with understanding the situation (didn't mention to them using a lot of modded msm tools) but I did tell them I used the tool to reset it to stock. that and my unlock_code.bin was no longer working. They put me on chat with the higher team and then the supervisor herself overtook chat and had a look at when my original application for my phone was. She decided she will reissue me a new code and said after 24-48hrs ill get the new code via email. How familiar are you with the erase script with the msm tool?

YourLocalDund33 said:
I'm already OOS12. still couldn't unlock bootloader. I was on chat with Oneplus support for an hour or so just a few minutes ago. They were a little slow with understanding the situation (didn't mention to them using a lot of modded msm tools) but I did tell them I used the tool to reset it to stock. that and my unlock_code.bin was no longer working. They put me on chat with the higher team and then the supervisor herself overtook chat and had a look at when my original application for my phone was. She decided she will reissue me a new code and said after 24-48hrs ill get the new code via email. How familiar are you with the erase script with the msm tool?
Click to expand...
Click to collapse
It's not the MSM Tool that's borked, it's the ROM itself.

Looking for a stock c61 LE2115 Global boot.img (oneplus 9)
I overwrote mine trying to root and now I can't get the phone to boot back into c61. I have access to fastboot though

Question Your device is corrupt. Oneplus 9

I tried putting the beta of OOS13 on my Oneplus and now i get that error message and ive been trying for so long.
the serial number is fb7b98a9

Flash by edl if you can't do it then pm I'll fix it by tv

Could you elaborate a little further? Are you just not able to flash OO13 beta or has the attempt of doing so corrupted your device completely?
If the latter, You will most likely need to flash an emergency MSMToolkit. It is an Indian OP9Pro variant but will bring your device back from the dead. Once that is done, you will just run a proper MSMToolkit and be right as rain.
EtherealRemnant wrote up an amazing guide on how to carry this out. SO amazing that its the only guide stickied on the 9 forums, currently.
- Here is a mega hosted copy of the Indian OP9Pro MSMToolkit,
I can personally vouch for the guide, as my 9 went into a bricked state with vague errors about corrupted system. I tried every toolkit, recovery and ROM and nothing worked. Thats when EthRem came to my rescue. Hopefully his work can come to yours as well.
and if that isn't what you meant and are just dying to get into OOS13, id just stick with one of the many A13 ROMs currently available. OOS13 is beautiful but, i just cant honestly suggest using Oneplus software anymore.
Good luck

applyscience said:
Could you elaborate a little further? Are you just not able to flash OO13 beta or has the attempt of doing so corrupted your device completely?
If the latter, You will most likely need to flash an emergency MSMToolkit. It is an Indian OP9Pro variant but will bring your device back from the dead. Once that is done, you will just run a proper MSMToolkit and be right as rain.
EtherealRemnant wrote up an amazing guide on how to carry this out. SO amazing that its the only guide stickied on the 9 forums, currently.
- Here is a mega hosted copy of the Indian OP9Pro MSMToolkit,
I can personally vouch for the guide, as my 9 went into a bricked state with vague errors about corrupted system. I tried every toolkit, recovery and ROM and nothing worked. Thats when EthRem came to my rescue. Hopefully his work can come to yours as well.
and if that isn't what you meant and are just dying to get into OOS13, id just stick with one of the many A13 ROMs currently available. OOS13 is beautiful but, i just cant honestly suggest using Oneplus software anymore.
Click to expand...
Click to collapse
applyscience said:
Could you elaborate a little further? Are you just not able to flash OO13 beta or has the attempt of doing so corrupted your device completely?
If the latter, You will most likely need to flash an emergency MSMToolkit. It is an Indian OP9Pro variant but will bring your device back from the dead. Once that is done, you will just run a proper MSMToolkit and be right as rain.
EtherealRemnant wrote up an amazing guide on how to carry this out. SO amazing that its the only guide stickied on the 9 forums, currently.
- Here is a mega hosted copy of the Indian OP9Pro MSMToolkit,
I can personally vouch for the guide, as my 9 went into a bricked state with vague errors about corrupted system. I tried every toolkit, recovery and ROM and nothing worked. Thats when EthRem came to my rescue. Hopefully his work can come to yours as well.
and if that isn't what you meant and are just dying to get into OOS13, id just stick with one of the many A13 ROMs currently available. OOS13 is beautiful but, i just cant honestly suggest using Oneplus software anymore.
Good luck
Click to expand...
Click to collapse
The tool that you linked doesnt have o2 as he is saying in the guide.
Also yes, i tried flashing OOS13 and it just corrupted my device i've been endlessly working to fix it all day

SubColdSnow said:
The tool that you linked doesnt have o2 as he is saying in the guide.
Also yes, i tried flashing OOS13 and it just corrupted my device i've been endlessly working to fix it all day
Click to expand...
Click to collapse
1st of all flash with op9pro india msm with uncheck sah and check lite firehorse if u have hard bricked ur device then the next steps as mention above

rizzmughal said:
1st of all flash with op9pro india msm with uncheck sah and check lite firehorse if u have hard bricked ur device then the next steps as mention above
Click to expand...
Click to collapse
i tried and just get device does not match image

SubColdSnow said:
i tried and just get device does not match image
Click to expand...
Click to collapse
try it again. if anything, you will be attempting on the other slot. Many haves had issues and it just started working.
it could have been slot related, or possibly some minor detail that is finicky. (ex. you usually want to start the msmtoolkit and let it stay in the "waiting for device" phase and plug in your phone (which should be in EDL mode . youll know by the peeps of it habitually connecting/disconnecting on your PC)
assure you have india selected, assure you have the proper conditionals on/off per the guide's explication.
Assure you have the qualcom drivers installed, and they reflect the naming convention.
follow along the guide again and Just keep attempting it and don't get discouraged. Part of the reason people offer guides here is that they themselves failed many times until they got they figured it out and are trying to save people from it.
youll get it, dont worry.

I had this problem because I flashed a custom kernel on a custom rom today

SubColdSnow said:
i tried and just get device does not match image
Click to expand...
Click to collapse
try the modded msm tool. it worked for me.