Is anyone else experiencing issues with core.jar modifications with lucky patcher? Phone says "please wait..." for a couple of minutes, reboots as if it was successful, but upon reboot the patches display as "Not Patched" still. Wondering if anyone had a fix for this or is this just a known issue.
*I have the latest SU binary installed and the latest busybox as well.
This is on a Verizon S6.
Thanks!
I think that you need to use a deodexed rom, because Lucky Patcher modifies the files. Maybe try to create an odex file in lucky patcher after modifying the .jar
I just tried that and it didn't seem to work. Same thing happens - Phone completes operation, reboots, and nothing has changed.
Does anyone have any thoughts on this?
I have this issue too, I've tried on both deodexed and odexed roms and I have no idea how to fix it...
Any other thoughts? I really need to sort this out.
I sent an email to Chelpus about this issue, no response after a week...
Last attempt at salvation: does anyone know how to fix this issue?
Having the exact same issue regarding core.jar. Patched a game and it works perfectly, just cannot patch core.jar. Phone restarts, still says "not patched" on the first two options in "Patch to android". Doing my brain in.
same thing here!
is it the problem of KNOX?
Lucky Patcher is warez.
Warez are NOT allowed on Xda. Not even for discussion.
Thread closed.
Thank you.
Related
[Hopefully I didn't miss this being covered somewhere else, as I am much the same as many of you and get beyond irritated with endless repeat questions. I searched using the best keywords I could think of for the issue, but to no avail. Apologies in advance if this has been covered!]
Alrighty. I've got a TF101, rooted it myself (thank you XDA), running 8.6.5.1.9 i believe, stock rom just with root. Used nvflash and Razorclaw. Worked like a charm.
It's been fine for the last 6 months, no issues. However, I decided to update busybox using its internal updater as I have before with no problems. I noticed I accidentally told it to install to /system/bin instead of /system/xbin, and the only reason I even knew about that was due to having to configure an app to find busybox in /xbin instead of /bin.
Now there's a problem. I can still access the internal virtual sd card, but that's about it. The device can't seem to read or write to the main directory (although it can deal with going DIRECTLY to /mnt/sdcard). Ghost commander can't view the main directory, but ESFile explorer _can_, although root browsing in ESFile Explorer is UNchecked. It shouldn't be able to do what it's doing, and it's only doing it in one of two apps.
As a result, I've got no access to any root apps obviousy, but the wifi is having issues as well, it tries connecting but it can't complete the connection.
I'm toying with just wiping and flashing a new rom entirely, but figured I'd ask before I jump in the deep end of things. I keep backups of stuff, but it's still such a pain in the ass reinstalling things.
Any suggestions? I have a feeling it's something "simple", a link file or ... something which linux gurus would know about and I would not, not being a guru or disciple myself.
Thanks in advance!
If only you have working CWM installed. You could just flash this Superuser3.0.7.
Ah, but the plot thickens. I had superuser on there. I even uninstalled and reinstalled it. No dice.
Update: I said fuggit and did a factory reset. However, my wifi is still not fully connecting to my network although it has no problem finding it. I don't have a recovery image on the external SD and unless i get the network working, will have to wait until tomorrow to get a working microsd->usb adapter to put it on there.
I CAN still get into CWM, thank god.
Current rom is stock 8.6.6.19
Razorclaw gives an error when trying to root.
Also, when trying to moust USB from the recovery menu. it fails, saying "E:unable to upen ums lunfile (no such file or directory).
I am hoping this will magically get fixed after re-installing stock from the SD card ... and that my device isn't somehow crippled.
Sorry for the massive details, but more data = better.
It will magically get fixed
I recommend you flash any Totally stock ota. Then upgrade to the latest OTA, then use my tool PERI (or another) to install recovery and root. Then you should be all fixed up.
Well, it looks like I did get things back on track, but oddly enough, neither of the standard OR modified for root stock ROMs would work. One just wouldn't install, another failed halfway through. MD5s checked out and everything. I had put Revolver 4 beta on there sort of as a "just in case", and that one installed fine (and I was pleased when it displayed "installing Busybox symlinks").
Phew. CLose close call. Now to deal with the bull**** of setting stuff back up again.
However, the question remains: I'm assuming this whole thing happened because of the busybox update and me accidentally installing it to /bin instead of /xbin, and I think it "cleaned up" its own symlinks or something.
I'm not saying don't update your busybox, although I'm sticking with what works and **** upgrading anymore, just be careful...
Thanks for the help!
Recently I used the busybox installer to update my busybox version and it went through great... but after reboot it reverted back to the old version.. And I never touch it since.. don't want to take the hassle further..
There are certain 'plague' versions of busybox that simply don't work. I'd find that list of working BBs and STICK with one that's good. I'm still on 1.63 or someat like that.
Mangraa said:
[Hopefully I didn't miss this being covered somewhere else, as I am much the same as many of you and get beyond irritated with endless repeat questions. I searched using the best keywords I could think of for the issue, but to no avail. Apologies in advance if this has been covered!]
Alrighty. I've got a TF101, rooted it myself (thank you XDA), running 8.6.5.1.9 i believe, stock rom just with root. Used nvflash and Razorclaw. Worked like a charm.
It's been fine for the last 6 months, no issues. However, I decided to update busybox using its internal updater as I have before with no problems. I noticed I accidentally told it to install to /system/bin instead of /system/xbin, and the only reason I even knew about that was due to having to configure an app to find busybox in /xbin instead of /bin.
Now there's a problem. I can still access the internal virtual sd card, but that's about it. The device can't seem to read or write to the main directory (although it can deal with going DIRECTLY to /mnt/sdcard). Ghost commander can't view the main directory, but ESFile explorer _can_, although root browsing in ESFile Explorer is UNchecked. It shouldn't be able to do what it's doing, and it's only doing it in one of two apps.
As a result, I've got no access to any root apps obviousy, but the wifi is having issues as well, it tries connecting but it can't complete the connection.
I'm toying with just wiping and flashing a new rom entirely, but figured I'd ask before I jump in the deep end of things. I keep backups of stuff, but it's still such a pain in the ass reinstalling things.
Any suggestions? I have a feeling it's something "simple", a link file or ... something which linux gurus would know about and I would not, not being a guru or disciple myself.
Thanks in advance!
Click to expand...
Click to collapse
You may have been hit with a bug I introduced.
There was a bug with version 8.0 of my application.
There is not an issue with Busybox V1.20.1.
I apologize for this bug, the application symlinked all applets to Busybox and on some devices there are applets which are unique to the device and should not be replaced by those offered by Busybox.
A simple way to fix this is to simply reflash your rom. You do not need to wipe or clear any data. This will fix the issue and you can update Busybox normally with my application as long as it is version 8.1 or higher.
I apologize for the frustration I have caused, please let me know if I can do anything to help you further. I am trying to find people who were affected to see if I can help rectify the situation.
yeah me too
I guess I should have done a more recent backup. I tell you, there is a reason i have 38 updates waiting, everytime I start going through them, boom blows up in my face
Hi! I recently upgraded to CM11 alpha build from CM10 and I must say that almost everything is perfect. But I have been having one problem. I can't seem to install APK files. I downloaded AdBlock Plus and when I tapped on the download to install it, it came up with an error, "Parse Error. There was a problem parsing the package." I know that CM11 is an alpha build and stuff, and that it most likely is due to a glitch with that, (so don't yell at me), but I was just wondering if anyone knew a quick answer to this problem. I have tried many different APK's even those that don't require root. All get the same error. I know it's not a KitKat issue because I have a friend with a Nexus 5 who is running AdBlock Plus fine. It's probably a CM11 error, but all the same I was just wondering if anyone knew anything about it.
Thanks in advance!
P.S. I have already spent an hour or more on Google looking for a solution and have found none that work. Common ones are "Enable unknown sources" and "Get the latest version" both of which I have done and don't work.
RewinX said:
Hi! I recently upgraded to CM11 alpha build from CM10 and I must say that almost everything is perfect. But I have been having one problem. I can't seem to install APK files. I downloaded AdBlock Plus and when I tapped on the download to install it, it came up with an error, "Parse Error. There was a problem parsing the package." I know that CM11 is an alpha build and stuff, and that it most likely is due to a glitch with that, (so don't yell at me), but I was just wondering if anyone knew a quick answer to this problem. I have tried many different APK's even those that don't require root. All get the same error. I know it's not a KitKat issue because I have a friend with a Nexus 5 who is running AdBlock Plus fine. It's probably a CM11 error, but all the same I was just wondering if anyone knew anything about it.
Thanks in advance!
P.S. I have already spent an hour or more on Google looking for a solution and have found none that work. Common ones are "Enable unknown sources" and "Get the latest version" both of which I have done and don't work.
Click to expand...
Click to collapse
Its a bug. Problem is already known about
Sent from my SGH-I727 using Tapatalk 2
Smittiegee19 said:
Its a bug. Problem is already known about
Sent from my SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Okay, thanks for responding! I had a feeling, there are always gonna be bugs with bleeding edge builds. Thanks again!
RewinX said:
Okay, thanks for responding! I had a feeling, there are always gonna be bugs with bleeding edge builds. Thanks again!
Click to expand...
Click to collapse
It is definitely fixed, but there has not been a release with the fix yet. The workaround is to use a file manager (the built in CM one will work) to copy the apk to somewhere like /data, set the permissions to rw-r--r--, and install from there, then delete the apk.
rpr69 said:
It is definitely fixed, but there has not been a release with the fix yet. The workaround is to use a file manager (the built in CM one will work) to copy the apk to somewhere like /data, set the permissions to rw-r--r--, and install from there, then delete the apk.
Click to expand...
Click to collapse
Thanks! I moved it to /data and set perms and it worked just like you said. Huge kudos. Will look forward to it being easier in next update.
Glad I could help. I believe it was mentioned in the CM11.0 Alpha General Discussion thread as well.
Hi all,
New to the forums and to android dev... your help and patience much appreciated. Made (hopefully) good faith effort to track down an answer, but no luck yet...
2 (related?) questions on Motorola Ultra root (4.4 KitKat):
On the adb side, having issues with signature/certs.
Using original mymoto apk from jcase's post...
I initially get INSTALL_PARSE_FAILED_NO_CERTIFICATES
I create key, run jarsign and zipalign per Android dev instructions (referred there from suggestions on stackoverflow).
This appears to successfully add signature, but then on install I just get parse failed inconsistent certs.
Most of the suggestions I've seen for inconsistent certs revolve around uninstalling the app... but since I haven't successfully installed to begin with, not sure if that applies. (Indeed, running pm list packages in adb shell, I don't see anything that looks like PwnMyMoto to uninstall).
Any thoughts much appreciated.
Secondly, I also tried to download apk direct to phone from web, and the message on install (attempt) was rather interesting:
"PwnMyMoto
Do you want to install an update to this built-in application? Your existing data will not be..." etc.
(When attempt to install, simply comes back: "App not installed").
The 'built-in application' part seemed strange to me, and I haven't found reference to it in forums. Assume this has something to do with the fact that PwnMyMoto takes over existing recovery boot function of the native system? Is this message unique / does it imply any additional workaround to uninstall existing packages?
(Saw the X has moved from PwnMyMoto to RockMyMoto... but haven't seen any similar updates on the Ultra side. If I've missed it please let me know).
Thanks for any help!
shen
I'm new here as well, with an unrooted verizon ultra 4.4. From what I can see now, the certificate issue is because the PwnMyMoto apk is relying on a previously rooted phone. It appears there is still a bounty for a stock root procedure.
Hopefully someone more experienced can chime in as if this is indeed the state of things.
aletoledo said:
I'm new here as well, with an unrooted verizon ultra 4.4. From what I can see now, the certificate issue is because the PwnMyMoto apk is relying on a previously rooted phone. It appears there is still a bounty for a stock root procedure.
Hopefully someone more experienced can chime in as if this is indeed the state of things.
Click to expand...
Click to collapse
Ah, okay. That puts a few things I read in other posts into place. Unfortunate. Was reading up on SlapMyMoto as a solution for those who already took the OTA for 4.4, but I think it's a similar situation... you can only perform the downgrade to 4.2 required to load SlapMyMoto if you already have a rooted device (from what I can tell). Not a solution for a stock 4.4.
Here's the new Pandora update it hasn't been released yet....
https://mega.co.nz/#!Q54BWA5Q!96NsfszBXf94OIKA0sXwRKEtGBbqtHa1ruCTnMq7JK4
Nice! Thank
Strange, same versions as me. I've installed it, enabled it in xposed, rebooted, changed the thumbs up option, made sure the download location is fine, enabled the prompt to download, rebooted etc etc.... Yet when I press thumbs up it just doesn't work. That's why I tried the logcat, but I see nothing obvious in there to describe any errors.
Think I'll uninstall and start again
Can somebody please tell me how i can get this? Im kind of new to the whole LG G3 rooting scene like i got it rooted but idk what I need in order to get this. I have a LG G3 VS985 by the way
Just an FYI... Previous threads that have included discussions of Pandora Patcher (a module that violates both XDA's rules and was banned from the Xposed repo as it's considered warez) have either been locked or thoroughly cleaned. If you're going to discuss this mod I'd suggest doing so via PM so as to not draw the attention of a moderator and get yourself in trouble.
THIS^^^
Any discussion about circumventing a paywall is considered warez discussions and will NOT be tolerated here.
Thread cleaned.
mjb152 said:
strange, same versions as me. I've installed it, enabled it in xposed, rebooted, changed the thumbs up option, made sure the download location is fine, enabled the prompt to download, rebooted etc etc.... Yet when i press thumbs up it just doesn't work. That's why i tried the logcat, but i see nothing obvious in there to describe any errors.
Think i'll uninstall and start again
Click to expand...
Click to collapse
patcher doesn't work with this version.
Hi all
I recently unlocked my phone, installed twrp, all that good stuff. On stock firmware atm
However, when I try to download and apply inside AdAway it doesn't work, and it says something about not being able to copy the host files. I'd attach a link to a picture but my account is new so I'll write it out. Here it is-
Code:
Copy failed
Copy of hosts file failed!
Please read Help for more information.
And when I flash viper it installs, however it doesn't actually work, as in the audio doesn't sound any different.
Also I forgot to put in the title, magisk doesn't work either. It has an error code 1 or something, once again I'd attach a picture but I can't.
By the way I have root through flashing supersu
Has anyone else run into these issues, and if so were you able to fix them? Thanks in advance.
Additional thing I just remembered to add- I tried AICP yesterday, however the headphone jack didn't work, regardless of if I was using viper or not. I'm gonna reflash it now and post my results see if that was just a fluke.