Develop Bugs

[GUIDE] How to bypass authentication and flash in EDL with NO auth for FREE

Thanks to:
chaosmaster / k4y0z: GitHub / XDA
xyzz / xyz`: GitHub / XDA
Dinolek: GitHub / XDA
How to install:
1. Download the attached file: VD171_MTK-bypass.zip.
2. Extract the file and open the folder.
3. Run and install python: python-3.9.1-amd64.exe.
Keep atention: You need to select "Add Python to PATH" before starting the installation.
{
"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"
}
4. Open cmd or powershell and execute this command:
pip install pyusb pyserial json5
5. Go to the Driver folder and right-click on the cdc-acm.inf file, then click Install and then, close window.
6. Run and install filter wizard: libusb-win32-devel-filter-1.2.6.0.exe.
7. Launch filter wizard.
8. Select Install a device filter and click Next.
9. Connect powered off phone with volume- button to boot in EDL mode.
10. Once you see new MediaTek USB Port in the list, select it and click Install.
Now, you are ready for bypassing EDL !
How to bypass:
1. Go to the Bypass folder. Run the script: bypass.bat.
2. Connect powered off phone with volume- button to boot in EDL mode.
3. Once you get "Protection disabled" at the end, without disconnecting phone and usb, run SP Flash Tool.
4. Once the SP Flash Tool opens, click Options > Options > Connection.
5. Select UART mode and select Baud rate to 921600.
Now, you are ready for flashing !
How to update:
1. Download latest release of the tool: https://github.com/MTK-bypass/bypass_utility/releases/latest
2. Download latest release of payloads: https://github.com/MTK-bypass/exploits_collection/releases/latest
3. Extract the content of both files to the Bypass folder.
Now, you are updated !
How does the bypass work?
Dissecting a MediaTek BootROM exploit
A bricked Xiaomi phone led me to discover a project in Github that uses a MediaTek BootROM exploit that was undocumented. The exploit was found by Xyz, and implemented by Chaosmaster. The initial exploit was already available for quite a while. Since I have managed to revive my phone, I am documenti
tinyhack.com
All Credits To:
chaosmaster / k4y0z: GitHub / XDA
xyzz / xyz`: GitHub / XDA
Dinolek: GitHub / XDA
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4225163/
#NoAuth #NoAuthentication #No-Auth #No-Authentication #MediaTek #Xiaomi
#MiAuth #MiAuthentication #Mi-Auth #Mi-Authentication #XiaoMiAuth #free
#XiaoMiAuthentication #XiaoMi-Auth #XiaoMi-Authentication #unbricking
#unbricked #unbrick
#MTK #MT6572 #MT6735 #MT6737 #MT6739 #MT6750 #MT6765 #MT6762
#MT6761 #MT6768 #MT6771 #MT6785 #MT8127 #MT8163 #MT8173 #MT8695

Good job, The guide helped a guy in telegram group unbrick his device.
Thanks for this

Communos said:
Good job, The guide helped a guy in telegram group unbrick his device.
Thanks for this
Click to expand...
Click to collapse
Good work, my friend
It solves all our problems for unbricking

woah this can speed up custom rom development for the device, just like the factory images on redmi note 8 pro, i hope lots of people see this!

Hi bro,
I have a problem with the bypass, when executing the .bat, it throws me the error in the image. I have been trying to do the process for a few days but the error is the same, it is a Redmi 9 (Lancelot) is on brick due to bad flashing. Do you know if there is any solution to this? I already tried disconnecting the battery and it doesn't even work.
Thanks for this great contribution

DavitidzeSh said:
woah this can speed up custom rom development for the device, just like the factory images on redmi note 8 pro, i hope lots of people see this!
Click to expand...
Click to collapse
It's already going good, LineageOS already out, Pixel Experience Plus released today, Few devs working on Other android Q roms, while 2 others are working on Android R tree

Communos said:
It's already going good, LineageOS already out, Pixel Experience Plus released today, Few devs working on Other android Q roms, while 2 others are working on Android R tree
Click to expand...
Click to collapse
Pixel Experience Released? Woah, I tried LineageOS and Its good for now, a few bugs here and there but it's good. I can't believe this is happening

Communos said:
It's already going good, LineageOS already out, Pixel Experience Plus released today, Few devs working on Other android Q roms, while 2 others are working on Android R tree
Click to expand...
Click to collapse
tbh it doesnt matter if its Q or R, If its stable im down

Communos said:
It's already going good, LineageOS already out, Pixel Experience Plus released today, Few devs working on Other android Q roms, while 2 others are working on Android R tree
Click to expand...
Click to collapse
btw, a link to pixel experience ROM? i can't find it

PathBoy92 said:
Hi bro,
I have a problem with the bypass, when executing the .bat, it throws me the error in the image. I have been trying to do the process for a few days but the error is the same, it is a Redmi 9 (Lancelot) is on brick due to bad flashing. Do you know if there is any solution to this? I already tried disconnecting the battery and it doesn't even work.
Thanks for this great contribution
View attachment 5219139
Click to expand...
Click to collapse
Apparentely you need to reinstall drivers and the device filter.
Try removing the device filter first and then reinstalling it too.
If you can, try in another computer.
Try to download and use the attached zip file, it is preconfigured to MT6768.
I get the exactly message you got with missconfigured drivers and device.
Certainly you need to check them.

DavitidzeSh said:
btw, a link to pixel experience ROM? i can't find it
Click to expand...
Click to collapse
PixelExperience_Plus_merlin-10.0-20210212-0344-UNOFFICIAL.zip | by itexpert120 for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com

Communos said:
PixelExperience_Plus_merlin-10.0-20210212-0344-UNOFFICIAL.zip | by itexpert120 for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Click to expand...
Click to collapse
Thanks, Do I need 12.0.3 to install this?

DavitidzeSh said:
woah this can speed up custom rom development for the device, just like the factory images on redmi note 8 pro, i hope lots of people see this!
Click to expand...
Click to collapse
I hope we can see all the partitions on this device demystified too.
There are many unused things on the device.
Many partitions have large sizes for few contents.
Other partitions are never used.
I would really like to know what they are all for.

I have tried with two different PCs and the result is always the same, I already tried uninstalling the drivers and installing everything again.

VD171 said:
I hope we can see all the partitions on this device demystified too.
There are many unused things on the device.
Many partitions have large sizes for few contents.
Other partitions are never used.
I would really like to know what they are all for.
Click to expand...
Click to collapse
to be honest i dont know anything about partitions. if it has potential value then im interested

PathBoy92 said:
I have tried with two different PCs and the result is always the same, I already tried uninstalling the drivers and installing everything again.
Click to expand...
Click to collapse
Probably it is not fully compatible with Lancelot.
I'm not sure.
I've tried with Dandelion (Redmi 9A / MT6765) and I can't bypass too.
But with Merlin, it works like a charm.
We need to keep watching the project and hope for newer releases as soon possible

VD171 said:
Probably it is not fully compatible with Lancelot.
I'm not sure.
I've tried with Dandelion (Redmi 9A / MT6765) and I can't bypass too.
But with Merlin, it works like a charm.
We need to keep watching the project and hope for newer releases as soon possible
Click to expand...
Click to collapse
Stay tuned for updates, thanks!

PathBoy92 said:
Stay tuned for updates, thanks!
Click to expand...
Click to collapse
I've attached a new zip file with the soon released files.
Please, try again and good luck

DavitidzeSh said:
Thanks, Do I need 12.0.3 to install this?
Click to expand...
Click to collapse
Would work on the same vendors needed for Lineage.

DavitidzeSh said:
Thanks, Do I need 12.0.3 to install this?
Click to expand...
Click to collapse
Pixel Experience doesn't work

Question Global ROM for Xiaomi Pad 5 (nabu)

Hi Guys,
Is there any update on the Global ROM of Xiaomi Pad 5 yet?
It is known that the global version of the tablet is being delivered at retail shops.
Bootloader Unlock has been done well so far, just waiting for the Global ROM.
Here are the reasons I must wait for the Global ROM:
1. Sogou Keyboard does not support well my local texts, especially with the physical keyboards (which I have already purchased thru shopee ~100USD ).
2. Sogou Keyboard automatically reverts back "default" keyboard after reboot even Gboard had been set to Default keyboard.
3. Bloatware, Fonts are horrible
4. No NEARBY SHARE found on the current China ROM 12.5.9.
Thank you!
--------------- Update Oct 13 2021 --------------------
You can flash the Global ROM now, it is available finally!
Do make sure:
1. You have completely unlocked your Xiaomi Pad 5 (bind Mi Account and wait 168hrs), enter Pad 5 to fastboot mode, connect Pad 5 to PC, run Unlock Tool on PC to check Pad 5 is successfully unlocked, it should state "Unlocked" with your device ID.
2. Choose "Clear All" option in XiaoMi Flash Tool to make sure that you will have a brand new ROM on the Device. Remember enter the right Directory Path to ROM folder.
3. There is an error at the end (something like your miss abc file...), that says your have successfully installed the Global ROM to your China Pad 5.
{
"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"
}
Links:
ROM Global: https://bigota.d.miui.com/V12.5.4.0...tZJOW_UXciRi5K230s3LRK6Tmhweh_WpLfIzRt3TYcGkA
XiaoMi Flash Tool: https://www.xiaomiflash.com/downloads/MiFlash20181115.zip
XiaoMi Unlock Tool: https://miuirom.xiaomi.com/rom/u1106245679/5.5.224.24/miflash_unlock-en-5.5.224.24.zip

How did you manage to unlock on the global computer? I can't do anything at all. the tablet is linked to the account. but when unlocking, writes: bind in developer mode. But in the tablet itself I can not bind

cezarek90 said:
How did you manage to unlock on the global computer? I can't do anything at all. the tablet is linked to the account. but when unlocking, writes: bind in developer mode. But in the tablet itself I can not bind
Click to expand...
Click to collapse
an error msg? its not the first time I have seen this problem

You should try with another PC/Laptop.
Make sure you have installed Xiaomi/Android Drivers, Enable Debugging Mode.
Check your USB port, Open the Xiaomi Unlock to check if your PC recognizes the Xiaomi Device when it is in fastboot mode.

Here's a mistake.
Spoiler: spoiler

I have the same "Request parameter error". Waiting to find something or an updated ROM.

Can confirm, same error shows up on my global Pad 5. I hope it will be fixed with a software update, I can't live without root lol

tikkalamt said:
I have the same "Request parameter error". Waiting to find something or an updated ROM.
Click to expand...
Click to collapse
me too....

we are all with the same problem in the global rom, we need root and a global rom to flash

I don't know what is taking them so much time to solve the unlock issue and release a global rom ! Plus release the kernel source !

xmae said:
we are all with the same problem in the global rom, we need root and a global rom to flash
Click to expand...
Click to collapse
The Global ROM is supposed to be here, however, I don't know why it is a blank page.
https://c.mi.com//miuidownload/detail?device=1900402

I don't know why is taking so much time to have an available global rom & to fix the unlock bootloader issue !

lakyman said:
I don't know why is taking so much time to have an available global rom & to fix the unlock bootloader issue !
Click to expand...
Click to collapse
They just release 12.5.10, but for China version only!!!

I ended up ordering a China version of the Xiaomi 5 (in Canada) and I am hoping that I can load the Global ROM on it once its available. Please tell me you can.
This is my first ever Xiaomi device.

puleen said:
I ended up ordering a China version of the Xiaomi 5 (in Canada) and I am hoping that I can load the Global ROM on it once its available. Please tell me you can.
This is my first ever Xiaomi device.
Click to expand...
Click to collapse
Definitely you can, but we need to wait!!!

uybaky said:
Definitely you can, but we need to wait!!!
Click to expand...
Click to collapse
I hear you friend, I guess I am just impatient. Waiting for my tablet to arrive, and want to get it to be Global-ified as soon as it arrives. As a newbie, I also hope the steps to load the Global ROM are idiot-proof.

The global rom is finally available but i can't unlock the bootloader for now !

lakyman said:
The global rom is finally available but i can't unlock the bootloader for now !
Click to expand...
Click to collapse
I bind xiaomi account successfully, and now wait about 5 days to unlock. Check it every day, I think your Pad will be get fixed soon.
Unlock Bootloader - "Request parameter error"
Tried to unlock bootloader using developer option "Mi unlock status". Whenever I press the "Add account and device" always give me this error! "Request parameter error" Does it happen also to you? any ideas to solve this problem?
forum.xda-developers.com

puleen said:
I hear you friend, I guess I am just impatient. Waiting for my tablet to arrive, and want to get it to be Global-ified as soon as it arrives. As a newbie, I also hope the steps to load the Global ROM are idiot-proof.
Click to expand...
Click to collapse
You can flash the Global ROM now, it is available finally!
Do make sure:
1. You have completely unlocked your Xiaomi Pad 5, enter fastboot mode, connect to PC, run Unlock Tool to check, it should state "Unlocked" with your device ID.
2. Choose "Clear All" option in XiaoMi Flash Tool to make sure that you will have a brand new ROM on the Device.
3. There is an error at the end (something like your miss abc file...), that says your have successfully installed the Global ROM to your China Pad 5.
Links:
ROM Global: https://bigota.d.miui.com/V12.5.4.0...tZJOW_UXciRi5K230s3LRK6Tmhweh_WpLfIzRt3TYcGkA
XiaoMi Flash Tool: https://www.xiaomiflash.com/downloads/MiFlash20181115.zip
XiaoMi Unlock Tool: https://miuirom.xiaomi.com/rom/u1106245679/5.5.224.24/miflash_unlock-en-5.5.224.24.zip

uybaky said:
You can flash the Global ROM now, it is available finally!
Do make sure:
1. You have completely unlocked your Xiaomi Pad 5, enter fastboot mode, connect to PC, run Unlock Tool to check, it should state "Unlocked" with your device ID.
2. Choose "Clear All" option in XiaoMi Flash Tool to make sure that you will have a brand new ROM on the Device.
3. There is an error at the end (something like your miss abc file...), that says your have successfully installed the Global ROM to your China Pad 5.
Links:
ROM Global: https://bigota.d.miui.com/V12.5.4.0...tZJOW_UXciRi5K230s3LRK6Tmhweh_WpLfIzRt3TYcGkA
XiaoMi Flash Tool: https://www.xiaomiflash.com/downloads/MiFlash20181115.zip
XiaoMi Unlock Tool: https://miuirom.xiaomi.com/rom/u1106245679/5.5.224.24/miflash_unlock-en-5.5.224.24.zip
Click to expand...
Click to collapse
Sweet, my tablet arrived today, so I will give this a shot tonight or tomorrow.

Question Op9 hard brick

So mine device was T le2127 mobile and i try to play with param and flashed wrong fastboot "developer preview" ota zip by force and device now just show FB mode and reboot even not able to take any msm tool file
Not T mobile or not indian file
Just invaild trg id
Even i follow the thread flash by python
But getting this
According to pick the parts done flashed but as u see its 0mb
Not flashed any single file
Si is there anyway to fix my device back?
{
"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"
}

Why is not working with MSM tool exactly, share more details?

Googling your error brings up these 2 links:
Oneplus 9 Pro (oneplus - Oneplus protection with prjid 19815 detected) · Issue #195 · bkerler/edl
I have the Oneplus 9 Pro T-MO [LE-2127] Project="2085A" I was trying to convert the phone back to its stock image and I used the SMT Download in MSM with the Indian image. [which I realize was a mi...
github.com
bkerler,edl
bkerler,edl | Error Oneplus 9 "Oneplus protection with prjid 18821 detected"
githubhelp.com
I think param partition holds you device model id. Your partiotion table also is f*ked up, so it can't write partitions.
The second link mentioned that edl developer fixed some algorithm issue with it. So maybe redownload the edl package and try again?
Don't know nearly enough about this to help you more. Sorry. Maybe contact edl dev about it...

IamTheBRAVE said:
Googling your error brings up these 2 links:
Oneplus 9 Pro (oneplus - Oneplus protection with prjid 19815 detected) · Issue #195 · bkerler/edl
I have the Oneplus 9 Pro T-MO [LE-2127] Project="2085A" I was trying to convert the phone back to its stock image and I used the SMT Download in MSM with the Indian image. [which I realize was a mi...
github.com
bkerler,edl
bkerler,edl | Error Oneplus 9 "Oneplus protection with prjid 18821 detected"
githubhelp.com
I think param partition holds you device model id. Your partiotion table also is f*ked up, so it can't write partitions.
The second link mentioned that edl developer fixed some algorithm issue with it. So maybe redownload the edl package and try again?
Don't know nearly enough about this to help you more. Sorry. Maybe contact edl dev about it...
Click to expand...
Click to collapse
i update edl 2 days ago and my partitions is not completely gone becoz its still detects all luns with partitions name
there,s some mistake in process i think but what idk
but your links is also good but never founded any solve issue in such case
have you any other idea about it?

ekin_strops said:
Why is not working with MSM tool exactly, share more details?
Click to expand...
Click to collapse
here,s the more details you asked about. as i said i just flash ota update by force via tool the rom was not good now after that i,m facing this issue even i played with param and also i flash stock param.bin from stock and again try to flash stock msm but getting the same error

Mr Hassan said:
i update edl 2 days ago and my partitions is not completely gone becoz its still detects all luns with partitions name
there,s some mistake in process i think but what idk
but your links is also good but never founded any solve issue in such case
have you any other idea about it?
Click to expand...
Click to collapse
Your partitions may still be there but flashing a partition (param) from a diff model may have changed start/end position of each following partition so the Part.Table is not valid.
Another thing, your last screenshot shows error "no valid trg id". Googling it gives this solution:
MsmDownloadTool error
Hey @QuinnLIVE, which download did you use? Was your phone T-Mobile version?
forum.xda-developers.com
.

I think your main problem is model id is not recognized. My previous post should solve it. Then you may be able to reflash all partitions back to stock. Good luck.

IamTheBRAVE said:
Your partitions may still be there but flashing a partition (param) from a diff model may have changed start/end position of each following partition so the Part.Table is not valid.
Another thing, your last screenshot shows error "no valid trg id". Googling it gives this solution:
MsmDownloadTool error
Hey @QuinnLIVE, which download did you use? Was your phone T-Mobile version?
forum.xda-developers.com
.
Click to expand...
Click to collapse
Bro bro i fixed this but still have same issue in op8 and in 8 i used smt mode and its wipe all partitions and not able to flash with same error
Trg id should not be 0

IamTheBRAVE said:
I think your main problem is model id is not recognized. My previous post should solve it. Then you may be able to reflash all partitions back to stock. Good luck.
Click to expand...
Click to collapse
Bro bro i fixed this but still have same issue in op8 and in 8 i used smt mode and its wipe all partitions and not able to flash with same error
Trg id should not be 0

Did you switch the enum target to T-mo? That's the solution for the trg id problem you have.

Mr Hassan said:
Bro bro i fixed this but still have same issue in op8 and in 8 i used smt mode and its wipe all partitions and not able to flash with same error
Trg id should not be 0
Click to expand...
Click to collapse
Use indian MSM, check the box that says lite firehose and flash. Your device will permanently be switched to IN model but you will be able to boot.

IamTheBRAVE said:
Did you switch the enum target to T-mo? That's the solution for the trg id problem you have.
Click to expand...
Click to collapse
no bro there no such msm unfor and also i tried indian msm but no luck
even its make no sense so fixed by remotely someone i just paid little bit
but the major issue is now my device is single sim and it was dual in le2123
now i try flash le2123 ota with locked BL so its giving error in 25 or between 30%

razercortex said:
Use indian MSM, check the box that says lite firehose and flash. Your device will permanently be switched to IN model but you will be able to boot.
Click to expand...
Click to collapse
yes i tried bro but no luck
here,s the thread link plz have a look
Oneplus 8 dead after try unlock bootloader
Op8 i think its was T or V But after try to unlock bootloader its bricked and now not taking any flash file I tried many file but the only one error Trg id error So i try with smt even with imei loss risk And the result was as you see in pick...
forum.xda-developers.com

Question Vivo X80 Pro Firmware Rollback file

Hello Vivo X80 Pro community,
I'm having issues flashing the rollback file from the Android 13 Developer Preview: https://developer.vivo.com/doc/detail?id=120
{
"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"
}
My guess is that the hyperlink is linking towards a W30 ROM instead of a W20 ROM. PD2185F_EX_A_12.0.12.5.W20.V000L1-update-full.zip.
Does anyone have a rollback file for the W20 version of the X80 Pro that they can upload to androidfilehost or Google Drive please?
I heard 12.0.11.2 is the best version to do a bootloader unlock so I'm hoping someone has this one, but right now I'll be happy just to go back to Android 12.
Thanks in advance!

it's best to write to Vivo. I couldn't find anything on the internet. Vivo linked an incorrect file.
Service Center | vivo Global
vivo provides comprehensive after-sales services and technical support for products. Check where our service centers are in your location here.
www.vivo.com

I thing the problem is you have a PD2185BF, the roll back is PD2185F....

morpheus620 said:
it's best to write to Vivo. I couldn't find anything on the internet. Vivo linked an incorrect file.
Service Center | vivo Global
vivo provides comprehensive after-sales services and technical support for products. Check where our service centers are in your location here.
www.vivo.com
Click to expand...
Click to collapse
That was the first thing I tried but I was thinking that surely someone had the ROM downloaded.
dzontra83 said:
I thing the problem is you have a PD2185BF, the roll back is PD2185F....
Click to expand...
Click to collapse
This was the A13 file I used to update successfully, so it is likely that PD2185F is my model number.
PD2185F_EX_A_13.1.8.7.W20.V000L1-update-full.zip

hamisgood said:
Hello Vivo X80 Pro community,
I'm having issues flashing the rollback file from the Android 13 Developer Preview: https://developer.vivo.com/doc/detail?id=120
View attachment 5690991
My guess is that the hyperlink is linking towards a W30 ROM instead of a W20 ROM. PD2185F_EX_A_12.0.12.5.W20.V000L1-update-full.zip.
View attachment 5690989
Does anyone have a rollback file for the W20 version of the X80 Pro that they can upload to androidfilehost or Google Drive please?
I heard 12.0.11.2 is the best version to do a bootloader unlock so I'm hoping someone has this one, but right now I'll be happy just to go back to Android 12.
Thanks in advance!
Click to expand...
Click to collapse
Try doing a reset of network only. That worked for me in the past with this issue.

diopskill said:
Try doing a reset of network only. That worked for me in the past with this issue.
Click to expand...
Click to collapse
Would you still happen to have the file you used for the rollback? I have tried to factory reset and it still did not help with the boot issue. I've also reported this to their support and they are working on a fix, but I am not sure how long it would take.
Edit - They fixed the link for the rollback file. I will now try to unlock the bootloader.
Edit 2 - I tried flashing unlocking the bootloader but it seems like it cannot be unlocked due to the June security patch. I am still hoping someone here has the 12.0.11.2 version firmware and it works to flashback...

hamisgood said:
Would you still happen to have the file you used for the rollback? I have tried to factory reset and it still did not help with the boot issue. I've also reported this to their support and they are working on a fix, but I am not sure how long it would take.
Edit - They fixed the link for the rollback file. I will now try to unlock the bootloader.
Edit 2 - I tried flashing unlocking the bootloader but it seems like it cannot be unlocked due to the June security patch. I am still hoping someone here has the 12.0.11.2 version firmware and it works to flashback...
Click to expand...
Click to collapse
Yes I have it ..
PD2185F_EX_A_12.0.11.2-BWDATA.W20.V000L1-update-full_1652274124.zip
drive.google.com

hamisgood said:
Would you still happen to have the file you used for the rollback? I have tried to factory reset and it still did not help with the boot issue. I've also reported this to their support and they are working on a fix, but I am not sure how long it would take.
Edit - They fixed the link for the rollback file. I will now try to unlock the bootloader.
Edit 2 - I tried flashing unlocking the bootloader but it seems like it cannot be unlocked due to the June security patch. I am still hoping someone here has the 12.0.11.2 version firmware and it works to flashback...
Click to expand...
Click to collapse
Did you download it?

diopskill said:
Yes I have it ..
PD2185F_EX_A_12.0.11.2-BWDATA.W20.V000L1-update-full_1652274124.zip
drive.google.com
Click to expand...
Click to collapse
Hi I just requested access! Many thanks for uploading it

Really strange, I am getting this error when trying to flash the package.. I'm gonna try to reboot to recovery and see if this can be flashed..

hamisgood said:
View attachment 5695503
Really strange, I am getting this error when trying to flash the package.. I'm gonna try to reboot to recovery and see if this can be flashed..
Click to expand...
Click to collapse
I flashed thru recovery. Only way it worked for me.

diopskill said:
I flashed thru recovery. Only way it worked for me.
Click to expand...
Click to collapse
Strange I can't flash through recovery, the only option I get is update through network.. Did u get to recover via "adb reboot recovery" or is there different recovery I need to access?

hamisgood said:
Strange I can't flash through recovery, the only option I get is update through network.. Did u get to recover via "adb reboot recovery" or is there different recovery I need to access?
Click to expand...
Click to collapse
I did a reset settings Not the erase all option. That did it for me

diopskill said:
I did a reset settings Not the erase all option. That did it for me
Click to expand...
Click to collapse
What I meant is this, I don't have the option to select the rom file apparently.
A few days ago I did have the option which is why I'm confused now

hamisgood said:
What I meant is this, I don't have the option to select the rom file apparently.
A few days ago I did have the option which is why I'm confused now
Click to expand...
Click to collapse
Oh...
I have that after every time I switch between beta and stable. Reset all settings fixes it every time.

diopskill said:
Oh...
I have that after every time I switch between beta and stable. Reset all settings fixes it every time.
Click to expand...
Click to collapse
Thanks! I will try resetting tonight or tomorrow if I have the time.
I do want to root (been using rooted Android since the Kindle Fire -> Galaxy S3 -> G2 -> V20 -> OP3T -> OP5T -> OP7T), but I seem to be surviving without root after blocking Ads through using AdGuard on private DNS settings.
Not being able to freeze apps on Titanium Backup is a bit of a pain but my banking apps work perfectly is pretty good upside.

hamisgood said:
Thanks! I will try resetting tonight or tomorrow if I have the time.
I do want to root (been using rooted Android since the Kindle Fire -> Galaxy S3 -> G2 -> V20 -> OP3T -> OP5T -> OP7T), but I seem to be surviving without root after blocking Ads through using AdGuard on private DNS settings.
Not being able to freeze apps on Titanium Backup is a bit of a pain but my banking apps work perfectly is pretty good upside.
Click to expand...
Click to collapse
I'm in the exact same boat. As you!! Nothing else to add lol!

diopskill said:
Try doing a reset of network only. That worked for me in the past with this issue.
Click to expand...
Click to collapse
Did reset network, all settings, but nothing helped

After I try to install A13 zip and failed of course I am receiving notification for a new version. I install this version and after another failed try of A13 is giving me the same version to download and install. And this is every time I try to install A13 I get PD2185F_EX_A_12.0.13.1.W30.

Question FIXED: HELP!!! OnePlus 9 Pro No Recovery No Fastboot Only Crashdump Mode

Dear Community
I have a major issue with my OnePlus 9 Pro:
I had Nameless AOSP 13 installed and rooted.
I then tried to revert back to original OOS 13 using Advanced Fastboot and the original payload.bin.
But when I flashed the payload, I got stuck on the Qualcomm Crashdump Mode with no information and also no recovery mode.
{
"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"
}
So tutorials like these:
Simply don't work, since I don't have the menu to select fastboot / recovery, etc.
Of course I also tried MSMTool but that always fails at "Param preload failed" and I can't seem to fix it.
What can I do now?
Edit: This was also posted on the official OnePlus Forum because it's really urgent.
https://community.oneplus.com/thread/1293380945168039936
IMPORTANT:​I seem to have fixed the problem:​I basically had the wrong drivers installed, even though I downloaded them from oneplus for this exact phone.
I was able to fix the issue by installing the drivers via Windows Update. They will appear in the optional updates but that worked for me just fine.

trgyt said:
Dear Community
I have a major issue with my OnePlus 9 Pro:
I had Nameless AOSP 13 installed and rooted.
I then tried to revert back to original OOS 13 using Advanced Fastboot and the original payload.bin.
But when I flashed the payload, I got stuck on the Qualcomm Crashdump Mode with no information and also no recovery mode.
So tutorials like these:
Simply don't work, since I don't have the menu to select fastboot / recovery, etc.
Of course I also tried MSMTool but that always fails at "Param preload failed" and I can't seem to fix it.
What can I do now?
Click to expand...
Click to collapse
Param preload failed "AND" device not match image? In MSM?

TheGhost1951 said:
Param preload failed "AND" device not match image? In MSM?
Click to expand...
Click to collapse
So basically MSM says "Param preload failed" and I tried different USB Cables, etc.
The Image matched the device, I downloaded the payload.bin from here:
https://service.oneplus.com/global/search/search-detail?id=2096329&articleIndex=1
https://oxygenos.oneplus.net/OnePlus9ProOxygen_22.O.13_OTA_0130_all_2111112104_31a8871ffe6142d9.zip

trgyt said:
So basically MSM says "Param preload failed" and I tried different USB Cables, etc.
The Image matched the device, I downloaded the payload.bin from here:
https://service.oneplus.com/global/search/search-detail?id=2096329&articleIndex=1
https://oxygenos.oneplus.net/OnePlus9ProOxygen_22.O.13_OTA_0130_all_2111112104_31a8871ffe6142d9.zip
Click to expand...
Click to collapse
You have to use the msm tool what is for this devices
Is it a india device you have to use the india msm tool and enabel in msm tool firehose Lite
Is this a us model use us msm tool
On a eu devices use eu msm tool
I mean not the rom what is installed i mean the real device region
And hold pressed vol+ and vol- when you hold the two buttons not the op goes out from edl after 10-15 secends

trgyt said:
So basically MSM says "Param preload failed" and I tried different USB Cables, etc.
The Image matched the device, I downloaded the payload.bin from here:
https://service.oneplus.com/global/search/search-detail?id=2096329&articleIndex=1
https://oxygenos.oneplus.net/OnePlus9ProOxygen_22.O.13_OTA_0130_all_2111112104_31a8871ffe6142d9.zip
Click to expand...
Click to collapse
Double check in PC device manager that your phone is recognized in ports driver as 9008....

ChrisFeiveel84 said:
You have to use the msm tool what is for this devices
Is it a india device you have to use the india msm tool and enabel in msm tool firehose Lite
Is this a us model use us msm tool
On a eu devices use eu msm tool
I mean not the rom what is installed i mean the real device region
And hold pressed vol+ and vol- when you hold the two buttons not the op goes out from edl after 10-15 secends
Click to expand...
Click to collapse
The Device is a EU Model, I will try the Firehose Lite

TheGhost1951 said:
Double check in PC device manager that your phone is recognized in ports driver as 9008....
Click to expand...
Click to collapse
It is:

trgyt said:
The Device is a EU Model, I will try the Firehose Lite
Click to expand...
Click to collapse
This you need only on india devices and china devices
Eu and global use no firehose lite

ChrisFeiveel84 said:
This you need only on india devices and china devices
Eu and global use no firehose lite
Click to expand...
Click to collapse
Ohh ok, but why?

trgyt said:
Ohh ok, but why?
Click to expand...
Click to collapse
China and india device is not the same as global, eu or us model

ChrisFeiveel84 said:
China and india device is not the same as global, eu or us model
Click to expand...
Click to collapse
Ah thank you, but it still doesn't work :/
I still get the param preload failed error

trgyt said:
Ah thank you, but it still doesn't work :/
I still get the param preload failed error
Click to expand...
Click to collapse
You sure that this is an real eu devices (not flashed with eu rom )

ChrisFeiveel84 said:
You sure that this is an real eu devices (not flashed with eu rom )
Click to expand...
Click to collapse
I purchased this from switzerland off a site that is seated in switzerland
So I am pretty sure that it's flashed with eu?
Or could I be wrong?

trgyt said:
I purchased this from switzerland off a site that is seated in switzerland
So I am pretty sure that it's flashed with eu?
Or could I be wrong?
Click to expand...
Click to collapse
It's not about the firmware that has been flashed onto the 9p, but for which region it is made (do you still have the box from the cell phone? When you have the box from this phone look on the box is this a eu or india model )

ChrisFeiveel84 said:
It's not about the firmware that has been flashed onto the 9p, but for which region it is made (do you still have the box from the cell phone? When you have the box from this phone look on the box is this a eu or india model )
Click to expand...
Click to collapse
I do have the box, and the Model Number is LE2123 which is (as far as I am concerned) the EU Version.

trgyt said:
I do have the box, and the Model Number is LE2123 which is (as far as I am concerned) the EU Version.
Click to expand...
Click to collapse
Start msm tool (ooen it ) and make a reboot with the op9p and hold pressed the two buttons vol+ and vol- and try it with ensure (hope is corekt ) and than flash after you sea the op9p on the msm tool
Or can you boot to fastboot/fastnootd ?

ChrisFeiveel84 said:
Start msm tool (ooen it ) and make a reboot with the op9p and hold pressed the two buttons vol+ and vol- and try it with ensure (hope is corekt ) and than flash after you sea the op9p on the msm tool
Or can you boot to fastboot/fastnootd ?
Click to expand...
Click to collapse
Sooo I tried but it failed at the Param preload part again
I have to go to bed now otherwise I will probably break my monitor.

trgyt said:
Sooo I tried but it failed at the Param preload part again
I have to go to bed now otherwise I will probably break my monitor.
Click to expand...
Click to collapse
If fastboot is available you can try switching slots and reboot , worked for me when I was in crash dump, at least I was able to install a ROM then work my way back to stock

IMPORTANT:​I seem to have fixed the problem:​I basically had the wrong drivers installed, even though I downloaded them from oneplus for this exact phone.
I was able to fix the issue by installing the drivers via Windows Update. They will appear in the optional updates but that worked for me just fine.