Hi, i have i few questions about it-.... my xperia zl says not allowed unlock bootloader.... but im still try to do it.
i download all the files and drivers from sdk, when i open the cmd or the terminal and i type fastboot.exe getvar like sony says, i put my phone in bootloader mode with +volume and plug the usb, the blue light turn it on and stay on... but my pc or command prompt just says waiting for devices, not devide detected, is that a problem of my drivers or is for the locked bootloader?
thanks.
leo_hacker82 said:
Hi, i have i few questions about it-.... my xperia zl says not allowed unlock bootloader.... but im still try to do it.
i download all the files and drivers from sdk, when i open the cmd or the terminal and i type fastboot.exe getvar like sony says, i put my phone in bootloader mode with +volume and plug the usb, the blue light turn it on and stay on... but my pc or command prompt just says waiting for devices, not devide detected, is that a problem of my drivers or is for the locked bootloader?
thanks.
Click to expand...
Click to collapse
If your status of unlock bootloader = no mean that you can't unlock your bootloader. At the moment no method can unlock that status. Maybe you can ask your mobile carrier and request one, most likely will cost you some money.
leo_hacker82 said:
Hi, i have i few questions about it-.... my xperia zl says not allowed unlock bootloader.... but im still try to do it.
i download all the files and drivers from sdk, when i open the cmd or the terminal and i type fastboot.exe getvar like sony says, i put my phone in bootloader mode with +volume and plug the usb, the blue light turn it on and stay on... but my pc or command prompt just says waiting for devices, not devide detected, is that a problem of my drivers or is for the locked bootloader?
thanks.
Click to expand...
Click to collapse
1. i think this is not the right place to post this kind of questions...
2. if says no it means NO, you cant unlock it, u must think in buy another phone with unlocked status:YES
3. i think if you keep trying you may brick your phone...
First I must say, I searched all over the internet for answer to this problem. None of the topics I read had matched my problem.
I want to unlock my bootloader so I can flash custom recovery and get root access.
When I want to access the bootloader ("adb reboot bootloader"), in my phone all goes fine (I see on my phone the Fastboot instructions, etc). The problem is in my computer that fastboot won't recognise my phone anymore. When I want to get the device-id, fastboot is stuck on "waiting for all devices". When I want to see the list of devices, ("fastboot devices"), I get nothing, wether my phone is on bootloader mode or not.
I installed all the LG drivers, including the ADB one. I am in USB debugging mode, and I disabled OEM protection.
Android version is Lollipop.
I need help on this matter, thanks in advance.
notrium dweller said:
First I must say, I searched all over the internet for answer to this problem. None of the topics I read had matched my problem.
I want to unlock my bootloader so I can flash custom recovery and get root access.
When I want to access the bootloader ("adb reboot bootloader"), in my phone all goes fine (I see on my phone the Fastboot instructions, etc). The problem is in my computer that fastboot won't recognise my phone anymore. When I want to get the device-id, fastboot is stuck on "waiting for all devices". When I want to see the list of devices, ("fastboot devices"), I get nothing, wether my phone is on bootloader mode or not.
I installed all the LG drivers, including the ADB one. I am in USB debugging mode, and I disabled OEM protection.
Android version is Lollipop.
I need help on this matter, thanks in advance.
Click to expand...
Click to collapse
not all phones can be unlocked.. search for g4 list of bootloader unlock youll see the list if yours isnt there you cant . only root 5.1 no twrp.
raptorddd said:
not all phones can be unlocked.. search for g4 list of bootloader unlock youll see the list if yours isnt there you cant . only root 5.1 no twrp.
Click to expand...
Click to collapse
I know mine can be unlocked. I actually can get to the bootloader via ADB. The problem is that fastboot won't recognise my phone afterwards. (I believe it's the european version of the H815 model, and according to one-click-root app, my phone can be safely rooted. Also my Lollipop version is 5.1.)
There are other few issues also:
Fastboot won't recognise my phone, even if the phone is not in bootloader mode.
Windows will recognise all of the LG related drivers including the ADB related driver, while the phone is powered on normally.
However, it fails to do so, in bootloader mode. I see non working driver in Windows 7 Device Manager, under "Other Devices" by the name "Android" with yellow exclamation mark. Nothing else.
Still looking for advice...
notrium dweller said:
I know mine can be unlocked. I actually can get to the bootloader via ADB. The problem is that fastboot won't recognise my phone afterwards. (I believe it's the european version of the H815 model, and according to one-click-root app, my phone can be safely rooted. Also my Lollipop version is 5.1.)
There are other few issues also:
Fastboot won't recognise my phone, even if the phone is not in bootloader mode.
Windows will recognise all of the LG related drivers including the ADB related driver, while the phone is powered on normally.
However, it fails to do so, in bootloader mode. I see non working driver in Windows 7 Device Manager, under "Other Devices" by the name "Android" with yellow exclamation mark. Nothing else.
Still looking for advice...
Click to expand...
Click to collapse
am sorry i cant help ive nver unlocked mine..
Still looking for suggestions, people...
I have the same problem, adb detects my phone but fastboot does not. Same Phone btw
Still no solution until now ? I have the same problems
My device is H815
Hi !
I have had this problem too...solved with strong battle to understand myself...
My solution : when you have installed driver ,when your phone go to fastboot mode and the pc don't want to reconize the phone : on the pc on windows go to harware manager (config panel) and you can see in theory "android" with a "?" ==> you have to install manually the driver by searching somewhere on the harware list "android adb interface " (i don't remember where it is) ==> your phone wil be reconized ! And you will have the 2 lines of ID on the adb comand interface....and follow the tutorial...
I have read hundreds of issues with driver problems when it comes to windows.
Please try Linux instead. There are live distributions like Ubuntu available. Install it on USB stick and start from there.
No driver issues anymore. Just works.
.
@steadfasterX it need some knowledge for to use Linux OS for adb thingsv (unlock bootloader ,instal TWRP,rom,apps...etc...) ? maybe you can do a small tutorial for to help ?
For windows i have found these pictures for an eventual help (see ZIP on attach file)
@Loulou-13 , now i can see my device-id - solved -
but now have another problems, my imei is not match with my device-id ...
my device is H815
yes...i know i have sent an answer too late ... but my solution is one of this problem and eventualy can be useful for other people.
for your new problem ,what happen ? .......have you enter the corect number ,without space or other ?
Loulou-13 said:
@steadfasterX it need some knowledge for to use Linux OS for adb thingsv (unlock bootloader ,instal TWRP,rom,apps...etc...) ? maybe you can do a small tutorial for to help ?
For windows i have found these pictures for an eventual help (see ZIP on attach file)
Click to expand...
Click to collapse
Well there are hundreds of guides out there just use google...
adb and fastboot working the same way under Linux so there is no need to have a specific guide for linux.
I haven't tested that guide here but it looks very good as a starting point:
http://forum.xda-developers.com/showpost.php?p=44739402&postcount=1
As said there are other maybe better guides but Google will tell you.
.
@steadfasterX thank for your link ,it's useful for people who have problem and read this thread
It's not for me .... i have my bootliader unlocked ,twrp...( and this fabulous Imperium MM rom !!!! )
Hey guys,
i've got a problem with my Z5 Premium and I hope you can help me.
I just got it repaired (flex cable broke) and I wanted to give it a try unlocking the bootloader and later rooting it. Unfortunately it fails already at the first point.
My model is a regular Z5 Premium E6853. I am currently on version 32.4.A.1.5 / R1E.
Everytime I try to unlock my bootloader, it says "FAILED (remote: Command did not succeed)".
I'm starting to run out of ideas and I really want that bootloader unlocked.
Things I checked before:
I octuple-checked the IMEI and the unlock code. I also quadruple-checked my IMEI (phone box, settings, phone pad and service menu)
I did reinstall all drivers and I did install the fastboot drivers using the unsigned drivers (tried with the google drivers too)
I did try to use different USB cables (unfortunately the original one is broken, but I tried it with another Sony cable and some brand-new aftermarket cables)
I did enable OEM unlocking, ADB debugging and untrusted sources in the settings
I did check my bootloader version: it's 0.5
I did check that my bootloader is unlockable. The service menu says "Bootloader unlock allowed: Yes"
Are there any other things I need to do? Like having a valid sim card in the phone (not that I havent tried)?
I hope you guys can help me.
Best regards
Lyrex
Ok guys I really need you help. I honestly feel like im losing it as I have not been able to make any progress with this. Believe me I have tried other threads to no avail....
Ok so, I bought this phone but the problem with it is that I cant use google pay due to its unlocked bootloader (bought it like this second hand). I'm on really old firmware (6.0.1, 1 September 2016 Security Patch) as you can see very behind from Oreo or whatever the latest firmware is because I cant get OTA updates due to the unlocked bootloader.
I'm literally just asking for a simple, noob friendly guide which will allow we to relock it and update to the latest firmware so my phone will be perfectly fine for work use.
Please guys. Apologies if I sound annoyed but this has been bugging me for ages. Let me know if I should add anything else.
Much appreciated guys!
EDIT: I Used this guide: https://forum.xda-developers.com/moto-z-play/how-to/guide-relock-bootloader-to-lasted-stock-t3718190 and followed it exactly and enable USB debugging but keep getting "<waiting for any device>"?
bump
Hmm, with the 'waiting for device' issue, do you have the Motorola drivers installed on the computer? https://support.motorola.com/uk/en/drivers Also, if you are running Windows 10 or 8.1, verify that you have driver signature enforcement disabled on your computer, so the Motorola fastboot driver can load properly: https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/ or you can try to manually load the fastboot driver when your device is connected to your computer. This should then help your computer communicate with your device when you boot your device to the bootloader for flashing the stock ROM.
Verify also that you have a high quality USB data cable (preferably the original cable) and that you've got your device connected to a powered USB 2.0 or 3.0 port. Double-check the communication between your computer and your device - boot your device to the bootloader, connect to your computer. Open the ADB terminal and enter 'fastboot devices' (without quotes) into the terminal. Press Enter. If communication is working, this command should return your device serial number.
For that guide as well, you do not need to be on a custom ROM to follow it. If you do get your device talking, then extract the stock ROM as per the guide to your ADB folder, and execute both sets of commands to re-lock your bootloader. Be aware that the re-locking will erase your device, so back up if you have not already. OTA updates are not dependent on unlocked/locked bootloader status - as long as you have a firmware build that was deployed on the retgb software channel, you should get OTA updates regardless of whether your bootloader is unlocked or not. However, as you correctly point out, Android Pay does care about the bootloader unlocked status, however, rooting with magisk (to hide your bootloader unlocked status) may help you get Android Pay working if you want to keep your bootloader unlocked. Depending on your work IT requirements though, you may want a locked bootloader and no root to be compliant with the IT regulations.
Good luck either way.
echo92 said:
Hmm, with the 'waiting for device' issue, do you have the Motorola drivers installed on the computer?.
Click to expand...
Click to collapse
I have now installed the program but get "There are no updates for your device at this time. Current Version: N/A"? My USB debugging is enabled.
Thanks for the detailed reply mate. Im going to get some new cables and follow your advice. Might take me a few days as i'm busy with work but definitely am looking forward to fixing my phone once and for all!
Omg it works. I downloaded the Motorola program and opened up adb minimal fastboot whilst in usb debugging. I just pasted everything and it started to work!...oh I also held the volume down button whilst the phone was turning on so it went to a screen with the android mascot. Then I pasted the codes to adbmininal fastboot.
Thanks for all you help mate !!
You can get OTA updates even if your bootloader is unlocked.
While trying to unlock bootloader I am getting Unknown error(900000) in flash tool. I have googled this issue and the solutions offered in it are not working(suggested to try old versions of flash tool, they wont even login). I have applied for unlocking before 20 days. Tool was showing 360hours wait at that time. attached the screenshot for reference,
I have tried unlocking at two different windows 7 PC, switching on and off - USB debugging. kindly suggest a solution for this.
Edit: Tool logins and detecting the device just fine, It checks the status of device, and in unlocking it goes upto 99% and shows unknown error