Related
There is an awesome (non-root might i add) app for those who don't like your info being shared with anybody called PDroid that can be found here;
http://forum.xda-developers.com/showthread.php?t=1357056
Among its huge feature arsenal is the ability to block app's from seeing your IMED, SIM details, sms/mms, etc. It consumes no battery life at all and is very customizable. the only downside is that you must make a patch for each device and each ROM. i took the liberty of making said patch for the Ba2tF CM7 ROM and have posted the CWM-flashable zips for your enjoyment. all you have to do is boot into CWM and flash. if for some reason you don't want your phone to be awesome you can flash the "restore" zip and the original files will be back.
I am not responsible for literally a single thing you do with these files. have fun.
If you found this helpful or just enjoyable to read the thanks button is somewhere down to the right.. but whatever you do, don't hold down shift while you press it!
UPDATE: PDroid is not yet compatible with ICS/CM9 but the dev is actively working on supporting this, so sit tight and i will update the OP when he does so.
Since it works on Ba2tf, would it also work on weekly/nightly builds?
It is very rom specific, i wouldnt use my zip for Ba2tF with that rom.
Sent from my MB860
IUH1991 said:
Since it works on Ba2tf, would it also work on weekly/nightly builds?
Click to expand...
Click to collapse
It does work just fine on Neutrino ROM which is based on the weekly builds.
I have created patches for Dorians Redpill, Ba2tf, Neutrino GT/GT+ will also be creating one for EE shortly. I will post the patches for the API for PDroid shortly.
BTW this privacy app is awesome! You just need Linux to create a API patch for your phone.
EDIT: I had to create a new post to add the attachments..... kept failing every time I tried to add here. See post below.
Below are the API patches required to run PDroid for the specific ROMs. RESTORE patch included to remove the patch if it doesn't work. lol Don't hold me responsible if they don't work or if something funky happens..... but it worked for every ROM I have tested it on.
Keep in mind you don't need to be rooted to run the app, but you need to be rooted to run the patch.
EDIT: Also remember if your ROM ever gets updated odds are you will have to create a new patch for the newest version.
I got a PM from the dev today who had some good news.. Previously the patch maker was only available for Linux..
The good news is that you now can make a patch for your ROM yourself. Check out the PDroid patcher for Windows in the PDroid thread: http://forum.xda-developers.com/showthread.php?p=19570091. Or download it directly: http://goo.gl/oztqS.
Click to expand...
Click to collapse
Thanks for the info.
Setting up to try my hand at rom devel soon; once cm9 is a bit more stable ill build from git. Have compiled source for "true" linux but not android.
Since I'm making it security centric, this could be a nice addition. Will be researching further.
Sent from my MB860 using xda premium
I have been using LBE Privacy Guard, which revokes these permissions and more on an app-by-app basis. It's not ROM specific but a little time-consuming setting up rules for each app.
I don't have access to Linux unfortunately at the moment. Can someone make a patch for redpill-cm7?
Sent from my unlocked Motorola Atrix.
kshiuan said:
I don't have access to Linux unfortunately at the moment. Can someone make a patch for redpill-cm7?
Sent from my unlocked Motorola Atrix.
Click to expand...
Click to collapse
You don't need Linux. There's a link for the Windows version a few posts above mine.
Sent from my MB860 using xda premium
georgelopez said:
You don't need Linux. There's a link for the Windows version a few posts above mine.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
If you look on his original post (the developer's), you will see that there is a bug in the windows autopatcher. So yes...I do need Linux.
Oops...looks like I had someone on ignore who's done the work for me. Will send over a thanks anyways. Bygones.
schwann said:
If you look on his original post (the developer's), you will see that there is a bug in the windows autopatcher. So yes...I do need Linux.
Click to expand...
Click to collapse
You're absolutely right. Seems like the developer updated his OP right before I posted. Although, it does say to check back soon.
Sent from my MB860 using xda premium
ToALL
Can anybode made a patch for Neutrino ROM 1.4-S ?
What exactly does this do? If it's good, I might as well cook it in Neutrino
Notorious544d said:
What exactly does this do? If it's good, I might as well cook it in Neutrino
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1357056 read this.
Perfect patch for manual changing permissions of appz.
zhuchella said:
http://forum.xda-developers.com/showthread.php?t=1357056 read this.
Perfect patch for manual changing permissions of appz.
Click to expand...
Click to collapse
WOW, that's pretty sick!!
Notorious544d said:
WOW, that's pretty sick!!
Click to expand...
Click to collapse
it is! if you do bundle it make sure to also bundle the app or put a link to the market or something so users know!
schwann said:
I don't have access to Linux unfortunately at the moment. Can someone make a patch for redpill-cm7?
Sent from my unlocked Motorola Atrix.
Click to expand...
Click to collapse
Semi OT but...
If you have a cd drive, dvd drive, or usb drive you can run pretty much any nix distro in a "live cd" environment.
Sent from my MB860 using xda premium
n1ckr0th said:
it is! if you do bundle it make sure to also bundle the app or put a link to the market or something so users know!
Click to expand...
Click to collapse
My update will have the tweak and the app integrated
I can't thank you enough for the patch n1ckr0th. I've been using droidwall and an app called permissions to stop other apps from sending my data out. Now it's up to me who sees my real data. I understand that a lot of companies make their livings on advertisements and the like, but why do they have to know about and acquire my personal data for me to play a game or run a process that allows me to work more effectively. It's issues like this that make me want to learn how to code for android and write some great apps that won't steal everything on your device that it can see. Hmm, actually that's a good idea. Thanks again.
B.B.
So does anyone feel like being rebellious today? I decompiled a couple of the system apk's in the stock 4.1.1 ROM, including SysScope.apk, and found a few very interesting things.
All work so far was done with some basic tools like dex2jar and JavaDecompiler, perhaps if any Java-savvy people could join in we could take it even further.
To spark some attention, here's a spoiler:
Code:
arrayOfResultCode[0] = OK;
arrayOfResultCode[1] = ADB_RUNNING_AS_ROOT;
arrayOfResultCode[2] = PARTITION_TAMPERED;
arrayOfResultCode[3] = ROOT_PROCESS_FOUND;
arrayOfResultCode[4] = DANGEROUS_FILE_DETECTED;
arrayOfResultCode[5] = NOT_OFFICIAL_BINARY;
metalboy94 said:
So does anyone feel like being rebellious today? I decompiled a couple of the system apk's in the stock 4.1.1 ROM, including SysScope.apk, and found a few very interesting things.
All work so far was done with some basic tools like dex2jar and JavaDecompiler, perhaps if any Java-savvy people could join in we could take it even further.
To spark some attention, here's a spoiler:
Code:
arrayOfResultCode[0] = OK;
arrayOfResultCode[1] = ADB_RUNNING_AS_ROOT;
arrayOfResultCode[2] = PARTITION_TAMPERED;
arrayOfResultCode[3] = ROOT_PROCESS_FOUND;
arrayOfResultCode[4] = DANGEROUS_FILE_DETECTED;
arrayOfResultCode[5] = NOT_OFFICIAL_BINARY;
Click to expand...
Click to collapse
Hack what?
Triangle away just does that!
I do not respond to tech support via PM
But does TriangleAway force "Official" status in modified devices?
No it doesn't, and I'm trying to understand how Samsung's checks work so I can make them always return Official status.
metalboy94 said:
But does TriangleAway force "Official" status in modified devices?
No it doesn't, and I'm trying to understand how Samsung's checks work so I can make them always return Official status.
Click to expand...
Click to collapse
It tries to, but it's not bulletproof.
http://forum.xda-developers.com/showpost.php?p=36360447&postcount=2
tys0n said:
It tries to, but it's not bulletproof.
http://forum.xda-developers.com/showpost.php?p=36360447&postcount=2
Click to expand...
Click to collapse
I tried it myself but it didn't work for that particular purpose. So I am now taking the other way around For example, here's the root process whitelist on the Mini:
"debuggerd", "init", "installd", "servicemanager", "vold", "zygote", "netd", "ueventd", "dock_kbd_attach", "pppd", "pppd_runner", "mpdecision", "thermald", "hdmid", "sec_keyboard"
One of the checks SysScope makes is whether there are any root processes with a name other than the ones in the whitelist. (Also, as I found out in another section, it checks specifically for busybox).
Just flash a purely stock ROM if you want it back to official.
Sent from Spaceball One.
blackknightavalon said:
Just flash a purely stock ROM if you want it back to official.
Sent from Spaceball One.
Click to expand...
Click to collapse
So then, if you can't make any modifications after you root (because root does not really change the status), why are we rooting again?
XDA used to be a place of wild experiments... oh well. Some code in SecSettings.apk hints that SysScope.apk needs to have the same checksum/signature as SecSettings. It's an awkward way of checking if it is a legitimate binary, and also it's probably impossible to have a fake one without modifying SecSettings as well, but it's another find.
I like the idea. I have a update.zip. I don't know if it would be useful or not.
kingmt01 said:
I like the idea. I have a update.zip. I don't know if it would be useful or not.
Click to expand...
Click to collapse
You have my attention.
UnityROM-2 v.2.5.0
*****Discontinued.... No way to test actively till I have a functional build.*****
HTC One M7 Sprint Edition ( m7spr )
Development Section...
Want to contribute to the project or become team member?
Contact Me by PM here or leave a post detailing what you can and are willing to do for the projects' advancement.
My Github: https://github.com/LiquidSmokeX64
All current project sources can be found there .
ALSO MY FOOL-PROOF BUILD GUIDE & SCRIPTS ARE THERE FOR THOSE TOO IMPATIENT TO WAIT FOR MY NEXT RELEASE .
**Sources current as of version 2.5.0**
**10/06/2014**
Direct link to guide:
https://github.com/LiquidSmokeX64/Guides-Scripts
Note: Noob Friendly. If you're new to building ROMs or have never done it at all. I will help for as long as you maintain civility and focus on the project goals.
Installation errors out. Here is a pastebin of log saved after error
http://pastebin.com/fz15gwwn
Edit: I was able to install after removing that set perm line from updater. I will let ya know how it goes.
gruesomewolf said:
Installation errors out. Here is a pastebin of log saved after error
http://pastebin.com/fz15gwwn
Edit: I was able to install after removing that set perm line from updater. I will let ya know how it goes.
Click to expand...
Click to collapse
Ok. I just removed it too. My bad adaptation from Evo LTE. Nothing too bad luckily.
Reuploading the fixed version now.
LiquidSmokeX64 said:
Ok. I just removed it too. My bad adaptation from Evo LTE. Nothing too bad luckily.
Reuploading the fixed version now.
Click to expand...
Click to collapse
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
gruesomewolf said:
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
Click to expand...
Click to collapse
So. You're a kernel dev... Got a question for you. How do I add more CFLAGS to the makefile without it not booting or whatever? I've tried adding -O3 to the 2 places I know to put CFLAGS. Same place I put the -w so it would work with GCC 4.8
gruesomewolf said:
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
Click to expand...
Click to collapse
Will you be releasing this kernel for the Evo 4G? [emoji14] Evo4gnoob here
LiquidSmokeX64 said:
So. You're a kernel dev... Got a question for you. How do I add more CFLAGS to the makefile without it not booting or whatever? I've tried adding -O3 to the 2 places I know to put CFLAGS. Same place I put the -w so it would work with GCC 4.8
Click to expand...
Click to collapse
I wouldn't say Im a kernel dev....more of a dabler...lol. I sent you a pm with my makefile so you can see adjustments I made for my kernels latest build (not yet publicly released)
Notorious said:
Will you be releasing this kernel for the Evo 4G? [emoji14] Evo4gnoob here
Click to expand...
Click to collapse
Umm....no I dont have any plans for that ATM
gruesomewolf said:
I wouldn't say Im a kernel dev....more of a dabler...lol. I sent you a pm with my makefile so you can see adjustments I made for my kernels latest build (not yet publicly released)
Umm....no I dont have any plans for that ATM
Click to expand...
Click to collapse
Was joking lol
Notorious said:
Was joking lol
Click to expand...
Click to collapse
So you're allowing the integration of it? Just to be clear.
So I'm not sure why but the kernel borked again. Maybe I need to go through one flag at a time? Or maybe forgot something....?
gruesomewolf said:
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
Click to expand...
Click to collapse
Hey. Im having nothing but issues building it in the ROM so I was curious if you could tell me what I need to do after copying the msm8960 folder to a new place and adding in the makefile changes? Ive never built a kernel independently before but would like it to be a boot.img like normal so I can just replace the one in the ROM zip with the new one. Im sure it's pretty easy, just figured I'd ask you rather than comb through 80 guides saying different stuff lol.
LiquidSmokeX64 said:
Hey. Im having nothing but issues building it in the ROM so I was curious if you could tell me what I need to do after copying the msm8960 folder to a new place and adding in the makefile changes? Ive never built a kernel independently before but would like it to be a boot.img like normal so I can just replace the one in the ROM zip with the new one. Im sure it's pretty easy, just figured I'd ask you rather than comb through 80 guides saying different stuff lol.
Click to expand...
Click to collapse
Could you pm me with more info. Exact process of building, errors during build, any changes made to source, etc.
I'm gonna download your source later, together we should be able to figure this out.
gruesomewolf said:
Could you pm me with more info. Exact process of building, errors during build, any changes made to source, etc.
I'm gonna download your source later, together we should be able to figure this out.
Click to expand...
Click to collapse
I'm not seeing errors. Hell I removed everything but the -O3 spots and it still refused to boot. I dont know what the deal is....
Anytim I do ANYTHING to the kernel its dead, no matter how stupid it is.
gruesomewolf said:
Could you pm me with more info. Exact process of building, errors during build, any changes made to source, etc.
I'm gonna download your source later, together we should be able to figure this out.
Click to expand...
Click to collapse
BTW. The makefile is borked. And was curious if you knew how to build AOSP for this device? CM was pretty easy, I'd figure AOSP isn't too different. Then I can try to get Android L running once I have a working Android K to cross-reference to and make the version specific changes in device, kernel, vendor, qcom-common, and s4-common
LiquidSmokeX64 said:
So. You're a kernel dev... Got a question for you. How do I add more CFLAGS to the makefile without it not booting or whatever? I've tried adding -O3 to the 2 places I know to put CFLAGS. Same place I put the -w so it would work with GCC 4.8
Click to expand...
Click to collapse
When certain flags or 03 is added it creates a larger zImage. In order to compensate the boot.img needs needs modified, either by kernel installer or if baked in the rom hex edited. To change the ramdiskaddr.
Sent from my HTCONE using Tapatalk
thicklizard said:
When certain flags or 03 is added it creates a larger zImage. In order to compensate the boot.img needs needs modified, either by kernel installer or if baked in the rom hex edited. To change the ramdiskaddr.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Absolutely correct. And to elaborate on this just a bit more. Since your source building here, you can actually adjust the ramdiskadd with the scripts, considering it uses mkbootimg commands to build the boot.img.
An additional line in your devices board config, to give it a new ramdiskaddr size. Then an additional line in the build folder factory_ramdisk.mk , to handle the command for a new ramdiskaddr size should do the trick.
As for your other question about building aosp. I'm afraid that would be beyond my area of expertise. You would have significantly modify aosp code to allow for caf. It would be much harder then building cm, cause cm already has all the adjustments needed for caf devices
thicklizard said:
When certain flags or 03 is added it creates a larger zImage. In order to compensate the boot.img needs needs modified, either by kernel installer or if baked in the rom hex edited. To change the ramdiskaddr.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
gruesomewolf said:
Absolutely correct. And to elaborate on this just a bit more. Since your source building here, you can actually adjust the ramdiskadd with the scripts, considering it uses mkbootimg commands to build the boot.img.
An additional line in your devices board config, to give it a new ramdiskaddr size. Then an additional line in the build folder factory_ramdisk.mk , to handle the command for a new ramdiskaddr size should do the trick.
As for your other question about building aosp. I'm afraid that would be beyond my area of expertise. You would have significantly modify aosp code to allow for caf. It would be much harder then building cm, cause cm already has all the adjustments needed for caf devices
Click to expand...
Click to collapse
I read this and my eyes glaze over. But you are in good hands with these two helping you. :highfive:
Yeah I'm working on it guys. Read the integrated kernel building guide and trying that. But if I could just get it to build me the boot.IMG and get my ramdisk sizes and whatever I'm looking at where to edit it in the device/BoardConfig changed the defconfig to a custom one I made based off the original one from the working boot.IMG but changed the I/O scheduler & CPU governed defaults. Gave it a local name (UnityKernel-x.x.x) and am fighting its last issues. So if nothing else help building it independently might be the most useful now. So if nothing else I can push a new boot.img
My bad. It just says the boot partition size so I think I might be almost there
Hi! I'm currently making a somewhat desperate attempt at porting cm12 to the d950. I know some basic things, I once tried to make a custom kernel. I have the device and vendor trees set up, with the cm12 source and the files from the flex source, and I've been making some changes. Can anyone help point me in some direction from here?
dongdong6968 said:
Hi! I'm currently making a somewhat desperate attempt at porting cm12 to the d950. I know some basic things, I once tried to make a custom kernel. I have the device and vendor trees set up, with the cm12 source and the files from the flex source, and I've been making some changes. Can anyone help point me in some direction from here?
Click to expand...
Click to collapse
Okay, so now I need to run extract-files.sh, only problem is it doesn't exist. and from my understanding, I have to already be running cm12 to do this, which obviously is not possible. Can anyone help me get the proprietary blobs?
You're better off looking at the g2 proprietary blobs as when I was trying I had the most success with them on CM11, its a good starting point
So should I take those, then make changes to suit the flex?
Yeah, its a good place to start, but it won't suddenly make it compile, it helped sort a couple of issues once we'd got it compiling in the first place....
Try msg playfulgod and see if he will point you in the right direction
Alright, I've got something that looks pretty good going, but I can't do anything without a working kernel. And as I don't know much about kernels, could Someone possibly try to make one for cm12? Also, I have the blobs from my boyfriend's g2, and I've made a lot of changes, but I might need a little more guidance. Any help is appreciated.
Do you have coding experience though thats the question.
Either Build a dummy kernel or modify the original kernel from cm11 roms that your device has and built it alongside the system images.
CyanogenMod doesnt allow Building of only the system.
Youll need to modify the following:
Kernel Source
Device Trees
Vendor Files
A good way to look at what is required for a cm12 bringup is to check other similar devices with the same architecture and compare the changes and the sources you have on your pc.
Regards
Sent from my Xperia SP using xda Forum
I took programming classes, and there were a few units on android.
So I just forked the blobs from playfulgods repo, and I've made a lot of changes to tbe devices folder, as well as 'POSSIBLY' do something good as for a kernel, but I doubt that will work. How does one build the kernel to test it? Using linux btw. I have all of the dependencies and everything, could someone explain breakfast/brunch/lunch?
HEY SO I THIN K I HAVE SOMETHING THAT MIGHT WORK AFTER HAVING SOME REALLY SMART PEOPLE HELP sorry for caps, but now I have something in the out folder for zee, what do i do with this, and how do i make it flashable? could someone do it for me? and also, kernels?
dongdong6968 said:
HEY SO I THIN K I HAVE SOMETHING THAT MIGHT WORK AFTER HAVING SOME REALLY SMART PEOPLE HELP sorry for caps, but now I have something in the out folder for zee, what do i do with this, and how do i make it flashable? could someone do it for me? and also, kernels?
Click to expand...
Click to collapse
I can write and add the meta-inf folders to make it flashable. But I don't do kernels
mattwheat said:
I can write and add the meta-inf folders to make it flashable. But I don't do kernels
Click to expand...
Click to collapse
I would really appreciate that! What means should I take of sending you the output?
dongdong6968 said:
I would really appreciate that! What means should I take of sending you the output?
Click to expand...
Click to collapse
I see 2 things with the Out Folder having problems.
1) What has the Build System Generate in the out folder?
2) CM12 will generate a pre configured Zip File if it doesn't, the build failed
Sent from my Huashan Device utilizing RR Milestone 1
Furrydaus said:
I see 2 things with the Out Folder having problems.
1) What has the Build System Generate in the out folder?
2) CM12 will generate a pre configured Zip File if it doesn't, the build failed
Sent from my Huashan Device utilizing RR Milestone 1
Click to expand...
Click to collapse
If anyone wants to take a look I zipped the out folder.
So you're going to tell us you zipped the folder but you're not going to tell us where it is? Lol
Sent from my Huashan Device utilizing RR Milestone 1
dongdong6968 said:
So I just forked the blobs from playfulgods repo, and I've made a lot of changes to tbe devices folder, as well as 'POSSIBLY' do something good as for a kernel, but I doubt that will work. How does one build the kernel to test it? Using linux btw. I have all of the dependencies and everything, could someone explain breakfast/brunch/lunch?
Click to expand...
Click to collapse
The device tree repos found in lg-devs github are the correct ones just change kernel source to our stock kernel and edit z.mk and verndor files can be extracted with the ./extract-fikes.sh script . But our kernel needs to be updated a little which i am working on mostly caf header need to be added to include/Linux for media and display. I trued using msm8974 kernel but our kernel has specific blobs we use which is easier to use stock kernel.
---------- Post added at 06:26 PM ---------- Previous post was at 06:16 PM ----------
dongdong6968 said:
HEY SO I THIN K I HAVE SOMETHING THAT MIGHT WORK AFTER HAVING SOME REALLY SMART PEOPLE HELP sorry for caps, but now I have something in the out folder for zee, what do i do with this, and how do i make it flashable? could someone do it for me? and also, kernels?
Click to expand...
Click to collapse
What you mean you got something lol. We just need to update our stock kernel which you can have a better understanding. Of what i mean visit lg-devs for z repos . we should stick to stock kernel doe.
dongdong6968 said:
I would really appreciate that! What means should I take of sending you the output?
Click to expand...
Click to collapse
Upload it to drive then message me with a link
mattwheat said:
Upload it to drive then message me with a link
Click to expand...
Click to collapse
https://www.dropbox.com/s/dx3sjp8bq720bkn/out.zip?dl=0
Furrydaus said:
So you're going to tell us you zipped the folder but you're not going to tell us where it is? Lol
Sent from my Huashan Device utilizing RR Milestone 1
Click to expand...
Click to collapse
Sorry, completely forgot. https://www.dropbox.com/s/dx3sjp8bq720bkn/out.zip?dl=0
Hi,
Could someone please explain the difference between stock, Xposed, GB, CM, or other? I've built pc's and servers but this would be the first time I attempt to fool around with an Android.
Thanks!
Dannym.asdf said:
Hi,
Could someone please explain the difference between stock, Xposed, GB, CM, or other? I've built pc's and servers but this would be the first time I attempt to fool around with an Android.
Thanks!
Click to expand...
Click to collapse
I'll try to keep it simple with this.
1) Stock :- The ROM and Kernel you get from the factory along with your phone.
2) Xposed :- Refers to a set of modules that can be added to the existing ROM to change appearance, add functionality and provide you with features that would otherwise not be available in your 'Stock' ROM option. - Xposed requires you to have root privileges on your phone (i.e super user or admin rights)
3) GB : Gingerbread ??
4) CM : Cyanogen Mod : Refers to the most wide spread ROMs available for android. It offers most features of Stock ROMs coupled with things like a theme engine, dedicated music controls etc.
Head over to the forum rules for a quick look and also see the WIki page for more info : http://forum.xda-developers.com/announcement.php?f=613 .
Have fun messing around :good:
GB
Thank you!
Gravity Box...?
Dannym.asdf said:
Thank you!
Gravity Box...?
Click to expand...
Click to collapse
Ah . That's an exposed module that incorporates several other Xposed modules in a single package