December 28, 2013 By: eagleeyetom
It’s been quite some time since Google launched Android 4.4 KitKat, alongside its Nexus 5. Google has even released two point revisions to the OS. And despite lacking official support, the Sony Xperia Tipo and Google Nexus Onehave already gotten unofficial ports of this OS. The number of older devices running KitKat gets bigger and bigger every day.
Now, developers from the AndroidArmV6 group, most notably XDA Recognized Developers psyke83 and erikcas, XDA Recognized Contributor yajnab, and few others did some remarkable development and brought initial builds to some extremely popular Samsung devices: Galaxy Ace, Galaxy Gio, Galaxy Mini and Galaxy Fit.
Builds for these devices are still quite early, so some bugs like the camera are still present. These devices have very little internal storage, so a lack of space is currently an issue. However, we hope that the developers will find a solution to solve all the issues. Android 4.4 on these devices is a big thing, as they were initially released with Android 2.2 and upgradeable to Android 2.3.
The newest KitKat builds for these devices can be found in the threads below:
January 2, 2013 By: Former Writer
The CM10.1 releases have been flying off the shelves in recent months. Porting has begun to slow down a little bit, but there is support for new devices on nearly a daily basis. There is no pattern to releases, as the specifications on a device don’t seem to matter. Now, there are unofficial CM10.1 builds for the Barnes & Noble Nook HD+ and the Samsung Galaxy Fit GT 5670. Once again, there is a new device and an old device receiving the latest Android at nearly the same time. The Galaxy Fit build was posted by XDA Senior Member erikcas. It’s based on the the Galaxy Ace version by XDA Senior Member Wayland_ACE. It is surprisingly stable, but there are a few things wrong including:
Audio routing issue: in some cases audio routes to handset instead of headset Secure wifi AP youtube control buttons
Since that is the running list of issues on the Galaxy Ace, it’s safe to assume they’re also the issues on the Galaxy Fit. It is still a beta, though, so there may be some smaller quirks and issues not reported.
XDA Senior Member verygreen posted the CM10.1 for the Nook HD+. This is a very interesting release because it’s geared to run specifically off of an SD Card. Thus, users don’t actually install this to their /system partition like a normal ROM. Instead, they install it on their SD card and boot from there. Since you can still boot into the regular OS, this means that installing CM10.1 means you’re essentially dual booting, albeit through cumbersome means.
There are some issues with the Nook HD+ ROM, which may make the build unsuitable for some. The /data partition is only 900MB for right now, there are some MTP issues that users should avoid, Bluetooth audio is reportedly awful, and users can’t boot back into the regular OS without removing the SD card.
February 26, 2012 By: Former Writer
There are a number of reasons why a MD5 checksum in ClockworkMod Recovery might fail. Flashing different versions of the recovery can do it, flashing custom versions of the recovery can do it, or attempting to restore a Nandroid from an old phone to a replacement can do it. Sometimes, there is a need to change the MD5 checksum to make a Nandroid work again.
XDA Junior Member arhant has shared a method that makes it pretty easy to alter the checksum of a Nandroid backup so that it matches the Nandroid backup key stored in ClockworkMod Recovery for the Samsung Galaxy Fit GT5670
The method is, as mentioned, pretty simple and involves using a couple of programs to change the checksum so that it works in recovery. Users simply need a program called MD5 calculator and Notepad++. Some users may be tempted to use regular Notepad in Windows, but Notepad++ doesn’t add any codecs to the text which will prevent any compatibility problems. Once completed, the Nandroid will no longer fail checksum errors and flash as normal.
It should be noted that a bad checksum can be caused by a corrupt backup. Flashing corrupt backups can cause some serious damage to the device, including bricking it. With this in mind, exercise the utmost caution when bypassing MD5 protection. If this looks like the fix you’ve been looking for, you can find the full method and discussion in the original thread.