Related
Hi there,
About 36 hours ago, I received my Xiaomi mi5 and I already am at the point where I want to throw it out the window and hope it will explode in 3 billions of pieces and so be unrecoverable for anyone !
My device came with the Chinese/english version of MIUI. More precisely, it's MIUI 8.07 that I have upgraded to MIUI 8.0.10.
But I would like to go to Global ROM in order to :
- have the phone in French ;
- hate the correct Google Apps installed ;
- possibly bypass some of the MIUI horrible limitations ;
- in the future, be able to unlock my device easily (if the unlock Code arrives one day ! Can't understand their stupid unlocking verifying process !).
My questions are really simple :
- is it possible to go from MIUI China Stable 8.0.10 to MIUI Global (Stable or Dev) with a locked BL ?
- if it is possible, how can I do that ?
Of course, I assumed it is possible. So I tried several methods :
- 1°) using the "Updater" app as given in the "Flash guide" provided on the official Xiaomi site where you can download several ROM for the mi5. I only get a message : "Could not verify file"... and so, that does not work.
- 2°) using the Mi PC Suite found on Xiaomi's own website. It's installed on a PC running Windows 10. If I hook up my mi5 to that PC, I can see the device, navigate in the internal storage and transfer files between the device and the PC. But the Mi PC Suite doesn't detect the device... If the device is in "Recovery mode" (with the Boby and cable on display), it seems to be detected, but it says : "MIUI 8.0.10 is installed. No need to upgrade"... Cool. So I tried to boot the phone into Fastboot. It is then detected but I get the message : "Try to run in normal mode before using this method"... Even nicer !
- 3°) so I tried the chinese Mi PC Suite. OK. There I do things blindly, but at least it seems to ask me what ROM I would like to flash... So I select the file (the original one downloaded from Xiaomi's website !). And obviously he doesn't want it... But can't tell for sure as it's all written in chinese
- 4°) Tried the MiFlash tool. No go. It simply doesn't detect my device at all
- 5°) of course tried to boot into fastboot... but then it says "UNlock device first".
So if anyone could answer those simple questions... And of course, giving an answer that applies to MIUI 8, because it seems that MIUI 8 is kind of... well, even worse than Apple iOS as a fortress !
Waiting for your replies....
Regards.
Hi,
Replying to myself.
Consider I did not asked. Looking at the MIUI download page, it's stated, in almost invisible caracters, that you first need to unlock your bootloader.
So, this answer the questions and solves the problem => I applied. Reports are : 2 days to over 3 weeks to get the unlock code.
Until then I am here with an almost unusable phone...
So it's already on an ad site to be sold and replaced with something else.
Regards.
NexusPenguin said:
Hi,
Replying to myself.
Consider I did not asked. Looking at the MIUI download page, it's stated, in almost invisible caracters, that you first need to unlock your bootloader.
So, this answer the questions and solves the problem => I applied. Reports are : 2 days to over 3 weeks to get the unlock code.
Until then I am here with an almost unusable phone...
So it's already on an ad site to be sold and replaced with something else.
Regards.
Click to expand...
Click to collapse
Hi Nexus, I´m in the SAME situation as you. Actually I am really disapointed with Xiaomi reason to lock bootloaders, I honestly don´t understand that. Why you need to ask permision to do whatever you want with something you bought... Looks like we bought an Iphone.
The tutorials that are flying around are not working for all devices, hardware speaking might difer a lot one to each other. I tryied everything but looks like we need to wait to get the famous code to "play" with our device. Till then we will need to wait to use our porche running with poliester seats and get used to the chinise notifications from the video app which wakes you in the middle of the night. And of course you cannot uninstall it :cyclops:
I really miss my Nexus 4...
Klyne said:
Hi Nexus, I´m in the SAME situation as you. Actually I am really disapointed with Xiaomi reason to lock bootloaders, I honestly don´t understand that. Why you need to ask permision to do whatever you want with something you bought... Looks like we bought an Iphone.
The tutorials that are flying around are not working for all devices, hardware speaking might difer a lot one to each other. I tryied everything but looks like we need to wait to get the famous code to "play" with our device. Till then we will need to wait to use our porche running with poliester seats and get used to the chinise notifications from the video app which wakes you in the middle of the night. And of course you cannot uninstall it :cyclops:
I really miss my Nexus 4...
Click to expand...
Click to collapse
Hi Klyne,
I have been fortunate enough to have a friend giving me his credentials on Xiaomi Unlock so I could unlock the device...
I Installed TWRP 3.0.2.0 as it seems the 3.0.2.1 is not working...
I will now flash Slim or Resurrection Remix...
Finally something usable !!!
I wish you luck and will tell you if the wait is worth it !
Regards.
NexusPenguin said:
Hi Klyne,
I have been fortunate enough to have a friend giving me his credentials on Xiaomi Unlock so I could unlock the device...
I Installed TWRP 3.0.2.0 as it seems the 3.0.2.1 is not working...
I will now flash Slim or Resurrection Remix...
Finally something usable !!!
I wish you luck and will tell you if the wait is worth it !
Regards.
Click to expand...
Click to collapse
Lucky man
I will wait one week more. At least right now I don´t have a fake ROM.
Enjoy!!
Hi,
yes, the phone runs... But MIUI has some flaws that irritate me so much !
The first one : no GApps and it took some time to figure out what to do to have it working ;
The second one : once GApps installed, nightmare to change default launcher ;
The third one : the one in the thread ! ;
The last one (that spilled it all over) : contacts management : the MIUI App just loads ALL people you have sent a mail to or received a mail from... So when I was looking for a contact to make a phone call, I had to sort 3750 people instead of just my 150/200 usual contacts !
Installing Resurrection Remix and OpenGApps at the moment.
Regards.
Hey guys I've run into an issuei bought a Mi 8 off swappa two weeks ago I've been using it and it's been absolutely amazing I love it but a few days ago global miui 9 came out and they phone came bootloader unlocked so I figured I'd flash the firmware and then lock the bootloader I flashed the firmware through Miuitool it worked fine I set it up and then went to lock the bootloader using the same tool I did it and then it started to boot but detected no os anymore so it was bootlooping. I can only access the recovery and fastboot mode I tried wiping didn't work I tried flash the firmware using miflash tool and manually doing the commands also tried getting into edl mode but says it's locked. I tried calling support but they told me they didn't do phone repairs and to call the manufacturer of which I bought it from (swappa) I'm kinda losing hope I'm not sure what to do I've tried so much maybe I'm missing something. If anyone has any suggestions I would love that thanks and here's what my recovery says if that helps
Did you try to flash twrp with fastboot and then from twrp flash the new rom?
xristos9 said:
Did you try to flash twrp with fastboot and then from twrp flash the new rom?
Click to expand...
Click to collapse
I did not but I doubt I could because the bootloader is locked
Had you try flashing it with Deep Flash Cable?
http://en.miui.com/thread-1597002-1-1.html
Mi 8 Fastboot ROM can be downloaded here:
https://forum.xda-developers.com/mi-8/development/firmware-global-china-stock-firmware-t3818194
Disclaimer: I had not tested this method but shared from the internet. The IP of the method is from the link shared above and I hold no responsibility in any event it cause damage to your phone.
To resurrect the phone, you will need a MI account with authorized access to the EDL. Look at the topic of Redmi 5 as they resurrect bricks. On our forum, several MI 8 & MI 8 SE have already been resurrected in this way.
Instructions (RU)
dogsly said:
To resurrect the phone, you will need a MI account with authorized access to the EDL. Look at the topic of Redmi 5 as they resurrect bricks. On our forum, several MI 8 & MI 8 SE have already been resurrected in this way.
Instructions (RU)
Click to expand...
Click to collapse
I can not register in your forum, could you give us the contact of the people taht can give us account EDL permissions?
BR
thanks for the suggestions guys I was thinking before getting super technical opening up my phone and modding a cable to let you guys know of an update. Last night I stayed up a while i found adb flash tool for recovery mode to flash back to official software (http://www.xiaomitool.com/adb) I downloaded both global and both china otas of stable and beta. First i flashed global successfully but forgot that going from china to global requires unlock boot loader to boot up so it did not boot next I tried china stable but the file is an older version and did not flash since it was "downgrading" and last I tried china beta which was newer in theory but did not flash since it was not stable. So i am going to wait for a new china stable rom to come out whenever it does because in theory it will flash correctly and completely fix the phone because its china miui thats newer than the one global version now i can only wonder if it can flash because i will be going from global to china but again I will let you guys know when i attempt it, I understand I will be waiting a while for a stable version those dont come often but in the meantime i can focus on other things and thankfully i have multiple back up phones. thanks guys
StarwarsMissionary said:
I tried china stable but the file is an older version and did not flash since it was "downgrading"
Click to expand...
Click to collapse
Theoretically and my previous experience with Nexus phone, older version of official ROM should be fine as it should get OTA to latest version. So, I think it is worth a try.
At the same time, I'm still patiently waiting for my 1st Mi 8 to arrive at door step.
ZhenMing said:
Theoretically and my previous experience with Nexus phone, older version of official ROM should be fine as it should get OTA to latest version. So, I think it is worth a try.
At the same time, I'm still patiently waiting for my 1st Mi 8 to arrive at door step.
Click to expand...
Click to collapse
I agree with you and I used to own a nexus too so I understand what your saying but I tried flashing miui 9 china stable and the error said it was an older version and it was "illegal to downgrade" which is weird so I'll just wait for an updated version which might take a while
Never lock a boatloader with aftermarket global on a China Xiaomi.
I think because of the flashing the bootloader is locked again, maybe try to unlock it with miui unlock.
Maby Xiaomi enable the anti roll back also for the Mi 8 after they did it to the Xiaomi redmi note 5 whyred? Many people have ended up with bricked phones.
Edit
Same problem solution is unlock boatloader
https://xiaomi.eu/community/threads/mi-8-safetynet-android-pay-and-related-issues.45286/
I faced the same problem with my Mi 8 when I locked the bootloader after installing Global ROM. Simply put your phone in Fastboot, and again Unlock the Bootloader using Xiaomi official Unlock tool. Once bootloader was unlocked, phone booted normally with Global ROM.
Hello, I have blocked bootloader and now I am with the bootloader loop.
I've tried to unlock again from console and from the Xiaomi tool, but it has not been possible. The tool says that the device is not associated. Any solution to this?
I have also tried from Recovery (With MiFlash) to put the stable Chinese version, but having a higher version installed does not leave me.
If I re-flash the same version, it completes it but when restarting, the loop returns.
Any solution?
Hi I have the same problem but now I have a new and BIG new problem...
When I try to unlock the bootloader with my account the software said me that my account is not bounded in this device... cry cry cry!!!
Somebody knows if it is normal and if I will fixed?
BR
The mi unlock tool problems are mainly because of either it's not verified with your account or because before it bricked you forgot to go to development settings and add your phone for unlock which I forgot to so whenever I try to unlock it again it says it isn't verified because I'm a moron and forgot to add my Mi8 to my account in case something like this happened, now I gotta wait for a stable newer miui 9 China version to flash from the adb software
Any news on how to solve the brick?
The perfect solution would be to have access to an account with EDL permissions to re-unlock the bootloader.
Enviado desde mi SM-G930F mediante Tapatalk
StarwarsMissionary said:
The mi unlock tool problems are mainly because of either it's not verified with your account or because before it bricked you forgot to go to development settings and add your phone for unlock which I forgot to so whenever I try to unlock it again it says it isn't verified because I'm a moron and forgot to add my Mi8 to my account in case something like this happened, now I gotta wait for a stable newer miui 9 China version to flash from the adb software
Click to expand...
Click to collapse
When you have any update on this, please let me know I have the same issue and did same mistake.
Let me know if you were able to un-brick it.
Looking fwd to see an update from you.
This. Is. F****d. Up. Someone needs to say it. They do totally crazy things and we saw too many bricks coming from their unexplained tinkering with ARB and locking. Additionally, their each new flagship gets always one step closer to the prices of better competition. We are getting too screwed and we desperately need a new, reasonably priced and logical brand. Nokia? Wouldn't say so. Essential? US only and seems to close down. OnePlus? Getting costlier. Google? Got really costly. **** happened. Really, sorry for OT, but my empathy and sociological thinking just hurts me when I see this.
j1505243 said:
This. Is. F****d. Up. Someone needs to say it. They do totally crazy things and we saw too many bricks coming from their unexplained tinkering with ARB and locking. Additionally, their each new flagship gets always one step closer to the prices of better competition. We are getting too screwed and we desperately need a new, reasonably priced and logical brand. Nokia? Wouldn't say so. Essential? US only and seems to close down. OnePlus? Getting costlier. Google? Got really costly. **** happened. Really, sorry for OT, but my empathy and sociological thinking just hurts me when I see this.
Click to expand...
Click to collapse
Yeah, I thought I was the only one thinking like this.
Companies want as much money as possible. Oneplus is increasing prices not because the components cost more but because they waste money on ads and want more profit. And they pull it off because people will still buy their phones.
Honestly, the Mi 8 is a " flagship killer-killer",it provides almost the same stuff as the OP6 for less money but people either never heard of Xiaomi or are hesitant when it comes to buying their phones ( I don't understand why, though ) .
As for their phones dying, I only saw bricks from people who tried tinkering with deep level stuff without actually knowing what they were playing with.
They don't suddenly die/lose basic functions out of the blue like e.g. Moto phones and I don't know of a single device which beats them at this price along with what you get in a phone.
The Marionette said:
I only saw bricks from people who tried tinkering with deep level stuff without actually knowing what they were playing with.
Click to expand...
Click to collapse
Just let me tell that you can do the **** even actually knowing what you are playing with. You just need to forget to change the "clean all and lock" option which comes selected by default. And believe me, it's not that difficult at 3 a.m. after some successful flashes.
I think it's not necessary to dive into the hurt, you know.
Cheers
descarao81 said:
Just let me tell that you can do the **** even actually knowing what you are playing with. You just need to forget to change the "clean all and lock" option which comes selected by default. And believe me, it's not that difficult at 3 a.m. after some successful flashes.
I think it's not necessary to dive into the hurt, you know.
Cheers
Click to expand...
Click to collapse
There is a need for that. This is an expensive toy and you shouldn't be playing with it if you are not 100% that you can undo the thing you will do if it goes wrong ( you are free to do it but then at least try to find a solution yourself ) .
After seeing posts which are pretty much like " uwu I made a f*cking boo boo, a weal f*cky wucky, pweese help me guys ;((((( " ( which could've been avoided by following some logic or by actually investigating before flashing stuff ) , it's high time people who are thinking about unlocking the bootloader actually see what they might be getting into if they "touch wrong things in the wrong way".
Today I got up real pissed with Samsung for being so restrictive around ROM flashing, rooting, flashing custom firmware or even stock firmware, so wanted to create this post to help anybody considering to get a Samsung phone to stay away from it.
This post is not intended to recommend any specific brand or model of android phone, but to recommend the exact opposite, which brand and model NOT TO EVEN THINK of purchasing.
This post relates to Samsung Galaxy S9 G9600 model which is Snapdragon architecture, but since Samsung is coming up with a bunch of "security features" I tend to think this may be the case for other models as well. I browsed all around XDA and other sources for guides on how to root and install custom roms, and it turns out Samsung manages to have limitations for EVERY step of the way.
Getting a few facts straight
Reference post: https://forum.xda-developers.com/ga.../rom-lineageos-17-1-s9-s9-snapdragon-t4093301
Ok, so there is a solid thread about a custom firmware and looks like several users got hands on it, but they might have been able to get passed though all Samsung security crap before it came out or before it got so tightened up. I'll list below every limitation I found:
OEM Unlock
There is a step where we need to tick OEM Unlock from the phone developer settings, it turns out Samsung has put a 7-day timer for this option to even appear listed to enable. If you do factory reset of the phone, the 7-day timer restarts. There are a few posts around on how to get passed this timer, but to me they were all crap, none of them worked. STRIKE ONE!
Bootloader unlock
After 7-days, we get the OEM Unlock option to appear, at this point you may think: Hurray!! .... WRONG! Now next step is to unlock the bootloader using an utility called CROM Services... And as you may have already guessed, did not work! I'm able to install the apk, but on launch it complains about wrong android version. (Tried with Android 8 and 10) STRIKE TWO!
There are some posts and guides claiming to be able to unlock bootloader by using fastboot utility, I can't reach to understand how, since fastboot commands rely on the bootloader to be previously unlocked (?). I least that is my understanding, correct me if wrong. Needless to say fastboot did not work for me. ADB lists my device but fastboot doesn't. There are a few troubleshoot guides around to try selecting proper USB driver from windows device manager, tried all that, tried a couple of ADB installations, fastboot didn't work.
Knox and RMM state
After some lookup in the web, Samsung incorporates some security features trying to prevent device theft and such things. For us power users this is in reality just a whole load of crap preventing us to get all the juice out of our phones.
Reference: https://www.goandroid.co.in/unlock-bootloader-of-galaxy-s9-plus-snapdragon/84688/
TWRP Recovery
Next step would be to flash a custom recovery such as TWRP with Odin or adb/fastboot, but since we are not able to unlock the bootloader in previous step, this is not doable at all. STRIKE THREE! OUT!
Fastboot utility doesn't recognize the device in download mode, so we can't send any commands to the phone.
Odin complains it is only able to flash signed stock roms, so since TWRP is not, we cannot flash it.
Rooting
Needless to say that if we don't have TWRP, we cannot flash the corresponding packages to root. Although this step may not be needed to install custom firmware, rooting has not been possible.
Stock ROM Flashing
Ok, so let's stay out of custom firmware - let's play around with stock firmwares. At this point, since flashing stock firmwares is kind of allowed by Samsung I was able to try out a couple from android 8 to 10 with Odin
Stock ROM Source: https://www.sammobile.com/samsung/galaxy-s9/firmware/#SM-G9600
But watch out! Once you get to install a specific build version, you cannot go back or downgrade to ROMS with previous Android build version. So now that I got Android 10 cannot go back to 8 or 9, this is probably because locked bootloader and unable to unlock. Here, Odin complains with FAIL! (AUTH) message.
STRIKE FOUR! EVEN OUTTER!
SIM Unlock
Ok, let's stay out of Samsung S9 G9600 model, let's crash it to the wall and throw it away to the garbage! Ok no, let's have it carrier unlocked and sell. Unlockbase is a well known and trusted sim unlock provider, I purchased a license to unlock by USB cable, but... GUESS WHAT! G9600 is not supported for unlocking operator network with this software... what a surprise!! I was able to apply for a refund and got my money back, so no worries here.
Note that flashing carrier free ROM does not unlock sim to use with any network operator.
I'll be trying to unlocking by code soon, as this is based on IMEI number, I may think this is independent to the phone model and edition, so I hope I have more luck with this option.
Conclusion
G9600 is a really crappy phone to mess around with. I may have ran low on luck with this specific Samsung Galaxy model since I got it as a gift, which is the latinamerican crappy edition. I wonder if other S9 editions and other Samsung models run with better luck than mine on this scenery... But as a lesson to myself, I will stay away of any Samsung smartphone in the foreseeable future.
OEM Unlock
The 7-day lock prevents stolen phones from being factory reset, leaving the thief with a phone permanently protected by your account. While a minor inconvenience, it's actually effective and not the worst compared to other manufacturers.
Bootloader Unlock
After OEM Unlocking, flashing TWRP through ODIN is effectively unlocking the bootloader. This is possible on both exynos and snap.
Knox and RMM
While this is an inconvenience, from Samsung's point of view, it's worth it. It makes the phone look more secure in the eyes of potential customers. If you really wish for NFC payments, I'm still able to use GPay with Magisk on a custom ROM.
TWRP Recovery
TWRP is flashed through ODIN, not fastboot. Look up an actual guide before complaining.
Root
Yes you can
Stock ROM Flashing
The one thing I could agree on with you is Samsung disabling OTA updates when OEM unlocking. I don't see the point really, but you're free to flash whatever you want through ODIN. Downgrading shouldn't be an issue. Not sure what's up with that.
Before buying a phone, how about you do some research before crying on forums. As a power user coming from the Oneplus One, I don't regret going for Samsung in the least.
Thanks for your reply, I had dropped all hope after several attempts over last few weeks. Found this option and I was able to get past my blocking issue with TWRP and moved on.
https://forum.xda-developers.com/ga...er-development/g9650zhu6dta7-android-t4051751
I have G960F and have to admit I totally disagree with your original post. I've been using custom ROMs on nearly every phone I ever had and don't think S9 (G960F) is bad in terms of unlocking. Just did an OEM unlock, waited a week, flashed TWRP through Odin, booted straight to TWRP and immediately flashed a custom ROM from it (because a boot to the stock ROM would replace TWRP back with the stock recovery IIRC). In the end I got sick of all the problems with Magisk and non-working google pay that I went back to the stock ROM - making S9 the first phone I use with a stock ROM even though it can be flashed. I think it's a great phone for power users.
And as far as SIM unlock goes - Samsung is not to blame, the carrier the phone was made for (and purchased from) is. Phones that Samsung itself sells are unlocked. I wonder why there's still some countries where SIM locking remains legal.
This thread is a prime example of how people end up with bricked devices. So much misinformation in one page LOL
I had the 9650 and most of what I'm doing here is user error. This was one of the best devices I've ever owned. I mention of fast boot and such you obviously just do not know samsung devices. You can't blame samsung on your own ignorance
Yeah, it's kind of a stupid question but I really need help to understand some things before doing anything and turning my phone into a paperweight. It's my first thread so I really hope you can help me with it
I'm from colombia btw.
Have to advice that english is not my first language so if you see any grammatical error it's probably that.
So; I've been investigating why my phone is still waiting for the miui 12.0.7.0 update since it's been stuck on miui 11.0.9.0 since a while, tried installing Every possible rom of the official site and that didn't worked. So I started to investigate and found that my phone has a custom rom installed by the business that selled me the phone; and that rom won't be updated anymore since that business is really lazy with that type of updates (I had phones by them in the past that just didn't updated at all since all the time I had them).
And now I'm wanting to change that rom to the official one (The Global One).
I've already started the bootloader unlock and I'm waiting right now for the 168 hours to be able to unlock it, but I've got some questions that i really need to get answered before I can start doing anything.
So let's start with this, ok?
Right, so my first doubt comes about the roms. Right now my phone has a Custom Rom made by "Claro" (also known as telcel on latam) and that custom rom is literally locking any update that comes from the global xiaomi updater; and it wouldn't be that bad if the phone wouldn't reset with A LOT of preinstalled apps and a custom logo for the startup that lags the phone even when starting up.
I would be able to change that custom rom from my phone into the official one without many complications?, I've been looking for some programs and it seems that Xiaomi Flash Tool and XiaoMiTool_V2 were some of my options (for not saying the only ones), and I would like to know your opinion about them and what of those two would you recommend me.
Both of the roms (the official one and the custom one) are "Global" so i would like to know if that would affect (or improve) anything at all.
My second doubt comes mostly on the unlocked bootloader, since what I had readed about it can actually block you from opening apps (like Netflix) and I wanted to know if it could be possible to lock it again since i'm installing the global one.
Have to clarify that it is a Redmi Note 9 with 128GB ROM and 4GB RAM, it's almost new (has like 2 weeks or so) and is currently running MIUI 11.0.9.0.
if you need anymore info or pictures I would be glad to give it to you if you can help me with my doubts.
Certainly, unlocking the bootloader is your best chance.
Unlock it first and then, flash the any other rom you want.
If you want, you can relock the bootloader again too.
!!! This is a HIGH RISK method of performing any form of modification, if you are on a T-Mobile ne2217 !!!
There are unidentified files that your device might have conflict with, and cause a bootloop!
Proceed at your own risk! You have been warned!
OK, first lemme explain. The NE2217 (10 pro) itself does not have any special restrictions on it, unlike the CPH 2419 (10T) which is an exclusive T-Mobile variant. My guide on region swapping the CPH2419 (10T, link below) is still valid for the NE2217 (US- NA) . But there are conditions required or you will enter an infinite bootloop which becomes un-recoverable, without an edl flash. I do not have the specifics as to exactly which partitions cause this, but basically the bottom line is, IF YOU HAVE NOT UNLOCKED YOUR BOOTLOADER, EVEN IF YOU ARE SIM UNLOCKED, do not attempt to region swap.
There are a couple of partitions that are specially locked, that ONLY become write capable using the fastboot command, "Unlock Critical". Without a Bootloader unlock, the Oxygen Updater/Local Update programs, CANNOT make the needed changes to the Kernel, as well as these other important partitions, which have instructions that implicitly block changing to other regions. I cannot confirm if this exists in other countries with carrier locks, but i do know for a fact that T-Mobile has this enforced on all of the 10 Pro (ne2217) purchased through them.
As mentioned in previous threads that ive replied in, I suspected that the apps Oxygen Updater and Local Update, do not have the permissions capable to make direct changes to the boot.img, or recovery.img directly, primarily because those partitons cannot be altered while the system is currently running. These images can only be altered through Fastboot, or EDL thus the need for an MSM Tool if you cannot unlock your bootloader via conventional methods. So what happens is upon "Pre-boot" those special instructions i spoke of, take authority and put the carrier specific files, into an untouchable state that are locked behind the USERDATA partition, so these applications just copy the updated files to the inactive partition and performs the changes during the next boot, and even a hard wipe factory reset does not have the authority to erase the carrier instructions. The only way they are removed is by Unlocking your Bootloader! When you do that, the Qualcomm Processor has an embedded command, which is required to ERASE the entire Userdata partition, to protect the encrypted files protected by the bootloader lock! You can read about that by googling "Qualcomm Bootloader Unlocking".
Hope that makes sense to the majority of you. So again, the ONLY requirement for you to be able to go from 'ne2217', to any other fw is YOUR BOOTLOADER MUST BE UNLOCKED!
Failure to follow that one requirement will indeed force your device into an unusable, infinite bootloop, which can be resolved only by an EDL flash, which as of right now we do not have the tools that can perform this on CONSUMER level. You will have to RMA, your device, or go thru third party channels, which in itself is very risky, and puts you at risk of viruses/malware/wormholes/zombie-apocalypse because you must give someone full access to your computer remotely, and pray that the person only does what you requested. (NOT IDEAL).
Now if you're on a T-Mobile locked device, you are NOT hopeless... as I am on a T-Mobile locked device, and i am now bootloader unlocked as well! These two conditions are independent of each other, but trust me when i tell you that YOU DO NOT WANT TO GO THRU WHAT I HAVE EXPERIENCED, IN ORDER TO REACH THIS GOAL!
In so I will not publicly disclose how i was able to enter the real Fastboot Mode, so that i could pull the unlock code needed to request the unlock token from T-mobile.
(If you are so inclined to do this that you are willing to forgo ALL precautions and risk the possibility of bricking your device, or you have already landed yourself in an unrecoverable bootloop state, and are willing to try ANYTHING, you can join Bootloopers Anonymous, by clickiing it, and drop a message. This is a brand new telegram channel, and i will try to watch it for your requests. And again i strongly advise that you DO NOT embark on MY adventure, but if Unlocked Bootloader by Any Means Necessary is your ultimate goal, and nothing less is acceptable, i will try to help you achieve it... *** YOUR DEVICE WILL ENTER A COMPLETELY UNUSABLE STATE FOR A MINIMUM OF 7 DAYS!! *** but bear in mind that EVEN IF you have to use my method, you will be still subject to the 7-day waiting period outlined by OnePlus company policy. No one can overcome that, as the unlock token comes thru a separate division of Oppo/Oneplus that only generates the token through an automated request which is pushed after the expiration of 7 full days (1-week) has passed. YOU HAVE BEEN WARNED!)
The 10-Pro doesn't require the "In-Depth Testing" app to get your BL unlocked. That said, it also does not mean that OPPO has not designed one for this device because indeed they have. That application is individually encoded with device specifications so that only devices and regions EXPRESSLY AUTHORIZED by Oppo, can submit a request to unlock. DO NOT TRY sideloading any "In Depth Testing" apk floating around on the internet, as these can be altered to contain malware or worse, and then if your device becomes corrupted by it, Oppo can deny you an RMA on your device, thus charging you for the repair as there are warnings that you must acknowledge to even run the app, and attempting to circumvent the safeguards that this app already has in place is considered a violation of ToS.
If OPPO adds your device/region to the list of allowed devices, you will be able to download this application through OFFICIAL channels, and it will be made known to the public.
Once you are completely knowledgeable that your BL has indeed been fully unlocked, you can proceed to follow the instructions in the link to my guide below. The guide is for the CPH2419 (10T), but the instructions are completely compatible with the 10 Pro entire series, assuming your BL is unlocked. On the 10T this is not a requirement, and i honestly do not understand why this enforcement was put into our 10 Pro model, released almost a year earlier. Probably just an oversight by T-Mobile which might be corrected in future builds.
How to use Oxygen Updater + Local Update apks to switch regions.
EDIT: Local Update downgrade it currently installing
No Go, The update installed and downgraded but it just loads to the welcome screen and crashes and boot loops
supercobaltss said:
EDIT: Local Update downgrade it currently installing
No Go, The update installed and downgraded but it just loads to the welcome screen and crashes and boot loops
Click to expand...
Click to collapse
again, what most ppl are failing to do is follow my guide exactly as i defined. The VERY 1st thing you MUST DO... prior to unlocking the Bootloader... Prior to even downloading ANY rollback packages is, you MUST go and Download ANY of the Android 13 beta updates that are available in Oxygen updater. Turn on advanced mode, and select the whichever model you prefer... Its actually best to choose the region you plan on swapping to, for easier transition with the rollback package. IMHO i would always pick the EU model whenever attempting this, simply because that one usually has more bands available. But the main idea behind this is to make the phone, first BREAK the connection it has with T-Mobile's custom kernel, and modem... which is done just by upgrading to an Android 13 beta, as T-Mobile does not EVER release any beta builds, so by doing an actual OS upgrade, your phone must load the OS kernel, and several other partitions/files which i am sure that T-Mobile has branded in the 2217. Upgrading to a newer OS will without a doubt overwrite the carrier locked files, because the Upgrade comes from a higher authority in the chain of trust. Until TMO releases an update, then this is a requirement so that the rollback package of that region can safely downgrade the files, in their correct partitions. If you download a beta 13 thru oxygen updater, you can local update flash it, without problem. I did it myself to several demo devices at Tmobile stores here in Texas to test the technique, after i bricked mine by using a rollback package first!
Remember the 2217 is a T-Mobile EXCLUSIVE! No other carrier may sell this same model... but ALL of the internals are the exact same, and as im sure we are all well aware of, T-Mobile doesnt have the fastest adaptations when it comes to OS updates.
But there are several key identifiers which point to a custom made BL, Kernel, and Modem: 1. The build for all T-Mobile versions is on a revision that no other model has released... This alone could cause BL because if you flash a build that is older than the one you have currently, several files have anti-downgrade measures built into them. This is why we need the signed rollback packages to downgrade. But even if OPPO signed a rollback, unless they released one with T-Mobiles file specs, then anything you flash can create a conflict with an existing file... BL! But i know of about 13 ppl who have attempted my method, plus i just did another one myself last night for someone who contacted me and offered to compensate me royally if i would meet them since we were local logistically. 2. AFAIK, when installing a different rom to a device, you cannot downgrade the modem version. I know this is apparent with Samsung... as if you try to flash a rom with a lower modem version, it usually bricks, and you have to use odin to flash the newer modem back, in order to boot. Again this is taken care of by installing the NEWEST beta for Android 13, unless you had my situation which is, my phone CAME WITH updated security, and build already installed for October 2022. I havent heard of anyone who has said they even have the option to update theirs past August. So new purchases have to be careful. T-mobile sold mine with a blocked Fastboot, that doesnt respond to the button combo. Which clearly identifies they modified the recovery partition. 3. E-fuses have become a staple in Android devices for the past 5+ years.
Sure we have not heard of anything being in the T-mobile fw... but also who here can say that they have a FULL BUILD of the Tmo fw to examine? No one.... there is a generic 2217 build floating around that claims to be official, yet it is the ONLY build that does not have an OTA formatted file structure. All the 10 Pro OTA have been in payload.bin format, yet this happens to come only as a decrypted OFP, or a compressed OFP. *** OPPO is not directly supporting the 10 Pro 2217 or 10 T 2419 ! As these are proprietary T-Mobile builds. This is why you cannot find either of those models fw in the Oppo repository. So if OPPO doesnt release builds for TMO, then how exactly did an "Official 'OFP' for 2217" get released? *** OFP is an Official OPPO format for all the OPPO model phones. 10 Pro is still branded Oneplus, thus just about any OFP file you find in the wild, is almost 100% guaranteed NOT to be an official released build for our phones. Every package for this and the 10T that they have OFFICIALLY released, has been in Payload.bin format, because they havent released any full images yet! So in theory, who's to say that TMO didnt place an efuse into their specific model? Its only code, and if set, then it could have been burned during the initial release, or a later update, like AMAZON did with updates to the Firestick/FireTV devices, which would ONLY allow newer updates to certain files in THEIR build. That would totally explain a bootloop, because the rollback packages all push you back to 11_A.013 .... that build is from Feb-March 2022. Rolling back would almost guarantee that some files are overwritten with older components, which would cause a brick by e-fuse standards. We had to be lucky enough to catch it early in the FIrestick forum, to stop ppl from installing the update. Everyone who did, had their ability to unlock/load custom fw to their devices blocked, and there is still today no way to circumvent it. Sure new methods to mod became available, but only minimal changes, cuz the e-fuse blocked downgrading to exploitable builds. Since TMO has gone this far to stop us from modifying this phone, you can bet solidly on the fact that they have several safeguards in place to protect their investment.
Now im not trying to discourage anyone or discredit anything anyone has said or experienced regarding this phone, but look at the NUMEROUS unanswered replies to handfuls of problems that only happen to 1 or 2 ppl... they all have the same final result, but its astounding how many different scenarios ppl have found, that no one else has experienced, yet it leads to another bricked device. If this problem was rampant among a significant number of users, and it was triggered by the exact same scenario, then TMO would have to address it with an update... But all we know for sure is that there is some file(s) that is not compatible with any other model except the 2217. Til we have an EXACT culprit identified, all we can do is speculate, which is why I am going to re-label this as HIGH RISK in the OP. It has about a 40-50% chance of causing a bootloop, and about a 10% chance to leave your device unresponsive! There have been several released guides for other devices that have close to the same success rate / risk factor. All i can do is share what I have done, and what i know from personal exp.
Im sorry if anyone lands themselves on the wrong side of that equation, but it is a risk that only you can decide if its worth taking. For me, that answer is and always will be YES because i will not own a device that i do not OWN! For others this may be a touch more out of their league, and if thats true they should steer clear, until I or another user can get hold of an official TMO OTA, to examine the diff files in each.
****** Now all of that being said.... if ANYONE wishes to contribute to finding a solution to this dumpster fire, I am not asking for donations.... What i am asking, is for SOMEONE who might have a T-Mobile 10Pro on the release build, or any build PRIOR to 11_A.13 and is looking to help, we NEED an exact copy of an OTA update that might be sitting in your notifications. All updates download to the /sdcard/ partition of your phone in a folder that is accessible without root permissions. If you accept the download for the update, and DONT begin the install immediately, you can locate and pull that OTA to your computer, then delete the file from your phone, and it will cancel the update on reboot. No loss to you, but EXTREMELY HELPFUL to us, because we will have something from TMO to work with, which may give us a clue as to what we need to remove from the updater script ! *******
and FYI the signatures used to sign some of the OTA we already have, are already deciphered and as such can be used to create new signatures after making some changes to the respective regions package. But to make having these be of any value, we need to know what to take out or change in the manifest, that will prevent alterations of the files causing bootloops. If anyone can help with an upload of a TMO-OTA please share publicly or dm myself or one of the other devs who have expressed interest in this issue.
Thanks
I can probably pull the update from my wifes phone. She never updates anything. I did get my 10 pro to boot to android 13 but everything just says its disabled. This is only the 3rd phone ive done this with so ill warranty another one if i have to lol.
supercobaltss said:
EDIT: Local Update downgrade it currently installing
No Go, The update installed and downgraded but it just loads to the welcome screen and crashes and boot loops
Click to expand...
Click to collapse
Yup, this happened to me as well. Setup wizard crashes before I even get very far in it, and I've wiped multiple times trying to complete it somehow.
GuyInDogSuit said:
Yup, this happened to me as well. Setup wizard crashes before I even get very far in it, and I've wiped multiple times trying to complete it somehow.
Click to expand...
Click to collapse
Ive tried to convert multiple different ways. Upgrading to 13 basically screws you with the disabled apps BS, Downgrading just crashes the device. Either way its broken. I've went through 3 devices now messing around.
So I guess it's time to replace it, then? Crap.
GuyInDogSuit said:
So I guess it's time to replace it, then? Crap.
Click to expand...
Click to collapse
Start a RMA on OnePlus website, don't go through T-Mobile. They will have you send in phone and then either reflash your phone and send it back or just send you a new phone which is what they did when I had to do it. All that bs about voiding warranty when unlocking bootloader is just that, bs. They fix or replace without any issues but you have to go through OnePlus.
FML.
I've gotten it working for the most part, but what's most concerning is that there's no IMEI. And it doesn't charge or even acknowledge the cable. Fantastic.
jeffsga88 said:
Start a RMA on OnePlus website, don't go through T-Mobile. They will have you send in phone and then either reflash your phone and send it back or just send you a new phone which is what they did when I had to do it. All that bs about voiding warranty when unlocking bootloader is just that, bs. They fix or replace without any issues but you have to go through OnePlus.
Click to expand...
Click to collapse
I can't even request an RMA as I don't have an IMEI to provide. It's blank in the phone. I think I'm screwed. Or try T-Mobile. Dunno. This sucks.
GuyInDogSuit said:
I can't even request an RMA as I don't have an IMEI to provide. It's blank in the phone. I think I'm screwed. Or try T-Mobile. Dunno. This sucks.
Click to expand...
Click to collapse
The T-Mobile version has your IMEI sketched into the back cover of your phone. You should be able to use that.
jeffsga88 said:
The T-Mobile version has your IMEI sketched into the back cover of your phone. You should be able to use that.
Click to expand...
Click to collapse
Oh. Uh.... completely forgotten about that.
I just updated to Android 13 on the TMO NE2217, device not unlocked, still financed. And now have the option to unlock the BL.
beatbreakee said:
All updates download to the /sdcard/ partition of your phone in a folder that is accessible without root permissions. If you accept the download for the update, and DONT begin the install immediately, you can locate and pull that OTA to your computer, then delete the file from your phone, and it will cancel the update on reboot.
Click to expand...
Click to collapse
Is this still useful, with the NE2217_11_C.26 update? And either way, how can I delete it? I couldn't find anything big in /sdcard. Thanks!
deleted
psm321 said:
Is this still useful, with the NE2217_11_C.26 update? And either way, how can I delete it? I couldn't find anything big in /sdcard. Thanks!
Click to expand...
Click to collapse
^
^
^
^
^
THIS Please my phone ignored my saying no and next reboot the damn thing will go off on me ... so frustrating that even when you set the darn thing to OFF on auto update and such it STILL does this BS...
Damn TMobile and their special lock junk UGH ...
anyway ... please can one direct with a screen shot and file manager they used to find this file so I can delete the thing? ... I have tried to find it and struck out ... but having got the notification today and the Oxygen app is showing 'REBOOT' instead of 'resume' when I ignored the update previously has me thinking if I reboot I will see android 13 pop up and in this case means I will lose my whoop as something with it breaks pairing my wearable ... whoop has offered no timetable for a fix