Develop Bugs

[ROM] Asus ROG Phone II ZS660KL WW Official ROM (3 Steps)

Update1: 22-09-2019
Update2: 23-09-2019
Update3: 02-10-2019 | Change The link
[ROM] Asus ROG Phone II ZS660KL WW 16.0622.1907.33 Fastboot ROM
This ROM To make Asus ROG Phone II ZS660KL in Version WW-16.0622.1907.33 [World Wide 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"
}
CN or WW will work here
You need 3 Steps Only
1- Unlock Bootloader [apk]
2- Flash The ROM [Fastboot] Then Factory Reset
3- Relock Bootloader [Fastboot] Then Factory Reset (Optional)
Now We will Go
1- Unlock Bootloader [apk]
Download the following file:
** USB Drivers
XQ55 Server: ZS660KL_SIGNED_UnlockTool_9.1.0.10_190702_fulldpi.apk
Asus Server: ZS660KL_SIGNED_UnlockTool_9.1.0.10_190702_fulldpi.apk
__________________________________________________
2- Flash The ROM [Fastboot] Then Factory Reset
Download the following file:
Update3: 02-10-2019 | Change The link
XQ55 Server: Fastboot ROM UL-ASUS_I001_1-ASUS-16.0622.1907.33-1.1.134-user
How To Go to Fastboot
Power Off your Phone Then Hold [Power + Volume up] For 5 Seconds
You will see Black Screen + Green START [This is Fastboot Mode]
Now Link your Phone With Your PC
** Use the Side Type C in your Phone
** Use Windows 64bit Only
** Use Original Cable or any other like it.
** Your Battery more than 50%
Your PC Shoud recognize your Phone as [Asus Fastboot Interface]
Now Your Phone in Fastboot Mode + link With your PC as Asus Fastboot Interface
Go to Folder: Fastboot ROM UL-ASUS_I001_1-ASUS-16.0622.1907.33-1.1.134-user
In any blank place inside the folder
In PC keyboard press the Shift button + right mouse Click
You will see New command [Open PowerShell window here] or [Open Command here]
Now inside the Blue Screen or Black Screen
Copy This Command one by one
fastboot flash abl abl.img
Then Enter
fastboot flash aop aop.img
Then Enter
fastboot flash asusfw asusfw.img
Then Enter
fastboot flash bluetooth bluetooth.img
Then Enter
fastboot flash boot boot.img
Then Enter
fastboot flash cmnlib cmnlib.img
Then Enter
fastboot flash cmnlib64 cmnlib64.img
Then Enter
fastboot flash devcfg devcfg.img
Then Enter
fastboot flash dsp dsp.img
Then Enter
fastboot flash dtbo dtbo.img
Then Enter
fastboot flash hyp hyp.img
Then Enter
fastboot flash keymaster keymaster.img
Then Enter
fastboot flash modem modem.img
Then Enter
fastboot flash qupfw qupfw.img
Then Enter
fastboot flash system system.img
Then Enter
fastboot flash tz tz.img
Then Enter
fastboot flash vbmeta vbmeta.img
Then Enter
fastboot flash vendor vendor.img
Then Enter
fastboot flash xbl xbl.img
Then Enter
fastboot flash xbl_config xbl_config.img
Then Enter
fastboot flash xrom xrom.img
Now Go to recovery mode
** The Same Fastboot mode just Choose Recovery mode
** Volume buttons to Move and Power button to Choose
Recovery mode > Wipe data/factory reset > Yes > Reboot system now
Now You have WW ROM
__________________________________________________
3- Relock Bootloader [Fastboot] Then Factory Reset (Optional)
Important Note: Relock the bootloader immediately after installing the Fastboot ROM is Wrong & you need to let the ROM to work normally first Then you can Lock the bootloader.
Or you will see [Slot _a is unbootable] & to FIX this you will need RAW ROM
Only if your Phone work normally you can Relock it
Only if your Phone work normally you can Relock it
Only if your Phone work normally you can Relock it
Now to Relock
Download the following file:
XQ55 Server: ZS660KL Relock Bootloader
Phone in Fastboot Mode + link With your PC as Asus Fastboot Interface
Go to Folder: ZS660KL Relock Bootloader
In any blank place inside the folder
In PC keyboard press the Shift button + right mouse Click
You will see New command [Open PowerShell window here] or [Open Command here]
Now inside the Blue Screen or Black Screen
Copy This Command
fastboot oem asus-csc_lk
Then Go th Recovery Mode
Recovery mode > Wipe data/factory reset > Yes > Reboot system now
Done
__________________________________________________
ZS660KL software Image：WW_V16.0622.1907.33 for WW
Improved Item:
1. Added three ROG live wallpapers
2. Light Luminous Core theme supports live wallpaper effect
3. Fixed the issue where occasionally can not turn on WiFi hotspot
Steps of Update:
1. Check software version of your device**
2. Download device software and Update SOP (From “Manual” Item)
3. Only apply to same SKU update, Example: WW->WW, CN->CN, TW->TW.
4. Software update cannot transfer the software SKU and downgrade the software version.
5. Wrong SKU may cause update failure, please update the same SKU version only.
**How to know the device model?
Path: Settings->About-> Model number
Example: ASUS PadFone2
**How to know the device software version?
Path: Settings->About-> software information->Build number
Example: CHT_PadFone2-user-10.4.17.15-UpdateLauncher
**System upgrade may cause part of data missing, please buckup your important data before system upgrading.
__________________________________________________
Asus ROG Phone 2 ZS660KL All My Files
__________________________________________________
Another Tools:
Tool All in One = Will Help to shortcut Fastboot Commands
Asus Flash Tool = Not work !
Fastboot adb = to use Fastboot CMD
Payload Dumper = To Change ROM Files From payload.bin To .img
SkipSoft ULTIMATE driver and Adb installer = Help With USB Drivers
__________________________________________________

Thanks :good:

Thank You
Thank You very much sir

any difference?
I have version WW_16.0622.1906.19_0... is there bug fixes with the touch latency or smoothness with this newer version?

This is outstanding and we all appreciate the work. However, is there a way to make a script that flashes ALL of the critical partitions, rather than having to flash them one at a time? Similar to #fuqop's fastboot roms.

Hi
is this method is allowing manual update later ?
also what is the different between this method and other method which enabling ww with manual update ?
great work
Thanks

Welcome back @XQ55 great work by the way :good:
your effort is highly appreciated

digitman xxx said:
Welcome back @XQ55 great work by the way :good:
your effort is highly appreciated
Click to expand...
Click to collapse
Thank You

abunhyan said:
Hi
is this method is allowing manual update later ?
also what is the different between this method and other method which enabling ww with manual update ?
great work
Thanks
Click to expand...
Click to collapse
So far I do not know whether this ROM will accept the aerial update after locking the bootloader or not
This Update is 2019/09/09

ZeroKool76 said:
This is outstanding and we all appreciate the work. However, is there a way to make a script that flashes ALL of the critical partitions, rather than having to flash them one at a time? Similar to #fuqop's fastboot roms.
Click to expand...
Click to collapse
This is of course technically possible

razor1234mike said:
I have version WW_16.0622.1906.19_0... is there bug fixes with the touch latency or smoothness with this newer version?
Click to expand...
Click to collapse
ZS660KL software Image：WW_V16.0622.1907.33 for WW
Improved Item:
1. Added three ROG live wallpapers
2. Light Luminous Core theme supports live wallpaper effect
3. Fixed the issue where occasionally can not turn on WiFi hotspot
ZS660KL software Image：WW_16.0622.1906.19 for WW
Improved Item:
1."Aura lighting -
Support 4 new lighting effects for AeroActive Cooler II - Rainbow, mixed lights, comet, flash and dash
Support 4 new lighting effects for TwinView Dock II - Rainbow, mixed lights, comet, flash and dash
Support 4 basic lighting effects for ROG Kunai Gamepad - Static, breathing, strobing, color cycle"
2.Added the aura light selection option for AeroActive Cooler II and TwinView Dock II
3.Support the classic Pixel-like system style

Could you please provide a list of added live wallpapers?

rogphone said:
Could you please provide a list of added live wallpapers?
Click to expand...
Click to collapse
But asus can check SN of your phone and know you changed your rom from CN to WW and dont let you to update OTA.
May be.

mazmazmaz said:
But asus can check SN of your phone and know you changed your rom from CN to WW and dont let you to update OTA.
May be.
Click to expand...
Click to collapse
Guess we'll find out when they update the WW rom again

I am currently on version WW-16.0622.1907.33 already. Is it possible to patch the boot.img with Magisk from inside the (Fastboot ROM UL-ASUS_I001_1-ASUS-16.0622.1907.33-1.1.134-user) file and flash via fastboot to gain root?
Edit: I was able to to root with the patched 1907 image from the other thread.

You should also include changing vendor to WW for the fingerprint also can flash raw of this instead of all 21 files

This Rom link is china Version

Tai Tran CDT said:
This Rom link is china Version
Click to expand...
Click to collapse
This is WW not CN

Thank you for the tutorial. I'm currently on Firmware 1906.19_0, is there a way for me to update to 1907.33 without unlocking the bootloader and factory resetting my device? Thanks!

Its lie it changed WW to CN which I didn't want
Hi everyone, I was on WW version of ROM and I wanted to update my ROM to latest version so I followed this post, but now my phone have changed from WW to CN. I'm not really liking this. and in main page its showing that he's on latest version of WW, while I'm now on CN. now I've to waste more time to go back to WW.
---------- Post added at 02:22 PM ---------- Previous post was at 02:20 PM ----------
XQ55 said:
This is WW not CN
Click to expand...
Click to collapse
You are wrong XQ55, its CN, I trusted you. and now I'm on CN, I was on WW and after following all steps I'm on CN version. you need to be honest.

[RMN8Pro][Global] Bootloop fix

Evening guys, let's fix the Bootloop of our RMN8Pro if we have installed a menu Recovery TWRP faulty/unsuitable or we have installed a ROM that does not belong to our smartphone.
This method is valid for China to global or Global to global.
NOT FOR INDIAN (sorry about that)
You'll need:
ADB files
Fastboot ROM V10.4.5.0.PGGEUXM
Download both files and unzip them in C:/ADB (if you don't have that folder... just create it)
You will need to rename the file extension of the file <<begonia_eea_global_images_V10.4.5.0.PGGEUXM_20191007.0000.0000_9.0_eea_f796762f8a.tgz>> from .tgz to .rar
Let's go!!
Turn the phone off, turn it on in fastboot mode (by pressing both POWER and VOL- ) and connect the phone to the PC with its USB cable.
Open a CMD command console (in administrator mode) in C:/ADB and type this (press enter when finished typing):
Code:
fastboot devices
If you have the drivers installed and everything goes well, a series of alphanumeric characters will appear, such as for example:
Code:
a6ghfxfv6 fastboot
Perfect, we can go on.
Next we will flash one by one the files needed to revive the phone.
Write the following lines and press enter at the end of each of them (wait for the files to be installed between line and line):
Code:
fastboot boot boot.img
fastboot flash system.img
fastboot flash vendor.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
When you're done, restart the phone with:
Code:
fastboot reboot
Congratulations, you have your RMN8Pro fixed.

klurosu said:
Evening, let's fix the Bootloop of our RMN8Pro if we have installed a menu Recovery TWRP faulty/unsuitable or we have installed a ROM that does not belong to our phone.
This method is valid for China to global or Global to global.
NOT FOR INDIAN (sorry about that)
You'll need:
ADB files
Fastboot ROM V10.4.5.0.PGGEUXM
Download both files and unzip them in C:/ADB (if you don't have that folder...create it)
You will need to rename the file extension of the file <<begonia_eea_global_images_V10.4.5.0.PGGEUXM_20191007.0000.0000_9.0_eea_f796762f8a.tgz>> from .tgz to .rar
Let's go!!
Turn the phone off, turn it on in fastboot mode (by pressing both POWER and VOL- ) and connect the phone to the PC with its USB cable.
Open a CMD command console (in administrator mode) in C:/ADB and type this (press enter when finished typing):
If you have the drivers installed and everything goes well, a series of alphanumeric characters will appear, such as for example:
Perfect, we can go on.
Next we will flash one by one the files needed to revive the phone.
Write the following lines and press enter at the end of each of them (wait for the files to be installed between line and line):
When you're done, restart the phone with:
Congratulations, you have your RMN8Pro fixed.
Click to expand...
Click to collapse
So, this is basically a guide of how to flash the images through fastboot, right? Why not just use MiFlash when we are in fastboot mode?

polfrank said:
So, this is basically a guide of how to flash the images through fastboot, right? Why not just use MiFlash when we are in fastboot mode?
Click to expand...
Click to collapse
Because it doesn't work???
Don't believe me?, Just try
send from an RMN8 Pro (xiaomi.eu custom rom)

Miflash will work if in fastboot and have an MI account had requested to unlock BL.
Don't believe me? You try.

idog8818 said:
Miflash will work if in fastboot and have an MI account had requested to unlock BL.
Don't believe me? You try.
Click to expand...
Click to collapse
You still need authorized account Sherlock.
(Omg this guys...)
send from an RMN8 Pro (xiaomi.eu custom rom)

klurosu said:
You still need authorized account Sherlock.
(Omg this guys...)
send from an RMN8 Pro (xiaomi.eu custom rom)
Click to expand...
Click to collapse
if you don't apply for the Mi account to unlock BL, how will you able to flash anything? Only 2 mins for a new account.....What the problem will be?

idog8818 said:
if you don't apply for the Mi account to unlock BL, how will you able to flash anything? Only 2 mins for a new account.....What the problem will be?
Click to expand...
Click to collapse
Read again (this time read well please) 2 posts above
send from an RMN8 Pro (xiaomi.eu custom rom)

klurosu said:
Read again (this time read well please) 2 posts above
send from an RMN8 Pro (xiaomi.eu custom rom)
Click to expand...
Click to collapse
Read again but didn't get it. What do you mean ....

idog8818 said:
Read again but didn't get it. What do you mean ....
Click to expand...
Click to collapse
That you still need an Authorized Xiaomi's Account to do that with the old method dude.
send from an RMN8 Pro (xiaomi.eu custom rom)

klurosu said:
That you still need an Authorized Xiaomi's Account to do that with the old method dude.
send from an RMN8 Pro (xiaomi.eu custom rom)
Click to expand...
Click to collapse
What do you mean by Authorized Xiaomi's Account?? As far as I know, there're 2 types of Mi accounts we commonly talk here.
1. Normal Mi account: used to unlock BL and this can be used in miflash to flash rom, I've tried 100 times in fastboot, and works every time. I registered this account I guess 5 years ago when I need to request unlock BL on note 3 . As I said above, it needs 2 mins to register.
2. Authorised service account: This is not we can easy to register, It's for Mi service center or developers for repair/develop purposes. If no rec, no recovery, blank screen, it can be recovered by SP flash tool, which will need this type of account. This is also why users in following post looking for unbricking.
[GUIDE] [begonia] UNBRICK - stuck on DA mode / Authorised Service Account required
https://forum.xda-developers.com/re...a-mode-authorised-t4000433/page7#post81175069
---------- Post added at 01:20 AM ---------- Previous post was at 01:17 AM ----------
I can prove this by my bricked redmi note 8 pro.
I used my mi account to unlock BL, flashed global rom, but I cannot use it in SP FLASH TOOL to restore because my MI account is not an Authorised Service Account

Hello,
I have a nex Redmi Note 8 pro, I unlocked it after I use Ifixit.. to install twrp, the phone was in bootloap, after I tried to flash with fastboot commands. Now the phone is off and I have a black screeen. I can't power it on (vol + or -) does not work. power on no more. It is not recognized with miunlock. No fastboot nor recovery. Please help me how I can do?

nutellamarco said:
Hello,
I have a nex Redmi Note 8 pro, I unlocked it after I use Ifixit.. to install twrp, the phone was in bootloap, after I tried to flash with fastboot commands. Now the phone is off and I have a black screeen. I can't power it on (vol + or -) does not work. power on no more. It is not recognized with miunlock. No fastboot nor recovery. Please help me how I can do?
Click to expand...
Click to collapse
At the moment you only can do a deep flashing in EDL mode, and need an authorized account... You need to contact someone with this type of account and flash... ( And give some money...)

nutellamarco said:
Hello,
I have a nex Redmi Note 8 pro, I unlocked it after I use Ifixit.. to install twrp, the phone was in bootloap, after I tried to flash with fastboot commands. Now the phone is off and I have a black screeen. I can't power it on (vol + or -) does not work. power on no more. It is not recognized with miunlock. No fastboot nor recovery. Please help me how I can do?
Click to expand...
Click to collapse
Some people are saying they managed to bring to life a phone without rocovery without fastboot mode.search and maybe you find a way. As i remember they said with phone turned off you press volume - and power and you have about 5 seconds to flash. I don't know more details.i wish you success

hello
thanks for your ideas, I can't enter in fastboot mode nor recovery. The screeen is black. When I tried with spflash, when I push together vol+ and vol- i hear a noise, but nothing happens with spflash.
I am trying. I think it is loosed.

nutellamarco said:
hello
thanks for your ideas, I can't enter in fastboot mode nor recovery. The screeen is black. When I tried with spflash, when I push together vol+ and vol- i hear a noise, but nothing happens with spflash.
I am trying. I think it is loosed.
Click to expand...
Click to collapse
as far as I know spflash tool should be ready to flash,. it means with all the files selected, the combination is keeping vol+ and connect the USB cable to PC port, I recommend you search in Google about flashing mediatek devices... Good luck

Literally this guide is really about just how to flash with fastboot instead of Mi Flash(tool which can use anyone with Xiaomi Phone - doesn't require Authorized Service ACC)
nutellamarco said:
hello
thanks for your ideas, I can't enter in fastboot mode nor recovery. The screeen is black. When I tried with spflash, when I push together vol+ and vol- i hear a noise, but nothing happens with spflash.
I am trying. I think it is loosed.
Click to expand...
Click to collapse
I had this problem at the weekend(Stuck at EDL mode - tried to flash with SP tool but without success(needed service acc - brom error)), you can use SP flash tool with authorized service acc - fastest way, maybe there will be some cracked security file in the future as one for redmi 6. Or do battery trick. You are stick at EDL mode and cannot reboot from it. You can wait to discharge your phone(Tooks ~2 day with pushed power button) then connect into computer and when the led turn less bright use vol - + power to get into fastboot or disconnect battery and reconnect with pushed vol - to get into fastboot(I have used this three times because of installing wrong recovery).

Aglik-x said:
Literally this guide is really about just how to flash with fastboot instead of Mi Flash(tool which can use anyone with Xiaomi Phone - doesn't require Authorized Service ACC)
I had this problem at the weekend(Stuck at EDL mode - tried to flash with SP tool but without success(needed service acc - brom error)), you can use SP flash tool with authorized service acc - fastest way, maybe there will be some cracked security file in the future as one for redmi 6. Or do battery trick. You are stick at EDL mode and cannot reboot from it. You can wait to discharge your phone(Tooks ~2 day with pushed power button) then connect into computer and when the led turn less bright use vol - + power to get into fastboot or disconnect battery and reconnect with pushed vol - to get into fastboot(I have used this three times because of installing wrong recovery).
Click to expand...
Click to collapse
Thanks a lot for your reply
I will do that. But How I can know that phone is on to discharge battery? Best regards

nutellamarco said:
hello
thanks for your ideas, I can't enter in fastboot mode nor recovery. The screeen is black. When I tried with spflash, when I push together vol+ and vol- i hear a noise, but nothing happens with spflash.
I am trying. I think it is loosed.[/QUOTE
My oneplus 6 I used to do kind of the same thing... With the phone plugged and everything ready to flash... I used to press - plus power button and it would starting the process..
Click to expand...
Click to collapse

petenoni said:
nutellamarco said:
hello
thanks for your ideas, I can't enter in fastboot mode nor recovery. The screeen is black. When I tried with spflash, when I push together vol+ and vol- i hear a noise, but nothing happens with spflash.
I am trying. I think it is loosed.[/QUOTE
My oneplus 6 I used to do kind of the same thing... With the phone plugged and everything ready to flash... I used to press - plus power button and it would starting the process..
Click to expand...
Click to collapse
I try this method, the spflash does not start
I tried all touche combinaisons.
I will wait until the battery were empty and try again.
Thanks for your reply
Click to expand...
Click to collapse

bootloop fix worked for me
I try to post this yesterday but nothing happened so what i did was...
i installed TWRP and in twrp i wipe all data , system, vendor and reboot phone. that was wrong and i stuck in bootloop. so i go back to fastboot and type commands as u say....
fastboot boot boot.img
fastboot flash system.img
fastboot flash vendor.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img - nothing worked
maybe u forgot some commands.... so i use...
fastboot boot boot.img -dont use, it didnt work
fastboot flash system system.img -ok
fastboot flash vendor vendor.img -ok
fastboot flash cust cust.img -ok
fastboot flash recovery recovery.img - but instead of official recovery i used TWRP.img and after reboot a finally boot into TWRP and i flash xiaomi.eu rom and after reboot magisk and all works fine. im not developer but this method worked for me and excuse my english i have global device

Question Help unbricking 9Pro after attempt to convert T-Mobile to Global

I recently purchased a 9 Pro T-Mobile edition. It was supposed to be a global edition, but this information was willfully obscured by the eBay seller. Whatever, I figured I could follow this guide to convert it to global firmware. I've rooted plenty of OnePlus phones before and am very comfortable with the process, as well as using MSM to fix things when they go wrong. However, things went even worse than normal. I went through the usual process of unlocking the bootloader, and began flashing the images from the download. However, as usual, they don't tell you to unlock flashing for critical partitions, so only half the partitions got flashed and the whole thing failed. Now I cannot access fastboot or recovery, or do quite literally anything with it.
I figured I'd use MSM and fix it just like I did when things like this happened to my OnePlus 8. So I downloaded the T-Mobile MSM from this thread and ran it. When I try to run it normally, it gets as far as "Start download Firehouse binary" and will attempt for 18 seconds, at which point it shows the error "Sahara Communication Failed. Please try again after power off phone (FH:258)". So I tried ticking the box to use Lite Firehose. It gets farther, but errors during Param preload, with the message "Device not match image."
I assumed that this error was due to the fact that some of the images that were successfully flashed are from the global image, while this MSM tool is for TMO specifically, so I tried to the global MSM tool from the same thread instead. It also fails Sahara communication with the exact same error. If I use Lite Firehose, it gives the error "Unsupported Target TMO."
At this point, I'm at a complete loss. I've tried to power off the phone via holding the power button + volume up button, but it never gives any response no matter how long I hold it. I'm not sure that the phone is able to turn on at all. My next guess would be to disconnect the battery and reconnect it, but I'm very hesitant to pull apart the phone without seeing if anyone has any better suggestions first. If I could access fastboot, I could have a download of a clean TMO firmware and could easily re-flash everything, but I can't get a single response out of the phone besides MSM errors. Any help would be much appreciated.

I just realized that that article is for the Oneplus 9 and NOT the Pro. That definitely explains why it broke in the first place, but doesn't help me get it back. The MSM Tools I'm using ARE for the Pro.

When you open Windows Device Manager and expand out the "Ports" section, what COM port is your phone using? Does that match up with the port the MSM tool is trying to use?

CZ Eddie said:
When you open Windows Device Manager and expand out the "Ports" section, what COM port is your phone using? Does that match up with the port the MSM tool is trying to use?
Click to expand...
Click to collapse
They're both using COM3

blindcat97 said:
They're both using COM3
Click to expand...
Click to collapse
Qualcomm.......9008?

TheGhost1951 said:
Qualcomm.......9008?
Click to expand...
Click to collapse
The full title of the device is Qualcomm HS-USB QDLoader 9008 (COM3)

blindcat97 said:
The full title of the device is Qualcomm HS-USB QDLoader 9008 (COM3)
Click to expand...
Click to collapse
That is the correct id and driver....however, is it the latest driver. That makes a difference as well.

TheGhost1951 said:
That is the correct id and driver....however, is it the latest driver. That makes a difference as well.
Click to expand...
Click to collapse
Windows lists the drivers version as 2.1.2.2 and date as 3/25/2016. I can't find anything newer by googling, and Windows automatic search for updated drivers reports it as the latest version.

Is there something in this link that will help?
Fix Sahara communication failed error in MSM Download Tool
In this tutorial, we will show you how to fix the Sahara communication failed and other related MSM Download Tool errors.
www.droidwin.com

CZ Eddie said:
Is there something in this link that will help?
Fix Sahara communication failed error in MSM Download Tool
In this tutorial, we will show you how to fix the Sahara communication failed and other related MSM Download Tool errors.
www.droidwin.com
Click to expand...
Click to collapse
No, I tried what I could in that article earlier already. At this point, I'm fairly certain that the only thing I could do would be to somehow force MSM to flash even though it thinks it has the wrong device, which I don't think is possible.

blindcat97 said:
No, I tried what I could in that article earlier already. At this point, I'm fairly certain that the only thing I could do would be to somehow force MSM to flash even though it thinks it has the wrong device, which I don't think is possible.
Click to expand...
Click to collapse
I'm a little confused about how you got your phone to its current state.
Your first paragraph has some minutia in it.
" I went through the usual process of unlocking the bootloader, and began flashing the images from the download. However, as usual, they don't tell you to unlock flashing for critical partitions, so only half the partitions got flashed and the whole thing failed."
What images did you download and how did you apply them to your phone?

I was following this guide to convert OP9 (not *pro*, which is where I messed up and I feel very stupid for not realizing that) from T-Mobile to Global firmware. It provided download links to a zip file full of img files, and a flash-all.bat which used fastboot commands to flash the individual files. Half of the files didn't flash because "Flashing critical partitions is not allowed", but some of them did flash successfully. There's no log file to tell me which ones did and did not work. Here's the chunk of the flash-all script that actually contains the fastboot commands:
Spoiler: flash-all excerpt
fastboot flash dtbo dtbo.img
fastboot flash splash splash.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot --disable-verity flash vbmeta_vendor vbmeta_vendor.img
fastboot reboot fastboot
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash dsp dsp.img
fastboot flash dtbo dtbo.img
fastboot flash splash splash.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash abl abl.img
fastboot flash bluetooth bluetooth.img
fastboot flash cpucp cpucp.img
fastboot flash devcfg devcfg.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash tz tz.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot reboot fastboot
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
It got through the first reboot okay (despite booting to fastbootd and me having to manually redirect it back to fastboot), but when it reached the second reboot command, it just died and wouldn't turn on any more, and the third block of commands were never executed. So I'm guessing that something it flashed in that second block is what completely broke its ability to boot. I would flash the images from a clean copy of OP9Pro TMO firmware, but I can't get to fastboot at all.

blindcat97 said:
Windows lists the drivers version as 2.1.2.2 and date as 3/25/2016. I can't find anything newer by googling, and Windows automatic search for updated drivers reports it as the latest version.
Click to expand...
Click to collapse
You will need a modded MSM tool....when you use the stock TMO MSM tool what error do you get?

im not really that experienced with this stuff but this kind of happened to me today so i decided to make an account and try to help you. Basically what I did was I deleted everything on it, like I could only use fastboot mode. Then i used an msm tool from here. make sure you get the tmobile one because i tried global and it didn't work. after i used the msm tool it started working again. once again, i am not experienced in this stuff, so my advice may screw you over, but at this point you don't really have anything to lose.

TheGhost1951 said:
You will need a modded MSM tool....when you use the stock TMO MSM tool what error do you get?
Click to expand...
Click to collapse
From my original post: When I try to run it normally, it gets as far as "Start download Firehouse binary" and will attempt for 18 seconds, at which point it shows the error "Sahara Communication Failed. Please try again after power off phone (FH:258)". So I tried ticking the box to use Lite Firehose. It gets farther, but errors during Param preload, with the message "Device not match image."

I've never run into the firehouse issue before.
But it's very common and is talked about in dozens of threads here.
But it looks like you've actually flashed some system files from a different phone.
I hope that doesn't mean MSM is rejecting you because it thinks you're a different phone.
Maybe try flashing a 9pro boot.img that would match the software you're supposed to be at right now?
Not sure if that'll mess you up more or not though.

Double-check that you've downloaded the correct MSM file
Research the SMT mode.
It's disabled for a reason - because it'll wipe your IMEI & other important things.
I don't know how to use it yet, but supposedly it'll fix unfixable things. When used properly.
{
"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"
}

I have no way of flashing. I can't get to fastboot, I can't get the phone to respond to quite literally anything other than MSM. Any combination of buttons does nothing. I'm not a professional with this stuff; if there's a way to flash to EDL without MSM, I don't know it. It looks like MSM rejecting because it thinks it's a different phone is exactly what's happening, and the only thing I can think to do would be essentially to mod it so that it thinks it's allowed to flash OP9 as well as 9Pro, or otherwise bypass the device check.
I'm certain I've got the right MSM tool. Doing some research into the SMT Download mode, it looks like it breaks core features, like the IMEI, and widevine. Is it possible to backup those partitions from EDL mode?
Basically, if my only way of recovering the device is to destroy critical sectors entirely, I might just send the device to OnePlus for repairs. My warranty was already voided by unlocking the bootloader.

blindcat97 said:
I can't get to fastboot
Click to expand...
Click to collapse
Why not? What happens when you power off the phone.
Wait 15 seconds.
And then press + hold the volume(-) and power button at the same time?
Remember to hold them until *after* the splash screen comes up.

CZ Eddie said:
Why not? What happens when you power off the phone.
Wait 15 seconds.
And then press + hold the volume(-) and power button at the same time?
Remember to hold them until *after* the splash screen comes up.
Click to expand...
Click to collapse
The phone is already off and cannot be turned on in any way, to any mode. Nothing happens when I hold that combination, nor any other. The phone is completely unresponsive.

Question Did I hard brick my phone? (SOLVED)

First off, I converted my Tmo version to EU using the MSM conversion tool... I then proceeded to fastboot flash the A13 OTA manually. (I was hoping to keep the bootloader unlocked by manually flashing) At the point that I needed to reboot in to fastbootD to flash critical partitions, I couldnt get it to do so. I may have hit recovery mode while in the bootloader and my phone just went blank. Now I can only access EDL mode but I cant get any of the MSM tools to work.
I get an "IMEI is incorrect" error with the TMo-EU MSM, Global MSM says "invalid target TMo" so it recognizes it as tmobile.
below are the fastboot commands I entered. Is there anything that would completely brick my phone and erase recovery and bootloader??
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img

In MSM tool, there's a check box which says 'Use Lite Firehose'. can you tick that once and try again ?

mbj731 said:
First off, I converted my Tmo version to EU using the MSM conversion tool... I then proceeded to fastboot flash the A13 OTA manually. (I was hoping to keep the bootloader unlocked by manually flashing) At the point that I needed to reboot in to fastbootD to flash critical partitions, I couldnt get it to do so. I may have hit recovery mode while in the bootloader and my phone just went blank. Now I can only access EDL mode but I cant get any of the MSM tools to work.
I get an "IMEI is incorrect" error with the TMo-EU MSM, Global MSM says "invalid target TMo" so it recognizes it as tmobile.
below are the fastboot commands I entered. Is there anything that would completely brick my phone and erase recovery and bootloader??
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
Click to expand...
Click to collapse
Also, you need T-Mobile msm

oddlyspaced said:
In MSM tool, there's a check box which says 'Use Lite Firehose'. can you tick that once and try again ?
Click to expand...
Click to collapse
I've tried that. Still no luck. Getting either "IMEI is incorrect" or "device doesnt match image" errors. Kind of odd getting different errors each time.
jamescable said:
Also, you need T-Mobile msm
Click to expand...
Click to collapse
I've tried them all just hoping one will work. Tmo-EU, Tmo, EU, Global etc etc

Sorry for your situation...for future concerns, once u unlock bootloader, theres nothing other than msm that will relock it. As far as restoring your phone, I've seen where some ppl who can't find luck with their correct msm tool, they've had to use EU, or in most cases IND msm. Again, u will have to check box for lite firehose for it to work.
Also another thing to note...u really need to use regular style USB cable. Not newer ones that are C to C. If u haven't tried the cable problem I'd go back and try older style cable with correct msm tool b4 trying IND msm.

Shooter7889 said:
Sorry for your situation...for future concerns, once u unlock bootloader, theres nothing other than msm that will relock it. As far as restoring your phone, I've seen where some ppl who can't find luck with their correct msm tool, they've had to use EU, or in most cases IND msm. Again, u will have to check box for lite firehose for it to work.
Also another thing to note...u really need to use regular style USB cable. Not newer ones that are C to C. If u haven't tried the cable problem I'd go back and try older style cable with correct msm tool b4 trying IND msm.
Click to expand...
Click to collapse
I use USB C to USB C 3.2 with no issues

Shooter7889 said:
Sorry for your situation...for future concerns, once u unlock bootloader, theres nothing other than msm that will relock it. As far as restoring your phone, I've seen where some ppl who can't find luck with their correct msm tool, they've had to use EU, or in most cases IND msm. Again, u will have to check box for lite firehose for it to work.
Also another thing to note...u really need to use regular style USB cable. Not newer ones that are C to C. If u haven't tried the cable problem I'd go back and try older style cable with correct msm tool b4 trying IND msm.
Click to expand...
Click to collapse
thanks for the reply. Actually, I upgraded through MSM Tmo-EU and then took system updates up til the latest A12 OTA... after installing A13 .16 that I got through Oxygen updater, I was no longer able to unlock the bootloader! I cant remember ever relocking it but either way, I couldnt unlock on Android 13 stable.
I'm beginning to wonder if maybe it's this Windows 7 pc thats giving me problems. but I've successfully used it before to MSM... just did my OnePlus 7t to get it back to working state while I try to figure out this 9pro situation. I've tried several cables and all of the MSMs at this point. I'm getting "device doesnt match image" a lot now. With my luck, I got home to try my laptop and the harddrive has crapped out on it! ha
I wonder if theres a way to modify the MSM tool to just flash to any Oneplus 9pro without identifying the variant. I know that would be dangerous, but at this point I just need SOMETHING to work! Or the next option is sending it back to OnePlus under warranty (I didnt request an unlock token etc so should still be good)

BTW, I've been doing this whole rooting/roming thing for a long time and I've also manually flashed through fastboot 100 times on different devices. I have NEVER ended up not being able to boot in to bootloader etc. I still dont understand how I lost bootloader and recovery etc flashing what I did,. Any ideas?

mbj731 said:
BTW, I've been doing this whole rooting/roming thing for a long time and I've also manually flashed through fastboot 100 times on different devices. I have NEVER ended up not being able to boot in to bootloader etc. I still dont understand how I lost bootloader and recovery etc flashing what I did,. Any ideas?
Click to expand...
Click to collapse
I'm not sure either. So after u converted using conversion tool, u booted into OS and then u needed to unlock BL once more, correct? It's strange u lost bootloader/recovery completely.

Shooter7889 said:
I'm not sure either. So after u converted using conversion tool, u booted into OS and then u needed to unlock BL once more, correct? It's strange u lost bootloader/recovery completely.
Click to expand...
Click to collapse
Yes, I had been running on A13 for a few days. Got the itch to root but as I said, I couldnt unlock bootloader (kept saying to flash token) so I decided to start the whole process over, unlock the bootloader and try to manually flash A13 instead of doing a local upgrade. (hadnt hit OTA for me yet)
During the process, theres a point where you have to boot in to fastbootD to flash critical partitions that wont flash in regular fastboot.... using the commands "fastboot reboot fastboot" wouldnt get me to fastbootD as I read it's supposed to. I think during all that and scrolling through the bootloader menu, I hit "recovery mode" which was apparently wiped because I just went straight to a black screen and thats where it's been ever since. I did all the button combos etc thinking it would just go back to bootloader but to no avail.
I wish there was a way to do manual commands in EDL or something. Maybe bootloader is there just that it's not responding to the hardware keys?

Oh. When u tried to unlock BL did u try "fastboot oem unlock? Yeh usually, eben if I mess up with msm or flashing imgs, it will kind of get stuck in edl, and I have to hold all three hardware buttons for some time b4 it will finally respond

Have you tried any of the older "all in one tools/fastboot enhance" posted on here in the past for older OP devices to see if they can do anything
Also, when I've had trouble in there past trying to find the right msm tool to work, each time I try one, if it shows connected on pc, then I try to run it, even if it fails, it kind of bricks edl, so I'd have to hold all three buttons to reset edl then try again(and it takes a little longer to respond than normal). If ur out of options other than returning it, id try the IND msm, check "lite firehose" and uncheck "sha256 check" and see if u have any luck

First I'd try holding all 3 buttons an UNGODLY long period of time and see if it finally boots to bootloader. Sometimes it takes for ever to shut down and restart. Then plug into pc use a USB 2 port if you have one. If pc sees the phone. If it does try adb devices in cmd terminal. If it list device try adb reboot bootloader and see if it boots.

kjslabber said:
First I'd try holding all 3 buttons an UNGODLY long period of time and see if it finally boots to bootloader. Sometimes it takes for ever to shut down and restart. Then plug into pc use a USB 2 port if you have one. If pc sees the phone. If it does try adb devices in cmd terminal. If it list device try adb reboot bootloader and see if it boots.
Click to expand...
Click to collapse
I taped all the buttons down and I'll watch it for a while and see if it boots up. I have tried holding them for a very good while with no luck already though

Shooter7889 said:
Have you tried any of the older "all in one tools/fastboot enhance" posted on here in the past for older OP devices to see if they can do anything
Also, when I've had trouble in there past trying to find the right msm tool to work, each time I try one, if it shows connected on pc, then I try to run it, even if it fails, it kind of bricks edl, so I'd have to hold all three buttons to reset edl then try again(and it takes a little longer to respond than normal). If ur out of options other than returning it, id try the IND msm, check "lite firehose" and uncheck "sha256 check" and see if u have any luck
Click to expand...
Click to collapse
I've tried the IND MSM gives me an "unsuspected target TMO" error or something like that. So at least some tools are seeing it as TMo... Tmo tools say the device doesnt match! I'll have to find another computer or 2 to try.. I was supposed to ship off my oneplus 7t tomorrow for trade in on this 9 pro but now I'm using the 7t again as it's my only working device. this has been a headache. lol
thanks for the feedback. I'm trying everything I can think of and researching too

Whew! I finally got it using EU MSM and the perfect combonation of cord/usb port, I guess. I had 3 cords, 10 usb ports and 5-6 MSMtools and after 2 days and probably 8+ hours of trying, I got my phone to boot again. lol

mbj731 said:
Whew! I finally got it using EU MSM and the perfect combonation of cord/usb port, I guess. I had 3 cords, 10 usb ports and 5-6 MSMtools and after 2 days and probably 8+ hours of trying, I got my phone to boot again. lol
Click to expand...
Click to collapse
Every one of us that's been at this long enough has gone thru this or a similar experience. It's a lot more headache but you also learn a lot more for the next time or to help others. Congrats on getting it up

mbj731 said:
thanks for the reply. Actually, I upgraded through MSM Tmo-EU and then took system updates up til the latest A12 OTA... after installing A13 .16 that I got through Oxygen updater, I was no longer able to unlock the bootloader! I cant remember ever relocking it but either way, I couldnt unlock on Android 13 stable.
I'm beginning to wonder if maybe it's this Windows 7 pc thats giving me problems. but I've successfully used it before to MSM... just did my OnePlus 7t to get it back to working state while I try to figure out this 9pro situation. I've tried several cables and all of the MSMs at this point. I'm getting "device doesnt match image" a lot now. With my luck, I got home to try my laptop and the harddrive has crapped out on it! ha
I wonder if theres a way to modify the MSM tool to just flash to any Oneplus 9pro without identifying the variant. I know that would be dangerous, but at this point I just need SOMETHING to work! Or the next option is sending it back to OnePlus under warranty (I didnt request an unlock token etc so should still be good)
Click to expand...
Click to collapse
You can use python3 to decrypt the .ops file, edit the first line parameters in the settings.ini, then python3 to encrypt the folder that was decrypted. Slow process but gives extra options.....

Stuck in Fastboot. Can't boot to anything except fastboot. Flashing stock ROM does not help.

Hello everyone.
Wifes Redmi Note 8 Pro (begonia) is stuck in fastboot. I have tried to flashing stock rom (many different versions) using MiFlash (have tried two different versions of MiFlash) and phone still stuck in pure fastboot. When I restart it, then it go straight to fastboot.
I have tried to flash custom recovery - TWRP (many different versions), but can't boot into it. Commands like "fastboot reboot recovery" or "fastboot boot twrp.img" does nothing - it restart, but again go straight into fastboot.
Commands like "fastboot flash recovery twrp.img" success, but can't boot to recovery.
Phone is unlocked and all flashing ends with SUCCESS message.
Have also tried flashing using SP FlashTool as it's in this video
it also ends with SUCCESS message, but phone is still stuck in fastboot screen only. Tried to flash it with battery, without battery, but it had no difference.
This stuck happened, after official MIUI freezed and none of hardware buttons worked. Battery died, phone went off. Then I have powered it and then this pure fastboot happened.. I have checked hardware buttons, but they works correctly.
Spoiler: Some screenshots..
{
"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"
}
Please if anyone know what to do with this except throwing it out from the window, I would appreciate it.
Thank you in advance!

Growicek said:
Hello everyone.
Wifes Redmi Note 8 Pro (begonia) is stuck in fastboot. I have tried to flashing stock rom (many different versions) using MiFlash (have tried two different versions of MiFlash) and phone still stuck in pure fastboot. When I restart it, then it go straight to fastboot.
I have tried to flash custom recovery - TWRP (many different versions), but can't boot into it. Commands like "fastboot reboot recovery" or "fastboot boot twrp.img" does nothing - it restart, but again go straight into fastboot.
Commands like "fastboot flash recovery twrp.img" success, but can't boot to recovery.
Phone is unlocked and all flashing ends with SUCCESS message.
Have also tried flashing using SP FlashTool as it's in this video
it also ends with SUCCESS message, but phone is still stuck in fastboot screen only. Tried to flash it with battery, without battery, but it had no difference.
This stuck happened, after official MIUI freezed and none of hardware buttons worked. Battery died, phone went off. Then I have powered it and then this pure fastboot happened.. I have checked hardware buttons, but they works correctly.
Spoiler: Some screenshots..
Please if anyone know what to do with this except throwing it out from the window, I would appreciate it.
Thank you in advance!
Click to expand...
Click to collapse
Try to press Volume down hard for 50 times. Then try to throw from high to the pilow/blanket many times. It's usually a hardware problem (Volume down got stuck). If they can't get help, you can try flash Engineer rom to test.

Kirasu2080 said:
Try to press Volume down hard for 50 times. Then try to throw from high to the pilow/blanket many times. It's usually a hardware problem (Volume down got stuck). If they can't get help, you can try flash Engineer rom to test.
Click to expand...
Click to collapse
I have tried to replace hardware buttons from another device. Problem is still here.

Made the experience that USB cables can be faulty. You can charge the phone with this cable. But you can't establish a working data connection with this cable. Sometimes it looks like it works, but it doesn't really ... you have weird behaviour. Therefore it is always a good idea to have many USB cables to switch.
Suggestion:
At first get Google's up-to-date ADB and fastboot: Linux or Windows.
Then get the latest TWRP recovery for begonia.
Then boot your device to bootloader mode.
Now try the boot-option within fastboot:
fastboot boot <twrp-recovery>.img
(Maybe try different USB-cables if this fails)
Now you can install/update TWRP within this booted TWRP instance
--> switch to install image and choose the recovery partition to install it.
HTH

shutdown-h_now said:
Made the experience that USB cables can be faulty. You can charge the phone with this cable. But you can't establish a working data connection with this cable. Sometimes it looks like it works, but it doesn't really ... you have weird behaviour. Therefore it is always a good idea to have many USB cables to switch.
Suggestion:
At first get Google's up-to-date ADB and fastboot: Linux or Windows.
Then get the latest TWRP recovery for begonia.
Then boot your device to bootloader mode.
Now try the boot-option within fastboot:
fastboot boot <twrp-recovery>.img
(Maybe try different USB-cables if this fails)
Now you can install/update TWRP within this booted TWRP instance
--> switch to install image and choose the recovery partition to install it.
HTH
Click to expand...
Click to collapse
Have tried two different cables. Fastboot boot recovery.img says success, but it loads back to fastboot.

Growicek said:
Have tried two different cables. Fastboot boot recovery.img says success, but it loads back to fastboot.
Click to expand...
Click to collapse
You really updated your fastboot?
Maybe try a different USB-port --> USB-ports on the back of your PC should works best.
The ones on the front plate of your PC are sometimes not satisfying!
And try another USB-cable (lend one from a friend).

shutdown-h_now said:
You really updated your fastboot?
Maybe try a different USB-port --> USB-ports on the back of your PC should works best.
The ones on the front plate of your PC are sometimes not satisfying!
And try another USB-cable (lend one from a friend).
Click to expand...
Click to collapse
Im using laptop. With same laptop, same cables I was able to restore few other phones in the past. Fastboot.exe is updated

Growicek said:
Im using laptop. With same laptop, same cables I was able to restore few other phones in the past. Fastboot.exe is updated
Click to expand...
Click to collapse
Have no ideas anymore.
Laptops / Notebooks are not my domain.
Maybe you should really try a PC of a friend ...

shutdown-h_now said:
Have no ideas anymore.
Laptops / Notebooks are not my domain.
Maybe you should really try a PC of a friend ...
Click to expand...
Click to collapse
I will give it a try

Original USB-C Cable from new Note 11 Pro 5G.
Have tried all of those with and also without battery.
mtkclient-gui for unlocking bootloader - SUCCESS
MiFlash 2020.3.14.0 flashing fastboot ROM - SUCCESS
Phone still in FASTBOOT mode.
____________________________________________________________________________
Latest ADB and Fastboot from your link
twrp-3.7.0_9-0-begonia.img
fastboot boot twrp-3.7.0_9-0-begonia.img - FAIL due to locked state
mtkclient-gui for unlocking bootloader - SUCCESS
Sending 'boot.img' (31380 KB) OKAY [ 0.688s]
Booting OKAY [ 0.062s]
Finished. Total time: 0.781s
Phone restarts back to FASTBOOT mode.
___________________________________________________________________________
mtkclient-gui for bypass SLA/DAA - SUCCESS
SP Flash Tool with: BegoniaDAfilesandAuthfile\MTK_AllInOne_DA_mt6765_mt6785.bin
BegoniaDAfilesandAuthfile\auth_sv5.auth
LATEST firmware
Download Only - SUCCESS
Phone restarts back to FASTBOOT mode.
___________________________________________________________________________
mtkclient-gui for bypass SLA/DAA - SUCCESS
SP Flash Tool with: BegoniaDAfilesandAuthfile\MTK_AllInOne_DA_mt6765_mt6785.bin
BegoniaDAfilesandAuthfile\auth_sv5.auth
ENGINEER ROM
Download Only - SUCCESS
Phone restarts normally!
____________________________________________________________________________
mtkclient-gui for bypass SLA/DAA - SUCCESS
SP Flash Tool with: BegoniaDAfilesandAuthfile\MTK_AllInOne_DA_mt6765_mt6785.bin
BegoniaDAfilesandAuthfile\auth_sv5.auth
LATEST firmware
Download Only - SUCCESS
Phone restarts normally to latest firmware.
Thank you very very very much for help. TIll today I didn't even know, that anything like ENGINEER ROM exists.
For everyone else, who whill have same problem. Try to flash ENGINEER ROM, then classic FIRMWARE.

Growicek said:
Original USB-C Cable from new Note 11 Pro 5G.
Have tried all of those with and also without battery.
mtkclient-gui for unlocking bootloader - SUCCESS
MiFlash 2020.3.14.0 flashing fastboot ROM - SUCCESS
Phone still in FASTBOOT mode.
____________________________________________________________________________
Latest ADB and Fastboot from your link
twrp-3.7.0_9-0-begonia.img
fastboot boot twrp-3.7.0_9-0-begonia.img - FAIL due to locked state
mtkclient-gui for unlocking bootloader - SUCCESS
Sending 'boot.img' (31380 KB) OKAY [ 0.688s]
Booting OKAY [ 0.062s]
Finished. Total time: 0.781s
Phone restarts back to FASTBOOT mode.
___________________________________________________________________________
mtkclient-gui for bypass SLA/DAA - SUCCESS
SP Flash Tool with: BegoniaDAfilesandAuthfile\MTK_AllInOne_DA_mt6765_mt6785.bin
BegoniaDAfilesandAuthfile\auth_sv5.auth
LATEST firmware
Download Only - SUCCESS
Phone restarts back to FASTBOOT mode.
___________________________________________________________________________
mtkclient-gui for bypass SLA/DAA - SUCCESS
SP Flash Tool with: BegoniaDAfilesandAuthfile\MTK_AllInOne_DA_mt6765_mt6785.bin
BegoniaDAfilesandAuthfile\auth_sv5.auth
ENGINEER ROM
Download Only - SUCCESS
Phone restarts normally!
____________________________________________________________________________
mtkclient-gui for bypass SLA/DAA - SUCCESS
SP Flash Tool with: BegoniaDAfilesandAuthfile\MTK_AllInOne_DA_mt6765_mt6785.bin
BegoniaDAfilesandAuthfile\auth_sv5.auth
LATEST firmware
Download Only - SUCCESS
Phone restarts normally to latest firmware.
Thank you very very very much for help. TIll today I didn't even know, that anything like ENGINEER ROM exists.
For everyone else, who whill have same problem. Try to flash ENGINEER ROM, then classic FIRMWARE.
Click to expand...
Click to collapse
Good to know, saw some with these kind of problems. Some can get out by engineer rom and some not. You're one of the lucky guy

Are you still facing the issue ???
Sorry for my bad English!!
I'm a Mobile technician,and this method work for me!!
I have tried this with my Redmi k20 !!
It's a lengthy process !! But it will help you !!
1)- Extract the Fastboot rom
2)- copy adb files from your adb/ platform tools folder and copy it into the extracted Fastboot rom folder !
3)- open ' images ' folder from extracted rom
4)- connect your device
5) open cmd in images folder ( shift+ right click- open command window here)
6) type in cmd :-
fastboot devices
fastboot flash boot boot.img
fastboot flash system system.img
( Wait for some time - 5 min atleast )
fastboot flash vendor vendor.img
( Wait for 3-5 min )
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
fastboot flash userdata userdata.img
fastboot reboot
7) your phone will automatically restart
( But still there will be no recovery or full rom..but it will just restart to miui- setup page )
8) again connect your phone in fastboot
9) open extracted Fastboot rom folder
10) run as administrator (or double tap ) the file -
" flash all.bat "
11) wait and watch --- it will take around 15 mins
12) your phone will automatically restarts
13) check the stock recovery is appeard or not ( it will definitely show the recovery )
14) done !! Enjoy