How does one root a Samsung Galaxy S II GT-i9100 (with its original Android 2.3 Gingerbread), preferably under Linux Mint? This questions pertains specifically the GT-i9100 version (not GT-i9100G nor GT-i9100T, et cetera), which currently has no entry under the rooting index . I am particularly looking for a rooting method which does not wipe the data on the phone, as [I am hoping to recover data afterwards](https://android.stackexchange.com/questions/89133/data-recovery-on-boot-looped-samsung-galaxy-s-ii-gt-i9100) . I have an 8GB external SD card.

I installed a custom ROM (MIUI Splitfire) on my phone with Magisk 23.0v. Later I saw Magisk update, so I decided to upgrade to the latest version which is 25.0v from the app and got this error:

- Target image: /dev/block/sde45
- Device platform: arm64-v8a
- Installing: 25.2 (25200)
- Unpacking boot image
- Checking ramdisk status
- Magisk patched boot image detected
- Patching ramdisk
! Boot image kernel_dtb was patched by old (unsupported) Magisk
! Please try again with *unpatched* boot image
! Installation failed

[Screenshot of the installation log](https://i.sstatic.net/CUoTv.jpg)

This question might seem to be a duplicate of [this question](https://android.stackexchange.com/questions/24525/why-is-custom-recovery-a-prerequisite-for-flashing-a-custom-rom) but it is different. But I'd like to have a brief explanation on why we need a custom recovery to flash a ROM. My main points of confusion are: 1. In stock recovery we have a option to "*Install Update from SD card*". Why can't we directly flash a ROM from there? 2. If signature verification is the problem regarding the first point, then how can we root and flash custom recovery using update from SD card? Why doesn't any signing or verification problem occur while flashing root package or custom recovery package? Like any other custom ROM package they are also unsigned. Why is this?

I see lots of tutorials telling me *how* to root my phone (Motorola Droid), but none of them mention any potential "side effects." Aside from a few relatively minor issues that seem to require rooting to fix, I'm basically happy with the phone and therefore a little leery of messing with a device that cost me a lot of money and is only a few months old. Assuming that I'm *just* talking about rooting, and none of the typical post-root actions (like installing a custom ROM), am I taking any risks by choosing to root? * Does it have the potential to brick the device? * Will it void my warranty? * Will I stop getting updates? * Will the cops show up at my front door the next day? *(Yes, I'm being facetious.)* * Anything else I should be aware of? (See also: https://android.stackexchange.com/q/21042/1465)

I had root on 4.2 previously, but the update lost it, and with it my ability to use Sixaxis, AdFree, some features of NFC Tools and Tasker and Xposed modules. I have searched, but it does not appear on this list: https://android.stackexchange.com/questions/1184/how-do-i-root-my-android-device/1185#1185 I also saw a similar question here, but this is the AT&T version, not Verizon: https://android.stackexchange.com/questions/116438/how-to-root-the-sm-g900f-android-5-0-without-tripping-knox Towelroot doesn't work (just tried) and the SM-G900V isn't listed here: https://autoroot.chainfire.eu/ Anyone have any experience with this?

I've been trying to root my xperia ray device by following the instruction given in this post. It doesn't seem to work properly for me. Whenever I try to flash with 4.1.A.0.562 kernel it says that my device USB debugging is off even when I've ticked it. Also I've put it onto MSC mode. When I try to put it on flash mode both kernel.sin & loader.sin is grayed out. Below is the log what I get. 02/016/2014 02:16:42 - INFO - <- This level is successfully initialized 02/016/2014 02:16:42 - INFO - Flashtool Version 0.9.13.0 built on 2013-06-04 22:50:00 02/016/2014 02:16:48 - INFO - Device disconnected 02/016/2014 02:16:50 - INFO - Selected ST18 / 4.1.A.0.562 / Kernel 02/016/2014 02:16:50 - INFO - Preparing files for flashing 02/016/2014 02:16:50 - INFO - Please connect your device into flashmode. 02/017/2014 02:17:28 - INFO - Device connected with USB debugging off 02/017/2014 02:17:28 - INFO - For 2011 devices line, be sure you are not in MTP mode 02/017/2014 02:17:44 - INFO - Device disconnected 02/017/2014 02:17:47 - INFO - Device connected with USB debugging on 02/017/2014 02:17:47 - INFO - Connected device : SonyEricson Xperia Ray 02/017/2014 02:17:48 - INFO - Installed version of busybox : BusyBox v1.18.5 (2011-07-18 07:43:28 PDT) multi-call binary. 02/017/2014 02:17:48 - INFO - Android version : 4.0.4 / kernel version : 2.6.32.9-perf / Build number : 4.1.B.0.587 02/018/2014 02:18:14 - INFO - Device disconnected 02/018/2014 02:18:31 - INFO - Device connected in flash mode 02/018/2014 02:18:31 - INFO - Opening device for R/W 02/018/2014 02:18:31 - INFO - Reading device information 02/018/2014 02:18:32 - INFO - Phone ready for flashmode operations. 02/018/2014 02:18:32 - INFO - Current device : ST18i - CB511VGBZ7 - 1252-6163_R1I - 1248-9545_4.1.A.0.562 - WORLD-i_4.1.B.0.587 02/018/2014 02:18:32 - INFO - Start Flashing 02/018/2014 02:18:32 - INFO - Processing loader.sin 02/018/2014 02:18:32 - INFO - Checking header 02/018/2014 02:18:32 - INFO - Flashing data 02/018/2014 02:18:37 - INFO - Loader : S1_Loader_Root_773f - Version : R4A066 / Boot version : R9A029 / Bootloader status : ROOTABLE 02/018/2014 02:18:37 - INFO - Disabling final data verification check 02/018/2014 02:18:37 - INFO - Processing kernel.sin 02/018/2014 02:18:37 - INFO - Checking header 02/018/2014 02:18:37 - INFO - Flashing data 02/018/2014 02:18:39 - INFO - Ending flash session 02/018/2014 02:18:39 - INFO - Flashing finished. 02/018/2014 02:18:39 - INFO - Please unplug and start your phone 02/018/2014 02:18:39 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings 02/018/2014 02:18:39 - INFO - Device connected in flash mode 02/018/2014 02:18:55 - INFO - Device disconnected And I've attached a sample screen of what I get. Please advise me what to do.. I'm totally lost... even the log says flashing finished, my current kernel build is in 4.1.A.0.587 but not 4.1.A.0.562. Model number: ST18! , Android Version: 4.0.4 , Build number: 4.1.B.0.587

I have a Samsung Galaxy J2 Ace, running Android 5.1.1. I want to root it now, and I have installed its respective system firmware from Frija. Initially, I followed David Bombal's tutorial on how to root Android (he used Magisk), but later found out that it is only supported for Android 6+, and so it is not applicable. I have tried Kingroot, Kingoroot, SuperSU, Magisk, Ding Dong Root, etc., and none support the device. I decided that if I unlock the bootloader and then upload a custom ROM using Odin, the phone might get rooted. Just asking if this technique will work. (I am a Windows/Linux user and don't know much about rooting, just had a useless phone) If not, then how?

**Problem** I want to install Android in a VM to restore a backup using Titanium Backup. For this to work, I need Android to be rooted. **What I tried** I've tried to install Android-x86 4.3 in a Virtualbox VM. The installation seems to work. I made an 8GB partition disk (sda1), made it bootable, and installed Android in it from an ISO file. This all seems to work. Android starts, I can browse the internet, install apps, etc. Then I want to restart the VM, and guess what?! I go back to the installation screen, like starting up from the ISO live image. For normal stuff, I can make a snapshot, start that up, and do anything. My problem is that I need root permission to restore a Titanium Backup in that VM. And I cannot root this VM because the disk is not writeable. With Alt-F1, I become root and I can use a script to root Android. But my guess is that I'm still on the ISO and that is not writeable. **Update - another try with Android 4.2** As mentioned in the comments, 4.3 would have problems with root access. I tried 4.4, which didn't start at all. Then I tried 4.2, which has the same problem as 4.3 for me. I made a screenshot of what I see when I try to run the rootscript , which is described here . You can see the errors: **rm failed - Read only filesystem** How can I fix this? **My question** How can I install Android permanently on this VM, so it can reboot and then be rooted?

I am following the below post to root my Xperia E Dual. > [How To Root Xperia E! Latest Update! (Locked Bootloader)\*LINKS > UPDATED* NOOB > GUIDE!](http://forum.xda-developers.com/xperia-j-e/general/how-to-root-xperia-e-update-locked-t2409525) In step 4 to install Framaroot APK we need to Check the option "Unknown sources" and "Usb dubugging" (in Developer options) But when I am turning on the Developer option Flashtool is showing an message like below: 08/048/2014 01:48:38 - INFO - Device connected with USB debugging off 08/048/2014 01:48:38 - INFO - For 2011 devices line, be sure you are not in MTP mode I have tried changing the Usb connection mode but problem is not resolved. Could you please help? **Some info:** Operating System Used to flash: Windows 8.1

I'm trying to root Samsung Galaxy A03s (Tracfone, SM-S134DL) with Magisk and can't get it to work without the OEM on in the developers option. How do I turn on OEM?

I am trying to root my Samsung Galaxy Ch@t GT-B5330 (4.1.2) following this guide. I have reached the point when I am intended to use the recovery mode menu (that is reached by holding volume-up when turning the phone on) but here am I stuck: whatever I choose gives me the error icon I am still able to boot the phone the normal way (though it has became a little bit slower than it was before flashing and starts Firefox on itself occasionally). How do I finish the rooting process?

I recently flashed a custom ROM and rooted my Redmi 7A, and now each time I try to connect to a network from a TP-Link router, it just says "Check password and try again," even though I insert the correct password. Also, before rooting and flashing a custom ROM, it worked just fine, and I have tried multiple ROMs, and it still doesn't work.

My android device CPU is MT6592 (8xARM Cortex –A7@1664 MHz) with instruction set 32-bit ARMv7. Board and product is ht1_107a_iball_mjk. Apart from this, Codename is REL, Internal Memory is 16GB and RAM is 2GB. I did root and un-root my device multiple times. I see connected device through **adb devices command**. After **adb reboot bootloader** and **fastboot oem unlock**, I confirmed on android device by pressing Volume Up key but there is no change on device screen and computer screen even after 30 min. I changed USB cable and USB port. However, there is no change. Therefore, I am not able to unlock its boot-loader. After **adb reboot bootloader** and **fastboot flash recovery twrp.img**, I found No TWRP or other Custom Recovery images are compatible for my device. Therefore, I am not able to install Custom ROM as well. I tried all above procedures multiple times and with multiple ways. However, at the end I am with Stock ROM (Android 4.4.4). And only two processes I can do successfully; rooting and un-rooting. In such scenario, may my device be hard bricked, if I continue above processes multiple times forcefully?

I'm attempting to root a Samsung Galaxy A20s (Android 10). I've already patched the boot image with Magisk and enabled "OEM Unlocking" in Developer Options. I ran

adb reboot fastboot

However, when it reboots, fastboot devices shows no devices. Looking online, I found the odin4 utility and attempted to flash the phone by

tar cf boot.tar boot.img
./odin4 -b boot.tar

However, it failed with

Check file : boot.tar
/dev/bus/usb/001/120
/dev/bus/usb/001/120
Setup Connection
initializeConnection
Receive PIT info
success getpit
Upload binaries
boot.img
Close Connection
Fail request receive -5
FAIL close
Fail Close Connection

On my phone's screen, I see

OEM LOCK: ON (U)
...KG STATUS: CHECKING # I can't read the beginning of the line because it's in the round corner of the screen.
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T1, R1, A2, P2
AP SWREV: K 2, S 2
SECURE DOWNLOAD : ENABLE
DID : 
download mode !!
    Custom Binary(boot) Blocked by OEM LOCK

How do I unlock the OEM?

Just under a year ago, I changed carriers due to carrier unlock policies. The provider I switched to I was able to get the Pixel 7 Pro on a payment plan (2 years). With it being a Pixel, I thought at the time all Pixels were OEM unlockable. Man was I wrong, not only am I stuck paying off this phone for 2 years, but without carrier unlock first that can't happen. I know in every other device that If I issued a certain adb disable command, it bypassed that. Is there not something similar I can do to get OEM unlock without carrier unlock? Any help is much appreciated.

Seems I have searched vastly across the internet to no avail. So far, I've tried using a CF-auto-root file with Odin 3, and vroot, neither of which worked. The only helpful thread I've found was an XDA thread from may 2015 which still did not seem to help http://forum.xda-developers.com/galaxy-alpha/help/want-to-to-root-alpha-sm-g850a-t3107199/ The only other resource I've found were several forums and websites that link back to the same blog that claims to have rooted the phone, but the download file is labeled as malicious by chrome and there is no conformation by anyone that it actually works.

I've been looking to root my LG G2 phone (AT&T LGE LG-D800), but all methods require installing binaries from little-known (by me) sites with no Web of Trust rating. I feel hesitant to do that. Here are some rooting links I found for my phone: * https://forum.xda-developers.com/showthread.php?t=2448887 * https://theunlockr.com/2013/10/25/root-lg-g2-versions-video/ * https://web.archive.org/web/20161224210036/https://wiki.cyanogenmod.org/w/Install_CM_for_d800 requires ioroot: https://forum.xda-developers.com/showpost.php?p=48709232&postcount=869 The latter one refers to Kingo Root (its Web of Trust says XDA does not recommend it until it goes open source due to some suspicious activities, such as sending IMEI to the server) Which of these is safer than the others? Also, there was a manual way to root via ADB, or if there was source code, or if there was a reputable, trustworthy site to download from, I'd be feeling much more secure. I am a Java developer, new to Android development, but it's something I want to learn, so programmatic solutions are welcome.

I have tried only the android emulator in the android sdk, and waydroid until now. Apps installed into both say that they are running on a rooted device, what is right - having access to their image files I could actually do there what I want. However, I would be more happy to run seamlessly also them. Is there a solution, ideally free but also paid might be fine, where I can execute these apps and they do not know that the phone is "rooted"?

Before we start, just want to make it clear that I am aware how easy it is to brick this device, and have decided to go ahead rooting and installing a custom ROM anyway. My goal currently is to use twrp to install magisk and root the phone, but I cannot get the thing to boot into twrp. In case it matters, I'm running Miui 12.0.8.0 Global with Android 10 (4/01/21 patch) on a Global phone. My device is a 6GB/64GB variant with plenty of storage available. I've grabbed the required twrp image from the link in the XDA developers guide (https://forum.xda-developers.com/t/guide-begonia-unlock-bootloader-flash-twrp-and-root-proper.3995919/) as well as a vbmeta image for a Redmi Note 8 because I couldn't find one for the pro variant. I wouldn't expect that's an issue because they run the same OS, but because mine has a mediatek SOC I won't rule it out; if someone has the right vbmeta for me, it would be appreciated. My procedure is as follows: - Boot phone into fastboot, open minimal fastboot/adb from the guide. - Make sure twrp.img and vbmeta.img are in the fastboot directory - fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img - fastboot erase recovery - fastboot flash recovery twrp.img - Hold power and volume up to try to boot recovery. At this point, as long as I keep holding power+vol up the phone will make it to the "REDMI" splash screen, show me the unlocked bootloader icon, and power off. A few seconds later, it will try again to the same result. This will loop indefinitely until I stop holding volume up, at which point it happily boots into Miui; I've let it loop 5 times to be sure. If I hold just vol up (no power) once the phone turns on, like the guide says, it will pass the splash screen and simply shut off. I've tried multiple twrp and vbmeta images to the same result. The next thing to try was to boot directly to the image. I erased recovery, flashed vbmeta, and ran 'fastboot boot twrp.img." The phone hung on the fastboot screen for about 90 seconds before shutting off, and frustratingly then rebooting into *Miui* like nothing happened. If I try to boot to recovery after successfully booting Miui, it works, but I get the stock Xiaomi recovery, which will not help me root my phone. I'm running out of ideas on how to get this thing into the custom recovery. Still a little suspicious it's an AVB related issue, or some form of anti-rollback protection kicking in. Anyone here got any better ideas?

I have a Vantron Tech Tablet model 5081G with Rockchip 3366H processor. All the settings are locked. My PC doesn't recognize it as a USB device. In recovery mode, the only option is to reboot. Can anyone help me to unlock it?