Database Develop

P10 lite bootloader unlock (June 2020, Windows install)

Damn, it's been a while since I was here. Back then it was mostly about Windows PDAs.
Disclaimer:
Your warranty after this process is void and your phone will tell you it can not be trusted because it's unlocked.
This is what worked for me. I did it on Windows 10. I just went through the process and it was a bit of mixing and matching various guides.
I'm not your tech support, the only one responsible for following this is you.
If any part of this guide doesn't work for you: too bad. Maybe Google or other users can help you with your problem.
Needed:
An internet-enabled PC
Huawei P10 Lite phone
USB to Micro-USB cable
HiSuite https://consumer.huawei.com/en/support/hisuite/
DC-Unlocker (comes with abd & fastboot) https://www.dc-unlocker.com/
Optional: Huawei Driver Tools https://mega.nz/file/qrpBUIKA#zaI8Th0ovgyK48VzFUFAzMNWF2r_R12lNc-uJZsIx4w
Note: I recommend not to buy credits until you've come to the part in my guide which says buy credits.
Install HiSuite
Unzip and install HiSuite on your PC
Start it at the end of the installation (it should show a button with "Start")
Connect the phone to your computer with the USB cable and follow the instructions in HiSuite to install HiSuite on your phone
At the bottom of the (Windows) HiSuite there's an option to do a System Upgrade, mine had the option to install an older version (Android 7 with EMUI 5.1) Install this. (This will take some time)
Note: I've read that some people couldn't downgrade because of modern security fixes. It's possible I didn't run the latest updates, but as far as I'm aware everything was up to date.
The following part might be annoying because HiSuite tries to connect to the phone. I uninstalled it at this point, but I had the Driver Tools installed (and did the Install within said tools).
Phone
Once the phone restarted, go through the set-up as quickly as possible (skip WiFi-setup, decline all optional things and skip account creation)
Go to Settings > System > About Phone > Keep tapping the "Build Number" until you're told you're a developer
Find the developer options (Usually in Settings > System and enable USB/ADB debugging
Open the telephone app and type: *#*#2846579#*#* (it should open a menu automatically after the last *)
Click Background Settings > USB Port Settings and select Manufacture Mode
Once Manufacture Mode is selected, leave the phone untouched
DC-Unlocker, part 1
Unzip the contents of the DC-unlocker zip
Start dc-unlocker2client.exe
In the top left, under "Select manufacturer" change "Huawei modems" to "Huawei phones"
Click the button with the magnifying glass, if you did the previous step hovering should say "Detect phone" on hover
Example out put (this might differ for you, but triple-check a port is detected):
Code:
DC - Unlocker 2 Client 1.00.1431
Detecting phone :
selection :
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM3
Model : Huawei HiSilicon Kirin Android phone
Serial NR. : [redacted]
Firmware : System 5.1.0.78(0VVV)
DC-Unlocker, part 2
Check again if a model and port is shown in both the output and above the big buttons.
In the top right, click About > Buy Credits
DC-Unlocker site
Select your payment processor
By default it creates a new account, unless you've used this service before, you probably want to keep it this way.
Fill in a username and an email address
You need 4 credits (€4 for me) at the time of writing this, but do check the link "How much do I need?"
Hit confirm and go through the payment process, wait until everything is processed (if you use a script blocker, you might want to temporarily disable it).
At the end you should get confirmation page with your username, a password and 4 credits. (Username and password will be mailed too.)
DC-Unlocker, part 3
Go back to DC-Unlocker
In the top right, click "Server" and enter the details you've gotten
Click "Check login" and see if the output window shows your username and the credits you have left (which should be 4 at the time of writing)
In the top right, click "Unlocking" and then click "Read bootloader code"
The output should show you the bootloader code once it's done. Copy this to a textfile and save it (and keep it in the memory).
You can close DC unlocker once you've saved the code.
Don't be lazy and try to copy/paste the commands following in the next section, since you want to keep the code in your memory, as seen in step 6. Besides, I'll show you some shortcuts anyway! Keep in mind that our example code is 1111222233334444 (yours most likely isn't, mine sure wasn't) and that [tab] will mean the tab-key on your keyboard.
PowerShell/Command Prompt
In the folder where you unzipped dc-unlocker2client.exe to, press [shift] on your keyboard and hold it while right-clicking in an empty area underneath the files, then click "Open PowerShell (or command prompt) here".
Whatever command-line you started will open, type ad[tab] and adb.exe should be appear (shows up as .\adb.exe in PowerShell)
Follow this by typing reboot bootloader. So it should show as
Code:
./adb.exe reboot bootloader
(no ./ in command prompt)
Hit [enter] and the phone should reboot to a screen with a white background
Once the bootloader screen shows (white background with the android mascot) type fast[tab] in PowerShell/Command prompt and follow it up by oem unlock[space]
If you still have the bootloader code in memory, right-click in PowerShell/Command prompt to paste it. Your entire line should be
Code:
./fastboot.exe oem unlock 1111222233334444
Hit [enter], the unlocking will start and factory reset your phone. My output was:
Code:
(bootloader) The device will reboot and do factory reset...
OKAY [ 10.330s]
If everything went right you'll see the Huawei/Android bootscreen and then a warning that the phone is "unlocked and can not be trusted" to use or something like that. It'll boot into the OS after that.
I'd like to remind you of the disclaimers at the top, but hopefully this will help some of you going through the process.
Edits
Forgot about USB debugging
Added the warning you get after a successful unlock
Changed the build number tapping sentence
Rewrote a sentence for clarity

Very nice guide, if ppl ask about unlocking we just link this from now on...

This is a very helpful guide, thank you so much! My question is, if I wanted to flash twrp when the bootloader is unlocked, is there a way to upgrade it to Oreo once again without locking the bootloader again? I can't seem to find a twrp tutorial where they use Nougat/Emui 5 to flash twrp, and all the tutorials to upgrade to Oreo/Emui 8 look like they're locking the bootloader once again and I don't really want to waste 4 euros to go back to the start.

A bootloader unlock should be permanent? I've been moving between Android 7 (EMUI 5), Android 8 (Emui 8) and Android 10 myself in all kinds of directions.
Besides, I think the code is tied to your device, so you should be able to use it again. (But I'm not sure about this!)

Syrion said:
A bootloader unlock should be permanent? I've been moving between Android 7 (EMUI 5), Android 8 (Emui 8) and Android 10 myself in all kinds of directions.
Besides, I think the code is tied to your device, so you should be able to use it again. (But I'm not sure about this!)
Click to expand...
Click to collapse
Thank you for your quick reply! So after the bootloader unlock, did you flash twrp on Android 7? or did you upgrade your phone to Android 8 and flash twrp then? How did you manage to upgrade it to Android 8?
I really appreciate your help with the previous tutorial, I've done everything until the buy credits part (I'm waiting a bit for that part) and I'm planning on getting to the end of the tutorial at least before August. My idea is to upgrade to Android 8 + flash twrp and Magisk, hopefully I'll be able to do all of that!

I did the above procedure on an up to date, official stock Huawei android. Both EMUI & Android are 8. I'm in the Netherlands, so it'should be the same model as in Spain. (WAS-LX1A)
The HiSuite step is to downgrade from EMUI 8 (Android 8) to EMUI 5 (Android 7), since that seems to have less securities to make it easier to unlock the bootloader.

Oh, I understand now! One more question (sorry if I'm being annoying, it's my first time playing with a Huawei, I must say that Samsungs are far easier to root/unlock lol): If I follow your method, but after getting the bootloader unlock code and right before unlocking the bootloader, I use HiSuite to upgrade back to Android 8/Emui 8, would the procedure be fine? like, it's totally fine to unlock the bootloader either with android 7 or 8, the only time I need android 7 is to get my code because DC unlocker supports them better, right?
Again, thank you so much!!!

I'm not sure to be honest. But I reverted to 7/EMUI 5 because I read around here on the board that's better for trying to unlock.

Thank you,
Only fastboot.exe oem unlock xxxxx failed with the following error: FAILED (remote: Command not allowed)
finished. total time: 0.022s
This was resolved by going back to settings, developer options and check 'enable oem unlocking'. I didn't read that in your guide.

Syrion said:
I did the above procedure on an up to date, official stock Huawei android. Both EMUI & Android are 8. I'm in the Netherlands, so it'should be the same model as in Spain. (WAS-LX1A)
The HiSuite step is to downgrade from EMUI 8 (Android 8) to EMUI 5 (Android 7), since that seems to have less securities to make it easier to unlock the bootloader.
Click to expand...
Click to collapse
Hi, I have the same model. But I can't figure out how to update to EMUI8 again (or which custom recovery works). It doesn't find the update in HiSuite and it doesn't find it via System update. Do you happen to know how? Thank you.

What should I do next?
I did manage to unlock the bootloader thanks to this very clear post. I did downgrade to Android 7 / Emui 5.1.1 and have a working rooted system but he is trying to upgrade again to android 8 / Emui 8. I know by experience that it will lock again with the higher version (the unlock code can be used several time fortunately).
I did try to flash some roms on it, going for instance to Lineage OS 14 but it was all a disaster and I think that I need some guidance now..
I am not a newbee for rooting and flashing but do not understand yet the Huawei system; is that so that I have to choose a new ROM with caution, especially with the Emui version? Looking at the old posts, I find some old ROM's even with Emui 5 version but do not understand the path that I should follow to progressively upgrade.
Thanks in advance for your orientations!

Syrion said:
A bootloader unlock should be permanent? I've been moving between Android 7 (EMUI 5), Android 8 (Emui 8) and Android 10 myself in all kinds of directions.
Besides, I think the code is tied to your device, so you should be able to use it again. (But I'm not sure about this!)
Click to expand...
Click to collapse
For me, I did get to relock by accident but I confirm that the unlock code is permanent (at least, I did use it 3 times with no problem!)

P10 lite Pinout
I would like to know if they have tried to unlock the bootloader with the Pinout method.

Correcaminos604 said:
I did manage to unlock the bootloader thanks to this very clear post. I did downgrade to Android 7 / Emui 5.1.1 and have a working rooted system but he is trying to upgrade again to android 8 / Emui 8. I know by experience that it will lock again with the higher version (the unlock code can be used several time fortunately).
I did try to flash some roms on it, going for instance to Lineage OS 14 but it was all a disaster and I think that I need some guidance now..
I am not a newbee for rooting and flashing but do not understand yet the Huawei system; is that so that I have to choose a new ROM with caution, especially with the Emui version? Looking at the old posts, I find some old ROM's even with Emui 5 version but do not understand the path that I should follow to progressively upgrade.
Thanks in advance for your orientations!
Click to expand...
Click to collapse
I ran into the same problem. Did you find a solution?
I followed this guide, downgraded to EMUI 5.1.1 and tried to install several custom ROMs. But none of them will boot. It is always stuck on the splash screen with the "bootloader unlocked" warning and doesn't get any further.
I tried installing LineageOS 17.1, 15.1, and RR on Android 9 but no luck on any of these. Also, is it possible to revert back to the stock ROM? Maybe that will help...
Thank you all for any help

Nothing unfortunately, I did finally reinstall Android 7 with HWOTA https://www.******.com/huawei-hwota-tool-for-huawei-devices/ and managed to have a working Android 7 / Emui 5 that works perfectly if you do not forget to make a complete wipe/reset when rebooting. The bootloader is still unlocked.
Strange enough this system is upgradable through the normal update system (parameter/system/update) and keeps the unlocked bootloader. Today, I did upgrade to a very last built today - 394(C432) - without problem. Apparently I just have to re-root it through trwp.
I keep it like this now, finally, the Huawei system is not bad! and it is yet rooted
be-rty said:
I ran into the same problem. Did you find a solution?
I followed this guide, downgraded to EMUI 5.1.1 and tried to install several custom ROMs. But none of them will boot. It is always stuck on the splash screen with the "bootloader unlocked" warning and doesn't get any further.
I tried installing LineageOS 17.1, 15.1, and RR on Android 9 but no luck on any of these. Also, is it possible to revert back to the stock ROM? Maybe that will help...
Thank you all for any help
Click to expand...
Click to collapse

Correcaminos604 said:
Nothing unfortunately, I did finally reinstall Android 7 with HWOTA https://www.******.com/huawei-hwota-tool-for-huawei-devices/ and managed to have a working Android 7 / Emui 5 that works perfectly if you do not forget to make a complete wipe/reset when rebooting. The bootloader is still unlocked.
Strange enough this system is upgradable through the normal update system (parameter/system/update) and keeps the unlocked bootloader. Today, I did upgrade to a very last built today - 394(C432) - without problem. Apparently I just have to re-root it through trwp.
I keep it like this now, finally, the Huawei system is not bad! and it is yet rooted
Click to expand...
Click to collapse
Is 394(C432) finally coming as OTA? Back in July I had to download it via firmware finder and flash it with HWOTA after unlocking the bootloader... lol just to relock after updating... However even Huawei support didn't know about 394 and denied it would even exist, not too surprising in hindsight! Still eversince I was wondering if it ever comes as simple OTA, which indeed seems the case eventually!
Sent from my Google Pixel 3 XL using XDA Labs

Yes, WASLX1A 8.0.0.0394(C432) did arrive as OTA around the end of October. I was surprised as I did not expect any new update on this phone!
Sam Nakamura said:
Is 394(C432) finally coming as OTA? Back in July I had to download it via firmware finder and flash it with HWOTA after unlocking the bootloader... lol just to relock after updating... However even Huawei support didn't know about 394 and denied it would even exist, not too surprising in hindsight! Still eversince I was wondering if it ever comes as simple OTA, which indeed seems the case eventually!
Sent from my Google Pixel 3 XL using XDA Labs
Click to expand...
Click to collapse

DC-Unlocker can't find my phone
I followed your instructions, but when I click the magnifying glass on DC-unlocker it says
===================================================================
DC - Unlocker 2 Client 1.00.1431
Detecting phone :
selection :
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM6
===================================================================
But then nothing else is listed .....
My model is WAS-LX1

Correcaminos604 said:
Yes, WASLX1A 8.0.0.0394(C432) did arrive as OTA around the end of October. I was surprised as I did not expect any new update on this phone!
Click to expand...
Click to collapse
Yeah, it's actually crazy cool that it was patched after all this years, I however read it was primary updated to support the coronavirus warning App framework! That's actually the reason for Huawei to push another last update!
Sounds like a crazy conspiracy theory but was written on their Homepage...
Sent from my Google Pixel 3 XL using XDA Labs

Downgrade option doesn't exist for me in Hisuite. My phone is WAS-LX2 8.0.0.370(C185). The last update I got was on 13 February 2019 with the 2019 Feb security patches. Is there a free way to unlock bootloader?

Unlocking Bootloader on Samsung Galaxy S10 SM-G973F

So basically my problem boils down to this: I own a S10 myself and rooted it no problem using patched AP procedure for system-as-root only A devices.
i followed topjohnwus git step by step and everything worked out fine for me so i told a friend to also buy a s10 as i have a working root stratatgy for it.
On my s10 unlocking Bootloader was the following. 1. Enable OEM Unlock as usual 2. go to Downloadmode and vol. Up hold to finalize unlock and wipe phone data 3. go to developer settings again and tap OEM Unlock again for it to grey out and unlock the bootloader indefinetly.
But on this S10 from my Friend I unlocked OEM and went to DL Mode to do the rest. But this time it only showed me the usual screen, no option to vol up longpress.
So question is: Can i now simply overlook this and flash patched AP as i used to or are there any problems i need to keep in mind. Its pretty important to know beforehands as my mate just spent 500 Bucks on this Phone cause i ensured him i will be able to get him magsik no problem.
Thanks in advance
EDIT: Issue solved, check 2 threads above for solution

.

B1itzy said:
Hello, I see that you are rooting your device and I am trying to do the same thing.
I am unable to find the OEM Unlocking in my Developer Options.
Click to expand...
Click to collapse
Do you have an active sim with internet in your phone? Also is your phone a exynos version?

Late to the S10 party. I've got a Samsung Galaxy S10 with the Exynos chip (which I got deliberately for rooting and such). But my model # is S10 SM-G973U1, which is not mentioned in this or similar threads. Will my S10 w/Exynos need separate instructions and software or will anything written for the S10 SM-G973F also work for myS10 SM-G973U1?

LewdBoiDex100 said:
So basically my problem boils down to this: I own a S10 myself and rooted it no problem using patched AP procedure for system-as-root only A devices.
i followed topjohnwus git step by step and everything worked out fine for me so i told a friend to also buy a s10 as i have a working root stratatgy for it.
On my s10 unlocking Bootloader was the following. 1. Enable OEM Unlock as usual 2. go to Downloadmode and vol. Up hold to finalize unlock and wipe phone data 3. go to developer settings again and tap OEM Unlock again for it to grey out and unlock the bootloader indefinetly.
But on this S10 from my Friend I unlocked OEM and went to DL Mode to do the rest. But this time it only showed me the usual screen, no option to vol up longpress.
So question is: Can i now simply overlook this and flash patched AP as i used to or are there any problems i need to keep in mind. Its pretty important to know beforehands as my mate just spent 500 Bucks on this Phone cause i ensured him i will be able to get him magsik no problem.
Thanks in advance
EDIT: Issue solved, check 2 threads above for solution
Click to expand...
Click to collapse
could u send me the threads ?

I think the same method would work.

Hello, as mentioned message #5 download mode long press on volume+.
When you are on a mutual aid forum, the politeness of saying hello before asking for help would be welcome.
Thanks

Samsung: worst ever for a power user!

Today I got up real pissed with Samsung for being so restrictive around ROM flashing, rooting, flashing custom firmware or even stock firmware, so wanted to create this post to help anybody considering to get a Samsung phone to stay away from it.
This post is not intended to recommend any specific brand or model of android phone, but to recommend the exact opposite, which brand and model NOT TO EVEN THINK of purchasing.
This post relates to Samsung Galaxy S9 G9600 model which is Snapdragon architecture, but since Samsung is coming up with a bunch of "security features" I tend to think this may be the case for other models as well. I browsed all around XDA and other sources for guides on how to root and install custom roms, and it turns out Samsung manages to have limitations for EVERY step of the way.
Getting a few facts straight
Reference post: https://forum.xda-developers.com/ga.../rom-lineageos-17-1-s9-s9-snapdragon-t4093301
Ok, so there is a solid thread about a custom firmware and looks like several users got hands on it, but they might have been able to get passed though all Samsung security crap before it came out or before it got so tightened up. I'll list below every limitation I found:
OEM Unlock
There is a step where we need to tick OEM Unlock from the phone developer settings, it turns out Samsung has put a 7-day timer for this option to even appear listed to enable. If you do factory reset of the phone, the 7-day timer restarts. There are a few posts around on how to get passed this timer, but to me they were all crap, none of them worked. STRIKE ONE!
Bootloader unlock
After 7-days, we get the OEM Unlock option to appear, at this point you may think: Hurray!! .... WRONG! Now next step is to unlock the bootloader using an utility called CROM Services... And as you may have already guessed, did not work! I'm able to install the apk, but on launch it complains about wrong android version. (Tried with Android 8 and 10) STRIKE TWO!
There are some posts and guides claiming to be able to unlock bootloader by using fastboot utility, I can't reach to understand how, since fastboot commands rely on the bootloader to be previously unlocked (?). I least that is my understanding, correct me if wrong. Needless to say fastboot did not work for me. ADB lists my device but fastboot doesn't. There are a few troubleshoot guides around to try selecting proper USB driver from windows device manager, tried all that, tried a couple of ADB installations, fastboot didn't work.
Knox and RMM state
After some lookup in the web, Samsung incorporates some security features trying to prevent device theft and such things. For us power users this is in reality just a whole load of crap preventing us to get all the juice out of our phones.
Reference: https://www.goandroid.co.in/unlock-bootloader-of-galaxy-s9-plus-snapdragon/84688/
TWRP Recovery
Next step would be to flash a custom recovery such as TWRP with Odin or adb/fastboot, but since we are not able to unlock the bootloader in previous step, this is not doable at all. STRIKE THREE! OUT!
Fastboot utility doesn't recognize the device in download mode, so we can't send any commands to the phone.
Odin complains it is only able to flash signed stock roms, so since TWRP is not, we cannot flash it.
Rooting
Needless to say that if we don't have TWRP, we cannot flash the corresponding packages to root. Although this step may not be needed to install custom firmware, rooting has not been possible.
Stock ROM Flashing
Ok, so let's stay out of custom firmware - let's play around with stock firmwares. At this point, since flashing stock firmwares is kind of allowed by Samsung I was able to try out a couple from android 8 to 10 with Odin
Stock ROM Source: https://www.sammobile.com/samsung/galaxy-s9/firmware/#SM-G9600
But watch out! Once you get to install a specific build version, you cannot go back or downgrade to ROMS with previous Android build version. So now that I got Android 10 cannot go back to 8 or 9, this is probably because locked bootloader and unable to unlock. Here, Odin complains with FAIL! (AUTH) message.
STRIKE FOUR! EVEN OUTTER!
SIM Unlock
Ok, let's stay out of Samsung S9 G9600 model, let's crash it to the wall and throw it away to the garbage! Ok no, let's have it carrier unlocked and sell. Unlockbase is a well known and trusted sim unlock provider, I purchased a license to unlock by USB cable, but... GUESS WHAT! G9600 is not supported for unlocking operator network with this software... what a surprise!! I was able to apply for a refund and got my money back, so no worries here.
Note that flashing carrier free ROM does not unlock sim to use with any network operator.
I'll be trying to unlocking by code soon, as this is based on IMEI number, I may think this is independent to the phone model and edition, so I hope I have more luck with this option.
Conclusion
G9600 is a really crappy phone to mess around with. I may have ran low on luck with this specific Samsung Galaxy model since I got it as a gift, which is the latinamerican crappy edition. I wonder if other S9 editions and other Samsung models run with better luck than mine on this scenery... But as a lesson to myself, I will stay away of any Samsung smartphone in the foreseeable future.

OEM Unlock
The 7-day lock prevents stolen phones from being factory reset, leaving the thief with a phone permanently protected by your account. While a minor inconvenience, it's actually effective and not the worst compared to other manufacturers.
Bootloader Unlock
After OEM Unlocking, flashing TWRP through ODIN is effectively unlocking the bootloader. This is possible on both exynos and snap.
Knox and RMM
While this is an inconvenience, from Samsung's point of view, it's worth it. It makes the phone look more secure in the eyes of potential customers. If you really wish for NFC payments, I'm still able to use GPay with Magisk on a custom ROM.
TWRP Recovery
TWRP is flashed through ODIN, not fastboot. Look up an actual guide before complaining.
Root
Yes you can
Stock ROM Flashing
The one thing I could agree on with you is Samsung disabling OTA updates when OEM unlocking. I don't see the point really, but you're free to flash whatever you want through ODIN. Downgrading shouldn't be an issue. Not sure what's up with that.
Before buying a phone, how about you do some research before crying on forums. As a power user coming from the Oneplus One, I don't regret going for Samsung in the least.

Thanks for your reply, I had dropped all hope after several attempts over last few weeks. Found this option and I was able to get past my blocking issue with TWRP and moved on.
https://forum.xda-developers.com/ga...er-development/g9650zhu6dta7-android-t4051751

I have G960F and have to admit I totally disagree with your original post. I've been using custom ROMs on nearly every phone I ever had and don't think S9 (G960F) is bad in terms of unlocking. Just did an OEM unlock, waited a week, flashed TWRP through Odin, booted straight to TWRP and immediately flashed a custom ROM from it (because a boot to the stock ROM would replace TWRP back with the stock recovery IIRC). In the end I got sick of all the problems with Magisk and non-working google pay that I went back to the stock ROM - making S9 the first phone I use with a stock ROM even though it can be flashed. I think it's a great phone for power users.
And as far as SIM unlock goes - Samsung is not to blame, the carrier the phone was made for (and purchased from) is. Phones that Samsung itself sells are unlocked. I wonder why there's still some countries where SIM locking remains legal.

This thread is a prime example of how people end up with bricked devices. So much misinformation in one page LOL

I had the 9650 and most of what I'm doing here is user error. This was one of the best devices I've ever owned. I mention of fast boot and such you obviously just do not know samsung devices. You can't blame samsung on your own ignorance

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.

Find X5 Lite: fastbootd/OEM unlock problems

Hello!
First of all: I know I am asking about the Lite, not the Pro - but there was no dedicated device listing for it, so I went for the next best thing I could find. I apologize in advance.
I have a highly visually impaired friend for whom reading a lot of text is very taxing. I, too, am visually impaired, but I practically live in a terminal - it's totally fine for me. However, we live all across the country (Germany). Basically, he lives in Berlin and I in Frankfurt. Thats a long way apart. So, the best I can help him with is by logging in via Parsec; hence, I have to ask him to do any hardware-related handling.
The TL;DR is: His device defaults to fastbootD, refuses both "flashing unlock" and "oem unlock" after toggling it in Developer options. Variations of adb/fastboot "reboot bootloader/recovery" all did not result in full fastboot. We were trying to extract the boot image to use with Magisk.
The long story: Late last year, he bought the phone off eBay once he heared that Oppo phones were no longer allowed to be sold in stores here in Germany and wanted to root it to see what he could do with it. Since it is a MediaTek device, I told him that hopes for a LineageOS port would be slim, considering MediaTek's history with OSS. So first we went on a hunt for the stock ROM to just grab the boot image off there. No luck; the only seemingly viable listing - a Google Drive link - has become completely unavailable (traffic limit reached). So the next best thought was to grab it off the device itself.
So I went to his maschine via Parsec and set up adb and fastboot and configured the proper Fastboot driver (the official Google one) and made sure the device was recognized as an Android Bootloader Device. Fastboot could also list it, so I was all set up. From there I made a dump of "get-var all" and sure enough, "unlock" was "no". So I sent his phone to reboot and him on his merry way to head into the Developer options and find OEM Unlock. And, it is indeed there. Once he enabled that, I attempted to unlock that bootloader. But I always get errors that the HAL can not be loaded or that the command would not be found. And, whilst researching more, I learned that fastboot can also load in userspace as fastbootd. Sure enough, I had him send me a photo of what the bootloader looked like, and in big bold letters it does indeed read "FASTBOOTD".
After looking up several guides and information, I have not managed to get anywhere at all untill I found this post: https://forum.xda-developers.com/t/...access-for-oppo-phones-starting-2016.3348114/
I could not find any verification that his phone is also affected, meaning that he might have a "castrated" bootloader alltogether - or fastboot, at least.
The model identifies itself as: CPH2371
If you have any possible ideas, please do let me know. Personally, I am at the end of my ideas. Rooting, and sub-sequently installing LineageOS, was astoutly simpler on my Razer Phone 2.
Thank you very much in advance - and, again, apologies for posting in the wrong thread, a proper X5 Lite one was nowhere to be seen.
Kind regards,
Ingwie
PS: The "vars.txt" attached was pre-OEM unlock setting.

any news? root possible?

I've forgot me pattern lock, when I tried to enter in recovery mode, my phone keep restarting again & Again what should I do, I need to reset my pattern, GMAIL ID method also not working....