[Q] Stuck at Splash Screen (HTC quietly brilliant) - One (M7) Q&A, Help & Troubleshooting

Hi guys
My HTC One is stuck at the splash screen and I can't hard reset it (tried all button combos, power, power + volume down, power + volume up). The soft buttons blink but it won't reboot. How this happened? Forst i got the OTA Update (2.24.161.1), but I was on CWM so it didn't install. I did a factory reset to remove xposed and to clean up my phone (this naturally preserved su binary and superuser app). I flashed stock e3 recovery and tried the update again, but it failed at "Running bug_fix1 tool". I was stuck there for 1 hour until the battery died. Re-downloaded the update, tried again but failed. Then I copied the OTA update to my computer (it's in /data/data/com.android.providers.downloads/cache) and edited the updater-script: I removed all the CID and Model checks and all apply_patch_check. Reflashed CWM and copied the patched OTA Update to the virtual SD-Card. The update failed again, something was wrong with ChromeWithBrowser.apk
Code:
assert(apply_patch("/system/app/ChromeWithBrowser.apk", "-",
ca5305a26ac876a698b8b58db8b4cd375f61cfff, 8088485,
87cd8a4bb3038a51e15ec032d4d8dbe5cfb412f6, package_extract_file("patch/system/app/ChromeWithBrowser.apk.p")));
So I made a new patch for the updater-script and I booted the phone. Now i'm stuck at the splash screen because the OTA update couldn't finish.
The phone doesn't charge (or at least the red light doesn't show up) and neither adb nor fastboot recognise the device. Only the OS seems to recognise it:
Code:
# nicolas at nbuntu in /data/Android/HTC One/Recovery [14:30:30]
$ lsusb
Bus 003 Device 060: ID 0bb4:0f91 HTC (High Tech Computer Corp.)
Bus 004 Device 002: ID 046d:c526 Logitech, Inc. Nano Receiver
Bus 005 Device 002: ID 046d:c318 Logitech, Inc. Illuminated Keyboard
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
I'm on Stock ROM with revone S-OFF, unlocked bootloader, super CID and CWM recovery. I have a backup of the system partition on my computer.
Before I tried the OTA update I did a fastboot getvar all:
Code:
fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.44.0000
INFOversion-baseband: 4A.14.3250.13
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.29.161.11
INFOversion-misc: PVT SHIP S-OFF
INFOserialno: SH**
INFOimei: **
INFOmeid: **
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: 1111111
INFObattery-status: good
INFObattery-voltage: 3744mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOgencheckpt: 0
all: Done!
I hope someone can give me a hint how to get out of that...

nicu96 said:
Hi guys
My HTC One is stuck at the splash screen and I can't hard reset it (tried all button combos, power, power + volume down, power + volume up). The soft buttons blink but it won't reboot. How this happened? Forst i got the OTA Update (2.24.161.1), but I was on CWM so it didn't install. I did a factory reset to remove xposed and to clean up my phone (this naturally preserved su binary and superuser app). I flashed stock e3 recovery and tried the update again, but it failed at "Running bug_fix1 tool". I was stuck there for 1 hour until the battery died. Re-downloaded the update, tried again but failed. Then I copied the OTA update to my computer (it's in /data/data/com.android.providers.downloads/cache) and edited the updater-script: I removed all the CID and Model checks and all apply_patch_check. Reflashed CWM and copied the patched OTA Update to the virtual SD-Card. The update failed again, something was wrong with ChromeWithBrowser.apk
Code:
assert(apply_patch("/system/app/ChromeWithBrowser.apk", "-",
ca5305a26ac876a698b8b58db8b4cd375f61cfff, 8088485,
87cd8a4bb3038a51e15ec032d4d8dbe5cfb412f6, package_extract_file("patch/system/app/ChromeWithBrowser.apk.p")));
So I made a new patch for the updater-script and I booted the phone. Now i'm stuck at the splash screen because the OTA update couldn't finish.
The phone doesn't charge (or at least the red light doesn't show up) and neither adb nor fastboot recognise the device. Only the OS seems to recognise it:
Code:
# nicolas at nbuntu in /data/Android/HTC One/Recovery [14:30:30]
$ lsusb
Bus 003 Device 060: ID 0bb4:0f91 HTC (High Tech Computer Corp.)
Bus 004 Device 002: ID 046d:c526 Logitech, Inc. Nano Receiver
Bus 005 Device 002: ID 046d:c318 Logitech, Inc. Illuminated Keyboard
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
I'm on Stock ROM with revone S-OFF, unlocked bootloader, super CID and CWM recovery. I have a backup of the system partition on my computer.
Before I tried the OTA update I did a fastboot getvar all:
Code:
fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.44.0000
INFOversion-baseband: 4A.14.3250.13
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.29.161.11
INFOversion-misc: PVT SHIP S-OFF
INFOserialno: SH**
INFOimei: **
INFOmeid: **
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: 1111111
INFObattery-status: good
INFObattery-voltage: 3744mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOgencheckpt: 0
all: Done!
I hope someone can give me a hint how to get out of that...
Click to expand...
Click to collapse
Why your CID is 1111111 instead of 11111111. ???

99piotrek said:
Why your CID is 1111111 instead of 11111111. ???
Click to expand...
Click to collapse
Sorry, it's 11111111, copy-paste fail...

Did u try hold power button and vol down under bright light?
It should help and go to bootloader...
For like 15-20 seconds

Thank you so much, it worked! Do you have a clue why the hard-reset is somehow dependent on the light sensor?

nicu96 said:
Thank you so much, it worked! Do you have a clue why the hard-reset is somehow dependent on the light sensor?
Click to expand...
Click to collapse
Our ONE is scared of darkness...
Nobody really knows...
We gotta be glad that somebody found out...

99piotrek said:
Our ONE is scared of darkness...
Nobody really knows...
We gotta be glad that somebody found out...
Click to expand...
Click to collapse
its to stop the phone resetting itself if its pressed inside someone's pocket

99piotrek said:
Did u try hold power button and vol down under bright light?
It should help and go to bootloader...
For like 15-20 seconds
Click to expand...
Click to collapse
Thanks guys you light up my life :victory:

Related

[solved] bricked my Captivate

I tried flashing ICS_4.0.3_r1-RC1.0.1-i897.zip to my Captivate, now my captivate won't go past the AT&T screen.
I was on CM7.1 before I attempted to flash. From what I understand, if I can get into Recovery mod I can flash CM7 to my phone and start this entire process over again. However, I downloaded ADB and now I'm not sure what to do to fix this. I have my phone in Download mode and it's connected to my laptop.
I don't think ADB recognizes my phone. What should I do?
Code:
[email protected]:/home/kenny2/AndroidSDK/platform-tools# adb reboot recovery
error: device not found
[email protected]:/home/kenny2/AndroidSDK/platform-tools# adb devices
List of devices attached
[email protected]:/home/kenny2/AndroidSDK/platform-tools# lsusb
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 046d:c52f Logitech, Inc. Wireless Mouse M305
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 010: ID 04e8:6601 Samsung Electronics Co., Ltd Z100 Mobile Phone
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0bda:0158 Realtek Semiconductor Corp. USB 2.0 multicard reader
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[email protected]:/home/kenny2/AndroidSDK/platform-tools#
I am using Ubuntu 11.04, 64 bit - if that matters.
Adb doesn't work in download mode
Flash stock. Then follow install instructions to flash any ROM you want.
Where can I get the stock roms? I just downloaded one from this thread but all I got was a rar file with an exe file inside.
I need something I can load up from Heimdall. I'll try running the exe file through WINE but I don't think it will work.
Edit: Confirmed, that does not work in Wine.
Edit2: Trying this now.
Hit the sig link below. Heimdall Stock KB2. After it's downloaded, right click/permissions/Mark as executable. Then just open with java.
Thanks for the tip mrhaley30705. However, I fixed it before I saw your link. I used this: http://forum.xda-developers.com/showthread.php?p=17050435
Which gave me SGH-i897-UCKH3-One-Click.jar. This put my phone on 2.3.4. Problem solved as I'm no longer bricked.
Glad you got it going.

(solved)bootloader problems linux mint

Hi everone
I recently bought Xperia Z. Now I'm trying to unlock my bootloader. I use linux mint 16, Windows and me are not friends,
I have got fastboot to work if I for exampel type fsatboot devices it works.But when i write
sudo fastboot -i 0x0fce oem unlock 0xKEY I get this:
...
FAILED (remote: Command did not succeed)
finished. total time: 0.004s
Someone how can help me?
With best regards
Bobin
Did you replace "key" with the key sony send you?
---------- Post added at 12:02 PM ---------- Previous post was at 12:02 PM ----------
Also is 0x0fce your phone?, what's the output of lsusb?
St.Jimmy90 said:
Did you replace "key" with the key sony send you?
---------- Post added at 12:02 PM ---------- Previous post was at 12:02 PM ----------
Also is 0x0fce your phone?, what's the output of lsusb?
Click to expand...
Click to collapse
About the key: Yes i did.
lsusb????
With best regards bobin
Type in the terminal lsusb and post the output
St.Jimmy90 said:
Type in the terminal lsusb and post the output
Click to expand...
Click to collapse
I got nothing
Now I got Windows fastboot working. I have tried from CMD and get the same thing, and with flashtool it is the same.
So i'm really stuck.
Anyone has an idea?
eldrood said:
Now I got Windows fastboot working. I have tried from CMD and get the same thing, and with flashtool it is the same.
So i'm really stuck.
Anyone has an idea?
Click to expand...
Click to collapse
Is your phone in fastboot, or in flashmode, when you try it?
What's the output of
fastboot devices
?
St.Jimmy90 said:
Is your phone in fastboot, or in flashmode, when you try it?
What's the output of
fastboot devices
?
Click to expand...
Click to collapse
In fastbootmode when i try it.
How can i see the output?
Lsusb don work...
eldrood said:
In fastbootmode when i try it.
How can i see the output?
Lsusb don work...
Click to expand...
Click to collapse
If there's a device connected, you will see it, you can try it both in windows and linux (I guess xD)
lsusb is a linux command, it shows what devices are connected via usb.
St.Jimmy90 said:
If there's a device connected, you will see it, you can try it both in windows and linux (I guess xD)
lsusb is a linux command, it shows what devices are connected via usb.
Click to expand...
Click to collapse
In linux i get nothing with lsusb....
How will i see it?
I see it if type, fastboot devices, but what is the commando for usb output?
eldrood said:
In linux i get nothing with lsusb....
How will i see it?
I see it if type, fastboot devices, but what is the commando for usb output?
Click to expand...
Click to collapse
Ok, on Arch my output of lsusb looks like this:
Code:
Bus 002 Device 003: ID 0fce:0193 Sony Ericsson Mobile Communications AB
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 058f:a014 Alcor Micro Corp. Asus Integrated Webcam
Bus 001 Device 009: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Though it looks the same in ANY linux. You have to type it into your terminal
St.Jimmy90 said:
Ok, on Arch my output of lsusb looks like this:
Code:
Bus 002 Device 003: ID 0fce:0193 Sony Ericsson Mobile Communications AB
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 058f:a014 Alcor Micro Corp. Asus Integrated Webcam
Bus 001 Device 009: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Though it looks the same in ANY linux. You have to type it into your terminal
Click to expand...
Click to collapse
Sudo solved it....
I get this:
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 002: ID 8087:07da Intel Corp.
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 064e:e263 Suyin Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 002: ID 1038:1384 Ideazon, Inc.
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 002: ID 0fce:0dde Sony Ericsson Mobile Communications AB Xperia Mini Pro Bootloader
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 046d:c31f Logitech, Inc.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Thaks for trying the help
Hope we can solve this
eldrood said:
Sudo solved it....
I get this:
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 002: ID 8087:07da Intel Corp.
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 064e:e263 Suyin Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 002: ID 1038:1384 Ideazon, Inc.
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 002: ID 0fce:0dde Sony Ericsson Mobile Communications AB Xperia Mini Pro Bootloader
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 046d:c31f Logitech, Inc.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Thaks for trying the help
Hope we can solve this
Click to expand...
Click to collapse
I just see a Xperia Mini... Was your Xperia Z plugged in?
St.Jimmy90 said:
I just see a Xperia Mini... Was your Xperia Z plugged in?
Click to expand...
Click to collapse
I saw that too, I dont own a Xperia mini?
Just an xperia Z thats plugged in....
Something is wrong
eldrood said:
I saw that too, I dont own a Xperia mini?
Just an xperia Z thats plugged in....
Something is wrong
Click to expand...
Click to collapse
Maybe you've installed the wrong drivers? I'm installing fastboot and adb drivers right now, I'll report back the output when they're installed
St.Jimmy90 said:
Maybe you've installed the wrong drivers? I'm installing fastboot and adb drivers right now, I'll report back the output when they're installed
Click to expand...
Click to collapse
Could you point me at the right drivers?
Sound good
eldrood said:
Could you point me at the right drivers?
Sound good
Click to expand...
Click to collapse
Do you have android sdk installed?
St.Jimmy90 said:
Do you have android sdk installed?
Click to expand...
Click to collapse
yes have sdk installed
eldrood said:
yes have sdk installed
Click to expand...
Click to collapse
Is usb-debugging on your phone turned on?
St.Jimmy90 said:
Is usb-debugging on your phone turned on?
Click to expand...
Click to collapse
Yes

Can't get ADB running

Hi,
i can't get ADB running. I activated it in the developer options and tried also checking and unchecking the usb 2 option.
On my Computer i'm running Linux Mint 17.1.
When imt checking for adb devices it's just an empty list.
I also tried this Instruction but it didn't help.
I really don't know what to do.
nme1337 said:
Hi,
i can't get ADB running. I activated it in the developer options and tried also checking and unchecking the usb 2 option.
On my Computer i'm running Linux Mint 17.1.
When imt checking for adb devices it's just an empty list.
I also tried this Instruction but it didn't help.
I really don't know what to do.
Click to expand...
Click to collapse
connect the device to a usb port and show the output of command
Code:
lsusb
Tommmii said:
connect the device to a usb port and show the output of command
Code:
lsusb
Click to expand...
Click to collapse
Code:
Bus 002 Device 003: ID 1532:010e Razer USA, Ltd
Bus 002 Device 004: ID 2b4c:1015
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 1210:25f4 DigiTech
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
while
Code:
Bus 002 Device 004: ID 2b4c:1015
is my Phone
Also my Phone doesn't ask for the permissions for the PC to connect with ADB.
And I tried switching between mtp and ptp.
nme1337 said:
Code:
Bus 002 Device 003: ID 1532:010e Razer USA, Ltd
Bus 002 Device 004: ID 2b4c:1015
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 1210:25f4 DigiTech
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Click to expand...
Click to collapse
what's in your file /etc/udev/rules.d/51-android.rules ?
Tommmii said:
what's in your file /etc/udev/rules.d/51-android.rules ?
Click to expand...
Click to collapse
****, somehow i'm the biggest idiot i misspelled and wrote 1013 instead of 1015.
feel so dump now. i was looking so often at it and didn't realize... sry

[SOLVED] Stock Nexus 6 in endless bootloop (without USB debugging!)

Hi!
:crying:
Help needed! My 10 year old kid has Motorola Nexus 6 (XT1100). The phone is a second hand phone but it should be in original condition? Service shop upgraded a new battery about 2 months ago.
Problem:
For some reason the phone has went into an endless bootloop (Google -logo screen, [vibration], reboot cycle). By pressing the volume down it goes to the bootloader (see details below).
Code:
AP Fastboot Flash Mode (secure)
BL: moto-apq8084-72.04 (sha-b11eacf, 2017-07-13 16:59:20)
Baseband: D4.01-9625-05.45+FSG-9625-02.117
Product/Variant: shamu XT1100 64GB P3A0
Serial Number: ZX1G5237TV
CPU: APQ8084 ES.1
eMMC: 64GB Hynix RV=07 PV=03 TY=57
DRAM: 3072MB Samsung S8 SDRAM DIE=6Gb
Console [NULL]: null
Battery OK (Charging)
Device is LOCKED. Status Code: 2
Transfer Mode: USB Connected
Trouble shooting:
In Bootloader clicking "Factory Mode" does nothing.
Can't put device to USB debugging mode as it is in bootloop?
https://developer.android.com/studio/debug/dev-options
Can't do full OTA update image as "adb reboot recovery" command do not recognize the device (see below)
https://developers.google.com/android/ota
Tried to follow the beginners guide without success as command [fastboot oem unlock] did not work!
[HOW-TO] The Nexus 6 All-In-One Beginner's Guide
https://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
I don't know what to do next? Please help :crying::crying::crying:
I connected it to my Ubuntu 18.04LTS laptop with USB cable.
Code:
$ lsusb
Bus 002 Device 005: ID 18d1:4ee0 Google Inc.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
$ adb devices
List of devices attached
$ adb reboot recovery
error: no devices/emulators found
$ fastboot devices -l
ZX1G5237TV fastboot usb:2-1
$ fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.006s
$ fastboot reboot
rebooting...
finished. total time: 0.151s
$
ADB without USB Debugging on?
I don't have USB debugging enabled. Otherwise I would solve it like this! Still waiting for a solution!
https://www.youtube.com/watch?v=Vscps1gNn0U
Connect phone with USB cable to computer
Start phone bootloader by pressing power and volume down
Select recovery mode
Open Recovery menu by pressing power and volume up
Check your software version (e.g. 7.1.1/N6F27M/4299435) and download the full OTA image version
https://developers.google.com/android/ota
select from Phone Recovery menu APPLY UPDATE FROM ADB
check from computer that ADB DEVICES command can see the phone in sideload mode
Execute ADB SIDELOAD [IMAGE.ZIP] command
[SOLVED]
Here's the solution! Thank you for the help :good::good::good::good:
Start phone bootloader by pressing power and volume down
Select recovery mode
Open Recovery menu by pressing power and volume up
Select Wipe data/Factory reset
Select Wipe cache partition
Select Reboot system now
how to apply solution when recovery mode screen is dead android with red triangle and "No Command" text?
janekw said:
how to apply solution when recovery mode screen is dead android with red triangle and "No Command" text?
Click to expand...
Click to collapse
Did you press the volume up key?
yes
janekw said:
yes
Click to expand...
Click to collapse
Interesting. Pressing the volume up key is how you get into the stock recovery when Andy is laying on his back. That may mean a bad volume control. In your case you may have little choice but to flash a factory image by entering the device's bootloader and using fastboot.

Can't connect with fastboot or adb, Fastboot Reason: Flash Failure

Hi,
A few months ago, I tried flashing e-os on my old Moto X (2014). Something went wrong and I didn't look at it until now because of a lack of time.
When I connect the phone to my computer or a power brick, it goes immediately in AP Fastboot Flash Mode (S). I think I flashed something wrong in the wrong place. I can't connect with adb or fastboot (tried the fastboot from the package in the openSUSE linux repositories, the one from the android-platform tools on the android website and linux-fastboot from mfastboot), I tried different USB-cables (even one labeled as a "data cable") and ports.
The screen looks like this:
AP Fastboot Flash Mode (S)
30.BE (sha-34b7ccb, 2015-04-22 12:57:17)
eMMC: 16GB Sandisk RV=06 PV=07 TY=17
DRAM: 2048MB Samsung S4 SDRAM DIE=4Gb
Up Time: 10 minutes
Device is UNLOCKED. Status Code: 3
Battery OK
Transfer Mode: USB Connected
Boot Mode Selection Menu
Vol Up Selects, Vol Down Scrolls
Normal Powerup
Recovery
Factory
Barcodes
BP Tools
Fastboot REason: Flash Failure
USB connected
Selecting Recovery shows the "bootloader unlocked" warning screen and then an android on his back with a red warning triangle ().
Selecting Factory or BP Tools leads to the warning screen and then the menu again.
Normal Powerup gives the warning screen, a black screen (and vibrates, probably it restarts), the warning screen again and then the dead android with the warning triangle.
I don't remember what exactly I did last time.
Thank you for any advice.
Kind regards,
Twijg
https://gist.github.com/smac89/251368c8df2ccd645baedc3e1238fdb4
Thank you for the reply.
No new usb-device showed up, which is weird. I tried all three ports and two different cables. The ports at least work with my keyboard and mouse.
This is an output I got, it was the same with or without the phone attached:
Code:
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 003 Device 004: ID 13d3:5458 IMC Networks USB2.0 HD UVC WebCam
Bus 003 Device 003: ID 413c:2003 Dell Computer Corp. Keyboard SK-8115
Bus 003 Device 006: ID 13d3:3563 IMC Networks Wireless_Device
Bus 003 Device 002: ID 046d:c063 Logitech, Inc. DELL Laser Mouse
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 0781:55ae SanDisk Corp. Extreme 55AE
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I also tried again with my keyboard and mouse unplugged.
disconnect usb, power off phone, press and keep holding both volume keys, connect usb
Thank you, that helped indeed. I was able to connect with fastboot and flash the recovery img.
That issue is solved now.
I now have a different problem where selecting recovery leads to an endless series of restarts to the unlocked bootloader warning screen. If you happen to know what the reason for that could be... I'll go looking online and in the fora as well and edit this message with the link to a solution if I find one.
Thank you again!

Categories

Resources