yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] alen1901:
Few mods here are for hdpi too, others needs dpi change only i think, maybe few pngs resolution change too.

Sent from SpeedMachine i9023
[Android Software/Hacking General [Developers Only]] Articudos:
Hope someone can work for hdpi devices:D

This is amazing tool, build-from-source in windows(cygwin). (Didn't read carefully;))

Sent from my Marmite flavoured rasbean crespo
[Android Software/Hacking General [Developers Only]] alen1901:
Yeah it is, i tried that, and guess what, i dont have option to download sources with that program. Also in this program, for Windows, there isnt a key/tab for build from source hahah. I was going to maintain that mods but i gave up because it is pain in the ass with windows, and i dont have free machine for ubuntu.

Sent from SpeedMachine i9023
[Android Software/Hacking General [Developers Only]] mateorod:
Well, that certainly sounds like stuff that is perfect for us. I will look at it tonight, thanks for the tips!

We didn't get pd2.0 working until Android 4.1.2, which came out maybe 3 days after pdroid 2.0 did. But we have had repeated problems with that device by Quarx. It is definitely "non-standard" CM10, although I don't know if that is based on hardware limitation or Quarx's preferences.

Although I haven't put any error messages related to to that in the program, AFAIK. Still true though, sorry. I would try again when 4.1.2 comes out for you.

You were a big part of that happening, so right back at ya.

I am guessing that you suggested adding one of the PDroid frameworks. Which pastime created for ICS and we then bumped up for Jellybean. Agrabren has integrated the Auto-Patcher into his Disarmed Toaster series, although to my shame, I still haven't gotten around to investigating exactly how he does that. I should, and soon. But thanks for the words. Building and compiling is actually a lot easier than people expect, but it does signify bigger things. Once you have built your own ROM, you pretty much have the Android bug bad.

My man fat-tire says your first ROM makes you an Android ninja, and I can't disagree with him.Good luck.
[Android Software/Hacking General [Developers Only]] muhse:
I9300_Omega_v31_XXDLJ4_Jelly_Bean

Hi everybody,

first of all, thanks for your great work and all the effort you put into making pdroid and other awesome tool work on all the different custom roms that are out there!!!!

And second comes my problem:

To put my it into context: I'm not a complete computer noob, but I'm a 100% Linux noob and I upgraded to a smartphone just 2 months ago from an 7 years old samsung, so I'm pretty newbish on Android, still ;)

Anyways got an Galaxy S 3 and have root since the first day, tried several custom roms and finally arrived at the omega rom for usability reasons (girlfriend does not want to get used to cyanogenmod ;)). Today I updated to the new Jelly Bean-based I9300_Omega_v31_XXDLJ4_Jelly_Bean rom. Also I searched again for a privacy protection solution because I was unsatisfied with the before solution (already two months ago I tried - unsuccessfully - to install pdroid on the omega rom with the old autopatcher that needed cygwin to run. Now with the pdroid 2.0 and the new autopatcher I tried it another time and finally ended up spending the whole Sunday on trying to get proid 2.0 running on my phone but I failed :crying: . I'm really frustrated that I'm obviously not able to get things running so I finally decided to ask for help - here :)

The custom rom I try to patch is I9300_Omega_v31_XXDLJ4_Jelly_Bean (Date: 19/10/2012) and the link is http://xdaforums.com/showthread.php?t=1663656 (am I allowed to post links to other xda-threads?).

My goal is to get pdroid 2.0 ([APP] PDroid 2.0 [2012-10-24 v1.50]) running.

The Autopatcher version I tried is ApG.2.0.0.0.exe.

I attached the error log from the autopatcher and I really hope that you can tell me what I'm doing wrong or directly attach a patch.

Thanks in advance!!!

muhse
[Android Software/Hacking General [Developers Only]] mateorod:
As an fyi, we don't have ANY pd2.0 that works on 4.1.1. Only 4.1.2 and up.

This is something that, no matter how much I pack into the OP, some of the info is left off. It is a fine line between providing the info and not wanting to overwhelm everyone into a 'tl;dr' mindset.

But we don't have any Pdroid or Pdroid2.0 patches that work with skinned AOSP. Which means anything based off manufacturer firmware. Even if it is custom made, they deviate far enough from Android source that we don't have patches.

The only thing you did wrong was minor, and that we got rid of the 'aosp-jb' and 'aosp-mod' stuff. Just use 'aosp'. But the patcher figured out what you meant, and the log you posted was using the correct patches. They just won't work for that rom.

I want to say that it isn't that we can't support it, just that we don't. Someone would have to join the team who builds Samsung stock firmware. The source (for 4.1.1 at least) is out there, so we can make patches for it. But we need to find a maintainer. wbedard is considering building for some skinned aosp, so there is at least one glimmer of hope.

Good luck finding something that works for you. We do have patches that work for your device, just not that ROM. You could always ask your ROM developer to contact me, we can support any rom that way as well.

I will add some of this to the OP today, I will just try and be judicious.
[Android Software/Hacking General [Developers Only]] muhse:
Hi mateorod,

thank you so much for your quick answer and again for your great work. I wrote to indie, the developer of the Omega rom, and probably he'll contact you. Would be great if you add support for this type of rom but there is too much out there to do it all, of course. I'll keep on checking this thread and the forum and probably the glimmer of hope materializes into a real patch :)

Greetings,

muhse
[Android Software/Hacking General [Developers Only]] Landvogt:
---------------------------> Please ignore my post. I updated to a newer nightly build with Android 4.1.2 Had sadly still no luck with pdroid and pdroid 2.0 <--------------------------

Thank you very much for the fast and helpful reply!

Sorry that i overlooked the incompatibility of Android 4.1.1 and pdroid 2.0.

I've tried to patch the ROM with proid but sadly had also no success. The log file is here: codepad.org/BI7wCb5d (due to spam prevention outside links can not be posted by me so only text).

I guess that the problem is somewhat the same as with pdoid 2.0. Or is there any other possibility to get pdroid working?

Thanks again!
[Android Software/Hacking General [Developers Only]] ilker555:
jelly BAM

Hi,

i tried to patch jelly bam ROM without success. I always get a message that the patch failed. Jelly bam is a combination of aokp, cm10 and paraoidandroid and i tried several ROM types in autoptacher without success.

Can anyone help?

ilker
[Android Software/Hacking General [Developers Only]] KicknGuitar:
Not to criticize your choice but simply to make a suggestion. Quarx's "universal," "non Defy specific" CM10 4.1.2 is for both Defy and Defy+, it works really well compared to the older builds (some report with the latest update (v4) great battery life). The only downside is if you're a MB525, the build will read MB526. :p

Visit Quarx server and grab the following to try the latest out,

• CM10-20121018-NIGHTLY-mb526.zip

• update_for_18.10_v4.zip
[Android Software/Hacking General [Developers Only]] Landvogt:
Thanks for the advice! I guess this shows that i am completely new to android :)

I somehow imagined that the MB525 with the green lens is not compatible with the newest builds.

Thanks again!

Edit:

I've updated to the newest nightly build (CM10-20121018-NIGHTLY-mb526.zip and update_for_18.10_v4.zip) and everything is running fine.

Sadly the patch process for pdroid ( codepad.org/gEN06OUp ) and proid 2.0 ( codepad.org/P8kjQa3F ) are both not working with this build (CM10-20121018-NIGHTLY-mb526.zip).

Any suggestions?

Thanks!
[Android Software/Hacking General [Developers Only]] AndroidXDAUser:
Error Patching SMOOTHROM 4.0 [4.1.2] with AutoPatcher 2.3.0

Hi,

today I tried to patch the SmoothROM 4.1.2 for Nexus 7 Tablet.

Even using latest AutoPatcher and different options I could not generate the patches.

See attached LogFiles and Link to SmoothROM (http://xdaforums.com/showthread.php?t=1899024)

It would be great if this could work.

Thanks to your work
[Android Software/Hacking General [Developers Only]] mateorod:
Well the release says based on Cyanogen...with kangs like this there is no way that the Auto-Patcher could know what the base rom was, so the user has to bring that knowledge with them.

Did you try

./auto_patcher Smooth.rom pd2.0 cm

Anyone else having problems, I need logs, and a link to your ROM can really help. That is how I found out the base of the rom above...
[Android Software/Hacking General [Developers Only]] AndroidXDAUser:
Sorry that I have not directly send it to you.

YES, I have already done that. Autopatcher has generated update.zip and restore.zip (see attached log).

BUT, when I apply update.zip there is following error an my Nexus 7 (clockworkmod):

ClockworkMod Recovery v6.0.1.0

--- Installing: /sdcard/update.zip
Finding update package...
Opening update package...
Installing update...
set_perm: some changes failed
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted

I have applied update.zip on different ways:

1. format / clear everything, apply SmoothROM.zip, boot, restart recovery, apply pdroid update.zip

2. format / clear everything, apply SmoothROM.zip, apply pdroid update.zip

Everytime same error when running update.zip

That is why I thought, that it maybe has to run without option "cm".

Thanks for help, when I can do something please let me know.
[Android Software/Hacking General [Developers Only]] mateorod:
Hmm...well that is relevant information. Sounds like they must have something, at the very minumum, non-standard in their updater-script. We simply copy the original updater-script into our zip file, and if it is made correctly, there is no problem. Which there has never been elsewhere. I will look at that today, thanks for the report.
[Android Software/Hacking General [Developers Only]] mateorod:
I have left just the relevant sections of the output in the above quote.

That isn't an error. As we have discussed here several times ( I know it is a long thread, I am not suggesting you should have read it all) that is a known operation.

When patching fails on this particular file, the script offers to paste in a pre-patched version of that file. So you have a complete, error-free patch made for both of those roms. There is no error. If there are errors patching, the Auto-patcher will not produce an update.zip. If you flash an update.zip, it will work 99% of the time. And the times it does not, that has been found to originate with the ROM, not the patcher.

I have added a line to the log that better explains what happens here.

We also have a file that manages 'unconditional copies', called smali.txt (example from CM10). I will probably add GSMServiceStateTracker.smali to that list since it fails so reliably.

But something still needs to be done to make this less confusing. I was blaming the confusion on the fact that ApG answers the yes/no question for you but it looks like even people who are answering 'yes' on the command-line don't realize what is going on.

Your roms are patched perfectly. I have downloaded, but not checked, SmoothRom. But the problem for that rom is something like 95% likely to be the updater-script packaged in Smooth, since we merely use the existing script. Something non-standard is probably included there.
[Android Software/Hacking General [Developers Only]] mateorod:
Well, it looks like some combo of AOKP/PA/CM10. So if romtypes pa or cm, or aokp all fail, then I guess it isn't patchable. So far we've been able to patch everything that isn't an AOSP OEM skin (i.e. Sense or TouchWiz.)

These device-specific kangs aren't all going to conform to the patches, that isn't possible. But we do pretty good.
[Android Software/Hacking General [Developers Only]] anomalya:
Boot Loops After PD2.0 Patch

@auto-patcher team,

Not sure if it is more appropriate to post on the PDroid 2.0 thread regarding this issue, but I figured I'd start here for help.

It isn't so much the patches that fail - in fact, they work accordingly with pretty much every ROM flavor (cm10, aokp, pa - of the latest builds) I've thrown at it for my SGS2 Skyrocket phone.

The problem comes up during initial boot (after fresh ROM install and flashed patches) when device asks to pick launchers (I don't use stock, so I install after-market), doing so immediately causes the screen to flicker and the device to boot. This happens to all the ROMs mentioned above.

I use the pd2.0,v6supercharger combo MODs exclusively and was able to narrow it down to just the PDroid 2.0 patch being the culprit because it only seems to occur after applying any patch that includes it. (The v6 mod alone when applied works fine.)

This might also just be an isolated incident because I don't see anyone else who's patched successfully shouting similar issues, but perhaps you can deduce more in detail about what might be conflicting behind the frameworks.
[Android Software/Hacking General [Developers Only]] mateorod:
Yeah, I would take that to the PDroid 2.0 thread. If our patches apply and produce an update.zip, I would take that problem to the dev thread until such time as he contacts me with a problem.

Bring him a logcat, and if he thinks it is patcher related, he can let me know. There are still some issues being worked out with Pdroid 2.0, from what I gather in the app thread, which has a mix of auto-patcher/ build from source users. Which is to be expected, of course, it just got released.

But since he is relying on Auto-Patcher to bring the app to the wider-world (and why wouldn't he, that is what we're here for) he will work with us if any problem arises.

As far as reported so far, there are no problems with our port (which will be true right up until it isn't, naturally. Android source code being a moving target and all.) Thanks for isolating it without the V6 first though, definitely a must for debugging purposes.
[Android Software/Hacking General [Developers Only]] anomalya:
I appreciate your advice. As you said about moving targets, I was a little suspicious that maybe something had become obsolete to make the patches break with these latest ROM builds that I've installed (but then again, they did produce update zips).

I'll bring it over to CollegeDev and see what he says - though I'm a little unsure how to go about producing a log for my case, if I can't boot and be able to record logs with the problem from my phone. I'm on a Windows system, so I'll have some research to do about adbs and such.

Thanks much and am always looking forward to your next work!
[Android Software/Hacking General [Developers Only]] mateorod:
I had misread your message, I didn't see that it was as serious as to cause a reboot. But if it happens with every flavor of rom type, it sounds more like a problem with Pdroid 2.0 and your source. ADB would for sure be the way to go, if you are on windows there are multiple tools out there that should set up the drivers you need for you (I seem to recall seeing Naked Driver a lot, although I have never used any of them).

As with any of our mods (info I should add to the OP when I have time) provide the dev with the information you have, as in tell them you used the auto-patcher. And for things like PDroid2.0 or 3gdongle, where we worked pretty closely with the original dev and they are familiar with our program, giving them the auto-patcher logs might be a good idea too. They may not know exactly what to do with them, but it could also give them hints if something is happening they don't expect.

They may say they don't need them, but I will let them decide how to handle that. I would want them...
[Android Software/Hacking General [Developers Only]] cliff03:
I tried to patch new revolt 2.6 but it can't doit.Here is the code

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

ROOT= /cygdrive/d/Downloads/Pdroid tools/ApGPackages/ap/

TOOL= /cygdrive/d/Downloads/Pdroid tools/ApGPackages/ap//patch_tools.tgz

ROM= /cygdrive/d/Downloads/Pdroid tools/ReVolt_JB_2.6_I9100.zip

ROMX= D:\DOWNLO~1\PDROID~1\REVOLT~1.ZIP

### verify tools ###

/cygdrive/d/Downloads/Pdroid tools/ApGPackages/cygwin/bin/patch

/cygdrive/d/Downloads/Pdroid tools/ApGPackages/cygwin/bin/tar

/cygdrive/d/Downloads/Pdroid tools/ApGPackages/Java/bin/jar

/cygdrive/d/Downloads/Pdroid tools/ApGPackages/Java/bin/java

/cygdrive/d/Downloads/Pdroid tools/ApGPackages/cygwin/bin/cpio

### verify ROM ###

### running ./auto_patcher /cygdrive/d/Downloads/Pdroid tools/ReVolt_JB_2.6_I9100.zip pd2.0 jellybean

PATH= /cygdrive/d/Downloads/Pdroid tools/ApGPackages/ap/tmp20121029213417:/cygdrive/d/Downloads/Pdroid tools/ApGPackages/Java/bin:/cygdrive/d/Downloads/Pdroid tools/ApGPackages/cygwin/bin:/cygdrive/d/Downloads/Pdroid tools/ApGPackages/cygwin/usr/sbin

### unzip patch tools ###

### unzip patch patches ###

... result of ROM check: RIL= Smdk4210RIL

### probe rom type ###

**************************************

**************************************

thanks for help

---------- Post added at 05:38 AM ---------- Previous post was at 05:36 AM ----------

same problem patching older version of pdroid

ROOT= /cygdrive/d/Downloads/Pdroid tools/ApGPackages/ap/

TOOL= /cygdrive/d/Downloads/Pdroid tools/ApGPackages/ap//patch_tools.tgz

ROM= /cygdrive/d/Downloads/Pdroid tools/ReVolt_JB_2.6_I9100.zip

ROMX= D:\DOWNLO~1\PDROID~1\REVOLT~1.ZIP

### verify tools ###

/cygdrive/d/Downloads/Pdroid tools/ApGPackages/cygwin/bin/patch

/cygdrive/d/Downloads/Pdroid tools/ApGPackages/cygwin/bin/tar

/cygdrive/d/Downloads/Pdroid tools/ApGPackages/Java/bin/jar

/cygdrive/d/Downloads/Pdroid tools/ApGPackages/Java/bin/java

/cygdrive/d/Downloads/Pdroid tools/ApGPackages/cygwin/bin/cpio

### verify ROM ###

### running ./auto_patcher /cygdrive/d/Downloads/Pdroid tools/ReVolt_JB_2.6_I9100.zip pdroid jellybean

PATH= /cygdrive/d/Downloads/Pdroid tools/ApGPackages/ap/tmp20121029213700:/cygdrive/d/Downloads/Pdroid tools/ApGPackages/Java/bin:/cygdrive/d/Downloads/Pdroid tools/ApGPackages/cygwin/bin:/cygdrive/d/Downloads/Pdroid tools/ApGPackages/cygwin/usr/sbin

### unzip patch tools ###

### unzip patch patches ###

... result of ROM check: RIL= Smdk4210RIL

### probe rom type ###

**************************************

**************************************
[Android Software/Hacking General [Developers Only]] Px80:
Hey,

just want to tell that it worked to create a update.zip for PACMAN!

i will test if pdroid works when i unrooted my phone :)

but i upload the log and the update.zip for anyone how wants to check on it!

If it works, great job you guys!! :good:
[Android Software/Hacking General [Developers Only]] thegodth:
It might be great if auto-patcher can patch deodexed stock rom.

Now it's only available for cm aosp aokp pa.
[Android Software/Hacking General [Developers Only]] mateorod:
Yeah. I can deodex and redex no problem. But I don't think the patches would get us very far. I think that is what is going on with the Revolt JB logs above. (Person with Revolt JB, what does the screen output say?).

I may look at it coming up here, but I don't hold out a lot of hope that our patches themselves will apply.
[Android Software/Hacking General [Developers Only]] thegodth:
Do you try patch from the original source theread?

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

I try to understand "how to" but I can't.

I try to find patch instruction but I don't know where.

If you guys know how to, please share your ideas. :good:
[Android Software/Hacking General [Developers Only]] mateorod:
Yeah, those are the patches we use. You apply those patches to the source code for your rom. I am building for the roms we offer here, and that is about as much as I can do. If you want to get support for Sense or Touchwiz, you will have to build yourself (following the directions you linked to) or find someone else willing to do so. Then we can talk about adding those to the auto-patcher, making it easier for others going forward.

If you are looking for advice as to how to apply the build patches, that thread would be where to go. I am active in that thread, and willing to help.
[Android Software/Hacking General [Developers Only]] thegodth:
Oh.. I just know this all about UI too.

Anyway thanks for your advice and very best auto-patcher project.

If I can find how to patch with deodexed stock I will share it to you.

BUT I hope you will find the way to make patch for deodexed stock rom too.

Best tool ever.

:good: :good: :good:
[Android Software/Hacking General [Developers Only]] psychowood:
Is it possible that using a pre-patched version of the file breaks some other patches that perhaps are included in the ROM? I'm having some problems (imilka's ParanoidAndroid v2.51 for the Galaxy Note) related to the 2G/3G automatic switching.

If you want to check, you can find both the patched and the non-patched jars linked in my signature.
[Android Software/Hacking General [Developers Only]] mateorod:
Such things are always possible. It is a series of trial and error finding out which files are capable of being 'provisionals'. That i one of the reasons that the Auto-Patcher, when run natively, has persisted in asking for permission, despite the confusion it sometimes causes. I want people to consider it as a cause should they encounter errors.

Having said that...at this point I feel like the chances are greater that any problems are more likely attributable to kinks PDroId itself. There seems to have been a good amount of data suggwsting that the provisional copying is working for this fie.

Best thing to do is to grab a logcat and post it in the Pdroid2.0 thread, where both CollegeDev and I can see it. When reporting errors over there, ut is best to mention your Rom info, and any provisional copying, for just that reason.
[Android Software/Hacking General [Developers Only]] Gargantuantua:
Hope this is the right thread you wanted me to post in if I was having trouble with ApG. I did as you said and told it, it was a aokp rom, and it worked. I flashed update.zip and pdroids working but keep getting pop up every few seconds saying "unfortunately the process com.android.phone has stopped." I tried fix permissions but didn't work.