2

After certain troubles with Android 5 (see How to fix file permissions on Android 5 so that a certain app can access certain files?) I decided to go back to 4.4.4 on my Nexus 4 for the time being. Thereto, I restored a backup I made prior to upgrading using the TWRP 2.8.2 restore function. The restore in itself went well, and after reboot the familiar 4.4.4 boot animation came up.

But when I entered my encryption password, I immediately (no discernible delay) got a "Try Again" message. I retried several times, but my password wasn't accepted. It was definitely the correct password I entered, for in TWRP, it works.

I now restored Android 5 from a backup I made immediately before restoring Android 4.4.4, and my password is accepted again, but of course the Android 5 problems are back as well.

So: how do I properly downgrade to 4.4.4 on my encrypted Nexus 4? Thanks.

Improve this question

1 Answer 1

Reset to default
2
  1. In L, take a backup of things you want to save (photos, videos, app data, etc)
  2. Go download a stock rom for your device, such as this one

  3. In TWRP, wipe data, system, cache and dalvik cache

  4. On your computer use fastboot to flash the system.img

  5. Reboot

  6. You should now boot into kitkat, without any encryption.

  7. Restore any backups you might've had. Note that if you simply backed up the /data partition, that might cause problems when restored.

    7b. If you did create a backup with twrp, you can still restore in a safe way
    with titanium backup pro, assuming you root the device.

Improve this answer
4
  • Thank you for your answer but it didn't work. On Step 5, I get a black screen when booting. Maybe it doesn't like the wiped data partition? In theory, if I do the full fastboot -w update image-occam-ktu84p.zip instead of just flashing system.img in Step 4, Step 7b should work as well, right? I might try that when I have more time.
    – Alexander Klauer
    Dec 7, 2014 at 23:01
  • When flashing boot.img, system.img and userdata.img in step 4, it works. I also had to do a factory reset, so the full 16 GB internal memory were recognised instead of just 8 GB.
    – Alexander Klauer
    Dec 9, 2014 at 10:04
  • @AlexanderKlauer the data partition hadn't had the right size?
    – saloalv
    Dec 9, 2014 at 10:05
  • yes, about 8 GB were missing. With an 8 GB model, everything would have been fine.
    – Alexander Klauer
    Dec 9, 2014 at 10:12

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .