yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] mateorod:
Okay, I don't know what is going on...I know some users have problems with ApG from time to time. I don't have Windows so I cannot debug it. But there must be some corruption somewhere. Very frustrating.

I just downloaded the cm-10.1-20130702-NIGHTLY-d2att.zip from get.cm and it patched perfectly. Will you just delete your ApG folder and reinstall? I am sorry I cannot give you any more technical advice than that...but your rom is patchable.

If it still fails, I will get the patched zip in your hand somehow. But I would like to fix the actual problem so that you are free to update on your own schedule.
[Android Software/Hacking General [Developers Only]] SirGeraint:
This is strange then. I just downloaded 07/02 from get.cm. I generally download from http://jenkinsmanifest.clockworkmod.com/device/d2att/all but they should be the same. I unzipped autopatcherv2.9.89.zip to a different drive/dir but I still get the same error.

Once when I had a problem in the past I setup one of my Linux systems to do the patching. I am trying to find where I had it. It might have been in /tmp so I may have to set it up again.

I would appreciate the patched zip but wouldn't want you to go to too much trouble. Maybe we'll figure this out soon. I will keep you posted.

Thanks...
[Android Software/Hacking General [Developers Only]] DualJoe:
[MENTION=2918890]SirGeraint[/MENTION]:

Can you post the log?
[Android Software/Hacking General [Developers Only]] SirGeraint:
It was the same as my previous post.

---------- Post added at 11:06 AM ---------- Previous post was at 11:00 AM ----------

Mateor,

I've got some good news. It works in Linux (Fedora 17). I started with the v2.9.895 that I got from github and it updated itself to v2.9.9 and succeeded. So I am good now.

I do prefer to use Auto-Patcher in Cygwin on my Windows laptop since it's right here in front of me. That way I don't have to transfer files back and forth between my Linux system. So I hope you do eventually find the issue.

Thanks...
[Android Software/Hacking General [Developers Only]] mateorod:
I am glad it worked...unfortunately I do not have the ability to update or fix ApG, as I didn't write it and do not have access to it's source code. But generally speaking, it periodically stops working for some people for unknown reasons...it only happens on ApG. The solution, pretty universally, is to complete delete ApG and redownload the entire folder. I know that can be a hassle.

I would have uploaded the zips for you, but I am glad you got it to run because I want users to be able to update their roms themselves, without waiting for someone else...it is why I made the program in the first place.
[Android Software/Hacking General [Developers Only]] DualJoe:
The log is not the shell output. Its a separate file called like this: log20130702184548.txt. I'm wondering if you have all 'Hunks failed' as well on framework patches. Are you also on a 32bit system?
[Android Software/Hacking General [Developers Only]] SirGeraint:
Ahh, gotcha. I wasn't thinking about those. I have attached the latest log. Looks like I do have a lot of those "3 out of 3 hunks failed" errors.

My errors were on my laptop currently booted to 64-bit Windows 7 and running Cygwin.
[Android Software/Hacking General [Developers Only]] DualJoe:
Thanks. Looks like we are in the same boat indeed. My log is identical with that framework error and that many failed hunks.

I've taken a first look on the reject files. Looks all ok. The question is why it was rejected/not accepted even though all data is fine. I suspect an environmental/localization issue or incompatible (patch) binary. Will take a further look later... I will let you know if successful.
[Android Software/Hacking General [Developers Only]] bone101:
I've tried it many times and there is always the same error.....:(

Also after update.... :(

MB525 red lens
[Android Software/Hacking General [Developers Only]] gps3dx:
Hi,

On my Nexus 7 I use SmoothRom v5.2 which is a AOKP based rom.

I managed to make the UPDATE.zip usin autopatcher v2.9.89 through the use of the terminal in ApG v2.6.0.2.

When I try to install the ZIP using TWRP or CWMR I get:

E:Error executing updater binary in zip....
Error flashing zip....

What did I do wrong ?:confused::confused:

I Even try in another time, changing the ZIP filename and put it directly on /sdcard when I try to install - still get that fraking error.:(:crying:

EDIT:

:

I tried to compile the UPDATE.zip from ubuntu so no ApG was used.

Again I got the zip successfully, but I can't install the zip on the device !

What is wrong in the latest autopatcher v2.9.89 ?
[Android Software/Hacking General [Developers Only]] DualJoe:
'Patch' 2.7.1-1 binary (cygwin) incompatible

[MENTION=4342828]mateorod[/MENTION] [MENTION=3433885]kobik77[/MENTION] [MENTION=4418789]Urinophoria[/MENTION] [MENTION=2918890]SirGeraint[/MENTION]

Incompatible 'patch' binary indeed. 'Patch' 2.7.1-1 is the culprit. Looks like Cygwin bumped 'patch' from 2.6.1-1 to 2.7.1-1 recently that is incompatible to auto-patcher 2.9.9. The old version (2.6.1-1) is still available (optionally) through Cygwin installer though.
[Android Software/Hacking General [Developers Only]] mateorod:
We need the autopatcher log...without your log, I can't tell you what is going on. But generally speaking, we don't really modify the updater-script. It is basically copied straight over. If you could link to a paste of your rom's updater script, that would help as well. Post your device, a link to the rom and the autopatcher log. I usually don't need anything but the log, but updater scripts issues can come from a lot of places.

That is a great find...you are good on error-checking these issues and always have your research done. I guess the best thing to do is to find out what the changes were and then modify the script...the easiest thing would be to specify which patch in ApG, but I believe ApG is in it's final form.

Thanks DualJoe

Edit

I can take a quick look, but I am not sure what I can do...if the smali binaries cannot recompile that rom's system apps, then it is probably unpatchable. I will look and see if you posted a link to the rom...if you did not will you do so now?
[Android Software/Hacking General [Developers Only]] DualJoe:
I don't know if ApG is affected at all though since i haven't used it (i've set up my cygwin environment manually) but if its auto updating cygwin, then it will be. If it's a general 'patch' binary issue linux users should be affected as well if their distribution updates to that binary.

I will take another look on the new 'patch' binary issue later to see what's wrong...
[Android Software/Hacking General [Developers Only]] Draygon:
Could someone tell me how I patch SlimBean 6.9 for my Nexus 7 with Openpdroid, please?
[Android Software/Hacking General [Developers Only]] badaeng:
thank you so much for fixing pa for samsung, I can return to sleeping peacefully now.:victory:
[Android Software/Hacking General [Developers Only]] gps3dx:
Seems that these next lines are the one that causes the problem when I try to install the UPDATE.zip in recovery:

( these files/folders are NON existent in my system )

set_perm_recursive(0, 0, 0755, 0755, "/system/modules");
set_perm(0, 0, 0755, "/system/bin/fix_permissions");
set_perm(0, 0, 0755, "/system/addon.d/70-gapps.sh");

After I removed these lines from the "updater-script" and updated the ZIP file, I get no errors, and installation goes fine.

I installed and run openpdroid with any problem so far.
[Android Software/Hacking General [Developers Only]] jamus28:
Hey I'm getting an error applying a tabletUI patch even with the latest github syncs. How can I see a more detailed report of what code failed to patch? The log says:

1 out of 1 hunk FAILED -- saving rejects to file smali/com/android/internal/policy/impl/PhoneWindowManager.smali.rej

!!! PATCHING FAILED FOR com/android/internal/policy/impl/PhoneWindowManager.smali !!!

but I don't see where the rejects file is saved. How can I output the rejects file?
[Android Software/Hacking General [Developers Only]] DualJoe:
[MENTION=4342828]mateorod[/MENTION]:

What i can tell is that the new 'patch' binary 2.7.1 (compared to 2.6.1) now honors EOLs (End of lines CR/LF<>LF. That's intended - not a bug). The problem is that the JavaVM creates different EOLs on different platforms resulting in baksmali.jar producing different files. Since you are creating LF diffs and get LF smali's on Linux you will never be affected. Windows users instead will get CR/LF smali's that are not compatible to the LF diffs with 2.7.1 patch binary. They will be rejected all.

Using the old binary on Windows should be sufficient for now. If this ever will be a problem additional prepatching (EOL conversion) could be added to the auto-patcher script if necessary.

[MENTION=3813358]jamus28[/MENTION]:

Change this in auto-patcher script:

[[ -n $ROOT ]] && \rm -rf "$ROOT"/tmp*

>>> to >>>

[[ -n $ROOT ]] #&& \rm -rf "$ROOT"/tmp*

The tmp* folder will not be deleted then.
[Android Software/Hacking General [Developers Only]] Didgesteve:
If you look on the first page of the OP there are some quite detailed instructions.

Download the ApG if you are on a windows machine. Download your rom. Start the ApG (in a non windows folder, like c:\temp), and let it update. Then drop your rom onto the title bar, select opendroid on the left menu and press start.

When ApG has finished it will have created two files. Put them on the SD card on your phone, and flash 'update' through CWM. Then once the phone has booted download pDroid manager from the play store.

Any problems after applying the patch, just re-flash the Slim rom.

Do not block system apps from your sim settings or this will cause problems.

Always make a Nandroid backup if you are unsure what you are doing.

I have made you the update to flash (see below), but this is only good for Slim 4.2.2 v6.9, and as soon as the next weekly build comes out chances are that the 6.9 patch won't work on it and you'll have to make a new set of patches.
[Android Software/Hacking General [Developers Only]] jpg001:
win8 pro can‘t download packages for ApG 2.6.0.2
[Android Software/Hacking General [Developers Only]] Didgesteve:
You need to put the ApG.exe in a non windows folder, ie: C:\Temp

and rightclick, run as admin.

Make sure that any firewall you have has a rule to allow.
[Android Software/Hacking General [Developers Only]] KingKuno:
ApG 2.6.0.2 ? I only can see v2.6.0.1, or ?
[Android Software/Hacking General [Developers Only]] Kimi123:
PA 3.65: Autopatcher not able to build patch

Hi,

ApG is not able to build OpenPDroid Patch with latest version of Paranoid Android 3.65.

pa_mako-3.65-20130706.zip

... apply framework.patch ...

Reversed (or previously applied) patch detected! Skipping patch.

6 out of 6 hunks ignored -- saving rejects to file smali/android/os/Looper.smali.rej

1 out of 9 hunks FAILED -- saving rejects to file 'smali/android/provider/Settings$Secure.smali.rej'

Reversed (or previously applied) patch detected! Skipping patch.

1 out of 1 hunk ignored -- saving rejects to file 'smali/com/android/internal/os/BatteryStatsImpl$Timer.smali.rej'

... apply preloaded.patch ...

!!! PATCHING FAILED FOR android/provider/Settings$Secure.smali' !!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

codepad.org/mTDfvH0y

No problems with previous versions of PA.

Regards, Kimi
[Android Software/Hacking General [Developers Only]] baastien:
Hi mateorod and all,

Strange error on ubuntu and v2.9.89 while :

error: failed extracting build.prop from /home/sebastien/Téléchargements/Android/N7000/Slim/7/Slim-n7000-4.2.2.build.7-OFFICIAL.zip !!!

Any clue someone ? Why is build.prop not recognised ?

EDIT : I might workaround with v2.9.89 patches and v2.9.8 script.

EDIT 2 : Did helps, but Settings$Secure.smali error. I guess we need to wait for a new autopatcher release
[Android Software/Hacking General [Developers Only]] karamelos:
Put your rom in auto-patcher folder (direct link work)
[Android Software/Hacking General [Developers Only]] baastien:
Thanks mate !

But I still have the Settings$Secure.smali error but as I said above I guess I've got to wait for the fix.
[Android Software/Hacking General [Developers Only]] jahrule:
Yea same on slim7
[Android Software/Hacking General [Developers Only]] Urinophoria:
About 5 min from home, I'll start building when I get there.

Unless someone beats me to it, lol
[Android Software/Hacking General [Developers Only]] josteink:
I've gotten a few complaints from people using tabletUI-mod on my ROM:

From https://github.com/josteink/device_asus_tf101/issues/40

From http://xdaforums.com/showpost.php?p=43324204&postcount=1054

Anyone else experiencing the same problems?
[Android Software/Hacking General [Developers Only]] pen²:
autopatcher with linux is also unable to patch paranoid android 3.65 for maguro:

(...)

### copy patch openpdroid/4.2/pa/20130213 ###

... copying system/media/PDroid.jpeg ...

... overwriting system/media/PDroid.jpeg from openpdroid ...

... overwriting ContentResolver.smali ...

### jar patch openpdroid/4.2/pa/20130213 ###

... apply framework.patch ...

... apply preloaded.patch ...

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!! error: failed android/provider/Settings$Secure.smali' in framework.jar cannot be remedied

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[Android Software/Hacking General [Developers Only]] Caldair:
Yes, everyone using tabletUI for recent CM nightlies was having the same problems;) ...until yesterday, when I pushed this commit out to github. :D

CM circle batteries should be working again for all devices, builds after June 27. There is a small window after June 20 where patching CM nightlies for tabletUI will fail, in part due to rapidly changing framework in CM over that period, and, in order to maintain patching for the Stable 10.1.0 release during that same period.

Here, I posted this yesterday in the Auto-Patcher tabletUI thread that I maintain. (Well "maintain" may be a stretch! Its usually like a ghost-town over there. I dont think too many AP tabUI users have found it, but it is there to report issues and I try to keep it updated with fixes or breakages to the patches:cowboy:)
[Android Software/Hacking General [Developers Only]] josteink:
Awesome. And thanks for the quick response :D

I just did a "git pull && ./batch.sh". Anything more I need to do to ensure I'm up to date?

Edit: I'll subscribe to your thread and see if I can report future issues there :)
[Android Software/Hacking General [Developers Only]] Caldair:
Thanks! (Sorry I'm out of 'xda thanks' right now) It'd be nice to get some traffic over there.:)

And it sounds like you should be updated and ready to rock! To be sure you can check the PATCHES_VERSION in your local Auto-Patcher script, it should be "20130705".
[Android Software/Hacking General [Developers Only]] RedSkyRoad:
Hi,

With regards to ApG, what is the alternative to the following in Windows?:

Do not run ApG under Windows directories such as C:\, C:\Windows, C:\Program Files\* and so on.
[Android Software/Hacking General [Developers Only]] linelock:
I'm pretty sure they just mean not in a windows system directory. For example I have mine in E:/Apps/ApG and it works fine normally.

I also get the failed android/provider/Settings$Secure.smali error when trying to patch pa_mako-3.65-20130706.zip

Log:http://pastebin.com/ST3GfH96
[Android Software/Hacking General [Developers Only]] RedSkyRoad:
Could someone please explain this to me as well? Is this bad?
[Android Software/Hacking General [Developers Only]] Magissia:
never had problems after seeing theses lines.

Regards
[Android Software/Hacking General [Developers Only]] Urinophoria:
Whoops, didn't see this one, working on it now :highfive:

Edit: Juggies beat me to it. PA and Slim were both sent to Mateor and pushed, so update autopatcher and let it rip.

Edit 2: Just sent Mateor patched and unpatched MMS.apk builds for Slim, so give Slim a bit, then let it rip :)
[Android Software/Hacking General [Developers Only]] mateorod:
As [MENTION=4418789]Urinophoria[/MENTION] said...we have updated the auto-patcher to v2.9.92 with new ParanoidAndroid and Slimrom patches. Everything onmthensupported list should be working fine, with perhaps some manual configuration needed for RCs and Final builds.

Thanks to [MENTION=4515360]juggies[/MENTION] for the PA builds and [MENTION=4418789]Urinophoria[/MENTION] for the Slimrom patches. Also, I have been noticing a lot of TabletUI patch threads around xda...check out Caldair's dedicated thread for shared bugfixes and reporting...it will make the mod better. The link to that thread is on the OP.
[Android Software/Hacking General [Developers Only]] awillis111:
I would like to patch Slim v7 for my GN7. Should I patch it as AOSP or CM.

Please forgive me if this has been asked before. I'm traveling and haven't had time to search the thread.

All battery related stats are using a ZeroLemon 7000mah battery.
[Android Software/Hacking General [Developers Only]] Bad-Pixel:
It's an AOSP rom. Btw you can read what you need to know (the ROM type) during first moments of the patching process
[Android Software/Hacking General [Developers Only]] awillis111:
Just patched it. And I'm about to flash now. Still can't PAC for my Samsung GT2 10.1 (P5113) to patch.

All battery related stats are using a ZeroLemon 7000mah battery.
[Android Software/Hacking General [Developers Only]] allofusjw:
JB support....THANK YOU!! gonna try it out tonight and think of a story to tell my wife for not getting any sleep. I don't think she'll properly appreciate the truth..."I couldn't sleep because autopatcher for pdroid was just updated and it includes jellybean support!" oh well, a fine problem to have. thanks so much guys!

update: not having any luck. tried aokp and cm10. both for maguro and located here. i'm tired and it's entirely possible i'm doing something stupid. I have applied the patch successfully many times before when using !CS roms so i have some past experience using autopatcher. I've attached a log.
[Android Software/Hacking General [Developers Only]] CollegeDev:
Hey,

Can you explain which code you've added to your script? The whole code of mine or only some improvements? Because I want to know if my addon is supported or not and all other new features (Wifi protection, Android ID random generator, cell location bugs etc?) which I have brought to PDroid.
[Android Software/Hacking General [Developers Only]] mateorod:
Ha. No man. I understood that you had been talking to pastime, but maybe the communication was less than i thought? I know future plans as far as supporting your add-on stuff hasn't been discussed outside of speculation, simply because we hadn't spoken to you.

But no, we don't have your whole code in here. You can go look, all the code is there in the download.

Pastime found this one section that looked like it could add some stability. In his words:

So its a pretty small piece. I think we were pretty fair about attribution, with three+ back links to your project.

Now people have been asking about supporting your add-on, which would be pretty neat, I think. But all this program does is replace the build patches for those who update to ROMs they don't build. At no point do we replace functions provided by something like the PDroid app itself, or the V6 script. Or your add-on app.

We've been pretty busy with JB, but if you check your inbox, you'll see I pm'd you about maybe working together to add support for your additions. The auto-patcher is a tool to distribute software, not take its place.

Thanks for your work, pastime says you've begun to really make some interesting changes. We're both interested in seeing where you're going with your work.
[Android Software/Hacking General [Developers Only]] mateorod:
Hey, thanks for trying it! Maguro, I know we can support. The nightly you have might just be off by a commit or so.

The log shows a one file, 5 hunk deviation. In a couple hours I will run a repo sync and generate some new patches and then see if they've changed. When the development on a platform is real heavy, and substantive changes are common, it can be pretty tough because the patches need updating so often.

One commit to frameworks can throw off the patch, you know? Try with last night's nightly for CM10. If it doesn't work, check back tomorrow afternoon because that will mean the repo changed to the point that I will need to push an update.

Which always happens within hours of a release. I don't know how they do that.
[Android Software/Hacking General [Developers Only]] pierx:
Hi mateorod

Thanks for JB support,..unfortunately it doesn't able to apply the patch into framework...

### apply framework.patch ###
5 out of 5 hunks FAILED -- saving rejects to file smali/android/content/ContentResolver.smali.rej

here's the complete log http://pastebin.com/Ug3Uchq7

I realize it's still an experimental build rom...

but hopefully this log useful for your future development ;)
[Android Software/Hacking General [Developers Only]] scourgeofgod:
Thanks for your great work Mateorod .

I built the patch for CM10 Paranoidandroid 1.3 ROM for Galaxy Note and tested it on chrome,dolphin,tapatalk etc and all the functions in PDroid app seem to be working perfectly.

The Pdroid app itself was not visible on market - so i used the alternative link given by syvat in his thread for install. Is it because iam running JB ?

FWIW, here is my Log

http://pastebin.com/aP6BFXfZ
[Android Software/Hacking General [Developers Only]] pastime1971:
the first success story of JB/Pdroid by a user. this is great.

@ mateo,

maybe we should like svyat's thread for downloading his app directly.

making a flashable zip of pdroid app may be easier, but i guess we may have to ask his permission before we do that.
[Android Software/Hacking General [Developers Only]] mateorod:
Yeah, I actually had to get it off his thread for the first time for my Nexus 7. It was viable, but registers as incompatible. We could link to his post again, but it IS pretty hard to find it there.

I can happily pm svyat. PM me if you'd rather do it, I think you guys have some existing relationship, right?

For those of you who are having some trouble on JB, I have a new build going which should hopefully resolve the errant commit. I will test on the Roma I know about before release. I know about CM10 maguro, and I think that other log is from a CM10 for the GalaxyS2 from Codeworxx. If anyone else is having trouble with contentresolver post and I will run your devices CM10 through the patcher myself.
[Android Software/Hacking General [Developers Only]] allofusjw:
success(maguro)! today i tried the patch on a cm10 which I had compiled myself on Aug4 and everything went fine. haven't flashed yet so can't comment on functionality but I expect all will be fine. last night I had tried patching cm10 ROMs dated Aug5 and Aug6 which I had downloaded instead of compiling myself and both failed. i am syncing with cm now and will compile and attempt patch to determine if its cm source after Aug4 which changed and caused error or a mod which existed in the ROMs I downloaded. will update with results when done.
[Android Software/Hacking General [Developers Only]] mateorod:
Confirmed working on cm-10-20120807-UNOFFICIAL-maguro.zip as well.

...but not on cm-10-20120806-EXPERIMENTAL-i9100-CODEWORKX.zip yet. Based on allofusjw's last post, the patcher is working on the maguro for 8-04 and 8-07 and the days in between when it failed at the same spot your nightlies from those dates failed.

That leads me to believe that a change had gone through and has been fixed or reversed. Either way, try a buld from the 4th and you might have success with that, but you should be fine for your 8/07 release, assuming it is straight CM10.

I just built new patches with up-to-the minut commits, and they haven't changed from the patches in our release. So we should cover the CM10 releases from 8/07 on.

And maybe some earlier, if allofusjw's results are repeatable!

Back to working on AOSP for me...