Develop Bugs

Root Access Possibly Lost Fix Root?

I have my N7 on bone stock, rooted with superSU 1.60 installed. I flashed the .zip made by Chainfire, and no matter the recovery CWM non-touch , CWM, or TWRP after making a backup , I hit reboot system, and I get this message every time.
Root Access Possibly Lost Fix?
THIS CANNOT BE UNDONE
1. YES fix root (/system/xbin/su)
2. NO do not fix
I've selecting option 1 multiple times and I still get the same message after a backup ,and before rebooting!! Root access works fine on all my apps and everything else I'm just curious as to why I'm seeing this via any recovery thanks. I'm sure its silly and an easy fix.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Try v1.55
http://download.chainfire.eu/346/SuperSU/UPDATE-SuperSU-v1.55.zip

Disabled auto-update SuperSU in the playstore , flashed v1.55 ,and problem solved . Thank You!
Sent from my Nexus 7 using XDA Premium 4 mobile app

I tried the latest version today, and It seems as though the problem still exists in SuperSU v1.65. I just flashed back to v1.55
Sent from my Nexus 7 using XDA Premium 4 mobile app

Jewveeski said:
Disabled auto-update SuperSU in the playstore , flashed v1.55 ,and problem solved . Thank You!
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've done this, i disable auto-update, flashed the v1.55 in CWM and rebooted. Now i cant use SuperSU anymore? tells me i have to update binaries. And i know that if i do the "root access possbibly lost" error comes again? any solutions?

In settings there is an option for reinstall as seen in the pic below click that then reboot your device , then reboot to recovery flash version v1.55 and make sure you still have the auto update feature in the play store unchecked. See if that works.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Same issue on a Galaxy Nexus running 4.3 stock rooted... SU requires an update and then the recovery thinks root has been lost (this is not actually the case)... any ideas?

lost root and twrp
so i first discovered i lost root when it said no binary found then when i was going into twrp to reflash the zip all i get is a dead android on its back with a red triangle hovering over it. Went back into adb and flash recovery twrp.img and it says successful but i still get the same thing. any one know the correct thread to point me to? ive looked but cant find this problem. my device boots fine and i can get to the boot loader just not recovery.

Same thing happens with my Nexus 4, I always hit No because it says root may have been lost even if I just enter CWM without flashing any rom or doing any action but rebooting to system

Jewveeski said:
I tried the latest version today, and It seems as though the problem still exists in SuperSU v1.65. I just flashed back to v1.55
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Same message on my SGS4 with stock Android 4.3 and SuperSU v1.80.

Same message with my GT-i9300, CWM 6.0.4.4 Touch (i've tried also with CWM 6.0.4.3 NO Touch) and SuperSU v.1.80

I have the same problem too on my Galaxy Nexus GSM 4.3 build JWR66Y with SuperSu by Chainfire v1.8.6 and CWM Touch Recovery v6.0.4.3
Is there a solution?
Thanks in advance
Happy Holidays and Merry Christmas

Same message, S4 mini GT-I9195 4.3 su 1.86

Same message here...
I am running CM 10.2 with CWM Touch and SuperSUv1.86
Is this a big problem?
I think CWM should work just fine regardless of this message right?
If anyone has truly found a "recent" fix please let us know.
Oh i tried reinstalling CWM Touch and that did not fix the problem..
Thank you all for your time and assistance.

Same, CM10.2 cwm, SuperSU 1.86, S4 MINI, GT-I9195, never got this message with CM10.1.3, nor with any other 4.2 ROM. I think it's a 4.3 issue not just with CM, I tried 2 other 4.3.1 ROMs, they all said the same thing, yrs the device still works fine when selecting "yes fix root"
My concern is to WHY does this message appear?? And it's there a way to fix this permanently?
Sent from my GT-I9195

kamikaze702k said:
Same, CM10.2 cwm, SuperSU 1.86, S4 MINI, GT-I9195, never got this message with CM10.1.3, nor with any other 4.2 ROM. I think it's a 4.3 issue not just with CM, I tried 2 other 4.3.1 ROMs, they all said the same thing, yrs the device still works fine when selecting "yes fix root"
My concern is to WHY does this message appear?? And it's there a way to fix this permanently?
Sent from my GT-I9195
Click to expand...
Click to collapse
I figured that my device was okay, I mean root still worked just fine.
I bet it has to do with SELinux...
Thanks for the response. I also would love to find a way to fix this permanently. I just did a ROM backup with CWM Touch and I didn't have any issues so this just must be some warning message that doesn't affect anything. Was a bit scary though...
Hopefully someone will find a universal fix soon...
-droidshadow

droidshadow said:
I figured that my device was okay, I mean root still worked just fine.
I bet it has to do with SELinux...
Thanks for the response. I also would love to find a way to fix this permanently. I just did a ROM backup with CWM Touch and I didn't have any issues so this just must be some warning message that doesn't affect anything. Was a bit scary though...
Hopefully someone will find a universal fix soon...
-droidshadow
Click to expand...
Click to collapse
See, I did a rom backup also with rom manager, after the backup was complete the message still appears, it's more scary if your using a custom recovery because officially my device isn't on rom managers list of supported devices. Hopefully we can get a fix for this.
I'm sure we will it's only a matter of time I guess, I've flashed 4 roms in 3 days just to check the roms and this message came upon after installing 3. However it didn't appear with 4.2.2 so it has to be something with 4.3.x roms
Sent from my GT-I9195

maybe we should switch to TWRP?...
kamikaze702k said:
See, I did a rom backup also with rom manager, after the backup was complete the message still appears, it's more scary if your using a custom recovery because officially my device isn't on rom managers list of supported devices. Hopefully we can get a fix for this.
I'm sure we will it's only a matter of time I guess, I've flashed 4 roms in 3 days just to check the roms and this message came upon after installing 3. However it didn't appear with 4.2.2 so it has to be something with 4.3.x roms
Sent from my GT-I9195
Click to expand...
Click to collapse
Has anyone gotten this message with TWRP Recovery Manager? I am thinking that this might only be a problem with ROM's running Android 4.3+ with CWM Recovery Manager.
I have a Nexus 7 2013 tablet which runs like 3 different KitKat ROM's and one JB ROM (4.3.1) and I have never gotten a message like that on TWRP.
Maybe we should just switch to TWRP until CWM works this out or unless someone comes up with a permanent solution...
-droidshadow

droidshadow said:
Has anyone gotten this message with TWRP Recovery Manager? I am thinking that this might only be a problem with ROM's running Android 4.3+ with CWM Recovery Manager.
I have a Nexus 7 2013 tablet which runs like 3 different KitKat ROM's and one JB ROM (4.3.1) and I have never gotten a message like that on TWRP.
Maybe we should just switch to TWRP until CWM works this out or unless someone comes up with a permanent solution...
-droidshadow
Click to expand...
Click to collapse
Your right, my other device I'm using TWRP recovery and few days ago I installed a 4.3 liquid smooth ROM and never got this message!
It's an issue with CWM combined with 4.3 ROMS from what I've tested.
I only thought it was happening on my GT-I9195 because i was using a custom based CWM recovery, but now I know it's across most devices this message is occurring
Sent from my GT-I9195

TWRP is the way to go!
kamikaze702k said:
Your right, my other device I'm using TWRP recovery and few days ago I installed a 4.3 liquid smooth ROM and never got this message!
It's an issue with CWM combined with 4.3 ROMS from what I've tested.
I only thought it was happening on my GT-I9195 because i was using a custom based CWM recovery, but now I know it's across most devices this message is occurring
Sent from my GT-I9195
Click to expand...
Click to collapse
So i just switched my Verizon SGS3 (d2vzw) from CWM Touch to TWRP Touch 2.6.31 and i go to error message/warning about the SU binary being corrupted. This seems to be just an isolated incident with CWM and Android ROM's running 4.3+
With all of the work I have been doing with my Nexus 7 FLO + TWRP Recovery I decided to go ahead and switch my phone to TWRP. It was kind of hard to switch because I started out with CWM but I have just quickly become such a fan of TWRP.
If you don't want to wait for CWM to fix this issue which i am sure they will in their next update try out TWRP i think you will like it!
If you want an easy way to install TWRP recovery manager use the app "GooManager" from the Google Play store and use the your menu button on your phone and choose the open install open recovery script.
Or you could just as easily download the recovery image file from the official TWRP website and flash it with the app flashify.
Don't you just love technology!?
-droidshadow

PA 3.99 Not Working on TMo Note 2 Help!

I am able to flash the rom successfully using CWM Recovery, but when the Rom starts up, it does not recognize any network or mobile data. I have flashed back to stock TW Rom, and it all works fine. I would love to give this rom a shot, but I would rather be able to use my phone. Please let me know how to get service and mobile data using this rom on my TMo SGH-T889 (Galaxy Note II). Thanks!

Nolan22 said:
I am able to flash the rom successfully using CWM Recovery, but when the Rom starts up, it does not recognize any network or mobile data. I have flashed back to stock TW Rom, and it all works fine. I would love to give this rom a shot, but I would rather be able to use my phone. Please let me know how to get service and mobile data using this rom on my TMo SGH-T889 (Galaxy Note II). Thanks!
Click to expand...
Click to collapse
Switch to TWRP recovery

Anu6is said:
Switch to TWRP recovery
Click to expand...
Click to collapse
Thanks for the reply! Why will TWRP allow me to use paranoid android?

Nolan22 said:
Thanks for the reply! Why will TWRP allow me to use paranoid android?
Click to expand...
Click to collapse
As far as i've seen from other posts, some versions of CWM cause issues with the baseband when flashing ROMs
TWRP does not have this issue.

Anu6is said:
As far as i've seen from other posts, some versions of CWM cause issues with the baseband when flashing ROMs
TWRP does not have this issue.
Click to expand...
Click to collapse
After installing TWRP on my TMo Note 2, I flashed PA 3.99 + GApps and it seems like everything is working fine. I have data and phone connectivity!
Since Paranoid Android was not working with CWM, does that mean that there might be certain ROMs that will not work with TWRP?

Nolan22 said:
After installing TWRP on my TMo Note 2, I flashed PA 3.99 + GApps and it seems like everything is working fine. I have data and phone connectivity!
Since Paranoid Android was not working with CWM, does that mean that there might be certain ROMs that will not work with TWRP?
Click to expand...
Click to collapse
I've not heard of any problems with TWRP (that does not mean they don't exist), also the issue with CWM only seemed to appear after a certain update (can't recall the number). Older version work without issue.

So I guess I spoke a little too soon. I was able to get data and cell connectivity, but it only lasted a couple hours and then disconnected. Any idea what is happening?
Sent from my SGH-T889 using xda app-developers app

Nolan22 said:
So I guess I spoke a little too soon. I was able to get data and cell connectivity, but it only lasted a couple hours and then disconnected. Any idea what is happening?
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Try the note2 thread...it could be a device specific issue.

Boot Loop after trying to Flash Cyanogenmod 11 through AutoRec?

Hello,
I am very new to rooting, and just rooted my Sprint LG G2 with 4.4.2 KitKat through IORoot 25 and then used AutoRec as my TWRP. I then downloaded Cyanogenmod11 from its website onto my phone, and tried to flash install it through AutoRec. However, when I try to install the CM11 ROM, I get the "MD5 not found" message, and when I try to reboot after this, my phone goes into what I think is Bootloop (the LG home screen continuously turns on for a couple seconds, then stops for a split second, and then turns back on for a couple seconds). Fortunately, I am was able to hard restart my phone by holding Power and Volume Up together while this screen is on, and I was able to restore my phone with the backup I made, and my phone is now working fine with the stock ROM. Has anyone else had this problem before, and if so is there a better way for my to install custom ROM, and/or fix that MD5 message? Does anyone know what that MD5 message means?
One other note, I have been doing some reading and I currently have ZVC radio. I'm not sure what this means exactly, but would this make a difference?
Thanks!

If you are on 4.4.2 cm won't work on that version yet
Sent from my LG-LS980 using XDA Premium 4 mobile app

secret.animal said:
If you are on 4.4.2 cm won't work on that version yet
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Interesting, thanks. Are there any ROMs that work for 4.4.2 that people have been using, or am I pretty much stuck with the stock ROM until CM is updated?

Cloudyfa has some in the G2 android development forum. There are some others that will work with sprint.
http://forum.xda-developers.com/showthread.php?t=2687613
[INDEX][REPO][AIO] LG G2 - ROMs | Kernels | MODs | Recoveries [UPDATED][9 June 14]
Has some info in it also
Sent from my Nexus 7 using Tapatalk

secret.animal said:
If you are on 4.4.2 cm won't work on that version yet
Click to expand...
Click to collapse
Hi, would you mind explaining further why it wont work, coz i have the exact problem that LGGuy83 is/was experiencing (i used autorec too and cm11 gives me an lg logo boot loop) and this is the closest thread to getting an answer

What radio are you on? Zv8 radio is required.
Sent from my AOSP on Grouper using Tapatalk

secret.animal said:
What radio are you on? Zv8 radio is required.
Sent from my AOSP on Grouper using Tapatalk
Click to expand...
Click to collapse
thanks for ur reply,
Im not sure what "radio" version, but i know its updated to VS980-26A
anyway i sorted the problem by using the cm11 version on this link
http://forum.xda-developers.com/showthread.php?t=2702958
i simply downloaded the one here and installed, (skipped all the steps and just put it in the internal memory and flashed it)
Now its working well. ill let you know if any problems arise.

Recovery issues.Cwm and philz work. Twrp bootloops

Just was wondering if anyone has run into this issue. I have tried flashing zips Odin and apps to install recoveries. Any version of TWRP I install will just put the phone in bootloop til I Odin a diff recovery. I have tried googling around and only thing I could get is maybe my motherboard going out. I know when I was on Whomp 4.1.2 I had always used twrp before 4.3 came out. I still have no Knox boot loader and never have had Knox on phone either. Could this just be a sign that I have corrupt memory sectors ? Any help or tips appreciated. Just trying to get phone to last til note 4. Other things I've done is even unmod back to old firmware and let it ota all the way to mc2 so I don't get a knox boatloader. Thanks again

Shadowpaw said:
Just was wondering if anyone has run into this issue. I have tried flashing zips Odin and apps to install recoveries. Any version of TWRP I install will just put the phone in bootloop til I Odin a diff recovery. I have tried googling around and only thing I could get is maybe my motherboard going out. I know when I was on Whomp 4.1.2 I had always used twrp before 4.3 came out. I still have no Knox boot loader and never have had Knox on phone either. Could this just be a sign that I have corrupt memory sectors ? Any help or tips appreciated. Just trying to get phone to last til note 4. Other things I've done is even unmod back to old firmware and let it ota all the way to mc2 so I don't get a knox boatloader. Thanks again
Click to expand...
Click to collapse
If you want twrp you need one of the versions before 2.7. Thing is twrp does not handle selinux context so it wont work on tw 4.3-4.4.3 and aosp 4.4.+.
I would suggest philz 6.07.9 it handles everything perfectly. So give it a shot and still have problems let me know.
Sent from my GT-N7105 using XDA Premium 4 mobile app

jlmancuso said:
If you want twrp you need one of the versions before 2.7. Thing is twrp does not handle selinux context so it wont work on tw 4.3-4.4.3 and aosp 4.4.+.
I would suggest philz 6.07.9 it handles everything perfectly. So give it a shot and still have problems let me know.
Sent from my GT-N7105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've read doesn't work on new versions but I 1st had the issue start months ago on 4.1.2 whomp I rebooted to recovery one day after on same ROM over 2 months not a issue and boot loops started then and haven't been able to use twrp since. Last night I finally wanted to try a 4.4 ROM and thats why I just now was posting about it. I'm on philz currently. I'll just stick with what works. Thanks again!
Sent from my SPH-L900 using XDA Premium 4 mobile app

Shadowpaw said:
I've read doesn't work on new versions but I 1st had the issue start months ago on 4.1.2 whomp I rebooted to recovery one day after on same ROM over 2 months not a issue and boot loops started then and haven't been able to use twrp since. Last night I finally wanted to try a 4.4 ROM and thats why I just now was posting about it. I'm on philz currently. I'll just stick with what works. Thanks again!
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
In case you dont already know philz can use you old twrp backups also.
Sent from my GT-N7105 using XDA Premium 4 mobile app

Xposed Framework question

So I am trying to figure out among the many threads how to get Xposed Framework on my LG G3. When I first got the phone I realized it was being worked on and now I decided to see what's been going on and realized all the threads. I've rooted my phone using this method, http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197, I have tried the one method of getting TWRP on my phone one of those one click apps and it bricked my phone so now I'm back to stock and rooted. Currently my software info is as follows, Android 5.0.1, Build number LRX21Y, Software version D85021q. Could someone just send me the proper links that won't cause a brick again? Thank you. What happened to the good old days of just installing the Xposed APK on a rooted device?!!

For lollipop we have always needed to flash via recovery.
Use flashify to install twrp
Sent from my Venue 8 7840 using Tapatalk

dcooterfrog said:
For lollipop we have always needed to flash via recovery.
Use flashify to install twrp
Sent from my Venue 8 7840 using Tapatalk
Click to expand...
Click to collapse
Thanks I'll give it a try. Kitkat was easier with it, that's what I'm saying. I miss when it was as easy as it was to install on kitkat, Thanks again!

Since updating to v21a trying to install exposed just leaves my phone stuck on the splash screen. Uninstalling it with the zip file restores my phone to working order. Has anyone else experienced this and know of a fix?
Sent from my LG-D855 using XDA Forums