[2014-07-08] ClockworkMod Recovery 6.0.5.0
- Thread starter M1cha
- Start date
bihariel
Members
- 13 May 2011
- 33
- 18
Hi m1cha,
Could you update your recovery to support the new aosp 4.4 kitkt rom?
Thank you in advance
Enviado desde mi MI 2 mediante Tapatalk
Could you update your recovery to support the new aosp 4.4 kitkt rom?
Thank you in advance
Enviado desde mi MI 2 mediante Tapatalk
linuxx
Members
- 6 Jul 2013
- 1,436
- 222
Recovery don't need to be update to flash 4.4 roms
Sent from my MI 2(s) using Tapatalk
bihariel
Members
- 13 May 2011
- 33
- 18
linuxx
Members
- 6 Jul 2013
- 1,436
- 222
I've just read, so we need to add tdb feature to Ivan's recovery
Inviato dal mio Nexus 7 utilizzando Tapatalk
linuxx
Members
- 6 Jul 2013
- 1,436
- 222
That recovery doesn't support tdb or system-partition flash choose, and it have a lot of bugs wiping /data, so it's unsafe....
Inviato dal mio Nexus 7 utilizzando Tapatalk
- 29 May 2011
- 1,747
- 297
then just delete this stupid recovery from ivan's rom.
In my opinion a a ROM should never ever contain any recovery(except stock roms from manufacturer) because the user can choose whatever recovery he wants to use. And if the user wants TWRP i.e. and the rom overwrites it with CWM it is very annoying.
@kekkojoker90: what do you mean? CWM reflashes touchscreen firmware already. but latest cm10.2 roms don't have the firmware bug anymore.
In my opinion a a ROM should never ever contain any recovery(except stock roms from manufacturer) because the user can choose whatever recovery he wants to use. And if the user wants TWRP i.e. and the rom overwrites it with CWM it is very annoying.
@kekkojoker90: what do you mean? CWM reflashes touchscreen firmware already. but latest cm10.2 roms don't have the firmware bug anymore.
linuxx
Members
- 6 Jul 2013
- 1,436
- 222
Yes you're right but with your I think that we can't flash... I'm downloading the ROM, and I'm going to analyze the script to get know why we need that recovery....
bihariel
Members
- 13 May 2011
- 33
- 18
I think the recovery is needed to do this script line well: set_metadata_recursive...
i don´t know if m1cha´s recovery support those commands.
if that is the problem, we can flash the new recovry, then flash the rom and go back to m1cha´s recovery, then we can enable TDB.
Edit: i can confirm that the problem are those new commands: set_metadata and set_metadata_recursive
i don´t know if m1cha´s recovery support those commands.
if that is the problem, we can flash the new recovry, then flash the rom and go back to m1cha´s recovery, then we can enable TDB.
Edit: i can confirm that the problem are those new commands: set_metadata and set_metadata_recursive
Last edited:
bihariel
Members
- 13 May 2011
- 33
- 18
In the cyanogenmod github, there are some changes in the recovery: https://github.com/CyanogenMod/andr...mmit/232abdd577307bbfe38bb84c45dabbbb09f15133
and here: https://github.com/CyanogenMod/andr...mmit/00492db13d161b8075b156cc273b28bcfb51e45f
and here: https://github.com/CyanogenMod/andr...mmit/00492db13d161b8075b156cc273b28bcfb51e45f
linuxx
Members
- 6 Jul 2013
- 1,436
- 222
This mean that we don't need to stay with ivan's recovery, we can disabe TDB and re enable it again later 
I'l try this now
I'l try this now
Code:
flash same rom on both partitions
backup partition 1+2
reboot
copy backup on pc
set $backup=yes
DISABLE tdb
set $TDB=no
if $TDB=no : flash recovery ivan
set $recovery=Ivan
reboot
reboot recovery
flash kitkat rom
boot rom
flash m1cha recovery
set $recovery=M1cha
Enable Tdb
set $TDB=yes
check if system 0 and 1 boot
done
Last edited:
bihariel
Members
- 13 May 2011
- 33
- 18
yeah man.Yes so do I, i found this, so if @M1cha add set_metadata_recursive and set_metadata edify commands, will be great
i already made a fork from m1cha´s recovery and applied the new changes but i don´t have time to compile the recovery. So if someone could compile it it would be great.
here are the sources: https://github.com/bihariel/android_bootable_recovery
[GUIDE] Build CWM recovery:
http://forum.xda-developers.com/showthread.php?t=2132672
Last edited:
bihariel
Members
- 13 May 2011
- 33
- 18
ok, i´will do the same.Tested, Everything works well enjoyng Kitkat and cm 10.2 with TDB
the problem is on new updates.
Edit: 4.4 kitkat is very very smooth.. wow
cbpbxecmecmbeh
Members
- 19 Sep 2013
- 390
- 52
Can you link me to the rom?
How did you keep the tdb? By flashing both recoveries? Thanks!
Sent from my MI 2 using Tapatalk
linuxx
Members
- 6 Jul 2013
- 1,436
- 222
See here everything is hereCan you link me to the rom?
How did you keep the tdb? By flashing both recoveries? Thanks!
Sent from my MI 2 using Tapatalk
http://xiaomi.eu/community/threads/aosp-4-4-kitkat-rom-aosp-by-ivan.22682/page-2#post-186045
cbpbxecmecmbeh
Members
- 19 Sep 2013
- 390
- 52
manohar
Members
- 6 Jun 2013
- 904
- 80
Can you share that recovery ? or give us simple steps to do retain TDB after flashing 4.4 by Ivan ?Tested, Everything works well enjoyng Kitkat and cm 10.2 with TDB
It is too technical to follow each steps as discussed above in the posts...
I hope you understand from noob perspective...
awaiting ur assistance...
Similar threads
