7
The ultimate guide to revert back from CM12 lollipop to CM11 kitkat

  1. uday_nugur Eclair May 19, 2015

    uday_nugur, May 19, 2015 :
    Dear friends as many of OPO users I also upgraded to CM12 but found it quite buggy,unpolished and half hearted attempt from CM12

    So I wanted to reverse back to the stable CM11 but there was no definitive guide in the process I have gone through many forums and at last I got back to CM11

    I found that there is no one stop thread for the entire process and thus I have decided to create one.

    PLEASE MANUALLY BACK UP YOUR DATA TO YOUR PC AND SYNC YOUR PHONEBOOK TO GMAIL (http://androidfact.com/how-to-backup-android-contacts/)

    ALL DATA WILL BE LOST

    Files to be downloaded :

    1. Google usb driver : http://developer.android.com/sdk/win-usb.html

    2. Android SDk : http://developer.android.com/sdk/index.html#download
    Scroll down to SDK TOOLS ONLY and download installer_r24.2-windows.exe

    3. Twrp custom recovery tool : https://dl.twrp.me/bacon/
    download version 2.8.6.1 (latest version)

    4. CM11 firmware : https://drive.google.com/folderview?id=0B98G0KTJwnBFRGhZeUNpMEI4ajg&usp=drive_web
    download cm 11 firmware

    5. CM11 official rom : https://www.androidfilehost.com/?fid=95916177934527555


    PROCEDURE:

    Step 1 : Installing adb and fastboot drivers

    Installing this drivers allows you to access your phone from your PC command prompt terminal.Use the google usb driver that you have downloaded.

    Here is the video guide :

    Step 2 : Unlocking bootloader and installing custom recovery

    Install the Android SDK and Install the following packages (there are a total of 4 packages):
    - Tools > Android SDK Tools, Android SDK Platform-tools
    - Extras > Android Support Library, Google USB Driver

    After installing the SDK go to C:\Program Files\Android\android-sdk\platform-tools
    And in this window press shift + right click mouse button, you should see a option OPEN COMMAND WINDOW HERE select it.

    To confirm that the above steps are indeed working, open a command prompt window and enter the following command in the terminal:

    adb version

    If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case. Close the command prompt window when you are done.

    Now lets unlock bootloader

    Unlocking Bootloader: Opens the door to the internal memory of the device to be written on to.This allows you to flash images onto the main partitions of the phone

    ->Turn the phone off. Then boot it into fastboot mode by holding volume up + power. The phone will display "fastboot" text indicating that it has successfully entered fastboot mode.

    ->Plug the phone into your PC.go to C:\Program Files\Android\android-sdk\platform-tools And in this window press shift + right click mouse button, you should see a option OPEN COMMAND WINDOW HERE select it and type

    fastboot devices

    This command will list the connected devices. If your phones serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.


    If the phone has been recognized by the command above, proceed to unlocking the bootloader with the following command:
    Remember that this step will wipe EVERYTHING off the phone


    fastboot oem unlock

    After the above command has finished excuting, run the following

    fastboot reboot

    The phone will reboot. Wait until the phone has fully booted up into android, then adjust the following settings on the phone:

    • USB Debugging - On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
    • Disable CM Recovery Protection - On your phone go to Settings > Developer options. Then disable the 'Update recovery with system updates' option.
    • Close the command prompt window and proceed onto the next section of the guide.
    Installing a Custom Recovery
    • Turn the phone off. Then boot it into fastboot mode by holding volume up + power.
    • Rename the recovery file that you downloaded above to twrp-recovery.img .U need to name the twrp file as twrp-recovery.img and not as recovery.img and then run this two things in terminal

      fastboot flash recovery twrp-recovery.img

      the above command flashes and then

      fastboot boot twrp-recovery.img

      it boots into recovery from fastboot directly, please note after flashing do not reboot and run this commands back to back.
    Now that u are in custom recovery, reboot your phone.

    Step 3 : Installing firmware and the OS itself

    Here there are two steps :

    1. Installing firmware by flashing it using TWRP tool
    2.Installing the rom in the FASTBOOT mode using ur PC

    Copy the cyanogen firmware file ( 28 MB ) to your phone please remember the location, it is better to copy it directly into root folder.

    Now copy the CM11 Rom ( 520 MB ) to C:\Program Files\Android\android-sdk\platform-tools and extract it there using winzip or 7-zip any such tool.

    Shutdown your phone.Reboot into twrp recovery by pressing volume down + power.

    In twrp recovery

    1)Select WIPE->swipe to factory reset and then home
    2)Select INSTALL->browse to firmware file ,select it ->swipe to confirm flash


    thus the firmware is flashed, for newbies here is video of how to use twrp tool to flash though this video has no relevance w.r.t our scenario it shows how to use twrp.Plase see the entire video in particular METHOD 2



    After flashing the firmware,turn off your phone and boot into fast boot mode

    Now go to C:\Program Files\Android\android-sdk\platform-tools where you have extracted the CM11 rom , hold down shift + right click in the folder with the files and click "open command line here"

    Type in all these commands in order one at a time , back to back(some of them may take some time so be patient), your phone must be in fastboot mode (Power button + Volume up) and must be plugged in to your computer:

    fastboot flash modem NON-HLOS.bin
    fastboot flash sbl1 sbl1.mbn
    fastboot flash dbi sdi.mbn
    fastboot flash oppostanvbk static_nvbk.bin
    fastboot flash aboot emmc_appsboot.mbn
    fastboot flash rpm rpm.mbn
    fastboot flash tz tz.mbn
    fastboot flash LOGO logo.bin
    fastboot flash boot boot.img
    fastboot flash cache cache.img
    fastboot flash recovery recovery.img
    fastboot flash system system.img
    fastboot flash userdata userdata.img (or userdata_64G.img)
    fastboot reboot


    AND VOLA CM11 IS HERE

    THIS WILL NOT BRICK YOUR OPO BCOZ UR FLASHING THE FIRMWARE FIRST AND THEN WITH ROM RATHER THAN GOING WITH THE ROM DIRECTLY IN MANY THREADS WHICH IS THE MAIN REASON THE OPO'S ARE GETTING BRICKED.

    you may have those single click bat files but they did not work for me but I am 100% sure that the above procedure should do the trick.

    References :

    https://forums.oneplus.net/threads/...oader-install-custom-recovery-and-root.64487/

    https://forums.oneplus.net/threads/tutorial-flashing-a-factory-image-from-scratch.142870/

    http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
     
    Last edited: May 20, 2015

    #1
    nikhil_sakre, andli430, wigam and 4 others like this.
  2. fallie Cupcake May 19, 2015


    #2
  3. biltoad Honeycomb May 20, 2015

    biltoad, May 20, 2015 :
    @uday_nugur actually, there's an easier way rather than flashing the firmware file in the recovery.
    fastboot erase modem
    fastboot erase sbl1
    fastboot erase dbi
    fastboot erase oppostanvbk
    fastboot erase aboot
    fastboot erase rpm
    fastboot erase tz
    fastboot erase LOGO
    fastboot erase boot
    fastboot erase cache
    fastboot erase recovery.img
    fastboot erase system

    fastboot erase userdata

    fastboot flash modem NON-HLOS.bin
    fastboot flash sbl1 sbl1.mbn
    fastboot flash dbi sdi.mbn
    fastboot flash oppostanvbk static_nvbk.bin
    fastboot flash aboot emmc_appsboot.mbn
    fastboot flash rpm rpm.mbn
    fastboot flash tz tz.mbn
    fastboot flash LOGO logo.bin
    fastboot flash boot boot.img
    fastboot flash cache cache.img
    fastboot flash recovery recovery.img
    fastboot flash system system.img
    fastboot flash userdata userdata.img (or userdata_64G.img)
    fastboot reboot
    Just make sure you don't reboot on each command.
    It's confirmed working. I've tried downgrading many times(around 5) with this method.
     

    #3
  4. Liamv4696 Donut May 20, 2015

    Liamv4696, May 20, 2015 :
    Everything worked except for that last lot of fastboots.. None seemed to work at all


    D:\Liam\New folder (2)\android-sdk-windows\platform-tools>fastboot flash modem N
    ON-HLOS.bin
    sending 'modem' (56369 KB)...
    FAILED (command write failed (Invalid argument))
    finished. total time: -0.000s

    D:\Liam\New folder (2)\android-sdk-windows\platform-tools>fastboot flash sbl1 sb
    l1.mbn
    sending 'sbl1' (295 KB)...
    FAILED (command write failed (Invalid argument))
    finished. total time: 0.001s

    D:\Liam\New folder (2)\android-sdk-windows\platform-tools>fastboot flash dbi sdi
    .mbn
    sending 'dbi' (11 KB)...
    FAILED (command write failed (Invalid argument))
    finished. total time: -0.000s

    D:\Liam\New folder (2)\android-sdk-windows\platform-tools>


    etc etc @uday_nugur

    Now my phone crashes when I try to change it's USB settings, and when it does show up on my list as a A001 if I click it in windows it tells me it's been removed or deleted..
     
    Last edited: May 20, 2015

    #4
  5. Liamv4696 Donut May 20, 2015

    Liamv4696, May 20, 2015 :
    Got the file onto my phone, when I go into the twrp thing and try to flash the CM11 ROM I get no MD5 file found, even though I can see one in the bloody folder. God Im sick of this ******* phone
     

    #5
  6. Liamv4696 Donut May 20, 2015


    #6
  7. mwayner KitKat May 20, 2015

    mwayner, May 20, 2015 :
    All is not lost. Can you boot into recovery?
     

    #7
  8. Liamv4696 Donut May 20, 2015


    #8
  9. Liamv4696 Donut May 20, 2015

    Liamv4696, May 20, 2015 :
    I downloaded the OPO Toolkit thingo.

    Selected that file above in the OPO toolkit, flashed it, and it gives me fastboot.exe has stopped working after a while -.-
     

    #9
    lie hwa likes this.
  10. mwayner KitKat May 20, 2015


    #10
  11. Liamv4696 Donut May 20, 2015

  12. uday_nugur Eclair May 20, 2015


    #12
  13. ci2ny Gingerbread May 21, 2015

  14. biltoad Honeycomb May 21, 2015

    biltoad, May 21, 2015 :
    Well, I'm not really sure actually but reverting to an older (firmware) by restoring a nand backup doesn't erase the partition first. So there will be remnants inside the partition (just like copt-paste ,overwrite) that somehow is can cause instability. So.. Yeah, using fastboot will ensure that your device's software is pure, just like from factory. Well, correct me if I'm wrong;)
     

    #14
  15. uday_nugur Eclair May 21, 2015


    #15
  16. pabc Cupcake May 24, 2015

    pabc, May 24, 2015 :
    All fine until I try to flash the firmware file from the root folder via twrp. Once I swipe to flash i get
    I get "E:Mount: unable to find partition for path '/cm-11-firmware-20141224.zip'

    Any suggestions as to how to get this step to work?
     

    #16
  17. pabc Cupcake May 24, 2015

    pabc, May 24, 2015 :
    solved. twrp wont flash from /

    I went into adb shell and moved the files to /sdcard. rebooted into recovery and it was fine. Back on CM11
     

    #17
  18. uday_nugur Eclair May 24, 2015

    uday_nugur, May 24, 2015 :
    so apart from this single issue everything else went fine
     

    #18
  19. dafid Cupcake May 24, 2015

    dafid, May 24, 2015 :
    Thank you! I succeeded, with some hiccups during the process, but I succeeded.
    However, my phone now has some personality issues: it thinks it is a 16GB version while it's actually a 64GB. Will this cause any problems?
     

    #19
  20. uday_nugur Eclair May 25, 2015

    uday_nugur, May 25, 2015 :
    fastboot flash userdata userdata.img (or userdata_64G.img)

    here in this command u have to use userdata_64G.img for 64GB OPO , have u done so and I also I request you to please mention the hiccups that u have faced so that we can make this thread as perfect as we can and thank you.
     

    #20