• Save
Taking Control of Your Mobile Device - Rooting-n-Roms
Upcoming SlideShare
Loading in...5
×
 

Taking Control of Your Mobile Device - Rooting-n-Roms

on

  • 424 views

Presentation on May 9, 2012 for MobileDevNJ.com.

Presentation on May 9, 2012 for MobileDevNJ.com.

Statistics

Views

Total Views
424
Slideshare-icon Views on SlideShare
384
Embed Views
40

Actions

Likes
1
Downloads
0
Comments
0

5 Embeds 40

http://thesmallbizcloudcompany.com 30
http://jamesmikusi.com 5
http://www.linkedin.com 2
http://www.docshut.com 2
https://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • History of CP/M vs DOS.

Taking Control of Your Mobile Device - Rooting-n-Roms Taking Control of Your Mobile Device - Rooting-n-Roms Presentation Transcript

  • MobileDevNJ.com, Wednesday 9 May 2012Taking Control of Your MobileDevice: Rooting’n’Roms
  • Before Desktop Computers Before IDE’s how was code written for microcontrollers? Modern Programming: Write/compile directly on target platform. Embedded Programming: Cross compile and transfer image/binaries. 2
  • Lil’ Bit o’ History Gary Kildall. CP/M. New era introduced by having a consistent environment loaded from disk. 3
  • App Stores and Mobile API’s Mobile platforms facilitate a high level “boot- strapping” to get compiled code onto device. Abstracts developer from hardware. No concerns of booting or loading app. 4
  • Embedded Development No BIOS. No boot options. Developer mode.  Grants access to system filesystem/boot loaders.  Ability to transfer system images/files. Bootstrapping. 5
  • Boot Loaders Developer Mode Access. Low-level device reset/wiping. 6
  • Disclaimer FOLLOW INSTRUCTIONS. Very bad things can happen  Have backup of data. Acknowledge risks. Only flash while connected to charger. 7
  • Boot Loaders OEM Boot ROM.  Basic facilities to reset/wipe device. On Android, file named “recovery.img.” Accessed from Developer Mode. 8
  • Boot Loaders Android – BootROM.  Filename: recovery.img. iOS – SecureROM. Alternate Recovery Mode BootLoader:  ClockWorkMod. 9
  • Imaging Your Device nandroid backups. Ext3 filesystems.  boot.img  /system  /data  /cache  .androd_secure 10
  • Rooting What’s gained? Make read-only filesystems read-write.  /system partition. Removes hardware access restrictions. 11
  • Demo: MIUI 12
  • Why? Customizations. CPU Governors. UI Changes. Direct access to hardware. Feature freedom (ie: WiFi hotspot). 13
  • Demo: CyanogenMod 9 (ICS) 14
  • Data Persistence Titanium Backup. ROM Toolbox. 15
  • Questions 16
  • Resources http://goo.im http://www.clockworkmod.com http://MIUI.us http://www.cyanogenmod.com http://MotorolaTriumphHacks.com http://www.xda-developers.com/ 17