This morning I woke up to discover that my phone will not boot. It just sits on the HTC splash screen until I hold the power button down and turn it off. I can get the phone into bootloader, but when I try to boot into recovery the phone just freezes. I can enter Fastboot mode, and it shows "fastboot USB" when connected to a computer, but any command I try to run via ADB fails. For example, when trying to erase cache it goes like this:
Code:
fastboot erase cache
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 1.369s
I've also tried running some commands using Hasoon2000's All-in-one toolkit, but it always returns a "error: device not found" message on the first popup, and then fails to complete the task. For example, attempting to flash a new recovery goes like this:
Code:
sending 'recovery' (7420 KB)...
OKAY [ 1.142s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.322s
The phone does show up as "My HTC" under the "Android USB Devices" heading in my PC's device manager, and the drivers appear to be up to date.
I was running Pac-man ROM nightly from Sept. 19, and I had no issues with it for over a week. Hboot version is 1.44.0000. I haven't flashed a custom kernel or radio at all.
Any thoughts on what could be wrong, and how I might go about fixing it?
I would also accept any tips on getting rid of the "this build is for development purposes only" screen so I can at least return the phone under warranty.
Related
does anyone know where to get help with fastboot in ubuntu? i have tried flashing a recovery image to my Dell Streak 7, but it keeps failing. fastboot is working, and when i send the command "fastboot reboot" it works fine. however, "fastboot devices" returns "????????????". when i try to flash the recovery, i get
"sending 'recovery' (3654 KB)...
FAILED (command write failed (No such device))
finished. total time: 0.000s"
"fastboot getvar version" returns version: LG7 0.4
so i know fastboot is working, and that it has at least some communication with the tablet, but something is not quite working. any ideas?
SOLVED
i'm not sure what happened differently, but i plugged the tablet into a different USB port, and then i got a max-download-size error when flashing the recovery. i came across another post that said to use "fastboot -S 0 flash..." to resolve that error, and it worked. everything seems to be good now
Ok, so I'll be the first to admit, I'm a bit new to all this.... I figured I was following directions, but something went amiss...
I was working through the process to put CM11 on my Razr i (which had the soak of 4.4.2 from Motorola on it...).
I unlocked the bootloader, rooted it, (but of course never made a back-up). I was able to put in TWRP into the recovery partition and attempt to flash the OS zip image - which failed.
In that thread, there were many options to try, which I did, and eventually my phone will either get stuck at the "Warning - Bootloader Unlocked" screen, or if I reboot with Power/VolDown I can get into Fastboot. But every option in Fastboot menu just reboots the phone.
I can get to the phone with Fastboot from the PC through USB - and it *looks* like I can re-flash different recovery images, but nothing seems to change. The Lebobo flasher will not flash to the device at all - keeps saying "waiting for device" with any option. I have the Motorola USB drivers loaded.
Not sure what else to try.....
Check your drivers again and even reinstall them. U will need the Motorola ones and maybe even the Google ones.
The lebobo flasher uses the 'fastboot' executable to interact with the phone in fastboot. Get a copy off the fastboot exe from the Index thread in the general section. If u have the fastboot.exe or 'fastboot' binary if u are on linux then reboot your phone in bootloader mode. Open a commandprompt in the directory where u have the fastboot executable (shift+right mouse button). Now do the command "fastboot devices" if your device shows up in it the drivers are correctly installed. If it doesn't it not. If it does, install a recovery by using the command "fastboot flash recovery recovery.img" assuming u renamed the recovery image to recovery.img.
i have the same probleme , my motorola razr i is stuck on warning ......... help me pleas:crying:
Verified Moto driver installed (reinstalled).
fastboot.exe is latest from Android SDK - api 21 version
fastboot devices shows "TA237059P0 fastboot"
fastboot flash recovery recovery.img looks like it works. on the PC says "OKAY" and finished. On the phone says Downloading.... then Flashing recovery ... but just sits there. Tried with 2 different Recovery images.
Forgot to mention - in command window on PC, when I use above commend - first thing that comes back "(bootloader) Variable not supported!"
If I use fastboot menu on the phone to then go to Recovery, the phone reboots and sits at the Warning screen again.
Lelobo still says "waiting for device" even though command line fastboot seems to connect to the device.
Wipe cache through fastboot and try again. It van help
fastboot -w give the following....
(bootloader) Variable not supported!
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote failure)
(bootloader) Variable not supported!
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote failure)
erasing 'userdata'...
(bootloader) Creating EXT4 FileSystem for userdata
OKAY [ 13.707s]
erasing 'cache'...
(bootloader) Creating EXT4 FileSystem for cache
OKAY [ 2.902s]
finished. total time: 16.614s
Then flashing recovery behaves same as above, except when I select it in the Fastboot menu, the phone just shuts off now (tried different recovery, now it reboots, stuck at Warning)
ccallana said:
fastboot -w give the following....
(bootloader) Variable not supported!
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote failure)
(bootloader) Variable not supported!
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote failure)
erasing 'userdata'...
(bootloader) Creating EXT4 FileSystem for userdata
OKAY [ 13.707s]
erasing 'cache'...
(bootloader) Creating EXT4 FileSystem for cache
OKAY [ 2.902s]
finished. total time: 16.614s
Then flashing recovery behaves same as above, except when I select it in the Fastboot menu, the phone just shuts off now (tried different recovery, now it reboots, stuck at Warning)
Click to expand...
Click to collapse
Success!! used "fastboot erase cache" instead.... then flashed in the suggested Newbie recovery on page 1 of the CM11 thread. adb wouldn't sideload the modded image, so I stuck it on an sd card and loaded it from there... and voila, it is booting!
There's a lot of similar threads on this and I have tried every method I could find and nothing has helped.
Yesterday I took a stock KFHD7 and rooted it, flashed teamwin recovery 2.6.3.1 and freedom boot 7.4.6, and then flashed CM 12.1 and the appropriate gapps. Everything was working GREAT except I had a problem downloading the Google Play Games app through the App store (Error -505) and I read the wasiest way to handle it on a new install was to just Factory Restore through CM 12.1. It wasn't until AFTER I rebooted that someone mentioned that doing that on CM 12.1 on a KFHD7 could seriously mess things up.
Now when I turn it on it shows the orange kindle fire logo, the blue kindle fire logo, then the teamwin logo, and then it flashes off briefly and goes back to the teamwin logo for a few more seconds before repeating flashing and teamwin over and over.
I was told I need to reflash the freeboot and teamwin recovery via fastboot. I had a lot of issues in that "fastboot dvices" does not return anything. "fastboot -i 0x1949 getvar product" returns that I have the Tate. Attempting to use fastboot without the "-i 0x1949" parameter causes it to display "< waiting for device >" indefinitely. adb seems to work, but any shell commands I attempt to send return that the command is not found.
So I tried this:
Code:
C:\Users\ChrisS2.HQ\Desktop\kinfire\root\stuff>fastboot -i 0x1949 flash boot kin
boot.img
target reported max download size of 1006632960 bytes
sending 'boot' (8145 KB)...
OKAY [ 2.173s]
writing 'boot'...
OKAY [ 0.572s]
finished. total time: 2.749s
C:\Users\ChrisS2.HQ\Desktop\kinfire\root\stuff>fastboot -i 0x1949 flash recovery
kinrecovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8145 KB)...
OKAY [ 2.182s]
writing 'recovery'...
OKAY [ 0.578s]
finished. total time: 2.763s
C:\Users\ChrisS2.HQ\Desktop\kinfire\root\stuff>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.001s
C:\Users\ChrisS2.HQ\Desktop\kinfire\root\stuff>
It's repeating the same behavior.
I've double checked and triple checked my drivers. The device is listed as "Kindle -> ADB Composite Device". Everythign seems to be fine on that end. I am using Windows 7 x64. I tried the fk scripts on Ubuntu with no success.
Edit: I also made my own Factory cable. Doesn't seem to have any affect on the process.
Two days of trying to figure this out and I fix it minutes after I ask for help.
I retried using the KFHD SRT v1.35 to recover the system image, deleted all user data and cache, then reformatted the /data partition. It can now boot properly into the teamwin recovery and flash ROMs as usual.
Here's a good article for people who had the same issue:
http://androidcowboy.com/2013/06/how-to-return-kindle-fire-hd-to-stock/
Got my bootloader unlocked, but when trying to flash or unlock critical I get an error and it goes to a screen with the razer logo, "powered by android" at the bottom, and super small text in the upper left "press any key to shutdown"
and shows this in the cmd window:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock_critical
< waiting for any device >
...
FAILED (command write failed (No error))
finished. total time: 0.027s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot_a arter97-kernel-r9-20190607.img
< waiting for any device >
target didn't report max-download-size
sending 'boot_a' (30140 KB)...
FAILED (command write failed (No error))
finished. total time: 0.011s
I do have the full sdk package and used android studios sdk manager to get the latest google usb driver.
HTML:
EDIT: Also I'm on a global version (bought it on razer's website)
Download any version of the firmware available on the Razer developer portal then run the flash-all script. Once that's done, flash boot and system images separately on both partitions just to be on the safe side. Your phone should be able to boot normally after that. Just run setup, flash arter97's kernel, boot into TWRP and try to enter your lock code (odds are this'll fail), then reboot into TWRP, this time your password/lock code should work, then flash Magisk
blackknightavalon said:
Download any version of the firmware available on the Razer developer portal then run the flash-all script. Once that's done, flash boot and system images separately on both partitions just to be on the safe side. Your phone should be able to boot normally after that. Just run setup, flash arter97's kernel, boot into TWRP and try to enter your lock code (odds are this'll fail), then reboot into TWRP, this time your password/lock code should work, then flash Magisk
Click to expand...
Click to collapse
Running the flash_all script just throws it into that shutdowns again and keeps going into it anytime I go back into fastboot mode.
also gives me this
Code:
C:\Users\zacha\Desktop\platform-tools>fastboot devices
my S/N fastboot
C:\Users\zacha\Desktop\platform-tools>flash_all
C:\Users\zacha\Desktop\platform-tools>set fastboot_cmd=fastboot
C:\Users\zacha\Desktop\platform-tools>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed.
or is just sits there likes this:
Code:
C:\Users\zacha\Desktop\platform-tools>adb reboot bootloader
C:\Users\zacha\Desktop\platform-tools>flash_all
C:\Users\zacha\Desktop\platform-tools>set fastboot_cmd=fastboot
C:\Users\zacha\Desktop\platform-tools>fastboot flash partition:0 gpt_both0.bin
In that case, fastboot flash each part individually under both partitions (where applicable) and you should be back to stock
blackknightavalon said:
In that case, fastboot flash each part individually under both partitions (where applicable) and you should be back to stock
Click to expand...
Click to collapse
Just does the exact same thing.
Cyclo_sarin said:
Just does the exact same thing.
Click to expand...
Click to collapse
I'm having the exact same issue. I'm unable to get any flash to work. Tried multiple different machines. Keep getting the same errors. Did you find a solution?
Code:
c:\adb>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.005s
Then my RP2 will go to the "Powered by Android" screen with the Razer logo and say "Press any key to shutdown"
I can use "fastboot devices" and get my devices serial number back along with rebooting the bootloader so I don't think it's a driver issue. Out of options and could use some help. At this point I can't even get the factory images to flash.
RP2 - ATT
xCROv said:
I'm having the exact same issue. I'm unable to get any flash to work. Tried multiple different machines. Keep getting the same errors. Did you find a solution?
Code:
c:\adb>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.005s
Then my RP2 will go to the "Powered by Android" screen with the Razer logo and say "Press any key to shutdown"
I can use "fastboot devices" and get my devices serial number back along with rebooting the bootloader so I don't think it's a driver issue. Out of options and could use some help. At this point I can't even get the factory images to flash.
RP2 - ATT
Click to expand...
Click to collapse
Incorrect cord?
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Razer recommends you use a USB 3 Type-A to Type-C spec-compliant cable for any device flashing.
Click to expand...
Click to collapse
Or old ADB/Fastboot: https://developer.android.com/studio/releases/platform-tools.html
xCROv said:
I'm having the exact same issue. I'm unable to get any flash to work. Tried multiple different machines. Keep getting the same errors. Did you find a solution?
Code:
c:\adb>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.005s
Then my RP2 will go to the "Powered by Android" screen with the Razer logo and say "Press any key to shutdown"
I can use "fastboot devices" and get my devices serial number back along with rebooting the bootloader so I don't think it's a driver issue. Out of options and could use some help. At this point I can't even get the factory images to flash.
RP2 - ATT
Click to expand...
Click to collapse
BeardKing said:
Incorrect cord?
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Or old ADB/Fastboot: https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
Have ya'll tried using this tool?? It works I'm telling you it'll solve any issues you have with ADB and or FASTBOOT period....
https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445
I am trying to unlock the bootloader and flash TWRP for the first time. I followed the steps from here: https://wiki.lineageos.org/devices/s2/install
I turned on the unlock option in settings and unlocked via fastboot, rebooted it manually (it didn't reboot), and then tried to flash:
Code:
$ ./fastboot oem unlock-go
OKAY [ 0.007s]
Finished. Total time: 0.007s
$ ./fastboot flash recovery twrp-3.3.1-0-s2.img
Sending 'recovery' (24618 KB) OKAY [ 0.859s]
Writing 'recovery' FAILED (remote: 'Partition flashing is not allowed')
fastboot: error: Command failed
$ ./fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.001s
$ ./adb reboot bootloader
$ ./fastboot flash recovery twrp-3.3.1-0-s2.img
Sending 'recovery' (24618 KB) OKAY [ 0.779s]
Writing 'recovery' FAILED (remote: 'Partition flashing is not allowed')
fastboot: error: Command failed
$ ./fastboot oem unlock-go
OKAY [ 0.007s]
Finished. Total time: 0.007s
$ ./fastboot flash recovery twrp-3.3.1-0-s2.img
Sending 'recovery' (24618 KB) OKAY [ 0.836s]
Writing 'recovery' OKAY [ 0.231s]
Finished. Total time: 1.071s
$ ./fastboot reboot recovery
Rebooting into recovery OKAY [ 0.001s]
Finished. Total time: 0.001s
However, I got into the stock recovery page instead of TWRP. You can see above that the flash failed before I rebooted, but succeeded after that. Interesting observations:
- The above webpage indicates that the device should reset when I reboot, but it didn't, which means the unlock didn't work.
- When I went back to bootloader, the first attempt to flash failed, but when I ran another unlock it worked though apparently it did nothing.
Am I missing a step? I am using fastboot version 29.0.6-6198805 on Mac OS Mojave 10.14.6.
Don't reboot to recovery via a command after flashing it.
Try rebooting using buttons, vol-up + power.
kalehrl said:
Don't reboot to recovery via a command after flashing it.
Try rebooting using buttons, vol-up + power.
Click to expand...
Click to collapse
Thank you! That got me into TWRP with a dialog titled "Unmodified System Partition" with a slider to allow modifications. I am googling to see what this dialogue is about and how to get TWRP to permanently get installed.
That's normal. Just enable modifications and that's it.
kalehrl said:
That's normal. Just enable modifications and that's it.
Click to expand...
Click to collapse
OK, I don't remember seeing it before (I haven't flashed in at least a couple of years). I ran `adb reboot recovery` and it did go back into TWRP, so I am assuming that it did get persisted. For some reason "Never show this screen..." option didn't work, which is fine, but does it indicate that something is still readonly?
I don't think so.
You're good to proceed.
I was able to sideload the ROM and opengapps nano and it is booting up for the first time. I skipped the optional step to install root (AddonSU), I guess I can do it later too if I feel the need to get root. Thanks a lot for your quick help.
No problem.
If you want to root it, do it with Magisk.
Nowadays, LineageOS team recommend it.