Database Develop

Unlocking Focus S

Hey guys,
So I need to unlock my Focus S and went to fastgsm.com, and there are two methods, one by USB and one via IMEI. Can anyone tell me what the difference is? I'm in the USA btw. Thanks!

tonynojutsu said:
Hey guys,
So I need to unlock my Focus S and went to fastgsm.com, and there are two methods, one by USB and one via IMEI. Can anyone tell me what the difference is? I'm in the USA btw. Thanks!
Click to expand...
Click to collapse
USB can be quicker and cheaper but more trouble sum to get working if it is possible at all (not all models work)
IMEI can take a while to come through and generally costs more, but is a lot easier to get working.
My phones yet to arrive so I cant say for sure what does and doesn't work, but after spending an hour or so researching unlocking via cable. it doesn't appear to be possible, in that the i937 isn't on any of the supported cable unlock lists..

I unlocked via USB and it worked fine. It's not working in Windows 8 though!
Also, in the event that the USB unlock doesn't work, the network unlock tool is actually displayed within the app, that you can then enter in the phone manually.

64GUNSHIP said:
I unlocked via USB and it worked fine. It's not working in Windows 8 though!
Also, in the event that the USB unlock doesn't work, the network unlock tool is actually displayed within the app, that you can then enter in the phone manually.
Click to expand...
Click to collapse
could you drop some details of where you did it?
still cant find any cable unlock sites that say they support the i937

FastGSM.com worked fine for me.
Sent from my SGH-i937 using XDA Windows Phone 7 App

Just tried to unlock my Focus S (updated via Zune to the latest 8773 version with Samsung drivers) using the USB method from FastGSM and the program failed to unlock my phone. Also tried using the program to unlock after restoring to a 7720 backup but usb unlock still failed - thinking it is the bootloader as its version number didn't revert to an earlier number even after restoration. Currently waiting for support from FastGSM to respond...

armodons said:
Just tried to unlock my Focus S (updated via Zune to the latest 8773 version with Samsung drivers) using the USB method from FastGSM and the program failed to unlock my phone. Also tried using the program to unlock after restoring to a 7720 backup but usb unlock still failed - thinking it is the bootloader as its version number didn't revert to an earlier number even after restoration. Currently waiting for support from FastGSM to respond...
Click to expand...
Click to collapse
Are you using Windows 8 by chance? It didn't work on W8 for me. The program actually displays the unlock code during the process. It's like "network code" or something in the dialog. You can simply enter that into your phone.

64GUNSHIP said:
Are you using Windows 8 by chance? It didn't work on W8 for me. The program actually displays the unlock code during the process. It's like "network code" or something in the dialog. You can simply enter that into your phone.
Click to expand...
Click to collapse
I am using Windows 7 Pro 64-bit. Hm...nothing like that comes up in the dialogue box of the FastGSM program. Here is the log (replace the IMEI and serial with X's):
7/4/2012 1:54:44 PM
1. Please ensure that battery of your phone is fully charged
2. Turn on your phone without simcard.
3. On keypad of your phone type ##634# and click "Call" button to show Diagnosis screen.
4. Type *#7284# onto Diagnosis screen, select "Modem, USB Diag." and confirm selection.
5. After the phone restarts please connect USB cable to your computer and to the phone
6. Wait until all drivers are installed.
7. Click "Next" button.
OPENING COM5 : [OK]
PDA VERSION : I937UCKJ1
CSC VERSION : I937ATTKJ1
PHONE VERSION : I937UCLE2
HARDWARE VERSION : REV1.0
BUILD VERSION : M7630A-AAEQMWZM-1.6.002407
PHONE IMEI : XXXXXX-XX-XXXXXX-X
PHONE SERIAL NUMBER : XXXXXXXXXX
PHONE MODEL : SGH-I937
PHONE PLATFORM : WP7_YUKON
BYPASSING MSL PROTECTION : [FAIL]
Log was created using FastGSM Client 1.0.0.65
Unfortunately no network code seems to be displayed

just to give an update, the fastgsm client is unable to unlock phones that have applied the new LE2 firmware update from samsung. they refunded my cost (rather than unlock it with IMEI for me :crying

if they won't.. try SAMSUNGimeiUnlock.com
i got mine there for my focus s

Can you guys tell me how much are they charging for unlocking Samsung focus s on http://www.samsungimeiunlock.com ?
and we are talking about network unlock right? could somone confirm if the below phone can be unlocked?
http://www.ebay.com/itm/AT-T-SAMSUN...0941959080?pt=Cell_Phones&hash=item4ab9a1a7a8

lsguntu said:
Can you guys tell me how much are they charging for unlocking Samsung focus s on http://www.samsungimeiunlock.com ?
and we are talking about network unlock right? could somone confirm if the below phone can be unlocked?
http://www.ebay.com/itm/AT-T-SAMSUN...0941959080?pt=Cell_Phones&hash=item4ab9a1a7a8
Click to expand...
Click to collapse
yeah it can be SIM unlocked via IMEI and if you don't update it (apparently) via USB cable as well.

One more question . Any other specific advantage on buying a unlocked device apart from price?

lsguntu said:
One more question . Any other specific advantage on buying a unlocked device apart from price?
Click to expand...
Click to collapse
Even being unlocked the chances are with the Focus S it will still be branded so the only difference buying unlocked against locked, is that its usually more expensive to buy an unlocked device, however unless you fail do to your research you will find that the price is usually about the same anyway, sometimes marginally more expensive, I suppose you could call it the "hassle tax"

My Experience with UNLOCKing Samsung Focus S i937
...this is is the worst to unlock. I went through 3 ebay sellers (range .99 to $25). No one could find a unlock code (but refunded my money...after complaining). I went to local 3rd party mobile phone shop...they couldn't find a unlock code.
I then went to FastGSM and selected USB unlock...since IMEI way hasn't worked. I paid, downloaded client...client connected..but didn't do anything.. I left it there for 30 mins. Contacted FastGSM, they referred me to online tutorial..which i followed to the "T". Still didn't work. So I deiced to hard reset my phone...still didn't work...i decided to update it to the latest version through Zune( DON'T DO THIS! without making a Backup first!! http://forum.xda-developers.com/showthread.php?t=13795711).. Then I found this thread...member "64GUNSHIP" stated that usb client doesn't work with Windows 8 ( which is what I was using). So I used another computer with Windows 7. The usb client works!!! I got unlock code...but somehow the "SIM Unlock Screen" didn't show up any more with or without a SIM card. [Unaware to me, the client somehow unlocked my phone without me entering the code]
So the entire time I was trying to figure out did the Zune update kill the Sim unlock menu, I tried the #7465625*638*CODE#. I even restored to a previous ROM Backup. The issue is that I was using an OLD OLD OLD Sim card from a different carrier that the phone didn't recognize. Once I put in a working Tmobile SIM ...everything worked great!

Developing the Focus S

Hi guys,
This is all about developing the Focus S, since we are on our own on this one I thought id start the ball moving but it would be great if others can help, my first target is to try and download as much of the device as possible
Can I promise anything at all? nope
Have I achieved anything yet? well id say 1 step above doing nothing at all, if you can call that progress then yes, there is progress
Is it even possible to do anything? i dunno
Could i brick my device? possibly, i honestly don't know
in short, this is me blindly wondering in the dark with absolutely no direction what so ever!
So what have i done, well, i managed to get the Focus S talking to Qualcomms diagnostic utility, QPST and RevSkills CDMA Workshop
I cant get QXDM to install on Win 8 x64 and im not sure we need that one anyway
it is possible to edit stuff on the phone at a very low level, NOT OS level, it should be possible to download the various images on the phone, but ive yet to have any luck with that, it keeps coming up with "Arm9 fatal error"
ive been able to download and backup various phone settings but this is still outside of the OS#
I can play about with the EFS but there are several folders that i cant get in to yet
So far,both the samsung download mode and the ARM9 (?) download mode IS visible and installes as a com port, but there is no response on that port, i can only get a response within windows when i enable USB diag mode....
i decided not to link to the various tools ive mentioned here, i dont know the legalities of it all so use google, they are all easy to find.
Samsung studio 3 drivers
http://downloadcenter.samsung.com/c...813082717640_Samsung_USB_Driver_Installer.exe
Install it with compability for windows vista.
Samsung Focus info (note that most of this doesn't work, its for the older focus but some does)
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Focus
Handy Diagnostic codes
*#7284# - USB Path control (select to change how your phone communicates with your computer)
*#197328640# - The Root Menu (seriously, don't get too cocky, you could bugger up your device)
Samsung USB Download mode
Turn off Device
hold the camera button and the Volume UP
Whilst holding those two push and hold the power button until it vibrates
Samsung Device Hard reset
Turn off Device
hold the camera button and the Volume Down
Whilst holding those two push and hold the power button until it vibrates
Follow on screen instructions
Enable Diagnostic mode and Connect to QPST or other GSM/CDMA software
Download and install the Samsung drivers above
open the diagnostic app and dial code *#7284#
Select Modem,USB Diag
Reboot
When you plug the phone in you should see a COM port install and appear in device manager
load QPST configuration
Click on the Ports Tab then Click add new port
Select your Phone com port
Click OK then select the phone from the list, hit enable
Click on start clients then you can play with a bunch of options
Please note that this is a serious piece of kit, its designed for low level editing, what I mean by that is that it couldn't care less about if it works or not after you finish playing, a couple of other software options to play with are CDMA tools and RevTools both have the potential to paperweight your phone!
NOTE: Zune will not connect and whilst connected to PC you may lose all GSM connectivity whilst connected as well.
Enable FTM (Factory Test Mode)
open Diagnostic app and dial code*#197328640#
select 6 (common)
Select 1 (FTM)
Select 1 (on)
Click return save (it doesn't always persist unless you do)
Hit Back until you back to the main menu then win key to Windows
REBOOT to enable
NOTE: You will lose ability to connect to GSM with this enabled, a reboot is required to enable it after its set and to deactivate it, ive not found a noticeable difference with this on

If im not wrong, WP uses arm v7.

Good luck with this, it would be nice to see a 7.8 ROM on this device before I go buy the ATIV.

tayfelix said:
If im not wrong, WP uses arm v7.
Click to expand...
Click to collapse
yes your right, but that's what it says, it reboots in to some sort of QC download mode, QPST is the waiting for it to talk to it which it doesn't do, it just sits there with this error message.
I have been able to backup the Important bits that make the phone work, and I have access to the EFS, I can change all sorts at a very low level but any time I try and download some of the various "partitions" it reboots to this special download mode. because we don't have any form of ROM I thought the first priority should be to see if we can make a backup of it, outside of MS encrypted zune backup I mean
the software is old so perhaps it doenst work with newer hardware, but then it does with android soooo.....

LudoGris said:
Good luck with this, it would be nice to see a 7.8 ROM on this device before I go buy the ATIV.
Click to expand...
Click to collapse
don't hold your breath, I still don't really know what im doing, consider this playing.....in a mine field

Hmmm. If this does work. Will it ever work on focus flash/ omnia w? Cuz it got the same spec except different screen sizes

tayfelix said:
Hmmm. If this does work. Will it ever work on focus flash/ omnia w? Cuz it got the same spec except different screen sizes
Click to expand...
Click to collapse
That depends what you mean by work, will the focus flash connect to various diagnostic tools? yes probably, will it be possible to download the ROM? maybe, beyond that I haven't got a clue
starting to run out of ideas, I think either the download mode via QPST is disabled or, and more likely, the driver isn't correct, when it enters the arm9 fatal error screen it is still using same driver, the same driver samsungs download mode uses, but both won't talk to QPST unless I enable diagnostic mode within windows phone OS, the prob with that is that it won't then allow access to the file systemSent from my fake Lumia 900 using XDA Windows Phone 7 App

It also have diagnostic tools .

tayfelix said:
It also have diagnostic tools .
Click to expand...
Click to collapse
be careful, you can bugger up your device!​i will write a more detailed guide later
First things first, you will need to make sure you have the samsung diagnostic tool install
bring up the phone dialer and dial
##634#​
you will now see a diagnostic app on your app list, run it and type in
*#7284#​that will enable you to change the USB connection mode,select
Modem USB diag​
OPTIONAL - Typing in the following code will bring up the diagnostic root menu
#197328640#​you can find a full list Here Many of the codes on that list just run functions found in the root menu
Bare in mind that pissing around with some of the things in there will bring about a swift crappy end to your day!
plugging in your your phone at this point will install a Samsung COM driver
next download and install QPST on your computer, run the config part of that, it will ask you to select your phone, you will need to add a com port, it should then list your phone to connect to it
you can then edit the EFS, service/phone settings, download settings
you will need to know your SPC number, mine was already 0000000, there are ways of working out your number if leaving it all at zeros doesnt work.
use the service editor to read the phone settings, it will ask for your SPC, once loaded,you can save those settings to a file, very important ifyou screw something up

Cool, I will try it when I'm free. Hmm what's UR focus s BOOTLOADER, firmware version and diagnostic version ?

tayfelix said:
Cool, I will try it when I'm free. Hmm what's UR focus s BOOTLOADER, firmware version and diagnostic version ?
Click to expand...
Click to collapse
as reported in windows phone about screen, note that the Focus S and Omnia 7, has a firmware update that will stop any interop unlocking, i had it installed but it killed my battery life and my phone reception so i took it off, id suspect the bootldt vs will be different between devices, even though they were released at the same time
bootldr 6.5.16.0
firmware 2103.11.10.1 (not the Samsung update that breaks interop)
diagnostic 0923 (not the Samsung update that breaks interop)

Er it's focus, focus s , focus flash/omnia w and omnia 7 that are affected by the freakin update. This is my version from the about info
Firmware: 2424.12.04.1
Bootloader: 6.4.4.0
Diagnostic : 1109
Note : I cant interlop unlock my omnia as Samsung fixed the exploit in the new firmware version
How did u remove the firmware ?

tayfelix said:
Er it's focus, focus s , focus flash/omnia w and omnia 7 that are affected by the freakin update. This is my version from the about info
Firmware: 2424.12.04.1
Bootloader: 6.4.4.0
Diagnostic : 1109
Note : I cant interlop unlock my omnia as Samsung fixed the exploit in the new firmware version
How did u remove the firmware ?
Click to expand...
Click to collapse
I made a backup before I installed it
I think we can get an xap of my version of the diagnostic tools, but the firmware update also changes drivers an a few other things, those cant be changed, if we could send custom cabs to the device we are laughing, but we cant, to cab send requires the cab to be signed, and the device would need to have that certificate, which cant be put on whilst its all in use

:S don't think so as diagnostic tool is based on firmware I think.

tayfelix said:
:S don't think so as diagnostic tool is based on firmware I think.
Click to expand...
Click to collapse
try this, remove your existing diagnostic app and install this xap

How can u install a xap..

Is your device still unlocked? The Samsung update will stop you applying the unlock but if you had it already installed it will still work, if it is unlocked then use an cap deployed, my link to the wee guide details how to do it, if it's interop unlocked but you can't install an xap deplorer the use the xap deplorer included with the WP SDK
Sent from my Lumia 900 using XDA Windows Phone 7 App

it's ok. I will just wait for someone to be able to unlock the device as I already got the exploit for interlop unlock patched

tayfelix said:
it's ok. I will just wait for someone to be able to unlock the device as I already got the exploit for interlop unlock patched
Click to expand...
Click to collapse
well there isn't anyone working on unlocking it as far as I know, so if its going to happen then we need to do it ourselves.
Ive exhausted just about every avenue I can think of getting access to the device, ive been able to dump parts of the RAM but still not the ROM,
EFS is writable but I cant get in to the secure folders. The only way I can think of for getting the ROM is to get it working in one of the two download modes, both will not talk to anything tho, perhaps if I had the commands to copy the ROM I could just send them in the hope it will reply but it sure as hell isn't saying anything to the commands I have sent.

Hmmm. Must there be a exploit? Zzz there's are very little/no hackers having a focus s or a focus flash/omnia w. they all have 1st gen devices I think.

Nokia 5&6&8 PROTOTYPE Comparison

Let's talk about the Nokia Android Phone prototypes.
Right now, I have Nokia 5&6&8 prototype phones. All of them has unlocked bootloaders, and that means I could install a third-party recovery on them.
However:
1. Right now, I could only install TWRP on Nokia 6 prototype - Of course, I backed up the original recovery, and I also rooted it and installed Xposed Framework on it.
2. When I got the Nokia 5 prototype, it got FRP Locked, and I managed to get rid of it. I could test the third-party recovery on it with "fastboot boot" command.
3. When I got the Nokia 8 prototype, it got boot loop, flash latest OFW doesn't help at all. I still have no idea of how to fix it. I didn't find any recovery in it's OFW.
In Nokia 5/6 prototype, the model is totally different from a retail phone. For Nokia 5 prototype, the manufacturer and model are "Heart". For Nokia 6, the manufacturer and model are "Unknown". However, there's no "Heart" or "Unknown" string in their respective build.prop. I wonder if Heart is Nokia 5's codename?
The design of Nokia 6 prototype is slightly different from retail phone as you can see. I can understand they used "BRAND" logo on the screen instead of "NOKIA", but the camera design is different.
Since I still can't bring the Nokia 8 back to life, I have no idea of its specification.
Here's the photos of them. I'm sorry for the "annoying" watermarks on them, but I need to avoid others to steal these photos for their own purposes.

hikari_calyx said:
Let's talk about the Nokia Android Phone prototypes.
Right now, I have Nokia 5&6&8 prototype phones. All of them has unlocked bootloaders, and that means I could install a third-party recovery on them.
However:
1. Right now, I could only install TWRP on Nokia 6 prototype - Of course, I backed up the original recovery, and I also rooted it and installed Xposed Framework on it.
2. When I got the Nokia 5 prototype, it got FRP Locked, and I managed to get rid of it. I could test the third-party recovery on it with "fastboot boot" command.
3. When I got the Nokia 8 prototype, it got boot loop, flash latest OFW doesn't help at all. I still have no idea of how to fix it. I didn't find any recovery in it's OFW.
In Nokia 5/6 prototype, the model is totally different from a retail phone. For Nokia 5 prototype, the manufacturer and model are "Heart". For Nokia 6, the manufacturer and model are "Unknown". However, there's no "Heart" or "Unknown" string in their respective build.prop. I wonder if Heart is Nokia 5's codename?
The design of Nokia 6 prototype is slightly different from retail phone as you can see. I can understand they used "BRAND" logo on the screen instead of "NOKIA", but the camera design is different.
Since I still can't bring the Nokia 8 back to life, I have no idea of its specification.
Here's the photos of them. I'm sorry for the "annoying" watermarks on them, but I need to avoid others to steal these photos for their own purposes.
Click to expand...
Click to collapse
Hi what twrp flashed on Nokia 6 and 5?
Please post twrp here...tank you

To answer your questions
1. "Heart" is Nokia 6 ROM here (start with PLE https://mega.nz/#F!1ENgnThL!FyL9uYCC3Dq-16elThKAPg ). I used to install it on my Nokia 5 to have root access 'cause I can't seem to find the Nokia 5 TWRP
2. Phone's name and parameters are stored in cda partition. Editing build.prop won't matter in Settings
3. From my point of view, your 6 got the retail's camera design
4. Plug your 8 into the computer to see if it can get to EDL as its ROM is available now
5. On your Nokia 6, try patching the boot.img with Magisk Manager and install instead of the SuperSU root as SuperSU and Google services ain't getting along
...

@hikari_calyx do you have the modified SuperSU zip in the recovery?

wolfyapl said:
@hikari_calyx do you have the modified SuperSU zip in the recovery?
Click to expand...
Click to collapse
Sure.
I've uploaded it in the Nokia 6 Root Guide, file name is verify-xinkid.zip .
https://forum.xda-developers.com/no...de-how-to-flash-custom-recovery-root-t3702354
wolfyapl said:
To answer your questions
1. "Heart" is Nokia 6 ROM here (start with PLE https://mega.nz/#F!1ENgnThL!FyL9uYCC3Dq-16elThKAPg ). I used to install it on my Nokia 5 to have root access 'cause I can't seem to find the Nokia 5 TWRP
2. Phone's name and parameters are stored in cda partition. Editing build.prop won't matter in Settings
3. From my point of view, your 6 got the retail's camera design
4. Plug your 8 into the computer to see if it can get to EDL as its ROM is available now
5. On your Nokia 6, try patching the boot.img with Magisk Manager and install instead of the SuperSU root as SuperSU and Google services ain't getting along
...
Click to expand...
Click to collapse
A4: Yes, Nokia 8 prototype can enter EDL by connect to PC while holding both volume keys. But Nokia 8 retail can only enter EDL by fastboot command with service purposed bootloader loaded.
A5: I've replaced a Nokia 6 Retail Phone TA-1000 with November Security Update, which SuperSU works pretty well with Google Services.

Removing Carrier Lock?

The Alcatel 5033T (Telstra) I have is Telstra-locked to the point that most online unlock-code providers can't get a code to free it up. The only places which say they can do it require you to bring it in (they're in other states) or they want you to install Teamviewer (!) and they'll do it remotely.
I'm sure this is a FAQ on other phone models, but I see nothing for the Alcatel 1 here yet. What are the chances someone with past experience on ADB can figure out how to get this working with a non-Telstra SIM?

Did you manage to sort this

How to mount sd card

saw someone posted this, any Guru can verify the steps? or make it clearer?
**********************************************************************************
On the 5033T fastboot will flash only the system.img not the boot or recovery
image,so Magisk or TWRP cannot be flashed via fastboot. Also to flash via SPflashtool for the MT6739 you now need a custom DA and Auth file for that phone.
The downloaded edited 5033D system image will give you root access but install
RootCheckerBasic app to check as sometimes the root access disappears.
The phone modem is in the vendor.img partition and so should be unaltered as you
have flashed the system.img partition only.Your bands should be unaltered. Install the MTK Engineering Mode apk and use the bandmode function to see the bands. (Phone Developer option must be on(Tap build number untill developer options appear)).
Now that you have root access you can now network unlock the phone. Using ES File Explorer or Root Explorer. In the phone /vendor/protect_f/md you will see a file ST33_004. This file determines whether the phone is network locked.
If you get this file from an unlocked phone and put it in place of the one
in the locked phone the phone will be then unlocked and vice versa.
Download the 5033A firmware from the Needrom site. From the download get the protect1.img (in another files). Download to your PC the Ext4Unpacker tool.
Use the tool to extract the ST33_004 file from the 5033A protect1.img .
This is the unlocked ST33_004.
Using ES or Root Exp rename the existing ST33_004 in the phone as ST33_004bac
and copy the new ST33_004 file into the directory. The phone will now accept
non Telstra/Boost SIMs .
Also download the Mobile Upgrade S Gotu2 v5.3.5 tool to your PC. This is the TCL(i.e.=Alcatel) official firmware upgrade tool. It replaces the firmware in
your phone with the latest version on their server for your phone. For a stock
phone it will upgrade to their latest stock version.
For the 5033T+5033D 'hybrid' ,when started the tool appears to be downloading
the 5033T firmware from the server, so it seems that the tool could be used
to return the phone to stock, but this not tried or tested yet.
bmscott said:
The Alcatel 5033T (Telstra) I have is Telstra-locked to the point that most online unlock-code providers can't get a code to free it up. The only places which say they can do it require you to bring it in (they're in other states) or they want you to install Teamviewer (!) and they'll do it remotely.
I'm sure this is a FAQ on other phone models, but I see nothing for the Alcatel 1 here yet. What are the chances someone with past experience on ADB can figure out how to get this working with a non-Telstra SIM?
Click to expand...
Click to collapse

saw someone posted this, any Guru can verify the steps? or make it clearer?
Click to expand...
Click to collapse
Where'd you find this? I'm willing to try 'cos it'll let me get my son off Telstra's overpriced plan and onto something affordable like Jeenee (which the rest of us are on). I've had this Telstra SIM for years so I was hoping they'd unlock the phone for me - after all, it was sent as a replacement for an older phone that'll be out of service when they retire some of the towers in our area - but when I call in to have them do that, they say they'll have to call me back and (of course) never do...

Found the post from ozbargain forum with this 5033D link
https://yadi.sk/d/_-dnrtKS499rww
The 5033A you need to get it from needrom

Any luck someone? I am unable to root it using kingroot

Yes

The Ozbargain thread now has a lot more info than it did a few months ago - I'm still working through it myself, but here's the link: https://www.ozbargain.com.au/node/446160

Unlock ANY Pixel from Carrier

____________________________________________________
UPDATE AS OF 16 OF MAY 2023:
The security patch of December of 2022 fixed the patch, so it doesn't work on this version and newer ones.
The project is still alive and I am working to get the exploit to work on newer version, but for now haven't found any.
However due to the complex nature of the project and that I have little free time, expect this to take sometime until a new exploit is available.
If anyone has any ideas or suggestions please let me know! Any help is welcome
____________________________________________________
Hey everybody!
So recently I bought a Google Pixel 4 XL. The thing is that in Europe they are too expensive compared to the US, so I bought one that was from AT&T(used of course). However is that I need to use my SIM on the phone, but of course, the phone refused to allow me to use my SIM from Spain. ⛔️
So after hours of research, I found a way to unlock it. Here are the steps:
1. Remove your SIM card if it is on the phone
2. Do a factory reset
3. Do OFFLINE SETUP. Also, DON'T PUT ANY PASSWORD OR ANY TYPE OF SCREEN LOCK
4. Once you are on the main screen, enable USB Debugging.
5. Connect the phone to the computer (I assume you already have the USB drivers, platform-tools downloaded and knowledge on how to use ADB commands. If you don't have the SDK downloaded, head to this link and follow the instructions)
6. Inside the platform-tools folder, open a terminal window and run "adb shell"(on mac, once you are on the directory you have to run "./adb shell") and then "pm uninstall -k --user 0 com.google.android.apps.work.oobconfig" (run them without quotes)
After this, you can already connect the phone to the internet and put your SIM in.
This didn't unlock the phone though . What we have just done is this:
When we connect the phone to the internet, it verifies if it should lock the SIM or not. So we did a setup without internet, so the phone can't do that. After that, we uninstall the package responsible for doing this.
So when we connect it to the internet, it won't check the SIM lock
However, the bootloader is still locked and grey out. This is because this app is responsible to grey or not the bootloader switch. If it is from a carrier, the package will disable the switch, and if not you will have the ability to unlock it. As we kill the app before it could do its job, the bootloader will be waiting until the package gives its answer.
Special thanks to this Jorge Cortés to make this post possible.
If you find the post useful, consider buying me a cup of coffee please with Revolut.

If anyone has problems/doubts please let me know!

Esim is unlocked as well?

Didn't try but should work, as the phone never check if it is from a carrier or not.

#mcl said:
Didn't try but should work, as the phone never check if it is from a carrier or not.
Click to expand...
Click to collapse
On another post someaone said esim is working on pixel 4 verizon unlocked trought this steps. So as you say, it works.
Thanks

Danny17va said:
On another post someaone said esim is working on pixel 4 verizon unlocked trought this steps. So as you say, it works.
Thanks
Click to expand...
Click to collapse
No problem. Just for curiosity, who did the test on unlocked Verizon Pixel?

Is there any work around to unlock to bootloader too??

Daniyal48 said:
Is there any work around to unlock to bootloader too??
Click to expand...
Click to collapse
Hey,
I am working on that. As it turns out there is a way to flash firmware to any device with a Qualcomm chip, even if the bootloader os locked. It's called EDL mode. This mode was designed to force flash firmware in bricked devices that can't use fastboot or adb.
I already find the app I need to flash, actually there a a lot of different ones( I chose QPST) but it needs some strange files that I didn't find yet, and it won't allow em to use the google firmware neither .
So when I find those files I will write a detailed guide on how to unlock the bootloader , but for now I only know how to use any SIM on a locked Pixel device.

#mcl said:
Hey,
I am working on that. As it turns out there is a way to flash firmware to any device with a Qualcomm chip, even if the bootloader os locked. It's called EDL mode. This mode was designed to force flash firmware in bricked devices that can't use fastboot or adb.
I already find the app I need to flash, actually there a a lot of different ones( I chose QPST) but it needs some strange files that I didn't find yet, and it won't allow em to use the google firmware neither .
So when I find those files I will write a detailed guide on how to unlock the bootloader , but for now I only know how to use any SIM on a locked Pixel device.
Click to expand...
Click to collapse
I have tried the same on a OnePlus device but they have MSM Tool to thet let you work in edl mode but I haven't found any tool for Pixel devices yet

Daniyal48 said:
I have tried the same on a OnePlus device but they have MSM Tool to thet let you work in edl mode but I haven't found any tool for Pixel devices yet
Click to expand...
Click to collapse
yeah unlike Oneplus Google didn't release any software designed specifically to the Pixel lineup, so you have to use the generic Qualcomm tools.

#mcl said:
yeah unlike Oneplus Google didn't release any software designed specifically to the Pixel lineup, so you have to use the generic Qualcomm tools.
Click to expand...
Click to collapse
Can you name other generic Qualcomm tools so I can experiment with them??

Yeah of course, there is QFIL also and some others that aren't official. I downloaded them from Androidmtk website.
With this link you go to the qpst download and use instructions section of their webpage. At the bottom you will find similar programs, but I didn't get to try them. You can try them, but make sure they are for Qualcomm Chipset, because some of them are for mediatek phones.

#mcl said:
Yeah of course, there is QFIL also and some others that aren't official. I downloaded them from Androidmtk website.
With this link you go to the qpst download and use instructions section of their webpage. At the bottom you will find similar programs, but I didn't get to try them. You can try them, but make sure they are for Qualcomm Chipset, because some of them are for mediatek phones.
Click to expand...
Click to collapse
Okay thank you I hope i find a solution with this

Daniyal48 said:
Okay thank you I hope i find a solution with this
Click to expand...
Click to collapse
No problem, good luck researching .
I will keep searching as well to see if I can find those files

#mcl said:
No problem, good luck researching .
I will keep searching as well to see if I can find those files
Click to expand...
Click to collapse
If you find any files please also send them to me. Can we use a working Device to get these files from. Like we extract these files for a normal pixel 4 xl and then flash it to ours?

Daniyal48 said:
If you find any files please also send them to me. Can we use a working Device to get these files from. Like we extract these files for a normal pixel 4 xl and then flash it to ours?
Click to expand...
Click to collapse
Of course, if I find them I will make them available for anyone .
Yes in theory you can extract this files from your phon, however as mine is locked I need them from an unlocked pixel I suppose, but I didn't try to extract the files from my home and the flash them again, it could work. In the QPST you even have a section to that, it's a backup I Believe but not sure about the name.
If you try and it works let me know!

#mcl said:
Of course, if I find them I will make them available for anyone .
Yes in theory you can extract this files from your phon, however as mine is locked I need them from an unlocked pixel I suppose, but I didn't try to extract the files from my home and the flash them again, it could work. In the QPST you even have a section to that, it's a backup I Believe but not sure about the name.
If you try and it works let me know!
Click to expand...
Click to collapse
Yes I am also looking for an unlock Pixel 4 XL if I find one I will try extracting these files and post it somewhere on the internet so anyone can access it

Yeah that is a way, but I was thinking that maybe these files are inside of the IMG files of the firmware from Google, and that firmware isn't lock , so if anyone manage to find those files there you wouldn't need to buy another pixel to extract the firmware.
I also think that in reality you don't need the firmware but rather some files for your Qualcomm Chipset to get the Sahara protocol working and I believe later on you flash the firmware, however I am not sure about that as I didn't try it.
I think this because you can find some Qualcomm snapdragon 855 programmer files (which had the extension we need), so they may be basic files that activates the Sahara protocol (which is the one used when the phone is in this mode) and only after I believe you can flash the firmware using some commands.
I would like to try out this but I can't as it could brick my phone and I don't have other to use, and I don't have any other pixel, this is my first and only Pixel ever.
So if you have an older pixel and you want you could try this theory...

#mcl said:
Yeah that is a way, but I was thinking that maybe these files are inside of the IMG files of the firmware from Google, and that firmware isn't lock , so if anyone manage to find those files there you wouldn't need to buy another pixel to extract the firmware.
I also think that in reality you don't need the firmware but rather some files for your Qualcomm Chipset to get the Sahara protocol working and I believe later on you flash the firmware, however I am not sure about that as I didn't try it.
I think this because you can find some Qualcomm snapdragon 855 programmer files (which had the extension we need), so they may be basic files that activates the Sahara protocol (which is the one used when the phone is in this mode) and only after I believe you can flash the firmware using some commands.
I would like to try out this but I can't as it could brick my phone and I don't have other to use, and I don't have any other pixel, this is my first and only Pixel ever.
So if you have an older pixel and you want you could try this theory...
Click to expand...
Click to collapse
I have Pixel 2 XL but it doesn't boot into EDL i tried fastboot commands and also abd commands but it doesn't even go there...I have Pixel 3 XL on the way I will try on that but that is already unlocked

#mcl said:
Yeah that is a way, but I was thinking that maybe these files are inside of the IMG files of the firmware from Google, and that firmware isn't lock , so if anyone manage to find those files there you wouldn't need to buy another pixel to extract the firmware.
I also think that in reality you don't need the firmware but rather some files for your Qualcomm Chipset to get the Sahara protocol working and I believe later on you flash the firmware, however I am not sure about that as I didn't try it.
I think this because you can find some Qualcomm snapdragon 855 programmer files (which had the extension we need), so they may be basic files that activates the Sahara protocol (which is the one used when the phone is in this mode) and only after I believe you can flash the firmware using some commands.
I would like to try out this but I can't as it could brick my phone and I don't have other to use, and I don't have any other pixel, this is my first and only Pixel ever.
So if you have an older pixel and you want you could try this theory...
Click to expand...
Click to collapse
Mbn Files from Pixel 4 Request
As title states, I am looking for the mbn files from the pixel 4. I downloaded the modem partition and could not seem to extract it and thought someone that owns a pixel 4 might have better luck than me. Thanks! The directory might be...
forum.xda-developers.com
Are these files related to our issue