I never post for help, but I am at my wits end.
I have a Vodafone tablet that's running 6.0 marshmallow that refuses to root. I did find a TWRP recovery compiled for the device, which I installed using SP Flash Tool.
TWRP seems to work as expected. I can make and restore backups, format partitions, mount system, delete files with the file manager and so on.
TWRP is also kept on every reboot. It never replaced by the stock recovery.
However, when I try and install the SuperSU zip 2.82 to root the device, it seems to be successful. However, when I boot into Android and open the SuperSU app, it says,"SU binary occupied" and closes.
That error is displayed when installing 2.82. When installing versions like 2.79, it shows the option to install the SU binary, again like normal, but it always fails to install the binary.
Using a root checker app from FDroid tells me the same thing, that root isn't avaliable. TWRP flashing should be working though, since I can flash busybox and it is detected correctly by the same root checker app.
Other root apps refuse to work.
Whilst in TWRP, I am able to browse the file system and the su file is located in system/xbin, again like it should be. Numerous other files from busybox are also located there, further signalling a successful flash. I can chmod 755 the su file without issue, but it doesn't fix anything.
The bootloader of the tablet is unknown to me. I can't boot into fastboot or bootloader mode. Trying to do so just reboots the tablet. Nothing is shown on the screen either, and it boots to Android again. I did enable ,"OEM Unlocking" in developer options.
Any ideas what I can do? I really want to give this device a thorough chance, since it is a surprisingly enjoyable device to use, and for the price I paid it's almost a total no-brainer.
I just want root so it can become a total no-brainer to own.
Thank you for your time.
I figured it out.
I tried installing Magisk by patching the boot.img within the app and flashing it via SP Flash Tool, and it worked perfectly.
I never thought of using that, but I am glad that I did.
So, yeah. Use Magisk.
Related
I have a quite strange problem on my HTC Hero (GSM).
Quite a while ago I flashed a backup of my stock 2.1 onto the phone because I forgot to titan-backup some apps, but in the process I seemingly somehow broke my recovery mode. Also since that point in time my superuser was ranting I should install an update of the su binary.
Now lately I tried some way to flash to cyanogenmod because of all the bloatware in stock HTC Éclaire. In this process I tried installing clockwork rom manager and titan. clockwork didn't have the rights to install recovery, regardless of the generally working root (universal androot states the device as rooted and at that point superuser worked as it should e.g. for ghost file manager and quikboot). So I googled and found that there was an alternative to superuser called supersu. I installed that after uninstalling superuser and that only gave me errors. Now I seem to have no working su bin, supersu only tells me anything I do fails and superuser gives me the following when trying to update the su bin (translated from German):
Downloading manifest... okay
Analyzing manifest... okay
Latest version = 3.1.1
Checking installed Version = legacy
Repairing database... okay
Unzipping sutools... okay
Checking current install path... /system/xbin/su
Downloading new binary... okay
Aquiring root access...
Remounting /system as rw... legacy
Copying su to /system... okay
Button saying "that was cool, do it again"
Click to expand...
Click to collapse
After that seemed not to work I tried flashing the recovery from fastboot, but that "remote operation" is "not permitted". Same goes for system remount via adb.
This means also, that in the current state I cannot flash a new su via update.zip as I don't have a recovery mode anymore.
Someone on the net suggested to install an OTA-update to fix most system files and reset root. Sadly the following update for my hero is buggy. It's a patch for the peep twitter client that broke my boot partition a couple of times before and every time I had to reset to Android 1.5 again via recovery - so I won't try it as I know I don't have recovery (only the red triangle of death)
Does anyone have any trick up their sleeves that could help restoring either the su bin or the recovery mode?
[edit]
just noticed I wrote a question about the semi-brick from the mentioned peep-update some time ago - including a solution. I will try that later on, but if someone figures something else so I can still backup my data before wiping everything I'd still be thankful for a hint.
[edit2]
I did reset the handset with a 2.1-RUU via hboot, but seemingly the recovery partition is still broken and I could not find a Clockworkmod Rom Manager-version that is a) running on 2.1 and b) actually working on my device to flash recovery and thus achieve anything... But at least I seem to have SU again, even though it is noted as outdated and I am unable to patch it.
Hello everybody !
Two days ago, I bought the Acer Liquid E3 (single SIM, not Duo), and after some research and a good thinking time, I went for rooting my device. I used the instructions provided on the official thread (actually, I used this simpler and french version provided by Shreps, since that's my mother tongue, but I checked that every step was the same).
I also checked that since my device is the single sim model, it wouldn't prevent the operations to go as intended. There is no clear info about this on the thread, but some guy having the same model as me didn't complain about anything, so I assumed he was able to root his phone with no problem.
As said in the instructions, I put the UPDATE-SuperSU-v1.99.zip file on my SD card, I installed the VCOM drivers to my computer, used SP Flash Tools to flash CWM 6.0.3.0 Recovery on my device, booted in Recovery mode (it was indeed CWM Recovery that booted), then navigated to :
install zip from sdcard > choose zip from sdcard > "UPDATE-SuperSU-v1.99.zip" > Yes - Install UPDATE-SuperSU-v1.99.zip
Everything seemed to go well, no error prompted and the operations ended with "Done !"
However, when I rebooted in normal mode ("reboot system now" in CWM Recovery) and checked with Root Checker, it was said that I wasn't root. SuperSU isn't installed, and when I manually look for the su binary, it can't be found neither in bin nor in xbin.
I did everything (from flashing CWM to install root from sdcard) again and again, and nothing changes. I tried to download again my SuperSU file or use an anterior version (v1.86) but it's still the same problem.
tl;dr : I tried to root via CWM Recovery, but even if no error prompts, su isn't neither in bin nor xbin.
Would you have an idea of what I'm doing wrong ? (And would be able to explain it to me in understable terms ? Even if I understand every step I've been through, I'm not very familiar with the rooting glossary...)
Also, by looking into the SuperSU zip, I found the installation script. Would it be dangerous to try these commands manually via ADB ? Could it work where the script failed (or help find the 'root' of the problem ?)
I have a last (but secondary) question : on the tuto from the official thread and its french version, it is said that I should change the name of "/system/recovery-from-boot.p" to "/system/recovery-from-boot.p.bak" to keep my custom Recovery ROM after a reboot, or the Stock Recovery would wipe it. As I failed to root the phone, I could change this file name, of course, but however, when I boot my phone into Recovery mode (unplugged from the computer), it boots directly on CWM Recovery.
It doesn't bother me as long as I have an operating Recovery ROM, but I was wondering if it was normal since I did nothing to keep CWM.
NB : I attached to this question a screenshot of the About menu of my Device, since it contains informations on my build version and maybe other things.
Just got a uhappy up580 mtk6580 5.1LP phone.
All sorts of problems with it if I try to do anything with it, as stock it works great, no issues. Install kingroot as thats the only way to root it, Ive tried them all... Cannot remove kingroot for super SU using ANY way including superSUme, all things on here and needrom etc... cant do it.
I cant unlock the bootloader using everything I've found on here, from simply selecting it in settings to ADB on the PC and terminal in root shell, says 'not permitted' or 'not allowed' or rewboots to a selection screen and the volume up button to select it wont work.
Cannot remove install.recovery.sh using an old esfile explore, root explore, adb root shell on PC and terminal etc... all say, not permitted or 'system is r/o' Used commands to r/w system but again, this isnt allowed/permitted.
Installed chainfires 'secureADB' I think it was called to allow ADB to to be used root in system, does nothing.
MTKdroidTools doesnt work on MTK6580 so cant get CWM recovery flashed that way.
Have downloaded numerous CWM/PhilzTouch/TWRP and tried to flash them with SPtools, and removing battery before rebooting recovery and that also, doesnt work.
MTKunpacktools cant unpack the recovery.img of stock rom....
Am really at the end of my tether now.
I have the full stock rom installed, and a full SPFlashTools stock back-up if anyone has any ideas? All I'm really wanting is Xposed installed, thats it, and know with another chainfire app I can flash a zip without a recovery, but needs super SU which I cant get installed....
Dont worry, sorted it.
Ive veen trying to root my sm-t380 to the point of even creating my own modded boot.img with security set to 0. When i felt like everything had been done correctly, magisk flashed successfully, and there were no bootloops, I go to magisk manager and see that only the ramdisk was modified. Sar and a/b were both no and the root status showed up as na. No app could detect the root.
What went wrong?
P.S SuperSU systemless dident work either
P.P.S SuperSU system puts me in a bootloop that lasts for around 15 minutes per bootloop
Bump
/\
The most simple method to detect Android is rooted:
Code:
adb devices
adb shell
You should now see either a ‘$’ or a ‘#’. The # means Android is rooted.
jwoegerbauer said:
The most simple method to detect Android is rooted:
Code:
adb devices
adb shell
You should now see either a ‘$’ or a ‘#’. The # means Android is rooted.
Click to expand...
Click to collapse
i know how to check, my problem is my device is **** and cant be rooted. Ive heard multiple places that say the sm-t380 is a sort of "touchy" device. It dosent like rooting AT ALL
Any updates with this? I'm trying to root with the latest OS this tablet has but is not picking magisk like it patch the BOOT.img perfectly but when I flash it with odin is not detecting anything.
I went through many guides for T380 and I get to the same point as OP and Barto604. TWRP installed success, Magisk-patched boot.img flashed success, system launches successfully, Magisk app shows "Installed N/A, Ramdisk Yes, A/B No, SAR No"
I tried running adb devices; adb shell and it shows $ so not rooted
flya258 said:
I went through many guides for T380 and I get to the same point as OP and Barto604. TWRP installed success, Magisk-patched boot.img flashed success, system launches successfully, Magisk app shows "Installed N/A, Ramdisk Yes, A/B No, SAR No"
I tried running adb devices; adb shell and it shows $ so not rooted
Click to expand...
Click to collapse
Hi I am reading through the xda treads have the same thing after patching the boot except my device in root checker says successfully rooted. What I did was switch from supersu to magisk( switch superuser app). I noticed the superuser binaries have to be installed or it will not work.
In my situation I just went inside supersu app and selected switch superuser app, then supersu uninstalls itself then reboot phone and open magisk app. root checker says successfully rooted.
I don't know if I am doing it right but my phone still says successfully rooted??
I rooted my Motorola One Macro today, I unlocked bootloader and installed Magisk. I don't have custom recovery beacuse i had problem with installing it. Root Checker says root is properly installed on my device, but I have somme issues with getting things to work. I downloaded Magic Mask Repo, and tried installing Energized module. It downloaded suscessfully, but installation doesn't seem to do anything even after reboot. I also tried installing it manually with Magisk, but I got this in console:
- Copying zip to temp directory
! Unzip error
I also tried installing busybox with the same result. Before that i also tried to install custom boot animation with Bootiful app which didn't done anything aswell. Reinstallation of Magisk dont help either. I dont really want to factory reset my phone, is there anything i can do?