Related
Question in title, so far I cannot found anything to solve this problem, not to mention Nokia does not offer official bootloader unlocking
Perhaps @hikari_calyx knows
mingkee said:
Perhaps @hikari_calyx knows
Click to expand...
Click to collapse
are you actually sure? like, Nokia just doesn't let you unlock their phones' bootloader, plus he doesn''t have my device, so how is he able to develop a tool to unlock it?
AltFantasy said:
are you actually sure? like, Nokia just doesn't let you unlock their phones' bootloader, and I actually asked someone on Discord if there's another way, and they said I need to use the EDL tool with a flash file that contains an unlock key, but both I (and they) do not know how to make the file
Click to expand...
Click to collapse
The poster found a patch of bootloader and I used it to unlock 8.3 bootloader and eventually rooted it.
mingkee said:
The poster found a patch of bootloader and I used it to unlock 8.3 bootloader and eventually rooted it.
Click to expand...
Click to collapse
cool, but there's no support for the Nokia X10, it's just released last June, and the poster might not support my phone
mingkee said:
The poster found a patch of bootloader and I used it to unlock 8.3 bootloader and eventually rooted it.
Click to expand...
Click to collapse
Well, apparently they do not support my model (which is the X10). Their tool can only detect the phone, not unlock its bootloader
Well, Nokia/HMD wants to have their phones and tablets deadlocked, and 8.3 is my only and final Nokia Android phone.
No more.
Good Morning,
I have arrived at this thread looking for how to unlock the bootloader of my Nokia X10/X20 for later rooting it.
It seems that there is no way to do it.
To do Root I have found this link (is in Spanish): https://www.ayudaroot.com/root/nokia/como-hacer-root-al-nokia-x10/
The option «Enable OEM unlocking», comes in gray and is not accessible, with which I have not been able to apply this solution.
I have found this other article: How to Unlock Bootloader on Any Nokia Smartphone.
Someone has tried?
If the answer is affirmative, does it work?
If nobody has tried it, do you think it can work?
All the best
gonzo1963 said:
Good Morning,
I have arrived at this thread looking for how to unlock the bootloader of my Nokia X10/X20 for later rooting it.
It seems that there is no way to do it.
To do Root I have found this link (is in Spanish): https://www.ayudaroot.com/root/nokia/como-hacer-root-al-nokia-x10/#comment-41075
The option «Enable OEM unlocking», comes in gray and is not accessible, with which I have not been able to apply this solution.
I have found this other article: How to Unlock Bootloader on Any Nokia Smartphone.
Someone has tried?
If the answer is affirmative, does it work?
If nobody has tried it, do you think it can work?
All the best
Click to expand...
Click to collapse
Nope, the "buying unlock bootloader keys" (I meant the thing in the "How to Unlock Bootloader on Any Nokia Smartphone" article, the official way also does not work anymore, due to the site is dead) way does not work on the Nokia X10/20 (the creators of those keys confirmed with me that it's literally impossible to unlock those phones and potentially any future Nokia phones).
The "Enable OEM unlocking" should not be not accessible, my Nokia X10 does not have that option greyed out.
About the tool used in the Spanish site? I'm not so sure about whether it will work or not. The tutorial video shows a different phone, but it seems so legit. Try it at your own risk, I guess.
AltFantasy said:
Nope, the "buying unlock bootloader keys" (I meant the thing in the "How to Unlock Bootloader on Any Nokia Smartphone" article, the official way also does not work anymore, due to the site is dead) way does not work on the Nokia X10/20 (the creators of those keys confirmed with me that it's literally impossible to unlock those phones and potentially any future Nokia phones).
The "Enable OEM unlocking" should not be not accessible, my Nokia X10 does not have that option greyed out.
About the tool used in the Spanish site? I'm not so sure about whether it will work or not. The tutorial video shows a different phone, but it seems so legit. Try it at your own risk, I guess.
Click to expand...
Click to collapse
Good morning,
Thank you very much for the answer, but I inform you:
My phone is new, just arrived from the provider (Nokia directly).
-Modelo: TA1332.
-Compilation 00WW_1_070.
-Android 11.
-Actualization May 5, 2021
I have not modified anything, and I assure you that the «Enable OEM Unlocking» option, is gray and is not accessible.
A rectification, I think.
The link in Spanish: https://www.ayudaroot.com/root/nokia/como-hacer-root-al-nokia-x10/#comment-41075
In the article, not in the video; It refers to a Qualcomm chip, but requires that the "Enable OEM Unlocking" option is unlocked.
Three questions apart:
1.- Is there any way to root this smartphone?
2.- Is this option valid to make a backup of the ROM?: [Tutorial] How to use Miracle Box to backup Qualcomm Android firmware
3.- And is it to restore the ROM?: [Tutorial] How to use Miracle Box / Thunder to flash firmware to Qualcomm devices
All the best
gonzo1963 said:
Good morning,
Thank you very much for the answer, but I inform you:
My phone is new, just arrived from the provider (Nokia directly).
-Modelo: TA1332.
-Compilation 00WW_1_070.
-Android 11.
-Actualization May 5, 2021
I have not modified anything, and I assure you that the «Enable OEM Unlocking» option, is gray and is not accessible.
A rectification, I think.
The link in Spanish: https://www.ayudaroot.com/root/nokia/como-hacer-root-al-nokia-x10/#comment-41075
In the article, not in the video; It refers to a Qualcomm chip, but requires that the "Enable OEM Unlocking" option is unlocked.
Three questions apart:
1.- Is there any way to root this smartphone?
2.- Is this option valid to make a backup of the ROM?: [Tutorial] How to use Miracle Box to backup Qualcomm Android firmware
3.- And is it to restore the ROM?: [Tutorial] How to use Miracle Box / Thunder to flash firmware to Qualcomm devices
All the best
Click to expand...
Click to collapse
Apparently, the creators of the site that sells bootloader unlocking keys for Nokia phones said that you should ignore sites like the Spanish link, because those websites write similar content for every device that exists and just replace the device name and publish it again, then again for another device. But I guess you can try using it and see, I guess?
For the first question, I don't think you can root the phone with Magisk? You need some files inside the ROM file, but there's no ROM files for Nokia X10/20.
For the second and third question, I do not know if the tool even works. I do ask the creators of that site (again), and I quote:
I don't think they will work. The only way to trigger EDL on the device would be to disassemble and then short the testpoint to trigger EDL. But what next? What do you aim to do while in EDL mode?
We do not know which bytes are written on the chip that remembers the unlocked status. So, even in EDL mode, there isn't much that we can tinker and re-write to the device. I am also unsure if the user firmware that hmd ships to the Nokia Care includes EDL programmer, they never did for the Nokia 7.2 (the last Nokia device I really tried to play around with). Without the programmer, none of the EDL flash tools will work and we can't load just any programmer. It has to be signed by the OEM. A wrong/invalid/modified firehose programmer can put the device into a non-recoverable state.
HMD hasn't done much magic into making the phones more appealing to the buyers. But they have money and time to make more mess behind the scenes to make their devices more secure (which they think is better).
Sorry for the rant, but there's no meaningful ways to unlock the Nokia X10/20 and possibly any forthcoming phone.
Click to expand...
Click to collapse
In conclusion: It's impossible, but you can try? (Try it at your own risk of course, you could brick the whole thing, and nothing will fix it.) I do not even know if it's possible or not, so... eh?
gonzo1963 said:
Good morning,
Thank you very much for the answer, but I inform you:
My phone is new, just arrived from the provider (Nokia directly).
-Modelo: TA1332.
-Compilation 00WW_1_070.
-Android 11.
-Actualization May 5, 2021
I have not modified anything, and I assure you that the «Enable OEM Unlocking» option, is gray and is not accessible.
A rectification, I think.
The link in Spanish: https://www.ayudaroot.com/root/nokia/como-hacer-root-al-nokia-x10/#comment-41075
In the article, not in the video; It refers to a Qualcomm chip, but requires that the "Enable OEM Unlocking" option is unlocked.
Three questions apart:
1.- Is there any way to root this smartphone?
2.- Is this option valid to make a backup of the ROM?: [Tutorial] How to use Miracle Box to backup Qualcomm Android firmware
3.- And is it to restore the ROM?: [Tutorial] How to use Miracle Box / Thunder to flash firmware to Qualcomm devices
All the best
Click to expand...
Click to collapse
Also, next time you buy a phone, just go buy a Samsung/Xiaomi or whatever brand that do support unlocking their phones' bootloader and pray that the phone you bought in the future got tons of custom ROMs ported to it or something, Nokia thinks that locking their phones' bootloader will make those phones more secure, which is purely bull****. If you ABSOLUTELY have to buy a Nokia phone however, go buy an older one, cause the site with unlock keys only support those old phones, and it might be impossible to even unlock new phones coming from Nokia in the future.
AltFantasy said:
Also, next time you buy a phone, just go buy a Samsung/Xiaomi or whatever brand that do support unlocking their phones' bootloader and pray that the phone you bought in the future got tons of custom ROMs ported to it or something, Nokia thinks that locking their phones' bootloader will make those phones more secure, which is purely bull****. If you ABSOLUTELY have to buy a Nokia phone however, go buy an older one, cause the site with unlock keys only support those old phones, and it might be impossible to even unlock new phones coming from Nokia in the future.
Click to expand...
Click to collapse
Good afternoon,
Thank you very much for all the information you have given me.
It has no solution, I bought an X10 and an X20, because they have Android One and will have updates for 3 years.
I thought I could unlock it and do root, and I see that it is impossible or it is very difficult.
All the best
gonzo1963 said:
Good afternoon,
Thank you very much for all the information you have given me.
It has no solution, I bought an X10 and an X20, because they have Android One and will have updates for 3 years.
I thought I could unlock it and do root, and I see that it is impossible or it is very difficult.
All the best
Click to expand...
Click to collapse
Wait, you bought both? Well, if you're trying to root them, then too bad, it's literally impossible. But if you're just using both phones normally, I would say: They're actually pretty good! The specs are great for medium gaming, the build quality is really nice, the cameras are not bad honestly. They're slightly overpriced, but they felt nice enough to use daily. Too bad Nokia ruined these phones with the bootloader unlocking problem though, and I swear I'll never buy a Nokia again, cause of this problem, even though they might be one of the best phones I've ever used.
Good evening,
I have tried to do what they explain in the article in Spanish: https://www.ayudaroot.com/root/nokia/como-hacer-root-al-nokia-x10/ and it has been impossible to do anything.
I have found the following problems:
1.- The option "Enable OEM unlocking", comes in gray and is not accessible on the smartphone.
2.- You can not extract the "boot.img" file, because at the link that explains how to do it: https://www.ayudaroot.com/actualizar/alternativa-para-conseguir-la-rom-de-un-telefono-movil/ do not explain how to do it for this smartphone, which is "Qualcomm", not "MTK"; with which it is impossible to extract it.
3.- The "Qualcomm" and «ADB» drivers that are installed with the application are not worth connecting the Nokia X10 to the computer, I had to uninstall them so that the computer itself detects the smartphone.
4.- You can not unlock the bootloader in the way they explain it, so nothing can be done.
5.- The video of the end still confuses more, it is not for this smartphone or a similar one.
Therefore, the item is not useful.
Better forget it and not waste time.
Greetings
gonzo1963 said:
Good evening,
I have tried to do what they explain in the article in Spanish: https://www.ayudaroot.com/root/nokia/como-hacer-root-al-nokia-x10/ and it has been impossible to do anything.
I have found the following problems:
1.- The option "Enable OEM unlocking", comes in gray and is not accessible on the smartphone.
2.- You can not extract the "boot.img" file, because at the link that explains how to do it: https://www.ayudaroot.com/actualizar/alternativa-para-conseguir-la-rom-de-un-telefono-movil/ do not explain how to do it for this smartphone, which is "Qualcomm", not "MTK"; with which it is impossible to extract it.
3.- The "Qualcomm" and «ADB» drivers that are installed with the application are not worth connecting the Nokia X10 to the computer, I had to uninstall them so that the computer itself detects the smartphone.
4.- You can not unlock the bootloader in the way they explain it, so nothing can be done.
5.- The video of the end still confuses more, it is not for this smartphone or a similar one.
Therefore, the item is not useful.
Better forget it and not waste time.
Greetings
Click to expand...
Click to collapse
Weird, my OEM unlocking is not greyed out.
jukyO said:
Weird, my OEM unlocking is not greyed out.
Click to expand...
Click to collapse
mine too, but then it's a useless feature anyway, cause Nokia does not let anyone to unlock its phones' bootloaders
jukyO said:
Weird, my OEM unlocking is not greyed out.
Click to expand...
Click to collapse
AltFantasy said:
mine too, but then it's a useless feature anyway, cause Nokia does not let anyone to unlock its phones' bootloaders
Click to expand...
Click to collapse
Good Morning,
After installing all security updates, it has also been made accessible.
It is no longer gray, but it does not work for nothing, since there is no way to unlock it.
Regards
gonzo1963 said:
Good Morning,
After installing all security updates, it has also been made accessible.
It is no longer gray, but it does not work for nothing, since there is no way to unlock it.
Regards
Click to expand...
Click to collapse
also, I think you should try contacting their customer service, and hope that they'll accept or something. If not, keep on annoying them with the "Can you unlock my phones' bootloaders?" question, and see if they will answer or not.
Hey brothers , am a random guy looking forward to get my brand new Nokia x10 soon. And according to all paragraphs I read above it seems the main thing I need from this device apart from daily usage is inaccessible which it ""unlocking the bootloader"* But am not totally sure if it's still impossible because it's almost a year since you're conversing and it seemed to be impossible according to what I've looked at in your Conversations. Back to the topic- I got a Nokia service-center in my area here so I need your advise if I'll be able to take there the Nokia x10 and they unlock the bootloader "Incase I buy it" on their end because there have access to everything I assume whereas they're working for Nokia but it looks risky for me to get a device before am sure if it'll go up with what I need from it.......In conclusion if any of you knows a method to unlock the bootloader currently "because it's almost a year when it was impossible". You may advise me before making the mistake I'll regret. Goodnight
Please upload this tool if you have it so i can fix my phone .. at this point t-mobile, metro pcs and god knows what they all were able not only to fix their phone but install the unlocked rom without the bloatware .. Honestly i don't get why OP refuses to release this .. or maybe they have but its not posted here ..
So if you bought your phone from oneplus.com and have the unbricking tool .. please upload it or tell me how you managed to fix your phone
Contact OnePlus support, and request a remote session to repair your phone.
If they set one up, they'll send you a link to download the MSMDownload Tools ahead of time.
So far everyone with unlocked version has been told to mail their phone in, rather than doing the remote session. Once someone gets the remote session, they'll be able to upload the MSMDownload Tools.
edale1 said:
Contact OnePlus support, and request a remote session to repair your phone.
If they set one up, they'll send you a link to download the MSMDownload Tools ahead of time.
So far everyone with unlocked version has been told to mail their phone in, rather than doing the remote session. Once someone gets the remote session, they'll be able to upload the MSMDownload Tools.
Click to expand...
Click to collapse
already went thru that and instead of sending my phone in chose to wait for the tool.. looks like i made a huge mistake and now is too late to send it in ... but thanks for suggesting
Also waiting for an ops for the unlocked variant - I have a theory that converts between variants without unlocking BL, but without the ops it can't be verified.
I believe One Plus is not releasing their MSM tool specifically because it could be used to convert variants to unlocked / retail. They have refused multiple board members, myself included, to utilize the tool to remotely fix broken devices.
Dimitrimem, check the unbrick thread for my instructions on how to fix phones using fastboot and a super.img or fastbootd and the OTA.
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
oCAPTCHA said:
I believe One Plus is not releasing their MSM tool specifically because it could be used to convert variants to unlocked / retail. They have refused multiple board members, myself included, to utilize the tool to remotely fix broken devices.
Dimitrimem, check the unbrick thread for my instructions on how to fix phones using fastboot and a super.img or fastbootd and the OTA.
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
Click to expand...
Click to collapse
Bootloader is locked so fastboot is not an option ..
Do you have the unlock code bin file?
If so do the following, because booting in fastboot itself will give you an error saying you cannot unlock the bootloader, you most boot into recovery, fastboot is not recovery it's considered the master recovery Incase if the Android recovery fails or you flashed the wrong file to the wrong partition.
Winnower Amber said:
Do you have the unlock code bin file?
Click to expand...
Click to collapse
I don't
You'll need to give that information. Check the box, your serial number should be on it.
Does Android recovery work?
Winnower Amber said:
You'll need to give that information. Check the box, your serial number should be on it.
Click to expand...
Click to collapse
I threw the box away .. let me see if I can find it in my mail with oneplus
Winnower Amber said:
You'll need to give that information. Check the box, your serial number should be on it.
Click to expand...
Click to collapse
The only thing I have from my mail with oneplus is the IMEI number from the form they made me fill in for the remote session only that later on they told me they don't have the files(msm) for my phone
If IMEI and serial number are the same let me know and I'll post thst here
The most you could do is get the unlock code bin. Then wait 7 days for a reply, flash your device with the TMobile msm, and then follow the TMobile to oem, that should do it.
If you need to reach me for stuff like this, I am available on discord via the xda,
Winnower Amber said:
Does Android recovery work?
Click to expand...
Click to collapse
From the screen itself. No it boots back to the error .. but I was able to get into recovery by pressing volume up and down
Winnower Amber said:
The most you could do is get the unlock code bin. Then wait 7 days for a reply, flash your device with the TMobile msm, and then follow the TMobile to oem, that should do it.
Click to expand...
Click to collapse
I have the fully paid variant.. so I don't need the unlock code... That's t-mobile.. my bootloader is locked or OEM is locked
Your phone comes preloaded with an emergency boot chip called Qualcomm download mode. Use the TMobile msm tool to flash your device back to factory, then you can essentially do what you need. To get back to oem.
I keep forgetting to quote reply I hate this lol.
Winnower Amber said:
Your phone comes preloaded with an emergency boot chip called Qualcomm download mode. Use the TMobile msm tool to flash your device back to factory, then you can essentially do what you need. To get back to oem.
Click to expand...
Click to collapse
My phone does not work with the MSM tool for TMobile... already tried that ( others already tried it so I'm not alone)
Just a quick heads-up.
unlock token - OnePlus (United States)
www.oneplus.com
By the way, to root without readily available stock firmware, first unlock bootloader, then boot a pre-rooted GSI with DSU Sideloader, pull stock boot partition from there, and finally patch/flash it. This applies to the Open variant as well.
AndyYan said:
Just a quick heads-up.
unlock token - OnePlus (United States)
www.oneplus.com
By the way, to root without readily available stock firmware, first unlock bootloader, then boot a pre-rooted GSI with DSU Sideloader, pull stock boot partition from there, and finally patch/flash it. This applies to the Open variant as well.
Click to expand...
Click to collapse
Tried to unlock but apparentpy my device only has 7 digits in the serial number which keeps me from being able to use the website to request the unlock code.
I used the debloat script I found on n200 threads to get oem unlock on option. T-Mobile variant
PsYk0n4uT said:
Tried to unlock but apparentpy my device only has 7 digits in the serial number which keeps me from being able to use the website to request the unlock code.
I used the debloat script I found on n200 threads to get oem unlock on option. T-Mobile variant
Click to expand...
Click to collapse
Try prepending 0s?
Well. I was thinking that doing that would make the unlock token they give me different from what the phone would be expecting
PsYk0n4uT said:
Well. I was thinking that doing that would make the unlock token they give me different from what the phone would be expecting
Click to expand...
Click to collapse
Tried adding zero on front and back of serial it just tells me invalid serial
PsYk0n4uT said:
Tried adding zero on front and back of serial it just tells me invalid serial
Click to expand...
Click to collapse
Chatting with OnePlus hasn't yielded anything so far
Just a tip, because in my infinite forgetfulness I wasted an hour last night trying to figure out why I was getting the error, fastboot could not open target HAL.
Remember that you must request the unlock code from fastboot, not fastbootd. Which is what you will boot into if you issue adb reboot fastboot.
So here's a quick step by step.
1.Enable usb debugging. 2. Connect your device and allow access for the computer. My device asks if I want it to charge or transfer files. Select transfer files/Android auto and then use adb start-server. May have to unplug the USB cable and reconnect. Select "always allow this device/PC".
3. Issue "adb devices" to make sure your connected.it should list your device by it's serial number. If not then try unplugging the device and revoke adb authorizations in dev options and toggle USB debugging off and back on, may even need to reboot the device to get it to connect after doing this.
4. If your device is listed under devices go ahead and issue "adb reboot fastboot"
5. Once rebooted issue "fastboot devices" and make sure the device is listed again.(If not listed make sure you have your driver's installed correctly and fastboot is installed correctly, may need to install Android SDK into same folder as fastboot)
6.You can select English or whatever language if you want but it doesn't seem necessary.You are in fastbootd mode you will see if you DO select a language.
So from here issue"fastboot reboot bootloader" device will reboot and you will have scrollable option at the top beginning with a big green START at the top. This is regular fastboot And where you wanna be to get your unlock code for submitting to Oppo for your unlock token.
7. Issue "fastboot oem get_unlock_code"
8. It should return the info you need, you will also need your IMEI number when submitting so be sure to copy that down.
you can copy and paste the unlock code into notepad or Word and delete out the extra stuff so your left with just the two lines of your unlock code as one single contiguous string of numbers.
8. Go to the link listed by OP and submit the required info. And wait for what seems like forever.
ADB/Fastboot commands-quick recap.
1. adb reboot fastboot
2. fastboot reboot bootloader
3. fastboot oem get_unlock_code
PsYk0n4uT said:
ADB/Fastboot commands-quick recap.
1. adb reboot fastboot
2. fastboot reboot bootloader
3. fastboot oem get_unlock_code
Click to expand...
Click to collapse
Simply "adb reboot bootloader". You won't need fastbootd until GSIs (which I already did ofc).
Thanks, definitely a quicker way to get to fastboot. I guess I wasn't sure if you could reboot directly. Seems maybe I was confusing an older device where you had to reboot to fastboot then "fastboot reboot fastboot" to get to fastbootd for a whole different reason.
This one goes directly to fastbootd when you "adb reboot fastboot"
Nice catch.
with this particular model in scope, what do either of you guys suggest I do if I have gottne the age old bricked message "destroyed boot/recovery image"".. I've tried the MSMTool route and cna't get it to register under Device Manager with the Qualcomm drivers.. It's highly upsetting..
I'm not really sure to be honest, this is my first OnePlus device and just trying to contribute anything I can to get the N20 section up and going as I make progress with the device.
Just a quick search though turns up this and maybe it could be of use if you can still access the bootloader.
the current image(boot/recovery) have been destroyed
I updated my oneplus 8t to KB2005_11.C.11 (OOS 12 ) by first booting to twrp-3.6.1_11-0-kebab.img and then flashed the KB2005_11_C_OTA_1100_all_362b9b_10100001.zip. After the upgrade I had no mobile data on t-mobile and had Volte instead of 5g...
forum.xda-developers.com
Someone mentions extracting the boot.img from stock image and flashing it. I would imagine it should work for you if the stock firmware can be found and circumstances are similar. Maybe at least a start. Wish I could be of more help, maybe someone else can chime in that knows more.
Try Linux, maybe a live dist. if your on a windows machine that won't recognize it just to get it into a state that you can work with it again.
Just an idea, I don't want to steer you wrong as i still have a lot to learn
DrScrad said:
with this particular model in scope, what do either of you guys suggest I do if I have gottne the age old bricked message "destroyed boot/recovery image"".. I've tried the MSMTool route and cna't get it to register under Device Manager with the Qualcomm drivers.. It's highly upsettinghav
Click to expand...
Click to collapse
DrScrad said:
with this particular model in scope, what do either of you guys suggest I do if I have gottne the age old bricked message "destroyed boot/recovery image"".. I've tried the MSMTool route and cna't get it to register under Device Manager with the Qualcomm drivers.. It's highly upsetting..
Click to expand...
Click to collapse
I want to try and help but I'm so new it's sketchy I don't want to say something and get bashed
Please feel free to comment. Don't worry about the trolls. We would love to have you to be part of this conversation. If you have suggestions just post them, and if your unsure about anything just mention that you are. It's a great way to learn. Don't worry about negative feedback, take it as constructive criticism. You may find that the feedback can clear up many questions and/or misconceptions. You never know how your dialogue with other members could help someone else in the future. These forums are here to document all of it just for that purpose. We are all here to learn or help others who want to learn. Though this account is only a year old I have been around these forums on and off for many years and I learn something each and every time I come in search of wisdom. I'm by no means an expert but I find that others benefit from my questions and answer just as much as I have over the years.
Fyi according to a recently made friend who also had the 7 digit serial issue, they were told by OnePlus their dev team is working on an OTA update that will resolve the serial number issues. I'm not sure how that's going to work but I saw the email between them and Oppo support
I guess this must be a widespread issue that they feel is cheaper to invest the amount of money it takes for r&d to come up with a fix than it was to replace a few devices or attempt to do remote repairs.
But this also makes me wonder what avenue they will take to correct the issue.
Also I wonder if someone with the right skillset could gather enough bootloader unlock codes along with the unlock tokens, serial, IMEI, pcba etc.. maybe the algorithm their using to generate the codes could be broken. I'm no crypto expert or math genius either, but if we have the variables to the equation minus one but have the answer, isn't this pretty simple almost pre-algebra?
I mean I guess their not worried about enough people being brave enough to give out sensitive info like that. But maybe Im just ignorant of the complexity of these algorithms.
64 digit key on one end
T-Mobile bought sprint and they have T-Mobile sims no. But I understand that sprint is still a somewhat seperate company (tried to buy a T-Mobile phone and it would not activate on my sprint account. So I bought this from the sprint side of the T-Mobile site so I knew it would work but I assume this is a sprint phone and not a T-Mobile phone so this method would not work.
Can anyone confirm this?
PsYk0n4uT said:
Please feel free to comment. Don't worry about the trolls. We would love to have you to be part of this conversation. If you have suggestions just post them, and if your unsure about anything just mention that you are. It's a great way to learn. Don't worry about negative feedback, take it as constructive criticism. You may find that the feedback can clear up many questions and/or misconceptions. You never know how your dialogue with other members could help someone else in the future. These forums are here to document all of it just for that purpose. We are all here to learn or help others who want to learn. Though this account is only a year old I have been around these forums on and off for many years and I learn something each and every time I come in search of wisdom. I'm by no means an expert but I find that others benefit from my questions and answer just as much as I have over the years.
Click to expand...
Click to collapse
okay peep theres a way i put my oneplus into efu mode, hold both vol up and down then put usb c in continue to hold u should hear PC recognize it
So, before i do it, would deleting the modemst1/modemst2 partitions still let me bypass the t-mobile sim lock and let me unlock the phone like it did on the old oneplus phones?
Flashed a patched boot.img and lost modems. Anyone willing to post the modems? Are they device specific like a device partition?
Sim locked and trying to recover. No radios are working
Ok , lemme cover my bases here... OnePlus 10t, Android 12, T Mobile. .
I have usb debugging on, oem unlock on, and device appears in ADB ... Newest platform tools, updated drivers.... When I run 'adb reboot bootloader', the phone shuts off, then I see 'fastboot mode' for like half a second , and it goes off and boots up normal. I can enter fastbootd .. but regular fastboot causes instant reboot! Can ANYONE help me with what I need to do? You can't unlock bootloader in fastbootd... So I need help figuring out how to make it NOT kick out of fastboot when I enter the command. (Usb 2.0)
OPPO locked the bootloader permanently. They do this on the find series as well.. basically bootloader mode is disabled.
I haven't heard about this before, is it a T-Mobile only thing? That seems really bad for oppo to do that...
Hurt Copain said:
OPPO locked the bootloader permanently. They do this on the find series as well.. basically bootloader mode is disabled.
Click to expand...
Click to collapse
ok , so how then can i either re activate this mode or root this device? because that is a deal breaker for me! I wont keep the ONLY model of this phone that has Fastboot disabled, and therefore is unable to be rooted! I have about 8 days left to package back up and send back to Tmobile for refund! Now i can fully reach EDL mode, so if there is a software that can let me flash the EU Unlocked FW , then please direct me. I saw some success written about here with the new MSM, but it requires some authentication. I am 100% fully committed to any method, no matter how complex, to rectify this travesty! The ONLY reason i jumped from Samsung to OnePlus years ago was because of how Developer friendly they were... Easy unlock of bootloader... yadda yadda! Now the curse of Beatbreaker has struck again, and the impossible has happened in that SAMSUNG bootloaders are now easily unlockable via purchased token... and Oneplus has become part of an asshat dictatorship.
Please advise if there is ANYONE here who can either help me with this situation, or can direct me to instructions/software that can flip this situation around. I mean, the fact that Fastbootd reports my device in "Fastboot" when running 'Fastboot devices' ... AND that even if only for a glimpse of a second i can see FASTBOOT MODE, before it kicks me out and reboots, tells me that there must be some glitch, exploit, or workaround that can re-enable it! I only state this because some phone companies (carriers) like Metropcs were pre-installing FW that made Download mode disabled for quite a few devices, but thru some low level (edl) actions, we were able to reverse that and load a global fw to the phones, restoring all functions!
ok long posts.... ANYONE... I am up for ALL suggestions, because i can fully brick this phone and return it , but my window closes in 7 days!
beatbreakee said:
ok , so how then can i either re activate this mode or root this device? because that is a deal breaker for me! I wont keep the ONLY model of this phone that has Fastboot disabled, and therefore is unable to be rooted! I have about 8 days left to package back up and send back to Tmobile for refund! Now i can fully reach EDL mode, so if there is a software that can let me flash the EU Unlocked FW , then please direct me. I saw some success written about here with the new MSM, but it requires some authentication. I am 100% fully committed to any method, no matter how complex, to rectify this travesty! The ONLY reason i jumped from Samsung to OnePlus years ago was because of how Developer friendly they were... Easy unlock of bootloader... yadda yadda! Now the curse of Beatbreaker has struck again, and the impossible has happened in that SAMSUNG bootloaders are now easily unlockable via purchased token... and Oneplus has become part of an asshat dictatorship.
Please advise if there is ANYONE here who can either help me with this situation, or can direct me to instructions/software that can flip this situation around. I mean, the fact that Fastbootd reports my device in "Fastboot" when running 'Fastboot devices' ... AND that even if only for a glimpse of a second i can see FASTBOOT MODE, before it kicks me out and reboots, tells me that there must be some glitch, exploit, or workaround that can re-enable it! I only state this because some phone companies (carriers) like Metropcs were pre-installing FW that made Download mode disabled for quite a few devices, but thru some low level (edl) actions, we were able to reverse that and load a global fw to the phones, restoring all functions!
ok long posts.... ANYONE... I am up for ALL suggestions, because i can fully brick this phone and return it , but my window closes in 7 days!
Click to expand...
Click to collapse
Dang! This is a messy situation for yah! I contacted support for an MSM tool and they said I have to send it in for them to flash it.
I think trying to have them flash some other variant would take you past your 7 day window and they may not do it anyways.
I would say least send an email to OnePlus support and ask if they would flash to other variant otherwise you will be returning the phone. You should get a response soon. Otherwise I'd lean towards returning it... Sadly.
Then buy straight from oneplus if you still want a 10t. They may have a good blackfriday deal on this phone as well.
maamdroid said:
Dang! This is a messy situation for yah! I contacted support for an MSM tool and they said I have to send it in for them to flash it.
I think trying to have them flash some other variant would take you past your 7 day window and they may not do it anyways.
I would say least send an email to OnePlus support and ask if they would flash to other variant otherwise you will be returning the phone. You should get a response soon. Otherwise I'd lean towards returning it... Sadly.
Then buy straight from oneplus if you still want a 10t. They may have a good blackfriday deal on this phone as well.
Click to expand...
Click to collapse
thank you ... i was waiting for the response from someone who had been in contact with them. I will mail them right away.
This is just a PSA for anyone currently with T-Mobile, looking to upgrade or purchase from the carrier.
The T-Mobile exclusive model of the 10T 5G is CPH-2419 ... This is a T-Mobile model ONLY. It can be SIM unlocked through regular methods, ie. paying the full contract off, but that is ALL!
There is absolutely NO WAY to unlock the bootloader of this model, because FASTBOOT is completely disabled, and unable to be re-enabled through any method which is currently available!
This is a software level block, which is specific to this model number.
AFAIK the chipset, board, and all internals are the exact same in respect to the 2413 (india) , 2415 (global) , and 2417 (EU) variants , so there is a SLIM possibility that if you stay BELOW the current A.11 build, you MIGHT be able to force a sideways shift to one of the other regions listed above via the Local Update, and Oxygen Updater combination, but i cannot confirm this due to my accidental mistake of not blocking updates! Mine is now on A.11 which is not available in any other region as of yet on the Oxygen Updater.
I really dont know whether changing regions will actually bring back FASTBOOT or not, except that when attempting to reach FASTBOOT via ADB or other methods, there is a brief, 1 second delay that does indeed make the "Fastboot Mode" screen appear, right before it automatically kicks out and reboots into normal mode. But even then with FASTBOOT running on my pc, and <waiting for devices>, it does not make the connection during the sequence. So this may just be remnants of the bootloader screen!
Also FASTBOOTD does work, and you can send commands regularly via command line, or Fastboot Enhance in that mode, but unlocking, and oem commands either fail or report unrecognized.
ANYONE proficient with probing ADB, Fastbootd, or EDL modes would be highly appreciated, in investigating any possibilities to exploit this restriction, because as with ALL android OS devices, I am almost 100% sure there is a way to mitigate this block, and flash a STOCK payload from one of the other variants. But EVERY cph2419 no matter what build, is shipped with FASTBOOT disabled at the factory level. It is an OPPO block, and has nothing to do with T-mobile other than the fact that they are the ONLY carrier listed in this model's designation.
I had a feeling that this was coming. First it starts with T-Mobile variants and then it starts trickling out to everything else. Keep in mind that Oppo disables fastboot on their devices too. The MSM Tool being locked down behind a technician login was the first hint of what's to come.
EtherealRemnant said:
I had a feeling that this was coming. First it starts with T-Mobile variants and then it starts trickling out to everything else. Keep in mind that Oppo disables fastboot on their devices too. The MSM Tool being locked down behind a technician login was the first hint of what's to come.
Click to expand...
Click to collapse
Yup man... see i never read much into the OPPO acquisition of OnePlus, or i would have researched affected devices further. But in all honesty i wouldn't have suspected that a phone such as the 10 series, which is reportedly going to be on all the major carriers in the next 3-4 months, would take such a drastic step BACKWARDS like this! One plus has ALWAYS been known as "Developer Friendly", and rivaled the Google Pixel series in ease of unlocking bootloader, and rooting! But even stranger is how for so long back in the early days of android, devices were model specific to each carrier, (samsung s2, 3, 4... Moto Z... etc.) then the manufacturers wised up and went to universal hardware that was only sim locked, and could be bought outright unlocked. THEN COMES THIS LEFT TURN, in OnePlus taking a flagship device, and going back to Carrier specific models!
Finally the MOST SHOCKING notion comes with the realization that (for a fee) you can get your Samsung devices bootloader unlocked, (s10 and newer, possibly others thru same service) but this OPPO/Oneplus trainwreck looks to be the possible path coming for even more models like you said!
I just dont understand the war on unlockable bootloaders?! Especially Oneplus... they had the PERFECT system in place. (US models) You had to PHYSICALLY submit a Bootloader Unlock request... Acknowledge that you are aware that you are giving up warranty... wait a week (buyers remorse)... Then if still committed, you have to flash the unlock token. Why go all DICTATOR on us and start moving the devices STILL BRANDED with OnePlus, to a locked down format? Maybe 3 in 10 customers unlock & mod their phones! It takes MORE effort to disable functions and remove them, while at the same time alienating those 3 in 10 thus ensuring LESS SALES!! I fail to understand the logic. I just pray someone always keeps probing these A-hole companies products, for vulnerabilities and exploits that circumvent all their overbearing attempts to control what we can do with OUR devices!
<rant... sorry, this crap just makes my blood boil. cuz i DID demo the 10T at a T-mobile store and they had CPH-2417 models as demo, which were fine. Come to find out that they always planned on only SHIPPING or SELLING these 2419 models to the public!>
beatbreakee said:
Yup man... see i never read much into the OPPO acquisition of OnePlus, or i would have researched affected devices further. But in all honesty i wouldn't have suspected that a phone such as the 10 series, which is reportedly going to be on all the major carriers in the next 3-4 months, would take such a drastic step BACKWARDS like this! One plus has ALWAYS been known as "Developer Friendly", and rivaled the Google Pixel series in ease of unlocking bootloader, and rooting! But even stranger is how for so long back in the early days of android, devices were model specific to each carrier, (samsung s2, 3, 4... Moto Z... etc.) then the manufacturers wised up and went to universal hardware that was only sim locked, and could be bought outright unlocked. THEN COMES THIS LEFT TURN, in OnePlus taking a flagship device, and going back to Carrier specific models!
Finally the MOST SHOCKING notion comes with the realization that (for a fee) you can get your Samsung devices bootloader unlocked, (s10 and newer, possibly others thru same service) but this OPPO/Oneplus trainwreck looks to be the possible path coming for even more models like you said!
I just dont understand the war on unlockable bootloaders?! Especially Oneplus... they had the PERFECT system in place. (US models) You had to PHYSICALLY submit a Bootloader Unlock request... Acknowledge that you are aware that you are giving up warranty... wait a week (buyers remorse)... Then if still committed, you have to flash the unlock token. Why go all DICTATOR on us and start moving the devices STILL BRANDED with OnePlus, to a locked down format? Maybe 3 in 10 customers unlock & mod their phones! It takes MORE effort to disable functions and remove them, while at the same time alienating those 3 in 10 thus ensuring LESS SALES!! I fail to understand the logic. I just pray someone always keeps probing these A-hole companies products, for vulnerabilities and exploits that circumvent all their overbearing attempts to control what we can do with OUR devices!
<rant... sorry, this crap just makes my blood boil. cuz i DID demo the 10T at a T-mobile store and they had CPH-2417 models as demo, which were fine. Come to find out that they always planned on only SHIPPING or SELLING these 2419 models to the public!>
Click to expand...
Click to collapse
I saw the writing on the wall after following the 10 Pro forum once I got my OnePlus 9 so I jumped ship to the Pixel 7 Pro. It's not a perfect device but man it's so much smoother than my 9 ever was. The only real complaint I have is the battery takes too long to charge and the fingerprint sensor is more finicky than the one on my OP9 but it's so nice not having lag everywhere and buggy software plus they're easy to root and keep rooted with the PixelFlasher tool.
As for the lockdown, it's probably T-Mobile that wanted it. People always bought the T-Mobile variants because they sell cheaper than the other ones and then they would convert them to global/EU firmware. What we really need is an end to carriers dictating what a phone manufacturer can and can't do with their product but Apple was the only one who ever successfully strong-armed a carrier (all of them basically in the end since they still don't allow bloatware on the phones). That said, Oppo probably doesn't have any complaints about being forced to disable this as it results in less technical support calls for them when people can't muck their devices up anymore. There were a ton of people bricking their OP9 and OP9P devices and those are just the ones that found their way to XDA to try to get help. I bet that a good chunk of their warranty repairs are from people modding their phones. In fact my OP9 almost became one of them until I got stubborn and sat down and figured out how to mod the MSM Tool myself.
Yeah, this is a bummer. Thanks for sharing! I almost never buy through a carrier anymore. My last oneplus was the 8T and it was a t-mobile variant, it was quite the mess to have to get it unlocked due to the person I bought it from not paying their bill...I got it all sorted out....my bad not double checking, but I got it for a sweet deal.
If Samsungs are easier to unlock the bootloader for their new phones, that changes my buying decisions.
I wonder if you could do the local update to the EU or India beta, then do the rollback to android 12 from a different region, India or EU. Does the local update across regions even work if your bootloader is locked?
maamdroid said:
Yeah, this is a bummer. Thanks for sharing! I almost never buy through a carrier anymore. My last oneplus was the 8T and it was a t-mobile variant, it was quite the mess to have to get it unlocked due to the person I bought it from not paying their bill...I got it all sorted out....my bad not double checking, but I got it for a sweet deal.
If Samsungs are easier to unlock the bootloader for their new phones, that changes my buying decisions.
I wonder if you could do the local update to the EU or India beta, then do the rollback to android 12 from a different region, India or EU. Does the local update across regions even work if your bootloader is locked?
Click to expand...
Click to collapse
ok, that i cannot confirm. YET... I screwed up and forgot to disable Auto Updates in the developer menu, and 1 reboot later, put me on the A.11 build for the OS. All the current OTA, and BETA in the Oxygen Updater, are A.10, and ive tried using the local update apk, but it fails stating something along the lines of, "The version you are trying to flash, is older than the current on im on, so to prevent boot problems, we wont allow you to continue"... I know those werent the actual words, but im sure you know what im talking about. So until the India, EU, or NA builds move up to A.11, I am in limbo! ... I have 3 days to request a RMA from Tmobile, if im gonna return it, and if i cannot circumvent this crap then i definitely aint about to get stuck with it for 2 years! Even if its only costing me $13 a month. I just cant accept a device that has actively removed THE VERY THING that i bought a OnePlus to do!
I am HOPING, i get lucky and an update drops, but my luck says it wont.
But to answer your question, YES... I would believe that you can do the Local update and shift sideways to Global or another region. MY plan was to try moving to ANY other region period, which will forcefully change the model number of the device as well... THEN use that regions Rollback Package, cuz it wipes everything and does a complete downgrade to reinstall. My logic is that IF i can update to say the India, or EU Android 13 Beta with the A.11 kernel, then the partitions are gonna change right? so in theory IT SHOULD flash all the CPH2413 or 2415 partitions, and files respectively. Now im sure that alone wont bring back FB because updates dont usually wipe all data! .... BUUUUUT .... once on that Model, then using the Rollback package WILL fully wipe the data and system so that it can format and place the partitions correctly for Android 12! And THAT is where i think my best opportunity to regain Fastboot will come from! Cuz my phone will be formatted as an Unlockable model number, and the rollback packages are supposed to be a Full Stock Rom, so naturally all the partitions and stock components would be installed as well, & the phone wont KNOW it was a 2419 so whatever was done (if only at software level) to disable FB wont be scripted to disable it on the new region.
Again this is only theory, but it sounds logical... unless someone familiar with OPPO can confirm that they use some hardware method of removing fastboot. But so far i have found a couple older OPPO discussions that at least cited exploits that were found in their respectively Locked devices, which they all had leveraged to get FULL ROOT, and subsequently flash different portions of other builds to their device. Personally, If I can have a full Magisk root, I am 100% content with JUST THAT! I lived with MANY a Samsung that had locked bootloaders, but had Root, and i can make that sacrifice!
Hopefully an update drops in time so i can try!
You would need to try the downgrade package.
https://oxygenos.oneplus.net/4248_sign_CPH2415_11_A_OTA_0080_all_44864f_10100111.zip
I would be surprised if it works but it is worth a shot with the APK.
That's the global/US package.
beatbreakee said:
ok, that i cannot confirm. YET... I screwed up and forgot to disable Auto Updates in the developer menu, and 1 reboot later, put me on the A.11 build for the OS. All the current OTA, and BETA in the Oxygen Updater, are A.10, and ive tried using the local update apk, but it fails stating something along the lines of, "The version you are trying to flash, is older than the current on im on, so to prevent boot problems, we wont allow you to continue"... I know those werent the actual words, but im sure you know what im talking about. So until the India, EU, or NA builds move up to A.11, I am in limbo! ... I have 3 days to request a RMA from Tmobile, if im gonna return it, and if i cannot circumvent
Click to expand...
Click to collapse
Yeah, give the beta a try and then rollback.
@beatbreakee Looks like India .12 full update is available in oxygen updater! Hopefully this works for yah.
EtherealRemnant said:
You would need to try the downgrade package.
https://oxygenos.oneplus.net/4248_sign_CPH2415_11_A_OTA_0080_all_44864f_10100111.zip
I would be surprised if it works but it is worth a shot with the APK.
That's the global/US package.
Click to expand...
Click to collapse
Global and US versions are different. That zip is for EU/Global, not US/NA, it says so right in the file name.
CPH2415 is EU/Global
CPH2417 is US/North America
That being said there is actually a member on the forums here that was able to flash that CPH2415 zip on a CPH2417 (US) phone without issue apparently. Flash at your own risk.
Edit:
This information I posted is not completely correct. Check the post after this one for more information regarding the versions.
Jager said:
Global and US versions are different. That zip is for EU/Global, not US/NA, it says so right in the file name.
CPH2415 is EU/Global
CPH2417 is US/North America
That being said there is actually a member on the forums here that was able to flash that CPH2415 zip on a CPH2417 (US) phone without issue apparently. Flash at your own risk.
Click to expand...
Click to collapse
OnePlus is ridiculous. Why the heck did they feel the need to change this? On the 9 series and 10 Pro, xxx0 was China, xxx1 was India, xxx3 was EU, xxx5 was global (which was US), xxx7 was T-Mobile.
Anyway, EU firmware has always worked fine on global variants, no doubt it's the same situation here.
Was about to post this and went to look but ummm... Actually, OnePlus themselves have listed it like this.
Want to go back to Android 12? Download the Rollback package from the links below:
OnePlus 10T (IN)
OnePlus 10T (EU)
OnePlus 10T (GLO)
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
community.oneplus.com
GLO file name is 2415 as well. The one I linked was the same one llinked here, the difference on the EU one is the beginning and end of the file name are different.
EU - https://oxygenos.oneplus.net/4189_sign_CPH2415_11_A_OTA_0080_all_44864f_01000100.zip
GLO - https://oxygenos.oneplus.net/4248_sign_CPH2415_11_A_OTA_0080_all_44864f_10100111.zip
Looks like they're basically the same firmware.
EtherealRemnant said:
OnePlus is ridiculous. Why the heck did they feel the need to change this? On the 9 series and 10 Pro, xxx0 was China, xxx1 was India, xxx3 was EU, xxx5 was global (which was US), xxx7 was T-Mobile.
Anyway, EU firmware has always worked fine on global variants, no doubt it's the same situation here.
Was about to post this and went to look but ummm... Actually, OnePlus themselves have listed it like this.
Want to go back to Android 12? Download the Rollback package from the links below:
OnePlus 10T (IN)
OnePlus 10T (EU)
OnePlus 10T (GLO)
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
community.oneplus.com
GLO file name is 2415 as well. The one I linked was the same one llinked here, the difference on the EU one is the beginning and end of the file name are different.
EU - https://oxygenos.oneplus.net/4189_sign_CPH2415_11_A_OTA_0080_all_44864f_01000100.zip
GLO - https://oxygenos.oneplus.net/4248_sign_CPH2415_11_A_OTA_0080_all_44864f_10100111.zip
Looks like they're basically the same firmware.
Click to expand...
Click to collapse
That's a lot more information than I had. Thank you for sharing! It's been confusing since I got the phone at the start of September coming from the 6T and 5T previously.
Thank you for the links as well, I have always been looking for this information regarding the difference in versions. I will be saving this for reference.
This definitely makes it clearer than what I was trying to explain in my previous post.
I'm one that flashed from Global to India. Then I flashed India to Android 13. Then I did rollback to India 12. And now I did India to EU android 12 .a10.
My bootloader is unlocked though.
I didn't know Global beta is out now. I'll flash to that now!!
So I was just in the 10 Pro section and I would be very cautious trying the downgrade package conversion. There have been a few bricks and a few successes converting T-Mobile to another variant and without an MSM Tool to use, I don't know that I would risk a $650 paperweight.
@beatbreakee This guy has the 2017 version and tried flashing the IN version. There aren't a whole lot of details, but whatever he did caused a softbrick. I posted for a little more details on it, but he might be able to provide some more info around this.
@jmayfield337
Full update from Global to EU?
I'm rooted and bootloader unlocked. There isn't a full update for . 08 yet. Could I use the EU full update and do local install or will that mess my current stuff up?
forum.xda-developers.com
EtherealRemnant said:
You would need to try the downgrade package.
https://oxygenos.oneplus.net/4248_sign_CPH2415_11_A_OTA_0080_all_44864f_10100111.zip
I would be surprised if it works but it is worth a shot with the APK.
That's the global/US package.
Click to expand...
Click to collapse
So sorry for the delay... But yes your rollback package worked in getting me off the T-Mobile 2419 , and now I'm on the 2415. A.08 (yay . KINDA...)
Unfortunately this did not have the intended outcome. I mean yes the phone works properly and all... But I'm sure you knew that fastboot did not come back. (Wouldn't be that easy huh?).
Now, here's the next phase.... After repeatedly beating on OP via their chat, and yelling at person after person, I got one of them to slip up and let a few MINOR things leak verbally.
(Bear with me cuz I might be stating something that might be slightly off from him... I could tell English wasn't his 1st language... Or even 2nd)
"Sir what you are requesting is a file authorization to unlock the bootloader on your device, correct" --- OP
"No, because even if I HAD a special file, I would not be able to flash it, because I have NO fastboot mode accessible on my phone. YOU removed or disabled it yourselves!" ---- Me
"Ok after reviewing your previous words sent, I think I know what it is you seek. There is a program called MSM, do you know of, yes?"-OP
"YES I know exactly of that, and you guys made it password restricted so I cannot log in to get what I need, so is it possible you can refer me to get an access account for the tool?"-Me
"Unfortunately sir that is department not of ours, but I will forward your request to them for email response by 24hrs."-OP
"Ok... So what then, you or them will get back to me with info on how to get an account?" -Me
"Well it yes, sir I do not know if that is how they resolve, or maybe they just give you factory fastboot ROM which can be use with the updater application, for local flash. It is my knowledge that other devices we have sold have had this ROM load special fastboot to allow unlock/lock/flash/wipe commands to be sent from your PC, but it was special tool for devices that not have it already!" - OP ...
BINGO!!
I'll spare you the rest of the chat, but of course no one has contacted me....
SOOO... here's my thoughts...
1. This phone is like Samsung in that there is NOT a permanent bootloader lock, and instead there's just a custom ROM (like the old "Combination FW" that restores permissions for higher level functions aka 'Fastboot ROM"
2. This ROM could TECHNICALLY be created or the fastboot portion extracted from another one that already is out for one of these older devices, and we swap it into one of these rollback packages, cuz I did edit the payload properties file to test if simple changes can be made and it still flash... (Answer : yes... It worked!)
3. One of you GURUs who have found TEMP ROOT access on so many other 'unrootable' devices, discover a way in to these, in which we can access the partition where the bootloader exists, and turn it back on with a hex edit, or flip it to UNLOCKED, then I can use Qfil or an EDL prog to flash custom recovery!?!
The reason I say turn it back on is because I am fairly confident it is still functional, primarily because it shows for a half a second, then reboots back into normal mode if 'adb reboot bootloader' is used. How can it be GONE, If the OS still recognizes it. (This suggests there's a script or init command being triggered once that command is sent, and it forces reboot before fastboot can connect to your PC! ... There is still a splash screen triggered from the command... AND all the updates and rollback packages are using something other than EDL to flash all the partitions as .img files, cuz EDL can't communicate with a device while running, but those packages loaded via local update are prepped while running, and processed only by a reboot, which almost confirms that it's fastboot being used. Fastbootd will not process ANY img files, but it does recognize every reg fastboot command!
(Sorry again for long post but I figured detail is needed to solve this.)
I have 48 hours to completely brick this device and still return it, so I am up for ANY actions that you all might suggest, with no regrets! If I get it AT LEAST rooted, I'll take it! Or if we get fastboot enabled again even better. I will monitor this thread for your replies.
Thanks for all input!
EtherealRemnant said:
So I was just in the 10 Pro section and I would be very cautious trying the downgrade package conversion. There have been a few bricks and a few successes converting T-Mobile to another variant and without an MSM Tool to use, I don't know that I would risk a $650 paperweight.
Click to expand...
Click to collapse
Ok... I KINDA followed part of what they did in the 10pro forums.. opening the zip 1st, I edited 1 line:. "Oplus_update_engine_verify_disable=1" it WAS 0 which I understand had something to do with it verifying something on either the device or in the package to be identical before allowing.
Using a 1 disabled that verification. Now whoever tries this MUST be patient! When you start this via local updater app, you need to be above 40% , AND it will look like it is frozen and not processing at 0% for close to 5 min ... Then it will just start ticking off about 1% every 15-30sec til it gets to 60-70... Then it is about 2 percent per 15 sec... Finally when it hits 99% it will again look like it's stuck, but just wait, cuz it will hit 100% about 3-4 min later.
Whole process went seamlessly smooth! I advise not doing ANYTHING on your device while running. But I successfully went from Android 12.1 A.11 to Android 12.0 A.08 2419 to 2015.
Don't know if it matters but I did enable OEM unlocking in dev options 1st. And it persisted thru the whole wipe/flash process.!
Don't know if this means anything...
Congrats on a successful conversion. Sucks that it's still walled off still but I can't say I'm surprised.
@beatbreakee
Dude I just want to thank you for all you hard work into this.
I have a T-Mobile OP10T and was so disappointed to find out there was no way to unlock bl/no root.
So when i found this thread, there is no hope. Now because of you, there's a chance.
Thanks
I would assume it's best not applying any updates if iv just got the phone? If my plan is somehow getting away from T-Mobile software. Right?