I'm at a loss as to what is wrong. I flashed a prerooted stock version of KitKat and I think root was working. But now for some reason it doesn't work. I flashed the supersu zip (v1.80) via TWRP recovery but after rebooting, the SuperSU app doesn't even show up on my device. When I install manually from thr Play Store it's as if I'm not rooted. I've flashed the zip multiple times and I do not want to factory reset and delete all my data (especially since I really can't backup without root atm). Any ideas?
Edit: sorry about the post title typo. *flashing
Related
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?
So i was trying to flash hacker kernel
It bootlooped.
So i reflashed renegade and tried reflashing.
it rebooted
now everytime i try and flash anything it reboots
super su is missing.
I installed super su from play store
when i go to flash binaries it reboots.
I updated TWRP
still same thing.
If i flash anything it just boots back to recovery.
Any thoughts?
Flashed back to stock and rerooted.
Did the trick.
Would you consider editing the topic to add the word "solved" please? The might help give others direction.
So when you started out from stock, you used Odin to install TWRP, but then thought you could get rooted by installing SuperSu from the Play store, which did not work.
Proper steps are to install TWRP using Odin with SuperSU on your phone. After TWRP is installed, instead or rebooting completely, reboot to Recovery and flash SuperSU that way.
Is that about right, @phelony?
koop1955 said:
Would you consider editing the topic to add the word "solved" please? The might help give others direction.
So when you started out from stock, you used Odin to install TWRP, but then thought you could get rooted by installing SuperSu from the Play store, which did not work.
Proper steps are to install TWRP using Odin with SuperSU on your phone. After TWRP is installed, instead or rebooting completely, reboot to Recovery and flash SuperSU that way.
Is that about right, @phelony?
Click to expand...
Click to collapse
No I had previously been rooted fine and dandy. for some reason TWRP started just rebooting on any flash.
so is it not going into bootloop mode anymore? because i've been having this problem for the last 6 months. i thought i'd try again and still doing the same, it'll get to the setup at the beginning and then reboot back to twrp????
My oneplus 3 was rooted (oxygen 3.2.5 maybe) but I installed the update 3.2.6 today from phone by going into settings. When the phone got updated my root does not work anymore. Please help.
I forgot how I rooted my phone before but it was still on android 6 when I rooted.
When I reboot I still get the black screen saying the device can't be trusted because xxxxxxxxxx Is unlocked, dont remember what.
Usb debugging is on as well as oem unlocked ( these options are still showing unlocked when i went to settings but don't know if they are ACTUALLY unlocked.
Xposed luck patcher, etc not working
Root checker says root not installed properly
Used twrp before.
Also is there any way that I can re-root my phone again without data loss?
Its my first post ever in any form so dont know about posting much.
You can mail me too at [email protected].
Thanks
Try flashing Super su manually from Recovery
Flash latest SuperSU (I think it is 2.78) in twrp. Flash xposed module in twrp too
If you did the official update from Settings > System Updates, then you are most likely back to stock recovery as well. You're going to have to re flash twrp before you can flash root and xposed. You will not lose data by performing any of these steps as your bootloader is still unlocked.
http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Download twrp
Boot to fastboot
fastboot boot sometwrp.img
Flash supersu from temporary twrp
Hw4ng3r said:
If you did the official update from Settings > System Updates, then you are most likely back to stock recovery as well. You're going to have to re flash twrp before you can flash root and xposed. You will not lose data by performing any of these steps as your bootloader is still unlocked.
Click to expand...
Click to collapse
If you had root and custom recovery (TWRP) then you couldn't have updated by this method as it wouldn't have worked. You need to reflash SuperSU in TWRP as others have stated.
Much simple: from recovery (hope you're having TWRP installed) flash latest SuperSU and Xposed zip file.
Then Wipe Cache/Dalvik, then reboot in System.
If you won't to lose root, you should consider a custom rom like FreedomOS, that provides SuperSU binary by itself (even Xposed, if I'm not wrong).
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.
hi,
i just installed the last beta version of OOS (beta 14) and my phone was previously rooted.
when i instaled the update, i reflashed super SU and when the phone booted up i had TWRP and SuperSU flashed but all my apps said the phone wasn't rooted (superSU showed me the message about SU binary not being installed or whatever).
i then uninstalled SuperSU and rechecked and all my apps said my phone was rooted. what did i do wrong? i am thinking that this is a temporary root without SuperSU so i would love it if someone had a solution and coul help me
Try to flash the superSU.zip once again without clearing cache .....it would work
i tried with and without clearing cache, nothing works. i also tried 4 different supersu zip files.
i even reflashed OOS and tried again (don't know if that does anything)