Database Develop

Help remove Retail Mode Samsung Tab S2 SM-T810

Hi to everyone. I have a Samsung Tab S2 SM-T810 with Android 5.1.1 / Kernel 3.10.9 that has retail mode on, it was a demo in a store. Is there anyway to remove this from the device? I already try doing a factory reset with stock firmware and odin and it stills the same. I think it has some kind of software installed on the ROM memory that prevents it to fully restore and wipe the retail mode app. Thanks in advance.

Please do a search this has been covered plenty of times already. There is no need to repeat over.

ashyx said:
Please do a search this has been covered plenty of times already. There is no need to repeat over.
Click to expand...
Click to collapse
I did it. that's why I specified re installing with odin didnt help. I checked all the forum. even this http://forum.xda-developers.com/galaxy-tab-s/help/samsung-galaxy-tab-s-sale-version-t2890171
and it stills the same.

huntejes said:
I did it. that's why I specified re installing with odin didnt help. I checked all the forum. even this http://forum.xda-developers.com/galaxy-tab-s/help/samsung-galaxy-tab-s-sale-version-t2890171
and it stills the same.
Click to expand...
Click to collapse
It's simple, make sure OEM unlock is enabled in developer settings, Install twrp, factory reset with twrp, boot to download then flash stock Firmware.
Done.

ashyx said:
It's simple, make sure OEM unlock is enabled in developer settings, Install twrp, factory reset with twrp, boot to download then flash stock Firmware.
Done.
Click to expand...
Click to collapse
I wouldn't be asking for help if it were that easy. I tried doing that too. All the option in the developer settings tab are gray. I can't change them. The retail app is blocking it.
Any other idea ?

huntejes said:
I wouldn't be asking for help if it were that easy. I tried doing that too. All the option in the developer settings tab are gray. I can't change them. The retail app is blocking it.
Any other idea ?
Click to expand...
Click to collapse
Just go ahead and install twrp and continue with the previous instructions. If you get the FRP block, just flash the stock Firmware.
Also if you carry on with the attitude you're on your own.

ashyx said:
Just go ahead and install twrp and continue with the previous instructions. If you get the FRP block, just flash the stock Firmware.
Also if you carry on with the attitude you're on your own.
Click to expand...
Click to collapse
Excuse me, I didn't mean to offend. I'll try to install twrp right now.
As I expected while I was trying to install twrp it always return an error on Odin so I gave up, then after a couple of hours the table ran out of battery and since it was the first time it went off without the retail app monitoring. I decide to boot it into download mode. and that's it.
After that the twrp finally got installed and I erased everything on the tab. after that that it got stuck on the samsung logo. And I could install the stock firmware with no problem.
All thanks to you.

Ok so ive got the Sm-810 and i was experiencing the same issue of it not letting odin flash to stock OR install twrp etc. etc. and i was going to give up and i **** you not i was trying to get into the recovery to see if i could jostle some solution loose and it fixed itself !! It was booted into download mode and i unplugged the cable and pressed and held power+vol down and as soon as the screen went black i did the same thing again and then i mustve messed up cuz it booted into the os but i repeated the process from there and no kidding after 2 or 3 cycles of power+vol down i got a blue screen with an android on it and it flashed and showed a dead android with the caution! sign and the next screen showed the regular android with the word "erasing" underneath and vio'la no more retail mode. After this Odin worked and let me autoroot and so on an so forth. sorry for my long post i just though i should share

I think the major issue is that OEM is disabled and there is no way to turn it on. So most of the solutions are a no go... So any other suggestions on make this work?

huntejes said:
Excuse me, I didn't mean to offend. I'll try to install twrp right now.
As I expected while I was trying to install twrp it always return an error on Odin so I gave up, then after a couple of hours the table ran out of battery and since it was the first time it went off without the retail app monitoring. I decide to boot it into download mode. and that's it.
After that the twrp finally got installed and I erased everything on the tab. after that that it got stuck on the samsung logo. And I could install the stock firmware with no problem.
All thanks to you.
Click to expand...
Click to collapse
Hi huntejes,
I've a SM-T650NU unit and have the same issue you faced on the Odin step (of course I'm using the specific TWRP file for my unit) just want to know what error showed up. In my case it returned: FAIL! (Auth).
Will let the battery fully drain and after that repeat the TWRP flash. Do you remember (step by step) what you did after the battery drained? I mean charged to 30% then put on download mode? Any feedback will be appreciated.
BR\

My husband and I also ran into the problem of having our Samsung Tablet E nook 2017 model stuck on Retail Mode.. we tried EVERYTHING we could possibly think of after the 5444 password didn't work. We rooted, we downloaded "easy uninstalled" apps, did the hard reset with the 3 button deal.. nothing! Then we finally came across a few passwords we were willing to give a try.. so when you go to the retail mode bar and it prompts you for a password to uninstall try blue. The word BLUE but in lowercase.. and it worked! We were then given tons of options and finally got that crap off our paid for device. I'm 100% sure that any device purchased from Best Buy and stuck in retail mode will use the password blue. A few other passwords we came across that might be worth a shot if blue doesn't work are: galaxy and unlimited. (Each by themselves as one password) Well good luck, we know how frustrating this has been!!

Skapino said:
Hi huntejes,
I've a SM-T650NU unit and have the same issue you faced on the Odin step (of course I'm using the specific TWRP file for my unit) just want to know what error showed up. In my case it returned: FAIL! (Auth).
Will let the battery fully drain and after that repeat the TWRP flash. Do you remember (step by step) what you did after the battery drained? I mean charged to 30% then put on download mode? Any feedback will be appreciated.
BR\
Click to expand...
Click to collapse
Dude, I have a SM-t560nu and I feel your pain. For months I was trying to find a solution and had to deal with obnoxious fools who couldn't get it thru there heads that this was NOT the usual Samsung Retail Mode but a special piece of software that puts the tablet into a rolling cycle of 2-10 minutes, shuts off all developer options, locks frp and basically makes anything you do null and void. I tried every password Imaginable including "BLUE," "5444" and the oft repeated "M729Q16K8546" all to no avail.
Here's the deal: this IS unique software and you'll find it at retailsamsung.com. (I can't post the actual url because of the new user rules, which is kind of funny because I've been a member for about 10 years but I don't think I've ever posted anything.)
Go there, search your device and download 2 items: One will be your installation package (for instance "Samsung_Retailmode_Global_Common _141006.apk") and the other will be called "RetailMedia.main." Download both to na sd card, put the sd card in your device, move the programs from the sd card to the download area ON the device. Now start your device, got to the download area and tap on the first program, the apk. Enter 5444 as your password, follow the instructions. the second password will be "M729Q16K8546." This will remove the Retailmode software and most likely trigger a Samsung lock. Go to Sammobile, download the original firmware and congrats, your new tablet is finally working right.
I was wary of downloading software from such a plain site, especially one I've never heard of but I figured after 6 months of no luck and my new tablet just sitting in a drawer, unusable, what did I have to lose? Well, it works, i'ts awesome and it's like new.
Hope this helps.

Mfb5159, You Are Awesome! A friend entrusted me to remove the Retail Mode from her Samsung Galaxy Tab A 9.7. I tried Everything. The passwords that can be found everywhere online, circumventing the FVP (of course that was useless), downloaded & installed the firmware with Odin in download mode... nothing. Then I ran across this forum. Tried two versions of retail mode from RetailSamsung.com and the second one worked. I had to open the retail app I installed, enter the generic passwords (5444 & the M729Q16K8546), then it gave me the option to factory reset the device. I chose yes & it worked! No sign of Retail Mode on the tablet. It's like a brand new tablet!! The .apk file that worked for me was SamsungRetailMode_GlobalCommon_141006
Thank you So Much for your help.

I hope I'm not posting on a dead thread. I saw a good deal on a T813 in retail mode (will provide link if needed, it's on a very popular and legal south american online store). The thing is, as explained by the vendor, someone attempted to remove the retail app and now is stuck on a countdown in the lock screen. After some time it reboots itself. I've been reading a lot about the topic and the main problem seems to be the OEM unlock off. Now apparently I won't be able to access any feature of the device at all. I thought maybe I could reinstall the retail mode and get back the app or just boldly odin flash twrp and a stock rom risking myself to an FRP lock.
However I thought better ask advice first, so what do you think? Any help is greatly appreciated.

Well, I bought it and first day has been no success. I can access guest user, could log in to my ggl account and downloaded some apps. OEM, third party apps and developers are out of reach and cannot access main account. No sign of retail app.
Flashed new stock rom, FRP asks for a password, tryed 5444 Mz$%"#$%& blue galaxy unlimited with no luck. Attempts to flash twrp via odin fail due qst (?) error. I guess because is OEM locked. Flashed some older rom and still a countdown that doesn't let me in in main account.
So far, this is my progress with it. Any advice to flash twrp, remove frp lock and/or remove retail mode? Thanks in advance

_Iffer_ said:
Mfb5159, You Are Awesome! A friend entrusted me to remove the Retail Mode from her Samsung Galaxy Tab A 9.7. I tried Everything. The passwords that can be found everywhere online, circumventing the FVP (of course that was useless), downloaded & installed the firmware with Odin in download mode... nothing. Then I ran across this forum. Tried two versions of retail mode from RetailSamsung.com and the second one worked. I had to open the retail app I installed, enter the generic passwords (5444 & the M729Q16K8546), then it gave me the option to factory reset the device. I chose yes & it worked! No sign of Retail Mode on the tablet. It's like a brand new tablet!! The .apk file that worked for me was SamsungRetailMode_GlobalCommon_141006
Thank you So Much for your help.
Click to expand...
Click to collapse
Did the same, although I had to use the older ap_SamsungRetailMode_Global_Tab_A_L_v1.0.4_15031100_M15031100_P0.apk with my SM-T550 (Galaxy Tab A (2016) 9.7") - I also had to stop the existing RetailMode Service from running by opening applications, swipe across to Running Applications, and tap on the Retail Mode executables to disable the "Sta" service. Annoyingly if you accidentally get the password wrong then it'll reset itself and delete the newer APK and you have to start the whole process over again

Could anyone at least point me in the right direction please? I can't access the main user of the tablet because there's a lock on the screen saying "Try again in 1440 minutes" which is a day. It self reboots every 5 minutes and each time the 1440 minutes thing resets. I booted in safe mode, now it doesn't reset and countdown is set for the next 4 hours.
Please, any light on the matter will be great. I have 4 days to return and I wouldn't like to do it cause it was extremely cheap unless, but I don't want to end with an expensive brick either.

Huntejes,
I had the same experience as you with my SM T810. The particular version of the Samsung Retail app (com.samsung.sta.retailagent.lite 6.9.20161101) installed on my unit didn't have a 'configuration settings' option; instead an option called 'Store Settings' prompted a password entry - but admin passwords 5444, blue, galaxy, unlimited all failed.
So then I went the Odin/flash stock firmware route. Unfortunately, despite two rounds of that, the Retail Mode application and restrictions remained. However, what did arise from this seemingly pointless process was the ability to enable installation of third party apps under Settings - all other admin access and functions (i.e. factory reset, program uninstallation, etc.) remained under the restricted control of Retail Mode. I went through that process about a year ago, assuming I had failed - the restrictions remained, and I was out of ideas/options.
Two days ago, I decided to revisit the problem, having to reeducate/remember what I had done previously along the way. Eventually, I came up with a novel workaround that hadn't occurred to me before - side-loading an apk file containing a different version of the Retail Mode software. Ironically, this worked. After installing and running the alternative Retail Mode app, using admin password 'blue' I was able to uninstall the original (i.e. problem) Retail Mode app, enable factory restore, and execute a complete wipe, which was successful.
I know this thread has been silent for a while, but it was one of only two threads that I thought took the larger conversation beyond the first basic step and I thought that contributing to it would be a small way to express my thanks.
Cheers.
---------- Post added at 04:56 PM ---------- Previous post was at 04:46 PM ----------
It now seems that others (SeriousEion) have used the approach I mentioned above to successfully bypass Retail Mode in several of the most troublesome cases - it's very interesting to me that this thread only reactivated last month after having gone dark by the time I came across it in 2016.
---------- Post added at 05:08 PM ---------- Previous post was at 04:56 PM ----------
It now seems that others, namely mfb5150's post from 20-07-2017, have used the approach I mentioned above to successfully bypass Retail Mode in several of the most troublesome cases - I can confirm that the approach he outlines also works for the Samsung Galaxy Tab S2 (SM T810) using the apk files available from samsungretail.com
So thank you, mfb5150, for your post - had I seen it earlier you might have saved me an hour or two of trial and error. It's interesting to me that this thread has finally reactivated after having gone dark by the time I came across it back in 2016. I'm not a developer, and have no programming/coding experience, so I hope that this thread continues to be a resource for any others like me out there.

Hi guys,
I have a galaxy tab and sm-t561, which presents the problem of retail mode that you can not remove in any way even with odin, I wanted to ask, how do I install a version of retail mode via apk? I downloaded the new version of retail mode but how do I install it?

whchapma said:
Huntejes,
I had the same experience as you with my SM T810. The particular version of the Samsung Retail app (com.samsung.sta.retailagent.lite 6.9.20161101) installed on my unit didn't have a 'configuration settings' option; instead an option called 'Store Settings' prompted a password entry - but admin passwords 5444, blue, galaxy, unlimited all failed.
So then I went the Odin/flash stock firmware route. Unfortunately, despite two rounds of that, the Retail Mode application and restrictions remained. However, what did arise from this seemingly pointless process was the ability to enable installation of third party apps under Settings - all other admin access and functions (i.e. factory reset, program uninstallation, etc.) remained under the restricted control of Retail Mode. I went through that process about a year ago, assuming I had failed - the restrictions remained, and I was out of ideas/options.
Two days ago, I decided to revisit the problem, having to reeducate/remember what I had done previously along the way. Eventually, I came up with a novel workaround that hadn't occurred to me before - side-loading an apk file containing a different version of the Retail Mode software. Ironically, this worked. After installing and running the alternative Retail Mode app, using admin password 'blue' I was able to uninstall the original (i.e. problem) Retail Mode app, enable factory restore, and execute a complete wipe, which was successful.
I know this thread has been silent for a while, but it was one of only two threads that I thought took the larger conversation beyond the first basic step and I thought that contributing to it would be a small way to express my thanks.
Cheers.
---------- Post added at 04:56 PM ---------- Previous post was at 04:46 PM ----------
It now seems that others (SeriousEion) have used the approach I mentioned above to successfully bypass Retail Mode in several of the most troublesome cases - it's very interesting to me that this thread only reactivated last month after having gone dark by the time I came across it in 2016.
---------- Post added at 05:08 PM ---------- Previous post was at 04:56 PM ----------
It now seems that others, namely mfb5150's post from 20-07-2017, have used the approach I mentioned above to successfully bypass Retail Mode in several of the most troublesome cases - I can confirm that the approach he outlines also works for the Samsung Galaxy Tab S2 (SM T810) using the apk files available from samsungretail.com
So thank you, mfb5150, for your post - had I seen it earlier you might have saved me an hour or two of trial and error. It's interesting to me that this thread has finally reactivated after having gone dark by the time I came across it back in 2016. I'm not a developer, and have no programming/coding experience, so I hope that this thread continues to be a resource for any others like me out there.
Click to expand...
Click to collapse
i just follow your instructions and awesome mine is unlock now and downloading the update to android 7.0 thanks bro

SM-T817V Firmware nowhere to be found?

I work with a private computer repair company and we often refurbish devices, like older computers and monitors. I'm attempting to refurbish an older Samsung Galaxy S2 tablet with Verizon a customer brought in, but FRP is preventing our factory reset. We've attempted calling and emailing the customer for that login information but they aren't responding, so we need to reflash the firmware. Is there anywhere we can get SM-T817V firmware? Also, if we can't find that specific firmware, i there any other version of firmware we can put on it that won't cause too many issues? We don't absolutely need LTE on the tablet, but keeping it would be a huge plus.

Iridix said:
I work with a private computer repair company and we often refurbish devices, like older computers and monitors. I'm attempting to refurbish an older Samsung Galaxy S2 tablet with Verizon a customer brought in, but FRP is preventing our factory reset. We've attempted calling and emailing the customer for that login information but they aren't responding, so we need to reflash the firmware. Is there anywhere we can get SM-T817V firmware? Also, if we can't find that specific firmware, i there any other version of firmware we can put on it that won't cause too many issues? We don't absolutely need LTE on the tablet, but keeping it would be a huge plus.
Click to expand...
Click to collapse
It depends on the reason frp has kicked in. Does download mode state any of the partitions are custom or is the device status official?
---------- Post added at 11:23 PM ---------- Previous post was at 11:09 PM ----------
Iridix said:
I work with a private computer repair company and we often refurbish devices, like older computers and monitors. I'm attempting to refurbish an older Samsung Galaxy S2 tablet with Verizon a customer brought in, but FRP is preventing our factory reset. We've attempted calling and emailing the customer for that login information but they aren't responding, so we need to reflash the firmware. Is there anywhere we can get SM-T817V firmware? Also, if we can't find that specific firmware, i there any other version of firmware we can put on it that won't cause too many issues? We don't absolutely need LTE on the tablet, but keeping it would be a huge plus.
Click to expand...
Click to collapse
It depends on the reason frp has kicked in. Does download mode state any of the partitions are custom or is the device status official?

ashyx said:
It depends on the reason frp has kicked in. Does download mode state any of the partitions are custom or is the device status official?
---------- Post added at 11:23 PM ---------- Previous post was at 11:09 PM ----------
It depends on the reason frp has kicked in. Does download mode state any of the partitions are custom or is the device status official?
Click to expand...
Click to collapse
FRP kicked in I can only assume because the original owner didn't properly reset the device. The current owner came in and stated it was like that when he bought it. When opening in download mode, it does state the device status as official.

Iridix said:
FRP kicked in I can only assume because the original owner didn't properly reset the device. The current owner came in and stated it was like that when he bought it. When opening in download mode, it does state the device status as official.
Click to expand...
Click to collapse
In recovery mode what does it state is the current firmware build?

ashyx said:
In recovery mode what does it state is the current firmware build?
Click to expand...
Click to collapse
In Odin mode:
Download speed: FAST
Product name: SM-T817V
Current binary: SAMSUNG OFFICIAL
System status: OFFICIAL
FRP Lock: ON
Secure download: Enabled
RP SWREV: B:2 K:0 S:0
Android Recovery (From top to bottom):
Verizon/gts210ltevzw/gts210ltevzw
7.0/NRD90M/T817VVRU2DQE1

I've tried different sites like Sammobile, Updato, and AndroidMTK. Only Updato has the file, but it's blocked behind a user account wall which isn't sending me an email. The other two don't have it at all. I'm skeptical that anywhere has it.

Iridix said:
I've tried different sites like Sammobile, Updato, and AndroidMTK. Only Updato has the file, but it's blocked behind a user account wall which isn't sending me an email. The other two don't have it at all. I'm skeptical that anywhere has it.
Click to expand...
Click to collapse
You either need the combo firmware or an eng boot. Neither of which seem to be available without payment.
The other option is to try one of the FRP bypass tricks.

ashyx said:
You either need the combo firmware or an eng boot. Neither of which seem to be available without payment.
The other option is to try one of the FRP bypass tricks.
Click to expand...
Click to collapse
Which of those tricks do you suggest?

Iridix said:
Which of those tricks do you suggest?
Click to expand...
Click to collapse
I can't recommend one, but you will find them on Google. They do work.
https://www.youtube.com/watch?v=-tI...IwAHoECAcQAQ&usg=AOvVaw3l1hlLK_t6mCf53D6HPFrR

ashyx said:
I can't recommend one, but you will find them on Google. They do work.
https://www.youtube.com/watch?v=-tI...IwAHoECAcQAQ&usg=AOvVaw3l1hlLK_t6mCf53D6HPFrR
Click to expand...
Click to collapse
The video you recommended is in Spanish, which isn't necessarily a problem. The problem is the tool he says to use doesn't work anymore (the download link is broken, taken down by MediaFire's TOS). If you've got any other suggestions, I'd be glad to consider them.

Iridix said:
The video you recommended is in Spanish, which isn't necessarily a problem. The problem is the tool he says to use doesn't work anymore (the download link is broken, taken down by MediaFire's TOS). If you've got any other suggestions, I'd be glad to consider them.
Click to expand...
Click to collapse
Like I say I can't recommend one, just got to try them. However the methods are pretty generic and I have used the method below successfully on a completely different device:
https://m.youtube.com/watch?v=a-A-poRZPzY

That one doesn't work either. I'm currently running the device on Android 7.0 and I've found a way to get into Settings. All I need to do is find a way to get into developer options and I'm golden. But, I can't do that. If anyone can help find a way to do that, it'd be wonderful.

Iridix said:
I work with a private computer repair company and we often refurbish devices, like older computers and monitors. I'm attempting to refurbish an older Samsung Galaxy S2 tablet with Verizon a customer brought in, but FRP is preventing our factory reset. We've attempted calling and emailing the customer for that login information but they aren't responding, so we need to reflash the firmware. Is there anywhere we can get SM-T817V firmware? Also, if we can't find that specific firmware, i there any other version of firmware we can put on it that won't cause too many issues? We don't absolutely need LTE on the tablet, but keeping it would be a huge plus.
Click to expand...
Click to collapse
I had the same issue and bought the files you need to do it on Odin if I can locate them on my laptop. If you are are still in need of them let me know and I will see if they can be loocated

update ASUS TF701T (k00c) android to latest version

Hi All.
I trust you well. I was wondering if I could request your assistance with updating my TF701T to a new version of android. I have tried many methods and none has worked. I am actually more confused now as to where to start and what to download and install. :silly:
If possible maybe direct me where I could get a step by step guide with the links to the correct downloads/procedure.
I imported the pad from USA to South Africa and barely used it.
Kind Regards
Rob

(h-tee-tee-pee-s) androidbiits.com/root-asus-transformer-pad-tf701t-easily/
probably use the versions of magisk + twrp that are linked at the site, as they are tested with that hardware -- the latest versions may not work. i do not own that particular device and am not a programmer -- just trying to help you out. search the web for info if anything is confusing in the instructions -- i can't really walk you through it, but the person at that site may be able to help you out if you get stuck.
you'll need to connect the asus pad to a computer, so you'll need the usb data cable & adb installed on the computer.
you will likely also need open gapps to get the play store + apps working. select processor type, android version, then variant. you can find it here ==> (h-tee-tee-pee-s) opengapps.org <== but i'm not sure how long that will be functional, as hosting is apparently migrating to sourceforge.
please note that there are no w's in either address mentioned previously.
here's an explanation of gapps ==> (h-tee-tee-pee-s + w's) androidfreeapks.com/apk/download-gapps-for-android/
...and there are also download links for various variations at that last address too. cheers!
you will not be able to install *the latest* version of android (it's just plain not out there as a mod for a device this old) but you *can* get something a bit newer than the stock version on it.
best of luck!

one last thing (pertaining to the very first thing you have to do) is unlock the bootloader.
(h...s + w's) asus.com/us/Tablets/The_New_ASUS_Transformer_PadTF701T/HelpDesk_Download/
you will find the utility to do so at the above site. select Android, then under "Utilities"
click "See All Downloads" - therein, the 2nd thing from the bottom in that section is the unlock tool,
which says: Unlock Device App. V1.o (there's only one thing with that name. size is 448.82 kb)
and it will only work from the stock Android version, which i assume is still functional on your device.
Magisk is apparently a newer replacement for SuperSU, which doesn't flag the system as altered...
therefore you *may not* need to install Gapps if using Magisk - that seems logical to me, but i am not certain.

thanks for the assistance Dorkus.........this is killing me....but I will keep the faith and try again

I am trying myself and cannot get the unlock tool to work, performed wipe data reset without google account and still "network error occurred" . Android version 4.4.2

bobwho said:
I am trying myself and cannot get the unlock tool to work, performed wipe data reset without google account and still "network error occurred" . Android version 4.4.2
Click to expand...
Click to collapse
Same here. I tried to contact Asus but no hope... We're completely blocked unless they do something? No other way to unlock?

greetings all, it is i, dorkus, of the house of mallorcus. haha. my name is actually reni.
xda keeps locking me out for some reason. i've now created 2 accounts (3 including the one from which this comment is posted) one even with a dedicated e-mail address just for this, but if i try to log in with either one, i get some "invalid" whatever message. admins: what have i said that was grossly incorrect? those links may not be presented in absolutely the most coherent way, but they're the best reasonable explanations of the procedure involved that i could find with about an hour or 2 of research, which i did because of intending to get one of these devices myself (which has now occurred! yay). besides that, who else with greater experience has chimed in on this thread? yes, i've reset my password, on both accounts. after i do so, both times: same "invalid" message. it's wasted over an hour of my time, when i'm just trying to help these people. it's highly annoying & if it continues, well, they'll just have to go it on their own.
to the point:
as luck would have it,
i was able to acquire one of these devices, still in superb condition, for a great deal from ebay. i have been in contact with Asus support & the word is: it's an EOL product, so the unlock servers have been shut down & there is currently no recourse end users have for unlocking their devices. i feel it's doubtful that they'll fire up a server again, but maybe we can pester them enough to develop a fastboot unlock tool? it sure would have been nice if it worked like that in the first place, but oh well, like the song says:
you can't always get what you want.
i will surely let you all know if am able to make any progress on unlocking my TF701T.
footnote: i also have a TF700 model which is in fact unlocked, has TWRP installed, and is running Android 5.1.1 {zombie-pop} which works a bit better than the Cyanogen mod flavor that it came to me with: somewhat improved user experience, maybe a little snappier too, but speed improvement is fairly minimal. most importantly, almost all of my apps work on it - a few don't even have an installer for Android 4 at the Play Store. the 701 is noticeably more responsive than the 700 model, even running 4.2.2 - the main issue with it for me is not being able to run all of my apps, some of which are purchased. i'd probably sell the 700 if i could get everything on the 701. oh well. it's an excellent reader + portable video viewing device even at stock. it's definitely worth what i paid in the condition received, but it'd be even better if i could unlock the bootloader & get a newer version of Android on it! i could possibly even be so happy that i'd float a couple bux Tim Duru's way, the guy primarily responsible for porting Android 6+7 (the latter of which apparently does not have a working camera) to this device.
footnote #2: the first day i got the 701, i tried to do a firmware update (proper region, latest available. full battery charge. the battery in the one i picked up is in fantastic condition, the thing is practically brand new + functions nicely... but now Asus won't let me unlock it, even though it's well out of warranty! grrrrr) which crashed mid-way & then it proceeded to get into an update / crash boot loop. i was pretty sad for a while, but did not give up & found a way to restore the original firmware (which turned out to be a very minor upgrade) from the SD card, thanks to information in a post here in the xda forums. that post is the link which follows. my thing would still go into fastboot (albeit slightly corrupted) + recovery mode, which enabled an SD card firmware flash to happen {...and lo, my little slab of Jelly Bean was resurrected...} so i did not require the NvFlash tool at all... but it's still there at the provided links in that thread.
to summarize the procedure:
1) format an SD card to fat32
2) download the appropriate firmware from Asus [**please note the region: if you flash the firmware from a wrong region onto your device, you will -hard- brick it + will then be required to use the NvFlash tool**]
3) un-zip the firmware (not completely, just remove nesting - so you have only one zip file)
4) rename the one remaining zip file: t4_sdupdate.zip
5) put that file on the root directory of SD card, then into the tablet (while turned off)
6) invoke recovery mode (power + vol down) & choose the recover [RCK] box (hit volume up, while it's the selected of the 3 choices) and from there the firmware update happens automatically. you can apparently upgrade to any official firmware by this method, but **cannot** downgrade... so i'd suggest leaving it at 4.2.2 until we are 100% sure that there are zero bootloader unlock options, because apparently the unlock tool, from what i understand, only works from the original 4.2.2
without further ado:
https://forum.xda-developers.com/transformer-tf701/tf701t-nvflash-unbrick-solutiontested-t3742848
it's now a few hours later from my original post, near bedtime for me, and the xda gods let me log into this account to make this edit... and it's even allowing URLs now! will wonders never cease? not sure what the problem was earlier, but it was quite annoying. anyway, if it lets me log into the account with the dedicated xda e-mail address, that's the one i'll use in future. username is renigade.

fly a kite said:
...
Click to expand...
Click to collapse
Hello @fly a kite @dorkus mallorcus @renigade
Please consult the inbox of your private messages. Thanks for your cooperation!
Stay safe and stay healthy!
Regards
Oswald Boelcke

Samsung: worst ever for a power user!

Today I got up real pissed with Samsung for being so restrictive around ROM flashing, rooting, flashing custom firmware or even stock firmware, so wanted to create this post to help anybody considering to get a Samsung phone to stay away from it.
This post is not intended to recommend any specific brand or model of android phone, but to recommend the exact opposite, which brand and model NOT TO EVEN THINK of purchasing.
This post relates to Samsung Galaxy S9 G9600 model which is Snapdragon architecture, but since Samsung is coming up with a bunch of "security features" I tend to think this may be the case for other models as well. I browsed all around XDA and other sources for guides on how to root and install custom roms, and it turns out Samsung manages to have limitations for EVERY step of the way.
Getting a few facts straight
Reference post: https://forum.xda-developers.com/ga.../rom-lineageos-17-1-s9-s9-snapdragon-t4093301
Ok, so there is a solid thread about a custom firmware and looks like several users got hands on it, but they might have been able to get passed though all Samsung security crap before it came out or before it got so tightened up. I'll list below every limitation I found:
OEM Unlock
There is a step where we need to tick OEM Unlock from the phone developer settings, it turns out Samsung has put a 7-day timer for this option to even appear listed to enable. If you do factory reset of the phone, the 7-day timer restarts. There are a few posts around on how to get passed this timer, but to me they were all crap, none of them worked. STRIKE ONE!
Bootloader unlock
After 7-days, we get the OEM Unlock option to appear, at this point you may think: Hurray!! .... WRONG! Now next step is to unlock the bootloader using an utility called CROM Services... And as you may have already guessed, did not work! I'm able to install the apk, but on launch it complains about wrong android version. (Tried with Android 8 and 10) STRIKE TWO!
There are some posts and guides claiming to be able to unlock bootloader by using fastboot utility, I can't reach to understand how, since fastboot commands rely on the bootloader to be previously unlocked (?). I least that is my understanding, correct me if wrong. Needless to say fastboot did not work for me. ADB lists my device but fastboot doesn't. There are a few troubleshoot guides around to try selecting proper USB driver from windows device manager, tried all that, tried a couple of ADB installations, fastboot didn't work.
Knox and RMM state
After some lookup in the web, Samsung incorporates some security features trying to prevent device theft and such things. For us power users this is in reality just a whole load of crap preventing us to get all the juice out of our phones.
Reference: https://www.goandroid.co.in/unlock-bootloader-of-galaxy-s9-plus-snapdragon/84688/
TWRP Recovery
Next step would be to flash a custom recovery such as TWRP with Odin or adb/fastboot, but since we are not able to unlock the bootloader in previous step, this is not doable at all. STRIKE THREE! OUT!
Fastboot utility doesn't recognize the device in download mode, so we can't send any commands to the phone.
Odin complains it is only able to flash signed stock roms, so since TWRP is not, we cannot flash it.
Rooting
Needless to say that if we don't have TWRP, we cannot flash the corresponding packages to root. Although this step may not be needed to install custom firmware, rooting has not been possible.
Stock ROM Flashing
Ok, so let's stay out of custom firmware - let's play around with stock firmwares. At this point, since flashing stock firmwares is kind of allowed by Samsung I was able to try out a couple from android 8 to 10 with Odin
Stock ROM Source: https://www.sammobile.com/samsung/galaxy-s9/firmware/#SM-G9600
But watch out! Once you get to install a specific build version, you cannot go back or downgrade to ROMS with previous Android build version. So now that I got Android 10 cannot go back to 8 or 9, this is probably because locked bootloader and unable to unlock. Here, Odin complains with FAIL! (AUTH) message.
STRIKE FOUR! EVEN OUTTER!
SIM Unlock
Ok, let's stay out of Samsung S9 G9600 model, let's crash it to the wall and throw it away to the garbage! Ok no, let's have it carrier unlocked and sell. Unlockbase is a well known and trusted sim unlock provider, I purchased a license to unlock by USB cable, but... GUESS WHAT! G9600 is not supported for unlocking operator network with this software... what a surprise!! I was able to apply for a refund and got my money back, so no worries here.
Note that flashing carrier free ROM does not unlock sim to use with any network operator.
I'll be trying to unlocking by code soon, as this is based on IMEI number, I may think this is independent to the phone model and edition, so I hope I have more luck with this option.
Conclusion
G9600 is a really crappy phone to mess around with. I may have ran low on luck with this specific Samsung Galaxy model since I got it as a gift, which is the latinamerican crappy edition. I wonder if other S9 editions and other Samsung models run with better luck than mine on this scenery... But as a lesson to myself, I will stay away of any Samsung smartphone in the foreseeable future.

OEM Unlock
The 7-day lock prevents stolen phones from being factory reset, leaving the thief with a phone permanently protected by your account. While a minor inconvenience, it's actually effective and not the worst compared to other manufacturers.
Bootloader Unlock
After OEM Unlocking, flashing TWRP through ODIN is effectively unlocking the bootloader. This is possible on both exynos and snap.
Knox and RMM
While this is an inconvenience, from Samsung's point of view, it's worth it. It makes the phone look more secure in the eyes of potential customers. If you really wish for NFC payments, I'm still able to use GPay with Magisk on a custom ROM.
TWRP Recovery
TWRP is flashed through ODIN, not fastboot. Look up an actual guide before complaining.
Root
Yes you can
Stock ROM Flashing
The one thing I could agree on with you is Samsung disabling OTA updates when OEM unlocking. I don't see the point really, but you're free to flash whatever you want through ODIN. Downgrading shouldn't be an issue. Not sure what's up with that.
Before buying a phone, how about you do some research before crying on forums. As a power user coming from the Oneplus One, I don't regret going for Samsung in the least.

Thanks for your reply, I had dropped all hope after several attempts over last few weeks. Found this option and I was able to get past my blocking issue with TWRP and moved on.
https://forum.xda-developers.com/ga...er-development/g9650zhu6dta7-android-t4051751

I have G960F and have to admit I totally disagree with your original post. I've been using custom ROMs on nearly every phone I ever had and don't think S9 (G960F) is bad in terms of unlocking. Just did an OEM unlock, waited a week, flashed TWRP through Odin, booted straight to TWRP and immediately flashed a custom ROM from it (because a boot to the stock ROM would replace TWRP back with the stock recovery IIRC). In the end I got sick of all the problems with Magisk and non-working google pay that I went back to the stock ROM - making S9 the first phone I use with a stock ROM even though it can be flashed. I think it's a great phone for power users.
And as far as SIM unlock goes - Samsung is not to blame, the carrier the phone was made for (and purchased from) is. Phones that Samsung itself sells are unlocked. I wonder why there's still some countries where SIM locking remains legal.

This thread is a prime example of how people end up with bricked devices. So much misinformation in one page LOL

I had the 9650 and most of what I'm doing here is user error. This was one of the best devices I've ever owned. I mention of fast boot and such you obviously just do not know samsung devices. You can't blame samsung on your own ignorance

How To Guide FYI: NE2217 T-mobile (Carrier locked, BL locked) <== Dont Flash Any Other Region w/o reading.

!!! This is a HIGH RISK method of performing any form of modification, if you are on a T-Mobile ne2217 !!!
There are unidentified files that your device might have conflict with, and cause a bootloop!
Proceed at your own risk! You have been warned!​
OK, first lemme explain. The NE2217 (10 pro) itself does not have any special restrictions on it, unlike the CPH 2419 (10T) which is an exclusive T-Mobile variant. My guide on region swapping the CPH2419 (10T, link below) is still valid for the NE2217 (US- NA) . But there are conditions required or you will enter an infinite bootloop which becomes un-recoverable, without an edl flash. I do not have the specifics as to exactly which partitions cause this, but basically the bottom line is, IF YOU HAVE NOT UNLOCKED YOUR BOOTLOADER, EVEN IF YOU ARE SIM UNLOCKED, do not attempt to region swap.
There are a couple of partitions that are specially locked, that ONLY become write capable using the fastboot command, "Unlock Critical". Without a Bootloader unlock, the Oxygen Updater/Local Update programs, CANNOT make the needed changes to the Kernel, as well as these other important partitions, which have instructions that implicitly block changing to other regions. I cannot confirm if this exists in other countries with carrier locks, but i do know for a fact that T-Mobile has this enforced on all of the 10 Pro (ne2217) purchased through them.
As mentioned in previous threads that ive replied in, I suspected that the apps Oxygen Updater and Local Update, do not have the permissions capable to make direct changes to the boot.img, or recovery.img directly, primarily because those partitons cannot be altered while the system is currently running. These images can only be altered through Fastboot, or EDL thus the need for an MSM Tool if you cannot unlock your bootloader via conventional methods. So what happens is upon "Pre-boot" those special instructions i spoke of, take authority and put the carrier specific files, into an untouchable state that are locked behind the USERDATA partition, so these applications just copy the updated files to the inactive partition and performs the changes during the next boot, and even a hard wipe factory reset does not have the authority to erase the carrier instructions. The only way they are removed is by Unlocking your Bootloader! When you do that, the Qualcomm Processor has an embedded command, which is required to ERASE the entire Userdata partition, to protect the encrypted files protected by the bootloader lock! You can read about that by googling "Qualcomm Bootloader Unlocking".
Hope that makes sense to the majority of you. So again, the ONLY requirement for you to be able to go from 'ne2217', to any other fw is YOUR BOOTLOADER MUST BE UNLOCKED!
Failure to follow that one requirement will indeed force your device into an unusable, infinite bootloop, which can be resolved only by an EDL flash, which as of right now we do not have the tools that can perform this on CONSUMER level. You will have to RMA, your device, or go thru third party channels, which in itself is very risky, and puts you at risk of viruses/malware/wormholes/zombie-apocalypse because you must give someone full access to your computer remotely, and pray that the person only does what you requested. (NOT IDEAL).
Now if you're on a T-Mobile locked device, you are NOT hopeless... as I am on a T-Mobile locked device, and i am now bootloader unlocked as well! These two conditions are independent of each other, but trust me when i tell you that YOU DO NOT WANT TO GO THRU WHAT I HAVE EXPERIENCED, IN ORDER TO REACH THIS GOAL!
In so I will not publicly disclose how i was able to enter the real Fastboot Mode, so that i could pull the unlock code needed to request the unlock token from T-mobile.
(If you are so inclined to do this that you are willing to forgo ALL precautions and risk the possibility of bricking your device, or you have already landed yourself in an unrecoverable bootloop state, and are willing to try ANYTHING, you can join Bootloopers Anonymous, by clickiing it, and drop a message. This is a brand new telegram channel, and i will try to watch it for your requests. And again i strongly advise that you DO NOT embark on MY adventure, but if Unlocked Bootloader by Any Means Necessary is your ultimate goal, and nothing less is acceptable, i will try to help you achieve it... *** YOUR DEVICE WILL ENTER A COMPLETELY UNUSABLE STATE FOR A MINIMUM OF 7 DAYS!! *** but bear in mind that EVEN IF you have to use my method, you will be still subject to the 7-day waiting period outlined by OnePlus company policy. No one can overcome that, as the unlock token comes thru a separate division of Oppo/Oneplus that only generates the token through an automated request which is pushed after the expiration of 7 full days (1-week) has passed. YOU HAVE BEEN WARNED!)
The 10-Pro doesn't require the "In-Depth Testing" app to get your BL unlocked. That said, it also does not mean that OPPO has not designed one for this device because indeed they have. That application is individually encoded with device specifications so that only devices and regions EXPRESSLY AUTHORIZED by Oppo, can submit a request to unlock. DO NOT TRY sideloading any "In Depth Testing" apk floating around on the internet, as these can be altered to contain malware or worse, and then if your device becomes corrupted by it, Oppo can deny you an RMA on your device, thus charging you for the repair as there are warnings that you must acknowledge to even run the app, and attempting to circumvent the safeguards that this app already has in place is considered a violation of ToS.
If OPPO adds your device/region to the list of allowed devices, you will be able to download this application through OFFICIAL channels, and it will be made known to the public.
Once you are completely knowledgeable that your BL has indeed been fully unlocked, you can proceed to follow the instructions in the link to my guide below. The guide is for the CPH2419 (10T), but the instructions are completely compatible with the 10 Pro entire series, assuming your BL is unlocked. On the 10T this is not a requirement, and i honestly do not understand why this enforcement was put into our 10 Pro model, released almost a year earlier. Probably just an oversight by T-Mobile which might be corrected in future builds.
How to use Oxygen Updater + Local Update apks to switch regions.

EDIT: Local Update downgrade it currently installing
No Go, The update installed and downgraded but it just loads to the welcome screen and crashes and boot loops

supercobaltss said:
EDIT: Local Update downgrade it currently installing
No Go, The update installed and downgraded but it just loads to the welcome screen and crashes and boot loops
Click to expand...
Click to collapse
again, what most ppl are failing to do is follow my guide exactly as i defined. The VERY 1st thing you MUST DO... prior to unlocking the Bootloader... Prior to even downloading ANY rollback packages is, you MUST go and Download ANY of the Android 13 beta updates that are available in Oxygen updater. Turn on advanced mode, and select the whichever model you prefer... Its actually best to choose the region you plan on swapping to, for easier transition with the rollback package. IMHO i would always pick the EU model whenever attempting this, simply because that one usually has more bands available. But the main idea behind this is to make the phone, first BREAK the connection it has with T-Mobile's custom kernel, and modem... which is done just by upgrading to an Android 13 beta, as T-Mobile does not EVER release any beta builds, so by doing an actual OS upgrade, your phone must load the OS kernel, and several other partitions/files which i am sure that T-Mobile has branded in the 2217. Upgrading to a newer OS will without a doubt overwrite the carrier locked files, because the Upgrade comes from a higher authority in the chain of trust. Until TMO releases an update, then this is a requirement so that the rollback package of that region can safely downgrade the files, in their correct partitions. If you download a beta 13 thru oxygen updater, you can local update flash it, without problem. I did it myself to several demo devices at Tmobile stores here in Texas to test the technique, after i bricked mine by using a rollback package first!
Remember the 2217 is a T-Mobile EXCLUSIVE! No other carrier may sell this same model... but ALL of the internals are the exact same, and as im sure we are all well aware of, T-Mobile doesnt have the fastest adaptations when it comes to OS updates.
But there are several key identifiers which point to a custom made BL, Kernel, and Modem: 1. The build for all T-Mobile versions is on a revision that no other model has released... This alone could cause BL because if you flash a build that is older than the one you have currently, several files have anti-downgrade measures built into them. This is why we need the signed rollback packages to downgrade. But even if OPPO signed a rollback, unless they released one with T-Mobiles file specs, then anything you flash can create a conflict with an existing file... BL! But i know of about 13 ppl who have attempted my method, plus i just did another one myself last night for someone who contacted me and offered to compensate me royally if i would meet them since we were local logistically. 2. AFAIK, when installing a different rom to a device, you cannot downgrade the modem version. I know this is apparent with Samsung... as if you try to flash a rom with a lower modem version, it usually bricks, and you have to use odin to flash the newer modem back, in order to boot. Again this is taken care of by installing the NEWEST beta for Android 13, unless you had my situation which is, my phone CAME WITH updated security, and build already installed for October 2022. I havent heard of anyone who has said they even have the option to update theirs past August. So new purchases have to be careful. T-mobile sold mine with a blocked Fastboot, that doesnt respond to the button combo. Which clearly identifies they modified the recovery partition. 3. E-fuses have become a staple in Android devices for the past 5+ years.
Sure we have not heard of anything being in the T-mobile fw... but also who here can say that they have a FULL BUILD of the Tmo fw to examine? No one.... there is a generic 2217 build floating around that claims to be official, yet it is the ONLY build that does not have an OTA formatted file structure. All the 10 Pro OTA have been in payload.bin format, yet this happens to come only as a decrypted OFP, or a compressed OFP. *** OPPO is not directly supporting the 10 Pro 2217 or 10 T 2419 ! As these are proprietary T-Mobile builds. This is why you cannot find either of those models fw in the Oppo repository. So if OPPO doesnt release builds for TMO, then how exactly did an "Official 'OFP' for 2217" get released? *** OFP is an Official OPPO format for all the OPPO model phones. 10 Pro is still branded Oneplus, thus just about any OFP file you find in the wild, is almost 100% guaranteed NOT to be an official released build for our phones. Every package for this and the 10T that they have OFFICIALLY released, has been in Payload.bin format, because they havent released any full images yet! So in theory, who's to say that TMO didnt place an efuse into their specific model? Its only code, and if set, then it could have been burned during the initial release, or a later update, like AMAZON did with updates to the Firestick/FireTV devices, which would ONLY allow newer updates to certain files in THEIR build. That would totally explain a bootloop, because the rollback packages all push you back to 11_A.013 .... that build is from Feb-March 2022. Rolling back would almost guarantee that some files are overwritten with older components, which would cause a brick by e-fuse standards. We had to be lucky enough to catch it early in the FIrestick forum, to stop ppl from installing the update. Everyone who did, had their ability to unlock/load custom fw to their devices blocked, and there is still today no way to circumvent it. Sure new methods to mod became available, but only minimal changes, cuz the e-fuse blocked downgrading to exploitable builds. Since TMO has gone this far to stop us from modifying this phone, you can bet solidly on the fact that they have several safeguards in place to protect their investment.
Now im not trying to discourage anyone or discredit anything anyone has said or experienced regarding this phone, but look at the NUMEROUS unanswered replies to handfuls of problems that only happen to 1 or 2 ppl... they all have the same final result, but its astounding how many different scenarios ppl have found, that no one else has experienced, yet it leads to another bricked device. If this problem was rampant among a significant number of users, and it was triggered by the exact same scenario, then TMO would have to address it with an update... But all we know for sure is that there is some file(s) that is not compatible with any other model except the 2217. Til we have an EXACT culprit identified, all we can do is speculate, which is why I am going to re-label this as HIGH RISK in the OP. It has about a 40-50% chance of causing a bootloop, and about a 10% chance to leave your device unresponsive! There have been several released guides for other devices that have close to the same success rate / risk factor. All i can do is share what I have done, and what i know from personal exp.
Im sorry if anyone lands themselves on the wrong side of that equation, but it is a risk that only you can decide if its worth taking. For me, that answer is and always will be YES because i will not own a device that i do not OWN! For others this may be a touch more out of their league, and if thats true they should steer clear, until I or another user can get hold of an official TMO OTA, to examine the diff files in each.
****** Now all of that being said.... if ANYONE wishes to contribute to finding a solution to this dumpster fire, I am not asking for donations.... What i am asking, is for SOMEONE who might have a T-Mobile 10Pro on the release build, or any build PRIOR to 11_A.13 and is looking to help, we NEED an exact copy of an OTA update that might be sitting in your notifications. All updates download to the /sdcard/ partition of your phone in a folder that is accessible without root permissions. If you accept the download for the update, and DONT begin the install immediately, you can locate and pull that OTA to your computer, then delete the file from your phone, and it will cancel the update on reboot. No loss to you, but EXTREMELY HELPFUL to us, because we will have something from TMO to work with, which may give us a clue as to what we need to remove from the updater script ! *******
and FYI the signatures used to sign some of the OTA we already have, are already deciphered and as such can be used to create new signatures after making some changes to the respective regions package. But to make having these be of any value, we need to know what to take out or change in the manifest, that will prevent alterations of the files causing bootloops. If anyone can help with an upload of a TMO-OTA please share publicly or dm myself or one of the other devs who have expressed interest in this issue.
Thanks

I can probably pull the update from my wifes phone. She never updates anything. I did get my 10 pro to boot to android 13 but everything just says its disabled. This is only the 3rd phone ive done this with so ill warranty another one if i have to lol.

supercobaltss said:
EDIT: Local Update downgrade it currently installing
No Go, The update installed and downgraded but it just loads to the welcome screen and crashes and boot loops
Click to expand...
Click to collapse
Yup, this happened to me as well. Setup wizard crashes before I even get very far in it, and I've wiped multiple times trying to complete it somehow.

GuyInDogSuit said:
Yup, this happened to me as well. Setup wizard crashes before I even get very far in it, and I've wiped multiple times trying to complete it somehow.
Click to expand...
Click to collapse
Ive tried to convert multiple different ways. Upgrading to 13 basically screws you with the disabled apps BS, Downgrading just crashes the device. Either way its broken. I've went through 3 devices now messing around.

So I guess it's time to replace it, then? Crap.

GuyInDogSuit said:
So I guess it's time to replace it, then? Crap.
Click to expand...
Click to collapse
Start a RMA on OnePlus website, don't go through T-Mobile. They will have you send in phone and then either reflash your phone and send it back or just send you a new phone which is what they did when I had to do it. All that bs about voiding warranty when unlocking bootloader is just that, bs. They fix or replace without any issues but you have to go through OnePlus.

FML.
I've gotten it working for the most part, but what's most concerning is that there's no IMEI. And it doesn't charge or even acknowledge the cable. Fantastic.

jeffsga88 said:
Start a RMA on OnePlus website, don't go through T-Mobile. They will have you send in phone and then either reflash your phone and send it back or just send you a new phone which is what they did when I had to do it. All that bs about voiding warranty when unlocking bootloader is just that, bs. They fix or replace without any issues but you have to go through OnePlus.
Click to expand...
Click to collapse
I can't even request an RMA as I don't have an IMEI to provide. It's blank in the phone. I think I'm screwed. Or try T-Mobile. Dunno. This sucks.

GuyInDogSuit said:
I can't even request an RMA as I don't have an IMEI to provide. It's blank in the phone. I think I'm screwed. Or try T-Mobile. Dunno. This sucks.
Click to expand...
Click to collapse
The T-Mobile version has your IMEI sketched into the back cover of your phone. You should be able to use that.

jeffsga88 said:
The T-Mobile version has your IMEI sketched into the back cover of your phone. You should be able to use that.
Click to expand...
Click to collapse
Oh. Uh.... completely forgotten about that.

I just updated to Android 13 on the TMO NE2217, device not unlocked, still financed. And now have the option to unlock the BL.

beatbreakee said:
All updates download to the /sdcard/ partition of your phone in a folder that is accessible without root permissions. If you accept the download for the update, and DONT begin the install immediately, you can locate and pull that OTA to your computer, then delete the file from your phone, and it will cancel the update on reboot.
Click to expand...
Click to collapse
Is this still useful, with the NE2217_11_C.26 update? And either way, how can I delete it? I couldn't find anything big in /sdcard. Thanks!

deleted

psm321 said:
Is this still useful, with the NE2217_11_C.26 update? And either way, how can I delete it? I couldn't find anything big in /sdcard. Thanks!
Click to expand...
Click to collapse
^
^
^
^
^
THIS Please my phone ignored my saying no and next reboot the damn thing will go off on me ... so frustrating that even when you set the darn thing to OFF on auto update and such it STILL does this BS...
Damn TMobile and their special lock junk UGH ...
anyway ... please can one direct with a screen shot and file manager they used to find this file so I can delete the thing? ... I have tried to find it and struck out ... but having got the notification today and the Oxygen app is showing 'REBOOT' instead of 'resume' when I ignored the update previously has me thinking if I reboot I will see android 13 pop up and in this case means I will lose my whoop as something with it breaks pairing my wearable ... whoop has offered no timetable for a fix