-
Notifications
You must be signed in to change notification settings - Fork 1
/
what-is-root.html
344 lines (265 loc) · 28.6 KB
/
what-is-root.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
<!DOCTYPE html>
<html >
<head>
<!-- Site made with Mobirise Website Builder v4.6.1, https://mobirise.com -->
<meta charset="UTF-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="generator" content="Mobirise v4.6.1, mobirise.com">
<meta name="viewport" content="width=device-width, initial-scale=1, minimum-scale=1">
<link rel="shortcut icon" href="assets/images/logo-blue-128x92-1.png" type="image/x-icon">
<meta name="description" content="Learn about Root for Android and its pro's and con's.">
<title>What is Root?</title>
<link rel="stylesheet" href="assets/bootstrap-material-design-font/css/material.css">
<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Montserrat:400,700">
<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Raleway:100,100i,200,200i,300,300i,400,400i,500,500i,600,600i,700,700i,800,800i,900,900i">
<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Lora:400,700,400italic,700italic&subset=latin">
<link rel="stylesheet" href="assets/tether/tether.min.css">
<link rel="stylesheet" href="assets/bootstrap/css/bootstrap.min.css">
<link rel="stylesheet" href="assets/soundcloud-plugin/style.css">
<link rel="stylesheet" href="assets/dropdown/css/style.css">
<link rel="stylesheet" href="assets/animate.css/animate.min.css">
<link rel="stylesheet" href="assets/theme/css/style.css">
<link rel="stylesheet" href="assets/mobirise/css/mbr-additional.css" type="text/css">
</head>
<body>
<!-- Google Analytics -->
<!-- Global site tag (gtag.js) - Google Analytics -->
<script async src="https://www.googletagmanager.com/gtag/js?id=UA-112465163-1"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'UA-112465163-1');
</script>
<!-- /Google Analytics -->
<section id="ext_menu-1s" data-rv-view="135">
<nav class="navbar navbar-dropdown transparent navbar-fixed-top bg-color">
<div class="container">
<div class="mbr-table">
<div class="mbr-table-cell">
<div class="navbar-brand">
<a class="navbar-caption" href="index.html">OwnDroid</a>
</div>
</div>
<div class="mbr-table-cell">
<button class="navbar-toggler pull-xs-right hidden-md-up" type="button" data-toggle="collapse" data-target="#exCollapsingNavbar">
<div class="hamburger-icon"></div>
</button>
<ul class="nav-dropdown collapse pull-xs-right nav navbar-nav navbar-toggleable-sm" id="exCollapsingNavbar"><li class="nav-item"><a class="nav-link link" href="index.html">HELP</a></li><li class="nav-item nav-btn"><a class="nav-link btn btn-white btn-white-outline" href="page3.html">Devices</a></li><li class="nav-item nav-btn"><a class="nav-link btn btn-primary" href="Contact.html">Contact</a></li></ul>
<button hidden="" class="navbar-toggler navbar-close" type="button" data-toggle="collapse" data-target="#exCollapsingNavbar">
<div class="close-icon"></div>
</button>
</div>
</div>
</div>
</nav>
</section>
<section class="engine"><a href="https://mobirise.ws/c">best web site maker</a></section><section class="mbr-section mbr-parallax-background mbr-after-navbar" id="content5-1v" data-rv-view="132" style="background-image: url(assets/images/android-root-645x318.png); padding-top: 80px; padding-bottom: 40px;">
<div class="mbr-overlay" style="opacity: 0.5; background-color: rgb(0, 0, 0);">
</div>
<div class="container">
<h3 class="mbr-section-title display-2">What is Root?</h3>
<div class="lead"><p>Source: Wikipedia.</p></div>
</div>
</section>
<section class="mbr-section article mbr-section__container" id="content1-1w" data-rv-view="137" style="background-color: rgb(255, 255, 255); padding-top: 20px; padding-bottom: 20px;">
<div class="container">
<div class="row">
<div class="col-xs-12 lead"><p><strong>first of all: You don't need root to install a custom ROM, the only thing you'll need is a custom Recovery!</strong></p><p><br></p><p>Rooting is the process of allowing users of smartphones, tablets and other devices running the Android mobile operating system to attain privileged control (known as root access) over various Android subsystems. As Android uses the Linux kernel, rooting an Android device gives similar access to administrative (superuser) permissions as on Linux or any other Unix-like operating system such as FreeBSD or macOS.
</p><p>
</p><p>Rooting is often performed with the goal of overcoming limitations that carriers and hardware manufacturers put on some devices. Thus, rooting gives the ability (or permission) to alter or replace system applications and settings, run specialized applications ("apps") that require administrator-level permissions, or perform other operations that are otherwise inaccessible to a normal Android user. On Android, rooting can also facilitate the complete removal and replacement of the device's operating system, usually with a more recent release of its current operating system.
</p><p>
</p><p>Root access is sometimes compared to jailbreaking devices running the Apple iOS operating system. However, these are different concepts: Jailbreaking is the bypass of several types of Apple prohibitions for the end user, including modifying the operating system (enforced by a "locked bootloader"), installing non-officially approved applications via sideloading, and granting the user elevated administration-level privileges (rooting). Only a minority of Android devices lock their bootloaders[citation needed], and many vendors such as HTC, Sony, Asus and Google explicitly provide the ability to unlock devices, and even replace the operating system entirely. Similarly, the ability to sideload applications is typically permissible on Android devices without root permissions. Thus, it is primarily the third aspect of iOS jailbreaking (giving users administrative privileges) that most directly correlates to Android rooting.</p></div>
</div>
</div>
</section>
<section class="mbr-section article mbr-parallax-background" id="msg-box8-1x" data-rv-view="139" style="background-image: url(assets/images/root-apps-android-670x335.jpg); padding-top: 80px; padding-bottom: 80px;">
<div class="mbr-overlay" style="opacity: 0.5; background-color: rgb(34, 34, 34);">
</div>
<div class="container">
<div class="row">
<div class="col-md-8 col-md-offset-2 text-xs-center">
<h3 class="mbr-section-title display-2">Overview</h3>
</div>
</div>
</div>
</section>
<section class="mbr-section article mbr-section__container" id="content1-1z" data-rv-view="142" style="background-color: rgb(255, 255, 255); padding-top: 20px; padding-bottom: 20px;">
<div class="container">
<div class="row">
<div class="col-xs-12 lead"><p>Rooting lets all user-installed applications run privileged commands typically unavailable to the devices in the stock configuration. Rooting is required for more advanced and potentially dangerous operations including modifying or deleting system files, removing pre-installed applications, and low-level access to the hardware itself (rebooting, controlling status lights, or recalibrating touch inputs.) A typical rooting installation also installs the Superuser application, which supervises applications that are granted root or superuser rights by requesting approval from the user before granting said permissions. A secondary operation, unlocking the device's bootloader verification, is required to remove or replace the installed operating system.
</p><p>
</p><p>In contrast to iOS jailbreaking, rooting is not needed to run applications distributed outside of the Google Play Store, sometimes called sideloading. The Android OS supports this feature natively in two ways: through the "Unknown sources" option in the Settings menu and through the Android Debug Bridge. However, some US carriers, including AT&T, prevented the installation of applications not on the Play Store in firmware, although several devices are not subject to this rule, including the Samsung Infuse 4G; AT&T lifted the restriction on most devices by the middle of 2011.</p><p>
</p><p>As of 2011, the Amazon Kindle Fire defaults to the Amazon Appstore instead of Google Play, though like most other Android devices, Kindle Fire allows sideloading of applications from unknown sources, and the "easy installer" application on the Amazon Appstore makes this easy. Other vendors of Android devices may look to other sources in the future. Access to alternate apps may require rooting but rooting is not always necessary.
</p><p>
</p><p>Rooting an Android phone lets the owner add, edit or delete system files, which in turn lets them perform various tweaks and use apps that require root access.</p></div>
</div>
</div>
</section>
<section class="mbr-section article mbr-parallax-background" id="msg-box8-20" data-rv-view="144" style="background-image: url(assets/images/nexus2cee-xposed-thumb-728x362.png); padding-top: 80px; padding-bottom: 80px;">
<div class="mbr-overlay" style="opacity: 0.5; background-color: rgb(34, 34, 34);">
</div>
<div class="container">
<div class="row">
<div class="col-md-8 col-md-offset-2 text-xs-center">
<h3 class="mbr-section-title display-2">Advantages</h3>
</div>
</div>
</div>
</section>
<section class="mbr-section article mbr-section__container" id="content1-21" data-rv-view="147" style="background-color: rgb(255, 255, 255); padding-top: 20px; padding-bottom: 20px;">
<div class="container">
<div class="row">
<div class="col-xs-12 lead"><p>Advantages of rooting include the possibility for complete control over the look and feel of the device. As a superuser has access to the device's system files, all aspects of the operating system can be customized with the only real limitation being the level of coding expertise. Immediately expectable advantages of rooted devices include the following:</p><p>
</p><p>- Support for themes, allowing everything to be visually changed from the color of the battery icon, to the boot animation that appears while the device is booting, and more.
</p><p> - Full control of the kernel, which, for example, allows overclocking and underclocking the CPU and GPU.
</p><p> - Full application control, including the ability to backup, restore, or batch edit applications, or to remove bloatware that comes pre-installed on many phones.
</p><p> - Custom automated system-level processes through the use of third-party applications.</p><p> - Ability to install a custom software (such as Xposed, Magisk, Busybox, etc.) that allows additional levels of control on a rooted device.</p></div>
</div>
</div>
</section>
<section class="mbr-section mbr-section__container article" id="header3-22" data-rv-view="149" style="background-color: rgb(255, 255, 255); padding-top: 20px; padding-bottom: 20px;">
<div class="container">
<div class="row">
<div class="col-xs-12">
<h3 class="mbr-section-title display-2">Varieties</h3>
</div>
</div>
</div>
</section>
<section class="mbr-section article mbr-section__container" id="content1-23" data-rv-view="151" style="background-color: rgb(255, 255, 255); padding-top: 20px; padding-bottom: 20px;">
<div class="container">
<div class="row">
<div class="col-xs-12 lead"><p>The process of rooting varies widely by device, but usually includes exploiting one or more security bugs in the firmware of (i.e., in the version of the Android OS installed on) the device. Once an exploit is discovered, a custom recovery image that will skip the digital signature check of firmware updates can be flashed. Then a modified firmware update that typically includes the utilities needed to run apps as root can be installed. For example, the su binary (such as an open-source one paired with the Superuser or SuperSU application) can be copied to a location in the current process' PATH (e.g., /system/xbin/) and granted executable permissions with the chmod command. A third-party supervisor application, like Superuser or SuperSU, can then regulate and log elevated permission requests from other applications. Many guides, tutorials, and automatic processes exist for popular Android devices facilitating a fast and easy rooting process.
</p><p>
</p><p>The process of rooting a device may be simple or complex, and it even may depend upon serendipity. For example, shortly after the release of the HTC Dream (HTC G1), it was discovered that anything typed using the keyboard was being interpreted as a command in a privileged (root) shell. Although Google quickly released a patch to fix this, a signed image of the old firmware leaked, which gave users the ability to downgrade and use the original exploit to gain root access.</p></div>
</div>
</div>
</section>
<section class="mbr-section article mbr-parallax-background" id="msg-box8-24" data-rv-view="153" style="background-image: url(assets/images/banner-demo1-960x438.png); padding-top: 40px; padding-bottom: 40px;">
<div class="mbr-overlay" style="opacity: 0.5; background-color: rgb(34, 34, 34);">
</div>
<div class="container">
<div class="row">
<div class="col-md-8 col-md-offset-2 text-xs-center">
<h3 class="mbr-section-title display-2">Manufacturer support</h3>
</div>
</div>
</div>
</section>
<section class="mbr-section article mbr-section__container" id="content1-25" data-rv-view="156" style="background-color: rgb(255, 255, 255); padding-top: 20px; padding-bottom: 20px;">
<div class="container">
<div class="row">
<div class="col-xs-12 lead"><p>Some manufacturers, including LG, HTC, and Motorola, provide official support for unlocking the bootloader which allows for rooting without exploiting a vulnerability. However, the support may be limited only to certain phones - for example, LG released its bootloader unlock tool only for certain models of its phones.</p><p>
</p><p>The Google-branded Android Google Nexus line of devices can be boot-loader unlocked by simply connecting the device to a computer while in boot-loader mode and running the Fastboot protocol with the command fastboot oem unlock. After accepting a warning, the boot-loader is unlocked, so a new system image can be written directly to flash without the need for an exploit.</p><p><br></p><p><strong>Difficulties</strong>
</p><p><br></p><p>In the past, many manufacturers have tried to make non-rootable phones with more elaborate protections (like the Droid X), but they are usually still rootable in some way. There may be no root exploit available for new or recently updated phones, but one is usually available within a few months.[22]</p></div>
</div>
</div>
</section>
<section class="mbr-section mbr-section__container article" id="header3-26" data-rv-view="158" style="background-color: rgb(255, 255, 255); padding-top: 20px; padding-bottom: 20px;">
<div class="container">
<div class="row">
<div class="col-xs-12">
<h3 class="mbr-section-title display-2">Industry reaction</h3>
</div>
</div>
</div>
</section>
<section class="mbr-section article mbr-section__container" id="content1-27" data-rv-view="160" style="background-color: rgb(255, 255, 255); padding-top: 20px; padding-bottom: 20px;">
<div class="container">
<div class="row">
<div class="col-xs-12 lead"><p>Until 2010, tablet and smartphone manufacturers, as well as mobile carriers, were mainly unsupportive of third-party firmware development. Manufacturers had expressed concern about improper functioning of devices running unofficial software and related support costs. Moreover, firmware such as OmniROM and CyanogenMod sometimes offer features for which carriers would otherwise charge a premium, such as tethering. Due to that, technical obstacles such as locked bootloaders and restricted access to root permissions have commonly been introduced in many devices. For example, in late December 2011, Barnes & Noble and Amazon.com, Inc. began pushing automatic, over-the-air firmware updates, 1.4.1 to Nook Tablets and 6.2.1 to Kindle Fires, that removed one method to gain root access to the devices. The Nook Tablet 1.4.1 update also removed users' ability to sideload apps from sources other than the official Barnes & Noble app store (without modding).</p><p><br></p><p>
</p><p>However, as community-developed software began to grow popular in the late 2009 to early 2010, and following a statement by the Copyright Office and Librarian of Congress (US) allowing the use of "jailbroken" mobile devices, manufacturers and carriers have softened their position regarding CyanogenMod and other unofficial firmware distributions. Some manufacturers, including HTC, Samsung, Motorola and Sony Mobile Communications actively provide support and encourage development.</p><p><br></p><p>
</p><p>In 2011, the need to circumvent hardware restrictions to install unofficial firmware lessened as an increasing number of devices shipped with unlocked or unlockable bootloaders, similar to the Nexus series of phones. Device manufacturer HTC has announced that it would support aftermarket software developers by making the bootloaders of all new devices unlockable. However, carriers, such as Verizon Wireless and more recently AT&T, have continuously blocked OEMs, such as HTC and Motorola, from releasing retail devices with unlocked bootloaders, opting instead for "developer edition" devices that are only sold unsubsidized and off-contract. These are similar in practice to Nexus devices, but for a premium and with no contract discounts.
</p><p>
</p><p>In 2014, Samsung released a security service called Knox, which is a tool that prevents all modifying of system and boot files, and any attempts set an eFuse to 0x1, permanently voiding the warranty.</p></div>
</div>
</div>
</section>
<section class="mbr-section article mbr-parallax-background" id="msg-box8-28" data-rv-view="162" style="background-image: url(assets/images/gavel-2000x1117.png); padding-top: 40px; padding-bottom: 40px;">
<div class="mbr-overlay" style="opacity: 0.5; background-color: rgb(34, 34, 34);">
</div>
<div class="container">
<div class="row">
<div class="col-md-8 col-md-offset-2 text-xs-center">
<h3 class="mbr-section-title display-2">Legality</h3>
</div>
</div>
</div>
</section>
<section class="mbr-section article mbr-section__container" id="content1-29" data-rv-view="165" style="background-color: rgb(255, 255, 255); padding-top: 20px; padding-bottom: 20px;">
<div class="container">
<div class="row">
<div class="col-xs-12 lead"><p>International treaties have influenced the development of laws affecting rooting. The 1996 World Intellectual Property Organization (WIPO) Copyright Treaty requires nations party to the treaties to enact laws against DRM circumvention. The American implementation is the Digital Millennium Copyright Act (DMCA), which includes a process for establishing exemptions for non-copyright-infringing purposes such as rooting. The 2001 European Copyright Directive implemented the treaty in Europe, requiring member states of the European Union to implement legal protections for technological protection measures. The Copyright Directive includes exceptions to allow breaking those measures for non-copyright-infringing purposes, such as to run alternative software, but member states vary on the implementation of the directive.</p></div>
</div>
</div>
</section>
<section class="mbr-section article mbr-section__container" id="content2-2a" data-rv-view="167" style="background-color: rgb(255, 255, 255); padding-top: 20px; padding-bottom: 20px;">
<div class="container">
<div class="row">
<div class="col-xs-12 lead"><blockquote><strong>Australia
</strong></blockquote><blockquote>In 2010, Electronic Frontiers Australia said that it is unclear whether rooting is legal in Australia, and that anti-circumvention laws may apply. These laws were strengthened by the Copyright Amendment Act 2006.
</blockquote><blockquote>
</blockquote><blockquote><strong>Canada
</strong></blockquote><blockquote>In November 2012, Canada amended its Copyright Act with new provisions prohibiting tampering with digital locks, with exceptions including software interoperability. Rooting a device to run alternative software is a form of circumventing digital locks for the purpose of software interoperability.
</blockquote><blockquote>
</blockquote><blockquote>There had been several efforts from 2008-2011 to amend the Copyright Act (Bill C-60, Bill C-61, and Bill C-32) to prohibit tampering with digital locks, along with initial proposals for C-11 that were more restrictive, but those bills were set aside. In 2011, Michael Geist, a Canadian copyright scholar, cited iPhone jailbreaking as a non-copyright-related activity that overly-broad Copyright Act amendments could prohibit.</blockquote><blockquote>
</blockquote><blockquote><strong>European Union
</strong></blockquote><blockquote>The Free Software Foundation Europe argues that it is legal to root or flash any device. According to the European Directive 1999/44/CE, replacing the original operating system with another does not void the statutory warranty that covers the hardware of the device for two years unless the seller can prove that the modification caused the defect.</blockquote><blockquote>
</blockquote><blockquote><strong>United Kingdom
</strong></blockquote><blockquote>The law Copyright and Related Rights Regulations 2003 makes circumventing DRM protection measures legal for the purpose of interoperability but not copyright infringement. Rooting may be a form of circumvention covered by that law, but this has not been tested in court. Competition laws may also be relevant. See also "European Union" section above.
</blockquote><blockquote>
</blockquote><blockquote><strong>India
</strong></blockquote><blockquote>India's copyright law permits circumventing DRM for non-copyright-infringing purposes.[42][43] Indian Parliament introduced a bill including this DRM provision in 2010 and passed it in 2012 as Copyright (Amendment) Bill 2012. India is not a signatory to the WIPO Copyright Treaty that requires laws against DRM circumvention, but being listed on the US Special 301 Report "Priority Watch List" applied pressure to develop stricter copyright laws in line with the WIPO treaty.</blockquote><blockquote>
</blockquote><blockquote><strong>New Zealand
</strong></blockquote><blockquote>New Zealand's copyright law allows the circumvention of technological protection measure (TPM) as long as the use is for legal, non-copyright-infringing purposes. This law was added to the Copyright Act 1994 as part of the Copyright (New Technologies) Amendment Act 2008.
</blockquote><blockquote>
</blockquote><blockquote><strong>Singapore
</strong></blockquote><blockquote>Rooting might be legal in Singapore if done to provide interoperability and not circumvent copyright, but that has not been tested in court.</blockquote><blockquote>
</blockquote><blockquote><strong>United States
</strong></blockquote><blockquote>The Unlocking Consumer Choice and Wireless Competition Act guarantees that consumers can unlock or let others unlock their phones. Under the Digital Millennium Copyright Act (DMCA) rooting was illegal in the United States except by exemption. The U.S. Copyright Office granted an exemption to this law "at least through 2015".</blockquote><blockquote>
</blockquote><blockquote>In 2010, in response to a request by the Electronic Frontier Foundation, the U.S. Copyright Office explicitly recognized an exemption to the DMCA to permit rooting. In their ruling, the Library of Congress affirmed on July 26, 2010 that rooting is exempt from DMCA rules with respect to circumventing digital locks. DMCA exemptions must be reviewed and renewed every three years or else they expire.
</blockquote><blockquote>
</blockquote><blockquote>On October 28, 2012, the US Copyright Office updated their exemption policies. The rooting of smartphones continues to be legal "where circumvention is accomplished for the sole purpose of enabling interoperability of [lawfully obtained software] applications with computer programs on the telephone handset." However, the U.S. Copyright office refused to extend this exemption to tablets, arguing that the term "tablets" is broad and ill-defined, and an exemption to this class of devices could have unintended side effects. The Copyright Office also renewed the 2010 exemption for unofficially unlocking phones to use them on unapproved carriers, but restricted this exemption to phones purchased before January 26, 2013.</blockquote><blockquote>
</blockquote><blockquote>Tim Wu, a professor at Columbia Law School, argued in 2007 that jailbreaking is "legal, ethical, and just plain fun."[54] Wu cited an explicit exemption issued by the Library of Congress in 2006 for personal unlocking, which notes that locks "are used by wireless carriers to limit the ability of subscribers to switch to other carriers, a business decision that has nothing whatsoever to do with the interests protected by copyright" and thus do not implicate the DMCA.[55] Wu did not claim that this exemption applies to those who help others unlock a device or "traffic" in software to do so.[54] In 2010 and 2012, the U.S. Copyright Office approved exemptions to the DMCA that allow users to root their devices legally.[56] It is still possible to employ technical countermeasures to prevent rooting or prevent rooted phones from functioning. It is also unclear whether it is legal to traffic in the tools used to make rooting easy.</blockquote></div>
</div>
</div>
</section>
<section class="mbr-section mbr-section-md-padding mbr-footer footer1" id="contacts1-1t" data-rv-view="169" style="background-color: rgb(46, 46, 46); padding-top: 90px; padding-bottom: 90px;">
<div class="container">
<div class="row">
<div class="mbr-footer-content col-xs-12 col-md-3">
<div><img src="assets/images/logo-blue-128x92.png"></div>
</div>
<div class="mbr-footer-content col-xs-12 col-md-3">
<p><font color="#ababab"><span style="font-size: 16px; letter-spacing: -1px;"><strong>Partners</strong></span></font><font color="#ababab"><span style="font-size: 16px; letter-spacing: -1px;"><strong><br></strong></span></font><br>No partners yet!<br><br>Contact us if you have <br>intresd to becom one</p>
</div>
<div class="mbr-footer-content col-xs-12 col-md-3">
<p><strong>Quick Links</strong><br><a href="https://github.com/OwnDroid/OwnDroid.github.io" target="_blank">Github</a></p>
</div>
<div class="mbr-footer-content col-xs-12 col-md-3">
<p><strong>.</strong><br><br></p>
</div>
</div>
</div>
</section>
<footer class="mbr-small-footer mbr-section mbr-section-nopadding" id="footer1-1u" data-rv-view="171" style="background-color: rgb(50, 50, 50); padding-top: 1.75rem; padding-bottom: 1.75rem;">
<div class="container text-xs-center">
<p>Copyright (c) 2018 OwnDroid - OpenSource Website. Want to contribute or use the files? Go <a href="https://github.com/OwnDroid/OwnDroid.github.io" target="_blank">HERE</a></p>
</div>
</footer>
<script src="assets/web/assets/jquery/jquery.min.js"></script>
<script src="assets/tether/tether.min.js"></script>
<script src="assets/bootstrap/js/bootstrap.min.js"></script>
<script src="assets/touch-swipe/jquery.touch-swipe.min.js"></script>
<script src="assets/smooth-scroll/smooth-scroll.js"></script>
<script src="assets/dropdown/js/script.min.js"></script>
<script src="assets/jarallax/jarallax.js"></script>
<script src="assets/viewport-checker/jquery.viewportchecker.js"></script>
<script src="assets/cookies-alert-plugin/cookies-alert-core.js"></script>
<script src="assets/cookies-alert-plugin/cookies-alert-script.js"></script>
<script src="assets/theme/js/script.js"></script>
<input name="animation" type="hidden">
<input name="cookieData" type="hidden" data-cookie-text="We use cookies to give you the best experience. Read our <a href='privacy.html'>cookie policy</a>.">
</body>
</html>