[Q] Not rooting, but got Lollipop! - Galaxy S 4 Mini Q&A, Help & Troubleshooting

Very strange, all looks good, but still not rooted!
Phone: Samsung Galaxy Mini S4 - GT-I9195
Has recovery image, has:
recovery-clockwork-6.0.5.1-serranoltexx
cm-12-20141127-UNOFFICIAL-serranoltexx
S4Mini_RootKit_v2
Used:
Odin_v3.09
Tried reinstalled S4Mini_RootKit_v2 several times looks fine, but root checker etc say not rooted ;(

Try downloading superSU from play store if you don't have it in app drawer and try again. If it doesn't work change the recovery. I prefer Philz touch over all

No joy with Phiz. Now trying to install SuperSU beta (BETA-SuperSU-v2.42).
Version from Play store does not go in as says can't find files and if upgraded to lollipop need to do it manually.
May later down grade and then upgrade if works in older verion.
Will also try newer version of Lollipop if can get files, currently site timing out.

Rootkit v2 is only for stock ROM its not meant to be used with cm12, download latest supersu zip and flash in recovery

Re-rooted, installed CW 12 and updated SuperSU with latest beta binary and works!
Binary was: BETA-SuperSU-v2.42
Later updated to latest CW 12 (cm-12-20141228-UNOFFICIAL-serranoltexx) and still working.

Related

[Q] Issues installing TWRP

Hi,
I have the Samsung Galaxy Tab Pro 10.1 (SM-T520) running on Android 4.4.2. Rooting did go well (had to reboot a few times before knox disabled). I tried root checker and its OK.
I then would install TWRP. I downloaded the latest version for my device (2.8.0.0) and tried to flash the IMG with Flashify.
It said complete and rebooted into Stock recovery! Something did go wrong.. I tried TWRP manager (app from app store) to install TWRP, but it wants BusyBox.
I tried to install Busy box but it said it had a problem with installation and said I could try another directory.
I did, and again the same error. I couldnt find the file busybox in system/bin nor system/xbin.
What might the problem be? Should I continue, or is my device unstable and might I brick it?
Edit: Or would Odin do the trick and flash TWRP properly?
This is common and someone should answer already!!
michael64142 said:
Hi,
I have the Samsung Galaxy Tab Pro 10.1 (SM-T520) running on Android 4.4.2. Rooting did go well (had to reboot a few times before knox disabled). I tried root checker and its OK.
I then would install TWRP. I downloaded the latest version for my device (2.8.0.0) and tried to flash the IMG with Flashify.
It said complete and rebooted into Stock recovery! Something did go wrong.. I tried TWRP manager (app from app store) to install TWRP, but it wants BusyBox.
I tried to install Busy box but it said it had a problem with installation and said I could try another directory.
I did, and again the same error. I couldnt find the file busybox in system/bin nor system/xbin.
What might the problem be? Should I continue, or is my device unstable and might I brick it?
Edit: Or would Odin do the trick and flash TWRP properly?
Click to expand...
Click to collapse
Seriously... Do I tell TWRP Manager Root to install Stericson busybox or not?

[Q] SuperSU won't install?

I have T999LUVUBNF4. Used Odin to install CWM Recovery (recovery works fine). I boot into recovery and flash SuperSU (version 2.0). It appears to flash fine, but when I reboot SuperSU is not in my app drawer and I donot have root. Tried it several times.
Download newest supersu version and flash again. If it still doesn't work, use cf-auto-root
serio22 said:
Download newest supersu version and flash again. If it still doesn't work, use cf-auto-root
Click to expand...
Click to collapse
Thanks - I flashed the latest SuperSU over the weekend and got it to work.

[FIXED] Unable to replace Kinguser with SuperSU, updating binaries & keeping Root

[FIXED] Unable to replace Kinguser with SuperSU, updating binaries & keeping Root
I'm on KitKat 4.4.2 B510 firmware. After days of struggling to replace Kinguser with SuperSU, updating of binaries failed & keeping Root, I finally solved the issue. Now SuperSU is working perfectly. I tried everything possible, thinking there was an issue with my configuration or compatibility conflicts between SuperSU, Kinguser & Huawei P6 firmware. The problem was with SuperSU. There is an incompatibilty issue with SuperSU 2.46 & earlier versions updating binaries on some P6 phones running KitKat & having rooted their phones with Chinese rooting tools which were installing Kinguser instead of SuperUser as the app of choice. If you wanted to replace the app with SuperSU/SuperUser, you would've encountered many issues. Like
updating binaries, root permissions not given to SuperSU & incorrect root setup.
The SOLUTION is simple.
I found the latest version of SuperSU[2.48] in the test section of the SuperSU thread. SuperSU 2.46 is the latest stable official release & therefore found on Google Play, but since 2.48 is still in beta & being tested, it isnt available on Play or as an apk. You can get SuperSU 2.48 beta here:
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
It is a zip file & should be installed via a recovery. It is not available as an apk as it is still in testing & still an unofficial release.
I used TWRP to install it.
Boot into recovery, select install or update, find the file you just downloaded from the link & install the zip. Reboot. When your phone is finished booting up, automatically, Kinguser will be replaced with SuperSU 2.48 beta & the binaries will automatically be updated. Kinguser will be deleted, full root permissions will be restored to SuperSU, & no more issues with updating binaries. Solved.
Here is the link for SuperSU 2.48 beta again:
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Kingo User was driving me nuts!
adnaanhitman said:
I'm on KitKat 4.4.2 B510 firmware. After days of struggling to replace Kinguser with SuperSU, updating of binaries failed & keeping Root, I finally solved the issue. Now SuperSU is working perfectly. I tried everything possible, thinking there was an issue with my configuration or compatibility conflicts between SuperSU, Kinguser & Huawei P6 firmware. The problem was with SuperSU. There is an incompatibilty issue with SuperSU 2.46 & earlier versions updating binaries on some P6 phones running KitKat & having rooted their phones with Chinese rooting tools which were installing Kinguser instead of SuperUser as the app of choice. If you wanted to replace the app with SuperSU/SuperUser, you would've encountered many issues. Like
updating binaries, root permissions not given to SuperSU & incorrect root setup.
The SOLUTION is simple.
I found the latest version of SuperSU[2.48] in the test section of the SuperSU thread. SuperSU 2.46 is the latest stable official release & therefore found on Google Play, but since 2.48 is still in beta & being tested, it isnt available on Play or as an apk. You can get SuperSU 2.48 beta here:
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
It is a zip file & should be installed via a recovery. It is not available as an apk as it is still in testing & still an unofficial release.
I used TWRP to install it.
Boot into recovery, select install or update, find the file you just downloaded from the link & install the zip. Reboot. When your phone is finished booting up, automatically, Kinguser will be replaced with SuperSU 2.48 beta & the binaries will automatically be updated. Kinguser will be deleted, full root permissions will be restored to SuperSU, & no more issues with updating binaries. Solved.
Here is the link for SuperSU 2.48 beta again:
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
Thanks bro. This Kingo User crap was driving me nuts. I just don't trust the Chinese programmers. Kingo seems to have installed a lot more than su binaries. It was constantly going to the internet and uploading/downloading God alone knows what kind of stuff!
KingUser irritated me for a long long time & I struggled to find a solution. The biggest issue was tht my start ups wouldn't stick after restarting my phone. It definitely installed more than just the appropriate binaries. It made it almost impossible to install any other SuperUser app therefore eliminating the competition. Avast also kept reporting it as a threat. Now tht SuperSU is back on my phone, I've had no problems. My smartphone is running smoother & better than ever.
Glad I could be of help bro.
Any solution to devices without recovery? I own a Xperia C3 and there isnĀ“t a recovery for my phone and I wanna try this method
I think all devices have recoveries. They are used by the phone manufacturer or repair service ppl to service & repair our phones. I take it u mean u don't have a custom recovery, but a stock recovery. I haven't tried installing the file via stock recovery as I have TWRP(custom) installed. Last time I checked, it was possible to install or flash zip files via stock recovery. You may have to rename the file to update. zip, then use the install update option to install your zip file. Also Google what button- combination u have to use in order to enter the stock recovery for ur type of phone.

G928TUVU4DPK6 Firmware Root Issues

Has anyone upgraded their firmware to PK6 and attempted to root? I don't have any issues flashing TWRP with Odin. None whatsoever. When I flash a SuperSU zip or a PHH Superuser zip, I cannot get past the T-Mobile boot animation. It freezes every time. Once this happens I cannot boot to recovery. I can only boot to Download Mode. Hell, I can't even power down my device after I flash a root zip. Just curios if anyone has dealt with this issue. I have attempted to flash SuperSu zips starting with the 2.71 Beta up to the 2.78 SR5 with zero luck. I've also tried with PHH Superuser and I get the same results. Can anyone shed and light on the subject?
After several failed attempts to root my Galaxy S6 Edge+ (SM-G928T) with the latest firmware update to 6.0.1, G928TUVU4DPK6, this is what I had to do to get a working root solution. At no time did I ever have a problem installing TWRP with Odin. Ive been using Odin 3.12.3 but I had the same issues with Odin 3.10.7.
I started with a clean slate and performed a fresh install of the stock firmware which I downloaded from here:
http://forum.xda-developers.com/tmo...al/sm-g928t-stock-odin-g928tuvu4dpk6-t3516310
After flashing the stock firmware with Odin 3.12.3 I did the basic setup on my device to make sure I could boot and everything was working. Next, I shut down my device and booted to Download Mode by using the key combination of Volume Down + Home + Power. Once booted into Download Mode I used Odin again to flash TWRP 3.0.2-0, which is available here:
https://dl.twrp.me/zenltetmo/
After the flash was complete I booted to recovery using Volume Up + Home + Power. When TWRP starts it will ask you if you want to swipe to allow system modification. If you swipe to allow system modifications you will trigger DM-Verity and you will not be able to boot normally unless you flash a custom kernel that has DM-Verity disabled in the fstab or you can flash the no-verity-opt-encrypt.zip that I dowloaded from here:
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
The newest version available is 5.0
So, I swiped to allow system modifications. Next, I transferred the no-verity-opt-encrypt.zip from my PC to my device and installed the zip in TWRP. Once this was completed, I transferred my root zip from my PC to my device. I used the PHH Superuser to root my device which is available here:
https://superuser.phh.me/superuser.zip
I installed the root zip in TWRP, wiped cache/dalvik cache and then selected Reboot System. I didnt know if I would be able to boot or not. I could never get past the T-Mobile boot animation each time I attempted to root this damn thing but low and behold everything went as planned and I was fully booted up and running. I went through the setup wizard and everything was working as it should.
I am using PHH Superuser instead of Chainfires SuperSU. Its a personal choice for me as I have been using PHH Superuser since the hand off of SuperSU to a new company, CCMT, LLC.
Once I was finally able to boot normally I downloaded PHH's app in the Play Store from here:
https://play.google.com/store/apps/details?id=me.phh.superuser
This is just my experience of what I had to do to get root working on my S6 Edge+. All of my root apps are working as designed. I cant remember the last time I didnt have a rooted device and it was starting to bother me. I was having root withdrawals. If anyone decides to upgrade to the latest firmware from T-Mobile and wants a working root solution, here is what worked for me. I have not tried to use Chainfires SuperSU again. If you dont want to use PHH Superuser and wanted to use SuperSU instead, try to insert SuperSU in place of PHH Superuser and see what happens. Do this at your own risk because I have not tested it with this solution that I found. Good luck. Happy Rooting!!
fast69mopar said:
Has anyone upgraded their firmware to PK6 and attempted to root? I don't have any issues flashing TWRP with Odin. None whatsoever. When I flash a SuperSU zip or a PHH Superuser zip, I cannot get past the T-Mobile boot animation. It freezes every time. Once this happens I cannot boot to recovery. I can only boot to Download Mode. Hell, I can't even power down my device after I flash a root zip. Just curios if anyone has dealt with this issue. I have attempted to flash SuperSu zips starting with the 2.71 Beta up to the 2.78 SR5 with zero luck. I've also tried with PHH Superuser and I get the same results. Can anyone shed and light on the subject?
Sent from my SM-G928T using XDA-Developers mobile app
Click to expand...
Click to collapse
Here is the one I used. works great
Venal_System said:
Here is the one I used. works great
Click to expand...
Click to collapse
I tried that version too and I ended up with the same problem each time. I figured it out last night though. Im going to update my OP with the steps I had to take to get it working and that way if anyone upgrades to the latest PK6 firmware for their G928T and has this problem my thread is available with a solution.

Pixel XL will not root

Pixel XL running 8.0.0 OPR3.170623.007, developer options and USB Debugging are both on.
I was rooted for a while now, then I tried using one of my root-only apps and it told me it can't get root access.
I looked for SuperSU, which was missing.
I unrooted and rerooted using Skipsoft Unified Android Toolkit.
It flashed SuperSU 2.82 and flashed TWRP 3.1.1.1. The TWRP flashed just fine, but no matter how many times I flash SuperSU, it doesn't show up in my app drawer and the phone is still not rooted. I tried SuperSU 2.82 and the SR5 stable beta, neither worked. I also tried installing it through the Play Store after flashing it, it goes through the install process then just give me the option to install again, never fixes my issue.
Any idea on what I can do next?
edit: I updated to 3.2.0.0 and was able to root. Flashing the most recent beta and non-beta Magisk versions did not work, neither did installing the SuperSU APK. Once I updated to 3.2.0.0 I was able to root with Magisk just fine.
Flash the stock boot.img to both slots and reroot. Use SR5.
I would also advise to start by flashing the stock boot image. I would then boot twrp, flash twrp, then flash latest su.
If that doesn't work I would try going with the latest magisk zip (14.5)
I should have mentioned this, Unified Tool Kit flashed the factory boot image before releasing the latest TWRP and then flashing the most recent SuperSU. I did try flashing SR5 with negative results.
I'll give Magisk a try.
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-8-1oreo-unlock-t3715279
I followed 1,2,3,4,8, zero issues on 8.1.
I had a problem rooting with SuperSU. When i TWRP flashed it, it wouldnt show up in my apps, but my device was still rooted. For some reason the app just wasnt showing up so im using Magisk 14.5 instead...
DeviceManagent said:
I had a problem rooting with SuperSU. When i TWRP flashed it, it wouldnt show up in my apps, but my device was still rooted. For some reason the app just wasnt showing up so im using Magisk 14.5 instead...
Click to expand...
Click to collapse
Common issue. You can grab the app apk from inside the zip and install it.
I tried flashing both beta and non-beta Magisk versions and installing the SuperSU APK, nothing worked.
I saw that a new TWRP got released, 3.2.0.0. I flashed that and was able to successfully root. Thanks for your help, guys.

Categories

Resources