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
Related
I just bought my vs987 less than a week ago, and when I install my T-Mobile sim card, I'm able to place calls but I'm unable to use the cellular data. I thought these were supposed to be unlocked? My data works fine when I use the Verizon sim card.
Also, when I first started it up I noticed that my "Software status" said "modified." Does that mean that this phone was previously owned/tampered with? I updated to 7.0 Nougat via Uppercut and LGUP, and now it says "Official." So, I'm a bit alarmed by what was there previously...
Can someone address both of these concerns?
Also, in "About Phone" in the settings menu there is no "Update Center" option. I looked in this video and it appears there.
https://youtu.be/gXeKZ6Dk4Fg
Is that normal, too?
I would appreciate the feedback because I'm a bit anxious due to the fact that Best Buy apparently charges $35 for returns or exchanges on phones. -_-
Do you know if the bootloader is unlocked? Because on some phones when the bootloader is unlocked if causes some problems especially on stock firmwares!
DevCharlie17 said:
Do you know if the bootloader is unlocked? Because on some phones when the bootloader is unlocked if causes some problems especially on stock firmwares!
Click to expand...
Click to collapse
How can I go about verifying whether it's unlocked or not? I swear if something is wrong they better not charge me $35. I will dispute them via my CC company if they do.
Well a simple way is when it boots up it says “bootloader unlocked and visit this link” or something in that nature and a nother way of checking is going into settings - about phone - software info - click build number 8 times - back to settings - developer options... And if enable OEM Unlock is checked... Your bootloader is unlocked
DevCharlie17 said:
Well a simple way is when it boots up it says “bootloader unlocked and visit this link” or something in that nature and a nother way of checking is going into settings - about phone - software info - click build number 8 times - back to settings - developer options... And if enable OEM Unlock is checked... Your bootloader is unlocked
Click to expand...
Click to collapse
I checked and there isn't an option for OEM Unlock in the dev options.
Edit: I think this is because the vs987 isn't rootable.
Hmm well I honestly don't know what could be causing this problem I would suggest finding another official KDZ (don't downgrade) from here http://downloads.codefi.re/autoprime/LG/LG_G5/VS987/VS98711A and if possible factory reset before and after
DevCharlie17 said:
Hmm well I honestly don't know what could be causing this problem I would suggest finding another official KDZ (don't downgrade) from here http://downloads.codefi.re/autoprime/LG/LG_G5/VS987/VS98711A and if possible factory reset before and after
Click to expand...
Click to collapse
Since I'm unable to create a backup of my current state I'd like to use this as a last resort. I'll wait a bit for other responses and if things don't seem good I'll give it a go. Thanks for the help so far. I appreciate it.
No Problem!
Does anyone else have any ideas? I'm running low on time with Best Buy's return policy, so I'd really appreciate it.
Hello XDA, I've been wanting to root my S6 for a while now, and i think you can do it with adb. So when trying this i noticed i needed an unlocked bootloader, and i thought i had it because i had CRom service on my S6, but never opened it. When i did, it just crashed. Now, i'm not sure if I can just use
Code:
fastboot oem unlock
or i need something else. I'm on Mac so i am very, very limited. I at least can get adb to work. If i can use adb and or fastboot to unlock my device's bootloader (without messing DM Verity) then please tell me right away.
iLoveMuffinz said:
Hello XDA, I've been wanting to root my S6 for a while now, and i think you can do it with adb. So when trying this i noticed i needed an unlocked bootloader, and i thought i had it because i had CRom service on my S6, but never opened it. When i did, it just crashed. Now, i'm not sure if I can just use or i need something else. I'm on Mac so i am very, very limited. I at least can get adb to work. If i can use adb and or fastboot to unlock my device's bootloader (without messing DM Verity) then please tell me right away.
Click to expand...
Click to collapse
What variant s6 do you have?
Go to Settings - About Device - Build number. Tap on that repeatedly until you see that Developer Options has been enabled.
Go back to Settings. You will now see a new entry called Developer options. Tap on that.
Under Developer options you will see OEM Unlock. Switch that to On.
And you are done! Just that easy!
koop1955 said:
Go to Settings - About Device - Build number. Tap on that repeatedly until you see that Developer Options has been enabled.
Go back to Settings. You will now see a new entry called Developer options. Tap on that.
Under Developer options you will see OEM Unlock. Switch that to On.
And you are done! Just that easy!
Click to expand...
Click to collapse
It's not that easy, the option is called "Allow OEM unlocking" which I already have turned on. All that option does is allow the bootloader to be unlocked.
sofir786 said:
What variant s6 do you have?
Click to expand...
Click to collapse
920T Unlocked.
I know. A rare S6 model, bought in Panama.
iLoveMuffinz said:
920T Unlocked.
I know. A rare S6 model, bought in Panama.
Click to expand...
Click to collapse
What version android are you on, btw the user previous is correct, once you use OEM unlock all you need to do is flash cf-autoroot, OEM unlock make sure that after rooting the phone does not trip frp and just lock you out of your device.
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
Just another note the g920t is classified as a T-mobile variant, it's got its own whole forum here on xda, if you don't get any luck here might be an idea to pop on over there and have a look see
sofir786 said:
What version android are you on, btw the user previous is correct, once you use OEM unlock all you need to do is flash cf-autoroot, OEM unlock make sure that after rooting the phone does not trip frp and just lock you out of your device.
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
Just another note the g920t is classified as a T-mobile variant, it's got its own whole forum here on xda, if you don't get any luck here might be an idea to pop on over there and have a look see
Click to expand...
Click to collapse
Ok, I'm on 6.0.1 (Y is Samsung so slow when releasing updates) and a quick reminder: I'm on Mac, how am I supposed to flash CF-autoroot?
And I got confused by "make sure after rootingthe phone does not trip frp and just lock out of your device" Do you mean to be careful not to brick my device?
iLoveMuffinz said:
Ok, I'm on 6.0.1 (Y is Samsung so slow when releasing updates) and a quick reminder: I'm on Mac, how am I supposed to flash CF-autoroot?
And I got confused by "make sure after rootingthe phone does not trip frp and just lock out of your device" Do you mean to be careful not to brick my device?
Click to expand...
Click to collapse
FRP is factory reset protection, if you don't allow OEM unlock when after you have carried out root and try to log into phone again you won't be able to do so, it's a security feature, frp is very tricky and it's important you make sure you have OEM unlock enabled before trying to do anything. You can use a software called heimdall which is similar to Odin and can be downloaded for mac. Yeah samsung always rolls out updates for international before anything else, just how they work. Before doing anything I highly advise you to visit the g920t forums, you will get more info there than you will here on the international forum. I hope you manage to get things done
sofir786 said:
What version android are you on, btw the user previous is correct, once you use OEM unlock all you need to do is flash cf-autoroot, OEM unlock make sure that after rooting the phone does not trip frp and just lock you out of your device.
Click to expand...
Click to collapse
Thanks for pointing that out. I don't know why I expect people to be grateful on XDA, just because someone tries to help them.
Using a Mac, you flash files using Heimdall: http://glassechidna.com.au/heimdall/
Ok so I think I'm good to go:
I attached some screenshots checking if everything is correct. Also, is http://glassechidna.com.au/heimdall/ the correct and official site to get Heimdall? And my device's build is G920TUES5DQD1 which was released a few days ago, and I'm not sure if the CF auto root file was based on an earlier update. Will I still be able to use it?
is g920v bootloader unlockable?
is it possible to downgrade thanks to this oem unlock?
sofir786 said:
FRP is factory reset protection, if you don't allow OEM unlock when after you have carried out root and try to log into phone again you won't be able to do so, it's a security feature, frp is very tricky and it's important you make sure you have OEM unlock enabled before trying to do anything. You can use a software called heimdall which is similar to Odin and can be downloaded for mac. Yeah samsung always rolls out updates for international before anything else, just how they work. Before doing anything I highly advise you to visit the g920t forums, you will get more info there than you will here on the international forum. I hope you manage to get things done
Click to expand...
Click to collapse
My phone has the front tripped, is there any way to reset it? I can't even figure out how to pull up the system info, I can pull up the recovery menu and hard reset but I don't know how to, if possible, reset the front. Any advice?
Sent from my LGE LG-LS777 using XDA Labs
iLoveMuffinz said:
Hello XDA, I've been wanting to root my S6 for a while now, and i think you can do it with adb. So when trying this i noticed i needed an unlocked bootloader, and i thought i had it because i had CRom service on my S6, but never opened it. When i did, it just crashed. Now, i'm not sure if I can just use
Code:
fastboot oem unlock
or i need something else. I'm on Mac so i am very, very limited. I at least can get adb to work. If i can use adb and or fastboot to unlock my device's bootloader (without messing DM Verity) then please tell me right away.
Click to expand...
Click to collapse
Install Windows in a Virtual Machine, Use ODIN to flash TWRP, flash Magisk.
help with unlock bootloader s6 920v
first, i want to thank the ones that can help and enlight others. thanks.
Now, i have a verizon s6 920v and doesnt present the "OEM..." option in Dev section. could i know if is unlock the bootloader, in other way?
thanks again.
joeknz said:
first, i want to thank the ones that can help and enlight others. thanks.
Now, i have a verizon s6 920v and doesnt present the "OEM..." option in Dev section. could i know if is unlock the bootloader, in other way?
thanks again.
Click to expand...
Click to collapse
As far as I know, and what has been the fact since the release of the 920V, there's has been no known case where the bootloader has been unlocked. Due to Verizon's restrictions, the S6 is hardlocked. The only way that it might ever be unlocked is if someone reverse engineers the bootloader software, creating an unlocked version that can be flashed, and that will still pass the phone's security checks. I wouldn't hold your breath for it though, because it's been 3 years and no solution yet.
i had same issues
i have been trying to unlock my s6 smg 9208 everything that i tried failed need really your help i can't use my keyboard and mouse ????
Most Samsung phones are unlocked, Only a small percentage of Samsung phones has locked bootloaders. Just pop a different carrier SIM and make sure it works, If different sims work then your device has an unlocked bootloader.
mzayd786 said:
Most Samsung phones are unlocked, Only a small percentage of Samsung phones has locked bootloaders. Just pop a different carrier SIM and make sure it works, If different sims work then your device has an unlocked bootloader.
Click to expand...
Click to collapse
That is incorrect, what you are referring to is carrier locked. and is done to most phones sold in the US. Most can be unlocked once fully paid for and after 90 days of service.
Bootloader lock has nothing to do with sim cards at ALL!! It does have everything to do with being able to install other roms and firmware via non official sources.
Sprint Samsung Galaxy S6 model SM g920p FRP lock is blocking me from enabling OEM unl
koop1955 said:
Go to Settings - About Device - Build number. Tap on that repeatedly until you see that Developer Options has been enabled.
Go back to Settings. You will now see a new entry called Developer options. Tap on that.
Under Developer options you will see OEM Unlock. Switch that to On.
And you are done! Just that easy!
Click to expand...
Click to collapse
Hello to you super techs I'm a newbie to this hope i'm not posting out of place but my question is how do I set up my Windows PC with ADB to use ADB fastboot unlock to unlock my bootloader because FRP protection has me locked out of the phone and I can't use the build number 2 unlock OEM or is that even possible I have been searching the web and XDA 2 try and find a way to open this phone I bought for myself for Christmas not knowing anything about a phone being FRP locked to a Google account is it possible to unlock this phone so that I can Flash it and maybe be able to use it I checked the IMEI number and it comes back good so say Sprint customer service but they couldn't help me with the FRP because I bought the phone second hand could you guys please point me in the right direction if I'm in the wrong spot posting my apologies to the thread host
Hi!
New here, hope I am in the right place...I have limited tech skills (born pre cell phones and computers) I did manage to install a custom ROM on an old HTC years ago, and thought I could do it again!
I have a Samsung A10e (SM-A102U) locked to sprint.
I can get the developer options but can't get the OEM unlock option. I also can't wait 7 days. Have tried a few things with the date and turning off updates etc, nothing worked. Here is what I am trying to do in order (please correct me if it is the wrong order) Ultimately I want my phone unlocked for use with any sim, and install a custom rom, to remove some bloatware. Could I wipe the phone totally take it to a piece of memory with no ROM and then re-load it, or use ADB to do it? Please excuse my ignorance - if I sound clueless I kinda am!
1. Unlock the bootloader
2. Install TWRP
3. Install custom ROM
It has taken me days of searching but to no avail, literally pulling my hair out. Happy to buy a beer for anyone that helps!
Wow,thanks...
Response has been overwhelming...
SandsCayman said:
Hi!
New here, hope I am in the right place...I have limited tech skills (born pre cell phones and computers) I did manage to install a custom ROM on an old HTC years ago, and thought I could do it again!
I have a Samsung A10e (SM-A102U) locked to sprint.
I can get the developer options but can't get the OEM unlock option. I also can't wait 7 days. Have tried a few things with the date and turning off updates etc, nothing worked. Here is what I am trying to do in order (please correct me if it is the wrong order) Ultimately I want my phone unlocked for use with any sim, and install a custom rom, to remove some bloatware. Could I wipe the phone totally take it to a piece of memory with no ROM and then re-load it, or use ADB to do it? Please excuse my ignorance - if I sound clueless I kinda am!
1. Unlock the bootloader
2. Install TWRP
3. Install custom ROM
It has taken me days of searching but to no avail, literally pulling my hair out. Happy to buy a beer for anyone that helps!
Click to expand...
Click to collapse
I have the exact same question.
it will not happen alot of us based carriers will lock down the phone via bootloader our best option is to find combination firmware and hopefully find root that way assuming that method still works.
Same situation here with Verizon. And sorry to tell you but I don't think anything will happen for you after seven days either, at least nothing did for me. I've spent a long time trying to get past this with no success, trying every trick I've found (the changing the date manually trick, factory resetting and trying on WiFi, etc.).
Also, using the app "Settings Database Editor," I've found the config/property where OEM bootloader unlock has been disabled:
"sys.oem_unlock_allowed" "0"
Screenshot here.
I'm hoping maybe we can edit that property via ADB or something. I'm not really holding out any hope here though. :-/
One other random discovery (not really helpful or relevant for our OEM bootloader unlock goal, but something I discovered while trying to obtain unlock): I believe I discovered a firmware error (at least on the Verizon build). When you hold volume up + power together for about 30 seconds, the phone shows the recovery menu for a split second but then instantly/immediately wipes all data and factory resets, without ever allowing the user to choose their own recovery menu selection and without giving any reset confirmation prompt before instantly wiping all user data. It's not supposed to work that way, according to the phone's user manual/Samsung technical support instruction. It's actually really pissed me off because I've triggered this instant reset twice now by accident just by having the phone in my back pocket and sitting down. I go to pick up my phone from my pocket and notice the screen is on and then discover everything was wiped. Very annoying! I called Samsung customer support twice to try to explain that I believe there to be a firmware error present (at least on Verizon models) but they didn't seem to care/their support script told them to have me take the device to some local authorized third-party screen repair place. One good outcome I've discovered from factory resetting the phone is that you can at least avoid enrolling the phone in part of the Knox security crap, the "kme" protection. I originally couldn't use remote apps like TeamViewer or AnyDesk without some stupid "Protected by Knox" notification popping up and then my remote app instantly exiting. Made me so angry. But now I'm able to use those apps without any issue. Though, the phone does try to have me agree to enroll in kme protection or whatever about once a day and I have to manually close the enrollment agreement form that pops up.
allenjthomsen said:
it will not happen alot of us based carriers will lock down the phone via bootloader our best option is to find combination firmware and hopefully finwww reset that way assuming that method still works.
Click to expand...
Click to collapse
I've had the same issue with entire A series. All OEM's are disabled regardless of carrier. It seems to be part of Samsung's firmware. After nothing but dead ends and contacting samsung directly i was left scratching my head. Came here searching for some insights I may have overlooked.
-Enable developer options
-Enable wifi
-Join a network
-Change date to 10 days forward
-Reboot phone
-OEM unlock will be available
Thank me later
moe7863 said:
-Enable developer options
-Enable wifi
-Join a network
-Change date to 10 days forward
-Reboot phone
-OEM unlock will be available
Thank me later
Click to expand...
Click to collapse
Nothing happens/doesn't work for Verizon. :-/
I mentioned having tried this technique already in my previous post above.
---------- Post added at 07:42 PM ---------- Previous post was at 07:38 PM ----------
For what it's worth, here's a sister thread I started on this topic with a few responses/potential bootloader unlock ideas shared by other members but no real solid progress made at this point:
https://forum.xda-developers.com/galaxy-a10/help/samsung-galaxy-a10e-to-t3990817/page4
the bl is not unlockable
Bump
I know this is possible I've seen it done before. I think it had to do with a modified ota update.
SHAD0WUSER said:
Bump
I know this is possible I've seen it done before. I think it had to do with a modified ota update.
Click to expand...
Click to collapse
Do you have proof of this being done?
Because as far as I'm aware, it's been impossible to unlock bootloader for years
I actually purchased this phone from Metro last week after searching for it on XDA and seeing that is was BL unlockable. I didn't realize any the time that this was only the international variants. Good luck to all devs whose skillset is better than my own.
ShaDisNX255 said:
Do you have proof of this being done?
Because as far as I'm aware, it's been impossible to unlock bootloader for years
Click to expand...
Click to collapse
it is not possible.. also u cant flash a modified ota cuz it will fail sig check
nateberhardt81 said:
I actually purchased this phone from Metro last week after searching for it on XDA and seeing that is was BL unlockable. I didn't realize any the time that this was only the international variants. Good luck to all devs whose skillset is better than my own.
Click to expand...
Click to collapse
if u looked u would have seen the model numbers are different
elliwigy said:
if u looked u would have seen the model numbers are different
Click to expand...
Click to collapse
Yeah... I I knew better than to just look at a10e and assume they were all the same. I went through the same struggle with a J7 not too long ago... Should have learned my lesson then.
nateberhardt81 said:
Yeah... I I knew better than to just look at a10e and assume they were all the same. I went through the same struggle with a J7 not too long ago... Should have learned my lesson then.
Click to expand...
Click to collapse
no biggie.. at least those r super cheap.. i got a a50 just to brick it to try an exploit that didnt work lol.. o well
I have an A10e as well but the model number is SM-S102DL, I am a complete novice when it comes t phones but will I be able to root this without unlocking the bootloader?
xSpookyx said:
I have an A10e as well but the model number is SM-S102DL, I am a complete novice when it comes t phones but will I be able to root this without unlocking the bootloader?
Click to expand...
Click to collapse
no.. are u sure u have a a10e?
you cant root without exploits that dknt exist without unlocking the bootloader
No matter about root. but I converted many of Samsung A10e to international variant to remove any boost metropcs or any other networks bloatware application.
you can also do it without any issue. Simply flash A102U1 Firmware. I m not sure that it will work on Network Locked/Sim locked devices. I flash and convert it after using a remote unlocking service which already changed the CSC version of EFS to XAA from the BST csc...
XAA is for US Unlocked Without carrier locked phones and BST for Boost mobile carrier only which came with lots of boost bloatwares but maybe that A10e boost remote unlock service saved me.
check the screenshot attached.
Shabby The Dev said:
No matter about root. but I converted many of Samsung A10e to international variant to remove any boost metropcs or any other networks bloatware application.
you can also do it without any issue. Simply flash A102U1 Firmware. I m not sure that it will work on Network Locked/Sim locked devices. I flash and convert it after using a remote unlocking service which already changed the CSC version of EFS to XAA from the BST csc...
XAA is for US Unlocked Without carrier locked phones and BST for Boost mobile carrier only which came with lots of boost bloatwares but maybe that A10e boost remote unlock service saved me.
check the screenshot attached.
Click to expand...
Click to collapse
Careful, don't post your IMEI on the internet as some bad people can do stuff with it
Samsung A02s(SM-A025F)
I do these steps any body help
1.I unlock oem through developer option
2.I unlock bootloader successfully
3.I downloaded firmware and patch AP with magisk to root
4.I flash Patched AP
5.After getting my phone rooted successfully I want to install TWRP Recovery
6.I downloaded unofficial version of TWRP from xdaforums....
7.I followed the steps guided here
The steps are as follows
1.reboot to boot loader and flash vbmeta_disable.tar
2.Put TWRP tar in AP and flash
3.Reboot to recovery
4.Disable encryption
Go to Advanced >Terminal : type "multidisabler"
5.Go back to wipe>Format Data>type "yes"
6.Reboot system
This is my first experience to root and flash TWRP.... but after that when I reboot my phone got lock .... only official binaries allowed to be installed....and stuck there
I got frightened so I locked my bootloader
But nothing happens...
I downloaded stock firmware and flash.....now my phone works perfectly But I want to root my phone I searched and found a correct way to root but now oem unlock option is not found in developer options....
I watched hundreds of videos on yt and searched a lot on Google but
found no proper solution.....someone tell me to wait 7 days....
In about phone> phone status>uptime
Uptime should be equal to 7days... then oem unlock option will appear but ...... I want another solution date change and WiFi connect is not solution ... If any body knows any other solution please guide me ... I'll be very thankful.....
@ladlabaloch512
Perhaps your device has the same "OEM unlock" block like mine.
On mine I was supposed to wait 7d after turning on dev options.
I bypassed that by
1. switching to airplane mode
2. Setting manually date back one month
3. Restart (still in airplane mode)
4. Turning off airplane mode and let it sync date
and voila OEM unlock option was there.
Perhaps that works on your device as well.
bmwdroid said:
@ladlabaloch512
Perhaps your device has the same "OEM unlock" block like mine.
On mine I was supposed to wait 7d after turning on dev options.
I bypassed that by
1. switching to airplane mode
2. Setting manually date back one month
3. Restart (still in airplane mode)
4. Turning off airplane mode and let it sync date
and voila OEM unlock option was there.
Perhaps that works on your device as well.
Click to expand...
Click to collapse
Thanks for reply...
This bypass method doesn't work in my device
Im too
i have tried everything But I read on somewhere that policy was upgrade to 1000 hours so i waited and hopping thats work!
Now it's almost 700 and i restarted before it on 200 so it's supposed to be 900
Mahmoudm.kamal said:
Im too
i have tried everything But I read on somewhere that policy was upgrade to 1000 hours so i waited and hopping thats work!
Now it's almost 700 and i restarted before it on 200 so it's supposed to be 900
Click to expand...
Click to collapse
Keep us updated.. I'd like to get my OEM unlock to come out of hiding.. this is frustrsting.. i see all these tutorials for the A02s root, twrp and ROMs and whatnot and I'm itching to get flashing!
Is it possible to flash an unlocked carrier firmware in ODIN and then be able to unlock OEM? Without carrier issues or anything? I'm a little nervous to be the first to try.. and not sure where to find US unlocked carrier firmware or if location even matters... I have the SM-A025AZ (US Cricket variant).. I guess as long as Download Mode (fastboot) is still accessible I could just flash the Cricket version back to the device.. bricked my LG-E980 back in the day.. took me a few months how to get it back up and running with LG flash tool.. i just dont want to repeat that fiasco lol... so anybody got any updates on hacking this OEM (un)lock bs??? Or any idea on flashing some other variant to the device without interrupting carrier stuff??.. seems like alot just to get a damn virtual switch to turn on.. but damnit I need root access! Lol.. about to just exchange this phone for an actual rootable phone.. i disagree with charging for hotspot.. that should be illegal.. getting charged twice to use th same bs internet.. eff that.. i just want Rooooooot!!!
Hello,
I have also been having these troubles, with no way to unlock oem after stock flash, and the closest I've got to finding a solution was this, but I simply cannot find samsung's bootloader unlocking form like it says in the guide. I bought my phone just for a bootloader unlockable version (A025M), and now I am very angry at samsung.
also, since over a 1000 hours have gone by since last post, have any one of you solved this issue just by waiting?
Noobiu said:
Hello,
I have also been having these troubles, with no way to unlock oem after stock flash, and the closest I've got to finding a solution was this, but I simply cannot find samsung's bootloader unlocking form like it says in the guide. I bought my phone just for a bootloader unlockable version (A025M), and now I am very angry at samsung.
also, since over a 1000 hours have gone by since last post, have any one of you solved this issue just by waiting?
Click to expand...
Click to collapse
Nope, More than 2000 hours and also changed firmwares and waited again an again and tried alot of ways but enable oem still disappeared
Im also very angry from samsung
Mahmoudm.kamal said:
Nope, More than 2000 hours and also changed firmwares and waited again an again and tried alot of ways but enable oem still disappeared
Im also very angry from samsung
Click to expand...
Click to collapse
its not only samsung that does this, many other companies like motorola does this. Dont be angry, just try a different device. Also, snapdragon US models (i dont think) arent able to be unlocked. If its a mediatek model and isnt sim/carrier locked, u can try MTKClient
Swyen said:
its not only samsung that does this, many other companies like motorola does this. Dont be angry, just try a different device. Also, snapdragon US models (i dont think) arent able to be unlocked. If its a mediatek model and isnt sim/carrier locked, u can try MTKClient
Click to expand...
Click to collapse
Yes dear, i had changed it since more than 7 months with A52S , thanks.
Mahmoudm.kamal said:
Yes dear, i had changed it since more than 7 months with A52S , thanks.
Click to expand...
Click to collapse
And, my A037W doesnt have the OEM Unlock option. Use an MTK tool to unlock it, thats how I did it
ewrecc said:
Is it possible to flash an unlocked carrier firmware in ODIN and then be able to unlock OEM? Without carrier issues or anything? I'm a little nervous to be the first to try.. and not sure where to find US unlocked carrier firmware or if location even matters... I have the SM-A025AZ (US Cricket variant).. I guess as long as Download Mode (fastboot) is still accessible I could just flash the Cricket version back to the device.. bricked my LG-E980 back in the day.. took me a few months how to get it back up and running with LG flash tool.. i just dont want to repeat that fiasco lol... so anybody got any updates on hacking this OEM (un)lock bs??? Or any idea on flashing some other variant to the device without interrupting carrier stuff??.. seems like alot just to get a damn virtual switch to turn on.. but damnit I need root access! Lol.. about to just exchange this phone for an actual rootable phone.. i disagree with charging for hotspot.. that should be illegal.. getting charged twice to use th same bs internet.. eff that.. i just want Rooooooot!!!
Click to expand...
Click to collapse
STOP TRYING TO UNLOCK A US DEVICE ITS NOT POSSIBLE
Swyen said:
And, my A037W doesnt have the OEM Unlock option. Use an MTK tool to unlock it, thats how I did it
Click to expand...
Click to collapse
Which tool did you use?
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?