My Samsung Galaxy have been inject some virus in /system/app. Now I root my phone and run rm command by root user, but still can not remove the apk file. The system show:
rm failed for /system/app/providerdown.apk, Operation not permitted
I want to know why the root use don't have the permission to remove some file?
I post the cmd log of my operation:
[email protected]:/system/app # ll -la |grep providerdown.apk
-rwsr-sr-x root root 178557 2015-06-11 14:07 providerdown.apk
[email protected]:/system/app # mount -o remount,rw /system
[email protected]:/system/app # rm -rf /system/app/providerdown.apk
rm failed for /system/app/providerdown.apk, Operation not permitted
The system file system have already mounted, and I can touch a new file, and also can remove new file by rm command.
Can Selinux affect the root permission, or there have some other permission that upon root user?
Any one can help me and Thank you for your ANSWER!
Have you tried with an app with root permissions, like Root Explorer? Or Titanium Backup? Found something about it here http://stackoverflow.com/questions/30771742/aggressive-adware-irremovable-apk-on-android but not a complete solution. I suspect the best way, if all else fails, is to reinstall the stock OS. 1 of 2 possible ways... 1 via Odin. 2 via flashing a rom zip of the same build via custom recovery. If you are just stock rooted and are REALLY against resetting your phone, then flashing the rom via a recovery like TWRP while only wiping /system, /dalvik cache, and cache partitions should let you be in the clear and not lose any settings, though always recommend backing up any important info before trying such a thing. If you do not have a popular model, then the rom option might not work if there is nothing available for it. If that is the case, then reinstalling the OS via Odin is about the only way, but will wipe everything on the phone.
Thanks so much, I will try.
es0tericcha0s said:
Have you tried with an app with root permissions, like Root Explorer? Or Titanium Backup? Found something about it here but not a complete solution. I suspect the best way, if all else fails, is to reinstall the stock OS. 1 of 2 possible ways... 1 via Odin. 2 via flashing a rom zip of the same build via custom recovery. If you are just stock rooted and are REALLY against resetting your phone, then flashing the rom via a recovery like TWRP while only wiping /system, /dalvik cache, and cache partitions should let you be in the clear and not lose any settings, though always recommend backing up any important info before trying such a thing. If you do not have a popular model, then the rom option might not work if there is nothing available for it. If that is the case, then reinstalling the OS via Odin is about the only way, but will wipe everything on the phone.
Click to expand...
Click to collapse
Thanks so much, I will try.
Related
Hello,
I had [JVT]Galaxydroid 2.0 but decided to go back to stock JVT. Now I'm having all kinds of trouble with copying a file to /system/etc.
I flashed stock JVT over Galaxydroid and rooted with speedmod kernel. Wiped caches and wiped user data. Then I installed su+busybox with speedmod's recovery option.
Titanium Backup didn't want to recognize su and busybox but after few tries it worked. Then I tried to copy spn-conf.xml to /system/etc (mounted /system as writeable with ES Root Explorer) and it seems like it copies succesfully, but the filesize is 0 bytes and the file is empty.
Then I tried adb, but it can't mount and doesn't even recognize cp or other commands. Where did I fail and how to fix this?
Thanks in advance
i'm on clockworkmod 5.0.2.3, my device is galaxy tab 10.1 P7510. i backup it with Titanium Backup. i've done CWM backup, i do know the CWM's backup file is sdcard/clockworkmod, but i can't delete it, either on my tablet or computer!! i've tried ES file and RE, nothing changes,,,,and the CWM file is as large as 1G, but i can't see anything in it! is that a new function of 5.0.2.3, to hide and protect its file? i've format the whole SDcard on my computer, and everything's gone, BUT the CLOCKWORKMOD file!!!!!! i'm crazy!!!!!
wohenyingyu01 said:
i'm on clockworkmod 5.0.2.3, my device is galaxy tab 10.1 P7510. i backup it with Titanium Backup. i've done CWM backup, i do know the CWM's backup file is sdcard/clockworkmod, but i can't delete it, either on my tablet or computer!! i've tried ES file and RE, nothing changes,,,,and the CWM file is as large as 1G, but i can't see anything in it! is that a new function of 5.0.2.3, to hide and protect its file? i've format the whole SDcard on my computer, and everything's gone, BUT the CLOCKWORKMOD file!!!!!! i'm crazy!!!!!
Click to expand...
Click to collapse
try makeing a new backup file in recovery as this should overright the last one
the file is probably corrupt
or using root explorer find the file and check the that folder is R/W
i dnt know if you can doo this on the sd card
You should be able to delete any file on the "SD card". Personally, although I use titanium backup as a great tool, CWM's backup is so easy and reliable for me.
thank u but it doesn't work. new backup changes nothing but make it biger, it seems that i can delete it by RE, but if i refresh i appears again. is there any way to format?
BroBot175 said:
try makeing a new backup file in recovery as this should overright the last one
the file is probably corrupt
or using root explorer find the file and check the that folder is R/W
i dnt know if you can doo this on the sd card
Click to expand...
Click to collapse
Tubes6al4v said:
You should be able to delete any file on the "SD card". Personally, although I use titanium backup as a great tool, CWM's backup is so easy and reliable for me.
Click to expand...
Click to collapse
yep, but it confuses me if the backup exists forever.......
wohenyingyu01 said:
yep, but it confuses me if the backup exists forever.......
Click to expand...
Click to collapse
aha me to :L did you try the root explorer way?
BroBot175 said:
aha me to :L did you try the root explorer way?
Click to expand...
Click to collapse
yep, it doesn't work.....finally i flash the rom with formating scripts through odin, it seems xwkg4, and flash back. now everything's gone~
You can rename and delete backups with the rom manager app from the market.
http://market.android.com/details?id=com.koushikdutta.rommanager
while in recovery:
adb shell mount /data
adb shell rm -r /data/media/clockworkmod/backup/DATED_FOLDER
Are you talking about the nandroid backup? If so, open the CWM recovery and the option to delete backups is there...
Also, you do realize that the CWM backup is not the same thing as the titanium backup, right? CWM backup is the whole system; titanium is just apps and settings...
got the same problem and tried a lot
slack04 said:
Are you talking about the nandroid backup? If so, open the CWM recovery and the option to delete backups is there...
Also, you do realize that the CWM backup is not the same thing as the titanium backup, right? CWM backup is the whole system; titanium is just apps and settings...
Click to expand...
Click to collapse
hi, i got the same issue and have tried to figure it out for hours and turn to here for help finally. my clockworkmod recovery's version is 5.5.0.4, probably. and i flashed 5.8.3.1 minutes ago.
i've tried to delete the backups in rom manager, but still can't and was told error occured while deleting.
and i tried to remove them in adb shell, rm command, and it says permission denied.
Code:
[email protected]:/sdcard/clockworkmod/backup # rm -r 2005-06-01.07.50.08
rm -r 2005-06-01.07.50.08
rm failed for 2005-06-01.07.50.08, Permission denied
255|[email protected]:/sdcard/clockworkmod/backup #
really need reply if anyone else is confused with the same problem ...
chenxian352 said:
hi, i got the same issue and have tried to figure it out for hours and turn to here for help finally. my clockworkmod recovery's version is 5.5.0.4, probably. and i flashed 5.8.3.1 minutes ago.
Click to expand...
Click to collapse
Is 5.8.3.1 for this tablet? If not...
chenxian352 said:
and i tried to remove them in adb shell, rm command, and it says permission denied.
Code:
[email protected]:/sdcard/clockworkmod/backup # rm -r 2005-06-01.07.50.08
rm -r 2005-06-01.07.50.08
rm failed for 2005-06-01.07.50.08, Permission denied
255|[email protected]:/sdcard/clockworkmod/backup #
Click to expand...
Click to collapse
In recovery (CWM) or android? Try with the -f switch (rm -rf), and do it in recovery from your PC (don't forget to mount the partition).
BTW, I can delete cwm backups in android with Root Explorer without problem.
slack04 said:
Is 5.8.3.1 for this tablet? If not...
Click to expand...
Click to collapse
If his tablet is the GT-P7510 model, yes.
slack04 said:
Is 5.8.3.1 for this tablet? If not...
Click to expand...
Click to collapse
sure about that, i got the recovery from clockworkmod.com.
i formatted it in windows, and everything was deleted but the clockworkmod folder! ghostly exist
something i just thought.. i'm using windows 7, when the tablet connect to my laptop, windows recognize it as a portable device. it's special i guess. is there any way to let it be removable disk?
---------- Post added at 04:43 AM ---------- Previous post was at 04:17 AM ----------
MapleSyrup said:
In recovery (CWM) or android? Try with the -f switch (rm -rf), and do it in recovery from your PC (don't forget to mount the partition).
BTW, I can delete cwm backups in android with Root Explorer without problem.
If his tablet is the GT-P7510 model, yes.
Click to expand...
Click to collapse
thx for reply. yes my tablet is GT-P7510. i can't delete them in re explorer, delete failed.
could you please tell me how to mount the partition?
chenxian352 said:
could you please tell me how to mount the partition?
Click to expand...
Click to collapse
One way is, in cwm, select "mount and storage" > "mount /data"
The other way is with adb (you're going to use it any way)
Code:
adb root
Code:
adb shell
Code:
mount /dev/block/mmcblk0p8 /data
If you keep getting the same error, try deleting everything inside the backup directory, I mean the 2005-06-01.07.50.08 directory.
Code:
cd /sdcard/clockworkmod/backup/2005-06-01.07.50.08
Inside the directory (be 100% sure to be in 2005-06-01.07.50.08 or you're going to delete something important. Always be careful when using the rm -rf * command)
Code:
rm -rf *
Or in one line
Code:
rm -rf /sdcard/clockworkmod/backup/2005-06-01.07.50.08/*
Then, delete the directory:
Code:
rmdir /sdcard/clockworkmod/backup/2005-06-01.07.50.08/
problem solved! thanks MapleSyrup
really thanks MapleSyrup! i executed all commands after normally powerup.
i just did them in cmw mode, all worked!
when normally powerup, in adb shell, command line prompt start with
Code:
[email protected]:/ #
in cmw(recovery) mode, it changes to
Code:
~ #
and no 'Permission denied' anymore when execute rm
i'm not English actually, literal words may be incorrect, hope readers could get it.
thanks sincerely. i've spent almost half day on the issue, you cant imagine how happy i am now, ha
MapleSyrup said:
One way is, in cwm, select "mount and storage" > "mount /data"
The other way is with adb (you're going to use it any way)
Code:
adb root
Code:
adb shell
Code:
mount /dev/block/mmcblk0p8 /data
If you keep getting the same error, try deleting everything inside the backup directory, I mean the 2005-06-01.07.50.08 directory.
Code:
cd /sdcard/clockworkmod/backup/2005-06-01.07.50.08
Inside the directory (be 100% sure to be in 2005-06-01.07.50.08 or you're going to delete something important. Always be careful when using the rm -rf * command)
Code:
rm -rf *
Or in one line
Code:
rm -rf /sdcard/clockworkmod/backup/2005-06-01.07.50.08/*
Then, delete the directory:
Code:
rmdir /sdcard/clockworkmod/backup/2005-06-01.07.50.08/
Click to expand...
Click to collapse
I'm a little more of a newb here, and Don't understand the above stuff. I'm having the exact same issue.
ROM Manager basically just messed up my phone to the point that I can't delete backups in clockworkmod. Also the backups are showing 0 bytes in size even though they've taken up 3 gigs on my SDCard
I Got ROM manager to install the latest CWM, which is great. I Then was trying it out, and noticed you can do a backup right from it. It Loads CWM and performs a normal Nandroid backup.
Here is the issue, It shows that it has take up the space on my SDCard, but the folder contents are empty in clockworkmod/backups
Also, I can't delete them at all. I Tried ES Explorer and nothing worked. Said denied.
Hi everyone.
I apologize for my first post because it's not one helping, but one asking for help instead.
I have recently struggled with the problem of not being able to move apps to the SD card which you may already be aware of.
So I read somewhere about changing some things on /system/etc/permissions/platform.xml and I had the stupid idea to try to change it without really understanding it.
So I did some ****. Now I can't mount sd (internal or external) and I don't have permissions to restore platform.xml (I have a platform.xml.bak in the same directory which is identical to the original one).
So I was wondering if there could be any trick to restore it. Neither ES File Manager nor Terminal Emulator were capable of replacing the files or edit platform.xml's content (even with root access, su - with terminal emulator).
What could I do? I honestly don't think a factory reset would solve that.
My ROM is stock UBDLI2 (4.1.1) which I found kinda hard to find.
Since you haven't posted a log of your Android Terminal Emulator session, here's my guess at trying to resolve this:
Code:
su
mount -o remount,rw /system
mv /system/etc/permissions/platform.xml.bak /system/etc/permissions/platform.xml
If you need it, chown root.root platform.xml && chmod 644 platform.xml.
similar problem with platform.xml
qwerty12 said:
Since you haven't posted a log of your Android Terminal Emulator session, here's my guess at trying to resolve this:
Code:
su
mount -o remount,rw /system
mv /system/etc/permissions/platform.xml.bak /system/etc/permissions/platform.xml
If you need it, chown root.root platform.xml && chmod 644 platform.xml.
Click to expand...
Click to collapse
I was trying to replace my platform.xml file with a modified platform.xml file and in doing so I moved the 0riginal platform.xml file to another folder (just in case I needed the 0riginal again), I changed the permissions of the permissions folder and rebooted for them to take affect without having the platform.xml file in there and boom I'm in never-never-bootloop land. Can anyone help me or does this phone need to be used for skeet shooting? Thanks in advance!
Reflash the same rom, no wipe.
boomboomer said:
Reflash the same rom, no wipe.
Click to expand...
Click to collapse
Thanks for the reply. I was rooted but still on stock since I had yet to successfully get a custom recovery on my phone (apparently SGH-I337 on the BN1 baseband is tough to get a custom recovery on)...so I only have the stock recovery which really doesn't offer many options. And everytime I have tried to flash anything via the custom recovery it fails due to it not being signed (or at least I think that is what it says). I'm open to try anything if you got more ideas.
Odin
Odin
boomboomer said:
Odin
Click to expand...
Click to collapse
I don't want to be "that guy" as described in your signature...so I want to first say I have searched on this, but I have only found various sections on Odin instructions for various versions of Odin typically pertaining to one specific topic rather than an actual manual/guide for how to use Odin to reinstall a file that was idiodically removed (that'd be me....the idiotical remover of pertinent files). So I hate ask you for more help, but I only can't seem to get anything I try flashing with odin to work, I'm not sure if I'm putting things in the wrong slot (BOOTLOADER, PDA, PHONE, CSC) or what, but I really need some guidance.
Go read the sticky thread in general forum, how to flash with Odin, you can only flash the whole firmware not one file.
Hello,
I want to root my device with odin and chainfire. I know this basically leaves my recovery
untouched and modifies some system files so as to allow root apps to install themselves
in a way that they can run with root permssion.
1. I would like to know more about exactly what changes this kind of rooting does to the
device's file system.
2. I want to back up my ROM before this (not my data, just the program that factory
resets my device). That way, if I don't like something or something doesn't work I know
I can go back.
3. If once I root my device I install ClockworkMod as my recovery, does that mean my
old recovery is gone forever and I cannot get it back (not that I would probably need it
but just in case).
Can someone please help?
Thanks,
John Goche
johngoche99 said:
Hello,
I want to root my device with odin and chainfire. I know this basically leaves my recovery
untouched and modifies some system files so as to allow root apps to install themselves
in a way that they can run with root permssion.
1. I would like to know more about exactly what changes this kind of rooting does to the
device's file system.
2. I want to back up my ROM before this (not my data, just the program that factory
resets my device). That way, if I don't like something or something doesn't work I know
I can go back.
3. If once I root my device I install ClockworkMod as my recovery, does that mean my
old recovery is gone forever and I cannot get it back (not that I would probably need it
but just in case).
Can someone please help?
Thanks,
John Goche
Click to expand...
Click to collapse
1. It doesn't make any changes to the file system. Are you sure you're using the right term?
It tells you what it does here:
http://autoroot.chainfire.eu
2. You cannot back up your rom before rooting. You require a custom recovery to do this... unless the s3 toolbox does this??have a look. There is a nandroid over adb option
http://forum.xda-developers.com/showthread.php?t=1746680
Factory reset only manages /data I.e your stuff. It doesn't restore roms
3. The toolbox in 2. Can flash stock recovery
Sent from my GT-I9300 using Tapatalk 2
1. OK, so there's the ROM, and there's the filesystem. So it's not like in Unix where everything is a file.
I thought the ROM includes all the files which are part of the filesystem including /system/xbin and the
kernel. I thought the filesystem is part of the flashed ROM, not a separate thing.
2. I have adb installed. How do I do a nandroid over adb?
3. OK, so the default recovery just restores the /data partition.
johngoche99 said:
1. OK, so there's the ROM, and there's the filesystem. So it's not like in Unix where everything is a file.
I thought the ROM includes all the files which are part of the filesystem including /system/xbin and the
kernel. I thought the filesystem is part of the flashed ROM, not a separate thing.
2. I have adb installed. How do I do a nandroid over adb?
3. OK, so the default recovery just restores the /data partition.
Click to expand...
Click to collapse
1. File system = ext4, fat32, ntfs etc.
The ROM is a collection of files, within the /system partition and a kernel (boot.img). Of course there is a file system beneath this but its completely irrelevant to our discussions.
But cf auto root puts an app in /system/app and a binary in /system/bin. I suppose you're using "filesystem" in the way linux uses that to navigate to the /root of the OS.
2. Download the windows application I linked you to and follow the prompts to set up correctly. Then its a menu option
3. The stock recovery only WIPES the /data partition. It restores nothing
Sent from my GT-I9300 using Tapatalk 2
1. OK, the ROM is a collection of files. Now I'm in sync. So only two files are modified during the rooting process,
and app in /system/app (which does what?) and a binary in /system/bin (presumably a shell?).
2. Download the windows application I linked you to and follow the prompts to set up correctly. Then its a menu option
Where is the windows application you linked me. With all the clutter on the XDA pages I can hardly see it.
3. The stock recovery only WIPES the /data partition. It restores nothing
Thanks. Not sure why the data partition is not browsable with adb shell by default.
Thanks.
The su binary is the actual root. But you need a superuser app too. The app acts as a gatekeeper. When you run an app that requires root, superuser app opens and asks you if you want to allow or deny access to this app. Think of it as a level of protection
The link in my first post in my number 2. Answer is a specific thread for the windows application called unified toolbox. Just read all of post one. It tells you everything you need to know.
/data is protected because things that could otherwise be deleted can prevent android from booting up.
Not sure if you're familiar with Linux, but /data isn't quite the same as your home directory. That would be /sdcard. I suppose the Linux equivalent of /data would be /usr (although not really as despite their similarity, linux and android are not the same. Only really the kernel)
Sent from my GT-I9300 using Tapatalk 2
Hi,
what started as an Idea seems to be working now. For once i wanted a phone that has warranty for more than two weeks (or at least a chance for warranty).
DISCLAIMER:
Do all of this at your own risk. Even though we will not be flashing a custom recovery, technically the warranty is lost the moment you root your phone.
None of the Tools is actually written by me, i just tinkered a bit and came up with this tutorial.
1. You will need
- Galaxy A3 (mine was an A300FU but i guess every one that can be rooted without flashing should do) on Lollipop (5.0.2).
- Minimal ADB or some other software that brings debugging drivers and adb.
- KingRoot 4.60+
- SuperSu-ME (from play Store or an older version is also fine) or any other way to go from the Kinguser Root Management to SuperSU
- Deodexed apks matching you phone model
- Flashfire Beta
- Xposed Installer, I used 3.0alpha4
- Xposed bridge for Samsung lollipop I used xposed-v75-sdk21-arm-arter97-snapdragon_requestConcurrentGC
2. If something goes wrong:
- Odin and a stock LOLLIPOP ROM for your device!
This is Important: Since we dont have a custom recovery, whenever something goes wrong the only rescue is going back to a stock rom and thereby wiping. If everything works in the first go there will be no wipe.
3. Rooting
First we need to root. Thanks to KingRoot thats very easy and just a matter of waiting. Install KingRoot (has to be 4.60+ for Lollipop), Click try to Root, wait for it, done. Know we need to get rid of the KingRoot stuff again and install SuperSU (FlashFire does not support KingUser but SuperSU) thats what we need SuperSU-ME for. There Will be some Left overs since KingRoot converts itself to a system app, you can remove this with Titanium Backup or a ROM Toolbox of you choice.
4. Deodexing
Next step is gonna be Deodexing. This one is a little Tricky without a Custom Recovery. Flashing the Deodex using FlashFire will leave you stuck at the Boot Logo.
Unpack the Flashable Deodex zip. you#ll find a META-INF and a system folder. Copy the system folder (or rename it, doesnt matter) to your SDcard or the phone memory using USB. At this point you can also copy the two Xposed files (zip+apk). Next we need USB Debugging. Install the minimal ADB, browse to the install location and start "adb devices" once (this will start the daemon). Now take your phone, browse to settings / phone info and tap the build number like 10 times (this gives you developers options) now go to settings / developers options and enable USB debugging.
Connect you phone via USB. This hould bring up a dialog granting your PC permission to connect. Click Yes.
Connect to the phone and request root using
Code:
adb shell
su
Now turn on the phones screen there should be a root request, allow it.
Next is the following commands, assuming the location of the extracted system folder is /storage/extSdCard/deodex_system
Code:
mount -o rw,remount /system
rm -Rf /system/app
rm -Rf /system/priv-app
rm -Rf /system/framework
cp -R /storage/extSdCard/deodex_system/* /system
chown -R root:root /system/app
chown -R root:root /system/priv-app
chown -R root:root /system/framework
chmod -R 755 /system/app
chmod -R 755 /system/priv-app
chmod -R 755 /system/framework
rm -Rf /data/dalvik-cache/*
reboot
This will replace all system apks with the deodexed ones, sets the right owner and permissions, clears the dalvik cache and reboots. Booting is gonna take a while and then you're enjoying you're rooted, deodexed stock ROM without flashing anything so far. So now about installing Xposed.
Don't be to slow with thus step. Deleting the three folders will make the phone go crazy and at some point reboot, you should be done by then.
Edit: I did this on a second device now, for some reason the remount did not work. In this case try disabling SElinux (http://forum.xda-developers.com/devdb/project/dl/?id=12178) and then remount.
5. Xposed
Install the XposedInstaller apk file like any other app, no need to start it yet. Next install FlashFire and launch it (granting root access) now select the Option "OTA or ZIP" in Flashfire and select the flashable Xposed zip you downloaded earlier. No further settings needed just hit Flash! The next reboot is again gonna take a while, but after that you can launch the Xposed Installer and start Installing Modules. We're done.
Whenever you do a factory reset (from the recovery), You need to root again using Kingroot, replace it with SuperSU and install Xposed again.
Once more, I did not develop any of the tools mentioned, all credits to their respective authors.
Cheers,
prometh
Edit: I did not try too many modules yet but Wanam for lollipop works just fine and that useless S Whatever bar is a thing of the past
Hi.
I already have a rooted Galaxy A3 (A300FU) and I have TWRP as my recovery so my warranty is already gone and I'm not too worried about that. However I have had no success at trying to deodex my rom to be able to install xposed.
Would it be possible to just flash the deodexed and the xposed zip from TWRP? And with regards to the deodexed zip would it matter if I flash it over the top of my current rom when I'm using a carrier rom rather than the BTU unlocked rom?
Squall88uk said:
Hi.
I already have a rooted Galaxy A3 (A300FU) and I have TWRP as my recovery so my warranty is already gone and I'm not too worried about that. However I have had no success at trying to deodex my rom to be able to install xposed.
Would it be possible to just flash the deodexed and the xposed zip from TWRP? And with regards to the deodexed zip would it matter if I flash it over the top of my current rom when I'm using a carrier rom rather than the BTU unlocked rom?
Click to expand...
Click to collapse
I think this would be a question for the deodex thread I linked but heres my 5 cents: The procedure in your case should be Flashing Deodex (eventually also gapps_replacement from that thread if you get Google Apps FCs) flashing Xposed, booting, installing the xposed installer. The Deodexed zip is meant to be flashed on top of your system. What I described is basically doing manually what the deodex zip file would do (deleting copying...). Since you have twrp already, I guess a system backup wouldn't hurt.
Many thanks for the help. I'll make a nandroid backup of system first just in case and then give it a go.
Thanks again.
Impossible with my SG A3 A300FU
Hello, I already have the root and TWRP installed, but if I try to type the command line with ADB it doesn't work and if I flash the zip, it doesn't work too. Any Idee ? With the first or the second method boot loop with the samsung logo !!
darwin345 said:
Hello, I already have the root and TWRP installed, but if I try to type the command line with ADB it doesn't work and if I flash the zip, it doesn't work too. Any Idee ? With the first or the second method boot loop with the samsung logo !!
Click to expand...
Click to collapse
If you try the adb commands whats the exact error? Permission Problems? Anyway the Command line should do nothing else than flashing the zip file (I dont know what the zip file wipes after flashing but I assume its dalvik and cache).
Great work prometh696 !!! I managed to get xposed on my A5 with knox 0x0 !!!
Some other steps I followed to get it for my A500FU; first I extracted my own system folders system/app/, system/framework/ & system/priv-app/ with root explorer to my ext SD card and then copied it to my computer.
On the computer I batch deodexed those folders with joeldroid's batch deodexer:
http://forum.xda-developers.com/and.../script-app-joeldroid-lollipop-batch-t2980857
Had some issues there as not every Java version seems to deliver the deodexed folders without errors; more details in that topic.
Then I followed your adb commands and installed xposed, and as you said, knox didn't change and is still 0x0 !!!
Thanks again !!!
---------- Post added at 01:30 PM ---------- Previous post was at 01:06 PM ----------
prometh696 said:
If you try the adb commands whats the exact error? Permission Problems? Anyway the Command line should do nothing else than flashing the zip file (I dont know what the zip file wipes after flashing but I assume its dalvik and cache).
Click to expand...
Click to collapse
The command lines are for copying the deodexed apks (so not in a zip). The zip is for xposed and is flashed by flashfire.
But as he already got TWRP (and thus knox 0x1) I see no use for him to use your method anyway
prometh696 said:
If you try the adb commands whats the exact error? Permission Problems? Anyway the Command line should do nothing else than flashing the zip file (I dont know what the zip file wipes after flashing but I assume its dalvik and cache).
Click to expand...
Click to collapse
When I type the first command line after this one "rm -Rf /system/priv-app" or this one "rm -Rf /system/framework" I don't know when exactly my phone reboot and bootloop on samsung logo (dynamic one) ???
My mobile restart before end of commands line
Hi,
your solution seems really good but my mobile (A300FU) is retarting before I typed all commands line.
Do you know a solution ?
Maybe cause I've no ExtSDcard and use the internal card ?
Thank you for your help !!
Regards
Virtua
update : I tried with trwp and made the necessary but the mobile does not boot.
This phone is a mess
It's the first time I can't do what I want with a phone. All posts seems to be a hoax. ;( ;(
Whenever you do a factory reset (from the recovery), You need to root again using Kingroot, replace it with SuperSU and install Xposed again.
Click to expand...
Click to collapse
This is actually incorrect unless root is systemless.
Root remains in system, and so does xposed. A factory reset does not touch the system partition.
You lose root after a reset because you need to reinstall superuser. If you make it a system app you won't lose root even after a reset.
The same with xposed just reinstall the apk.