Related
If you noticed, Superuser updated to 2.3 - make sure you do an nandroid backup before you attempt to apply it. I was able to apply it, and when I attempted to launch the application, it FCed on me. I was able to grant ROM Manager SU rights, but I just wanted everyone to be aware. You can see the original Superuser 2.3 thread here.
I did a nandroid restore and got rid of it since it was FC like mad.
SU 2.3.1 is up, and so far seems to be working without any issues.
maltzer said:
SU 2.3.1 is up, and so far seems to be working without any issues.
Click to expand...
Click to collapse
FYI, I am also using 2.3.1 without problems. The only crash I noticed was when you checked the log before actually trying anything that used superuser it caused a FC. After using a couple of root apps, I can check the log without a crash.
Can I flash the 2.3.1 over the 2.3 version? I can't find any confirmation that this is the right procedure to update su.
Can't even get this to install properly on the Captivate. Installation aborted every time in recovery mode.
When I try to install from the market, I get package not signed properly error. What is the correct procedure to update your SuperUser.apk file?
might be helpful
rajendra82 said:
When I try to install from the market, I get package not signed properly error. What is the correct procedure to update your SuperUser.apk file?
Click to expand...
Click to collapse
if you go to the g1 thread and go to themes and ****....they got the apk for free......just gotta sideload it...ya digg
oh yeah it works perfect on my captivate....
I have su 2.3.1 and it works perfectly i upgraded it from market had 1.8 before i think on one of the one click root packages. No issues at all though and im back on stock rom right now.
My rooted 4.2 c5502 started showing ota for 4.3 (file size is 307.1Mb), I was hoping update via ota would retain the root. Unfortunately, after many tries, the update keep on failing.
When click on update, system will reboot and screen showing android icon with a progress bar. The progress bar will run for about 3 or 4 second and system just rebootsback to lockscreen and show a msg saying "could not install".
I assume this might be due to the dual recovery I installed? Before I try restore the recovery, anyone else able to update via ota and still got root?
I too rooted my phone nd tried to update the phone via OTA. But I was getting error message.
I didnt install any recovery. I just rooted my phone via vroot.
Sent from my C5502 using xda app-developers app
soorajskn said:
I too rooted my phone nd tried to update the phone via OTA. But I was getting error message.
I didnt install any recovery. I just rooted my phone via vroot.
Sent from my C5502 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the confirmation. I know for sure you can update through PCC as I did for another phone. I too rooted using vroot. Anyone else with other rooting method pls share the result.
I had the same problem! (Got root via bootloader unlock)
Mine also got problem cannot update my ZR. my ZR also root and boatloader still lock. If hard reset can solve the problem or not?
Just try this
Hi, sorry for my bad english
You should try this, you can get root and the latest version (locked/unlocked bootloader)
I got my with this metod, really working and no bug (only the original bugs from Sony
http://forum.xda-developers.com/showthread.php?t=2655893
In another thread a possible solution for this problem was mentioned: if you have renamed or deleted some original files (like system apk's or some other protected files) the upgrade routine recognizes it and stops the upgrade process.
In my case the problems were caused by removed apps, when I restored them, everything worked flawlessly.
wihushae said:
In another thread a possible solution for this problem was mentioned: if you have renamed or deleted some original files (like system apk's or some other protected files) the upgrade routine recognizes it and stops the upgrade process.
In my case the problems were caused by removed apps, when I restored them, everything worked flawlessly.
Click to expand...
Click to collapse
Well did hard reset and remove the root yesterday on my zr then update thru Ota still fail.
I have 3 apps that when I try to download (after flashing a rom) that give me an "unknown error code during application install -505"
Thoughts?
I've cleared cache and data and forced stopped the play store...
I've checked to see if any folders or files are in root or in data/data and I found some and deleted but nothing. Still won't download.
CCJ22 said:
I have 3 apps that when I try to download (after flashing a rom) that give me an "unknown error code during application install -505"
Thoughts?
I've cleared cache and data and forced stopped the play store...
I've checked to see if any folders or files are in root or in data/data and I found some and deleted but nothing. Still won't download.
Click to expand...
Click to collapse
i had one that got that code. what i did to fix this is i found that app using google(not play store), installed it that way, then uninstalled it via the pkay store, then reinstalled it in the play store.
Yea I'm getting that problem with Terminal Emulator for Android by Jack Palevich. Not sure what the deal is. Aggravating since ROM Toolbox Terminal FC, and another that I've tried. Rastapop with leanKernel.
Last time that happened to me I fixed it by using Root Explorer (any file manager with root access should work tho) and deleted the "com.appname......" file from data/data partition from system root level, not SD.
Then went back to Play Store and installed fine.
via OnePlus or N5
truckroot said:
Last time that happened to me I fixed it by using Root Explorer (any file manager with root access should work tho) and deleted the "com.appname......" file from data/data partition from system root level, not SD.
Then went back to Play Store and installed fine.
via OnePlus or N5
Click to expand...
Click to collapse
I found the location, but not the app that supposedly downloaded and didn't install. App is Terminal Emulator by Jack Palevich.
saddog5523 said:
I found the location, but not the app that supposedly downloaded and didn't install. App is Terminal Emulator by Jack Palevich.
Click to expand...
Click to collapse
Look for jackpal.androidterm file?
via OnePlus or N5
simms22 said:
i had one that got that code. what i did to fix this is i found that app using google(not play store), installed it that way, then uninstalled it via the pkay store, then reinstalled it in the play store.
Click to expand...
Click to collapse
I tried that but the outsourced .apk didn't install. It said error. Tried 3 other sources. Same problem.
saddog5523 said:
Yea I'm getting that problem with Terminal Emulator for Android by Jack Palevich. Not sure what the deal is. Aggravating since ROM Toolbox Terminal FC, and another that I've tried. Rastapop with leanKernel.
Click to expand...
Click to collapse
Man I'm sorry. I know the feeling. Is yours a -505 error #?
truckroot said:
Last time that happened to me I fixed it by using Root Explorer (any file manager with root access should work tho) and deleted the "com.appname......" file from data/data partition from system root level, not SD.
Then went back to Play Store and installed fine.
via OnePlus or N5
Click to expand...
Click to collapse
Tried that. Still the problem remains.
CCJ22 said:
I tried that but the outsourced .apk didn't install. It said error. Tried 3 other sources. Same problem.
Man I'm sorry. I know the feeling. Is yours a -505 error #?
Tried that. Still the problem remains.
Click to expand...
Click to collapse
Yes, it's a -505 error. That's the only app I've had that problem with, though I don't download too many. I just want a terminal app to use with leanKernel so I can access lkconfig. I am thinking it might have something to do with me being on rastapop which is 5.0.1, what version and/or ROM are you using?
@saddog5523 I'm on euphoria beta, about to dirty flash to the latest version 1.0 off beta.
This -505 sucks...
had this happened a few days ago. had to restore a twrp backup. in mycase, it was some frozen/degreenified app
stas333 said:
had this happened a few days ago. had to restore a twrp backup. in mycase, it was some frozen/degreenified app
Click to expand...
Click to collapse
I have no twrp backup of the play store or my apps.
Strangely the download happens from the play store, it's the install that hoses up. Making me think I have some file somewhere shettin bricks on the install.
I feel like I've tried everything.
Well. My main issue was with Terminal Emulator for Android by Jack Palevich. I clean flashed the new 5.0.1 and wiped/factory reset my device. Still had the same 505 error. It was crazy aggravating. I Google'd it to see if anyone else had the same issue, and found out that it was a permissions issue: http://android.stackexchange.com/qu...deal-with-unknown-installation-error-code-505
Every time I tried to access the baked in terminal emulator within Rom Toolbox Lite, it would force close the app. I got aggravated at Rom Toolbox Lite and uninstalled it, and while I was in the play store, decided to try Terminal Emulator for Android again. This time it worked. I uninstalled Terminal and installed Rom Toolbox Lite to test my new theory, and found that the two apps do not play well with each other for some reason. Even when I try to install Rom Toolbox Lite after I already have Terminal installed, it would give me the same 505 error. Apparently I can have one or the other, which honestly makes no sense at all.
I'm guessing that error could be fixed (possibly) by uninstalling applications that have the same feature. i.e. Terminal Emulator for Android and Rom Toolbox Lite. One of the apps you have installed might be causing the error in trying to install another app. Hope this helps someone with the same issue.
@CCJ22 @simms22 @truckroot @stas333
saddog5523 said:
Well. My main issue was with Terminal Emulator for Android by Jack Palevich. I clean flashed the new 5.0.1 and wiped/factory reset my device. Still had the same 505 error. It was crazy aggravating. I Google'd it to see if anyone else had the same issue, and found out that it was a permissions issue: http://android.stackexchange.com/qu...deal-with-unknown-installation-error-code-505
Every time I tried to access the baked in terminal emulator within Rom Toolbox Lite, it would force close the app. I got aggravated at Rom Toolbox Lite and uninstalled it, and while I was in the play store, decided to try Terminal Emulator for Android again. This time it worked. I uninstalled Terminal and installed Rom Toolbox Lite to test my new theory, and found that the two apps do not play well with each other for some reason. Even when I try to install Rom Toolbox Lite after I already have Terminal installed, it would give me the same 505 error. Apparently I can have one or the other, which honestly makes no sense at all.
I'm guessing that error could be fixed (possibly) by uninstalling applications that have the same feature. i.e. Terminal Emulator for Android and Rom Toolbox Lite. One of the apps you have installed might be causing the error in trying to install another app. Hope this helps someone with the same issue.
@CCJ22 @simms22 @truckroot @stas333
Click to expand...
Click to collapse
Thanks I will have to try this tonight.
Are you running 5.0.1 ? I had this issue with an app when I first got my phone and with some research found out the problem was apparently fixed in the 5.0.1 OTA, well it fixed it for me. This is one of the changes that fixes it.
cupfulloflol said:
Are you running 5.0.1 ? I had this issue with an app when I first got my phone and with some research found out the problem was apparently fixed in the 5.0.1 OTA, well it fixed it for me. This is one of the changes that fixes it.
Click to expand...
Click to collapse
I've got 5.0.1 and am still having this issue installing GTasks. Does anyone have a solution?
carrot34 said:
I've got 5.0.1 and am still having this issue installing GTasks. Does anyone have a solution?
Click to expand...
Click to collapse
Are you running the stock ROM?
The problem is explained here in more detail. You basically have to uninstall whatever is conflicting with the app install. A logcat should be able to tell you where the conflict is.
cupfulloflol said:
Are you running the stock ROM?
The problem is explained here in more detail. You basically have to uninstall whatever is conflicting with the app install. A logcat should be able to tell you where the conflict is.
Click to expand...
Click to collapse
Thanks. Yes, I'm running the stock ROM and not rooted. It's basically just out of the box and with the 5.0.1 OTA update. The conflict is between Pure Calendar Widget and GTasks. If I uninstall one app, the other will install. But if I try to install _both_, I get the 505 error. Is there any way around this? The post you linked to says that this has been fixed in 5.0.1, but it doesn't look like that to me.
Thanks!
Alan
carrot34 said:
Thanks. Yes, I'm running the stock ROM and not rooted. It's basically just out of the box and with the 5.0.1 OTA update. The conflict is between Pure Calendar Widget and GTasks. If I uninstall one app, the other will install. But if I try to install _both_, I get the 505 error. Is there any way around this? The post you linked to says that this has been fixed in 5.0.1, but it doesn't look like that to me.
Thanks!
Alan
Click to expand...
Click to collapse
I honestly think it's something either the developers will have to work out in a new version of their app, or Google will have to fix in a new phone update. Whichever comes first. 5.0.1 was supposed to fix it, but like you and I and others have noticed, it's still a problem. You're just going to have to use one or the other for now.
so, what you're saying is we're pretty much SOL until it is actually fixed...
the thing is, google is saying they fixed it on 5.0.1
if it's not actually fixed then people who can report it, should report it...
I do not have the permissions or "prestige" to post on StackOverFlow or code.google.com to say that the bug has not been fixed...
Hi all, I'm having the classic issue of Titanium Backup getting hung up at 0% when restoring on the N dev preview. I flashed supersu beta 2.71 and have busy box installed. I also have allowed installation from unknown sources, have enabled USB debugging, and disabled mount namespace separation in supersu. I'm all out of ideas and I really need to restore this foshiz. Any help would be appreciated. (This is a nexus 6 of course).
I've never like titanium backup with my Nexus 6. Always had problems. My g2, droid, Gnex, etc all loved it.
Anyways, my guess is either selinux (check and set for permissive), or titanium just isn't compatible with Android N currently (highly likely as android N is just a preview to let developers see what they're working with)
I'm not on N but when I switched from L to M I got the same problem.
What always worked for me was using the update.zip method.
You create it in TitaniumBackup out of your saved apps + data and flash it after you're on N via TWRP.
TB can have problems installing some apps, and get stuck, but if you install that app from Play, it will continue. I recommend you let Google install the apps, then use TB to install data.
Sent from my Nexus 6 running cyosp using Tapatalk
The same issue, but with Marshmallow and Samsung s7 edge..
@RatchetPanda has a mod that allows for restoring apps on N
http://forum.xda-developers.com/nexus-6/development/rom-stock-flashables-t3348657
SageWilliams said:
@RatchetPanda has a mod that allows for restoring apps on N
http://forum.xda-developers.com/nexus-6/development/rom-stock-flashables-t3348657
Click to expand...
Click to collapse
Yes it works, thanks to Aroma you can even flash it, disable all the extras that you don't want and TBU will work.
People post about issues yet leave out any sort of log that will tell what the issue is. This is one of the biggest issues developers have with users. This is why most developers will not reply to issues and almost never come in the Q&A section
If you are gonna post about issues then make sure to do your homework first. Get logs and post them. Try to figure it out for yourself before asking for help. This is not a support forum.
adambombz said:
Hi all, I'm having the classic issue of Titanium Backup getting hung up at 0% when restoring on the N dev preview. I flashed supersu beta 2.71 and have busy box installed. I also have allowed installation from unknown sources, have enabled USB debugging, and disabled mount namespace separation in supersu. I'm all out of ideas and I really need to restore this foshiz. Any help would be appreciated. (This is a nexus 6 of course).
Click to expand...
Click to collapse
You might wanna try changing "app processing mode" in preferences, indirect method may help and interactive will install apps using the standard installer if all else fails.
On a related note I'd highly recommend backup+ I've started using it for specifically backups between roms and it worked for me perfectly on N. The app was built with the SELinux changes in mind as one of the first apps to work with restoring apps on Lollipop and I'd guess it has a bit to do with it working for Marshmallow and N w/o needing updates during the previews. It probably won't replace TiBup if you use it for stuff like freezing apps and whatnot. (It is capable of doing system apps, wifi, SMS, and phone logs though it's a separate in-app purchase totaling 2.61USD).
istperson said:
TB can have problems installing some apps, and get stuck, but if you install that app from Play, it will continue. I recommend you let Google install the apps, then use TB to install data.
Sent from my Nexus 6 running cyosp using Tapatalk
Click to expand...
Click to collapse
dude you just saved me from reverting to marshmallow
bhavstech said:
dude you just saved me from reverting to marshmallow
Click to expand...
Click to collapse
Glad I could help!
So after getting my replacement N910T, I rooted it using the method here, and it seemed to go well, but during the process of reinstalling apps, I noticed some erratic behavior like the device not allowing root access when root checker says it is rooted. Or SuperSu not asking for SU access on apps that normally do, thereby denying root access, like Root Explorer. When I go back and check root checker again, sometimes it shows that it has access and other times it says that it doesn't. For a device with a supposedly unlocked bootloader, I've never encountered so many issues. My AT&T S4 which has a locked BL never gave me any issues once it was rooted. With all the devices I've rooted over the years, I've never had this much trouble. So I'm wondering if it's corrupted somehow? Or is there something about this systemless root that is the issue?
Here are the basics:
Android 5.1.1
Baseband OK2
Kernel Version 3.10.40-6209177
Build Number LMY47X.N910TUVU2DOK2
I've read threads until I'm crosseyed and googled but couldn't really come up with anything, so I could use some help here.
I had the same problem with a Note 4 Tmo I am working with. What SuperSU version are you using?
I had root issue problems (root chk says rooted, issues in ES File Expl, etc) when I used anything higher than 2.65.
Try flashing SuperSU 2.65 stable through recovery (I use TWRP 2.8.?.?) and when exiting out of recovery DO NOT allow SuperSU to be installed as SuperSU installation says...
Thanks much for the response. I'm using SuperSu 2.71; I didn't choose this version, it came with the root I got from here. So where do I find this version you're referring to?
Sent from my iPad using Tapatalk
Hi have you figured out your issue yet. If not, Try using supersu 2.52. It's the last full system root I believe. I have had much better luck with full system than systemless.
noob4598 said:
Hi have you figured out your issue yet. If not, Try using supersu 2.52. It's the last full system root I believe. I have had much better luck with full system than systemless.
Click to expand...
Click to collapse
I haven't tried anything else yet, I giving my head some time to clear. I've been at this for hours now, so I need a rest. Can I find that version of SuperSu as a flash able zip?
I used the links from Chainfire's thread on XDA
http://forum.xda-developers.com/showthread.php?t=1538053
Download to stable 2.65 is in that thread points to this link:
https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
https://download.chainfire.eu/743/supersu this is link to 2.52 zip if u need it
Thanks for all the help, I'm glad this happened to someone other than me. One thing though: I'm on OK2, I thought you couldn't have system root with that.
Sent from my iPad using Tapatalk
Okay, the installation of supersu 2.52 via TWRP has definitely made a difference! The device is noticeably stabler now. One last thing, though: root checker shows it's rooted, but says that a superuser app isn't installed, which is what I thought supersu was. So now what?
Did you flash over 2.71. And do you have a su app icon on your scrren.
noob4598 said:
Did you flash over 2.71. And do you have a su app icon on your scrren.
Click to expand...
Click to collapse
Yes, I just flashed it from TWRP without doing anything else. And no, there isn't a Su app icon on the screen. I have a nandroid backup that'll put it back to the way it was before I did that, just in case it crashed and burned.
Download the app from playstore and then go to settings and do a full unroot. Then reboot to recovery and flash 2.52 then wipe cache and dalviche and reboot
MUCH BETTER!!! I'm in the process of reinstalling all of my apps; I don't want to take a chance of restoring my backup from Titanium, just in case there's something that won't play right.
I'll report back in a day or so.
Thanks to everyone who provided answers, it is most appreciated!
Welcome bud.
Thank you for the information guys. I was having the same issue as OP. Reverted SU as described and everything is much smoother
Yes, it's been a few days and my device is working the way it is supposed to. Interestingly enough, my SuperSU has automatically updated to version 2.65 but it's still working fine.
I've since turned off automatic updates in Google Play for fear of getting a version that begins the cycle all over again.
I still have the issue with the device telling me that the recovery is not seandroid enforcing even though I've updated to TWRP 3.0, and the set warranty bit: kernel issue. In spite of these, my device seems to work just fine with no issues.
Thanks again to everyone who offered help. It's nice when people offer help instead of posting just to tell you to find the answer yourself.
Sent from my SM-N910T using Tapatalk
Your welcome. And I get kernel is not seandroid enforcing on every reboot. Thought it was normal ha
My research on this has taken me all over the place, but none of the suggestions or explanations seem to apply. The device isn't ostensibly crippled, so I don't know.
Sent from my SM-N910T using Tapatalk
I think it's normal...maybe...ha Im pretty sure it's the warranty bit
are there root for N910A 5.1.1