hello, i am faced with the decision to get the tmobile OnePlus N20 or the N200.
I am abandoning samsung after years of being disappointed by not being able tto do witthg my phone what i choose.
I want a device i can root and tinker with and modify as i please.
so im looking at these 2 phones and obviousl the n20 wins according tto tthe specs. butt i would like tto know if anyone has been able tto roott this device yet? or do yyou foresee any major obsttacles to unlocking the boottloader? i dont wantt to be stuck yet again with a device tthat i cant mod the way i want. i would like tto eventually be able to run kali or some custom roms on it. i need a device that i can mosl replace my lapttopwith. i cant afford tthe f;lagship pohone rightt now or i would go witth tthat. if anyone has an suggestions or info i would greatly appreciate it.
also i know these are supposed tto have to be sim unlocked first but i saw in anotther thread on anotherdevice i believe it was an OPO something but there was a script hat got rid of tthe services/apps that prevented unlocking the booloader while sim locked.
does anone know if the same script could be run on this device or will i have to sim unlock i?
The unlocked variant can be rooted as easily as any, as long as you get a copy of its boot image. The TMo variant (which you're after) has yet to get its bootloader unlock token.
To me, having high refresh rate is paramount, so N20 omitting that is a critical flaw. Plus, having tried GSIs on both, I felt N20 was weirdly stuttery/unresponsive for its specs.
PsYk0n4uT said:
hello, i am faced with the decision to get the tmobile OnePlus N20 or the N200.
I am abandoning samsung after years of being disappointed by not being able tto do witthg my phone what i choose.
I want a device i can root and tinker with and modify as i please.
so im looking at these 2 phones and obviousl the n20 wins according tto tthe specs. butt i would like tto know if anyone has been able tto roott this device yet? or do yyou foresee any major obsttacles to unlocking the boottloader? i dont wantt to be stuck yet again with a device tthat i cant mod the way i want. i would like tto eventually be able to run kali or some custom roms on it. i need a device that i can mosl replace my lapttopwith. i cant afford tthe f;lagship pohone rightt now or i would go witth tthat. if anyone has an suggestions or info i would greatly appreciate it.
also i know these are supposed tto have to be sim unlocked first but i saw in anotther thread on anotherdevice i believe it was an OPO something but there was a script hat got rid of tthe services/apps that prevented unlocking the booloader while sim locked.
does anone know if he same scrip could be run on his device so as no o have o wai il i sim unlock i?
Click to expand...
Click to collapse
Get the n20 over the n200 if the final price difference is less than $60.
The n200 is a bad device for its specs because oneplus has no interest in optimizing the OS for its low end phones with 4gb ram, because oneplus has only two devices with 4gb ram: the n100 and n200. Oneplus put an OS designed for 6gb/8gb ram with mid-high end cpus on the N200 which has only 4gb ram and lower end cpu, and as a result, the N200 performs like a Motorola phone with 2gb/3gb ram.
Similarly speced Motorola phones perform much better than oneplus.
Ironically, if you update the N200 to android 12, the system will say the phone has a snapdragon 855 cpu, while it has a low end snapdragon 480 cpu. So basically oneplus software engineers just put an OS designed for high end phones onto the low end N200 without any optimization, and even forgot to change the cpu model name.
If you buy the carrier tmo/metro version, you need to obtain unlock token bin to unlock the bootloader, and you need to sim unlock first to enable OEM unlock or you can use the disabling Qualcomm uim app trick.
googlephoneFKLenAsh said:
Get the n20 over the n200 if the final price difference is less than $60.
The n200 is a bad device for its specs because oneplus has no interest in optimizing the OS for its low end phones with 4gb ram, because oneplus has only two devices with 4gb ram: the n100 and n200. Oneplus put an OS designed for 6gb/8gb ram with mid-high end cpus on the N200 which has only 4gb ram and lower end cpu, and as a result, the N200 performs like a Motorola phone with 2gb/3gb ram.
Similarly speced Motorola phones perform much better than oneplus.
Ironically, if you update the N200 to android 12, the system will say the phone has a snapdragon 855 cpu, while it has a low end snapdragon 480 cpu. So basically oneplus software engineers just put an OS designed for high end phones onto the low end N200 without any optimization, and even forgot to change the cpu model name.
If you buy the carrier tmo/metro version, you need to obtain unlock token bin to unlock the bootloader, and you need to sim unlock first to enable OEM unlock or you can use the disabling Qualcomm uim app trick.
Click to expand...
Click to collapse
Care to elaborate on what this Qualcomm uim app trick happens to be?
So I went with the n20. Actually seems to be a pretty decent phone other than the fact that it shipped with a 7 digit serial so I can't get an unlock token. Been back and forth with OnePlus trying to get it resolved but they always just tell me they will email a response within a few days. Their last response was to add a zero before the serial. But doing so just gives me an error that the serial/unlock code don't match. Hopefully I can get this taken care of and get the bootloader unlocked. OEM unlock was easy peasy to get with the debloat script found elsewhere in the opo threads here
Actually I have to say this is one of the better performing devices that I've owned. Similar to some of the flagship phones I've had. Only the refresh rate I guess would be a turn off for some though it doesn't bother me at all.
N20 of course
6/128 can make big difference from N200
Due to limit of response time, 90Hz IPS may not be better than 60Hz AMOLED
695 is like 750 according to Geekbench
PsYk0n4uT said:
So I went with the n20. Actually seems to be a pretty decent phone other than the fact that it shipped with a 7 digit serial so I can't get an unlock token. Been back and forth with OnePlus trying to get it resolved but they always just tell me they will email a response within a few days. Their last response was to add a zero before the serial. But doing so just gives me an error that the serial/unlock code don't match. Hopefully I can get this taken care of and get the bootloader unlocked. OEM unlock was easy peasy to get with the debloat script found elsewhere in the opo threads here
Click to expand...
Click to collapse
Oem unlock means sim unlock or bootloader unlock?
eagle3489 said:
Oem unlock means sim unlock or bootloader unlock?
Click to expand...
Click to collapse
in short, bootloader unlock.
OEM stands for Original Equipment Manufacturer. It refers to the manufacturer lock on the bootloader. It is a security feature to keep you from accidentally bricking your device by tampering with the system images/files or malware from being able to modify or tamper with your system. This is why SafetyNet fails when you root and many banking apps and games check SafetyNet at the beginning of execution to make sure that your running a secure system before they allow an app to open. There are some ways to get around that by hiding root/magisk with Xposed modules(LSposed) etc... Some methods work for some apps and others dont. Make sure you have everything backed up before doing any modifications to your system because its easy to brick your device(make it unbootable/nonfunctional)
I havent found a way to SIM unlock without going through the carrier. There are services out there that claim to be able to SIM unlock your device for a fee, and many have been reviewed by other members. I have not personally ever used one. But here Im referring to unlocking the bootloader so that the system on the device can be modified (rooted, non-stock ROMs, system tweaks/mods)
ScarletWizard said:
I have the n20 and was able to unlock boot loader and root with still being carrier locked.
Click to expand...
Click to collapse
Yeah, mine is rooted tooted and reasdy to be booted and is sitll carrier locked and not paid off..
ScarletWizard said:
Post your t mobile bill. Here is mine View attachment 5772795
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I read your posts and decided on the N20 as well and I must say this is an AWESOME little phone.
It came with the stock July OS. I have read many of the posts on here but I'm sort of stuck. I can't seem to figure out how to get a copy of the original OS. Read some options saying if i couldnt get a copy I could try to make one using twrp but that went down a dead end and I am back to square one. I have enabled developer mode, debug over usb, and set the setting to allow oem unlock and I'm kind of stuck at this point. My goal is to root this thing so that I can get call recording working like my older phones.
jonathandeath said:
I read your posts and decided on the N20 as well and I must say this is an AWESOME little phone.
It came with the stock July OS. I have read many of the posts on here but I'm sort of stuck. I can't seem to figure out how to get a copy of the original OS. Read some options saying if i couldnt get a copy I could try to make one using twrp but that went down a dead end and I am back to square one. I have enabled developer mode, debug over usb, and set the setting to allow oem unlock and I'm kind of stuck at this point. My goal is to root this thing so that I can get call recording working like my older phones.
Click to expand...
Click to collapse
File folder on MEGA
mega.nz
ScarletWizard said:
I brick my n20 daily trying exposed modules and I restore everytime using my boot.img backup
Click to expand...
Click to collapse
You should seriously flash this before anything and it'll save you from bootloop
Thank you so much! I am downloading now.
This is the one I picked up just for reference. 8 digit serial number on this model.
I disabled automatic updates and had the oem bootloader unlocked as well as all playstore options for updates disabled and this morning the phone updated itself without warning to the august update. It started talking about upgraded to android s and i factory reset it hoping it would roll everything back, but nope. Stuck on stupid August Update. I just wanted to get root back on it with call recording and lock down all android os updates.
ScarletWizard said:
Where do you find these zips. I haven't seen that in any repo
Click to expand...
Click to collapse
Hours and hours of shospelessly searching the bowels of th einternet my good man.
DrScrad said:
You should seriously flash this before anything and it'll save you from bootloop
Click to expand...
Click to collapse
How do I flash this first? I am starting fresh again tonight and want to do it right.
Gotcha,
So I have chosen to begin this portion with the following.
Disable DM-Verity or Android Verified Boot without TWRP
In this tutorial, we will show you the steps to disable DM-Verity or Android Verified Boot (AVB) without using TWRP Recovery.
www.droidwin.com
First step is to get a stock image file. However I have not been able to make a copy of my stock rom nor the current stock rom on my Phone now which is now on August patch 2022-09-05. I have downloaded several copies but there have been posts saying not to use just any version of stock rom so I'm trying to make sure i'm doing this right.
I am also on
Build Number CPH2459_11_A.08
Basebane version Q_V1_P14
Kernel version 5.4.147-qgki-g26211b5d5105
Hardware version CPH2459_11
I have the following files downloaded to work with.
I'm thinking of using this one.
Inside the following files can be found
If this is all right then I will try to continue with this portion of their instructional.
Does this sound about right?
Related
Hi!
I recently purchased a Verizon-build Samsung Galaxy A10e (the "economy Flagship" / little-brother of the A10) but XDA has very little information on this phone. Would this be the best place to try to find/request information?
Thanks for your help!
where can i get more developer information on this phone
Give it some time before developers start posting, since the phone was released only a couple of monthes ago. It will be a good minute before you start seeing significant posts for the galaxy a10 e. Keep updating by searching on a regular basis. Check howardforums or android central as well.
On another note:
Some of us need to know the a10e galaxy update to android 10, anyone got then lastest news on that yet? I got one with metro pcs.
Thx
Sent from my SM-A102U using Tapatalk
yea like alot of sites keep saying galaxy a10e will not be getting android 10 and one ui 2.0 but the fail to see samsung own site says they will probavly in may or june of 2020
Also using an SM-A102U device, I believe the official Android 10 date is sometime in the first half of 2020. I believe March.
What would really help us is pHH-Treble support for these devices and Android 10, which I can't find any info for, aside from a GSI post on the Galaxy a20, which has (essentially) the same Exynos chip.
timba123 said:
On the metro variant I was trying to figure out bootloader unlock and the phone vibrated and a yellow exclamation ! Appeared at bottom of black screen. What is that?
Click to expand...
Click to collapse
depends on wat u mean by trying to figure it out lol.. if its like any the other usa variants its not unlockable which is why u dont see oem unlock
timba123 said:
This.
Click to expand...
Click to collapse
i dont kno wat that is but seems to be a indicator for your charger.. maybe not fast charging or something.. i assume the device is off when you get this screen.. if its off and plugged in via pc it could simply be indicating its not fast charging as its being charged from the usb port.
Sent from my SM-N976V using Tapatalk
timba123 said:
It's not off exactly. Kinda reminds me of system crash on eng fac roms. I've seen articles about older devices and it meaning no battery or no charging like you say. Guess I got over excited for nothing lol. Though it might be a hackable situation etc or different mode of some kind.
Click to expand...
Click to collapse
Yea.. and fyi, a common misconception is "eng fac" roms are two completely different things lol.. it's a pet peeve of mine which I owe to all the firmware sites and generic "guides" on the web lol.
They always refer to factory/combo roms as "eng" when they are not eng at all.. fac roms are debuggable (ro.debuggable=1) and permissive and adb enabled by default and dmv disabled with a bare bone os mainly used for testing or fixing issues with the device.
Eng on the other hand is typically a stockish build with su binary by default (allows actual adb root shell) is permissive, verity disabled, contains other high level engineering software etc etc that is supposed to be used by engineers to test their software and things of that nature. My sampwnd root for s8/s8+ for example used eng system.img to gain root. Older devices did have eng boot.img many used to root devices but since s8 and newer they are no longer used because samsung implemented security measures to where u cant flash or run them without an eng token and device being in actual eng mode. Eng tokens are hard to find as they are device specific and need to be generated on samsung servers at which if u can find someone willing to make one they are usually expensive since they need to have a legit business, purchase a signing cert from samsung to be able to generate eng tokens as well as they typically need to also pay for each individual token which just the signing cert alone I've heard various prices from thousands to 100k lol. Then after all that if you have an eng token and device is in eng mode then it's not the same as a bl unlock as you would need to flash eng firmware which is another adventure to locate and probably another pretty penny.
Rant on eng/fac differences is over lmao.
On a side note, I'm working on something that "might" work... according to my dev buddies it will work.. it's a process tho as I need to generate some custom files and I never did this before (I mainly use usa locked snaps) .. but if all goes as planned with some trickery could probably unlock the bl and at the very least root the device.. stay tuned lol
timba123 said:
On the metro variant I was trying to figure out bootloader unlock and the phone vibrated and a yellow exclamation ! Appeared at bottom of black screen. What is that?
Click to expand...
Click to collapse
I also tried (with my limited knowledge here) to enable OEM bootloader unlock by changing the settings flag in the phone but have not had luck. I talk about what I tried to do/have a screenshot showing where the system has it looked in this post:
https://forum.xda-developers.com/ga...rint-oem-lock-developer-t3963898/post80909957
I have also looked at using Tasker/other tools to try to change something here or to see if there's an intent or action or something that will trigger the unlock but haven't had luck.
timba123 said:
So since this is the only A10e root thread. I'll post here. After browsing the internet I found out that Samsung changed some security. Now fac combo cant be flashed with 3.14 odin which newer devices like our A10e will not work with odin 3.13 and before patched or not. A new odin needs to be made. Patched. And the new Security for samsung.
Click to expand...
Click to collapse
This isnt new information. I do not think a new/patched odin will work since it uses a token system. Trying to flash will say you need approval to use factory binary.
With that being said you can use a factory bin token which will then allow you to flash combo rom.
There are ways to bypass need for a token but they are not public.
Also tokens are device specific and if you can find someone to get them they are not free.
Side question that's not totally related but I'm finding conflicting answers online:
Does the A10e NOT have USB-OTG capabilities? :-/
I don't have a USB-C OTG cable to test myself. I realize this phone purposely does not have some features/capabilities that I guess are supposedly deemed more "premium," in order to keep this phone in a class I've heard described as "Economy-Flagship," (lol ). Hence: no wireless charging, no fingerprint reader, no gyroscope, no proximity sensor (this exclusion is kind of annoying - surely I can't be the only person experiencing the annoying phenomenon of chronic cheekbone-call-muting? ). But overall, I'm super happy with this phone!
I also wish I could disable Knox but I don't think that's possible without the OEM bootloader unlock setting enabled.
timba123 said:
No not new info but figured alot of people especially new people could use the info. Lol they sure are locking down phones. I wonder what influence the NSA etc have.
Click to expand...
Click to collapse
govt contracts are definitely a big part of it.. every device manufacturer wants that govt money lol
elliwigy said:
govt contracts are definitely a big part of it.. every device manufacturer wants that govt money lol
Click to expand...
Click to collapse
^This makes a lot of sense.
Sorry for my english. I'm looking for help ... i was 3 weeks in US and i lost my phone. So i buyed this A10e with boost mobile but i didn't activate it because they were trying to force me to buy a monthly subscription, wich i didn't... I bring the phone just for wifi use because is a phone with good specs for the price of 90$... and then the horror shows in a form of Harassing message ... trying to make me "accept terms and conditions" and then Boom the phone was restricted from data usage and other things, i tried to unlock the OEM and nothing, also i wipe the phone and it works fine but it keeps harassing with sudden appears of that screen asking if you accept, the icon of that screen is a peace of chess. So my question is ... Can i force an instalation of other rom? in sammobile is a international rom, so, even if i can't unlock the oem , can i install it? is there a way to root the device without the oem unlock? Thanks in advance
reyesergio23 said:
Sorry for my english. I'm looking for help ... i was 3 weeks in US and i lost my phone. So i buyed this A10e with boost mobile but i didn't activate it because they were trying to force me to buy a monthly subscription, wich i didn't... I bring the phone just for wifi use because is a phone with good specs for the price of 90$... and then the horror shows in a form of Harassing message ... trying to make me "accept terms and conditions" and then Boom the phone was restricted from data usage and other things, i tried to unlock the OEM and nothing, also i wipe the phone and it works fine but it keeps harassing with sudden appears of that screen asking if you accept, the icon of that screen is a peace of chess. So my question is ... Can i force an instalation of other rom? in sammobile is a international rom, so, even if i can't unlock the oem , can i install it? is there a way to root the device without the oem unlock? Thanks in advance
Click to expand...
Click to collapse
no.. bl is locked.. only stock official firmware can be flashed
timba123 said:
Found a rooted AP tar but gives SHA error using Odin 3.14
Click to expand...
Click to collapse
doesnt work.. ur getting error bcuz its modified which cant use bcuz bl is locked
timba123 said:
Seems to be verizon firmware by the bootloader number etc. The firmware I posted pics of. I'd upload it but my browser keeps crashing trying to upload it
---------- Post added at 04:42 AM ---------- Previous post was at 04:25 AM ----------
https://support.halabtech.com/index.php?a=downloads&b=file&c=download&id=200612
Looks like root kernel for metro or tmobile
Click to expand...
Click to collapse
correct.. all it is is stock firmware with a rooted/patched kernel for unlockable variants
Combination File, for FRP & bootloop Repair
http://www.mediafire.com/file/ekejzhig7b9zx7r/ROMProvider.COM_SM-A102USQU1ASF1.rar/file
mark332 said:
Combination File, for FRP & bootloop Repair
http://www.mediafire.com/file/ekejzhig7b9zx7r/ROMProvider.COM_SM-A102USQU1ASF1.rar/file
Click to expand...
Click to collapse
how do you expect people to flash it without a factory binary token?
timba123 said:
Is OTP similar or related to the factory token? Like a password?
Click to expand...
Click to collapse
nope.. otp more of a one time password.. the token is something that uses device specific identifiers that then gets sent to a server where it gets signed and sent back.. then it needs to b physically flashed to the device
Sent from my SM-G977P using Tapatalk
I saw the other thread on unlocking the T-Mobile variant, so I thought I'd document my experience unlocking the version bought directly from the OnePlus store.
WarningsThis guide applies exclusively to OnePlus Nord N200 5G phones bought from the USA OnePlus online store.
It may work for other carrier-unlocked Nord N200 5G phones. However, I haven't tested them.
As always, this voids your warranty.
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about this process before following it. YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will not help you.
Click to expand...
Click to collapse
In addition, this adds an unremovable warning screen from the bootup process. After unlocking your device, the device will show a warning screen on every bootup for 5 seconds. It will read as follows:
The boot loader is unlocked and software integrity cannot be guaranteed. Any data stored on the device may be available to attackers. Do not store any sensitive data on the device.
Visit this link on another device:
g.co/ABH
PRESS POWER KEY TO PAUSE BOOT
Click to expand...
Click to collapse
As a last note, if successful, this will wipe your device. Backup all data you care about.
Prerequisites1. A OnePlus Nord N200 5G bought from the USA OnePlus store, running OxygenOS 11.
2. A computer with the `fastboot` android platform tool set up and working.
You can download a package containing fastboot from https://developer.android.com/studio/releases/platform-tools.
3. A usb-C cable to plug the phone into the computer.
Steps1. Enable developer settings.
Go to Settings -> About phone. Tap "Build number" 5 times until it brings up a prompt to enter your device password. Enter it.
On success, it will bring up a note saying "You are now a developer!"
2. Enable OEM Unlocking
Go to Settings -> System -> Developer Options. Tap "OEM Unlocking" and follow prompts.
3. Reboot into fastboot
Long-press the power button, then select "Restart". As the phone is restarting, hold down the volume down and volume up buttons.
The phone should now be showing a text interface. You can select different options with the volume buttons, and use the power button to select.
3. Unlock using fastboot
Connect the phone to the computer.
In a command prompt on the computer, use the following fastboot command:
Bash:
fastboot devices
Verify that your device is connected, and the serial code matches the "SERIAL NUMBER" shown on the screen of the phone. For instance, my device shows as:
Code:
$ fastboot devices
SERIAL_NUMBER_REDACTED fastboot
And on my phone screen, it shows "SERIAL NUMBER - SERIAL_NUMBER_REDACTED".
Once you've verified this, use the following command to unlock the device:
Reminder: THIS COMMAND WIPES YOUR DATA. All data on the phone will be erased by this.
Bash:
fastboot oem unlock
If successful, the computer will output this:
Code:
$ fastboot oem unlock
OKAY [ 0.042s]
Finished. Total time: 0.042s
On the phone, you will see a prompt for unlocking the device. Read it, and follow the instructions. Use the volume up/down buttons as up/down arrow keys, and the power button as "OK" or "Enter".
After you've confirmed you want to unlock the device, your phone will reboot several times, and erase all data. Once it's done, you'll be rebooted into the operating system.
4. Confirm the unlock worked
To confirm the unlock worked, reboot into fastboot mode again.
On the screen, the bottom row should now read "DEVICE STATE - unlocked".
Congrats! You've unlocked your device. Once someone builds a custom recovery or ROM, you'll be able to use fastboot to flash it to your device.
So does this mean you can now pull the files someone would need to start on a custom recovery and/or a custom rom or at least majisk?
alarmdude9 said:
So does this mean you can now pull the files someone would need to start on a custom recovery and/or a custom rom or at least majisk?
Click to expand...
Click to collapse
Unfortunately, this doesn't let you pull any files from the device. All it does is allow you to flash a custom recovery, ROM, or boot.img once someone develops one.
With that said, I have started researching steps for porting TWRP to the device.
Edit: since this is the only place I've mentioned it, might as well give an update. I'm giving up on porting TWRP for now - I think we really will need binary blobs, or a lot more hacking on things and finding a similar device. And given that our device is the first wave of devices with the sm4350 platform.... I think our best bet is OnePlus releasing binary blobs.
I've taken notes on everything I've been trying at https://github.com/daboross/android_device_oneplus_holi_notes, if anyone's interested.
Man that stinks. I was hoping we could have at least gotten the files needed for majisk.
2 alternate ways to get into fastboot mode:
ADB:
The command
'adb reboot bootloader'
will restart the device in fastboot mode.
Advanced Reboot:
In the developer options, turn on 'Advanced Reboot'.
Hold the power button for a few seconds to bring up the power off/restart dialog.
At the top right corner will be 3 dots, tap them, select 'bootloader' from the resulting dialog.
The phone will reboot into fastboot mode.
alarmdude9 said:
Man that stinks. I was hoping we could have at least gotten the files needed for majisk.
Click to expand...
Click to collapse
I'm thinking it'll be a chain reaction as soon as we have *anything*.
Like, if we get magisk, we'll quickly be able to then pull the stock ROM and recovery and use those to build TWRP.
Or if someone can build TWRP, we can use that to pull boot.img and get magisk working, and pull the stock ROM and get a custom ROM built.
Or if someone can port a custom rom (though I imagine this is harder than the above two - probably impossible without binary blobs?) - we can include root in it, then use that to grab boot.img and the recovery image.
As soon as we get *any* control which gives us root access or otherwise unimpeded access, we should be able to do everything.
daboross said:
I'm thinking it'll be a chain reaction as soon as we have *anything*.
Like, if we get magisk, we'll quickly be able to then pull the stock ROM and recovery and use those to build TWRP.
Or if someone can build TWRP, we can use that to pull boot.img and get magisk working, and pull the stock ROM and get a custom ROM built.
Or if someone can port a custom rom (though I imagine this is harder than the above two - probably impossible without binary blobs?) - we can include root in it, then use that to grab boot.img and the recovery image.
As soon as we get *any* control which gives us root access or otherwise unimpeded access, we should be able to do everything.
Click to expand...
Click to collapse
i dont specialize in oneplus phones but maybe you could somehow get the stock rom and extract the boot.img file to then patch with magisk or the recovery.img whatever it is
areallydumbperson said:
i dont specialize in oneplus phones but maybe you could somehow get the stock rom and extract the boot.img file to then patch with magisk or the recovery.img whatever it is
Click to expand...
Click to collapse
The hard part is "somehow get the stock rom".
As soon as we can get that, everything else will indeed be possible.
daboross said:
The hard part is "somehow get the stock rom".
As soon as we can get that, everything else will indeed be possible.
Click to expand...
Click to collapse
maybe try to intercept an update package download
How to Capture OTA Update URL for your Android (2 Methods)
In this guide, you will learn how to capture OTA update URL for your Android device. We have provided two methods to help you capture the OTA URL with or without PC. OTA updates are standard among all…
www.thecustomdroid.com
ota updates usually have all the partitions it need like boot.img
areallydumbperson said:
maybe try to intercept an update package download
How to Capture OTA Update URL for your Android (2 Methods)
In this guide, you will learn how to capture OTA update URL for your Android device. We have provided two methods to help you capture the OTA URL with or without PC. OTA updates are standard among all…
www.thecustomdroid.com
Click to expand...
Click to collapse
I think the thread has been deleted now, but someone did do that for the Metro variant. I believe there was also a grab for the T-Mobile variant.
Unfortunately, both of those OTA updates were partial updates, and are useless without an original ROM image. I've also been watching for an update to my OnePlus non-carrier-variant, but no updates have been pushed at all.
I think it's not a bad idea. Just unfortunately all the updates so far have been partial, and since a new version of android is a ways away, I think they will continue to be partial updates, still useless.
Aw that sucks if only someone was on a firmware before oxygenos 11
areallydumbperson said:
Aw that sucks if only someone was on a firmware before oxygenos 11
Click to expand...
Click to collapse
Ah, but the device shipped with OxygenOS 11!
There have been so few updates since the device was released a little over a month ago. No OxygenOS 10 firmware ever existed for it.
Is the N200 directly bought from oneplus dual sim?
It seems like the device has the space/pins for second sim but disables dual sim via software.
Check on youtube for "N200 teardown" and the motherboard likely has space/pins for second sim.
BTW: does the unlocked version of N200 have FM radio? Can you install app "NextRadio" and see if it works?
GSMArena lists the N200 as dual sim with FM radio.
googlephoneFKLenAsh said:
Is the N200 directly bought from oneplus dual sim?
It seems like the device has the space/pins for second sim but disables dual sim via software.
Check on youtube for "N200 teardown" and the motherboard likely has space/pins for second sim.
BTW: does the unlocked version of N200 have FM radio? Can you install app "NextRadio" and see if it works?
GSMArena lists the N200 as dual sim with FM radio.
Click to expand...
Click to collapse
I'm not sure if it's dual sim or not, but it doesn't look designed to be. There's only one IMEI listed in settings, and while the SIM tray is long enough for two different SIM cards, the second one is filled in with plastic and you'd have to modify it to put a SIM card there.
Here's a picture of the front and back of the SIM tray:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The nextradio app does not work.
daboross said:
I'm not sure if it's dual sim or not, but it doesn't look designed to be. There's only one IMEI listed in settings, and while the SIM tray is long enough for two different SIM cards, the second one is filled in with plastic and you'd have to modify it to put a SIM card there.
Here's a picture of the front and back of the SIM tray:
View attachment 5376771
The nextradio app does not work.
Click to expand...
Click to collapse
The motherboard may have pins for second sim card.
Maybe like the t-mobile version of oneplus 6T, we just need to replace the sim card tray and flash compatible firmware to enable dual sim function.
Even with one IMEI, both sim cards can still work simultaneously like the T-Mobile oneplus 6T. People have reported two sims work on t-mobile simultaneously or on two different carriers on t-mobile oneplus 6T with one imei.
daboross said:
I'm not sure if it's dual sim or not, but it doesn't look designed to be. There's only one IMEI listed in settings, and while the SIM tray is long enough for two different SIM cards, the second one is filled in with plastic and you'd have to modify it to put a SIM card there.
Here's a picture of the front and back of the SIM tray:
View attachment 5376771
The nextradio app does not work.
Click to expand...
Click to collapse
I'm surprised the radio app doesn't work. There is a default package installed with a radio app, and the original phone (A91?) comes with an fm radio.
Can someone explain if they really switched the camera modules? I can't find any info on what the specific camera module is, plus the a54 (oppo) has a 48 mp camera versus the 13 mp in the n200. It seems like they really wouldn't switch the cameras on a phone so similiar, but who am I?
Fishwithadeagle said:
Im surprised the radio app doesn't work. There is a default package installed with a radio app, and the original phone (A91?) comes with an fm radio.
Click to expand...
Click to collapse
What is the default package? I can't find any on my device that looks like it'd be a radio app.
Here's a screenshot of NextRadio. To be clear, I have done no debugging to see if I could get it to work. I just installed it via the play store and opened it.
Fishwithadeagle said:
Can someone explain if they really switched the camera modules? I can't find any info on what the specific camera module is, plus the a54 (oppo) has a 48 mp camera versus the 13 mp in the n200. It seems like they really wouldn't switch the cameras on a phone so similiar, but who am I?
Click to expand...
Click to collapse
I'm not against discussing this here, but I think you may have more luck with a new Question thread specifically for this question. I'm not an expert on phone hardware.
daboross said:
Ah, but the device shipped with OxygenOS 11!
There have been so few updates since the device was released a little over a month ago. No OxygenOS 10 firmware ever existed for it.
Click to expand...
Click to collapse
Have you tried downloading full ROM of OxygenOS11 using the Oxygen Updater app?
jilebi said:
Have you tried downloading full ROM of OxygenOS11 using the Oxygen Updater app?
Click to expand...
Click to collapse
Thanks for referring to that!
Unfortunately, I downloaded the app, and there's only one update channel available - "Stable". No option to select between Incremental and Full on this device. Screenshot of this below:
I tried downloading something in my developer options and it seemed to work, but when my phone restarted I got a message saying, "your device is corrupt. It Can't be trusted and will not boot". The message seems to be in some sort of boot loop, (keeps restarting with the same message). Is there any way I can fix this without sending my phone in to One Plus? I purchased the phone inside of a Metro store.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If your phone is from T-Mobile or Metro, check out this forum post to recover your phone: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4324431/
If your phone was factory unlocked, contact OnePlus for a repair. The easiest way to tell if your phone is a carrier device or not is to check the back of the phone. If there's an IMEI engraved on the back of the phone, it's a T-Mobile or Metro phone. If there's not IMEI engraver, its factory unlocked.
I think what you used was the DSU Loader.
If I recall earlier posts in this forum correctly, you need to Bootloader Unlock your phone before messing with DSUs, or you will brick your phone.
As Izgmc said, you'll need to use the MSM Download Tools in the thread he linked to fix your phone, assuming you have the T-Mobile or Metro versions; or to contact OnePlus support if you have the factory unlocked variant.
edale1 said:
I think what you used was the DSU Loader.
If I recall earlier posts in this forum correctly, you need to Bootloader Unlock your phone before messing with DSUs, or you will brick your phone.
As Izgmc said, you'll need to use the MSM Download Tools in the thread he linked to fix your phone, assuming you have the T-Mobile or Metro versions; or to contact OnePlus support if you have the factory unlocked var
Click to expand...
Click to collapse
Yeah that was it! Lesson learned. Thank you!
Thats how I managed to mess up my phone and is currently bricked for several months .. no msmdownload for the unlocked .. please try and get a remote session with the oneplus tech guys .. and share if possible
Hold up a second here. If you have tried to relock the bootloader (which will result in the device is corrupt and will not boot message) try this:
Hold down all 3 buttons (Vol+ Vol- and power) for about 8 seconds or so. As soon as the device vibrates quickly release the power button. When you do, the device should be in fastboot. If you are in fastboot you should now be able to connect it to the PC and type the command fastboot oem unlock. This will now attempt to unlock the bootlaoder. Chances are you have previously unlocked the bootloader and have attempted to relock it. Doing so will cause this error message on the UNLOCKED version of the device.
This will wipe the data but return the device to an unlocked state but not completely bricked on stock firmware. Go through the normal prompts to start the device and you should be good.
Remember, if you have fastboot its not COMPLETELY bricked. Not yet anyways.
I had this happened on my OnePlus Nord 200 5g literally the next day after I got it from Metro at T-Mobile. Phone updated as it should but restarted with the same message you received. They tried to accuse me of putting a virus on the phone which did not make any sense and after going through insurance who couldn't accept the claim for "software damage" ... I contacted one plus and had them remote view my laptop with downloaded tar files and had a technician try to reinstall them back to its original factory condition but to no luck. Metro being a franchise company, has the loophole not accepting returned merchandise even under the return policy stated on the receipt, and customer service technically has no control or power over any particular franchise Metro store. I suggest the only answer I had after 2 weeks of frustration from contacting everyone I possibly could to writing corporate, I finally had a CSR tell me to just get a warranty exchange at any Metro store in which I did in two days later I received a new phone which actually works this time so I would suggest just doing the warranty exchange in order to get yourself a workable phone. Hope that helps. \m/
edale1 said:
I think what you used was the DSU Loader.
If I recall earlier posts in this forum correctly, you need to Bootloader Unlock your phone before messing with DSUs, or you will brick your phone.
As Izgmc said, you'll need to use the MSM Download Tools in the thread he linked to fix your phone, assuming you have the T-Mobile or Metro versions; or to contact OnePlus support if you have the factory unlocked variant.
Click to expand...
Click to collapse
I did this exact thing. Mine is the oem unlocked variant. Is contacting oneplus support still the only option? It's on the metro/tmobile network if that matters. I really fcked up here with dsu loader. Pretty desperate right now for a fix. Please.
superspecialgueststar said:
I did this exact thing. Mine is the oem unlocked variant. Is contacting oneplus support still the only option? It's on the metro/tmobile network if that matters. I really fcked up here with dsu loader. Pretty desperate right now for a fix. Please.
Click to expand...
Click to collapse
You can try the MSM Tools and see if it works, if not, then yes, OP Support is your only option.
edale1 said:
You can try the MSM Tools and see if it works, if not, then yes, OP Support is your only option.
Click to expand...
Click to collapse
Thanks, I downloaded msm tools and there are msm tools included in https://www.terabox.com/web/share/link?surl=7fjfMJSEcdl5zCjPT92IKA
for
dre8t_10_O.05_210713.tar.bz2 -can someone point me to the stock firmware I should be using msmtools error device not match image. Can I use the ~3gb ota zips?
Taking a break and then going to look for a guide for MSM tools.
edit - as an additional point of confusion, my bootloader was unlocked, I was rooted with magisk patched upstream boot.img. Did this happen because I did not know about uninstalling magisk and installing magiosk to the inactive slot? My bootloader is still unlocked, but flashing boot backups etc does not get me out of fastboot loop, and unable to verify boot image error when I try to fastboot boot twrp or orangefox.
You're past the point I can help with, maybe someone else has some more advice for you?
Thanks. And technical support turns out is the only way and sending it in is the only way for the oem unlocked version. I requested a remote session and ended up being told the files aren't working so they can't do a remote session. If they arent working how are they going to flash my device lol...who knows.
Superspecialgueststar,
The released MSM tool is only for the carrier variant and cannot be used for the unlocked variant. There is cryptographic security in place to restrict its use.
You can still fix your unlocked device, just use an unbrick guide for the unlocked version.
[GUIDE] How to unbrick your Nord N200 5G (ALL VARIANTS) or switch bootable slot (REQUIRES UNLOCKED BOOTLOADER)
I've seen alooot of issues lately of people "bricking" their Nord N200's without a method of unbricking (at the time of writing, only T-Mobile variant has MSMTool) I've noticed a reoccurring theme. i myself am guilty of doing it and not...
forum.xda-developers.com
or use my unbrick experience and advice
Un-bricking my Nord N200
Don't ask me why, but I tried to upload a GSI using fastboot to my N200. And that didn't work. So I then read online about other people getting the same error I had, and their fix was deleting the "product" partition and erasing the system...
forum.xda-developers.com
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?