Related
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?
25.11.2017 - Update: I've just used same tutorial to unlock Z5 6653 and it was success ! Good luck to everyone!
23.09.2021 - Files shared again by request. If any questions occur - write me.
This is solution that i used to unlock found device Xperia Z5 Premium, which was locked with fingerprint, bootloader is locked and FRP (google account security) is activated.
Dear friends, as everyone here, i must say USE THIS GUIDE ON YOUR OWN RISK ! ! !
I'm not responsible for bricked devices, if your dog unplug the cable or you lost electricity durring flashing!
First i want to say HUGE thanks to @YasuHamed !!! He knows why !
*to get in flash mode: press volume down and connect device to PC; - green notification LED
*to get in Fastboot mode: press volume up and connect device to PC; - blue notification LED
DOWNLOADS:
Xperia E6853 - Google Drive
drive.google.com
Xperia E6853 - Google Drive
drive.google.com
*I'm trying to share folder with unattended access, but google asks me everytime. Usually i respond fast, but do not hesitate to PM me if you have no access.
GUIDE:
1st you need Sony flashtool and drivers, and ADB fastboot.
-Download Sony Companion to have all sony drivers.
-Download Flashtool (flashtool-0.9.23.1-windows.exe) and install it.
-I updated Flashtool from 0.9.23.1 to 0.9.23.2. Simply download (x10flasher.jar) and replace existing file in C:/Flashtool/.
-Next download ADB fastboot (minimal_adb_fastboot_v1.4_setup.exe) and install it.
2nd i flashing another Android using Flashtool thru flash mode, for clean start of the device.
-Open Flashtool (C:/Flashtool/Flashtool.exe)
-Connect your device in flash mode.
-Click on the black XE button on the right end of the toolbar in FlashTool.
-Choose your device, choose region and customization and on the right side, bellow the picture of the phone you can see "Available Firmware:"
Here i've choose 1300-1579 Internal Promoter 32.0.A.6.170 / R2B. This is old 5.1.1 Android which allow you to get in to the phone menu itself and do the FRP Unlock.
-Click on the firmware , bellow phone picture, and download it.
-After it is downloaded, close that windows and on main window, will see in console that firmware is prapairing for flashing.
-Phone is still connected in flash mode, and flashing will start automaticly when firmware is ready.
Have patience! Prepairing and flashing took around 10 mins for my PC.
3rd Bypass FRP ( google account security lock)
-check FlashTool console if flashing status is DONE, and if it is, unplug your device and power it up.
-now download the video file ( Bypass Google Account SONY Xperia Z5 - How to Remove FRP Lock.mp4 ) and follow the steps as it is shown.
On the last step when you have to switch from GUEST to Owner user, my device just frozen on waiting screen, and after 5-6 minutes screen went disturbingly black, like it is dead and went OFF.
I power it up and voila, there was 2 steps to complete setting up of the new phone.
4. If you want you can unlock your bootloader now (if it is available by SONY) and use custom roms, root and etc.
-go to dialer and dial *#*#7378423#*#*
-tap Service info” go to “Configuration ” go to ” Rooting Status.
-if Boot loader unlock allowed says ” Yes” then you can follow below guide. If it says NO - sorry, you can't unlock your bootloader.
-you need your IMEI number, You can check it in settings menu or dial *#06#.
-turn on OEM Unlocking and USB debugging options in Settings > Developer options. (To enable Developer options menu, go to Settings > About phone , and tap several times on Build number.)
-switch off your Sony Xperia Z5 Premium by pressing power button.
-now connect phone in fastboot mode. To do so, you must hold Volume UP and plug device to PC.
-next go to https://developer.sonymobile.com/unlockbootloader/ and finish the steps using your IMEI to get unlock KEY from Sony.
When you have the key, you will see instructions on the same site, what command you have to use in fastboot ADB. To get in Fastboot ADB:
-on your PC go to the folder (C:/adb/) where you installed minimal ADB and fastboot, hold shift + Right click, choose Open command window here.
-check if device is propperly connected. Write in CMD : fastboot devices . Your device should be listed there if it is connected in fastboot mode.
-now you have to write the command, same as on Sony site with the key: fastboot -i 0x0fce oem unlock 0x“your unlock code”.
example : – fastboot -i 0x0fce oem unlock 0x87eb234h6212g5646
-If it says OK [time] finished , you are done well.
After bypass FRP you can flash Android 7.0, there is no problem or security issues.
I've used those guides:
https://forum.xda-developers.com/xperia-z/general/tutorial-how-to-flash-stock-roms-t2240614
http://www.gogorapid.com/unlock-bootloader-sony-xperia-z5-premium/
this is very well xplained tutorial.
i have book marked it and will be referencing it in future
best of luck
FRM Bypass Not Working with Nougat
YasuHamed said:
this is very well xplained tutorial.
i have book marked it and will be referencing it in future
best of luck
Click to expand...
Click to collapse
Guide is awesome. Only problem now, bypassing the Google account video does not work with Nougat which is what the flashtool downloaded by default for me.
Is there any other way please?
EDIT UPDATE: I found a way with another video on YouTube. Maybe could use this one also to update your guide. It worked for me. I thank you once again for this awesome guide, helping me to reset this phone.
https://www.youtube.com/watch?v=PdSo5hkB7SI
KayCee-Kepz said:
Guide is awesome. Only problem now, bypassing the Google account video does not work with Nougat which is what the flashtool downloaded by default for me.
Is there any other way please?
EDIT UPDATE: I found a way with another video on YouTube. Maybe could use this one also to update your guide. It worked for me. I thank you once again for this awesome guide, helping me to reset this phone.
https://www.youtube.com/watch?v=PdSo5hkB7SI
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=A5ok_s8zxKc
Not working
I bought a phone that was damaged and I repaired it. It has the google frp lock all the guides so far dont work. It is on android 7 and I am stumped how to get passed this can you help?
mintminty59 said:
I bought a phone that was damaged and I repaired it. It has the google frp lock all the guides so far dont work. It is on android 7 and I am stumped how to get passed this can you help?
Click to expand...
Click to collapse
Read 2nd step in instructions! First of all you have to downgrade the Android version !
thanks for bootloader unlocking method. For frp bypass you can follow this guide ~ http://www.frpghost.com/2017/03/sony-xperia-frp-unlock.html
My bootloader cannot be unlocked via Sony as my rooting status says NO. (Phone has Android 7.1.1) so even with your instructions I cannot root the phone and or downgrade to Android v7.0. Is this correct?
---------- Post added at 03:33 AM ---------- Previous post was at 03:31 AM ----------
grosseader said:
25.11.2017 - Update: I've just used same tutorial to unlock Z5 6653 and is was success ! Good luck to everyone!
This is solution that i used to unlock found device Xperia Z5 Premium, which was locked with fingerprint, bootloader is locked and FRP (google account security) is activated.
Dear friends, as everyone here, i must say USE THIS GUIDE ON YOUR OWN RISK ! ! !
I'm not responsible for bricked devices, if your dog unplug the cable or you lost electricity durring flashing!
First i want to say HUGE thanks to @YasuHamed !!! He knows why !
*to get in flash mode: press volume down and connect device to PC; - green notification LED
*to get in Fastboot mode: press volume up and connect device to PC; - blue notification LED
DOWNLOADS:
https://drive.google.com/open?id=0ByQNHZjTS8SNWDdDTkpCUDFfSGM
GUIDE:
1st you need Sony flashtool and drivers, and ADB fastboot.
-Download Sony Companion to have all sony drivers.
-Download Flashtool (flashtool-0.9.23.1-windows.exe) and install it.
-I updated Flashtool from 0.9.23.1 to 0.9.23.2. Simply download (x10flasher.jar) and replace existing file in C:/Flashtool/.
-Next download ADB fastboot (minimal_adb_fastboot_v1.4_setup.exe) and install it.
2nd i flashing another Android using Flashtool thru flash mode, for clean start of the device.
-Open Flashtool (C:/Flashtool/Flashtool.exe)
-Connect your device in flash mode.
-Click on the black XE button on the right end of the toolbar in FlashTool.
-Choose your device, choose region and customization and on the right side, bellow the picture of the phone you can see "Available Firmware:"
Here i've choose 1300-1579 Internal Promoter 32.0.A.6.170 / R2B. This is old 5.1.1 Android which allow you to get in to the phone menu itself and do the FRP Unlock.
-Click on the firmware , bellow phone picture, and download it.
-After it is downloaded, close that windows and on main window, will see in console that firmware is prapairing for flashing.
-Phone is still connected in flash mode, and flashing will start automaticly when firmware is ready.
Have patience! Prepairing and flashing took around 10 mins for my PC.
3rd Bypass FRP ( google account security lock)
-check FlashTool console if flashing status is DONE, and if it is, unplug your device and power it up.
-now download the video file ( Bypass Google Account SONY Xperia Z5 - How to Remove FRP Lock.mp4 ) and follow the steps as it is shown.
On the last step when you have to switch from GUEST to Owner user, my device just frozen on waiting screen, and after 5-6 minutes screen went disturbingly black, like it is dead and went OFF.
I power it up and voila, there was 2 steps to complete setting up of the new phone.
4. If you want you can unlock your bootloader now (if it is available by SONY) and use custom roms, root and etc.
-go to dialer and dial *#*#7378423#*#*
-tap Service info” go to “Configuration ” go to ” Rooting Status.
-if Boot loader unlock allowed says ” Yes” then you can follow below guide. If it says NO - sorry, you can't unlock your bootloader.
-you need your IMEI number, You can check it in settings menu or dial *#06#.
-turn on OEM Unlocking and USB debugging options in Settings > Developer options. (To enable Developer options menu, go to Settings > About phone , and tap several times on Build number.)
-switch off your Sony Xperia Z5 Premium by pressing power button.
-now connect phone in fastboot mode. To do so, you must hold Volume UP and plug device to PC.
-next go to https://developer.sonymobile.com/unlockbootloader/ and finish the steps using your IMEI to get unlock KEY from Sony.
When you have the key, you will see instructions on the same site, what command you have to use in fastboot ADB. To get in Fastboot ADB:
-on your PC go to the folder (C:/adb/) where you installed minimal ADB and fastboot, hold shift + Right click, choose Open command window here.
-check if device is propperly connected. Write in CMD : fastboot devices . Your device should be listed there if it is connected in fastboot mode.
-now you have to write the command, same as on Sony site with the key: fastboot -i 0x0fce oem unlock 0x“your unlock code”.
example : – fastboot -i 0x0fce oem unlock 0x87eb234h6212g5646
-If it says OK [time] finished , you are done well.
After bypass FRP you can flash Android 7.0, there is no problem or security issues.
I've used those guides:
https://forum.xda-developers.com/xperia-z/general/tutorial-how-to-flash-stock-roms-t2240614
https://www.youtube.com/watch?v=GmaK1bfiaTo
http://www.gogorapid.com/unlock-bootloader-sony-xperia-z5-premium/
Click to expand...
Click to collapse
My bootloader cannot be unlocked via Sony as my rooting status says NO. (Phone has Android 7.1.1) so even with your instructions I cannot root the phone and or downgrade to Android v7.0. Is this correct?
xectis said:
My bootloader cannot be unlocked via Sony as my rooting status says NO. (Phone has Android 7.1.1) so even with your instructions I cannot root the phone and or downgrade to Android v7.0. Is this correct?
Click to expand...
Click to collapse
You should be able to flash OE rom and downgrade using 2nd step!
What you want to to ? Bypass FRP ? root? or ?
4. If you want you can unlock your bootloader now (if it is available by SONY) and use custom roms, root and etc.
-go to dialer and dial *#*#7378423#*#*
-tap Service info” go to “Configuration ” go to ” Rooting Status.
-if Boot loader unlock allowed says ” Yes” then you can follow below guide. If it says NO - sorry, you can't unlock your bootloader.
Click to expand...
Click to collapse
This is what I don't get it, my Z5P says NO in bootloader, so even so, can I do this process to unlock? or definitely i can't unlock it in any way
I haven't started the process yet, because first I would like to know if I can still unlock it with this process even if it says no in the configuration menu.... I'm still on 7.1
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.
Hi !
I need your help please, my phone doesn't want to enter in fastboot mode.
* Black Screen 100%
* If I press power button after 4 or 5 seconds it does a vibration
* Power button + Volume Up (looks llike it turn off the phone)
* Power button + Volume Down (looks like it want to enter in fastboot mode)
When my phone is connected to the PC it is recognized as: Unknown USB Device ( Device Descriptor Request Failed )
Blue LED always turned on (once the phone is recognized as Unknown)
The first that I tought when I saw the message ( Unknown USB Device ) was... ok this phone is really hard bricked and is needing a Test Point.
I did the Test point and my phone still giving the same message.
I tried different USB ports and same problem. (USB ports are ok)
I didn't tried a different USB cable and it has higher probabilities that my USB could be damaged. because (Device Descriptor Failed) is a problem from faulty USB ports or Cable.
But my USB Cable looks like new and it was used few times... also I tried moving a bit the connectors to see if it does something but no.. nothing happened.
The USB Port from the phone is like new. (I opened the phone)
If you have experience with the message: "Unknown USB Device (Descriptor Request Failed)
Please give me some help !
Hi !
Looks like the real problem was from drivers. Finally I installed the K20 drivers from this site : https://gsmusbdriver.com/xiaomi-redmi-k20
Then I did the test point
1) I Pressed power button with the test point
2) I heard a vibration
3) I released the power button but I continued with the test point
4) Voila the drivers were installed correctly and now my phone is recognized as: " Qualcomm HS-USB QDLoader 9008 "
EDITED:
If you are experiencing in device manager: USB Device Unknown Descriptor Request Failed maybe could be faulty USB port or cable. In my case was the cable. Now is working perfectly everything with a new USB Cable.
Now I'm trying to flash the phone using " Mi Flash Tool "
I downloaded the stock rom from Xiaomi site.. By the way my phone is with bootloader locked and is not rooted.
I pressed Flash button and the program asked for EDL Authentication. "I Created a new account" Logged suscessfull and then:
"Error" Root Element is missing.
WTF? why xiaomi is asking me for a rooted phone??
Please Help, any Idea about what I'm doing wrong?
romeosantos said:
Now I'm trying to flash the phone using " Mi Flash Tool "
I downloaded the stock rom from Xiaomi site.. By the way my phone is with bootloader locked and is not rooted.
I pressed Flash button and the program asked for EDL Authentication. "I Created a new account" Logged suscessfull and then:
"Error" Root Element is missing.
WTF? why xiaomi is asking me for a rooted phone??
Please Help, any Idea about what I'm doing wrong?
Click to expand...
Click to collapse
I think EDL is a special account authorised by Xiaomi.
Enviado do meu Mi 9T através do Tapatalk
Yeah u need a EDL Flash and for that an EDL verified Account, which u can't get anymore from xiaomi ..
you have to find someone who are willing to do it for you. Usually you have to pay for it .. around $50.
or try this
https://forum.xda-developers.com/showpost.php?p=79004670&postcount=82
solved said:
Yeah u need a EDL Flash and for that an EDL verified Account, which u can't get anymore from xiaomi ..
you have to find someone who are willing to do it for you. Usually you have to pay for it .. around $50.
or try this
https://forum.xda-developers.com/showpost.php?p=79004670&postcount=82
Click to expand...
Click to collapse
I went to S-Unlock and they said "Service offline" do you know or somebody know from other site? or someone that can help me?
romeosantos said:
I went to S-Unlock and they said "Service offline" do you know or somebody know from other site? or someone that can help me?
Click to expand...
Click to collapse
Did you try this :
- Download the stock ROM from xiaomi website, no tools needed, just adb and fastboot installed
- Extract the rom to a folder and launch "flash_all.bat" with admin.
- If you encounter an issue try it with another OS (try this if you don't want to install another OS : https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755)
Tell us if it works.
Gimlouuuu said:
Did you try this :
- Download the stock ROM from xiaomi website, no tools needed, just adb and fastboot installed
- Extract the rom to a folder and launch "flash_all.bat" with admin.
- If you encounter an issue try it with another OS (try this if you don't want to install another OS : https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755)
Tell us if it works.
Click to expand...
Click to collapse
Good news? I think that my phone now is booting on Fastboot mode? I don´t know how but today it was recognized by the PC as:
MTP USB Device
Please help What I can do to flash my phone¿? it is fastboot mode right? in fastboot mode I can do flash without an account authenticated righT?
Im trying to use Mi Flash TOOL again and Im getting this message:
fed4e139]:info1:$for /F "tokens=2 delims=: " %i in ('fastboot -s fed4e139 getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
Im using the latest rom for the K20 global phone but dont know why it is stuck with that message and STATUS: Flashing but it doesnt do any progress.
What Can I do?? is ok MTP USB Device? is that the correct drivers to do a flash in fastboot mode??
Thanks guys!
romeosantos said:
Good news? I think that my phone now is booting on Fastboot mode? I don´t know how but today it was recognized by the PC as:
MTP USB Device
Please help What I can do to flash my phone¿? it is fastboot mode right? in fastboot mode I can do flash without an account authenticated righT?
Im trying to use Mi Flash TOOL again and Im getting this message:
fed4e139]:info1:$for /F "tokens=2 delims=: " %i in ('fastboot -s fed4e139 getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
Im using the latest rom for the K20 global phone but dont know why it is stuck with that message and STATUS: Flashing but it doesnt do any progress.
What Can I do?? is ok MTP USB Device? is that the correct drivers to do a flash in fastboot mode??
Thanks guys!
Click to expand...
Click to collapse
Does the phone display the fastboot logo? If it does, then you have to remove some lines from the flash_all.bat file. The first ones where it says something about getvar product.
you can fastboot and just push it in cmd if fastboot active. I bever use bat files, because its only 2 lines to flash
yaro666 said:
you can fastboot and just push it in cmd if fastboot active. I bever use bat files, because its only 2 lines to flash
Click to expand...
Click to collapse
This is what happened:
I was watching my phone recognized as MTP USB Device and I tought yeah! my luck is from my side! now will be possible to flash my pohne in fastboot mode !!
I tried a lot of times with FLASH TOOL and it never passed from:
fed4e139]:info1:$for /F "tokens=2 delims=: " %i in ('fastboot -s fed4e139 getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
then I tried in adb: "adb devices" but I never saw my device connected even with MTP USB Device driver activated in Device Manager.
so I tried anyway to use the flash_all.bat and same message received "getvar anti" bla bla..
I never deleted the lines about getvar from the file "flash_all.bat" because now my phone it is exactly as in the begin....
Now the PC doesn't want to recognize the phone... again the same ****.. " USB Device Unknown (Descriptor Request Failed) "
I did the test point and the same crap... the phone doesn't want to be recognized USB Unknown...
Come on... I can't believe it... I had decided to pay for the service flash with EDL authentication in the next week and now I can't even make it boot in EDL... exactly as in the begin I'm.... the phone it is with the same sympthoms.. :crying:
EDITED:
Now the Phone was recognized by the PC again as: MTP USB Device but with yellow sign..
I disconnected, reconnected the cable and nothing yellow sign.
I did the test point and boom Im back again into the same ****... USB UNknown (Descriptor Request Failed)
what the **** is happening?? Im not so sure how the phone can be recognized as MTP USB Device but i guess that it is fastboot mode. and that is what I want to try the solution from the first post of this threads.
or the second solution understand what I have to do to put the phone into EDL. Because I did a lot of times with sucess at the begin and now Im doing exactly the same and nothing. it doesnt want to work.
Looks like drivers problem?
romeosantos said:
This is what happened:
I was watching my phone recognized as MTP USB Device and I tought yeah! my luck is from my side! now will be possible to flash my pohne in fastboot mode !!
I tried a lot of times with FLASH TOOL and it never passed from:
fed4e139]:info1:$for /F "tokens=2 delims=: " %i in ('fastboot -s fed4e139 getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
then I tried in adb: "adb devices" but I never saw my device connected even with MTP USB Device driver activated in Device Manager.
so I tried anyway to use the flash_all.bat and same message received "getvar anti" bla bla..
I never deleted the lines about getvar from the file "flash_all.bat" because now my phone it is exactly as in the begin....
Now the PC doesn't want to recognize the phone... again the same ****.. " USB Device Unknown (Descriptor Request Failed) "
I did the test point and the same crap... the phone doesn't want to be recognized USB Unknown...
Come on... I can't believe it... I had decided to pay for the service flash with EDL authentication in the next week and now I can't even make it boot in EDL... exactly as in the begin I'm.... the phone it is with the same sympthoms.. :crying:
EDITED:
Now the Phone was recognized by the PC again as: MTP USB Device but with yellow sign..
I disconnected, reconnected the cable and nothing yellow sign.
I did the test point and boom Im back again into the same ****... USB UNknown (Descriptor Request Failed)
what the **** is happening?? Im not so sure how the phone can be recognized as MTP USB Device but i guess that it is fastboot mode. and that is what I want to try the solution from the first post of this threads.
or the second solution understand what I have to do to put the phone into EDL. Because I did a lot of times with sucess at the begin and now Im doing exactly the same and nothing. it doesnt want to work.
Looks like drivers problem?
Click to expand...
Click to collapse
Most likely. I had similar issues with a rn7. Try it on another pc. I had issues getting the phone recognized in w10, then I switched to an old laptop I had with w7. Didn't install drivers, didn't do anything, windows installed it's driver and the phone was there. So it may be a issue with your OS. And again, delete the first two lines from the flash_all.bat to get over that error.
Edit: The flashing with MiFlash tool will only work if you see the fastboot logo on your phone. If the phone is seen in cmd after you type "fastboot devices".
attitude12 said:
Most likely. I had similar issues with a rn7. Try it on another pc. I had issues getting the phone recognized in w10, then I switched to an old laptop I had with w7. Didn't install drivers, didn't do anything, windows installed it's driver and the phone was there. So it may be a issue with your OS. And again, delete the first two lines from the flash_all.bat to get over that error.
Edit: The flashing with MiFlash tool will only work if you see the fastboot logo on your phone. If the phone is seen in cmd after you type "fastboot devices".
Click to expand...
Click to collapse
Thanks for the answer, I have the notebook with two windows.
W10 64 bits and W7 32 Bits.
Same problem in both, don't know how can be driver problem, because I installed exactly the correct versión. (I know that is the correct because I could do the test point correctly two days ago) and it was recognized as: "Qualcomm HS-USB QDloader 9008 (COM4)" But today it doesnt want to recognize anymore the phone. Only "USB Device Unknown (Descriptor Request Failed)"
So hard is to make it boot in EDL mode? i saw the picture for test point (k20 xiaomi) and it is really easy. but PC recognize the phone as Unkonwn after test point. The first day that I did the test point happened the same ****.. I was hours and hours trying to make it work.. till I installed the correct drivers. and now is happening the same.. hours and hours trying to boot in EDL and using the same drivers, same process, but nothing.
Except at 3:00 pm dont know how the phone was recognized as MTP USB Device (with yellow sign error in device manager) so i did again the test point and boom.. USB Unknown again...
If I press Power button + volume up the phone looks like turn off and instantly I do the connection from usb cable and nothing appears in device manager but 2 mins or 3 mins later the phone is recognized as unknown and blue led light start to blink every 1 second.
If i do the test point it is recognized instantly as Unknown but there isnt any blue led light blinking.
I tried test point without battery and same. problem.. I tried to do the test point without release the pins so fast.. and same problem I tried releasing fast.. slow... etc
I tried to removed the battery and press power button to drain all the energy from board.
I tried to charging battery with power supply and the blue led light is turned on after 2 mins and it continue on over 10 or 15 mins then it is off the blue light. I used a tester to see the voltage from battery and is ok looks like it is full of charge.
If I do the EDL Cable could it be different? or is the same as test point?
Thanks for your help guys you are good people!
Have you tried with Linux? With the distribution I mentioned?
Gimlouuuu said:
Have you tried with Linux? With the distribution I mentioned?
Click to expand...
Click to collapse
Hi! Thanks for your help.
The problem was the usb cable. Now works perfectly with a new cable. But now I have to unbrick it hahaha
romeosantos said:
Hi! Thanks for your help.
The problem was the usb cable. Now works perfectly with a new cable. But now I have to unbrick it hahaha
Click to expand...
Click to collapse
great, good news. To unlock it, go back at my first message.
Gimlouuuu said:
great, good news. To unlock it, go back at my first message.
Click to expand...
Click to collapse
Hi! Thanks! Yes I tried to flash in fastboot mode. I did adb devices command and it was recognized ok.
But when I tried to flash_all.bat it gave me error: "bootloader locked" looks like I need the bootloader unlocked to flash via ADB in fastboot mode.
what I want to try is like a bug in xiaomi mi flash tool. The first time that I tried to use it. I made a new account and I received a message like:
"Logged Suscessfull"
"Your Account was blind to this PC. Now you can start the process"
Then I received an error like "no root permission" or something like that (maybe was because the usb cable was bad)
Looks like the xiaomi flash tool passed the EDL Authentication. because now each time that Im trying to use MI TOOL this is the message that Im getting.
"Logged Sucessfull"
You are not authorized for this operation
romeosantos said:
Hi! Thanks! Yes I tried to flash in fastboot mode. I did adb devices command and it was recognized ok.
But when I tried to flash_all.bat it gave me error: "bootloader locked" looks like I need the bootloader unlocked to flash via ADB in fastboot mode.
what I want to try is like a bug in xiaomi mi flash tool. The first time that I tried to use it. I made a new account and I received a message like:
"Logged Suscessfull"
"Your Account was blind to this PC. Now you can start the process"
Then I received an error like "no root permission" or something like that (maybe was because the usb cable was bad)
Looks like the xiaomi flash tool passed the EDL Authentication. because now each time that Im trying to use MI TOOL this is the message that Im getting.
"Logged Sucessfull"
You are not authorized for this operation
Click to expand...
Click to collapse
Ok, suddenly you can not reinstall via all these methods because your bootloader is locked... Have you tried asking a member here if anyone has an EDL account (a real haha) ?