Alright guys, I know this is actually not an issue with newer evo's but need to confirm some stuff about it so lets start giving you reasons why this happens:
I have only seen this effect Hardware Revision 0001 Evo 4G's that used Unrevoked as an S-off method.
Symptoms?
Won't turn on (Vibrate 5 times + green light)
Asking for Qualcomm MSM drivers when plugged into the computer ( see fix for won't turn on below)
Random S-on
SD card refuses to mount
Unusable in ADB
If you RUU it starts rebooting constantly giving the vibrate 5 times + green light
Fixes?
Wont turn on = Plug into your computer and turn it on
S-on = none
SDCard refusing to mount = run fastboot oem enableqxdm 0 from the Fastboot USB mode while it's connected to your computer.
Unusable in ADB: Use this script with terminal emulator [should fix] here You need to run either script manager or terminal emulator as su and move all the files to the root of your sdcard. Then run sh /sdcard/sdcard.sh.
RUU = None (sorry, I learned there is nothing you can do about this.
Causes: It seems to be consistent with only release day (or close to) evo's that are doing something while flashing, backing up, wiping, or doing something with a custom rom being added or removed from the device. It is possible that it could be a NAND failure and it would actually explain why it requires qualcomm drivers when you plug it in as it's in a forced download mode.
What can you do about it?
Only thing you can do is RUU and take it back to sprint to show them. This is the device's way of bricking itself WITHOUT turning into a paperweight.
Just figured I would post this thread so people who want information on it can find it and fix it. In the past 2 days, I've helped 2 people fix the SDcards and no ADB. Unfortunately unable to get them back S-off or to remove the vibrate and green flash.
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...
hi
someone gave me this broken phone so i don't know what happened to get it to this point
here's the breakdown of what it's doing and what i've tried
it's a sprint variant
bootloader ver mata-8a1a76e
baseband ver 2.0.c4-m2.0.2
secure boot yes
device state locked
no power and won't turn on unless connected with a usb cable to laptop or charger but when connected stays on until unplugged
i've tried multiple cables
stuck in boot loop on powered by android screen
with vol up and power just boot loops back to the powered by android screen like there is no recovery
with vol down and power boots into fastboot mode and is visible in simple adb under the fastboot tab i'm able to see the serial number but not under the adb tab there's no devices listed
when i try to use erase or flash commands it says cannot be done in a locked state which tells me the bootloader is locked and the oem and usb debug is not turned on
it says the active slot is b but won't let me change slots because of locked statues
is there anyway to turn on oem unlock and usb debug with it not booting i've tried all of the flashing unlock bootloader commands in simple adb's fastboot tab but nothing is working i can see and talk to the phone with fastboot but because of locked bootloader i can't do anything.
any help would be great it's not important it's just a phone to play around with abd and roms to see what i can do and try to teach myself somethings but it was stock the guy that gave it to me dosen't know anything about phones he dropped it and broke the touch screen and just got another one
so if anyone could point me in the right direction or tell me if it's possible to get oem unlock and usb debug turned on in a non booting no adb connection but fastboot connectable phone with no bootable recovery
if you need anymore info just let me know
thanks in advance
hippiehemp
hippiehemp said:
hi
someone gave me this broken phone so i don't know what happened to get it to this point
here's the breakdown of what it's doing and what i've tried
it's a sprint variant
bootloader ver mata-8a1a76e
baseband ver 2.0.c4-m2.0.2
secure boot yes
device state locked
no power and won't turn on unless connected with a usb cable to laptop or charger but when connected stays on until unplugged
i've tried multiple cables
stuck in boot loop on powered by android screen
with vol up and power just boot loops back to the powered by android screen like there is no recovery
with vol down and power boots into fastboot mode and is visible in simple adb under the fastboot tab i'm able to see the serial number but not under the adb tab there's no devices listed
when i try to use erase or flash commands it says cannot be done in a locked state which tells me the bootloader is locked and the oem and usb debug is not turned on
it says the active slot is b but won't let me change slots because of locked statues
is there anyway to turn on oem unlock and usb debug with it not booting i've tried all of the flashing unlock bootloader commands in simple adb's fastboot tab but nothing is working i can see and talk to the phone with fastboot but because of locked bootloader i can't do anything.
any help would be great it's not important it's just a phone to play around with abd and roms to see what i can do and try to teach myself somethings but it was stock the guy that gave it to me dosen't know anything about phones he dropped it and broke the touch screen and just got another one
so if anyone could point me in the right direction or tell me if it's possible to get oem unlock and usb debug turned on in a non booting no adb connection but fastboot connectable phone with no bootable recovery
if you need anymore info just let me know
thanks in advance
hippiehemp
Click to expand...
Click to collapse
Hi, were you able to fix this issue?
I have the same exact problem here, its been few months actually, but still trying to figure this out.
download the offical firmware images and flash with fastboot
bootloader lock has not effect on flashing stock firmware or whatever slot its on
Legitsu said:
download the offical firmware images and flash with fastboot
bootloader lock has not effect on flashing stock firmware or whatever slot its on
Click to expand...
Click to collapse
Are you sure of that? Because Essential specifically instructs to enable "OEM Unlocking" and unlock the BL before flashing the factory image via fastboot...
Legitsu said:
download the offical firmware images and flash with fastboot
bootloader lock has not effect on flashing stock firmware or whatever slot its on
Click to expand...
Click to collapse
Oh God...
Please stop...
You are full of bad information...
You cannot use fastboot with a locked bootloader .. it is the Essential way...
hippiehemp said:
hi
someone gave me this broken phone so i don't know what happened to get it to this point
here's the breakdown of what it's doing and what i've tried
it's a sprint variant
bootloader ver mata-8a1a76e
baseband ver 2.0.c4-m2.0.2
secure boot yes
device state locked
no power and won't turn on unless connected with a usb cable to laptop or charger but when connected stays on until unplugged
i've tried multiple cables
stuck in boot loop on powered by android screen
with vol up and power just boot loops back to the powered by android screen like there is no recovery
with vol down and power boots into fastboot mode and is visible in simple adb under the fastboot tab i'm able to see the serial number but not under the adb tab there's no devices listed
when i try to use erase or flash commands it says cannot be done in a locked state which tells me the bootloader is locked and the oem and usb debug is not turned on
it says the active slot is b but won't let me change slots because of locked statues
is there anyway to turn on oem unlock and usb debug with it not booting i've tried all of the flashing unlock bootloader commands in simple adb's fastboot tab but nothing is working i can see and talk to the phone with fastboot but because of locked bootloader i can't do anything.
any help would be great it's not important it's just a phone to play around with abd and roms to see what i can do and try to teach myself somethings but it was stock the guy that gave it to me dosen't know anything about phones he dropped it and broke the touch screen and just got another one
so if anyone could point me in the right direction or tell me if it's possible to get oem unlock and usb debug turned on in a non booting no adb connection but fastboot connectable phone with no bootable recovery
if you need anymore info just let me know
thanks in advance
hippiehemp
Click to expand...
Click to collapse
Same problem here. After a official upgrade i can only access to fastboot mode. Select recovery, start, etc... reset the phone and returns to fastboot mode.
Secure boot - yes
only diference - Bootloader version mata-b9326aa and baseband 2.0.c4-M2.0.10
YaKuM0 said:
Same problem here. After a official upgrade i can only access to fastboot mode. Select recovery, start, etc... reset the phone and returns to fastboot mode.
Secure boot - yes
only diference - Bootloader version mata-b9326aa and baseband 2.0.c4-M2.0.10
Click to expand...
Click to collapse
If the bootloader is locked, and you can't get to recovery to sideload, you're stuck
Hey,
I'm trying to find a solution to this problem. My tablet is off, when I plug the tablet in I want it to boot instead of showing the charge indicator. I've tried a bunch of different avenues but I just can't get my head around how the ramdisk works for this device.
I've tried the fastboot method with "fastboot oem off-mode-charge 0" but I can't seem to get this tablet into a fastboot state.
I've tried unpacking the ramdisk from the boot partition to see if I could modifiy the init.rc script but apparently that file doesn't exist in the ramdisk, just a binary file which I can't edit.
I've tried finding a low power mode or power management binary in the /system/bin folder but none of the usual are there. How does this tablet launch its charge screen and how can we override that so it just boots?
The reason I ask is I got this tablet to use as a android auto dash in my car (new headunit is not an option as it's a Nissan Leaf and a bunch of charge timers etc. is controlled through the OEM headunit).
Laykun said:
Hey,
I'm trying to find a solution to this problem. My tablet is off, when I plug the tablet in I want it to boot instead of showing the charge indicator. I've tried a bunch of different avenues but I just can't get my head around how the ramdisk works for this device.
I've tried the fastboot method with "fastboot oem off-mode-charge 0" but I can't seem to get this tablet into a fastboot state.
I've tried unpacking the ramdisk from the boot partition to see if I could modifiy the init.rc script but apparently that file doesn't exist in the ramdisk, just a binary file which I can't edit.
I've tried finding a low power mode or power management binary in the /system/bin folder but none of the usual are there. How does this tablet launch its charge screen and how can we override that so it just boots?
The reason I ask is I got this tablet to use as a android auto dash in my car (new headunit is not an option as it's a Nissan Leaf and a bunch of charge timers etc. is controlled through the OEM headunit).
Click to expand...
Click to collapse
I guess I should mention that I'm on the 32GB WiFi. I have it on the current custom Nexus Rom and have it rooted through Magisk.
Hello!
I have an Asus zenfone 2 laser ze500kl.
Initially few day ago it was stuck on Asus Logo only I can access is twrp recovery and fastboot mode so in order to make it normal boot i flashed zip file through Aft all flash file initially in command prompt on pc it shows that "device unlock true erase sbl... and at the end Failed unknown error. Now we will try it again!"
but at that moment I disconnected my device from pc. And removed battery to turn off fastboot mode and want see will it turn on but my phone won't turn on. It's dead. no charging, no leds, no vibration. it is not recognized by PC with usb. nothing. Just dead. i removed the battery, let it without battery like, 20 seconds, put it back on, and still dead.
What can i do? Now is there any chance to make it on although device is dete to pc when I connect but won't turn on at all so pls if is there any chance to make it on pls let me I shall be much obliged to him. This is my favorite phone.
So. That's why i posting here. Some ideeas? Some chances ? i think it's I erased some file while flashing due to it wasn't turn on either in fastboot or in recovery.
Pls see attached flashing pic
*Sorry for bad english*