Mon14

Introduction to Wireframes

Posted by on Nov 14, 2011 in Design, Product Reviews, Programming, Strategy, Web Sites | 0 comments

Wireframes are the road map or blueprints to the start of any good website design. The plans describe the structure, functionality and structure without over-developing the details. The initial layout may not always be perfect, but the elements of the design should accurately relay how the site will lbe layed out but not how the site will look and function in the initial stages.
Read More
Sun14

Private or Corporate Computer Lessons: SEO, Social Media, Personal Branding, Web Design or Computer Basics

Posted by on Aug 14, 2011 in Advertising and Marketing, Blogging, Events, Facebook, Personal Branding, Productivity, Public Speaking, Social Media, Strategy, Tools, Tutorials, Twitter, Web Sites | 0 comments

I’m an experienced community class instructor with over seven years in IT. I own an interactive agency and work as a UI (user interface) designer for a large corporation. My background is in html, css, php, graphic design, photoshop, social media marketing, SEO, online advertising, online marketing strategy, event planning and branding.

Read More
Tue03

Android Hacking the Pros and Cons of Rooting / Jailbreaking / Free Wifi Tethering Hot Spot

Posted by on May 3, 2011 in Gadgets, Programming, Tools, Tutorials | 2 comments

AndroidTechnically Rooting an Android is NOT jail breaking in the since that an iPhone gets Jail broken. Instead, it’s more like making a super user or administrative user for your phone (the same as what you would do for a computer).

This tutorial was originally made to show someone else who asked me to do this for them, the pros and cons. Plus has all the data I found on technical terms and how to run through the process of “rooting” an Android phone.

Enjoy.

The first step in what you asked me for (tethering aka using your phones internet on your computer) is to “root your phone”. Rooting an android is named that because it makes you a root user. A root is basically a superuser account for your OS (the software on your phone that runs the show), it basically gives you an administrative account. Without being a root user you can not modify system tasks and files because normal users don’t have that kind of access. In short, rooting your android will allow you access to edit your phone, the caveat is that its super powerful and you’ll need to not tinker with the code on your own or you could lock up your phone (this is called bricking the phone). The main command (code or series of buttons you don’t want to give your phone when you are in the terminal shell) is SU, that in the most simplest term possible makes you God to the Android. It WILL NOT ask you for confirmation it just does as you tell it to, and assumes that root users know what they are doing but to do this you would need to be in the phones terminal and I can show you the difference, you will not just arrive there on accident (well unless your butt it pushing the perfect series of buttons).
YES, I read all of this information already (and wrote the majority of it.. anything I didn’t write is annotated) and watch EVERY one of the videos I recommended.

A basic list of commands for the terminal and what they mean:
  • su – Command that makes you a root user, allowing file system access.
  • cp - Copy (to copy a file from one place to another)
  • mv – Move (to move a file from one place to another, also good for renaming files because with renames you just move the file to a new file name).
  • mount - Mounts the device (storage card) allowing the phone to see and access the file system on the device. This gives you read/write access, by default you have read only access. Meaning you can’t edit the system. Once edited I could essentially remount the device back to read only so that you can not accidentally edit anything.
  • cd – this changes your main directory in the command shell to any directory I specify. Basically its like moving information from one folder to another.
  • sync - syncs changes on the device.
  • reboot - boot: cause to load (an operating system) and start the initial processes; “boot your computer” (It’s like restart)
  • adb shell – needed to setup adb (see below in terms you may not know)
Other terms you may not know:

  • ADB (android developer bridge) – allows you/me to access your phone via a terminal on your pc.
  • SPL – Specific Programming Location
  • MDN – Mobile Directory Number (your phone number)
  • ROM - A ROM contains the operating system and often additional software which can be “installed” to your mobile device. Most ROMs provided by the chefs (people who create customized ROMs) just contain the operating system and additional applications. Shipping ROMs (ROMs provided by the manufacturer or official providers) also contain a Radio ROM and a bootloader. A ROM can ONLY be flashed to a device it is made for. Custom ROM instructions:
  • Bootloader – A bootloader contains information about your device. It is quite similar to a computer’s BIOS. Official bootloader also have a security option called CID (Carrier-ID) which allows you just to install ROM’s from the provider of your phone. So, if you want to flash another ROM, you first have to turn off this security option by “CID-unlocking” your device. Check the flashing instructions below on how to do this.
  • Radio ROM -  The Radio ROM contains the drivers for the communication devices of your phone. Some ROMs need one or more specific Radio ROM’s to work properly. Usually the chef, who created the ROM recommends a Radio ROM. But don’t mind, if your Radio ROM does not match, you can always flash another without needing to flash the ROM containing the Operating System (OS) again.
    • You can check the version of your Radio ROM when you click Start > Settings > System > Device Information or booting your device (there will appear three lines of red text. The Radio ROM version is the number after the R:.
    • You can download Radio ROM’s at the xda-developers FTP-Server in the Uploads/Kaiser/Radio-Folder. Username and password are both ‘xda’. To install it, download, extract and execute it. Then follow the instructions on your screen. Flashing a Radio does not delete any files on your device’s ROM.
  • CID – All known providers add a Carrier ID to their devices. This CID is added to prevent a device being flashed with a ROM which is not from the provider and/or not designed for your device. You’re sure to brick your Kaiser if you try to flash a ROM designed for a Wizard.
  • SIM Unlock - Lots of providers want to bind their customers. So they add a SIM-Lock to their devices with only allows to use SIM-Cards using their networks. If you want to use a SIM-Card from another provider, you need to SIM-unlock your device.
  • Recovery image/ nandroid – Unlocked SPL this relates generally to your backup.
  • Backup and Restore – I’d hope this was fairly obvious, but just in case it means to save your data in case something goes wrong (as a double somewhere other then the version that is currently in use) and then to restore it is to revert back to that saved version. Broken, walla.. fixed. More info:
  • Hard Reset & Soft Reset - A softreset reboots your device. A hardreset sets all settings back to the ROM’s defaults. All of your data, settings and additionally installed programs will be deleted.
  • Cab-files for WINCE-Devices are different to the files you may have seen (e.g. on your Windows Installation CD). They do not only contain files but also installation information similar like a MSI package. To install them, just copy the *.cab to your Mobile Device and run it from there. Most shipped ROMs delete cab-files after executing, most cooked do not. To be sure, check the registry. If HKLM\Software\apps\Microsoft Application Installer\nDynamicDelete 0 (DWORD decimal), cab-Files will not be deleted after execution.
  • Brick – (from wikipedia) When used in reference to consumer electronics, “brick” describes a device that cannot function in any capacity (such as a device with damagedfirmware). This usage derives from the fact that some electronic devices (and their detachable power supplies) are vaguely brick-shaped, and so those which do not function are useful only as actual bricks. The term can also be used as a verb. For example, “I bricked my MP3 player when I tried to modify its firmware.”[1]In the strictest sense of the term, bricking must imply that software error has rendered the device completely unrecoverable without some hardware replacement. However, it is common to use the term for a problem which can be rectified but only by a complex and difficult procedure, often requiring additional software.

     

    Bricking a device is usually an unwanted consequence of an attempt to update the device. Many devices have an update procedure which must not be interrupted; if interrupted by a power failure, user intervention, or any other reason the existing firmware may be partially overwritten and unusable. The risk of corruption can be minimized by taking all possible precautions against interruption.

    Installing incorrect firmware can also brick a device, e.g., installing firmware for a different revision of the hardware, or installing firmware incompetently patched by certain developers to get around restrictions imposed by official firmware, such as DVD firmware which only plays DVDs sold in a particular region. Most updating software makes all possible checks that firmware is valid for the device, but this cannot be relied upon.

    Devices can also be bricked by malware (malicious software), and sometimes by running software not intentionally harmful but with errors which cause damage.

    Some devices include two copies of firmware, one active and the other stored in fixed ROM or writable non-volatile memory and not normally accessible to processes that could corrupt it, and a way to copy the stored firmware over the active version even if corrupt, so that if the active firmware is damaged it can be replaced by the copy and the device will not be bricked. Other devices have minimal “bootloader” firmware, enabled usually by operating a switch or jumper, which does not enable the device to work normally but can reload the main firmware.

     

  • Unbricking – (wikipeda) Some devices which are “bricked” because the contents of their nonvolatile memory are incorrect can be “unbricked” using separate hardware (a debug board) that accesses this memory directly.[2] This is similar to the procedure for loading firmware into a new device when the memory is still empty. This kind of “bricking” and “unbricking” occasionally happens during firmware testing and development. In other cases software and hardware procedures, often complex, have been developed that have a good chance of unbricking the device. There is no general method; each device is different. There are also user-created modifier programs to use on bricked or partially bricked devices to make them functional. An example is the Wiibrew program BootMii used to fix semi-bricked Nintendo Wii’s.
    • http://code.google.com/p/android-roms/wiki/Unbrick
    • http://www.addictivetips.com/mobile/how-to-un-brick-android-phones-boot-loop-fix/
    • 2.1:
      -shut down
      -Power+x
      -Camera+Vol+
      -Format
  • USB Driver – Needed to edit/access files from your computer
  • Partitioning SD Card – BACKUP BEFORE DOING THIS!
  • Radio -
  • Tethering or Hot Spot – In short it lets you use your phones internet on another device like your computer.
Dangers:
  • Bricking your phone (see description above)
    • The only for sure way to brick your device is to corrupt both the recovery image and the secondary program loader and the actual rom itself (assuming you have a recovery image that can flash modified roms, an SPL that can fastboot, and a rom with root access)
      As long as you have at least one of the three items listed, you are not the proud owner of a bricked device and can recovery your phone.
      It is only when you are unable to enter recovery, fastboot, or your rom, and your device is stuck on the splash screen indefinitely, do you have a bricked device.

      Also note that rooting your phone will block over the air updates that your carrier may provide you. You are pretty much consenting to opt out of OTA’s; you have to update your own phone from now on.

    • How do I brick my device?:
      In most cases, you really have to try, to brick your device. As long as one of the three safety’s built into your phone are functioning, you should have no problem resurrecting your phone. HOWEVER, the most common cause of bricking to date involves the flashing of the Haykuro “death/danger/special” SPL. A hacked developer SPL designed by Haykuro for the HTC DREAM, the SPL partitions the phone’s internal memory (therefore allowing end users to flash larger sized roms). Errors can occur when flashing the SPL or if the user flashes the SPL before flashing the complimenting system radio.
      - http://www.droidforums.net/forum/droid-hacks/632-what-root-means-stop-asking.html
    • If you have the custom recovery installed and make a nandroid backup then you can’t brick it. However if we get into flashing new SPL’s then you have the potential to truly brick it.
    • Home key + power and wait for the ! sign after that press the search key and scroll down to wipe data/factory reset using volume down key and press the camer button for ok.
    • Just go into recovery by turning off device and holding the power button and x till a exclamation point appears and a droid appears(non-rooted users only) then use camera key and volume keys to bring up a menu that will say factory reset and rebboot and some other stuff. Using the dpad go down to factory reset and click ok then go to yes wipe all data and reboot and tada!
  • By flashing a new ROM you could Brick your device, but if you follow all instructions, it is quite implausible that your device bricks.
  • Flashing can invalidate your warranty, but as long as your device can be flashed again, you can find dumped original ROMs to reset everything back if you’d like.
  • “The first step, downgrading your phone from 2.1 to 2.0, can be dangerous. If any part of this process has the ability to brick your phone, it’s this step. I can say that I have done this to two Droids without any phones getting bricked, but as always, your mileage may vary. Know that the software is a little bit finicky, and sometimes fails at re-flashing the stock ROM. If it does, you can just run it again to make it work. I had to run it three times on my friend’s Droid before it flashed, and at one point in the middle his phone was stuck on the bootloader. If this happens to you, don’t panic. We just ran through the process a third time and everything succeeded. If you are not comfortable doing this, then don’t do it—again, I have had great results (despite finicky software), and so have many other people, but your mileage may vary. You have been warned.” — Life Hacker
  • If you do this, you will need to NOT update software when Google sends out updates, you’ll have to have them manually done or you could screw up your device.
Benefits:
  • http://www.androidpolice.com/2010/04/17/detailed-mega-review-of-android-2-1-on-our-htc-hero-discover-all-the-new-features-with-lots-of-screenshots/
  • “The Motorola Droid has been rooted, according to Hack a Day, paving the way for wireless tethering, customized UIs, multitouch support, and other features not specifically endorsed by Verizon on the Android 2.0 platform. The hack was posted by Zinx Verituse on the AllDroid forums, adding the Droid to the ranks of other rooted smartphones.”
  • http://lifehacker.com/#!5563924/the-start-to-finish-guide-to-rooting-your-android-phone
  • http://www.wired.com/gadgetlab/2009/12/droid-unlocked/
  • Multitouch
  • Tethering for Free
  • Custom Themes
  • Custom Apps
  • Performance Increase
  • Speed Increase
  • Can have increased battery life (depend on ROM)
  • Live Wallpapers

How To:


More thorough tutorials:

    • http://www.android.net/forum/android-rooting/58089-droid-incredible-rooting-unrooting-flashing-roms-tutorials.html
    • http://www.taranfx.com/how-to-root-motorola-droid
    • http://lifehacker.com/#!5789397/the-always-up+to+date-guide-to-rooting-any-android-phone
    • http://lifehacker.com/#!5563924/the-start-to-finish-guide-to-rooting-your-android-phone
    • http://www.wired.com/gadgetlab/2009/12/droid-unlocked/
Video Tutorials:

  • (Unrooting) www.youtube.com/watch?v=zv9LneT0O0s
  • Root http://www.youtube.com/watch?v=k4Hfs99vmHU
  • Tethering: http://www.youtube.com/watch?v=aen1E-LM7AE&feature=related
  • Tethering (no real description – meaning no talking – and the music sucks): http://www.youtube.com/watch?v=xpUaUUGDllg&feature=related
  • Rooting: http://www.youtube.com/watch?v=MPKdd4oFb-M
  • Tethering: http://www.youtube.com/watch?v=jcDSWgp0Fpo
  • Tethering (he’s a little loud and long winded, skip halfway through the video to get the info) http://www.youtube.com/watch?v=7uDvcMsjS_Y
  • Tethering – probably one of the better videos http://www.youtube.com/watch?v=nTSD-wZYMT0
  • Root - http://www.youtube.com/watch?v=86GJ2oC3M8Q
  • Overclocking (speed up) http://www.youtube.com/watch?v=SFLpRNyzM_U
  • Overclock - http://www.youtube.com/watch?v=7SM48c4ySdM
  • Overclock (best of the three) - http://www.youtube.com/watch?v=nV-RYSWwtI0


EDIT: As it seems to have come up a few times across the forum and in this thread, I am going to try and explain what the recovery image/nandroid are in terms that make it easy to understand. For WinMo users, you can think of the recovery image (which is nandroid) as an unlocked SPL for your WinMo phone. Much like with the touch pro, diamond, mogul, vogue, etc., you had to flash the unlocked SPL to be able to flash unsigned ROMs, the same thing applies to the Droid. You must install a new recovery image that allows the installation of unsigned programs. The difference is that nandroid is far more than just an SPL analog. It is a truly useful utility that allows you to do many things, create backups, restore them, modify the file system, and install roms and updates. It is NOT necessary to install the hacked recovery image if you don’t plan on messing with custom ROMs and the phone itself. But the truth is, if you don’t plan one doing those things, you should ask yourself why you are rooting your phone and taking any risk whatsoever. That being said, if you plan on rooting your phone, installing the recovery image and creating a backup is just good common sense. It allows you to have a way to get your phone back shoud you do something that screws it up. The other nice thing about said backups, is they allow you to completely return to where you were when you backed the phone up. EVERYTHING is restored! No more reinstalling and reconfiguring all of your programs every time you want to try a new ROM. Simply create a backup before you install the new ROM, and install the new one. If you don’t like how the new one works, simply restore the backup and your right back to where you were at!

HOW TO Create a backup: To create a nandroid backup, reboot your phone into recovery by holding ‘x’ while powering on the phone, or typing reboot recovery into a terminal with root access. Once you have booted into the recovery mode, select backup/restore, push the camera button, select simple nandroid backup, and push the camera button. After a minute or two, the process will complete and you can use the power button to go back and select reboot phone. The backup is stored in the nandroid folder on your SD card.


AS OF 1/10/2010, THE MOST CURRENT VERSION OF THE NANDROID RECOVERY IMAGE IS 0.99.2b. MAKE SURE THAT YOU FLASH THE LATEST VERSION AND KEEP IT UPDATED, ESPECIALLY IN THESE EARLY STAGES BEFORE A TRUE 1.0 RELEASE.


I take no credit for this tutorial, I just copied it from here. I made a few changes, but the bulk of the content was writtend by bootsdscoob at droidforums.net

I AM NOT RESPONSIBLE FOR ANYTHING. DAMAGE TO YOUR PHONE, WORLD WAR, STARVING KIDS IN AFRICA, OR BRICKED PHONES…DO NOT TRY THIS IF YOU DONT KNOW WHAT YOUR DOING!
that being said, this is all pretty simple

1) MANUALLY UPDATE TO 2.0.1(this can be used to unroot also)

1 – Download file. 2.0.1 android OS_update.zip
2 – Rename the file to “update.zip”.DO NOT USE .zip if your using windows vista/7
3 – Plug your Droid into your computer via USB. On the Droid go to the Notifications bar and select “USB Connected” then press “Mount”.
4 – Once the device is mounted, the SD card will show as a removable device on your computer
5 – Put the “update.zip” file you just renamed into the Root (top) directory of your SD Card.
6 – Unmount the device from your computer, and turn the Droid off.
7 – Hold down the “X” key on the physical keyboard and while doing so press the power button. Hold both of them down until you see a Triangle with an !.
8 – Hold the Vol+ button then press the camera button and you will see a menu.
9 – Using the D-pad on the physical keyboard, select the option to update with the update.zip file.
10 – This should take a little bit. Once it’s done select the option to reboot the phone.
11 – The phone will take much longer than normal to boot, don’t worry as it is normal.

2) ROOT (all in one file, doesnt require superuser permissions)

1 – Download file. root for droid.zip
2 – Rename the file to “update.zip” Make sure that you don’t include the “.zip” extension if your computer is not displaying file extensions (Vista/Windows 7 doesn’t show extensions by default)
3 – Plug your Droid into your computer via USB. On the Droid go to the Notifications bar and select “USB Connected” then press “Mount”.
4 – Once the device is mounted, the SD card will show as a removable device on your computer
5 – Put the “update.zip” file you just renamed into the Root (top) directory of your SD Card.
6 – Unmount the device from your computer, and turn the Droid off.
7 – Hold down the “X” key on the physical keyboard and while doing so press the power button. Hold both of them down until you see a Triangle with an !.
8 – Hold the Vol+ button then press the camera button and you will see a menu.
9 – Using the D-pad on the physical keyboard, select the option to update with the update.zip file.
10 – This should take a little bit. Once it’s done select the option to reboot the phone.
11 – The phone will boot. now you have root

3)blocking OTA updates

open terminal emulator (available in the android market)
enter exactly like this NOTE: Linux file and directory names are CASE SENSITIVE, mind your capitals and punctuation!!!

su (after typing this you will most likely get a popup asking you to allow root privelages to the program, allow them)
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
cd /system/etc/security
mv otacerts.zip otacerts.zip.bak (mv is the linux command for renaming a file, by just using mv, the file remains for you to restore later if you so choose)
mount -o ro,remount -t yaffs2 /dev/block/mtdblock4 /system
sync
reboot

If you visit the link in the top, the tutorial continues on replacing your recovery image, which installs nandroid and allows you to make backups and flash custom ROMs. I would skip that and follow this tutorial which continues from here:http://alldroid.org/viewtopic.php?f=210&t=792

This gentleman has written a nice program that installs busybox (a linux command shell that includes a lot of commands that are needed for various things!), flash_image (the program used to flash images, imagine that!), and the patched recovery image for nandroid.

Updated for 14.0 recovery and added better instructions.
This version will remain here on alldroid and get small updates constantly(I will do my best to keep up with new recovery.img’s especially) but I have put a full version on the marketplace that has more features like numerous theme change buttons multiple boot animation and font change buttons so you can change quick but still have that one you really like lol…. I will be updating the full version constantly as well but it will be more features added instead of just keeping up with the recovery, if there is something you would like to see added to it please don’t hesitate to ask.

I have made an app for rooted droids to assist in installing busybox,flash_image and such.To use the app though you must have root first found here and have the the folder named Tools on the root of your sdcard (the folder and all files needed are included in the .zip file attached.) You must have the box in settings checked to allow install of apps from unknown sources (settings/applications)

Instructions for use:
Download attached Droid root helper.zip and unzip it, now copy the folder named Tools to the root of your sdcard.
Next install the DroidRootHelper.apk to your phone.
Now run DroidRootHelper…The first time you run it it will ask for su access then it will probably freeze(seems to be a problem with most apps requiring su access) give it a second or two and if a force close dialogue pops up click force close.Now re-enter the app and as long as you checked to always allow root access it wont have any more problems.

Now for the fun stuff first, mount the system
Next install busybox, then you can move on to install flash_image.
Now that you have flash_image working you can flash SirPsycoS’s 0.14.0 recovery.img but dont forget to click Rename recovery-from-boot.p before rebooting to avoid the default recovery being re-flashed upon reboot.(as lot of people have already found out if you wanna flash a different recovery and I haven’t updated this just put the recovery you want in the Tools folder on your sd card but rename it to the same name as the one in there. Example:The current recovery in the folder is recovery-0.14.0.img if you have recovery-1.13.5.img rename it to recovery-0.14.0.img and stick it in the Tools folder then use the flash recovery button.This method will work for alot of the new options like flash skull theme if theres a themed Launcher.apk and framework-res.apk made for the droid you want it installed put them in the skulltheme folder located inside the tools folder. )

Once done with that I would suggest to click reboot recovery and make a Nandroid backup by using the volume up/down buttons to highlight selection camera button chooses highlighted selection and the power button backs out of submenu’s.

A breakdown of the buttons and what they do:
Mount = mounts the system read/write with the command: mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Unmount = unmounts the system with the command: mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
Sync = syncs system with the command: sync
Rename recovery-from-boot.p = renames the recovery from boot patch to recovery-from-boot.old so your recovery is not overwritten by the default one on reboot.
Install and chmod busybox = Installs busybox to /system/bin and chmods it by running the busybox.sh in the Tools folder.
Install and chmod flash_image = Installs flash_image to /system/bin and chmods it by running the flashimage.sh in the tools folder
Flash 14.0 recovery = Installs the recovery-0.14.0.img with the command: flash_image recovery /sdcard/Tools/recovery-0.12.0.img
Install Skull Theme = Installs the Launcher.apk and framework-res.apk from the skulltheme folder inside the Tools folder by running theme.sh
Install Default Theme = Installs the Launcher.apk and framework-res.apk from the defaulttheme folder inside the Tools folder by running theme1.sh
Flash bootanimation.zip = Installs the bootanimation.zip from the bootanimation folder inside the Tools folder to /data/local
Reboot = reboots the phone with the command: reboot
Reboot Recovery = reboots the phone into recovery with the command: reboot recovery
Most of these options require the phone to be mounted so the files can be written to the system folders.Example:Install skull theme if you click this and the phone is not mounted the only command from the .sh its using that will work is reboot as the commands to copy the themed .apks reqire the system to be mounted.

Update version 5 adds user friendly tips.
If you have any questions and I am not responding quick enough here please feel free to email me at[email protected]
As with all apps and themes of this nature I accept no responsibility for any bricked or damaged devices you use this at your own risk!Attachment:
Droid root helper.zip [19.48 MiB]
Downloaded 1572 times

Attachments:

3.png [ 87.37 KiB | Viewed 1437 times ]


2.png [ 71.92 KiB | Viewed 1437 times ]

Hopefully this provides the information necessary to get the task done. If you have any questions, post em up and we can try to get them answered!

EDIT: After that is all done, go to the market and download the free app AdFree, which will modify your hosts file (the file that tells linux what internet sites are ok to connect to) and block most ad servers across the net, making it so you don’t have to look at ads in your free ad based apps!

EDIT: As it seems that crotalusfreak has not updated his program in a while, I am going to explain how to updgrade your recovery image manually. This little tutorial assumes you have followed all the steps above and now have the 0.14 recovery image installed. Download the latest version of recovery image at http://sholes.info. As of 1/10/10, that version is 0.99.2b. Place that file (recovery-0.99.2b.img) in the root of your SD card. Now, in your favorite terminal program (adb shell on the PC or Terminal Emulator on your phone for example), type the following commands

su This command allows you root privileges
flash_image recovery /sdcard/recovery-0.99.2b.img This command flashes the file to the recovery partition
reboot recovery This command reboots the phone into recovery mode, much easier than holding ‘x’ while powering on

At this point the phone will have rebooted into recovery mode, and you can verify proper installation by looking at the version number at the top of the screen.

 

Read More