Database Info

[Q] Xperia E1 locked bootloader

Good Evening,
I've tried to unlock my Xperia E1(D2005); however with no success. I've followed the steps on Sony's official website, as did I follow every step thoroughly in this video https://www.youtube.com/watch?v=iIdJg7KNH3A. Did everything he requests, checked if the bootloader was unlockable - which it was and is - by typing in the dailer this code *#*#7378423#*#*; installed android SDK and downloaded all the required tools; downloaded the fastboot driver for windows - I'm using windows 8.1 btw - and inserted it in the requested place (USB driver folder); enabled USB debugging; Turned off my device and connected it through fastboot; installed the fastboot driver manually in the device manager; opened CMD and pointed to "C:\android-sdk-windows\platform-tools" where fastboot.exe is located, pasted the code and supposedly unlocked my smartphone. Just to be clear, my first attempt to run the code in the CMD returned an error message, saying the procedure was unsuccessful, but when I run the code for the second time it returned a success message.
For my surprise, when I turned the phone on, it started to bootloop. When pressing the Key down + insert USB cable combo, Sony's flashtool (Emma) returns a message saying that "phone is locked".
Just for elucidation purposes, my pc recognized my phone in every instance. It was recognized in normal circumstances, as it were recognized in fastboot. I've checked it in the device manager and everything was spot on.
So I'm kinda lost in the middle of this, suggestions would be highly appreciated. I would still like to unlock it and - if God permits - fix the bootloop problem and access my phone as I need it for work and daily routine.
To finalize, I would like to thank everyone in this forum for the amazing support and for the service provided.
Kind regards,
Absinto10

Good evening,
I've found a solution for 1/2 of the problem. If you're having a bootloop problem, the easiest fix I could find is to simply plug in your cellphone to your pc, open Sony pc companion, and update the phone's software. Just follow the instructions on this video:
http://www.dailymotion.com/video/x2...stock-in-sony-logo-always-restarting-etc_tech
Hope this helps.

Can't unlock bootloader. No idea what to do at this point.

Hi,
I'm trying to unlock the bootloader of my new Mi Note 3 but it's not working. Hopefully you can help me out. Quick recap:
PC:
- I applied for permission and got it within ~10 hours (this was ~24 hours ago).
- On i.mi.com, the device is 'connected'.
- I ran MiUsbDriver from the unlock tool.
- The driver as listed in the device manager is 'Android something 7.1.0.0' (I don't remember exactly and I don't have my computer right now).
- 'fastboot devices' lists my phone as connected.
- 'fastboot oem unlock' returns an error: 'Verify Token failed'.
- In Mi Unlock Tool, after I click the gear icon and then 'check', I get 'Mi Drive installed'.
- When I try to unlock, I get an error at 50%: 'couldn't verify device' (the error code is -1 I think).
Phone:
- My ROM is 'MIUI Global 9.5 | Stable 9.5.3.0 (NCHMIFA)'.
- Mi Account is logged in, the ID is the same as on my computer.
- OEM unlocking and USB debugging are both on.
- In 'Mi Unlock status', tapping 'Add account and device' returns 'Added successfully' but doesn't do anything else.
Misc:
- 'fastboot oem device-info' returns 'Verity mode' and 'Charger screen enabled' as true, and 'Device unlocked' and 'Device critical unlocked' as false.
- I have tried on different USB ports (and only used the USB cable that came with the phone).
- I have tried on two different computers.
- I have tried everything multiple times, signing out of and back in accounts, uninstalling and reinstalling drivers.
- I have received multiple SMS verification codes for stuff I don't even remember.
... My bootloader is still locked. I don't know what to do at this point. Do I need a DEV ROM? But then how do I flash it with a locked bootloader? Is this a driver issue? Should I just wait?
This is all so frustrating! Not having control over my own device... Being forced to borrow a Windows machine to run Chinese software with terrible translation... A manufacturer imposing unknown wait times and obscure procedures... I haven't had an Android device in a long time, everything used to be much simpler. *sigh*
Anyway, I'm pretty salty at the moment but other than that both the phone and this community seem great. I hope you can help me overcome this. If you need any other information let me know.

You have to wait 72 hours(after account added on smartphone).
Unlock is possible only with mi unlock tool.
http://en.miui.com/unlock/

dzidexx said:
You have to wait 72 hours(after account added on smartphone).
Click to expand...
Click to collapse
Thanks, I sure hope that's it.
It's weird that I have to wait even though I have received confirmation by SMS, I can download from the same link you provided, and the waiting time isn't mentioned anywhere...
Well, no harm in waiting, I'll report back!

Did you first connected device with Mi account in developer mode ? For that you will need VPN if you are outside of China.
Mi Note 3 Telegram group >>> https://t.me/joinchat/HxEbOEfaKQdfYZsbU6SR1A

I haven't any problems after 72 hours. Poland, Europe, without changing VPN .

I've just tried again. It still didn't work but this time it went up to 99% and told me to 'wait 6 hours before unlocking'. So... That's progress, I guess?
I'll wait the six hours and try again, if it still doesn't work I'll start over with a VPN.

bhuz said:
wait 6 hours before
Click to expand...
Click to collapse
72 hours, not less.

Does it work?
Seems only old device users cannot unlock

It finally worked!
After waiting the six hours, all went smoothly, the phone was unlocked in a matter of seconds.
So my advice to anyone who might read this in the future is to make sure everything is set up correctly (account, drivers, etc.) and then just be patient!
EDIT: I almost forgot, thank you guys for the help!

bhuz said:
It finally worked!
After waiting the six hours, all went smoothly, the phone was unlocked in a matter of seconds.
So my advice to anyone who might read this in the future is to make sure everything is set up correctly (account, drivers, etc.) and then just be patient!
EDIT: I almost forgot, thank you guys for the help!
Click to expand...
Click to collapse
hello, is there a thread i can get of unlocking the bootloader for mi note 3?

mucho979 said:
hello, is there a thread i can get of unlocking the bootloader for mi note 3?
Click to expand...
Click to collapse
Here.
If you get an error, you should wait a few days.

Question ROG 5s program speaks firehose protocol while your target is speaking sahara (Actual FIX)

Edit: I am keeping the information below intact, just incase someone goes through the same issues that I had gone through.
My recommendation is follow through with Johnny886 video on his installation guide and just skip any steps that aren't applicable to your set up. I recommend using his 0-update_image_edl.bat and not using Qfil or xiaomi. His video ends up showing most of the steps required to accomplish the repair, with exception of showing the phone and when you have to bring your phone into bootloader mode and what not.
I can personally attest to the fact this does bring a hard bricked phone from the grave. When I mean hard bricked, I mean black screen and in edl mode (shows up as a usb devices or port on your PC).
I am not a regular on these forums so I probably won't be here for long. I'll help if I see your posts, if I can help.
//////////////////////////////////////////////////////
Hello,
I am having issues installing johnny 886 ROG 5s firmware install via any method (Qfil, xiaomi flash, and update image edl windows batch file).
It says that the program speaks firehose and the device speaks sahara protocol on a text file on my computer.
I tried using xiaomi flash, but it makes a device disconnect sound and fails to ping target via firehose. (I am guessing because device is speaking sahara protocol).
I tried using Qfil flat build, and running firehose_ddr.elf and rawprogram and patch files 0-6 and it starts running the firehose_ddr.elf but it also runs into an error. (sahara_rx_data:276 Unable to read packet header. Only read 0 bytes. ( I think this also relates to the program speaks Firehose / device speaks Sahara protocol issue.)
Anyone have a way forward with dealing with this firehose/sahara issue?
I am also in windows 10 test mode.
EDIT, Fix found:
So I found out what was wrong. It shows "program speaks firehose protocol while your target is speaking sahara" because I was using the ddr.elf file.
If you pay attention to it, which I didn't at first, it says this:
"
This can mean
1. You forgot to send DeviceProgrammer first (i.e. QSaharaServer.exe -s 13: prog_firehose_lite.elf)
2. OR, you did send DeviceProgrammer, but it has crashed and/or is not correct for this target"
I found out you are suppose to use the prog_firehose_lite.elf file (or whatever file it say is the device programmer first).
When using the QFIL program, I was using the prog_firehose_ddr.elf and this caused the error to appear.
I will post an image showing how it is suppose to look like when configured correctly.
NOTE: (I ended up bricking my phone to the point of not having an accessible bootloader/recovery when ONLY using raw program 0 and patch 0 files). This made it so you can only turn on the phone using the - volume and power button and it gets stuck on the "republic of gamers" splash screen. I have a solution for that issue further down in the thread.

Trash.umu said:
Hello,
I am having issues installing johnny 886 ROG 5s firmware install via any method (Qfil, xiaomi flash, and update image edl windows batch file).
It says that the program speaks firehose and the device speaks sahara protocol on a text file on my computer.
I tried using xiaomi flash, but it makes a device disconnect sound and fails to ping target via firehose. (I am guessing because device is speaking sahara protocol).
I tried using Qfil flat build, and running firehose_ddr.elf and rawprogram and patch files 0-6 and it starts running the firehose_ddr.elf but it also runs into an error. (sahara_rx_data:276 Unable to read packet header. Only read 0 bytes. ( I think this also relates to the program speaks Firehose / device speaks Sahara protocol issue.)
Anyone have a way forward with dealing with this firehose/sahara issue?
I am also in windows 10 test mode.
Click to expand...
Click to collapse
Try here
Repair ROG Phone 5S through edl firmware, no need to unlock Bootloader to modify COUNTRY CN to WW
Success is disgusted by some people, and will not share any files for free in the future.
forum.xda-developers.com

JazonX said:
Try here
Repair ROG Phone 5S through edl firmware, no need to unlock Bootloader to modify COUNTRY CN to WW
Success is disgusted by some people, and will not share any files for free in the future.
forum.xda-developers.com
Click to expand...
Click to collapse
I did, but no one seems to be answering. Also, I am not sure if the error itself is related to the firmware, such as a setting in qfil or xiaomi needs to be changed somewhere. Other people seem to have similar issues on other phones but it didn't look like anyone actually replied to their question.

Trash.umu said:
I did, but no one seems to be answering. Also, I am not sure if the error itself is related to the firmware, such as a setting in qfil or xiaomi needs to be changed somewhere. Other people seem to have similar issues on other phones but it didn't look like anyone actually replied to their question.
Click to expand...
Click to collapse
You need to install the correct Qualcomm driver, and then your folder cannot have spaces or some unsupported characters.

After prompting the error, the phone needs to re-enter the edl mode, and then operate again.
Trash.umu said:
I did, but no one seems to be answering. Also, I am not sure if the error itself is related to the firmware, such as a setting in qfil or xiaomi needs to be changed somewhere. Other people seem to have similar issues on other phones but it didn't look like anyone actually replied to their question.
Click to expand...
Click to collapse
After prompting the error, the phone needs to re-enter the edl mode, and then operate again.

johnny886 said:
After prompting the error, the phone needs to re-enter the edl mode, and then operate again.
After prompting the error, the phone needs to re-enter the edl mode, and then operate again.
Click to expand...
Click to collapse
So my phone attempted to install the firmware but now it does not have a bootloader, it does not connect to the PC and it can only get up to the point of showing the republic of gamers logo and letters.
I am guessing the only way forward is opening this thing up or buying a new phone. Unless you have a way out of this?
1. It is no able to go into edl via computer through adb.
2. It does not appear on device manager nor disk management.
3. It does not have a recovery option appearing and pressing +volume and power button does nothing.
4. You can only press the - volume and power button, the regular power button does nothing and when using the - volume button and power button, it just gets stuck on the republic of gamers screen.
5. It does not go into edl mode when connected to either the bottom or the side port on the phone.
6. It does not connect to the computer even if you delete the device, the drivers, reinstall the drivers and device. reset the computer and device and all forms of these things in different orders.
If the only way forward is possibly removing the battery and maybe shorting two pins together, do you have an idea which pins these are?
EDIT, Fix found:
So I found out that if you connect the ROG 5s phones side port to the computer while it is frozen in the republic of gamers logo for about 20 minutes, it resets and the android recovery screen pops up with only the options of "try again" and "factory data reset" and appears as an asus I005D in universal serial bus devices on my device manager. Now that I have it connected to the PC, I have a way forward.
It appears as in recovery mode in adb. you can not do anything other than enter "adb devices" and "adb reboot edl"
forcing the phone into edl using the adb cmd of "adb reboot edl" makes the device appear as a port device. This will allow me to reinstall the firmware again using the QFIL program.

I seem to keep falling through the same loop of errors. I wonder if there is a firmware error somewhere or if my phone is somehow rejecting the firmware.
I will update if I get anywhere.

NOTE:
If for some reason you can not get your phone to turn on or it turns off as you press the recovery option.
You need to connect the usb port to provide power via the bottom port and NOT the side port.
I am not sure why it is required, maybe the bottom port energizes more things than the side port does and it causes this fault. If you have both ports connected, it disconnects the bottom port and automatically uses the side port.

Trash.umu said:
我似乎不断陷入同样的错误循环。我想知道某个地方是否存在固件错误，或者我的手机是否以某种方式拒绝了固件。
如果我到达任何地方，我会更新。
Click to expand...
Click to collapse
There is no error in the firmware, and it is only released after it has been tested and there is no problem.

johnny886 said:
There is no error in the firmware, and it is only released after it has been tested and there is no problem.
Click to expand...
Click to collapse
I'll attempt to figure out why my phone isn't working properly. It may take awhile. Maybe it has to do with multiple attempts of installing the same firmware, or it could be that some of my phones components are already dying and it is just a coincidence.

NOTE: My phone kept failing to properly download johnny886 firmware because my phone (in particular) kept requiring me to switch between the side and bottom ports to keep my phone alive. I am unsure why I this was the case but I was able to finally install the firmware on my phone and my phone is now up and running properly.
I have to give thanks to johnny886 for his files, his video and his efforts. If not for him, my phone would still be a brick.

Rooting problem and strange phone behaviour while it

Hello. I'm an owner of a Xiaomi Redmi 9A and I have following rooting problems with it:
1. while beeing in phone's fastboot mode and after sending from the computer's terminal (after sucessfull connection):
"fastboot oem unlock"
the phone "thinks" for a short bit before restarting itself without doing anything
2. I have a Xiaomi account bound to the phone and when selecting the "check unlock state" the phone ask me to turn off wifi, enable the (paid) data transfer and bind the phone to the account
3. while using the official Xaiomi unlock tool (with was downloaded from the phone producer's website), the phone isn't even seen in it
Could anyone help me ?

Try installing usb drivers or the phone will never be detected.

VD171 said:
Try installing usb drivers or the phone . never be detected.
Click to expand...
Click to collapse
in case of adb and fastboot, I had used them on Linux.
Only the official unlocking tool was for Windows, on with the usb drivers were installed.
Linux detect it without any issue

Just use it to unlock on Linux:
XiaoMiTool V2 - Modding of Xiaomi devices made easy for everyone
XiaoMiTool V2 is a easy to use tool to install rom on your Xiaomi device. Modding made easy for everyone! Download it for free now!
xiaomitool.com

VD171 said:
Just use it to unlock on Linux:
XiaoMiTool V2 - Modding of Xiaomi devices made easy for everyone
XiaoMiTool V2 is a easy to use tool to install rom on your Xiaomi device. Modding made easy for everyone! Download it for free now!
xiaomitool.com
Click to expand...
Click to collapse
thanks, but it seem to don't work correctly with my phone.
After my phone had become detected when was in the fastboot mode and after clicking the "select" button in the app, the phone has rebooted to the normal mode and asked to scan again. It hasn't done anything except the mentioned above.

mcgiwer said:
thanks, but it seem to don't work correctly with my phone.
After my phone had become detected when was in the fastboot mode and after clicking the "select" button in the app, the phone has rebooted to the normal mode and asked to scan again. It hasn't done anything except the mentioned above.
Click to expand...
Click to collapse
Did you enable usb debugging on developer settings?
Did you allow the usb debugging for the actual computer?

VD171 said:
Did you enable usb debugging on developer settings?
Did you allow the usb debugging for the actual computer?
Click to expand...
Click to collapse
yes in both cases... I have even enabled the "oem unlock" option in the setting

Install windows on partition 30Gb, change cable

yaro666 said:
Install windows on partition 30Gb, change cable
Click to expand...
Click to collapse
The cable is new and I won't wipe my Linux to install a Windows (about with I have a bad opinion)

Make a dual boot, just resize partition, you need 30Gb and in 45min you will know what is the problem.
Or you can try to liveboot windows from usb stick.

yaro666 said:
Make a dual boot, just resize partition, you need 30Gb and in 45min you will know what is the problem.
Or you can try to liveboot windows from usb stick.
Click to expand...
Click to collapse
Question: Why do you push so much on me to install Windows?
This forum is dedicated to mobile phones and my topic is about anormal phone behaviour of a phone while attempt to root it. Wiping out a safe Linux and installing a Windows won't help at all....
I tryed to root the phone on friend's laptop with a Windows (with the latest drivers and software installed) and it didn't worked.
I suspect that the producer probably has fabrically instaled a damaged or improper firmware

As you wish. Windows is more device friendly. I just suggest to do it on W, nothing more.
You state that fastboot works, but Linux don't see your phone, like in case you don't have drivers for adb. We don't know if you installed everything on Linux properly

yaro666 said:
As you wish. Windows is more device friendly. I just suggest to do it on W, nothing more.
You state that fastboot works, but Linux don't see your phone, like in case you don't have drivers for adb. We don't know if you installed everything on Linux properly
Click to expand...
Click to collapse
hello. You had missread my post. I wrote that it isn't seen only in the unlock software. Fastboot and ADB detect it correctly

Question Hidden oem unlock

I upgraded to android 12. Oem unlock is not visible. I went back to android 11 and it still doesn't show. help

hhhhhhhhheeelllpp

And i search on recovery mode tap bootloader but i see black screen

is there no one to answer on huge xda? interesting

I think you can just use the official OEM unlock too app to one-step unlock the BL....

asus bootloader unlock tool apk. I tried maybe 20 times and it didn't work
yurishouse said:
I think you can just use the official OEM unlock too app to one-step unlock the BL....
Click to expand...
Click to collapse

I did not understand anything.
OEM unlock does not visible in developer options. I cannot enter the bootloader in the recovery menu. asus unlock tool.apk doesn't work.
i regret buying an asus phone

Robocop36 said:
I did not understand anything.
OEM unlock does not visible in developer options. I cannot enter the bootloader in the recovery menu. asus unlock tool.apk doesn't work.
i regret buying an asus phone
Click to expand...
Click to collapse
This device does not have OEM unlock. Contact ASUS to try and resolve the issue with the unlock app but I suspect you have a converted phone that is getting rejected by the ASUS side. Attempting too fix it yourself will involve amending some device parameters, I think someone has added some notes somewhere on the forums here..

I made a comment on asus zentalk. I've been waiting for a week, no answer. There are 20 moderators, but one person is not responding. a disgraceful place.
Hey man i went to the internet cafe yesterday to install raw firmware. I downloaded win10 asus qualcom usb drivers , downloaded usb minimal android sdk, pressed the volume up power button, the computer did not see my phone on the start screen, I tried many times and it didn't work.
The computer sees the phone without entering the start screen. I even copied 40 movies to the phone. but every time I press the volume up/power button the computer does not see the phone when the start screen comes up.

Andrologic said:
This device does not have OEM unlock. Contact ASUS to try and resolve the issue with the unlock app but I suspect you have a converted phone that is getting rejected by the ASUS side. Attempting too fix it yourself will involve amending some device parameters, I think someone has added some notes somewhere on the forums here..
Click to expand...
Click to collapse
If I try this, will the computer see my phone on the start screen?
ASUS Android Bootloader Interface Drivers Download for Windows 10, 8.1, 7, Vista, XP
Download the latest drivers for your ASUS Android Bootloader Interface to keep your Computer up-to-date.
www.driverscape.com

hhhhhhhheeeeeellppppp

It had HTC, Samsung, Xiaomi. I switched to ASUS. maybe my version is cn but the chinese changed it to ww! I didn't know it was like this i wouldn't have bought this phone had I known.

How do I get out of this job? I risk losing imei and more. maybe my device will be hard bricked. Flashing raw software takes a lot of effort. first of all, my computer doesn't see my device on the start screen, I couldn't even take a step. I unlocked the bootloader hundreds of times on my previous phones. I rooted hundreds of times , I installed custom roms hundreds of times,. but I could not progress even one step on the Asus phone.

Robocop36 said:
If I try this, will the computer see my phone on the start screen?
ASUS Android Bootloader Interface Drivers Download for Windows 10, 8.1, 7, Vista, XP
Download the latest drivers for your ASUS Android Bootloader Interface to keep your Computer up-to-date.
www.driverscape.com
Click to expand...
Click to collapse
Suggest using the orginal Andrid driver directly from Google. There is no specific ASUS drivers needed for this device although the one in your link may work too. And yes, you do need to sort out your driver before you can flash from PC to the device with Fastboot commands.

Andrologic said:
Suggest using the orginal Andrid driver directly from Google. There is no specific ASUS drivers needed for this device although the one in your link may work too. And yes, you do need to sort out your driver before you can flash from PC to the device with Fastboot commands.
Click to expand...
Click to collapse
Ok

Hi, your device seems to be a converted chinese version (with Tencent Games on the back) so you need to use this method to spoof the region if your phone and force the bootloader unlock: https://forum.xda-developers.com/t/...the-bootloader-of-your-rog-phone5-5s.4371255/

Saying and complaining ain't gonna help you out.
Lost people don't wanna reply as this is covered many times and can be found with search option on this forum.
Anyway his is relevant info for you :
1: The usb c port needed to use to flash etc in bootloader mode is on the side, NOT the bottom one.
2 : if option 1 this Still not working add device manual in driver section of computer, then is driver problem.
3: adb drivers/software/map with adb commands etc needs to be present on computer, or commands will not be executed correctly and give error.
4: of you have a Chinese phone CN FW that is flashed with the WW firmware, you will get problems, only way to solve this is to use correct firmware on device and upgrade.
This is also covered in a big topic on this forum.
5: of you need to go to a internet cafe do to flashing and install firmware, and you had Samsung xaomi etc and can't work this out yourself or Ith search option, o ask myself if you should mess with the phone in the first place,
When it goes wrong, it is bad phone, crap etc.... While it is user error. No hard feelings.
Hope you know enough now and get it fixed
Sending from Rog 5 ultimate android12 fw ww91 unlocked and rooted.

Read this : https://forum.xda-developers.com/t/...the-bootloader-of-your-rog-phone5-5s.4371255/

1: i was plugging it into the bottom usb c port not the side usb c port I'll try it when I have free time. thank you all so much