yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] Deviant Ollam:
thanks to all for the fast responses and great work. i'll try manually patching in a little while.

i'm trying to patch these two ROMs...

http://download.cyanogenmod.org/get/jenkins/7104/cm-9.1.0-i9300.zip

http://download.cyanogenmod.org/get/jenkins/12602/cm-10.0.0-d2tmo.zip

...for pDroid (well, pDroid 2.0 i suppose, since that's where things are headed, i imagine)
[Android Software/Hacking General [Developers Only]] ixrs:
I got it working via a linux VM, that's not ideal but it works.

However, after patching pd2.0, I end up with a very tiny update.zip file (144kb). Is this normal? I flashed it via TWRP and tried the pdroid2.0 app but it just kept on giving me the "unfortunately, pdroid 2.0 has stopped" message.

I'm trying to use pdroid 2.0 on the Nexus 7's stable CM 10.0 rom.
[Android Software/Hacking General [Developers Only]] grayfoxmg1:
@mateorod: finished patching smeininja's rom. both the DEC 30th and the JAN 4th successfully patched with the tabletUI patch. Click on each date to grab the .zip of the ROM and patches relevant to it.
[Android Software/Hacking General [Developers Only]] kobik77:
Released a little ApG update to include patch mod in the file name as a user suggested (sorry can't remember who, it was some time ago), so now you can create multiple mods without worrying they will be overwritten.

Windows 32bit users, please let me know if you're having problem running this version, thanks.

http://xdaforums.com/showthread.php?p=31648393#post31648393

And thanks for all who have donated :good:
[Android Software/Hacking General [Developers Only]] m0d:
It would have helped if you attached screenshots below,

Hope this helps: "Specifically: The system cannot find the file specified."

I guess it is trying to Run cygwin without downloading it first.

See image below.

On first run, no manual adding of cygwin or java:

​

Quick question,

I have not tried yet, but have you modified ApG to also check if Cygwin and Java are copied to folders -

Or, are you still just checking the ApG.ini file for them, meaning in ApG.ini the following need to be modified manually if you download and copy them yourself:
[Android Software/Hacking General [Developers Only]] Chaussette_:
I have exactly the same problem than m0d.

Fresh install no a new computer, in "C:\ApG\". If I launch "ApG.2.0.0.0.exe" or "ApG.2.1.0.0.exe" (I tried both), I get the same dialog boxes.

My previous install on my "old" computer still works fine...

I wonder if there was a change on "Dev - Host" server.
[Android Software/Hacking General [Developers Only]] Deviant Ollam:
i get the exact same problem as seen in the other screenshots.

when it starts up, it fails to get update information for [blank] and then launches ApG. the app mentions syncing with GiyHub, but that seems to not happen. Then i see the same message...

Error: Failed attempt to launch program or document:

Action: <ApGPackages\cygwin\bin\bash.exe>

Params: <-- init-file ApGPackages\cygwin\bash.sh>

Specifically: The system cannot find the file specified.

Line#

--> 248: RunWait, %CYGWIN_PATH%\bin\bash.exe --init-file

&BASH_PATH%,,%Hide%

The current thread will exit.
[Android Software/Hacking General [Developers Only]] kobik77:
Probably there was done change in Dec host as mentioned. Although there is a check whether or not Java and Cigwin are installed.

Anyway, I'll look into it.

Sent from my Galaxy Nexus
[Android Software/Hacking General [Developers Only]] ixrs:
The patches that I create via the auto-patcher on linux aren't working, they're missing all the system files. Any clue as to what's going on?

Edit: Using the latest version of auto-patcher fixes things. I might be able to make patches if people want them.
[Android Software/Hacking General [Developers Only]] mateorod:
Thanks...did you get a bootloop?

I saw your earlier pm. For ApG you should pm Kobik, he does the ApG. I will for sure keep you in the loop as we slowly make our way to wider formats. There is a possiblity of a PDroid discussion board, I will be in touch about that. Thanks Grayfoxmg1!

My guess was downed mirrors...thanks for looking Kobik.
[Android Software/Hacking General [Developers Only]] desalesouche:
same here...what to do?
[Android Software/Hacking General [Developers Only]] kobik77:
For now try version 2.0.0.0.

It seems that dev-host are ok and it's Windows 8 that is causing me real headache with this issue.

Sent from my Galaxy Nexus
[Android Software/Hacking General [Developers Only]] Chaussette_:
Hello kobik77,

I also tried version 2.0.0.0 on my fresh install (ie empty "C:\ApG" folder), and there is still a problem. I can extract manually cygwin and java, but can you just post the content of the .ini file in order to tell ApG these plugins are already installed ?

Thank you!

EDIT : I finally solved that problem.

I changed cygwin path in "ApGPackages\cygwin\" .bat .sh files. Then I altered cygwin and java version in the .ini file to something "incorrect" :

Then I launched ApG and checked for updates, and ApG fixed correctly the .ini file to :

If it can help...
[Android Software/Hacking General [Developers Only]] kobik77:
There are two problems here:

1. ApG fails in downloading packages.

One of ApG functions I'm importing and using for downloading packages have suddenly misbehaving or at least I though so.

The only reason I'm thinking of is that I've switched to Windows 8, hence, installed everything fresh and there is something wrong with my configuration.

Or maybe there is a change in Dev-Host after all.

2. ApG screws up in its packages verification because of a wrong assumption I've made.

I'll into this again tonight, hopefully I won't fall asleep in front of my PC like last night :o

In the meanwhile you can download the packages manually and add the following lines to the ApG INI file as Chaussette_ (Thanks!) suggested.

[JAVA]
JAVA_VER=20120904072035
[CYGWIN]
CYGWIN_VER=20120916205609
[Android Software/Hacking General [Developers Only]] les02jen17:
I had to reformat my Windows 8 computer and in doing so, and I forgot to backup my ApG folder (I remember using the version 2.0.0.0, then) and seeing that there's a newer version (2.1.0.0) available, I've tried it but unfortunately I'm getting the same errors as the above people. I tried 2.0.0.0, it seems to work, but once it tried to download java and cygwin, a similar (if not the same) error pops up. I'm waiting for a fix and I'm currently trying to remedy it by downloading the said packages separately, as mentioned above. I hope it works. I'll update this post if it does.

UPDATE:

It worked! :)
[Android Software/Hacking General [Developers Only]] Deviant Ollam:
i am not running Windows 8 (honestly, i'm pretty shocked at the number of folk here who seem to be... most people on XDA use their computers for real work and not just dicking around, so Win8 is a surprise indeed)

but my Win7 box is a supreme headache with the auto-patcher. someone suggested letting us know the INI modification needed to tell it that CygWin and Java are installed (i tried manually changing the 0 to the current versions of my installations of those platforms) but we could even go one better...

Would anyone who CAN manage to get ApG working be able to just put ALL the requisite files in a single directory (or set of sub-directories) and zip the whole thing? That way, people like us can unzip it, everything is there and allegedly already configured, and we just run ApG. Then, if there are STILL errors we all know that we're playing on an even field.

That would eliminate many of the question marks surrounding all of us, no? Questions about whether people's Java installation is correct or if CygWin paths are properly set, etc.
[Android Software/Hacking General [Developers Only]] kobik77:
I had to make quite a few changes as for some reason some basic functions just stopped working as expected (2K13 bug?) and there were some changes in dev-host too, so I had to rewrite them from scratch.

Currently packages downloading seems slow as hell but I'll be working on a fix.

So for now I've uploaded a new version for you guys to test but I haven't tested it extensively to say the least, so just let me know if you're still having problems.

http://xdaforums.com/showthread.php?p=31648393#post31648393
[Android Software/Hacking General [Developers Only]] Deviant Ollam:
Just fired up the new version, and Java is downloading and extracting! I'll edit/post more here soon with the next result.

EDIT 1: CygWin is now downloaded and extracting, too.

EDIT 2: extractions went well and now the INI file has the following details in it...

[JAVA]

JAVA_VER=20120904072035

[CYGWIN]

CYGWIN_VER=20120916205609

however, i was then met with the error message "Failed getting patch list from patch_patches.tgz"

clicking OK caused ApG to exit. :(

EDIT 3: after trying things yet again from another directory, it seems the GitHub sync worked. however, i couldn't patch pDroid 2.0 since a CM9 rom was too old, but now i'm working on getting a CM10 rom patched. looks promising.

EDIT 4: hooray! i was able to patch the CM9 rom for pDroid 1.0 and the CM10 rom for pDroid 2.0. All looks to be successful. when the new Samsung Galaxy S3 arrives i'll have some options to try out. thanks so much to all for the help in getting the latest version of ApG working!

for the record, it was ApG 2.1.2.0 that worked... thanks so much, kobik!
[Android Software/Hacking General [Developers Only]] Deviant Ollam:
just patched my KAOS rom for my Nexus 7, as well. now that it's all working, i can't believe how easy it is and how happy it makes me.

my latest Twitter post kind of says it all. :) http://twitter.com/deviantollam/status/288090918895108097

in the past, others were so kind in offering to help me patch roms when i was having trouble. i'd like to extend the same offer here... if you, too, are unable to get a rom to patch properly with auto_patcher or ApG, reach out to me with a link to the zip file. if i can get it to patch for you, i will gladly do so and shoot the link back to you where you can download the update zip.

(i realize some might think that is insecure, but it's all about how much you value the help versus how much you might choose to trust me versus how difficult life is being for you in other ways. i just want to do whatever i can.)
[Android Software/Hacking General [Developers Only]] Didgesteve:
Firstly, thanks Kobik for all the hard work that you put into this tool.

I have used it several times in the past and it's always been very easy.

Now I've switched to a new rom: SlimBean 4.2.1

Having shuffled the Autopatcher folder around my pc until I found a place for it to work from, I now get:

!!! error: unknown ROM version 4.2.1

I know there must be a huge amount of work to do for you, every time a new rom comes out.

What can I do to help?
[Android Software/Hacking General [Developers Only]] karamelos:
Wait 4.2.1 not supported for the moment
[Android Software/Hacking General [Developers Only]] grayfoxmg1:
If you were to search through all the pages of the thread(because I don't remember where it's at) you'll notice that we have always had issues with slim beam. So even when 4.2.1 is widely support through autopatcher you might still get issues with SlimBean.
[Android Software/Hacking General [Developers Only]] Didgesteve:
I've used Autopatcher on the last three versions of Slimbean without any problems, it's a fantastic tool. Admittedly I had to do it manually as it didn't recognise the rom, but it did work ok.

I was only offering help :(
[Android Software/Hacking General [Developers Only]] grayfoxmg1:
if you did it manually, then what you can do to help would be to test what ever you did against different versions of slimbean for different devices. If you can get an installation method that consistently works than let mateorod and kobik know about it in detail. Perhaps you could crack the slim bean issue, you might even find that you like it and could become the guy that handles slimbean/autopatcher support.
[Android Software/Hacking General [Developers Only]] devm2024:
Problem with Auto Patcher with pd2.0 patch

Hi again,

With auto-patcher, I tried to generate a patch for

cm 10 jelly bean version 4.1.2 for Pdroid2.0

on my device

Samsung galaxy ace

Everything goes fine, no error, It also generated update and restore zip files,

BUT flashing them is doing nothing

. When I open Pdroid2.0 app, is says "

Unfortunately Pdroid2.0 have stopped"

. It is similar error which I used to get when I had not applied any patch. Can anyone help me?

I have downloaded everything : patches, cygwin, java and it took 3 days for me to do it but now I am not able to make a working patch for Pdroid2.0.
[Android Software/Hacking General [Developers Only]] mateorod:
When you say "But flashing them is doing nothing..." What do you mean, exactly?

Tell me exactly the name of the zips you are flashing. You should only flash the update.zip.
[Android Software/Hacking General [Developers Only]] devm2024:
Yes mateorod,

I have generated two files using command

$ ./auto_patcher beta_1.zip pd2.0 cm

, update.zip and restore.zip, and then rebooted in recovery, flashed update.zip, And then after rebooting when I install pdroid2.0, it starts as says "Please wait while caching Application" for 4-5 seconds and then Stops saying "

Unfortunately Pdroid2.0 have stopped working

" SO I suppose that the patch I am making is not working.

I have recently flashed this awesome rom cm 10 tw5 beta_1 http://xdaforums.com/showthread.php?t=1962762 which is based on Jellaxy 5-12-2012 release.

Please help me.
[Android Software/Hacking General [Developers Only]] echoedge:
So Pdroid 2.0 isn't compatible with 4.2.1 roms?

I tried it on an evolv rom, says 'UNKNOWN ROM VERSION: 4.2.1'

works on the previous update (4.1.2)
[Android Software/Hacking General [Developers Only]] devm2024:
yeah I know it works on 4.1.2 and mine us also 4.1.2. Can you please make a working patch for me?

Any kind of help will be appreciated.
[Android Software/Hacking General [Developers Only]] stealthmouse:
Unable to patch Pdroid or PD2.0 to JB 4.1.2 / RAZR

Hi. I'm dual-booting JB 4.1.2 using SS3.11 and the 3.0.8 (ICS) kernel (patched to work with the recent JB OTA leak), on a RAZR XT912. I can patch V6 on any ROM zip that I have, ICS or JB based, but when I try to patch Pdroid or PD2.0, I get either a smali error or a boot.img error. Not sure if this is just problematic of JB 4.1.2, my setup, or if there's something I can change/delete in framework to get it to work. I searched the forum, but wasn't clear if pdroid/pd2.0 was working for 4.1.2 or not. Perhaps there's a different build date that will work? Tried a few different ones, but couldn't tell. I did get pdroid patch to a JB-based ROM that uses the ICS kernel in original state.

If it's not compatible, will it work with pastime1971's smali patches http://xdaforums.com/showthread.php?t=1554960 ? I thought they were probably the same code as the patcher, but wasn't sure. And I'd try the windows patcher, but don't have Parallels right now. I'm comfortable working with ADB/shell and to a lesser degree, JDK/JRE, but not so much with full-on compiling from git, so if there's something easier than that, I'd appreciate it. Thanks for such a great tool for android!!!

I attached a couple logs - one shows the smali error, the other the boot.img error. Probably just user error, I'm sure...
[Android Software/Hacking General [Developers Only]] mateorod:
You are trying to do too much with the patcher. Don't push it so hard, follow the directions.

For instance, in the first log, you specify aosp-mod as the romtype. But if you look in the directions you quoted, that is not an option. That is only an internal designation.

In the next log, you just use aosp as you should, but you try and force a build date, from sometime in August, even though your ROM was built in December.

The patches from pastime are build patches for jellybean that he and I made. The auto-patcher is the only place with smali patches. You should not need to compile a ROM just use the command line tool here.

./auto_patcher ROM.zip pdroid

The auto-patcher will read your build.prop and attempt the best match. If the match doesn't work, start adding valid romtypes until you have tried all four. Hopefully, one of them will work for you.

The valid ROM types are (cm, aokp, aosp and pa)
[Android Software/Hacking General [Developers Only]] mateorod:
Shoot, I replied to you this afternoon and now I don't see it. Check this post in an hour...sorry.
[Android Software/Hacking General [Developers Only]] grayfoxmg1:
mate's right, when it comes to using the auto_patcher(even apg) sometimes less it more. For instance, even if your rom of choice is an "aosp" rom, they might actually be using the CM or PA repo and are just adding in the things that make that rom unique. Thus when you try and use auto patcher and select aosp it kicks an error, but if you had just selected your patch without specifying your build type, it would have matched it to which ever build was closest and successfully patched. With all the Work Mateorod and pastime put into the Auto_patcher and all of the work kobik did for the ApG UI, I don't ever select my rom type anymore. Auto-patcher is smart enough to figure it out on it's own.
[Android Software/Hacking General [Developers Only]] mateorod:
CollegeDev is the only one who can update Pdroid2.0 it is his closed source app.

Well, let me say that the reason I made this software is so that everyone would have access to the exact same tools I do. So whatever I make over here is the exact same thing you are making over there. We are using the same software. The bigger problem is one of two things:

1) The software isn't working or

2) You are doing something wrong when flashing

Since this version of the autopatcher has been out for over a month, I feel pretty good that the script itself is doing what we want. Are you using ApG? I think kobik added a feature but it seems to be working for others.

I ran your rom through the autopatcher. I can guarantee that it is patching correctly. I see it decompile and I watched it apply the patches, which are our two major points of failure. If this was a new update of the auto-patcher, there might be other places to check, but for now I think that covers it.

I am attaching an update.zip. If your rom is already installed, only flash this update.zip, nothing more.

Edit: Sorry, I made this hours ago, I just never hit submit. It was sitting on my desktop when I just got home.
[Android Software/Hacking General [Developers Only]] stealthmouse:
Actually, I used it on auto first, then with different dates and builds when that failed. The logs I attached were just examples from those later attempts, and to show the error at the end (same one I get when I let patcher choose on its own). I didn't know about repos being different, though, so I'll try the other builds besides AOSP and see what happens. Thanks.

Sent from my DROID Spyder using Xparent Blue Tapatalk 2
[Android Software/Hacking General [Developers Only]] devm2024:
Well big thanks for this update:):):):):). It has made Pdroid2.0 to run. I suppose flashing was correct but I was not able to patch the rom correctly. I will try ApG but it needs big files to download. Unfortunately I dont have that bandwidth.

Thanks again.

Envoyé de mon GT-S5830 avec xda-developers app app

---------- Post added at 11:28 AM ---------- Previous post was at 11:12 AM ----------

But still my pdroid is not able to hide my private data? I am hiding my location and network info but apps are able to access it.

Do I have to do something more to hide my private data?

:o

Envoyé de mon GT-S5830 avec xda-developers app app
[Android Software/Hacking General [Developers Only]] mateorod:
Any problems with a specific mod or app I port is best to take it to the developer. Pdroid2.0 thread can maybe help you with configuration issues. I am not privy to how that program functions internally. And when you ask in that thread, be specific.

The amount of permissions you need to block varies depending on what you are trying to do.

There are several pdroid experts there, maybe they can help.
[Android Software/Hacking General [Developers Only]] devm2024:
Hmm. Yes I am moving my problem to other forum for pdroid.

Thanks again for patching my rom

Envoyé de mon GT-S5830 avec xda-developers app app
[Android Software/Hacking General [Developers Only]] karamelos:
Pdroid2 for 4.2.1 ......Release coming soon (first or second week of February) :D
[Android Software/Hacking General [Developers Only]] vitocor:
Hello friends,

first of all....great Forum here...cool people...and so much to learn from you guys!

Can't wait for the amazing Auto Patcher Update for Android 4.2.1

I have now this great Slim Bean Rom 4.2.1 in ready to flash....but i don't want to use it without Pdroid!

Is there a small possibility that it will come out in nearly future? I mean maybe this oder next month?

Many greetings and thanks

Vito
[Android Software/Hacking General [Developers Only]] yavu:
I need a pdroid patch for Slim Bean 3.1. Please help.
[Android Software/Hacking General [Developers Only]] vitocor:
Hi, which Smartphone do you have?

I know how to do it for 3.1.... I'm also on 3.1 right now with a perfectly working patch....so i can make you one, no problem i guess.

Vito
[Android Software/Hacking General [Developers Only]] yavu:
i9000. Please tell me after done how you get it exactly.
[Android Software/Hacking General [Developers Only]] vitocor:
Here you go...two Attach Files below.

I made the Patches with this...:good:

Comand: $ ./auto_patcher Slim-I9000-3.1.0-OFFICIAL.zip pdroid cm

Enjoy

Vito
[Android Software/Hacking General [Developers Only]] yavu:
Thank you very much. You selected as CM Rom ? I now that autopatcher function if you choose CM, but it isnt CM. Therefore I don't used it. AOSP and CM10 are not the same. I have looked for the needed files in both Roms and there are 2 file different. Its to dangerous I think. If it function than it could be make problems / will be slower.
[Android Software/Hacking General [Developers Only]] vitocor:
Ok, up to you. On my N7000 there are no problems at all, and i've tested a lots of permissions with this cm patch, and all work fine.

Vito
[Android Software/Hacking General [Developers Only]] yavu:
MATEOROD

Can you tel me if its ok to make a pdroid patch for slim bean 3.1 i9000 if I choose rom typ as "CM" ? This is the only possiblity to get a patch without an error. Any choosen Rom Typs as AOSP, AOSP-JB etc. make errors. Please dont tell me that I should make a nandroid and try. Please have a look. Thanks
[Android Software/Hacking General [Developers Only]] grayfoxmg1:
If he doesn't have the device how can he have a look and try? The great thing about auto_patcher is that it will never brick your device. You might get a bootloop or flash faliure that just means your patch failed, but your device will never become un-recoverable. While auto_patcher has a small dedicated team (by small I mean all fit in one room) it is mostly community supported. Thus, the best way for you to find out if it works is to make a nandroid and flash. One of two things will happen, it works, or it doesn't and you just restore your backup.