Database Info

Delete

??

Can anyone confirm this working before I go ruin my phone haha

Clank50AE said:
Can anyone confirm this working before I go ruin my phone haha
Click to expand...
Click to collapse
You won't. Enjoy the better software!

suzook said:
You won't. Enjoy the better software!
Click to expand...
Click to collapse
Thank you for the Swift reply! My RM3 is glitchy as albeit and I'd like more stability. I know it's just the OS but it's very annoying.

Looks great. There's a big red warning to your thread tho that don't use if you're phone is Red Magic 3 it will damage the motherboard. Hmm

Any one besides OP tried this ?

leipnacht said:
Looks great. There's a big red warning to your thread tho that don't use if you're phone is Red Magic 3 it will damage the motherboard. Hmm
Click to expand...
Click to collapse
Everything is the same, other than the CPU. Nothing will happen. If people want to stick with the buggy rm3 sw, than go ahead. Not sure why you would want to.

so if rm3s fw works with rm3, can we try to install it thro twrp???

hagouba said:
so if rm3s fw works with rm3, can we try to install it thro twrp???
Click to expand...
Click to collapse
TWRP states ERROR 7 when i tried this
LE: Avoid using this so called GUIDE, this is a bad joke... I tried using the Tool on RM3 and the cmd remains stuck with at Downloading firehouse program... then after some time "Error]: Download programer FAIL.Please check phone status and reset into edl mode and try again.
Software download FAIL.Press any key exit:
I also swapped USB's, different cable and so on... COM 5 6 and 7 were used

@JerryYin I completely understand now why you were not sharing the tool ???

hagouba said:
so if rm3s fw works with rm3, can we try to install it thro twrp???
Click to expand...
Click to collapse
Absolutely not. Different sized partitions. You need to use the tool 1st.

Alex4455 said:
TWRP states ERROR 7 when i tried this
LE: Avoid using this so called GUIDE, this is a bad joke... I tried using the Tool on RM3 and the cmd remains stuck with at Downloading firehouse program... then after some time "Error]: Download programer FAIL.Please check phone status and reset into edl mode and try again.
Software download FAIL.Press any key exit:
I also swapped USB's, different cable and so on... COM 5 6 and 7 were used
Click to expand...
Click to collapse
Bad joke? Maybe you dont know what you are doing.
I did 3 phones. No issues. Its on your end.

suzook said:
Bad joke? Maybe you dont know what you are doing.
I did 3 phones. No issues. Its on your end.
Click to expand...
Click to collapse
You don't realize this is not a GUIDE, this is a statement and you are telling us to use the tool for something.... You did not provide steps, video, guide, pre-requirements, nothing
This is not my 1st time using this tool so i know how it works, i kept crashing my CN <-> EU roms and needed to use the tool
So, why don't you provide with these 3 x RM3's a video on how did you use the tool, on what hardware did you use it (PC hardware, maybe Ryzen is overkill for the app and does not know how to use the scripts), what drivers you have installed (because this tool does not provide drivers vs the RM3 tool that provides) and all that kind of stuff ?

Alex4455 said:
You don't realize this is not a GUIDE, this is a statement and you are telling us to use the tool for something.... You did not provide steps, video, guide, pre-requirements, nothing
This is not my 1st time using this tool so i know how it works, i kept crashing my CN <-> EU roms and needed to use the tool
So, why don't you provide with these 3 x RM3's a video on how did you use the tool, on what hardware did you use it (PC hardware, maybe Ryzen is overkill for the app and does not know how to use the scripts), what drivers you have installed (because this tool does not provide drivers vs the RM3 tool that provides) and all that kind of stuff ?
Click to expand...
Click to collapse
I'll delete the thread. I was trying to do people a favor. Didn't realize I needed to hold people's hands.

suzook said:
I'll delete the thread. I was trying to do people a favor. Didn't realize I needed to hold people's hands.
Click to expand...
Click to collapse
You shouldn't listen to aggressive people, they're the minority, thanks for whatever you were trying to do. I would like to give it a read if you still have the guide saved

If you speak the truth then please provide us with a picture or anything. First I don't know if rm3s fw is more stable than rm3 but if it is, I would definitely come back to stock rom as I missed the fan and triggers very much.

Sangyedorje said:
You shouldn't listen to aggressive people, they're the minority, thanks for whatever you were trying to do. I would like to give it a read if you still have the guide saved
Click to expand...
Click to collapse
Aggressive people ? Guide ?
The Guide was like this:
Use this tool from this thread (https://forum.xda-developers.com/red-magic-3/how-to/tool-nubia-red-magic-3s-unbirck-tool-t4025207) and enjoy the much more stable firmware of the RM3S "END"
And like i said in my previous posts, i asked him for a detailed explanation because what he said does not work, it always ends up with sahara_rx_data:237, i even tried on my laptop with with windows 7 fresh install
Then he suddenly reacts like a 12 years old and deletes everything

Alex4455 said:
Aggressive people ? Guide ?
The Guide was like this:
Use this tool from this thread (https://forum.xda-developers.com/red-magic-3/how-to/tool-nubia-red-magic-3s-unbirck-tool-t4025207) and enjoy the much more stable firmware of the RM3S "END"
And like i said in my previous posts, i asked him for a detailed explanation because what he said does not work, it always ends up with sahara_rx_data:237, i even tried on my laptop with with windows 7 fresh install
Then he suddenly reacts like a 12 years old and deletes everything
Click to expand...
Click to collapse
Well, you said his post was a bad joke that comes off as aggressive, even if the guide is dangerously unexplained he didn't wrote it with malicious intent so you shouldn't talk to a fellow forum member that way.
I think he is onto something, it seems reasonable that if RM3 and RM3S share so much hardware in common their firmwares won't differ that much either.

Sangyedorje said:
Well, you said his post was a bad joke that comes off as aggressive, even if the guide is dangerously unexplained he didn't wrote it with malicious intent so you shouldn't talk to a fellow forum member that way.
I think he is onto something, it seems reasonable that if RM3 and RM3S share so much hardware in common their firmwares won't differ that much either.
Click to expand...
Click to collapse
Bad Joke of a guide is considered aggressive these days ? Whoaw, the newer generation is way over sensitive
Besides the so called guide, i lost almost 4-5 hours investigating this so called guide with error fixing and so on, here is what worked for me
The below "what worked for me steps" resulted and complete WIPE of the device !
I have no responsibility over bricked devices, i simply shared what some one did not bother to "info"
Do this on your own RISK !
What worked for me as on flashing the RM3s firmware on my RM3 is that 1st of all you need Windows 8.1, i tried on different hardware AMD and Intel with the Unbrick Tool RM3S and does not work on Windows 10 no matter what (windows 7 did not worked on Ryzen and my Laptop)
1. Have Windows 8.1 X64 (i used my Intel Celeron Laptop)
2. Have the drivers for the QDLoader HS-USB Driver_64bit_Setup
3. Download the tool for the Unbrick RM3S
4. Install the QDLoader drivers on the newly installed windows 8.1 and choose to restart
5. Turn the phone off and leave it like that until the Unbrick tool is ready
6. Run the Tool's exe and let it extract (the RM3S Unbrick Tool)
7. Power on the Phone holding PWR and Vol Down
8. Connect to a USB 2.0 port directly in to the motherboard with a quality cable
9. Select EDL mode from the Bootloader menu of the phone
10. Search within Device manager the phone's COM port
11. When the tool is ready, input the COM Number and select continue and install
These steps worked for me and phone booted fine... Conclusion is: I went Back to CN V2.38 and restored backup via TWRP, no performance gain, the device is still seen as RM3 but running with RM3S firmware
GPU and CPU frequency is of a normal SD855
My personal opinion is: This is a waste of time after all the hype I've gotten in to believing it would run like a SD855+

Alex4455 said:
Bad Joke of a guide is considered aggressive these days ? Whoaw, the newer generation is way over sensitive
Besides the so called guide, i lost almost 4-5 hours investigating this so called guide with error fixing and so on, here is what worked for me
The below "what worked for me steps" resulted and complete WIPE of the device !
I have no responsibility over bricked devices, i simply shared what some one did not bother to "info"
Do this on your own RISK !
What worked for me as on flashing the RM3s firmware on my RM3 is that 1st of all you need Windows 8.1, i tried on different hardware AMD and Intel with the Unbrick Tool RM3S and does not work on Windows 10 no matter what (windows 7 did not worked on Ryzen and my Laptop)
1. Have Windows 8.1 X64 (i used my Intel Celeron Laptop)
2. Have the drivers for the QDLoader HS-USB Driver_64bit_Setup
3. Download the tool for the Unbrick RM3S
4. Install the QDLoader drivers on the newly installed windows 8.1 and choose to restart
5. Turn the phone off and leave it like that until the Unbrick tool is ready
6. Run the Tool's exe and let it extract (the RM3S Unbrick Tool)
7. Power on the Phone holding PWR and Vol Down
8. Connect to a USB 2.0 port directly in to the motherboard with a quality cable
9. Select EDL mode from the Bootloader menu of the phone
10. Search within Device manager the phone's COM port
11. When the tool is ready, input the COM Number and select continue and install
These steps worked for me and phone booted fine... Conclusion is: I went Back to CN V2.38 and restored backup via TWRP, no performance gain, the device is still seen as RM3 but running with RM3S firmware
GPU and CPU frequency is of a normal SD855
My personal opinion is: This is a waste of time after all the hype I've gotten in to believing it would run like a SD855+
Click to expand...
Click to collapse
Can you tell if it far more stable and less bug than our rm3 fw? As for the performance it depend on device prosessor.

[DISCUSSION] Bypassing Authorization of MSM Download tool of Realme/Oppo

Hello everyone!
So today something that could potentially let users flash/unbrick their phones using the current MSM Download tool came to my mind.
I'm also very sorry if this is the wrong place for this, i'm new to xda.
So as you might know for Realme phones there are people who have authorized account out there and once you pay them they will connect to yoprur computer and then start flashing ocess, online with no verification. I even tried getting my phone flashed but due to them not flashing twice if one package doesn't work my device was bricked (I have A.xx variant and i tried getting B.xx flashed) and i had to send to service center to wait for unbricking process which took over a month, yes you heard it right! They couldn't even repair it with software flashing so they had to replace the whole motherboard.... At least i'm grateful i didn't have to pay for motherboard replacement and it was considered in-warranty.
So yes, again let's go back to our topic and my idea.
What came to my mind is, what happens if i create a virtual machine using VMWare, get an authorized account to login to the application then cut connection of that TeamViewer connection and immediately "Save current state of VM" after someone logs in. Would that account be still logged in? This VM can also be shared with it's own folder as far as I know too! Is there a verification after you login to the app? As far as i know there's only a verification while you login to the app and there isn't anything afterwards which i think is also illogical to do so.
I know and i'm aware Realme can patch this possible "vulnerability" overnight because on the server side, literally everything depends on them (I really hope they don't) but thanks to their habit of not caring about development, releasing broken kernel sources and not even providing official bootloader unlock (even after nearly a year in my case) has come to a point where it's irresistably annoying for me so i decided to think of possible ways to maybe bypass the verification part of the application so that they can flash a firmware as their liking.
It's Android! It had to be free! It had to be allowed to do these type of stuffs to your Android phone! Why? Why? Why Realme?!

daeMysterious said:
Hello everyone!
So today something that could potentially let users flash/unbrick their phones using the current MSM Download tool came to my mind.
I'm also very sorry if this is the wrong place for this, i'm new to xda.
So as you might know for Realme phones there are people who have authorized account out there and once you pay them they will connect to yoprur computer and then start flashing ocess, online with no verification. I even tried getting my phone flashed but due to them not flashing twice if one package doesn't work my device was bricked (I have A.xx variant and i tried getting B.xx flashed) and i had to send to service center to wait for unbricking process which took over a month, yes you heard it right! They couldn't even repair it with software flashing so they had to replace the whole motherboard.... At least i'm grateful i didn't have to pay for motherboard replacement and it was considered in-warranty.
So yes, again let's go back to our topic and my idea.
What came to my mind is, what happens if i create a virtual machine using VMWare, get an authorized account to login to the application then cut connection of that TeamViewer connection and immediately "Save current state of VM" after someone logs in. Would that account be still logged in? This VM can also be shared with it's own folder as far as I know too! Is there a verification after you login to the app? As far as i know there's only a verification while you login to the app and there isn't anything afterwards which i think is also illogical to do so.
I know and i'm aware Realme can patch this possible "vulnerability" overnight because on the server side, literally everything depends on them (I really hope they don't) but thanks to their habit of not caring about development, releasing broken kernel sources and not even providing official bootloader unlock (even after nearly a year in my case) has come to a point where it's irresistably annoying for me so i decided to think of possible ways to maybe bypass the verification part of the application so that they can flash a firmware as their liking.
It's Android! It had to be free! It had to be allowed to do these type of stuffs to your Android phone! Why? Why? Why Realme?!
Click to expand...
Click to collapse
I flashed the stock recovery n stock rom on a RMX1993 Realme X2 that I had rooted already with TWRP.
Everything was fine, till I got the great idea on relocking the bootloader.
As soon as I put the command the device reboot and showed that message with chinese letters n "recovery/boot has been destroyed" etc.
Got no fastboot either, only com port EDL mode works. The next and main problem is I am not authorized to flash roms due to that user/pw in msm tool. I just found this out after bricking the device. Why the hell did I lock the bootloader....
I heard there are websites that offer user/password for msm tool flashing n you need to buy credits for it. I'm not gonna bother nor paying for something that I own and should have the right to fix by myself. Amaz0n will take care from it this time, they'll probably refund.
Tip: Do not relock bootloaders,
and a better one: do not buy realme devices.

Morphine1 said:
I flashed the stock recovery n stock rom on a RMX1993 Realme X2 that I had rooted already with TWRP.
Everything was fine, till I got the great idea on relocking the bootloader.
As soon as I put the command the device reboot and showed that message with chinese letters n "recovery/boot has been destroyed" etc.
Got no fastboot either, only com port EDL mode works. The next and main problem is I am not authorized to flash roms due to that user/pw in msm tool. I just found this out after bricking the device. Why the hell did I lock the bootloader....
I heard there are websites that offer user/password for msm tool flashing n you need to buy credits for it. I'm not gonna bother nor paying for something that I own and should have the right to fix by myself. Amaz0n will take care from it this time, they'll probably refund.
Tip: Do not relock bootloaders,
and a better one: do not buy realme devices.
Click to expand...
Click to collapse
Same mistake as yours, Did you found any fix/bought new phone? Regretting now.

PrateekPanwar64X said:
Same mistake as yours, Did you found any fix/bought new phone? Regretting now.
Click to expand...
Click to collapse
did you find any solution stuck with the same problem

ZUESHACKED said:
did you find any solution stuck with the same problem
Click to expand...
Click to collapse
Yeah, I wrote later in a forum: https://forum.xda-developers.com/t/...tloader-and-no-recovery.4316853/post-86998293

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.

T-Mobile OnePlus 8T stuck in a QualCom loop?

Hello,
So, to start off, I genuinely hate asking for help because it makes me feel like a failure but.... I'm desperate.
Preface; I got my token today to unlock this and I thought it was going to be as simple as it was with my 6 to root or whatever. well...
Cut to me thinking I remembered how to do it, only to get myself into a whirlwind of anxiety because it's been 8 hours now and I am at a loss.
Not sure if I'm just not grasping what I need to do, if my computer has something to do with it, if I'm using the wrong files, etc.
So, I was trying to just root the OOS because I genuinely like that... well some how I ended up installing lineageOS because I kept getting the QualCom error screen, and it wouldn't do anything.
Then, when I finally got lineageos to work, nothing on the phone actually worked. I've tried a million roms now and a dozen or two different version of the OOS... to no avail. I can't even turn the phone on now, it just goes to fastboot immediately.
I just want my tmobile oos back with magisk :'(
-sobs quietly-
Any help is appreciated. I've followed dozens of tutorials and guides and used that MSM thing and absolutely nothing is working. I feel like a complete idiot because all of my previous phones were so smooth to deal with. This, I want to legit throw it through the wall :/
Please help
EDIT: Update! Resolved!
After nearly pulling me hair out for two days... I decided to completely uninstall all my ADB Drivers and Qualcom drivers... Reinstalled everything from SDK AND I used the drivers at the bottom of https://onepluscommunityserver.com/list/Unbrick_Tools/
Those seem to be the only qualcom drivers that worked for me... I've tried probably 10 different ones and these are the ones that work. Follow the instructions that come with it, it's pretty basic but holy hell, it finally let me use MSM and it immediately started installing on the MSM program.

MSM should work.
I have a TMob 8T+5G as well and soft bricked it as well on my first attempt to take OTA after rooting.
MSM tool saved my bacon.
Would you please expand on the MSM efforts?
It should restore the SoC without any regard for the state of the partitions as long as there is no hw failure.

parakleet said:
MSM should work.
I have a TMob 8T+5G as well and soft bricked it as well on my first attempt to take OTA after rooting.
MSM tool saved my bacon.
Would you please expand on the MSM efforts?
It should restore the SoC without any regard for the state of the partitions as long as there is no hw failure.
Click to expand...
Click to collapse
Thanks for the reply!
I have been trying to use MSM all day and I can't get my phone to show up when putting it into EDM. I've fixed the drivers and when in fastboot, it shows up on my device manager as the correct qualcom device, but in the MSM program it shows the COM port that the phone is plugged in to, it just doesn't show the phone, just says waiting for device.
I'm at my wit's end lol. I have tried different cords, different USB ports, etc. x.x

Resolved! See OP!

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.