Develop Bugs

[Rom][7.0]Lenovo ZUK Z2 PLUS (2132) INDIAN firmware V2.5.104ST using MI Flash tool

{
"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 am not responsible for anything that may happen to your phone as a result of installing custom roms and/or kernels. you do so at your own risk and take the responsibility upon yourself.
Part -A Configure Computer
1) Download and extract the Stock firmware, Setup tools & Drivers
2) Install ADB Drivers
3) Install Lenovo ZUK Z2 PLUS (2132) Drivers
4) Setup Tool all in one
5) Setup Mi Flash tool
Part -B Booting device in to EDL Mode
Note : Thank to @mauronofrio for his tool
1) Enable Android debugging (ADB) in developer options
2) Connect your device to PC
3) open Tool all in one
4) The tool detects your device and pop up a window on your z2 plus device
5) chick and click OK
6) Know go to Tool all in one > Advance Options
7) click Reboot EDL
8) Device will boot in to EDL Mode
Part -C Flashing stock Firmware
1) Open Mi Flash tool
2) Click on refresh to detect your Z2 plus as COM X ( Note : X represents device port numbers )
3) If you want to lock bootloader then select " clear all and lock " which was present on right bottom corner
4)Click on flash
Note : Never disconnect your device while MI tool was flashing
5) It take 300 sec to complete task after that hold power key for 15 sec to boot your device​
Lenovo ZUK Z2 Plus ( 2132) Nougat
Indian firmware ( Note : all partitions fixed by me :good: )
Mi Flash tool ( Note : Recommended and Modified version by Me for deep partitions:fingers-crossed: )
Tool All In One ( Note : for Booting in to EDL, flashing TWRP , Unlock & lock bootloader )
adb-setup ( Note : Very important )
Other useful links ( If you want )
Drivers
PdaNet
Qualcomm_QHSUSB
ZUK_Z2132_drivers_V1.0.5
Tools
QPST
@ZUK ................................... for device
@zukfans.eu ..................... for source
@Francko76 .................... for source
@xiaomi .............................. for MI Flash tool
@mauronofrio ................. for Tool All In One
@Annabathina .................. for fixing deep partitions
@XDA ................... developers for helping me
@lenovo forum ........... developers
Lenovo ZUK Z2 Plus ................. Model 2132​
XDA:DevDB Information
[Rom][7.0]Lenovo ZUK Z2 PLUS (2132) INDIAN firmware V2.5.104ST using MI Flash tool, ROM for the Lenovo ZUK Z2 (Plus)
Contributors
Annabathina
ROM OS Version: 7.x Nougat
Based On: Stock rom
Version Information
Status: Stable
Current Stable Version: 2.5.104ST
Stable Release Date: 2017-04-18
Created 2017-09-25
Last Updated 2017-09-25

Reserved

Reserved

RESERVED

Good to see you buddy.....loved your work in yu forums. Hope you will do same with thus device too.....looking forward
Sent from my Z2 Plus using Tapatalk

Anna in zuk z2 forum :silly::laugh:
Now this phone will rock

Dextron01 said:
Good to see you buddy.....loved your work in yu forums. Hope you will do same with thus device too.....looking forward
Click to expand...
Click to collapse
stop quoting op please...

Dextron01 said:
Good to see you buddy.....loved your work in yu forums. Hope you will do same with thus device too.....looking forward
Sent from my Z2 Plus using Tapatalk
Click to expand...
Click to collapse
Dont quote everything. Fvck!
El Psy Congroo

https://t.me/joinchat/ExDwekLF21qSDmOwudq3gg I suggest you to join here @Annabathina

Interesting! Will try it out.
Thanks a lot for sharing!
Update. Be careful when flashing! Selecting save user data still wipes the phone and locks the bootloader. I made a backup like a week ago so didn't lose important data.

Can I use QFIL to flash this?
El Psy Congroo

Magz Heaven said:
Can I use QFIL to flash this?
El Psy Congroo
Click to expand...
Click to collapse
of course you can but I did not tried on QFIL
it works excellent on Mi Flash tool including deep partitions , bootloader locking etc

daviduco said:
Is this stock indian? What modifications does it has?
Click to expand...
Click to collapse
Its just the Indian version without any chinese apps or bloatwares... Indian version lacks some features which are present in the Chinese version and has some bugs too

I have flash today the 7.0(as you given for downloading) firmware using mi flash tool the process was successful but after that I have tried to install AEX 4.6 but Volte was not working then I flashed the official 6.0 firmware using QFIL Volte we as enabled then I again tried to flash AEX but Volte was not working even I have turned on Volte in stock rom before flashing custom ROM
Any help?

kany1 said:
I have flash today the 7.0(as you given for downloading) firmware using mi flash tool the process was successful but after that I have tried to install AEX 4.6 but Volte was not working then I flashed the official 6.0 firmware using QFIL Volte we as enabled then I again tried to flash AEX but Volte was not working even I have turned on Volte in stock rom before flashing custom ROM
Any help?
Click to expand...
Click to collapse
wowo did you really flash a 7.x ROM on top of 6.x stock?

fallen.kn said:
wowo did you really flash a 7.x ROM on top of 6.x stock?
Click to expand...
Click to collapse
Before flashing with mi flash tool I was using AEX 4.6 and then i tried this flashing and when i was having problem with Volte then I flashed the original firmware (marshmallow) using QFIL)Volte was working then I flash AEX 4.6 but then also Volte was not working. I don't know why that strange behavior was there with Volte because I have flashed tons of rom before and I know all the procedure that how to flash a custom rom. So i think there was some problem with the package which is provided for flagging with mi tool because the flashing was done using EDL method. But my Volte is again working fine because someone provide the solution on AEX 4.6 discussion.

When I click on Reboot EDL , my device just reboots to system. How does the EDL mode looks like? Is it like fastboot mode? Why is my device booting into system again. I followed all the steps provided, am i missing somthing

Phone isn't booting into edl mode... Instead of that phone is rebooting.

I had the same problem
kany1 said:
Before flashing with mi flash tool I was using AEX 4.6 and then i tried this flashing and when i was having problem with Volte then I flashed the original firmware (marshmallow) using QFIL)Volte was working then I flash AEX 4.6 but then also Volte was not working. I don't know why that strange behavior was there with Volte because I have flashed tons of rom before and I know all the procedure that how to flash a custom rom. So i think there was some problem with the package which is provided for flagging with mi tool because the flashing was done using EDL method. But my Volte is again working fine because someone provide the solution on AEX 4.6 discussion.
Click to expand...
Click to collapse
What was the solution? I had the same problem.

I think developers are sleeping... Nobody is giving solution.

[V1][ENGINEERING][ROM] OFFICIAL Engineering Firmware for MERLIN (Redmi Note 9 / Redmi 10X 4G)

Version 1
{
"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"
}
Works with:
- Xiaomi Redmi Note 9
- Xiaomi Redmi 10X 4G
Build Date:
2020/05/13
Android Version:
QP1A.190711.020
Display ID:
AL2522-Merlin-V039-Q-0513
Build Fingerprint:
Redmi/merlin/merlin:10/QP1A.190711.020/258:userdebug/test-keys
Security Patch:
2019/12/05
Radio/Modem/Baseband Version:
MOLY.LR12A.R3.MP.V94.3
Kernel Version:
4.14.141-gf3c3c7a
Wed May 13 12:49:46 CST 2020
Download:
https://www.mediafire.com/file/lon7...V039-Q-0513_QP1A.190711.020_by-VD171.zip/file
Password:
Pass is in the attached file: PASSWORD_by_VD171.txt
How to flash it?
Use any scatter file specific for MERLIN.
Radio/Modem/Baseband properties:
Code:
md1_dbginfodsp=DbgInfo_DSP_MT6768_MOLY_LR12A_R3_MP_V94_3_2019_12_31_16_23.xz
md1_dbginfo=DbgInfo_LR12A.R3.MP_HUAQIN_Q0MP1_MT6769_SP_MOLY_LR12A_R3_MP_V94_3_2020_03_26_19_19.xz
md1_mddbmeta=MDDB.META_MT6768_S00_MOLY_LR12A_R3_MP_V94_3.EDB
md1_mddbmetaodb=MDDB.META.ODB_MT6768_S00_MOLY_LR12A_R3_MP_V94_3.XML.GZ
md1_mddb=MDDB_InfoCustomAppSrcP_MT6768_S00_MOLY_LR12A_R3_MP_V94_3.EDB
Prop.default:
Code:
ro.build.version.incremental=258
ro.odm.build.version.incremental=258
ro.vendor.build.version.incremental=258
ro.build.version.security_patch=2019-12-05
ro.vendor.build.security_patch=2019-12-05
ro.build.display.id=AL2522-Merlin-V039-Q-0513
ro.vendor.mediatek.version.release=alps-mp-q0.mp1.tc8sp2-V1.4_huaqin.q0mp1.k69v1.64_P1
ro.build.product=merlin
ro.product.board=merlin
ro.product.odm.device=merlin
ro.product.odm.model=merlin
ro.product.odm.name=merlin
ro.product.product.device=merlin
ro.product.product.model=merlin
ro.product.product.name=merlin
ro.product.system.device=merlin
ro.product.system.model=merlin
ro.product.system.name=merlin
ro.product.vendor.device=merlin
ro.product.vendor.model=merlin
ro.product.vendor.name=merlin
ro.build.flavor=merlin-userdebug
ro.build.description=merlin-userdebug 10 QP1A.190711.020 258 test-keys
ro.board.platform=mt6768
ro.build.id=QP1A.190711.020
ro.odm.build.id=QP1A.190711.020
ro.product.build.id=QP1A.190711.020
ro.system.build.id=QP1A.190711.020
ro.vendor.build.id=QP1A.190711.020
ro.bootimage.build.fingerprint=Redmi/merlin/merlin:10/QP1A.190711.020/258:userdebug/test-keys
ro.odm.build.fingerprint=Redmi/merlin/merlin:10/QP1A.190711.020/258:userdebug/test-keys
ro.product.build.fingerprint=Redmi/merlin/merlin:10/QP1A.190711.020/258:userdebug/test-keys
ro.system.build.fingerprint=Redmi/merlin/merlin:10/QP1A.190711.020/258:userdebug/test-keys
ro.vendor.build.fingerprint=Redmi/merlin/merlin:10/QP1A.190711.020/258:userdebug/test-keys
ro.build.tags=test-keys
ro.odm.build.tags=test-keys
ro.system.build.tags=test-keys
ro.vendor.build.tags=test-keys
ro.build.type=userdebug
ro.odm.build.type=userdebug
ro.system.build.type=userdebug
ro.vendor.build.type=userdebug
ro.bootimage.build.date=Wed May 13 12:41:51 CST 2020
ro.build.date=Wed May 13 12:41:51 CST 2020
ro.odm.build.date=Wed May 13 12:41:51 CST 2020
ro.product.build.date=Wed May 13 12:41:51 CST 2020
ro.system.build.date=Wed May 13 12:41:51 CST 2020
ro.vendor.build.date=Wed May 13 12:41:51 CST 2020
MD5 hashes:
Code:
APDB_MT6768_S01__W1953 -> 3adfe0c4e41828cd51ed783da774bd08
boot-debug.img -> e9dfb7dde67795157a871bc14b490054
boot.img -> d6e19a30d85a27379d91072665ad43c9
cache.img -> c40c137a18a26980d406d4ef0ccd7e61
cust.img -> e8c4e9f4ee0fe5052cf0dc356aedd8de
DbgInfo_LR12A.R3.MP_HUAQIN_Q0MP1_MT6769_SP_MOLY_LR12A_R3_MP_V94_3_2020_03_26_19_19_1_ulwctg_n -> b5bf654ddaacfd61e78c131f721974af
dtb.img -> ec4b37b164f1bd9ce6f2b1b911ac0872
dtbo-verified.img -> 9b0fa19089a0310325b88eebc8e41ae7
dtbo.img -> 9b0fa19089a0310325b88eebc8e41ae7
efuse.img -> 421f2cead0fbea555680b96136555941
exaid.img -> e8c4e9f4ee0fe5052cf0dc356aedd8de
lk-verified.img -> 0ba475d8c216b2613815b59e3db8da2b
lk.img -> 0ba475d8c216b2613815b59e3db8da2b
logo.bin -> 257508aa9cdeb690e4a4ed038c91ff76
md1arm7.img -> a0453e723dc84255940d7791740d06db
md1img-verified.img -> 27cd78644df092ade4ca03799dc3c2a3
md1img.img -> 27cd78644df092ade4ca03799dc3c2a3
md3img.img -> 9a9c185e3f6234103e5949716b9962d2
MDDB.META.ODB_MT6768_S00_MOLY_LR12A_R3_MP_V94_3_1_ulwctg_n.XML.GZ -> 4e040508c1878706a428c54ef0844e0f
MDDB.META_MT6768_S00_MOLY_LR12A_R3_MP_V94_3_1_ulwctg_n.EDB -> 7c1ecfd4e3d626957b6655f107824649
MDDB_InfoCustomAppSrcP_MT6768_S00_MOLY_LR12A_R3_MP_V94_3_1_ulwctg_n.EDB -> b24757bd125ad435bd2d26575b5c1d75
MT6768_Android_scatter.txt -> 0a8f16b2276ee9c37337a3937f71a7c8
preloader.img -> dbc21da31860042674fab69d07444e95
preloader_emmc.img -> dbc21da31860042674fab69d07444e95
preloader_merlin.bin -> bc7ebc0c2ca06b0d99856d595949e215
preloader_ufs.img -> 29ef0e631a45bf14555fd6b7adb7a7bf
product.img -> 7ec4f1ffd2b49d7c5b4f1bb5d3ba0dc6
ramdisk-debug.img -> b6048055b240d3c9f6933544b86416b5
ramdisk-recovery.img -> 77de275ef543e46bbedfd53b7e36f945
ramdisk.img -> 545ec84cf25662d1e4f4cf7e496fa56e
recovery.img -> 6362f1beb617572680f3fc91640d3767
scp-verified.img -> 2cac6177dc7eec82421cb3f4a2776aff
scp.img -> 2cac6177dc7eec82421cb3f4a2776aff
secro.img -> 096587b863e1252d67b1b8307291db09
spmfw-verified.img -> 40345cc1edec88bcd510fa62eac01739
spmfw.img -> 40345cc1edec88bcd510fa62eac01739
sspm-verified.img -> 0ceaf392e89bf70c9a52a5c91cc75865
sspm.img -> 0ceaf392e89bf70c9a52a5c91cc75865
super.img -> 542873466ecc6603c81758cf6a000390
super_empty.img -> a6d56d7a12d989bf31511d866449291d
system.img -> 27976b65c09bd01e7963a5f3db563fc7
tee-verified.img -> 4f2fdf78d5be3a5de0154c46af69d476
tee.img -> 4f2fdf78d5be3a5de0154c46af69d476
userdata.img -> 802561cd4739f2f0aae7a51890a5866f
vbmeta.img -> 31da88d4a00b99b36081f859f17f808a
vbmeta_system.img -> a6b560b53a42c98fba204f2b69e70fd7
vbmeta_vendor.img -> 86fae46d211bdedcb49bd08e901d4d3f
vendor.img -> 1a15f790bf6c32fb959da9bc4dfce6e4
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/

Can I flash this in MI Flash?

DavitidzeSh said:
Can I flash this in MI Flash?
Click to expand...
Click to collapse
I'm not sure. Maybe yes if your bootloader is unlocked.
You can try to flash this in MiFlashTool and then tell us, please
But, certainly you can flash this in SP Flash Tool.

VD171 said:
I'm not sure. Maybe yes if your bootloader is unlocked.
You can try to flash this in MiFlashTool and then tell us, please
But, certainly you can flash this in SP Flash Tool.
Click to expand...
Click to collapse
Well, the file format looks like Stock firmware fence the assumption. But I guess I'll go with SP flash since I'm a student and i can't afford to hard brick this

DavitidzeSh said:
Well, the file format looks like Stock firmware fence the assumption. But I guess I'll go with SP flash since I'm a student and i can't afford to hard brick this
Click to expand...
Click to collapse
Yes, it has all flashing scripts.
Taken care for NOT flashing the flash_all_lock script or your device will be locked again.

Sorry for the Noob question, but what's Engineering rom? Its a custom rom? And what changes from miui?
Thank you

jvfigueredo said:
Sorry for the Noob question, but what's Engineering rom? Its a custom rom? And what changes from miui?
Thank you
Click to expand...
Click to collapse
It is an OFFICIAL ROM by Xiaomi.
It helps engineers to make updates, bug fixes, new improvements and many other things on the device, because this rom does not have all the security steps and procedures.
In other words, it helps for DEBUGGING and DEVELOPMENT.

DavitidzeSh said:
Well, the file format looks like Stock firmware fence the assumption. But I guess I'll go with SP flash since I'm a student and i can't afford to hard brick this
Click to expand...
Click to collapse
Yes, you can flash with MI Flash. You might need to erase vendor and system.

VD171 said:
It is an OFFICIAL ROM by Xiaomi.
It helps engineers to make updates, bug fixes, new improvements and many other things on the device, because this rom does not have all the security steps and procedures.
In other words, it helps for DEBUGGING and DEVELOPMENT.
Click to expand...
Click to collapse
It is not OFFICIAL, it is not released to public. It has been released by Halabtech. and engineering rom is used as a base to build the stock rom for the device.
Also, please credit @ErdilS, as he provided the firmware originally.

Can
VD171 said:
Yes, it has all flashing scripts.
Taken care for NOT flashing the flash_all_lock script or your device will be locked again.
Click to expand...
Click to collapse
Can anyone tell me what is engineering rom i am tired but not able to find any answer and developer plzz tell me simply about engineering rom

[email protected] said:
Can
Can anyone tell me what is engineering rom i am tired but not able to find any answer and developer plzz tell me simply about engineering rom
Click to expand...
Click to collapse
Engineering rom is base firmware used by the company to test features and build stock rom for the device.
It is not for daily use, just for unbricking device.

Communos said:
It is not OFFICIAL, it is not released to public. It has been released by Halabtech. and engineering rom is used as a base to build the stock rom for the device.
Also, please credit @ErdilS, as he provided the firmware originally.
Click to expand...
Click to collapse
YES, this is leaked but it is OFFICIAL developed and signed by xiaomi.
Only Xiaomi can sign images with xiaomi signature.
Are you insane?
Do you mean halabtech has any developer on its team?
LOL, LOL, LOL.
Halabtech is just a (good) copier.
I've never seen anything developed by halabtech team.
Except some bat files compiled to exe... LOL, LOL, LOL.
( IF ANYBODY NEEDS ANY FILE UPLOAED TO halabtech, JUST TELL ME AND I WILL PROVIDE THIS FILE TO YOU FOR FREE ! )
[email protected] said:
Can
Can anyone tell me what is engineering rom i am tired but not able to find any answer and developer plzz tell me simply about engineering rom
Click to expand...
Click to collapse
Read this: https://forum.xda-developers.com/t/...dmi-note-9-redmi-10x-4g.4227933/post-84441883

I guess merlin can come under miatoll category

Jas Grover said:
I guess merlin can come under miatoll category
Click to expand...
Click to collapse
Unhappy, it can't.
Merlin, does NOT shares the same kernel with Curtana, Joyeuse, Excalibur and Gram.
It shares the same kernel of Redmi 10X 4G, Redmi 9 and Redmi POCO M2.
You can see this here: https://github.com/MiCode/Xiaomi_Kernel_OpenSource/

Hello mod, if i flash this Rom, i may repair imei null for my device?

p233 said:
Hello mod, if i flash this Rom, i may repair imei null for my device?
Click to expand...
Click to collapse
I'm not a mod.
Engineering Firmware does NOT repair your imei.
It just allow you to enter in meta mode and use maui meta.
You need to do everything by yourself.
Talking about changing imei is not allowed on XDA, please don't ask about how to do that.
Good luck

VD171 said:
I'm not a mod.
Engineering Firmware does NOT repair your imei.
It just allow you to enter in meta mode and use maui meta.
You need to do everything by yourself.
Talking about changing imei is not allowed on XDA, please don't ask about how to do that.
Good luck
Click to expand...
Click to collapse
If you can post FRP bypass threads on XDA, You can talk about changing IMEI too.

Still waiting for you to credit @ErdilS, he got this for Redmi Note 9. Remember that you did not find this yourself, we brought it to you. Even the screenshot you posted is mine.
Forum rules clearly state you are supposed to credit the source.

VD171 said:
I'm not a mod.
Engineering Firmware does NOT repair your imei.
It just allow you to enter in meta mode and use maui meta.
You need to do everything by yourself.
Talking about changing imei is not allowed on XDA, please don't ask about how to do that.
Good luck
Click to expand...
Click to collapse
How enable meta mode and use maui meta in ROM 12.0.4 China (Redmi 10x 4G)? Thanks pro.

p233 said:
How enable meta mode and use maui meta in ROM 12.0.4 China (Redmi 10x 4G)? Thanks pro.
Click to expand...
Click to collapse
(Retracted)

Question Bricked POCO F3 ( Qualcomm HS-USB QDLoader 9008 ) Need Help

I bricked my POCO F3 Global while converting it into Redmi K40 after BL unlocking - I have tried everything - did whatever it takes to bring it back to life - but for me, nothing works.
I need experts advice, I would really appreciate if you could do something to fix this phone. (After trying whatever it takes, I came to a conclusion, while flashing it via Mi-Flash-Tool it says that it requires an Xiaomi Authorized Account to flash it to life, and it is hard to have one, probably)
Any help would be appreciated.
Thank you for your time.
{
"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"
}

AndroidsKings said:
I have bricked my POCO F3 Global while converting it into Redmi K40 after BL unlocking - I have tried everything - did whatever it takes to bring it back to life - but for me, nothing works.
I need experts advice, I would really appreciate if you could do something to fix this phone. ( but I have noticed a thing when flashing it via Mi-Flash Tool it requires a authorized account to flash it to life, and it is hard to have one, because of scammers out there.
View attachment 5305857
Click to expand...
Click to collapse
What exact steps did resulted into this? Is bootloader not accessible? I also have global version of POCO F3 and I also did the same to convert to Chinese version from global version, but flash tools gave me multiple errors. And didn't let me Flash the ROM.
But soon when I rebooted the phone it got stuck in Fastboot screen. Later on I flashed TWRP Recovery and Flashed CrDroid which booted up the phone, But due to some bugs and personal preferences I switched to Xiaomi.eu 12.5 stable.

What rom did you had before bricking your device?

malick186 said:
What exact steps did resulted into this? Is bootloader not accessible? I also have global version of POCO F3 and I also did the same to convert to Chinese version from global version, but flash tools gave me multiple errors. And didn't let me Flash the ROM.
But soon when I rebooted the phone it got stuck in Fastboot screen. Later on I flashed TWRP Recovery and Flashed CrDroid which booted up the phone, But due to some bugs and personal preferences I switched to Xiaomi.eu 12.5 stable.
Click to expand...
Click to collapse
I am having a black screen, and nothing but just my PC can detect it but in Qualcomm HS-USB QDLoader 9008 mode, I was flashing it as I have told, it was on Fastboot Screen but after giving it a restart, it didn't show any sign of light, and now my life is in darkness, but after a research I have found out that I am lost somewhere is EDL mode which is not easily flashable without a Mi Authorized Account as shown in the attached picture.

hexisg said:
What rom did you had before bricking your device?
Click to expand...
Click to collapse
I was on ( miui_ALIOTHGlobal_V12.0.3.0.RKHMIXM ) and I was flashing it/converting it into Redmi K40 12.5.20 after unlocking the bootloader.

AndroidsKings said:
I was on ( miui_ALIOTHGlobal_V12.0.3.0.RKHMIXM ) and I was flashing it/converting it into Redmi K40 12.5.20 after unlocking the bootloader.
Click to expand...
Click to collapse
Did u choose the clean all and lock option ?

AndroidsKings said:
I was on ( miui_ALIOTHGlobal_V12.0.3.0.RKHMIXM ) and I was flashing it/converting it into Redmi K40 12.5.20 after unlocking the bootloader.
Click to expand...
Click to collapse
Hold volume - and power for 15sec. If fastboot pop-up, Flash the original rom and select clean all

I wonder how you managed to do that because i was on stock EEA variant and i unlocked bootloader and flashed xiaomi EU 12.5.2 without issues.
If you cannot acces bootloader your only chance is EDL authorized account , which you have to pay someone who has one.

X0PIRAT3 said:
Did u choose the clean all and lock option ?
Click to expand...
Click to collapse
Yup did that.

X0PIRAT3 said:
Hold volume - and power for 15sec. If fastboot pop-up, Flash the original rom and select clean all
Click to expand...
Click to collapse
Not workking !

hexisg said:
I wonder how you managed to do that because i was on stock EEA variant and i unlocked bootloader and flashed xiaomi EU 12.5.2 without issues.
If you cannot acces bootloader your only chance is EDL authorized account , which you have to pay someone who has one.
Click to expand...
Click to collapse
I think you are right, an EDL authorised account must be needed.

you can use qfil and an approperiate flashable rom,not sure where you can get the qfil rom from but qfil itself is easily downloadable.
edit:actually with qfil you can flash the boot partition only and then you should be able to have a working fastboot again.i think.

metalspider said:
you can use qfil and an approperiate flashable rom,not sure where you can get the qfil rom from but qfil itself is easily downloadable.
edit:actually with qfil you can flash the boot partition only and then you should be able to have a working fastboot again.i think.
Click to expand...
Click to collapse
I am gonna try it tonight. Thank you, I'll report you back.

Now i undersand what you did: you used mi flash to flash stock redmi k40 12.5.2 rom on a stock unlocked Poco F3 Global and you had lock option thicked.That obviously did the trick by bricking your device.You did not searched for the right info on what you need to do.

metalspider said:
you can use qfil and an approperiate flashable rom,not sure where you can get the qfil rom from but qfil itself is easily downloadable.
edit:actually with qfil you can flash the boot partition only and then you should be able to have a working fastboot again.i think.
Click to expand...
Click to collapse
Tried this, but failed !

AndroidsKings said:
Tried this, but failed !
Click to expand...
Click to collapse
theres full EDL roms here:
Download Poco F3 Flash File Firmware EDL ROM
Download Poco F3 Firmware Flash File Stock ROM, here we share latest firmware for Poco F3 with flash tool & usb driver
romprovider.com

I see in mi flash tool the rom you try to flash is the global one not the china rom

metalspider said:
theres full EDL roms here:
Download Poco F3 Flash File Firmware EDL ROM
Download Poco F3 Firmware Flash File Stock ROM, here we share latest firmware for Poco F3 with flash tool & usb driver
romprovider.com
Click to expand...
Click to collapse
Thank you, I am having an error.

hexisg said:
Now i undersand what you did: you used mi flash to flash stock redmi k40 12.5.2 rom on a stock unlocked Poco F3 Global and you had lock option thicked.That obviously did the trick by bricking your device.You did not searched for the right info on what you need to do.
Click to expand...
Click to collapse
You might be right, I did something like that. I'll take care of this next time, mistakes teach a lot.

AndroidsKings said:
Thank you, I am having an error. View attachment 5306329
Click to expand...
Click to collapse
Not really sure but what happen is that something in that path (that's trying to access is wrong). Next time click on details (so we can see the call stack). Try to run it as administrator and extract the mi flash to a "shorter" path: "C:/Miflash"
At this point I think you want to try anything so...

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 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.