(My first post on the forums! You guys have helped me out so much in the past, and I'm excited to finally communicate with you. Wish me luck!)
I recently installed the 4.3 OTA update on my Samsung Galaxy S3, using the zips and instructions from these threads:
http://forum.xda-developers.com/showthread.php?t=2387423
http://forum.xda-developers.com/showthread.php?t=2538991
It went perfectly, without a hitch. Everything was running great, and I was loving everything about stock, de-samsungized 4.3, root and custom bootloader.
I was very interested in the dSploit app, and installed it, found out I needed Busybox. I installed it using the busybox installer. This is where the trouble begins. SuperSU needed a binary update after I installed busybox for some reason, even though I was fairly certain I already had the latest binaries. I tried running it through the automatic update with my teamwin bootloader, but it only booted into recovery and nothing installed. After googling it for a bit, decided to re-flash SuperSU. Suddenly, I began recieving the message "Unfortunately, SuperSU has stopped working" every time I tried to access anything requiring root priviledges. Anything that had already been granted root access (including Titanium Backup, thank goodness) seemed to work fine as long as it didn't need to request additional privileges. Unfortunately, I'm now locked out of ES File Explorer and the xposed framework (all prior installed modules continue to function though)
My initial thought was to wipe and reload using the process I used to get here in the first place, but I'm running 4.3 now, and I understand that downgrading is impossible now, and no flashable 4.3 stock roms seem to exist.
So I'm lost, guys. I need my root back somehow... If I forgot any information you think would be relevant and/or helpful, let me know and I'll provide anything you need. I've been googling and searching the forums for days, but I haven't found anyone with this exact problem.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
RidleyofZebes said:
(My first post on the forums! You guys have helped me out so much in the past, and I'm excited to finally communicate with you. Wish me luck!)
I recently installed the 4.3 OTA update on my Samsung Galaxy S3, using the zips and instructions from these threads:
http://forum.xda-developers.com/showthread.php?t=2387423
http://forum.xda-developers.com/showthread.php?t=2538991
It went perfectly, without a hitch. Everything was running great, and I was loving everything about stock, de-samsungized 4.3, root and custom bootloader.
I was very interested in the dSploit app, and installed it, found out I needed Busybox. I installed it using the busybox installer. This is where the trouble begins. SuperSU needed a binary update after I installed busybox for some reason, even though I was fairly certain I already had the latest binaries. I tried running it through the automatic update with my teamwin bootloader, but it only booted into recovery and nothing installed. After googling it for a bit, decided to re-flash SuperSU. Suddenly, I began recieving the message "Unfortunately, SuperSU has stopped working" every time I tried to access anything requiring root priviledges. Anything that had already been granted root access (including Titanium Backup, thank goodness) seemed to work fine as long as it didn't need to request additional privileges. Unfortunately, I'm now locked out of ES File Explorer and the xposed framework (all prior installed modules continue to function though)
My initial thought was to wipe and reload using the process I used to get here in the first place, but I'm running 4.3 now, and I understand that downgrading is impossible now, and no flashable 4.3 stock roms seem to exist.
So I'm lost, guys. I need my root back somehow... If I forgot any information you think would be relevant and/or helpful, let me know and I'll provide anything you need. I've been googling and searching the forums for days, but I haven't found anyone with this exact problem.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Have you tried uninstalling and reinstalling SuperSu?
Since SuperSU was flashed to the device via Odin, it is registered as a system app. The app store only has the open option, and I can't access the app in the system folder without root privileges, which it won't give me, so...
Yeah. Unless there's a script I can run through recovery, that's a dead end.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
there is a zip of SuperSU you can flash from recovery
Sent from my SGH-I747M using Tapatalk
I've tried this. In fact, that was when SuperSU began force-closing. I just need to completely uninstall it and start fresh, I think.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Have you tried the cleanup/unroot options inside supersu settings? Then starting over?
I might not have stated this directly before, but the SuperSU app won't launch. I tap on it and immediately get the "Unfortunately" error. I have no way of accessing anything within the app.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
RidleyofZebes said:
I might not have stated this directly before, but the SuperSU app won't launch. I tap on it and immediately get the "Unfortunately" error. I have no way of accessing anything within the app.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Ok well then find one of the 4.3 roms in development that you can use. I'm on s3rx 3.0 and other than some hiccups (still a wip atm) that are liveable, its pretty stable. You can flash this safely in recovery without the bootloader/modem package since you already took the OTA without risk of bricking. Its prerooted so no worries there. Good luck
pre4speed said:
Ok well then find one of the 4.3 roms in development that you can use. I'm on s3rx 3.0 and other than some hiccups (still a wip atm) that are liveable, its pretty stable. You can flash this safely in recovery without the bootloader/modem package since you already took the OTA without risk of bricking. Its prerooted so no worries there. Good luck
Click to expand...
Click to collapse
Thank you for that. It's always good to have a fallback option.
I'm still wondering though, is there a script I could flash that would completely remove SuperSU / BusyBox / superUSER (CWM) to scratch and allow me to re-flash CF-Autoroot? Barring that, how difficult would it be to code one myself?
FIXED IT.
Apparently, flashing the latest version of SuperSU from the developer's website (1.86) will not work on Android 4.3. I flashed version 1.65 as provided in the original 4.3 Rooting Guide, then updated it in the Play Store followed by a binary update and re-installed BusyBox, and everything is back to running order. Thank you all for your help and advice!
Related
Hey guys,
I have looked around for the solution to this but can't find one.
Starting out rooted, I updated my phone to SkyNote 4.3 (not sure if that helps) and still had root for a minute. I went through the process of setting up the phone how I like it, and after a few restarts, the root went away. This has happened twice. I've read posts where people talked about Android 4.3 deleting root but here's where the story gets interesting:
The threads/posts that people are pointing to to fix it is pretty much centered around Chainfire's post on Google+ https://plus.google.com/+Chainfire/posts/Jkuu84odnx6 .
The difference between the similar posts are that Chainfire has updated the version over the months. I have tried flashing that update zip over and over but I still have no root and the SU app is still buried in my system/app folder, which of course I can't delete because I have no root. I guess my questions are does anyone know how to delete this system/app apk for SU without wiping and starting from another ROM or know how to correct it in general?
Thanks you guys for reading.
Search the skynote thread your answer is there its called 1click
Sent from my SAMSUNG-SGH-I317 using Tapatalk
420techcloud said:
Search the skynote thread your answer is there its called 1click
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Click to expand...
Click to collapse
Thanks, I didn't think about that, but because of my unique situation, I couldn't even get 1click to recognize my phone. So after searching more and more, the answer is exactly what I was doing but a more updated SU zip. It's in the second post of SkyNote 4.3 http://forum.xda-developers.com/showpost.php?p=46798454&postcount=2
That may help another Android 4.3 ROM user
**
I have the exact same issue with my SGH_I317M. I rooted with CF-Root, flashed TWRP, flashed Skynote 4.3, flashed the update, flashed the Rogers modem and flashed the WIFI fix all with ODEN. Everything works. Even WIFI. But I lost Root. I made 2 full backups with TWRP. 1st. right after flashing TWRP still with 4.1.2 ROM and the 2nd after flashing 4.3 and all the patches. When I restore back to 4.1.2 all is good. When I restore to 4.3 Skynote, I loose Root. I tried flashing the SuperUser Update but it fails. Any help would be much appreciated.
Sent from my SAMSUNG-SGH-I317M using xda app-developers app
StevieG_007 said:
I have the exact same issue with my SGH_I317M. I rooted with CF-Root, flashed TWRP, flashed Skynote 4.3, flashed the update, flashed the Rogers modem and flashed the WIFI fix all with ODEN. Everything works. Even WIFI. But I lost Root. I made 2 full backups with TWRP. 1st. right after flashing TWRP still with 4.1.2 ROM and the 2nd after flashing 4.3 and all the patches. When I restore back to 4.1.2 all is good. When I restore to 4.3 Skynote, I loose Root. I tried flashing the SuperUser Update but it fails. Any help would be much appreciated.
Sent from my SAMSUNG-SGH-I317M using xda app-developers app
Click to expand...
Click to collapse
My last comment should help. When you flash the update, make sure it's the one from the post above. It carries the latest SU. If that doesn't work, I'm not sure what to do, but it worked for me because the SU binaries want to update but it needs the correct one.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Thank you Deon. I was reading this thread yesterday using the XDA app on my mobile for the first time. I downloaded the updated binary from this thread using my mobile. After several install failures I opened propertie for the zip and discovered it was empty. I downloaded the update from the OP through my PC, transferred the file to my SD and now all is good again with my root. CHEERS!
Sent from my SAMSUNG-SGH-I317M using xda app-developers app
Is there any chance that flashing the zip on ChainFire's page will brick your phone?
doran10 said:
Is there any chance that flashing the zip on ChainFire's page will brick your phone?
Click to expand...
Click to collapse
It won't brick your phone its pretty hard to trust me lol I used cf auto root tho
Hi I am new to this forum and a casual user. I wanted to root my note 2 tmobile android version 4.3 and actually rooted it once but knox created a lot of problem. I could not even launch titanium backup to freeze knox. Or was completely unable to disable knox. Now as android 4.3 has been released for quite a few months. Does anyone know of a method which will root my galaxy note 2 tmobile (SGH-T889) for sure and let me completely disable knox? If so please give me step by step instruction of rooting my device or alteratively you can provide me a link of the instruction so I can root my note 2 phone. I appreciate your help.
cooljd1 said:
Hi I am new to this forum and a casual user. I wanted to root my note 2 tmobile android version 4.3 and actually rooted it once but knox created a lot of problem. I could not even launch titanium backup to freeze knox. Or was completely unable to disable knox. Now as android 4.3 has been released for quite a few months. Does anyone know of a method which will root my galaxy note 2 tmobile (SGH-T889) for sure and let me completely disable knox? If so please give me step by step instruction of rooting my device or alteratively you can provide me a link of the instruction so I can root my note 2 phone. I appreciate your help.
Click to expand...
Click to collapse
cf auto root should work for root. what did you use to root? if you are rooted install a custom recovery and flash a knoxfree rom from the dev section
Flash CF auto root via Odin then download latest superuser from play store and you are ready to go.
All credits to ChainFire
Did you try this method, if so did it work for you? Im having similar issues with my tmobile note 2 running 4.3 too. I'd appreciate it, thanks in advance...
Sent from my SGH-T889 using XDA Premium 4 mobile app
J3D1mineTR1X said:
Did you try this method, if so did it work for you? Im having similar issues with my tmobile note 2 running 4.3 too. I'd appreciate it, thanks in advance...
Sent from my SGH-T889 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Just as a suggestion, something that happened to me while playing around with the phone: if you're running Stock rom and then flash a custom recovery via Odin (I used Philz Touch) upon booting on recovery just to wipe cache/dalvik I found something interesting: my phone wasn't rooted, so when chosing the option "reboot system now" a message that said something like "root is broken, would you like to root your phone before rebooting" appeared. I was curious, as I normally use a website called Kingo root that does it in a one-click kinda way. When I chose Yes in the recovery, upon booting my phone it was rooted. After, I just intalled Chainfire's SuperSU from the play store and it was all good.
It's worth trying I believe.
Cheers
Sobaro said:
Flash CF auto root via Odin then download latest superuser from play store and you are ready to go.
All credits to ChainFire
Click to expand...
Click to collapse
wavv.drama said:
Just as a suggestion, something that happened to me while playing around with the phone: if you're running Stock rom and then flash a custom recovery via Odin (I used Philz Touch) upon booting on recovery just to wipe cache/dalvik I found something interesting: my phone wasn't rooted, so when chosing the option "reboot system now" a message that said something like "root is broken, would you like to root your phone before rebooting" appeared. I was curious, as I normally use a website called Kingo root that does it in a one-click kinda way. When I chose Yes in the recovery, upon booting my phone it was rooted. After, I just intalled Chainfire's SuperSU from the play store and it was all good.
It's worth trying I believe.
Cheers
Click to expand...
Click to collapse
+wavv.drama
I have a question. If you don't run odin as a administrator do you get this error message: Windows cannot access the specific device path or file. You may not have the appropriate permissions to access. The last time I tried to root my phone i didn't run odin in administrator mode. I'm just finding out about this recently. I have all of the files installed on the computer and ready. Odin, recovery, keis, and supersu zip on sd card. Im just trying to figure out why I got that error message. Any ideas or suggestions would be appreciated. Thanks in advance... Awaiting your response...
"What good is knowledge if it's not to be shared"...
Sent from my SGH-T889 using XDA Premium 4 mobile app
J3D1mineTR1X said:
+wavv.drama
I have a question. If you don't run odin as a administrator do you get this error message: Windows cannot access the specific device path or file. You may not have the appropriate permissions to access. The last time I tried to root my phone i didn't run odin in administrator mode. I'm just finding out about this recently. I have all of the files installed on the computer and ready. Odin, recovery, keis, and supersu zip on sd card. Im just trying to figure out why I got that error message. Any ideas or suggestions would be appreciated. Thanks in advance... Awaiting your response...
"What good is knowledge if it's not to be shared"...
Sent from my SGH-T889 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The only answer that pops up in my mind would be that you weren't running Odin as an administrator, like you mentioned. Maybe try running Odin as an admin, or alternatively (and I haven't tried this myself but Chainfire's thread gives a good step-by-step and people in the forum do help) use mobile Odin ------> http://forum.xda-developers.com/showthread.php?t=1347899. The first time I wanted to root my phone I was having issues too, not being able to do it because of lack of experience. I stumbled upon this website: http://www.kingoapp.com/. Check it out, if you would like. This kingo app is a downloadle app (kind of like Odin) that Roots yourm phone alone, without needing to flash anything. The step-by-step's are there, just turn on your developer options and then turn on USB debugging. I personally rooted A Galaxy Tab, SIII, a Note I i717 and an Asus MemoPad with that website and it worked perfectly for me. Rooting via custom recovery is something that I learned recently, and by chance. I do not know whether it trips the Knox counter or not to be honest with you, to me it doesn't make a difference since I will not be returning any of the devices I rooted, After rooting the phone like so you could potentially download mobile Odin from Chainfire's thread and then use Odin without needing to use your computer.
Hope this helps
+wavv. Drama
Yeah that was it, i rooted it earlier today. I do have another question for you. I ran root checker pro and it says I'm rooted. I tried to install busybox but it said remove supersu permissions reinstall supersu and to delete and reinstall busybox. Also the adb shell doesn't have root access either. So is that a common occurrence, or is it the norm after rooting and installing custom recovery? Awaiting your reply. Thanks in advance...
What good is knowledge if it's not to be shared...
Sent from my SGH-T889 using XDA Premium 4 mobile app
Sorry for the late reply, hadn't been to the forum in a minute. To be honest with u, I don't know for sure. I haven't personally yet served myself from adb so I can't tell u. However, the reason why you received that response from busybox may be because when u were partially rooted it gained root access (if it ever did, I only assume).
Try what was asked of u and I'm sure busybox will work no problems. Also, if u have the terminal emulator apk try entering the command "root" (without the ") and if u gain roots access it will definitely mean you are rooted for sure.
What do you want to use adb for, if I may ask?
Sent from my SGH-T889V using XDA Premium 4 mobile app
So I haven't been on xda for a while. I've rooted my note a good 12x. I got a replacement and decided to keep it stock as long as possible. Now my phone just pisses me off with touchwiz. I wanna flash a twrp or cwm so i can flash cm11 and so on. I know Samsung just puahed this new update out so idk if anyone has rooted it yet. Does any one know how to root and instal cwm on 4.4.2? Really want to flash a rom. Thank you very much for time and feedback
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
Jonahng1994 said:
So I haven't been on xda for a while. I've rooted my note a good 12x. I got a replacement and decided to keep it stock as long as possible. Now my phone just pisses me off with touchwiz. I wanna flash a twrp or cwm so i can flash cm11 and so on. I know Samsung just puahed this new update out so idk if anyone has rooted it yet. Does any one know how to root and instal cwm on 4.4.2? Really want to flash a rom. Thank you very much for time and feedback
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
Click to expand...
Click to collapse
I used cf auto root heres the link
http://forum.xda-developers.com/showthread.php?t=1980644
Can you please confirm that cf worked on 4.4.2? Their site only shows compatibility up to 4.3. I've been searching everywhere, but found no confirmed reports of cf or anything else working on 4.4.2. I want to root my i317 while retaining the stock rom so that I can enable tethering.
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
MikeKidder said:
Can you please confirm that cf worked on 4.4.2? Their site only shows compatibility up to 4.3. I've been searching everywhere, but found no confirmed reports of cf or anything else working on 4.4.2. I want to root my i317 while retaining the stock rom so that I can enable tethering.
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
Click to expand...
Click to collapse
Ive used it myself it works just fine
CF method worked on my i317 with Stock 4.4.2. I seen that the compatibility was up to 4.3 but I tried it anyways.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
What recovery are you using, and how did you install it, TWRP bricked mine.
C auto root is flashed with odin in download mode. While rooting, it installs a custom recovery.
maybe it's kitkat, but it didn't install one for me. When I went into recovery, it was the normal factory recovery, which allowed nothing. I tried with Rom Manager, but nothing.
CF worked
I had to manually install the latest Supersu apk then update the binaries to get it working afterword, but I'm finally rooted
Now to get tether working
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
did you get a recovery to work, and if you did, how!
jappel2 said:
did you get a recovery to work, and if you did, how!
Click to expand...
Click to collapse
Download a recovery like philz and flash it in odin while the phone is in download mode
Let me ask you this:
1. root with odin.
2. install CWM with odin?
3. Not I have 4.4.2 stock rom with root.
4. Can I install a custom rom with 4.4.2. stock rom still on the phone?
jappel2 said:
Let me ask you this:
4. Can I install a custom rom with 4.4.2. stock rom still on the phone?
Click to expand...
Click to collapse
Yes, if 1 - 3 is accomplished, you are ready for experiments in custom roms. You use the recovery to flash.
But make sure you have the latest recovery, and that you check the rom instructions a few times before you do anything.
Ok....cwm from Rom manager, or twrp through odin? I don't mean to break chops, I've rooted a captivate and played with it for a year, when my wtty was over with this phone, I rooted it, and had JediX 19 on it. I went back to stock, and then 4.4.2 When samsung stock 4.4.2 was installed, for some reason, it keeps bricking on me.
Ok, I rooted, and installed twrp from odin,.... passed. When I go into recovery, it's not there.
Ok. Hopefully someone has an answer. I rooted with CF auto root, Odin....fine. Installed CWM, fine. Downloaded SuperSU.....unfortunately superuser stopped working everytime I press on it. I cannot uninstall it, because it DOES NOT show up in application manager. I installed root checker, and says phone is not rooted. I can get into clockwork MOD, but no zip files show up. Can I use Odin to re flash CF auto root?, or just quit, I would hate to brick this again.
Sounds like Knox is blocking you. After rooting, install the latest Supersu apk (2.02) and install manually. Then when you open it, it should ask to update binaries. Let it, then it should ask about dialing Knox. Click yes. Viola, you're fully rooted. After the above is done, you can play with ROMs n such.
Up till that point, there is no need to flash anything, as auto root is designed to do the work for you from a pure stock rom.
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
MikeKidder said:
Sounds like Knox is blocking you. After rooting, install the latest Supersu apk (2.02) and install manually. Then when you open it, it should ask to update binaries. Let it, then it should ask about dialing Knox. Click yes. Viola, you're fully rooted. After the above is done, you can play with ROMs n such.
Up till that point, there is no need to flash anything, as auto root is designed to do the work for you from a pure stock rom.
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you sir! I went into ES file explorer, and manually installed SuperSU. Although it never asked about dialing KNOX. I installed Root Checker, and it says I'm rooted. Appreciate yours and everyone else's help. Have a great day.
H i all Let me start by apologizing as I'm sure I'm doing something here that I'm not supposed too. Although I am new to XDA, until recently I didn't know I was such a tech virgin.. I have spent off and on months trying to figure out why my LG G2 has prematurely entered mechanical menopause. I have read scores of articles, tried numerous "fixes", various roots etc, but I can't get it right because I can't make out what's wrong. About the phone: Sprint Lg G2 LS980 ZVE running Android 4.4.2. I rooted my phone not long after I got it, which was back before the latest updates. Unfortunately I lost my phone for several months and when I got it back it had of course been updated. When installing a root checker the phone says Not Rooted, when it's in download mode or when I tried to use Stumproot it says I'm already Rooted. Upon opening SuperSU I get this warning, "There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3 you need to manually re-root - consult the relevant forums for your device." Upon opening BusyBox I get this message, "There was a problem opening a shell with root access. This is either being caused by Superuser/SuperSU or by a device that is improperly rooted. Try removing permissions, uninstalling and then reinstalling this application, blah blah blah, but of course SuperSU acts as previously mentioned when opened. I don't know what to do besides potentially flash stock but I really don't want to do that. I am a stubborn, learn by doing kind of techie but after months of learning everything but the answer, I raise the white flag. Please someone tell me there is an easy/obvious answer that I missed as I'd rather be a moron with an ignorant miss, than a stubborn ass with time consuming fixes in my immediate future.
Thank you so much, Jo
You will have to use the zve tot that's the only way to fix it, then stump will work perfectly.
Sent from my LG-LS980 using XDA Free mobile app
Thank you
I have gone through the process of flashing back to stock twice now and both times it ends in an error that says there is no kdz file. Any advice please?
Kdz is for Verizon or other carriers. Sprint is strictly tot. Make sure you are following the right directions.
Sent from my LG-LS980 using Tapatalk
i would suggest zv8 and root and custom recovery , after the zvc onto zve,zvd root with stumproot, also do not upgrade(OTA) on a custom recovery, i would hightly consider, downgrade to zv8 updgrade all the way to zvd stumproot and then install custom recovery
Even better, downgrade zv8, root via ioroot25, install auto-rec.
Flash upgraded TWRP, flash resurrection remix, gapps. And be done with it.
Sent from my LG-LS980 using Tapatalk
secret.animal said:
Even better, downgrade zv8, root via ioroot25, install auto-rec.
Flash upgraded TWRP, flash resurrection remix, gapps. And be done with it.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
yup that is the right way^ thats what i have done i always downgrade because most people who try to get there MSL dont realize you can get it be downgrading to zv8 root and install the recovery, all on that version.
Do you lose band 26/41 LTE by running zv8? I agree with above, must use a tot file to return to stock, then root will work.
secret.animal said:
Even better, downgrade zv8, root via ioroot25, install auto-rec.
Flash upgraded TWRP, flash resurrection remix, gapps. And be done with it.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
How stable is this ROM? Does GPS and everything work on it? Only thing stopping me from doing this is losing stability of stock.
KelevrA_8 said:
How stable is this ROM? Does GPS and everything work on it? Only thing stopping me from doing this is losing stability of stock.
Click to expand...
Click to collapse
I've had no issues and funny thing you ask about GPS. I have never had an issue with any rom with GPS. Though many others do.
secret.animal said:
I've had no issues and funny thing you ask about GPS. I have never had an issue with any rom with GPS. Though many others do.
Click to expand...
Click to collapse
Good deal
Hi all,
I'm running a Sprint Note 2 (SPH-L900). I finally bit the bullet this week and upgraded from CM 11 to CM 12.1. However in the upgrade from KitKat to Lollipop, I seem to have lost root. I tried reinstalling SuperSU via both apk and by flashing in Philz recovery, but whenever I reopen SuperSU, I get a message that says "The SU binary is missing and SuperSU cannot install it. If you recently upgraded to Android 5.0, you need to manually re-root. Please consult the forums."
I've looked in the forums, but it seems like the answer that worked for most people is to flash SuperSU from recovery, which I have already done. Do I have to flash a file again through ODIN download mode like I did when I first rooted? If that's the case, can I flash a file which includes CWM on top of Philz that I already have, and will that be compatible with Lollipop?
I'd like some guidance so I don't accidentally brick my phone. Thanks for any guidance in advance!
Well all 5.1.1 roms come rooted. You just have to enable developer options (google it) and allow root for apps. If you want supersu then you need the newest version which only the new twrp has (although I think there is still issues with twrp for our device). I suggest using CyanideL if you like cm. CyanideL can be found under the development section.
FYI there is almost no brick on this device that cannot be recovered from. Flashing roms/recoveries/kernels are no real worries.
Sent from my GT-N7105 using XDA Premium 4 mobile app
jlmancuso said:
Well all 5.1.1 roms come rooted. You just have to enable developer options (google it) and allow root for apps. If you want supersu then you need the newest version which only the new twrp has (although I think there is still issues with twrp for our device). I suggest using CyanideL if you like cm. CyanideL can be found under the development section.
FYI there is almost no brick on this device that cannot be recovered from. Flashing roms/recoveries/kernels are no real worries.
Sent from my GT-N7105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks. I forgot about developer options; did that and set option to all Root Access for Apps only, but my apps still don't have root. Any other ideas?
pillzbury said:
Thanks. I forgot about developer options; did that and set option to all Root Access for Apps only, but my apps still don't have root. Any other ideas?
Click to expand...
Click to collapse
My other suggestion is not to use stock cm.
Sent from my SPH-L900 using XDA Premium 4 mobile app