Originally Posted by fenixjn (Post 1815490)

The way I tested this is installing mobile defense as a system app.

Background:
Mobile defense is a program that allows you to locate your cellphone (coarse and GPS specific), start an audible alarm and lock it down if it lost.

Problem:
Although is nice MD has a fatal flaw: MD can be uninstalled and/or the GPS can be disabled making the application kinda useless.

Solution:
if MD is installed as a system app, it will turn on the GPS on its own and it cannot be uninstalled

By using the FULL root method, you can, in fact, transfer the MD apk to the system where the user cannot shut it down (at least not if he/she does not know about XDA/PPCG).

The instructions (using method 2) are here

Note that step 9:


would not work/spit an error about that location being out of memory if you were using the previous methos (Rooting step 1 only), now if you do this line again after performing step 2 of rooting the command will execute successfully confirming that the system partition can be written to now.

Originally Posted by fuzzy26 (Post 1815548)

Sorry guys, but when I run the recovery-windows file it just runs for about 5 sec and then disappears. I ran it as admin. Does it have anything to do with the type of EVO that I have? I am still rooted though. Just don't have the option to backup.. oh yeah, I am assuming I enter these lines separately. TIA
adb shell
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image recovery /sdcard/recovery.img
reboot recovery

Originally Posted by freeza (Post 1815596)

Too bad that removing /system/data apps won't give you any internal memory. Almost makes deleting the Sprint bloatware pointless. Unless we can somehow allocate that memory to internal.

Originally Posted by fenixjn (Post 1815553)

Do not run recovery-windows as admin, run it as a standard user AND make sure USB debugging is enabled on the EVO.

Yes, those lines run separately, replace adb with adb-windows (if you are typing the commands from the evo-recovery folder):