Related
I have unlock my sgh-I747M "version 4.3" via spt box , after unlock everything work well "3G + calls + signal" but I can't use carrier USSD code
how can I fix this problem ????
Are you using a custom rom?
replay
DocHoliday77 said:
Are you using a custom rom?
Click to expand...
Click to collapse
no I use stock rom, No root, No CWM
Im assuming since you unlocked you are using it on a different carrier then. May be that the codes you are entering are trying to communicate with AT&T networks and if you arent with AT&T is probably why they aren't working.
Just a guess.
replay
DocHoliday77 said:
Im assuming since you unlocked you are using it on a different carrier then. May be that the codes you are entering are trying to communicate with AT&T networks and if you arent with AT&T is probably why they aren't working.
Just a guess.
Click to expand...
Click to collapse
is there any way to use ussd code on this phone "and file or program"
No idea. Sorry. Might be something hidden in one of the xml files, or it may be hard coded into an app. Im really not sure.
Your non carrier-specific codes work, right?
replay
DocHoliday77 said:
No idea. Sorry. Might be something hidden in one of the xml files, or it may be hard coded into an app. Im really not sure.
Your non carrier-specific codes work, right?
Click to expand...
Click to collapse
yes none carrier code work perfectly like *#06# and many other.
Hello,
In different locations on the 'net', I read that the Verizon Google Pixel XL cannot be rooted because the bootloader is locked. Can someone clarify if this is true?
I just received a brand new Pixel XL from Verizon, but have not connected it to WiFi and have not yet activated my service and I want to know if I can root my Pixel XL with the following:
BL = 8996-012001-1611091517
Baseband = 8996-012511-1611190200
Console = DISABLED
Secure Boot = PRODUCTION
Device is LOCKED
Thanks in advance!
gil_happy said:
Hello,
In different locations on the 'net', I read that the Verizon Google Pixel XL cannot be rooted because the bootloader is locked. Can someone clarify if this is true?
I just received a brand new Pixel XL from Verizon, but have not connected it to WiFi and have not yet activated my service and I want to know if I can root my Pixel XL with the following:
BL = 8996-012001-1611091517
Baseband = 8996-012511-1611190200
Console = DISABLED
Secure Boot = PRODUCTION
Device is LOCKED
Thanks in advance!
Click to expand...
Click to collapse
Hello... I would simply power it on without sim. Skipping the google setup and go to settings > about phone. If your Android version is below 7.1.1, ex: 7.1, you can try this:
http://theroot.ninja/depixel8.html
Some users reported that they have received new Verizon Pixel XL devices on 7.1.1 where they were able to toggle the "OEM unlock" in developer options (tap build number 7 times in about phone to see developer options in settings) and go in fastboot unlocking their bootloader directly with:
fastboot flashing unlock
Good luck... :good:
Shoot.... I removed the SIM (and didn't connect to WiFi), performed the very minimum set up so I could get into the settings > and unfortunately my version is 7.1.1.
I don't know if this had anything to do with it, but the phone was shipped directly from Verizon with the SIM card already installed (it is not activated because my old cell phone on Project Fi is still working), and I turned on my phone earlier today for 10 minutes or so and didn't touch anything. Hopefully it did not attempt any type of upgrade, etc during this time.
gil_happy said:
Shoot.... I removed the SIM (and didn't connect to WiFi), performed the very minimum set up so I could get into the settings > and unfortunately my version is 7.1.1.
I don't know if this had anything to do with it, but the phone was shipped directly from Verizon with the SIM card already installed (it is not activated because my old cell phone on Project Fi is still working), and I turned on my phone earlier today for 10 minutes or so and didn't touch anything. Hopefully it did not attempt any type of upgrade, etc during this time.
Click to expand...
Click to collapse
Did you try to activate developer options and toggle the "OEM unlock" though?
Good luck...
5.1 said:
Did you try to activate developer options and toggle the "OEM unlock" though?
Good luck...
Click to expand...
Click to collapse
Unfortunately the 'OEM unlocking' option is grayed out.
Ya I think Verizon caught on finally and that's why warranty (Asurion) and newer ship outs are coming g with 7.1 .1. I got lucky and had ordered mine from local Verizon store and was shipped to my house. Turned on and saw was on 7.1 so I immediately ran the depixel8 software and now enjoy unlocked bootloader and rooted if I desire. But I am enjoying PN non rooted !!
gil_happy said:
Unfortunately the 'OEM unlocking' option is grayed out.
Click to expand...
Click to collapse
Sorry... Use your phone and see if it has any manufacturing defect or any little bug and claim a warranty replacement. Hopefully you'll be luckier and have an unlock option.
Good luck...
aaronpw0621 said:
Ya I think Verizon caught on finally and that's why warranty (Asurion) and newer ship outs are coming g with 7.1 .1. I got lucky and had ordered mine from local Verizon store and was shipped to my house. Turned on and saw was on 7.1 so I immediately ran the depixel8 software and now enjoy unlocked bootloader and rooted if I desire. But I am enjoying PN non rooted !!
Click to expand...
Click to collapse
Lucky, got mine at a Verizon corporate store and came with 7.1.1.
Ok, so it sounds like there is no current root solution on 7.1.1 - I think that is where my confusion was when researching this topic on the 'net'.
So I just bought a Verizon Pixel XL off ebay with the intention of using it on T-Mobile because I was under the impression that taking it to T-Mobile was no issue and would be no different than using a google store one on T-Mobile. Although I am reading some concerning threads about the bootloader issue. If this phone happens to have 7.11 will I be unable to flash the T-Mobile factory image onto it? Or is there really no benefit in doing this anyway? Do I and will I be able to flash at least the T-Mobile radio over to it?
Then if it is before 7.11 and I unlock the bootloader right away can I keep it unlocked even if I play around with images and stuff such as trying out the O beta? or do I have to avoid Factory images once its unlocked and only use custom roms?
Thanks in advanced!
tuxdreamerx said:
So I just bought a Verizon Pixel XL off ebay with the intention of using it on T-Mobile because I was under the impression that taking it to T-Mobile was no issue and would be no different than using a google store one on T-Mobile. Although I am reading some concerning threads about the bootloader issue. If this phone happens to have 7.11 will I be unable to flash the T-Mobile factory image onto it? Or is there really no benefit in doing this anyway? Do I and will I be able to flash at least the T-Mobile radio over to it?
Then if it is before 7.11 and I unlock the bootloader right away can I keep it unlocked even if I play around with images and stuff such as trying out the O beta? or do I have to avoid Factory images once its unlocked and only use custom roms?
Thanks in advanced!
Click to expand...
Click to collapse
Only thing that matters is if the origin of the phone is Verizon or Google.
If the origin is Google you can install the Google factory image and use it on anywhere, unlock the bootloader, root and have a grand old time.
If the origin is Verizon you are relegated to the Verizon image regardless of where you use the phone, no flashing for you.
Compare the build code of your phone to the build codes on google factory image website and you will know what you have.
good luck
parakleet said:
Only thing that matters is if the origin of the phone is Verizon or Google.
If the origin is Google you can install the Google factory image and use it on anywhere, unlock the bootloader, root and have a grand old time.
If the origin is Verizon you are relegated to the Verizon image regardless of where you use the phone, no flashing for you.
Compare the build code of your phone to the build codes on google factory image website and you will know what you have.
good luck
Click to expand...
Click to collapse
Well this was a display model I guess, no specifics on what kind of store but its listed as being a Verizon model. So I may be SOL. As far as working on T-Mobile if that is the case are there any downsides to using the Verizon model aside from flashing?
tuxdreamerx said:
Well this was a display model I guess, no specifics on what kind of store but its listed as being a Verizon model. So I may be SOL. As far as working on T-Mobile if that is the case are there any downsides to using the Verizon model aside from flashing?
Click to expand...
Click to collapse
Verizon model is fine for what the phone is.
You shouldn't have any issues using it on T-Mobile USA . Verizon phones are sim unlocked . The only thing with the Verizon version is that if it had the update where they don't let the bootloader unlock then you can't unlock it and root. Besides that you can use it on TMobile as a regular Google phone.
Sent from my Pixel XL using Tapatalk
parakleet said:
Only thing that matters is if the origin of the phone is Verizon or Google.
If the origin is Google you can install the Google factory image and use it on anywhere, unlock the bootloader, root and have a grand old time.
If the origin is Verizon you are relegated to the Verizon image regardless of where you use the phone, no flashing for you.
Compare the build code of your phone to the build codes on google factory image website and you will know what you have.
good luck
Click to expand...
Click to collapse
This is partially false, I'm using a Verizon pixel XL on TMO and when I dropped out of beta, Google rolled out the TMO branch to my phone.
If you can depixl8 it and unlock the bootloader, you can flash custom Roms or the factory images to your heart's desire with no issues. Just never relock the bootloader, since it won't be able to be unlocked again(if it truly is a Verizon pixel XL)
parakleet said:
Only thing that matters is if the origin of the phone is Verizon or Google.
If the origin is Google you can install the Google factory image and use it on anywhere, unlock the bootloader, root and have a grand old time.
If the origin is Verizon you are relegated to the Verizon image regardless of where you use the phone, no flashing for you.
Compare the build code of your phone to the build codes on google factory image website and you will know what you have.
good luck
Click to expand...
Click to collapse
You can sideload updates to a locked device so OP could sideload a current ota from tmobile. It can in fact beneficial to run the tmobile software on tmo because of optimizations for network connectivity
If you haven't updated it yet and its version is older than last November, you should be able to unlock the bootloader. Once it's been updated to a newer version, it can't be unlocked.
JimSmith94 said:
If you haven't updated it yet and its version is older than last November, you should be able to unlock the bootloader. Once it's been updated to a newer version, it can't be unlocked.
Click to expand...
Click to collapse
I have a BL unlocked, Verizon rooted Pixel XL. Can I put an ATT sim card in it and use it on the ATT network? Would I need to flash a different rom?
STraver said:
I have a BL unlocked, Verizon rooted Pixel XL. Can I put an ATT sim card in it and use it on the ATT network? Would I need to flash a different rom?
Click to expand...
Click to collapse
Should be able to just pop in the ATT sim
JimSmith94 said:
If you haven't updated it yet and its version is older than last November, you should be able to unlock the bootloader. Once it's been updated to a newer version, it can't be unlocked.
Click to expand...
Click to collapse
I guess that'll be the big question. If the phone was only a display model since it was released. I wonder if the display models get the updates pushed automatically... I will find out tomorrow.
Well the phone came with 7.1.2 so no fun for me. Thanks for the info from everyone.
Very interesting, I stuck a T-mobile SIM in it and I can now switch on OEM unlocking. It was greyed out before I put the SIM in.
tuxdreamerx said:
Very interesting, I stuck a T-mobile SIM in it and I can now switch on OEM unlocking. It was greyed out before I put the SIM in.
Click to expand...
Click to collapse
I'm curious, have you tried unlocking the BL now that you can toggle OEM unlocking?
Grubling said:
I'm curious, have you tried unlocking the BL now that you can toggle OEM unlocking?
Click to expand...
Click to collapse
I have not I will this evening or tomorrow though. I was just under the impression that all Verizon Editions had that switch disabled no matter what SIM card went it. As I stated before this was a display model, I got it for next to nothing due to very minor screen burn from the demo mode, I can barely see it so i'm good with what I paid. So I wonder if display models weren't Verizon models? Or maybe this was a third party Verizon store and not corporate. Either way is there anyway to tell which one it is? The SKU on the back is G-2PW2100-021-B and it has build number N2G47E on it, which is not the verizon build I don't think.
tuxdreamerx said:
I have not I will this evening or tomorrow though. I was just under the impression that all Verizon Editions had that switch disabled no matter what SIM card went it. As I stated before this was a display model, I got it for next to nothing due to very minor screen burn from the demo mode, I can barely see it so i'm good with what I paid. So I wonder if display models weren't Verizon models? Or maybe this was a third party Verizon store and not corporate. Either way is there anyway to tell which one it is? The SKU on the back is G-2PW2100-021-B and it has build number N2G47E on it, which is not the verizon build I don't think.
Click to expand...
Click to collapse
Google points to that being a Verizon SKU. But with the build number being non-Verizon, you might be able to unlock it.
There may be some relevant information here: https://forum.xda-developers.com/pixel/help/bootloader-unlock-verizon-pixels-t3616101
tuxdreamerx said:
Very interesting, I stuck a T-mobile SIM in it and I can now switch on OEM unlocking. It was greyed out before I put the SIM in.
Click to expand...
Click to collapse
Count your blessings, most of us with Verizon models are still locked on other carriers.
parakleet said:
Only thing that matters is if the origin of the phone is Verizon or Google.
If the origin is Google you can install the Google factory image and use it on anywhere, unlock the bootloader, root and have a grand old time.
If the origin is Verizon you are relegated to the Verizon image regardless of where you use the phone, no flashing for you.
Compare the build code of your phone to the build codes on google factory image website and you will know what you have.
good luck
Click to expand...
Click to collapse
Hi, I was about to buy Google Pixel XL off the eBay how can I tell if its Verizon phone or Google phone? I asked two sellers, they didn't know if it was Verizon on Google phone, they are just selling as Unlocked GSM , I never bought Google phone so I'm very new to it, per my understanding Verizon phones wont able to have unlock bootloaders? and Google phones will do? also Google phones can work with Verizon and GSM phones without any issues or they are only good with GSM?
you were saying something about build id to check
https://developers.google.com/android/images
I went to this webpage but I dont see any differences in model # for both ver?
zfk110 said:
Hi, I was about to buy Google Pixel XL off the eBay how can I tell if its Verizon phone or Google phone? I asked two sellers, they didn't know if it was Verizon on Google phone, they are just selling as Unlocked GSM , I never bought Google phone so I'm very new to it, per my understanding Verizon phones wont able to have unlock bootloaders? and Google phones will do? also Google phones can work with Verizon and GSM phones without any issues or they are only good with GSM?
you were saying something about build id to check
https://developers.google.com/android/images
I went to this webpage but I dont see any differences in model # for both ver?
Click to expand...
Click to collapse
You can unlock the bootloader on Verizon.
tuxdreamerx said:
So I just bought a Verizon Pixel XL off ebay with the intention of using it on T-Mobile because I was under the impression that taking it to T-Mobile was no issue and would be no different than using a google store one on T-Mobile. Although I am reading some concerning threads about the bootloader issue. If this phone happens to have 7.11 will I be unable to flash the T-Mobile factory image onto it? Or is there really no benefit in doing this anyway? Do I and will I be able to flash at least the T-Mobile radio over to it?
Then if it is before 7.11 and I unlock the bootloader right away can I keep it unlocked even if I play around with images and stuff such as trying out the O beta? or do I have to avoid Factory images once its unlocked and only use custom roms?
Thanks in advanced!
Click to expand...
Click to collapse
I literally just did this 2 months ago. Got a pixel xl and it was a verizon phone but I have Tmobile. The phone can be unlocked, it can be rooted, it can be rommed, yes it can! Mine came with 711 or 712 cant remember but whatever doesnt matter. Just follow the guide in the other thread by @Homeboy76, it's a GREAT read and tutorial. It will put you from stock nougat to stock pie, but afterwards you can go to nougat, oreo, or pie. I know because after I did it, i went to an custom rom, then to a custom oreo rom, back to stock pie, back to custom pie lol. I would put a link up to the thread but idk how to do hyperlinks lmao, i skipped that day of school.
Hi XDA, I have an unlocked pixel XL on verizon network. I cannot connect to LTE or anything other than 2g networks. I have clean installed, changed APNs and tried everything to properly get the LTE back. Help?
kingbri said:
Hi XDA, I have an unlocked pixel XL on verizon network. I cannot connect to LTE or anything other than 2g networks. I have clean installed, changed APNs and tried everything to properly get the LTE back. Help?
Click to expand...
Click to collapse
I mean this is gonna sound dumb but have you looked at the mobile networks setting page and have your preferred network on LTE?
loeffler23 said:
I mean this is gonna sound dumb but have you looked at the mobile networks setting page and have your preferred network on LTE?
Click to expand...
Click to collapse
Yes
Can you change the network operators on 8.1?
Is your unlocked Pixel XL from the USA? It seems it doesn't support the correct bands for your network
All pixels have the same radios. Dial *#*#4636#*#* click on phone info. Change settings if needed
SIM card is toast. I have had this exact thing happen to me. Just go into a VZW store and request a new one. Sim handshake needed for LTE connection only on VZW.
SynisterWolf said:
SIM card is toast. I have had this exact thing happen to me. Just go into a VZW store and request a new one. Sim handshake needed for LTE connection only on VZW.
Click to expand...
Click to collapse
I did get a new sim card, problem still persists
kingbri said:
I did get a new sim card, problem still persists
Click to expand...
Click to collapse
After you got the new sim and installed it did you go back to factory rom and waited a bit for it to connect to the network?
Sent from a Glade[emoji768] PlugIns[emoji768]
SynisterWolf said:
After you got the new sim and installed it did you go back to factory room and waited a bit for it to connect to the network?
Sent from a Glade[emoji768] PlugIns[emoji768]
Click to expand...
Click to collapse
I put the sim in when I reset, no connection, should I try again?
kingbri said:
I put the sim in when I reset, no connection, should I try again?
Click to expand...
Click to collapse
What firmware version are you on? And when you update are you flashing all or just flashing a certain thing?
loeffler23 said:
What firmware version are you on? And when you update are you flashing all or just flashing a certain thing?
Click to expand...
Click to collapse
I'm on the February patch, stock. I'm flashing everything, also, is it normal for your phone number to not be your phone number with a new sim?
My number showing up on about phone is 908-770-6054. This is not my number, could it be human error?
kingbri said:
My number showing up on about phone is 908-770-6054. This is not my number, could it be human error?
Click to expand...
Click to collapse
Contact your carrier or go in and tell them that it is not your number and that you are stuck on 2g they should be able to tell you how to fix it or if you go in they can fix it
I did contact my carrier, they cannot figure out what to do. Replaced the sim about 4 times, still no luck. I go into testing (secret code) and I am on 1x network @loeffler23
Sounds like your efs data could be corrupt and there is no way to fix that. Or your LTE radio is toast. Did someone try to carrier unlock your phone?
DR3W5K1 said:
Sounds like your efs data could be corrupt and there is no way to fix that. Or your LTE radio is toast. Did someone try to carrier unlock your phone?
Click to expand...
Click to collapse
my phone's unlocked by default and there has to be a way to fix efs, not accessible by recovery? (what is efs)
It holds the imei and other radio proprietary info not sure what partition that data is actually in on this device. I think the efs data is no longer in /efs
Twrp used to have a option for efs backup with the data system backup and restore options
Just a real quick question before i return the phone tomorrow.
On the g981u1 (purchased from google through Fi), same as everywhere else, has the sim manager disabled, bootloader not unlockable.
From all the searching i did today, which was horrible, i just wanted to verify in a last ditch effort before sending it back.
The only way i found to enable esim is to modify the features.xml (from sounds of it). However to do so you need root, and of course it appears root requires unlocked bootloader(unless i missed something somewhere)
I have been unable to find a way to unlock bootloader(am i wrong?)
I havent found root (without unlocked bootloader)
Edit- nvm i found what i was looking for
skullzaflare said:
Just a real quick question before i return the phone tomorrow.
On the g981u1 (purchased from google through Fi), same as everywhere else, has the sim manager disabled, bootloader not unlockable.
From all the searching i did today, which was horrible, i just wanted to verify in a last ditch effort before sending it back.
The only way i found to enable esim is to modify the features.xml (from sounds of it). However to do so you need root, and of course it appears root requires unlocked bootloader(unless i missed something somewhere)
I have been unable to find a way to unlock bootloader(am i wrong?)
I havent found root (without unlocked bootloader)
Edit- nvm i found what i was looking for
Click to expand...
Click to collapse
So what is your solution?
Sent from my SM-G985F using Tapatalk
skullzaflare said:
Just a real quick question before i return the phone tomorrow.
On the g981u1 (purchased from google through Fi), same as everywhere else, has the sim manager disabled, bootloader not unlockable.
From all the searching i did today, which was horrible, i just wanted to verify in a last ditch effort before sending it back.
The only way i found to enable esim is to modify the features.xml (from sounds of it). However to do so you need root, and of course it appears root requires unlocked bootloader(unless i missed something somewhere)
I have been unable to find a way to unlock bootloader(am i wrong?)
I havent found root (without unlocked bootloader)
Edit- nvm i found what i was looking for
Click to expand...
Click to collapse
did you manage to unlock Esim. I have same issue. I need to know hot to enable esim
axelrade said:
did you manage to unlock Esim. I have same issue. I need to know hot to enable esim
Click to expand...
Click to collapse
So far, no go on the esim. I did get unlocked etc, but it seems something else is keeping the esim inactive. I almost need a snapdragon with esim working (from another country) to compare to
skullzaflare said:
So far, no go on the esim. I did get unlocked etc, but it seems something else is keeping the esim inactive. I almost need a snapdragon with esim working (from another country) to compare to
Click to expand...
Click to collapse
Snapdragon variants aren't eSIM enabled, only Exynos devices.
I remember seeing the option enabled when you flash the Exynos magisk module on a Snapdragon device. It also gave me call recorder.
ChongoDroid said:
I remember seeing the option enabled when you flash the Exynos magisk module on a Snapdragon device. It also gave me call recorder.
Click to expand...
Click to collapse
CSC change does not appear to work on snapdragon, i already tried it.
HOWEVER, editing Build.prop in vendor did enable sim manager for me, however status is showing esim imei as unknown (yes my box has 2 imei) and the add gets stuck
skullzaflare said:
CSC change does not appear to work on snapdragon, i already tried it.
HOWEVER, editing Build.prop in vendor did enable sim manager for me, however status is showing esim imei as unknown (yes my box has 2 imei) and the add gets stuck
Click to expand...
Click to collapse
Can you specify how you accessed Build.prop and also what you edited to enable sim manager?
axelrade said:
did you manage to unlock Esim. I have same issue. I need to know hot to enable esim
Click to expand...
Click to collapse
dnldcs said:
Can you specify how you accessed Build.prop and also what you edited to enable sim manager?
Click to expand...
Click to collapse
I am rooted/unlocked
In vendor\build.prop i found "persist.radio.multisim.config=ss" which is single sim. dsds would be for dual sim. Phone would not let me modify or replace the build.prop.
With the recommendation from Orphee i installed this package in my magisk
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
From there it let me change that line to dsds, and thus here we are. I am unsure if dsds should be a different line for esim, or if something else is needed to "start" the esim.
Are both modules enabled ? CSC and Props config
And is there 2 IMEI written in phone About screen ? Not only the box.
View attachment 5131175
Orphee said:
Are both modules enabled ? CSC and Props config
And is there 2 IMEI written in phone About screen ? Not only the box.View attachment 5131175
Click to expand...
Click to collapse
Currently the IMEI for esim shows unknown, so it IS possible i broke that during UL/root or something, but i feel more inclined to believe it is just not enabled. On stock rom it only showed the normal IMEI
I have tried both yes
Then you must fix or find how to have the IMEI number shown in the phone menu.
Esim registration will not work until you have the IMEI number shown.
Orphee said:
Then you must fix or find how to have the IMEI number shown in the phone menu.
Esim registration will not work until you have the IMEI number shown.
Click to expand...
Click to collapse
Correct! That is where i am currently stuck lol
Download Google dialer and then enter *#*#467#*#" and there's some esim related toggles available now.
You can enable RCS here too if you know what you're doing.
ChongoDroid said:
Download Google dialer and then enter *#*#467#*#" and there's some esim related toggles available now.
You can enable RCS here too if you know what you're doing.
Click to expand...
Click to collapse
Just tried. It does not work.
insomniacandroid said:
Just tried. It does not work.
Click to expand...
Click to collapse
Dang
ChongoDroid said:
Dang
Click to expand...
Click to collapse
Do you a screenshot?
Inviato dal mio SM-G9860 utilizzando Tapatalk