Database Develop

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.

##778# no longer working for PRL update in 4.4.2 KitKat???

I did the KitKat update yesterday. I'm stock, S-OFF with FireWater and rooted (verified by RootChecker). I made the change ro.build.type=dev in /system/build.prop. The change remained over reboot. I also have developer options enabled. I dialed ##778#, as listed in the FAQ, but nothing happens. I've used ##778# to change the PRL on my EVO 4G LTE, but I actually never tried it on the ONE to see if it worked prior to the KitKat update. ##3282# will bring up EPST and prompt for MSL if "Edit" is chosen, but the menus that come up don't seem to have any options to change PRL.
Any suggestions on what to do? Is there anything else that needs to be changed? Cache wipe or something?? I did a lot fooling around on the EVO 4G LTE before I got the PRL change to work, including installing an EPST.apk at one point, but I don't know if that acutally did anything. I think my issues were due to initially being S-ON with hboot 2.09, and fixed when I went to S-OFF.
Thanks!

jbhtexas said:
I did the KitKat update yesterday. I'm stock, S-OFF with FireWater and rooted (verified by RootChecker). I made the change ro.build.type=dev in /system/build.prop. The change remained over reboot. I also have developer options enabled. I dialed ##778#, as listed in the FAQ, but nothing happens. I've used ##778# to change the PRL on my EVO 4G LTE, but I actually never tried it on the ONE to see if it worked prior to the KitKat update. ##3282# will bring up EPST and prompt for MSL if "Edit" is chosen, but the menus that come up don't seem to have any options to change PRL.
Any suggestions on what to do? Is there anything else that needs to be changed? Cache wipe or something?? I did a lot fooling around on the EVO 4G LTE before I got the PRL change to work, including installing an EPST.apk at one point, but I don't know if that acutally did anything. I think my issues were due to initially being S-ON with hboot 2.09, and fixed when I went to S-OFF.
Thanks!
Click to expand...
Click to collapse
From what I can tell ##778# does not work on stock no matter what changes you make (changing from user to dev or flashing the modded EPST) I have tried, never got it to work on stock.
There is a modded EPST.apk floating around the general section that will work on a custom rom if you change the ro.build=dev

BD619 said:
From what I can tell ##778# does not work on stock no matter what changes you make (changing from user to dev or flashing the modded EPST) I have tried, never got it to work on stock.
There is a modded EPST.apk floating around the general section that will work on a custom rom if you change the ro.build=dev
Click to expand...
Click to collapse
Is that your experience as well on the EVO 4G LTE? I am stock on the EVO 4G LTE, and did manage to get it to work there.

jbhtexas said:
Is that your experience as well on the EVO 4G LTE? I am stock on the EVO 4G LTE, and did manage to get it to work there.
Click to expand...
Click to collapse
I just updated my Evo 4G LTE to 4.3 last week and it would not work on a stock rom.
Something changed with both devices once they hit 4.3 (no longer able to use ##778# on stock)

BD619 said:
I just updated my Evo 4G LTE to 4.3 last week and it would not work on a stock rom.
Something changed with both devices once they hit 4.3 (no longer able to use ##778# on stock)
Click to expand...
Click to collapse
Thanks for the update. I haven't done the 4.3 stock update yet on my EVO 4G LTE

Would the CDMA workshop method for changing PRL work on the stock 4.4.2? If there's a reasonable chance it should, I can round up the files and give it a try...

jbhtexas said:
Would the CDMA workshop method for changing PRL work on the stock 4.4.2? If there's a reasonable chance it should, I can round up the files and give it a try...
Click to expand...
Click to collapse
I could never get the drivers to install...so not sure

chas posted the hacked epst for kitkat.... http://forum.xda-developers.com/showthread.php?t=2517223

BD619 said:
I could never get the drivers to install...so not sure
Click to expand...
Click to collapse
From Device Manager (and I was doing this on XP), it looks like the HTC diagnostic port has a Device ID of USB\VID_0BB4&PID_0FAB&MI_03. I found several versions of posted HTC diagnostic drivers, and checked the .inf file with the driver, but none of them supported a "model" matching this device ID (in particular, the bolded part). IT looks like a newer set of diagnostic drivers is needed...

O.M.J said:
chas posted the hacked epst for kitkat.... http://forum.xda-developers.com/showthread.php?t=2517223
Click to expand...
Click to collapse
Just for reference, I tried both of the EPST zips in that post with the stock ROM, but neither of them worked.

jbhtexas said:
Just for reference, I tried both of the EPST zips in that post with the stock ROM, but neither of them worked.
Click to expand...
Click to collapse
how are u installing on a stock ROM? it does work...

O.M.J said:
how are u installing on a stock ROM? it does work...
Click to expand...
Click to collapse
Copy KK_EPST.zip to sdcard
Boot to TWRP, press "Install", and select KK_EPST.zip
After install completes, press "Wipe Cache/Dalvik"
Reboot

I believe there is a solution to the problem of getting diagnostic drivers installed for the ONE. My wife has the ONE at work, so I can't test that right now, but I played around a bit with my EVO 4G LTE, for which I also previously could not get the diagnostic drivers installed. I added a line to the [Models] section of the driver's htcdiag.inf file that matched the Device ID obtained from Device Manager as described in my post above. This allowed the diagnostic driver to install, and I was able to access the EVO 4G LTE, and successfully send the MSL from CDMA Workshop. That's all I had time for this morning.
Again, this testing was done on the EVO 4G LTE, but since it seems that this driver is just installing some kind of USB serial port, it seems reasonable that it should work with the ONE as well; I will try the ONE tonight and report back.

I was able to get a PRL downloaded to the HTC ONE with the KitKat 4.4.2 stock ROM from CDMA Workshop. In order to do so, it was necessary to make a small change to the htcdiag.inf file that is part of the HTC Diagnostic driver. This change is described below. I was working with Windows XP SP3 32-bit. The procdure can probably be adapted to Windows 7. You will need CDMA Workshop (trial edition works) and a set of HTC diagnostic drivers. I would recommend making a backup of the phone and the htcdiag.inf file.
PLEASE NOTE THAT YOU USE THIS PROCEDURE AT YOUR OWN RISK. WORKING WITH CDMA Workshop CAN POTENTIALLY DAMAGE/BRICK YOUR PHONE IF YOU ARE NOT CAREFUL. INSTALLING FAULTY DRIVERS MAY DAMAGE YOUR WINDOWS INSTALLATION. YOU ARE RESPONSIBLE FOR ANY DAMAGE TO YOUR EQUIPMENT.
1. Dial ##DIAG# (##3424#) on the HTC ONE, and select "YES" to enable diagnostic mode. If you a trying this on a different phone or different ROM, diagnostic mode may already enabled after dialing ##DIAG#. This should cause Windows to present several prompts for installing drivers. Cancel all of these requests.
2. After this, open Device Manager, and you should find the "unkown" devices shown in the attached image xd1.png. The HTC ONE presents two devices "HTC DIAG" and "HTC 9K DIAG". For the ONE, I could only get "HTC 9K DIAG" to work. For the EVO 4G LTE on Android 4.4.1, only the "HTC DIAG" device is presented, and it does work.
3. Right-click on the "HTC 9K DIAG" device, select "Properites", and then the "Details" tab. You should see something similar to what is shown in attachment xd2.png. Note the part of the Device Instance ID inside the red box.
4. Find the htcdiag.inf file in your set of HTC diagnostic drivers. In my driver set, this file was located in the "Win x86" foler. The version of my driver is shown in attachment xd3.png.
5. Locate the [Strings] section of the inf file, as shown in attachment xd4.png. Note the variable assigned to "HTC Diagnostic Interface" . In the case of this inf file, that variable is "OEMDevice02".
6. Locate the [Models] section of the inf file, as shown in attachment xd5.png. Find a line in this section that begins with the variable identified in step 5. Copy this line to a new line in the [Models] section. Modify the Device Instance ID portion of the copied line to match the portion of the Device Instance ID inside the red box as described in step 3. Save the inf file.
7. Right-click on the "HTC 9K DIAG" device in Device Manager and select "Update Driver..." The steps below may vary a bit, but ultimately you want to get to the point where you can select the htcdiag.inf file modified in step 6.
6a. Select the "Install from a list or specific location (Advanced)" radio button, and click"Next"
6b. Select the "Don't Search. I will select the driver to install" radio button, and click"Next"
6c. Select "Show All Devices" in the listbox and click "Next"
6d. Select the "Have Disk" button and click "Next"
6e. Select the "Browse" button, locate and select the htcdiag.inf file modified in step 6, and click "Open"
The driver should now install if the inf file has been correctly modified. You will have to ignore the complaints about the driver being unsigned.
7. After the driver is installed, you should see an "HTC Diagnostic Interface" in Device Manager's "Ports" tree, as shown in attachment xd6.png. The "(COMx)" portion indicates the port that will be used with CDMA Workshop. From this point, the procedure documented at http://forum.xda-developers.com/showthread.php?t=1673490 can be used to load the PRL of your choice. Be sure to reboot the phone after installing the PRL.
This worked for me. Given the fickle nature of computers, it may or may not work for you. Thanks!

Help with Bootloader and Root. I'm stuck! XT1063

Hello!
I'm from Puerto Rico, my carrier is Claro PR. I've been trying to root my device but so far I haven't even been able to unlock the Bootloader. I get the annoying and indefinite < waiting for device > message on the Fastboot CMD screen. I have installed ADB drivers from Google and it didn't help since the Motorola drivers did not even recognize my device in Fastboot. It seems that the only time my device is recognized in Fastboot mode is when there are no ADB or Fastboot drivers installed and Device Manager lists it as a Fasboot Titan device. Quite honestly this is very frustrating since I've been searching for days to no avail. I do not wish to update to Lollipop(Until it is available officially in my area), which is what most articles I found are for. I just want root access. I'm beginning to doubt if my device is even supported and its just an extremely well made clone.
I was trying this on Windows 8.1 Pro x64. Some people told me Fastboot drivers had some issues with 8.1 so I did my best to clean out old drivers and plug the phone into different USB ports. At first I was trying on my USB 3.0 ports, people also told me USB 3.0 has issues with FB, so I used my 2.0 ports on the front of my computer case. Again, people told me that I had to use ports directly on the motherboard, so I plugged the phone into my PC's back USB ports. I also tried a different micro USB cable, same result. At that time I figured it was probably Windows causing the problems so I pulled a hard drive from and old PC, hooked it up to my own and installed my old copy of Windows 7 Ultimate x64. I installed all the essentials, from ADB to Motorola Device Manager for the drivers. My phone is still not being recognized, although I did get to have it listed under ADB Devices by using USB Debugging, yet it appears offline, as shown in the image below. I figured it was my particular PC because its custom built with salvaged parts from another PC, so I tried the procedure from my family's Dell Optiplex (running win7 Home Premium x32) only to hit the same dead-end. At this point I'm tearing off hair from my head. I don't want to be bald yet! I'm only just turning 20 at the end of the month!
A few details:
Device: Moto G 2014 16GB XT1063. Android Kitkat 4.4.4 (5.0 has yet to be released for my area)
System Version: 21.11.14.titan_amxpr.amxpr.en.PR amxpr
Build number: KXB21.85-14

Inquisitor956 said:
yet it appears offline
Click to expand...
Click to collapse
If you connect your device with usb-debugging enabled in the developer options, a dialog pops up, presenting a RSA fingerprint, asking to allow usb-debugging. If not, type "adb version" in your terminal. If version is below 1.0.31 you have to update adb.

doppelhelix said:
If you connect your device with usb-debugging enabled in the developer options, a dialog pops up, presenting a RSA fingerprint, asking to allow usb-debugging. If not, type "adb version" in your terminal. If version is below 1.0.31 you have to update adb.
Click to expand...
Click to collapse
Thanks solved a problem I had on other laptop that would not show phone

doppelhelix said:
If you connect your device with usb-debugging enabled in the developer options, a dialog pops up, presenting a RSA fingerprint, asking to allow usb-debugging. If not, type "adb version" in your terminal. If version is below 1.0.31 you have to update adb.
Click to expand...
Click to collapse
Thank you! The RSA Fingerprint popup never appeared on my phone. I kept toggling USB Debugging on and off until it did. I managed to get the keys. Now I hit another wall... (image below)
I also tried it onto the Latin America page. This time no matter how I paste my code whether manually typing it or just copy/pasting, it always returns a popup with "Your input text was not recognized as a valid dataset. Please try again." This happens on Chrome, Firefox and even Internet Explorer and combined with the really slow loading of any official Motorola page I try to enter I'm guessing the forces of life itself are preventing me from unlocking this particular phone's Bootloader.

Inquisitor956 said:
preventing me from unlocking this particular phone's Bootloader.
Click to expand...
Click to collapse
Please have a look here: https://forums.motorola.com/posts/f2061da875

doppelhelix said:
Please have a look here:
Click to expand...
Click to collapse
Thank you once again! My device IS unlockable, I was told to wait for some time before requesting my unique unlock key, since the page has been having a few hiccups. I will report back if I was successful or not.
Edit: I successfully unlocked bootloader, installed TWRP and rooted. Thank you for your assistance!

http://developer.sonymobile.com/ instructions to Unlock Bootloader - problems

I'm having some problems following the instructions from http://developer.sonymobile.com/ regarding setting up Android Studios and the recommended 'fastboot' drivers on Win 10. I have done some vocoder development in the past and have a background in tech development and dedicated microprocessor programming, but i'm in over my head here. I could use a little help.
This is on a Sony Xperia Z Model C6606 4.3 T-Mobile variant Build 10.4.C.0.814. Even though I checked (by *#*#7378423#*#*) and got unlock bootloader allowed: No.; T-Mobile tier 2 technical support indicated that I should try the OEM method anyway. When I checked their site, I plugged in all the info about my phone and it indicated that I could unlock the boot loader. :Big Grin:
Now to the problems. This is where you hear the *blub blub* as I wade into the deep end.
Their instructions read in part, "1. Download and install the Android SDK."; which I did, including loading the Google USB drivers.
2. If you’re running Windows, you also need to download and install an updated Fastboot driver. This is the standard android_winusb.inf-file, with a few lines of code added to enable Fastboot to support Sony & Sony Ericsson devices. Replace the original android_winusb.inf-file with the downloaded file in the usb_driver folder, located in the Android SDK > extras > google folder on your computer. If you can’t find the usb_driver folder, make sure you are running Google USB Driver package revision 4 or higher in your Android SDK. If not, install the Google USB Driver Packager using the Android SDK manager.
Note: Google USB Driver Packager is ver. 11
After a visit to the device manager, following numerous tips from various sources and floundering about, I looked at the two INFs and found some discrepancies. The first is the one from the Sony 'fastboot driver' link above for their version of android_winusb.inf. The error I get here is based on the fact that this download contains NO CABS and the Google USB cabs do not have the installation files the Sony INF needs. On the other hand the Google USB 'extras' loaded by Android Studio do not include specific support for the Sony Xperia Z. :forehead slap:
Short version, I can't connect to fastboot.
I have tried both INFs and in each case with USB debugging enabled on the Z, I powered it down, held the VOL up button as I plugged the cable into the USB port. In all cases I got the blue light but no windows prompt asking for a driver! Even when I open a command window in the directory where the INF resides I DO NOT get a list of adb devices. If I enter 'fastboot devices' from the command prompt, I get the stock windows error that 'fastboot' isn't a recognized command.
If I could get a little direction here as to next steps, I would really appreciate it. Thanks.

Download an install flashtool, you'll find a link here in the forum. Can't search myself right now as I'm on the phone with slow Internet. In the thread is everything explained and it's very simple to use.

Oops
The correct folder is \AppData\Local\Android\sdk\platform-tools. No wonder it wouldn't load fastboot. Ultimately however, fastboot with the OEM unlock code didn't work. "FAILED (remote: Command not allowed)". BUMMER!
Thanks anyway. Now I'm off to flash what I can...

Best mehod is to install 15 second adb install-it installs adb and fastboot and can be open anywhere
give it a try
http://forum.xda-developers.com/showthread.php?p=48915118

ManagementCritic said:
....Even though I checked (by *#*#7378423#*#*) and got unlock bootloader allowed: No.....
Click to expand...
Click to collapse
Your bootloader cannot be unlocked. Blame your operator...

Hey ptmaniac,
Thanks for the response.
Yeah, I get that. I wrote in another thread how I had attempted to negotiate a remedy through both the OEM and the carrier; not that I expected a good result, but probing for what was left unsaid. I wanted to see if I could determine their reasons and motivation and whether they would consider any alternatives. The only admission was that they could, but would not. Best guess? It has to do with existing agreements they are unwilling to revisit.
ptmaniac said:
Your bootloader cannot be unlocked. Blame your operator...
Click to expand...
Click to collapse

@ManagementCritic
No problem,
In my country it's the same endless loop unfortunately... the carrier says i should talk to the oem, the oem says the phone was locked at carrier request and they can't do anything about it so i should talk to the carrier instead
I still blame myself from buying a full priced device locked to the carrier, i thought all of them could be unlocked anyway by submitting imei to the sony developer website... if i had researched a bit more i would have figured out that i should have bought it unlocked directly from the oem... lesson learned i guess.

Where to get Nokia Drivers for Linux?

Got an old Nokia 8 that I wish to flash. The instruction says first I need to get Nokia drivers and unlock but the link provided requires NextCloud login. I googled and only found "Nokia USB Drivers for Windows". I'm using a Linux machine and I'm not sure whether this "USB drivers" is what I need. Help please?

All you need are "adb" & "fastboot" drivers. You can get them from your package manager.
EDIT: Those are used for flashing. For unlocking the bootloader I have no idea.

To unlock the bootloader the manufacturer-Nokia no longer supports this terminal, it no longer supported it in December 2021 when I wanted to unlock the bootloader of my Nokia 8 TA-1052, I unlocked mine through a website called techmesto .com. It's been commented on this forum about it.