Related
Hi everyone,
I would like to root my device but i need the drivers, i search and install what i find on the web and sony website but every time when my divice is in fastboot mode it not recognize by windows.
I think this thread can be usefull for many persons so i open it.
Mobile : Sony XZ1 Compact
This is a screenshot of my device when i plug it in fastboot mode :
{
"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"
}
Thanks you :good:
Braindeadz said:
Hi everyone,
I would like to root my device but i need the drivers, i search and install what i find on the web and sony website but every time when my divice is in fastboot mode it not recognize by windows.
I think this thread can be usefull for many persons so i open it.
Mobile : Sony XZ1 Compact
This is a screenshot of my device when i plug it in fastboot mode :
Thanks you :good:
Click to expand...
Click to collapse
If you're stuggling to find the ADB drivers for your phone, I'm not sure that you should be trying to root your phone, no offence.
Rooting it will break the camera completely. There is a DRM fix, which does leave all the functions of the camera working. But I wouldn't go down that route personally. The 'fix' was actually stolen from another developer and released without permission. The Dev who's running the drm fix thread didn't build the fix and has no idea how it works. Read for yourself, support is very patchy, it's a difficult thing to get right. You need to apply the right patches in the right sequence on top of a 8.49 CE firmware build, or it wont work.
It's a fix not a workaround, you destroy your TA keys buy unlocking your phone and you will never get them back.
Also you're dependent on the Dev (sToRm//) compiling a new fix to go with any new firmware released.
You could never update again without his help, and right now, he's got the hump.
Didgesteve said:
If you're stuggling to find the ADB drivers for your phone, I'm not sure that you should be trying to root your phone, no offence.
Rooting it will break the camera completely. There is a DRM fix, which does leave all the functions of the camera working. But I wouldn't go down that route personally. The 'fix' was actually stolen from another developer and released without permission. The Dev who's running the drm fix thread didn't build the fix and has no idea how it works. Read for yourself, support is very patchy, it's a difficult thing to get right. You need to apply the right patches in the right sequence on top of a 8.49 CE firmware build, or it wont work.
It's a fix not a workaround, you destroy your TA keys buy unlocking your phone and you will never get them back.
Also you're dependent on the Dev (sToRm//) compiling a new fix to go with any new firmware released.
You could never update again without his help, and right now, he's got the hump.
Click to expand...
Click to collapse
Thanks you for you help, i think you are right but it's very difficult to tell me i don't "root" my phone because every smartphone i have in my life was root. I buy a Sony phone for the first time and maybe the last because it's what i like with Android, Root, change ROM, again and again. Maybe Modpunk release a stable LineageOS ?
I buy this phone because it is small, very small, snap 835, sd card, speakers on the front and fingerprint on the right but i hope Oneplus make a little phone like this a day
I feel like I'm in prison
Braindeadz said:
Thanks you for you help, i think you are right but it's very difficult to tell me i don't "root" my phone because every smartphone i have in my life was root. I buy a Sony phone for the first time and maybe the last because it's what i like with Android, Root, change ROM, again and again. Maybe Modpunk release a stable LineageOS ?
I buy this phone because it is small, very small, snap 835, sd card, speakers on the front and fingerprint on the right but i hope Oneplus make a little phone like this a day
I feel like I'm in prison
Click to expand...
Click to collapse
I know, every phone I've ever owned I rooted, it's almost a habit, but with this bootloader Sony is giving us the finger. The main reasons I wanted to root were usually to get a better battery and to mod the framework to make it look better, but the battery with this phone is already good, it doesn't need any help.
If you want to mod the looks then it's possible to do that too.
I don't want to be negative and put you off trying to do amazing things with your phone, but I thought you should know the details before you start.
Edit: yes, I think LineageOS is very close now, perhaps when that is working I might move to that.
Didgesteve said:
I know, every phone I've ever owned I rooted, it's almost a habit, but with this bootloader Sony is giving us the finger. The main reasons I wanted to root were usually to get a better battery and to mod the framework to make it look better, but the battery with this phone is already good, it doesn't need any help.
If you want to mod the looks then it's possible to do that too.
I don't want to be negative and put you off trying to do amazing things with your phone, but I thought you should know the details before you start.
Edit: yes, I think LineageOS is very close now, perhaps when that is working I might move to that.
Click to expand...
Click to collapse
Thanks for your tips, I'm waiting for LineageOs now, it seems like a better idea.
Thanks you Didgesteve
Braindeadz said:
Hi everyone,
I would like to root my device but i need the drivers, i search and install what i find on the web and sony website but every time when my divice is in fastboot mode it not recognize by windows.
I think this thread can be usefull for many persons so i open it.
Mobile : Sony XZ1 Compact
This is a screenshot of my device when i plug it in fastboot mode :
Thanks you :good:
Click to expand...
Click to collapse
I ran into a similar issue when trying to use Emma. It only runs on Windows, so I had to go through this as well.
First, download and install Android Studio for your OS:
developer . android .com/studio/ index. html
(Note: Android Studio is not required, just the SDK. But Android Studio will install the SDK for you in a standard location. This might make things easier for you.)
Once this is done, launch it to install the SDK. You can select all defaults.
Once the SDK is installed, click Configure in the bottom-right of Android Studio and select SDK Manager. On the first screen, select the SDK Tools tab in the middle. Here you will want to select Google USB Driver and click Apply. This should install the driver.
Then, go back to the device in the device manager and right-click the device and select Update Driver.
After that, I followed the steps here:
stackoverflow . com /questions/14559734/ install-adb-interface-driver-for-android
to get the driver installed. This was because I kept getting an error that the system could not find the Android ADB Interface.
For the record, the Google USB Driver was installed on a Windows 10 box in the following location:
%localappdata%\Android\Sdk\extras\google\usb_driver
Hope this helps you out..
crummmcakes said:
I ran into a similar issue when trying to use Emma. It only runs on Windows, so I had to go through this as well.
First, download and install Android Studio for your OS:
developer . android .com/studio/ index. html
(Note: Android Studio is not required, just the SDK. But Android Studio will install the SDK for you in a standard location. This might make things easier for you.)
Once this is done, launch it to install the SDK. You can select all defaults.
Once the SDK is installed, click Configure in the bottom-right of Android Studio and select SDK Manager. On the first screen, select the SDK Tools tab in the middle. Here you will want to select Google USB Driver and click Apply. This should install the driver.
Then, go back to the device in the device manager and right-click the device and select Update Driver.
After that, I followed the steps here:
stackoverflow . com /questions/14559734/ install-adb-interface-driver-for-android
to get the driver installed. This was because I kept getting an error that the system could not find the Android ADB Interface.
For the record, the Google USB Driver was installed on a Windows 10 box in the following location:
%localappdata%\Android\Sdk\extras\google\usb_driver
Hope this helps you out..
Click to expand...
Click to collapse
Unfortunately, these drivers do not contain the correct drivers. I do not have any idea, I've been desperate.
hage_JK said:
Unfortunately, these drivers do not contain the correct drivers. I do not have any idea, I've been desperate.
Click to expand...
Click to collapse
What do you mean by "these drivers do not contain the correct drivers"? Did they fail to install for you?
I just spun up a new Windows 7 VM to test this out again, and it worked for me.
What steps are you taking exactly?
Did you receive any errors when you tried to install the driver this way?
How is your device appearing in the device manager?
crummmcakes said:
What do you mean by "these drivers do not contain the correct drivers"? Did they fail to install for you?
I just spun up a new Windows 7 VM to test this out again, and it worked for me.
What steps are you taking exactly?
Did you receive any errors when you tried to install the driver this way?
How is your device appearing in the device manager?
Click to expand...
Click to collapse
The device in fastboot will appear in the device manager as Android as the first stick.
Drivers dowload from Sony developed or Android SDK reports not found driver.
Drivers from Sony or Google they work in USB debugging but not driver in fastboot, still reports Android without drivers.
Testing on Windows 10 x64 and Windows 7 x32
Thank you in advance for any ideas
Hi, is there a solution to this? I am also looking for the fastboot driver. I have no issue with ADB driver... its just fastboot. My Z5 with fastboot is ok.... but Z1C not. Im running windows 10
Dean F said:
Hi, is there a solution to this? I am also looking for the fastboot driver. I have no issue with ADB driver... its just fastboot. My Z5 with fastboot is ok.... but Z1C not. Im running windows 10
Click to expand...
Click to collapse
Sometimes the drivers don't install properly in Windows 10, although it doesn't tell you they failed to install (helpful). You need to start Windows in safe mode and look for 'Disable driver signing'
Also, if you've used your computer for another device, then it's likely those drivers are still in it kicking about and probably getting in the way. You might have better luck going to another computer that has never been used for ADB and starting fresh.
Hi everyone,
Dunno if this is the right thread to post my question but the subject is Fastboot so I am trying my luck. Want to unlock the bootloader of my phone via Sony website... step 1 and 2 are no problem and I have my unlock code. Unfortunately I can't get my phone into FASTBOOT mode. Connected cable to laptop, hold volume button up and connected phone to cable but nothing happens. Is there anyone that can help me out?
thnx!
van_vugt said:
Hi everyone,
Dunno if this is the right thread to post my question but the subject is Fastboot so I am trying my luck. Want to unlock the bootloader of my phone via Sony website... step 1 and 2 are no problem and I have my unlock code. Unfortunately I can't get my phone into FASTBOOT mode. Connected cable to laptop, hold volume button up and connected phone to cable but nothing happens. Is there anyone that can help me out?
thnx!
Click to expand...
Click to collapse
It's been mentioned before on a different thread.
Didgesteve said:
It's been mentioned before on a different thread.
Click to expand...
Click to collapse
Thnx... overlooked that thread. Will try that!
hage_JK said:
The device in fastboot will appear in the device manager as Android as the first stick.
Drivers dowload from Sony developed or Android SDK reports not found driver.
Drivers from Sony or Google they work in USB debugging but not driver in fastboot, still reports Android without drivers.
Testing on Windows 10 x64 and Windows 7 x32
Thank you in advance for any ideas
Click to expand...
Click to collapse
Did you use the standalone SDK, or did you use Android Studio?
If you used Android Studio, what do you see in: %localappdata%\Android\Sdk\extras\google\usb_driver\
If you did not use Android Studio, would you be willing to try it? I only suggest it since it installs everything to specific locations, so perhaps removing an additional variable could be useful.
Otherwise, Didgesteve's suggestion seems like a good next step.
I have the exact same problem. Sony driver and Google driver both don't work. Driver sign in Windows 10 is disabled. How can I don now?
Edit: After followed the steps showed in this video the drivers are successfully installed but when unlocking the bootloader it says "command not allowed". Do I have to unlock it if I want to root my phone?
k_basara said:
I have the exact same problem. Sony driver and Google driver both don't work. Driver sign in Windows 10 is disabled. How can I don now?
Edit: After followed the steps showed in this video the drivers are successfully installed but when unlocking the bootloader it says "command not allowed". Do I have to unlock it if I want to root my phone?
Click to expand...
Click to collapse
Yes, unlocking your phone is the first part of rooting your phone. Unlocking is a one way process, you can't ever undo it and it will break your camera, completely. Be aware of that before you continue, the threads are full of people crying about broken phones that can't be re-locked.
It might be your phone is not allowed to be unlocked. Some phone providers in the UK sell phones that cannot be unlocked, mostly because they don't want the headache of people claiming unlocked phones be repaired.
Type *#*#7378423#*#* into your phone dialer to access the service menu.
Then look under Service info/configuration.
Under Rooting Status it should say Bootlock unlock allowed - yes.
If it says no then forget it.
Edit: you also need to allow OEM unlocking in the developer options
Didgesteve said:
Yes, unlocking your phone is the first part of rooting your phone. Unlocking is a one way process, you can't ever undo it and it will break your camera, completely. Be aware of that before you continue, the threads are full of people crying about broken phones that can't be re-locked.
It might be your phone is not allowed to be unlocked. Some phone providers in the UK sell phones that cannot be unlocked, mostly because they don't want the headache of people claiming unlocked phones be repaired.
Type *#*#7378423#*#* into your phone dialer to access the service menu.
Then look under Service info/configuration.
Under Rooting Status it should say Bootlock unlock allowed - yes.
If it says no then forget it.
Edit: you also need to allow OEM unlocking in the developer options
Click to expand...
Click to collapse
Yes, I forgot to allow OEM unlock in my phone settings.
I gave up unlocking my phone anyway, compare to years ago, stock rom nowadays isn't that unacceptable after all.
Hi - after months I finally solved the fast boot issue by using the above mentioned video: https://www.youtube.com/watch?time_continue=105&v=nQjg6ePnGAc
Basically - the key is that there are 2 steps:
1. Connect phone in usb debugging mode - then install sony adb driver using device manager and "have disk"
2. Boot into fastboot - and again install sony adb driver using device manager and "have disk"
Result = fastboot now working!
today I root my XZ1C
I have lots of problems with fastboot and i have other solution
for ADB i use driver from Sony ( installed by device manager )
but for fastboot
I use "Android ADB Interface" installed with Android Studio (you can choose it device manager --> update driver --> manual install --> installed on pc --> google or on my PC it was Samsung and there was google --> Android ADB Interface )
thats was only think that work for my device
I lost today 3/4h for this one think
maybe it will help someone to safe this time
Enjoy !
I am on a quest to root my phone and i want to unlock bootloader ect... since no application can do this i need to use adb fastboot
i am using a chromebook Acer 15 developer options open all that etc...(i beileve all needed) when moto e5 plus plugged in by data usb cord and tryin to connect by adb devices command it gives me a List of devices attached
ZL522BQ46M unauthorized (did same for my lg g6 but not a galaxy or zte) also it doesnt show up in my files as a attached device or outside storage unit but about 10 mins prior to this it had shown up as attaced but kept dis connecting causing multipule file windows to apper. i hace searched it multiple times on many diffrent acasions and have tried many "fixes" please can i get some assistance.
Enabled developer options
System->About Phone-> Scroll to bottom and TAP on BUILD 5x (I believe)
then go back once , Developer options , Enable USB DEBUGGING , Authorize your Device and you should be able to proceed onto the bootloader unlocking guide on Motorola's Website
whodat711 said:
Enabled developer options
System->About Phone-> Scroll to bottom and TAP on BUILD 5x (I believe)
then go back once , Developer options , Enable USB DEBUGGING , Authorize your Device and you should be able to proceed onto the bootloader unlocking guide on Motorola's Website
Click to expand...
Click to collapse
Still not working. Re set the Chromebook even rest the phone. Did everything from the start did the Linux applications restarted the Chromebook didn't go with the Linux applications even got the ADB extensions for the Chromebook and nothing will work still says no permissions when it pulls up the phone I don't know. This isn't like I'm totally brand new to this just never used a Chromebook thanks for your help anyway
i solved the issue with the no permissions in adb. a few minor issues i should of noticed and actually taking the time to think the problem through solved it......
but i somewhere messed up when rooting my phone (shouldnt of been drinking and thought i could still do it...) and know i am in a reboot coming out of my bootloader... will not boot into my recovery whrn it dows its only for a few seconds and the command lines runnung it says that script is finishing but it quickly reboots to a black screen that says bad key and reboots then says n a on it. fastboot will not do anything but say waiting on device. so...... i guess i got a project for a few days
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.
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.
Hello Developers!
I have found an easy way to unlock the bootloader of our Huawei Nova 2 Plus. No need to use Testpoint or pay for software to unlock. it is an Python Script which would brute force the code through the IMEI number you have entered
IMPORTANT: MAKE SURE THE PHONE IS CONNECTED TO ADB OR THIS TOOL WILL NOT WORK AS IT WILL RESTART INTO FASTBOOT AND TRY ALL THE CODES IT GENERATED!!!!!!!.
THIS TOOL WORKS FOR Linux and Windows. the guide is for windows but the script would work for linux completely fine.
REQUIREMENTS
Download The Tool from the thread
Install Python From Microsoft Store Or The Python Website
Run Powershell as Admin
Run the Command:- python unlock.py
Enter Your IMEI Number
MAKE SURE YOUR PHONE IS CONNECTED TO ADB!!!!!
Wait for the code to be found
If your phone reboot into EMUI reboot back into bootloader mode and the tool will start the bootloader unlocking process
The Phone May Reboot Several Times.
If you get an warning about unlocking the bootloader you have succeeded to unlock the bootloader
Special Thanks To KASHIFALIKHAN For the tool . the download will be down below
Hello does unlocking bootloader resets my data? As in will it factory reset?
Yes it would reset your data. It happens on all phones for security reason
deleted
Hello..could you please explain more about the process and what should we do about attached file?
you have to extract the ZIP and run the unlock script and enter your imei number make sure you have python installed on your PC
TMHAKIM said:
you have to extract the ZIP and run the unlock script and enter your imei number make sure you have python installed on your PC
Click to expand...
Click to collapse
Thank you for your answer..
So ,unlocking bootloader resets my data..
My phone is nova 3i android 9 LX2..
Is this procedure safe for my phone?
Have you tried it on this model?
Hello,
I have a chinese Honor 9x (bought from alieExpress). I currently have the HarmonyOS installed that doesn't allow me to run any google-apps, so I'm trying to unlock the bootloader. Out of desperation I tried to use this program to try bruteforce the unlock code. However as I start running it (USB debug enabled and all in options), after the first reboot it arrives in fastboot mode (as I believe should be expected), but then it gives the error that no devices have been found, and therefore remains hanging at 10% / first code tried.
I have a feeling that somehow after the reboot the usb debugging/OEM mode is not on anymore and therefore the python program doesn't identify the phone. I feel this has to do with the setting "enable OEM mode" not being available in any of the settings in my phone (probably a little chinese easter egg to make all this more difficult?). I don't really know how to tackle this issue tho, any advice is appreciated.
honorable9x said:
Hello,
I have a chinese Honor 9x (bought from alieExpress). I currently have the HarmonyOS installed that doesn't allow me to run any google-apps, so I'm trying to unlock the bootloader. Out of desperation I tried to use this program to try bruteforce the unlock code. However as I start running it (USB debug enabled and all in options), after the first reboot it arrives in fastboot mode (as I believe should be expected), but then it gives the error that no devices have been found, and therefore remains hanging at 10% / first code tried.
I have a feeling that somehow after the reboot the usb debugging/OEM mode is not on anymore and therefore the python program doesn't identify the phone. I feel this has to do with the setting "enable OEM mode" not being available in any of the settings in my phone (probably a little chinese easter egg to make all this more difficult?). I don't really know how to tackle this issue tho, any advice is appreciated.
Click to expand...
Click to collapse
Have you installed Hisuite drivers? And check device manager when you boot into fastboot if it shows Android bootloader interface then you're good to go if not then try installing Hisuite drivers
honorable9x said:
Hello,
I have a chinese Honor 9x (bought from alieExpress). I currently have the HarmonyOS installed that doesn't allow me to run any google-apps, so I'm trying to unlock the bootloader. Out of desperation I tried to use this program to try bruteforce the unlock code. However as I start running it (USB debug enabled and all in options), after the first reboot it arrives in fastboot mode (as I believe should be expected), but then it gives the error that no devices have been found, and therefore remains hanging at 10% / first code tried.
I have a feeling that somehow after the reboot the usb debugging/OEM mode is not on anymore and therefore the python program doesn't identify the phone. I feel this has to do with the setting "enable OEM mode" not being available in any of the settings in my phone (probably a little chinese easter egg to make all this more difficult?). I don't really know how to tackle this issue tho, any advice is appreciated.
Click to expand...
Click to collapse
Since you could enter the bootloader when you first trying, I'm guess it might be the Harmony OS. You can try use Hisuite to roll back your HarmonyOS to EMUI, then try to unlock the bootloader. Most of modified Android OS removed the OEM mode to make you have a hard time on unlock bootloader. These will be really easy if you use some phones like Google's Pixel.
I have an old Huawei Nova 3i and it's updated into the Harmony OS, which is not what I want, I'd like to have a more cleaner OS that not with so much preinstalled apps. Then I roll back to EMUI as the first step to install other ROM, and that script it's working now. It's still trying get the password so I can't say it worked or some thing else.
And alter is that, if you just want install some google-apps, you may just roll back to EMUI, it should worked fine. And I'm not really suggest you have any phone from Huawei now since they really push their Harmony OS as a thing (at least, in China) and not really friendly towards people not in China (since lots of popular apps' depended G-apps). I'm annoyed even I'm Chinese though.