Hi,
I unlocked the bootloader for my z5c quite a while ago and am now preparing to flash lineageos.
But unfortunately it's somehow unpossible to enter fastboot mode.
First I tried Vol- and connecting to PC, what never worked. Then via "adb reboot fastboot" - that partially worked, the LED lit blue, but the smartphone wasn't recognized on the PC anymore.
Starting up directly with Vol- + powerbutton would lead into a short bootup (showing Sony Xperia logo).
Then I tried downloading the newest Sony drivers, but on Windows 10 x64 it's not possible to install them (as they are not signed). Therefore I rebooted with signature testing turned off and installed the drivers. Now the smartphone won't boot anymore with blue LED lit, it directly boots into android system.
Next thing I tried was installing flashtool (0.9.25.0) but that won't work either - after installing driver for fastboot etc. the software would take forever to start (see picture 1).
Can anyone help? I'm completely lost
Best,
ssdnvv
Seems I have to enter "adb reboot bootloader" to switch to fastboot mode. With that I was able to flash most recent TWRP 3.2.1.0 and the custom ROM I was aiming for.
Related
I was on Neutrino 2.5, I flashed to 2.5p (without wiping).
It wasn't working as I wanted so I went in to recovery to reflash the google apps zip.
After that I'm now stuck in a boot cycle loop and I can't even boot in to recovery mode. When I try to enter recovery it says "Entering Android Recovery Mode" then the screen just goes blank.
Really sorry to make this my first post but I'm kinda freaking out right now. Don't have any idea how to recover from this.
rodabi said:
I was on Neutrino 2.5, I flashed to 2.5p (without wiping).
It wasn't working as I wanted so I went in to recovery to reflash the google apps zip.
After that I'm now stuck in a boot cycle loop and I can't even boot in to recovery mode. When I try to enter recovery it says "Entering Android Recovery Mode" then the screen just goes blank.
Really sorry to make this my first post but I'm kinda freaking out right now. Don't have any idea how to recover from this.
Click to expand...
Click to collapse
flash the recovery again using fastboot
Thanks for the reply. So my problem so is that I'm trying to boot in to RSD mode but it get the message "Battery is too low to flash".
I'm trying to charge the battery but whenever i plug it in to charge phone starts up and ends up in the boot cycle, and the battery doesn't end up charging.
How can i force the phone not to turn on when I plug it in to the wall charger?
Ok, I was able to McGyver a usb charger from an old cable and I got the battery charged enough where it would enter fastboot.
However... now I can't get either of my laptops to recognize the phone in fastboot.
I attach the phone to the usb port, turn the phone on and hold the volume down button. I press the volume up button when fastboot appears, the message "Starting Fastboot protocol support" appears and then nothing happens. Windows just sits there, the phone just sits there...
If I do moto-fastboot devices at the command prompt there is no serial.
Any thoughts?
Well, normally nothing happens until you issue a fastboot command. I usually boot into fastboot mode first, THEN connect the phone & open a command line, etc.
What happens if you do the above and type "fastboot devices"? Does it see your phone then?
Ok, so I tried your method, and installing some different windows drivers and now windows does recognize the phone!
For the record, I am on windows xp and currently i'm using driver version 2.0.40 (same problem with 2.0.53).
Now windows isn't able to install the fastboot drivers, it comes up as an unrecognized device. Is there a way to manually install the fastboot drivers?
Although it's recognized by windows, issuing the moto-fastboot devices command still returns blank.
Hi!
I've been trying to flash my Xperia Mini with Cyanogenmod 9, but I'm stuck at step 6 under Flashing CyanogenMod in the Xperia Mini full guide. (Would post link, but as I do not have 10 posts, I can't. :crying: )
I've followed through the entire guide, successfully unlocked the bootloader and so on. However, after step 5 (Volume up + connect to computer = blue LED, which should be correct according to the guide), the device will not appear in command prompt after typing "adb devices". However, it appears whenever the phone is on and connected to the PC (with USB debugging enabled).
I have tried everything from reinstalling drivers (from the official Sony website, Google USB drivers, the ones that are mentioned in the guide for use with CM flashing, etc.) to the whole process of reinstalling the Android SDK. I have tried googling around with no luck, despite finding tonnes of threads with people having the same problem. Anyone know what might be the problem?
Download Flashtool and connect the device in Fastboot mode (volume up while connecting usb). What happens? Flashtool reports a device in fastboot mode?
mihahn said:
Download Flashtool and connect the device in Fastboot mode (volume up while connecting usb). What happens? Flashtool reports a device in fastboot mode?
Click to expand...
Click to collapse
It appears in DooMLoRD's "Get Device Info" for some reason. What should I do here? Proceed to flash using Flashtool through "Select kernel to Flash"?
*EDIT*
I got things working! Installed it through recovery and everything is working fine! Thanks!
I'm trying to flash TWRP, i've got ADB and i've got the Universal ADB Drivers. The device is properly detected when in EUI and my Device ID is displayed correctly when I type 'adb devices', however when I reboot into fastboot and type 'fastboot devices', nothing is listed and cannot continue.
Which drivers do I use? What is it that I need to continue?
Thanks!
Edit: Nevermind, connected it into my linux machine and got it to work easier (lol winBLOWS amirite) and finally got it to recognize the device in fastboot mode. I kept rebooting and failing to get into TWRP. I found somewhere else that before doing 'fastboot reboot' that you should hold VOL UP so you can immediately boot into twrp and make it permanent, which ended up working for me. Freedom!
ItsJono said:
I'm trying to flash TWRP, i've got ADB and i've got the Universal ADB Drivers. The device is properly detected when in EUI and my Device ID is displayed correctly when I type 'adb devices', however when I reboot into fastboot and type 'fastboot devices', nothing is listed and cannot continue.
Which drivers do I use? What is it that I need to continue?
Thanks!
Edit: Nevermind, connected it into my linux machine and got it to work easier (lol winBLOWS amirite) and finally got it to recognize the device in fastboot mode. I kept rebooting and failing to get into TWRP. I found somewhere else that before doing 'fastboot reboot' that you should hold VOL UP so you can immediately boot into twrp and make it permanent, which ended up working for me. Freedom!
Click to expand...
Click to collapse
I believe you need to configure in the developers options that you don't want to have the recovery overwritten on reboot. What also seems to work is to boot into the TWRP from the command line via 'fastboot boot <recovery-file-name>'
I have the exact same problem. I have installed all drivers and adb, but as soon as i am into fastboot and my device doesnt show up in the command line. If i want to install the recovery the command line just says <waiting for device> and nothing happend.
I already enabled the "Enable AT Port" Settings (http://forum.le.com/in/index.php?threads/le-max-2-x820-qpst-not-working.14820/) but i think this is not permanent turned on on my phone, because i have to repeat this step after every reboot.
Anybody got some tips?
Edit: Also booting directly into TWRP doesnt work, 'fastboot boot <recovery-file-name>' just ends up in <waiting for device>..
If you're using Win 8 or Win 10 you should turn off the driver singing verification before installing usb drivers for device.
In your case one of the drivers was blocked from installing and the systom does not see the device after it switches in fastboot/recovery mode.
I am not allowed to post urls, so google this: How to Disable Driver Signature Verification on 64-Bit Windows 8.1 or 10 (So That You Can Install Unsigned Drivers)
RovnyiK said:
If you're using Win 8 or Win 10 you should turn off the driver singing verification before installing usb drivers for device.
In your case one of the drivers was blocked from installing and the systom does not see the device after it switches in fastboot/recovery mode.
I am not allowed to post urls, so google this: How to Disable Driver Signature Verification on 64-Bit Windows 8.1 or 10 (So That You Can Install Unsigned Drivers)
Click to expand...
Click to collapse
Thanks for this Hint! Didnt know this
Nevertheless, no improvement so far. I Unistalled every driver and installed them again, but the PC doesnt recognize the phone when its in fastboot mode
Kampfgans said:
Thanks for this Hint! Didnt know this
Nevertheless, no improvement so far. I Unistalled every driver and installed them again, but the PC doesnt recognize the phone when its in fastboot mode
Click to expand...
Click to collapse
There is a chance, that your computer has installed the WRONG driver for the fastboot mode, so find any related to the phone entries in Device Manager when the phone is connected in fastboot mode, and if it is not "Android Phone/Android ADB Interface" -> remove them with remove driver checkbox checked. Optionally, if nothing changes -> try to manually pick the device driver to Android ADB Interface
RovnyiK said:
There is a chance, that your computer has installed the WRONG driver for the fastboot mode, so find any related to the phone entries in Device Manager when the phone is connected in fastboot mode, and if it is not "Android Phone/Android ADB Interface" -> remove them with remove driver checkbox checked. Optionally, if nothing changes -> try to manually pick the device driver to Android ADB Interface
Click to expand...
Click to collapse
I tried it now with the fifth computer and after a few strange error messages, it "succesfully" installed TWRP.
BUT: There is no TWRP installed on my phone. I followed every tip which i found how to exit the fastboot mode (pressing Vol+ & Power / Removing USB Cable / Tried TeamSpains Automatic Installer).
What is wrong with this phone ? - I think i will oben a new thread, thanks for your help!
Kampfgans said:
I tried it now with the fifth computer and after a few strange error messages, it "succesfully" installed TWRP.
BUT: There is no TWRP installed on my phone. I followed every tip which i found how to exit the fastboot mode (pressing Vol+ & Power / Removing USB Cable / Tried TeamSpains Automatic Installer).
What is wrong with this phone ? - I think i will oben a new thread, thanks for your help!
Click to expand...
Click to collapse
Kampfgans: Klingt irgendwo zwischen lustig und richtig bedrohlich...
Lots of ROMs (including most CM variants) like to "automatically 'recover'" recoveries, that is they overwrite the recovery partition with a copy of the "original" every time you reboot.
I seem to remember that my first attempt to overwrite the stock recovery using "fastboot flash recovery <twrp-image-name>" also didn't succeed in making TWRP "stick".
Within the CM13 which I installed next (over the stock v15) there is a developer option to control that, but in this case I simply used a trick, which seems to bypass the recovery overwrite: I told the phone to boot the TWRP recovery over USB after flashing.
It went like this:
fastboot flash recovery <name-and-path-of-TWRP-recovery> //puts the TWRP image on the recovery partition
fastboot boot <name-and-path-of-TWRP-recovery> //bypasses the recovery overwrite logic of either the bootloader or whereever it hides
That booted TWRP over USB and allowed me to install CM13.
There I disabled recovery overwrite in the deveoper's options and I've never had issues with TWRP disappearing since.
Actually you should in theory be able to leave the stock recovery in place and still use TWRP by booting it over USB on the fastboot command line.
I install drivers and USB but when trying to go to fast boot I receive "waiting for device"
I'm running into issues with my Compact X. Current situation:
- Omni 8.1 rom installed, but doesn't boot. Stuck on Sony logo.
- TRWP 3.3
- Rooted
- When in fastboot mode (vol up + connect usb cable) the device manager shows: Android Device > Sony Fastboot Interface.
- Windows 10 running in "Test mode"
- adb & fastboot v1.4.3
ADB does not recognize my device when the device is in fastboot mode. When it's in recovery mode the command 'adb devices' shows me the device listed. I can then reboot in fastboot mode, but then the device isn't listed anymore. I'm not sure what happened because a couple of hours ago I installed TWRP using fastboot.
I'm trying to get this thing up and running again, but not being able to flash anything via fastboot complicates things. Any idea's what could be the culprit?
Download official Android drivers by Google and force Install them (search: Force Install Windows drivers" anywhere preferably YouTube
Some random said:
Download official Android drivers by Google and force Install them (search: Force Install Windows drivers" anywhere preferably YouTube
Click to expand...
Click to collapse
Thank you for your reply. As far as I know the official drivers were already installed. Because at first my device did show up listed when using the command 'adb devices' and I successfully flashed TWRP recovery. But to be sure I repeated the process:
- Connected my phone in fastboot mode (vol up + connect usb cable). The blue led lights up.
- Go to the device manager, right click on 'Android ADB interface' device and manually install the driver via 'Have disk'.
- The driver installs with no errors.
But still my phone is not listed and I cannot flash anything.
When the phone is in recovery mode it is listed using the 'adb devices' command. But when I'm trying to flash something I get the message <waiting for device> .
Ok, I restored my computer to a point before I started messing with my phone. After installing the official drivers my phone is still not listed (adb devices), but this time flashing did work. I managed to flash the AOSP 8.1 image. My phone is up and running again!
Hi,
i tried to upgrade to the latest 11.0.6 global ROM and as usually I only booted to TWRP and sideloaded the ROM. Bootloader is unlocked, already flashed a lot of different stock & custom ROMs.
adb reboot fastboot
fastboot boot twrp.img (used 3.2.3 with working recovery)
[factory reset from within TWRP]
adb sideload [the new 11.0.6 ROM]
adb sideload had an error 7 at some point and did not finish. No big deal I thought -> [reboot system] from within TWRP and tried to enter fastboot again at first boot [volume down]
BUT: now I am not able to enter fastboot again. The phone starts with the orange 'POCOPHONE by Xiaomi' screen and seems to reset after a minute or so -> loop. Holding [volume down] while booting only brings a black screen (not off, a little grey but no fastboot logo etc.). Probably, fastboot didn't flash correcly. Also, it is not recognized either in fastboot or adb.
Anybody else had this before? Is there something I can try to revice it? Any helpful information is highly welcome,
thanks
I'm no expert, did you try another data cable? Just in case you could use a dry toothbrush and clean the phone's connector . What does the computer says in power+volume down mode? It should say what device you're connecting and add drivers.
There might be a way to repair the bootloader , it involves qcom tool. There's a guide somewhere. I'd try first change cable and computer.