I replaced Rom with Resurrection Remix

Home Forums Xiaomi Mi4c libra General Discussion I replaced Rom with Resurrection Remix

Tagged: , ,

This topic contains 6 replies, has 6 voices, and was last updated by  aan2007 1 year ago.

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #12182

    PlutonFI
    Participant

    So, I switched from TS CM13.1 to the Resurrection Remix 5.8(Android 7.1.1) because I want to experience newer Android system on my Mi4C.
    I will flash back to your Cyanogenmod/Lineage OS if something goes wrong.
    I used your TS TWRP recovery and it flashed Resurrection Remix without problems.

    #12224

    darknebula
    Participant

    I don’t manage to flash RR, i wipe dalvik, data, sistem and cache and flash the rom with gapps but the phone is stuck on boot logo.

    • This reply was modified 1 year, 2 months ago by  darknebula.
    #12226

    SvenK
    Participant

    The actual Resurrection Rom needs new MIUI blobs. But the new blobs/firmware will lock your bootloader!

    #12231

    PlutonFI
    Participant

    Now with the latest RR I flashed new blobs by accident.
    I gave my Mi4c for someone if he/she can flash the official ROM for it.
    Now I don’t use my Mi4c anymore so I only use my phone at email, internet and calling. My phone is now Oukitel K10000.

    #12241

    Luka3
    Participant

    I also had RR, and today i come back to CM13.1.

    • This reply was modified 1 year, 2 months ago by  Luka3.
    • This reply was modified 1 year, 2 months ago by  Luka3.
    #12246

    katana101
    Participant

    Im also back to cm 13.1 from RR i dont want a locked Bootloader

    • This reply was modified 1 year, 2 months ago by  katana101.
    #12440

    aan2007
    Participant

    there is new Lineage 14.1 released in May by Cozzmy13 for Lollipop bootloader, feel free to flash it, links on XDA or Mi4c subreddit, I use it as daily driver without any bugs, stable, good battery life

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.