I've searched and tried most guides/fixes for adb but it fails to work when i start the phone up while holding the volume up button. The light will turn blue, and one sony fastboot driver will show on device manager but nothing else. If i turn the phone on, there is a sony adb tab with the driver and the device will show up on adb devices, but as soon as i use adb reboot fastboot it just reboots normally without going into fastboot.
latest firmware, installed android sdk,android studio, reinstalled every usb driver multiple times, downloaded xperia compact drivers from sony themselves etc. It's a ***** on a computer without a ssd.
Will provide pictures and/or videos if problem isn't apparent from description. Thanks in advance
Related
Please excuse me if I'm repeating a prior question but it seems far too specific to trawl through pages of related threads to make sure.
I decided I was going to sit down and root my Xperia Z1....
Steps:
1. I installed ADB and Fastboot via the latest windows Android SDK (r23-.0.2), in fact I had to source a sony version of the fastboot driver in order to get it working but once I'd done that all went ahead as planned.
2. Generally followed this guide (wont let me post a link but google "honami cyanogenmod" and it's the 2nd result)
3. All was going swimmingly, I entered fastboot mode absolutely fine, flashed CWM using fastboot which all loaded up absolutely fine.
3. At this stage ADB was not picking up my device at all, tried different cables, ports, all of the usual. What I didn't do was make a backup, and then I wiped all of the things that it's possible to wipe thinking to myself that I was going to get Cyanogenmod on there so all would be fine...
4. Finally I (quite stupidly) restored from memory card (which had already been wiped) from inside CWM, the device restarted and now I am getting no response AT ALL.
5. Sometimes it will load the Sony 'splash' logo that first appears but sometimes not, when plugged in the device is recognised and ADB actually sees the device but lists it as offline... Interestingly at this stage windows device installer actually installs Sony ADB driver for me automatically.
6. All I'm getting at the moment is a red flashing LED although when I plug in via USB the device is again recognised when I type adb devices but again is offline...
If any more information is needed please, I will be more than happy to give a quick reply.
Thank you in advance
JJrmc said:
I decided I was going to sit down and root my Xperia Z1....
Steps:
1. I installed ADB and Fastboot via the latest windows Android SDK (r23-.0.2), in fact I had to source a sony version of the fastboot driver in order to get it working but once I'd done that all went ahead as planned.
2. Generally followed this guide (wont let me post a link but google "honami cyanogenmod" and it's the 2nd result)
Click to expand...
Click to collapse
Were you trying to root your phone or install cyanogenmod? You followed a guide to install cyanogenmod on xperia Z1.
AkiraProject said:
Were you trying to root your phone or install cyanogenmod? You followed a guide to install cyanogenmod on xperia Z1.
Click to expand...
Click to collapse
I was trying to end up with a rooted device running Cyanogenmod, I've been putting it off and off looking into the whole rooting scene and mistakenly dived in a little too quick without knowing what I was doing.
after that you move cm-11-20141112-SNAPSHOT-M12-honami.zip to your sd card. Now you have flashed boot.img you can't move zip to your sd card using z1 you had to do that before using fastboot. use some sd card adapter and do it. then put the sd card back in your phone. turn it on then enter the cwm recovery pressing Vol+ for a few seconds when the sony logo shows up. select full wipe data. then install from zip. choose cm-11-20141112-SNAPSHOT-M12-honami.zip. reboot. ADB won't work until you have installed cyanogenmod zip. You have only installed cyanogenmod kernel and custom recovery when you flashed the boot.img.
AkiraProject said:
after that you move cm-11-20141112-SNAPSHOT-M12-honami.zip to your sd card. Now you have flashed boot.img you can't move zip to your sd card using z1 you had to do that before using fastboot. use some sd card adapter and do it. then put the sd card back in your phone. turn it on then enter the cwm recovery pressing Vol+ for a few seconds when the sony logo shows up. select full wipe data. then install from zip. choose cm-11-20141112-SNAPSHOT-M12-honami.zip. reboot. ADB won't work until you have installed cyanogenmod zip. You have only installed cyanogenmod kernel and custom recovery when you flashed the boot.img.
Click to expand...
Click to collapse
Firstly AkiraProject thank you for your time on this.
I do realise that in my stupidity I could have loaded the cm-11-20141112-SNAPSHOT-M12-honami.zip to my SD card (if I'd had one or waited and gotten one).
What I did however was wipe everything I possibly could, and then hit restore from sdcard/0/ I believe - it may have been a different directory.
I believe what I have done is restored to a blank image......
WHen not plugged into usb I get a red blinking LED when just pressing the power button once.
When holding volume-up + Power the phone vibrates as if it is trying to boot but is unable to
If I leave it plugged into USB AND then press , the device shows the sony Logo and then proceeds to display a backlit but plain black screen, Sony PC Companion recognises the device as connected but is unable to interact with it. The output of "adb devices" shows my device but says "unauthorized" and windows is attempting to install MTB driver....
The behaviour doesnt seem to be quite the same every time.
I believe the device is soft bricked.... is this likely to be a case of a wiped partition table? Or at least loss of the boot partition?
If I leave the device plugged in via USB it periodically reboots itself, shows the Sony logo, remains on a bank screen then shuts itself down.
Shows in device manager as "USB Input Device" on win 7 x64 pro
Thanks in advance
Pretty certain it's not hard bricked, there will be instructions here you can follow:
http://forum.xda-developers.com/showthread.php?t=2574764
Sent from my C6903 using XDA mobile app
D33KK said:
Pretty certain it's not hard bricked, there will be instructions here you can follow:
http://forum.xda-developers.com/showthread.php?t=2574764
Sent from my C6903 using XDA mobile app
Click to expand...
Click to collapse
I have done quite a lot of reading etc on the subject....
according to This thread, Sony Xperias have the bootloader in non-writable mask ROM... so you should always be able to access Fastboot or Flash Mode?
The problem I am having is that I don't seem to be able to activate EITHER Fastboot OR Flash mode in order to flash some new firmware onto my device....
My device is recognized as a "USB Input Device" on Device Manager and windows tries to install MTP driver. I'm going to have a go at the process with a fresh install of windows 7 x64 and 'windows auto-install drivers' turned off.
What is the maximum damage I could have done here?
Thanks
Update
Hard reset (red button inside of the sim-card slot) resets the phone with three vibrates and it restarts.
The phone powers on and displays Sony splash screen and then displays a back-lit black screen.
The phone gets much hotter than normal and powers on to the blank back-lit screen when on charge.
I have NO ACCESS to flash mode or fast boot. Any combination of buttons leads to the same outcome: single vibrate, red LED and the phone shows the Sony splash screen then blank screen, as if the button combinations are just ignored...
Flashtool DOES NOT recognize the device, although it is recognized as C6903 in device manager (I have Sony adb driver installed and have disabled the MTP driver that windows recommends).
Flashtool gives me the red error text about making sure drivers are installed and making sure the device isn't in MTP mode.
I'm at an absolute loss as to what to try next, can somebody shed any light on this? There are plenty of guides but they all seem to rely on EITHER fastboot or flash mode and I can access neither although the phone powers on!
Thanks in advance!
Maybe the partition was corrupted when you flash "blank" image..........
So....JTAG....or send to Sony service....
Shutdown with power+vol up (will vibrate thrice) and see if it doesn't turn on automatically.
If it didn't turn on now check your task manager on windows, go to process tab, kill adb.exe (every adb.exe)
Back on phone connect usb holding down the vol down button (phone have to be off before you connect usb), if green led turns on and doesn't turn off you are on flashmode.
Check on flashtool or flashtool64 (for 64bits) and see if flashtool detects your device. If it detects and recognizes your phone flash the FTF for your device and let it do its job.
As you messed the phone Sony will charge for repairs.
Recently my Z3 has started acting up, I can't turn on either bluetooth or wifi and attempting to do so will freeze the phone for a good few seconds before I can use it again. I've been attempting to revert back to stock firmware using flashtool to no avail. I've enabled USB debugging, flashtool recognizes my device fine. I've installed all of the drivers that come with flashtool however my issue is whenever I select "flashmode" in the bootmode chooser menu nothing happens. I've read and watched several tutorials and after selecting flashmode I thought I was supposed to get a drop down menu allowing me to select a FTF file (which I have downloaded and put in the firmwares folder) however no menu appears. If I select fastboot mode a window appears with all the fastboot options however flashmode results in nothing occuring. I've tried using two different PC's however I have the same issue with both (One PC running Windows 10 other running Windows 7). This might be a stupid issue with an easy fix however I've found no information on how to do so and it's been driving me insane the past hour and a half. Any support would be appreciated.
ur problem is confusing me. please elaborate what u did step by step.
pls specify ur exact phone model, flashtool version, pc windows version.
Hallo Everybody,
I'm new to flashing/rooting/etc. on mobile android devices, but since my Motorola RAZR I is stuck at the red Motorola logo, it is time to gather some experiance.
As said, the phone stucks at the Motorola logo, propably a bootloop. Fastboot access is possible, it is also possible to get into the recovery menu. But when I try to connect adb via the recovery menu option "apply update via usb" my PC (Win7) gets an "Unknown Device" in the Device Manager under USB-Controller.
I used adb before for playing a little bit around, so all Motorola drivers for the normal debug mode work, but I don't find a driver for the "Unknown Device" (recovery mode adb).
I already tried different USB cables and restarted my PC serveral times, but still no driver for the "Unknown Device". I also tried the Intel Driver update for android devices and forced to install the Motorola drivers for this "Unknown Device" but nothing helps.
I wanted to try to download/backup some files from the internal storage. Afterwards, I want to flash a lineageOS.
I also searched a day in the internet and in this forum but I didn't find a solution. Sorry if I didn't find the Solution-Thread.
Has somebody an Idea?
Many Thanks in advance.
Hi,
I wanted to install Lineage OS on my Sony Xperia XZ2 compact. It has the latest stock firmware installed.
adb devices lists my device, preconditions are ok (bootloader unlock yes and debugging enabled and authorized)
adb reboot bootloader: the phone turns off, red light for 3 seconds, vibration, cyan light and black screen
fastboot devices simply does nothing
turn phone on again
turn off phone
hold volume down + power on -> vibration, "SONY" appears, "SONY" disappears, vibration, phone boot into normal work mode
I do not get into fastboot mode
Any ideas?
Best regards,
Ghost
Trash
Trash
RelaxIamOnlyAghost said:
adb reboot bootloader: the phone turns off, red light for 3 seconds, vibration, cyan light and black screen
fastboot devices simply does nothing
Click to expand...
Click to collapse
Can you try
Code:
fastboot getvar all
If your device is recognized correctly it should either give you a long list of values or an error.
Else you get something like "Waiting for devices".
< waiting for any device >
nothing else
RelaxIamOnlyAghost said:
< waiting for any device >
nothing else
Click to expand...
Click to collapse
Okay. Then it makes sense that "fastboot devices" shows nothing.
Your problem is that your computer doesn't detect your phone in fastboot mode.
I think your cable should be okay (since adb works) but maybe you need some additional drivers?
You can also try solutions you find in the web if you search something like this:
Computer doesn't detect phone in fastboot
Click to expand...
Click to collapse
Or "Windows" instead of "Computer" if you use windows etc.
User699 said:
Okay. Then it makes sense that "fastboot devices" shows nothing.
Your problem is that your computer doesn't detect your phone in fastboot mode.
I think your cable should be okay (since adb works) but maybe you need some additional drivers?
You can also try solutions you find in the web if you search something like this:
Or "Windows" instead of "Computer" if you use windows etc.
Click to expand...
Click to collapse
Ok, I got it. I did not turn "driver signature enforcement" off on my Win 10 system (but I got no error during driver install). After switching off "driver signature enforcement" and re-installed the adb and fastboot drivers, I got a warning that a driver without signature will be installed. I confirmed that warning and now fastboot is working well.
Hello, hopefully someone can help me.
I have the same problem as mentioned above. I also tried to deactivate driver signature and install new but it didn't work. Maybe I did it wrong.
I used this command and rebooted with deactivated driver signature.
shutdown.exe /r /o /f /t 00
I also tried to install specific adb drivers for xperia xz2c manually instead of universal adb drivers.
Any more ideas?
Thanks and regards
I'm facing the same problem. I've installed multiple adb drivers, with and without driver signature enforcement, and nothing works.
adb works fine, and device is listed, but as soon as I do an adb reboot bootloader, the device is gone. Also, for some reason, I do not see any cyan blue LED lighting up in my unit (the LED itself does work though).
Was able to fix it. The trick is to start the phone into fastboot (vol down+power), and then go to Device Manager and install the drivers from Sony on the recognized device.
a.bispo said:
Was able to fix it. The trick is to start the phone into fastboot (vol down+power), and then go to Device Manager and install the drivers from Sony on the recognized device.
Click to expand...
Click to collapse
Hi, a.bispo, do you have any link for these driver because I have tried several on sony website and none work for me.
Thank you,
I got them from Sony's website as well.
The trick was putting the phone into fastboot, letting Windows recognize it, and then manually install those drivers' files.
Just an update from my experience: I had to go into device manager and select an alternative driver for the Android! device that popped up. Not sure if this is mandatory or not but I did this after the fastboot devices step where my device isn't detected.
Hello everybody,
To explain things a bit better than just this title. I have a Mi 5 that was working smoothly for quite a long time. Had a modified MIUI ROM flashed on it with many specific apps such as xposed, Magisk and also TWRP. However, my GPS has turned completely dead for some months. Couldn't use it anymore. After some researches, I found out it could be software related. So I decided to flash a new ROM (AOSP Extended) to see if that could fix the GPS issue.
First I backed up the whole system via adb on my laptop and then wiped the whole system. It turns out after trying to flash the AOSP ROM, I came across a message saying I should have MIUI 8.1.30 or older. Or something like that... Can't remember exactly. Just read that I was supposed to update my ROM to a newer stock ROM to be able to flash AOSP in a second time. I did a lot of different operations and I can't remember them all but it turns out one moment, adb started to flash a ROM because the adb command line was saying it. But it failed. Aftert that moment, my phone definitely got bricked. I have no clue what exactly happened, it's kind of confused...
Currently, the phone is always displaying dark screen with mi logo and "unlocked" mention below. Power and volume up will just reboot it to the same state (meaning twrp is not longer installed or accessible). In this dark screen mode, plug the phone to a computer will do nothing, it's not even detected in devices manager. On the other side, power and volume down will boot the phone into fastboot mode, the computer beeps when I plug the USB cable and I can briefly see the Android device with a yellow warning in the dev manager. But after something like 20 seconds, fastboot mode goes off and phone restarts on black MIUI screen.
I've tried to install Google drivers, Qualcomm drivers and did numerous actions but the phone isn't detected anymore. Also, tried to type command "adb devices" in the short time when the phone is detected by computer in fastboot but it shows an empty list. I'm pretty desperate, seems I've tried anything and I've no ideas now... Just saw there is possibly a hardware fix which requires to dismount the back of the phone. Not sure what it does but I'll try it out if no other solution shows up...
Any idea is welcome ! Thanks
Well, looks like my thread wasn't so popular Finally found a workaround after nearly 8 hours searching for a fix. Thought that might help anybody else having the same struggle as mine. What I can tell is that it's not related to the computer used since I've made the same operations on 3 different computers, same problem for each of them. In fact, there were two problems :
First the bootloader not remaining more than 30 seconds. To stop this, I had to open the devices manager and as soon as the Android device would appear after turning it into Fastboot, I would right click on the visible device (appearing with an exclamation mark) and update manually the driver following the process that is described in many topics (locate the Google Android devices USB drivers that I downloaded right before). The time is quite short so you have to be pretty fast, otherwise, the MI 5 would disappear, forcing you to do the fastboot mode operation again. I have to say that doing it without the device being recognized is not working. So if you install with the legacy driver option, it's not going to be associated directly to the device. At least, not in my case.
Once I had done this, the Fastboot mode would remain on. I found my way pretty fast until that moment but the problem was adb wouldn't detect my device. Typing "adb devices" command would return no result, no matter what I did. Strangely, installing an old version of MiFlash (last ones gave me error) would help the computer to detect the device. I don't know why, possibly because the drivers are better ? Anyway, MiFlash helped me to access the phone and Flash a new ROM. Usually, I was just using adb and it would do the job but this time not.
Hope it can help !