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.

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.

I need help to unlock bootloader

Hello everyone,
I've decided to unlock my device to flash vanilla android but I couldn't unlock it. I've tried almost everything but even the latest MiUnlock doesn't recognize my device on fastboot, the PC itself recognizes it before and after getting into fastboot, I hear usb device connected sound and can see the phone under Windows devices.
Adb devices command works if the phone is switched on, my dev settings are ok, oem unlocking and adding account under dev settings are ok, I've tried it with disabled windows signature enforcement too but nothing happened. MiUnlock simply doesn't want to see the device on fastboot.
Can anybody help me, please?

abstra said:
Hello everyone,
I've decided to unlock my device to flash vanilla android but I couldn't unlock it. I've tried almost everything but even the latest MiUnlock doesn't recognize my device on fastboot, the PC itself recognizes it before and after getting into fastboot, I hear usb device connected sound and can see the phone under Windows devices.
Adb devices command works if the phone is switched on, my dev settings are ok, oem unlocking and adding account under dev settings are ok, I've tried it with disabled windows signature enforcement too but nothing happened. MiUnlock simply doesn't want to see the device on fastboot.
Can anybody help me, please?
Click to expand...
Click to collapse
The issue that you are experiencing is strictly with your PC.
You need to ensure that you are using an account that has admin privileges, and be sure that you antivirus is not neutering your usb drivers and Miflash program.
Next, if you are using a newer computer with usb 3 ports, you will need to use a USB hub ( USB 2 is your best option.) , then the phone will be seen in fastboot. As long as you have setup developer options, and your MiCloud account is setup.
Finally, it will take 2 weeks to unlock the bootloader , after your first request. Some people who had been syncing the phone to MiCloud for some time before attempting were able to immediately unlock. Personally we have 3 Mi8's in our house and I had to wait 2 weeks on each one.
To reiterate, your main issue is probably the usb ports, and your antivirus the the 2nd most likely culprit. Worst case use another computer. The process is much easier on older PC's.
you can use the the All in one tool to double check that your drivers, adb , and system wide privileges are up to date and setup correctly. https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
Instructions are available on that thread.

Thanks for your help, I've already tried almost everything you've said up there and even gave a try on virtualbox Windows 7 with USB 2.0 setup.
I remember I've unlocked my friend's device last year on an only USB 2.0 computer, my laptop has unfortunately only two 3.0s and one USB-C. The phone can be seen under fastboot devices command if MiUnlock is not running, if I click on that cr*p program my device either falls from fastboot devices list or says press any key to shutdown.
The main problem is the ports and that damned program itself, how come it lockdowns the connection and after that pc couldn't even show my phone in devices list but can be seen in device manager. I'm literally shocked by the cheapness of this very software.

abstra said:
Thanks for your help, I've already tried almost everything you've said up there and even gave a try on virtualbox Windows 7 with USB 2.0 setup.
I remember I've unlocked my friend's device last year on an only USB 2.0 computer, my laptop has unfortunately only two 3.0s and one USB-C. The phone can be seen under fastboot devices command if MiUnlock is not running, if I click on that cr*p program my device either falls from fastboot devices list or says press any key to shutdown.
The main problem is the ports and that damned program itself, how come it lockdowns the connection and after that pc couldn't even show my phone in devices list but can be seen in device manager. I'm literally shocked by the cheapness of this very software.
Click to expand...
Click to collapse
Again the issue is with windows, I have personally dealt with the exact same issue. That is why I recommended using an older computer that has not been recently updated.
But you are absolutely right, Xiaomi has not made any development improvements with their desktop applications in over a year and that is ridiculous.
I would suggest using alternate versions of the software : I just did a google search and on this link people were saying just one week ago that this linked software worked for them, note its a video, the software link is in the description : https://www.youtube.com/watch?v=l_PEAJ-n2_c
Finally, I am personally using this version of Mi Flash : https://androidfilehost.com/?fid=11410932744536991669 on a brand new intel PC.
and the last time that I unlocked a xiaomi phone I used unlocker software from here ( Note the multiple versions at bottom of page)
https://mi-globe.com/download-xiaomi-mi-unlock-tool-all-versions/
If one doesn't work try another. just be sure that you have developer options setup correctly and that you are signed in a syncing with mi-cloud. You will get it unlocked eventually. I can assure you that it was a Pain in the A*$ for me too!

Thanks man, these are the exactly same links I’ve found and checked out while trying to connect my phone but I just gave up after three days of struggling and pressing volume+power buttons and ordered a USB 2.0 hub online. Unfortunately there are no older computers around me or anyone I can ask for because of you know, the quarantine. I’m actually using cloud actively, so I should better be prepared for an immediate unlocking, and backup my data beforehand as usual.

Just wanted to write about the news, I've backed up my data and connected my device to MiUnlock on USB 2.0 Hub and ta-da it's immediately unlocked without any waiting time. That was a smooth process, I'm shocked but happy.

abstra said:
Just wanted to write about the news, I've backed up my data and connected my device to MiUnlock on USB 2.0 Hub and ta-da it's immediately unlocked without any waiting time. That was a smooth process, I'm shocked but happy.
Click to expand...
Click to collapse
Nice, so my original suggestion about using 2.0 usb was correct. I am glad that you have the issue sorted. I am also surprised about you being able to avoid the wait time. That is a nice break. Enjoy your phone.
PS: Be sure to make a full TWRP backup and save it to your desktop. That backup will save you if you ever experience a bad issue.

tsongming said:
Nice, so my original suggestion about using 2.0 usb was correct. I am glad that you have the issue sorted. I am also surprised about you being able to avoid the wait time. That is a nice break. Enjoy your phone.
PS: Be sure to make a full TWRP backup and save it to your desktop. That backup will save you if you ever experience a bad issue.
Click to expand...
Click to collapse
Thanks man, and yes that was all about fastboot which is written to be used with older usb versions. After plugging in the hub, it’s connected directly in just milliseconds. I am surprised that I’ve really skipped the waiting for two weeks or maybe more and yeah it makes me happy.
I made a full data backup before unlocking and then all the dangerous partitions including modem, efs and bluetooth in TWRP to avoid any irreversible loss. I never skip my recovery backups since 2010 and my first Android smartphone which was an HTC Desire A8181, I learned it in a hard way to never skip them, if you do, you either lose your data or your mobile device identification. :victory:
A question from a Xiaomi-newbie; If I run clean all and lock command on MiFlash, should I wait for an unknown time to unlock the device again? Or does Xiaomi let users to lock/unlock their devices anytime without waiting if you’ve unlocked your bootloader once before?

abstra said:
Thanks man, and yes that was all about fastboot which is written to be used with older usb versions. After plugging in the hub, it’s connected directly in just milliseconds. I am surprised that I’ve really skipped the waiting for two weeks or maybe more and yeah it makes me happy.
I made a full data backup before unlocking and then all the dangerous partitions including modem, efs and bluetooth in TWRP to avoid any irreversible loss. I never skip my recovery backups since 2010 and my first Android smartphone which was an HTC Desire A8181, I learned it in a hard way to never skip them, if you do, you either lose your data or your mobile device identification. :victory:
A question from a Xiaomi-newbie; If I run clean all and lock command on MiFlash, should I wait for an unknown time to unlock the device again? Or does Xiaomi let users to lock/unlock their devices anytime without waiting if you’ve unlocked your bootloader once before?
Click to expand...
Click to collapse
I have only unlocked my device once. But I wouldn't think there would be an issue to unlock a second time. In fact, I have read about some people needing to wait 72 hours to unlock it again after relocking. if using Mi-Flash just try to be sure uncheck that lock bootloader box, that is unless you want it locked.
One last thing, if you ever decide to restore the phone using the flashall.bat method, the bootloader stays unlocked.

Unlock carrier locked bootloader Pixel [BETA]

UPDATE AS OF 16 OF MAY 2023
This project isn't working right now, but I am still working on it.
However due the complicated nature of the projects and the fact that I have little free time means this project will probably still take time to get to functional state.
If anyone has any idea please contact me, any hell is welcome!
______________________________________________________
Hi!
So I decided I wanted to flash custom software into my phone, but it's bootloader was locked so I figure a way to unlock it!
I am going to leave 2 methods:
1. It's the most risky but has more chance of working. The idea is to flash the whole firmware again to the phone, but from an unlocked model.
This is posible using the EDL mode and Sahara protocol.
The EDL mode is an emergency mode which allows user to flash firmware in case fastboot and ADB fails. It's also available in all Qualcomm devices.
It is also completly independent from the rest of the phone, and it's the first bootloader we have. If everything is ok it triggers the second bootloader(fastboot) which then boots the system(See the diagram if you want).
As we want to reflash the firmware keep in mind this could brick your phone and I won't take any resposability if it happen
Materials:
-QPST
-Qualcomm Driver
-Working USB Cable
-Fastboot and ADB set up and working
-knoledge on using ADB
Procedure:
1. Download and install Qualcomm drivers
2. Download and install QPST
4.Downlaod the MBN file
3. Reboot
4. Connect the phone to the PC, then open cmd and run "adb reboot edl".
If you are on fastboot mode, then try "fastboot oem edl", "fastboot reboot-edl", "fastboot reboot edl". One of this should work
5. Go to C:\Program Files\Qualcomm\QPST\bin\
6.Open QPST Config(it's a blue phone, see picture)
7. Click on "Start clients" and then "Software download". A new window should open
8. Now we need to select the phone image using the browser button
9. Click on start to flash ⚡️
Please be aware the method wasn't tested, so this could brick your phone.
If you decide to try it, and have questions or ru into problems during the process, please let me know.
Also remember to take a backup of your data, as it is goig to be lost. ℹ
____________________________________________________________________________
As for the second method, I tried it and it didn't work for me, but is completly safe so you may want to give it a try.
1. Enrrol on the android 12 beta program, AND MAKE A BACKUP OF YOUR DATA
2. Install the update
3. Now exit from the beta program
4. Now you should have an update, it's a rollback to the stable version of android 12. After you installed the update the phone will restart and factory reset.
5. Do the setup as normal
In the end you may have unlocked the bootloader, to check just go to developer options and check if it is enabled or not.

Can we get a video of how to do this?

trzpro said:
View attachment 5491701
Click to expand...
Click to collapse
So you attempted one of these methods and did it work or not work.What device did you use?

trzpro said:
View attachment 5491701
Click to expand...
Click to collapse
That seems to be a probelm with the drivers. Did you install everything properly?
You may want to uninstall them and reinstall again to see if we solve the problem. Also try to run the app with admin privileges
Let me know how if you have more issues or if this doesn;t solve the problem at all.

AtrixHDMan said:
Can we get a video of how to do this?
Click to expand...
Click to collapse
I can make a video, but I can only publish it on January. Untill then I think the guide is easy to understand so if you want to try the method you shouldn't have problems.

#mcl said:
I can make a video, but I can only publish it on January. Untill then I think the guide is easy to understand so if you want to try the method you shouldn't have problems.
Click to expand...
Click to collapse
I understand thanks

#mcl said:
这似乎是驱动程序的问题。您是否正确安装了所有内容？
您可能需要卸载它们并重新安装，看看我们是否能解决问题。还尝试以管理员权限运行该应用程序
如果您有更多问题，或者这根本无法解决问题，请告诉我
MOD EDIT: You may need to uninstall them and reinstall to see if we can fix the problem. Also tried running the app with admin rights
Let me know if you have more questions, or if this doesn't solve the problem at all.
Click to expand...
Click to collapse
同样的问题，无法解决。
MOD Edit: Same problem, can't solve it.

Looks like this is a common issue, I will look the documentation of QPST and see if I see the cause of the problem. Thank you guys for helping up this project

So I found that that version of QPST is outdated(it's the 2.7 build 140 and the latest version is 2.7 build 460). I am leaving a zip with it here.
Try and see if this time around we manage to unlock the bootloader

MOD EDIT:
This is the latest version
这是最新版本

#mcl, I have the same problem as you have, I live in Portugal and bought a used Pixel 4 but apparently it's origin is the US, Verizon. From your original post I take it that you didn't try this method yourself and hope others will try? Or were you successful?

for anyone in the same situation, read this thread: https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel
My guess is: if your pixel's " OEM unlocking " is greyed out it will not be possible to unlock. Although I didn't try the EDL route I'm quit sure that at some point you will get a message "bootloader is locked"

gentle_giant said:
for anyone in the same situation, read this thread: https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel
My guess is: if your pixel's " OEM unlocking " is greyed out it will not be possible to unlock. Although I didn't try the EDL route I'm quit sure that at some point you will get a message "bootloader is locked"
Click to expand...
Click to collapse
Hey I am quite busy recently so I haven't really had time to look more on the thread, though I believe there will always be a way, it may be hard to find but no OS is perfect, and Android is no exception. As it turns out, even if this method worked, when it connect to the internet there will be a high chance that using the IMEI of the phone it will "remember" it's a locked model and won't allow you to flash new firmware.
However I am working on a new method, which is also safer, though I have still work to do, so when It is ready I am going to publish another guide.
Good luck all untill them

Hi mcl, my problem is: I do like to change OS and I did so on my previous HTC M7 and M10. And these 2 phones still function with PixelExperience 10 or 11.
But at best I'm a simple layman with a lot of enthusiasm.
Anyway, I will keep an eye on this thread and hopefully you will find time to make this new method work!
By the way, I see that we are "neighbors", I live in Portugal.

gentle_giant said:
Hi mcl, my problem is: I do like to change OS and I did so on my previous HTC M7 and M10. And these 2 phones still function with PixelExperience 10 or 11.
But at best I'm a simple layman with a lot of enthusiasm.
Anyway, I will keep an eye on this thread and hopefully you will find time to make this new method work!
By the way, I see that we are "neighbors", I live in Portugal.
Click to expand...
Click to collapse
Hahah yeah we are definitely neighbors.
Well I do want to become a software engineer though right now I am just a busy enthusiastic.
I also really enjoy custom OS, when I had my Galaxy S9 I used to have custom ROMs.
Hope I manage to find a new solution as soon as posible for all if you guys!!!

How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com

any luck with that? can I backup my firmware before doing it?

darknmy said:
How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com
Click to expand...
Click to collapse
We are not doing physical atack, so that is not a problem for us.
Also, I don't believe the pixel 4 XL is perfect, for sure there are errors and security vulnerabilities. We just need to find them.

Question Update OnePlus 10 Pro from HydrogenOS (CN) to OxygenOS (EU/GL/IN) without rooting

This process uses Oxygen Updater as I haven't found the full EU/GL/IN stock ROMs anywhere else.
Update OnePlus 10 Pro NE2210 (CN) from HydrogenOS (NE2210_11_A.12) to OxygenOS EU (NE2213_11_A.12)
Download [Play Store] apk and install
[Play Store] install [Oxygen Updater]
[Oxygen Updater] Device: One Plus 10 Pro EU
[Oxygen Updater] Update method: Stable (full)
[Oxygen Updater] Settings > Advanced Mode - activate
[Oxygen Updater] Update > Download the full stock ROM (4.15 GB)
Activate Developer Options
Update > Local install
CURRENT STATUS: Verification failed
I've done this process before for other OnePlus phones and it was very straightforward. For some reason is not working with this OnePlus 10 Pro. Any insight on how to continue?
Thanks!

Bump, redownloaded again the EU version, resetted phone, still fails. Whyyy! Anyone can advise how to go from Hydrogen to Oxygen? Thanks!

Short description for "How to switch from ColorOS (Chinese version) to OxygenOS (IND/EU) on OnePlus 10 Pro". I did the flash under Windows 10, even if I'm usually a Linux guy...
BEFORE DOING THIS MANUAL, MAKE A BACKUP OF THE DATA OF YOUR DEVICE! Your phone will be DELETED completely!
1.)
- Download the desired ROM (Oxygen OS 12.1 A11 (IND) or Oxygen OS 12.1 A12 (EU) (Auntie Google has the answer, effective April 2022) -> extract
- download OnePlus_USB_driver.zip:
https://oneplususbdrivers.com/download-oneplus-usb-driver/ -> extract
- download Android Platform SDK:
https://www.techspot.com/downloads/downloadnow/5425/?evp=de0a68064118855fcddcc3980a2143c4&file=6062 -> extract
- download "Fastboot Enhance Tool": https://forum.xda-developers.com/t/...enhance-payload-dumper-image-flasher.4310553/ -> extract
2.) First of all, disable driver signature check for Windows 10, because the OnePlus drivers are not signed (yet).
3.) After restarting Windows, install the OnePlus drivers by executing the .exe file from the extracted folder.
4.) Copy the payload.bin file from the downloaded ROM into the folder where the fastbootenhance tool is located
5.) Enable Developer Options on your phone
6.) Enter the Developer Options, enable OEM unlock and USB debugging there
7.) Now connect your OnePlus 10 Pro to your computer by a USB cable. Make sure it's started, screen unlocked and charged over 60%
8.) On your computer, open File Explorer and switch to the Android SDK folder. Click in the address line above and type CMD [Enter]. A CMD window opens in the SDK folder.
9.) In CMD, type "adb devices". A new line should appear with the encrypted name of your device. When an empty line is returned, check the driver installation. If this line returns the name, but the suffix "not allowed", you must first allow this connection ON YOUR PHONE. Disconnect and reconnect your device and confirm the popup that appears on your phone! (Best is to enable "Always allow connections from this computer"!)
10.) Now type "adb reboot bootloader" in CMD. Your telephone restarts automatically to bootloader mode. In this mode your phone should tshow you it's name and beside of some other information you don't need, that the bootloader is LOCKED.
11.) Type in CMD "adb flashing unlock [Enter]". Now your phone should restart and ask you, if you want to unlock the bootloader or do not unlock the bootloader. With the volume buttons, switch to "UNLOCK BOOTLOADER" and confirm by pressing the Power Button.
12.) After doing so, restart your phone. After rebooting, go back to CMD and type "adb reboot fastboot". Your phone now should restart to "FASTBOOTD MODE". You are asked to choose a language (I recommend english after all... ;-) )
13.) Open the "Device Manager" on your computer.
14.) If device manager shows you some unknown device like "Android: ! 'ossi'" or similar, your device is not recognized in fastbootd mode. In that case continue with pt. 15. Otherwise continue with pt. 19
15.) Right-click on the unknown Android device and choose "Update driver..." -> "Search my computer for drivers" -> "Pick from a list of available drivers on my computer"
16.) When OnePlus drivers where installed correctly some steps above, Device Manager should suggest you 3 different possible drivers. Choose "OnePlus ADB Interface Manager" and confirm your choice. Windows will warn you that a wrong choice will crash Windows. Confirm also this warning.
17.) If everything went good, the before unknown device will change to an Android ADB Interface Device. When that happend, everything is good and you're good to go on.
18.) Just to be really sure: Type in CMD again "fastboot devices" and your computer should tell you the s/n of your phone with the suffix "fastboot". This will tell you your device is recognized in fastboot mode.
19.) Start "FASTBOOTENHANCE" tool from the respective folder (Folder name "release")
20.) Now you can follow the instructiions here at pt. 8.:
How to Install Indian ROM on Chinese OnePlus 10 Pro
In this comprehensive tutorial, we will show you the detailed steps to install the Indian ROM on the Chinese OnePlus 10 Pro.
www.droidwin.com
Puuuuuuh! That was enoying..! Maybe I have missed something... If so, please tell me by PN and I will complement this manual. But at this time, I guess it should work. I did it right like that this day - and it works fine! Finally I have my foremost chinese OP10Pro with a EU ROM in (swiss) german!
And if it works just like that (after my manual), please let me know as well!
Have fun! Oliver
Oh, there's something I forgot: I had after flashing still about a dozen of chinese apps I had to delete manually. Don't be surprised by that!

Thank you! Can you relock the bootloader afterwards? What model shows in the phone info screen?

This worked for me! Thanks very much.
After installing EU firmware, I factory reset the phone but Google Pay wont work saying the phone is rooted but when I launch Root Checker, it says ' Sorry! Root access is not properly installed on this device'
Is the root broken? Do I need to root again? Any ideas how to fix?

Lynxy0 said:
This worked for me! Thanks very much.
After installing EU firmware, I factory reset the phone but Google Pay wont work saying the phone is rooted but when I launch Root Checker, it says ' Sorry! Root access is not properly installed on this device'
Is the root broken? Do I need to root again? Any ideas how to fix?
Click to expand...
Click to collapse
If you relock the bootloader and reset, does it behave like a normal non-rooted phone with EU firmware?

Ultimatum99 said:
If you relock the bootloader and reset, does it behave like a normal non-rooted phone with EU firmware?
Click to expand...
Click to collapse
Good shout - Let me try that and get back to you.

Yes, this worked

Lynxy0 said:
Yes, this worked
Click to expand...
Click to collapse
Did the Chinese apps disappear once you locked the bootloader and resetted? Which method did you use to relock? What model is being shown in the phone info page? Thanks!!!

No they did not. After the first flash, the OP Launcher was back (previously it was Google Phone Launcher) . I factory reset and Chinese apps were back.

Ultimatum99 said:
Thank you! Can you relock the bootloader afterwards? What model shows in the phone info screen?
Click to expand...
Click to collapse
Hi Ultimatum99
I didn't relock my bootloader yet, but I'll do it in the next days, I'll post the update here. (Speaking technically it's possible, yes, but I don't know yet what happens...) And my model shows "NE2213" after the update.

Lynxy0 said:
This worked for me! Thanks very much.
After installing EU firmware, I factory reset the phone but Google Pay wont work saying the phone is rooted but when I launch Root Checker, it says ' Sorry! Root access is not properly installed on this device'
Is the root broken? Do I need to root again? Any ideas how to fix?
Click to expand...
Click to collapse
Hi Lynxy0
No, your phone is not rooted, but the bootloader is still unlocked, even after the update. And that means your phone is vulnerable to attacks from outside. So Google Pay tells you your phone is rooted, just to keep you safe. Try to relock your bootloader, this should solve the problem. (I didn't do it yet, but I'll post the update when I've done it.)

Lynxy0 said:
Yes, this worked
Click to expand...
Click to collapse
Haha... I was too late then!(See my last replay...) But thanks for the feedback!

Lynxy0 said:
No they did not. After the first flash, the OP Launcher was back (previously it was Google Phone Launcher) . I factory reset and Chinese apps were back.
Click to expand...
Click to collapse
This is unfortunately a bad thing... Some chinese apps are really back, even after flashing and resetting the device. But I could delete them manually. Yeah, it took me a few minutes, but at least, I had (finally) my beloved OxygenOS back! (After I crashed my OP6T almost 2 years ago, I chose a Oppo FindX 2 Pro - and after almost 2 years I still regret to have paid for this phone... The hardware was really cool, but ColorOS is ... So I was really terrified when I learned my brand new [chinese] OP10Pro had ColorOS installed by default..!)

Loba74 said:
This is unfortunately a bad thing... Some chinese apps are really back, even after flashing and resetting the device. But I could delete them manually. Yeah, it took me a few minutes, but at least, I had (finally) my beloved OxygenOS back! (After I crashed my OP6T almost 2 years ago, I chose a Oppo FindX 2 Pro - and after almost 2 years I still regret to have paid for this phone... The hardware was really cool, but ColorOS is ... So I was really terrified when I learned my brand new [chinese] OP10Pro had ColorOS installed by default..!)
Click to expand...
Click to collapse
Let us know if you manage to relock the bootloader and share the full process please, I can update the guide with your findings. Thanks!

Loba74 said:
Hi Lynxy0
No, your phone is not rooted, but the bootloader is still unlocked, even after the update. And that means your phone is vulnerable to attacks from outside. So Google Pay tells you your phone is rooted, just to keep you safe. Try to relock your bootloader, this should solve the problem. (I didn't do it yet, but I'll post the update when I've done it.)
Click to expand...
Click to collapse
It was pretty straight forward, unroot by uninstalling Magisk. adb into the bootloader and send the adb bootloader lock command, then boom, its locked. It wipes your phone in doing so, so you will have to everything again.

Lynxy0 said:
It was pretty straight forward, unroot by uninstalling Magisk. adb into the bootloader and send the adb bootloader lock command, then boom, its locked. It wipes your phone in doing so, so you will have to everything again.
Click to expand...
Click to collapse
Thanks @Lynxy0
So, just to clarify, after relocking the bootloader (which causes a full wipe) Google Pay works again?
Also, do you know if Netflix installs after relocking the bootloader? (Because in most phones once the bootloader is unlocked the status changes from "L1" and doesn't change back again after locking. Netflix reads that status, and Netflix will only install if it is L1.)
Many thanks

Hi Guys
It seems like a straight forward process, It was all good until I try flash it. . When I loaded the downloaded zip file, I couldn't get the payload file in fastbootd and flash it those buttons are missing(after I load it to payloadDumper .) . I thought it might be file download has some issue. I tried different ones , the same thing.
any ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
C.

never mind , I figured it out . My case is the ADB driver problem , even u unlocked the bootloader , somehow the fastbootenhance wont work correctly , strange , ... but.
C

@Loba74 I think there is an error in your guide, in step 11 maybe it should say "fastboot flashing unlock" rather than "adb flashing unlock" ?