yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] mateorod:
Sorry for being out of touch guys, I have had to be Mr.Mom at home because my wife has 10 million grants due this week.

I have not gone over the history of the thread, which I assume is voluminous. But there is a small update now, and I will be adding a couple other things late tonight.

I want to have everyone welcome new Autopatcher team member Caldair, who has taken over the maintenance of the TabletUI mod. I am really excited by Caldair's work and initiative.

I have pushed his changes to the tabletUI mod, which enables TabletUI on 4.2.2. It has not been tested on that many devices, so if you can please try it and report. Caldair also has a tabletUI thread where you can report your experiences and he can look for fixes.

This is an infinitely better solution than the status quo of me just feeling guilty because I hadn't fixed it yet. Go to the tabletUI thread and thank Caldair after flashing!

AutoPatcher v2.8.6

TabletUi test run for 4.2.2 (courtesy of Caldair)

I did see that people are still having trouble with a disappearing Mms app. That indicates that something had changed in the Android package manager, because the fix seems to be installing the AussieLampChop attachment. That attachment is the exact same app that is copied over by the autopatcher.

If you experience this, please post your autopatcher logs, so that I can find the problem. A logcat would make a big difference as well. If someone has already done this, I apologize, I haven't looked yet, I will.

Thanks all.
[Android Software/Hacking General [Developers Only]] mssngr:
I had some trouble with the missing MMS apk. So I hope this helps, I just reran the CM10.1 M2 through the Autopatcher and copied the link to the log. Thanks again for all your and the teams hard work! :good:

http://codepad.org/m3hMvpYL
[Android Software/Hacking General [Developers Only]] My Gnexi:
Doesn't it install Java and stuff? Installing things usually requires admin permissions. It is recommended to test with Windows 7 and default settings.

I guess most power users turn UAC off.
[Android Software/Hacking General [Developers Only]] AuSSiELaMbChOpS:
Re: [Utility][2.8.3][03/01] Auto-Patcher (4.2.2)

ApG doesn't actually install anything it downloads Java & cygwin but uses a local directory to reference these downloads. No admin rights are needed at all to use ApG. :thumbup:
[Android Software/Hacking General [Developers Only]] Didgesteve:
Slim 4.2.2. build 2

Did you get a build that worked?
[Android Software/Hacking General [Developers Only]] karamelos:
Re: [Utility][2.8.3][03/01] Auto-Patcher (4.2.2)

Yes I submit jar files to @mateorod
[Android Software/Hacking General [Developers Only]] Chaussette_:
Hi,

I also have the MMS app missing problem. I'm trying to patch "OpenPDroid" to CyanogenMod 10.1 for SGS III I9300.

Here is my full log, hope that will help ! : http://codepad.org/4825BDfe
[Android Software/Hacking General [Developers Only]] kobik77:
It downloads Java and Cygwin packages and extracts them to its working directory.

There is no installation to system folders and no registry read/writes, thus, no need for elevated permissions at all.
[Android Software/Hacking General [Developers Only]] My Gnexi:
Good!:good:
[Android Software/Hacking General [Developers Only]] noobsgs2:
still haz patch fail

http://codepad.org/toA00iEZ
[Android Software/Hacking General [Developers Only]] mateorod:
Hi sorry I hadn't noticed that those patches had broken. I am a little behind in the thread from being busy last week. Karamelos was on top of it though and already sent in new builds. So there will be new SlimRom patches today.

Thanks for the logs to the two who posted. I have some things I intend to look at for the update later today. Everyone who encounters this, please post at least your autopatcher logs, ok?
[Android Software/Hacking General [Developers Only]] mateorod:
For those with SlimRom, I just pushed the changes to ApG. If you have a Linux or Mac, you can grab the changes from Github or wait until I release a package to our download page later tonight.

Thanks karamelos for the SlimRom patches!

for the PA rom look at the link at the the top of the OP for a a fix. For PACman don't tell the autopatcher to use PA patches. Just leave the patch type empty or use AOSP.
[Android Software/Hacking General [Developers Only]] SecUpwN:
To the maintainers of this thread, would you please link "try ApG" in the OP to the release page of ApG? make searching it much easier, I'm sure I'm not the only one who would appreciate an easy way of finding it. Thanks!
[Android Software/Hacking General [Developers Only]] Didgesteve:
BIG thank you to Karamelos and Mateorod. Patches have been tested and work fine.

I will post them on the Slim thread (with credits of course)

Great!

:)
[Android Software/Hacking General [Developers Only]] mateorod:
If someone's Mms app disappears from Launcher, would you try fixing permissions and then rebooting? I got a suggestion that this could simply be permission related.
[Android Software/Hacking General [Developers Only]] karamelos:
for fix suggestion :p

if user able to post if has this problem

pasta this in terminal or adb shell

ls -l /system/app/

& post return of this command

@SecUpwN

some error appeared

https://www.dropbox.com/s/tmm1hpxsy59fawu/log20130319214855.txt

no restore (make backup)

https://www.dropbox.com/s/jujy8dlh2eqrbrl/update-aokp-gsm_shooteru-20130319-openpdroid.zip
[Android Software/Hacking General [Developers Only]] Flambo182:
Hey digisteve, when installing the patch did you have problems with the play store on slim 4.2.2 build 2? Mine kept force closing, I fixed it by reflashing myliferocks multi DPI play store, removing my google account, signing back in and I had to push an install from the play store to my device to get the "terms and conditions" dialog box you have to accept to pop up. Just would like to know if you had the same problem or if I'm the only one.

That being said, thanks a lot karamelos and mateorod, I really appreciate your work!! It's so awesome to have control over my device, and it was somewhat shocking to see all of the data an app has access to. Glad I can block that now :).

Thanks again!
[Android Software/Hacking General [Developers Only]] freddysam:
I just tried to patch Slim-mako-4.2.2.build.2-OFFICIAL with openpdroid

and got this error:

http://codepad.org/Ek8hGP6C

I am using ApG.2.6.0.2 with Auto-Patcher v2.8.6.7

Update:

It looks like it was just using the wrong set of patches. I changed the build date in the build.prop and it patched correctly.

from this ro.build.date.utc=1363215464

to this ro.build.date.utc=1363450155

http://codepad.org/Kyx1eyup
[Android Software/Hacking General [Developers Only]] karamelos:
In your fist log

running ./auto_patcher /cygdrive/m/Sharing/Slim-mako-4.2.2.build.2-OFFICIAL - Copy.zip openpdroid aosp

in second

running ./auto_patcher /cygdrive/m/Sharing/Slim-mako-4.2.2.build.2-OFFICIAL-full.zip openpdroid aosp

You have space in first command
[Android Software/Hacking General [Developers Only]] freddysam:
It's actually the other way around. The first one (the one that failed) had no space. The second one (the one that patched) had a space. I didn't think that spaces mattered in ApG.

If you look at the logs, the first one has:

Patches are openpdroid/4.2/.aosp-slim/20130222

and the second one with the modified build date:

Patches are openpdroid/4.2/.aosp-slim/20130315

You can try it yourself. Many of the slim roms produced the same error, except for the one for i9100. Once I added the build date from i9100 to the mako rom, ApG patched it correctly. Something about going from a March 13th build date to a March 16th build date changed which patches were applied.
[Android Software/Hacking General [Developers Only]] karamelos:
ok i try it

same error on linux

command:

./auto_patcher ~/Téléchargements/Slim-mako-4.2.2.build.2-OFFICIAL.zip openpdroid

result

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

patch

openpdroid patch date has been set to: 20130222

but i have not exactly same error

With force patch

command:

./auto_patcher ~/Téléchargements/Slim-mako-4.2.2.build.2-OFFICIAL.zip openpdroid aosp 20130315

patch is created but same error "at brut.androlib.res" in logs
[Android Software/Hacking General [Developers Only]] bustedwings:
same results trying to patch Slim-d2att-4.2.2.build.2-OFFICIAL.zip for the i747.

when using apg and when force patch my logs look the same as yours. any ideas?
[Android Software/Hacking General [Developers Only]] freddysam:
Is that error significant? I installed the patch and everything seems to work. It's hard to test all of the permissions, but I know the gps permission works with pdroid manager.

I ran the force patch on the original rom zip and I get this error instead of the one you posted:

http://codepad.org/kVpEdreA
[Android Software/Hacking General [Developers Only]] AuSSiELaMbChOpS:
Re: [Utility][2.8.3][03/01] Auto-Patcher (4.2.2)

Nothing to worry about from what I can tell, there is an issue decompiling the mms.apk possibly caused by the framework-res.apk when it is loaded it is generating errors. But if you look right near the end of the log auto_patcher falls back and copies over the pre-compiled version of mms.apk.

So all functions of OpenPdroid should be functioning correctly. :thumbup:
[Android Software/Hacking General [Developers Only]] Chaussette_:
I tried, but MMS app is still missing.

All files in "/system/app" have same rights : "-rw-r--r--" :

-rw-r--r-- root root 2687388 2008-08-01 14:00 Mms.apk

Here is the full dump : http://codepad.org/cDPute3j
[Android Software/Hacking General [Developers Only]] Didgesteve:
No I didn't get any problems with Play, sorry.

Do you block Play services from accessing your sim details? that would break it.

I would try and stick to the Slim gapps, as they are made to go with the rom.

Reflashing the AIO_aroma_v1.0 should have fixed it.

But this isn't the Slim thread...
[Android Software/Hacking General [Developers Only]] karamelos:
Re: [Utility][2.8.3][03/01] Auto-Patcher (4.2.2)

Hi

I make new build today
[Android Software/Hacking General [Developers Only]] Didgesteve:
GsmServiceStateTracker.smali

I noticed that when I was building the patches for Slim yesterday, I got an error about

!!! PATCHING FAILED FOR com/android/internal/telephony/gsm/GsmServiceStateTracker.smali !!!

but it carried on and finished building the patch, complete with an update & restore

I was wondering what a GsmServiceStateTracker is and what happens when the phone doesn't have one?

I had someone report in the Slim thread

Is this related?

I don't use google maps, and I have that and network location disabled with titanium as they are such battery hogs, so maybe I wouldn't notice.

It's not a problem for me, but I am just curious.
[Android Software/Hacking General [Developers Only]] mateorod:
What you have is that you are using the older patches. I tried to guess when the SlimRom patches broke and I guessed 3/15. If the autopatcher is using the older patches, then you must be using a rom from before 3/15 and I guessed the wrong date. I will back the patch date back to the 12th.

The autopatcher does it's best to match the best patches for your rom. That involves matching rom type (Slim, Cyanogen, AOKP etc.) and patches build date. It queries your rom's build date (in the build.prop as you figured) and then uses the patch closest to (but not past that build date. So in your case, there are 3 4.2 slim patches in the autopatcher, 0201, 0209 and 0315. It saw your build date was 0312, so it used the best match, which is 0209.

I have mostly eliminated users having to match patch dates by using this rom query. But in cases like yours it can be necessary. It is still possible with the Auto-Patcher on the command line, just add the romtype and patch date to the command. For your rom it would be:

./auto_patcher slimrom.zip openpdroid aosp 20130315

You could also use the ".aosp-slim" romtype, but that is not recommended except in advanced cases.

Use the tip above, or if the command line is too intimidating, you could just download a newer build after the 0315.

Those are apktool errors and are a bug in either apktool or more likely in SlimRom's Mms.apk. Looks like dup resources, maybe. That same errors happen with apktool and SlimRom downloaded from the Slim website, no autopatcher involved.

It doesn't matter too much, we have a work-around in place for situations like that.

Now as to what is happening with some people having the Mms disappear, I haven't figured that out yet. Does clearing dalvik by itself help, or do you have to install the apk again?

If you look, the Mms.apk is copied over. If that doesn't appear in your launcher, just reinstall the apk linked at the top of the OP. I see you are using CM10, please use a build from before 0209 or it won't work.

Not everything you posted is showing up in my above quote. But as for the GSMServiceStateTracker, it is still in your phone. I copy over an older version of that file, one that we are able to patch. You should notice no difference. The bugs people are ascribing to this process are very dubious. The two bugs I see referenced is cell location and mobile data, but I happen to know that cell tower location is an upstream bug and is being fixed elsewhere.

Did I miss anything of importance? The traffic on this thread is intense, and if I don't visit the thread in between each post, my email alerts stop (which is super irritating as I don't always want to load the browser for each post.)
[Android Software/Hacking General [Developers Only]] superdog404:
Hi mateorod - Great job. The good news is that the Slimbean 4.2.2 Official release 2 worked for me. It did get the error about gsm part but it made the patch files and did install and is working.

The bad news is that on my Galaxy Tab 2 10.1" running the aokp_p5113_jb_milestone-1 it made the patches but when I try to install it under recovery the tab comes up with an error "unfortunately, the process com.android.phone has stopped working." That error comes up on boot and I can't clear it. All I can do is install the restore patch. I think that milestone rom is from around the end of October 2012. Since there was no error to report through your code pad I think it's called I will attack the log here.

This Tab 2 is wifi only.

Thank you

superdo404
[Android Software/Hacking General [Developers Only]] hellunn:
Re: [Utility][2.8.3][03/01] Auto-Patcher (4.2.2)

Well, actually my settings for play services only allow network and accounts info and it works well. Probably you need to wipe cache or delete the play services data to make it "forget" the previously gathered ids.

---------- Post added at 11:15 PM ---------- Previous post was at 10:16 PM ----------

Now I use autopatcher on Linux, so probably the problem I have once experienced is not present in last ApG versions.

I had to move ApG to c:\ in the first use of it in december 2012, and updated there the next versions, so I have never tried again in a different path.
[Android Software/Hacking General [Developers Only]] kobik77:
Well, that's a damn old version.

Please don't report bugs for older ApG versions as the chances are they won't be relevant for the latest one.

---------- Post added at 04:22 PM ---------- Previous post was at 04:14 PM ----------

You have a little miss-assumption there.

What I meant was that when you're patching automatically using ApG, it take cares for the spaces for you.

But when you're patching manually from the command line, ApG isn't involved anymore so you need to take care for paths with spaces by yourself.

Hence, you should run the command like this:

./auto_patcher "/cygdrive/m/Sharing/Slim-mako-4.2.2.build.2-OFFICIAL - Copy.zip" openpdroid

or like this:

./auto_patcher /cygdrive/m/Sharing/Slim-mako-4.2.2.build.2-OFFICIAL\ -\ Copy.zip openpdroid
[Android Software/Hacking General [Developers Only]] sakej:
the first time ivg got error but i figure it out, the issue was that Ive put autopatcher in folder that contains space in name "auto patcher" when changed it to autopatcher it works but than i get this:

any help?

Im was trying to apply pd2 patch to cm10 by invendor beta 2
[Android Software/Hacking General [Developers Only]] epapsiou:
error 4.2.2

Getting following error with the latest 4.2.2 aosp based rom(AOCP) . Using autopatcher 2.8.6

Is the patcher old or am i doing something wrong

!!! PATCHING FAILED FOR android/app/Fragment.smali android/content/AsyncTaskLoader.smali android/os/SystemProperties.smali android/provider/Settings$Secure.smali' !!!

File for which patching failed:

---------------------------------------------

Fragment.smali

---------------------------------------------

We can try to add a premade copy of those files.

This sometimes works.

You only need to report this if running the program gives you problems!!!

Do you want to proceed ? (YES/no)

... replace android/app/Fragment.smali ...

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

!!! error: failed android/content/AsyncTaskLoader.smali in framework.jar cannot be remedied

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

usage: ./auto_patcher <ROM> <MODS> <ROMTYPE>

example: ./auto_patcher CM10.zip openpdroid cm

Use ./auto_patcher -h for the help menu
[Android Software/Hacking General [Developers Only]] meviox:
I'm using ApG v2.6.0.2 on Windows XP and the latest autopatcher v2.8.6.7.

Some issues I've noticed:

after launching the ApG executable the program performs the auto-synchronization with the GitHub repository. After that, both "Select Mod Types" and "Select ROM Types" fields are empty (see attached screenshot)

when I try to perform the "Manual Patching" operation I get

$ ./auto_patcher -h
./auto_patcher: line 2: $'\r': command not found
./auto_patcher: line 4: $'\r': command not found
./auto_patcher: line 7: $'\r': command not found
./auto_patcher: line 11: $'\r': command not found
./auto_patcher: line 123: $'\r': command not found
./auto_patcher: line 127: $'\r': command not found
./auto_patcher: line 130: $'\r': command not found
: invalid optionline 132: set: -
set: usage: set [--abefhkmnptuvxBCHP] [-o option-name] [arg ...]
./auto_patcher: line 133: $'\r': command not found
./auto_patcher: line 134: syntax error near unexpected token `$'{\r''
'/auto_patcher: line 134: `printusage_help () {

if e.g. I launch the script with ./auto_patcher -h to show the help/usage options.

Both issues I mentioned above I've observed since autopatcher version 2.8.4. That said, it works just fine if I download version 2.8.3 and copy all three files from the archive into the /ap directory.
[Android Software/Hacking General [Developers Only]] sakej:
yeah.. i have the same, it works for me at some point today but now it the same.. nothing on mod list .. i think it may be some server side issue, maybe files was deleted on it or something ...
[Android Software/Hacking General [Developers Only]] hallydamaster:
Could anyone help me understand why patching this ROM won't work?:

http://xdaforums.com/showthread.php?t=1699801

I think I have tried every combination I can think of, and it just will not do. Always exits with this message:

I have included a log. Thank you very much!
[Android Software/Hacking General [Developers Only]] mateorod:
Have you tried the aokp patches? Your log has you trying generic.

./auto_patcher ROM.zip pdroid aokp

If there are no failed hunks, it is likely a working update.zip. ignored hunks or patches are usually OK.
[Android Software/Hacking General [Developers Only]] hallydamaster:
I am not sure I understand what you mean by no failed hunks! It says 105 out of 106 hunks failed in the end of the log!? :confused:
[Android Software/Hacking General [Developers Only]] mateorod:
Yes. That patch will not work. It did not even produce a flashable update.zip. I brought up ignored hunks because you said you tried every possible combination. I wasn't sure if that included AOKP though. Since your ROM is based on aokp, it will likely work with aokp or nothing. But since you posted a log with a very-unlikely-to-succeed command, I thought it would be prudent to check and make sure you tried the aokp patches lest we throw the baby out with the bath water.

Did you try the aokp patches like I suggested? I have patched several aokp milestone 6 Roms with the patches in the autopatcher. Try the command I posted before, and if it doesn't work then try some of the listed patch dates by adding a date at the end of the command.

You can see the available patch dates by executing:

./auto_patcher ROM.zip -h
[Android Software/Hacking General [Developers Only]] kbeezie:
Just replying to let you know that I've used the auto-patcher for EliteMod ICS (120706) to patch in pDroid and it appears to be working just fine with the pDroid app from the market place.

I used akop rom type (it's a modified cm9 kernel in an aokp rom):

./auto_patcher EliteModICS120706.zip pdroid aokp 20120706
### verify tools ###
### verify ROM ###
### unzip patch tools ###
### unzip patch patches ###
### unzip rom ###
inflated: system/framework/core.jar
inflated: system/framework/framework.jar
inflated: system/framework/services.jar
### create updater script ###
inflated: META-INF/com/google/android/update-binary
inflated: META-INF/com/google/android/updater-script
### using Clockworkmod installer ###
### create restore.zip ###
### decompile framework.jar ###
... extract preloaded-classes ...
### decompile core.jar ###
### decompile services.jar ###
### patch pdroid/aokp/latest ###
### apply framework.patch ###
Reversed (or previously applied) patch detected! Skipping patch.
15 out of 15 hunks ignored -- saving rejects to file 'smali/com/android/internal/telephony/RIL$RILSender.smali.rej'
Reversed (or previously applied) patch detected! Skipping patch.
4 out of 4 hunks ignored -- saving rejects to file 'smali/com/android/internal/telephony/sip/SipPhone$SipConnection.smali.rej'
... apply preloaded.patch ...
### apply core.patch ###
### apply services.patch ###
### rebuild framework.jar ###
### rebuild core.jar ###
### rebuild services.jar ###
### create updater.zip ###
### finished ###
flash update.zip to install the modified
flash restore.zip to restore the original
[Android Software/Hacking General [Developers Only]] hallydamaster:
Tried all the patch dates for aokp, and w/o specifying any date, just aokp.

./auto_patcher ROM.ZIP pdroid aokp

above command fails with the same output as all others do. Logfile attatched.

Maybe I should just ask the cooks to add the patch at buildtime instead, but thanks for your help anyway.
[Android Software/Hacking General [Developers Only]] Px80:
will the autopatcher also be available for windows?
[Android Software/Hacking General [Developers Only]] mithrial:
Did you read the startpost? Use cygwin.

Here the link for the description: http://xdaforums.com/showpost.php?p=28196231&postcount=104

But I think it will be quicker and way more informative if you install VirtualBox and use a virtual machine with Ubuntu or Mint.
[Android Software/Hacking General [Developers Only]] kobik77:
Sorry, but there is no reason installing VM for using auto patcher unless one needs Linux for other stuff.

Sent from my Galaxy Nexus
[Android Software/Hacking General [Developers Only]] zergborghybrid:
There is never a need for installing a VM.

Just download a virtualbox-image and run it. Takes about 30 sec, compared to 5min for installing Cygwin.

If you don't need the image anymore, dump it.

But it is simple a matter of personal preference.