It's been a long time since I've rooted a phone, and I used to be fairly good at it... as in I usually don't have problems.
I've managed to get TWRP recovery, I've flashed Magisk and SuperUser and the phhSuperUser.
Once the phone boots I can open the SuperUser app without issues. I've moved files to the System folder with ES Explorer.
BUT, after a couple minutes, or instantly after I try to use something like Titanium Backup, the permissions toast message from SU keeps popping up and when I open SU it says something about not being able to flash binaries and "this is a bad thing". At this point if I try to do something that requires root access it fails. Can someone tell me what I'm missing here?
thefatalepic said:
It's been a long time since I've rooted a phone, and I used to be fairly good at it... as in I usually don't have problems.
I've managed to get TWRP recovery, I've flashed Magisk and SuperUser and the phhSuperUser.
Once the phone boots I can open the SuperUser app without issues. I've moved files to the System folder with ES Explorer.
BUT, after a couple minutes, or instantly after I try to use something like Titanium Backup, the permissions toast message from SU keeps popping up and when I open SU it says something about not being able to flash binaries and "this is a bad thing". At this point if I try to do something that requires root access it fails. Can someone tell me what I'm missing here?
Click to expand...
Click to collapse
May you post some screenshots?
Pretty much stuck here. I did a factory reset, then tried flashing supersu again. Tried flashing Magisk and phh SU. Tried flashing an older supersu, reflashed the current supersu. Before I had root for a few minutes at least. Now I can't root at all...
Edit: using TWRP Recovery by the way.
Edit: it's messing up at "decompressing ramdisk , failed"
Are you on MM or Nougat?
I'm still on 6.0.1
thefatalepic said:
...
Edit: it's messing up at "decompressing ramdisk , failed"
Click to expand...
Click to collapse
I need a screenshot of this... take a pic of it.
enetec said:
I need a screenshot of this... take a pic of it.
Click to expand...
Click to collapse
I don't really have a way of doing that, I saw someone else post it verbatim if that helps...
*****Boot image patcher*****
- Finding boot image
--- Boot image: /dev/block/mmcb1k0p33
- Extracting ramdisk
- Decompressing ramdisk
--- Failure, aborting
Note, it may say someone else after boot image on mine, but this is basically what I see...
thefatalepic said:
I don't really have a way of doing that, I saw someone else post it verbatim if that helps...
*****Boot image patcher*****
- Finding boot image
--- Boot image: /dev/block/mmcb1k0p33
- Extracting ramdisk
- Decompressing ramdisk
--- Failure, aborting
Note, it may say someone else after boot image on mine, but this is basically what I see...
Click to expand...
Click to collapse
Problem seems to be here...
I would reflash original boot.img (do you have a twrp backup of it still untouched?) and then retry to root using my "hacking experiences" tips...
Related
Rooted last night, superuser was working fine but this morning I lost all superuser access. Uninstalled SU and reinstalled it. Rom manager gained access but others won't. Now even when I try to flash CWM recovery it says "an error occurred while attempting to run privileged commands!". Any ideas?
you might have to look in this thread, and get the working SU that way
http://forum.xda-developers.com/showthread.php?t=1003088
magneticzero said:
you might have to look in this thread, and get the working SU that way
http://forum.xda-developers.com/showthread.php?t=1003088
Click to expand...
Click to collapse
Thanks, I was reading over that a few minutes ago. I'll give it a try
Tried to flash that patch but I can't boot into recovery. It boots into the bootloader, I select recovery and it just goes back to the white bootloader screen. Am I missing something?
since su works with rom manager, press menu and clear cache and try to push clockwork back on your phone. also there is a option to wipe clockwork mod everytiem you update it. alot of people have success with that.
magneticzero said:
since su works with rom manager, press menu and clear cache and try to push clockwork back on your phone
Click to expand...
Click to collapse
I did that, rebooted like 10 times trying to get into recovery and for some reason I know have su permissions again.... I dunno what happened.
But how do I get into cwm to install rom's and backup/restore? I keep getting the white bootloader screen for some reason.
Sorry, double post....
ugadroid said:
I did that, rebooted like 10 times trying to get into recovery and for some reason I know have su permissions again.... I dunno what happened.
But how do I get into cwm to install rom's and backup/restore? I keep getting the white bootloader screen for some reason.
Click to expand...
Click to collapse
there is an option in rom manager to boot into clockwork recovery, but i edited my last post.. maybe you need to push clockwork again if it isnt going into recovery the manual way, might not be loading the files properly
magneticzero said:
there is an option in rom manager to boot into clockwork recovery, but i edited my last post.. maybe you need to push clockwork again if it isnt going into recovery the manual way, might not be loading the files properly
Click to expand...
Click to collapse
Seems like something might have gotten messed up. Now I lost all su permissions again. lol. I probably should unroot and do the process over again. I've tried the option in rom manager but it takes me to the bootloader screen and when I select recovery it just takes me right back.
I also had this same exact problem. The reason was I had messed something up during the root process. What happened to me is I switched the RUU's around and ended up with the wrong one. My opinion would be to re-root using the original ADB method and make sure you are using the correct RUU. If you need assistance just PM me and I will guide you step through step to re-rooting your T-Bolt.
stedrocklp said:
I also had this same exact problem. The reason was I had messed something up during the root process. What happened to me is I switched the RUU's around and ended up with the wrong one. My opinion would be to re-root using the original ADB method and make sure you are using the correct RUU. If you need assistance just PM me and I will guide you step through step to re-rooting your T-Bolt.
Click to expand...
Click to collapse
I thought for sure I used the right RUU files but it was late so I could have messed up. I would appreciate any help, I used the windows one click method. Not too familar with ADB but I have played with it a lil. PM me when ever you get a chance. Thanks bro.
Mad props to stedrocklp for all the help last night. The help that people give on this site is why it's the best.
ok so i got my replacement thunderbolt and tried to use the 3 step root tool on here and i think something went wrong. i made it to step 3, it says s off and seemed ok. i rebooted, tried to fix permissions to test and it failed. now all i get is the HTC white boot screen and thats it. i can go into bootloader (the screen with hboot, recovery, etc) and i can load up recovery but when i try to do a restore (backup from the old phone) i get an error and it fails. is it screwed? what can i do to correct this? thanks guys!
[email protected]|ice said:
ok so i got my replacement thunderbolt and tried to use the 3 step root tool on here and i think something went wrong. i made it to step 3, it says s off and seemed ok. i rebooted, tried to fix permissions to test and it failed. now all i get is the HTC white boot screen and thats it. i can go into bootloader (the screen with hboot, recovery, etc) and i can load up recovery but when i try to do a restore (backup from the old phone) i get an error and it fails. is it screwed? what can i do to correct this? thanks guys!
Click to expand...
Click to collapse
If you can get into recovery, wipe EVERYTHING (data/cache/dalvik). Then mount USB and put a rom on your SD. Flash that. If you tried to fix permissions BEFORE you installed a ROM, then you kinda skipped a step mate.
DO NOT RERUN THE ROOT METHOD. IF you have S-OFF, jut flash a ROM
cj2566 said:
If you can get into recovery, wipe EVERYTHING (data/cache/dalvik). Then mount USB and put a rom on your SD. Flash that. If you tried to fix permissions BEFORE you installed a ROM, then you kinda skipped a step mate.
DO NOT RERUN THE ROOT METHOD. IF you have S-OFF, jut flash a ROM
Click to expand...
Click to collapse
thank you for the quick reply! so there is some hope for this thing then, woohoo!
yes i have wiped everything you mentioned. how does one mount usb from that menu? from within recovery? i saw a usb option on that (is it called bootloader?) is that what your speaking of?
now as a rom i DO have the gingerjane rom from jcase on there somewhere, is that safe to flash on there to fix this? thanks again!
If you have access to recovery (as you said you do) just load it, wipe, and flash any Thunderbolt rom you put on your sdcard (or already have in your case). Whether the rom you flash will fully works or not depends on whether it is compatible with your current radio.
But as long as you have access to recovery, you are set.
it booted! thank you both.
now im positive the root failed but it says s-off and superuser does show in the app drawer. im gonna try to d/l rom manager since its not on here anymore and see if it works.
if root failed am i safe to do the three step process again?
just don't flash roms with Rom Manager. It's known to cause problems with the Thunderbolt..
[email protected]|ice said:
it booted! thank you both.
now im positive the root failed but it says s-off and superuser does show in the app drawer. im gonna try to d/l rom manager since its not on here anymore and see if it works.
if root failed am i safe to do the three step process again?
Click to expand...
Click to collapse
Not sure what "3 step process" you are referring to but I'm gonna say no.
You have recovery. You can clearly flash roms. The roms contain Superuser.apk and su binaries which means THEY are rooted. Flash a good copy of a rooted rom from recovery and you will have working SU.
If that means you have to download another copy of a rom and put it on your sdcard then do it. Point is, roms are "rooted" not the phone. You can't "root" something that doesn't have an OS. Common misconception but I'm leaving it at that.
Everything is working great now, thank you all for your guidance and support. Love my android community. Can't thank you enough.
[Q]Sony BootLoop Solution??
Only post here is somebody get the solution of bootloop problem..
i think that the only think that we can do is wait for someone that posts an update.zip to be flashed via recovery, obviously for the different versione..mine is 16gb 3g (europe sgpt114it)...your is?
I understand that we're all happy we got root, but you gotta be careful running out and deleting/freezing everything without a proper way to restore!
Also, these question threads should all be moved to general.
sorry for posting here, but I can see many people facing this similar boot loop issue & other threads are getting flooded, that is why I posted here..
Lets try to find some way as of now to get rid of this frustrating boot loop !!!
EDIT:
Can anyone tell me, what exactly should be present inside those update.zip?
I am not able to unzip or see the content of signed-nbx03_001XXXXXXXXX.zip, giving some error !!!
it gives errors because the zip is encrypted
what if someone posts a full rom dump and i flash all the files manually via adb?
I tried with another zip and now in Recovery Mode , getting below error:
E:signature verification failed
Installation aborted.
xperiax10.awesome said:
I tried with another zip and now in Recovery Mode , getting below error:
E:signature verification failed
Installation aborted.
Click to expand...
Click to collapse
on that boot loop - do you have access to adb? for a second or two?
br
condi
i had, now it just hangs on the sony logo on the boot..the only hope left is an original update.zip for my model...
condi said:
on that boot loop - do you have access to adb? for a second or two?
br
condi
Click to expand...
Click to collapse
No..
sent via awesome aRc (rooted 2.3.4)
sapphire88 said:
it gives errors because the zip is encrypted
what if someone posts a full rom dump and i flash all the files manually via adb?
Click to expand...
Click to collapse
Since some files are encrypted or contain personal keys, I would think that this would be not advisable. Especially if you have the 3G version (IMSI keys, eyc.)
However, if you can remember what was the last action you performed before the bootloop (for example, uninstalled a particular system app), I would be happy to find the .apk and/or relevant system folder for you so you can install it via ADB (I suppose this would be possible, provided you still have ADB access and root/su).
I was trying to change the fonts using FONT CHANGER, I have not deleted any of the default apps or anything.
Tablet S, 16GB WiFi version (SGPT111SG)
xperiax10.awesome said:
No..
sent via awesome aRc (rooted 2.3.4)
Click to expand...
Click to collapse
****.. thats not good.. you cant even reflash the same version of update..
you could wait for another update from sony, or wait for some hack of recovery, or hm... warranty?
are you able to get into recovery?
I am able to go into Recovery Mode, tried updating thru sdcard but I think we dont have the proper firmware to restore!!!
Its under warranty but donno wanna go there, it needs a solution coz I will again try to change fonts for sure
Did you try looking at condi's post? I am not quite sure what condi managed to achieve, but it sounds at least relevant.
Also, bear in mind I have posted a link to the contents of the (stock) font folder. If we knew exactly what changes are made by this application, it would be possible to revert them. If you can find out, I can find the stock files for you so you can manually reverse this issue.
EDIT: Do NOT try any of the above -- according to sapphire88. You've been warned!
tried both the way, by replacing the fonts with the original ones and by editing the build.prop...the results is that now i'm stucked at the sony logo (no more one time access to the home screen) ...contacted sony to ask them if i could have the original firmware in update.zip format...perhaps (i don't really think that they will give it to me)...
Well, this still makes no sense however. Can we approach the developer of Font Changer and ask the sort of changes the application is performing? I assume that it is not just replacing fonts, but also some system files that point to the fonts that are being used. If we could track all changes and reverse them, surely this would fix the issue.
What about condi's downgrade/upgrade option? (you said it did not work)
Also, do you still have access to ADB (perhaps in recovery)? If you do, then you can still essentially find ways to fix this issue. But for the time being let's black list Font Changer.
i haven't used an app to change the fonts, i've manually replace the three clock fonts (only those three files), and it ended in a bootloop, in recovery adb doesn't work and i can't no more access to the home screen to use adb..
anyone know about Safety Mode?? How to enter into safety mode.
Note: I am NOT talking about Recovery mode..
grcd said:
What about condi's downgrade/upgrade option? (you said it did not work)
Click to expand...
Click to collapse
I think that I found a way to downgrade. Will check it today evening, will post the results.
sapphire88 said:
i haven't used an app to change the fonts, i've manually replace the three clock fonts (only those three files), and it ended in a bootloop, in recovery adb doesn't work and i can't no more access to the home screen to use adb..
Click to expand...
Click to collapse
ADB is available in recovery - just wait a minute or two - it will become available. But its not fully working as in normal boot. Check it, you can 'adb push' some files, maybe you could turn your fonts to stock ones?
xperiax10.awesome said:
anyone know about Safety Mode?? How to enter into safety mode.
Note: I am NOT talking about Recovery mode..
Click to expand...
Click to collapse
Yes, I figured it out some time ago, press power + vol-down, and keep vol-down pressed until tab fully start system.
ohh, so safe mode of no use as we are stuck with boot loop !!!
So I used the rooting guide at http://forum.xda-developers.com/showthread.php?t=1996389 and found a different superuser/busybox package to use. (don't remember the link right now).
However, whenever I open SuperSU to try to update it, it says installation failed or just reboots. And if I try to use root things for AdFree, it can't find the partition or just restarts.
Is anyone else having this problem or is there a different SU package I should use? My bootloader IS unlocked.
xDexter said:
So I used the rooting guide at http://forum.xda-developers.com/showthread.php?t=1996389 and found a different superuser/busybox package to use. (don't remember the link right now).
However, whenever I open SuperSU to try to update it, it says installation failed or just reboots. And if I try to use root things for AdFree, it can't find the partition or just restarts.
Is anyone else having this problem or is there a different SU package I should use? My bootloader IS unlocked.
Click to expand...
Click to collapse
Ive been using ViperDNA which comes with what seems like a custom SuperUser type of all in it.
But when I origionally rooted my phone, i seem to remember having an issue with SuperSU, and the first time i rooted i said screw it and just installed Superuser without any problems. The second time i rooted, i Installed SuperSU, then had to download Superuser form the Android Market, to update the binary, which updated it for SuperSU, and that solved my problem.
When you try to open an app that needs to use root access, do you get the notification asking for permission?
perhaps the "other" superSU/busybox package that you used didn't properly do what it needed to do?
I see the link on that tutorial is broken, fortunately i have the file that i originally downloaded form that very same tutorial saved to my hard drive, and now uploaded to DropBox if you would like to download it and try flashing this zip while in recovery to see if it gives you a proper root.
I would recommend downloading the above file, and flashing that to see if it helps. I'll try to remember to check back here to see if you posted anything in reply, but let me know if it doesn't work. Ill try to help as much as I can
BigRed35m said:
I would recommend downloading the above file, and flashing that to see if it helps. I'll try to remember to check back here to see if you posted anything in reply, but let me know if it doesn't work. Ill try to help as much as I can
Click to expand...
Click to collapse
I installed your package, and get the same errors before in SuperSU. It wants to upgrade but then force restarts whilst trying.
I then tried the Superuser app by Chainsdd, and I make a little progress?
First, when I try to upgrade, it asks for root from SuperSU and Superuser. Since SuperSU came with the busybox package, I can't uninstall it.
When I first go to the updater, it shows me this: (See attachment 1, I can't do links :S)
After I upgrade it, I am left with this screen: (see attachment 2)
It looks like it reverts back to su v .98 from 1.02?
Either way, as soon as I hit lets do it again, the phone restarts. Did I screw up the unlock/root somehow? In the top left of my fastboot screen it shows ***TAMPERED*** and ***UNLOCKED***
I am using CWM 6.0.2.1
BigRed35m said:
When you try to open an app that needs to use root access, do you get the notification asking for permission?
Click to expand...
Click to collapse
If I do it right when I reboot my phone it usually asks correctly
Thanks again for the help so far!
xDexter said:
I installed your package, and get the same errors before in SuperSU. It wants to upgrade but then force restarts whilst trying.
I then tried the Superuser app by Chainsdd, and I make a little progress?
First, when I try to upgrade, it asks for root from SuperSU and Superuser. Since SuperSU came with the busybox package, I can't uninstall it.
When I first go to the updater, it shows me this: (See attachment 1, I can't do links :S)
After I upgrade it, I am left with this screen: (see attachment 2)
It looks like it reverts back to su v .98 from 1.02?
Either way, as soon as I hit lets do it again, the phone restarts. Did I screw up the unlock/root somehow? In the top left of my fastboot screen it shows ***TAMPERED*** and ***UNLOCKED***
I am using CWM 6.0.2.1
If I do it right when I reboot my phone it usually asks correctly
Thanks again for the help so far!
Click to expand...
Click to collapse
It's difficult for me to troubleshoot when i haven't had to fix this problem since december haha.
The tampered, and unlocked is standard that is what it shows for everyone who unlocked the boot-loader.
So let me get this straight,
Do me a favor, un-install Superuser, download RootChecker from the market by JoeyKrim, And run it, what does it say?
->When you run it, did it ask for permission from SuperSU?
With just the SuperSU installed, if you run a program that requires root permission (For example, RootChecker), Nothing shows up asking if you want to Allow/Deny?
->When you open SuperSU to update the binary, it fails to update and restarts the APP?
With the SuperSU/BusyBox package flashed, when you install Superuser from the android market and try to update the binary, it *appears* to revert back to an older version of the binary?
-> After updating the binary through Superuser (despite the appparent reversion), if you un-install Superuser, and try to run RootChecker, does it work?
Sorry, i know it is a lot and i'm not much help, i'm troubleshooting blindly and from a distance haha.
xDexter said:
So I used the rooting guide at http://forum.xda-developers.com/showthread.php?t=1996389 and found a different superuser/busybox package to use. (don't remember the link right now).
However, whenever I open SuperSU to try to update it, it says installation failed or just reboots. And if I try to use root things for AdFree, it can't find the partition or just restarts.
Is anyone else having this problem or is there a different SU package I should use? My bootloader IS unlocked.
Click to expand...
Click to collapse
you need to install a kernel with /system writing enabled. Such as lk's or cubed
htc has a line wrong in their code and it makes it so that /system cant be edited while booted into android, only while in recovery. Installing a kernel that fixed this bug will let you use supersu from the play store and other apps such as adfree which need to edit system files to function
Bigandrewgold said:
you need to install a kernel with /system writing enabled. Such as lk's or cubed
htc has a line wrong in their code and it makes it so that /system cant be edited while booted into android, only while in recovery. Installing a kernel that fixed this bug will let you use supersu from the play store and other apps such as adfree which need to edit system files to function
Click to expand...
Click to collapse
Yeah this is what I figured out too.
Sent from my HTC6435LVW using XDA Premium HD app
Even with a writeable kernel SuperSu gives a hiccup at first. Download SuperUser, update the binary of SuperSu, then uninstall SuperUser. SuperSu will be fine after that.
orangechoochoo said:
Even with a writeable kernel SuperSu gives a hiccup at first. Download SuperUser, update the binary of SuperSu, then uninstall SuperUser. SuperSu will be fine after that.
Click to expand...
Click to collapse
I never had an issue with supersu
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
I never had an issue with supersu
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Quite a few of us running a version of Supercharged Hatka had problems when they switched to SuperSu,but now they switched back to SuperUser and the problem hasn't reared its head.
Below you will find my procedure to root the SM-J727P Galaxy J7 Perx / MSM8953
This procedure has only been tested on J727PVPU1AQB9 firmware. It may work for future releases or it may not.
If an updated firmware becomes available my advice is to update with FLASHFIRE to maintain root.
This took some doing and was a tough nut to crack. I don't own this device and much thanks goes to those that stuck with it in the testing phase, without whom it would not have even been possible. Credits below.
To see how we got here and before asking any questions click this link: https://forum.xda-developers.com/galaxy-j7/help/root-sm-j727p-galaxy-j7-perx-galaxy-j7-t3598117
DISCLAIMER: YOU FLASH THESE AT YOUR OWN RISK. THE KNOX COUNTER WILL BE TRIPPED AND WILL POTENTIALLY VOID YOUR WARANTY. HAVING THE STOCK FIRMWARE TO HAND IS ALSO ADVISED
NOTE: BEFORE MAKING MODIFICATIONS, ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Instructions:
◘ 1. Download the files below:
J727P-SuperSU-v2.79-SR3_rooted_boot_AQB9
ODIN 3.12
SAMSUNG_USB_Driver_for_Mobile_Phones
◘ 2. Install the USB driver and ODIN to Windows.
◘ 3. Boot your device to RECOVERY mode then select FACTORY RESET. THIS WILL WIPE YOUR DEVICE AND YOU WILL LOSE ALL DATA. (This procedure is required to remove encryption or your device won't boot)
◘ 4. From RECOVERY, IMMEDIATELY Boot your device to DOWNLOAD mode then connect your USB cable. (DO NOT LET YOUR DEVICE REBOOT NORMALLY OR YOUR DEVICE WILL RE-ENCRYPT)
◘ 5. Run ODIN and place the J727P_SuperSU-v2.79-SR3_rooted_boot_AQB9.tar file as is in the AP slot. Don't change any options and hit START.
◘ 6. Wait for the device to flash and reboot.
◘ 7. Install the SuperSU apk from Play store and you should be rooted.
◘ 8. Have fun!
Credits: ME, @Borams @Project89Odin @Chainfire and special thanks to @RS.85243
PLEASE LEAVE FEEDBACK IF YOU FIND MY WORK USEFUL. THANKS.
IF YOU APPRECIATE WHAT I DO AND WISH TO DONATE ME A COFFEE/BEER THEN CLICK HERE OR HIT THE THANKS BUTTON IF I HELPED YOU
I got the encryption error on reboot. I then did the reset it required and rebooted. I installed supersu just to see what it would say. It says root not properly installed in root checker, so I guess that means its there but I guess its a binary issue? Is there something that I didnt do correctly or a step I missed?
scbcskin said:
I got the encryption error on reboot. I then did the reset it required and rebooted. I installed supersu just to see what it would say. It says root not properly installed in root checker, so I guess that means its there but I guess its a binary issue? Is there something that I didnt do correctly or a step I missed?
Click to expand...
Click to collapse
Whoops glad you pointed that out, forgot to include that step!
I factory reset, booted directly to download mode, flashed tar, phone rebooted. I installed Supersu but still not rooted.
scbcskin said:
I factory reset, booted directly to download mode, flashed tar, phone rebooted. I installed Supersu but still not rooted.
Click to expand...
Click to collapse
When you open the SuperSU app does it complain about no binary installed?
ashyx said:
When you open the SuperSU app does it complain about no binary installed?
Click to expand...
Click to collapse
It sure does!!
scbcskin said:
It sure does!!
Click to expand...
Click to collapse
Strange, it works perfectly on Marshmallow. Looks like we're going back to the old method of manually pushing su.img to data!
Will update shortly.
Have you tried rebooting again to see if works after that?
Just did a reboot and same deal.
scbcskin said:
Just did a reboot and same deal.
Click to expand...
Click to collapse
I think I've just found the issue. Try this version instead, no need to format, just install with ODIN.
https://www.androidfilehost.com/?fid=961840155545567256
.
If you grant root permission before opening supersu apk but after downloading it, it does not ask to update binary with first op build
Project89Odin said:
If you grant root permission before opening supersu apk but after downloading it, it does not ask to update binary with first op build
Click to expand...
Click to collapse
Say again. Can you explain in more details, not sure I understand?
After process in op, after downloading supersu do not open it, download something that requires root and grant it. It will grant without ever opening supersu. I granted flashfire and flashed sr3 just to make sure. After reboot i opened the supersu app and it asks for no update. Although disabling knox did not work for me.
Project89Odin said:
After process in op, after downloading supersu do not open it, download something that requires root and grant it. It will grant without ever opening supersu. I granted flashfire and flashed sr3 just to make sure. After reboot i opened the supersu app and it asks for no update. Although disabling knox did not work for me.
Click to expand...
Click to collapse
OK I see. Can you do me a favour and test the updated version?
First delete su.img from /data or just unroot from SuperSU settings then reboot to download mode and install the new version. Your device should auto re-root.
https://www.androidfilehost.com/?fid=961840155545567256
ashyx said:
I think I've just found the issue. Try this version instead, no need to format, just install with ODIN.
https://www.androidfilehost.com/?fid=961840155545567256
.
Click to expand...
Click to collapse
Root has been achieved my friend. At first a flashed it and when it booted I got the encryption error. I just pulled the battery and then tried to boot into recovery. Instead of going in recovery it booted like normal. I installed Supersu and it got stuck attempting to disable Knox. Well after about 2 minutes or so of watching that I just went to root checker and there it was. I think I can speak for everyone when I say job well done!!!:good:
---------- Post added at 01:09 AM ---------- Previous post was at 01:00 AM ----------
Quick question, must you have custom recovery in order to install Xposed or is it just a suggestion?
After deleting su in /data andfull unroot, flashed newer build and supersu reports no binary, not even one to update, no root
scbcskin said:
Root has been achieved my friend. At first a flashed it and when it booted I got the encryption error. I just pulled the battery and then tried to boot into recovery. Instead of going in recovery it booted like normal. I installed Supersu and it got stuck attempting to disable Knox. Well after about 2 minutes or so of watching that I just went to root checker and there it was. I think I can speak for everyone when I say job well done!!!:good:
---------- Post added at 01:09 AM ---------- Previous post was at 01:00 AM ----------
Quick question, must you have custom recovery in order to install Xposed or is it just a suggestion?
Click to expand...
Click to collapse
Thanks for confirming. OP updated.
You can use Flashfire to install Xposed.
ashyx thank you for your efforts. Thanks to everyone else that helped as well. Guess what I just ordered. Can't wait to get my new phone and root, install viper4android. Both are a must for me and I never own a phone I can't have both on.
scbcskin said:
Just did a reboot and same deal.
Click to expand...
Click to collapse
When the reboot is repeated,
please flash the original firmware to odin
and try again from the beginning.
from CIAO7
after unrooting, repeating format is required to reroot. Works flawless. Thankyou again. Looking forward to a fully functional twrp now!!
Project89Odin said:
Thankyou again. Looking forward to a fully functional twrp now!!
Click to expand...
Click to collapse
It's next on my hit list. Just need to figure out why the source built kernel doesn't boot.
Now that root is achieved there's more chance of finding out what's going on, so I'll be calling on you guys again at some point for logs.