There are a lot of Verizon branded unlocked Pixel 3. It is reported on the web that eSim has been disabled on these. However, a quick check with *#06# shows two IMEI on this phone. So maybe eSim is there. I need eSim to use International roaming using USMobile plans. Anybody have any ideas about what happened to the eSim on this phone?
rajivtiwary said:
There are a lot of Verizon branded unlocked Pixel 3. It is reported on the web that eSim has been disabled on these. However, a quick check with *#06# shows two IMEI on this phone. So maybe eSim is there. I need eSim to use International roaming using USMobile plans. Anybody have any ideas about what happened to the eSim on this phone?
Click to expand...
Click to collapse
I am fine to root this phone. Will that enable eSim?
Code:
adb shell settings put global euicc_provisioned 1
I have had a personal conversation with a representative at Google fi and Google. Unfortunately because Google has no idea how Verizon restricted the use of this function, unfortunately any pixel 3 with a sku from Verizon is unable to have this feature activated at this moment. However they expressed interest in that if I discover a way to activate it and file a bug report, they will most certainly be interested in looking into the idea of activating the future on all pixel 3s.
In the meantime they do offer a free SIM card for anyone who wants to join Google fi and has a Verizon pixel 3. They have confirmed that although the device is Verizon made or rather Verizon issued, their SIM card for Google fi does indeed work on this device. It's just unfortunate you need the physical SIM card. If you do not get the SIM card through Google you will have to pay about $10 maybe a little bit more to get it anywhere else.
rajivtiwary said:
I am fine to root this phone. Will that enable eSim?
Click to expand...
Click to collapse
How to root a Verizon pixel 3/3xl please?
Pixel 3xl said:
Code:
adb shell settings put global euicc_provisioned 1
Click to expand...
Click to collapse
My Phone is a refurbished one. Imei.info says it was originally purchased in Japan. With no esim option.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have tried adb shell settings put global euicc_provisioned 1. nothing happens. No + Appears for me to add network.
I have tried adb shell get props euicc_provisioned . It shows that the property has been set to 1.
Pixel 3xl said:
How to root a Verizon pixel 3/3xl please?
Click to expand...
Click to collapse
See my recent post in the thread you commented on earlier. I think I'm getting closer. One thing that works in my favor is an existing unpatched CVE in citadel
captainwifi said:
My Phone is a refurbished one. Imei.info says it was originally purchased in Japan. With no esim option.
View attachment 5306635
I have tried adb shell settings put global euicc_provisioned 1. nothing happens. No + Appears for me to add network.
I have tried adb shell get props euicc_provisioned . It shows that the property has been set to 1.
Click to expand...
Click to collapse
There is no real distinguishable way to tell whether your phone is actually through Verizon or not. The only way I pretty much was able to tell was looking through the installed applications using an activity launcher. It lists the package names such as com.package.name. one of the carrier setup applications is a Verizon application to set up a phone through Verizon. That's pretty much how I got the message this was a Verizon phone. Google says on any pixel 3 phone that has a Verizon SKU, the esim option is disabled. They don't know how Verizon did it therefore they do not have a process to activate it. They did not however deny my process did anything and seemed genuinely intrigued by the fact I even managed to get that far. That tells me I can probably do more but I only just stumbled upon this and never looked into it any further because I never had any intentions of looking into it any further. Only because I didn't think anybody had any interest in it and I stand corrected. If I come across anything else I will gladly update everybody.
captainwifi said:
My Phone is a refurbished one. Imei.info says it was originally purchased in Japan. With no esim option.
View attachment 5306635
I have tried adb shell settings put global euicc_provisioned 1. nothing happens. No + Appears for me to add network.
I have tried adb shell get props euicc_provisioned . It shows that the property has been set to 1.
Click to expand...
Click to collapse
Try
*#*#794824746#*#*
In your dialer
It will give you a message esim enabled
Try and see if it works.
I got the esim enable message. Thanks. But still stuck in the checking network info loop.
This thread hasn't been active in awhile, but thought I'd add my experience.
I have a vzw pixel3, but it was bought on Woot and it was new in box, never activated. Following another thread that indicated; remove vzw sim, minimal startup but connect wifi, enable dev options, select oem unlock. It worked.
I immediately did a firmware update with latest google generic 06/05 zip. Then decided to relock bootloader. No probs, and it can still be unlocked.
Then, today, tried info in this thread. Sure enough, changed the setting to 1 and then a '+' sign showed up for additional networks. Followed though with that and 2 showed up; Google Fi and Sprint, and also an option to scan a Q code if your's wasn't listed.
So, I guess one can say that the vzw phones, so long as they haven't been activated on vzw network, can be made to work as one might like. A big **IF** though, I realize.
AsItLies said:
This thread hasn't been active in awhile, but thought I'd add my experience.
I have a vzw pixel3, but it was bought on Woot and it was new in box, never activated. Following another thread that indicated; remove vzw sim, minimal startup but connect wifi, enable dev options, select oem unlock. It worked.
I immediately did a firmware update with latest google generic 06/05 zip. Then decided to relock bootloader. No probs, and it can still be unlocked.
Then, today, tried info in this thread. Sure enough, changed the setting to 1 and then a '+' sign showed up for additional networks. Followed though with that and 2 showed up; Google Fi and Sprint, and also an option to scan a Q code if your's wasn't listed.
So, I guess one can say that the vzw phones, so long as they haven't been activated on vzw network, can be made to work as one might like. A big **IF** though, I realize.
Click to expand...
Click to collapse
I can confirm I am able to reproduce exactly what you are seeing on a Vzw unlocked Pixel 3 . Unfortunately, I believe that Vzw wiped the device EID before shipping these phones. I am unable to view the individual devices EID which is required to register the device as an Esim. The processes outlined above appear to be simply software locks to keep you out of something that is not available on the device. I would love for someone to prove me wrong on this theory.
woodysgate said:
I can confirm I am able to reproduce exactly what you are seeing on a Vzw unlocked Pixel 3 . Unfortunately, I believe that Vzw wiped the device EID before shipping these phones. I am unable to view the individual devices EID which is required to register the device as an Esim. The processes outlined above appear to be simply software locks to keep you out of something that is not available on the device. I would love for someone to prove me wrong on this theory.
Click to expand...
Click to collapse
I don't think you're wrong actually. I didn't go any farther than what I mentioned, iow, didn't actually add an esim account.
But research and trying to add acct, yeah, no EID is a big issue. I didn't try extensively as I don't need esim ability, but thought after what I'd done, unlock, flash generic rom, etc, that everything would be working... and mostly it is, but not esim it appears.
alas, cheers
Related
Hi
i have successfuly unbrand my locked,vodafone branded 8X and flash a Stock HTC rom ! :victory:
the process has been tested on PM232****/c620e Device & also 8S using different filename....
this process bypass the CID check like Wp7 goldcard & can also fix some bad flash/reboot loop.
Caution!
use at your own risk.
I take no responsibility for any conflict or damage to your device
Requirements:
-An Y-cable
-sd card or usb drive key
-the 3 .nbh extracted from those 2 exe using winrar:
official rom HTC_Europe_2.00.401.03
ACDU FIX*
-RUU_Signed.nbh
-UEFI_signed.nbh
-ACDU_UEFI_PROV_KEY.nbh
How to flash:
1- Format your sdcard or usb key in fat32
2-Copy the file .nbh you want to flash to the usb key
3-Rename it ACDUDIAG.nbh
4-Connect the usb key to the Y-cable powered
5-Shutdown the phone press camera button and connect the cable
you will see the text ACDUDIAG.nbh on top left during 1 second
then the flash will start.
___________________________________________________________________
For my european device with Bootloader 162966 i have flash in this order:
-UEFI_signed.nbh
-ACDU_UEFI_PROV_KEY.nbh
-UEFI_signed.nbh
-RUU_Signed.nbh
-ACDU_UEFI_PROV_KEY.nbh
-UEFI_signed.nbh
* Notice:
(try different order for flash files if you have problem or if stuck on bootloader screen with uefi message)
I have used this step but i think you can directly flash
UEFI_signed.nbh then -RUU_Signed.nbh without Acdu depending on your software version
<3
tofu- said:
<3
Click to expand...
Click to collapse
Sadly doesn't work on an Orange handset (UEFI 161722). It sees the nbh file, scrolls through a list of partitions, and then ends up at the bootloader after 2-3 seconds.
David Horn said:
Sadly doesn't work on an Orange handset (UEFI 161722). It sees the nbh file, scrolls through a list of partitions, and then ends up at the bootloader after 2-3 seconds.
Click to expand...
Click to collapse
D'oh - bootloop.
Remember those images posted of the Windows recovery menu on a Windows Phone? Well, they weren't fake.
David Horn said:
D'oh - bootloop.
Remember those images posted of the Windows recovery menu on a Windows Phone? Well, they weren't fake.
Click to expand...
Click to collapse
Woohoo! It worked (eventually). Not entirely sure the instructions above are entirely in the right order, but a random combination followed by a hard reset and re-flash got me back into Windows. The question is, has this fixed the missing features that Orange for whatever reason stripped out?
Update: Yep, there they are... Though I am somewhat disappointed that I don't get to take the phone back to the shop with the Windows Recovery Menu on display.
Would this work on my Canadian phone (Bell Mobility), even though the RUU if for the European version?
EDIT: Ummm, it seems my phone is a PM2330002 and not PM232xx...
Portuguese (Brazil)??
I would like to know if this rom has multi-language and if has Portuguese (Brazil). would it be possible to someone who was successful in installing the rom to tell me this?
Please help!
@xboxmod
I get ACDU_UEFI_PROV_KEY.nbh file?
{
"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"
}
Video
Could you please make a video on how to do that ...
thanks :good: :fingers-crossed:
Anyone know if this will work on a Verizon HTC 8X? I am a little hesitant to try and force this flash and have it brick the phone. Attached is a screen shot of the software/hardware version.
I bought this phone from Verizon due to them selling it "unlocked" and under the assumption that Microsoft/HTC would be controlling the updates and not Verizon. I was wrong, even though the phone is “unlocked” Verizon is blocking MMS and internet connection sharing even if my SIM supports said features. An HTC rep has also confirmed that Verizon is blocking such features after several support calls. Talking to Verizon they have no knowledge of any update forth coming to Windows Phone 8. Verizon refered me to HTC even after I instructed them the international and AT&T/T-Mobile verisions have the Portico update, they denied any update exists!!
Same problem
Brett VanKirk said:
Anyone know if this will work on a Verizon HTC 8X? I am a little hesitant to try and force this flash and have it brick the phone. Attached is a screen shot of the software/hardware version.
I bought this phone from Verizon due to them selling it "unlocked" and under the assumption that Microsoft/HTC would be controlling the updates and not Verizon. I was wrong, even though the phone is “unlocked” Verizon is blocking MMS and internet connection sharing even if my SIM supports said features. An HTC rep has also confirmed that Verizon is blocking such features after several support calls. Talking to Verizon they have no knowledge of any update forth coming to Windows Phone 8. Verizon refered me to HTC even after I instructed them the international and AT&T/T-Mobile verisions have the Portico update, they denied any update exists!!
Click to expand...
Click to collapse
Hello,
I bought the same phone at Microsoft store at Chicago.
Although it works fine in Israel, I have some problems.
I cant send SMS (it adds to all numbers +1 - like in States).
I can recieve SMS of course. I also cant share internet connection(hot spot).
I talked to HTC guys who sent me to Verizon and they sent me to F#@[email protected]# myself .
So I would like very much to set the European ROM with my PC on HTC 8x.
Can anyone tell me how to do it? I have normal USB cable to connect HTC to
my Win7 or W8 PC to transfer music or pics.
Thanks,
Aaron
Hi thanks for the post..
I'm just wondering if this will work on an 8X that has already had an OTA update?
mans550 said:
Hi thanks for the post..
I'm just wondering if this will work on an 8X that has already had an OTA update?
Click to expand...
Click to collapse
this is big news! If this bypasses the cid, could you not make this a "custom" rom? Somewhat like what devs were doing with Motorola Droid X when Motorola was locking their bootloaders down and the eFuse? In theory the signatures and verifications would be "officially signed".
Where can I get "ACDU_UEFI_PROV_KEY.nbh" file from?
waiting for this ..anybody tried on at&t ...?
cannot try because no ACDU_UEFI_PROV_KEY.nbh file anywhere.
Hello. I was wondering if anyone has been able to achieve this on the Verizon HTC 8X. I'm tired of waiting for Portico from them and if I could unbrand my device then I could receive Portico as well as have the ability to group text. Also I'm not sure what you mean by a "Y Cable". If you could elaborate on that I would greatly appreciate it.
Thank you!
DrummerJDM25 said:
Hello. I was wondering if anyone has been able to achieve this on the Verizon HTC 8X. I'm tired of waiting for Portico from them and if I could unbrand my device then I could receive Portico as well as have the ability to group text. Also I'm not sure what you mean by a "Y Cable". If you could elaborate on that I would greatly appreciate it.
Thank you!
Click to expand...
Click to collapse
You should check if the hard/software versions match, If they do you can try. If they don't you can still try but risk of the device not booting anymore.
Y cable is two female USB plugs connected, and a USB male plug only for +5v DC. check here:
http://forum.xda-developers.com/showthread.php?t=1676794
kid1988 said:
You should check if the hard/software versions match, If they do you can try. If they don't you can still try but risk of the device not booting anymore.
Y cable is two female USB plugs connected, and a USB male plug only for +5v DC. check here:
http://forum.xda-developers.com/showthread.php?t=1676794
Click to expand...
Click to collapse
My bootloader version is 157404 which is before the version listed on page one. However since I'm a noob to Windows Phone I'd rather have someone with more experience attempt it first and let me know the results. I'd really like to get the group text feature that Verizon disabled back.
I currently see the whoopping 4 days of average phone usage after this update, it was 1.5 days max before.
Can somebody else confirm the prolonged battery life, or its just a placebo effect?
I bought an xt925 on eBay. It originated in Latin America (I believe Claro Puerto Rico). I am trying to use it on AT&T, using CM 10.2.
I have tried everything I can find to get this phone to detect the SIM card. I cut my SIM card from my previous phone. It still works with an adapter in the previous phone (Samsung Captivate). It also works without the adapter in a Nokia Lumia 920. I tried putting in my girlfriend's SIM from her iPhone 4S into the xt925, but that wasn't detected either. I have tried flashing several other ROMs (CM 10.1, Slim, Xenon, etc.) with the same results.
I have done a lot of searching, and it seems everyone else having a similar problem does not see their Baseband or IMEI. I see both of those things fine. It's acting as if there is no SIM in there at all. No voice, no data.
If I go to Network Operators in the settings, it detects AT&T and T-Mobile as options. When I try to manually select either of them, it says "Your SIM card does not allow a connection to this network."
Can someone steer me in the right direction? Do I have a hardware issue? Modem/radio?
isharted said:
I bought an xt925 on eBay. It originated in Latin America (I believe Claro Puerto Rico). I am trying to use it on AT&T, using CM 10.2.
I have tried everything I can find to get this phone to detect the SIM card. I cut my SIM card from my previous phone. It still works with an adapter in the previous phone (Samsung Captivate). It also works without the adapter in a Nokia Lumia 920. I tried putting in my girlfriend's SIM from her iPhone 4S into the xt925, but that wasn't detected either. I have tried flashing several other ROMs (CM 10.1, Slim, Xenon, etc.) with the same results.
I have done a lot of searching, and it seems everyone else having a similar problem does not see their Baseband or IMEI. I see both of those things fine. It's acting as if there is no SIM in there at all. No voice, no data.
If I go to Network Operators in the settings, it detects AT&T and T-Mobile as options. When I try to manually select either of them, it says "Your SIM card does not allow a connection to this network."
Can someone steer me in the right direction? Do I have a hardware issue? Modem/radio?
Click to expand...
Click to collapse
The phone is either SIM locked or the US carriers are blocked via NV Item 8322:
http://forum.xda-developers.com/showthread.php?t=2166542
You have to be running the stock firmware (not CM) to perform the unlock.
kabaldan said:
The phone is either SIM locked or the US carriers are blocked via NV Item 8322:
http://forum.xda-developers.com/showthread.php?t=2166542
You have to be running the stock firmware (not CM) to perform the unlock.
Click to expand...
Click to collapse
Ah, that makes sense. Thanks for the reply, kabaldan. I'll see if I can make some time to work through this tonight and post my results.
The eBay post said it was unlocked, but I doubt it went though that process.
I flashed the stock firmware and went through the steps. It was reading all of the data fine (IMEI, ESN, PESN, etc.). When I did a read on 8322, it populated the Data box with 00. However, the Read button was red instead of green. Not sure if that's expected.
I rebooted the phone. Still the same issue. I went ahead and wrote 00 to 8322. Still no difference.
Is there a way I can tell if it is SIM locked?
I'm bumping this because it fell off the first page. Does anyone have any advice for me?
Im having a similar issue with a razr hd (xt925)
My problemis that the phone does not read an item 8322. Any help help for us both is appreciated!:cyclops:
DaNpPR said:
My problemis that the phone does not read an item 8322. Any help help for us both is appreciated!:cyclops:
Click to expand...
Click to collapse
It sounds like you actually have the XT926 which is typically for Verizon. You'll need to do the NV edit on 8322, if the button shows up red then something is wrong. Check to make sure you have proper drivers for ADB / etc and are booted into the proper mode when doing the edit (I can't remember now -- Factory mode comes to mind. It appears to boot normally but when you get into the OS you'll see the battery icon with a ?.
Your EBay seller is technically correct, the phone is unlocked for every carrier except ATT/TMobile in the US (without the NV edit).
-- Dan
I have decided to give this another try. I'll post some data to explain what I'm seeing. Can anyone tell me if the symptoms I see are consistent with a locked SIM card? Or could it possibly be another issue?
Here's what I get from RadioComm
{
"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"
}
Anyone know what the red Read button means?
Here's the full output if that helps:
Code:
Sending 'NVRead' command with data '822000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000' to the radio...
Sent to radio: 268220000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000004C647E
Returned from radio: 26822000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000500F41A7E
NVRead ==>SUCCESSFUL
Time to execute command: 0.012 seconds.
Command timeout set to : 15 seconds.
EDIT: I after doing the NV item 8322, I haven't tried a newer SIM card. I put in a "dummy" SIM from a phone that was purchased and never activated, and the SIM errors went away. I'll try to pry away someone's newer, valid SIM tonight to see if I have any luck.
I went to the AT&T store and swapped out my old SIM card for a new micro SIM card. With an adapter, the new SIM with all of my older AT&T phones. I'm still getting no SIM detected on my xt925.
What else could be my issue? Does the AT&T SIM card have some protection that's blocking the xt925 from reading it? I am pretty sure other people are using AT&T SIM cards with xt925.
The only other data I have is that I purchased a Nokia Lumia 920 a while ago as an upgrade for a different line in my family plan, but I never activated that phone or SIM. If I take the SIM out of that phone, the xt925 reads the information fine. It reads the phone number of the line that I "upgraded."
Hey, title is very much self descriptive. After debloating and removing a lot of what i would think were not essentials for the phone, GPS STILL does work, but only on OsmAnd, and not on other aps that use the map, and even then it takes several minutes for me to find location on the map. I ASSUME that this is because i removed something that lets app interact with mobile towers to get location and instead it relies only on sattelites to know where i am however this is mere speculation. I'd like to know if anyone with a lot more knowledge than i have could point me at which apps this phone would use stock with GPS or location services so that i could reinstall them and see what exactly did i break.
Consider this a bump, but in more specific terms. Could anyone help me identify or show me a list of potential GPS-related functionality APKs that would make other map apps not work properly?
Come on dude. Re-flashing is clearly your only option.
You would be better asking in other more popular Samsung Galaxy forums for general advice.
TimmyP said:
Come on dude. Re-flashing is clearly your only option.
You would be better asking in other more popular Samsung Galaxy forums for general advice.
Click to expand...
Click to collapse
This is usually where most of the advice regarding modifying the OS and debloating came from so i suspected it was the best place to ask.
Releases · 0x192/universal-android-debloater
Cross-platform GUI written in Rust using ADB to debloat non-rooted android devices. Improve your privacy, the security and battery life of your device. - 0x192/universal-android-debloater
github.com
use this and connect your phone via USB cable and enable ADB debugging in developer settings and give it perms when it pops up a prompt. Then set the 3 menus on the right to say All, Disabled/Uninstalled(Try Disabled and if it doesn't show anything try Uninstalled), and All Lists. It should show you a list of all the apps you have that you got rid of and you can press the button to get it back. It might work for you or it might not. If you mess up your phone even more its on you not me.
{
"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"
}
CloudRealm said:
Releases · 0x192/universal-android-debloater
Cross-platform GUI written in Rust using ADB to debloat non-rooted android devices. Improve your privacy, the security and battery life of your device. - 0x192/universal-android-debloater
github.com
use this and connect your phone via USB cable and enable ADB debugging in developer settings and give it perms when it pops up a prompt. Then set the 3 menus on the right to say All, Disabled/Uninstalled(Try Disabled and if it doesn't show anything try Uninstalled), and All Lists. It should show you a list of all the apps you have that you got rid of and you can press the button to get it back. It might work for you or it might not. If you mess up your phone even more its on you not me.View attachment 5476313
Click to expand...
Click to collapse
Interesting, so that way i can keep track of which apk i removed?
Well, i just installed a maps app in the phone after having a reset from factory and.... Its working exactly like it used to? It still wont get GPS signal. Now im wondering what's going on.
hahaNSAgoBRRRR said:
Interesting, so that way i can keep track of which apk i removed?
Click to expand...
Click to collapse
Yep
hahaNSAgoBRRRR said:
Well, i just installed a maps app in the phone after having a reset from factory and.... Its working exactly like it used to? It still wont get GPS signal. Now im wondering what's going on.
Click to expand...
Click to collapse
Strange... maybe update the os?
You need to reflash everything with Odin *mod and start again. Sorry I cant help you as I needed it myself when I did the same with camera as I was debloating, and Im not sure how to do it.
I am, however, sure this is what you need to do. It is more than a factory reset.
Well... I did a factory reset again and this time the second that i connected the phone to the internet i downloaded a maps apk that i was using and... Yeah, it cant locate the phone, so either using only GPS no wifi the phone is hardly able to locate itself, or the phone is doing something weird about the GPS that my previous phone didn't, or the only time i accidentally dropped my phone from like 1 feet into the ground i broke something which is real unlikely, or the GPS receiver of this phone is THAT bad and my house is THAT good at blocking GPS signal.
What a weird conondrum.
I mean, crap, even google maps doesn't know where i am. Is this because i refused google's location services?
You need to reflash everything with Odin *mod and start again. Sorry I cant help you as I needed it myself when I did the same with camera as I was debloating, and Im not sure how to do it.
I am, however, sure this is what you need to do. It is more than a factory reset.
TimmyP said:
You need to reflash everything with Odin *mod and start again. Sorry I cant help you as I needed it myself when I did the same with camera as I was debloating, and Im not sure how to do it.
I am, however, sure this is what you need to do. It is more than a factory reset.
Click to expand...
Click to collapse
Dont worry dude, i already did a factory reset. My problem persists with the factory reset is the current topic of trouble to me.
FACTORY RESET WILL NOT FIX. REFLASHING ROM WILL NOT FIX.
I screwed my Camera up the same way, with just removing apks. You need to reflash the slots in odin and run multi-disabler and all that again.
TimmyP said:
FACTORY RESET WILL NOT FIX. REFLASHING ROM WILL NOT FIX.
I screwed my Camera up the same way, with just removing apks. You need to reflash the slots in odin and run multi-disabler and all that again.
Click to expand...
Click to collapse
Is it really "again" if i never did it to begin with?
Yes.
TimmyP said:
Yes.
Click to expand...
Click to collapse
Im a bit lost, how does this all work, what do you say i broke, and why do i need to use odin that factory reset wont fix?
idk why did I need odin when my camera stopped from doing the same thing? I flashed a new rom and went through initial setup, also did a factory reset, it still didnt work! Its a guess obviously since its not the exact same problem, but id say something similar is happening to your gps hardware.
TimmyP said:
idk why did I need odin when my camera stopped from doing the same thing? I flashed a new rom and went through initial setup, also did a factory reset, it still didnt work! Its a guess obviously since its not the exact same problem, but id say something similar is happening to your gps hardware.
Click to expand...
Click to collapse
Well, my issue so far seems to be quite similar to this one:
Is there a way to get GPS to work without Google Location Service constantly enabled?
The GPS on my Samsung Galaxy S2 cannot find my current location whenever Google Location Service is disabled. I have it disabled most of the time because my battery drains much faster when the ser...
android.stackexchange.com
If I were you (op) I would reflash stock, copy everything to PC (all apps/apks) and slowly remove a few at a time and test gps as I go along. I know that would take some time but eventually you would find which ones have to do with gps. You could also make a list of all the names of the apks and throw them in your "search" on a browser and see what all you can find out about them that way..
The most detailed explanation I have ever seen of descriptions of apps is definitely xXx No Limit magisk rom for OnePlus 6,7,8 devices. The dev has a user configuration file where you choose whether you want to keep, delete, replace each apk in the entire device and he has an explanation for every single app that tells what it's used for and if it's safe to delete or not. I would search all I could, and maybe do the copy/delete apk first and see what all you can find then maybe shoot No Limit rom dev a msg asking him. IDK him personally except from here using his rom when I had a OnePlus 6t but I bet he would respond. Most people will help you out "if" they can see whoever is asking for the help has already done some work in to whatever it is themselves.
Since i updated to VA2, getting this message over and over:
{
"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"
}
Any solution????
What happens when you restart it?
ashraftheboss said:
What happens when you restart it?
Click to expand...
Click to collapse
Nothing happens when i tap "Restart". Screen goes dark, when i press back, everything goes normal.
Bust the message is annoying a lot. After every 10 or 15 minutes it appear again.
I've never really seen this happen before.
Had a quick look online and this has been an issue for the S8 and S20 as well. What these people are saying is when they had 3G Sim Cards in their phone and the phone was trying to update those Sim Cards to support 4G or something along the lines.
Maybe your phone is trying something similar?
The only solutions I've found is either changing your Sim Card or wiping the cache partition, which I would only recommend after you've tried another sim card.
ashraftheboss said:
I've never really seen this happen before.
Had a quick look online and this has been an issue for the S8 and S20 as well. What these people are saying is when they had 3G Sim Cards in their phone and the phone was trying to update those Sim Cards to support 4G or something along the lines.
Maybe your phone is trying something similar?
The only solutions I've found is either changing your Sim Card or wiping the cache partition, which I would only recommend after you've tried another sim card.
Click to expand...
Click to collapse
Might be an issue, but i don't think its the case for me.
Both of my sim cards are 4G, so i'm not sure about it.
Wiping the Dalvik and Cache partition also did not help.
Did not have this isuue in VA1, its happening in VA2 and VB3.
SRooks1976 said:
Might be an issue, but i don't think its the case for me.
Both of my sim cards are 4G, so i'm not sure about it.
Wiping the Dalvik and Cache partition also did not help.
Did not have this isuue in VA1, its happening in VA2 and VB3.
Click to expand...
Click to collapse
What I would try is to take the sim cards out for a while, just to see if the pop-up comes back. If it does, then its most likely a software issue. If it doesn't, then it will most likely be an issue with either one or both of your sim cards. In that case, you could try each sim card on its own, just to see whether it is one of them that's triggering this pop-up. That would be what I'd do to sort of troubleshoot and get to the root of the problem.
I am on VA2 with XFE CSC right now and no problem so far. I also saw something about an app called AutoPreConfig that was a bit of an issue for S7 users. It isn't present on my phone, maybe it could be on your's?
ashraftheboss said:
What I would try is to take the sim cards out for a while, just to see if the pop-up comes back. If it does, then its most likely a software issue. If it doesn't, then it will most likely be an issue with either one or both of your sim cards. In that case, you could try each sim card on its own, just to see whether it is one of them that's triggering this pop-up. That would be what I'd do to sort of troubleshoot and get to the root of the problem.
I am on VA2 with XFE CSC right now and no problem so far. I also saw something about an app called AutoPreConfig that was a bit of an issue for S7 users. It isn't present on my phone, maybe it could be on your's?
Click to expand...
Click to collapse
Have you rooted your device?
No no, haven't rooted mine. Is your's rooted?
The app that's causing this issue is called CIDManager
I rooted and deleted it. Maybe you can disable it without rooting. It hasn't had any negative effects on me as of yet.
ShaDisNX255 said:
The app that's causing this issue is called CIDManager
I rooted and deleted it. Maybe you can disable it without rooting. It hasn't had any negative effects on me as of yet.
Click to expand...
Click to collapse
I don't have this app, maybe that's why I don't have the issue.
ashraftheboss said:
I don't have this app, maybe that's why I don't have the issue.
Click to expand...
Click to collapse
It's hidden in system/priv-app
I think this problem only appears when you flash another country firmware on your phone. It wasn't much of a problem in Android 11 but in Android 12 I received that message over and over again too.
ShaDisNX255 said:
It's hidden in system/priv-app
I think this problem only appears when you flash another country firmware on your phone. It wasn't much of a problem in Android 11 but in Android 12 I received that message over and over again too.
Click to expand...
Click to collapse
Oh that explains why I didn't see it, my bad
ashraftheboss said:
What I would try is to take the sim cards out for a while, just to see if the pop-up comes back. If it does, then its most likely a software issue. If it doesn't, then it will most likely be an issue with either one or both of your sim cards. In that case, you could try each sim card on its own, just to see whether it is one of them that's triggering this pop-up. That would be what I'd do to sort of troubleshoot and get to the root of the problem.
I am on VA2 with XFE CSC right now and no problem so far. I also saw something about an app called AutoPreConfig that was a bit of an issue for S7 users. It isn't present on my phone, maybe it could be on your's?
Click to expand...
Click to collapse
Both sim cards have the same issue, nothing changed.
ashraftheboss said:
No no, haven't rooted mine. Is your's rooted?
Click to expand...
Click to collapse
Yes, I always root my device. That's the reason I Switched from VIVO Y51 to Samsung Galaxy A52.
ShaDisNX255 said:
It's hidden in system/priv-app
I think this problem only appears when you flash another country firmware on your phone. It wasn't much of a problem in Android 11 but in Android 12 I received that message over and over again too.
Click to expand...
Click to collapse
I live in Pakistan and software I flashed is specifically for my country.
PAK-A525FXXU4BVB3-20220217141450.zip
I have ordered my S22 Ultra 1 TB storage ( SM-S908B) from Samsung website in UK.
I have enabled the Developers mode in settings and now when i wanted to root my phone i can't believe it... my device doesn't have the OEM Unlock option in there.
I'm wondering if i can activate the oem Unlock trough ADB. I will tray to see if possible
If anybody knows a work around please let me know
I would like to mention that I found an very interesting article about the missing OEM Unlock feature atvthis link.
Looks like Samsung have implemented an extra security feature that disables it for a week or so after farst boot. Thay did mention in an e-mail this. They are waiting for my old S21 Ultra to be received at their depot or they will lock my new device until full payment is made or old phone is received.
I will update this post once i have some news.
A very useful link for anyone interested in this process
How to Fix Missing OEM Unlock in Samsung Devices
In this tutorial, we have shared four methods that will help you to fix the missing OEM Unlock option in various Samsung devices and tablets.
www.droidwin.com
{
"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"
}
from memory; option should appear after 7 days
Or try the manual change Date & Time trick (forward by > 7 days) - may take a few attempts & reboots.
AFAIK this is related to the so called "KG state"..... there are multiple sources about this, I have this one bookmarked
elmor0 said:
Or try the manual change Date & Time trick (forward by > 7 days) - may take a few attempts & reboots.
Click to expand...
Click to collapse
This does not work unfortunately. I have the same issue as post author and tried all the different manual date change tricks with reboots and none worked.
When s22u first came out (2/15), there were demo phones at samsung shop, I went to experience s22u and found out all demo phones didn't have the OEM Unlock option. They said demo phones might lock some functions.
donkeyman1234 said:
When s22u first came out (2/15), there were demo phones at samsung shop, I went to experience s22u and found out all demo phones didn't have the OEM Unlock option. They said demo phones might lock some functions
donkeyman1234 said:
When s22u first came out (2/15), there were demo phones at samsung shop, I went to experience s22u and found out all demo phones didn't have the OEM Unlock option. They said demo phones might lock some functions.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
OEM unlock toggle was available on my s22 ultra but disappeared after a software update - I wish I could go back in time.
lanchexi said:
OEM unlock toggle was available on my s22 ultra but disappeared after a software update - I wish I could go back in time.
Click to expand...
Click to collapse
It's quite odd if oem option disappear after update.
donkeyman1234 said:
It's quite odd if oem option disappear after update.
Click to expand...
Click to collapse
Yes, that hasn't been the norm after an update but Android 12 OneUI 4.0 locks down the bootloader on S21 devices as well.
I don't have option either on S22 Ultra 512 gb unlocked
Besides US variant, I would like to know what variants do not have OEM unlock option after update.
In my case, I didn't see OEM unlock until.... turning wifi on.
bobimbap said:
In my case, I didn't see OEM unlock until.... turning wifi on.
Click to expand...
Click to collapse
Yes, the OEM unlock option only can be seen with network connected. I don't think anyone will forget to turn it on.
I have a Samsung S22 Ultra, bought it unlock from the Samsung website here in the US, so Snapdragon chip. It did not have the OEM unlock option and I have tried all the steps I found except the Odin Firmware flash because I don't know if is going to work. It is very odd that is not letting us unlock OEM
The bootloader for the US and Canadian S22's are locked and currently there is no way to unlock the bootloader. Getting an unlocked phone only gives you the ability to use it with any carrier you choose.
I also have a 1tb s22 ultra exynos UK variant. Is the option not available?
Using the S22U 12/512 UK running the latest firmware and I still have OEM Unlock option.
I have an Exynos S22 Ultra 1TB. The information floating online regarding the "OEM unlocking" toggle found within Settings > Developer options is confusing, more often than not conflicting, as many people copied and pasted the same article, modified, and re-translated many times, without checking what and if it actually works. I'll spare you with my rambling, and how I have lost my last two days researching into this and going through many failed attempts, sometimes successful ones, but ususally not. I wanted a 100% reproducible way of getting to that toggle, and I think I have found it:
1. Log out of your Samsung account
2. Log out of your Google account
3. Power OFF your device, remove SIM card
4. Boot into bootloader
5. Wipe data <- you will lose all your data, so make sure you have backups
6. Reboot system <- first option in the bootloader
7. Go through the setup process, decline/disable/skip everything, besides Samsung EULA which you must agree to, do not connect to any network, do not plug in your SIM
8. Once you reach the Home screen, go to Settings, enable Developer mode
9. Power OFF your device
10. Power ON your device, as soon as you reach the Lock screen, swipe from the top to bring the Control/Notification Centre, hit Settings, scroll to the bottom, and hit Developer settings. Now the "OEM unlock" setting should be exposed
You must do the 10th step as fast as possible. Don't overdo it, but you've got maybe 5 to 10 seconds. You've got no password to go through, so you have plenty of time. The option will be there for you to toggle ON or OFF. You may re-do the 10th step to check its status, or toggle it the other way around.
I don't know if this information matters, but I'll provide it anyway. Phone runs the latest April update, as of 29th April 2022, and the date and time was correctly set prior to the first step. During the setup process, as you do not connect to the internet, you will have to just hit Ok/Next on Date/Time as it should be already set according to your region. I have also set my phone to English US. Again, this probably doesn't matter, and I'm willing to bet this can be narrowed down even further, but at least doing all this will always give you access to that setting, and you also do not get to rely on any update server pinging you back, date/time, 7 days of wait, and all that nonsense. Given that unlocking the bootloader usually also implies wiping the user data, it's not really a big deal.
slash4real said:
I have an Exynos S22 Ultra 1TB. The information floating online regarding the "OEM unlocking" toggle found within Settings > Developer options is confusing, more often than not conflicting, as many people copied and pasted the same article, modified, and re-translated many times, without checking what and if it actually works. I'll spare you with my rambling, and how I have lost my last two days researching into this and going through many failed attempts, sometimes successful ones, but ususally not. I wanted a 100% reproducible way of getting to that toggle, and I think I have found it:
1. Log out of your Samsung account
2. Log out of your Google account
3. Power OFF your device, remove SIM card
4. Boot into bootloader
5. Wipe data <- you will lose all your data, so make sure you have backups
6. Reboot system <- first option in the bootloader
7. Go through the setup process, decline/disable/skip everything, besides Samsung EULA which you must agree to, do not connect to any network, do not plug in your SIM
8. Once you reach the Home screen, go to Settings, enable Developer mode
9. Power OFF your device
10. Power ON your device, as soon as you reach the Lock screen, swipe from the top to bring the Control/Notification Centre, hit Settings, scroll to the bottom, and hit Developer settings. Now the "OEM unlock" setting should be exposed
You must do the 10th step as fast as possible. Don't overdo it, but you've got maybe 5 to 10 seconds. You've got no password to go through, so you have plenty of time. The option will be there for you to toggle ON or OFF. You may re-do the 10th step to check its status, or toggle it the other way around.
I don't know if this information matters, but I'll provide it anyway. Phone runs the latest April update, as of 29th April 2022, and the date and time was correctly set prior to the first step. During the setup process, as you do not connect to the internet, you will have to just hit Ok/Next on Date/Time as it should be already set according to your region. I have also set my phone to English US. Again, this probably doesn't matter, and I'm willing to bet this can be narrowed down even further, but at least doing all this will always give you access to that setting, and you also do not get to rely on any update server pinging you back, date/time, 7 days of wait, and all that nonsense. Given that unlocking the bootloader usually also implies wiping the user data, it's not really a big deal.
Click to expand...
Click to collapse
I have the same problem...Is there another way to unlock the OEM unlock?