Hi.
I'm wondering why we have only ClockWorkMod recovery.
Does anybody heard about TWRP?
Great, fast, stable and very functional recovery.
Look really nice, but there's a chicken or the egg problem here.
As long as a new recovery can't process a CWM backup, no dev's going to compile it in their kernel.
opt1user said:
Hi.
I'm wondering why we have only ClockWorkMod recovery.
Does anybody heard about TWRP?
Great, fast, stable and very functional recovery.
Click to expand...
Click to collapse
SGS is not in the list of supported devices on the page through the link you have provided!
Yes, but I created this thread to enlighten some people and maybe some of them can join to TWRP team or unofficialy port TWRP to SGS.
CWM is very chaotic and have basic features comparing to TWRP.
I contacted with TWRP team and the problem of SGS TWRP is that SGS doesn't have normal recovery partition (it's related in some way with boot partition, don't remeber exactly).
Related
I've seen some roms posting about cwm but I don't have it. I am rooted running khanning's AOSP rom but i wan to flash the cm10 port. When I go into rom manager it recognizes my ideapad as a Transformer so I can't flash clockworkmod recovery there. Is there another place to download it?
If you're using khanning's AOSP rooted rom you already have cwm recovery.
Read 1st post on that thread and he has explained how to get to cwm recovery.
Don't install any other cwm recovery unless you know and are sure about what you're doing. You might brick your device.
install cwm recovery image for IdeaPad K1
Hetalk said:
If you're using khanning's AOSP rooted rom you already have cwm recovery.
Read 1st post on that thread and he has explained how to get to cwm recovery.
Don't install any other cwm recovery unless you know and are sure about what you're doing. You might brick your device.
Click to expand...
Click to collapse
I think you need to nvflash to install cwm recovery image first, then use khanning's AOSP CMW Rom.
the link posted by khanning for K1_CWM_120109_Rooted_nvflash_R2.zip is no longer working. does anyone have a refresh link?
http://forum.xda-developers.com/showthread.php?t=1564002
heyis4horses said:
I've seen some roms posting about cwm but I don't have it. I am rooted running khanning's AOSP rom but i wan to flash the cm10 port. When I go into rom manager it recognizes my ideapad as a Transformer so I can't flash clockworkmod recovery there. Is there another place to download it?
Click to expand...
Click to collapse
From a terminal session:
su
k1recovery
The K1 will will reboot in recovery with CWM running.
http://forum.xda-developers.com/showthread.php?t=1769847 this rom says that i need cwm recovery, but can i not just use my teamwin recovery project?
I'd be very surprised if a ROM needed a specific recovery program installed. If you have TWRP and have taken a backup of your current ROM, then install the new one.
Sent from my Nexus 7
harmvv said:
http://forum.xda-developers.com/showthread.php?t=1769847 this rom says that i need cwm recovery, but can i not just use my teamwin recovery project?
Click to expand...
Click to collapse
twrp is better anyways, you can use it. its not only for cwm recovery.
in teamwin official website i couldn't find twrp recovery support for motorola bravo, however motorola defy was in the list to get twrp recovery.
does TWRP for defy work on bravo? or we need a different for bravo? i love that recovery ...can some body help me install that on my bravo???
hiandro said:
in teamwin official website i couldn't find twrp recovery support for motorola bravo, however motorola defy was in the list to get twrp recovery.
does TWRP for defy work on bravo? or we need a different for bravo? i love that recovery ...can some body help me install that on my bravo???
Click to expand...
Click to collapse
The Defy TWRP works on the Bravo, but its only up to version 2.1 and can't install large Aroma roms (WR, Pikachu, etc). Your better off reading the thread over at Defy Development. Its neat and works, but our custom CWM 5 is the best for us in terms of reliability and stability.
skeevy420 said:
The Defy TWRP works on the Bravo, but its only up to version 2.1 and can't install large Aroma roms (WR, Pikachu, etc). Your better off reading the thread over at Defy Development. Its neat and works, but our custom CWM 5 is the best for us in terms of reliability and stability.
Click to expand...
Click to collapse
can u give me link to download latest CWM please.
hiandro said:
can u give me link to download latest CWM please.
Click to expand...
Click to collapse
Its installed be default with CM10 or PA. The newer the rom, the newer the recovery.
You can copy the zip/system/bootmenu/.... to other roms to get the touch ui in the bootmenu, just don't overwrite your current roms init scripts....and use a PRE 2nd Kernel zip when porting the bootmenu to non custom kernel roms. This isn't something I'd advise doing cause if you don't know what your fully doing you can easily put yourself in a position to flash the sbf. I sbf'd 3 times adding the JB Touch bootmenu to CM7.
skeevy420 said:
Its installed be default with CM10 or PA. The newer the rom, the newer the recovery.
You can copy the zip/system/bootmenu/.... to other roms to get the touch ui in the bootmenu, just don't overwrite your current roms init scripts....and use a PRE 2nd Kernel zip when porting the bootmenu to non custom kernel roms. This isn't something I'd advise doing cause if you don't know what your fully doing you can easily put yourself in a position to flash the sbf. I sbf'd 3 times adding the JB Touch bootmenu to CM7.
Click to expand...
Click to collapse
I installed cm10 then after I went to stable recovery and I wipe data/factory reset and then wipe cache and again wipe dalvik cache,and then I went to install zip from SD card and then choose mokee and flashed the zip.and when I reboot the phone it got stuck at Motorola red logo. again i boot into recovery (it was different, which mokee installed maybe)and when i wipe data and cache it said something like this:can't mount E/cache/recovery/log .and then i went to backup and restore and restored my cm10 backup and it only restored system(no data) why did this happen did I did something wrong?? or is there problem in recovery?? please tell me about this.
hiandro said:
I installed cm10 then after I went to stable recovery and I wipe data/factory reset and then wipe cache and again wipe dalvik cache,and then I went to install zip from SD card and then choose mokee and flashed the zip.and when I reboot the phone it got stuck at Motorola red logo. again i boot into recovery (it was different, which mokee installed maybe)and when i wipe data and cache it said something like this:can't mount E/cache/recovery/log .and then i went to backup and restore and restored my cm10 backup and it only restored system(no data) why did this happen did I did something wrong?? or is there problem in recovery?? please tell me about this.
Click to expand...
Click to collapse
I have a couple of ideas, but I'd be guessing with all of them. Probably just an error from CM10 using a newer recovery than Mokee. Since CM10's /system was restored, so was its bootmenu\recovery -- try doing a full restore now that you're using the same recovery that backed it up .
Crap like this is why we need an unlocked bootloader, or even just a place to hide a custom recovery -- with every rom you flash, your recovery changes and bad things can\have happened. While its nowhere as bad as it once was, problems like yours still occur from time to time. Its the same reason that there's so many posts with people having problems from using BandroidX Recovery -- its a very old CWM based recovery that uses different formats than whats used now (can't even install newer roms with it). Old and new don't usually play nicely with us .
skeevy420 said:
I have a couple of ideas, but I'd be guessing with all of them. Probably just an error from CM10 using a newer recovery than Mokee. Since CM10's /system was restored, so was its bootmenu\recovery -- try doing a full restore now that you're using the same recovery that backed it up .
Crap like this is why we need an unlocked bootloader, or even just a place to hide a custom recovery -- with every rom you flash, your recovery changes and bad things can\have happened. While its nowhere as bad as it once was, problems like yours still occur from time to time. Its the same reason that there's so many posts with people having problems from using BandroidX Recovery -- its a very old CWM based recovery that uses different formats than whats used now (can't even install newer roms with it). Old and new don't usually play nicely with us .
Click to expand...
Click to collapse
Yeah, i tried to restore backup using cm10 recovery and although it said cant restore .android.secure something like that(iam not quite sure) it restored system as well as data.
The thing is i like mokee os .its speed, clean and clear... ecetra but it is not jelly bean.can't we have a cm10 tweaked and modified for bravo.of course I love your PA jelly bean there are lots of tablet tweaks can you also add some other functions like in pimp my rom.
And thanks man for answering my queries
@o-l-a-v have made latest twrp 2.8.6.0 recovery with f2fs for flashing on fota partition. I publish it here bcs there is no development behind it. It works with latest cm12 nightlies
f2fs is untested report pls
All thanks to @o-l-a-v
Install through fastboot:
fastboot flash recovery
https://mega.co.nz/#!3gRwGZiK!sXMsMx1GGwUVkTCCsr8ntZekCE-o-hB4DDp6wlhVQqA
New version again
You don't need any app for flashing, use fastboot, see above
be careful if you write: fastboot flash boot you won't be able to boot
Cool, what ROMs did you test this on ?
OmarEinea said:
Cool, what ROMs did you test this on ?
Click to expand...
Click to collapse
i´m on liquid, but it works on every no stock rom,i used previous version on all your roms
i have made it bcs @championswimmer has not amami support for twrp in his recovery manager only for philz and i prefer twrp
funiewski said:
I have made latest twrp 2.8.0.1 recovery for flashing on fota partition. I publish it here bcs there is no development behind it.
Install through fastboot:
fastboot flash recovery fotaZ1cTWRP2.8.0.1.img
https://dl.dropboxusercontent.com/u/17658154/fotaZ1cTWRP2.8.0.1.img
Click to expand...
Click to collapse
How does this work? I wasn't aware that the amami had a recovery partition... How is it accessed after installation?
Rekoil said:
How does this work? I wasn't aware that the amami had a recovery partition... How is it accessed after installation?
Click to expand...
Click to collapse
That was TWRP developer @Dees_Troy who found the possibility of using fota partition on xperia devices for recovery flashing. Here: http://forum.xda-developers.com/showpost.php?p=38640389&postcount=2
You access it in usual way, Sony logo+led light press volume+. Advantage of it is that recovery persist new kernel or rom flashing, aosp and cm roms and kernels use different recoverys, a backup made with one recovery is maybe not compatible with new recovery you have just flashed. If you are flashoholic like me it is quite a pain. With recovery on fota partition it is no longer a problem. @championswimmer has made a small paid app for flashing recovery on fota, but as i wrote before it does not support twrp for amami only philz and you can flash it easily with fastboot. This works only on aosp and cm roms, if you want to overwrite recovery on fota you can either use flashtool and flash only fota, uncheck all other boxes or you can use recovery manager i mentioned earlier.
funiewski said:
Advantage of it is that recovery persist new kernel or rom flashing, aosp and cm roms and kernels use different recoverys, a backup made with one recovery is maybe not compatible with new recovery you have just flashed.
Click to expand...
Click to collapse
Nice, expirienced same problems.
Thanx @funiewski
Thanks, finally we can install a persistent recovery after flashing another boot.img. So is this a usual recovery.img or has it a special format for xperia devices?
CoolDevelopment said:
Thanks, finally we can install a persistent recovery after flashing another boot.img. So is this a usual recovery.img or has it a special format for xperia devices?
Click to expand...
Click to collapse
As you know i´m far from developer, you can read about twrp for xperia devices here: http://teamw.in/project/twrp2/144
z1c is not officially supported by teamwin, there is philz touch fota recovery images for xperia devices made by @championswimmer: http://forum.xda-developers.com/crossdevice-dev/sony/recovery-philz-touch-fotakernel-images-t2826333, downloads here:http://files.championswimmer.in/?developer=championswimmer&folder=recovery/philz
what i have done: i used teamwin recovery image for sirius, unpacked it with this tool: http://forum.xda-developers.com/showthread.php?t=2073775 (this is simple enough even for me),edited default.prop with notepad++ (model,device, fingerprint, density and so on) , changed res folder to one from twrp for z1c ( i think i use one from @[NUT] ) than repacked it.
If you can get it to work with your f2fs patch it would be great bcs it´s way over my horizon
funiewski said:
As you know i´m far from developer, you can read about twrp for xperia devices here: http://teamw.in/project/twrp2/144
z1c is not officially supported by teamwin, there is philz touch fota recovery images for xperia devices made by @championswimmer: http://forum.xda-developers.com/crossdevice-dev/sony/recovery-philz-touch-fotakernel-images-t2826333, downloads here:http://files.championswimmer.in/?developer=championswimmer&folder=recovery/philz
what i have done: i used teamwin recovery image for sirius, unpacked it with this tool: http://forum.xda-developers.com/showthread.php?t=2073775 (this is simple enough even for me),edited default.prop with notepad++ (model,device, fingerprint, density and so on) , changed res folder to one from twrp for z1c ( i think i use one from @[NUT] ) than repacked it.
If you can get it to work with your f2fs patch it would be great bcs it´s way over my horizon
Click to expand...
Click to collapse
Seems it still (not surprisingly) requires interaction from the boot image to load the recovery from the FOTA partition, making it pretty useless as you can just stick it in the boot partition in that case. Pity, this is about the only irritating thing about Xperia devices, no recovery partition.
How does it work that the phone enters recovery from FOTA partition and not kernels internal recovery?
Rekoil said:
Seems it still (not surprisingly) requires interaction from the boot image to load the recovery from the FOTA partition, making it pretty useless as you can just stick it in the boot partition in that case. Pity, this is about the only irritating thing about Xperia devices, no recovery partition.
Click to expand...
Click to collapse
as i wrote the difference is the recovery on fota partition persist flashing of roms and kernels regardless which recovery they use, thats the point for me
funiewski said:
as i wrote the difference is the recovery on fota partition persist flashing of roms and kernels regardless which recovery they use, thats the point for me
Click to expand...
Click to collapse
Yeah but it is still executing the kernel from the boot partition, so if you **** up boot partition you'll **** up recovery, so it's not much of a recovery. It just loads data from the FOTA partition. A true recovery has its own kernel.
On the TWRP webpage the xperia z2 is "officially" supported. How does this work? recovery?
paulle said:
On the TWRP webpage the xperia z2 is "officially" supported. How does this work? recovery?
Click to expand...
Click to collapse
Exactly in same way as this one.
@funiewski can i post here working boot.img for stock ROM (UB)?
with this boot.img recovery is working very well
russel5 said:
@funiewski can i post here working boot.img for stock ROM (UB)?
with this boot.img recovery is working very well
Click to expand...
Click to collapse
Do you mean fota recovery is working with stock kernel?I thought it was not possible, of course you can post it here
funiewski said:
Do you mean fota recovery is working with stock kernel?I thought it was not possible, of course you can post it here
Click to expand...
Click to collapse
Not stock, but for stock ROM with stock ramdisk (except RIC is disable)
This boot NOT have any recovery, only work with FOTA recovery
View attachment boot.zip
Hi! Thanks for this
But there seems to be several problems with it. I can boot it, but I'm unable to mount external sd-card, and backup fails. I have not had balls to try anything other than that.
Does the recovery actually work as it should on your phone?
(I'm on CM11 nightly from 21.10.. No custom kernel)
o-l-a-v said:
Hi! Thanks for this
But there seems to be several problems with it. I can boot it, but I'm unable to mount external sd-card, and backup fails. I have not had balls to try anything other than that.
Does the recovery actually work as it should on your phone?
(I'm on CM11 nightly from 21.10.. No custom kernel)
Click to expand...
Click to collapse
Are you on "stock " cm kernel? Bcs I'm on pimped kernel with liquid rom which is cm based and have no problems with ext-sd card or with backup, and it´s same for me with carbon which is aosp
funiewski said:
Are you on "stock " cm kernel? Bcs I'm on pimped kernel with liquid rom which is cm based and have no problems with ext-sd card or with backup, and it´s same for me with carbon which is aosp
Click to expand...
Click to collapse
Yes, stock CM kernel. Hm. I'll try again. Eventually try that custom kernel.
I have build a twrp recovery for Wileyfox storm (kipper)
Enjoy it.
All credits go to TeamWin developpers.
flash with fastboot
fastboot flash recovery TWRP-2.8.7.0-kipper-recovery.img
TWRP-2.8.7.0-Kipper-brown-recovery
Edit:
TWRP-2.8.7.0-Kipper-blue-recovery
Nice job ;D
Awesome. It works flawlessly Is there any chance of any custom rom? maybe pure AOSP marshmallow with layers support? is the kipper source released?
I saw twrp 3.0.0.0 can you please compile it?
This works very well, backup, restore. Just one thing i just hope would be great to be there is the OTG drive support.
aciupapa said:
I saw twrp 3.0.0.0 can you please compile it?
Click to expand...
Click to collapse
What extra features does twrp3.0.0.0 have please? The current cm13 marshmallow nightly for wileyfox storm require the cm recovery to install the update zip.
You can able to update to every nightly even you're on TWRP 2.8.7.0 ( I've been using it since and been able to do nandroid backup for that matter, which you can't using CM recovery).
BTW TWRP main highlight is "•Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow"
If your using adopted storage on Android M, using TWRP 2.8.7.0 will not show the adopted SD card.
You can further check the released note from TWRP website for more info.
backfire_12 said:
You can able to update to every nightly even you're on TWRP 2.8.7.0 ( I've been using it since and been able to do nandroid backup for that matter, which you can't using CM recovery).
BTW TWRP main highlight is "•Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow"
If your using adopted storage on Android M, using TWRP 2.8.7.0 will not show the adopted SD card.
You can further check the released note from TWRP website for more info.
Click to expand...
Click to collapse
https://s.basketbuild.com/devs/beroid/Wileyfox%20Storm%20-%20Kipper/TWRP
Anyone tried TWRP_3.0.0-0_kipper recovery at all yet? I have the TWRP_3.0.1-0_crackling_20160402 recovery working fine on my Swift, however since my backups are from the TWRP 2.8.7.0 kipper recovery i have not tested the TWRP_3.0.0-0 version on my Storm!
On the 3.0.0 v2 touchscreen doesnt work for me
aciupapa said:
On the 3.0.0 v2 touchscreen doesnt work for me
Click to expand...
Click to collapse
I had a try at installing both test version 1 and 2 however the recovery loads yet none of the tile's responded after installation/ loading up completed.
hi i need video how do this recovery plz
Ok so I tried to install the given 2.8.7 version and it worked, but it always said 'wrong password' when trying to decrypt my phone. The same password worked when regularly booting the system. So I thought I might try a newer version and downloaded the _test.zip from the link provided in the thread. Unfortunately, now my phone seems to be bricked! It always boots into Recovery, which asks for my password but does not react to any input on the touchscreen. I can not boot the system or the bootloader, adb and fastboot do not find the device and if I hold the power button (or volume-down + power button) for several seconds it just again reboots into the broken recovery. Does anyone have an idea how to get out of this? Any help is greatly appreciated.
Edit: OK, now I feel dumb. The key combination to get into the bootloader is volume-up+power, not volume-down+power. Now I can continue to try different recoveries in the hope that one of them can decrypt the phone correctly and reacts to the touchscreen.
saikoa7a8a said:
hi i need video how do this recovery plz
Click to expand...
Click to collapse
If that's how you write, good luck breaking your phone... This thread has good instructions if you want to risk it, just replace the recovery image it has you download and use with this one.
http://forum.xda-developers.com/wileyfox-storm/general/root-wileyfox-storm-t3250992