yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] Finitesimal:
I'm trying to build AOKP MR1 for the Nexus 7, on OS X.

I'm having the exact same problem, down to the number of "hunks" failed.

/auto_patcher ../aokp_grouper_jb-mr1_build-2.zip openpdroid,v6supercharger aokp

The Auto-Patcher v2.6.25

### verify tools ###
### verify ROM ###
### unzip patch tools ###
### unzip patch patches ###
inflated: system/build.prop
### probe rom type ###
... result of ROM check: version= 4.2.1 rom= aokp ...
... Using aokp patches ...
... openpdroid patch date has been set to: 20130201 ...
### unzip rom ###
inflated: system/framework/core.jar
inflated: system/framework/framework.jar
inflated: system/framework/services.jar
inflated: system/framework/telephony-common.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 system files ###
... decompile framework.jar ...
... extract preloaded-classes ...
... decompile core.jar ...
... decompile services.jar ...
... decompile telephony-common.jar ...
### copy patch openpdroid/4.2/aokp/20130201 ###
... copying system/app/Mms.apk ...
... copying system/media/PDroid.jpeg ...
### jar patch openpdroid/4.2/aokp/20130201 ###
... apply framework.patch ...
... apply preloaded.patch ...
... apply core.patch ...
... apply services.patch ...
146 out of 149 hunks FAILED -- saving rejects to file smali/com/android/server/ServerThread.smali.rej
!!! PATCHING FAILED FOR com/android/server/ServerThread.smali !!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!! error: failed com/android/server/ServerThread.smali in services.jar cannot be remedied
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[Android Software/Hacking General [Developers Only]] Jdgp42:
I patch a CM10.1 rom for Galaxy Tab 2 7" for the TabletUI, I patch it manualy because ApG don't show TabletUI as a patch in the GUI, it work and gave me the 2 flashable zip's and it work after flashing it but notifications bar force close the systemUI everytime I click it. Any solution for this?
[Android Software/Hacking General [Developers Only]] Febby:
Re: [Utility][2.6.25][2/01] Auto-Patcher (4.2.1)

If that's with a Galaxy nexus, issues are very well known about... pain in the bootay
[Android Software/Hacking General [Developers Only]] Completely_Clueless:
SGH-I777 OpenPDroid Mod for AOKP 4.2.1

I decided to retry the openpdroid mod for the ROM Jellybean 4.2.1 AOKP for SGH-I777. I did three attempts, and all three failed.

The first time I used the default patches that were determined by the ROM probing. The second attempt I used the AOSP patches (./auto_patcher <ROM>.zip openpdroid aosp), and the third attempt I used AOKP patches (./auto_patcher <ROM>.zip openpdroid aokp).

I've attached the log files below. It seems that the problem is with "ServerThread.smali;" patching fails at that point. Remember, the only mod I applied (and would like to apply) is OpenPDroid. My device is a Samsung Galaxy S2 (AT&T).
[Android Software/Hacking General [Developers Only]] :
Error patching ParanoidAndroid Beta 3:

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

Using:

Autopatch 2.6.25:

http://codepad.org/nueloWVZ
[Android Software/Hacking General [Developers Only]] AuSSiELaMbChOpS:
Re: [Utility][2.6.25][2/01] Auto-Patcher (4.2.1)

I noticed your patching failed for the Paranoid Android Rom I have had issues too but worked out a fix for mine, I am running an S2 and see you are trying to patch a Note. You could try my fix which is a page or two back, the same file is failing in your log RIL$RILsender.smali requires a bit of modification of the patch file but it is very easy. Let me know if you want any help, worst case if it doesn't work you just flash the restore zip.

Sent from my Paranoid GT-i9100 using Xparent ICS Tapatalk 2
[Android Software/Hacking General [Developers Only]] meteorrock:
ooo HI there. lol. Thanks for this tool.

Just found it. :laugh:
[Android Software/Hacking General [Developers Only]] :
Re: [Utility][2.6.25][2/01] Auto-Patcher (4.2.1)

Tell me what to do and I'll do it ;)
[Android Software/Hacking General [Developers Only]] AuSSiELaMbChOpS:
Ok here you go its pretty easy:

1. Open the following file in your preferred text editor:

\auto-patcher\patches\openpdroid\4.2\pa\20130201\telephony-common.patch

Search for the following:

This is the section of the patch file causing problems:

RIL$RILSender

Nite find the lines with the following code:

invoke-static {v10}, Lcom/android/internal/telephony/RIL;->access$200(Lcom/android/internal/telephony/RIL;)V

Replace each occurrence of this with:

invoke-static {v10}, Lcom/android/internal/telephony/RIL;->access$000(Lcom/android/internal/telephony/RIL;)V

From memory there are about 3 or 4 replacements, save it once you are done.

Now go back to the root directory of auto-patcher and delete the following files:

autopatcher.zip

patch_patches.tgz

patch_tools.tgz

As you are using Windows & ApG you need to select Manual Patch to open the cygwin command prompt so you can access the following script.

Now execute the following:

./batch.sh

This script will regenerate the auto-patcher files using the modified telehony-common.patch file you made.

Once that is done just patch manually from where you are, if you rom zip is called something else just use the correct name I took the detail below from your log file:

./auto_patcher pa_n7000-2.99-02FEB2013-084641.zip openpdroid pa

Fingers crossed it should patch successfully and create the update and restore zips for you.

I am pretty confident this should work as the RIL is the same on my Galaxy S2 and your Note:

... result of ROM check: RIL= SamsungExynos4RIL

Let me know how you go.
[Android Software/Hacking General [Developers Only]] :
Results my good friend:

http://codepad.org/zn25rhJ6

Thanks my friend :D
[Android Software/Hacking General [Developers Only]] baastien:
Hello,

AuSSiELaMbChOpS Thank you very much for the tip !

Running Linux I just extracted telephony-common.patch and done the "access$000 trick"

then

copy/paste into patch_patches.tgz

And :good: YES it is !
[Android Software/Hacking General [Developers Only]] pappyN4:
Hi all

I have a Nexus 4 arriving at some point and I've spent most of today looking up on things to setup before using it. So far I have root, AFWall, and OpenPDroid on my list. I'm prepared for the first two, but after reading most of the original PDroid thread, most of the PDroid2.0 thread, some of the OpenPDroid, PDroidManager, and this Auto-Patcher thread, I cant think straight anymore.

Simple question before I read through this thread again.

Would openPDroid work on my phone by patching the factory image?

Nexus4, rooted, original ROM, winxp64

It seems to me that the answer would be yes since a fresh from factory N4 would be using aosp 4.2.1 no? I should be able to patch the phone using ApG.

Thanks

Pappy
[Android Software/Hacking General [Developers Only]] wbedard:
Re: [Utility][2.6.25][2/01] Auto-Patcher (4.2.1)

Hi Pappy,

The short answer is no. While the factory image is based on AOSP, it is "odexed" and therefore (I believe) not supported by autopatcher. However, if you (or someone else) can build you a ROM from the AOSP source, pre-patched with OpenPDroid, then you should be good to go.

Now, I had been hearing that the Nexus4 wasn't actually supported under AOSP but Google just released an update (AOSP build JOP40G) which does support that device. With that hurdle out of the way, the biggest obstacle will be adding in all the non-AOSP stuff (i.e. proprietary vendor libraries and config files...) that inevitably make it into a released device. It's very do-able, just tedious.

If you will browse the forums for your device here on XDA, someone will almost certainly create a "stock" ROM with all that stuff already integrated. Make sure to read the release notes of any published ROM to make sure you are aware of what works and what doesn't as it is common for ROMs of newer devices to have some "growing pains". Once you find a ROM based on code supported by autopatcher, it should be able to patch it for OpenPDroid for you.

Good luck and keep us informed on what you find that looks promising!

R/

wbedard
[Android Software/Hacking General [Developers Only]] pappyN4:
Wow, thanks for the quick response guys.

I do have some experience with linux, enough to know the pain of makefiles and dependency issues. I dont have any objections to flashing custom firmware (ie:tomato on my router) but for my computers I tend to have a minimalist base install and then add whatever I need (personalized nLite and vLite isos).

Looking over instructions for CM seems pretty straighforward. The only difference is when I root the device I would have to flash clockwork onto it (which I wasnt planning to do originally), then install CM onto the phone, then superSU.

For any updates to openPDroid, I would then have to repatch CM and install it again on to the phone.

So for any kernel updates, I would have to wait for a new CM to come out or would I be able to update normally?

Does installing CM wipe all the data on the phone? So if I wanted a newer CM or openPDroid, would I lose whatever I've done on the phone?

Alright, time for work.

I'll download CM (looks like there's no stable or RC build yet for N4) and play around with it after work.

Last question before I go, the backup option in clockwork, is it the equivalent of Arconis or Ghost, so if I restore it it goes back to the original build?

Thanks

Pappy
[Android Software/Hacking General [Developers Only]] SecUpwN:
AW: [Utility][2.6.25][2/01] Auto-Patcher (4.2.1)

Could anyone please provide me with the new patch for AOKP 4.2.1 by helicopter88? Thanks will be given!
[Android Software/Hacking General [Developers Only]] flash5000:
Actually there's no reason not to flash a custom recovery. You gain some benefits, and I've not heard of serious problems on the Nexus 4 yet.

That's correct. You would need to patch a "fresh" copy of your ROM install ZIP in order to have the last OpenPDroid updates.

There's no need to repatch afaik, you can just install any kernel you like over the existing installation.

No, you can flash CM without doing a wipe (wipe = you lose your data, eg. phone is put back to "factory state").

But in order to install a custom recovery (= Clockworkmod or TWRP), you need to unlock the boot loader, which is not possible without a full wipe performed automatically due to security reasons. Once your custom recovery is installed and you have root access, it's easy to backup your apps and settings, for example using the famous app TitaniumBackup, and restore them later.

I would go for the Modaco Custom CyanogenMod ROM, it's been very stable for me and gets regular updates. See http://xdaforums.com/showthread.php?t=2099226 for more information.

Exactly. It performs a full 1:1 backup of your current state, which allows you to return to the previous state in case of problems.
[Android Software/Hacking General [Developers Only]] mateorod:
Auto-Patcher 2.6.50 is out (uploading to techerrata now).

Inlcuded

The only new fix is I fixed the OpenPDroid AOKP patches. They have been tested to work with AOKP build 2 for grouper, mako, SGH-I777 and a couple others. Sorry for the mix-up.

Not included:

No changes to tabletUI (look for 2.7.0 for a final decision or fix)

GNex issues (toro/toroplus--- try modaco roms)

Anything else? Let me know, I am aiming at letting 2.7.0 be a LTS (like 2.4.7 was...2 months of support) so if I don't hear about it, it can't be fixed. Logs, please.

Also not fixed yet is the problem that was found/solved by AussieLampChops about the RILSender in some PA roms. They look to be Samsung roms, baastia was posting about a TouchPad but I don't know if that was the device the fix worked for...I need to find some commonality or reason behind this problem, and then incorporate something reasonable in response. It will be fixed, but since the ones who need it seem to have gotten it and have provided a support network for themselves, I am going to take the time to try and do this right.

Sorry, I don't 100% know what the exact problem you are having is...could you post the log generated by the auto-patcher? If it applied correctly, then perhaps you could go to trevd's thread and get some help. He is the dev behind this mod, and if the mod applied cleanly, then I think he would be the one to ask. Also, when this mod is applied on the comman-line, I output a message asking users to check out his trouble-shooting guide...maybe that has an answer.

---------------------
For the 3G Dongle Mod
---------------------

Please, Go to trevd's OP for usage. All the hard parts are done...
...But it will be frustrating if it doesn't work because you didn't read the Troubleshooting guide!

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

But post the log here first, and I will look to make sure you aren't missing some vital piece.
[Android Software/Hacking General [Developers Only]] wbedard:
Hey Pappy & mateorod,

Thanks for the flattery but let's see how it holds up as I push back a bit on your reply (mateorod). Specifically, could you please clarify what you mean when you say that the Nexus4 (i.e. "mako") is not supported in AOSP? I will clarify a few of my remarks to say that, as of the "android-4.2.1_r1.2"/JOP40G release that I mentioned previously, "full_mako-userdebug" is a target in AOSP (I'm looking at it right now on my build environment...). Additionally, there are already people building the custom ROMs that I alluded to, such as the following project here on XDA:

[ROM] [AOSP] [4.2.1] Perfect Android [MAKO] [2-3-13]

Going back to the issue of the availability of the various "proprietary binaries" that are required to fully support the hardware, Google did release the binaries to support their shipping software (JOP40C) but have since removed them from their download site. People have, of course, archived them and they are still available but it's not clear how well they support the latest release.

OK, enough from me. Please clarify what you meant when you have a chance. When we talk to users here in the forums, I want to make sure that all of us "principals" on projects like Autopatcher, OpenPDroid, etc speak using the same language so to avoid confusion with our users. Thanks and let me apologize in advance for any lack of accuracy/research on my part!

R/

wbedard
[Android Software/Hacking General [Developers Only]] mateorod:
A couple of points...first, just because there are AOSP based ROMs does not mean that the device is supported by AOSP. There are lots of devices that are not supported by aosp, my device, tilapia, is one. It is usually a licensing issue related to the binaries and not a technical issue per se. The GSM stack is a frequent culprit.

Also, Nexus stock ROMs aren't, despite common misconception, pure AOSP. The full grouper builds you make are different than the stock factory image, including odexing and other changes. It is subtle, especially when it comes to user experience, but to those of us who are deep in the framework, it is a real difference.

You can build a Mako or Tilapia target, but it will not produce a working ROM. Cyanogen and the custom ROM crowd skirts a very grey area by using the extract-files.sh scripts, which grab the binaries. But it is usually not as simple as just jumping in those binaries, some very talented people have to code in the framework to make it all work. That is why, if you scan the CM tree, you will area bunch of Nexus 4 fixes.

Here is AOSP's lead engineer addressing the topic (obliquely, surely due to attorney advice)

Now, you could get lucky and a deodexed stock ROM might work. Or some enterprising person will pop out an AOSP-based rom for Nexus 4. Paul O'Brien with Modaco is usually very fast with these. But as a non-Officially supported AOSP build, it can cause us at the auto-patcher some problems. The PDroid family requires major surgery...it is very intensive. These little differences add up.

In the final analysis, I would characterize the relationship as being similar to the way the Auto-Patcher responds to Official CM builds and non-Official builds. We pretty much guarantee that we can port to the devices that have an Official Cyanogen build while the unofficial builds are hit and miss (mostly hit, but still.). The 'unsupported' AOSP devices break down in about the same manner...and are often the same devices. The breakdown starts when AOSP engineers don't code out the needed hardware interfaces...after all they are the ones with the engineering degrees and spec sheets.

Hope that is somewhat clearer.
[Android Software/Hacking General [Developers Only]] pommegmx:
Milestone

Ok, thank you very much in advance :o

You're right about the milestone, it's a phone with a physical keyboard, so it maybe make it "different" :rolleyes:

No problem for waiting ! :fingers-crossed:
[Android Software/Hacking General [Developers Only]] wbedard:
Yes, I do appreciate you clarifying your remarks. While I was speaking from the standpoint of a user who simply wanted OpenPDroid on my new Nexus4, the post was in the Autopatcher thread and I know things are a lot more difficult for you in that regard. However, in terms how well a device is "supported" in AOSP, let's keep an open mind when we're talking to users. For instance, while your clarification does back down quite a bit from your original assessment of "NO" support in AOSP, even my Galaxy Nexus (maguro) doesn't have what many/most users would consider "adequate" support since a straight AOSP build, even using Google's provided binaries, won't support either the camera or GPS. This is in spite of the fact that my device is likely regarded as one of the better supported devices out there right now.

Anyhow, thanks again for the clarification and I'll be sure to keep in mind the high standard required for you to provide proper support in Autopatcher in future comments...:good:

R/

wbedard
[Android Software/Hacking General [Developers Only]] mateorod:
Well, it isn't so much a question of standards as it is that a deodexed stock ROM is not likely to be able to be auto patched for the reason that the stock ROM is different than aosp, and that that device is not supported by AOSP. It has been a matter of much frustration for device owners.

As far as the GNex is concerned...maguro is supported by AOSP. Toro and toroplus are not, and as the toro users here can tell you, that has caused problems for them even onto the Cyanogen builds. That goes back to no AOSP support.

It isn't so much that Google just withholds binaries. I was only just last week able to finally support Cyanogen10.1 for mako...it failed for the first round of patches because they hadn't worked out all the hardware kinks that were not available due to no aosp.

Edit: how about this...it isn't so much that ROM devs cannot make workable AOSP roms for officially unsupported devices...it is that those things they do to make it work often specifically conflict with what we do with OpenPdroid patching. Better to be clear about that upfront or else we will have some frustrated people. I am not warning them off semantically, auto patching a stock Mako ROM is hard and currently does not work. The lack of aosp support is the baseline reason for this. Hope that makes some sense.
[Android Software/Hacking General [Developers Only]] 51liberty:
AOKP for N4 openpdroid succeed

thank U very much
[Android Software/Hacking General [Developers Only]] pappyN4:
OK, so I tried out ApG, worked like a charm and created the CM_openpdroid_update.zip file. I've read over the install docs for CM as well and it looks pretty easy.

Heres the plan.

1.unlock bootloader

2.flash CWM and make backup image

3a.sdcard\install CM.zip

3b.sdcard\install CM_openPDroid_update.zip

3c.sdcard\install SuperSU.zip (not needed for this but will for other stuff like AFwall)

4 boot and install PDroid Manager.apk

If an update comes out for CM or openPdroid, i'll have to create the update file again and redo the relevant parts of step 3

As long as I dont select "wipe data/factory reset", I can reinstall newer CM and openPDroid_updates without losing call history, apps,etc..

Sweet.

Now I just need for the phone to arrive before I get too many other ideas from this site ;)
[Android Software/Hacking General [Developers Only]] karamelos:
attached zip & log

Filename: aokp_shooteru_unofficial_Feb-04-13.zip

MD5sum: f7677a17b5a757f0c3ae713c152d9bcc

MD5 Sum: 1f917586008062f4cdaa52abe917c046

http://d-h.st/aNP
[Android Software/Hacking General [Developers Only]] Didgesteve:
New autopatcher 2.6.50

I have tried the link to the new Autopatcher, but can't see 2.6.50 listed.

Am I looking in the right place?

http://techerrata.com/browse/mateorod/pastime1971

Thanks
[Android Software/Hacking General [Developers Only]] karamelos:
Re: [Utility][2.6.25][2/01] Auto-Patcher (4.2.1)

no

here

https://github.com/mateor/auto-patcher
[Android Software/Hacking General [Developers Only]] djkidy123:
Could anyone please provide me with the patch for http://goo.im/devs/frankinstine/AOKP_4.1.2_JellyBean/aokp_pyramid_unofficial_Jan-20-13.zip

http://xdaforums.com/showthread.php?t=1828250&highlight=aokp

Thanx!
[Android Software/Hacking General [Developers Only]] karamelos:
@materod & @SecUpwN

This version make with 2.6.25

With last auto_patcher 2.6.50 patch is broken

!!! error: failed com/android/server/ServerThread.smali in services.jar cannot be remedied

Filename: aokp_pyramid_unofficial_Jan-20-13.zip

MD5sum: 097564454cc15b3a350ece00a74e3cdb

link log & zip

Filename: auto-patcher-master_aokp_pyramid.zip

MD5 Sum: 682a4431e1982f546dde036a9c0de306

It's an 4.1 version, pdroid2 app is necessary
[Android Software/Hacking General [Developers Only]] I900-Nutzer:
Hmm - that means that the "cell tower location" - problem is now fixed??

Thx!
[Android Software/Hacking General [Developers Only]] scutworker:
No, it is not fixed yet. The slowdown with camera and GPS are, but not this. It will come soon in a new release. See the OpenPdroid thread for details of that.

See here:

http://xdaforums.com/showpost.php?p=37453301&postcount=156
[Android Software/Hacking General [Developers Only]] mateorod:
There you go! It is easy once you do it once and there are a bunch of resources to help you out if you need it. It is the best thing for your hardware, that is for sure.

Dangit. I uploaded 2.6.50 to the root directory of the server instead of the regular download spot. I am reuploading now, maybe 20 mins, okay? Sorry guys.

Yeah, sorry karamleos. We had a bug (which i have not found out why) in the AOKP patches. I uploaded a fix in 2.6.50, but, as I admitted above, uploaded it to the wrong place. You can patch them with earlier versions, but those are the OpenPDroid 1.0.0 patches, which are way inferior to the 1.0.1 patches. Should be up soon, thanks for the tip.

Yeah, I guess I should have been more clear, I meant bugs or concerns with the Auto-patcher itself. There are a couple of lingering issues with OpenPDroid itself, as well as a bunch of conversations to be had about what direction to take the project (ps. Make your voices heard! This is the community fork, your opinions matter.)

But I was asking for any specific Auto-patcher stuff there, Thanks scutworker.
[Android Software/Hacking General [Developers Only]] Completely_Clueless:
Success!

Hey mateorod, Auto Patcher v2.6.50 solved the problem I was having with AOKP on the SGH-I777. Thank you very much! :laugh:

I did two attempts. The first one, I let the Auto Patcher probe and automatically apply the patch. Strangely, it detected the ROM as AOSP and attempted to apply those patches, despite the ROM being AOKP-based. Unsurprisingly, that patch failed. I wasn't too concerned, because on the second attempt I just manually used the aokp switch and then it patched without a problem.

I've attached the log files of both attempts, just in case you want them for diagnostics or anything else. The first one is when it automatically detected AOSP and the second log is when I told it to manually use the AOKP patches. Thanks again, and keep up the great work!