Develop Bugs

[Q] HELP Unfortunately SuperSu has stopped

I tried rooting to chainfires root process but after doing this 6 times after it boots back i get the message that Unfortunately SuperSu has stopped working and on top of that i keep getting the notification Unauthorized access to a secured area has been blocked. Im not sure if i did something wrong cause i followed his instructions step by step exactly right am i missing something or what is the deal.. please help
update i realize i forgot to say what phone im rooting lol
i have samsung galaxy note 2 with 4.3

I am in the same situation. I was able to root my S4, but I can't get my wife's Note 2 to root. Every issue you have I am having also. Hopefully someone will be able to help us.

critter1332 said:
I tried rooting to chainfires root process but after doing this 6 times after it boots back i get the message that Unfortunately SuperSu has stopped working and on top of that i keep getting the notification Unauthorized access to a secured area has been blocked. Im not sure if i did something wrong cause i followed his instructions step by step exactly right am i missing something or what is the deal.. please help
update i realize i forgot to say what phone im rooting lol
i have samsung galaxy note 2 with 4.3
Click to expand...
Click to collapse
+1.
Frustrated. :banghead:
Any help would be appreciated.
Sent from my SPH-L900 using Tapatalk

chconser said:
+1.
Frustrated. :banghead:
Any help would be appreciated.
Sent from my SPH-L900 using Tapatalk
Click to expand...
Click to collapse
I finally got mine rooted. Do everything in this post. I was able to remove KNOX and finally get my damn phone rooted! This was used to root my wife's Sprint Note 2 with the OTA 4.3 update. here
is the complete thread if you want to see it all. The link I posted first is the 3rd post from that thread.
Doing those steps WILL FIX your issues with not being able to root your Note 2.
I actually boot looped my wife's Note 2 in the process, so if you do brick/boot loop it, then follow these instructions. That put the phone back to the OTA 4.3 stock version. I had to put my wife's SD card into my phone and add the files to her SD card (provided in the link I just posted) to get it to work. Me being an idiot is how I boot looped her phone. This was the ONLY way I could get it to work... and I tried so many methods I found here, youtube, and online.
Good luck gentleman! Let me know if I can help you anymore!

baseband version
i was wondering if the baseband version could have anything to do with it (im still new to rooting) i have L900VPUBMK4 on my phone but when i looked around in other places i noticed people having L900VPAMK4 is there a difference an could this be why mine wont root
i will try your method above an thanks so much for posting this i will let you know of my outcome
oops miss spelled the baseband version i have LP900VPUBK4 but others have L900VPAMK4

tried
smashedixnay said:
I finally got mine rooted. Do everything in this post. I was able to remove KNOX and finally get my damn phone rooted! This was used to root my wife's Sprint Note 2 with the OTA 4.3 update. here
is the complete thread if you want to see it all. The link I posted first is the 3rd post from that thread.
Doing those steps WILL FIX your issues with not being able to root your Note 2.
I actually boot looped my wife's Note 2 in the process, so if you do brick/boot loop it, then follow these instructions. That put the phone back to the OTA 4.3 stock version. I had to put my wife's SD card into my phone and add the files to her SD card (provided in the link I just posted) to get it to work. Me being an idiot is how I boot looped her phone. This was the ONLY way I could get it to work... and I tried so many methods I found here, youtube, and online.
Good luck gentleman! Let me know if I can help you anymore!
Click to expand...
Click to collapse
I tried this but when i did the kingo software it immediately asked me to grant supersu an had a button on bottom of kingo that said ok so i look at my phone but no supersu so i still kept going thru the process an then noticed in kingo where its suppose to say what phone type is connected it says samsung device an from seeing it on other sites of people connecting there devices it had there device names reconised so not sure if its not doing that correctly for my phone or what but after running the software which frozen for awhile when it came to the part that said checking root an then it said waiting for device for awhile an then stopped an said root failed
i cant even get passed step one

I finally rooted my note 2
i tried cf's method an im not sure what went wrong but something did an it wouldnt root so i then tried kingo but at first i noticed that when connecting my note to kingo it just said samsung device it didnt reconize it fully to it saying samsung sphl900 so i knew something wasnt right an then after trying to root it failed so i then noticed that in download mode it said it was customized so i downloaded USER_L900_SPT_MC2_to_MK4_Update_FWD an used odin an then opened the download again on my phone an it finally said samsung official so i then went back to kingo an it did reconize my phone an it did finally root it ,,, im new to rooting an not sure if this will actually help anyone but its what i went thru to get mine rooted an thanks to everyone that has helped me

I was able to fix the same issue...
chconser said:
+1.
Frustrated. :banghead:
Any help would be appreciated.
Sent from my SPH-L900 using Tapatalk
Click to expand...
Click to collapse
I had the same issue and fixed it like this -
1. Installed ES File explorer and open it.
2. Press Menu on the phone and scroll down and turn ON Root Explorer and hit Back.
3. Choose Device from the top menu (dropdown)
4. From the bottom menu, choose search and search for super and you should see superuser.apk.
5. Choose that and install it.
From there you should be able to disable KNOX and open SuperSu

kkgiyer said:
I had the same issue and fixed it like this -
1. Installed ES File explorer and open it.
2. Press Menu on the phone and scroll down and turn ON Root Explorer and hit Back.
3. Choose Device from the top menu (dropdown)
4. From the bottom menu, choose search and search for super and you should see superuser.apk.
5. Choose that and install it.
From there you should be able to disable KNOX and open SuperSu
Click to expand...
Click to collapse
I tried this to no avail, getting error message 'Application not installed'. The thing is, when I go into the Play Store it says SuperSU IS installed but I only have the option to open it. There is no 'update' option available like I keep reading everyone suggests to do to fix this problem. And when I attempt to open SuperSU, I get the error message 'Unfortunately, SuperSU has stopped' followed by the KNOX security notice 'Unauthorized access to a secured area has been blocked'.
Sent from my SPH-L900 using Tapatalk

Ahh
I am having a similar issue

PhonezDoctor said:
I am having a similar issue
Click to expand...
Click to collapse
Same.

Everyone I figured out a simple solution to this. I got my phone back on the 13 from replacement. On the 16 I tried to root for the first time. And KNOX led me into a panic. Reading all the forums and knox blocked every attempt I made, but I neat that ***** into the ground.
1. Get some kind of file Explorer and find the SuperSU apk.
2. ReInstall that bad boy.
3. Immediately after install a message will appear asking if SuperSU can try to disable KNOX.
4. Click it quickly, if you don't knox will try to block it again.
5. You should now have KNOX out of the way. You should now be free to delete that slut!
I chose system app safe remover and searched for all files with KNOX and deleted it. I feel you could probably kill it with any root explorer and know the files you are looking for.
Sent from my SPH-L900 using xda app-developers app

kkgiyer said:
I had the same issue and fixed it like this -
1. Installed ES File explorer and open it.
2. Press Menu on the phone and scroll down and turn ON Root Explorer and hit Back.
3. Choose Device from the top menu (dropdown)
4. From the bottom menu, choose search and search for super and you should see superuser.apk.
5. Choose that and install it.
From there you should be able to disable KNOX and open SuperSu
Click to expand...
Click to collapse
For further clarification, simply clicking on it did not work for me. It gave me an "There is a problem parsing the package."
If you long press on the file then select More from the bottom menu then select Install, it will install properly.
Just wanted to clarify for anybody else who ended up with that issue.

It worked!
kkgiyer said:
I had the same issue and fixed it like this -
1. Installed ES File explorer and open it.
2. Press Menu on the phone and scroll down and turn ON Root Explorer and hit Back.
3. Choose Device from the top menu (dropdown)
4. From the bottom menu, choose search and search for super and you should see superuser.apk.
5. Choose that and install it.
From there you should be able to disable KNOX and open SuperSu
Click to expand...
Click to collapse
This worked for me. Once I reinstalled the SuperUser APK, ES asked for access and everything else fell into place. Thanks!

use esfile to solve it
chconser said:
I tried this to no avail, getting error message 'Application not installed'. The thing is, when I go into the Play Store it says SuperSU IS installed but I only have the option to open it. There is no 'update' option available like I keep reading everyone suggests to do to fix this problem. And when I attempt to open SuperSU, I get the error message 'Unfortunately, SuperSU has stopped' followed by the KNOX security notice 'Unauthorized access to a secured area has been blocked'.
Sent from my SPH-L900 using Tapatalk
Click to expand...
Click to collapse
I got this done by the following:
1. Do exactly as aforementioned instruction, untill you find superuser.apk
2. Hold your finger on that apk icon untill a little squre show up that you can mark it
3. Find "more"(my is at the right lower corner of the screen), choose it and find "install" on your right.
4. Then install.
I dont know why this apk can be installed through es file, basically it still needs to Android to run the installation, yet it works in this way.
have a try and good luck

I keep having to go back into the file explorer and installing it. It will work for a while then out of the blue it pops up and says it has quit. I am very skeptical to try and go through the flash process to install a different ROM. Currently bone stock 4.3 eff bomb. Any suggestions?
JD

Try and use ODIN to flash TWRP then flash @billard412 to get back to MC2 stock, it will remove KNOX and reset flash counters, if any. Then ODIN TWRP again since it will re-install the stock recovery you can then flash the MK4 kernel, WIFI Fix and MK4 ROM of your choice.

flynhawn2002 said:
Try and use ODIN to flash TWRP then flash @billard412 to get back to MC2 stock, it will remove KNOX and reset flash counters, if any. Then ODIN TWRP again since it will re-install the stock recovery you can then flash the MK4 kernel, WIFI Fix and MK4 ROM of your choice.
Click to expand...
Click to collapse
I have warranty bit 1 showing.
JD

jdougs said:
I have warranty bit 1 showing.
JD
Click to expand...
Click to collapse
Ok....since you tripped KNOX you cant get rid of that but its ok if you are not returning your phone (maybe out of warranty?) then just ignore it.
Flash away!

Ya the warranty didn't mean squat...I went ahead and tried the SGS3 JELLYBOMB VER 20.0.0.MD5 and it went with no problems. Haven't got the SuperSU has stopped since flashing. Thanks for the encouragement here. So far so good.
JD

[Q] Troublesome installation of Xposed and GravityBox on Fairphone

Dear internet community,
i would like to adress my problems concerning the installation of Xposed and GravityBox on my Fairphone. You must know that this is my very first smartphone and i dont really know how to use them yet. But i know that i would like to be able to change my Locksreen wallpaper, whích is the only intention for me to try to install Xposed in the first place.
So lets get to the nuts and bolts:
Firstly i tried to "unroot" my phone (of which i dont have any clue what that might mean), but the program i used (universal unroot) gave me this message upon trying: "please allow root access now. If you cant allow root access your device is most likely not rooted". At this point i dont know if i am able to allow root acess to that program, which ist rediculous in itself since this program should allow me to do that in the first place. I checked in the settings but couldnt find anything that looked like root access.
The next step was to install Xposed (version 2.6.1 and then 2.7 both with the same result). After the installation and the reboot, Xposed states unter the "Framework" category that: "the latest version of Xposed is currently not active (my app manager tells me it is). Did you install the framework and reboot?". Again i did the reboot and i installed it. If try to go further into the Framework menu and press the "install/update"-button it tells me: "failed to get root access. make sure your device is rooted properly and you have not blocked shell commands".
My question now is: do you have a solution for my problem? I would be very thankfull and appreciative if you would offer me a solution, since my intentional desire of changing the Lockscreen Wallpaper is such a small thing that it is quite hillaours as to how much effort has to be put in to change this small detail. Please dear community, help me out!
With kind regards
Alex

Hi Alex,
AdmirAlex said:
Firstly i tried to "unroot" my phone (of which i dont have any clue what that might mean), but the program i used (universal unroot) gave me this message upon trying: "please allow root access now. If you cant allow root access your device is most likely not rooted". At this point i dont know if i am able to allow root acess to that program, which ist rediculous in itself since this program should allow me to do that in the first place. I checked in the settings but couldnt find anything that looked like root access.
Click to expand...
Click to collapse
First of all: I see no point in "unrooting" my device. Since you said, you don't have any clue what that might mean, maybe this helps.
The term "root" is comparable to the "admin rights" on your computer. Some people do not need those rights. But If you don't need it just don't use it. If you "unroot" your device, what you do is, you throw away those admin rights. I don't see why you want to do this. The only reason which comes to my mind, is if you want your manufacture to repair your phone using your warranty. They basically don't like it if your phone is rooted, and say it violates the warranty conditions. But then again: fairphone comes pre-rooted, so having root does not void the warranty of your fairphone.
Usually if a program wants to have those root(/admin) rights, a screen pops up where you have to confirm that the app might use those rights.
If you want to know for what root rights can be good for, just google "rooting android" or something like that to read up on that topic.
AdmirAlex said:
The next step was to install Xposed (version 2.6.1 and then 2.7 both with the same result). After the installation and the reboot, Xposed states unter the "Framework" category that: "the latest version of Xposed is currently not active (my app manager tells me it is). Did you install the framework and reboot?". Again i did the reboot and i installed it. If try to go further into the Framework menu and press the "install/update"-button it tells me: "failed to get root access. make sure your device is rooted properly and you have not blocked shell commands".
Click to expand...
Click to collapse
Seems like you are actually unrooted. To use xposed and all its cool modules you need to have root rights. Unrooting your phone to use xposed is just contra productive. Maybe install SuperSU to re-gain root rights. But maybe you need to re-flash your OS.
AdmirAlex said:
My question now is: do you have a solution for my problem? I would be very thankfull and appreciative if you would offer me a solution, since my intentional desire of changing the Lockscreen Wallpaper is such a small thing that it is quite hillaours as to how much effort has to be put in to change this small detail. Please dear community, help me out!
Click to expand...
Click to collapse
Wait, what? Did I understand correctly, that you unrooted your phone to use an app that requires root so that you can change your lockscreen background?
Dude, you can do this in the settings without any root/unroot/xposed stuff.
As you said it is just a small detail, and such a standard feature, so it would be CRAZY if you need to go through such a hassle.
Just go into settings and somewhere in the display or lockscreen settings you can choose a background (you might need to disable the mood background for this). I do not have my fairphone anymore, so I cannot tell you where exactly that option is. Maybe someone else can point to the the exact location of that setting.

Hyst said:
...Maybe someone else can point to the the exact location of that setting.
Click to expand...
Click to collapse
I can't find any option for a different lockscreen image on my FP - only normal background image (wich is then also used for lockscreen, if I have mood background disabled). So I would also suggest GravityBox, which seems to be a too complex topic for your first smartphone ever...

dirtycutmaster said:
I can't find any option for a different lockscreen image on my FP - only normal background image (wich is then also used for lockscreen, if I have mood background disabled). So I would also suggest GravityBox, which seems to be a too complex topic for your first smartphone ever...
Click to expand...
Click to collapse
I know that this option is there. I had a custom lockscreen background (without using some xposed module like gravitybox). I will check with a friend who has a Fairphone, and tell you where the setting is.

I am sorry. Apparently I was mistaken. Changing the lockscreen background to a different wallpaper than the homescreen background seems not to be possible. You can just choose between mood background or not. I thought I had two different backgrounds while I had my Fairphone, but seems like I was wrong. sorry
Why is this not implemented? What I know for sure is that is a feature in CM and and Samsungs stock android version. I do not know about AOSP android.

Thanks for your feedback, Hyst!
I second your question about the missing implementation, but that's quite in a row with some other phone's stock features I am missing on the FP - e.g. a more solid gps, special character search in contacts and some other things other phones can do. Then I remember, Fairphone is still quite new on the market and neither has the experience nor the financial background to act like e.g. Samsung would do. And taken that into account, I'm sure they will grow with the requirements...

Hyst said:
Hi Alex,
First of all: I see no point in "unrooting" my device. Since you said, you don't have any clue what that might mean, maybe this helps.
The term "root" is comparable to the "admin rights" on your computer. Some people do not need those rights. But If you don't need it just don't use it. If you "unroot" your device, what you do is, you throw away those admin rights. I don't see why you want to do this. The only reason which comes to my mind, is if you want your manufacture to repair your phone using your warranty. They basically don't like it if your phone is rooted, and say it violates the warranty conditions. But then again: fairphone comes pre-rooted, so having root does not void the warranty of your fairphone.
Click to expand...
Click to collapse
Yeah i know now why the Phone needs to be rooted in order to work in a way i would like it to.
Seems like you are actually unrooted. To use xposed and all its cool modules you need to have root rights. Unrooting your phone to use xposed is just contra productive. Maybe install SuperSU to re-gain root rights. But maybe you need to re-flash your OS.
Click to expand...
Click to collapse
So atm the only viable solution that i could find is to reflash the Android of my phone. I tried to but the installation progress aborts itself so i am not able to reflash atm. The Fairphone support team got a mail from me, so lets wait and see.
Wait, what? Did I understand correctly, that you unrooted your phone to use an app that requires root so that you can change your lockscreen background?
Dude, you can do this in the settings without any root/unroot/xposed stuff.
As you said it is just a small detail, and such a standard feature, so it would be CRAZY if you need to go through such a hassle.
Click to expand...
Click to collapse
Now in a later post of yours you said that it is not possible. But i qould like to go into why i unrooted my phone. I was watching a Video from this site and misunderstood what has been said. I unrooted my phone, thinking that this would be necessary to make Xposed work. By that time i didnt really know how all of this works. I know its a rookie mistake and a "stupid" one, but i learned something and i am okay with it.
The next task now is to reflash my phone. Maybe you guys have an idea as to why it wont work: I followed the instructions on the Fairphone website and it still aborts during installation.
Edit: I am not allowed to linkt external websites, so i cant give you the video and fairphone installation guide links.
Greetings
Alex

Hope I didn't get it completely wrong but just wanna throw in another idea: why don't you reset your phone to factory settings? Reflashing it sounds like a lot of work for a beginner like you.. (Didn't do it either)
Since the phone is/was rooted from release on, resetting it should do the charme, imo. If you don't have a lot of files to lose I'd try that.
PS: really funny how complicated it got for you since your main intention was to change the lockscreen wallpaper )
PPS: follow this http://forum.xda-developers.com/wiki/Fairphone_Fairphone/Guides#How_to_partition_your_Fairphone from the 4th point on

arghwhymustiregister said:
Hope I didn't get it completely wrong but just wanna throw in another idea: why don't you reset your phone to factory settings? Reflashing it sounds like a lot of work for a beginner like you.. (Didn't do it either)
Since the phone is/was rooted from release on, resetting it should do the charme, imo. If you don't have a lot of files to lose I'd try that.
Click to expand...
Click to collapse
Yeah, i tred that a couple of times, but it wouldnt remove the unroot
PPS: follow this http://forum.xda-developers.com/wiki/Fairphone_Fairphone/Guides#How_to_partition_your_Fairphone from the 4th point on
Click to expand...
Click to collapse
Thanks for the link, i will try that in the meantime
PS: That, unfortunately, didnt do the trick
Edit2:
Since the Fairphone support hasn't replied yet, i tried another solution, but i need to ask you guys for help. I was following the instructions in the Fairphone wiki under the "How to restore Fairphone if you totally bricked it" topic. All the necessary files and programes are downloaded. Now when i choose the scatter file of the fairphone binarys the program gives me this message: "Error initialising scatter file failed. Please check the name of scatter file which you load is legal". if i press the download button the program gives me this message: "Download list is empty, please select a scatter file before executing"
I really dont get this. The fairphone binarys are supposed to work with this program, yet they are not. Can anyone help? Is there something really pbvious i have overlooked?
Greetz
Alex

Bump --> Please help me to figure out the SP Flash tool. To see the details check the post above
Thank you sooo much

AdmirAlex said:
Please help me to figure out the SP Flash tool.
Click to expand...
Click to collapse
I don't think you need to go through that mouch trouble as you're still able to use your phone (if I understood that correctly).
How about re-installing the Fairphone software from recovery? There's a nice guide on how to do that at:
fairphone.zendesk.com/hc/en-us/articles/202478028-Manually-install-Fairphone-OS-software-update-version-Cherry-1-6
Afterwards the superuser binaries should be back and you will have root access again.

haffenloher said:
I don't think you need to go through that mouch trouble as you're still able to use your phone (if I understood that correctly).
How about re-installing the Fairphone software from recovery? There's a nice guide on how to do that at:
fairphone.zendesk.com/hc/en-us/articles/202478028-Manually-install-Fairphone-OS-software-update-version-Cherry-1-6
Afterwards the superuser binaries should be back and you will have root access again.
Click to expand...
Click to collapse
Thanks for the hint, but that exact process does not work, since the update aborts itself giving an error message but not specifiying on which error exactly cause it to abort... I am frustrated at this point.
Greetings
Alex

AdmirAlex said:
Thanks for the hint, but that exact process does not work, since the update aborts itself giving an error message but not specifiying on which error exactly cause it to abort... I am frustrated at this point.
Click to expand...
Click to collapse
Which Fairphone model do you have? If it's the old one (from last year's batch), did you already use the repartitioning tool to "unify" your internal storage? Which update did you try to apply (exact filename)?

haffenloher said:
Which Fairphone model do you have? If it's the old one (from last year's batch), did you already use the repartitioning tool to "unify" your internal storage? Which update did you try to apply (exact filename)?
Click to expand...
Click to collapse
Its the second Batch phone, so the FP1U. I tried it with almost any OS given on the homepage. Those are the ones i tried:
OTA_AOSP-4.2.2_2014-08-05.zip
Fairphone_FP1_OS_v1_6_OTA_2014-07-31.zip
Fairphone_Cherry_1.6_FUSE_Image_2014-07-31.zip
Fairphone_FP1_OS_1G13G_v1_6_OTA_2014-07-31.zip
The Fairphone updater tells me that my phone is running the "Chenpi" version 1.5 which i cannot find on the hompage (thats strange isnt't it?)
What else could be done here?
Greetings and thank you very much for your ideas so far!
Alex

AdmirAlex said:
Fairphone_FP1_OS_v1_6_OTA_2014-07-31.zip
Click to expand...
Click to collapse
Applying that one from recovery clearly should have worked. I've even used it myself with my (already repartitioned) first batch phone.
If you want to be sure the .zip file you downloaded is not corrupted, compute its MD5 checksum. If you're under Windows, use a tool like heise.de/download/md5summer.html
Under Linux, just use md5sum <filename>
The checksum should match the one found on Fairphone's software update page: 664ca09368a4c922a12dc2526afe092b
AdmirAlex said:
The Fairphone updater tells me that my phone is running the "Chenpi" version 1.5 which i cannot find on the hompage (thats strange isnt't it?)
Click to expand...
Click to collapse
1.5 is the version your phone was shipped with, I think. As they issued the update to 1.6 just a few days after the new phones started shipping, I guess they thought putting only the new image up on their website was enough.

haffenloher said:
Applying that one from recovery clearly should have worked. I've even used it myself with my (already repartitioned) first batch phone.
Click to expand...
Click to collapse
The awesome support Team worked something out and my phone is finally rerooted! Now, i have installed Xposed, rebooted it, installed Gravitybox, rebooted it and both programs are working fine. After some fiddling around it finally has worked!! For most of you it might seem to be a small thing and really not that important, but for me it is. Honestly the only two things i really use to personalize the phone is the Wallpaper / Lockscreen and the WakeupCall ringtone.
Thank you so much for all of your support and patience!
Greetings
Alex

New update?

Is anyone else getting prompted for a system update? I'm rooted so I don't want to install. Update is 154.6 MB.
UPDATE: DO NOT install the update if you don't have stock recovery. You will end up in a boot loop.
Sent from my LG-D851 using XDA Free mobile app

Lol I just created a thread myself! I am rooted and custom rom so I am totally waiting.

i just got it too, it said android update but I'm not entirely sure what it's for

InsaneJester17 said:
Is anyone else getting prompted for a system update? I'm rooted so I don't want to install. Update is 154.6 MB.
Sent from my LG-D851 using XDA Free mobile app
Click to expand...
Click to collapse
I also did, I am on sky rom and it probably won't work, but I don't want to try to install it.

Well its quite a small update at 154 mb

Installed update
Hey guys I just installed the update and it broke my root :cyclops:

Were you able to root again?

Apparently it's D85110m update. So it's updating from D85110c to m. The person that I saw that updated hadn't rooted so no clue on the rooting thing.

Count me in the group with system update notification. I got rid of it by installing xposed module GravityBox, going under status bar settings - ongoing notification blocker - Google Play services (picture looks like that of update) - reboot.
I don't know what other notifications this may block, but for now, it gets rid of that. Also of note, I would NOT take the OTA. Usually it breaks root and/or bootloops you.

HELP
So in my half awake brilliance, I installed the update. My phone is now boot cycling to the TWRP recovery. Any ideas?

zcgofaster said:
Were you able to root again?
Click to expand...
Click to collapse
I haven't tried to re-root yet. I was rooted with stump root earlier. Stump root doesn't work again because it thinks that my phone is already rooted. I'm going to do some light battery tests before trying to root again, this time with purple drake.

Maybe i might restore the slimkat alpha and hide there until this gets sorted out

I decided not to update to fear my bootloader/root so I tried to extract this with file manager and kept crashing. I can only post the name of the file but above users are correct contains 10m from 10c hopefully devs can find out exactly what's in the update. b1847cae892006ffa11c6822a408fe8528142a54.D85110c_00-D85110m_00_update.zip

thiefinthenight said:
So in my half awake brilliance, I installed the update. My phone is now boot cycling to the TWRP recovery. Any ideas?
Click to expand...
Click to collapse
I would try and follow this guide:
http://forum.xda-developers.com/showthread.php?t=2818667

Wonder if i could do a restore and keep wifi off so it won't download

hawkstwelve said:
I would try and follow this guide:
http://forum.xda-developers.com/showthread.php?t=2818667
Click to expand...
Click to collapse
Will this reset the phone? Will I lose all data?

thiefinthenight said:
Will this reset the phone? Will I lose all data?
Click to expand...
Click to collapse
I believe so yes. But if you are truly bootlooping, I don't believe you have many (if any) other choices than wiping clean and starting fresh.

I'm all stock so I upgraded.
It is in fact D85110m
I've only had it up and running for a few minutes and I already noticed two things.
- There is a slider feature added to the lock screen to instantly open the camera.
- I didn't think the phone was sluggish or laggy out of the box but I immediately could tell it runs smoother now with transitions between screens/apps. e.g. There used to be a bit of lag when opening the Recent Apps. Not anymore.
We'll see how it goes.

The IR blaster works better for me now. I guess the update made it more powerful somehow.

if you have twrp installed or have modified /system you should not take this OTA. if on twrp things will get weird(as evidenced above..) and if removing/modding any default files in /system the zip will most likely fail.. as it checks for all original files first before the OTA update gets patched in.
as for the twrp issue.. I can only assume that it's due to the update/phone expecting stock recovery... and not getting it. there are flags set in the phone that tell the phone what mode to boot into... since you dont have stock recovery the phone is confused. check out this thread - http://forum.xda-developers.com/showthread.php?t=2451696
the fota and misc partitions are tied to this... try to zero out fota first. if that alone doesnt let you out of twrp... you may need to wipe misc. be sure to backup any partition to computer(dont just save on phone sdcard.. never know when it could get wiped..) before erasing anything.
as for this update(10m)... anyone taking it should be careful that the bootloader/downgrades have not been locked/blocked. I'll be waiting for others to take that risk first before even considering taking the ota.
*update* can confirm update is safe.. bootloader is not locked.. still rootable.
as for root... I doubt purple drake is blocked.. but is possible. I'm very sure Stump is still available as an option(tho app may need update).
if you got the update and dont want to take it.. and want the notification gone you should be able to use a file explorer to delete the update zip from the the /cache directory... as well as rename the LGFOTA.apk file in /system to LGFOTA.apk.bak.
I can also confirm that disabling OTA updates in the hidden menu works. the moment I set it back to "on" (i set mine to off day 1) and rebooted the update came in.
d851 hidden menu > wlan test > ota setting > off > reboot (if you have been notified of an available update do NOT reboot until you have deleted the ota zip first)

[Q] Recent SuperSU Updates - Issues

Figured I would start here in my device thread before trying the SuperSU thread.
Anybody have issues with SuperSU since the last few updates ago?
SuperSU does not even open. Root-dependent apps do not open. Titanium sits there at the initial screen "asking for root rights" until I kill the app. AdAway does not open... just goes right to a black screen until I kill the app. AdAway seems to work though, as my web surfing does not have ads.
I've also tried manually going in and applying the latest update via (philz) recovery.
Would I be safe to roll back to an older version of SuperSU?
Mods... if you're going to gun the thread, please at least point me in the right direction as I did search, but did not find anything related to recent issues on the Note 2 for SuperSU.
TIA for help and suggestions.

Oh yeah its still sitting in the play store. I lost root the last couple updates ago. I had to re flash my rom and start over.

ceabbott2 said:
Oh yeah its still sitting in the play store. I lost root the last couple updates ago. I had to re flash my rom and start over.
Click to expand...
Click to collapse
As part of my search, I did see Chainfire mention in his "fix" thread that some apps like wanam can cause issues. Of course, I have xsposed installed, so that could be the issue.
Do you (or did you) also have xsposed installed as well?
I have tried older versions of SU, uninstalling via philz then redownloading from Play - which now tells me the binaries are out of date and can't be done by SU, and I need to re-root.
Think I might try one of the other SuperUser apps "just to see how it works", or if it does.

lennykravitz2004 said:
As part of my search, I did see Chainfire mention in his "fix" thread that some apps like wanam can cause issues. Of course, I have xsposed installed, so that could be the issue.
Do you (or did you) also have xsposed installed as well?
I have tried older versions of SU, uninstalling via philz then redownloading from Play - which now tells me the binaries are out of date and can't be done by SU, and I need to re-root.
Think I might try one of the other SuperUser apps "just to see how it works", or if it does.
Click to expand...
Click to collapse
For me, I just reflashed the ROM I was running at the time and that resolved it. Of course seeing that the update was " fixed" I attempted it and lost root again. I then did the same as before, wiped and relashed. I didn't do clean installs either time. Just wiped caches and reflashed. That sucks if you have to re-root. I mean, it's easy and all but it shouldn't have to be done.
D

Before attempting any drastic measures (i.e., full wipe and reinstallation of the ROM), try this. This trick usually works for me.
Open your Application Manager, and locate your SuperSU application. Turn it off (i.e., click the "Turn Off" button). It may prompt you that updates are about to be uninstalled; that's ok. Download "BETA-SuperSU-v2.25.zip" and verify the MD5. Reboot into recovery and flash this file. Reboot and re-enable the SuperSU application from the Application Manager (it will be easy to find this time - scroll all the way over to the right, under "Turned Off"). Open SuperSU and it should let you reinstall the binaries.
Recently I've inexplicably lost root a number of times, and the above method has fixed it for me every time.

DJ_Barcode said:
Before attempting any drastic measures (i.e., full wipe and reinstallation of the ROM), try this. This trick usually works for me.
Open your Application Manager, and locate your SuperSU application. Turn it off (i.e., click the "Turn Off" button). It may prompt you that updates are about to be uninstalled; that's ok. Download "BETA-SuperSU-v2.25.zip" and verify the MD5. Reboot into recovery and flash this file. Reboot and re-enable the SuperSU application from the Application Manager (it will be easy to find this time - scroll all the way over to the right, under "Turned Off"). Open SuperSU and it should let you reinstall the binaries.
Recently I've inexplicably lost root a number of times, and the above method has fixed it for me every time.
Click to expand...
Click to collapse
Thanks for the try. Did not work though.
Looks like I just need to re-flash the ROM.

My problem was odd. Before I discovered the aforementioned trick, I'd re-root with Chainfire or Kingo. I'd reboot, and my device would be rooted. But those two methods have an additional payload - they flash the stock recovery. So I'd ODIN the Philz Touch recovery back to the device, reboot, and root would be gone. Never figured out what was going on.

Yup. Issues with new version. Only last 2 or three updates.
They seemed to be perfectly fine with cm12 though.
Sent from my SPH-L900 using XDA Free mobile app

Thanks for all of the input.
After doing a full wipe, and then re-loading Classic Stock 4.4.2, life is good again! Back to running awesome for a few weeks now.
Having said that, I did want to follow-up and ask others what current version of SuperSU you are on. As of right now, I am still on v2.01 (which is what was packaged with the ROM) and have not updated yet. Only other versions of SuperSU I have zips downloaded for are: 2.25 from post above, 2.36, and 2.37.
Any suggestions or confirmations on which newer/more recent versions will not bork my root status? Or which versions to definitely stay away from trying to use?
Thanks, and I appreciate any help and suggestions!

lennykravitz2004 said:
Thanks for all of the input.
After doing a full wipe, and then re-loading Classic Stock 4.4.2, life is good again! Back to running awesome for a few weeks now.
Having said that, I did want to follow-up and ask others what current version of SuperSU you are on. As of right now, I am still on v2.01 (which is what was packaged with the ROM) and have not updated yet. Only other versions of SuperSU I have zips downloaded for are: 2.25 from post above, 2.36, and 2.37.
Any suggestions or confirmations on which newer/more recent versions will not bork my root status? Or which versions to definitely stay away from trying to use?
Thanks, and I appreciate any help and suggestions!
Click to expand...
Click to collapse
The actual issue is not superuser or the updates. The issue is 4.4.2 and the original way we (ROM devs) had to implement superuser.
There are two routes to take to keep from losing root. The easiest for most users is to turn off auto updates and not to update superuser (app or binaries). The second is more difficult for the average user. Do a complete removal of superuser and install the latest.
I suggest the first way for everyone. It is simple and fool proof.
Sent from my XT1045 using XDA Free mobile app

jlmancuso said:
The actual issue is not superuser or the updates. The issue is 4.4.2 and the original way we (ROM devs) had to implement superuser.
There are two routes to take to keep from losing root. The easiest for most users is to turn off auto updates and not to update superuser (app or binaries). The second is more difficult for the average user. Do a complete removal of superuser and install the latest.
I suggest the first way for everyone. It is simple and fool proof.
Sent from my XT1045 using XDA Free mobile app
Click to expand...
Click to collapse
As always, thanks for your response. Your recommendation is what I've been doing, just wanted to follow-up on this and see if there was anything else I needed to consider or change as well.
My main concern was to make sure I was not going to run into any "big" issues (especially security) by staying on current version. Thanks for explaining where the issue really lies on this too. I'm obviously not a dev, however I do want to understand what is exactly going on and responses like yours always provide that type of info. :good: Thank you.
And, FWIW, using "fool proof" to describe a process only makes me more curious (and no, not in that way) about your suggestion. :laugh:
Now I HAVE to find out more about that option... (only after some of the best BBQ in all of the land - Sugarfire BBQ in STL )

jlmancuso said:
The actual issue is not superuser or the updates. The issue is 4.4.2 and the original way we (ROM devs) had to implement superuser.
There are two routes to take to keep from losing root. The easiest for most users is to turn off auto updates and not to update superuser (app or binaries). The second is more difficult for the average user. Do a complete removal of superuser and install the latest.
I suggest the first way for everyone. It is simple and fool proof.
Sent from my XT1045 using XDA Free mobile app
Click to expand...
Click to collapse
How do you disable auto update of binary on SuperSU? I keep seeing it in the notification bar, very annoying.

Stock Lollipoop rooted with SuperSU - but it keeps resetting everything I do

see #5 for problem
Hi guys,
so after quite some time with custom Roms I decided to go stock again as somehow I don't need root at all. Well, that's not true. I miss AdAway.
As there is no possibility to root the stock rom, is there ANY AdBlocker that works on Lollipop? AdBlock Plus doesn't (yet).

Why did you say there is no possibility to root the stock rom ?
I'm running Stock ROM, rooted and AdAway running fine.

ckpv5 said:
Why did you say there is no possibility to root the stock rom ?
I'm running Stock ROM, rooted and AdAway running fine.
Click to expand...
Click to collapse
How do you root the stock rom? I couldn't find out how.
Can I root without losing my data?

fBx said:
How do you root the stock rom? I couldn't find out how.
Can I root without losing my data?
Click to expand...
Click to collapse
Flash twrp recovery and root through the recovery. It'll ask you when you reboot the system if you want to root it
Sent from my HTC One_M8 using XDA Free mobile app

Huh. Didn't know it was THAT straightforward and I've been flashing my phones for years.
Well. I flashed TWRP and SuperSU 2.46, succeeded. But Adaway and Adfree don't work correctly. They block the ads but only until you reboot, then it's reverted, kinda like with a tethered jailbreak on iPhones.
What am I doing wrong here? Also the block is not like on KitKat - there it was really blocked, really removed, here only the images of the ads are removed but you still see the space they were supposed to be.
I also used a system app removal tool that also didn't work although it shows success. It just removes the installed data like updates.
When I delete apps manually via ES Explorer, they just reappear at the next reboot.
Root Checker says root is fine but it isn't supposed to behave like that and undo my changes.
What's wrong? Do I need another kernel maybe? As I said I went back to stock completely and updatet through to L.

I believe I got whats causing the issue.
After deleting a system app and rebooting, I got a message saying that the phone was restored from an "unnormal behaviour". Does Lollipop bring some kind of system restore point that just automatically restores itself when "weird" things like host file alteration happens? If yes, how do I get rid of that?

This phone has always had system files protected since KitKat. You need a kernel mod to delete system apps.
Don't know why the ad blockers aren't working. Adaway is working fine for me on stock US Dev Edition rooted. You said you are using Adaway and AdFree? Are you actually using both at the same time? maybe they are interfering with each other?

No I meant it happens with both. Only use adaway now. They work but after a reboot the adblock is gone and I need to apply it again. In fact, AdAway says it's deactivated and AdFree says it's already up to date but ads show anyway and I need to install the fix again to get rid of them.
Can you maybe point me to a kernel mod? Would want to get rid of some bloatware.
Maybe I should try installing xposed and see if it's gone after a reboot.

fBx said:
Can you maybe point me to a kernel mod? Would want to get rid of some bloatware.
Click to expand...
Click to collapse
The thread is here: http://forum.xda-developers.com/showthread.php?t=2701816
But unfortunately, flar2 hasn't had the time to update for LP. A user posted the kernel module in Post #210, but a subsequent user said it doesn't work. Custom ROMs have write protection disabled, as does Dev Edition stock ROM.
fBx said:
No I meant it happens with both. Only use adaway now. They work but after a reboot the adblock is gone and I need to apply it again. In fact, AdAway says it's deactivated and AdFree says it's already up to date but ads show anyway and I need to install the fix again to get rid of them.
Click to expand...
Click to collapse
Odd, as mentioned, I've used AdAway for quite some time now, and don't have these issues.

Yes, very odd indeed. Well, if I don't get it sorted out somehow I might as well switch to Viper or some other close to stock custom Rom again, or make it Dev like you.

Things are getting worse, in 1 of 2 cases AdAway spits an error at me when trying to apply the fixes and the phone just reboots and undos everything. It's like some protection from rooting or changing anything although I am rooted. I don't understand it. I can't possibly be the only one having problems with root on Stock Lollipop
This is really annoying me. I think I'm better of just installing a custom rom and setting the phone up again, will cost me an hour but at least I'm done with the bugs.

Yup, decided to jump the gun, wipe and install ViperOne and now everything works as I wanted it to. AdAway stays active and working.

fBx said:
Yup, decided to jump the gun, wipe and install ViperOne and now everything works as I wanted it to. AdAway stays active and working.
Click to expand...
Click to collapse
Interesting. I wonder if Adaway is dependent on the system write protection being disabled. I wouldn't normally suspect that, and only thinking of it since you mentioned the system write protection issue as well.
On the other hand, its the only difference I can think of between my phone and yours that would matter. I am on stock rooted Dev Edition, which apparently does not have the system write protection enabled by default.

redpoint73 said:
Interesting. I wonder if Adaway is dependent on the system write protection being disabled. I wouldn't normally suspect that, and only thinking of it since you mentioned the system write protection issue as well.
On the other hand, its the only difference I can think of between my phone and yours that would matter. I am on stock rooted Dev Edition, which apparently does not have the system write protection enabled by default.
Click to expand...
Click to collapse
I also assume that's the reason. I've never been on a stock rom since I don't know when, but figured that actually I only wanted AdAway which would normally not require a custom rom per se... but as it didn't really work in the end (and also other root-requiring stuff), I went back to custom again. Well, it's not that it's that difficult to wipe the phone occasionally and set up a clean custom rom to get it back to perfect performance. Gonna go with it.