Database Develop

Bootloader Won't Unlock

Soo, trying to unlock my C6603 bootloader via adb however I'm having some problems.
- I'm getting "Failed" and then if I try a second time "Okay" (connected properly, returned version 0.5)
- Then I'm stuck in a bootloop and cannot turn my phone back on and need to wipe my data.
- Note: Bootloader Unlock Allowed: Yes
Any ideas?...

KyronTaylor said:
Soo, trying to unlock my C6603 bootloader via adb however I'm having some problems.
- I'm getting "Failed" and then if I try a second time "Okay" (connected properly, returned version 0.5)
- Then I'm stuck in a bootloop and cannot turn my phone back on and need to wipe my data.
- Note: Bootloader Unlock Allowed: Yes
Any ideas?...
Click to expand...
Click to collapse
Which operation system are you using? Did you follow the steps on the sony webpage?

4.3 Rooted (Using the steps on this forum.) I did try to unlock the bootloader previous to rooting the phone and still the same problem..
Here are screenshots of my settings and (cropped) service menu for reference.

(Sorry for double post, the app will not let me edit...)
Yes, I followed all steps on the unlockbootloader Sony webpage, exactly.

KyronTaylor said:
4.3 Rooted (Using the steps on this forum.) I did try to unlock the bootloader previous to rooting the phone and still the same problem..
Here are screenshots of my settings and (cropped) service menu for reference.
Click to expand...
Click to collapse
I meant the os on your pc, if it is Windows 8 or 8.1 you have to do some tricks. I can't remember though what tricks, you'll have to search for it

St.Jimmy90 said:
I meant the os on your pc, if it is Windows 8 or 8.1 you have to do some tricks. I can't remember though what tricks, you'll have to search for it
Click to expand...
Click to collapse
Ahh. Yes, I'm running Windows 8.1, however, I'm in Test-Mode.. No idea what other "tricks" I'd need to do..

KyronTaylor said:
Ahh. Yes, I'm running Windows 8.1, however, I'm in Test-Mode.. No idea what other "tricks" I'd need to do..
Click to expand...
Click to collapse
Are fastboot drivers correctly installed?
Btw: I meant this:
http://forum.xda-developers.com/showthread.php?t=2095087

St.Jimmy90 said:
Are fastboot drivers correctly installed?
Btw: I meant this:
http://forum.xda-developers.com/showthread.php?t=2095087
Click to expand...
Click to collapse
Already did that, drivers installed fine. /:
I also tried the Flashtool's built-in Bootloader Unlocking Tool. Exact same deal..

What a bummer...

St.Jimmy90 said:
What a bummer...
Click to expand...
Click to collapse
Alright I have no idea how I did it, but I just put my phone in flashmode and kept disconnecting the USB and reconnecting it and messed with Flashtool.. Somehow I ended up unlocking it... I'm so angry but happy right now. I wish I could provide a solution.. But I can't... I think my bootloader was just corrupt or had an error..
Anyway, now I'm running the Pac-Man Nightly 4.4 KitKat ROM . Yaaay.
I was considering learning Java and just tinkering with this.. But.. This has been so frustrating... Taken days.. Gah..

[Q&A] [Tutorial] Unlocking BootLoader

Q&A for [Tutorial] Unlocking BootLoader
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

same problem
Darkfunnyguy said:
Can you help I get waiting for device when command prompt when entering fastboot.exe -i 0x0fce getvar version.
So what the problem please?
---------- Post added at 09:48 PM ---------- Previous post was at 09:37 PM ----------
I manage to get it to work by reconnect the cable.
My Xperia V is now unlocked. :good::good::good::good:
Click to expand...
Click to collapse
I am having the same of waiting and waiting and could not work it out like u did.. can u help me out??

Install driver first

do we need a flashing tool to unlock bootloader ?
Hi ,
I am new to this unlocking boot loader. Do we need some flash tool or something to do as mentioned in the link ?
http://forum.xda-developers.com/showthread.php?t=2090268
Kindly help .
Thanks to awesome developers

Blue LED
1) The blue LED is on only for a few seconds and then it starts to charge the battery. Any ideas?
2) When I try to update the drivers it gives me the Android ADB Interface failure. Added the picture of it to the attachment.
(I did root the phone before without unlocking the bootloader, does it matter?)
Thanks

mEh91 said:
1) The blue LED is on only for a few seconds and then it starts to charge the battery. Any ideas?
2) When I try to update the drivers it gives me the Android ADB Interface failure. Added the picture of it to the attachment.
(I did root the phone before without unlocking the bootloader, does it matter?)
Thanks
Click to expand...
Click to collapse
I have the same problems​

ModiYasser said:
I have the same problems​
Click to expand...
Click to collapse
I finally fixed the problem. The reason why the blue light was on for only a few seconds is that your PC doesn't have the right drivers. To fix that you should install fastboot, it has the needed drivers, but to install them you have to put your PC into some sort ''test mode'', I lost the links where I found the right commands for this, anyways, after that it will work like a charm.

why does my computer can't detect the driver it just appearing that ANDROID ADB INTERFACE is updated i can't update my phone why?

Xperia V no 3G/4G data connection
Hi. I unlocked the bootloader of my Xperia V. The procedure was successful, but since then, I lost 3G/4G data connection. I tried restarting, removing battery, but nothing. I can only be connected through WiFi.
Any ideas of fixing it? Thank you.

Lord_69 said:
Hi. I unlocked the bootloader of my Xperia V. The procedure was successful, but since then, I lost 3G/4G data connection. I tried restarting, removing battery, but nothing. I can only be connected through WiFi.
Any ideas of fixing it? Thank you.
Click to expand...
Click to collapse
Did you made a ta back up?
Sent from my LT25i using XDA Free mobile app

harrymason37 said:
Did you made a ta back up?
Sent from my LT25i using XDA Free mobile app
Click to expand...
Click to collapse
No. I'm completely newbie. What is that and how can it be done?

Will this work on other xperia phones?? like xperia t?
edit: in the device manager, my phone is listed as "Android Device". And I can only select "update driver" on something named "ROMaster ADB Interface".

hi, noob question here.
Do you need to download the SDK which has a very large size of about 800MB to unlock the bootloader?
Im trying to install cm11

jimbait said:
hi, noob question here.
Do you need to download the SDK which has a very large size of about 800MB to unlock the bootloader?
Im trying to install cm11
Click to expand...
Click to collapse
No, just download ADB (along with the ADB drivers for your device).

Antiga Prime said:
No, just download ADB (along with the ADB drivers for your device).
Click to expand...
Click to collapse
Thanks! btw i installed mini adb. The size is less than 2mb :laugh:

Hello please help me i have a micromax aq5000 n i tried to unlock the bootloafer through xda provided minimal fastboot app from my pc but it failed how can i unlock my bootloader

[Q] Error While Disabling Secure Boot on Windows Phone ARM Processor

I got error while disabling secure boot on windows phone for arm.
Error code is C0000135
Unable to trace :/

djamol said:
I got error while disabling secure boot on windows phone for arm.
Error code is C0000135
Unable to trace :/
Click to expand...
Click to collapse
Interesting...What is it that you need exactly?

feherneoh said:
@djamol: a SecureBoot exploit just got released that supports any of the Windows UEFI devices (x86/x64/arm)
Click to expand...
Click to collapse
Yeah I know that since long days ago.

feherneoh said:
I knew about it since it was found, just couldn't get my hands on it
but question stays: how did you try to disable it?
Click to expand...
Click to collapse
I just was reversing
"EnableUEFISB.exe /disable"

feherneoh said:
I would have laughed quite lot if that actually worked
Click to expand...
Click to collapse
Lol, its should be work fine but the whole part of the code is missing.
Need to write your own one.

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.

Pixel 5 - Removal from Beta 13 - Corrupt Error

So.... I removed my Pixel 5 form the beta 13 program, selected update on the devices and had it download Android 12 a few weeks back. On reboot I get the "device is corrupt" error with visit the g.co/ABH link. If I hit the power button that error loops, and trying a hard / factory reset does nothing.
I tried several of the steps but since I cannot get into Dev mode to unlock the bootloader I'm kind of stuck.
The most I have been able to do is with the rescue tool, but that throws a "software on device is newer then this tool" error and wont go forward.
Any suggestions? Should I just send in to a repair shop? Or move on?

I heard from a friend yesterday that this happens with USB C to USB C. Try an A or B port and sideload the OTA

xunholyx said:
I heard from a friend yesterday that this happens with USB C to USB C. Try an A or B port and sideload the OTA
Click to expand...
Click to collapse
Tried both types of cables, no luck...

grmacd said:
Tried both types of cables, no luck...
Click to expand...
Click to collapse
As recommended by @xunholyx try sideloading the OTA, if you're able to get into recovery.
If you didn't have OEM unlocking enabled in Developer Options, you might be SOL.

V0latyle said:
As recommended by @xunholyx try sideloading the OTA, if you're able to get into recovery.
If you didn't have OEM unlocking enabled in Developer Options, you might be SOL.
Click to expand...
Click to collapse
Yeah since the OEM unlock was not in place before the beta downgrade was triggered and failed, I can't get into the OS to turn it on. So SOL I bet

grmacd said:
Yeah since the OEM unlock was not in place before the beta downgrade was triggered and failed, I can't get into the OS to turn it on. So SOL I bet
Click to expand...
Click to collapse
Unfortunate and I feel for you.
It's generally advisable to always unlock the bootloader when running any kind of beta software, just because of this eventuality - if something goes wrong, you need to have a way to recover the device.

grmacd said:
Yeah since the OEM unlock was not in place before the beta downgrade was triggered and failed, I can't get into the OS to turn it on. So SOL I bet
Click to expand...
Click to collapse
You should be able to boot to recovery from the bootloader

I can boot to recovery, but the software wont sideload since the boot locker is locked.
My one hope is the fact Rescue mode on the web is throwing "software on the device older then this tool" so I am hoping once that gets a newer version I will be ok. So into the drawer it goes...

But you don't need an unlocked bootloader to sideload an OTA....

xunholyx said:
But you don't need an unlocked bootloader to sideload an OTA....
Click to expand...
Click to collapse
Ok... perhaps I will give it another try tomorrow.

grmacd said:
Ok... perhaps I will give it another try tomorrow.
Click to expand...
Click to collapse
Try flashing it a second time when you get the error. A friend is mine had trouble with it and a locked bootloader as well. I don't remember how he fixed it, but I think that that was it. I'll get in touch with him later. I'm at work right now

xunholyx said:
Try flashing it a second time when you get the error. A friend is mine had trouble with it and a locked bootloader as well. I don't remember how he fixed it, but I think that that was it. I'll get in touch with him later. I'm at work right now
Click to expand...
Click to collapse
So this AM I downloaded the newest ZIP file and followed the step on the site - after about 10 minutes presto the phone is back up and running with Android 13! Thanks for your help!