Hi everyone, I accidentally locked my phone after I tried to remove the bootloader warning message that booted up everytime I turned on my phone. Now it says that my phone is corrupted in red and I can only boot to fastboot mode. My device is now locked and customer support told me that I needed to go to a OnePlus repair shop. The problem is that I don't live in the US. If anyone can help me I'll be appreciated.
twomad said:
Hi everyone, I accidentally locked my phone after I tried to remove the bootloader warning message that booted up everytime I turned on my phone. Now it says that my phone is corrupted in red and I can only boot to flashboot mode. My device is now locked and customer support told me that I needed to go to a OnePlus repair shop. The problem is that I don't live in the US. If anyone can help me I'll be appreciated.
Click to expand...
Click to collapse
Can you access fastboot? Is the bootloader unlocked or did you lock the bootloader
Kenora_I said:
Can you access fastboot? Is the bootloader unlocked or did you lock the bootloader
Click to expand...
Click to collapse
yes. i can access fastboot mode. Windows recognizes my device when I enter "fastboot devices". I accidentally locked the bootloader while running Pixel Experience 12 GSI and now it says "your device is corrupt. It can't be trusted and will not boot".
twomad said:
yes. i can access fastboot mode. Windows recognizes my device when I enter "fastboot devices". I accidentally locked the bootloader while running Pixel Experience 12 GSI
Click to expand...
Click to collapse
Try to unlock it again with fastboot flashing unlock
Kenora_I said:
Try to unlock it again with fastboot flashing unlock
Click to expand...
Click to collapse
{
"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"
}
twomad said:
View attachment 5587563
Click to expand...
Click to collapse
this is what is says in Fastboot:
-PRODUCT NAME - holi
-VARIANT - SM_ UFS
-BOOTLOADER VERSION -
-BASEBAND VERSION -
-SERIAL NUMBER - eb375f3e
-SECURE BOOT - yes
DEVICE STATE - locked
twomad said:
this is what is says in Fastboot:
-PRODUCT NAME - holi
-VARIANT - SM_ UFS
-BOOTLOADER VERSION -
-BASEBAND VERSION -
-SERIAL NUMBER - eb375f3e
-SECURE BOOT - yes
DEVICE STATE - locked
Click to expand...
Click to collapse
You'll have to try get into EDL mode, but there's no MSM tool released for the unlocked varient of this phone only the T-Mobile varient
Kenora_I said:
You'll have to try get into EDL mode, but there's no MSM tool released for the unlocked varient of this phone only the T-Mobile varient
Click to expand...
Click to collapse
exactly. I tried to follow this guide https://forum.xda-developers.com/t/...le-slot-requires-unlocked-bootloader.4401113/ but it's only applicable to bricked phones that have bootloader unlocked
twomad said:
exactly. I tried to follow this guide https://forum.xda-developers.com/t/...le-slot-requires-unlocked-bootloader.4401113/ but it's only applicable to bricked phones that have bootloader unlocked
Click to expand...
Click to collapse
Yeah unfortunately you're stuck here, without the MSM tool
You could try calling One Plus customer support, explain there are no OP repair shops locally, and request a remote session to fix it.
It's been a while since anyone tried, you might luck out and they could have the MSM tools for the unlocked variant now. (PLEASE share them if they do, they'll send you a link to download the MSM tools ahead of time for the remote session)
Barring that, they'll probably want you to mail the phone in to get it fixed.
edale1 said:
You could try calling One Plus customer support, explain there are no OP repair shops locally, and request a remote session to fix it.
It's been a while since anyone tried, you might luck out and they could have the MSM tools for the unlocked variant now. (PLEASE share them if they do, they'll send you a link to download the MSM tools ahead of time for the remote session)
Barring that, they'll probably want you to mail the phone in to get it fixed.
Click to expand...
Click to collapse
I was actually looking into this for the OnePlus 10 Pro but it seems unlikely but who knows?
A remote session is how we got the T-Mobile MSM tools. It's just every time someone's tried with the Unlocked variant, they've been told the remote support team doesn't have access to the MSM tools for the Unlocked variant. As I said, it's been a while since the last attempt, so there's a chance they may have gotten it by now.
edale1 said:
You could try calling One Plus customer support, explain there are no OP repair shops locally, and request a remote session to fix it.
It's been a while since anyone tried, you might luck out and they could have the MSM tools for the unlocked variant now. (PLEASE share them if they do, they'll send you a link to download the MSM tools ahead of time for the remote session)
Barring that, they'll probably want you to mail the phone in to get it fixed.
Click to expand...
Click to collapse
yeah, I emailed OnePlus and they immediately told me to send the phone for repair. I emailed them again so that they can provide me an MSM tool so let's see how it goes.
twomad said:
yeah, I emailed OnePlus and they immediately told me to send the phone for repair. I emailed them again so that they can provide me an MSM tool so let's see how it goes.
Click to expand...
Click to collapse
Hopefully it will work, the talk about the unlocked version of the MSM tool has kind of died down for around 2 months or so. (On this forum, at least)
Sorry if I missed something and am plucking at brain cells that have already been plucked, but has anyone tried EDL mode and emmcdl.exe with the available firehose? Its not as straight forward to do being as the n200 is UFS amd not EMMC, but it should still be do'able. Its how I managed to get my brick back to fastboot... For that matter, the UFS provisioning xml is available for QFil. You'd have to determine which storage make you have (samsung or toshiba).... Just a thought
the.real.p3y0t3 said:
Sorry if I missed something and am plucking at brain cells that have already been plucked, but has anyone tried EDL mode and emmcdl.exe with the available firehose? Its not as straight forward to do being as the n200 is UFS amd not EMMC, but it should still be do'able. Its how I managed to get my brick back to fastboot... For that matter, the UFS provisioning xml is available for QFil. You'd have to determine which storage make you have (samsung or toshiba).... Just a thought
Click to expand...
Click to collapse
Thing is we don't have the firehose, otherwise it would be easy with qfil
biff_train said:
Hopefully it will work, the talk about the unlocked version of the MSM tool has kind of died down for around 2 months or so. (On this forum, at least)
Click to expand...
Click to collapse
"About your query, we would like to inform you that, currently, we are unable to perform a remote session for OnePlus Nord N200, in this case, we request you to send the device to the serviceable region to get it repaired." I'm screwed
twomad said:
"About your query, we would like to inform you that, currently, we are unable to perform a remote session for OnePlus Nord N200, in this case, we request you to send the device to the serviceable region to get it repaired." I'm screwed
Click to expand...
Click to collapse
Yeah they did that for the OnePlus 10 Pro as well
Kenora_I said:
Thing is we don't have the firehose, otherwise it would be easy with qfil
Click to expand...
Click to collapse
Firehose should be right inside the (extracted) OPS and common to the variants, but I believe OPlus firehoses are encrypted and can't simply be used with QFIL.
AndyYan said:
Firehose should be right inside the (extracted) OPS and common to the variants, but I believe OPlus firehoses are encrypted and can't simply be used with QFIL.
Click to expand...
Click to collapse
Yeah, we tried it but it's not loading actually
Related
Apparently VIVO phones are the black horses of the hacking community because they are near impossible to root!
Also I'm new, I hope I'm posting in the right thread.
Now onto the details, I've been trying to root my phone lately and so far absolutely nothing is working at all! I've not seen anyone whatsoever on XDA to root this specific phone. Mostly V3 and Xshot series
I've tried every single rooting app there is, but I noticed that my efforts are worthless because my phone has an impenetrable bootloader! Of course I immediately head to the internet and found about ADB and Fastboot. Now I've been trying to confirm my suspicions about a locked bootloader by using the "device-info" command on ADB, then I get
Code:
<bootloader> unlock:false
.
Now since I was trying to unlock the bootloader and to this day I absolutely CANNOT bust through it. Whenever I use the "oem-unlock" command, it will always say "FAIL: check device or oem lock"
I forgot most of the commands I used on ADB, (first time using it, actually :silly: ) but the commands I used were normally the ones used to unlock a phone's bootloader.
Going to their forums, they always say that they do not allow their users to tamper with their devices and I was this close to giving up, but after going to the phone's recovery mode, I immediately see at the bottom "The Phone: not root" (yes that's what it exactly says, that's not my grammar) which means that it SHOULD be possible to root it in the first place, and because of that I have not stopped trying.
However every last method I tried failed and I am desperate enough to come here, to XDA forums where I learned to root my now 6+ year old Samsung Galaxy Y.
I really need your help, guys.
Nagazumi said:
Apparently VIVO phones are the black horses of the hacking community because they are near impossible to root!
Also I'm new, I hope I'm posting in the right thread.
Now onto the details, I've been trying to root my phone lately and so far absolutely nothing is working at all! I've not seen anyone whatsoever on XDA to root this specific phone. Mostly V3 and Xshot series
I've tried every single rooting app there is, but I noticed that my efforts are worthless because my phone has an impenetrable bootloader! Of course I immediately head to the internet and found about ADB and Fastboot. Now I've been trying to confirm my suspicions about a locked bootloader by using the "device-info" command on ADB, then I get .
Now since I was trying to unlock the bootloader and to this day I absolutely CANNOT bust through it. Whenever I use the "oem-unlock" command, it will always say "FAIL: check device or oem lock"
I forgot most of the commands I used on ADB, (first time using it, actually :silly: ) but the commands I used were normally the ones used to unlock a phone's bootloader.
Going to their forums, they always say that they do not allow their users to tamper with their devices and I was this close to giving up, but after going to the phone's recovery mode, I immediately see at the bottom "The Phone: not root" (yes that's what it exactly says, that's not my grammar) which means that it SHOULD be possible to root it in the first place, and because of that I have not stopped trying.
However every last method I tried failed and I am desperate enough to come here, to XDA forums where I learned to root my now 6+ year old Samsung Galaxy Y.
I really need your help, guys.
Click to expand...
Click to collapse
Can u plz give me ur num
I have Vivo Y55l (1603). I am unable to root this device
I have Vivo Y55l (1603). I am unable to root this device. Please tell me appropriate method for rooting this device.
{
"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 unlock bootloader and flash twrp recovery
but not boot
guide :
qiurigao said:
View attachment 4129802
i unlock bootloader and flash twrp recovery
but not boot
Click to expand...
Click to collapse
Any chance you can tell me how you did this.
Rakesh37187 said:
Any chance you can tell me how you did this.
Click to expand...
Click to collapse
add my google talk: [email protected]
or QQ:1239120048
Same problem
Is there any way to root this phone or not?? Tried everything and every root app feeling so low please someone help *=*
OEM Unlock In Developers Options?
Did You Turn On The OEM unlock in Developers Option??
James480 said:
Did You Turn On The OEM unlock in Developers Option??
Click to expand...
Click to collapse
没有用
qiurigao said:
没有用
Click to expand...
Click to collapse
好的，我猜那么
qiurigao said:
没有用
Click to expand...
Click to collapse
Everyone plz join this Telegram Group for further development
Vivo y55
https://t.me/vivoy55Development
are you able to unlock it
Tandyeyd said:
are you able to unlock it
Click to expand...
Click to collapse
plzz tell me how to root vivo y55l (1603)
divu jadeja said:
plzz tell me how to root vivo y55l (1603)
Click to expand...
Click to collapse
y55 dont root
It offered to boot as flashed...if you tapped power, I suppose.
Would it just loop into the notice, and not boot the TWRP recovery if you pressed a hardware key (power, say?) Good effort, keep freeing the MSM8974!
Lugralunoogos said:
Would it just loop into the notice, and not boot the TWRP recovery if you pressed a hardware key (power, say?) Good effort, keep freeing the MSM8974!
Click to expand...
Click to collapse
yes
Unlock Vivo bootloader
Vivo phones bootloader can be easily unlocked with modified fastboot binary
Here's the xda thread with downloads
How to root vivo y71
Hi everyone, I am new to the forum but I have a question that has been giving me a headache for a long time, I have a Redmi Note 3 Pro (Kate) and I can not unlock the bootloader of the device, I tried everything this error appears in the 99% asking me to check the mi unlock status in the device settings. and when I try to add the account appears another error as shown in the image. Does anyone know a definitive solution to this error?
{
"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"
}
alvesluscas said:
Hi everyone, I am new to the forum but I have a question that has been giving me a headache for a long time, I have a Redmi Note 3 Pro (Kate) and I can not unlock the bootloader of the device, I tried everything this error appears in the 99% asking me to check the mi unlock status in the device settings. and when I try to add the account appears another error as shown in the image. Does anyone know a definitive solution to this error?
Click to expand...
Click to collapse
Some days ago I flashed latest Global Stable on my Kate just for cleanup and I faced the same problem, but the funniest part: even with that error at 99%, MiUnlock opened my bootloader.
Boot in fastboot, connect the phone to your pc and check your bootloader status.
onliner said:
Some days ago I flashed latest Global Stable on my Kate just for cleanup and I faced the same problem, but the funniest part: even with that error at 99%, MiUnlock opened my bootloader.
Boot in fastboot, connect the phone to your pc and check your bootloader status.
Click to expand...
Click to collapse
how do I check the bootloader status?
alvesluscas said:
how do I check the bootloader status?
Click to expand...
Click to collapse
Reboot in fastboot, connect the phone to your pc, open cmd and type: fastboot oem device-info
You are looking for "device unlocked: true".
onliner said:
Reboot in fastboot, connect the phone to your pc, open cmd and type: fastboot oem device-info
You are looking for "device unlocked: true".
Click to expand...
Click to collapse
I just check here it is not unlocked
device unlocked: false
onliner said:
Some days ago I flashed latest Global Stable on my Kate just for cleanup and I faced the same problem, but the funniest part: even with that error at 99%, MiUnlock opened my bootloader.
Boot in fastboot, connect the phone to your pc and check your bootloader status.
Click to expand...
Click to collapse
Because when u flashed using miflash it did not relock your bootloader and that's why it's still unlocked it happened to me 3 times so this legitimate.
Androbots said:
Because when u flashed using miflash it did not relock your bootloader and that's why it's still unlocked it happened to me 3 times so this legitimate.
Click to expand...
Click to collapse
No, MiFlash blocked my bootloader, I made sure the program did it, I wanted to close my bootloader, after the flashing process I checked it and it was blocked (from fastboot "device unlocked : false".
My Unlock behaves strangely sometimes with Kate devices, in some spanish group, another person commented the same, 99% > error > but bootloader unlocked.
onliner said:
No, MiFlash blocked my bootloader, I made sure the program did it, I wanted to close my bootloader, after the flashing process I checked it and it was blocked (from fastboot "device unlocked : false".
My Unlock behaves strangely sometimes with Kate devices, in some spanish group, another person commented the same, 99% > error > but bootloader unlocked.
Click to expand...
Click to collapse
I see that now...
There is no other reason than your internet connection.
U need working internet connection to verify your device while unlock.
I had same problem. But later when i connected to internet while full process of unlocking it got unlocked...
mohsiin4u said:
There is no other reason than your internet connection.
U need working internet connection to verify your device while unlock.
I had same problem. But later when i connected to internet while full process of unlocking it got unlocked...
Click to expand...
Click to collapse
but the device is connected to the internet
alvesluscas said:
but the device is connected to the internet
Click to expand...
Click to collapse
Your computer Must be connected to internet, and not the device
mohsiin4u said:
Your computer Must be connected to internet, and not the device
Click to expand...
Click to collapse
Yes, my computer is connected to the internet, if I were not connected I would not be able to log in to my unlock
alvesluscas said:
Yes, my computer is connected to the internet, if I were not connected I would not be able to log in to my unlock
Click to expand...
Click to collapse
Your PC connected to ur device hotspot internet connection? If yes then connect another hotspot to ur pc it need when u connect ur Device to PC in fastboot mode
alvesluscas said:
Yes, my computer is connected to the internet, if I were not connected I would not be able to log in to my unlock
Click to expand...
Click to collapse
Hope you got permission from Xiaomi to unlock your account/phone. Then the problem next is just need to map the account for unlocking from phone.
For this follow the instructions below..
Go to Developer settings -> Enable OEM unlocking and also go to Unlock status -> then 'Add my account' for unlocking. (You should see toast message that account is added)
The next painful part is you have to wait 72 hours after adding account. Then try unlock tool (Ver.2) to unlock it.
Hope it helps!
NewBee3 said:
Hope you got permission from Xiaomi to unlock your account/phone. Then the problem next is just need to map the account for unlocking from phone.
For this follow the instructions below..
Go to Developer settings -> Enable OEM unlocking and also go to Unlock status -> then 'Add my account' for unlocking. (You should see toast message that account is added)
The next painful part is you have to wait 72 hours after adding account. Then try unlock tool (Ver.2) to unlock it.
Hope it helps!
Click to expand...
Click to collapse
Yes, I have the permission of xiaomi to unlock the device, being that the problem is that the error is when trying to add the account in my unlock status. an error message appears
Have you try to flash fastboot global or developer with clean flash?
alvesluscas said:
Yes, I have the permission of xiaomi to unlock the device, being that the problem is that the error is when trying to add the account in my unlock status. an error message appears
Click to expand...
Click to collapse
Same error with me as well...i'm gonna try putting only one sim that i use as mi account
Will report if anything changes
PS: i'm new to this device modding and unlocking is really a tricky part here
Any help is appreciated,i wish to unlock officially rather than any dirty hacks
SH3H1 said:
Same error with me as well...i'm gonna try putting only one sim that i use as mi account
Will report if anything changes
PS: i'm new to this device modding and unlocking is really a tricky part here
Any help is appreciated,i wish to unlock officially rather than any dirty hacks
Click to expand...
Click to collapse
try flash stable china rom..
dinoredfield said:
try flash stable china rom..
Click to expand...
Click to collapse
I was told to do this, but mine is Kate (Special Edition) there is no Chinese rom for him
rainsmile said:
Have you try to flash fastboot global or developer with clean flash?
Click to expand...
Click to collapse
I tried both with developer and stable global
So it looks like some of you really need help with unbricking your device - let me guide you.
This is my first Xiaomi device (K20 Pro) and i hard bricked it after 30h of usage.
fastboot locked and "your system has been destroyed" message - nice!
So yeah, i was looking for some unbrick methods and didn't found any, so i researched a bit and after a few hours it was done.
Unfortunatly this method isn't free - but it is the cheapest solution out there without a needed appointment - aka fully automated.
For the moderators: this is the one of few available services to authorize a EDL flash, it is the cheapest and the only automated service.
I do not intend to do any kind of promotion here. Once a free method or cheaper service will be available, i'll update the thread accordingly.
Step 1: Open your phone - take off the backpanel and mainboard shield
JerryRigEverything K20 Pro Teardown - https://www.youtube.com/watch?v=Sd6KpX5MRtI
Note: only top mobo shield needs to be removed, you can use a thin guitar pick instead of the razorblade (to prevent damage)
Step 2: Get your K20 Pro/Mi 9T Pro into EDL 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"
}
1. First of all, unplug the battery connector (blue) from the phone.
2. Now short the 2 points (red) and keep them shorted.
3. Last but not least, plug the usb cable into your usb 2.0 port
(yes, the battery must be disconnected, yes, while doing so you must have the test points shorted)
4. Your phone should now show up in device manager as "Qualcomm HS-USB QDLoader 9008" or "QHSUSB_BULK"
5. if your phone appears in device manager as "QHSUSB_BULK", you have to install the proper driver before proceeding,
please check out this tutorial: https://xiaomibuzz.com/downloads/download-qualcomm-qdloader-usb-driver.html
Step 3: Flash your device
1. Make an account at https://s-unlock.com
2. Press "Add fund" in the main navigation bar
3. Add 15$ to your account, i prefer to pay via PayPal - this would be 0.98$ fees - so after fees you pay 15,98$
4. After clicking on "+Add Fund", you'll be redirected to an invoice where you can pay through paypal
(paypal express selected in payment gateway option) via the "Pay Now" button
5. now the necessary credits will be available in the credits balance in the main navigation bar
6. download and install the latest version of xiaomitool (v0.2 currently) here: https://xiaomitool.net/download
7. after installation is complete, open the program and copy the "Fingerprint" from the "Login Area" section
8. open the site where you can order the needed service for the edl flash https://s-unlock.com/users/server-order?server_service_id=172
9. paste the previously copied fingerprint from xiaomitool into the fingerprint input field of the website and input quantity 15 (just like shown on the screenshot)
Note: the username and password on the order site do not have to match your s-unlock user account, you can pick a different username/password - just remember them!
10. press submit - your credit balance on the s-unlock site should show 0 now - don't worry, your credits have been transferred to the xiaomitool account
11. Open xiaomitool again and login with the credentials you chose during the order process (see step 9)
12. after clicking login, the program connects to the server and shows your current balance of 15 credits
13. download the correct fastboot-firmware for your phone from here https://mirom.ezbox.idv.tw/en/phone/raphael/
Note: Chinese variant requires chinese firmware on locked bootloader, same applies to india, russia, eea (eu) and global.
14. extract the downloaded fastboot firmware through winrar
15. select the extracted firmware folder in xiaomitools
16. Press "EDL flash" - it should detect your phone as "Qualcomm HS-USB QDLoader 9008 Device" and request an edl authentication for 10 credits
17. confirm the popup - and the flash process starts if you did everything right
18. Congrats, you unbricked your device - and i'm sure you are able to reassemble it again by yourself
very detailed guide, thanks!
I have two questions,
how was your device bricked?
why does this work? why normal edl flash method wouldn't work?
IMTLD said:
very detailed guide, thanks!
I have two questions,
how was your device bricked?
why does this work? why normal edl flash method wouldn't work?
Click to expand...
Click to collapse
some pictures are still missing, but they'll be added soon.
i locked my chinese k20 pro while beeing on the eea rom, turned out that was a bad idea.
well, xiaomi requires an edl flash to be authorized, and they just do that for service centers for example.
regards
Great, thx.
That's it... I have no intention to brick my device, but is really nice to know that, if all goes wrong, we still has a last solution. This forum needs this tutorial...
Congrats.
Great tutorial bro.
why shouldn't we try authorised service centres first?
sanjib734 said:
why shouldn't we try authorised service centres first?
Click to expand...
Click to collapse
You can, but if you've bought the phone from a different region they will probably refuse to look at it. If they will look at it, they will charge more than the cost of s-unlock credits.
Nice tutorial , useful for someone in the situation that you was are in to.
I have one other question that you probably do not have the answer to.
If you flash using this method an for example GLOBAL rom on CN device, will it unlock all the bands?
Using this method does it flash the modem firmware? Because the 855 modem supports all the available bands, but some are disabled by software.
vasil_d said:
Nice tutorial , useful for someone in the situation that you was are in to.
I have one other question that you probably do not have the answer to.
If you flash using this method an for example GLOBAL rom on CN device, will it unlock all the bands?
Using this method does it flash the modem firmware? Because the 855 modem supports all the available bands, but some are disabled by software.
Click to expand...
Click to collapse
No. You cannot unlock radio bands by flashing the modem firmware. If it was this easy there would be no point to Xaiomi setting different bands for different regions.
I have a question about rom, the model of my redmi k20 pro is M1903F11A, during my research to get rom I saw that for this model would be rom Davinci and not Raphael, or am I mistaken? Does this process you describe only work with this raphael rom?
ZteRacerUser said:
I have a question about rom, the model of my redmi k20 pro is M1903F11A, during my research to get rom I saw that for this model would be rom Davinci and not Raphael, or am I mistaken? Does this process you describe only work with this raphael rom?
Click to expand...
Click to collapse
it is raphael - k20 pro.
This process can be also applied to other xiaomi devices, but would need other fastboot firmwares.
Regards
So we need to add credit if we need to flash again?
SkipperRyujin said:
So we need to add credit if we need to flash again?
Click to expand...
Click to collapse
yes, 15$.. its the cheapest solution available atm
Why this(Hard Brick) happened exactly?
last doubt before trying
Hello,
One last question, as I'm afraid of just spending another $ 15 and further increasing my $ 280 loss.
When you needed to do the procedure was your cell phone completely dead like mine? No bootloader, no fastboot, only black screen, no led on? Just being recognized in Window as QDloader 9008?
I am finding it very strange that my mobile is recognized as QDLoader 9008 without having to do the testpoint procedure. When I do testpoint nothing changes, continues QDloader 9008.
And another question, with $ 15 I only have one try? Or one flash successfully completed?
ZteRacerUser said:
Hello,
One last question, as I'm afraid of just spending another $ 15 and further increasing my $ 280 loss.
When you needed to do the procedure was your cell phone completely dead like mine? No bootloader, no fastboot, only black screen, no led on? Just being recognized in Window as QDloader 9008?
I am finding it very strange that my mobile is recognized as QDLoader 9008 without having to do the testpoint procedure. When I do testpoint nothing changes, continues QDloader 9008.
And another question, with $ 15 I only have one try? Or one flash successfully completed?
Click to expand...
Click to collapse
++1
ZteRacerUser said:
Hello,
One last question, as I'm afraid of just spending another $ 15 and further increasing my $ 280 loss.
When you needed to do the procedure was your cell phone completely dead like mine? No bootloader, no fastboot, only black screen, no led on? Just being recognized in Window as QDloader 9008?
I am finding it very strange that my mobile is recognized as QDLoader 9008 without having to do the testpoint procedure. When I do testpoint nothing changes, continues QDloader 9008.
And another question, with $ 15 I only have one try? Or one flash successfully completed?
Click to expand...
Click to collapse
it'll authorize first before flashing everything but it sends a package to test everything to the device before, otherwise i can only suggest to pick a USB2.0 port while flashing.
And yes, i think its also possible to enter edl mode through a modified usb cable. Give it a try, it should work if you flash your original rom -> rom the device came with.
Regards
Ok, thanks for the tips, I will try this weekend calmly and well rested :good:
Although I am not very confident as i do not know so far if may phone is in EDL mode at all.
ZteRacerUser said:
Ok, thanks for the tips, I will try this weekend calmly and well rested :good:
Although I am not very confident as i do not know so far if may phone is in EDL mode at all.
Click to expand...
Click to collapse
Let us know how it went, otherwise open it up and get it in tespoint manually again through the method described in OP - just to make sure you don't fail and have to pay for a second attempt.
Regards
Disclaimer: I hope you don't break your phone, but if you do, it's not my fault. Since you are choosing to modify your phone, you accept full responsibility for whatever happens to it, including any damage that may have occurred as a result of incorrectly flashing your device.
Hey guys, similar to all of @Some_Random_Username's unbrick threads, here are the EDL packages (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus Nord N200 5G.
Important: This is only for the T-Mobile variant of the N200. This will not work on the factory unlocked variant and may or may not work for the Metro variant.
Downloads:
11.0.1.5.DE18CB
Original archive
Google Drive
7z format (thanks @edale1)
AnddoidFileHost
MEGA
zip format (thanks @nv270)
Rethink Files
Also available at https://onepluscommunityserver.com/
Instructions:
Launch MsmDownloadTool V4.0.exe.
On the login prompt select "Others" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Press Start button so that it waits for your device to be connected
Power off your device
Press and hold the volume up and down buttons to get into Qualcomm EDL mode.
Plug your device to your computer.
Should you not manage to do that and have adb access, you can use adb reboot edl instead
Wait ~300 seconds.
Enjoy your brand new device.
FAQ:
Does this work on Mac or on Linux?
Unfortunately no, tool is Windows only. You should need at least Windows 7.
Why is my antivirus freaking out when unzipping the archive or running the tool?
In an effort to protect reverse engineering from being done (and by extension prevent conversion process like it was done on 6T and 7Pro), OnePlus now use VM Protect V3 in their MSM tools. As this tries to detect debug environment, this is seen as malicious behaviour by some antivirus.
How can I check my device project ID?
Use getprop ro.boot.project_name. This however involve having ADB access or access to OxygenOS to use Termux or whatever terminal emulator you prefer.
My device isn't detected
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsof...updateid=8ee52ba0-bdef-4009-88cf-335a678dd67a ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
If you can't get into EDL mode by hardware keys, you may use adb reboot edl (will require your phone to still have ADB access)
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
MSM tool is stuck on "Sahara communication failed"
Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.
What is SMT Download mode?
Just don't try to unlock that mode, it will wipe your IMEI and your Widevine certificate if you use it.
How can I fix "SMT config not found" error?
Please refer to https://forum.xda-developers.com/showpost.php?p=83448961&postcount=61
Credits:
@Some_Random_Username for help getting files and for the mirror
@edale1 and @nv270 for repacking and mirroring the files
@nache2001 for testing the tool out on his device
OnePlus for the device and OS
@Nache and others who have the unlocked version from the oneplus store and have the bootloader locked and phone bricked .. This version will not work with your phone as i just tried it myself today .. hopefully someone gets a hold of the msmdowmload from the tech support ..
patiently waiting for the unlock
So just to confirm: For those of us with Tmobile version, this will install default rom from OnePlus and get rid of all the bloatware from Tmobile and technically make our devices be like they are originally purchased from OP?
And of course, in order to use this our bootloader needs to be unlocked?
Will this lock bootloader again?
And do we unlock it with same code we got from OP first time?
Thanks!
xentonix said:
So just to confirm: For those of us with Tmobile version, this will install default rom from OnePlus and get rid of all the bloatware from Tmobile and technically make our devices be like they are originally purchased from OP?
And of course, in order to use this our bootloader needs to be unlocked?
Will this lock bootloader again?
And do we unlock it with same code we got from OP first time?
Thanks!
Click to expand...
Click to collapse
My understanding is the T-Mobile MSM Tools will restore a T-Mobile variant phone to the state it was in coming from T-Mobile; meaning if you debloated the phone, the bloat will be back.
You can use the MSM Tools even with a locked bootloader.
If your bootloader is unlocked, I believe this will lock it. (it may SIM lock your phone again as well, unsure...)
I think the same unlock token will work, but I'm hesitant to say 'yes' without someone testing it first.
xentonix said:
So just to confirm: For those of us with Tmobile version, this will install default rom from OnePlus and get rid of all the bloatware from Tmobile and technically make our devices be like they are originally purchased from OP?
And of course, in order to use this our bootloader needs to be unlocked?
Will this lock bootloader again?
And do we unlock it with same code we got from OP first time?
Thanks!
Click to expand...
Click to collapse
1. Nope, this will revert your device back to the T-Mobile stock ROM, including all the bloatware. Thsi does not convert your device into an unlocked variant.
2. This works whether your bootloader is locked or unlocked. If your bootloader is unlocked, using this tool will lock it again, and you will need to unlock it by flashing unlock_code.bin again.
edale1 said:
My understanding is the T-Mobile MSM Tools will restore a T-Mobile variant phone to the state it was in coming from T-Mobile; meaning if you debloated the phone, the bloat will be back.
You can use the MSM Tools even with a locked bootloader.
If your bootloader is unlocked, I believe this will lock it. (it may SIM lock your phone again as well, unsure...)
I think the same unlock token will work, but I'm hesitant to say 'yes' without someone testing it first.
Click to expand...
Click to collapse
lzgmc said:
1. Nope, this will revert your device back to the T-Mobile stock ROM, including all the bloatware. Thsi does not convert your device into an unlocked variant.
2. This works whether your bootloader is locked or unlocked. If your bootloader is unlocked, using this tool will lock it again, and you will need to unlock it by flashing unlock_code.bin again.
Click to expand...
Click to collapse
Thank you!
I read an article that was bit unclear and pointed to this so I wanted to confirm.
Also, from everything else I gathered, there is still no way to flash Tmob variant with non Tmob rom?
I was interested to try LineageOS but that's not available also seems like.
Phone's too new still. I think we need the MSM Tools for all the variants available before someone can figure out how to flash one variant into another, and we currently only have the T-Mobile variant's MSM Tools.
{
"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"
}
incoming August 176 patch
I have update installed.
You can use restore image on Magisk uninstall before you start. If you encounter problem, you can use original boot image and run "mock patch"
Install update and switch to Magisk when you're prompted to restart, and let Magisk to install in unused partition, and restart after finished
If you have problem with CTS after update, install riru from Magisk and download safetynet fix, and install in Magisk as well (you have to reboot twice)
I've successful restored my N200 phone several times using the MSM, but this most recent time it appears the process was interrupted and I get the following error when turning on the phone. I can not boot the phone back into EDL mode to run MSM tool again. Every 10 or so boots the phone will boot into fastboot instead of throwing the error. I tried flashing a backed up boot.img and super.img, but no luck getting past the error. Any way to recover?
automatic ddr failed
Thank you! I could only get this to work by:
Unplug phone
Open MSMDownloadTool, don't click start
Hold down volume up and down
Plug phone into USB 2.0 port
Release volume up and down, verify device shows up as QDLOADER in Device Manager
Click "Enum" in MSMDownloadTool
Click on the device in the list and click "Start"
I got bootloader unlock code. I need SIM unlock "One Plus Nord N200 5G" by Metro. Help me!
towardsdawn said:
Thank you! I could only get this to work by:
Unplug phone
Open MSMDownloadTool, don't click start
Hold down volume up and down
Plug phone into USB 2.0 port
Release volume up and down, verify device shows up as QDLOADER in Device Manager
Click "Enum" in MSMDownloadTool
Click on the device in the list and click "Start"
Click to expand...
Click to collapse
I bricked my phone late last night and found this forum & thread; my problem was that each time my computer kept showing my phone as "Kedacom" until I scrolled through and found this post.
You guys saved my ass AND saved me a trip to T-Mobile too! I owe you guys big time!
I successfully flashed a metro-pcs device using the tool in this thread. I bricked my device using the dsu loader in developer options. "Oem unlocking" is greyed out. Can anyone point me to a good bootloader unlocking tutorial for this devicel? Is it possible to use this tool with a rom that has already been rooted? Thanks,
Noob here. One thing to note: device was not recognized in the beginning. I held vol up/down at the same time and then plugged in device. Although the screen was black, the device was shown as "connected" and had no issues flashing. After 300 secs, voila!
bleezycheesy said:
I successfully flashed a metro-pcs device using the tool in this thread. I bricked my device using the dsu loader in developer options. "Oem unlocking" is greyed out. Can anyone point me to a good bootloader unlocking tutorial for this devicel? Is it possible to use this tool with a rom that has already been rooted? Thanks,
Noob here. One thing to note: device was not recognized in the beginning. I held vol up/down at the same time and then plugged in device. Although the screen was black, the device was shown as "connected" and had no issues flashing. After 300 secs, voila!
Click to expand...
Click to collapse
You can try this tutorial. It worked for me on Tmobile, no idea about MetroPCS. Key line is
Code:
adb shell pm uninstall --user 0 com.qualcomm.qti.uim
MSMDownloadTool wipes the entire device and relocks the bootloader if it was unlocked, it doesn't care if you're rooted.
towardsdawn said:
You can try this tutorial. It worked for me on Tmobile, no idea about MetroPCS. Key line is
Code:
adb shell pm uninstall --user 0 com.qualcomm.qti.uim
MSMDownloadTool wipes the entire device and relocks the bootloader if it was unlocked, it doesn't care if you're rooted.
Click to expand...
Click to collapse
Thanks for the reference. It worked!
why no have msm tool for global n200 be2117,
jasmok said:
why no have msm tool for global n200 be2117,
Click to expand...
Click to collapse
OnePlus doesn't seem to want to release it.
bleezycheesy said:
Thanks for the reference. It worked!
Click to expand...
Click to collapse
no it doesn't works on metro variant
I tried downloading something in my developer options and it seemed to work, but when my phone restarted I got a message saying, "your device is corrupt. It Can't be trusted and will not boot". The message seems to be in some sort of boot loop, (keeps restarting with the same message). Is there any way I can fix this without sending my phone in to One Plus? I purchased the phone inside of a Metro store.
{
"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"
}
If your phone is from T-Mobile or Metro, check out this forum post to recover your phone: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4324431/
If your phone was factory unlocked, contact OnePlus for a repair. The easiest way to tell if your phone is a carrier device or not is to check the back of the phone. If there's an IMEI engraved on the back of the phone, it's a T-Mobile or Metro phone. If there's not IMEI engraver, its factory unlocked.
I think what you used was the DSU Loader.
If I recall earlier posts in this forum correctly, you need to Bootloader Unlock your phone before messing with DSUs, or you will brick your phone.
As Izgmc said, you'll need to use the MSM Download Tools in the thread he linked to fix your phone, assuming you have the T-Mobile or Metro versions; or to contact OnePlus support if you have the factory unlocked variant.
edale1 said:
I think what you used was the DSU Loader.
If I recall earlier posts in this forum correctly, you need to Bootloader Unlock your phone before messing with DSUs, or you will brick your phone.
As Izgmc said, you'll need to use the MSM Download Tools in the thread he linked to fix your phone, assuming you have the T-Mobile or Metro versions; or to contact OnePlus support if you have the factory unlocked var
Click to expand...
Click to collapse
Yeah that was it! Lesson learned. Thank you!
Thats how I managed to mess up my phone and is currently bricked for several months .. no msmdownload for the unlocked .. please try and get a remote session with the oneplus tech guys .. and share if possible
Hold up a second here. If you have tried to relock the bootloader (which will result in the device is corrupt and will not boot message) try this:
Hold down all 3 buttons (Vol+ Vol- and power) for about 8 seconds or so. As soon as the device vibrates quickly release the power button. When you do, the device should be in fastboot. If you are in fastboot you should now be able to connect it to the PC and type the command fastboot oem unlock. This will now attempt to unlock the bootlaoder. Chances are you have previously unlocked the bootloader and have attempted to relock it. Doing so will cause this error message on the UNLOCKED version of the device.
This will wipe the data but return the device to an unlocked state but not completely bricked on stock firmware. Go through the normal prompts to start the device and you should be good.
Remember, if you have fastboot its not COMPLETELY bricked. Not yet anyways.
I had this happened on my OnePlus Nord 200 5g literally the next day after I got it from Metro at T-Mobile. Phone updated as it should but restarted with the same message you received. They tried to accuse me of putting a virus on the phone which did not make any sense and after going through insurance who couldn't accept the claim for "software damage" ... I contacted one plus and had them remote view my laptop with downloaded tar files and had a technician try to reinstall them back to its original factory condition but to no luck. Metro being a franchise company, has the loophole not accepting returned merchandise even under the return policy stated on the receipt, and customer service technically has no control or power over any particular franchise Metro store. I suggest the only answer I had after 2 weeks of frustration from contacting everyone I possibly could to writing corporate, I finally had a CSR tell me to just get a warranty exchange at any Metro store in which I did in two days later I received a new phone which actually works this time so I would suggest just doing the warranty exchange in order to get yourself a workable phone. Hope that helps. \m/
edale1 said:
I think what you used was the DSU Loader.
If I recall earlier posts in this forum correctly, you need to Bootloader Unlock your phone before messing with DSUs, or you will brick your phone.
As Izgmc said, you'll need to use the MSM Download Tools in the thread he linked to fix your phone, assuming you have the T-Mobile or Metro versions; or to contact OnePlus support if you have the factory unlocked variant.
Click to expand...
Click to collapse
I did this exact thing. Mine is the oem unlocked variant. Is contacting oneplus support still the only option? It's on the metro/tmobile network if that matters. I really fcked up here with dsu loader. Pretty desperate right now for a fix. Please.
superspecialgueststar said:
I did this exact thing. Mine is the oem unlocked variant. Is contacting oneplus support still the only option? It's on the metro/tmobile network if that matters. I really fcked up here with dsu loader. Pretty desperate right now for a fix. Please.
Click to expand...
Click to collapse
You can try the MSM Tools and see if it works, if not, then yes, OP Support is your only option.
edale1 said:
You can try the MSM Tools and see if it works, if not, then yes, OP Support is your only option.
Click to expand...
Click to collapse
Thanks, I downloaded msm tools and there are msm tools included in https://www.terabox.com/web/share/link?surl=7fjfMJSEcdl5zCjPT92IKA
for
dre8t_10_O.05_210713.tar.bz2 -can someone point me to the stock firmware I should be using msmtools error device not match image. Can I use the ~3gb ota zips?
Taking a break and then going to look for a guide for MSM tools.
edit - as an additional point of confusion, my bootloader was unlocked, I was rooted with magisk patched upstream boot.img. Did this happen because I did not know about uninstalling magisk and installing magiosk to the inactive slot? My bootloader is still unlocked, but flashing boot backups etc does not get me out of fastboot loop, and unable to verify boot image error when I try to fastboot boot twrp or orangefox.
You're past the point I can help with, maybe someone else has some more advice for you?
Thanks. And technical support turns out is the only way and sending it in is the only way for the oem unlocked version. I requested a remote session and ended up being told the files aren't working so they can't do a remote session. If they arent working how are they going to flash my device lol...who knows.
Superspecialgueststar,
The released MSM tool is only for the carrier variant and cannot be used for the unlocked variant. There is cryptographic security in place to restrict its use.
You can still fix your unlocked device, just use an unbrick guide for the unlocked version.
[GUIDE] How to unbrick your Nord N200 5G (ALL VARIANTS) or switch bootable slot (REQUIRES UNLOCKED BOOTLOADER)
I've seen alooot of issues lately of people "bricking" their Nord N200's without a method of unbricking (at the time of writing, only T-Mobile variant has MSMTool) I've noticed a reoccurring theme. i myself am guilty of doing it and not...
forum.xda-developers.com
or use my unbrick experience and advice
Un-bricking my Nord N200
Don't ask me why, but I tried to upload a GSI using fastboot to my N200. And that didn't work. So I then read online about other people getting the same error I had, and their fix was deleting the "product" partition and erasing the system...
forum.xda-developers.com