Alternate CWM install? - Kindle Fire General

anyone had success with using KFU to install CWM? Seems like you would just replace the TWRP image with the CWM image...or I could be wrong and brick my fire
Sent from my VS910 4G using XDA App

you can replace twrp with cwm but not with kfu
you have to install it manually as described in the op of cwm
http://forum.xda-developers.com/showthread.php?t=1454241
edit: just realized what you are tying to do ! don't think that this will work cause the install command is different
twrp starts a install routine with the "boot" command - cwm will be directly flashed with the "flash" command

Well I tried it before I read your response and now I'm stuck at fff boot logo...kfu is at "waiting for device"...I'm sure there's a thread for that somewhere
Sent from my VS910 4G using XDA App

http://forum.xda-developers.com/showthread.php?t=1490719

future refference, use this to install cwm directly, no fastboot required.
http://forum.xda-developers.com/showthread.php?t=1500935
Sent from my HTC Glacier using xda premium

Related

Clockwork recovery...

My phone was going through bootloops and I went to recovery and clockwork definitely WASN'T there. So I improvised and used the 1 click stock method to restore my phone. Any idea why clockwork wasn't there and how to change it to where it is in case it happens again?
Sent from my Nexus S 4G using XDA App
Did you flash it yet???
I recently answered a question similar to this, so see if it works:
1. Reboot into your bootloader
2. Download a clockwork img and save it to a directory on ur computer
3. CD into that directory on the terminal and do the following command:
fastboot flash recovery _____.img
(Blank line is name of img)
And reboot into recovery from bootloader
See if that works
Sent from my Nexus S using XDA App
Btw wrong section ;D
Sent from my Nexus S using XDA App
You flashed recovery, then installed su. You needed to rename install-recovery.sh to install-recovery.bak in /system/etc/

Stupidity... Typed something wrong some guidance

Rooted fine my tf101. Recovery installed fine. So I wanted to save my buttons and install CWM Touch. Tried to install via terminal and typed the wrong mmcblock 4 instead of 3. Now its stuck in the splash screen with no recovery. I am able to access the tablet by cold boot only. Anyway I can fix this?
Sent from my S2 using xda premium
NVFlash fixes all
Just download.bat but I get "usb write failed"
Try RecoveryInstaller to see of out can install cwm again
Did a factory reset and its working. Just have to reroot. Thanks
Sent from my Epic 4g Touch using xda premium

[Q]CWR or TWRP?

I just want to know which recovery should I install...I'm new to the pad game and I just wanted some input...I just rooted my N7 and ready to install a recovery...I'm used to CWR on my sgIII...but I see that TWRP is the new recovery that some guys are installing...also is there problem with boring into recovery from the device? Thanks in advanced...
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I prefer cwm touch which you can get from the site. Or you can flash the button version from rommanager
Twrp does work tho, but I've read issues with restoring backups.
Booting into recovery on the device in a way is messed up. The button combo method to enter using the bootloader hangs when not connected to a PC, so there are two options on getting into recovery.
A. Connect to a PC and use bootloader
B. With a working OS, reboot to recovery using an app such as rommanager or goomanager
If you ever flash a rom that won't boot, u need to connect to a PC and boot into recovery via bootloader (button combo).
Sent from my Nexus 7 using xda premium
I use TWRP and had successfully restored now a couple of times. Once was a complete device replacement where I restored the TWRP restore files from my workstation.
How I do my backups to ensure I can restore from a total loss.
http://forum.xda-developers.com/showthread.php?p=29550640
Sent from my Nexus 7
smirkis said:
Booting into recovery on the device in a way is messed up. The button combo method to enter using the bootloader hangs when not connected to a PC, so there are two options on getting into recovery.
A. Connect to a PC and use bootloader
B. With a working OS, reboot to recovery using an app such as rommanager or goomanager
If you ever flash a rom that won't boot, u need to connect to a PC and boot into recovery via bootloader (button combo).
Click to expand...
Click to collapse
Ah, I was curious if this bug still existed or not.
I'd go with CWM, quite stable, easy to use, and you can flash the touch recovery, speeds it up.
Sent from my Nexus 7 using xda app-developers app
Thanks, I read somewhere that if you go into system/ and rename recovery-from-boot.p to recovery-from-boot.bak, fixes the bootloop...can anyone confirm this... thank in advance
Sent from my Nexus 7 using xda app-developers app
Try it. Bootloader issue still exists regardless.
Sent from my Nexus 7 using xda premium
I'm a TWRP guy all the way. I have never had an issue restoring a backup, and the ability to compress my nandroid is invaluable.
Sent from my Nexus 7 using Tapatalk 2
TWRP has definitely converted me.
Sent from my SAMSUNG-SGH-I747 using xda premium
05GT said:
TWRP has definitely converted me.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
+1

Clockwork recovery touch mod help

Hey i haven't been able to figure out how to install this .img file can anyone help me
You can find out if you search for 'flashing recovery through fastboot'. In any case, the best recovery for this device is 4ext touch recovery. Download 4ext Recovery Updater from www.4ext.net and use that to flash recovery (you need to be rooted and bootloader unlocked).
Sent from my Desire HD using xda premium
All good got it to work
Sent from my Desire HD using xda app-developers app

Need help with recovery.

I've installed CWM through ROM Manager in order to install 4.4, but I'm still booting into TWRP every time. Any idea what my issue is?
Sent from my Nexus 4 using xda app-developers app
Use Flashify or manually boot into fastboot, erase recovery, and reflash CWM.
Sent from my AOSP on Mako using XDA Premium 4 mobile app
Theonew said:
Use Flashify or manually boot into fastboot, erase recovery, and reflash CWM.
Sent from my AOSP on Mako using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Flashify works on and off for me. The surefire way (as Theonew mentioned) is to manually overwrite in fastboot with
Code:
fastboot flash recovery recoveryfile.img

Categories

Resources