Question Few questions about My A326U1UEU3AUH1 (5G) - Samsung Galaxy A32 5G

So, I purchased the A32 5g version a little over a year ago and when I came to xda to find the method to root, I found out the bad news. But read in one of the threads that if your sitting on build 1,2 or 3 to not update because there was a possible method to unlock the bootloader coming soon and taking the updates would make it harder/impossible to unlock the bootloader. So I have been sitting on the build that came with my phone when they handed it to me which is RP1A.200720.012.A326U1UEU3AUH1.
I have been ignoring the update notifications for a year in hopes of a *free* method to be released to no avail.... I think... Right?
Also The old update notifications I would get were easy to ignore and swipe away from the notification swipe down menu and I wouldn't see them again for another week or two. But now just in the past few days for some strange reason the update notifications are different and more annoying. Whenever I restart my phone and unlock it for the first time after restart I always get a whole window notification that takes up my whole screen asking me to update so I always click "later". And it's also permanently in my notification swipe down menu now, I can't swipe it away or turn the notis off. And they've also pinned a huge banner at the top of my main settings menu that says "A software update is available" with an accept button right below it.
So, a couple questions:
If I haven't taken any updates how did my carrier change all of these update notifications and pin one to the top of my settings menu that was never there before? Are they able to do that without me taking an update? It's almost like they're trying to put it everywhere on my phone in hopes that there's more of a chance of me accidentally accepting it. Also, I believe that eventually I will accidentally hit accept on one of these constant notifications and I've waited so long for a *free* method to unlock the bootloader that hasn't come yet, should I just update and get it over with? Or is there a *free* method somewhere or word of one coming?
I also have a couple off topic questions about my carrier. So I believe my build # is the Verizon version of the A32 but my actual cell company is cellcom (American cellcom) and cellcom uses Verizon's network. So why does my carrier use Verizon software and the Verizon network? Why doesn't Verizon just open up shop where I live?
All the previous phones I've gotten from cellcom have always been pretty easy to root and they've always been carrier unlocked. Not sure why but they have been. That is until I made the mistake of getting this phone without doing any research on whether or not it was rootable.
Sorry for the long, all over the place post but If anyone could answer my few questions, it'd be greatly appreciated! Because at this point I'm thinking of just pulling the trigger on the updates if there's no way to unlock the bootloader without paying for a token.

Mine is bootloader version 8 so it can't be rooted; but yours is below 6 so this thread says it can be rooted. Please check it out & let the rest of us know how it works out for you if you try those rooting methods.
How to ROOT A32 5G

Related

SM-955U S8plus

I had it unlocked almost 3 months ago it a Sprint phone. Im using Tmobile but i can't get any software updates it will show on my top notification bar on phone but when i try to download it, nothing it won't download. The company that unlocked did they mess it up? I'm very new at this. When i shut my s8plus off and back on a screen comes on home screen I sent a screenshot what is says all the time i turn it back on I have to hit update successful ok...don't make no sense to me it did it after they unlocked it for me. I know my S8plus is a great phone but it very behind on updates and security patch. Please help me. I call the company that unlocked it says nothing they did lol...well they done something wrong for when i shut it off and back on that screen keeps coming on...Thank you. I went to Tmobile being better network and unlimited and the bill one monthly cost the same.
eek88dj said:
I had it unlocked almost 3 months ago it a Sprint phone. Im using Tmobile but i can't get any software updates it will show on my top notification bar on phone but when i try to download it, nothing it won't download. The company that unlocked did they mess it up? I'm very new at this. When i shut my s8plus off and back on a screen comes on home screen I sent a screenshot what is says all the time i turn it back on I have to hit update successful ok...don't make no sense to me it did it after they unlocked it for me. I know my S8plus is a great phone but it very behind on updates and security patch. Please help me. I call the company that unlocked it says nothing they did lol...well they done something wrong for when i shut it off and back on that screen keeps coming on...Thank you. I went to Tmobile being better network and unlimited and the bill one monthly cost the same.
Click to expand...
Click to collapse
Try moving to the unlocked firmware or update it manually through Odin.
Thank you but i dont know how to do that. I'm new at this I'm learning. If you could help i appreciate it.
Occurs to every phone that gets unlocked from the original carrier. Even though it's quite dumb. My suggestion is to continue to read and learn more about the device. However if you can locate the proper tmo build for your phone.. Should be CRB7 or higher. Maybe CRB9 you can update to the latest version through the SD card if you have one. I stress that if you have any issues with how you can get into recovery mode, or updating in this manner, do not attempt until you feel comfortable doing this. The quick and easy way would be to switch to the Sprint SIM and then you can get the updates over the air. If you unlocked the phone this should not be a problem.
Try to use my old Sprint SIM card not activated. Says no data connection or network. I have a SD card. I want to do this. I know how to get into recovery mode etc...with power button and volume up and Bixby button.

Can you convert SM-N915V to ATT ?

I just received a new Galaxy edge phone (out of the box). And did the lengthy updates to 6.0.1.
Ready to activate I went to ATT store and they tried a sim card on it.
Well nothing happened.
They could not get it connected to anything.
This was an existing Sim that they had laying around. So not sure if it was even active.
Was going to test on my own sim for home testing, but it is a nanosim size and doesn't fit.
When I get it completed was going to root the phone and get rid of all the junk on it. And load magisk as well.
Have just started looking at guides for that.
Any help getting me on the right track for getting this to go to ATT and root (unlock bootloader) would be great.
If there is any more information that is needed please ask.
Thank you
Talked to the right person at ATT the wrong one the first time.
Can delete thread !

I just bootloader unlocked a Verizon branded Pixel 3 - how is this possible??

I mean, I'm not complaining. But I was incredibly surprised! I bought the phone BRAND NEW AND SEALED, from the current sale on woot ($170), and yet was still intending on returning it after I realized I had bought a Verizon variant, albeit carrier unlocked. Yeah, it's only the 64gb version, but I literally just bought this for testing, and as a backup. Actually bought a P3 from a friend that was in decent condition. A really close, trusted friend too, but unfortunately it just happened that about a month later the battery started exhibiting the dreaded behavior indicating it was starting to fail, so I decided to pull the trigger on the sale, not realizing it was a Verizon model. I went into much more detail about it in my post on Slickdeals: https://slickdeals.net/forums/showpost.php?p=146850461&postcount=127
It's also pink, but I'm putting on the Mint colored Spigen Neo Hybrid case on it anyway
So anyway, from all my collective knowledge about Pixels, and plenty of knowledge about (and hate towards) certain US carriers locking down devices, I wasn't expecting to be able to bootloader unlock this phone. Luckily I decided to open the box anyway and see if the OEM unlocking toggle was greyed out (which is what I fully expected!)... And it wasn't!? I still expected something, anything, to go wrong, but no, it actually successfully unlocked the bootloader (proceeded to factory reset as usual, etc)!! Unfortunately, it seems that the eSIM is still locked up and disabled, but like I said, for my usages as a simple dev'ing, testing, and/or backup phone, the eSIM isn't really important to me.
Don't think it matters, but I did this immediately upon opening the brand new phone, and it was on firmware PQ3A.190505.002 (May 2019, Pie). I mentioned it in my SD post, but the IMEI does start with 35, and checking it through Verizon's prepaid check system also indicated it as Verizon branded. I know that historically (on older Pixels, not even the 3, iirc), there was a [anecdotal] workaround where some owners would pop out the VZW SIM card before ever turning on the phone and they could then unlock the bootloader. Crazier for me is that I didn't even bother pulling out the VZW SIM card the phone came with before turning it on.
The only thing I can think, is that (and my memory here is foggy about the anecdotal posts) maybe when people were buying the phones from Verizon, those phones were actually turned on with then-active SIM cards, thus allowing them to "phone home" and permanently lock up the bootloader, at some point before ultimately shipping to the buyers. However, as these brand new Pixel 3's being sold are just leftover old, albeit brand new and factory sealed, stock, they were never turned on, whether at all or with active VZW SIM cards, at any point. When I initially turned on this new phone earlier today, since I left in the VZW SIM card included with the phone, I got a message pop up saying something along the lines of "we couldn't activate the device" or whatever.
So anyway, I wanted to say all of this because I'm always fascinated by flukes like this, where someone (me in this case!) is able to bootloader unlock a phone that should otherwise be completely unable to do so... Also attaching screenshots to show that it is indeed a Verizon branded Pixel 3 with the bootloader now unlocked. Note that it now shows current April 2021 firmware installed, but like I mentioned before it shipped with May 2019 installed from the factory, and I updated the firmware after unlocking the bootloader immediately after opening. Is there any explanation to this? Did I just get incredibly lucky? Does my theory in the previous paragraph possibly make sense? Or is there already a known explanation somehow and I just was completely unaware (and if so please let me know)?
final note: pics look like phone's screen is fuzzy because I haven't even removed the factory plastic wrap yet, lol. amazon glass screen protectors come tomorrow!
EDIT: LMAO! The listing on Woot now says in big bold letters, "The bootloader is LOCKED on these phones". Pretty sure it didn't say that when I bought it, so must be a lot of people complaining about it and trying to return! Not sure how I was able to do it though still... even if I couldn't, I would have just cited the lack of eSIM as my reason for return. Fully Unlocked != eSIM Neutered, lol.
Should I buy one to try to get an OEM unlock version?
Hey, i5lee8bit
I was poking around and saw this. I ordered one of these from the woot sale. SHould be arriving in the next day or so. Mine is the 128 GB version.
I'm down to try your process and see if I am able to have success too.
What method did you use to unlock the bootloader?
aNewHoax said:
Hey, i5lee8bit
I was poking around and saw this. I ordered one of these from the woot sale. SHould be arriving in the next day or so. Mine is the 128 GB version.
I'm down to try your process and see if I am able to have success too.
What method did you use to unlock the bootloader?
Click to expand...
Click to collapse
First of all, I would remove the SIM card before you ever turn it on, just in case. I didn't bother and it still worked, but just in case that somehow allows it to "phone home" and lock itself up.
I just did "fastboot flashing unlock" from bootloader.
Just skip through setup, connect to wifi, enable developer options, and check (hopefully) OEM unlocking toggle is not greyed out. Enable the OEM unlock toggle, reboot to bootloader. While phone is booted to bootloader, connect to PC (or another Magisk rooted Android device with adb / fastboot module installed), and use command "fastboot flashing unlock" without quotes. Should hopefully prompt you to confirm unlock bootloader / wipe data.
To reboot to bootloader, either shut off and then power on while holding volume down, or enable adb debugging and send command "adb reboot bootloader" without quotes from command line / terminal.
I saw that deal you mentioned, haha. Are you a SD user / browser? I think the deal popped up this morning or something. If it's indeed brand new and sealed, hopefully it works! Best of luck, I hope you manage to get the bl unlocked!
Thanks for the direction. Haven't done a root on a phone in a long time.
Indeed, I am a Slicker ha. Over there I am @Skullk. The name was taken here so I used an alternate. Been a long time lurker on these forums.
This was the Slickdeal https://slickdeals.net/f/14972183-google-pixel-3-128gb-not-pink-199-99-with-free-shipping-on-woot
I received the phone yesterday. Made sure no SIM installed. Battery was completely dead, that makes sense though as these are some older stock.
Hope to have some time this weekend to give it a try. I'll report back with my findings.
Cheers!
Dude! It totally worked!!
I feel like we got something here. Maybe since the phones batteries were completely dead for a while in stock? Or just starting with a fresh phone on whatever exact version these are out of stock.
Are you sure theyre not Google phones
that were jus set up with Verizon in their former lives?
aNewHoax said:
Dude! It totally worked!!
I feel like we got something here. Maybe since the phones batteries were completely dead for a while in stock? Or just starting with a fresh phone on whatever exact version these are out of stock.
Click to expand...
Click to collapse
Woohoo! Back a while ago, when I was still on AT&T, I was researching Pixel 4 series and saw that bootloader was indeed unlockable once SIM is unlocked (like Apple, SIM unlock is controlled on Google's side servers, but once whitelisted, not only unlocks the SIM but also "flags" the OEM unlock toggle to be allowed as well - unfortunately not the case for Verizon Pixels). Unfortunately I had problems with AT&T and eventually bought a factory (Google store) Pixel 4 XL and switched to Xfinity Mobile. Anyway, during all that research, I also saw that some Verizon Pixel 4 / 4 XL phones (iirc) were able to be bootloader unlocked as well. There were a few theories, one of which (again, iirc) applied to older gen Pixels - this particular one being that as long as the phones were never turned on with a Verizon SIM inserted, they could be bootloader unlocked (some theories suggesting doing factory reset gymnastics and stuff). But this didn't work for everyone (actually, it didn't work for the overwhelming majority of people - a lot of people suspecting lies / hoax / misunderstanding). But now I'm starting to think this theory may hold some water, though. Perhaps when you buy phones from Verizon, they're doing something on their end that essentially processes your account info to the IMEI of the phone you bought, somewhere in the backends of their systems. That, or maybe they're doing something with the SIM cards to set up for your account and turning on the phone once before shipping to you (I have no idea, I've never been a VZW customer). Either way, the phone's IMEI gets to "phone home" to Verizon thus locking the bootloader.
But since we're buying these old stock, never touched, never processed / activated into their system, completely factory sealed Pixel 3 / 3 XL phones that are total virgins to Verizon's systems (other than being preinstalled with a VZW SIM card), maybe that's why we can unlock the bootloaders. I don't think it has anything to do with the exact firmware versions they shipped with. I believe I remember seeing people on SD having bootloader unlocked on various firmware levels. Hard to say which thread(s), because the deal popped up so many times in the last few months, but I definitely remember seeing scattered preloaded firmware versions being bootloader unlocked.
Another theory had to do with a mistake on Google's end. Some people got lucky, some people got EXTREMELY unlucky. Some phones were manufactured and branded for the wrong carrier. For example, a phone manufactured for Tracfone ended up being locked to Verizon (not sure of the specific carriers and whether vice versa but you get the idea). But some people would get a phone that should have been bootloader locked down (OEM unlock toggle disabled) but still be able to do so. Not sure if the latter is related at all to how we're able to unlock these, but I doubt it. These were very small batches that got mixed up in manufacturing. Right now, we're seeing definitely Verizon locked phones, old stock, that all seem to be able to be bootloader unlocked. I really do suspect that there is a "phone home" process when initially setting up the phone that seals the deal with ending up with a permanently unlockable bootloader.
Now, an interesting experiment (that I wouldn't wish for anyone to try to be honest, lol) would be to have someone buy one of these old stock, brand new Pixel 3 Verizon phones, and initially turn it on WITH AN ACTIVE VZW SIM CARD INSTALLED. See if that permanently locks the bootloader. If not, maybe Verizon's side only perma-locks these phones up to a certain date (like their activation server sends some sort of command to permanently lock the bootloader, but that behavior of their activation server is only active during a certain lifespan of the device)? Either way, it would be interesting if smarter people could somehow use this information to come up with an exploit to bypass the initial bootloader locking mechanism, whatever it may be, and allow bootloader locking on future Verizon Pixel variants (though you'd likely be screwed once it's perma-locked).
On an alternate note, I absolutely hate that these carriers are screwing us, the end consumers and ultimate OWNERS of the device, for no damn legit reason. Ok, I can somewhat understand that they want to prevent modifications to the device to use their network (and by understand, I mean BARELY understand). But once the phone reaches end of life, ALLOW US TO UNLOCK THE DAMN BOOTLOADERS!! Otherwise, they should automatically chop off the sale price in half to whatever is the best current price from another vendor. F|_|CK Verizon and AT&T!
rocketrazr1999 said:
Are you sure theyre not Google phones
that were jus set up with Verizon in their former lives?
Click to expand...
Click to collapse
100% definitely Verizon branded. They're factory sealed, and come with a preinstalled Verizon SIM card. Also the IMEI starts with 35, and (unfortunately) the eSIM is locked and unusable. Like I posted in the OP, the box shows it's a Verizon locked variant.
Worked for me!
Hi, I too bought pixel 3 64gb from woot last week, I started the setup as well without taking the included sim card out. After completing setup, I can verify that OEM unlocking is not grayed out.
I am very noob to custom roms, but definitely interested in trying out the custom rom when the official support ends, Is there anything else I should do before popping in my Visible sim card in it, so that the bootloader stays unlock.
Thanks, long story short this worked for me too.
I ordered my pixel 3 from woot on june 7th when it clearly said "The bootloader is LOCKED on these phones." and got it today. I removed the sim card before turning it on, skipped most of the setup including WIFI, enabled developer options, and the "OEM unlocking" option was greyed out . Then I found a post about it needing to have internet access to enable that option - sure enough I connected to wifi and the option was live! I guess I should have mimicked your procedure exactly.
I then followed the instructions from here: https://android.gadgethacks.com/how-to/unlock-bootloader-your-pixel-3-3-xl-beginners-guide-0189128/
and the rest of the process completed successfully.
So, you did not do any special thing but just enabled Developer Options and the bootloader unlock was not grey? But mine was grey when I enabled Developer Options.
aNewHoax said:
Dude! It totally worked!!
I feel like we got something here. Maybe since the phones batteries were completely dead for a while in stock? Or just starting with a fresh phone on whatever exact version these are out of stock.
Click to expand...
Click to collapse
You also did nothing special, but just enabled Developer Options and found that the bootloader unlock was not greyed out?
yourrealking said:
So, you did not do any special thing but just enabled Developer Options and the bootloader unlock was not grey? But mine was grey when I enabled Developer Options.
Click to expand...
Click to collapse
I didn't do anything else. It was greyed out right after I enabled developer options but after I connected to WIFI for the first time and went back into that menu it was active.
yourrealking said:
You also did nothing special, but just enabled Developer Options and found that the bootloader unlock was not greyed out?
Click to expand...
Click to collapse
It's a little confusing, your question. Did you read the posts from the beginning? I mean the OP **specifies** exactly what he did... so when you say 'you did nothing special'... He says exactly what he did, would u call it 'special'?
it's impossible to answer your question, he did exactly what he said he did, what more do you want to know?
AsItLies said:
It's a little confusing, your question. Did you read the posts from the beginning? I mean the OP **specifies** exactly what he did... so when you say 'you did nothing special'... He says exactly what he did, would u call it 'special'?
it's impossible to answer your question, he did exactly what he said he did, what more do you want to know?
Click to expand...
Click to collapse
His posts are long, so I am not sure I got it correctly or not, but it seems that all he did was just enabling developer mode and ran "fastboot flashing unlock" in the bootloader mode. But that is a regular method that Google should have disallowed to work on a bootloader-locked device, so I wondered if there were some other "special" hacking-ish thing he did.
I thought I had tried that, but it was a long time ago, so just to be sure, I did that again now, and all I got was
"FAILED (remote: 'flashing unlock is not allowed')
fastboot: error: Command failed
Thanks to the OP, think I got the last one from woot. Did exactly as this post described and sure enough, oem unlock not grayed out.
It seems, as others have said, that when vzw disables oem unlock is when they 'set the phone up' for you at the store, or maybe simply when it connects to the vzw network with their sim.
I've unlocked and fb flashed to latest A11 non - verizon firmware, relocked bootloader, and am still able to unlock if I want.
Google sure does make it a lot easier to flash new firmware using fastboot. Especially compared to LG and lgup (only on windows), and patched dll's so u can crossflash, and one dll version for this, and another for that... meh.
Google even gives you an shell script that works with Linux Awesome!
i5lee8bit said:
I mean, I'm not complaining. But I was incredibly surprised! I bought the phone BRAND NEW AND SEALED...
Click to expand...
Click to collapse
Registered just to thank you for this. Bought a Pixel 3 from a B+H sale for my wife (who was really looking forward to her new phone) - we're in Canada, so thought I was screwed. Took awhile to get the USB drivers set up properly, but she's now got her new phone.
Thank you! It worked for me too for two Pixel 3 phones, one from B&H (software version PD1A.180720.031) and one from Woot (software version PQ1A.181105.017.A1). Here are the steps I followed (with android platform tools including adb and fastboot already installed):
1. Removed verizon sim card (just in case) before powering on
2. Powered on and skipped through Google setup
3. Connected to my T-Mobile tethered wifi instead of Verizon Fios home wifi (just in case)
4. Enable developer options, wait for "OEM Unlocking" to become not-greyed-out (requires wifi)
5. Enable USB debugging in developer options
6. Issue `adb reboot bootloader` from PC (or shutdown and use hardware keys)
7. Issue `fastboot flashing unlock` from PC
8. execute `flash-all.sh` from the official stock pixel 3 factory image zip from here: <https://developers.google.com/android/images#blueline>
a. This gets rid of Verizon's firmware completely
9. Wait for it to complete, reboot into bootloader
10. Issue `fastboot flashing lock` (erases user data) to re-lock bootloader
11. Booted normally and setup. OEM Unlocking is still available in developer options if I want it in the future.
johannish said:
Thank you! It worked for me too for two Pixel 3 phones, one from B&H (software version PD1A.180720.031) and one from Woot (software version PQ1A.181105.017.A1). Here are the steps I followed (with android platform tools including adb and fastboot already installed):
1. Removed verizon sim card (just in case) before powering on
2. Powered on and skipped through Google setup
3. Connected to my T-Mobile tethered wifi instead of Verizon Fios home wifi (just in case)
4. Enable developer options, wait for "OEM Unlocking" to become not-greyed-out (requires wifi)
5. Enable USB debugging in developer options
6. Issue `adb reboot bootloader` from PC (or shutdown and use hardware keys)
7. Issue `fastboot flashing unlock` from PC
8. execute `flash-all.sh` from the official stock pixel 3 factory image zip from here: <https://developers.google.com/android/images#blueline>
a. This gets rid of Verizon's firmware completely
9. Wait for it to complete, reboot into bootloader
10. Issue `fastboot flashing lock` (erases user data) to re-lock bootloader
11. Booted normally and setup. OEM Unlocking is still available in developer options if I want it in the future.
Click to expand...
Click to collapse
So we don't need to download the blueline images that say Verizon and can just use the latest 11.0.0 (RQ3A.210705.001, Jul 2021) image instead?
I haven't done this forever, is there still a need for TWRP if we are sticking with the stock rom, unlocking the bootloader and installing Magisk?

Question Can't remove old Carrier's information on Global Unlocked phone

Hi all,
I have been stay up two days to looking for my solutions and would you guys at least let me know if this is impossible or possible?
1. Bought Global Unlocked AT&T phone from my friend. When he sold it to me, I made sure it is unlocked and move to any carriers.
2. I check IMEI numbers and everything from Verizon (I called them) they confirmed this phone is compatible in their netowrk and will work.
3. I switch my iphone 11 max pro sim card (verison) and put it to Samsung Z flip 3 5g.
4. Everything works find but, I saw AT&T logo when I start the phone. I also some of AT&T setting's everywhere. I did factory format and showing the same thing.
5. I called verzion and they said, because I use 4g sim to 5g phone and asked me to visit their direct retailer to get free 5g sim card and I did.
6. HOWEVER, after change even sim, it shows still AT&T logo and AT&T related menu in the settings and everywhere. Also, I did not even have wifi calling feaatures.
6. After that I have been search and study two days but, still couldnt' figure out what's going on. What I found is I need ask my current carrier to push OTA. (that's the one of other people suggested and I did chat with verizon and they said, they will get back to me after senior engineer to check if they can do it.
7. They also make sure my phone is registered their networks and works fine.
It is really bothering me to see some of AT&T settings still turn on and also shwoing in this phone.
Probably this phone is global unlocked phones provided from AT&T from the beginning.
While i am searching and reading the articles, lots of people told me to gave up because i am even on Verizon, they said I have to depends on AT&T's OTA updates and etc....
it is my fault to bought it from my friend even tho I belived that because it worked, I thoguht that everyhthing would be fine......
What should I have to do? Just stay with it and sell it when z flip 4 is come out? Do I really didn't have any change to correct this issue?
I was fan of iphone and i swiched to android first in my life and everything went wrong. I want to fix and stay on Samsung. Would you guys can at least let me know there's no way or there's way to correct this so that at least I can ignore everthing and stop trying to find answer all day wrong........
Thank you and sorry for long question... you guys are my last hope.
Thank you in advance.
Respectfully,

Question s22 Ultra - unlocking issues

Does anyone have any tips on how to bypass carrier lock that seems to be set up on the software side of my phone. For context:
I have had my phone over 12 months and it is paid off in full. I have requested and unlock from Boost mobile and they keep telling me they unlocked it on their end however the phone is still showing it is networked locked. I've not had any issues with them unlocking an eligible device in the past and in my experiences its usually done within 48 hours. I have been back and forth with them and they keep opening a new case and then it ends up closed stating the device is already unlocked.
I have even tried factory resetting the device after the time period. At this point I'm a bit annoyed as I have been trying to activate my new s23 ultra but my s22 ultra is still carrier locked to boost which makes re-sale harder then having an unlocked device.
I've considered unlocking the bootloader and re-flashing firmware via odin but I'm honestly not to sure if that would do anything. I have also formally filed a complaint with the FCC however that could take forever and I just want to be able to have this s22 ultra unlocked so i can activate my new phone on the line.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also it is a SM-S908U
So even when I put in another sim it doesn't prompt for an unlock code it just indicates that it's locked to the carrier.
I have tried over and over with boost and every case they open they close within 48 hours saying it's already unlocked. I honestly don't think they are being shady I just genuinely think it's incompetence and they don't know how to unlock this device. As I've never had issues with them unlocking my devices upon request in the past.
You don't need to unlock the bootloader to flash official firmware. Instead of "re-flashing" the firmware you have, I recommend flashing the official U1 variant of the firmware you're on which is the firmware that is installed on unlocked Samsung phones sold from Samsung directly. Have done this myself in past and confirmed it works, you'll have access to all unlocked content.
Flashing firmware from U to U1 will require a complete data wipe. When you turn on your phone for the first time after flashing, ensure you remove your sim card and go through the initial set up process without restoring any data from backup using Google or Samsung. After that's done, you can shut phone off and reinsert sim card. This will prevent carrier provisioned firmware from being installed on your device which includes all the carriers bloatware. You'll be 100% unlocked running on unlocked firmware without having to unlock bootloader or root your device. Unlocking bootloader is only required when you flash unofficial ROMs. There's plenty of guides which I'm sure you can figure out how to properly flash official firmware which will confirm what I'm telling you.
After that's done, follow this GUIDE for instructions on how to unlock all US/CA LTE and NR5G bands (Includes instructions on removing FRP which is a requirement for some devices).
Thank you!
This is what I was looking for. I had already downloaded the u1 firmware last night but just didn't want to waste my time as it will wipe data again.
I'll try this out now thanks! Also does csc or home csc need to be flashed with it?
bingblop said:
You don't need to unlock the bootloader to flash official firmware. Instead of "re-flashing" the firmware you have, I recommend flashing the official U1 variant of the firmware you're on which is the firmware that is installed on unlocked Samsung phones sold from Samsung directly. Have done this myself in past and confirmed it works, you'll have access to all unlocked content.
Flashing firmware from U to U1 will require a complete data wipe. When you turn on your phone for the first time after flashing, ensure you remove your sim card and go through the initial set up process without restoring any data from backup using Google or Samsung. After that's done, you can shut phone off and reinsert sim card. This will prevent carrier provisioned firmware from being installed on your device which includes all the carriers bloatware. You'll be 100% unlocked running on unlocked firmware without having to unlock bootloader or root your device. Unlocking bootloader is only required when you flash unofficial ROMs. There's plenty of guides which I'm sure you can figure out how to properly flash official firmware which will confirm what I'm telling you.
After that's done, follow this GUIDE for instructions on how to unlock all US/CA LTE and NR5G bands (Includes instructions on removing FRP which is a requirement for some devices).
Click to expand...
Click to collapse
So I flashed the u1 firmware and although the "network lock status" disappeared from the settings menu it still appears the device is carrier locked to boost.
I imagine they just didn't correctly unlock on their end.
This is very frustrating hopefully the FCC complaint prompts them to take care of it.
With the u1 firmware if they were to send on their servers for the device to be unlocked do you know if that would potentially create any issues? Do you think I should flash back to the U firmware just to play it safe?
Ya no way they unlocked it like you said. I'm not sure how that would effect it. You shouldn't have to switch back. U1 firmware doesn't carrier unlock you, but it will tell you if you are carrier locked though without a shadow of doubt. Once they properly unlock you should be fine with U1 firmware. Decision to jump back to be safe is a lot of work lol. Your decision.
I personally, would try calling again and try to get a different rep who knows what to do. A lot of these people don't know what they're doing. Keep in mind, once they do unlock you, it could take a little bit to take effect (Could be instant, could take some time can't give you estimate, it was instant for me once I rebooted, but I have T-Mobile) and would only appear as unlocked after a reboot. Have you tried using a different carriers sim card to make sure it doesn't work?
Sorry, this must be super frustrating to go through. Sounds like you're at the point that nobody here could help further though. Just offering up some tips you probably already know. Good luck!
To add to that ask to speak to a higher up (account manager or otherwise) and let them know you've filed a complaint with the FCC for violating not only the law but their own terms and conditions. This should light a fire under their ass.
bingblop said:
Ya no way they unlocked it like you said. I'm not sure how that would effect it. You shouldn't have to switch back. U1 firmware doesn't carrier unlock you, but it will tell you if you are carrier locked though without a shadow of doubt. Once they properly unlock you should be fine with U1 firmware. Decision to jump back to be safe is a lot of work lol. Your decision.
I personally, would try calling again and try to get a different rep who knows what to do. A lot of these people don't know what they're doing. Keep in mind, once they do unlock you, it could take a little bit to take effect (Could be instant, could take some time can't give you estimate, it was instant for me once I rebooted, but I have T-Mobile) and would only appear as unlocked after a reboot. Have you tried using a different carriers sim card to make sure it doesn't work?
Sorry, this must be super frustrating to go through. Sounds like you're at the point that nobody here could help further though. Just offering up some tips you probably already know. Good luck!
Click to expand...
Click to collapse
Yeah I have tried other carriers sims and e-sims its for sure still locked. I have been speaking with a different rep every 48 hours because i keep having to call them back. They all seem pretty clueless they just tell me they are escalating it to the managers and then when i check back after the 48 hours(because its still not unlocked) they close the case that they opened stating that it was already unlocked.
I've had a rep tell me it was something on my end maybe - that advised me i need to factory reset it - which i did for the sake of being able to tell them i did. that obviously was nothing more than a waste of time. I've had another one tell me i need to contact samsung. Which i did and samsung basically laughed at me stating that only the carrier can unlock it and that they couldnt assist me(which i also knew before reaching out to them) all for the sake of going through this whole process so that the next rep in 48 hours can try to tell me the same thing.
I will probably just dirty flash back to the U firmware - i worry that the phone may not correctly take the unlock if I'm on u1.
On u1 I get prompted for an unlock code when i put in another Sim:
On the U firmware it doesnt prompt for a code when using another sim it just give me a message to contact carrier.
Also in more connection settings on the U firmware it shows the network lock status under more connection settings whereas on the U1 firmware it doesnt.
Contacted them again this morning via chat and this is what im dealing with(I have added "Me:" to the lines that i typed to them, to help distinguish myself from the boost rep):
"
We have checked your device unlock request and upon checking here, the case for unlocking was already resolved.
ME: no it has not
they keep closing the case and have not unlocked the device
Can you please go to Settings > General > About > Look for Carrier Lock.
1) If it says No SIM restrictions, then your phone is unlocked. If it says SIM locked or anything else, it is locked.
ME: there is no general option on samsung
Please go to About phone.
ME: there is network lock status in connections > more connection settings and its still locked
I'd like to try a power cycle on your phone to make it reacquire the network after the reboot. Press and hold the power button, which is typically along the side or top of the device until the device powers off completely
ME: no i have done that many times
ME: u guys have not unlocked it
ME: i can provide screen shots proving it is still locked
Uploaded image
Please give me 2-4 minutes to check my resources for the best possible resolution for your concern. I will get back with you and get this resolved before we end this chat session.
Your device appears to be eligible for unlocking. The process can take up to two business days to complete. Unlocking a device does not automatically make it operable with another carrier's network. Even when a device is unlocked it needs to be compatible with the other carrier's network. To ensure that your device receives the unlock notification follow these instructions: You will receive a text message once your phone is unlocked. When you receive this text message, make sure your Boost SIM card is still in the device, and perform the Update Data Profile (on Android phones.) This is typically done by accessing Settings, then tap System Updates, and then tap Update Data Profile. For inactive devices, this function should be performed within 14 days of the text notification. All Android devices must have the Boost SIM inserted to receive the Boost unlock notification.
Uploaded image
ME:i have went through that process EVERY TIME my boost sim card has remained in the phone the entire time
ME: phone powered on
ME: connected to the network
Me: waited 48 hours
Me: waited another 48 hours
ME:waitied another 48 hours
The reason why it takes longer is because our specialist needs to escalate this to a higher up for full validation."
I'm just very annoyed. Thanks for trying to help out though I guess I'll just have to wait for the FCC complaint to prompt boost to get someone who knows what they are doing to take care of it.
dj24 said:
To add to that ask to speak to a higher up (account manager or otherwise) and let them know you've filed a complaint with the FCC for violating not only the law but their own terms and conditions. This should light a fire under their ass.
Click to expand...
Click to collapse
Have done that. Per the FCC they have been served and have 30 days to reach back out to me. It's just so frustrating. I'd like to be able to activate my s23 ultra and dont want to keep waiting lol. Even when I spoke with a supervisor who sent the case to their manager i checked back after the 48 hours and they just closed it again stating the device was already unlocked. Which it absolutely has not been.
Their incompetence is mind boggling. I really hope going the FCC route will bring the resolution you richly deserve.
tytyty11 said:
Have done that. Per the FCC they have been served and have 30 days to reach back out to me. It's just so frustrating. I'd like to be able to activate my s23 ultra and dont want to keep waiting lol. Even when I spoke with a supervisor who sent the case to their manager i checked back after the 48 hours and they just closed it again stating the device was already unlocked. Which it absolutely has not been.
Click to expand...
Click to collapse
Can you not take it to their physical store and have them look at it?
TheMystic said:
Can you not take it to their physical store and have them look at it?
Click to expand...
Click to collapse
I could, however, most boost mobiles stores are more like authorized vendors who just operate under their name. I'm doubtful that the experience will be much better. If I get no results from the FCC complaint I'd consider trying that but im doubtful they will be any more competent.
tytyty11 said:
I could, however, most boost mobiles stores are more like authorized vendors who just operate under their name. I'm doubtful that the experience will be much better. If I get no results from the FCC complaint I'd consider trying that but im doubtful they will be any more competent.
Click to expand...
Click to collapse
You have already wasted a lot of time on something that shouldn't exist to begin with. This includes the long posts here on XDA. .
Since they haven't been of any help as their system incorrectly reports it having been unlocked, and each time they ask you to wait 48 hours, you're better off visiting one of their 'main' stores or the head office directly and sort this out.
May be carry a written complaint too and get them to acknowledge receiving it.
Not sure if you've seen this yet but this is somebody with the same problem you're having with Boost Mobile and actually received a solution about 45 days later. https://androidforums.com/threads/p...mobile-claims-it-is-already-unlocked.1345103/

Categories

Resources