Hi friends,
Hopefully this will be newbie appropriate questions that are easy to answer:
1. I just bought a used ATT Lg G5 H820 (Titan I think) where the seller gave me an unlock code - I've never bought a used phone before, but it's for my son, and I don't know how to execute unlocking and what not, but I figure Google is my friend there.
2. I want to downgrade android from 7 N to 6 Marshmellow - I've been reading that there are a couple of Flash tools that can do that if I have the image - I've searched high and low and moved heaven and earth to find one that I think is bona fide without making me go through a sea of click ad traps, to no avail - my assumption is all I need are the tools and just the stock image.
So here are my questions:
A. Can anyone share a link to the image that I seek where downloading it doesn't require a ninja to do the download?
B. Do I have to use an ATT image? can I use a Tmobile H830? bad idea?
C. If I flash it down to Marshmellow with either of the images as mentioned in (B) are there negative ramifications to unlocking the phone?
Thank you in advance - I sincerely appreciate any and all advice on the matter.
Mike
mikey332211 said:
Hi friends,
Hopefully this will be newbie appropriate questions that are easy to answer:
1. I just bought a used ATT Lg G5 H820 (Titan I think) where the seller gave me an unlock code - I've never bought a used phone before, but it's for my son, and I don't know how to execute unlocking and what not, but I figure Google is my friend there.
2. I want to downgrade android from 7 N to 6 Marshmellow - I've been reading that there are a couple of Flash tools that can do that if I have the image - I've searched high and low and moved heaven and earth to find one that I think is bona fide without making me go through a sea of click ad traps, to no avail - my assumption is all I need are the tools and just the stock image.
So here are my questions:
A. Can anyone share a link to the image that I seek where downloading it doesn't require a ninja to do the download?
B. Do I have to use an ATT image? can I use a Tmobile H830? bad idea?
C. If I flash it down to Marshmellow with either of the images as mentioned in (B) are there negative ramifications to unlocking the phone?
Thank you in advance - I sincerely appreciate any and all advice on the matter.
Mike
Click to expand...
Click to collapse
1. To unlock the phone from a stock rom power off the phone and insert a sim card for another network and power it up. Phone will ask for the unlock code when it finishes booting. Since it's an ATT variant use a t mobile sim card. I'd make sure you can unlock it before you do anything else.
2. Why do you want to downgrade to marshmallow? Doesn't seem like its worth the effort. Besides you are going to have to then turn off updates or your going to get updated to nougat. If you decide to downgrade you have to downgrade to an ATT image. Using a T mobile image will most likely brick your phone. Not sure if it will be a soft or hard brick but it's not worth it.
idontkn1 said:
1. To unlock the phone from a stock rom power off the phone and insert a sim card for another network and power it up. Phone will ask for the unlock code when it finishes booting. Since it's an ATT variant use a t mobile sim card. I'd make sure you can unlock it before you do anything else.
2. Why do you want to downgrade to marshmallow? Doesn't seem like its worth the effort. Besides you are going to have to then turn off updates or your going to get updated to nougat. If you decide to downgrade you have to downgrade to an ATT image. Using a T mobile image will most likely brick your phone. Not sure if it will be a soft or hard brick but it's not worth it.
Click to expand...
Click to collapse
Good idea on #1 - I wondered about that, but wasn't sure if that mattered - I did do a complete reset as soon as I got the phone, and haven't unlocked still, so I'm hoping that I didn't ruin the 'unlockability' by resetting it.
Anyway on your #2, I did a phone upgrade recently from G5 to G6, and was on Marshmellow with the G5 - there were aspects that I'm familiar with that Android version, so I want to try to downgrade - I've never experimented with the phones that I pay service on because I've always been afraid of bricking it bad, so I figure that with my sons used phone, I can tinker a bit without losing too much sleep if I mess things up.
Thank you for that great response - I sincerely appreciate it!
M
idontkn1 said:
1. To unlock the phone from a stock rom power off the phone and insert a sim card for another network and power it up. Phone will ask for the unlock code when it finishes booting. Since it's an ATT variant use a t mobile sim card. I'd make sure you can unlock it before you do anything else.
2. Why do you want to downgrade to marshmallow? Doesn't seem like its worth the effort. Besides you are going to have to then turn off updates or your going to get updated to nougat. If you decide to downgrade you have to downgrade to an ATT image. Using a T mobile image will most likely brick your phone. Not sure if it will be a soft or hard brick but it's not worth it.
Click to expand...
Click to collapse
Hi there,
Might I ask if you have any ideas on how I can proceed to downgrade to Marshmellow? - I want to try rooting Marshmellow if I can.
This is a bit off topic, but when I was exploring this site, I found this subdomain https://depot.xda-developers.com - and I'm very interested in purchasing one of those lifetime VPN services, but wanted to get more info from the community about the VPN options, as there seemed to be many pretty low cost VPN products to choose from.
And off the top of your head, do you know of a Simcard that I can purchase with no contracts where the minutes do not expire at the end of the month, that you personally like? - it seems like there are so many GSM options for this unlocked used phone. tia
Hi, I have no doubt this is a common question, but I'm here because after researching all day on this website and others, I have heard conflicting narratives and want to see if I can get some clarity with someone who has knowledge on this.
TLDR; I am wondering if all U.S. phones with Snapdragon cannot be normally rooted by just enabling OEM unlock/unlocking bootloader and must be rooted in an expert/costly method. Or if accounts from people saying they enabled OEM unlock on their Moto G Powers I read were not just fictional or with non-U.S. phones.
Click to expand...
Click to collapse
I live in the U.S. What I understand is that all U.S. Android phones with the Snapdragon chipset are impossible to easily root because they cannot have their bootloaders unlocked. I found this to be the case with the (unlocked, not carrier-specific) U.S. Moto G Power 2021 phone I just bought. I cannot tick OEM Unlocking in Developer settings, it's greyed out. I found users here and on other forums saying that it's possible to conventionally root Moto G Power 2021 phones, which I thought up till recently because I easily got an ID from the Motorola website, but obviously couldn't proceed with fastboot because OEM Unlocking is disabled and I can't change that. (in CMD fastboot said exactly this: OEM must be unlocked to proceed.)
Oddly, some users said that the option stopped being greyed out after a few days or a week. I contacted Motorola to see if this is a design thing but they were of no help, just telling me not to root as if I was unaware it voids warranty. Notably, just as many users said that the option would always be disabled, which began to make sense given what I learned next.
It was soon after I found people saying that all U.S. Android phones with Snapdragon consciously lock bootloader. All carrier-specific and unlocked varieties. (Consequently, there are services that do it for you, but this costs money and I'm interested in a phone I can root myself for free.) I was surprised it took me as long as I did to hear of this, and afterwards I searched for this specifically to get more clarity but didn't find any articles or documentation. It explains everything, of course, except for why I read some people (including here) were able to enable OEM Unlocking on their Moto G Power 2021 devices. (perhaps they were not U.S. phones but this was not mentioned.)
At this point if there's no way to enable OEM unlock I'm simply going to return the phone as I want a phone that I can root.
Snapdragon Androids disabling OEM unlock/bootloader unlocking is simply because of U.S. company decisions, because non-U.S. Android phones with Snapdragon do allow it. Because of this, I'm looking at international/European GSM Androids with Snapdragon, (such as the Xiaomi Mi A3) which the majority of anywhere-near-recent Androids clearly have, that would allow me to do this. I'm going to be as sure as I can it will be compatible in the U.S. (I use AT&T) and that it will be feasible to root for free.
Thanks for reading, especially if you got this far.
To root a phone's Android it isn't needed to unlock phone's bootloader. Android is rooted as soon as SU binary is present in Android's file system.
jwoegerbauer said:
To root a phone's Android it isn't needed to unlock phone's bootloader. Android is rooted as soon as SU binary is present in Android's file system.
Click to expand...
Click to collapse
Motorola system partition is write-protected, the bootloader must be unlocked for permanent root.
KindleMatchLight said:
Hi, I have no doubt this is a common question, but I'm here because after researching all day on this website and others, I have heard conflicting narratives and want to see if I can get some clarity with someone who has knowledge on this.
I live in the U.S. What I understand is that all U.S. Android phones with the Snapdragon chipset are impossible to easily root because they cannot have their bootloaders unlocked...
Click to expand...
Click to collapse
See the CID and OEM unlock posts
[Guide]Un/locking Motorola Bootloader
UnLocking and ReLocking Motorola Bootloader https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a Moto Bootloader Unlocking site Re-Locking see Post #4 More about bootloader UnLocking Post #2 Can my...
forum.xda-developers.com
If you get the bootloader unlocked
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
sd_shadow said:
Motorola system partition is write-protected, the bootloader must be unlocked for permanent root.
Click to expand...
Click to collapse
Absolute nonsense.
KindleMatchLight said:
Hi, I have no doubt this is a common question, but I'm here because after researching all day on this website and others, I have heard conflicting narratives and want to see if I can get some clarity with someone who has knowledge on this.
I live in the U.S. What I understand is that all U.S. Android phones with the Snapdragon chipset are impossible to easily root because they cannot have their bootloaders unlocked. I found this to be the case with the (unlocked, not carrier-specific) U.S. Moto G Power 2021 phone I just bought. I cannot tick OEM Unlocking in Developer settings, it's greyed out. I found users here and on other forums saying that it's possible to conventionally root Moto G Power 2021 phones, which I thought up till recently because I easily got an ID from the Motorola website, but obviously couldn't proceed with fastboot because OEM Unlocking is disabled and I can't change that. (in CMD fastboot said exactly this: OEM must be unlocked to proceed.)
Oddly, some users said that the option stopped being greyed out after a few days or a week. I contacted Motorola to see if this is a design thing but they were of no help, just telling me not to root as if I was unaware it voids warranty. Notably, just as many users said that the option would always be disabled, which began to make sense given what I learned next.
It was soon after I found people saying that all U.S. Android phones with Snapdragon consciously lock bootloader. All carrier-specific and unlocked varieties. (Consequently, this there are services that do it for you, but this costs money and I'm interested in a phone I can root myself for free.) I was surprised it took me as long as I did to hear of this, and afterwards I searched for this specifically to get more clarity but didn't find any articles or documentation. It explains everything, of course, except for why I read some people (including here) were able to enable OEM Unlocking on their Moto G Power 2021 devices. (perhaps they were not U.S. phones but this was not mentioned.)
At this point if there's no way to enable OEM unlock I'm simply going to return the phone as I want a phone that I can root.
Snapdragon Androids disabling OEM unlock/bootloader unlocking is simply because of U.S. company decisions, because non-U.S. Android phones with Snapdragon do allow it. Because of this, I'm looking at international/European GSM Androids with Snapdragon, (such as the Xiaomi Mi A3) which the majority of anywhere-near-recent Androids clearly have, that would allow me to do this. I'm going to be as sure as I can it will be compatible in the U.S. (I use AT&T) and that it will be feasible to root for free.
Thanks for reading, especially if you got this far.
Click to expand...
Click to collapse
You must wait, I believe it was several days of the device being online (wifi at least) to get it to permit unlocking the bootloader. I know with mine (US Xfinity Wireless), out of the box, it was gray, but 2 or 3 days later it was able to be toggled and I unlocked and got Magisk installed easily, using the patch stock boot.img method, and flashing it via fastboot beyond that. So you can do it, just can't do it before you activate the thing properly I think is the main block there you're describing. So perhaps those outside the US (with US models they can't toggle) can connect to a VPN'd wifi network and have it look like it's in the US, maybe.
There's a lot that can be done on these with just tinkering to get it there is all. But make sure you have your stock firmware is all, so you can quickly get it back into bootloader and just a flash away to fix anything really.
jwoegerbauer said:
Absolute nonsense.
Click to expand...
Click to collapse
Okay. Legit question here... How does one go about injecting SU binary to the system on the moto g 2021 series with secured boot?
Why should SU binary get housed in /system/... ? It's irrelevant where it's located, the main thing is that it's available and executable. Even Magisk doesn't store it in /system/.. but in /data/..
Because folder /data/local/tmp by default is mounted as RW my recommendation is to store it there. Using this storage place isn't conflicting with SELinux and/or AVB.
Code:
adb devices
adb push <FULL-PATH-OF-SU-BINARY-ON-PC-HERE> /data/local/tmp/
adb shell "chmod +x /data/local/tmp/su"
When you have to run a shell command what requires elevated rights, then you run
Code:
adb devices
adb shell "/data/local/tmp/su -c '<SHELL-COMMAND-HERE>'"
Deleted member 1890170 said:
To root a phone's Android it isn't needed to unlock phone's bootloader. Android is rooted as soon as SU binary is present in Android's file system.
Click to expand...
Click to collapse
it needs to be unlock
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?