Last night I installed SuperSU on my Nexus.. it's awesome but I'm having issues with some apps. Though 98% of them are still recognized from before I installed SuperSU couple are now not compatible.
Anyone else run into this issue?
Sent from my Nexus 7 using xda app-developers app
What does not compatible mean. SuperSu doesn't recognize some app's or won't grant them 'root'? Are the app's in SuperSu but won't complete root actions?
Iffn it was me I would tell SuperSu to forget all app's. Then wipe data in manage app's in setting. Then uninstall and reinstall SuperSu. Of course you will lose your 'remembered' app's but I can't see that being a very big deal.
Sent from my Nexus 7 using xda premium
I'm not trying to root this app, I had it installed on my tablet prior to SuperSU but now it says "your device is not compatible with this version"
Sent from my Nexus 7 using xda app-developers app
Related
My nexus 7 is rooted. Is that why it can't accept the 4.1.2 update? What should I do? It keeps reminding me to install the update every 15 minutes. When I try to, it just crashes.
Sent from my Nexus 7 using xda app-developers app
You want to eat from two tables ... ? It's your choice, original or rooted ...
Sent from my Nexus 7 using xda app-developers app
I'm trying to update it while keeping root. I downloaded ota root keeper. But I keep getting the "dead Android with red exclamation mark" screen every time I try to install the OTA update. I even tried its option to temporarily un-root before performing the update, but no luck. Anyone have any ideas?
Edit - Also I tried installing it manually. Used GooManager to install TWRP and tried installing 4.1.2 through it. Still fails every time. I'm disgusted.
Sent from my Nexus 7 using xda app-developers app
I had my Nexus 7 rooted w/ the "Google Nexus 7 Toolkit" and I was able to update to 4.1.2 w/o any problems.
Sent from my Nexus 7 using xda app-developers app
Having the same issue as well..Can't root.
Sent from my GT-I9100 using xda premium
---------- Post added at 02:41 PM ---------- Previous post was at 02:25 PM ----------
Well after trying again I finally successed doing so.
Sent from my GT-I9100 using xda premium
Backup--unroot--relock--update--unlock--reroot--recover? I'm brand new to this stuff (don't even have a N7 yet), but seems like this would work.
The stock update will only install with stock recovery being root has no effect. If you have changed system apps. Like to the 4.2 apps floating around could stop the update as well. Google does not care another root or unlocked. I would say do factory reset then update then root. Or download one of the stock cwm/twelve roms and be done with it.
Sent from my Nexus 7 using Tapatalk 2
Well it happened again. The 4.2.2 update is out and I can't update to it. Every time I try, I get the dead android error icon.
It sure gets old saying this, but...
The error message is recorded in the recovery log at
/cache/recovery/recovery.log
You will find that the problem has nothing to do with root per se - generally the root user (or apps that were granted root privilege) have altered or deleted something in /system needed for the OTA to correctly complete.
In general, OTAs are not meant for customized ROMs - it is unreasonable for anyone to have an expectation that they will work correctly on a customized ROM.
But I didn't install a customized rom. I just rooted/unlocked it.
You can always download the update from Google's servers and flash it through fastboot. No hassle.
Bryon15 said:
But I didn't install a customized rom. I just rooted/unlocked it.
Click to expand...
Click to collapse
the proof is in the pudding...
...and the pudding is at /cache/recovery/recovery.log
bftb0 said:
generally the root user (or apps that were granted root privilege) have altered or deleted something in /system needed for the OTA to correctly complete.
Click to expand...
Click to collapse
Note that the recovery.log file gets overwritten every time you boot the recovery, so the thing you are trying to retrieve (let's say with the booted OS) will be from the immediately prior use of the recovery. So, attempt the OTA (let it fail), then boot into the OS and capture that file (using something which is root-privileged).
I was using device perfectly till today. I've installed nocturnal kit lastly. Don't know if it's related to this or not but it seems i've lost my root access. Now I can't use CM file manager which was working well and can't edit any app's settings in paranoidandroid. Both need root access. It keeps saying "couldn't get privileges" So is it possible to lose root by installing apps, mods or any software issues?
Not likely. Just go to your superuser app and make sure root access is being given.
Sent from my Nexus 4 using Tapatalk 2
joshnichols189 said:
Not likely. Just go to your superuser app and make sure root access is being given.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
checked su app and all root needed apps are seems to have access but they don't work I'm gonna wipe and reflash I think.
Try wiping cache for superuser. And you can try switching to superSU, it's better than the original.
Sent from my Nexus 4 using xda app-developers app
get the supersu app from the market, free. install it, open it, then press yes when it asks you to update your su binaries. supersu works well for jelly bean, superuser is hit and miss.
Ace42 said:
Try wiping cache for superuser. And you can try switching to superSU, it's better than the original.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Tried that too. Also wiped cache & dalvik and didn't work.
Hey, I've done a full wipe as well as return to stock, then proceed to install jwr66y from scratch, after installing i proceeded installing twrp and superuser, everything seems to run fine with root and all. The only thing which has been bothering me is that some apps are displaying force close error immediatly after starting them. Examples are Adaway, Adfree and Yelp.
Anyone knows what's going on there?
Same thing with me, some apps just crash immediately. I'm glad I made a backup before I installed. I installed the ota through a zip to preserve root/custom recovery and also just installing it normally. Same thing happens with crashes.
Sent from my Nexus 4 using Tapatalk 4
CCDillon said:
Same thing with me, some apps just crash immediately. I'm glad I made a backup before I installed. I installed the ota through a zip to preserve root/custom recovery and also just installing it normally. Same thing happens with crashes.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Yeah i also installed though a Zip which was supposed to be vanilla with added busybox and root.
I had my nexus 7 running so i was backing up from there which fixed the problem. However i am really wondering why apps which were downloaded straight from google play messed around.
I hope they won't mess around later.
I was completely stock and the same thing happened to me. I had to erase recovery, data and boot loader through fastboot and then reinstall everything new from the factory image on Google's site.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Oh wow. I had to do that with the initial 4.3 release. Don't think I'll do it for such a minor update unless I have a lot of free time. Though, the software update notification is in the way most of the time.. In surprised this isn't affecting more devices.
Sent from my Nexus 4 using Tapatalk 4
Has anyone tried this method? SuperSU has a full unroot option in its settings. I have read many posts saying it is impossible to unroot at this time.
I did a little searching around and didn't find much. Just suggestions to try it and no one ever reported back if it works or doesn't.
I personally don't have the OTA and have a custom ROM, but i would like to know any confirmation of it working or not working by anyone that has tried it.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
I did the ota to mf3 and successfully rooted it I then realized that I had like 6gbs missing so in an effort to restore I went into the SU settings and chose the remove root option and it seemed to work I checked with root checker and I no longer had root access I still was unable to restore it just bumps me into Odin mode and I have to boot power+home+volume- then cancel to reboot my phone into working order
But as far as I can tell I have no root
Since I can't restore and try and clear up my missing storage I wanted to take it in and try and get a new one under warranty but I'm afraid to use triangle away so I'm just gonna wait it out until we get a mf3 restore firmware for Odin since my phone works fine for now
Sent from my SAMSUNG-SGH-I337 using xda premium
So that is 1 confirmation for an unroot. Basically hit unroot, it sends the phone to bootloop. Remove battery, put it back, then boot to download mode with power+volume down, then hit volume down again to cancel and reboot to a fully functional phone with no root. If that doesn't work, use power+home+volume down. Anyone else?
Btw,
Don't use triangle away. It flashes a temporary recovery to reset the binary. It will brick you or just fail.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
graydiggy said:
Has anyone tried this method? SuperSU has a full unroot option in its settings.
Click to expand...
Click to collapse
I fully un-rooted using the method in my post here - http://forum.xda-developers.com/showthread.php?p=44495559 . For me, it just threw the custom-lock icon boot up screen and showed "Custom" status in the "About Phone" menu when using the SuperSU's un-root method.
The problem was busy box. The MF3 root scripts install Busybox files into the /xbin directory, but SuperSU's "full unroot" doesn't touch Busybox's files. Not even any Busybox apps can remove those files.
So delete the busybox files first, then unroot. That is 2 confirmed unroots.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
ou812bkewl said:
I fully un-rooted using the method in my post here - http://forum.xda-developers.com/showthread.php?p=44495559 . For me, it just threw the custom-lock icon boot up screen and showed "Custom" status in the "About Phone" menu when using the SuperSU's un-root method.
The problem was busy box. The MF3 root scripts install Busybox files into the /xbin directory, but SuperSU's "full unroot" doesn't touch Busybox's files. Not even any Busybox apps can remove those files.
Click to expand...
Click to collapse
graydiggy said:
So delete the busybox files first, then unroot. That is 2 confirmed unroots.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This method also worked for me as well. Had no problems following the steps.
3 confirmed
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
graydiggy said:
3 confirmed
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Good info to know. Thanks graydiggy
I am going to change this to a how to thread later today. Anyone else try it?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
this may be a stupid question, but if you went through the trouble of rooting after the mf3 update.. why would you want to unroot?
Warranty replacement in case of a hardware issue, testing purposes, also, some people only want a temp root to remove bloat. After that, they don't want root anymore.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
So to summarize the steps from what I've read on rooting & unrooting MF3:
Root:
Use this guide by jortex: http://forum.xda-developers.com/showthread.php?t=2387577&highlight=mf3
Unroot: http://forum.xda-developers.com/showpost.php?p=44495559&postcount=39
1. Re-root again using the same method you did before for MF3, then:
--a) Reboot, update SuperSU app and it's binary
--b) Reboot again, verify device status is back to"Official"
--c) Reboot again, verifying that, this time, the boot screen is back to normal again
2. Download a file manager app in the Play Store called "Total Commander" and enable "Root functions everywhere" in its settings.
3. Navigate to a folder called "/system/xbin"
4. Delete ONLY files in that folder with the word "busybox" within its filename or symlink path. You should end up with three files left. I did. Two of them are SuperSU related. DO NOT DELETE ANY OF THEM!
5.Open SuperSU and, in its settings, select the "Full un-root" option. Once SuperSU closes, reboot.
Click to expand...
Click to collapse
Follow step 1 if not rooted or messed up somewhere during unrooting process.
Just double checking step 2: We can use es file explorer with root explorer option as well correct?
Also I noticed superSU got updated today:
http://forum.xda-developers.com/showthread.php?t=1538053
05.09.2013 - v1.60
- Added SELinux+Enforcing compatibility (for new SGS4 ROMs)
- Fixed (newest) CWM versions asking you question that break root if answered wrongly
- Fixed issue with the TWRP/CWM binary installer
- Fixed 4.3 OTA survival looping
Click to expand...
Click to collapse
Does the new update have something to do with our mf3 baseband like SELinux?
haremmon said:
So to summarize the steps from what I've read on rooting & unrooting MF3:
Root:
Use this guide by jortex: http://forum.xda-developers.com/showthread.php?t=2387577&highlight=mf3
Unroot: http://forum.xda-developers.com/showpost.php?p=44495559&postcount=39
Follow step 1 if not rooted or messed up somewhere during unrooting process.
Just double checking step 2: We can use es file explorer with root explorer option as well correct?
Also I noticed superSU got updated today:
http://forum.xda-developers.com/showthread.php?t=1538053
Does the new update have something to do with our mf3 baseband like SELinux?
Click to expand...
Click to collapse
This worked for me! But I skipped all the steps in the beginning. They sounded useless to me. Rerouting to unroot? Hah
I deleted all busybox files and was left with 3 files then went to SuperSU and did the full unroot and restart.
I check with root checker and installed SuperSU as well. Root checker said I have no root and SuperSU fails. Status is official.
Going to restart a few times to be sure.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
WezzleD said:
This worked for me! But I skipped all the steps in the beginning. They sounded useless to me. Rerouting to unroot? Hah
I deleted all busybox files and was left with 3 files then went to SuperSU and did the full unroot and restart.
I check with root checker and installed SuperSU as well. Root checker said I have no root and SuperSU fails. Status is official.
Going to restart a few times to be sure.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Nice! Thank you. Looks like 4 confirmed. Also, was SuperSU on v1.60?
haremmon said:
Nice! Thank you. Looks like 4 confirmed. Also, was SuperSU on v1.60?
Click to expand...
Click to collapse
I'm actually not sure. Didn't look at version numbers.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
4 confirmed. Let's get 5 and I will post a how to.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
ou812bkewl said:
I fully un-rooted using the method in my post here - http://forum.xda-developers.com/showthread.php?p=44495559 . For me, it just threw the custom-lock icon boot up screen and showed "Custom" status in the "About Phone" menu when using the SuperSU's un-root method.
The problem was busy box. The MF3 root scripts install Busybox files into the /xbin directory, but SuperSU's "full unroot" doesn't touch Busybox's files. Not even any Busybox apps can remove those files.
Click to expand...
Click to collapse
That method worked for me also. I'm so glad it was discovered. Successfully unrooted.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
5!
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
graydiggy said:
5!
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was able to unlock as well. However my phone stopped showing the custom unlocked symbol at bootup a few days ago (before doing this) and I am at a loss as to why. So I am not sure I can count as a real confirmation.
I did your unroot process, root checker confirms I no longer have root and the unlock symbol has not come back.
Stay tuned guys. Getting everything ready to quickly make a more organized how to.
Being horribly sick is not helping
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
I recently rooted my Verizon note3 using towel root checked with root check to verify proper root and it does. Installed SuperSU and installed like it should but when I go into settings within SuperSU it says installation failed even though it does grant superuser permissions. I'm still learning so if it does grant superuser privileges then why the notice about installation failed? Should I try another SuperSU program? Experts I'm waiting for advice. Thanks. Jesse
Sent from my GT-P5113 using XDA Free mobile app
Did you restart anytime during that? Happened to me, rebooted and its fine
Yes I did reboot but didn't change the message
Sent from my GT-P5113 using XDA Free mobile app
Actually everything that I have added that required give giving it permission for access has worked flawlessly so I'm not sure that that message interferes with anything but I would like to be sure.
Sent from my GT-P5113 using XDA Free mobile app