All known issues in TWRP and CWM on locked boot loaders apply, see their respective threads for more information.
Be especially careful with the cache partition when using CWM. Hopefully version 2.0 solved the cache issues but in case of problems with /cache use the FTF in my files to restore the cache partition if yours ever stops mounting due to the CWM issues, read this and this for more info on that.
TWRP Usage warning: It seems TWRP 22.214.171.124 has issues with the internal storage, which seem related to the changes made to support encrypted storage volumes... This means the internal storage sometimes shows up almost empty (just folders) and no files. Try to use CWM when that happens.
Busybox Updater/Installer: If you have XZDualRecovery installed, un-install any Busybox updating app/tool as most if not all of them will install a version of busybox which does not support the lzma compression applets XZDualRecovery depends on. The version installed together with XZDualRecovery is very stable and I have yet to hear anyone complain about it's stability.
exFAT Warning: If you are using an exFAT formatted sdcard there are 2 things to take in to account: CWM currently does not know how to handle them at all. In TWRP it could be that it can't mount it, though it can use it: you need to eject the card and reinsert it, you will be able to mount and use it afterwards.
Frequently Asked Questions:
This is about TWRP 2.6 and the use of INTERNAL STORAGE:
A workaround for this issue is to use TWRP's advanced options, after creating a backup you wish to move to the PC:
try this way. in this thread too.
Sent from my C6602 using xda premium
Already faced a bootloop issue when i try to flash TWRP 126.96.36.199 touch recovery v2 in to my xperia z running on 10.3.1.A.0.244 i think this is the latest my question is will i face the same bootloop issue again if i try to flash this dual recovery ?
any help will be great
|cwm, doomkernel, locked bootloader, recovery, twrp|
|Thread Tools||Search this Thread|