I am trying to find a way to block permissions to certain apps after installation. I came across this app called PDroid but requires a patched ROM using a linux script. App can be found here http://forum.xda-developers.com/showthread.php?t=1357056.
Has anyone tried this app?
splttingatms said:
I am trying to find a way to block permissions to certain apps after installation. I came across this app called PDroid but requires a patched ROM using a linux script. App can be found here http://forum.xda-developers.com/showthread.php?t=1357056.
Has anyone tried this app?
Click to expand...
Click to collapse
I haven't. I use App Shield, and it works well
I forgot to mention there is also LBE privacy guard but I wanted to see all my options
You can try permissions denied.
Sent from my SAMSUNG-SGH-I777 using xda premium
If you have a ROM in mind, if be happy to compile for you. I've been using it on icscrewd personally the last few versions. It is a really easy install, just flash a zip in cwm and install pdroid from the market
Sent from my SGH-I777 using xda premium
avidmovies said:
If you have a ROM in mind, if be happy to compile for you. I've been using it on icscrewd personally the last few versions. It is a really easy install, just flash a zip in cwm and install pdroid from the market
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
I am currently using UnNamed v1.3.2 from this thread: http://forum.xda-developers.com/showthread.php?t=1299474 second post.
Do you mind making a flashable patch? Thanks!
Sure expect one and a revert zip tomorrow.
Sent from my SGH-I777 using xda premium
There's a windows version of the patcher now if you're feeling adventurous
Downloading the ROM to my Linux box right now, in any case.
Sent from my SGH-I777 using xda premium
Mount /system in CWM before flashing.
Clear cache and dalvik for good luck
Install PDroid app from market to access features.
avidmovies said:
Mount /system in CWM before flashing.
Clear cache and dalvik for good luck
Install PDroid app from market to access features.
Click to expand...
Click to collapse
Thanks I will try it out this week.
UPDATE: Bad news bears. I flashed the patch as described (mounted system, wiped cache) but the system went into a boot loop. The boot animation kept cycling over and over again.
Did the restore zip work at least? That's the first I've heard of a bout loop caused by it.
It only edits 3 files, none of which could possibly cause more than a boot loop in any case.
EDIT: May have been a corrupted download, I'll be sure to post MD5, hashes next time. Sorry about that!
Sent from my SGH-I777 using xda premium
avidmovies said:
Did the restore zip work at least? That's the first I've heard of a bout loop caused by it.
It only edits 3 files, none of which could possibly cause more than a boot loop in any case.
EDIT: May have been a corrupted download, I'll be sure to post MD5, hashes next time. Sorry about that!
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
I don't think it was a corrupt download. I just created a patch myself using the Windows program and it also produced a boot loop. I restored from a nandroid the first time, trying out the restore file right now.
Alright sounds good. That's still really is though, and I have no idea why it happens. Did you flash any addons on top of the stock ROM?
Sent from my SGH-I777 using xda premium
avidmovies said:
Alright sounds good. That's still really is though, and I have no idea why it happens. Did you flash any addons on top of the stock ROM?
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Nope. Just the patch. Although the second time I didn't mount the system. Is this a necessary step? I didn't see anything in the OP of the PDroid thread.
Possible reasons for failure:
* Corrupt download first time
* Second time, didn't mount system
What is this "If you "integrated sys Dalvik into ROM" with Titanium Backup, you will have to undo it"? I am using TB but I'm not sure if this applies to my situation.
I noticed the ROM must be deodexed and I didn't see any odex filetypes in the system/framework directory. That should be the only place they appear right?
On a better note, the restore file works =) Thanks for the help
Yes, you should mount /system in CWM, as I didn't manually edit the patch to add in auto-mounting.
I just tried on Unnamed 2.2.1 and experienced the boot loop as well (created the patch using the Windows patcher). Restore zip works fine, and tried with and without mounting /system in CWM. There apparently is something in Unnamed that the code doesn't like
Too bad, sounds like a good program (I also use LBE and wanted to use it along side).
pinoymutt said:
I just tried on Unnamed 2.2.1 and experienced the boot loop as well (created the patch using the Windows patcher). Restore zip works fine, and tried with and without mounting /system in CWM. There apparently is something in Unnamed that the code doesn't like
Too bad, sounds like a good program (I also use LBE and wanted to use it along side).
Click to expand...
Click to collapse
It's a great app. I am running it on a Hellraised ROM. None of the AT&T base ones work. I sent the dev an error log from UnNamed 1.3.1 and he knows what the problem is and will try to address it in a future patcher release. (http://forum.xda-developers.com/showpost.php?p=22111242&postcount=757)
Check back on that thread whenever he updates it. It's worth it!
Alright, I'm currently running it on the latest ICScrewD flawlessly
Sent from my SGH-I777 using xda premium
stone_ship said:
It's a great app. I am running it on a Hellraised ROM. None of the AT&T base ones work. I sent the dev an error log from UnNamed 1.3.1 and he knows what the problem is and will try to address it in a future patcher release. (http://forum.xda-developers.com/showpost.php?p=22111242&postcount=757)
Check back on that thread whenever he updates it. It's worth it!
Click to expand...
Click to collapse
Thanks! I guess I didn't go far enough back in the dev's thread (DUH!) so hopefully he's got the info he needs to fix it. I'd really like to try it sometime.
The developer of PDroid has released an update to his patcher that fixes the bootloop issue for AT&T roms. I just installed using UnNamed v1.32 and it works great.
Feels good to block all of those permissions.
Related
Original Thread:
http://forum.xda-developers.com/showthread.php?t=1197274
For people that wants their VVM back, here you go!
Not my work, just stumbled upon it and would like to
spread the good news.
Happy Rooting
I get an error flashing this. sideload/tmp/... error. CM7 VAlpha 3
Edit: Got it to work by unpacking the zip and using Root Explorer to put the file in /system/app and setting 777 permissions.
You get that when its a bad download. Also I've read it could be cause its from your phone browser or comp browser. Try out different options and report back
blackroseMD1 said:
I get an error flashing this. sideload/tmp/... error. CM7 VAlpha 3
Click to expand...
Click to collapse
Sent from my PG86100 using XDA App
If you backup the vvm from sense with tb then restore it while on aosp it'll work too.
Sent from my Premium XDA app
Hey there guys I came across this useful tool today when I was poking around the ARC section it lets you make a nandroid without having to boot into recovery. This isnt my work Im simply passing it on so I hope he doesnt care too much about me posting this here.
***ALL crdeit goes to ameer1234567890***
Nandroid backups are usually performed in recovery mode. This means you would have to turn off your phone and reboot in recovery mode, which wastes a whole lot of time rebooting and a lot more time offline. For me, this has been a killer as I do regular nandroid backups. Having to reboot in recovery and finding missed calls, sms from my wife and friends is totally not accepatable for me. So, I set to develop an online nandroid backup tool which can do nandroid backups without switching off my phone.
Today, I am releasing it to public, as it may serve good for some others too. This tool is specifically for Xperia phones, but should work with any model of android phones.
This tool backups /system , /data , /cache & .android_secure partiotions to /sdcard/clockworkmod/backup directory. The date format used for folder name is the same used by CWM itself and nandroid backups created with this tool can safely be restored using CWM. If you would want to have a custom name for backup folder, pass an argument with the name to the script and it will use the name.
Feedback (especially ideas to improve) are most welcome.
Requirements
1. Rooted android phone
2. A terminal emulator installed on phone
3. Busybox
4. A working CWM based recovery installed
5. Some patience
Installation
1. Download and copy zip file to SD card
2. Reboot into recovery
3. Choose install zip from SD card, select zip and flash .
4. Reboot!
Usage
1. Open terminal emulator
2. Type su to obtain root
3. Type onandroid
4. Wait and watch
Original thread: http://forum.xda-developers.com/showthread.php?t=1620255
As usual Im not responsible if your phone explodes, catches fire, etc, etc so please read everything and try not to post stupid questions like " does this really work?" cause it wont be answered. I wouldnt of bothered posting this here if it didnt work. Have fun guys!!
Well let me the 1st....does it work? :banghead:Sorry I'm just playing friend.lol. I'm going to try this right now.
Sent from my R800i using xda premium
thanks for this gonna try rite now!!! i myself do regular backups as well.
edit: working working as i type! this is sick
hey you should post a link to the dev`s original thread so we could thank him and if possible donate for this amazing work.
My backup completed in 4 min 43 sec. And it seems to have worked fine. Thanks.
Sent from my R800i using xda premium
cyrusalmighty said:
Well let me the 1st....does it work? :banghead:Sorry I'm just playing friend.lol. I'm going to try this right now.
Sent from my R800i using xda premium
Click to expand...
Click to collapse
Ha ha ha! I knew it was bound to happen. Its pretty straight forward and really low risk I doubt anything could be messed up even if you tried but yea have fun! Hopefully it is useful to some out there
Sent from my R800a using XDA App
solomon4400 said:
thanks for this gonna try rite now!!! i myself do regular backups as well.
edit: working working as i type! this is sick
hey you should post a link to the dev`s original thread so we could thank him and if possible donate for this amazing work.
Click to expand...
Click to collapse
Will do give me a few minutes..... link to original thread in OP throw some thanks his way when you get a chance.
Sent from my R800a using XDA App
Thanks for sharing!
When I tried to run this, it says "Checking for required tools" followed by "mkyaffs2image not found in path"
I tried uninstalling/reinstalling busybox and installing it to /system/bin and not xbin. This time it sort of ran but I got a bunch of errors and no backup.
Any suggestion on how to fix this?
Sent from my R800x using xda premium
Isn't this inherently flawed since files on the rom are still being used and written while the backup is taking place? Neat idea though, don't get me wrong
netizenmt said:
When I tried to run this, it says "Checking for required tools" followed by "mkyaffs2image not found in path"
I tried uninstalling/reinstalling busybox and installing it to /system/bin and not xbin. This time it sort of ran but I got a bunch of errors and no backup.
Any suggestion on how to fix this?
Sent from my R800x using xda premium
Click to expand...
Click to collapse
No idea never seen that error its been working perfectly on my other play and bro's arc, I'd check the original thread and see if anyone else has the same issue
Sent from my R800a using XDA App
thatsupnow said:
No idea never seen that error its been working perfectly on my other play and bro's arc, I'd check the original thread and see if anyone else has the same issue
Sent from my R800a using XDA App
Click to expand...
Click to collapse
Yeah, I thought of that right after I posted here. There are plenty of people posting the same error, so we'll see what happens.
Sent from my R800x using xda premium
jacklebott said:
Isn't this inherently flawed since files on the rom are still being used and written while the backup is taking place? Neat idea though, don't get me wrong
Click to expand...
Click to collapse
I have been asked the same question. Have a look at here for the answer.
ameer1234567890 said:
I have been asked the same question. Have a look at here for the answer.
Click to expand...
Click to collapse
Fair enough. Hopefully people follow the advice of not doing anything during the backup, so they aren't disappointed when the changes don't get backed up
Should be fine I've taken a call and sent a few text messages while backing up. No problems for me at all
Sent from my R800a using XDA App
I tried to do a restore from the online nandroid backup I made and even though it said "restore complete" my SD-ext(4) partition would not load its shortcuts and widgets. The funny part is link2sd didn't even detect any SD-ext as if it wasn't backed up. I thought it said that it backed up SD-ext during online backup, but not sure. I'm wondering if it might help to factory restore before restoring backup. I may try that to see and I'll report back if noone reports similar problem.
Edit**During backup I was not doing anything else with phone other then watching the amazing online backup screen. Also I tried to "re-create mount scripts" but never got option from link2sd even after reboot.
Sent from my R800i using xda premium
cyrusalmighty said:
I tried to do a restore from the online nandroid backup I made and even though it said "restore complete" my SD-ext(4) partition would not load its shortcuts and widgets. The funny part is link2sd didn't even detect any SD-ext as if it wasn't backed up. I thought it said that it backed up SD-ext during online backup, but not sure. I'm wondering if it might help to factory restore before restoring backup. I may try that to see and I'll report back if noone reports similar problem.
Edit**During backup I was not doing anything else with phone other then watching the amazing online backup screen. Also I tried to "re-create mount scripts" but never got option from link2sd even after reboot.
Sent from my R800i using xda premium
Click to expand...
Click to collapse
This tool (prior to v3) does not backup sd-ext partition. In the first post, you can see what the tool backups.
PS: If you can send me a previous backup of your sd-ext, I can work on adding sd-ext backup support to the script.
I still can't get this to work.
Sent from my R800x using xda premium
netizenmt said:
I still can't get this to work.
Click to expand...
Click to collapse
Can you post the error?
ameer1234567890 said:
Can you post the error?
Click to expand...
Click to collapse
Here it is, the same error as before. This is with the latest 2.0 version. I'm running stock 2.3.4 rooted. Busybox is1.94 full.
Sent from my R800x using xda premium
wow.. that would be great backing up online... i'm gonna try now..
I have a question about Moboot. How do you change the boot options? I had installed a version of AOKP and a version of CM on top of eachother (wiping and then installing) and the old ROM I was running is still there. Is there a way to delete some of the moboot options?
spencer88 said:
I have a question about Moboot. How do you change the boot options? I had installed a version of AOKP and a version of CM on top of eachother (wiping and then installing) and the old ROM I was running is still there. Is there a way to delete some of the moboot options?
Click to expand...
Click to collapse
A Google.search would get you a LONG way
Sent from my cm_tenderloin using Tapatalk 2
cdzo72 said:
A Google.search would get you a LONG way
Sent from my cm_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the awesome, helpful response.
I did do a couple of quick searches on XDA and through Google but couldn't find what I needed. I figured somebody here knew off the top of their head what to do.
If you have Root Explorer, or some other root-level explorer, load it up and browse to /boot. Mount it as read-write, and find the file uImage.<whatever you wanna delete> and delete it. Don't delete any other files. You wanna keep the following:
uImage.Clockworkmod (that's CWM / TWRM Recovery)
uImage.webOS
uImage.CyanogenMod (that's the CM install)
If you have any questions, feel free to drop me a PM. Unlike the useless known as cdzo up there, I actually do like to help people.
Classic nerd has a flashable zip called moboot cleaner here's a link: http://rootzwiki.com/topic/26003-cm9-to-classicnerd-discussion/
If there is a problem posting a link to another forum I will remove it. Also if you want to change the main OS at start up or increase time download cyboot on webOS.
Sent from my cm_tenderloin using XDA
spencer88 said:
Thanks for the awesome, helpful response.
I did do a couple of quick searches on XDA and through Google but couldn't find what I needed. I figured somebody here knew off the top of their head what to do.
Click to expand...
Click to collapse
i would actually agree with him just did a simple search and even got a youtube video as part of my serch results that does it step by step by reverendjkr
https://www.google.com/search?q=delete+moboot+entries&ie=utf-8&oe=utf-8.
specifically this one
http://www.youtube.com/watch?v=7iquJvUyOL4
spencer88 said:
I have a question about Moboot. How do you change the boot options? I had installed a version of AOKP and a version of CM on top of eachother (wiping and then installing) and the old ROM I was running is still there. Is there a way to delete some of the moboot options?
Click to expand...
Click to collapse
Run this from recovery: http://classictomatoe.net/classicnerd.net/Betas/update-remove-tga_uImages.zip
That's a script from classicnerd. After you run that, re flash the rom without wiping anything to get the correct entries back into moboot.
Sent from my DROIDX using Tapatalk 2
So I wanted to change my keyboard... In fact I *did* change my keyboard.
At first whenever I wanted to use the keyboard (for notepad for example) it would say something like "Unable to reach" but after a while the keyboard just started working.
Then I switched on wifi and everything started crashing with the usual "Unfortunately (insert every task) has stopped working".
I know I can probably solve this by doing a factory wipe... but I also know that there MUST be a better way to solve this problem.
I have adb installed. I have Siyah kernel.
I can access the whole damned phone from my laptop in or out of recovery mode. I just don't know where to look to fix the problem.
A possible clue:
I tried flashing Keyboard-Blau.zip when my keyboard wasn't working. But CWM aborted the flash with an unknown error.
This is very similar to what happened the last time I had this problem. The only thing in the zip anyway was AXT9IME.apk in the system/app folder.
Any ideas would be appreciated.
P.S. I have also wiped cache and davlak cache AND attempted to install a rom. All permissions in system/app seem fine.
Could it be that system is mounted as r/w somehow?
EDIT2: Just now when I tried to to wipe dalvik (sp) cache it said something about:
"Unknown volume for path sd-ext"
Just a note.
Also I have erased /system then installed the rom again and it's still acting up.
TeamRainless said:
So I wanted to change my keyboard... In fact I *did* change my keyboard.
At first whenever I wanted to use the keyboard (for notepad for example) it would say something like "Unable to reach" but after a while the keyboard just started working.
Then I switched on wifi and everything started crashing with the usual "Unfortunately (insert every task) has stopped working".
I know I can probably solve this by doing a factory wipe... but I also know that there MUST be a better way to solve this problem.
I have adb installed. I have Siyah kernel.
I can access the whole damned phone from my laptop in or out of recovery mode. I just don't know where to look to fix the problem.
A possible clue:
I tried flashing Keyboard-Blau.zip when my keyboard wasn't working. But CWM aborted the flash with an unknown error.
This is very similar to what happened the last time I had this problem. The only thing in the zip anyway was AXT9IME.apk in the system/app folder.
Any ideas would be appreciated.
P.S. I have also wiped cache and davlak cache AND attempted to install a rom. All permissions in system/app seem fine.
Could it be that system is mounted as r/w somehow?
EDIT2: Just now when I tried to to wipe dalvik (sp) cache it said something about:
"Unknown volume for path sd-ext"
Just a note.
Also I have erased /system then installed the rom again and it's still acting up.
Click to expand...
Click to collapse
What rom are you on? Did you do a full wipe when you flashed it?
Sent from my GT-P7510 using xda premium
kilometers4 said:
What rom are you on? Did you do a full wipe when you flashed it?
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
Wanamlite. Latest version. And I sure did...
TeamRainless said:
Wanamlite. Latest version. And I sure did...
Click to expand...
Click to collapse
What keyboard did you choose? One from the play store?
Edit : have you tried to flash the rom over what you have now, with no wipe?
Sent from my GT-P7510 using xda premium
kilometers4 said:
What keyboard did you choose? One from the play store?
Edit : have you tried to flash the rom over what you have now, with no wipe?
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
Yes I tried it.
And somebody had uploaded the stock, touchwiz keyboard. So I copyed it over and set the permissions correctly.
TeamRainless said:
Yes I tried it.
And somebody had uploaded the stock, touchwiz keyboard. So I copyed it over and set the permissions correctly.
Click to expand...
Click to collapse
Hmm.. The only thing I can think of is wiping cache, dalvik one more time EDIT: and try to fix permissions from cwmr. If that doesn't work I would make a nandroid backup and flash your rom with a full wipe again to see if that fixes it. At least you can restore the backup if it doesn't
Sent from my GT-P7510 using xda premium
kilometers4 said:
Hmm.. The only thing I can think of is wiping cache, dalvik one more time EDIT: and try to fix permissions from cwmr. If that doesn't work I would make a nandroid backup and flash your rom with a full wipe again to see if that fixes it. At least you can restore the backup if it doesn't
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
Yeah I know a full wipe will fix it. I've already done that and screwed it up again a few more times for testing purposes.
My point is that there SHOULD be a way to fix it without a full wipe.
I mean if you've got root access, CWM recovery, AND you can actually boot the phone and access adb at the home screen... Then it should be possible to fix the problem.
It's a shame android dosnt return an error telling you WHY something is crashing. Then it would be a cinch.
TeamRainless said:
Yeah I know a full wipe will fix it. I've already done that and screwed it up again a few more times for testing purposes.
My point is that there SHOULD be a way to fix it without a full wipe.
I mean if you've got root access, CWM recovery, AND you can actually boot the phone and access adb at the home screen... Then it should be possible to fix the problem.
It's a shame android dosnt return an error telling you WHY something is crashing. Then it would be a cinch.
Click to expand...
Click to collapse
What keyboard are you trying?
Sent from my GT-P7510 using xda premium
kilometers4 said:
What keyboard are you trying?
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
This one: http://forum.xda-developers.com/showthread.php?t=1483428
...from post #2. Then I tried the zip in post 3 and four. (If you'd like to replicate the error just backup your /data then you can do whatever the hell you want and just restore /data and you'll have everything.) Then I tried flashing the zip from post 3 or 4... which didn't work. Followed the directions for changing permissions on the keyboard.
I hadn't realized you could backup everything from CWM Recovery. And hadn't even considered that just restoring /data would work without screwing everything up again... but work it did! Wish I had realized that a couple of weeks ago... but I didn't really want that data anyway.
Basically I just want the touchwiz keyboard because the standard android one is too small for my hands.
But I can't quite figure out how changing two files... and even changing them back later... could crash the whole damned OS beyond repair.
TeamRainless said:
This one: http://forum.xda-developers.com/showthread.php?t=1483428
...from post #2. Then I tried the zip in post 3 and four. (If you'd like to replicate the error just backup your /data then you can do whatever the hell you want and just restore /data and you'll have everything.) Then I tried flashing the zip from post 3 or 4... which didn't work. Followed the directions for changing permissions on the keyboard.
I hadn't realized you could backup everything from CWM Recovery. And hadn't even considered that just restoring /data would work without screwing everything up again... but work it did! Wish I had realized that a couple of weeks ago... but I didn't really want that data anyway.
Basically I just want the touchwiz keyboard because the standard android one is too small for my hands.
But I can't quite figure out how changing two files... and even changing them back later... could crash the whole damned OS beyond repair.
Click to expand...
Click to collapse
It might be a bad zip/apk file
Sent from my GT-P7510 using xda premium
kilometers4 said:
It might be a bad zip/apk file
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
It absolutely was. But what did it do and how could I fix it?
So basically I can't install apk files on my phone. It's a recent issue since I switched over to the newest fj stock mod rom. I download an .apk, I put it on my phone but when I click on it to install it, the option to install it won't respond. I can click cancel. but I can't click install... I can't seem to figure out why it won't do it, and I'm sure it's something stupid that I'm not getting...
This exact thing happened to me.. The ONlY way to fix it is to flash new roms sorry
Sent from my SAMSUNG-SGH-I717 using xda premium
That is not the only way to fix it. You can put the apk in the data/app folder and reboot and it should install. You do have unknown sources checked right?
Sent from my SAMSUNG-SGH-I717 using xda premium
Yeah, I have that option checked. I'll try moving them there and see if that works.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Tried doing that and it didn't work... I guess you could try and see if you have any luck.
Sent from my SAMSUNG-SGH-I717 using xda premium
It didn't work when I put them in that folder and rebooted. What did work was turning off JuiceDefender and then trying to install them. Not sure why but turning it off made things install. Whatever... lol
Hello sorry to bring back old thread but what is juice defender... Problem has raised for me again.... :/
Sent from my SAMSUNG-SGH-I717 using xda premium
OPGT said:
Hello sorry to bring back old thread but what is juice defender... Problem has raised for me again.... :/
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
assuming you flash roms as a solution, would you have a few backups?
juice defender:
https://play.google.com/store/apps/details?id=com.latedroid.juicedefender&hl=en
As rquiett mentioned.....put the app into the data/app folder via any good root explorer app, then reboot.
The apk can also be placed into the system/app folder for the same outcome. the major difference here, is the device now sees the apk as a system app, and will not be removable via traditional methods like a user app. It would need removal by the root explorer app that placed it there.
Flashing "the same" build to get an app, is generally not needed, however, I have used this method many times over the years after I removed a system app I needed back.
You can simply flash the "same" rom over the top of the existing rom, and the pre-loaded rom apps are back.
Note: you must wipe the caches after using this method, or data corruption could occur. "cache and dalvik cache"
Long story short:
Root explorer app to place into data/app......or system/app
and if you are feeling adventurous....then flash the "same" base build over the top of your current build, then wipe caches and reboot.
Standard disclaimers apply....g