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
Related
WARNINGS:- Possible risk of data loss ! Backup your files and contents !
- NO dongle and NO box is required.
- NEVER try to flash in "format all" mode ! Otherwise, you will LOSE all secure and identifying infos for your device. Like IMEI.
- Keep your backup files safe and secure ! If you can, encrypt them.
- Never try to share your backups or your security and privacy will be compromised.
- USE AT YOUR OWN RISK. I AM NOT RESPONSIBLE FOR YOUR ACTIONS.
As we all know, we can not restore the IMEI for SLOT1.
But as we are already tired of seeing, every day are several people with this same problem.
So we are opening this thread to discuss possibilities for how to recover the IMEI for SLOT1 too.
If you have any idea or discovered something, share with us so we can discover new possibilities, methods and solutions.
Possible Method # 1:This method was released by HALABTECH. This method was tested by @jasmin811
The idea is simple. Flash the ENGINEERING ROM, write the IMEI in META MODE and then flash the CUSTOM ROM: PixelPlusUI or PixelExperience.
Steps:
#1. Flash the ENGINEERING ROM:
[V1][ENGINEERING][ROM] OFFICIAL Engineering Firmware for MERLIN (Redmi Note 9 / Redmi 10X 4G)
Version 1 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...
forum.xda-developers.com
#2. Enter in META MODE and write the IMEI for both slots (SLOT1 and SLOT2):
How to use Modem Meta Tool to Flash or Write IMEI on Mediatek Device
Step-by-Step guidelines to Flash, Write or Fix IMEI on devices running on Mediatek Chipset using the Modem Meta Tool.
androidmtk.com
#3. Backup the partition NVDATA:
[GUIDE] What should I backup before trying to customize my MERLIN device ? (Redmi Note 9 / Redmi 10X 4G)
WARNINGS: NEVER try to flash in "format all" mode ! Otherwise, you will LOSE all secure and identifying infos for your device. Like IMEI. Keep your backup files safe and secure ! If you can, encrypt them. Never try to share your backups or your...
forum.xda-developers.com
#4. Flash the CUSTOM ROM:
PixelPlusUI: https://forum.xda-developers.com/t/...ui-for-redmi-note-9-merlin-merlinnfc.4254885/
PixelExperience: https://forum.xda-developers.com/t/...-redmi-note-9-redmi-10x-4g-aosp-beta.4236913/
#5. Restore the partition NVDATA.
#6. Flash the version AL2522-Merlin-V039-Q-0513 of the partition MD1IMG:
[BASEBAND][IMG][STOCK][MD1IMG] MODEM Image Partition for MERLIN (Redmi Note 9 / Redmi 10X 4G)
Original Stock MD1IMG.IMG for MERLIN Works with: - Xiaomi Redmi Note 9 - Xiaomi Redmi 10X 4G What is it? This image partition contains the MODEM/BASEBAND/RADIO. How to flash it? fastboot flash md1img md1img.img (Engineering)...
forum.xda-developers.com
#7. Boot to the system and then reboot.
Done.
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/
Reserved.
Hi guys,
This method works pretty well with custom rom pixel experience for note9 merlin.
I'm still looking a way to get it work with stock roms.
For this method we need one file to make it work properly,it calls 'patched md1img'.
I will make later more details about it how it is working and I will upload this file later.
VD171 said:
Dual ime working only on custom rom?
Click to expand...
Click to collapse
for now yes
jasmin811 said:
for now yes
Click to expand...
Click to collapse
Must be rom PixselPlusUi?
This method working on another custom roms?
akbarshoxdedamirzayev said:
Must be rom PixselPlusUi?
This method working on another custom roms?
Click to expand...
Click to collapse
I'm not sure.
Choose any other custom rom, try this method and let us to know too
VD171 said:
I'm not sure.
Choose any other custom rom, try this method and let us to know too
Click to expand...
Click to collapse
Thank you i will be test on xiaomi.eu rom
I will share the result with you
akbarshoxdedamirzayev said:
Thank you i will be test on xiaomi.eu rom
I will share the result with you
Click to expand...
Click to collapse
Allright, thanks.
Good luck
no,it will not work without patched file i mentioned before,if it is ok with Vd171 that i upload it when i make new thread.
jasmin811 said:
no,it will not work without patched file i mentioned before,if it is ok with Vd171 that i upload it when i make new thread.
Click to expand...
Click to collapse
Did you try with other md1img files?
VD171 said:
Did you try with other md1img files?
Click to expand...
Click to collapse
yes,i tried it is not working.
jasmin811 said:
yes,i tried it is not working.
Click to expand...
Click to collapse
Here, you can find many versions of the MD1IMG, including the AL2522-Merlin-V039-Q-0513 of the ENGINEERING ROM:
[BASEBAND][IMG][STOCK][MD1IMG] MODEM Image Partition for MERLIN (Redmi Note 9 / Redmi 10X 4G)
Original Stock MD1IMG.IMG for MERLIN Works with: - Xiaomi Redmi Note 9 - Xiaomi Redmi 10X 4G What is it? This image partition contains the MODEM/BASEBAND/RADIO. How to flash it? fastboot flash md1img md1img.img (Engineering)...
forum.xda-developers.com
VD171 said:
Here, you can find many versions of the MD1IMG, including the AL2522-Merlin-V039-Q-0513 of the ENGINEERING ROM:
[BASEBAND][IMG][STOCK][MD1IMG] MODEM Image Partition for MERLIN (Redmi Note 9 / Redmi 10X 4G)
Original Stock MD1IMG.IMG for MERLIN Works with: - Xiaomi Redmi Note 9 - Xiaomi Redmi 10X 4G What is it? This image partition contains the MODEM/BASEBAND/RADIO. How to flash it? fastboot flash md1img md1img.img (Engineering)...
forum.xda-developers.com
Click to expand...
Click to collapse
which section(partition )is responsible for imei security(nv data corrupted)
If dual slot write on ENG rom its working
But when flashing stok rom
Give nv data corrupted on recovery
I mean if we are write which partition frol eng rom maybe its working on stok rom ?
It's possible?
But i don't know which partition responce for sim 1 slot protect
akbarshoxdedamirzayev said:
which section(partition )is responsible for imei security(nv data corrupted)
If dual slot write on ENG rom its working
But when flashing stok rom
Give nv data corrupted on recovery
I mean if we are write which partition frol eng rom maybe its working on stok rom ?
It's possible?
But i don't know which partition responce for sim 1 slot protect
Click to expand...
Click to collapse
It is not working in eng. rom imei 1 only imei 2
akbarshoxdedamirzayev said:
which section(partition )is responsible for imei security(nv data corrupted)
If dual slot write on ENG rom its working
But when flashing stok rom
Give nv data corrupted on recovery
I mean if we are write which partition frol eng rom maybe its working on stok rom ?
It's possible?
But i don't know which partition responce for sim 1 slot protect
Click to expand...
Click to collapse
You can write both imei using the engineering rom.
But you can't use both imei on stock rom.
If you want to use both imei, you need to read carefully and follow the guide.
Both imei will work only in the custom rom: PixelPlusUI or PixelExperience.
Good luck
Anyone know if i can run the meta tool via VMWare windows? or if theres a osx version of it?
Ive got the rom installed via flash_all, screen goes black (assuming powered off) but it keeps coming up with a connect to windows or mac that vm does with usb connections and the meta tool cant connect
update: fixed the constant connections although the meta tool still cant see it, installed the unsigned the drivers but still nothing connecting. Any thoughts?
Seems to be able to see it in device manager
{
"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"
}
VD171 said:
You can write both imei using the engineering rom.
But you can't use both imei on stock rom.
If you want to use both imei, you need to read carefully and follow the guide.
Both imei will work only in the custom rom: PixelPlusUI or PixelExperience.
Good luck
Click to expand...
Click to collapse
partition "proinfo" is about imei
st3v3 said:
Anyone know if i can run the meta tool via VMWare windows? or if theres a osx version of it?
Ive got the rom installed via flash_all, screen goes black (assuming powered off) but it keeps coming up with a connect to windows or mac that vm does with usb connections and the meta tool cant connect
update: fixed the constant connections although the meta tool still cant see it, installed the unsigned the drivers but still nothing connecting. Any thoughts?
Seems to be able to see it in device manager View attachment 5287291
Click to expand...
Click to collapse
you need correct drivers,this one won't work.Needs to be mediatek da vcom usb driver not mtk usb.
jasmin811 said:
partition "proinfo" is about imei
Click to expand...
Click to collapse
proinfo?
i mean for imei responce partiton
nvdata
nvram
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
Hello All,
I have successfully rooted my red magic 6 pro phone using the method described in the forum post:
Root achieved! Here's how to root the Red Magic 6 and Red Magic 6 Pro
I've been up 24 hours dealing with bootloops. I finally found a way to root the phone and have it boot up! :ROFLMAO: Join our Discord Channel https://discord.gg/8RHyc6Rw Youtube Video Tutorial: UPDATED VIDEO: For all those...
forum.xda-developers.com
I am faced with the issue of the fingerprint reader not working.
Tried fixing it by running the calibration procedure (https://forum.xda-developers.com/t/...er-print-after-loss-data-calibration.4132961/) with no success.
If anyone of you has an operational fingerprint reader in their red magic 6 pro and they would like to help me fix mine, please sent me the persists.img of your phone so I can flash it in my own and get the reader operational again.
There is another post that describes the procedure on how to extract the img from your phone from the forum:
Extracting stock Boot, Recovery and Persist images
Talking here about how to extract the stock Boot, Recovery and Persist images, needed in case of e.g. bootloop upon flashing Magisk or TWRP, to reflash the stock image(s). Also, boot image is needed for patching from Magisk Manager (and flashing...
forum.xda-developers.com
Any assistance will be greatly appreciated.
Ragemanster said:
Hello All,
I have successfully rooted my red magic 6 pro phone using the method described in the forum post:
Root achieved! Here's how to root the Red Magic 6 and Red Magic 6 Pro
I've been up 24 hours dealing with bootloops. I finally found a way to root the phone and have it boot up! :ROFLMAO: Join our Discord Channel https://discord.gg/8RHyc6Rw Youtube Video Tutorial: UPDATED VIDEO: For all those...
forum.xda-developers.com
I am faced with the issue of the fingerprint reader not working.
Tried fixing it by running the calibration procedure (https://forum.xda-developers.com/t/...er-print-after-loss-data-calibration.4132961/) with no success.
If anyone of you has an operational fingerprint reader in their red magic 6 pro and they would like to help me fix mine, please sent me the persists.img of your phone so I can flash it in my own and get the reader operational again.
There is another post that describes the procedure on how to extract the img from your phone from the forum:
Extracting stock Boot, Recovery and Persist images
Talking here about how to extract the stock Boot, Recovery and Persist images, needed in case of e.g. bootloop upon flashing Magisk or TWRP, to reflash the stock image(s). Also, boot image is needed for patching from Magisk Manager (and flashing...
forum.xda-developers.com
Any assistance will be greatly appreciated.
Click to expand...
Click to collapse
You need your persist.img that shipped with phone. Someone elses will NOT. You have lost FP forever.
bs3pro said:
You need your persist.img that shipped with phone. Someone elses will NOT. You have lost FP forever.
Click to expand...
Click to collapse
I've read for another phone that they were able to restore the functionality with the persist of another phone. I understand that the sensors are calibrated per device but it seems that the issue is more related to the security of the root rather than persist being actually corrupted.
Are you aware if I flash stock rom again if there is possibility for FP to work again?
why don't you extract it from the payload in the original ROM?
Andrologic said:
why don't you extract it from the original ROM?
Click to expand...
Click to collapse
If I am not mistaken, this is a per device partition and is not included in any ROM. As I understand it, persist.img contains all the sensors calibration data for the phone.
This is why I request from someone who has the same phone to extract and share so I can have a chance to save the FP functionality in my phone.
Ragemanster said:
If I am not mistaken, this is a per device partition and is not included in any ROM. As I understand it, persist.img contains all the sensors calibration data for the phone.
This is why I request from someone who has the same phone to extract and share so I can have a chance to save the FP functionality in my phone.
Click to expand...
Click to collapse
Understood. Yes, it's not a ROM file. I may switch to this device in the next day or two. Don't mind giving you a copy of mine if you haven't got it by then..
Andrologic said:
Understood. Yes, it's not a ROM file. I may switch to this device in the next day or two. Don't mind giving you a copy of mine if you haven't got it by then..
Click to expand...
Click to collapse
I would greatly appreciate it!
Thank you very much!
Andrologic said:
Understood. Yes, it's not a ROM file. I may switch to this device in the next day or two. Don't mind giving you a copy of mine if you haven't got it by then..
Click to expand...
Click to collapse
Hello bro i have same issue just for sure do u have redmagic6 pro with 5050mAh (international) version???
If yes please help me, im struggle two months with this issue and now know i lost my a file named persist.img lol
Any luck guys. I've got the same problem.
Ragemanster said:
Hello All,
I have successfully rooted my red magic 6 pro phone using the method described in the forum post:
Root achieved! Here's how to root the Red Magic 6 and Red Magic 6 Pro
I've been up 24 hours dealing with bootloops. I finally found a way to root the phone and have it boot up! :ROFLMAO: Join our Discord Channel https://discord.gg/8RHyc6Rw Youtube Video Tutorial: UPDATED VIDEO: For all those...
forum.xda-developers.com
I am faced with the issue of the fingerprint reader not working.
Tried fixing it by running the calibration procedure (https://forum.xda-developers.com/t/...er-print-after-loss-data-calibration.4132961/) with no success.
If anyone of you has an operational fingerprint reader in their red magic 6 pro and they would like to help me fix mine, please sent me the persists.img of your phone so I can flash it in my own and get the reader operational again.
There is another post that describes the procedure on how to extract the img from your phone from the forum:
Extracting stock Boot, Recovery and Persist images
Talking here about how to extract the stock Boot, Recovery and Persist images, needed in case of e.g. bootloop upon flashing Magisk or TWRP, to reflash the stock image(s). Also, boot image is needed for patching from Magisk Manager (and flashing...
forum.xda-developers.com
Any assistance will be greatly appreciated.
Click to expand...
Click to collapse
If you solve your problem please share with us.
You can directly use the persist image recovery of red Magic 5 mobile phone. The effect is the same. I have tested it
Hey guys!
I also lost the "persist" and with it almost all my sensors...Someone please share with me. I know it's not calibrated for my phone, but it can only be better :/ I've read all the RM6 forums that google puts out, but I can't find a solution :/
Thank you very much!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.