Develop Bugs

Xiaomi Mi 5 Recovery ROM and Fastboot ROM; MIUI 7

Official Xiaomi MIUI 7
Xiaomi Mi 5
Recovery ROM and Fastboot ROM​
Introduction
This topic will just gather all available MIUI ROM Versions (Fastboot and Recovery) for the Xiaomi Mi 5. I will keep it up to date, as good as possible.
The same information you can get from the official MIUI forum, but as the forum is big, it' s nice to have a short summary here. Please be aware that for the moment there is only the China stable ROM. Included languages are some Chinese + English.
Stable ROM
Waiting for global.
Developer ROM
Waiting for global.
Developer ROM Naming:
It's all about the date. like MIUI6.3.17 is 2016/03/17
Disclaimer
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. P You are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Why this disclaimer
People often fail to read and do stupid stuff. The disclaimer is just here to remind you of this. Mistakes happen, mistakes happen fast. Think before you act.
There is a good amount of guides online on how to flash a Fastboot ROM on a MIUI. But there is something new for locked phones. The old recovery is gone , it got replaced! So be careful, know what you are doing before you do it.

Hope this is helpful to you guys.

will flashing one of these lock the bootloader again? anyone knows?

gajrut said:
will flashing one of these lock the bootloader again? anyone knows?
Click to expand...
Click to collapse
It's up to you.
I unlocked my phone on the first day of use, did loads of updates through stock recovery and mi-flash, and none of it locked my bootloader.
Assuming you do it right: Recovery ROM's won't lock it again
I tested it and so far: Going from 7.2.3 to 7.2.4 to 7.2.5 to 7.2.6 did not lock my phone again.
But if you want to you can use the flash_all_lock.bat or flash_all_lock.sh to lock the bootloader.
Picture of an extracted Fastboot-ROM:
{
"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"
}
These scripst are identical to the flash_all.bat / flash_all.sh up to the following lines:
Additional lines in flash_all_lock:
Code:
...
fastboot %* erase devinfo
...
fastboot %* oem lock
....
So as long as you don't flash using flash_all_lock, you should be fine. And your bootloader should stay unlocked.
But things might change, I only tried it with all available firmware versions, no guarantee for the future. I don't know about that.

Bootloader comes unlocked?

Me_Ashish_ said:
Bootloader comes unlocked?
Click to expand...
Click to collapse
No, the bootloader is locked.
Have a look at this: http://forum.xda-developers.com/mi-5/how-to/unlocking-xiaomi-mi-5-bootloader-t3336243

TheUltrametricSpace said:
It's up to you.
I unlocked my phone on the first day of use, did loads of updates through stock recovery and mi-flash, and none of it locked my bootloader.
Assuming you do it right: Recovery ROM's won't lock it again
I tested it and so far: Going from 7.2.3 to 7.2.4 to 7.2.5 to 7.2.6 did not lock my phone again.
But if you want to you can use the flash_all_lock.bat or flash_all_lock.sh to lock the bootloader.
Picture of an extracted Fastboot-ROM:
These scripst are identical to the flash_all.bat / flash_all.sh up to the following lines:
Additional lines in flash_all_lock:
Code:
...
fastboot %* erase devinfo
...
fastboot %* oem lock
....
So as long as you don't flash using flash_all_lock, you should be fine. And your bootloader should stay unlocked.
But things might change, I only tried it with all available firmware versions, no guarantee for the future. I don't know about that.
Click to expand...
Click to collapse
I tried flashing 7.2.5 & 7.2.6 using mi flash (flash_all_except_storage.bat) tool. MiFlash says success but I think it bootloop. I've waited about half an hour for it to boot. It's just showing mi logo and running three dots at the bottom. How long more should I wait? Any thoughts?

gajrut said:
I tried flashing 7.2.5 & 7.2.6 using mi flash (flash_all_except_storage.bat) tool. MiFlash says success but I think it bootloop. I've waited about half an hour for it to boot. It's just showing mi logo and running three dots at the bottom. How long more should I wait? Any thoughts?
Click to expand...
Click to collapse
I've no idea.

updated. Added developer and latest stable

TheUltrametricSpace said:
updated. Added developer and latest stable
Click to expand...
Click to collapse
Thanks......
fixed the bootloop issue :good:

TheUltrametricSpace said:
Hope this is helpful to you guys.
Click to expand...
Click to collapse
sure will... nothing like being able to slap different ROM's on the device of this calibre.
being in India, we are yet to see the Mi5 here up for sale just yet.
all the previous claimed release dates has whoooooshed by

Can we flash the developer china MIUI or global MIUI from updater, without unlocking bootloader.

updated to 7.2.8; the new developer 6.3.24 will follow as soon it's out.

Hi, i want to flash my Mi5 with fastboot mode
I have downloaded the updated MiFlash (http://bigota.d.miui.com/tools/MiPhone20151028.exe)
and the ROM.
My phone already entered fastboot mode, but it's not detected on MiFlash.
I've attached the screenshot at http://en.miui.com/thread-249284-1-1.html
What's wrong or what is missing?
thank you in advance

Guys you can't post roms that have the Mi-store built in.

zelendel said:
Guys you can't post roms that have the Mi-store built in.
Click to expand...
Click to collapse
Is this up to date?
I read on en.miui.com that Xiaomi takes copyright stuff serious now, but dunno.

Ok stop and think about that for a mine. They take copy rights seriously? They rip off the design of IOS for the software and every other oem on the hardware.
And yes. It is up to date. The Mi-store is a known warez market. It is only in the China based versions of their roms.

zelendel said:
Ok stop and think about that for a mine. They take copy rights seriously? They rip off the design of IOS for the software and every other oem on the hardware.
And yes. It is up to date. The Mi-store is a known warez market. It is only in the China based versions of their roms.
Click to expand...
Click to collapse
Why do you lurk here to post negative remarks everywhere?

kickassdave said:
Why do you lurk here to post negative remarks everywhere?
Click to expand...
Click to collapse
I'm sorry if you find the truth negative. I was just explaining the reasoning behind our stance.

zelendel said:
Ok stop and think about that for a mine. They take copy rights seriously? They rip off the design of IOS for the software and every other oem on the hardware.
And yes. It is up to date. The Mi-store is a known warez market. It is only in the China based versions of their roms.
Click to expand...
Click to collapse
Cut it, and be reasonable!
All companies copy. (So does Apple.)
And the worst evil are phones that ship with a Webbrowser (according to your logic). As web-browser allow to download childporn and other highly highly illegal stuff.
So the question is: Are Web browser banned as they may give access to some stuff or is the user in charge?
Is it in the ends, the users fault if he broke any kind of law?
It's important to keep people aware of it, but don't overreact! Keep it reasonable.

[TOOL][PIXEL 2 XL] TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery)

This is the Pixel 2 XL's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"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"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
​

Cant wait to try it

Toejam1998 said:
Cant wait to try it
Click to expand...
Click to collapse
Tell me if it's work for you

I'll wait for a few others as well

Finally i got a solution for Nexus and Pixel Factory Image flash, now it works perfectly

does this do the critical unlock as well?

razgriz1234 said:
does this do the critical unlock as well?
Click to expand...
Click to collapse
I have integrated "fastboot flashing unlock_critical" for pixel 2 xl only, i have not tested it but it should work

mauronofrio said:
I have integrated "fastboot flashing unlock_critical" for pixel 2 xl only, i have not tested it but it should work
Click to expand...
Click to collapse
ok cool thanks for the quick reply

razgriz1234 said:
ok cool thanks for the quick reply
Click to expand...
Click to collapse
I saw now that i forgot to unlock the flash factory image option for all 4 Pixel, i have released an update to solve that, tell me if it works

This saved my ass last night got bootloop from hell nothing would flash at all run this and boom back in business so like to say thanks for the tool :good:

jaythenut said:
This saved my ass last night got bootloop from hell nothing would flash at all run this and boom back in business so like to say thanks for the tool :good:
Click to expand...
Click to collapse
I'm happy this tool helped you:good:
Do you flash a factory image with this tool?

mauronofrio said:
I'm happy this tool helped you:good:
Do you flash a factory image with this tool?
Click to expand...
Click to collapse
Yes mate

jaythenut said:
Yes mate
Click to expand...
Click to collapse
People like to see feedback and in this thread this is the first

Does this tool work well for Pixel XL2? If I wipe phone to unencrypt, will flashing stock re-encrypt it?

almahix said:
Does this tool work well for Pixel XL2? If I wipe phone to unencrypt, will flashing stock re-encrypt it?
Click to expand...
Click to collapse
I think way early on it was established we can't have it unencrypted once the OS install it's completed, unless something changed or I got it wrong. Lol

almahix said:
Does this tool work well for Pixel XL2? If I wipe phone to unencrypt, will flashing stock re-encrypt it?
Click to expand...
Click to collapse
You can uncrypt your phone but if you.flash a stock rom, the kernel at first boot will automatically encrypt your memory again. There are 2 different encryption, one by code and one with standard image key. At this moment the twrp will automatically uncrypt the system key but you need to manually write the code (if is setted). The tool will uncrypt both method, the flash of stock rom will re-uncrypt with system key but not with code key

mauronofrio said:
You can uncrypt your phone but if you.flash a stock rom, the kernel at first boot will automatically encrypt your memory again. There are 2 different encryption, one by code and one with standard image key. At this moment the twrp will automatically uncrypt the system key but you need to manually write the code (if is setted). The tool will uncrypt both method, the flash of stock rom will re-uncrypt with system key but not with code key
Click to expand...
Click to collapse
Grazie.

Just got my Pixel 2XL the other day and am excited to root and start modding. I have been monitoring this thread just to see what issues people are running into but it looks like not many people are even doing this surprisingly. I mean that's why I bought this Google phone, so I don't have to deal with locked bootloaders that these carriers put in them to discourage rooting. I know this phone is also locked but it's not for the purpose of keeping people from rooting them. I just think that it's so odd that this thread has very little activity.

dricacho said:
I just think that it's so odd that this thread has very little activity.
Click to expand...
Click to collapse
I think it too, but i don't know why.

dricacho said:
Just got my Pixel 2XL the other day and am excited to root and start modding. I have been monitoring this thread just to see what issues people are running into but it looks like not many people are even doing this surprisingly. I mean that's why I bought this Google phone, so I don't have to deal with locked bootloaders that these carriers put in them to discourage rooting. I know this phone is also locked but it's not for the purpose of keeping people from rooting them. I just think that it's so odd that this thread has very little activity.
Click to expand...
Click to collapse
mauronofrio said:
I think it too, but i don't know why.
Click to expand...
Click to collapse
The device is very expensive, has dual partitions, has gotten a lot of bad press, and not near as Dev friendly as some others. Having said that, there are about 5 custom roms, root, exposed, substratum, and various launcher and active edge mods. So it's not like we're hurting too bad ??

Question Red Magic 6 Pro / Persist.img needed to restore fingerprint reader operation

Hello All,
I have successfully rooted my red magic 6 pro phone using the method described in the forum post:
Root achieved! Here's how to root the Red Magic 6 and Red Magic 6 Pro
I've been up 24 hours dealing with bootloops. I finally found a way to root the phone and have it boot up! :ROFLMAO: Join our Discord Channel https://discord.gg/8RHyc6Rw Youtube Video Tutorial: UPDATED VIDEO: For all those...
forum.xda-developers.com
I am faced with the issue of the fingerprint reader not working.
Tried fixing it by running the calibration procedure (https://forum.xda-developers.com/t/...er-print-after-loss-data-calibration.4132961/) with no success.
If anyone of you has an operational fingerprint reader in their red magic 6 pro and they would like to help me fix mine, please sent me the persists.img of your phone so I can flash it in my own and get the reader operational again.
There is another post that describes the procedure on how to extract the img from your phone from the forum:
Extracting stock Boot, Recovery and Persist images
Talking here about how to extract the stock Boot, Recovery and Persist images, needed in case of e.g. bootloop upon flashing Magisk or TWRP, to reflash the stock image(s). Also, boot image is needed for patching from Magisk Manager (and flashing...
forum.xda-developers.com
Any assistance will be greatly appreciated.

Ragemanster said:
Hello All,
I have successfully rooted my red magic 6 pro phone using the method described in the forum post:
Root achieved! Here's how to root the Red Magic 6 and Red Magic 6 Pro
I've been up 24 hours dealing with bootloops. I finally found a way to root the phone and have it boot up! :ROFLMAO: Join our Discord Channel https://discord.gg/8RHyc6Rw Youtube Video Tutorial: UPDATED VIDEO: For all those...
forum.xda-developers.com
I am faced with the issue of the fingerprint reader not working.
Tried fixing it by running the calibration procedure (https://forum.xda-developers.com/t/...er-print-after-loss-data-calibration.4132961/) with no success.
If anyone of you has an operational fingerprint reader in their red magic 6 pro and they would like to help me fix mine, please sent me the persists.img of your phone so I can flash it in my own and get the reader operational again.
There is another post that describes the procedure on how to extract the img from your phone from the forum:
Extracting stock Boot, Recovery and Persist images
Talking here about how to extract the stock Boot, Recovery and Persist images, needed in case of e.g. bootloop upon flashing Magisk or TWRP, to reflash the stock image(s). Also, boot image is needed for patching from Magisk Manager (and flashing...
forum.xda-developers.com
Any assistance will be greatly appreciated.
Click to expand...
Click to collapse
You need your persist.img that shipped with phone. Someone elses will NOT. You have lost FP forever.

bs3pro said:
You need your persist.img that shipped with phone. Someone elses will NOT. You have lost FP forever.
Click to expand...
Click to collapse
I've read for another phone that they were able to restore the functionality with the persist of another phone. I understand that the sensors are calibrated per device but it seems that the issue is more related to the security of the root rather than persist being actually corrupted.
Are you aware if I flash stock rom again if there is possibility for FP to work again?

why don't you extract it from the payload in the original ROM?

Andrologic said:
why don't you extract it from the original ROM?
Click to expand...
Click to collapse
If I am not mistaken, this is a per device partition and is not included in any ROM. As I understand it, persist.img contains all the sensors calibration data for the phone.
This is why I request from someone who has the same phone to extract and share so I can have a chance to save the FP functionality in my phone.

Ragemanster said:
If I am not mistaken, this is a per device partition and is not included in any ROM. As I understand it, persist.img contains all the sensors calibration data for the phone.
This is why I request from someone who has the same phone to extract and share so I can have a chance to save the FP functionality in my phone.
Click to expand...
Click to collapse
Understood. Yes, it's not a ROM file. I may switch to this device in the next day or two. Don't mind giving you a copy of mine if you haven't got it by then..

Andrologic said:
Understood. Yes, it's not a ROM file. I may switch to this device in the next day or two. Don't mind giving you a copy of mine if you haven't got it by then..
Click to expand...
Click to collapse
I would greatly appreciate it!
Thank you very much!

Andrologic said:
Understood. Yes, it's not a ROM file. I may switch to this device in the next day or two. Don't mind giving you a copy of mine if you haven't got it by then..
Click to expand...
Click to collapse
Hello bro i have same issue just for sure do u have redmagic6 pro with 5050mAh (international) version???
If yes please help me, im struggle two months with this issue and now know i lost my a file named persist.img lol

Any luck guys. I've got the same problem.

Ragemanster said:
Hello All,
I have successfully rooted my red magic 6 pro phone using the method described in the forum post:
Root achieved! Here's how to root the Red Magic 6 and Red Magic 6 Pro
I've been up 24 hours dealing with bootloops. I finally found a way to root the phone and have it boot up! :ROFLMAO: Join our Discord Channel https://discord.gg/8RHyc6Rw Youtube Video Tutorial: UPDATED VIDEO: For all those...
forum.xda-developers.com
I am faced with the issue of the fingerprint reader not working.
Tried fixing it by running the calibration procedure (https://forum.xda-developers.com/t/...er-print-after-loss-data-calibration.4132961/) with no success.
If anyone of you has an operational fingerprint reader in their red magic 6 pro and they would like to help me fix mine, please sent me the persists.img of your phone so I can flash it in my own and get the reader operational again.
There is another post that describes the procedure on how to extract the img from your phone from the forum:
Extracting stock Boot, Recovery and Persist images
Talking here about how to extract the stock Boot, Recovery and Persist images, needed in case of e.g. bootloop upon flashing Magisk or TWRP, to reflash the stock image(s). Also, boot image is needed for patching from Magisk Manager (and flashing...
forum.xda-developers.com
Any assistance will be greatly appreciated.
Click to expand...
Click to collapse
If you solve your problem please share with us.

You can directly use the persist image recovery of red Magic 5 mobile phone. The effect is the same. I have tested it

Hey guys!
I also lost the "persist" and with it almost all my sensors...Someone please share with me. I know it's not calibrated for my phone, but it can only be better :/ I've read all the RM6 forums that google puts out, but I can't find a solution :/
Thank you very much!
{
"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"
}

How to recover your device after flashing incorrect DDR xbl images

No matter how you are experienced or skilled in flashing ROM's, the things sometimes just happens. And you are here now...
Even I was aware which DDR model was my device, yes.. I did it - flashed by mistake DDR4 xbl.img to my DDR5 noodlep.
Of'coz, I wasn't that happy when I achieved it. Many googling, many searches - nothing. The only option was to return to OnePlus for repair.
But; there is a way. The idea came from Tom Marshall ( @tdm ) - he said that I can try to force "deep flash method" using EDL CABLE.
How to recover ? It's really simple.
Pre-requisites:
1. Windows 7 - 10 based PC (for msmtool) with properly installed 9008 COM port drivers.
Follow this guide to set and prepare: [OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
2. Buy EDL cable. it looks like that:
{
"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"
}
Now to revive your toy !
1. Start msmtool, click others (as it's recommended for msmtool), choose region of your device. Get ready to start flashing.
You'll see that the line with COM port says it's not connected (yet)
2. Connect the cable to your device - but not to PC yet.
3. Press the button on the cable - It's called "deep flash" button...
4. While you are still pressing the button, connect the other side of the cable to your PC (where msmtool is opened and ready to go).
5. Release the button and you'll hear that your device is connected. Check the line with COM port and you'll see it's connected.
EDL port will be opened for about 10 seconds. so you must be ready to start the installation.
6. Start the msmtool and wait till the finish.
7. The rest is well known msmtool flashing way.
Enjoy !!!
Credits goes to @tdm , @jabashque & @AnierinB for their support.
This method shall work on EVERY QUALCOMM device, as it's QualComm thing...

Haha, thanks for the confirmation, everyone said that the ram is fried and you have to change mobo, i said that there is no proof of that, and i was right.
Btw could you share link to where you got that cable?

ppajdek said:
Haha, thanks for the confirmation, everyone said that the ram is fried and you have to change mobo, i said that there is no proof of that, and i was right.
Btw could you share link to where you got that cable?
Click to expand...
Click to collapse
Actually available on Amazon or eBay for a few bucks.

ppajdek said:
Haha, thanks for the confirmation, everyone said that the ram is fried and you have to change mobo, i said that there is no proof of that, and i was right.
Btw could you share link to where you got that cable?
Click to expand...
Click to collapse
Okay first off Qualcomm has multiple things in their source code that tell you you can ram flash your phone back secondly software can't fry hardware

Thanks @samdoc, @tdm , @jabashque ! I was able to fix my phone and get it back to working . I'm very grateful for the help and wanted to express my appreciation. Without this post, I'm not sure what I would have done. Thanks again, samdoc!

jef_00 said:
Thanks @samdoc, @tdm , @jabashque ! I was able to fix my phone and get it back to working . I'm very grateful for the help and wanted to express my appreciation. Without this post, I'm not sure what I would have done. Thanks again, samdoc!
Click to expand...
Click to collapse
I'm trying it out tomorrow myself

AkayamiShurui said:
I'm trying it out tomorrow myself
Click to expand...
Click to collapse
Good luck brother

jef_00 said:
Good luck brother
Click to expand...
Click to collapse
I'm literally about to do it right now I'm just waiting for the MSM tool to finish downloading I got official qualcomm drivers on the computer

did you have success brother @AkayamiShurui

jef_00 said:
did you have success brother @AkayamiShurui
Click to expand...
Click to collapse
Trying again I downloaded the wrong MSM lol

Thank you @semdoc for the suggestion
Because I used similar like semdoc attached image deep flash cable and followed the steps, its seems to be not work. (no new notification in Device Manager)
@jef_00 do you mind share what type of deep flash cable/ shopping link?
After wrongly flashed XBL, is that normal the phone will be hot?
(I have just unplug the battery so it won't over heat mobo)

Hi @bingchilling sure!
1. I used a hydra EDL v2 cable i get mine from AliExpress
2. Not noticed that

AkayamiShurui said:
Trying again I downloaded the wrong MSM lol
Click to expand...
Click to collapse
Aah allright

jef_00 said:
Hi @bingchilling sure!
1. I used a hydra EDL v2 cable i get mine from AliExpress
2. Not noticed that
Click to expand...
Click to collapse
Thank you @jef_00, will give it a try!

bingchilling said:
Thank you @jef_00, will give it a try!
Click to expand...
Click to collapse
no problem!

i guess im a little bit late for this party? successfully switched motherboard, but broke the screen in the process (wrong screw into wrong hole)
anyway i'll pray and hope this works on your phones cause this issue needs to be tech fckd, just switched to OP9Pro for 200 bucks, dont ask how.. guess someone in much need at ebay

Hi everyone, I might need some help here...I have a OnePlus 8T EU model and I too have flashed the wrong xbl.img (DDR5 instead of DDR4X in my case). Reading this post gave me some hope and I bought an EDL cable, looking just as the one in the picture OP posted.
My phone has never been in EDL mode before, therefore it is not showing up at all in device manager, no QHUSB_BULK, no anything. It is therefore impossibile for me to try and install the drivers by updating the device entry there, as specified in the guide.
I tried to install the drivers in several other ways, using an installer executable or manually installing the .inf files, but the outcome is always the same: after following all the steps given, MSM, as well as Device manager, do not read my device.
What can I possibly try differently here?

joker925 said:
Hi everyone, I might need some help here...I have a OnePlus 8T EU model and I too have flashed the wrong xbl.img (DDR5 instead of DDR4X in my case). Reading this post gave me some hope and I bought an EDL cable, looking just as the one in the picture OP posted.
My phone has never been in EDL mode before, therefore it is not showing up at all in device manager, no QHUSB_BULK, no anything. It is therefore impossibile for me to try and install the drivers by updating the device entry there, as specified in the guide.
I tried to install the drivers in several other ways, using an installer executable or manually installing the .inf files, but the outcome is always the same: after following all the steps given, MSM, as well as Device manager, do not read my device.
What can I possibly try differently here?
Click to expand...
Click to collapse
İssues are with your Windows and quallcom drivers probably... I remember I had to switch to safemod in order to installl quallcom drivers.

I'm facing the same issue. Flashed ddr5 firmware instead of ddr4. The phone is completely hard bricked and is not showing on device manager as well.
Will the edl cable enable the connectivity so that i can do MSM?
Ordered youkiloon hydra v2 edl cable and planning to test tomorrow.

abhi92raj said:
I'm facing the same issue. Flashed ddr5 firmware instead of ddr4. The phone is completely hard bricked and is not showing on device manager as well.
Will the edl cable enable the connectivity so that i can do MSM?
Ordered youkiloon hydra v2 edl cable and planning to test tomorrow.
Click to expand...
Click to collapse
Could you Please share the result after testing

Question [NEW ONEPLUS USER] - Happy to be amoung you.

Hello everyone, I just bought the OnePlus 9 Pro 5G LE2123 Dual SIM 12GB+256G. Due to my inexperience, I ask for considerations in reference to a possible procedure for obtaining Root + TWRP permissions. ​I also ask if obtaining root permissions invalidate the warranty with some alleged counter (for example samsung knox counter). ​In the previous smarphone ( samsung galaxy note 9 ) I corrupted the EFS IMEI file by mistake and I don't want to repeat the same mistake. Thanks to all the Admins of the topic for your attention, as I can't help but be happy to be part of your oneplus family ​​
{
"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"
}

[GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13.1.0.500
Different variants of Magisk that are available for use : Magisk Variant Stable / Beta / Canary Release Official Android / OOS OOS 11 and above Maintainer topjohnwu Project Link GitHub Zygisk No...
forum.xda-developers.com

Thank you so much my friend

Congratulations on your OnePlus 9 Pro! Enjoy!!

You are phenomenal, I am reading the best guide indicated above and it is perfect and very clear in its explanation. ​I have only three questions: ​
To possibly send it to assistance, would it be enough to just lock the bootloader and flash the original boot? ​
Is it essential to have twrp recovery? ​
What bekup operation should I do to avoid stumbling into some errors ( ex. EFS IMEI)? ​
​Thank you for your time.​

pronegate said:
You are phenomenal, I am reading the best guide indicated above and it is perfect and very clear in its explanation. ​I have only three questions: ​
To possibly send it to assistance, would it be enough to just lock the bootloader and flash the original boot? ​
Is it essential to have twrp recovery? ​
What bekup operation should I do to avoid stumbling into some errors ( ex. EFS IMEI)? ​
​Thank you for your time.​
Click to expand...
Click to collapse
Use the MSM tool to get back to stock.
I don't install TWRP, but boot it in temp mode for flashing etc.
SwiftBackup app for backing up apps and data, call logs and sms. Messed up data, MSM tool to factory and restore with SwiftBackup. Copy internal storage to PC for it's backup.....

Thanks friend
Other questions
In your experience, do you recommend staying on OOS 13 or immediately flashing some of the custom roms you recommend?
Before flashing the new custom rom, which partition should I wipe?
Once the new custom rom is installed, for ota updates is the same procedure with magisk to maintain root permissions?
Thank you for your time @TheGhost1951.​

pronegate said:
Thanks friend
Other questions
In your experience, do you recommend staying on OOS 13 or immediately flashing some of the custom roms you recommend?
Before flashing the new custom rom, which partition should I wipe?
Once the new custom rom is installed, for ota updates is the same procedure with magisk to maintain root permissions?
Thank you for your time @TheGhost1951.​
Click to expand...
Click to collapse
As for custom roms, it is just a matter of choice. I have seen people that are happy and seen some that have had problems. As for me I prefer stock because it is made specifically for your phone. Less chance of problems. If you install a custom ROM it is usually advisable to go into recovery and factory reset. That is the wiping that is talked about. Finally, go back and read the link I gave you on keeping root. Read it until you have a clear picture as to what you need to do...

TheGhost1951 said:
As for custom roms, it is just a matter of choice. I have seen people that are happy and seen some that have had problems. As for me I prefer stock because it is made specifically for your phone. Less chance of problems. If you install a custom ROM it is usually advisable to go into recovery and factory reset. That is the wiping that is talked about. Finally, go back and read the link I gave you on keeping root. Read it until you have a clear picture as to what you need to do...
Click to expand...
Click to collapse
Thank you for your time @TheGhost1951 ​

pronegate said:
Thank you for your time @TheGhost1951 ​
Click to expand...
Click to collapse
You are most welcome. Like I said, staying with stock roms are more trouble free. They are made for your phone. Custom roms are ok for the most part, but I have seen too many in the forums trying to run a custom ROM and having too many problems or it doesn't have everything the stock ROM has to begin with. On the OnePlus 9 Pro, there is one more little nugget I can offer the will give you full root that Magisk is short on. Once you are rooted with Magisk, send me a PM and I will clue you in on it....

Oh, by the way, you need to disable driver signing on windows PC from this link https://www.techpout.com/disable-driver-signature-enforcement/ and then search for and install latest OnePlus and Qualcomm USB drivers and install them. This way you can connect your phone to PC in ADB, Fastboot and EDL modes for maintenance tasks!

TheGhost1951 said:
You are most welcome. Like I said, staying with stock roms are more trouble free. They are made for your phone. Custom roms are ok for the most part, but I have seen too many in the forums trying to run a custom ROM and having too many problems or it doesn't have everything the stock ROM has to begin with. On the OnePlus 9 Pro, there is one more little nugget I can offer the will give you full root that Magisk is short on. Once you are rooted with Magisk, send me a PM and I will clue you in on it....
Click to expand...
Click to collapse
I INSTALLED THE DRIVERS AS GIVEN IN YOUR GUIDE
I WAIT VERY HURRY FOR THE ARRIVAL OF MY ONEPLUS 9 PRO. I WILL UPDATE YOU AS SOON AS I HAVE NEWS

I would recommend first testing Oxygen OS software, I thinks it is not necessary for most users to tinker with custom roms.
In some time you will discover if your needs are covered with official soft or not, I know Oxygen Os is not what it used to be, it is nor good nor bad, it just was so much better before merging with Oppo because it had its own dev team and they actually did care about users, now they pretend to but ignore important matters, just answer silly questions in their forums but always abstract and tasteless...
You can always root your phone and stay in Oxygen Os but with benefits of magisk, you can tinker with it staying in Oxygen OS, but beware, you need to dome some certain things in order to "trick" some sensitive apps to root, like banking, when it detects your phone is rooted some functions may not work for "safety reasons", read magisk tutorial and enable saferynet, magisk hide deny list and you will be good to go, pretty easy for certainly experienced user, if not feel free to ask, we all will be happy to help!

pronegate said:
You are phenomenal, I am reading the best guide indicated above and it is perfect and very clear in its explanation. ​I have only three questions: ​
To possibly send it to assistance, would it be enough to just lock the bootloader and flash the original boot? ​
Is it essential to have twrp recovery? ​
What bekup operation should I do to avoid stumbling into some errors ( ex. EFS IMEI)? ​
​Thank you for your time.​
Click to expand...
Click to collapse
When you have your phone in edl and recognized by the msm tool, you can press F8 and choose partitions to back up. Take a backup of modemst1/2, efs/persist and while you're in there, grab boot_a so you can inject magisk into that boot image for root.
After you select the partitions you want, press read back and they will be saved to C:\ - with the partitions backed up, even if you do manage to break something the msm tool can't fix, you'll have the originals to put back in place.
The password is oneplus, one word all lowercase.
I don't use twrp anymore but that's your choice. I also stay on oos11. Some stay on 11, some go to 13, some go custom rom. It just depends on what you want and need from your phone. For now, we have the last OnePlus phone with real custom rom support as the newer OnePlus phones don't have public msm tools for flashing or recovering from brick state