yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] mateorod:
Webedard is looking into bringing support for a wider variety of AOSP roms. Right now, we only support straight AOSP and deodexed factory images.

Well, I think there is another problem then. I had you run the v6 patch because it is so simple that it cannot break a proper install. Pdroid is a very complicated thing and so there is always the possibility of some obscure error. But the logs told me everything was successful in your case.

Here is what is happening, and I can't necessarily tell you why this is happening, but somehow you are flashing system apps that are incompatible with the ROM that is currently running on your machine. There are things that can cause this, maybe the rom on your PC was a bad download, or corrupted, perhaps you had an aborted flash and did not realize it, or something even different out of your control.

But the fact remains that the system jars you are using the auto-patcher on do not mesh with the ones on your device. This is a fact, we now know. The v6 has very simple edits, everything could go completely wrong (which is basically impossible with the patch command, but for arguments sake) and you would face nothing more crippling than a FC. The logcat complains of ServerThread, which I have only seen in incompatible jar situations (of which I have seen plenty).

This is what I would ask of you. Download a whole new nightly, run it for v6 again. Put the rom and the update.zip on your device then flash the rom and then update.zip in succession. This should work for you and then you can pursue pdroid.

Now there are mysteries in this world; we all must recognize the ineffable. Perhaps there is a different story, a newness which will awaken our minds. If for some reason this latest tact still produces boot loops, then I will make an update.zip for you personally and we can see if the setup is somehow damaging your files.

ahhhh...that's what I'm talking about.
[Android Software/Hacking General [Developers Only]] dirtyreturn:
http://droidbasement.com/galaxy/roms/cm10/p4tmo. I do not intend to try to piss you off or anything. It is frustrating. This rom does not want to seem to get patched. I have tried the windows patcher and linux. Last night's attempt as I already posted stopped com.android.phone.
[Android Software/Hacking General [Developers Only]] mateorod:
Well, the times you entered a date on the command-line? You want the date of your patches to be sometime right after the build date of your rom. Looking at your download page, the latest build is from 20120816. So the command most likely to patch this rom is :

./auto_patcher cm-10-20120816-EXPERIMENTAL-p4tmo.zip pdroid cm10 20120806

Do you see how that works?

Jelle: Do you see how his rom fails to patch at the ServerThread? That is due to the same incompatiblilities that you face; those patches are from a different set of system.jars.
[Android Software/Hacking General [Developers Only]] dirtyreturn:
Yes, thanks for your replies and work on this. I am still really on gingerbread with my sensation- patched the rom with svyat's patcher. So far all the cm10 nightlies patch fine and do not loop for the nexus. The aosp-jb roms do not seem to be updated as often and I'm not so sure I should 'dirty' flash cm10(if i were to do that - would i have to repatch the rom), so the aosp-jb roms are 'maybe???' a little more stable? All the aosp-jb roms fail at i think server.thread, maybe.

Yes, the code for terminal is what i had tried the other night and got com.android.phone has stopped. You had mentioned to wait for the update. Again, thanks for your work, atleast i can use pdroid with cm10 so not much need to whine or whatever i guess. Appreciate it.

Edit- I gave the p4tmo cm10 tab another try, patching was successful, did not loop. Using the 20120806 patcher build again it still gives com.android.phone has stopped. Attached is the succesfull patch with the process error.
[Android Software/Hacking General [Developers Only]] koz:
ratelutz - you ever get this working on your HD2 with PA? I've tried a couple roms (PA with JB & Energy with GB), but neither work when I go to start Pdroid.
[Android Software/Hacking General [Developers Only]] mateorod:
I haven't had any reports on aosp-jb for awhile. I haven't had a chance to test those patches myself, as it has been a challenge keeping up with aokp and cm10. I will build for grouper in the next day or two and test.

So the 2.1.1 patcher is giving you phone FC's still? The RIL deletion is new, we had thought it was fixed. Maybe we missed something that affects a few carriers. This function was put together by pastime, I will see what he thinks. If you could grab a log cat, that would be helpful.
[Android Software/Hacking General [Developers Only]] xMemphisx:
I cannot get this working with JB-AOSP roms at all (GSM Galaxy Nexus). I'm running on OSX from the command line, and it gets about halfway through, gets to the boot.img file... and then says "File to Patch" and outputs the following

... applying boot.img.patch ...
The text leading up to this was:
--------------------------
|--- a/init.rc	2012-07-24 08:30:41.117467102 -0500
|+++ b/init.rc	2012-08-06 13:16:20.508878999 -0500

It does this every time and never works.

I've tried using "Revolution" Rom, AOKP, and 2 different AOSP roms (even specifying aosp-jb)

My command looks like this...

./auto_patcher ROM.zip pdroid aosp-jb

Here's the AOSP Rom that I WANT to be using:

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

But I cannot get this working on Windows or on OS X and it's getting really frustrating.
[Android Software/Hacking General [Developers Only]] mateorod:
Please upload the logs generated by the program, otherwise I am blind.
[Android Software/Hacking General [Developers Only]] mateorod:
That ROM is odexed, which by definition is not meant to be modified. We have spoken about adding deodexing, but that usually is found in factory images, which have their own complications, and generally need special unique attention.

There is a deodexed version at that site, which your Dev recommended anyway. The Roms must be deodexed to work with the auto-patcher.

In addition, you are not using the latest version of the patcher, check our download page. And you are entering the dates wrong, no periods are used,, e.g.20120826 is correct. Check the list of available patches by ./auto_patcher romname.zip -h.

You mentioned that aokp-jb isn't working, but I say it is. So if you have trouble with an aokp-jb ROM, post log. The aosp Roms can vary wildly, we support the Nexus and Galaxy families, other devices are unknown. Not "not working", just unknown due to limited data.
[Android Software/Hacking General [Developers Only]] pastime1971:
could you post a logcat ?

your device uses SamsungHCRIL.java and it should only depends on RIL.java... :(
[Android Software/Hacking General [Developers Only]] dirtyreturn:
https://dl.dropbox.com/u/36695231/SGH-T859/Paste.txt ,hope it does some good.
[Android Software/Hacking General [Developers Only]] mithrial:
Hey,

I just want to say, that the patching of CM7 (nightlies; only PDroid as addon) still doesn't work. The patcher runs through but after flashing my Desire bootloops with the same error messages I posted months ago.

Was someone able to patch CM7 and could give me a hint?
[Android Software/Hacking General [Developers Only]] pastime1971:
it helps a lot, but i still can't figure out why it happens.

could you post me a link to the ROM zip that you were patching ?
[Android Software/Hacking General [Developers Only]] HyperCriSiS:
Oh no, paching went fine but PDroid still does not work :-/

Using ROM:

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

And I also cannot find Paranoid Android. My fault? :confused:

How can I add it?
[Android Software/Hacking General [Developers Only]] dirtyreturn:
http://droidbasement.com/galaxy/roms/cm10/p4tmo/cm-10-20120816-EXPERIMENTAL-p4tmo.zip
[Android Software/Hacking General [Developers Only]] xMemphisx:
Downloaded de-odex ROM version. Tried again... still failed.

GSM Galaxy Nexus. AOSP JB Rom

Log:

http://pastebin.com/Eqs8k7Vz

Rom:

http://xdaforums.com/showthread.php?t=1737849
[Android Software/Hacking General [Developers Only]] jelle2503:
Patching working fine now. Must've been user error lol. Thanks

Only thing I did now was grabbed the nightly from my phone sd, which i had already flashed.

edit: weird i checked MD5 sum, both files match md5 from getcm, so the one I had downloaded with my PC isn't corrupt either. I didn't change anything except update the three autopatcher files in AP folder..
[Android Software/Hacking General [Developers Only]] mateorod:
I don't know what you mean about finding Paranoid Android. I will need more info to help you. You ran the autopatcher, flashed the update.zip over the rom you patched and then what?

Do you get boot loops or FC's? Or does Pdroid say your platform is not supported when you install it?

If bootloops or FC's, please link to a logcat. In either case, please pastebin the log generated by the Auto-Patcher.

I believe we had reports of successful pdroid patching recently. What does your log say? I haven't looked at CM7 in awhile, it has been work enough staying up with all the Android 4.x stuff.

We need the details to try and help.

I have addressed this a couple times recently, I thought to you but maybe not. Our patches for aosp-jb aren't addressed towards heavily modified builds. AOSP, as it comes out of the can, only has framework.jar and no framework2.jar. The framework2.jar has been added by kangers like Cyanogen to allow them to squeeze more code into the framework.jar.

The rom you are trying to patch has had framework2.jar added already. So when our patcher tries to add it, the patches fail because it already exists. I am looking into adding a patch that allows for this scenario. But it isn't ready yet, simply because it is hard and we keeping up with everything else takes time.

I know you are frustrated, but we have a bunch of options offered here that aren't available anywhere else. PDroid support was halted by its developer midway through CM7. As you can see, some users of the OS it was meant for are still coming here for help. We have been able to bring it to the majority of available roms. I guarantee that you have a rom for your device that we can patch. We are working double time on expanding our support, and do so with every update.

Servicing that particular ROM is in the plans, and will hopefully be available soon. But for now you will have to try aokp-jb or cm10 if you want PDroid. If the aokp-jb for your device fails, try the cm10. I will move the aosp-jb patches that allow for a framework2.jar up a few slots on my to-do list.

Good luck.
[Android Software/Hacking General [Developers Only]] xMemphisx:
I apologize... did not mean to come off as frustrated with you guys, or the work you've been doing (i'm very appreciative of it). I was just frustrated trying to make it work in general -- and with my inability to make that happen. Thanks for the feedback and I will look into it more to see if I can get it working with aokp or cm10.
[Android Software/Hacking General [Developers Only]] mateorod:
No worries, I think I will have that option next update. So before next Tuesday at worst.

Heads up now, I will be gone next week so thread support will have to be crowd-sourced. Take care of each other, OK?
[Android Software/Hacking General [Developers Only]] LMBBananaJoe:
i got slimrom 2.5.0-gt-i9100 succesfully patched with auto patcher 2.1.1 pdroid cm10 patch :good:

now trying it out
[Android Software/Hacking General [Developers Only]] tonyp:
It looks like the SamsungHCRIL.java file got deleted, which shouldn't have happened.
[Android Software/Hacking General [Developers Only]] mateorod:
Will you try the attached update.zip in this deodexed version of your AOSP rom? It should work, I made it with my test-version of the new function. I attached the restore.zip for professional reasons, but you can also simply reflash your ROM if it doesn't work.

But this should work for you no problem. How to integrate this into the patcher is another question, for this test I just added an "aosp-mod" romtype.

Edit: XDA wouldn't let me upload restore for some reason...just keep a copy of the rom on emmc or sdcard, just in case.
[Android Software/Hacking General [Developers Only]] InfinityFTW:
Has anyone tried TabletUI on touchwiz ROMs? If it works, I will freak out!
[Android Software/Hacking General [Developers Only]] mateorod:
Oooohh, I wanna know this too! Run your rom through the patcher...if it pumps out an update.zip then it will work. If you want to use Launcher2 (I don't know if they have a stock launcher or what..) you will need to flash a companion zip that edits the margins. But you can always use whatever launcher you normally do instead...let us know and post the log if it doesn't work please.
[Android Software/Hacking General [Developers Only]] InfinityFTW:
FYI, it is a touchwiz JB ROM for the Galaxy tab 2 7"

Tomorrow I will do the following:

Make ROM, Try to use tabletUI, report back ;€
[Android Software/Hacking General [Developers Only]] dirtyreturn:
pastime1971/materod if there is any further development . I'm sure there will be. Like, if you were to focus on that specific rom or have any untested parcheesi and so forth. Ill run them, if they patch, flash them or something. Or if you have any status on pershoots cm10 send a pm or something. Only if you feel I could be of some service.
[Android Software/Hacking General [Developers Only]] InfinityFTW:
Got this error with APG: http://codepad.org/E1f7rOkV
[Android Software/Hacking General [Developers Only]] mateorod:
We probably need the Log file. The rom needs to be deodexed, and a zip not a system.img, BTW.
[Android Software/Hacking General [Developers Only]] InfinityFTW:
oh, im sorry! It justtold me if i wanted to put the error on pastebin.

So i browse to the zip file, and it says that the zip file is selected. But in the menu below, it is just blank. It's a JouchWiz JB ROM with PhabletUI.

When i drop it, it says ''invalid ROM file'' Whats wrong?
[Android Software/Hacking General [Developers Only]] kobik77:
As a verification, ApG would only allow you to select or drop a ZIP file type.

What's the exact file name of your ROM?
[Android Software/Hacking General [Developers Only]] poncik:
i'm using nikez jb rom on my desire. i tried to patch it before several times, all failed. now i tried with aosp-mod parameter like this:

./auto_patcher Evervolv-turba-3.0.0p10-bravo.zip pdroid aosp-mod 20120809

got too many "hunks ignored" messages but finally update.zip created. i flashed it and its working now.

but new file sizes are smaller than originals. will it be problem in future or its normal?

edit:

20120817 didnt work (pdroid didnt start after flashing update.zip), log attached.
[Android Software/Hacking General [Developers Only]] mateorod:
What do you mean? The patches from 0809 worked but not 0817? Why not just use 0809 then? And what do you mean by didn't work? Boot loops, or pdroid did not work or what?

Will you link to the ROM?

The sizes of the files is normal. Some side effect of the email binaries, happens with apktool as well. We take the debugging stuff out additionally, although I can't swear that effects the size.

The reason for all the hunks ignored is because that patch is looking for the classes that are in framework2.jar in order to delete them, but since they are already moved, the patch is ignoring that command. So it is ugly, but has no bearing on the patching process functionally.

This patch set wasn't meant to be public yet, I just pushed it for pastime to look at. Are you using ApG or did you clone it yourself? And if ApG, kobik what branch are you updating from? It should be master, the other branches are WIP and will likely cause problems for people.
[Android Software/Hacking General [Developers Only]] otwo76:
Failing on a CM10 rom

I've tried using ApG1.0.0.9 to patch a CM10 based rom for HTC One X - ([22-09] [ROM] CyanogenMod 10 - Endeavor Unleashed | 017), but I've failed miserably.

$ ./auto_patcher ../../cm10_endeavoru-ota-eng.noeri-017.zip -h

The Auto-Patcher v2.1.1

### verify tools ###
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!! error: patch tool is missing
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

! please refer to /cygdrive/c/android/ApGPackages/ap/log20120923002127 for any debugging

! patching failed.
! it may be possible to patch /cygdrive/c/android/cm10_endeavoru-ota-eng.noeri-017.zip using other patch version

The Auto-Patcher v2.1.1
pdroid 1.32 patches 2012.09.13.
v6supercharger patches 2012.08.17.

[snip]

o2@otto3 /cygdrive/c/android/ApGPackages/ap

The log contains:

$ cat log20120923002127
ROOT= /cygdrive/c/android/ApGPackages/ap/
TOOL= /cygdrive/c/android/ApGPackages/ap//patch_tools.tgz
ROM= /cygdrive/c/android/cm10_endeavoru-ota-eng.noeri-017.zip
ROMX= C:\android\CM10_E~2.ZIP

### verify tools ###
/cygdrive/c/android/ApGPackages/cygwin/bin/patch
/cygdrive/c/android/ApGPackages/cygwin/bin/tar
/cygdrive/c/android/ApGPackages/Java/bin/jar
/cygdrive/c/android/ApGPackages/Java/bin/java
/cygdrive/c/android/ApGPackages/cygwin/bin/cpio

Patch itself is there:

$ patch -v
patch 2.6.1
[snip]

Any pointers on what could be going on?

Cheers,

otwo76
[Android Software/Hacking General [Developers Only]] TheDrake:
I solved executing:

$ ./batch.sh

from cygwin "manual prompt" that appears after pressing Manual Patching button. It will make the appropriate patch.tgz from git files.

Then, try again restarting ApG.

Bye,

Paolo.
[Android Software/Hacking General [Developers Only]] :
*deleted
[Android Software/Hacking General [Developers Only]] poncik:
i tried 0817 first, after flashing update.zip, pdroid didnt work, said "not supported"

now i'm using 0809 without any problem.

and yes, i downloaded patch set myself but using it with ApG manual mode.
[Android Software/Hacking General [Developers Only]] otwo76:
Thank you very much Paolo,

that did the trick :)

Cheers,

otwo76
[Android Software/Hacking General [Developers Only]] magisterludi:
Regardless of which rom type / patch date I choose, I hit failures on SurfaceView.smali every time. Would anyone be able to shed some light on the issue? Assistance with a resolution would be so very appreciated.

Here is a paste of a recent failed attempt.

http://codepad.org/9hkgrs1z

update.zip for ROM found here http://dev.crackflasher.com/tucstwo...on Kexec/Jekyllv136-CM9-UNOFFICIAL-signed.zip

ROM Dev Thread here http://www.droidrzr.com/index.php/t...te-jekyll-cm9-v13-92012-now-with-ota-updates/

:edit:

I have tried manual patching using a standalone install of cygwin , the ApG auto method, and manual patch from the cygwin environment bundled in with ApG. fails all around.

::further edit::

CDMA Moto Razr. Safestrap recovery 2.11

v6supercharger only mod works flawlessly. woot! So helpful, thanks devs

Dropbox link of unedited SurfaceView.smali

https://dl.dropbox.com/u/16863630/SurfaceView.smali.orig
[Android Software/Hacking General [Developers Only]] CollegeDev:
Thank you for your quick answer. But I'm using Pdroid on cm7 long time ago with same settings and it is very stable at all. I can't see any FC before system soft-reboot. That's the problem.

I thinkt it comes with code changings since android ICS. So we need some additional changes in Pdroid to solve the Problem. I will try to get logcat information while soft-reboots.
[Android Software/Hacking General [Developers Only]] chris29020:
no luck with the older nightly either guess ill keep trying roms as they come out lol this phone is a headache i swear
[Android Software/Hacking General [Developers Only]] mateorod:
Patches for current CM7 nightlies now added!

Download autopatcher20120627v066 from the OP.

Thank pastime1971 for finally figuring out the patches here
[Android Software/Hacking General [Developers Only]] skillazis:
failed autopatching butta v4.0.05 touchpad pdroid

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

tried all the patch dates, any help?
[Android Software/Hacking General [Developers Only]] SecUpwN:
Ok, fair. At least you got the balls to tell me the truth. Last question to this story: Would you please hand me a script or linux command to try ALL patches in a given folder? So that I can just sit and listen to some funky music while your patcher works it's ass off until it succeeds? ^^
[Android Software/Hacking General [Developers Only]] mithrial:
I hate to say it but still doesn't work.

(./auto_patcher cm-7-20120624-NIGHTLY-bravo.zip pdroid cm7)
[Android Software/Hacking General [Developers Only]] pastime1971:
@ CM7 users,

maybe i missed the memo, but to me, it looks like CM7 changed from nightly to weekly. (can anyone confirm ?)

if that is the case, the next nightly weekly will be up this coming sunday.

i am building/cumulating patches everyday, so i will be ready for it.

once CM7-20120701 is out, we will test it again and see if we can fix it.

i appreciate your support and patience.
[Android Software/Hacking General [Developers Only]] chris29020:
ok i had no luck with any rom currently out for the bionic with any patcher using every date available am i just left with the option of compiling with the pdroid source and if so exactly how hard is it?
[Android Software/Hacking General [Developers Only]] Omnichron:
will this work on my droid 2 global?:confused:
[Android Software/Hacking General [Developers Only]] mateorod:
Not too hard at all, and compiling your own ROM is a very rewarding step in opening Android up for yourself.

Let me look at some of your roms today, and I will get back with you about what we can do next.

Depends wholly on the ROMs available for the device. AOKP and CM9 roms are patchable for every device. We have patches for CM7 as well, but the recent changes for this ROM are giving us some stability hiccups.

Just pick a rom and try it following the directions in the OP.
[Android Software/Hacking General [Developers Only]] pastime1971:
today's nightly weekly is up.

at the same time, i built a cm7 nightly for bravo as well as pdroid-cm7.

looking at the weekly and my build, there are 75 smali differences in framework.jar, and 9 smali differences in services.jar

i don't really understand how cm7 weekly is built, and why it is different from my nightly... :(
[Android Software/Hacking General [Developers Only]] pastime1971:
one more test: we usually make patch between nightly build and pdroid build, but this time, i made a patch between today's weekly from cm and my pdroid build.

could cm7 bravo & ace users test it ?

ace :

weekly cm7 rom, http://get.cm/get/2VD

pdroid framework (attached)

bravo :

weekly cm7 rom, http://get.cm/get/2VG

pdroid framework (attached)

edit: install the weekly above first, and then flash pdroid zip attached.

edit: hmm. i can't remove attachment. do not use attachment.
[Android Software/Hacking General [Developers Only]] mithrial:
Didn't work for me.
[Android Software/Hacking General [Developers Only]] pastime1971:
for CM7, we will have to stop its support in auto patcher.

i will compile the whole rom for bravo with pdroid and upload it on my mediafire.

hopefully, cm7 won't get updated any further. (development is really slow as it is finished...)

edit: i will compile and upload pdroid/cm7 rom for each officially-supported device upon request (pm me)

edit: this week's bravo/cm7/pdroid http://www.mediafire.com/?eh7pech1ejheto8

edit: this week's ace/cm7/pdroid http://www.mediafire.com/?9cunxhgpma3b9a1

edit: our patcher should still work for CM7 based roms.

it just doesn't for CM7 nightly for some reasons

.
[Android Software/Hacking General [Developers Only]] mateorod:
Now that's commitment! Thanks, pastime!

I will continue to tinker with it...I believe that there is a solution but I'll be damned if I know what it is right now.

I think pulling support until/if we resolve this problem is the right idea. Better to deliver on what we know works while we look into what CM did that is throwing us off.