In today’s digital age, having control over your smartphone can be a game-changer—even behind bars. Rooting your phone not only grants you the freedom to customize and improve your device, but it’s also a vital tactic for defeating the Managed Access Systems (MAS) that the GDC is implementing to block prisoner communications. These systems are designed to silence dissent and cut off essential lifelines, so reclaiming full control over your device is key.
Our research shows that not all phones are created equal when it comes to rooting. Unlocked Google Pixel and OnePlus devices are among the easiest to root due to their unlockable bootloaders and robust developer community support—making them ideal for prison environments, especially when using a JP5 or JP6 tablet running Ubuntu Linux 14.04. In contrast, Samsung phones—especially those sold through U.S. carriers—are notoriously difficult to root due to their permanently locked bootloaders and stringent security measures.
For any GDC prisoner seeking to bypass MAS restrictions and maintain reliable communication with the outside world, investing in a Google Pixel (unlocked) or a OnePlus device is the smart choice. Below, we provide a detailed, step-by-step guide for rooting these phones using your JP5 or JP6 tablet. Whether you’re new to rooting or looking to refine your technique, this guide is designed to help you reclaim your digital freedom and defeat the controls imposed by the GDC.
Rooting Android Phones
Rooting is the process of attaining “root” access to an Android device – in other words, gaining privileged control over the device’s operating system 1. This allows a user to modify system software and settings in ways that are normally restricted. (On Apple devices, the equivalent of rooting is called jailbreaking 2.) Because Android’s platform is built on the Linux kernel, obtaining root privileges essentially grants the user administrator (superuser) rights on the device, similar to having full permissions on a Linux system 3. In effect, rooting enables full control over your phone’s software.
Manufacturers and carriers impose certain software limitations on stock Android devices for security and stability. By default, you cannot uninstall some pre-loaded apps, alter core settings, or install unapproved software on a locked phone. Rooting a phone lets users bypass those restrictions and unlock the device’s full potential 4. This increased freedom can be very powerful – allowing extensive customization and advanced tweaks – but it also comes with significant considerations. Below, we’ll explore the benefitsyou gain from rooting, the risks involved, how rooting is typically done, and important precautions to take if you decide to root your Android phone.
Benefits of Rooting
Root access gives you administrative privileges over Android, opening the door to many enhancements and customizations that are not possible on an unrooted device. Some of the major benefits include:
• Removing bloatware: You can uninstall or disable pre-installed apps that came with your phone (so-called bloatware) which are normally impossible to remove on stock devices 5. Eliminating these unwanted apps can free up storage and system resources.
• Deep customization: Rooting allows full theming and interface tweaks. You gain the ability to customize nearly every aspect of the UI – from icons and animations to system color themes – beyond what the default settings permit 6. This means you can truly personalize the look and feel of your Android device to your liking.
• Install any app or mod: With root, you are no longer limited to the apps available in the official Play Store. You can install third-party apps or mods from any source, including powerful apps that require root privileges to work 7. For example, you could use advanced backup tools, ad-blockers that work at the system level, or other special utilities not possible without root access.
• Improved performance and battery life: Many users root their phones to apply tweaks or use apps that can boost hardware performance or extend battery life. For instance, you could underclock or overclock the CPU, adjust kernel settings, or use apps to intelligently manage battery consumption – actions that typically require root permissions 8. When done carefully, these tweaks can make an aging device run faster or last longer on a charge.
• Latest Android updates and custom ROMs: If your phone’s manufacturer has stopped providing software updates, rooting can allow you to install the newest Android version (or even a completely custom operating system) on your device 9. Enthusiast communities create custom ROMs that offer updated Android releases and extra features. With root access, you can flash these custom firmware packages, effectively upgrading or replacing the stock OS beyond the official support lifespan of the phone.
These advantages show why power users are drawn to rooting – it removes barriers and gives you control of the device as if it truly were your own. You can tailor the software to fit your needs and keep your phone running optimally for longer. However, all these benefits come at a cost. It’s important to understand that rooting also has some serious potential downsides, as described next.
Risks of Rooting
Before you root your Android phone, you should be aware of the significant risks and disadvantages associated with the process. Gaining root access means bypassing many of the built-in safeguards of the operating system. Here are the primary risks of rooting:
• Possible “bricking” of the device: Mistakes during the rooting process or installing incompatible software can corrupt your device’s software. In the worst case, a failed root attempt might render your phone completely unbootable – effectively turning it into a useless brick 10. There is always some chance of irreversibly damaging the device if something goes wrong, so the process must be done carefully.
• Voiding your warranty: Rooting is legal, but manufacturers often consider it a violation of your warranty terms. Once you root a phone, you typically forfeit any warranty support 11. This means if your device malfunctions (even due to a hardware issue unrelated to rooting), the manufacturer or carrier can refuse free repairs or replacements. Essentially, you’re on your own if problems arise after you’ve rooted the device.
• Security vulnerabilities and malware: By removing Android’s built-in restrictions, rooting can leave your phone more exposed to malware or hacking. Android’s security model is designed to keep apps isolated for your protection. Rooting bypasses some of these protections, which means malicious apps or code could gain deeper access to your data if you’re not careful 12. For example, installing apps from untrusted sources or granting root permissions to the wrong app could introduce viruses, spyware, or other threats that can compromise your personal information. Using strong mobile security tools becomes even more crucial on a rooted device.
In short, rooting amplifies both power and responsibility. You get much more control, but you also assume the risks of things going wrong. Problems like software instability, lost warranty coverage, or potential security breaches are important to consider. For many casual users, these risks outweigh the benefits – modern Android phones are quite capable out-of-the-box, and the advanced tweaks from rooting aren’t necessities. But for some enthusiasts, the extra capabilities are worth the trade-off.
How to Root an Android Phone
The exact process for rooting an Android device can vary widely depending on the phone model and manufacturer 13. There is no one-size-fits-all method – each device has its own quirks, and rooting methods range from using official unlock tools to running third-party exploit programs. In general, there are two primary approaches to root an Android phone:
• Unlocking the bootloader: Many manufacturers lock the device’s bootloader (the program that launches the operating system) to prevent modifications. Unlocking the bootloader is often the first step to rooting. Some companies (such as Xiaomi, OnePlus, and Motorola) even provide official support for bootloader unlocking, making it easier to root their devices without hacking around vulnerabilities 14. Once the bootloader is unlocked, you can flash a custom recovery or firmware that includes the tools needed for root access. Typically, this involves installing a small program (often the su binary) that grants superuser permissions, along with a management app to control which apps get root rights.
• Exploiting software vulnerabilities: For devices that don’t have an unlockable bootloader or official method, the rooting process often relies on finding a security hole in the device’s software. A developer may discover an exploit in the Android system or manufacturer’s firmware that allows unintended privileged access. By running a specialized program or script that takes advantage of this vulnerability, you can gain root rights on the device without formal permission. This is essentially a hack – sometimes packaged as a “one-click root” tool that automates the steps. Many community-developed tools and tutorials exist for popular phone models to streamline rooting via exploits 15.
No matter the method, rooting typically requires connecting your phone to a computer and running command-line tools or dedicated software. It’s crucial to follow instructions specific to your exact device model and Android version, since using the wrong files or commands can cause failures. Reputable forums (like XDA Developers or Android enthusiasts communities) are excellent resources for step-by-step guides tailored to almost every device. You should never attempt to root your phone using a method for a different model – always double-check that the guide or tool matches your device precisely.
Precautions Before Rooting
If you decide that you want to proceed with rooting your Android phone, it’s wise to take some precautions to minimize the risks. Here are a few important tips to follow before and during the rooting process:
1. Do thorough research and get expert advice: Read up on the rooting procedure for your specific phone model and Android version. The process can be very different from one device to another, so make sure you understand the exact steps required for your phone 16. It helps to follow tutorials from trusted sources and to browse user feedback. If possible, ask for guidance on dedicated Android forums or have a tech-savvy person assist you, especially if you’re not confident doing it alone.
2. Back up your data and secure your device: Before rooting, always back up all important data on your phone (photos, contacts, files, etc.) in case something goes wrong and you need to reset the device. Also, install a reputable mobile antivirus/security app priorto rooting 17. Since a rooted phone is more vulnerable, having security software in place can help catch malware or suspicious behavior early. Keeping backups and security measures will save you from a lot of pain if the root attempt doesn’t go as planned.
3. Know how to un-root or restore the system: It’s a good idea to familiarize yourself with the procedure to un-root your device or return it to factory settings. If you change your mind or encounter issues after rooting, most devices can be restored to their original state by reflashing the stock firmware or using the root management app to remove root access 18. Having the unroot or recovery instructions on hand will give you a safety net. (In many cases, un-rooting can re-enable warranty service if you need to send the phone in for repair, though this isn’t guaranteed.) When in doubt, seek expert help to correctly un-root so that your device is fully back to normal.
By taking these precautions – researching, backing up, securing your phone, and knowing your fallback options – you greatly increase the chances of a successful root with minimal problems.
Which Phones Should We Root
Easiest Phones to Root
• Google Nexus / Pixel (unlocked models) – Google’s own phones are known for being root‑friendly. They have easily unlockable bootloaders (using a simple fastboot command) and no extra locks or bloatware. For example, Nexus devices could be rooted in minutes with a few commands since there are no carrier‑locked bootloaders to worry about 19. Pixel phones (when purchased as unlocked models, not through certain carriers) continue this tradition – you can toggle OEM Unlock and use standard tools to gain root access relatively easily 20.
• OnePlus (all models) – OnePlus flagships consistently rank among the most root‑friendly phones. OnePlus officially allows bootloader unlocking without voiding the warranty 21. Their devices have a strong developer community and OnePlus provides kernel sources quickly, so tools like TWRP recovery and Magisk root are usually available soon after release. In short, OnePlus phones are designed with modders in mind, making rooting straightforward.
• Motorola (unlockable models) – Many Motorola phones (especially the unlocked or international versions) can be rooted easily because Motorola provides an official bootloader unlock program. Devices like the Moto G series and Moto X (unlocked editions) allow you to request an unlock code from Motorola’s website, after which you can flash TWRP recovery and install Magisk for root. For example, the 2013 Moto G was popular for its simple unlock‑and‑root process. (Motorola even sold “Developer Edition” phones explicitly to cater to enthusiasts.) As long as the model isn’t one that the carrier blocked from unlocking, root is usually as easy as: unlock the bootloader, flash a custom recovery, and flash SuperSU/Magisk 22.
• Custom ROM Developer Favorites – Certain phone models are known in the community for being “rooter‑friendly” because they were popular with ROM developers. For instance, the Google Nexus 5 and OnePlus One were famous for how easily they could be unlocked and modded (and thus became reference devices for custom ROMs). Even some niche devices like Xiaomi’s Poco series (which allow bootloader unlock with an official tool, albeit with a waiting period) are considered relatively easy to root once unlocked. In general, any device with an unlockable bootloader, accessible fastboot/Odin interfaces, and a large user community tends to be easy to root.
Hardest Phones to Root
• Samsung Galaxy (U.S. carrier models, recent) – Samsung’s flagship phones sold through carriers like Verizon and AT&T are notoriously difficult or nearly impossible to root. These models come with bootloaders that are permanently locked (no official unlock method), and Samsung’s Knox security further hardens the system. For example, the U.S. Galaxy S7 and S7 Edge on Snapdragon were released with locked bootloaders and could not be rooted at all 23 (developers never found a public exploit, meaning those devices remain unrootable to this day). This trend—starting from the Galaxy S4 through S5, S6, S7 and onward on certain carriers—shows that if the bootloader is locked and no exploit exists, you simply cannot gain root. Newer Galaxy models (S8, S9, S10… up through S21/S22, etc.) continue this: the Verizon/AT&T units cannot be rooted because you cannot unlock them. Only the international (Exynos) or factory‑unlocked variants can be rooted. In short, a Samsung phone with a carrier‑locked bootloader is one of the hardest devices to root.
• Motorola Droid series / carrier‑locked Motos – Similar to Samsung’s situation, Motorola phones sold by carriers (especially Verizon’s “Droid” lineup and some AT&T models) often have no unlock option and thus are extremely hard to root. Motorola’s policy is to allow bootloader unlock on most factory‑unlocked devices, but not on carrier‑specific models. For instance, Verizon’s Droid Razr, Droid Turbo, Moto Z4 (Verizon variant) and others were never given unlock codes—if an exploit wasn’t found, those phones stayed unrootable 24. A common sentiment is: “If you plan to root the device, never buy a Verizon phone.” There have been a few hacky workarounds in the past (such as the paid tool Sunshine for certain Motorola models), but support was limited and it required finding a serious vulnerability. By and large, a Moto phone with a “Your device does not qualify for bootloader unlocking” message means no root for end users.
• Huawei / Honor (2018 and newer) – Huawei officially shut down its bootloader unlocking service in mid‑2018, which has made rooting new Huawei/Honor devices practically impossible 25. Without an unlock code, the bootloader stays locked and Huawei’s firmware is highly secure against tampering. Devices like the Huawei Mate 20, P30, Mate 30, and onward cannot be rooted because you cannot unlock them (Huawei stopped providing codes even to developers). A few boutique services have tried selling hacks for certain models, but for the average user there’s no reliable root method. Huawei’s strong security measures and reduced exploit development make these phones among the hardest to root.
• Nokia (HMD Global Android phones) – Nokia‑branded Android phones (since 2017, made by HMD Global) are known to have locked bootloaders with no official unlock method (with only rare exceptions). HMD did not provide any unlock tool for most models, and as a result, phones like the Nokia 6, 7, 8, 9 PureView, etc., have almost no rooting avenue. In 2018 an official unlock was briefly offered for the Nokia 8, but it was discontinued 26. Even today, Nokia smartphones are generally among the most difficult to root due to their policy.
• Vivo / iQOO and some Oppo devices – Vivo (and its sub‑brand iQOO) are examples of manufacturers that completely forbid bootloader unlocking. These phones often lack any publicly accessible unlock command, and Vivo does not provide codes to users. Without unlock, rooting is usually impossible because no known exploit has surfaced for their firmware. Tech enthusiasts often cite Vivo phones as some of the hardest to root. Oppo is related and, although sharing some tools with OnePlus in certain regions, many Oppo phones in specific markets remain effectively not rootable.
• Sony Xperia (carrier variants) – Sony generally allows bootloader unlocking on its global models (via an official site), so those aren’t hard. But some Xperia phones sold through carriers (e.g. Japan’s DoCoMo or certain U.S. carrier models in the past) had their bootloaders permanently locked with no official unlock method. Those specific variants can be extremely difficult to root – often no one bothers to target them. For instance, if you buy an Xperia on a carrier that doesn’t allow unlock, you might never see root on that unit (short of hardware‑level hacks). Overall, Sony’s own policy is better than most, so this is a more niche case.
• Google Pixel (Verizon models) – While Pixel phones are typically easy to root if you buy the unlocked version, the ones sold through Verizon are an exception. Verizon Pixels come with the bootloader unlock setting disabled by the firmware, and there is no way to unlock those bootloaders. Thus, a Pixel 3 or Pixel 4 from Verizon is essentially un‑rootable (unless a very drastic exploit is found). This is due to Verizon’s policy rather than Google’s; in fact, Google’s support pages confirm that you cannot unlock the bootloader on a Verizon‑sold Pixel 27.
• Other niche cases – There are other devices that are extremely hard to root: Amazon Fire devices (many Fire tablets and the Fire Phone have locked bootloaders; exploits exist but are hit-or‑miss), Microsoft Surface Duo (with a locked bootloader and little community support for rooting Verizon variants), and some Alcatel/BlackBerry Android phones (often no unlock provided). Generally, any device that is both obscure and has a locked bootloader will likely have no root method because no one invests the effort to crack it.
Samsung & Motorola Rooting Feasibility
Because most phones in the GDC seem to be either Samsung or Motorola, we’ll look into this further.
Bootloader Unlockability:
• Samsung: Outside of a few developer editions, Samsung does not provide official bootloader unlock codes for its devices. However, on international models (with Exynos chipsets), there is an “OEM Unlock” toggle in Developer Options that users can enable, allowing use of fastboot/Odin to flash custom firmware. This effectively unlocks the bootloader (though it will trip Knox). On U.S. Snapdragon‑based Samsung models, that OEM Unlock option is absent or blocked – the bootloader is cryptographically locked from the factory. Carriers like Verizon and AT&T insist on these locks 28. Thus, an unlocked (or unlockable) Samsung is easy to root, whereas a locked one is essentially unrootable. For instance, a U.S. Galaxy S9 (Snapdragon) cannot be unlocked, but an international Galaxy S9 (Exynos) can be unlocked and rooted with no issue.
• Motorola: Motorola offers an official bootloader unlock program on their website. Users can submit a string from their device and receive an unlock key, which when used via fastboot unlocks the bootloader. Many Motorola models (Moto G, Moto X, Moto Z series, etc.) can then be easily rooted. However, Motorola excludes certain carrier-branded models from this program. If you try to unlock a carrier‑locked device, you’ll receive a message stating “Your device does not qualify for bootloader unlocking.” Thus, unlocked Motorola devices are root‑friendly, while carrier‑locked ones are not.
Carrier Restrictions:
Both Samsung and Motorola are heavily influenced by U.S. carrier policies. Verizon, for instance, forbids bootloader unlock on all of its branded devices (affecting Samsung, Motorola, and even Pixel models) 29. Phones sold as “unlocked” or purchased directly from the OEM typically lack these carrier locks, making them easier to root.
Known Exploits & Custom Recovery Support:
• For Samsung, the typical method is to flash a custom recovery (like TWRP) or a patched boot image via Odin. Then you can flash Magisk to achieve systemless root. Developers such as Chainfire and topjohnwu have extensive documentation on rooting Samsung devices. If a specific Samsung model has TWRP available and an unlockable bootloader, it is usually rootable. In locked Samsung devices (e.g. Verizon models), because you cannot flash custom images via Odin (the process fails signature checks), attempts at exploit‑based root are rare and usually unsuccessful 30.
• For Motorola, once the bootloader is unlocked, you can flash TWRP and root with Magisk in a straightforward manner. Many Motorola devices have official or unofficial TWRP builds available, making rooting smooth. Exploit‑based methods existed for older Moto models (e.g., using apps like SunShine), but these are largely obsolete on modern devices.
Impact of Knox and Other Protections:
Samsung’s Knox technology is designed to discourage rooting by permanently tripping a fuse (the Knox warranty bit) when a custom binary is flashed, voiding the warranty and disabling certain secure features like Secure Folder and Samsung Pay 31. In contrast, Motorola lacks a comparable system, so while rooting may disable DRM for some apps, there’s no permanent hardware fuse.
General Factors Affecting Rooting Difficulty
• Bootloader Lock Status: If the bootloader can be unlocked (officially or via an exploit), rooting is almost always possible; if not, it becomes extremely difficult 32.
• Manufacturer Policy & Attitude: Root‑friendly manufacturers (e.g., OnePlus, Google) provide unlock tools and resources, whereas others (e.g., Huawei, Nokia) impose strict restrictions 33.
• Carrier Customizations and Restrictions: Carrier‑locked versions (especially in the U.S.) are often unrootable 34.
• Software Exploit Availability: Older devices often had one‑click root apps (e.g., Towelroot, Z4Root); modern devices are usually patched 35.
• Hardware Security Features: Newer devices with features like Titan M (Pixel) or Knox (Samsung) are inherently more secure and difficult to root.
• Community & Developer Support: Devices with large user bases have extensive guides and custom recovery support, making them easier to root.
• Android Version and Updates: Older versions (pre‑Lollipop) are typically easier to root due to unpatched vulnerabilities.
Conclusion
In summary, whether a Samsung or Motorola phone is easy or hard to root depends largely on the bootloader’s unlockability, manufacturer policies, carrier restrictions, and the availability of exploits or developer tools. Unlocked models from these manufacturers are generally easy to root with standard tools (Odin or fastboot + Magisk), while carrier‑locked variants (especially from Verizon/AT&T) are extremely difficult or impossible to root. Always check whether the bootloader can be unlocked first—that single factor often determines the overall rootability 36.
Rooting the Google Pixel
Below is a guide that explains how you can root an unlocked Google Pixel using our JP5 or JP6 tablets. Make sure your Pixel is an unlocked model or that you can unlock its bootloader (this will wipe your data).
Step 1. Prepare Your Tablet Environment
1. Install ADB and Fastboot:
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
(I know ADB is already installed, but I can’t remember if fastboot is)
37Step 2. Prepare Your Pixel Phone
1. Enable Developer Options:
• On your Pixel, go to Settings > About phone.
• Tap the Build number seven times until you see “You are now a developer.”
2. Enable OEM Unlock and USB Debugging:
• Return to Settings, then go to Developer options.
• Toggle OEM unlocking and USB debugging to ON.
38Step 3. Unlock the Bootloader
Warning: Unlocking your bootloader will erase all data on your device. Back up your data first.
1. Connect the Pixel to Your JP5 or JP6 Tablet:
Use a USB OTG adapter and a compatible USB cable to connect your Pixel to the tablet.
2. Reboot into Bootloader Mode:
On the Pixel, you can either use the power+volume buttons or type in a terminal (with the phone connected and USB debugging enabled):
adb reboot bootloader
3. Unlock the Bootloader:
Once in bootloader mode, run the following command on your tablet:
fastboot flashing unlock
Follow the on‑screen instructions on your Pixel to confirm.
39Step 4. Patch the Boot Image with Magisk
To gain systemless root, you’ll install Magisk. One common method now is to patch the boot image using the Magisk Manager APK (which can work without a PC).
1. Download and Install Magisk Manager:
• Download the latest Magisk Manager APK directly onto your Pixel (via a trusted source such as the official XDA thread or GitHub).
• Install it (you may need to allow installation from unknown sources in Developer Options).
2. Obtain Your Stock Boot Image:
• Download the official factory image for your Pixel from Google’s website.
• Extract the downloaded archive on your tablet to obtain the boot.img file.
403. Transfer the Boot Image to Your Pixel:
Use either an OTG USB drive or a file-sharing method to copy the boot.img file to your Pixel’s storage.
4. Patch the Boot Image with Magisk Manager:
• Open Magisk Manager on your Pixel.
• Use the “Install” option and select “Patch Boot Image File.”
• Navigate to and select the boot.img file.
• Magisk Manager will create a patched image (typically named magisk_patched.img).
415. Transfer the Patched Boot Image Back to Your Tablet:
Once patched, copy the magisk_patched.img file back to the tablet for flashing.
Step 5. Flash the Patched Boot Image
1. Reboot Your Pixel into Bootloader Mode Again:
Either use the power+volume buttons or run:
adb reboot bootloader
2. Flash the Patched Boot Image:
In your tablet’s terminal, navigate to the directory containing magisk_patched.img and run:
fastboot flash boot magisk_patched.img
423. Reboot Your Device:
fastboot reboot
Your Pixel should now boot with Magisk installed, giving you root access.
Step 6. Verify Root Access
1. Install a Root Checker App:
From the Play Store (or sideload an APK), install a root checker app to confirm that your device has root privileges.
2. Open Magisk Manager:
The Magisk Manager app should show that Magisk is installed properly and that your system is rooted.
Additional Notes:
• One-Click Root Apps:
Modern Pixel devices typically require bootloader unlocking and flashing via fastboot rather than “one-click” apps. Most one‑click root methods were common on older Android versions and devices. However, the above method does not require a full desktop computer—it can be done from your Jaypay tablet running our latest Ubuntu release.
By following these steps using your JP5 or JP6 tablet, you can root a Google Pixel phone without needing a traditional desktop computer. The process uses fastboot commands and Magisk’s patching tool via the Magisk Manager app, all of which can be managed from your tablet’s terminal and the phone’s interface.
Rooting a OnePlus Phone
Below is an example guide for rooting a OnePlus device using a JP5/JP6. As always, be aware that rooting may void your warranty, risk data loss, or even brick your device. Proceed only if you’re comfortable with these risks and have an unlocked device or can unlock the bootloader. This guide assumes you’re using a OnePlus phone with an unlockable bootloader and that you have a USB OTG adapter and cable available.
Step 1. Prepare Your Tablet
1. Install ADB and Fastboot:
Open a terminal on your JP5/JP6 tablet and run:
linux
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
43Step 2. Prepare Your OnePlus Device
1. Enable Developer Options:
• Go to Settings > About phone and tap the Build number seven times until you see a message that says “You are now a developer.”
442. Enable OEM Unlocking and USB Debugging:
• In Settings > Developer options, toggle on both OEM unlocking and USB debugging.
45Step 3. Unlock the Bootloader
Important: Unlocking the bootloader will erase all data on your device. Back up everything important first.
1. Connect Your OnePlus to the Tablet:
Use your USB OTG cable to connect the OnePlus to your tablet.
2. Reboot into Bootloader Mode:
In the terminal on your tablet, type:
adb reboot bootloader
Alternatively, power off the device and then press and hold the Volume Up + Power buttons until you see the bootloader screen.
3. Unlock the Bootloader:
Once in bootloader mode, enter the following command:
fastboot oem unlock
On newer OnePlus models (from 5 and onward), you may also use:
fastboot flashing unlock
Follow the on‑screen instructions on your OnePlus device to confirm the bootloader unlock.
46Step 4. Patch the Boot Image with Magisk
For a systemless root (which is preferable), you’ll install Magisk.
1. Download the Stock Boot Image:
• Visit the official OnePlus website or trusted developer forum (e.g., XDA) to download the factory image for your specific OnePlus model. Extract the downloaded archive on your tablet to obtain the boot.img file.
472. Transfer the Boot Image to Your OnePlus (if needed):
You can use an OTG USB drive or a file transfer app to copy the boot.img file to your OnePlus’s internal storage.
3. Install Magisk Manager:
• Download the latest Magisk Manager APK from the official source (for example, from GitHub or XDA Threads). Install it on your OnePlus (you may need to enable installation from unknown sources).
484. Patch the Boot Image:
• Open Magisk Manager on your OnePlus.
• Select the “Install” option, then choose “Patch Boot Image File.”
• Navigate to and select the boot.img file you transferred earlier.
• Magisk Manager will create a patched image (commonly named magisk_patched.img).
5. Transfer the Patched Image Back to Your Tablet:
Once patched, copy the magisk_patched.img file to your tablet for flashing.
Step 5. Flash the Patched Boot Image
1. Reboot into Bootloader Mode Again:
With your OnePlus connected to the tablet, type:
adb reboot bootloader
2. Flash the Patched Boot Image:
On your tablet, navigate to the folder containing magisk_patched.img and run:
fastboot flash boot magisk_patched.img
493. Reboot the Device:
After flashing, type:
fastboot reboot
Step 6. Verify Root Access
1. Install a Root Checker App:
Download a root checker app from the Google Play Store or sideload an APK to verify that root is working.
2. Open Magisk Manager:
Magisk Manager should indicate that Magisk is installed properly and that you have root access.
Additional Considerations:
• One-Click Root Apps:
While some older devices were rooted using one-click apps, most modern OnePlus devices require bootloader unlocking and flashing via fastboot, as outlined above.
• Community Resources:
The OnePlus community on forums such as XDA Developers is very active. If you encounter issues, check for device-specific guides.
By following these detailed steps using your JP5/JP6 tablet, you should be able to root your OnePlus device without needing a full desktop computer. The process uses fastboot commands and Magisk Manager’s patching feature, all manageable from your tablet’s terminal and your phone’s interface.
Rooting Motorola Phones
Below is an example rooting guide tailored for Motorola devices using your JP5/JP6 tablet (running Ubuntu Linux 14.04). Note that this guide applies only to unlocked (or unlockable) Motorola models—carrier-locked variants typically cannot be rooted.
Rooting Motorola Phones Using a JP5/JP6 Tablet (Ubuntu Linux 14.04)
Overview:
Motorola devices, when purchased in their unlocked or international versions, are generally easier to root. Motorola even provides an official bootloader unlock program. In this guide, we’ll walk you through the process of unlocking the bootloader, flashing a custom recovery (TWRP), and installing Magisk for systemless root—all from your JP5 or JP6 tablet running Ubuntu Linux 14.04.
Prerequisites:
• An unlockable Motorola phone (e.g., an unlocked Moto G, Moto X, or similar model).
• Your Motorola phone’s USB cable.
• A JP5 or JP6 tablet running Ubuntu Linux 14.04 with ADB and Fastboot installed.
• Basic knowledge of using terminal commands.
• Backup your data—this process will erase data on your device.
[efn_note]For installing ADB and Fastboot on Ubuntu 14.04, refer to: https://developer.android.com/studio/releases/platform-tools[/efn_note]
Step 1: Enable Developer Options and USB Debugging
1. On your Motorola phone, go to Settings > About phone.
2. Tap Build number seven times until you see a message saying “You are now a developer!”
3. Go back to Settings and enter Developer options.
4. Enable USB debugging and OEM unlocking.
Step 2: Unlock the Bootloader
1. Connect the Device:
Plug your Motorola phone into the JP5/JP6 tablet via USB.
2. Reboot to Bootloader Mode:
Open a terminal on your tablet and enter:
adb reboot bootloader
3. Obtain the Unlock Code:
Motorola provides an official unlock service. Visit Motorola’s bootloader unlock page on another device (or use a browser on your tablet) to request an unlock code. (Note: You may need to follow instructions provided on Motorola’s website.)
[efn_note]Motorola’s official bootloader unlock service can be found at: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device[/efn_note]
4. Unlock the Bootloader:
With your phone in bootloader mode and after receiving the unlock code, run:
fastboot oem unlock [unlock code]
Replace [unlock code] with the code provided by Motorola. Confirm the unlock on your phone’s screen if prompted.
Warning: Unlocking the bootloader will factory-reset your device.
Step 3: Flash a Custom Recovery (TWRP)
1. Download the TWRP Image:
Find the correct TWRP image file for your Motorola model from the official TWRP website. Save it to your tablet.
2. Flash TWRP:
In the terminal (with your device still in bootloader mode), navigate to the directory containing the TWRP image and run:
fastboot flash recovery twrp.img
Replace twrp.img with the exact filename of your TWRP image.
3. Boot into TWRP:
Once the flash is complete, use:
fastboot boot twrp.img
This command will boot the phone into TWRP immediately without overwriting the system (ensure you do not reboot normally just yet).
Step 4: Install Magisk for Root Access
1. Download Magisk:
Download the latest Magisk ZIP (available from the official GitHub repository) and transfer it to your phone’s internal storage.
[efn_note]Magisk releases can be found here: https://github.com/topjohnwu/Magisk/releases[/efn_note]
2. Flash Magisk in TWRP:
In TWRP, tap Install, navigate to the Magisk ZIP file, and swipe to confirm the flash.
Tip: Ensure your battery is sufficiently charged before proceeding.
3. Reboot Your Device:
Once Magisk is installed, reboot the device by selecting Reboot System in TWRP.
Step 5: Verify Root Access
1. Once your phone boots up, install a root checker app from a trusted source (if not pre-installed).
2. Run the root checker to confirm that Magisk has successfully granted root access.
Conclusion
By following these steps using your JP5/JP6 tablet, you can gain root access on an unlocked device—giving you more control over your phone. This guide is designed with the needs of GDC prisoners in mind, as rooting your phone can help bypass MAS systems imposed by the GDC to restrict communication. With root access, you can disable or circumvent these restrictions and maintain vital lines of communication. For more information on the specifics of circumventing MAS, see our guide: https://gps.press/understanding-mas-a-prisoners-field-guide/.
For more details on rooting and troubleshooting, check out comprehensive guides on XDA Developers: https://forum.xda-developers.com/
Sources and footnotes
https://nexus5.gadgethacks.com/how-to/root-nexus-4-nexus-5-under-minute-0155646
https://android.stackexchange.com/questions/189993/how-to-root-nokia-8
https://www.gsmarena.com/huaweis_bootloader_unlock_service_is_being_shut_down-news-31268.php
https://www.reddit.com/r/oneplus/comments/wr0rka/rooting_and_warranty_of_oneplus_phones/
https://developer.android.com/studio/releases/platform-tools
https://forum.xda-developers.com/t/guide-unlocking-bootloader-on-oneplus-devices.3711141
https://www.oneplus.com/support/softwareupgrade
https://topjohnwu.github.io/Magisk
https://forum.xda-developers.com/t/guide-flashing-magisk-to-any-device.3564430
https://nexus5.gadgethacks.com/how-to/root-nexus-4-nexus-5-under-minute-0155646
https://android.stackexchange.com/questions/189993/how-to-root-nokia-8
https://www.gsmarena.com/huaweis_bootloader_unlock_service_is_being_shut_down-news-31268.php
https://www.reddit.com/r/oneplus/comments/wr0rka/rooting_and_warranty_of_oneplus_phones/
- https://en.wikipedia.org/wiki/Rooting_(Android)
- https://us.norton.com/blog/mobile/android-rooting-risks
- https://en.wikipedia.org/wiki/Rooting_(Android)
- https://us.norton.com/blog/mobile/android-rooting-risks
- https://en.wikipedia.org/wiki/Rooting_(Android)
- https://us.norton.com/blog/mobile/android-rooting-risks
- https://us.norton.com/blog/mobile/android-rooting-risks
- https://us.norton.com/blog/mobile/android-rooting-risks
- https://en.wikipedia.org/wiki/Rooting_(Android)
- https://us.norton.com/blog/mobile/android-rooting-risks
- https://us.norton.com/blog/mobile/android-rooting-risks
- https://us.norton.com/blog/mobile/android-rooting-risks
- https://en.wikipedia.org/wiki/Rooting_(Android)
- https://en.wikipedia.org/wiki/Rooting_(Android)
- https://en.wikipedia.org/wiki/Rooting_(Android)
- https://us.norton.com/blog/mobile/android-rooting-risks
- https://us.norton.com/blog/mobile/android-rooting-risks
- https://us.norton.com/blog/mobile/android-rooting-risks
- https://nexus5.gadgethacks.com/how-to/root-nexus-4-nexus-5-under-minute-0155646/
- https://android.stackexchange.com/questions/249938/pixel-3-xl-verizon-unlock-bootloader-oem-not-highlighted-in-developer
- https://www.reddit.com/r/oneplus/comments/wr0rka/rooting_and_warranty_of_oneplus_phones/
- https://www.reddit.com/r/GalaxyS23Ultra/comments/13rnx24/does_my_warranty_get_void_if_i_root_my_phone_eu/
- https://forums.androidcentral.com/threads/u-s-carrier-s7-models-have-locked-bootloaders-and-no-rooting.658418/
- https://android.stackexchange.com/questions/189993/how-to-root-nokia-8
- https://www.gsmarena.com/huaweis_bootloader_unlock_service_is_being_shut_down-news-31268.php
- https://android.stackexchange.com/questions/189993/how-to-root-nokia-8
- https://www.androidpolice.com/2020/05/27/you-cant-unlock-a-verizon-pixel-4/
- https://forums.androidcentral.com/threads/u-s-carrier-s7-models-have-locked-bootloaders-and-no-rooting.658418/
- https://android.stackexchange.com/questions/249938/pixel-3-xl-verizon-unlock-bootloader-oem-not-highlighted-in-developer
- https://www.droid-life.com/2010/11/11/z4root-is-the-newest-1-click-root-app-should-root-almost-anything/
- https://www.reddit.com/r/GalaxyS23Ultra/comments/13rnx24/does_my_warranty_get_void_if_i_root_my_phone_eu/
- https://en.wikipedia.org/wiki/Android_Verified_Boot
- https://www.gsmarena.com/huaweis_bootloader_unlock_service_is_being_shut_down-news-31268.php
- https://android.stackexchange.com/questions/249938/pixel-3-xl-verizon-unlock-bootloader-oem-not-highlighted-in-developer
- https://www.droid-life.com/2010/11/11/z4root-is-the-newest-1-click-root-app-should-root-almost-anything/
- https://www.reddit.com/r/oneplus/comments/wr0rka/rooting_and_warranty_of_oneplus_phones/
- https://developer.android.com/studio/releases/platform-tools
- https://developer.android.com/studio/debug/dev-options
- https://forum.xda-developers.com/t/unlocking-bootloader-guide.3185103/
- https://developers.google.com/android/images
- https://topjohnwu.github.io/Magisk/
- https://forum.xda-developers.com/t/guide-flashing-magisk-to-any-device.3564430/
- https://developer.android.com/studio/releases/platform-tools
- https://www.xda-developers.com/how-to-enable-developer-options-on-android/
- https://www.oneplus.com/support/faq/detail/en/1547
- https://forum.xda-developers.com/t/guide-unlocking-bootloader-on-oneplus-devices.3711141/
- https://www.oneplus.com/support/softwareupgrade
- https://topjohnwu.github.io/Magisk/
- https://forum.xda-developers.com/t/guide-flashing-magisk-to-any-device.3564430/