Recovery don't need to be update to flash 4.4 romsHi 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
I know but i want dual boot supportRecovery don't need to be update to flash 4.4 roms
Sent from my MI 2(s) using Tapatalk
I've just read, so we need to add tdb feature to Ivan's recoveryI know but i want dual boot support
Enviado desde mi MI 2 mediante Tapatalk
That recovery doesn't support tdb or system-partition flash choose, and it have a lot of bugs wiping /data, so it's unsafe....Does ivan's rom contain CWM or why is this a problem?(that would be stupid)
I think he meant that the ROM doesn't support TDB for some reason.
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....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.
yeah i know but i misunderstood your wordsthen 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.
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
yeah man.Yes so do I, i found this, so if @M1cha add set_metadata_recursive and set_metadata edify commands, will be great
ok, i´will do the same.Tested, Everything works well enjoyng Kitkat and cm 10.2 with TDB
ok, i´will do the same.
the problem is on new updates.
Edit: 4.4 kitkat is very very smooth.. wow
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
See here everything is here
http://xiaomi.eu/community/threads/aosp-4-4-kitkat-rom-aosp-by-ivan.22682/page-2#post-186045
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
yeah man.
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
https://github.com/bihariel/android_bootable_recovery
[GUIDE] Build CWM recovery:
http://forum.xda-developers.com/showthread.php?t=2132672
We use essential cookies to make this site work, and optional cookies to enhance your experience. Cookies are also used for ads personalisation