Hey guys, if you follow me on Twitter, you know that myself and Michael Faro-Tusino have been working tirelessly over the past month testing out the BlackBerry 10 Dev Alpha OS on the PlayBook. We wanted to make sure we could find (almost) all major bugs before we post a tutorial, so that people wouldn't end up with a bricked device. Shout outs go out to for posting the original tutorial here in the CB Forums, xsacha for a handful of helpful tips, and for partnering up with me on this project. So here it is! Please remember to use extreme caution when installing this OS, and if something goes wrong, I'm not responsible. Install at your own risk! The following outlines how to get the BB10 Dev Alpha OS running on the BlackBerry PlayBook.

This will work for both Windows & Mac – just ensure you have the tools that run for your machine’ 1. Install DingleBerry & DDPB/Some form of sideloading BAR software 2. Download the 10.0.9.44 Dev Alpha OS from here 3. Change your PC and PlayBook date to September 24 2012 – Also turn off your Playbook’s WiFi 4. Enable Dev Mode on your.

Note: This is in no way a final release and is highly unstable. Carrying out this procedure is entirely at your own risk and no parties other than yourself are responsible for any and all consequences that may result This will work for both Windows & Mac - just ensure you have the tools that run for your machine 1. Install & DDPB/Some form of sideloading BAR software 2. Download the 10.0.9.44 Dev Alpha OS from 3. Change your PC and PlayBook date to September 24 2012 - Also turn off your Playbook's WiFi 4.

Enable Dev Mode on your PlayBook 5. Extract the Winchester SDK coreOS BAR file from the 10.0.9.44 folder and place it in the Dingleberry/Firmware/custom folder 6. Connect your PlayBook to your PC 7. Open Dingleberry and enter your Dev Mode password into the field in top left 8. On Dingleberry, select Firmware and Make sure the Buttons say Custom & Core OS 9. Check that your PlayBook is detected by Dingleberry (top right corner) 10. Click update at the bottom 11.

The device should have an update screen - if not make sure it is connected and try again. If it fails to install, simply disconnect, reconnect and try flashing again. If successful, the Playbook will reboot itself - When it comes alive, enable dev mode again and sideload (using DDPB or similar) the Settings app, BBM, Browser, Camera, AppWorld 13. Reboot your device 14. When it comes back on - go to the NEW Settings app and change your date and time to be correct 15. Enable WiFi 16. Go to Settings>BB ID and check that it retrieves info/allows you to sign in - if so, you're good to go - if not, reflash back to 2.1 (using Dektop Manager) and repeat 17.

Enjoy BBM and AppWorld - Browser and Camera will work whether your BB ID works or not Known issues: DO NOT allow your battery to die while running this OS. The device will not know to turn itself off before the battery completely drains. If it does drain, you will have to perform a stacked charge. It will be difficult to revive your PlayBook if this happens.

DO NOT power off your PlayBook with the current date and time. If you need to turn your PlayBook off, roll the date back to September 24 2012. Star wars blu ray changes. AppWorld currently only pulls PlayBook apps. It does not pull BB10 apps. The icons in the top right corner of the home screen are inaccessible. Rotation Lock, Bluetooth, WiFi, and Battery indicator icons do not work, though oddly enough, the Settings icon does work. The backlight appears to timeout much quicker than the length of time defined in the settings.

The list of known issues will be updated periodically. Remember, this OS is NOT a suitable replacement for 2.1. This should only be installed if you're feeling adventurous and brave. Also, please keep in mind that this isn't completely new. The time change workaround and a few other steps are new, but people have been installing Dev OS'es on the PlayBooks since mid-late 2012. I do not take credit for the original method. Last edited by Kyle27; 06-13-13 at 03:50 AM.