My device was permanently unlocked before I accidentally erased modemst1 and modemst2 partitions without even knowing what these partitions do. Now my phone is network locked again and I can't unlock it. Tell me how to fix this problem please. I don't have backup of modemst1 and modemst2 partitions. I did MSM and also updated to latest software version but network unlock app is giving 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"
}
Can someone give modemst1 and modemst2 partitions backup for tmobile oneplus 9 ?
VioletPotato said:
Can someone give modemst1 and modemst2 partitions backup for tmobile oneplus 9 ?
Click to expand...
Click to collapse
Someone gave me these partitions but the problem is not solved. I am never going to buy tmobile phone again. Network lock is pain. It should have been fixed by re-flashing those partitions. Unlock app is also having server error.
VioletPotato said:
Someone gave me these partitions but the problem is not solved. I am never going to buy tmobile phone again. Network lock is pain. It should have been fixed by re-flashing those partitions. Unlock app is also having server error.
Click to expand...
Click to collapse
There is one solution for network unlock try root and use magisk module to fix data dual sim bug that works even in network locked devices
[TMO] OOS/COS DATA FIX
TO CLARIFY THIS IS A ROOT ONLY FIX After gaining root install given module. Data is now retained. Even after reboot(s). No empty slot or waiting. Issue is TMO variant is showing multi sim. So props were added to make it like a conversion to...
forum.xda-developers.com
rizzmughal said:
There is one solution for network unlock try root and use magisk module to fix data dual sim bug that works even in network locked devices
Click to expand...
Click to collapse
Okay I will try it.
Modemst1/2 are unique to your device. Deleting them was not a good idea. This isn't really fair to blame the tmobile variant for this. You said it was previously unlocked. If your phone was globally unlocked and you deleted the modemst1/2, you'd still have a problem as it holds more than lock/unlock status. It has your imei1/2 and more. I believe it's tied to your hardware serial ID as well
What does your imei show right now when you do *#06# in dialer? If 0, use qualcomm tool to set imei back to normal.
You may be able to extract a valid modemst1/2 from efs/fsg. Using dd to pull efs and flashing that back in or causing efs to repair itself, then maybe or maybe not need using qpst to set your imei back to what it was. Then unlock the sim again.
There's a method I've read about is using qualcomm's tools and a valid qcn. Samsung qpst. But I don't know if it works for OP9!
You get a known good qcn and edit it, then use qualcomm tools to flash the edited qcn into your device. Flashing someone else's modemst1/2 is not a good idea for you or them. Which is why you don't find tons of modemst1/2 files all over xda for people to flash and unlock their phones with. No idea if this works on your device.
You can read more about it here:
https://www.reddit.com/r/Xiaomi/comments/903k2v
Appreciative said:
Modemst1/2 are unique to your device. Deleting them was not a good idea. This isn't really fair to blame the tmobile variant for this. You said it was previously unlocked. If your phone was globally unlocked and you deleted the modemst1/2, you'd still have a problem as it holds more than lock/unlock status. It has your imei1/2 and more. I believe it's tied to your hardware serial ID as well
What does your imei show right now when you do *#06# in dialer? If 0, use qualcomm tool to set imei back to normal.
You may be able to extract a valid modemst1/2 from efs/fsg. Using dd to pull efs and flashing that back in or causing efs to repair itself, then maybe or maybe not need using qpst to set your imei back to what it was. Then unlock the sim again.
There's a method I've read about is using qualcomm's tools and a valid qcn. Samsung qpst. But I don't know if it works for OP9!
You get a known good qcn and edit it, then use qualcomm tools to flash the edited qcn into your device. Flashing someone else's modemst1/2 is not a good idea for you or them. Which is why you don't find tons of modemst1/2 files all over xda for people to flash and unlock their phones with. No idea if this works on your device.
You can read more about it here:
https://www.reddit.com/r/Xiaomi/comments/903k2v
Click to expand...
Click to collapse
I didn't delete the partitions but just erased them. You should know that IMEI is not stored in the modemst partition. Reflashing modemst partition from another tmobile unlocked phone should have fixed the problem but it is still there. This shiit would not have happened on the global model by erasinig modemst partition. My sim is detected but the phone is network locked by t-mobile and the unlock app is not working.
I know how to repair IMEI. SIM Unlock app isn't working with any IMEI including the original IMEI written on the back of phone.
Erasing the modemst1, modemst2 partitions did nothing except fcking up the network unlock. My IMEI , serial number etc is not changed by doing anything to the modemst1,modemst2 partitions. Even after flashing those partitions that @rizzmughal gave me, it didn't change any device information.
rizzmughal said:
There is one solution for network unlock try root and use magisk module to fix data dual sim bug that works even in network locked devices
Click to expand...
Click to collapse
Just tried that magisk module but it didn't work. So I guess will have to sell phone now. TMOBILE is such a nightmare. And that guy @Appreciative is now haha reacting because I told him he is wrong about modemt1,2 partitions lol.
VioletPotato said:
Just tried that magisk module but it didn't work. So I guess will have to sell phone now. TMOBILE is such a nightmare. And that guy @Appreciative is now haha reacting because I told him he is wrong about modemt1,2 partitions lol.
Click to expand...
Click to collapse
Module will work on oos 12 c6x firmwares
VioletPotato said:
it didn't change any device information.
Click to expand...
Click to collapse
It clearly changed something with sle exchange.
As for the rest, maybe so man. I'm not an expert at modemst1 like you are. I haven't ever been expert enough to erase them without a backup either. I'm going by the dozens of reports I've read online and in documents that say modemst1/2 are tied to a hwID, contain imei information, bands and control more than just lock and unlock status.
I guess your experience is great news for the community, we can all share unlocked modemst1/2s and our phones will be unlocked. Oh yeah, how's that working out for you?
There is an initial exchange that takes place when you boot and open the RSU (sim unlock app built in) that sends a registration to tmobile. If you've changed something without rebooting, reboot and open it again to send a new registration request.
You can https log this initial registeatiom request and the attempted unlock request that's failing to see what is being sent over https and see if it's recognizing your imei as it's part of the exchange outbound and inbound.
You will need some method of monitoring https traffic to see that. Burp, fiddler, canary etc. I will include an edited screenshot of what the exchange will look like so you know what to look for if you decide to try it.
Thread closed at OP's request.
Related
I bought my Korean s8 plus new and everything worked great at first.
I rooted it, installed twrp and flashed renovate 3.0 on it. This week I decided to update to renovate 5 but after doing a full wipe to get everything working I ran into the issue of my phone asking for a sim unlock code.
I can restore my backup to renovate 3 and all is fine but if I wipe the phone or restore with Odin I get prompted for the unlock code. I'm using the phone on t mobile.
Any ideas on this?
{
"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"
}
Sent from my SM-G955N using Tapatalk
deh2002 said:
I bought my Korean s8 plus new and everything worked great at first.
I rooted it, installed twrp and flashed renovate 3.0 on it. This week I decided to update to renovate 5 but after doing a full wipe to get everything working I ran into the issue of my phone asking for a sim unlock code.
I can restore my backup to renovate 3 and all is fine but if I wipe the phone or restore with Odin I get prompted for the unlock code. I'm using the phone on t mobile.
Any ideas on this?
Sent from my SM-G955N using Tapatalk
Click to expand...
Click to collapse
That screen appears when your phone isnt unlocked for use in any other career, that's when you have to enter the unlock code for IMEI, but when shows PUK network lock code is when you entered a wrong imei unlock code many times... First... Put 12345678 or 11111111 to unlock the sim network PUK and it will ask again for the imei unlock code , if you don't have it.. You'll have to pay for it.
When a phone is attached to one specific career, if you put another sim that isn't from the native career.. It won't show anything.. That's when you have to change Rom in order to show that screen asking for the code.. That's how you unlock it.
Paxin said:
That screen appears when your phone isnt unlocked for use in any other career, that's when you have to enter the unlock code for IMEI, but when shows PUK network lock code is when you entered a wrong imei unlock code many times... First... Put 12345678 or 11111111 to unlock the sim network PUK and it will ask again for the imei unlock code , if you don't have it.. You'll have to pay for it.
When a phone is attached to one specific career, if you put another sim that isn't from the native career.. It won't show anything.. That's when you have to change Rom in order to show that screen asking for the code.. That's how you unlock it.
Click to expand...
Click to collapse
The Korean smg955n is supposed to be unlocked.
It worked fine at first then all of a sudden started asking for unlock codes as well as the puk code which I got from t mobile.
For a sim unlocked and bootloader unlocked phone this thing is a pain in the butt to flash roms on...lol
Sent from my SM-G955N using Tapatalk
I have a similar problem with Korean S8+ that was given to me by my nephews friend who was in OZ studying. There are no issues with sim lock or network lock or anything like that, but I think the reoccurring password request has to be somehow linked to a Korean carrier or previous owner or even possibly the IMEI? I have loaded combo software on it successfully but have tried every trick to get OEM unlock to show up and can’t, therefor I cannot root. I’ve even installed different firmware versions and still the same persistent password request in Korean is the first thing you see when the phone has loaded the new software??
Can anyone please tell me if they have encountered this type of thing before and if there is a way around it. All checks on blacklisting both internationally and local here in Australia comes up clean.
Look forward to some advice.... cheers
I got this phone on ebay, it was listed as "broken with a clean imei and unlocked" but when I got it, what I received was a "clean" imei, as in the imei wasn't there. I was able to recover the imei in other devices, but here on this device I can't, no matter how hard I try, enable diag mode or, in that case, do anything to come close to modify the imei code. It is written on the back of the phone, and I even opened the phone itself, in order to check if some modem cables were disconnected (which isn't the case). I hope that I didn't get the category wrong, and that you can help me. I was thinking of restoring the phone to stock fw, but I don't think it will change anything. For additional info, every code that i found online crashed my phone, and writing *#06#* returns a blank screen with only "imei" and no actual code. Thanks again in advice, please help me.
Settings, about phone, imie 1 and 2 should show
djhulk2 said:
Settings, about phone, imie 1 and 2 should show
Click to expand...
Click to collapse
I don't need to see it, i need to edit it, since it doesn't exist in the phone, it has been erased
Flash stock rom again
most of the replays are pointless. the efs partition is wiped. You need something to rewrite the efs partition to restore imei.
NoSenze said:
I got this phone on ebay, it was listed as "broken with a clean imei and unlocked" but when I got it, what I received was a "clean" imei, as in the imei wasn't there. I was able to recover the imei in other devices, but here on this device I can't, no matter how hard I try, enable diag mode or, in that case, do anything to come close to modify the imei code. It is written on the back of the phone, and I even opened the phone itself, in order to check if some modem cables were disconnected (which isn't the case). I hope that I didn't get the category wrong, and that you can help me. I was thinking of restoring the phone to stock fw, but I don't think it will change anything. For additional info, every code that i found online crashed my phone, and writing *#06#* returns a blank screen with only "imei" and no actual code. Thanks again in advice, please help me.
Click to expand...
Click to collapse
u should backup ur modemst1 and modemst2
then erase modemst1 and modemst2 and fsg
thene write imei using QCN
Just as I tought, I recovered from it installing the stock fw but now, I've got the error that I was scared of; The network locked error. If someone knows how to network unlock a (probably not payed off) OP7 Pro 5g from sprint, then please let me know. I didn't know all these things when I bought the phone, but now I can't send it back at the other side of the world
I have an alcatel 1b which I am trying to install Magisk and TWRP on (any decent guides on that would be appreciated).
I'm told I first need to unlock the bootloader.
I am on a mac so I have installed ADB via homebrew
If I run
Code:
adb devices
, the device shows up.
I then run
Code:
adb reboot bootloader
and the device boots up into a screen which says "fastboot mode" at the top
I then try
Code:
fastboot oem unlock
and get
Code:
FAILED (remote: 'unknown command')
fastboot: error: Command failed
I tried
Code:
fastboot flashing unlock
and
Code:
fastboot oem unlock-go
and
Code:
fastboot oem get_unlock_code
and get the same response.
I also tried
Code:
ADB fastboot flashing unlock
and got
Code:
ADB: unknown command fastboot
If I enter recovery mode and then select "enter fastboot" I get a different screen with big red text saying "fastbootd" at the top.
If I then try
Code:
fastboot oem unlock
I get
Code:
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
Anybody know what I'm doing wrong/what I can do to get past this?
Same issue here!?
same here its because the bootloader is not unlocked and queries all say it is we need a backup or pull of someones boot.img to make a magisk boot img for our particular phone (seoul tct alcatel 5002s 1b) greatly appreciated if i could get a copy of that
To get Fastboot working try to use Alcatel's USB Driver
Download Alcatel USB Driver for Windows (Latest Driver)
Download the latest and original Alcatel USB Driver to connect any Alcatel Smartphone and Tablets to the Windows Computer quickly.
androidmtk.com
I'm also having the exact same issue. Anyone have a solution yet?
jokey carrot said:
I'm also having the exact same issue. Anyone have a solution yet?
Click to expand...
Click to collapse
Try fastboot flashing unlock-critical, I'm sceptical of it'll work
this is a goid phone to remove bloatware ob and use it for simple things, like an MP3 player. can someone pull the boot.img or show me where i can learn how to do it myself? and how would i patch it with Magisk?
i may just be a newbie, but doesnt putting the device in download mode let you flash anything? could i be able to flash majisk and obtain root while in download mode? or flash TWRP?
I am hoping to unlock the bootloader and use any customer recovery like TWRP or orangefox. Also Alcatel 1b 5002s (Canada) firmware would greatly appreciate if some one can help?
Its not yet possible to unlock the bootloader. For the past year i worked hard to figure this phone out. All of that lead to this
new link down below, the original file had alcatel protection not removed causing imei loss
that file contains firmware, flash tools and has intstructions on how to restore a lost imei.
Hope it helps you. You can also try to look at the bootloader file and try to unlock the phone.
If you need anything more feel free to dirrect message
KashiNEC said:
Its not yet possible to unlock the bootloader. For the past year i worked hard to figure this phone out. All of that lead to this
.........................................................................
that file contains firmware, flash tools and has intstructions on how to restore a lost imei.
Hope it helps you. You can also try to look at the bootloader file and try to unlock the phone.
If you need anything more feel free to dirrect message
Click to expand...
Click to collapse
Where is the firehose loader.bin file located?
I made an error zipping the file. New link here
It is in description
*firehose included*
I have noticed that in other devices they manage to unlock the bootloader through the EDL mode, who removes and needs to perform Test Point or needs more than that, for example a special EDL cable may be necessary, this morning I was trying to backup my Stock ROM with the Inferno Unitool, the funny thing is that it recognized the port but I don't know, it seemed that something else was missing, in the end I ended up flashing the @KashiNEC ROM with the guide of your audit. I'm still interested in installing GSI to at least get an upgrade to A12, I won't give up in the meantime.
Alain+ said:
I have noticed that in other devices they manage to unlock the bootloader through the EDL mode, who removes and needs to perform Test Point or needs more than that, for example a special EDL cable may be necessary, this morning I was trying to backup my Stock ROM with the Inferno Unitool, the funny thing is that it recognized the port but I don't know, it seemed that something else was missing, in the end I ended up flashing the @KashiNEC ROM with the guide of your audit. I'm still interested in installing GSI to at least get an upgrade to A12, I won't give up in the meantime.
Click to expand...
Click to collapse
For now its is not possible to unlock. Alcatel/TCL have clearly thought of someone dumping the system and have taken measures. boot partition doesnt contain the usual "unlock" stuff and bootloader seems to be modified and needs to be signed for the phone to accept it. The only thing you can do is upgrade to the newer russian version of the firmware by changing traceability.bin. But theres a little bit of hope. The bootloader makes a few references to a "secret key" and that it needs to be updated. If we can somehow get the secret key, we can unlock
This device is full of secrets everywhere, it obviously looks like a safe.
{
"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"
}
There were days when I knew there was an engineer mode, however I didn't know how to access that corner, until with the utility shown in the image, I also got the code: *#*#825364 #*#* although not much can be done with this...
Alain+ said:
This device is full of secrets everywhere, it obviously looks like a safe.
View attachment 5685055
There were days when I knew there was an engineer mode, however I didn't know how to access that corner, until with the utility shown in the image, I also got the code: *#*#825364 #*#* although not much can be done with this...
Click to expand...
Click to collapse
Interesting discovery. I think i got how to unlock bootloader now. There is a hidden app on this device called TCL TOKEN. It enables you to unlock bootloader, but requires a valid connection. I couldnt get it to connect
KashiNEC said:
Interesting discovery. I think i got how to unlock bootloader now. There is a hidden app on this device called TCL TOKEN. It enables you to unlock bootloader, but requires a valid connection. I couldnt get it to connect
Click to expand...
Click to collapse
I'm in the same situation. It seems that something else is missing or that service is disabled.
For a moment I thought it was my connection or that I was doing something wrong.
I've recently unlocked the bootloader on my Xiaomi device and have encountered an issue getting past the 'This device is Locked' screen.
I have access to the Xiaomi account that was linked to the device, and have entered the correct information, several times using a combination of both with WIFI and without (mobile data) using two different sim cards, and my email address to verify the account using the 2fa on the device.
Unfortunately the screen just disappears for a second before re-appearing and I'm stuck trying to enter the prompts again.
Has anyone encountered this? Does anyone know how I can bypass this screen to continue with the setup process?
I'll try attaching a video that shows the process of what Is happening and I apologise for the sound -- it's hard trying to juggle two devices and record at the same time.
Video
doomanix said:
I've recently unlocked the bootloader on my Xiaomi device and have encountered an issue getting past the 'This device is Locked' screen.
I have access to the Xiaomi account that was linked to the device, and have entered the correct information, several times using a combination of both with WIFI and without (mobile data) using two different sim cards, and my email address to verify the account using the 2fa on the device.
Unfortunately the screen just disappears for a second before re-appearing and I'm stuck trying to enter the prompts again.
Has anyone encountered this? Does anyone know how I can bypass this screen to continue with the setup process?
I'll try attaching a video that shows the process of what Is happening and I apologise for the sound -- it's hard trying to juggle two devices and record at the same time.
Video
Click to expand...
Click to collapse
Check here that your device appears and that the phone number matches, otherwise delete the phone from your account and try again.
Or use the reset after deleting the device from the account.
Disregard the i clicked on it wanting to click on the video link.
.
.
NOSS8 said:
Check here that your device appears and that the phone number matches, otherwise delete the phone from your account and try again.
Disregard the i clicked on it wanting to click on the video link.
.
.
Click to expand...
Click to collapse
The device appeared originally and I removed it from the account yesterday in the hopes I could get through this barrier.. I've been two days on this being blocked by the 2fa limit in 24h. Unfortunately removing the device didn't seem to help.
Should I look to do a fastboot reset of the device? Do you think that could help? I could try a flashing the xiaomi.eu rom again.
And no worries. I've found it pretty funny past few days how ridiculous it is.
doomanix said:
The device appeared originally and I removed it from the account yesterday in the hopes I could get through this barrier.. I've been two days on this being blocked by the 2fa limit in 24h. Unfortunately removing the device didn't seem to help.
Should I look to do a fastboot reset of the device? Do you think that could help? I could try a flashing the xiaomi.eu rom again.
And no worries. I've found it pretty funny past few days how ridiculous it is.
Click to expand...
Click to collapse
To summarize you have unlocked the bootloader then install a Xiaomi eu rom from a stock rom, right.
What stock rom?
NOSS8 said:
To summarize you have unlocked the bootloader then install a Xiaomi eu rom from a stock rom, right.
What stock rom?
Click to expand...
Click to collapse
Yes, It was Chinese stock.
I did the steps to unlock the bootloader, unlocked, waited for reboot, encountered this screen.
First night I tried to unlock on stock rom -- encountering the same issue as in the video.
Second night I tried after flashing Xiaomi.eu. After 2fa ran out I tried deleting the device from the account.
Tonight, same issue after deleting the device from the account.
I've also tried to submit my request to unlock the device to Xiaomi, but it says I'm unsuccessful as current region is different from frequent sign-in regions (though my country isn't in the dropdown and only 'other' is available).
doomanix said:
Yes, It was Chinese stock.
I did the steps to unlock the bootloader, unlocked, waited for reboot, encountered this screen.
First night I tried to unlock on stock rom -- encountering the same issue as in the video.
Second night I tried after flashing Xiaomi.eu. After 2fa ran out I tried deleting the device from the account.
Tonight, same issue after deleting the device from the account.
I've also tried to submit my request to unlock the device to Xiaomi, but it says I'm unsuccessful as current region is different from frequent sign-in regions (though my country isn't in the dropdown and only 'other' is available).
Click to expand...
Click to collapse
Flashing a Xiaomi Eu rom on a locked device after unlocking the bootloader is not a good idea.
The account and the sim card must be the same as the one used for unlocking.
try reset
{
"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"
}
or flash the same CN rom as the origin with this tool. (do not lock the bootloader)
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
You could try fastboot erase frp command and see if that helps. Thats the command for removing any account locks.
But flashing a new firmware on a locked, or re locked bootloader is generally a big no
Evo400 said:
You could try fastboot erase frp command and see if that helps. Thats the command for removing any account locks.
But flashing a new firmware on a locked, or re locked bootloader is generally a big no
Click to expand...
Click to collapse
For Google account not Xiaomi.
NOSS8 said:
Flashing a Xiaomi Eu rom on a locked device after unlocking the bootloader is not a good idea.
The account and the sim card must be the same as the one used for unlocking.
try reset
View attachment 5721107
or flash the same CN rom as the origin with this tool. (do not lock the bootloader)
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Click to expand...
Click to collapse
Thank you for your support. I reflashed the stock Chinese rom using the flash_all.sh script and unfortunately have encountered the same issue as shown before in the video. To be clear, this issue was happening on the stock rom, then I flashed xiaomi.eu and problem still persisted.
I've used the same number as was used in the unlocking process -- same result occurs it just loops at the unlock screen. Is there anything else you could recommend I do?
The device is no longer linked to my account and I still receive this message upon opening it.
EDIT:
Issue was resolved either by Xiaomi, or by going to Xiaomi Cloud and Find device, selecting the device, selecting the erase device option, then the delete device option from the hamburger menu. Device now seems to be unlocked and setup is appearing. I guess after removing the device from the Xiaomi account it persists in other aspects of the Xiaomi ecosystem.
Expert needed in this Phone Unlocking.
I Need some help.
I will share all files that require to unlock this model.
{
"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"
}
rfeeykhan said:
Expert needed in this Phone Unlocking.
I Need some help.
I will share all files that require to unlock this model.View attachment 5787835
Click to expand...
Click to collapse
how to instant unlock bootloader?
zishhaider said:
how to instant unlock bootloader?
Click to expand...
Click to collapse
Brother you need to get unlock token from : oneplus.com/us/unlock_token
Fill up your info and you will get your unlock token within 1 week. With that token you are able to unlock bootloader.
Reminder!! If you don'y have enough knowledge about this, so I will not recommend you to do this. You may lost your device as I lost.
Khateeb2110 said:
Brother you need to get unlock token from : oneplus.com/us/unlock_token
Fill up your info and you will get your unlock token within 1 week. With that token you are able to unlock bootloader.
Reminder!! If you don'y have enough knowledge about this, so I will not recommend you to do this. You may lost your device as I lost.
Click to expand...
Click to collapse
I got it second hand from olx. Some one has played with imei. Now i don't hv orignal one and since I can't follow official way to unlock bootloader. And i hv some technical knowledge to deal with it but I am still banging here and there to get bl unlock un officially and it seems door has been closed by oneplus.
zishhaider said:
I got it second hand from olx. Some one has played with imei. Now i don't hv orignal one and since I can't follow official way to unlock bootloader. And i hv some technical knowledge to deal with it but I am still banging here and there to get bl unlock un officially and it seems door has been closed by oneplus.
Click to expand...
Click to collapse
I also have T mobile version whose imei is changed. But you can try by putting the original IMEI on OnePlus website at unlock token request, they will process your request. Original IMEI is written at the back of your phone glass if you are using T mobile version. If it's not the T mobile then you don't need that token to unlock bootloader.
Khateeb2110 said:
I also have T mobile version whose imei is changed. But you can try by putting the original IMEI on OnePlus website at unlock token request, they will process your request. Original IMEI is written at the back of your phone glass if you are using T mobile version. If it's not the T mobile then you don't need that token to unlock bootloader.
Click to expand...
Click to collapse
Now I converted my T mobile OnePlus 8 to Global version. And I used the imei that is written at the back of my phone and OnePlus accepted my request and I got the unlock token.
Khateeb2110 said:
This is my unlock token with same device. I'm not sure if it gonna work or not but you can try this one if you don't have your token.
Click to expand...
Click to collapse
Comparing the unlock_code.bin that I have, and yours, they're both different.
You have 2 choices to unlock OP8 TMO variant. Official way ofc is to apply for unlock_code.bin
But also there's a walkaround method which u will have to use MSM Tool to EDL Flash EU fw in your TMO Instantnoodle, and since EU variant is Global, u can easily unlock the bootloader ( but be aware, this method is not going to unlock Network for u if u r still Network locked with TMO )
LinhBT said:
You have 2 choices to unlock OP8 TMO variant. Official way ofc is to apply for unlock_code.bin
But also there's a walkaround method which u will have to use MSM Tool to EDL Flash EU fw in your TMO Instantnoodle, and since EU variant is Global, u can easily unlock the bootloader ( but be aware, this method is not going to unlock Network for u if u r still Network locked with TMO )
Click to expand...
Click to collapse
I tried this once but It said:"Device not matched.."
Khateeb2110 said:
I tried this once but It said:"Device not matched.."
Click to expand...
Click to collapse
U have to find correct MSM Tool.
Khateeb2110 said:
I tried this once but It said:"Device not matched.."
Click to expand...
Click to collapse
You can always use the EDL Tool, though I discourage it. I didn't know what I was doing and permanently destroyed my persist.img, though I think everything went wrong before that, and now I'm unable to use my Fingerprint Sensor with no solution (besides possible recalibration) in view.