Z5C has an option now to check/un-check OEM Unlock (bootloader)
(tap mutiple times on buildnumber in 'about phone' and go to 'developer options')
But it seems very uncertain what the DRM loss is. MyXperia, maybe low light camera features? And etc.
I do not take any responsibility of any DRM loss.
Very interesting indeed! Thanks for sharing!
Thanks for sharing this.
I take the opportunity to ask. Sony voids the warranty if you unlock the bootloader? (Like Motorola and almost every other company with the exception of Nexus/GPE devices and maybe some more).
Thanks!
Shouldn't be the case in EU. See [INFO][EU] Rooting and Flashing don't void the warranty or https://www.reddit.com/r/Android/comments/2r8nqa/phones_with_warranty_friendly_rootbootloader/cne2u95 . However I don't have any experience with this myself.
This is good news indeed if it holds up untill the release date.
Here is a list of supported devices if you want to keep track.
developer.sonymobile com/unlockbootloader/unlock-yourboot-loader
I got my z5c yesterday. If I follow the step-by-step guide for z3c (because z5c is not listed, yet?) and call *#*#7378423#*#*, go to service info > configuration > rooting status, it says "Rooting status: Bootloader unlocked allowed: yes".
Continuing the process and providing a mail and then my IMEI, I received a unlock link for my Sony Xperia Z5 Compact using the Z3 Compact guide. I have not tried to use it yet but I will when I get home.
Cool, let us know how you get on! Looks like you're the first one to have a go at it.
I tried doing it but I can connect to fastboot. With z3c, this was done like this:
1. Turn off your Xperia™ Z3 Compact.
2. Connect a USB-cable to your computer.
3. On your Xperia™ Z3 Compact, press the Volume up button at the same time as you connect the other end of the USB-cable. For Windows users, when asked for a driver, point to the usb_driver folder where you placed the android_winusb.inf-file, and select the Android Boot loader Interface-file.
4. When your device is connected, open a command window on your computer and go to the platform-tools folder within the Android SDK folder.
5. Enter the following command:
fastboot devices
6. Verify that you get an answer back without any errors.
This does not seem to apply on z5c. Any ideas?
OEM Unlock Bootloader - Preserving DRM most likley!?
Did you check bootloader allowed option from settings --> developers options as posted earlier
Sent from my iPad using Tapatalk
mele80 said:
Did you check bootloader allowed option from settings --> developers options as posted earlier
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
If you mean Enable OEM unlock, then yes, I have that checked. I also have USB debugging enabled.
I tried and the device boots into fastboot mode just fine. It also is listed normally using
Code:
fastboot devices
But I am too much of a coward to try
Code:
fastboot oem unlock
because I bought the device mostly for the camera and don't want to break it.
How did you do it? Nothing showed up for me.
I turned the device off and while holding the volume up key I plugged it in. Then the blue light for fastboot lit up and I had access. Volume down and plugging it in just just very shortly lights up the green flashmode led. I hope flashing still works with flashtool.
itaq said:
How did you do it? Nothing showed up for me.
Click to expand...
Click to collapse
i hope there will be a way to root the device without losing the drm-keys (finally).
i will receive my z5c today and don't want to use it without e.g. adaway.
why is the thread starter thinking that the new developer option would affect the losing of drm-keys?
lowtraxx said:
I turned the device off and while holding the volume up key I plugged it in. Then the blue light for fastboot lit up and I had access. Volume down and plugging it in just just very shortly lights up the green flashmode led. I hope flashing still works with flashtool.
Click to expand...
Click to collapse
Okey, so I tried what you said. I turned it off, plugged the cable in the computer, held down the volume up button and plugged in the cable in the phone. The light turned red and then blue and stayed blue. Here is what I got:
Code:
C:\Users\itaq\AppData\Local\Android\sdk\platform-tools>fastboot devices
C:\Users\itaq\AppData\Local\Android\sdk\platform-tools>
No output, it did not find the device. I also tried this:
Code:
C:\Users\itaq\AppData\Local\Android\sdk\platform-tools>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
The computer did not find my device. I tried changing USB port and I tried doing it when the phone was on, no luck.
Did it find your device when you did
Code:
fastboot devices
?
itaq said:
Okey, so I tried what you said. I turned it off, plugged the cable in the computer, held down the volume up button and plugged in the cable in the phone. The light turned red and then blue and stayed blue. Here is what I got:
Code:
C:\Users\itaq\AppData\Local\Android\sdk\platform-tools>fastboot devices
C:\Users\itaq\AppData\Local\Android\sdk\platform-tools>
No output, it did not find the device. I also tried this:
Code:
C:\Users\itaq\AppData\Local\Android\sdk\platform-tools>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
The computer did not find my device. I tried changing USB port and I tried doing it when the phone was on, no luck.
Did it find your device when you did
Code:
fastboot devices
?
Click to expand...
Click to collapse
Do you hear the Windows' sound when you connect your phone in Bootloader (Fastboot) mode?
If so, then you'll probably need to "manually install" the fastboot driver using the Windows "Device Manager". Selecting the .inf file from the Android SDK folder (the Extras folders where Google USB Drivers are installed). Or using the "Have Disk" option in the device manager (and then selecting the .inf file) or something like that.
Then you put "Fastboot devices" and your device should appear.
Yes, I got the device listed when I did fastboot devices. I am using linux so I cannot say what the specific problem is, but as @thesebastian suggested I would guess that the fastboot driver is not installed or not installed correctly.
itaq said:
Okey, so I tried what you said. I turned it off, plugged the cable in the computer, held down the volume up button and plugged in the cable in the phone. The light turned red and then blue and stayed blue. Here is what I got:
Code:
C:\Users\itaq\AppData\Local\Android\sdk\platform-tools>fastboot devices
C:\Users\itaq\AppData\Local\Android\sdk\platform-tools>
No output, it did not find the device. I also tried this:
Code:
C:\Users\itaq\AppData\Local\Android\sdk\platform-tools>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
The computer did not find my device. I tried changing USB port and I tried doing it when the phone was on, no luck.
Did it find your device when you did
Code:
fastboot devices
?
Click to expand...
Click to collapse
lowtraxx said:
Yes, I got the device listed when I did fastboot devices. I am using linux so I cannot say what the specific problem is, but as @thesebastian suggested I would guess that the fastboot driver is not installed or not installed correctly.
Click to expand...
Click to collapse
That most be it. I'll look in to drivers and report back if I get it working.
---------- Post added at 05:15 PM ---------- Previous post was at 05:08 PM ----------
thesebastian said:
Do you hear the Windows' sound when you connect your phone in Bootloader (Fastboot) mode?
If so, then you'll probably need to "manually install" the fastboot driver using the Windows "Device Manager". Selecting the .inf file from the Android SDK folder (the Extras folders where Google USB Drivers are installed). Or using the "Have Disk" option in the device manager (and then selecting the .inf file) or something like that.
Then you put "Fastboot devices" and your device should appear.
Click to expand...
Click to collapse
That's it, thank you. I hear the sound when I plug it in. Checking the drives was the next thing I was going to do.
Continuing this discussing in this thread keep this thread on topic.
you would also need a code for the fastboot oem unlock command from sony dev site, right?
Related
Hi guys,
I searched forums, web with no positive results. So I start a new thread. Here is the situation: one day my Nexus S (Worldwide edition) froze on restarting with the Google Logo on the screen. Every time I try to turn the phone on it stacks at Google logo. When in the fastboot mode the status is Locked. Every time I try fastboot oem unlock I get Phone’s prompt with Yes or Not to unlock bootloader and after choosing Yes, the status doesn’t change to Unlock. Tried on Linux, Mac, Windows (drivers installed successfully), the same result. Tried to force Flash Stock + Unroot in Wugfresh, doesn’t work due to the Locked Bootloader.
typing "adb devices" in cmd (should return the device number) shows:
List of devices attached
......
Empty line above
Any word of advise how to force Unlocking the Bootloader would be greatly appreciated. Please help. Thank you!
alpheus said:
Hi guys,
I searched forums, web with no positive results. So I start a new thread. Here is the situation: one day my Nexus S (Worldwide edition) froze on restarting with the Google Logo on the screen. Every time I try to turn the phone on it stacks at Google logo. When in the fastboot mode the status is Locked. Every time I try fastboot oem unlock I get Phone’s prompt with Yes or Not to unlock bootloader and after choosing Yes, the status doesn’t change to Unlock. Tried on Linux, Mac, Windows (drivers installed successfully), the same result. Tried to force Flash Stock + Unroot in Wugfresh, doesn’t work due to the Locked Bootloader.
typing "adb devices" in cmd (should return the device number) shows:
List of devices attached
......
Empty line above
Any word of advise how to force Unlocking the Bootloader would be greatly appreciated. Please help. Thank you!
Click to expand...
Click to collapse
It looks like your device is not recognized in Fastboot mode...
Have you turned on USB Debugging while connecting PC and Allow in Device when Prompt some message ..
Go to fastboot mode and write this command... fastboot devices
If it will give you a message like this
List of devices
1235456785164
Then your devices is successfully recognized...:good:
It is not recognized by adb devices, but:
fastboot devices - gives the following output:
ERROR: could not get pipe properties
3331E6EBCA6000EC fastboot
Click to expand...
Click to collapse
fastboot oem unlock - gives the following:
ERROR: could not get pipe properties
...
FAILED (remote: Erase Fail)
finished. total time: 4.753s
Click to expand...
Click to collapse
alpheus said:
It is not recognized by adb devices, but:
fastboot devices - gives the following output:
fastboot oem unlock - gives the following:
Click to expand...
Click to collapse
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
demkantor said:
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
Click to expand...
Click to collapse
Thanks, I tried 3 different cables on 3 different operating systems, with the same problem unlocking the fastboot. When I send fastboot oem unlock the device opens a prompt with Yes or No choice, but after choosing Yes, it stays Locked
Something indeed is strange...
So fastboot is for bootloader and adb is for within os and in recovery.
Try booting into recovery and see if adb works, also boot normal into your bootloop and see if adb works there too
demkantor said:
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
Click to expand...
Click to collapse
demkantor said:
Something indeed is strange...
So fastboot is for bootloader and adb is for within os and in recovery.
Try booting into recovery and see if adb works, also boot normal into your bootloop and see if adb works there too
Click to expand...
Click to collapse
Loading into basic recovery and trying to wipe data/factory reset - doesn't work. adb devices returns the following output:
./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
****empty line here****
Somehow, adb doesn't recognize the device, whereas fastboot devices shows it.
Is there a way to flash new bootmode with the currently locked bootloader?
Thank you!
alpheus said:
Loading into basic recovery and trying to wipe data/factory reset - doesn't work. adb devices returns the following output:
./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
****empty line here****
Somehow, adb doesn't recognize the device, whereas fastboot devices shows it.
Is there a way to flash new bootmode with the currently locked bootloader?
Thank you!
Click to expand...
Click to collapse
I am damn Sure What's Your problem is, ADB is not working..
PROCEDURE:-
1) Download My attachement and unzip it and Place it in Folder...
See image 1.png
2) Go to that folder and Press CTRL+SHIFT+ Right click on mouse and Select Open Command Window here..
See image 2.png
3) Now type here Fastboot devices and Now you will get Those list of devices Number..
See image 3.png
If Everything will be done as Procedure and you will get List of devices Number... Now, You type those command for Unlocking bootloader and Root Your Devices...:good:
Hope this Guide will help..
UPDATE (resolved)
Here is an update. Hope this would help others with similar issue, as I've read many threads and folks complaining that they weren't able to unlock fastboot and further root their Nexus S, and who can't boot the phone, which stacked with Google Logo (soft loop). This was the case with my device and finally I got it resolved. I've read some guy tried to hit the phone and after that he was able to boot phone normally. It related to some hardware electrical circle issue. Anyways, I tried to hit my phone by placing it under the direct sun in balcony for some time until the phone got hot and then power it on. And ooops, my phone started booting passed by that Google Logo which was the good sign. Once the phone booted up, I went ahead and activated USB debugging and restarted the phone into the Fastboot mode. while the phone was still hot and in Fastboot mode I run "fastboot oem unlock" and hey, fastboot is Unlocked! Again, this was done while the phone was hot, any previous attempts (read above) weren't successful. From that point, I went ahead and rooted my Nexus S by Nexus Root Toolkit, available on wugfresh.com/nrt, without a slightest problem. Now my phone is fully rooted, bootable and working fine. I thank all who replied to my thread and tried to help and hope this info would help someone with the similar issue.
Rushabh22 said:
I am damn Sure What's Your problem is, ADB is not working..
PROCEDURE:-
1) Download My attachement and unzip it and Place it in Folder...
See image 1.png
2) Go to that folder and Press CTRL+SHIFT+ Right click on mouse and Select Open Command Window here..
See image 2.png
3) Now type here Fastboot devices and Now you will get Those list of devices Number..
See image 3.png
If Everything will be done as Procedure and you will get List of devices Number... Now, You type those command for Unlocking bootloader and Root Your Devices...:good:
Hope this Guide will help..
Click to expand...
Click to collapse
Thank you for your help and suggestions.
Q Mobile X 32
bootloader oem unlock problem
plz help
Q-mobile said:
Q Mobile X 32
bootloader oem unlock problem
plz help
Click to expand...
Click to collapse
Wrong device thread..
Try here..
https://forum.xda-developers.com/showthread.php?t=2363923
Setting.Out said:
Wrong device thread..
Try here..
https://forum.xda-developers.com/showthread.php?t=2363923
Click to expand...
Click to collapse
can you help me in rooting Qmobile x32
Q-mobile said:
can you help me in rooting Qmobile x32
Click to expand...
Click to collapse
That thread didn't help?
Here's what the guide says...
Hi guys,
a week ago my ZUK Z1 started to bootloop without any evident reason.
I found it in this state picking it up from my pocket, so I guessed it was due to some random reboot that occasionally happened to it.
So, stating that:
- I'm with original stock CyanogenOS,
- I never rooted, or even accessed to the recovery menu prior to this event,
- I'm perfectly able now to communicate and send commands to device via adb or in fastboot mode,
problem is that I did NOT enable "USB debugging" and I did NOT OEM unlock when I had the chance to reach Developer options menu through the Android GUI (now I'm blocked by bootloop), resulting in an obvious "no unlocked device" error message each time I try to flash or write system partitions.
The output from "fastboot oem get-info" confirms this status.
I'm operating from a shell with adiministrator's grant in Windows 8.
No luck with "fastboot oem unlock", "fastboot flashing unlock_critical" or "adb root".
I used also "-i 0x2b4c" (vendor code) option in my commands.
Then, my question for you:
is there still a way to unlock bootloader in order to recover with CyanogenOS stock image, in this condition?
I saw there's a "debuggable" image on Cyanogen site, but I've no hint on how to use it and if it could help me.
Maybe ZUK has to provide to me an unlock key: I read on this forum that OnePlus and Huawei have similar option.
Thanks a lot in advance for any hint and suggestion you can give to me.
---------- Post added at 05:43 PM ---------- Previous post was at 05:43 PM ----------
[/COLOR]
dalviking said:
Hi guys,
a week ago my ZUK Z1 started to bootloop without any evident reason.
I found it in this state picking it up from my pocket, so I guessed it was due to some random reboot that occasionally happened to it.
So, stating that:
- I'm with original stock CyanogenOS,
- I never rooted, or even accessed to the recovery menu prior to this event,
- I'm perfectly able now to communicate and send commands to device via adb or in fastboot mode,
problem is that I did NOT enable "USB debugging" and I did NOT OEM unlock when I had the chance to reach Developer options menu through the Android GUI (now I'm blocked by bootloop), resulting in an obvious "no unlocked device" error message each time I try to flash or write system partitions.
The output from "fastboot oem get-info" confirms this status.
I'm operating from a shell with adiministrator's grant in Windows 8.
No luck with "fastboot oem unlock", "fastboot flashing unlock_critical" or "adb root".
I used also "-i 0x2b4c" (vendor code) option in my commands.
Then, my question for you:
is there still a way to unlock bootloader in order to recover with CyanogenOS stock image, in this condition?
I saw there's a "debuggable" image on Cyanogen site, but I've no hint on how to use it and if it could help me.
Maybe ZUK has to provide to me an unlock key: I read on this forum that OnePlus and Huawei have similar option.
Thanks a lot in advance for any hint and suggestion you can give to me.
Click to expand...
Click to collapse
Sideload the official stock rom with zuk z1 tool. That s how i managed to un-brick my zuk. Download the stock rom , cm-12.1-YOG4PAS3OH-ham-signed.zip from this page https://cyngn.com/support. Use the toolkit provided here : http://forum.xda-developers.com/zuk-...alpha-t3235964 to sideload the rom. Wait until the phone restarts and thats it. You must also install adb and fastboot and have adb driver installed.I used the shenqi adb composite driver, but i guess the universal adb driver can work too. I had the same problem. Stuck in bootloop with USB debugging not enabled and bootloader locked.
Or you can try to fastboot the stock rom with the command provided in this useful tool.
Extentho said:
---------- Post added at 05:43 PM ---------- Previous post was at 05:43 PM ----------
[/COLOR]
Sideload the official stock rom with zuk z1 tool. That s how i managed to un-brick my zuk. Download the stock rom , cm-12.1-YOG4PAS3OH-ham-signed.zip from this page https://cyngn.com/support. Use the toolkit provided here : http://forum.xda-developers.com/zuk-...alpha-t3235964 to sideload the rom. Wait until the phone restarts and thats it. You must also install adb and fastboot and have adb driver installed.I used the shenqi adb composite driver, but i guess the universal adb driver can work too. I had the same problem. Stuck in bootloop with USB debugging not enabled and bootloader locked.
Or you can try to fastboot the stock rom with the command provided in this useful tool.
Click to expand...
Click to collapse
Thanks a lot Extentho for your feedback.
I've already tried your fair suggestion: unfortunately, I'm stuck at the end of sideloading the signed .zip.
In fact, I see on screen logs that it's applying the update "unconditionally" (that sounds good), but nevertheless, when finished it returns "xfer: 1.00x" on PC shell and in recovery menu, on device.
Now, either if I reboot or power down and boot it again, the result is the same: still bootloop-ing.
Of course, at any other attempts leveraging on administrative privilege, it says that "device is locked", including those done through the shell tool.
Some excerpts from my last launched commands:
c:\_APP\CM>adb devices
List of devices attached
51f8941d sideload
c:\_APP\CM>adb shell
error: closed
c:\_APP\CM>adb kill-server
c:\_APP\CM>adb root
error: closed
c:\_APP\CM>adb kill-server
c:\_APP\CM>adb usb
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: closed
c:\_APP\CM>adb kill-server
c:\_APP\CM>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
51f8941d sideload
c:\_APP\CM>adb sideload cm-12.1-YOG4PAS3OH-ham-signed.zip
Total xfer: 1.00x
You must have the phone in sideload mode. There is an option to sideload in recovery menu.
Then use the command to sideload from the toolkit. The stock rom must pe renamed sideload and placed on desktop.
If the phone communicates in any way with pc, there is still hope. When you start the sideload process from pc, the phone should show an animation showing the flashing process. Post some pictures from where you are stuck, so i can make an idea about what is going on
my zuk z1 stuck to bootloop,
and android debugging is disabled.
phone can not detecting in fastboot mode.
please help.
Extentho said:
You must have the phone in sideload mode. There is an option to sideload in recovery menu.
Then use the command to sideload from the toolkit. The stock rom must pe renamed sideload and placed on desktop.
If the phone communicates in any way with pc, there is still hope. When you start the sideload process from pc, the phone should show an animation showing the flashing process. Post some pictures from where you are stuck, so i can make an idea about what is going on
Click to expand...
Click to collapse
I've tried also with the toolkit, but it's heavy bugged (also in 5.4 version) and, after all, it gets the exact same problem like me (not surprising, it launches my same commands ).
There's no useful image or snapshot I can share, because I see the animated green android logo moving its antennas on my device, while logs below saying that it's verifying package and then it's unconditionally overwriting system partition.
It seems all so normal and plain.
At the end of the process, no "installation complete" message, but simply I get back to recovery menu (where I started from).
In other attempts, I also wiped cache and user data, prior to rebooting, just to test if it was going to change something, but no luck.
The phone reboots, the "Cyanogen" logo starts to glow for 7/8 times and then... bzzzz, short vibration and all over again (i.e. bootloop).
I tried with an older official signed .zip from Cyanogen OS (cm-12.1-YOG4PAS3AJ-ham-signed, instead of newer cm-12.1-YOG4PAS3OH-ham-signed), but even worst, it fails at "verify package" step, aborting procedure.
MD5 signatures triple-checked each time versus source.
I saw some threads where it seems possible to change the bit, on system image, controlling developer option, to manually post-enable unlocking, but it's suitable only for Nexus or OnePlus One. No instructions for ZUK Z1.
Or maybe do I need a "donor" sharing a stock .zip with this option yet enabled?
Bootloop would be still there, but I possibly could enable to "flash", "boot" and "shell" vs the device, giving me much more options to try.
One last doubt anyway. If I press "Volume Down" + "Power" button at boot, I get into a menu like this:
http: // postimg.org/image/s5badiefh/ (remove extra spaces).
Viewing other examples posted on forums, I noted that at least the "Factory reset" is missing.
Could it be an hint for anything useful?
dalviking said:
I've tried also with the toolkit, but it's heavy bugged (also in 5.4 version) and, after all, it gets the exact same problem like me (not surprising, it launches my same commands ).
There's no useful image or snapshot I can share, because I see the animated green android logo moving its antennas on my device, while logs below saying that it's verifying package and then it's unconditionally overwriting system partition.
It seems all so normal and plain.
At the end of the process, no "installation complete" message, but simply I get back to recovery menu (where I started from).
In other attempts, I also wiped cache and user data, prior to rebooting, just to test if it was going to change something, but no luck.
The phone reboots, the "Cyanogen" logo starts to glow for 7/8 times and then... bzzzz, short vibration and all over again (i.e. bootloop).
I tried with an older official signed .zip from Cyanogen OS (cm-12.1-YOG4PAS3AJ-ham-signed, instead of newer cm-12.1-YOG4PAS3OH-ham-signed), but even worst, it fails at "verify package" step, aborting procedure.
MD5 signatures triple-checked each time versus source.
I saw some threads where it seems possible to change the bit, on system image, controlling developer option, to manually post-enable unlocking, but it's suitable only for Nexus or OnePlus One. No instructions for ZUK Z1.
Or maybe do I need a "donor" sharing a stock .zip with this option yet enabled?
Bootloop would be still there, but I possibly could enable to "flash", "boot" and "shell" vs the device, giving me much more options to try.
One last doubt anyway. If I press "Volume Down" + "Power" button at boot, I get into a menu like this:
http: // postimg.org/image/s5badiefh/ (remove extra spaces).
Viewing other examples posted on forums, I noted that at least the "Factory reset" is missing.
Could it be an hint for anything useful?
Click to expand...
Click to collapse
For me, this method worked exactly as described, booting into stock rom correctly.
now, if you mentioned it in the picture, there is another option. so, i ve noticed too this menu. There is an app called QPST wich can help you. Follow this thread: http://forum.xda-developers.com/zuk-z1/help/bricked-zuk-z1-t3277257 .
So when you enter in QFIL, connect the phone to computer and boot with volume down+ power into this menu from your picture. The Qfil app should detect some ports. You must choose the 9008 one, from what i have read.
Anyway, for me this method, didn t work because the pc couldn t detect the right port, only the zuk tookit did it for me.
You read the thread i suggested, and try that method, it may work for you.
Extentho said:
For me, this method worked exactly as described, booting into stock rom correctly.
now, if you mentioned it in the picture, there is another option. so, i ve noticed too this menu. There is an app called QPST wich can help you. Follow this thread: http://forum.xda-developers.com/zuk-z1/help/bricked-zuk-z1-t3277257 .
So when you enter in QFIL, connect the phone to computer and boot with volume down+ power into this menu from your picture. The Qfil app should detect some ports. You must choose the 9008 one, from what i have read.
Anyway, for me this method, didn t work because the pc couldn t detect the right port, only the zuk tookit did it for me.
You read the thread i suggested, and try that method, it may work for you.
Click to expand...
Click to collapse
Thanks again Extentho.
I saw QPST trick, but it's not catching right port and/or not getting right permission to stop phone from re-booting.
I think that adb/toolkit method should work also for me. I made attempts with other official ROMs: I noticed that for the older ones, the result is a bit different. They get stuck in a "black screen + notify led lighted in blue" state, rather than bootlooping.
Maybe erasing system partitions is needed, but I'm very reluctant to such dangerous way, without expertised advice.
Weirdest thing is that I did anything to get this situation, I just found my device in this mess.
Of course ZUK official support is well silent at my requests.
dalviking said:
Thanks again Extentho.
I saw QPST trick, but it's not catching right port and/or not getting right permission to stop phone from re-booting.
I think that adb/toolkit method should work also for me. I made attempts with other official ROMs: I noticed that for the older ones, the result is a bit different. They get stuck in a "black screen + notify led lighted in blue" state, rather than bootlooping.
Maybe erasing system partitions is needed, but I'm very reluctant to such dangerous way, without expertised advice.
Weirdest thing is that I did anything to get this situation, I just found my device in this mess.
Of course ZUK official support is well silent at my requests.
Click to expand...
Click to collapse
Try to post some pics about the troubles you encounter. If we receive a solution, this may be helpful for all of us in the future. Now, exactly, what can you acces on phone(recovery, fastboot, )?
Also, check varios threads from other phones with the same problems(one plus one, lg , htc) ,etc. Find a solved situation like yours, and we may adapt that solution to you
Hi guys,
Just to close this topic.
I was finally able to install the ZUI ROM through the QFIL program.
It's a little bit tricky, due to the fact that it is strongly suggested:
- to use a Windows 7 machine started without Signature Enforcement enabled;
- to start QFIL (admin mode) and be prepared with all needed files loaded in its GUI;
- to power off the phone, then, while pressing volume up button, inserting the USB cable, attached (better if) on a 2.0 port to PC;
- to be fast pressing "Download" button on QFIL program.
After that, I unlocked the bootloader and performed a lot of alternative recovery process.
So, I installed on the device:
- ZUI ROM
- Cyanogen OS convert from ZUI ROM
- Cyanogen OS last updated ROM
- CyanogenMod 12.1 last nightly ROM
- CyanogenMod 13.0 last nightly ROM
and the winner is...
...
...
...
... none of the above.
Each time the very same behaviour: bootloop. So, my last conclusion is: hardware failure (I guess wi-fi module).
I give up.
But for anyone searching a safe way to unlock a bootloader without accessing to developer options: the QFIL method works like a charm (once installed properly).
Thanks for support.
Messed my zuk z1
I tried to flash stock room in my zuk z1 , I downloaded Qualcomm file for the ROM and installed the required in my laptop,I wiped all data in my phone using TWRP .though my power button is not working I used tool kit to reboot my phone by connecting into fast boot mode,here comes the prob by mistake I entered the wrong command which locks my bootloader .I don't know what to do...help me.....
Hi all!
I've been researching this for the past few days. I recently dropped my Nexus 6P and it broke the LCD display. Google voice commands still work and I was able to unlock it with a USB OTG cable, so it appears that the only thing that's broken is the display. Of course, I didn't have USB debugging, Developer Mode, or it set up as an MTP device. I've only had the phone for a couple months so it's not a big deal but I would like to get my pictures back if at all possible. I know almost 0 things about android development, but am fairly tech savvy so I'm trying, here.
I have Android Development Studio with the Google USB Driver installed. Plugging the phone in via USB shows a "Nexus 6p" device with no files on it. I've gone through some tutorials but always get stuck at the "adb device" part.
I get the following from running commands:
Code:
C:\Android\Sdk\platform-tools>adb.exe devices
List of devices attached
C:\Android\Sdk\platform-tools>fastboot devices
XXXXXXXXXXXXXX fastboot
C:\Android\Sdk\platform-tools>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.031s
I think I am able to boot my device into recovery mode, but that hasn't helped as of yet.
Would appreciate any and all advice. Thanks for taking a look. Don't worry, I immediately set up my new phone in case I'm ever in this situation again. Take it from me... set it up now
OK so fastboot is for the bootloader and adb is for either recovery or the system itself.
You also won't type .exe after it either. Boot up your phone and unlock it then type "adb devices" into the command prompt. If that doesn't work (since you mentioned USB debugging is off) try from stock recovery. I'm honestly not 100% sure this will work TWRP is the 1st thing on my phone's. I don't mess with stock, but it's worth a shot. Reboot while holding volume up and it should bring you to stock recovery. Wait a few seconds and then hold the power button and quickly press and release volume up and then let go of both buttons. Do this plugged into a PC since when you enter the bootloader you get the little noise that plays. That way you know when it actually reboots and when to try the button combos. Now run "adb devices" again and it should show "XXXXXXXXXXXXXXXXX recovery"
From there just try adb pull.
"adb pull /storage/emulated/0 c:/Users/YourUserNameHere/Downloads"
Obviously in the path above, you'd enter your own username and entirely change the path to wherever you want your data saved. The above pull command will take your entire internal storage, all files if it works.
Hey Roy,
Thanks for posting. Still no luck getting it to show up on the device list. Followed your instructions and got a connected noise for the boot screen, then unconnected noise and connected noise again when I held the power button and pushed the volume up button, then released. So I think I got it into recovery mode but still no dice. Any other ideas on things I could try?
ahalbert said:
Hey Roy,
Thanks for posting. Still no luck getting it to show up on the device list. Followed your instructions and got a connected noise for the boot screen, then unconnected noise and connected noise again when I held the power button and pushed the volume up button, then released. So I think I got it into recovery mode but still no dice. Any other ideas on things I could try?
Click to expand...
Click to collapse
Sadly if you fully booted into stock recovery and adb still isn't working, I'm not sure there's a way to enable Android debugging at this point. Maybe someone else could chime in, but I think you'd need to get your screen replaced at a local repair shop.
RoyJ said:
Sadly if you fully booted into stock recovery and adb still isn't working, I'm not sure there's a way to enable Android debugging at this point. Maybe someone else could chime in, but I think you'd need to get your screen replaced at a local repair shop.
Click to expand...
Click to collapse
That's too bad. Thank you for the advice though!
So I looked around here and on the interwebz to find an answer to my question before I decided to state my question to you.
I just acquired the Sony Xperia X Compact (F5321; Android 7.1.1).
In order to get TWRP on it, I consulted a lot of online guides including those described here. Of which I thought this would be the most suitable:
https://forum.xda-developers.com/x-compact/development/recovery-twrp-3-1-1-xperia-x-compact-t3640914
So after:
having adb tools and fastboot incl. drivers (also tried the minimal)
developer options -- oem unlocking -- bootloader allowed to be unlocked; and developer options -- USB debugging -- debug mode when USB is connected
checking the service *#*#7378423#*#* , which shows "bootloader unlock allow : YES"
phone connected to PC
I encounter the following problem.
While the sony stock rom it comes with is running,
via adb I am able to feed the phone the following command with the respective outcome:
adb reboot fastboot (reboots into Android, with the LED lighting briefly up in red)
adb reboot recovery (reboots into Android, with the LED lighting briefly up in red)
adb reboot bootloader (boots down, but does not boot into Android; there is only a black screen and the LED is on and stays blue)
in any of those states, if I enter an adb command there is always this output as if the phone wasn't connected or recognized or off:
error: device '(null)' not found
So I am able to communicate commands to the phone when it is running. I assume this means my drivers are all in order, right?
Also. While it is off and disconnected from the PC.
I keep the power button and the volume down button pressed, the Sony Logo comes up and after that it takes turns with a black screen as long as I keep pressed.
I keep the power button and the volume up button pressed. It is followed by one short vibration, another short one, and the three in a row. And then no further reaction.
I feel pretty dumb, can anyone help me with how to enter any of the alternative boot options? Thanks in advance!
I just don't know if there is something I am not seeing or if there is plainly something wrong with the phone. Not knowing this for sure is driving me crazy. Hopefully this is something others might learn from, as well.
____________
little edit about the text format
From your description, it seems like TWRP was not installed correctly. But don't worry, on this phone you do not have to install the recovery to use it. You can boot straight into recovery from your PC while the phone is in 'fastboot' mode. The 'fastboot' mode is what you get when you do 'adb reboot bootloader'. The screen off, blue LED is signalling that the phone is ready for fastboot commands. You can then run:
Code:
fastboot boot <recovery image file>
The phone should load and run the recovery.
Please note that adb will not see your device while it is in fastboot mode. Likewise, fastboot does not work while the phone is accessible through adb. adb support comes from the ROM, but TWRP also supports adb, so you can also use adb while in TWRP.
Rendini said:
So I looked around here and on the interwebz to find an answer to my question before I decided to state my question to you.
I just acquired the Sony Xperia X Compact (F5321; Android 7.1.1).
In order to get TWRP on it, I consulted a lot of online guides including those described here. Of which I thought this would be the most suitable:
https://forum.xda-developers.com/x-compact/development/recovery-twrp-3-1-1-xperia-x-compact-t3640914
So after:
having adb tools and fastboot incl. drivers (also tried the minimal)
developer options -- oem unlocking -- bootloader allowed to be unlocked; and developer options -- USB debugging -- debug mode when USB is connected
checking the service *#*#7378423#*#* , which shows "bootloader unlock allow : YES"
phone connected to PC
I encounter the following problem.
While the sony stock rom it comes with is running,
via adb I am able to feed the phone the following command with the respective outcome:
adb reboot fastboot (reboots into Android, with the LED lighting briefly up in red)
adb reboot recovery (reboots into Android, with the LED lighting briefly up in red)
adb reboot bootloader (boots down, but does not boot into Android; there is only a black screen and the LED is on and stays blue)
in any of those states, if I enter an adb command there is always this output as if the phone wasn't connected or recognized or off:
error: device '(null)' not found
So I am able to communicate commands to the phone when it is running. I assume this means my drivers are all in order, right?
Also. While it is off and disconnected from the PC.
I keep the power button and the volume down button pressed, the Sony Logo comes up and after that it takes turns with a black screen as long as I keep pressed.
I keep the power button and the volume up button pressed. It is followed by one short vibration, another short one, and the three in a row. And then no further reaction.
I feel pretty dumb, can anyone help me with how to enter any of the alternative boot options? Thanks in advance!
I just don't know if there is something I am not seeing or if there is plainly something wrong with the phone. Not knowing this for sure is driving me crazy. Hopefully this is something others might learn from, as well.
____________
little edit about the text format
Click to expand...
Click to collapse
Switch the phone off.
To enter fastboot mode: Hold the Volume UP and connect your phone to the USB port of your PC. The blue LED should come on and provided you have correctly installed drivers, you will be able to use fastboot commands.
To enter bootloader/flashmode: Hold Volume DOWN button and plug USB cable to your PC. Green LED should lit up and provided you have correctly installed the drivers, you will be able to use Flashtool, Emma or other software to flash firmware files.
FAILED (remote: Command not allowed)
Hey guys!
First of all, thanks for taking the time!
So, confirming how to enter bootloader/flashmode is much appreciated, since I was very much in doubt about the fact that the screen stayed off. On other devices I always had something on the screen in recovery mode and the like.
Now I know it was problem with the drivers indeed. Also appreciated, the hint that adb and fastboot work separately. While the device was recognized by adb when it was turned on, it was not in fastboot mode because of missing drivers. Finally it is being recognized and I can address the device via fastboot command.
And yet, I have the next brick wall. Any command I send via fastboot is answered by this output:
Code:
FAILED (remote: Command not allowed)
up to this point, I have not found one command that is being acknowledged and triggers another output, so I think it is a general problem. Maybe still with the drivers. Any hints would be celebrated. Anyways, in the meantime I will keep on trying until I succeed or until I get too frustrated and send it back and never try Sony devices again
not kidding XD
Rendini said:
Hey guys!
First of all, thanks for taking the time!
So, confirming how to enter bootloader/flashmode is much appreciated, since I was very much in doubt about the fact that the screen stayed off. On other devices I always had something on the screen in recovery mode and the like.
Now I know it was problem with the drivers indeed. Also appreciated, the hint that adb and fastboot work separately. While the device was recognized by adb when it was turned on, it was not in fastboot mode because of missing drivers. Finally it is being recognized and I can address the device via fastboot command.
And yet, I have the next brick wall. Any command I send via fastboot is answered by this output:
Code:
FAILED (remote: Command not allowed)
up to this point, I have not found one command that is being acknowledged and triggers another output, so I think it is a general problem. Maybe still with the drivers. Any hints would be celebrated. Anyways, in the meantime I will keep on trying until I succeed or until I get too frustrated and send it back and never try Sony devices again
not kidding XD
Click to expand...
Click to collapse
because your bootloader is not unlocked. you have set your bootloader to allow unlocking in developers options, but you need to do the actual unlock using "fastboot unlock" command. you need a unique unlock code from Sony Developers portal and keep in mind that unlocking your device irrevocably deletes DRM keys. it is advisable that you backup your DRM keys before unlocking your device.
the problem is not Sony device, but your unability to read and follow guides and get yourself informed and educated before you dive into trial and error, finaly blaming manufacturer for your own faults...
Hello! I don't know if there might a be a solution for this problem, we've tried many stuff that's been posted here on the forums but ended up in the same results, so no luck. My friend's Moto G5 Plus "bricked" itself while updating to Oreo some time ago, wasn't rooted or anything, bootloader wasn't unlocked either. We can access the recovery menu with "power + vol+", but any option we try to use ends up with the message "Failed to pass validation, backup to fastboot". Some of the solutions I've tried require the bootloader to be unlocked, but I haven't been able to unlock it since my friend never checked the "Allow OEM unlock" option. He took the phone to the official service but they said they couldn't do anything and wanted to sell him a new phone. Any help is appreciated. Thanks in advance!
ZSparda said:
Hello! I don't know if there might a be a solution for this problem, we've tried many stuff that's been posted here on the forums but ended up in the same results, so no luck. My friend's Moto G5 Plus "bricked" itself while updating to Oreo some time ago, wasn't rooted or anything, bootloader wasn't unlocked either. We can access the recovery menu with "power + vol+", but any option we try to use ends up with the message "Failed to pass validation, backup to fastboot". Some of the solutions I've tried require the bootloader to be unlocked, but I haven't been able to unlock it since my friend never checked the "Allow OEM unlock" option. He took the phone to the official service but they said they couldn't do anything and wanted to sell him a new phone. Any help is appreciated. Thanks in advance!
Click to expand...
Click to collapse
Would be helpful to know what exactly you've done to rescue that device.
For example, did you try to wipe the complete device and fastboot flash the latest signed Oreo firmware?
Is the device recognised by a PC?
What about using Lenovo Motorola Smart Assistant?
Wolfcity said:
Would be helpful to know what exactly you've done to rescue that device.
For example, did you try to wipe the complete device and fastboot flash the latest signed Oreo firmware?
Is the device recognised by a PC?
What about using Lenovo Motorola Smart Assistant?
Click to expand...
Click to collapse
Hey! From what he told me, at first he was able to access the recovery menu, when then little Android with the red mark shows up, then he used the Smart Assistant and after that he gets the validation error message that I mentioned. I suppose the Smart Assistant made things worse? The device was initially recognised by the PC, but now it isn't. We tried to flash the stock firmware and unlock the bootloader but we didn't have any luck either. Since the PC didn't recognized it anymore we tried a few things to make it work but ended up giving up.
ZSparda said:
Hey! From what he told me, at first he was able to access the recovery menu, when then little Android with the red mark shows up, then he used the Smart Assistant and after that he gets the validation error message that I mentioned. I suppose the Smart Assistant made things worse? The device was initially recognised by the PC, but now it isn't. We tried to flash the stock firmware and unlock the bootloader but we didn't have any luck either. Since the PC didn't recognized it anymore we tried a few things to make it work but ended up giving up.
Click to expand...
Click to collapse
So you can't get to the screen with the dead android (fastboot mode) or recovery with the key combination (power and vol down/power and vol up)? You should be able to get there and check the connection by typing
fastboot devices
or
adb devices
Is the battery full enough to start?
Do you see the device in Windows devices manager?
PC should recognise it at very worst, as qhsusb_bulk. Your PC must be in test mode, and then when you connect look in device manager, under usb devices, and a hard bricked phone will show as qhsusb_bulk. Anything else, you should be able to communicate with ADB/fastboot, as Wolfcity stated. If it does show as qhsusb_bulk, you will need to use vaches' blankflash to recover the unit.
Wolfcity said:
So you can't get to the screen with the dead android (fastboot mode) or recovery with the key combination (power and vol down/power and vol up)? You should be able to get there and check the connection by typing
fastboot devices
or
adb devices
Is the battery full enough to start?
Do you see the device in Windows devices manager?
Click to expand...
Click to collapse
I tried to attach a couple of screenshots but I get the "bad request" message here. Anyways, when we do a normal boot we get the validation error message and we are sent directly to fastboot menu, but there we cannot choose any options because all of them lead to the error message again.
It's been a couple of weeks now but the last time we tried doing something, the device wasn't showing up in device administrator nor being recognized by adb.
As regards to the battery, we've left it charge up for some hours, so I guess that's not a problem, although we cannot see the percentage.
[email protected] said:
PC should recognise it at very worst, as qhsusb_bulk. Your PC must be in test mode, and then when you connect look in device manager, under usb devices, and a hard bricked phone will show as qhsusb_bulk. Anything else, you should be able to communicate with ADB/fastboot, as Wolfcity stated. If it does show as qhsusb_bulk, you will need to use vaches' blankflash to recover the unit.
Click to expand...
Click to collapse
I'll tell him to check if it shows up as qhsusb_bulk and update here. Could you explain a bit more or link to a thread about vache's blankflash? What is it exactly?
ZSparda said:
I'll tell him to check if it shows up as qhsusb_bulk and update here. Could you explain a bit more or link to a thread about vache's blankflash? What is it exactly?
Click to expand...
Click to collapse
This thread is long, but alot of good info on hard bricked Moto G5 plus devices.
Code:
https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457
To get PC in test mode
Code:
Here is how to turn on or off the Test Mode feature in Windows 10.
IMPORTANT: Please remember that turning off the Test Mode feature may force the program/driver which is not digitally signed stop working.
Step 1: Open Command Prompt as administrator. To do so, type CMD in Start menu search to see Command Prompt in the search result. Right-click on Command Prompt entry and then click Run as administrator option. Click Yes button when you see the User Account Control screen.
Step 2: At the Command Prompt window, execute the following commands:
To enable the Test Mode:
Bcdedit.exe -set TESTSIGNING ON
To disable the Test Mode:
Bcdedit.exe -set TESTSIGNING OFF
If the above command didn’t work, this one must work:
Bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS
Bcdedit.exe -set TESTSIGNING OFF
You may exit the Command Prompt now.
[email protected] said:
This thread is long, but alot of good info on hard bricked Moto G5 plus devices. To get PC in test mode
Click to expand...
Click to collapse
Thanks! I'll send him all these so he can try. I'll update as soon as possible.
[email protected] said:
This thread is long, but alot of good info on hard bricked Moto G5 plus devices. To get PC in test mode
Click to expand...
Click to collapse
Update: The PC detects the phone as Android Device > Mot Composite ADB Interface.
But once in adb, adb devices isn't working. It doesn't recognize the device.
ZSparda said:
Update: The PC detects the phone as Android Device > Mot Composite ADB Interface.
But once in adb, adb devices isn't working. It doesn't recognize the device.
Click to expand...
Click to collapse
It is recognizing the device, " Mot Composite ADB Interface" is correct.How about
Code:
fastboot devices
? It should show the device #. ADB doesn't always show devices.
[email protected] said:
It is recognizing the device, " Mot Composite ADB Interface" is correct.How about ? It should show the device #. ADB doesn't always show devices.
Click to expand...
Click to collapse
Yes! Fastboot devices shows the device! So now we have to procede with the flashblank.zip and all that from the other post right? Also sorry for the late reply, I've been pretty busy these past days so I left him with all the work.