hi
can anyone tell me if my device is locked or not?
anyway I can't unlock
matteo 06 said:
hi
can anyone tell me if my device is locked or not?
anyway I can't unlock
Click to expand...
Click to collapse
Very interesting. Your device is in the Engineering state (where the secure boot fuses are not blown). This is more unlocked than normal unlocked. You can run unsigned bootloaders and TrustZone images, access more logs and features from the bootloader itself, and do some other cool things. One suggestion: NEVER run fastboot oem lock on this device. After locking, you can never go back into engineering state.
May I ask where you got this device? Was it unlocked before and did it turn into this somehow? Or did you buy it like this? Engineering devices are normally not sold to the public.
I gotta know this!
squid2 said:
Very interesting. Your device is in the Engineering state (where the secure boot fuses are not blown). This is more unlocked than normal unlocked. You can run unsigned bootloaders and TrustZone images, access more logs and features from the bootloader itself, and do some other cool things. One suggestion: NEVER run fastboot oem lock on this device. After locking, you can never go back into engineering state.
May I ask where you got this device? Was it unlocked before and did it turn into this somehow? Or did you buy it like this? Engineering devices are normally not sold to the public.
Click to expand...
Click to collapse
I had sent it motorola for repair he changed motherboard, yes it was unlocked, now I can't root 100%,only read-only not read-write,for exemple I can't install apk adway
Ps:sorry of it translator Reverso
matteo 06 said:
I had sent it motorola for repair he changed motherboard, yes it was unlocked, now I can't root 100%,only read-only not read-write,for exemple I can't install apk adway
Ps:sorry of it translator Reverso
Click to expand...
Click to collapse
Sell it to the highest bidder then buy a new one for $9.99 on BlackFriday @ Bestbuy
matteo 06 said:
I had sent it motorola for repair he changed motherboard, yes it was unlocked, now I can't root 100%,only read-only not read-write,for exemple I can't install apk adway
Ps:sorry of it translator Reverso
Click to expand...
Click to collapse
Engineering devices have write protect turned on by default, but it can be disabled by creating a particular utag by issuing a particular command over fastboot. Unfortunately, I've forgotten the exact command though.
You have a very special device on your hands The extra debugging features available on engineering hardware make kernel development significantly easier.
squid2 said:
Engineering devices have write protect turned on by default, but it can be disabled by creating a particular utag by issuing a particular command over fastboot. Unfortunately, I've forgotten the exact command though.
You have a very special device on your hands The extra debugging features available on engineering hardware make kernel development significantly easier.
Click to expand...
Click to collapse
I am not able to do debugging,so I prefer a device normal, if somebody helps me to deactivate engineer mode It would be better
matteo 06 said:
I am not able to do debugging,so I prefer a device normal, if somebody helps me to deactivate engineer mode It would be better
Click to expand...
Click to collapse
Sell it to Squid2 maybe ?
Squid make him an offer he can't refuse
You got one guy who needs it and the other who just wants a rooted phone..
if i was you Squid i would PM him and offer to buy him a fancy new top of the line Moto X or something LOL
Well... What happened with your special device?
Hey guys,
So thanks to this thread : https://forum.xda-developers.com/pixel-2-xl/how-to/guide-qxdm-port-activation-pixel-2-xl-t3884967
I got my com ports open (see attached photo)
I cant however get past the part about pdc , as pdc gives me "QMI connection not ready, please use USB driver version 1.00.32 or later and fix the connection before using PDC tool."
I'm not sure how to go about fixing this but if we can, then there is the possibility that we could enable voLTE/voWIFI on the pixel 3 with carriers who don't support it(such as bouygues, who supports voLTE but not anything else)
I'm wondering if it is the qpst version I am using or something else?
I am on windows 7 and also had to disable driver signature enforcement.
Hello!
Did you achieve progress in this issue after the publication of the message?
Any success?? I have this damn same issue on my Redmi 4x...
Has anyone figured out the correct drivers yet?
Ingenium13 said:
Has anyone figured out the correct drivers yet?
Click to expand...
Click to collapse
Check this method! Hope this helps.
crok.bic said:
Check this method! Hope this helps.
Click to expand...
Click to collapse
He already mentioned in his last line that he is using windows 7 and also disabled driver signature enforcement.
can you tell me steps for enable QPST on pixel 3
Xdevillived666 said:
Hey guys,
So thanks to this thread : https://forum.xda-developers.com/pixel-2-xl/how-to/guide-qxdm-port-activation-pixel-2-xl-t3884967
I got my com ports open (see attached photo)
I cant however get past the part about pdc , as pdc gives me "QMI connection not ready, please use USB driver version 1.00.32 or later and fix the connection before using PDC tool."
I'm not sure how to go about fixing this but if we can, then there is the possibility that we could enable voLTE/voWIFI on the pixel 3 with carriers who don't support it(such as bouygues, who supports voLTE but not anything else)
I'm wondering if it is the qpst version I am using or something else?
I am on windows 7 and also had to disable driver signature enforcement.
Click to expand...
Click to collapse
can you tell me steps for enable QPST on pixel i am unable to open port on my pixel
Gautamgzb2 said:
can you tell me steps for enable QPST on pixel i am unable to open port on my pixel
Click to expand...
Click to collapse
Hey. I honestly dont remember now. Its been a long time and it was a lot of trial and error by reading that thread I linked. In the end it was useless because A-google no longer provides images for debugging purposes and B-PDC tool doesnt recognize pixel 3 even after opening the ports. Sorry man.
i hve enabled diag port fully edited values in qxdm took ota updates but upon re locking bootloader pixel 3 resets every change i made what the hell how can factory reset revert nvram changes.
"QPST" stands for "Qualcomm Product Support Tool". It's a proprietary tool used to directly write a binary image to the NAND devices on the device. Neither QPST nor the binary images are freely available, and are generally only used during the factory process to flash the initial firmware to the device.
V0latyle said:
"QPST" stands for "Qualcomm Product Support Tool". It's a proprietary tool used to directly write a binary image to the NAND devices on the device. Neither QPST nor the binary images are freely available, and are generally only used during the factory process to flash the initial firmware to the device.
Click to expand...
Click to collapse
Hmmm, no, not true. Qpst / qfil is freely available, We've used it many times with various LG devices especially.
The binary images are freely available for many devices, here's a list of the binary images free to download for the pixel 3 (from google):
In addition, for LG devices, anyone can freely download the kdz image, which is the entire rom, and use the kdz extraction tool to retrieve any individual partition image.
Not all carriers, like at&t / sprint, don't make their kdz available, thus no access to those images, but most do.
AsItLies said:
Hmmm, no, not true. Qpst / qfil is freely available, We've used it many times with various LG devices especially.
The binary images are freely available for many devices, here's a list of the binary images free to download for the pixel 3 (from google):
In addition, for LG devices, anyone can freely download the kdz image, which is the entire rom, and use the kdz extraction tool to retrieve any individual partition image.
Not all carriers, like at&t / sprint, don't make their kdz available, thus no access to those images, but most do.
Click to expand...
Click to collapse
So QPST can be used to flash bootloader, at which point someone should be able to use adb to flash the factory images? Wouldn't someone need to know the starting/ending addresses when writing to block devices?
Is there a reputable source from which to download QPST?
V0latyle said:
So QPST can be used to flash bootloader, at which point someone should be able to use adb to flash the factory images? Wouldn't someone need to know the starting/ending addresses when writing to block devices?
Is there a reputable source from which to download QPST?
Click to expand...
Click to collapse
QPST / qfil links can be found in many places, I've found them in LG v35, v40, v50, G8 forums in guides section, usual title names include 'unlock bootloader' as qfil is used to flash the 'engineering abl' to gain fastboot.
addresses of the partitions are in the partition table of ea device. Depending on how you flash a partition you may need to know it specifically, but almost always you don't. The RawprogramX.xml has them in it if needed though.
There is one caveat, for qfil to work (or any EDL access to happen), with any device, one has to have the 'programmer firehose', which is a signed specific file, for that specific device type. Many mfgs make that file available, Google does not.
AsItLies said:
QPST / qfil links can be found in many places, I've found them in LG v35, v40, v50, G8 forums in guides section, usual title names include 'unlock bootloader' as qfil is used to flash the 'engineering abl' to gain fastboot.
addresses of the partitions are in the partition table of ea device. Depending on how you flash a partition you may need to know it specifically, but almost always you don't. The RawprogramX.xml has them in it if needed though.
There is one caveat, for qfil to work (or any EDL access to happen), with any device, one has to have the 'programmer firehose', which is a signed specific file, for that specific device type. Many mfgs make that file available, Google does not.
Click to expand...
Click to collapse
This was going to be my next question. We aren't talking about LG devices here; we're talking specifically about the Pixel 3. So if the firehose files aren't available, exactly how is QPST any good to anyone?
V0latyle said:
This was going to be my next question. We aren't talking about LG devices here; we're talking specifically about the Pixel 3. So if the firehose files aren't available, exactly how is QPST any good to anyone?
Click to expand...
Click to collapse
I know what we're talkin about here, and I know it's not LG devices. And I never said qpst was any good to anybody here, I just said that it is available, and you said it wasn't, and I said the stock images are available, and you said they weren't.
AsItLies said:
I know what we're talkin about here, and I know it's not LG devices. And I never said qpst was any good to anybody here, I just said that it is available, and you said it wasn't, and I said the stock images are available, and you said they weren't.
Click to expand...
Click to collapse
I think you misunderstand me. As I asked before, please post a legitimate and trustworthy source of QPST. According to Qualcomm, it's only available for specific commercial use.
Secondly, I was specific by what I meant by "binary images" - files to be flashed directly to the NAND devices by means of JTAG or other hardware level protocols. This would include the firehose images, although I admit I'm not sure if those are binary.
Either way, I reiterate that we are talking about the Pixel 3 here. If you know of a trustworthy source for QPST, that's a start. However, the fact remains that the files needed are not available, so what may or may not be possible with LG devices is not relevant in this thread.
V0latyle said:
I think you misunderstand me. As I asked before, please post a legitimate and trustworthy source of QPST. According to Qualcomm, it's only available for specific commercial use.
Secondly, I was specific by what I meant by "binary images" - files to be flashed directly to the NAND devices by means of JTAG or other hardware level protocols. This would include the firehose images, although I admit I'm not sure if those are binary.
Either way, I reiterate that we are talking about the Pixel 3 here. If you know of a trustworthy source for QPST, that's a start. However, the fact remains that the files needed are not available, so what may or may not be possible with LG devices is not relevant in this thread.
Click to expand...
Click to collapse
I think you misunderstood me. You indicated that QPST / qfil is not availabel, it is, I told you where to find it, put in the effort.
And what you mean by 'binary images' is obviously open to interpretation, how in the world would I (or anyone) know you mean anything other than what is available (from google), which are the binary images one would flash with qfil for that device. So again, you're wrong as they are available.
And I'll repeat again, I know we're talking about the p3 and not LG devices. You're using that as a deflection, to try to avoid that your post was obviously wrong in it's information. I bring up LG devices only because they have lots of documentation here on XDA re these utilities, while the p3 does not.
"what may or may not be possible with LG"... yer again wrong. Ea and every qualcomm device can be put in EDL mode, that's what QPST is used for, it's relevant to all devices that have a qualcomm chip.
AsItLies said:
I think you misunderstood me. You indicated that QPST / qfil is not availabel, it is, I told you where to find it, put in the effort.
Click to expand...
Click to collapse
I asked you to provide a specific source. I don't know which forums you're talking about on what site. They could be here on XDA, or Reddit, or any LG forum out there. Your response is akin to "just Google it". The only reputable source I know of is Qualcomm themselves, who, as I stated, are pretty picky about who gets access to the software. Sure, a Google search will turn up a handful of third party sites that claim to have it, but are they trustworthy?
AsItLies said:
And what you mean by 'binary images' is obviously open to interpretation
Click to expand...
Click to collapse
Not really. Binary images = files in purely binary format. Not Java, not hex - ones and zeroes, the file you would use to directly flash a memory device. I was pretty specific about that.
AsItLies said:
how in the world would I (or anyone) know you mean anything other than what is available (from google), which are the binary images one would flash with qfil for that device. So again, you're wrong as they are available.
Click to expand...
Click to collapse
Two posts ago you stated:
AsItLies said:
for qfil to work (or any EDL access to happen), with any device, one has to have the 'programmer firehose', which is a signed specific file, for that specific device type. Many mfgs make that file available, Google does not.
Click to expand...
Click to collapse
So, since no "firehouse" files are available from Google, could QPST be used to flash the partition images in the factory zips?
AsItLies said:
And I'll repeat again, I know we're talking about the p3 and not LG devices. You're using that as a deflection, to try to avoid that your post was obviously wrong in it's information. I bring up LG devices only because they have lots of documentation here on XDA re these utilities, while the p3 does not.
Click to expand...
Click to collapse
No, I'm pointing out that information on LG devices is not relevant. There might be documentation regarding the use of QPST but if the necessary files are not available, that's not much use.
AsItLies said:
"what may or may not be possible with LG"... yer again wrong. Ea and every qualcomm device can be put in EDL mode, that's what QPST is used for, it's relevant to all devices that have a qualcomm chip.
Click to expand...
Click to collapse
I'm specifically referring to the possibility of hardware level device recovery which may be possible on LG devices due to the availability of the required files, but is not currently possible on the Pixel series because we do NOT have the required files.
I'm not going to continue this argument as we are rather OT at this point. This isn't conducive to finding a solution.
XDA thrives on the willingness of users to help out everyone else - the ability and willingness to solve problems. You said there is a solution to this problem; I am asking you provide it. It doesn't matter who is right or wrong in the end; it only matters that we find a solution.
Hi, all. Please help me with some issues. Have Sonim XP5s dualsim gsm phone ATT locked.
1 Bootloader. Trying to unlock it.
*#*#2387#*#* activated USB debug. Set OEM unlock, but bootloader locked. fastboot unlock, fastboot oem unlock, fastboot flashing unlock do nothing. How i can unlock it?
2 Firmware. Does anyone have image to flash with QFIL? I try to flash empty one but QFIL say timeout and take no action. EDL started but ignore all requests. Bootloader issue?
3 SIM2 activation. Phone disable second SIM at all. Need correct firmware?
4 ATT unlock. How i can do it, with correct firmware installed?
5 Root. Kingroot, kingoroot no success. Custom recovery not found. Flashing\booting custom recovery is locked.
Thanks.
bumpity-bump
I have the same phone that I just bought and (sheepishly) just found out has wi-fi calling disabled by AT&T. That was a main reason for getting it, but unfortunately I went by the Sonim website's info and not AT&T's regarding that feature. Verizon's version has it enabled, but it's also much scarcer on the secondary market. The XP5800 doesn't seem to be a popular phone for tinkering judging by the lack of info on doing so.
Does anyone know if wi-fi calling could hypothetically be activated by rooting and then toggling some values, or is it more likely that the involved code was omitted entirely? I saw something to the former about tethering.
Bit_Basher said:
be activated by rooting and then
Click to expand...
Click to collapse
Still have found no rooting way. Bootloader locked, so no custom recovery can be used. Very unpopular phone, as you see, thread dead.
SpectralUA said:
Still have found no rooting way. Bootloader locked, so no custom recovery can be used. Very unpopular phone, as you see, thread dead.
Click to expand...
Click to collapse
Each Android can get rooted by means of SuperSU ZIP. Only requirement is to have successfully USB debugging option enabled in Android->Settings->Developer options. You install this ZIP via phone's stock recovery.
To access developer mode, google "developer mode sonim xp5s". Open article: kb.eschat.com "Open Developer Options Tab on Sonim XP5, XP5s or XP3...". The device will then open the Developer Options tab. Ensure the take bug report option is enabled, and that USB debugging is also enabled. You may also add a menu button to the Power tab for future access to this feature.
Be sure you use a clean SuperSU ZIP to avoid malware. Suggest getting one from the xda forum.
Hi. Is there any success with rooting or enabling second sim to working 2 sims together?
jwoegerbauer said:
Each Android can get rooted by means of SuperSU ZIP. Only requirement is to have successfully USB debugging option enabled in Android->Settings->Developer options. You install this ZIP via phone's stock recovery.
Click to expand...
Click to collapse
How i can do it? Stock recovery have no menu. /cache access denided from user. Putting update.zip do nothing without /cache/recovery/command. Did you know some trick to proceed install? ADB debugging enable, but no root rights there.
haikkk said:
Hi. Is there any success with rooting or enabling second sim to working 2 sims together?
Click to expand...
Click to collapse
Nothing.
Here are the firmware images for the Sprint XP5s
5SA.0.4-05-8.1.0-29.33.00_USER_PST.zip
Root has been achieved with Magisk!
ytagger said:
Root has been achieved with Magisk!
Click to expand...
Click to collapse
Is there any way to get Android Auto to work on the XP5s?
Hello All.
sorry for off topic, but can’t find anywhere.
does anybody know how to remove PIN on Sonim XP5s? Can’t access phone without entering PIN.
I would really appreciate for any help.
Thank you.
bkarshibaev said:
how to remove PIN on Sonim XP5s?
Click to expand...
Click to collapse
Recovery mode. Power + volUp long to show menu. Factory reset.
SpectralUA said:
Recovery mode. Power + volUp long to show menu. Factory reset.
Click to expand...
Click to collapse
Hello SpectralUA,
Does it really remove PIN?
I’m planning on buying Sonim XP5s and send it overseas. I just want to be 100% sure that Recovery mode will remove PIN.
Thank you.
bkarshibaev said:
Hello SpectralUA,
Does it really remove PIN?
I’m planning on buying Sonim XP5s and send it overseas. I just want to be 100% sure that Recovery mode will remove PIN.
Thank you.
Click to expand...
Click to collapse
Yes, it does, except if Factory Reset is blocked by Scout
ytagger said:
Yes, it does, except if Factory Reset is blocked by Scout
Click to expand...
Click to collapse
Is there way to check if Scout has restriction?
also, do you know which XP5s (AT&T, SouthernLinc, Sprint or Verizon) has wifi calling enabled and 2nd sim card slot is unlocked? I mean unlocked version of those 3 carriers.
Thank you.
bkarshibaev said:
Is there way to check if Scout has restriction?
Click to expand...
Click to collapse
Not if the device is PIN locked and you don't know it, obviously .
If it's open, just try to reset the phone from the regular menu and you'll see if it's restricted
bkarshibaev said:
2nd sim card slot is unlocked?
Click to expand...
Click to collapse
2nd sim usable without 1st. Found no way to enable both at same time.
Maybe anyone know how to dualsim (standby mode, etc) this unit?
ytagger said:
Here are the firmware images for the Sprint XP5s
5SA.0.4-05-8.1.0-29.33.00_USER_PST.zip
Click to expand...
Click to collapse
The link is not working. Do you have a different one?