Related
So I got my Kindle Fire a few months ago, already rooted. I went from TWRP to a CWM-based recovery, and I've been installing ROMs ever since without any issues. I'm currently running a CM9-based ROM, and I decided to play around with the softkeys, because I was tired of the bland white look. So I found some custom softkeys and flashed the .zip. I made sure to make a Nandroid before flashing, of course.
Upon rebooting from the flash, my KF got stuck in a bootloop. No biggie, this has happened before. I shut it down and rebooted to recovery, to restore the backup. But when it boots into recovery, it automatically reflashes the softkeys zip, and then reboots into the never-ending bootloop.
So the KF isn't necessarily bricked, I just can't get into recovery without it flashing a corrupted zip. I've tried two different unbricking tools, neither had any effect on it. Any ideas?
Can you mount SD card in Recovery and delete the Zip file through your PC?
linktohack said:
Can you mount SD card in Recovery and delete the Zip file through your PC?
Click to expand...
Click to collapse
I only wish I could. As soon as I boot into recovery, it flashed the zip, then reboots into the bootloop. I suspect this happens because I used ROM Manager to flash the zip, and recovery hasn't reset itself because the device isn't booting up all the way. So every time I try to access recovery, it performs the last action I gave it, which was to flash the zip.
I hope you aren't using Hashcode's (older) CWMR or you might be looking at a much larger problem.
http://forum.xda-developers.com/showthread.php?t=1651413
I'm not sure what's going on with your device, but the only way I know to get the recovery to do something on start up is to create a /cache/recovery/command file. That file should be a one time use command and get deleted after use, so your report of it happening each time you boot into recovery is puzzling.
If you want to take that out of the equation, I think you should either get to a shell prompt and delete the file manually or erase the cache partition entirely. Try getting to fastboot mode, boot a copy of the TWRP image, and hopefully it won't reboot on you automatically so you can use adb shell. Alternatively, erase the cache partition entirely with fastboot. If you do the latter, you'll probably need to remake the ext4 filesystem on the cache partition. Here are some fastboot references to get you started...
http://forum.xda-developers.com/showthread.php?t=1668159
http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3
kinfauns said:
I hope you aren't using Hashcode's (older) CWMR or you might be looking at a much larger problem.
http://forum.xda-developers.com/showthread.php?t=1651413
I'm not sure what's going on with your device, but the only way I know to get the recovery to do something on start up is to create a /cache/recovery/command file. That file should be a one time use command and get deleted after use, so your report of it happening each time you boot into recovery is puzzling.
If you want to take that out of the equation, I think you should either get to a shell prompt and delete the file manually or erase the cache partition entirely. Try getting to fastboot mode, boot a copy of the TWRP image, and hopefully it won't reboot on you automatically so you can use adb shell. Alternatively, erase the cache partition entirely with fastboot. If you do the latter, you'll probably need to remake the ext4 filesystem on the cache partition. Here are some fastboot references to get you started...
http://forum.xda-developers.com/showthread.php?t=1668159
http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3
Click to expand...
Click to collapse
Thanks for all that, but I managed to fastboot into it, and then wipe system and data. Then I rebooted to recovery and restored my backup. Never fastbooted into a device before, or done anything with adb commands, so it was a fun experience.
same symptoms: KF bootlooping, no recovery
Hi there,
I have a rooted/modded KF with MIUI, FFF 1.4a and TWRP.
After I gave it away to someone, who only "used it", it is now stuck in a bootloop.
I can get into fastboot via fastboot.exe and re-flashed FFF and TWRP, but no change: KF boots with the white/blue logo, I can press the powerbutton to get into recovery, but TWRP doesn´t show up. When I boot normally, it looks the same: Black screen after a few seconds.
I read about the battery issues, so I booted the KF with a fastboot command waiting to the device. The white/blue KF logo showd up and I left the device at the USB port at my PC for a complete night: no change
I tried to set another bootmode via fastboot.exe but the code doesn´t seem to make any difference.
I have a second KF which runs just fine (now with AOKP M5.1).
Is it bricked now?
Elviz42 said:
Hi there,
I have a rooted/modded KF with MIUI, FFF 1.4a and TWRP.
After I gave it away to someone, who only "used it", it is now stuck in a bootloop.
I can get into fastboot via fastboot.exe and re-flashed FFF and TWRP, but no change: KF boots with the white/blue logo, I can press the powerbutton to get into recovery, but TWRP doesn´t show up. When I boot normally, it looks the same: Black screen after a few seconds.
I read about the battery issues, so I booted the KF with a fastboot command waiting to the device. The white/blue KF logo showd up and I left the device at the USB port at my PC for a complete night: no change
I tried to set another bootmode via fastboot.exe but the code doesn´t seem to make any difference.
I have a second KF which runs just fine (now with AOKP M5.1).
Is it bricked now?
Click to expand...
Click to collapse
I'm not an expert on the KF, but from what you've described, I don't think it's bricked. Have you tried fastboot wiping system and data?
Mardenator said:
I'm not an expert on the KF, but from what you've described, I don't think it's bricked. Have you tried fastboot wiping system and data?
Click to expand...
Click to collapse
I just did:
D:\root>tools\fastboot erase system
erasing 'system'... OKAY [ 51.245s]
finished. total time: 51.246s
D:\root>tools\fastboot erase data
erasing 'data'... FAILED (remote: : partition doesn't exist)
finished. total time: 0.002s
D:\root>tools\fastboot erase userdata
erasing 'userdata'... OKAY [108.555s]
finished. total time: 108.577s
D:\root>tools\fastboot reboot
rebooting...
finished. total time: 0.001s
D:\root>
I tried to get into Recovery but no change.
Maybe it's a problem with TWRP. Have you tried fastboot flashing a CWM-based recovery?
Doesnt sound like you have twrp installed or its broken just resend twrp it should overwrite whatever is there
Thepooch said:
Doesnt sound like you have twrp installed or its broken just resend twrp it should overwrite whatever is there
Click to expand...
Click to collapse
He might want to fastboot erase recovery and then reflash TWRP.
I tried CWM:
D:\root>tools\fastboot flash boot recovery\fff.bin
sending 'boot' (243 KB)... OKAY [ 0.065s]
writing 'boot'... OKAY [ 0.052s]
finished. total time: 0.117s
D:\root>tools\fastboot flash recovery recovery\cwm.img
sending 'recovery' (5198 KB)... OKAY [ 1.321s]
writing 'recovery'... OKAY [ 1.418s]
finished. total time: 2.740s
D:\root>tools\fastboot oem idme bootmode 5001
... OKAY [ 0.667s]
finished. total time: 0.668s
D:\root>tools\fastboot reboot
rebooting...
finished. total time: 0.002s
D:\root>
No change, same behavior: Starts with white/blue letters and than "off". Entering recovery is not working.
Are you pushing the power button several times quickly when you see the white kindle blue fire and selecting recovery?
---------- Post added at 11:51 AM ---------- Previous post was at 11:49 AM ----------
You need to select with the power button or the new fff will just tell it to boot normal also twrp is better if you intend to flash anything ics related
Thepooch said:
Are you pushing the power button several times quickly when you see the white kindle blue fire and selecting recovery?
Click to expand...
Click to collapse
Yes. I also tried to enter recovery just by setting bootmode to 5001 with fastboot. This didn´t work either.
Try setting the bootmode to normal then use the power button to toggle to recovery after reflashing twrp also how your flashing them is incorrect
---------- Post added at 12:09 PM ---------- Previous post was at 12:00 PM ----------
fastboot -i 0x1949 flash recovery <file path> <name of recovery>
fastboot -i 0x1949 flash bootloader<file path><name of bootloader>
not fff.bin to recovery as you are doing but to bootloader
D:\root>tools\fastboot flash boot recovery\fff.bin
sending 'boot' (243 KB)... OKAY [ 0.065s]
writing 'boot'... OKAY [ 0.052s]
finished. total time: 0.117s
this one is really wrong your flashing the bootloader to the recovery partition dunno your doing something strange and thats your issue
you may wanna use firekit to get your bootloader and recovery correctly sent to avoid further issues http://forum.xda-developers.com/showthread.php?t=1430038
or like this leaving the id out
fastboot flash bootloader \path\to\fff.bin
fastboot flash recovery \path\to\twrp.img
Hi,
i did flash fff.img to boot(loader) , and after that CWM.img to recovery. But the image is in a folder called "recovery", perhaps this was confusing.
you wrote that you flashed it to boot not bootloader but yes its confusing
try again after an erase I guess
fastboot erase bootloader
fastboot erase recovery
or with the id -i 0x1949
Did that, no success:
D:\root>tools\fastboot getvar product
< waiting for device >
product: kindle
finished. total time: 0.000s
D:\root>tools\fastboot erase bootloader
erasing 'bootloader'... OKAY [ 0.511s]
finished. total time: 0.512s
D:\root>tools\fastboot erase recovery
erasing 'recovery'... OKAY [ 2.429s]
finished. total time: 2.429s
D:\root>tools\fastboot flash bootloader recovery\fff.bin
sending 'bootloader' (243 KB)... OKAY [ 0.065s]
writing 'bootloader'... OKAY [ 0.052s]
finished. total time: 0.117s
D:\root>tools\fastboot flash recovery recovery\openrecovery-twrp-blaze-2.1.1.img
sending 'recovery' (5568 KB)... OKAY [ 1.404s]
writing 'recovery'... OKAY [ 0.543s]
finished. total time: 1.947s
D:\root>tools\fastboot reboot
rebooting...
finished. total time: 0.001s
D:\root>
ok unplug it then hold your power button down for 1 min then power it on use power button to toggle to recovery option in boot menu see what you get if that doesnt work redownload twrp img and send that again without erase also there is a small chance you could be remaining in fastboot but I doubt it try select reset bootmode as well but you have no system at this point so getting to recovery is imperative
What does "fastboot boot twrp.img" do for you?
Short Version: Phone doesn't complete boot, bug droid red triangle exclamation in recovery. Only fastboot works in bootloader; adb doesn't work at any point anywhere. Is it possible to recover data somehow? (that's all he wants to know)
Long Version:
My coworker was at the Baltimore races this past weekend, taking pictures & video. Phone got down to about 29% so it holstered it. A while later he reaches for the phone but its dead. "Must be a dead battery" he thought. Got home, charged it up but the phone doesn't successfully boot.
This is a stock Verizon Galaxy Nexus (Toro) running 4.0.4: not unlocked & not rooted and thus USB debugging never enabled. The phone will turn on, and it displays the Google logo but never progresses beyond that. We are able to boot into the bootloader and fastboot is able to communicate with the phone without issue. But when we try booting into recovery, it takes a while and we end up seeing the droid logo with the red triangle; nothing else displayed on screen.
If we hold the three buttons from there, text fills the screen with errors like:
Code:
E:failed to mount /cache (Invalid Argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid Argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:Failed closing /dev/block/platform/omap/omap_hsmmc.0/by-name/misc (I/O error)
...
From recovery if we try wiping cache it says
Code:
-- Wiping cache...
Formatting /cache...
E:format_volume: make_extf4fs failed on /dev/block/platform/omap/omap_hsmmc.0/by-name/cache
Cache wipe complete.
(more of the same cache errors as above)
From recovery if we try to reboot it eventually reboots, but not before showing loads of errors, and it doesn't actually reboot - it turns the phone off but its in an odd state that requires battery pull.
All he really wants to do is recover as much data; mainly pictures etc. Is this possible?
Phylum said:
Short Version: Phone doesn't complete boot, bug droid red triangle exclamation in recovery. Only fastboot works in bootloader; adb doesn't work at any point anywhere. Is it possible to recover data somehow? (that's all he wants to know)
Long Version:
My coworker was at the Baltimore races this past weekend, taking pictures & video. Phone got down to about 29% so it holstered it. A while later he reaches for the phone but its dead. "Must be a dead battery" he thought. Got home, charged it up but the phone doesn't successfully boot.
This is a stock Verizon Galaxy Nexus (Toro) running 4.0.4: not unlocked & not rooted and thus USB debugging never enabled. The phone will turn on, and it displays the Google logo but never progresses beyond that. We are able to boot into the bootloader and fastboot is able to communicate with the phone without issue. But when we try booting into recovery, it takes a while and we end up seeing the droid logo with the red triangle; nothing else displayed on screen.
If we hold the three buttons from there, text fills the screen with errors like:
Code:
E:failed to mount /cache (Invalid Argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid Argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:Failed closing /dev/block/platform/omap/omap_hsmmc.0/by-name/misc (I/O error)
...
From recovery if we try wiping cache it says
Code:
-- Wiping cache...
Formatting /cache...
E:format_volume: make_extf4fs failed on /dev/block/platform/omap/omap_hsmmc.0/by-name/cache
Cache wipe complete.
(more of the same cache errors as above)
From recovery if we try to reboot it eventually reboots, but not before showing loads of errors, and it doesn't actually reboot - it turns the phone off but its in an odd state that requires battery pull.
All he really wants to do is recover as much data; mainly pictures etc. Is this possible?
Click to expand...
Click to collapse
If he has fastboot, boot a custom recovery image using 'fastboot boot recovery nameofrecovery.img. Then boot into recovery, this will allow adb access. Use adb to pull the /sdcard.
Petrovski80 said:
If he has fastboot, boot a custom recovery image using 'fastboot boot recovery nameofrecovery.img. Then boot into recovery, this will allow adb access. Use adb to pull the /sdcard.
Click to expand...
Click to collapse
??? for real? Recovery can use ADB ??? i always thought it has to be in the Android system only
qtwrk said:
??? for real? Recovery can use ADB ??? i always thought it has to be in the Android system only
Click to expand...
Click to collapse
Nope, CWM and TWRP has USB debug on and thanks to that, ADB is possible through them. Really useful when you do a SuperWipe and need to transfer ROM or just clumsy and wiped without transferring ROM
kyokeun1234 said:
Nope, CWM and TWRP has USB debug on and thanks to that, ADB is possible through them. Really useful when you do a SuperWipe and need to transfer ROM or just clumsy and wiped without transferring ROM
Click to expand...
Click to collapse
so , we can use ADB commands in Recovery just as the same way we do in Android ???
qtwrk said:
so , we can use ADB commands in Recovery just as the same way we do in Android ???
Click to expand...
Click to collapse
If you have a custom recovery yes
Sent from my Galaxy Nexus using Tapatalk 2
Zepius said:
If you have a custom recovery yes
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
So flashing a custom recovery ROM will not affect the other data stored on the internal memory of the phone?
on$ said:
So flashing a custom recovery ROM will not affect the other data stored on the internal memory of the phone?
Click to expand...
Click to collapse
Flashing a custom recovery will only affect the recovery..
Sent from my Galaxy Nexus using xda app-developers app
Zepius said:
If you have a custom recovery yes
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
mrgnex said:
Flashing a custom recovery will only affect the recovery..
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I have essentially the same issue that this thread started with, no root, locked phone.. essentially bone stock verizon moto droid razr maxx HD (XT926).. and it's boot looping at the red eye.. I can get the bootloader menu and I can get into recovery, but I'd like to get data off of it before I do a FDR...
THEREFORE;
I tried the commands "fastboot boot recovery imgname.img" and I get cannot load 'recovery': No such file or directory
I'm not sure if that is an issue with the version of the fastboot utility on my computer or on my handset (getvar shows vanquish & 109B(*) and hardware revision 0x8300
I tried the command "fastboot boot imgname.img" and I get the following
downloading 'boot.img'...
OKAY [ 0.522s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.554s
I can confirm that my device is connected via the fastboot devices command
here is a list of options from my version of fastboot
fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format if supported by partition type)
-u do not first erase partition before formatting
-s <specific device> specify device serial number or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address. default: 0x10000000
-n <page size> specify the nand page size. default:2048
-S <size>[K|M|G] automatically sparse files greater than size. 0 to disable
is this an issue of getting the right version of fastboot on my computer or just formatting the fastboot boot recovery command in a different way that works with my version??
on$ said:
I have essentially the same issue that this thread started with, no root, locked phone.. essentially bone stock verizon moto droid razr maxx HD (XT926).. and it's boot looping at the red eye.. I can get the bootloader menu and I can get into recovery, but I'd like to get data off of it before I do a FDR...
THEREFORE;
I tried the commands "fastboot boot recovery imgname.img" and I get cannot load 'recovery': No such file or directory
I'm not sure if that is an issue with the version of the fastboot utility on my computer or on my handset (getvar shows vanquish & 109B(*) and hardware revision 0x8300
I tried the command "fastboot boot imgname.img" and I get the following
downloading 'boot.img'...
OKAY [ 0.522s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.554s
I can confirm that my device is connected via the fastboot devices command
here is a list of options from my version of fastboot
fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format if supported by partition type)
-u do not first erase partition before formatting
-s <specific device> specify device serial number or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address. default: 0x10000000
-n <page size> specify the nand page size. default:2048
-S <size>[K|M|G] automatically sparse files greater than size. 0 to disable
is this an issue of getting the right version of fastboot on my computer or just formatting the fastboot boot recovery command in a different way that works with my version??
Click to expand...
Click to collapse
You used the wrong command. What you need to do: put the recovery.img you downloaded into the same folder as where your fastboot is located. Then for the sake of it rename the recovery image to: "recovery.img". Then fire up cmd and type: "fastboot flash recovery recovery.img". If you want to boot into it once: "fastboot boot recovery recovery.img". This should do it (without the quotes of course Hoped this helped!
Sent from my Galaxy Nexus using xda app-developers app
mrgnex said:
You used the wrong command. What you need to do: put the recovery.img you downloaded into the same folder as where your fastboot is located. Then for the sake of it rename the recovery image to: "recovery.img". Then fire up cmd and type: "fastboot flash recovery recovery.img". If you want to boot into it once: "fastboot boot recovery recovery.img". This should do it (without the quotes of course Hoped this helped!
Click to expand...
Click to collapse
OK- so here's what I get
>fastboot boot recovery.img recovery
cannot boot a boot.img *and* ramdisk
however if I use the OTHER command
>fastboot flash recovery recovery.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (7890 KB)...
OKAY [ 0.613s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.760s
on my phone the initial fastboot display reads as follows:
AP Fastboot Flash Mode (S)
10.9B(*) (SHA-1e9f557, 2013-09-25 16:26:59)
eMMC Info: Size 32GB
Device is LOCKED. Status Code: 0
Battery: OK
Transfer Mode:
USB Connected
Invalid image size for partition recovery
it gave me the same response for both the Clockwork Recovery and the clockwork Touch Recovery which I copied into the directory and renamed "recovery.img" in both cases... going to try the TWRP and oudhs next..but I'm wondering if I might actually have a variation of the xt926 and not know it?? (it is a droid razr maxx HD)... any other suggestions??
Your device is locked. But when you unlock it you'll lose all your data..
Sent from my Galaxy Nexus using xda app-developers app
Similar issue
mrgnex said:
You used the wrong command. What you need to do: put the recovery.img you downloaded into the same folder as where your fastboot is located. Then for the sake of it rename the recovery image to: "recovery.img". Then fire up cmd and type: "fastboot flash recovery recovery.img". If you want to boot into it once: "fastboot boot recovery recovery.img". This should do it (without the quotes of course Hoped this helped!
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I am having a similar issue getting twrp to install...
./fastboot flash recovery twrp-2.8.6.0-m8.img
ERROR: could not get pipe properties
target reported max download size of 1826414592 bytes
sending 'recovery' (5 KB)...
OKAY [ 0.131s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.133s
xtravaluemeal said:
I am having a similar issue getting twrp to install...
./fastboot flash recovery twrp-2.8.6.0-m8.img
ERROR: could not get pipe properties
target reported max download size of 1826414592 bytes
sending 'recovery' (5 KB)...
OKAY [ 0.131s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.133s
Click to expand...
Click to collapse
Can you still boot into the OS?
If you can remove an app and see what happens, if moments later or after reboot the app is there again your EMMC might be fried.
To check that lock the bootloader. If that is locked upon reboot you're fine, if not the EMMC is fried. If this succeeds though your data is lost.
If all this does not apply to you, then it is probably a driver culprit.
HTC One X won't boot. Somehow it stuck in bootloop while leaved unattended and spend all the battery.
Ok, I've read many threads here about the topic and after many different things tried (Power+VolUp under bright light, Charger batch script...)
I finally opened up the phone and disconnect battery, then charge the battery and tried fastboot...
So I manage to flash clockwork recovery but when try to get into recovery it stuck at HTC quietly brilliant screen
I figure, maybe I should flash original kernel (altough they shouldn't have to be linked) but flashing boot partition didn't work.
Code:
fastboot getvar battery-voltage
battery-voltage: 4052mV
finished. total time: 0.100s
fastboot flash recovery clockwork-touch-5.8.4.0-endeavoru.img
sending 'recovery' (5742 KB)...
OKAY [ 0.745s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.539s]
finished. total time: 1.285s
fastboot flash boot boot.img
and after last command I get error in syslogs
usbfs: USBDEVFS_CONTROL failed cmd fastboot rqt 128 rq 6 len 254 ret -110
(that's linux)
In windows,
Code:
fastboot flash boot kernel.img
sending 'boot' (6008KB)...
OKAY [ 0.811s]
writing 'boot'...
(bootloader) Format partition LNX done
and stays like that
After 10mins waiting I disconnected USB cable and get
Code:
FAILED (status read failed (Too many links ))
finished. total time: 621.177s
Should I just relock bootloader and try some RUU update or try something else?
I'm afraid, since flashing boot won't finish, that some problems may occur during RUU update and then... bye bye HOX :crying:
freedom74 said:
HTC One X won't boot. Somehow it stuck in bootloop while leaved unattended and spend all the battery.
Ok, I've read many threads here about the topic and after many different things tried (Power+VolUp under bright light, Charger batch script...)
I finally opened up the phone and disconnect battery, then charge the battery and tried fastboot...
So I manage to flash clockwork recovery but when try to get into recovery it stuck at HTC quietly brilliant screen
I figure, maybe I should flash original kernel (altough they shouldn't have to be linked) but flashing boot partition didn't work.
Code:
fastboot getvar battery-voltage
battery-voltage: 4052mV
finished. total time: 0.100s
fastboot flash recovery clockwork-touch-5.8.4.0-endeavoru.img
sending 'recovery' (5742 KB)...
OKAY [ 0.745s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.539s]
finished. total time: 1.285s
fastboot flash boot boot.img
and after last command I get error in syslogs
usbfs: USBDEVFS_CONTROL failed cmd fastboot rqt 128 rq 6 len 254 ret -110
(that's linux)
In windows,
Code:
fastboot flash boot kernel.img
sending 'boot' (6008KB)...
OKAY [ 0.811s]
writing 'boot'...
(bootloader) Format partition LNX done
and stays like that
After 10mins waiting I disconnected USB cable and get
Code:
FAILED (status read failed (Too many links ))
finished. total time: 621.177s
Should I just relock bootloader and try some RUU update or try something else?
I'm afraid, since flashing boot won't finish, that some problems may occur during RUU update and then... bye bye HOX :crying:
Click to expand...
Click to collapse
NO RUU for this Hboot and you flash too old recovery. After flashing the recovery run the command fastboot erase cache then flash the boot.img
Thant said:
NO RUU for this Hboot and you flash too old recovery. After flashing the recovery run the command fastboot erase cache then flash the boot.img
Click to expand...
Click to collapse
Should I use Philz-recovery
http://forum.xda-developers.com/showthread.php?t=2240646
and if everything goes well, meaning
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash boot boot.img
I go back to HBOOT and choose RECOVERY in menu, right?
freedom74 said:
Should I use Philz-recovery
http://forum.xda-developers.com/showthread.php?t=2240646
and if everything goes well, meaning
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash boot boot.img
I go back to HBOOT and choose RECOVERY in menu, right?
Click to expand...
Click to collapse
Yes. depend what you want to install I prefer Philz 5.15.9 there mount sd card work perfect.
Tried.
It stuck at
(bootloader) Format partition SOS done
Maybe <fastboot erase cache> before every operation should help?
But what's annoying me most is that when it stuck, there is no way I can get into bootloader but to disassemble the phone again and disconnect the battery and try again
Is there a way to get to bootloader without that?
freedom74 said:
Tried.
It stuck at
(bootloader) Format partition SOS done
Maybe <fastboot erase cache> before every operation should help?
But what's annoying me most is that when it stuck, there is no way I can get into bootloader but to disassemble the phone again and disconnect the battery and try again
Is there a way to get to bootloader without that?
Click to expand...
Click to collapse
change usb cable or usb port on the computer. Maybe faulty cable
@freedom74 what is your batter-voltage now?
Tried on two different computers, three different USB cables and ports... no rules whatsoever.
Anyway, now everything goes fine...
Code:
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.218s]
finished. total time: 0.234s
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (8050 KB)...
OKAY [ 1.139s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.655s]
finished. total time: 1.810s
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.218s]
finished. total time: 0.218s
C:\adb>fastboot flash boot boot.img
sending 'boot' (5086 KB)...
OKAY [ 0.764s]
writing 'boot'...
(bootloader) Format partition LNX done
OKAY [ 0.499s]
finished. total time: 1.264s
Then I disconnect USB cable, go to HBOOT and choose RECOVERY
it stuck on three android screen...
freedom74 said:
Tried on two different computers, three different USB cables and ports... no rules whatsoever.
Anyway, now everything goes fine...
Code:
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.218s]
finished. total time: 0.234s
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (8050 KB)...
OKAY [ 1.139s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.655s]
finished. total time: 1.810s
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.218s]
finished. total time: 0.218s
C:\adb>fastboot flash boot boot.img
sending 'boot' (5086 KB)...
OKAY [ 0.764s]
writing 'boot'...
(bootloader) Format partition LNX done
OKAY [ 0.499s]
finished. total time: 1.264s
Then I disconnect USB cable, go to HBOOT and choose RECOVERY
it stuck on three android screen...
Click to expand...
Click to collapse
wich recovery do you flash. Run again only the command fastboot erase cache and then try go in recovery
Thant said:
wich recovery do you flash. Run again only the command fastboot erase cache and then try go in recovery
Click to expand...
Click to collapse
The one you suggest... Philz 5.15.9
Code:
C:\adb>fastboot getvar battery-voltage
battery-voltage: 3976mV
finished. total time: 0.172s
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.218s]
finished. total time: 0.218s
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.234s]
finished. total time: 0.234s
C:\adb>
Stuck again, but now on "htc quietly brilliant" screen
freedom74 said:
The one you suggest... Philz 5.15.9
Click to expand...
Click to collapse
ok this is good are you run the command fastboot erase cache and then try to go in recovery
Go in bootloader with disconected phone from computer then choice recovery and confirm with power button
@freedom74 you must to put recovery.img and boot.img in your fastboot folder and then flash it
Thant said:
ok this is good are you run the command fastboot erase cache and then try to go in recovery
Go in bootloader with disconected phone from computer then choice recovery and confirm with power button
Click to expand...
Click to collapse
Did that... <fastboot erase cache> and then with disconnected phone tried to RECOVERY
Thant said:
you must to put recovery.img and boot.img in your fastboot folder and then flash it
Click to expand...
Click to collapse
@Thant As you can see from terminal output, that is the case.
freedom74 said:
Did that... <fastboot erase cache> and then with disconnected phone tried to RECOVERY
Click to expand...
Click to collapse
maybe bad download on the recovery try download again or flash TWRP2.8.0
Any suggestion/link for a kernel image?
Does it matters anyway?
@Thant
Done it with TWRP 2.8.0.0... shows "htc quietly brilliant" for a few sec and screen goes black...
freedom74 said:
Any suggestion/link for a kernel image?
Does it matters anyway?
@Thant
Done it with TWRP 2.8.0.0... shows "htc quietly brilliant" for a few sec and screen goes black...
Click to expand...
Click to collapse
try again with fastboot erase cache and then go in recovery the black screen means the phone try to go in recovery
Thant said:
try again with fastboot erase cache and then go in recovery the black screen means the phone try to go in recovery
Click to expand...
Click to collapse
Still nothing...
HTC screen, then goes black, phone vibrates, then again HTC screen... stays for a minute and then again, vibrates, HTC screen and stays
freedom74 said:
Still nothing...
HTC screen, then goes black, phone vibrates, then again HTC screen... stays for a minute and then again, vibrates, HTC screen and stays
Click to expand...
Click to collapse
no I am sure you don't do something right try again redownload CWM or TWRP check the MD5SUM then flash it don.t flash boot.img.
1. Delete all img files from your fastboot folder
2. Paste only your ecovery.img file there and rename it to recovery.img
3. run fastboot flash recovery recovery.img
4. run fastboot erase cache
5. Powerdown the power from bootloader manu and disconnect the phone from computer
6. Press and hold volume down and then press and hold power button until you go in bootloader, choice recovery and press power button
7. Report
Don't flash any boot.img or other things only recovery. If you go in recovery then install the rom and then and last flash the boot.img from rom.archive
Thant said:
Don't flash any boot.img or other things only recovery. If you go in recovery then install the rom and then and last flash the boot.img from rom.archive
Click to expand...
Click to collapse
Done exactly as you said...
When powerdown from bootloader menu, red LED turned on before I disconnect USB cable.
When cable was disconnected red LED stays ON.
I tried Power+VolDn - nothing
Long press Power after 10sec turn red LED off.
Tried again Power+VolDn to get into bootloader but without success.
I disconnect the battery and will try another round...
freedom74 said:
Done exactly as you said...
When powerdown from bootloader menu, red LED turned on before I disconnect USB cable.
When cable was disconnected red LED stays ON.
I tried Power+VolDn - nothing
Long press Power after 10sec turn red LED off.
Tried again Power+VolDn to get into bootloader but without success.
I disconnect the battery and will try another round...
Click to expand...
Click to collapse
You don't do the things as I say. Read again point 6
Press and hold FIRST THE VOLUME DOWN then PRESS and HOLD THE POWER BUTTON until you go in bootloader
And why you don't disconnect the cable from PC and with the volume down go to Power Down option in bootloader and press Power button to confirm this will turn off your phone
Thant said:
You don't do the things as I say. Read again point 6
Press and hold FIRST THE VOLUME DOWN then PRESS and HOLD THE POWER BUTTON until you go in bootloader
Click to expand...
Click to collapse
As I wrote eariler, I've done exactly as you said.
I know the combo for entering bootloader and I know it suppose to be first VolDn and then Power.
My Power+VolUp in previous post does not show the order I pressed the key. Sorry for me not being clear enough.
Thant said:
And why you don't disconnect the cable from PC and with the volume down go to Power Down option in bootloader and press Power button to confirm this will turn off your phone
Click to expand...
Click to collapse
I am disconnecting, but since you wrote
5. Powerdown the power from bootloader manu AND disconnect the phone from computer
Click to expand...
Click to collapse
I was follow that order, first powerdown from menu and then disconnect.
In that case red LED turn on before I was able to disconnect the USB cable.
I will try to first disconnect USB cable so that phone goes back from FASTBOOT USB into just FASTBOOT and then power down from menu.
And then VolDn+Power to enter bootloader and recovery.
My battery drop to 3.700mV so I need to recharge it a while.
p.s.
Thanks for your help and time.
No progress. Always ending at "htc quietly brilliant" screen.
I will try different recoveries with same steps but I don't see why would other work
when twrp 2.8.0.0 with good md5sum does not.
Code:
C:\Android>fastboot.exe getvar battery-voltage
battery-voltage: 3698mV
finished. total time: 0.109s
C:\Android>fastboot.exe flash recovery recovery.img
sending 'recovery' (6536 KB)...
OKAY [ 0.842s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.577s]
finished. total time: 1.420s
C:\Android>fastboot.exe erase cache
erasing 'cache'...
OKAY [ 0.218s]
finished. total time: 0.234s
C:\Android>
Hey everyone! In the past I've been able to boot TWRP through fastboot, after flashing the right dtbo.img found around here. But after updating to 134-7 (and now 134-9) I'm not being able to boot TWRP anymore, even after doing all the process again. In windows cmd it returns me the following:
input:
fastboot boot twrp.img
output:
downloading 'boot.img'...
OKAY [ 0.490s]
booting...
FAILED (remote failure)
finished. total time: 0.617s
All the other fastboot commands seems to work just fine (except for 'fastboot erase data', but 'fastboot erase userdata' works fine too). Does any of you knows how to solve this and boot TWRP?
Luqueuris150 said:
Hey everyone! In the past I've been able to boot TWRP through fastboot, after flashing the right dtbo.img found around here. But after updating to 134-7 (and now 134-9) I'm not being able to boot TWRP anymore, even after doing all the process again. In windows cmd it returns me the following:
input:
fastboot boot twrp.img
output:
downloading 'boot.img'...
OKAY [ 0.490s]
booting...
FAILED (remote failure)
finished. total time: 0.617s
All the other fastboot commands seems to work just fine (except for 'fastboot erase data', but 'fastboot erase userdata' works fine too). Does any of you knows how to solve this and boot TWRP?
Click to expand...
Click to collapse
Use the updated TWRP and instructions found here.
Thank you! I'll try it as soon as I can.
after an unsuccessful firmware of my device, it started to boot constantly in fastboot mode. when I try to restore via miflash and xiaomi tool v2, I get the error "Flash super error". how to solve this problem?
P.S. : sorry if something is written incorrectly, I wrote through a translator
Hi,
did you look at this topic ?
newbie_or_not_newbie said:
Hi,
did you look at this topic ?
Click to expand...
Click to collapse
yes, they advised me to install the xiaomi.eu firmware, but I get the error of flashing the partition (?) "super"
Sending sparse 'super' 1/9 (729624 KB) OKAY [ 16.439s]
Writing 'super' FAILED (remote: 'failed to check sparse crc')
fastboot: error: Command failed
******** Did you mean to fastboot format this ext4 partition?
Erasing 'metadata' FAILED (remote: 'failed to check sparse crc')
fastboot: error: Command failed
try to delete shares and data from adb fastboot
fastboot erase recovery
fastboot erase system –w
fastboot erase boot
fastboot erase system
fastboot erase data
fastboot erase cache
then flash the rom
WaldoVM said:
try to delete shares and data from adb fastboot
fastboot erase recovery
fastboot erase system –w
fastboot erase boot
fastboot erase system
fastboot erase data
fastboot erase cache
then flash the rom
Click to expand...
Click to collapse
thats work!!
thanks bro