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?
I'm trying to flash twrp to my lg g4. I've reached the part where I run
Code:
fastboot flash recovery twrp.img
And everything seems to work fine, but when I try to enter recovery mode, I get the default lg recovery (restore factory mode options) and not twrp.
Here's what it prints out when I run the flash command:
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (32060 KB)...
OKAY [ 0.827s]
writing 'recovery'...
OKAY [ 0.341s]
finished. total time: 1.168s
What am I doing wrong?
I tried doing it from a different computer and tried flashing older version of twrp.
No mate, you're not doing something wrong. You must overwrite the stock recovery, because it auto-flashes every time when phone starts. Best way is to use these commands :
adb reboot bootloader
fastboot boot recovery.img (rename recovery recovery.img , without .img (that's the extension, only "recovery", to make it clear)
I'm waiting the results....
Boot the image like. Azza_09 said then when TWRP has booted click on install then change to img instead of zip and select your twrp image. That should work, but Lg front end will be shown when booting to bootloader, simply answer both questions with yes then TWRP will load
I just uninstall magisk, download and install last security patch (february 2018) from https://developers.google.com/android/ota
When I try to re-install twrp on my LG Nexus 5X, everything seems fine :
Code:
fastboot flash recovery twrp-3.2.1-0-bullhead.img
target reported max download size of 536870912 bytes
sending 'recovery' (16477 KB)...
OKAY [ 0.485s]
writing 'recovery'...
OKAY [ 0.210s]
finished. total time: 0.695s
But after several reboot (and several tries reinstalling twrp in fastboot mode) twrp is not installed
The screen just says "No command" with a dead bugdroid
Am I the only one ?
greee said:
I just uninstall magisk, download and install last security patch (february 2018) from https://developers.google.com/android/ota
When I try to re-install twrp on my LG Nexus 5X, everything seems fine :
Code:
fastboot flash recovery twrp-3.2.1-0-bullhead.img
target reported max download size of 536870912 bytes
sending 'recovery' (16477 KB)...
OKAY [ 0.485s]
writing 'recovery'...
OKAY [ 0.210s]
finished. total time: 0.695s
But after several reboot (and several tries reinstalling twrp in fastboot mode) twrp is not installed
The screen just says "No command" with a dead bugdroid
Am I the only one ?
Click to expand...
Click to collapse
Do this. First boot twrp, fastboot boot twrp.img. Once in twrp install magisk. Then either boot back into the bootloader and flash twrp or if you have the twrp.img on your device flash that with twrp that you're already booted into.
Sent from my [device_name] using XDA-Developers Legacy app
Thank you, it works
What I've done precisely is
Code:
adb reboot bootloader
fastboot flash recovery twrp.img
Then reboot in RECOVERY MODE choosing recovery on my phone with sound volume button (do not fastboot reboot to normal mode at this point !)
then in twrp recovery mode I have :
install magisk.zip (version 15.3 for now), and also (don't exit twrp now!)
install again (just after rooting) the img file of twrp to the recovery partition (if not on your memory, you can connect and mount your phone during this twrp session)
then wipe dalvik and cache and "reboot System" to end the twrp recevery session
and it works !
On my first normal boot, I've installed Magisk manager (version 15.3 for now) and tested succesfully the abality to boot in twrp recovery mode again
Here is how I proceed and stuck in bootloop :
[email protected]:~$ fastboot -i 0x0bb4 oem unlock
...
(bootloader) Start unlock flow
OKAY [ 40.920s]
finished. total time: 40.920s
[email protected]:~$ fastboot -i 0x0bb4 flash recovery recovery-yu.img
target reported max download size of 134217728 bytes
sending 'recovery' (8390 KB)...
OKAY [ 0.661s]
writing 'recovery'...
OKAY [ 0.398s]
finished. total time: 1.059s
[email protected]:~$ fastboot reboot
rebooting...
finished. total time: 0.052s
But, neither device is going to off nor anything is happening, just Powered by android logo is showing.
How do I go into recovery mode or switch off the phone.
Kindly help me.
I can only try to suggest, as I don't have your device.
Try variuos combinations :
Just before device is blacking out
1. Press Vol up (Keep pressing) ,wait till it vibrates and the original logo appears. If the recovery you flashed is stock or a working custom recovery, it will open into recovery mode. Then you can do what you want i.e. wipe data ,etc.
2. If the above doesn't work, try with pressing both Vol up and Vol down. Usually Vol down is for fastboot mode.
But, the question is which recovery have you flashed? Is it stock/custom and was it working for you earlier?
Is your rom a custom or stock rom ?
Yogesh1969 said:
I can only try to suggest, as I don't have your device.
Try variuos combinations :
Just before device is blacking out
1. Press Vol up (Keep pressing) ,wait till it vibrates and the original logo appears. If the recovery you flashed is stock or a working custom recovery, it will open into recovery mode. Then you can do what you want i.e. wipe data ,etc.
2. If the above doesn't work, try with pressing both Vol up and Vol down. Usually Vol down is for fastboot mode.
But, the question is which recovery have you flashed? Is it stock/custom and was it working for you earlier?
Is your rom a custom or stock rom ?
Click to expand...
Click to collapse
Thanks for your reply. I tried all efforts by pressing volume up and down both the ways, but phone just switch on and off automatically, nothing else. It is not going into recovery nor into fastboot mode. I don't know why after successful flashing the recovery, which I have down in OP, why phone is automatically in auto switch on and off mode. My device is YU6000 which is having stock rom and recovery.
GirishSharma said:
Thanks for your reply. I tried all efforts by pressing volume up and down both the ways, but phone just switch on and off automatically, nothing else. It is not going into recovery nor into fastboot mode. I don't know why after successful flashing the recovery, which I have down in OP, why phone is automatically in auto switch on and off mode. My device is YU6000 which is having stock rom and recovery.
Click to expand...
Click to collapse
I don't know details of your device bootloader etc. ,but this link has information of flashing Twrp recovery and rooting.
https://forum.xda-developers.com/an...ted-twrp-recovery-yureka-note-yu6000-t3613896
Also, I think you will have to use SP flash tool to flash boot.img and twrp. it should solve your problem.
you will have to install mtk vcom drivers for sp flash tool.
(About battery, last option is to remove cover and battery connector, which is risky.)
@GirishSharma
You can try flashing YU6000 factory image. Since there is no official files released (I'm not sure though) by YU, you can download from Firmwarefiles. You can watch YouTube videos for instructions.
Yes, that can be done by YGDP tool, or SP flash tool. as per the image type.
hello,
in Fastboot-mode I flash TWRP successfull, but when I want to boot recovery, it starts Redmi-Recovery 3.0.
No start of twrp-recovery.
Commands: (same commands I have tried with Windows 10, other TWRP-versions I tried too.)
$ fastboot devices
tkx4gm5575vod69p fastboot
$ fastboot flash recovery twrp-3.7.0_9-0-begonia.img
Sending 'recovery' (31380 KB) OKAY [ 0.876s]
Writing 'recovery' OKAY [ 0.248s]
Finished. Total time: 5.123s
Shutdown phone, Press Power On/off + Volume-Up, Press Volume-Up and it starts Redmi-Recovery 3.0.
Where is my mistake?
got done, used alternative twrp
"twrp-3.7.0_9-0-begonia.img"
I think this is official twrp, but this is for Android 9.0
I tried flash LineageOS20 by using twrp-3.5.0_10-UNIFIED_UNOFFICIAL.img.
I installed Lineage from twrp but now hard brick has happened... nothing boots, no bootloader/fastboot
so I will try windows connects with dead phone and flash Stock-Rom Begonia / Android 9.
edu.mc said:
I tried flash LineageOS20 by using twrp-3.5.0_10-UNIFIED_UNOFFICIAL.img.
I installed Lineage from twrp but now hard brick has happened... nothing boots, no bootloader/fastboot
so I will try windows connects with dead phone and flash Stock-Rom Begonia / Android 9.
Click to expand...
Click to collapse
which lineage did you flash?
There is no official as far as I can see. unofficial too.
lineage-20.0-20220822-UNOFFICIAL-begonia.zip
(I don't know from which address I download it. I searched unsuccessful)
https://sourceforge.net/projects/darkjoker360-developements/files/Xiaomi/Redmi%20Note%208%20Pro/ROM/20.x/lineage-20.0-20220822-UNOFFICIAL-begonia.zip/download?use_mirror=netcologne&use_mirror=netcologne&r=