OnePlus just informed me they will NOT unlock bootloader for a device on bought on Ebay.
-
@ChromiumOS-Guy said
@oldbutndy download the EU firmware (EOL) and the real firmware for your version for EOL, then copy the identifers in the scatter xml file from that version to the EU one, then flash through EOL phone will check see T-mobile or whatever it is you have pass the check and flash EU rom with unlockable bootloader worked on my N100
UPDATE:
I ordered another (low price) Oneplus Nord N10 via Ebay (stupid me).
Seller stated 'BE2029', and FACTORY UNLOCKED.
Seller did state phone would NOT read SIM, but I was OK with that. (see below).
I thought that I could at least install UT, and use it for everything but cellular (I read that band 17 NOT on BE2029, and T-Mobile (my spare SIM) requires that).
At least I could get started with UT !
When it arrived today, it flashes T-mobile on boot screen (uh-ohhh...), then in Settings, shows BE2028 !
Very depressing.Anyway, this inspired me to ask for more details on the process you mentioned, of downloading 2 different install files and merging old valid info into the file we want, so it will install even with locked bootloader.
-
@rocket2nfinity said
@oldbutndy The porter is also looking into this. Will update if we figure out why it did not work like the N100.
I did not yet try what ChromiumOS-Guy suggested - downloading 2 files & merge relevant bits from EOL official into newer.
Is your comment saying someone else tried on N10 and it failed (whereas it worked for N100 ?)
If you know this process, please explain or send relevant link. I will try. -
@oldbutndy Yes, someone else tried on the N10 and although they successfully converted to Global, they still required a token to unlock. Not sure if they skipped/changed something in the instructions and that's why it didn't work, or it just didn't work. The instructions are in the N100 forum. Also posted here in a post I replied to above.
Try it, and confirm for us whether it works like the N100 patch does, or token is still required. Join us on Telegram and we can walk you through it.
-
@rocket2nfinity said
@oldbutndy . The instructions are in the N100 forum. Also posted here in a post I replied to above.
Thank you. I found the post above and read through, then realized I HAD read it in the last few weeks. I have been reading everything I could find on the subject of converting N10 to UT for weeks, to the point of exhaustion.
In any case, he still (if I read the proper lengthy message) had to ask 1+ for the token. Which I failed at. -
@oldbutndy Also read the instructions in the N100 thread. It goes into detail on what you need to copy over in the files - don't just copy the files without modifying them. That's the part that may have gone wrong. If done correctly, you are not supposed to need a token. It could also be it was done correctly, and OnePlus just changed things with the N10. We will not know until others try it.
-
@rocket2nfinity said
@oldbutndy Also read the instructions in the N100 thread.
I have been reading and re-reading those instructions for past while. Not sure I am reading the correct ones.
One that had some details, by Dugen & Joko is: Oneplus Nord N100 MetroPCS (BE2015) Install Success.
I this the best one to refer to ? -
@oldbutndy yes. Just adjust for N10
-
@rocket2nfinity said
@oldbutndy yes. Just adjust for N10
I downloaded the OxygenOS global 10.5.7 zip.
This BE2028 shows software version as 11.0.15BE88CB.
Where do I download this version zip file to extract the relevant info from ?
Or do you recommend some method of pulling it from phone ?
Also, use bkerler oppo_decrypt from github to extract the settings.xml ? -
https://forums.ubports.com/post/83968
https://forums.ubports.com/topic/10341/how-to-downgrade-nord-n10-t-mobile/24#
Yes, on the decrypt. You need to unpackage the files, swap the required info, repackage with oppodecrypt and flash with msmDownloadtool
-
@oldbutndy When I think about it, you might want to try using the T-mobile 10.5.7 package from xda-developers or directly from OnePlus and the global 10.5.7 from Ruben. The mismatch in version numbers could be why it did not work for the others.
Then swap the relevant info as per instructions of course.
-
@rocket2nfinity OK. I will look for those. I copied the detailed posts into 2 files to edit steps into numbered checklists, and merge & highlight important details. Trying to ensure I don't leave out a critical step. hopefully simplify troubleshooting failure. Or, if lucky/successful, repeat the process.