I'm trying to unlock the bootloader but the phone doesn't stay in fastboot mode. Service menu rooting status says that unlocking bootloaders is allowed.
The LED turns orange after a few seconds of entering fast boot and the phone shows up a charging battery icon.
How do i fix this?
tvirus7 said:
I'm trying to unlock the bootloader but the phone doesn't stay in fastboot mode. Service menu rooting status says that unlocking bootloaders is allowed.
The LED turns orange after a few seconds of entering fast boot and the phone shows up a charging battery icon.
How do i fix this?
Click to expand...
Click to collapse
How are you entering fastboot mode? The LED should go blue for fastboot.
Also, you may need to reinstall the drivers.
Download and install flashtool, goto the driver folder in the installation path of flashtool (usually c:\flashtool) and run driver.exe
Choose TX, flashmode and fastboot drivers
flashtool z is perfect unlock relock bootloader
Comment allez-vous entrer dans le mode fastboot? La LED bleue devrait aller pour fastboot.
Aussi, vous devrez réinstaller les pilotes.
Téléchargez et installez Flashtool, allez dans le dossier du pilote dans le répertoire d'installation de Flashtool (généralement c: \ Flashtool) et courent driver.exe
Choisissez TX, flashmode et pilotes fastboot
link http://forum.xda-developers.com/showthread.php?t=2162907 perfect for unlock and relock !!!
English language only please.
Read the rules, if you post in non English you must provide an English translation
Sent from my star trek communicator
Sony Flagship device circa 2145
gregbradley said:
How are you entering fastboot mode? The LED should go blue for fastboot.
Also, you may need to reinstall the drivers.
Download and install flashtool, goto the driver folder in the installation path of flashtool (usually c:\flashtool) and run driver.exe
Choose TX, flashmode and fastboot drivers
Click to expand...
Click to collapse
The LED goes blue, yeah.
I'll try updating the drivers
gregbradley said:
English language only please.
Read the rules, if you post in non English you must provide an English translation
Click to expand...
Click to collapse
I think that guy just rewrote your words in French lol
gregbradley said:
English language only please.
Read the rules, if you post in non English you must provide an English translation
Sent from my star trek communicator
Sony Flagship device circa 2145
Click to expand...
Click to collapse
xrenoix said ...
"How to enter the fastboot way you? The blue LED should go to fastboot.
Also, you will need to reinstall the drivers.
Download and install Flashtool, go to the driver folder in the installation directory Flashtool (usually c: \ Flashtool) and run driver.exe
Choose TX, flashmode and fastboot drivers"
Yes, my limited French did get that he quoted me in French, but some puerile may have an even worse understanding of French than me...
Sent from my star trek communicator
Sony Flagship device circa 2145
Hello.
I would like to replace this old stock ROM Android 4.3 by an Android 10 custom ROM.
But already the first step makes problems: Unlocking the bootloader.
All descriptions in the internet seem to be deprecated cause they don't discuss a problem with command 'fastboot devices'.
Although 'adb devices' finds my mobile properly (when being booted in Android) - which confirms that my usb driver and adb installation is correct - 'fastboot devices' doesn't at all. I tried this now with a fastboot.exe version of 2021, of 2018 and also 2016. No chance!
So what is going on here? Does anybody know why JUST this fastboot commands are not working and so also not the necessary command 'fastboot oem unlock 0x<insert your unlock code>' ?
By the way I face the same problem as tvirus7: Unusually my Xperia V doesn't stay in fastboot mode after a start with volume up button. The blue LED - confirming fastboot mode - generally glows for just about 6 seconds before it changes back to orange. I don't know this from other Sony mobiles. Those stay in fastboot mode a long time without any timeout.
So are there even TWO problems here?...
Who can explain all that - and help?... As I am quite sure, everything is installed fine here and my mobile hardware is okay as well.
Related
my xperia z cant connect in fastboot anymore , right after I unlocked it .heres what my drivers look like.
https://docs.google.com/file/d/0B9_2y2HWWD2aZ1RmYi1NMm1kN2c/edit?usp=sharing
it says waiting for device .
9breaker said:
my xperia z cant connect in fastboot anymore , right after I unlocked it .heres what my drivers look like.
https://docs.google.com/file/d/0B9_2y2HWWD2aZ1RmYi1NMm1kN2c/edit?usp=sharing
it says waiting for device .
Click to expand...
Click to collapse
Just a question : Why do you have unlocked your bootloader? So many people unlock it for nothing, i'm sure i can do nearly same things with a locked bootloader, also with an unlocked bootloader you can't use PCC and SUS. Also unlocking bootloader avoid your warranty.
QualQuek said:
Just a question : Why do you have unlocked your bootloader? So many people unlock it for nothing, i'm sure i can do nearly same things with a locked bootloader, also with an unlocked bootloader you can't use PCC and SUS. Also unlocking bootloader avoid your warranty.
Click to expand...
Click to collapse
to flash cm 10.
9breaker said:
to flash cm 10.
Click to expand...
Click to collapse
Ok you got the point, you need an unlocked bootloader for a custom kernel.
So have you tried to restore it with PCC/SUS or Flashtool and retry? Maybe something haven't worked correctly the first time.
Do you have followed this thread http://forum.xda-developers.com/showthread.php?t=2153261 ?
This is after flashing the unlock token?
Can you power on the phone normally?
Are there any signs of life (LED indicator, screen backlight, vibration, etc.)?
QualQuek said:
Ok you got the point, you need an unlocked bootloader for a custom kernel.
So have you tried to restore it with PCC/SUS or Flashtool and retry? Maybe something haven't worked correctly the first time.
Do you have followed this thread http://forum.xda-developers.com/showthread.php?t=2153261 ?
Click to expand...
Click to collapse
I didn't flash anything the first time . i just unlocked the bootloader , i think the its a driver problem .when i plug it in in fastboot it says 'waiting for device' .the phone still works perfectly btw.
more info : Kernel 10.1.A.1.350 there's an update to .253 but I haven't installed it yet
9breaker said:
I didn't flash anything the first time . i just unlocked the bootloader , i think the its a driver problem .when i plug it in in fastboot it says 'waiting for device' .the phone still works perfectly btw.
more info : Kernel 10.1.A.1.350 there's an update to .253 but I haven't installed it yet
Click to expand...
Click to collapse
I can't tell exactly by your comments, but are you aware you need to start the phone in a different mode to access it via fastboot?
Disconnect USB
Hold Power & Volume Up until the phone vibrates three times in quick succession.
Let go of the buttons.
While holding Volume Up, connect USB cable between phone and computer.
The LED should turn blue to indicate you are in fastboot mode at which point you will need to install fastboot (not ADB) drivers. It shouldn't be possible to install ADB drivers if you do this properly.
Rekoil said:
I can't tell exactly by your comments, but are you aware you need to start the phone in a different mode to access it via fastboot?
Disconnect USB
Hold Power & Volume Up until the phone vibrates three times in quick succession.
Let go of the buttons.
While holding Volume Up, connect USB cable between phone and computer.
The LED should turn blue to indicate you are in fastboot mode at which point you will need to install fastboot (not ADB) drivers. It shouldn't be possible to install ADB drivers if you do this properly.
Click to expand...
Click to collapse
whilst in fastboot i get the message waiting for device .the device has connected in fastboot before , that's how i unlocked the boot loader .
Hi all,
I have a Xperia Z (C6603). (I'm from the Netherlands btw) I have unlocked the bootloader and rooted my telephone today. Then I wanted to install CWM. So I downloaded a few files to do this (a kernel from Doomlord) and a Fastboot package. I started my phone in Fastboot, installed the drivers but the command 'fastboot flash boot boot.img' didn't work as it kept waiting for my device.
And then I did something stupid. I started Flashtool and it saw my device in Fastboot mode. I then selected Flash in Fastboot mode and in the pop-up screen I chose 'Select kernel to Hotboot' and then I selected the boot.img I had downloaded. It said Okay and Okay, then gave the message that my device was disconnected and should be rebooting but it didn't!!!
It now is still in some sort of fastboot mode as the blue light is still burning but nothing happens. I can't switch it off, windows doesn't recognise the phone, PC Companion doesn't see anything and Flashtool says 'device disconnected' and I am slowly getting desperate... I have a tiny hope that, when the battery has run out, it might come back to life...
I have tried it on all my usb-ports but nothing happens!
Is there anybody out there who has an idea what to do?
a look at this topic. I hope you can bring your XZ back to life.
http://forum.xda-developers.com/showthread.php?t=2229250
C.Eduardo said:
a look at this topic. I hope you can bring your XZ back to life.
http://forum.xda-developers.com/showthread.php?t=2229250
Click to expand...
Click to collapse
THX!!!!!
It was as easy as pressing Vol-UP and Power at exactly the same time (as described in the topic you send)!!! It's working again!!!
TheDjave said:
THX!!!!!
It was as easy as pressing Vol-UP and Power at exactly the same time (as described in the topic you send)!!! It's working again!!!
Click to expand...
Click to collapse
lmao saved me almost 10 years later thx
I have a sony xperia z c6603 , it was never unlocked from the start but it worked very fine on its original firmware, android 4.1.2. But then someone flashed a c6602 android 4.1 on it and now the IMEI is corrupted and it restarts every 9.3minutes.
It says bootloader unlock allowed: Yes which I guess means the bootloader is locked and can be unlocked, but since IMEI is corrupt, i cant request for unlock code from sony or use fastboot.
My only other option is the famous flashtool. I have three issues with flashtool.
1. I already downloaded the correct firmware and preparing to flash, so I click on the flash icon and start flash (Using Androxyde flash tool). It goes through the normal process and then an empty device selector screen comes up, with no option but to cancel. and when i cancel, it says "loader not found for this device"
2. Okay, after step 1, i am thinking "maybe i have to unlock the bootloader first" so i click on the BLU button and connect the device in flash mode, it starts and the empty device selector screen comes up again, once i cancel, it says "your device can not be officially unlocked"
3. So i did a little bit of digging around on here more and found that i have to update xflasher.jar to beta6, and so i did and flash tool started as "androxyde and bin4ry flash tool" .Only problem is when i click on the flash icon and choose flash mode, nothing comes up, i cant get into flash mode. but I can get into every other thing like fastboot mode and BLU
Please if you think you have an idea on how to solve this problem, please reply. I cant afford a new phone and I would also like to know if my phone can be repaired too, I also dont have a lot of time to waste trying to repair it.
try to reinstall flashtool after deleting it first .. install fastboot and flashmode drivers and drivers for ur device from drivers folder in flashtool folder.. disable any antivirus and any app that could interfere and unplug any usb device ... try to flash with flashmode
---------- Post added at 12:39 AM ---------- Previous post was at 12:35 AM ----------
mordr3d said:
I have a sony xperia z c6603 , it was never unlocked from the start but it worked very fine on its original firmware, android 4.1.2. But then someone flashed a c6602 android 4.1 on it and now the IMEI is corrupted and it restarts every 9.3minutes.
It says bootloader unlock allowed: Yes which I guess means the bootloader is locked and can be unlocked, but since IMEI is corrupt, i cant request for unlock code from sony or use fastboot.
My only other option is the famous flashtool. I have three issues with flashtool.
1. I already downloaded the correct firmware and preparing to flash, so I click on the flash icon and start flash (Using Androxyde flash tool). It goes through the normal process and then an empty device selector screen comes up, with no option but to cancel. and when i cancel, it says "loader not found for this device"
2. Okay, after step 1, i am thinking "maybe i have to unlock the bootloader first" so i click on the BLU button and connect the device in flash mode, it starts and the empty device selector screen comes up again, once i cancel, it says "your device can not be officially unlocked"
3. So i did a little bit of digging around on here more and found that i have to update xflasher.jar to beta6, and so i did and flash tool started as "androxyde and bin4ry flash tool" .Only problem is when i click on the flash icon and choose flash mode, nothing comes up, i cant get into flash mode. but I can get into every other thing like fastboot mode and BLU
Please if you think you have an idea on how to solve this problem, please reply. I cant afford a new phone and I would also like to know if my phone can be repaired too, I also dont have a lot of time to waste trying to repair it.
Click to expand...
Click to collapse
try to install a newer version of flashtool ...
My C6903 in LP 5.1.1 doesn't take photos (or videos) when the app tries to focus. Without focus enabled (using other app) it goes perfectly. I've tried with 14.6.A.1.236 Customized BAL, 15.5.A.0.242 Movistar AR and a few more, all obtained from XperiFirm.
I tried pushing that "4k and timeshift" .zip which I read could fix the camera but no luck.
Curious thing is that Rooting Status shows "Unknown", I don't know if this could be related or not. I bought the phone on eBay (used) and I couldn't tell you if it's been unlocked or not.
But I know that everything can't be messed up because in JB 4.3 (14.2.A.1.136 Generic BAL from XperiFirm) camera works well, and Rooting Status shows "Bootloader Unlock Allowed: Yes"; And in KK 4.4 (updated via OTA from mentioned JB firmware) camera stops working in the same way but Rooting Status keeps on "Bootloader Unlock Allowed: Yes".
What could I try? I think I've already read everything related to the Rooting Status Unknown and Camera freeze problems in this forum and still have no clue (even in other Xperias forums too).
Thanks by the way
PS: Yet I didn't tried unlocking bootloader just because it may bring more problems, but if needed I would do it in a blink
matidx said:
PS: Yes I didn't tried unlocking bootloader just because it may bring more problems, but if needed I would do it in a blink
Click to expand...
Click to collapse
This is definitely a bad way to troubleshoot your problem, but go ahead and make yourself a backup of your phone's TA partition and unlock the bootloader of your phone. As long as you made a backup of the partition, the DRM keys will stay intact when you re-lock the bootloader; thus, you won't lose any exclusive Sony features upon restore. Make sure you have the proper adb and fastboot drivers before you begin.
Backup TA partition: http://forum.xda-developers.com/showthread.php?t=2292598
Unlock bootloader: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
Flash any custom ROM (don't flash the Marshmallow ROMs) found in either the Android Development or Original Development page for Z1. You can also flash a modified Sony ROM in the Android Development section that has mostly all of the features in Sony's stock ROM plus some additional ones picked from CM/AOSP ROMs. Either way, if your problem is fixed, then it's a problem with the FTFs you flashed. If not, restore your TA/DRM keys (it'll re-lock your phone's bootloader) and report back.
Good luck fixing your problem!
kentexcitebot said:
This is definitely a bad way to troubleshoot your problem, but go ahead and make yourself a backup of your phone's TA partition and unlock the bootloader of your phone. As long as you made a backup of the partition, the DRM keys will stay intact when you re-lock the bootloader; thus, you won't lose any exclusive Sony features upon restore. Make sure you have the proper adb and fastboot drivers before you begin.
Backup TA partition: http://forum.xda-developers.com/showthread.php?t=2292598
Unlock bootloader: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
Flash any custom ROM (don't flash the Marshmallow ROMs) found in either the Android Development or Original Development page for Z1. You can also flash a modified Sony ROM in the Android Development section that has mostly all of the features in Sony's stock ROM plus some additional ones picked from CM/AOSP ROMs. Either way, if your problem is fixed, then it's a problem with the FTFs you flashed. If not, restore your TA/DRM keys (it'll re-lock your phone's bootloader) and report back.
Good luck fixing your problem!
Click to expand...
Click to collapse
Tried that but it looks like the volume up button isn't recognized when booting or something like that. What really matters is I can't enter to fastboot mode, tried everything. Any ideas?
matidx said:
Tried that but it looks like the volume up button isn't recognized when booting or something like that. What really matters is I can't enter to fastboot mode, tried everything. Any ideas?
Click to expand...
Click to collapse
Install proper drivers for fastboot. Power the phone off completely, then while plugging your phone into the computer, hold the top volume button. You should be able to enter fastboot if fastboot drivers are properly set up.
kentexcitebot said:
Install proper drivers for fastboot. Power the phone off completely, then while plugging your phone into the computer, hold the top volume button. You should be able to enter fastboot if fastboot drivers are properly set up.
Click to expand...
Click to collapse
Is there a way to know if fastboot drivers are properly installed? I've checked and reinstalled them about 5 times, but I'll try again tomorrow just to be sure I'm not missing anything.
I don't know if there are different drivers but always installed the flashtool ones. By the way I'm running Win10 but also tried in Win7 and no luck.
matidx said:
Is there a way to know if fastboot drivers are properly installed? I've checked and reinstalled them about 5 times, but I'll try again tomorrow just to be sure I'm not missing anything.
Click to expand...
Click to collapse
If your computer can successfully detect the device and output it's serial number when you input through command prompt:
Code:
fastboot.exe devices
you'll know that fastboot is working and drivers are set up correctly. If you look at your device LED, the LED will be lit blue. Remember: you need to already have downloaded and installed the applications through the executabe in the adt folder to get the fastboot and adb applications.
matidx said:
I don't know if there are different drivers but always installed the flashtool ones. By the way I'm running Win10 but also tried in Win7 and no luck.
Click to expand...
Click to collapse
Go here to download the correct fastboot driver files: http://doomlord.xperia-files.com/download.php?dlid=Rmxhc2h0b29sLWRyaXZlcnMtMS4zLTIwMTQwMjA5
If your computer can successfully detect the device and output it's serial number when you input through command prompt:
Click to expand...
Click to collapse
Right, I know what that command line does, but that will work only when drivers are properly installed AND phone is detected. What I believe is that there are some kind of problems with the phone to not go into fastboot mode, so it wont be detected at fastboot, always in flashmode.
Is there a way to know if drivers are properly installed even if the phone isn't recognized?
Remember: you need to already have downloaded and installed the applications through the executabe in the adt folder to get the fastboot and adb applications.
Click to expand...
Click to collapse
What is the adt folder? You mean adb or the obsolete Android Development Tools (now Android Studio)?
By the way, I'm also having this issue... http://forum.xda-developers.com/xperia-z1/help/baseband-lost-reboot-t3352858
Maybe it could be related someway (like motherboard going bad or something else).
matidx said:
What is the adt folder? You mean adb or the obsolete Android Development Tools (now Android Studio)?
Click to expand...
Click to collapse
My apologies, I should've been more clear and double-checked the information!
They apparently renamed the file. I was referring "adt" to my folder that's dated all the way back to 2013, so....whoops!
You can grab the download from here: http://developer.android.com/sdk/index.html. If you don't want the entire bundle, search for "Get just the command line tools" and click on the links for your platform.
matidx said:
Right, I know what that command line does, but that will work only when drivers are properly installed AND phone is detected. What I believe is that there are some kind of problems with the phone to not go into fastboot mode, so it wont be detected at fastboot, always in flashmode.
Is there a way to know if drivers are properly installed even if the phone isn't recognized?
Click to expand...
Click to collapse
Just download the S1 driver file through the link I provided earlier, install, reboot computer, then run the same command as I told you from my previous post: if it outputs the serial number of your phone, then you're fine; but if it doesn't, post back. As long as your computer can establish a basic connection to your Z1 (PC can see it in flash mode, could access it somehow), your phone is capable of fastboot.
kentexcitebot said:
My apologies, I should've been more clear and double-checked the information!
They apparently renamed the file. I was referring "adt" to my folder that's dated all the way back to 2013, so....whoops!
You can grab the download from here: http://developer.android.com/sdk/index.html. If you don't want the entire bundle, search for "Get just the command line tools" and click on the links for your platform.
Just download the S1 driver file through the link I provided earlier, install, reboot computer, then run the same command as I told you from my previous post: if it outputs the serial number of your phone, then you're fine; but if it doesn't, post back. As long as your computer can establish a basic connection to your Z1 (PC can see it in flash mode, could access it somehow), your phone is capable of fastboot.
Click to expand...
Click to collapse
I think I've followed everything right but to be clear I'm gonna explain what I've done so far:
- Installed Android Studio (I believe it comes with those "just the command line tools").
- Installed Flashtool's driver (same as the DoomLord link you provided, even a later update than that link), also did that thing about "Disable Driver Signature Enforcement" because I'm on Win10 64bit.
- Always checked by cmd command line "fastboot.exe devices", I've never get any error (so cmd always detected it as a valid command line) or any other cmd print.
- I have a TA backup but after I made it tried to unlock bootloader but no luck. Anyway, just restored the backup and only sign I got is "Upgrading NFC firmware" or something like that after booting, the "NFC upgrade" went well but still no fastboot access.
---
- When I plug the usb + press volume up button to try get fastboot mode, phone's led goes red then green then it goes off and in flashtool I get flashmode with no led on.
---
By the way, I have an Xperia SP and already unlocked bootloader so I pretty know how it should go. Having no problem with it accessing fastboot or even locking or unlocking on the XSP.
Because of this and baseband problem, I can't stop thinking motherboard is messed up.. But anyway, whatever you think I could try just let me know.
hello i get this error every time when i try to use fastboot, can some one help me?
c:\sdk\platform-tools>fastboot erase cache
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.004s
i tried many diffrent commands, each time i get this error
have install google usb driver, device manager calls all fine.
have also tried the flashtool driver, device manager calls all fine but cmd.exe (admin) and fastboot same error.
only working command is to unlock the bootloader .
so my bootloader is unlocked and fastboot driver senn to be right.
can you please help me
windows 8.1 64 bit
xperia z c6603
bootloader open
no idea?
Sent from my C6603 using XDA-Developers mobile app
bump
If no one replies, in my experience, just inbox one of the old devs from our phone. Sometimes, if their not too busy they'll give you some time. They're just dudes trying to help people have cooler phones, anyway.
In my case, I get those errors because my bootloader was locked. I've unlocked a lot of times but not with the right code. I suggest you to try unlocking the bootloader with the right IMEI (not the one on the box nor the one in Flashtool) and enabling USB debugging.
i have order the unlock code 3 times from sony, also look on the rooting status:
Bootloader unlocked: Yes
i´m using the sony emma flashtool, and this works only with unlocked bootloader, but on fastboot i cant execute comands
dont know what is wrong
steve233 said:
i have order the unlock code 3 times from sony, also look on the rooting status:
Bootloader unlocked: Yes
i´m using the sony emma flashtool, and this works only with unlocked bootloader, but on fastboot i cant execute comands
dont know what is wrong
Click to expand...
Click to collapse
In case you use linux, try this setting permissions first:
http://forum.xda-developers.com/xperia-z/help/flashing-rom-twrp-bootloader-boot-img-t3241148
Edit:
You mentioned cmd.exe, so I guess you use windows and this is not the case,
however it may be similar issue for windows, since you run cmd from admin.
In my case, on linux, without permissions, my computer could only recognize the device from superuser/admin. With permissions like in the thread above, any user could run commands to device, and finally I did the trick without superuser/admin.
so you think it is an administrator premission problem?
i have format my windows pc today and reinstall all, but same problem, fastboot and device driver is without issue in device manager.
also create new administrator account, didn´t help.
edit:
i tried some more commands and some of them worked
HTML:
> fastboot erase boot works
> fastboot erase system works
> fastboot erase userdata works
> fastboot erase cache faild
> fastboot erase recovery faild
> fastboot oem lock faild just show 3 dots and nothing happening i wait 1 hour for sure
I can see you are using Windows 10. There are problems with driver verification. Have a look in device manager and check if your device is recognized properly in fastboot mode. If drivers cannot be installed you have to boot windows with signed driver verification turned off. For this press and hold shift and klick on reboot. Then choose troubleshooting and then something like restart options. At the next boot you have to press 7 - I think. Now fastboot drivers should install correctly.
Sent from my E6653 using XDA-Developers mobile app
its windows 8.1 x64 and driver are already installed no problems on device manager, i also have open bootloader.
I am having the same problem with windows 10 64 bit.
I give up.
pls help
try to run fastboot.exe under administrator's permission (either by setting properties on fastboot.exe or by running administrative cmd).
I'm using android sdk on ubuntu, I have to add "sudo" (run as root) before fastboot command but there's no need for "adb".
I think the device (xperia z c6603) isn't supporting some commands, but (boot system userdata) erase works.
maybe some experts can give a final answear
Try enabling OEM unlocking in the developer settings on the phone first.
This!
jackflap said:
Try enabling OEM unlocking in the developer settings on the phone first.
Click to expand...
Click to collapse
Thanks, been trying to unlock the BL of my Z5. I didn't know that this has the option. Previously on my Z1C and Z3 Dual there was no such option or lock
jackflap said:
Try enabling OEM unlocking in the developer settings on the phone first.
Click to expand...
Click to collapse
Awesome, thanks for that needle in a haystack!
Worked on Xperia X F5121 US version with the UK firmware to enable fingerprint scanner.
remote: command not allowed
Honor 6X BLN-L24
I had the same issue for the longest and tried everything possible under XDA's advice. its for the first time that I was not able to find the soloution to my isuues with the phone. Desperation led me to keep on trying until I accidently found how to do a "Hard Reset" which eventually solved this issue
1) Power your phone off.
2) Press Vol Up (+) Button and while keeping it pressed push the power Button (keeping both pressed).
3) As soon as you see the honor logo (blueish color), move from Vol up (+) to Vol down (-) While Still Pressing On The Power Button.
4) Keep Pressing Vol (-) and Power Button, --> will go through "turning your device on" --> Blank Screen --> Hard Reset Menu.
5) Well everyone knows from this point onwards --> Wipe It Clean, Reboot, Just like New.
Hope this helps.
I have bricked my phone (sony logo and nothing else) and can only connect in fastboot (not even flashmode). I try to flash a kernel but shows the same error. What should i do now? (Im on wind10 64bit)
Totesz00 said:
I have bricked my phone (sony logo and nothing else) and can only connect in fastboot (not even flashmode). I try to flash a kernel but shows the same error. What should i do now? (Im on wind10 64bit)
Click to expand...
Click to collapse
same problem.....
gungsye said:
same problem.....
Click to expand...
Click to collapse
Lograste solucionar el problema, a mi me pasa lo mismo...solo reconoce mi móvil en modo Fastboot y me muestra el mismo mensaje de error. Habrá alguna forma de instalar todo por fasstboot y recuperar mi Xperia Z (c6603)?
De antemano garcías.