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.
Related
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...
Edit: No guarantee that this will work!
Disclaimer: Your warranty may be void after this procedure. I will not be responsible for any mishap that may happen after unlocking.
Backup you data! Device resets after unlocking!
Step 0: Enable developer options.
It is visible under Settings -> Additional settings after tapping 7 times on the build number.
Step 1: Install the apk linked below.
https://download.c.realme.com/flash/Unlock_tool/DeepTesting_X50pro_Q.apk
Step 2: Update this app by installing this -
https://forum.xda-developers.com/at...327195/?hash=232650ae3997a68a5743c72cdf121c9b
Step 3: Open the app and apply for deep-testing.
It takes sometime to get it reviewed and approved. My request took about a day to get enrolled in this deeptesting progam.
Step 4: Get the latest Android platform-tools and Google usb_driver for Windows. Extract wherever is comfortable for you.
Step 5: Reboot into the bootloader.
Connect the phone to your PC with the provided cable.
Enter the following in a cmd terminal where the extracted platform-tools are. Shift+Right click in that folder for getting the option to open a PowerShell terminal.
Note the prefix.
.\adb reboot bootloader
Step 5: Install the driver.
Open the device manager and right-click on the "Android" device. Choose "Update driver" option.
Select the manual installation option. Now, select the option at the top called "All devices".
Click the "Have Disk" button and then choose the .inf file in the usb_driver folder.
Choose "Android Bootloader Interface" option.
It will show "Operation completed successfully" message.
Step 6: Unlock time.
.\fastboot flashing unlock
Your device will show a warning.
Now is the time to rethink.
Vol up to proceed.
Now, the device will reset. Disconnect the cable and let it boot.
Ohhh....Good Job ¡¡ Thank you ¡¡
Teletubi said:
Ohhh....Good Job ¡¡ Thank you ¡¡
Click to expand...
Click to collapse
Happy to help
Do let me know of any issues
Does it work on realme q3i 5g bro ? Mine was 4/128gb version , rmx3042
Cuonglla117 said:
Does it work on realme q3i 5g bro ? Mine was 4/128gb version , rmx3042
Click to expand...
Click to collapse
It should work. Hardware is almost same.
This may work with all Realme models launched with 11
The only difference I found is that the radio (modem) has extra CDMA bands, irrelevant for unlocking.
crazo7924 said:
It should work. Hardware is almost same.
This may work with all Realme models launched with 11
The only difference I found is that the radio (modem) has extra CDMA bands, irrelevant for unlocking.
Click to expand...
Click to collapse
My q3i 5g unlocked sucessfully , thanks sir !
crazo7924 said:
It should work. Hardware is almost same.
This may work with all Realme models launched with 11
The only difference I found is that the radio (modem) has extra CDMA bands, irrelevant for unlocking.
Click to expand...
Click to collapse
Did u try any of gsi on your device please ? I wanna flash gsi but i dont know if it working or not .
Cuonglla117 said:
Did u try any of gsi on your device please ? I wanna flash gsi but i dont know if it working or not .
Click to expand...
Click to collapse
Not yet. I've tried the DSU loader in developer options (12 beta). Doesn't require fastboot.
crazo7924 said:
Not yet. I've tried the DSU loader in developer options (12 beta). Doesn't require fastboot.
Click to expand...
Click to collapse
thank you , but can i port twrp or custom recovery for this device
And what if deep testing gives out that the "phone model does not support deep testing "(rmx3242)?
I have realme narzo 30 4g and it says "failed to submit", "this model doesnt support deep testing".
I tried to unlock my device with this. (Realme 8 5G, identical twin) I get prompt saying this phone model doesn't support deep testing, what should I do?
alexmalek9274 said:
I tried to unlock my device with this. (Realme 8 5G, identical twin) I get prompt saying this phone model doesn't support deep testing, what should I do?
Click to expand...
Click to collapse
i think u need to use another deep testing apk
alexmalek9274 said:
I tried to unlock my device with this. (Realme 8 5G, identical twin) I get prompt saying this phone model doesn't support deep testing, what should I do?
Click to expand...
Click to collapse
I too have Realme 8 5G. I've not yet tried on the latest update.
Edit: it works
{
"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"
}
crazo7924 said:
I too have Realme 8 5G. I've not yet tried on the latest update.
Edit: it worksView attachment 5432067
Click to expand...
Click to collapse
teketi13 said:
I have realme narzo 30 4g and it says "failed to submit", "this model doesnt support deep testing".
Click to expand...
Click to collapse
alexmalek9274 said:
I tried to unlock my device with this. (Realme 8 5G, identical twin) I get prompt saying this phone model doesn't support deep testing, what should I do?
Click to expand...
Click to collapse
I have same problem! Do we have a solution?
Hello guys, my Realme 8 5G face the same problem, and i'd try this instruction. This is my Deep Test result. " oplus Verify fail need to verify signature of another brand oplus Verify pass fastboot verify success fastboot_unlock_verify ok" What should i do next?
My Device had no Data Connection Because it downgrade to India ota_downgrade.zip File anyone can help me fix this problem?
BaldOne22 said:
Hello guys, my Realme 8 5G face the same problem, and i'd try this instruction. This is my Deep Test result. " oplus Verify fail need to verify signature of another brand oplus Verify pass fastboot verify success fastboot_unlock_verify ok" What should i do next?
My Device had no Data Connection Because it downgrade to India ota_downgrade.zip File anyone can help me fix this problem?
Click to expand...
Click to collapse
I also downgrade, and the version was probably the same for India. I had to send it to service, wait 2 weeks. They changed motherboard ( I don't know why ) and returned with BETTER FASTER SMOOTHER UI 2.0.
After I messed with ADB and face a boot-loop, to solve the problem I had to update again to laggier and awkward UI 3.0. So now I have to revert to UI 2.0 and don't know how.
I assume a Global rollback package can solve your problem also.
BaldOne22 said:
Hello guys, my Realme 8 5G face the same problem, and i'd try this instruction. This is my Deep Test result. " oplus Verify fail need to verify signature of another brand oplus Verify pass fastboot verify success fastboot_unlock_verify ok" What should i do next?
My Device had no Data Connection Because it downgrade to India ota_downgrade.zip File anyone can help me fix this problem?
Click to expand...
Click to collapse
Step 6
I can't install the app it say it conflicts with another app package
Hey,
It's been quite quiet in here so I am guessing not many people purchased one an X30.
Do we think like most of the previous Moto and Lenovo chinese phones we will be able to flash the global rom once available?
I managed to do it on my Lenovo Legion phones before and most chinese sellers do this too.
What do you think?
hi,
edge x30 will be available in europe 24th february
it wll be rebranded edge 30 pro
apparently maybe it will have onscreen fingerprint (instead of on side)
hope we can flash this rom even if it's not the same name, but it's the same phone
Yeah I am aware that it's out on the 24th which is why I posted above. I am hoping it's the exact same hardware!
I was try to use this global rom from Brazil, but it doesnt work out, reboot looping, I believe Indian ROM more compatible to Chinese version, waiting for someone share the stock rom.
Pls try on this link brazil version, got any fix let me know.
AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
abbasaj said:
I was try to use this global rom from Brazil, but it doesnt work out, reboot looping, I believe Indian ROM more compatible to Chinese version, waiting for someone share the stock rom.
Pls try on this link brazil version, got any fix let me know.
AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Click to expand...
Click to collapse
have you try these firmware?
{
"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 tried to flash the retail global rom while keeping the original radio of the China version rom. it booted successfully. but i can't get NFC to work. Also noted that the global rom has wireless charging, which the x30 doesn't have. it appears that the hardware is not exacly the same.
ddt3541 said:
i tried to flash the retail global rom while keeping the original radio of the China version rom. it booted successfully. but i can't get NFC to work. Also noted that the global rom has wireless charging, which the x30 doesn't have. it appears that the hardware is not exacly the same.
Click to expand...
Click to collapse
are you using a service file or flashing file?
can you please attach the .bat file here?
zlebors said:
zlebors said:
are you using a service file or flashing file?
can you please attach the .bat file here?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
zlebors said:
are you using a service file or flashing file?
can you please attach the .bat file here?
Click to expand...
Click to collapse
i just used moto flash pro to do the flash. used flash.xml. just dont select the radio when you flash.
ddt3541 said:
i just used moto flash pro to do the flash. used flash.xml. just dont select the radio when you flash.
Click to expand...
Click to collapse
send the link of the program you use and how you did it please, I couldn't get it in any way
gersonrsj said:
send the link of the program you use and how you did it please, I couldn't get it in any way
Click to expand...
Click to collapse
[Utility] MotoFlashPro
- = MotoFlashPro = - Utility to flash for Motorola devices on Qualcomm processors. Instruction Pre-extract the firmware archive to either an adb&fastboot driver folder or another location on your PC if you are catching firmware from any drive...
forum.xda-developers.com
ddt3541 said:
[Utility] MotoFlashPro
- = MotoFlashPro = - Utility to flash for Motorola devices on Qualcomm processors. Instruction Pre-extract the firmware archive to either an adb&fastboot driver folder or another location on your PC if you are catching firmware from any drive...
forum.xda-developers.com
Click to expand...
Click to collapse
doesnt work for me
I already placed the firmware on data folder of the app
the ROM works, but the bootloader and radio have to be Chinese version, it is using a lot of battery and it heats up more than the Chinese one
gersonrsj said:
the ROM works, but the bootloader and radio have to be Chinese version, it is using a lot of battery and it heats up more than the Chinese one
Click to expand...
Click to collapse
so flashed all the files except Bootloader & Radio, and the phone able to boot to homescreen,, correct?
zlebors said:
so flashed all the files except Bootloader & Radio, and the phone able to boot to homescreen,, correct?
Click to expand...
Click to collapse
Yes its working flash without bootloader and radio, but too much heat on the phone.
NFC is not working, any solution for this
gersonrsj said:
the ROM works, but the bootloader and radio have to be Chinese version, it is using a lot of battery and it heats up more than the Chinese one
Click to expand...
Click to collapse
abbasaj said:
Yes its working flash without bootloader and radio, but too much heat on the phone.
NFC is not working, any solution for this
Click to expand...
Click to collapse
did you guys perform a factory reset and still facing heat and NFC issue?
zlebors said:
did you guys perform a factory reset and still facing heat and NFC issue?
Click to expand...
Click to collapse
Yes flashed with complete wipe of the device, still heating issue NFC not working, battery drain so fast, @gersonrsj is correct.
I've tried RETAPAC and RETAIL firmware, both NFC broken.
on progress with RETBR
RETAPAC, RETAIL, RETEU. RETBR all broken NFC
the global ROM is not fully compatible with the X30, the Edge 30 pro has induction charging and other networks so I think the bootloader and radio doesn't work
So the edge 30 pro not similar hardware spec of edge x30 isn't?
We have to wait for some team to work on the updates I guess.
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
No matter how you are experienced or skilled in flashing ROM's, the things sometimes just happens. And you are here now...
Even I was aware which DDR model was my device, yes.. I did it - flashed by mistake DDR4 xbl.img to my DDR5 noodlep.
Of'coz, I wasn't that happy when I achieved it. Many googling, many searches - nothing. The only option was to return to OnePlus for repair.
But; there is a way. The idea came from Tom Marshall ( @tdm ) - he said that I can try to force "deep flash method" using EDL CABLE.
How to recover ? It's really simple.
Pre-requisites:
1. Windows 7 - 10 based PC (for msmtool) with properly installed 9008 COM port drivers.
Follow this guide to set and prepare: [OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
2. Buy EDL cable. it looks like that:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now to revive your toy !
1. Start msmtool, click others (as it's recommended for msmtool), choose region of your device. Get ready to start flashing.
You'll see that the line with COM port says it's not connected (yet)
2. Connect the cable to your device - but not to PC yet.
3. Press the button on the cable - It's called "deep flash" button...
4. While you are still pressing the button, connect the other side of the cable to your PC (where msmtool is opened and ready to go).
5. Release the button and you'll hear that your device is connected. Check the line with COM port and you'll see it's connected.
EDL port will be opened for about 10 seconds. so you must be ready to start the installation.
6. Start the msmtool and wait till the finish.
7. The rest is well known msmtool flashing way.
Enjoy !!!
Credits goes to @tdm , @jabashque & @AnierinB for their support.
This method shall work on EVERY QUALCOMM device, as it's QualComm thing...
Haha, thanks for the confirmation, everyone said that the ram is fried and you have to change mobo, i said that there is no proof of that, and i was right.
Btw could you share link to where you got that cable?
ppajdek said:
Haha, thanks for the confirmation, everyone said that the ram is fried and you have to change mobo, i said that there is no proof of that, and i was right.
Btw could you share link to where you got that cable?
Click to expand...
Click to collapse
Actually available on Amazon or eBay for a few bucks.
ppajdek said:
Haha, thanks for the confirmation, everyone said that the ram is fried and you have to change mobo, i said that there is no proof of that, and i was right.
Btw could you share link to where you got that cable?
Click to expand...
Click to collapse
Okay first off Qualcomm has multiple things in their source code that tell you you can ram flash your phone back secondly software can't fry hardware
Thanks @samdoc, @tdm , @jabashque ! I was able to fix my phone and get it back to working . I'm very grateful for the help and wanted to express my appreciation. Without this post, I'm not sure what I would have done. Thanks again, samdoc!
jef_00 said:
Thanks @samdoc, @tdm , @jabashque ! I was able to fix my phone and get it back to working . I'm very grateful for the help and wanted to express my appreciation. Without this post, I'm not sure what I would have done. Thanks again, samdoc!
Click to expand...
Click to collapse
I'm trying it out tomorrow myself
AkayamiShurui said:
I'm trying it out tomorrow myself
Click to expand...
Click to collapse
Good luck brother
jef_00 said:
Good luck brother
Click to expand...
Click to collapse
I'm literally about to do it right now I'm just waiting for the MSM tool to finish downloading I got official qualcomm drivers on the computer
did you have success brother @AkayamiShurui
jef_00 said:
did you have success brother @AkayamiShurui
Click to expand...
Click to collapse
Trying again I downloaded the wrong MSM lol
Thank you @semdoc for the suggestion
Because I used similar like semdoc attached image deep flash cable and followed the steps, its seems to be not work. (no new notification in Device Manager)
@jef_00 do you mind share what type of deep flash cable/ shopping link?
After wrongly flashed XBL, is that normal the phone will be hot?
(I have just unplug the battery so it won't over heat mobo)
Hi @bingchilling sure!
1. I used a hydra EDL v2 cable i get mine from AliExpress
2. Not noticed that
AkayamiShurui said:
Trying again I downloaded the wrong MSM lol
Click to expand...
Click to collapse
Aah allright
jef_00 said:
Hi @bingchilling sure!
1. I used a hydra EDL v2 cable i get mine from AliExpress
2. Not noticed that
Click to expand...
Click to collapse
Thank you @jef_00, will give it a try!
bingchilling said:
Thank you @jef_00, will give it a try!
Click to expand...
Click to collapse
no problem!
i guess im a little bit late for this party? successfully switched motherboard, but broke the screen in the process (wrong screw into wrong hole)
anyway i'll pray and hope this works on your phones cause this issue needs to be tech fckd, just switched to OP9Pro for 200 bucks, dont ask how.. guess someone in much need at ebay
Hi everyone, I might need some help here...I have a OnePlus 8T EU model and I too have flashed the wrong xbl.img (DDR5 instead of DDR4X in my case). Reading this post gave me some hope and I bought an EDL cable, looking just as the one in the picture OP posted.
My phone has never been in EDL mode before, therefore it is not showing up at all in device manager, no QHUSB_BULK, no anything. It is therefore impossibile for me to try and install the drivers by updating the device entry there, as specified in the guide.
I tried to install the drivers in several other ways, using an installer executable or manually installing the .inf files, but the outcome is always the same: after following all the steps given, MSM, as well as Device manager, do not read my device.
What can I possibly try differently here?
joker925 said:
Hi everyone, I might need some help here...I have a OnePlus 8T EU model and I too have flashed the wrong xbl.img (DDR5 instead of DDR4X in my case). Reading this post gave me some hope and I bought an EDL cable, looking just as the one in the picture OP posted.
My phone has never been in EDL mode before, therefore it is not showing up at all in device manager, no QHUSB_BULK, no anything. It is therefore impossibile for me to try and install the drivers by updating the device entry there, as specified in the guide.
I tried to install the drivers in several other ways, using an installer executable or manually installing the .inf files, but the outcome is always the same: after following all the steps given, MSM, as well as Device manager, do not read my device.
What can I possibly try differently here?
Click to expand...
Click to collapse
İssues are with your Windows and quallcom drivers probably... I remember I had to switch to safemod in order to installl quallcom drivers.
I'm facing the same issue. Flashed ddr5 firmware instead of ddr4. The phone is completely hard bricked and is not showing on device manager as well.
Will the edl cable enable the connectivity so that i can do MSM?
Ordered youkiloon hydra v2 edl cable and planning to test tomorrow.
abhi92raj said:
I'm facing the same issue. Flashed ddr5 firmware instead of ddr4. The phone is completely hard bricked and is not showing on device manager as well.
Will the edl cable enable the connectivity so that i can do MSM?
Ordered youkiloon hydra v2 edl cable and planning to test tomorrow.
Click to expand...
Click to collapse
Could you Please share the result after testing