ROM Manager Fix Permissions Blank Screen [solved] - Droid Incredible General

Running ROM Manager Premium v4.7.0.5 with ClockworkMod 3.0.0.8 (newer versions did not flash ROMs properly) on Cyanogenmod 7.1 with SuperUser 3.0.6 (su binary 3.0.2).
When I try to run Fix Permissions from ROM Manager, it asks me to confirm as normal. When I confirm, it just sits there in the Fix Permissions window where the log output would usually appear. I've let it go for several minutes and nothing ever seems to show up. It should be noted that ROM Manager never requests root permissions for this either.
Am I not waiting long enough, or has anyone seen this issue before?
Edit: I also posted this to reddit under Android (can't link because I don't have enough posts).

Are you running the latest su? I had an issue with the latest version and had to uninstall updates to get it to work, once I did that it let me flash the latest CWM and fix permissions
Sent from my ADR6300 using XDA App

I was running the latest version of Superuser and su. I uninstalled updates to Superuser, but that only brings it down to 3.0.4, and the same problem results.
Edit: It would appear this is deeper than just ROM manager, and that SuperUser is the culprit. I just tried updating the su binary, and it's stuck at "Gaining root access." Always exciting when Superuser can't give itself root rights...
This is affecting everything requiring root permissions. The programs just hang because the root prompt never shows up. Not really sure what would've caused this. Must be an su/Superuser update. I can't flash from ROM manager because Superuser is broken. Is there any place to install an older Superuser APK?

Did you downgrade in the market? That just put me back to version 2.3.6.3 which shouldn't give you problems, and I'm pretty sure there's a way to install it with adb but I'm not sure how, you could always install a new ROM with CWM.
Sent from my ADR6300 using XDA App

I also just noticed your binary is outdated... Try updating that and c if it fixes anything, the latest version of su with the latest binary are actually working for me but, the previous version didn't .
Sent from my ADR6300 using XDA App

The SuperUser update screwed me.
I had to reflash the older 2.3.5.3 version.
If you look at his website there's a way to download the older versions. Flash it like you would a rom. Solved my problems. I'm not upgrading until I know it works for Incredible phones.
I can't seem to find where I got mine from but here's a link to another place that has it.
http://rootzwiki.com/topic/194-superuser-2363-17-june-2011/

gadzooks64 said:
The SuperUser update screwed me.
I had to reflash the older 2.3.5.3 version.
If you look at his website there's a way to download the older versions. Flash it like you would a rom. Solved my problems. I'm not upgrading until I know it works for Incredible phones.
I can't seem to find where I got mine from but here's a link to another place that has it.
Click to expand...
Click to collapse
That fixed it, thanks. Now running Superuser 3.0.6/su 2.3.5.3 and things requiring root permission are actually asking for them again.

Why not just "Fix Permissions" straight through the recovery?

Related

Re root incredible after ota?

Is it possible to re root the incredible after you apply the OTA or is it still broken?
if you have s-off, its just update, place the recovery image on the sd card, reboot into into hboot, and hit yes to upgrade and then itll flash the custom recovery and all is good
I am curious of this too. As mine is s-on and now I can't reroot. It gets to the part where it says it is "waiting for root" and never goes any further.
as of right now unrevoked will not work after the latest update is applied.
Do NOT update if you want to keep root....
If your running a rom built with the latest version this update won't come to you anyway.
If you see the update then you are using a rom that is built with old code.... tell the rom developer to update his shiat! If HTC can come out with updates faster then your rom developer can.... should you be using his rom?
And I assume there is no other way to root other than unrevoked?????? Surely the developers of unrevoked are working on finding the loop hole? I hope anyway. I miss my root apps that I had on my droid!
You can root without unrevockeds method. I can't remeber the exact procedure as i dont even know what i did wholly. But it involved unrooting but leaving the app and su. Upgrading to the proper baseband. Receiving the ota then pushing su again. I did this a few months ago though right after the 2.2 ota update. Took me like 3 hours to achieve root. If your interested i can try to repeat my method tomorrow and report back.
Sent from Conical. 07
or just downgrade.. reroot, have s-off, then update, then reroot
I like the downgrade idea. But I come from the motorola droid so I know the procedures are a lot different. I am not a noob by any means on rooting but I am to this phone. Could you please walk me through it and point me in the direction of the files??
Man I wish I read this thread before doing the OTA manually. I upgraded the OTA last night and my phone had S-on. Everything was ok, until I tried to install the payload zip and Superuser zip from Clockwork afterward. Before I did that, I was able to boot in the phone after the OTA even with Clockwork but after applying those 2 zip files, my phone will go in a loop after the droid animation and back to the HTC screen and forever stuck in reboot. I was so freaked out but with clockwork I just flashed wipe everything and installed Virtuous 3.1. Everything is working fine now, but if you do the OTA, do not install SU and payload in Clockwork
So you can do the OTA on a rooted phone running a custom rom?
Sent from my ADR6300 using XDA App
RamAir02 said:
So you can do the OTA on a rooted phone running a custom rom?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Not sure if the 10/13 build of Virtuous 3.1 already have the OTA or not. At this point, I kind of don't really care, just glad I have my phone up and running again. Plus unless you really want Bloatware, most of the changes don't seem to be that signficiant. Here's the change log
* Updated Flash Player with security enhancements
* Visual Voice Mail Wifi improvements and removal of incorrect service messages and post-call notifications
* Better support for Yahoo IMAP e-mail
* Update to Slacker Radio app
* You can attach files larger than 5MB
* Updated Cox POP3 e-mail settings
* Updated Comcast POP3 e-mail settings
* Play YouTube videos in the YouTube app (that's new?)
* Seamlessly switch between portrait/landscape in Google Maps
* Search key and other buttons displayed in the correct order (what's the wrong order?)
* VCAST app lets you bill apps to your Verizon account
Yeah. Lots of Bloatware. I just flashed the 10/13 "almost"stock ROM over my previous ROM and everything works fine. Battery life is great with the new stock kernel. I'm not using setcpu. Quadrant speed is lower but the phone is very fast. BT connects much better although I find BT volume to be low. 3G is very stable. I had to go back into ADB and remove VCast, VVM etc but that's not too big a deal.
ok so i have s-off and cant reroot using the unrevoked3. it hangs at the waiting for root screen. can i just apply the clockworkmod update zip and call it a day to get root again
I can't seem to get a clear answer on this: Do I need to have the stock recovery to successfully install this OTA? I have S-OFF and Clockworkmod, and so far I haven't figured out for sure if I should accept the OTA through the dialog, or if I can apply it through ROM Manager, or if I can apply it through Clockworkmod. Can anyone clear this up for me?
thevoiceless said:
I can't seem to get a clear answer on this: Do I need to have the stock recovery to successfully install this OTA? I have S-OFF and Clockworkmod, and so far I haven't figured out for sure if I should accept the OTA through the dialog, or if I can apply it through ROM Manager, or if I can apply it through Clockworkmod. Can anyone clear this up for me?
Click to expand...
Click to collapse
The update will go through HBOOT, you can update with clockwork and s-off. though it seems from what i've read in this thread if you do you will no longer be rooted.
I remeber what i did for the 2.2 update. What i did was restore the stock recovery but leave su and superuser. This makes the phone look stock without root. Then take the ota. Reflash clockworkmod. Su and superuser apk should still be there. Then use a super usr app. Im pretty sure thats what i did to reroot
Edit. This process assumes that su and superuser.apk are on the phone and not removed.
Sent from Conical. 07
I have s-off but not Su or root. How do I reroot
Sent from my ADR6300 using XDA App
If anybody wants the stock recovery ill find and post it.
Sent from Conical. 07
morph3k said:
The update will go through HBOOT, you can update with clockwork and s-off. though it seems from what i've read in this thread if you do you will no longer be rooted.
Click to expand...
Click to collapse
So then do I need to reinstall the bloat apps that it will look for? And can't I just use unrevoked to re-root?
linuxmotion said:
If anybody wants the stock recovery ill find and post it.
Sent from Conical. 07
Click to expand...
Click to collapse
If you could that would be great. Thanks.
Cary

Binary update

I just got a message saying that my su binary is outdated. Should I update? I have nero 5 running on my vibrant.
I just didn't know if this was some factory update that I shouldn't do.
Thanks.
Sent from my SGH-T959 using xda premium
That's a update from superuser! So yes u do update it
Sent from my SGH-T959 using xda premium
Alright, thanks alot.
Sent from my SGH-T959 using xda premium
Did it work?
I also got the notification. I then discovered this app had checked auto update in the market. To add insult to injury, the update FC'd AND get this: BROKE ROOT. All root apps stopped working. I was able to recover by uninstalling updates.
I then go looking for a fix only to discover that the dev removed the zip that is supposed to fix it from his website. I tried the zip that was there last night but was unsuccessful. I see another update that came out yesterday in the market. It is supposed to suppress outdated binary notification. I am a little gun shy with this app/dev. Lone update in my apps now.
IrieBro said:
I also got the notification. I then discovered this app had checked auto update in the market. To add insult to injury, the update FC'd AND get this: BROKE ROOT. All root apps stopped working. I was able to recover by uninstalling updates.
I then go looking for a fix only to discover that the dev removed the zip that is supposed to fix it from his website. I tried the zip that was there last night but was unsuccessful. I see another update that came out yesterday in the market. It is supposed to suppress outdated binary notification. I am a little gun shy with this app/dev. Lone update in my apps now.
Click to expand...
Click to collapse
Try the newest 3.0.5, it fixes that fc stuff. You can dl through rom manager (only flashing recovery and possibly reboot to recovery need root).
Also, it wasn't the binary, it was the app that had those issues.
Sent from my HTC Sensation 4G using XDA App
I had gotten it 4 times over the last 5 days...just followed it, let it run, and all is well.
3e Recovery
Thanks for the tip. I tried as you suggested and ran into signature issues while in recovery. I guess I have to mod recovery so that it doesn't check sigs or wipe. This is getting more convoluted than I wanted just to get su updated. I think I read somewhere that an updated busybox might help too. Anyway, I will dive into fixing my "E:failed to verify whole-file signature" issues later and put this su thing to rest. I am on 3.05 and have disabled binary notification for now.
SU and BB are updated through the "binary update". It is version 3.0.5--had me run it a couple of times. I also use "fix permissions" after serious updates, and nightly flashes to keep things in order.

No SuperUser prompt in (stock) ICS

I have a Galaxy Tab 10.1 (PT-7500R from Rogers), trying to root on the new official ICS.
I have followed the directions at http://forum.xda-developers.com/showthread.php?t=1239185
CWM installed and works fine. After applying "Samsung_Galaxy_Tab_10.1_root.zip" in CWM, I boot into Android, I see SuperUser in my app menu and can bring up its interface.
However, when I try to launch a su-required function (such as Reboot Recovery in ROM Manager), I don't get a prompt for SU permissions.
I have tried this with both OTA and manual (Odin3) installs of the official ICS from Rogers, from unrooted stock Honeycomb, several times.
I don't encounter this problem with stock Honeycomb... rooting that version appears to work fine.
I have experimented with some community builds, perhaps I have installed an incompatible kernel that needs replacing? I don't know, but any advice would be greatly appreciated.
Regards,
diggerB
diggerb said:
I have a Galaxy Tab 10.1 (PT-7500R from Rogers), trying to root on the new official ICS.
I have followed the directions at http://forum.xda-developers.com/showthread.php?t=1239185
CWM installed and works fine. "After applying Samsung_Galaxy_Tab_10.1_root.zip" in CWM, I boot into Android, I see SuperUser in my app menu and can bring up its interface.
However, when I try to launch a su-required function (such as Reboot Recovery in ROM Manager), I don't get a prompt for SU permissions.
I have tried this with both OTA and manual (Odin3) installs of the official ICS from Rogers, from unrooted stock Honeycomb, several times.
I don't encounter this problem with stock Honeycomb... rooting that version appears to work fine.
I have experimented with some community builds, perhaps I have installed an incompatible kernel that needs replacing? I don't know, but any advice would be greatly appreciated.
Regards,
diggerB
Click to expand...
Click to collapse
Have you tried to see if superuser had an update in the market? I recommend to also make sure the binary is up to date in the superuser app.
Sent from my SAMSUNG-SGH-I747 using xda premium
nakedninja42 said:
Have you tried to see if superuser had an update in the market? I recommend to also make sure the binary is up to date in the superuser app.
Click to expand...
Click to collapse
Thank you for your reply.
I updated to the latest version in Play Store, it shows Binary v2.3.1-ef , update check shows latest version 3.1.1 but when I click Update, it fails on the step "Gaining root access..."
Cheers
diggerB
You're not rooted anymore. The superuser app is there but it can't do anything since the su is missing. You have to re-root.
Sent from my GT-I9300 using Tapatalk 2
Tyxerakias said:
You're not rooted anymore. The superuser app is there but it can't do anything since the su is missing. You have to re-root.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the feedback... but I just went back into CWM and applied the root again, still in exactly the same boat.
Thanks to all, I found a solution in another thread: http://forum.xda-developers.com/showthread.php?p=31179418#post31179418
Superuser just didn't want to work. The SuperSU root method referred by the OP in that thread worked great. All is well again. Until next time of course.
Hi, if you go to "www.galaxytabhacks.com" you will find the solution, there is an upgrade to superuser.

I'm not rooted and I keep getting Custom Status...why?

I really don't understand this phone. I've been on a quest of 2 weeks to be rooted and on official status, finally i gave up everything because i was not able to have both. Finally i flashed factory rom through odin, formated a couple of time the phone, and i got back official status. I much rather gave up a few rooting benefits then OTAs, at least until they fix the phone's problems.
Well, this morning, i wake up, and that DAMN custom status is back....WHY????????? I'm not rooted, i'm 100% stock, i checked with rootchecker and my phone doesnt have root....then why does that damn status keep coming back??? There is obviously something else that triggers it......man i'm so deperate! Please help!
polish_pat said:
I really don't understand this phone. I've been on a quest of 2 weeks to be rooted and on official status, finally i gave up everything because i was not able to have both. Finally i flashed factory rom through odin, formated a couple of time the phone, and i got back official status. I much rather gave up a few rooting benefits then OTAs, at least until they fix the phone's problems.
Well, this morning, i wake up, and that DAMN custom status is back....WHY????????? I'm not rooted, i'm 100% stock, i checked with rootchecker and my phone doesnt have root....then why does that damn status keep coming back??? There is obviously something else that triggers it......man i'm so deperate! Please help!
Click to expand...
Click to collapse
It's really not as big of a deal as you are making it. The way I see it you have 2 choices.
1. Exchange the phone for another (that might do the same thing)
2. Ignore it.
Just like every other Galaxy phone out there (you remember the skyrockets, right?) not all of them react the same way. Some get custom, some do not. Others switch back and forth.
I've noticed you have made many posts about this same thing. If someone hasn't provided a concrete answer that has worked for you by now it just doesn't exist yet. No matter how frustrated you are over it, making new posts about it are not going to change anything.
Its up to you if you keep wanting to post about it (I'm not complaining about it), I just don't think it's going to get you any more information at this point than what already has been said. Maybe I am wrong and someone will tell you exactly what to do to make it "official", but I haven't seen anything yet.
Good luck and try not to let it get to you so much.
euhhh no, they are not about the same thing, one was about retaining officiel while rooted, and now that i've given up on that, i still have a custom status, the reson why i dont report there is becuase poeple have seen the thread and will not go back, so in order to attract new poster i create a new thread. And no, i dont want to ignore anything because i want OTAs. If you have a problem with that, dont answer
You need to re-root (motochopper method) and then using a file browser such as "root explorer" go to:
/System/Xbin
Once you have navigated to the above path, delete these two files:
"su" and " busybox"
Once you've deleted the two files, uninstall SuperSU and reboot your phone twice.
You'll notice that after the second reboot the "custom" will revert back to "official"
Sent from my SGH-I337M using Tapatalk 2
peoples_flip said:
You need to re-root (motochopper method) and then using a file browser such as "root explorer" go to:
/System/Xbin
Once you have navigated to the above path, delete these two files:
"su" and " busybox"
Once you've deleted the two files, uninstall SuperSU and reboot your phone twice.
You'll notice that after the second reboot the "custom" will revert back to "official"
Sent from my SGH-I337M using Tapatalk 2
Click to expand...
Click to collapse
correct me if i'm wrong but these 2 files, should not even exist if you install a firmware thru odin and format the phone a few times...
I went through what you have, I completed a full stock restore via Odin and these two files I mentioned were still there. Use a file explorer and go to the path I suggested and you'll see them there
Sent from my SGH-I337M using Tapatalk 2
polish_pat said:
correct me if i'm wrong but these 2 files, should not even exist if you install a firmware thru odin and format the phone a few times...
Click to expand...
Click to collapse
I don't believe the current Odin contains a pit...or whatever it is that formats the phone...
So all Odin is going to do is reinstall everything...so replace missing or corrupted files - it will not delete your new files
Formating from the phone itself won't delete everything...its just going to delete your apps, app data, and cache
Therefore doing multiple factory resets and odins likely will not remove all traces of root...someone correct me if I'm wrong but that's what I believe is the case...
Sent from my HTC PH39100 using Tapatalk 2
Is there a reason why it showing custom is a bad thing?
Sent from my SAMSUNG-SGH-I337 using xda premium
XGhozt said:
Is there a reason why it showing custom is a bad thing?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
AT&T software update push or download will not work for your phone if it is showing custom. People like to be getting these stock updates as soon as they are published by the provider, not when some good heart packages a new ROM using them.
polish_pat said:
correct me if i'm wrong but these 2 files, should not even exist if you install a firmware thru odin and format the phone a few times...
Click to expand...
Click to collapse
Good info here, I did this procedure as you described, and yes, official is showing, but you can NOT delete su, it will unroot. I just renamed the 2 files, and root was gone. renamed su back, re-installed su superuser, and reboot, root is back with official status.
Thanks.
TheAxman said:
Good info here, I did this procedure as you described, and yes, official is showing, but you can NOT delete su, it will unroot. I just renamed the 2 files, and root was gone. renamed su back, re-installed su superuser, and reboot, root is back with official status.
Click to expand...
Click to collapse
I tried this procedure and still have custom after 2 reboots. I renamed su and busybox then verified root was gone. Then renamed su back. I guess the part I was confused at was reinstall super user. Do I uninstall then re-install from play store?
Thank you.
EDIT: Followed my thought of uninstalling and re-installing through play store and still get custom.
CAG-man said:
I tried this procedure and still have custom after 2 reboots. I renamed su and busybox then verified root was gone. Then renamed su back. I guess the part I was confused at was reinstall super user. Do I uninstall then re-install from play store?
Thank you.
EDIT: Followed my thought of uninstalling and re-installing through play store and still get custom.
Click to expand...
Click to collapse
Same here
CAG-man said:
I tried this procedure and still have custom after 2 reboots. I renamed su and busybox then verified root was gone. Then renamed su back. I guess the part I was confused at was reinstall super user. Do I uninstall then re-install from play store?
Thank you.
EDIT: Followed my thought of uninstalling and re-installing through play store and still get custom.
Click to expand...
Click to collapse
Correct. the one from the playstore updates the binaries. then uninstall.
---------- Post added at 07:11 PM ---------- Previous post was at 07:10 PM ----------
XGhozt said:
Is there a reason why it showing custom is a bad thing?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
Good answer, why does it matter if it says custom? whats the big deal here. If you are wanting the update, why not just wait until a dev does what they need to do to it, and flash it later. I updated 1 time in a year on my GS3, and never did it again. When a new rom is developed, it usually is a base from the update...so....
Had a posting. Could not delete
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Did some digging in the forums and I am rooted with OFFICIAL.
This is how to do it. Taken from this thread.
http://forum.xda-developers.com/showthread.php?t=2252248&page=42
Mr. Q said:
Well, you do not have to install the ZIP, but instead, do the following:
- Install SuperSU from the market
- Grant SuperSU root access
- When asked to update su-binary, please do
- Remove SuperUser from your device
- Reboot (I read two reboots are needed to make the icon disappear again.)
Click to expand...
Click to collapse
My process completely.
Remove Busybox from system/xbin (or your busybox backup)
Install SuperSU by Chainfire from playstore.
Open SuperSU and Grant SU root
Update the binary
Say yes to try to remove other root apps. This will remove superuser.
reboot
reboot
On second reboot you will notice the Galaxy S4 logo returns and Official Status has returned.
If it has not returned then some other issue is causing the custom status.
CAG-man said:
Did some digging in the forums and I am rooted with OFFICIAL.
This is how to do it. Taken from this thread.
http://forum.xda-developers.com/showthread.php?t=2252248&page=42
My process completely.
Remove Busybox from system/xbin (or your busybox backup)
Install SuperSU by Chainfire from playstore.
Open SuperSU and Grant SU root
Update the binary
Say yes to try to remove other root apps. This will remove superuser.
reboot
reboot
On second reboot you will notice the Galaxy S4 logo returns and Official Status has returned.
If it has not returned then some other issue is causing the custom status.
Click to expand...
Click to collapse
I was able to get official and root, the problem is it comes back after 2-3 days, please report back on sturday and tell me if its still official, also this logo you are talking about, i never see it because im in canada and my bootloader is unlocked already
EDIT: Ok, so once i was rooted and installed SuperSU and got superuser out, i deleted busybox, i then rebooted ONCE and got official just like that. I also took out SD card because i know this screwed me up last time. I'm happy because i'm rooted and official, but i'm not convinced this will last very long because it has never lasted more than 2 days. I will report back in a few days. Thanks Cagman, you've been very helpful and what you told me to do did the best results for me, i just hope they last
so far so good!!!:fingers-crossed:
polish_pat said:
so far so good!!!:fingers-crossed:
Click to expand...
Click to collapse
Try rebooting a few more times.
For about a week i was getting the custom status every 2nd or 3rd reboot, and then eventually it just went away...
joeybear23 said:
Try rebooting a few more times.
For about a week i was getting the custom status every 2nd or 3rd reboot, and then eventually it just went away...
Click to expand...
Click to collapse
Hahaha, i did it!! earlier this afternoon i sort of challenged my phone by rebooting it constantly, ive rebboted probbaly 20-30 times and its still official, i guess deleting busybox sealed the deal!!
Polish_pat I am glad I was able to help. You are welcome. Congratulations.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

[Q] Nexus 4 with android 4.3 not correctly rooted?

I downloaded and flashed a fresh version of stock 4.3, and installed the supersu zip file through CWM. now i have a working device that is supposedly rooted.
my problem is that something is causing root privileges to do some weird things. I enabled root file manager on the rhythm software file manager, and it suddenly cant access my data on the internal SD card, but when i disable root for it, i can see the stuff fine.
As well, when i try to start Hola using Root, it starts, then flashes several times and stops.
Apps ask for root permissions fine, and it grants them fine, but they just aren't working right.
I have tried re-downloading and flashing a couple different versions of supersu through CWM, including the newest, v1.43.
Is this something that can be fixed, or will i need to start from scratch again?
Hey,
Got the same thing for getting to my sdcard content. Get to it thru /mnt/sdcard instead of /sdcard. This works for me with rooted 4.3.
Cheers
Sent from my Nexus 4 using xda app-developers app
Ricx94 said:
I downloaded and flashed a fresh version of stock 4.3, and installed the supersu zip file through CWM. now i have a working device that is supposedly rooted.
my problem is that something is causing root privileges to do some weird things. I enabled root file manager on the rhythm software file manager, and it suddenly cant access my data on the internal SD card, but when i disable root for it, i can see the stuff fine.
As well, when i try to start Hola using Root, it starts, then flashes several times and stops.
Apps ask for root permissions fine, and it grants them fine, but they just aren't working right.
I have tried re-downloading and flashing a couple different versions of supersu through CWM, including the newest, v1.43.
Is this something that can be fixed, or will i need to start from scratch again?
Click to expand...
Click to collapse
have you tried updating to the newest superSU to version 1.44 in the playstore ? should've been the first thing you did after flashing 1.43 as it fixes alot of the root problems
Sgace said:
Hey,
Got the same thing for getting to my sdcard content. Get to it thru /mnt/sdcard instead of /sdcard. This works for me with rooted 4.3.
Cheers
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Nope...doesn't work as it redirects to the same place. There is a single file there that is unreadable named 0 and its 0kb, same as what I currently see
paul_viado said:
have you tried updating to the newest superSU to version 1.44 in the playstore ? should've been the first thing you did after flashing 1.43 as it fixes alot of the root problems
Click to expand...
Click to collapse
That was the first thing i tried as well. i also did a cleanup and reinstalled from the play store several times hoping it would work, but nothing. SuperSU seems to think i am rooted, because it doesn't complain about the binaries or anything, it simply grants permissions, but the permissions don't work right.
https://plus.google.com/113517319477420052449/posts/7o5H214hRSv
Sent from my Nexus 4 using xda premium
stuart0001 said:
https://plus.google.com/113517319477420052449/posts/7o5H214hRSv
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
tried installing newest version, didn't have any effect. i think I'll just flash a new ROM onto the phone...maybe cyanogenmod 10.1.2
Thanks you guys for the help, though.

Categories

Resources