I have a rooted device, it is Lenovo tab3 710F, this device does not have a ROM custom build, I need to do some customization, and I am doing that manually by updating the device files, (i.e. boot logo, startup/shutdown animation, system apps, home launcher .. etc), then I read back the ROM, and flash it to other devices. It works.
Because I cannot install system application with INSTALL_PACKAGE permission (the device ROM is locked and I cannot sign the apk, nor I found it easy to re-sign the whole ROM), so I create an app, placed it under /system/app (so when device factory reset it won't be gone), and this app is used to install apps using su -c pm install <apk> command. The thing here is that when the app tries to get su access it show a popup to user asking for permission to grant it. and I want to remove this grant popup so app get it without any user prompt. Few things :
- No security concern here, I am Ok if the whole device is chmod 777 but I don't know how to do that!!
- I am wondering if I can update init.rc or any other boot script that will mount the /system as read-write-execution for other users, so that the app can install apks silently? also it can be helpful when user factory reset that we will still have the android device rooted with full permissions granted.
Anyone know how or what I need to edit, and what is the command I should use ? I have full control over the devices (ownership), and everytime I updated it I Readback ROM then flash it to other devices.
tasqat said:
I have a rooted device, it is Lenovo tab3 710F, this device does not have a ROM custom build, I need to do some customization, and I am doing that manually by updating the device files, (i.e. boot logo, startup/shutdown animation, system apps, home launcher .. etc), then I read back the ROM, and flash it to other devices. It works.
Because I cannot install system application with INSTALL_PACKAGE permission (the device ROM is locked and I cannot sign the apk, nor I found it easy to re-sign the whole ROM), so I create an app, placed it under /system/app (so when device factory reset it won't be gone), and this app is used to install apps using su -c pm install <apk> command. The thing here is that when the app tries to get su access it show a popup to user asking for permission to grant it. and I want to remove this grant popup so app get it without any user prompt. Few things :
- No security concern here, I am Ok if the whole device is chmod 777 but I don't know how to do that!!
- I am wondering if I can update init.rc or any other boot script that will mount the /system as read-write-execution for other users, so that the app can install apks silently? also it can be helpful when user factory reset that we will still have the android device rooted with full permissions granted.
Anyone know how or what I need to edit, and what is the command I should use ? I have full control over the devices (ownership), and everytime I updated it I Readback ROM then flash it to other devices.
Click to expand...
Click to collapse
You say it's rooted so can you tell me exactly how you did it and what rom firmware number update you run please
Related
This is not a question about how to root the Atrix. I've already done that.
My question is about what actually is changed in the phone by following the root procedure. (I searched the forum but didn't find elsewhere the answers I look for).
Why do I ask?
1) Because I'd like to have a better understanding of the android OS.
2) Because I'd like to understand and know what do I need to do in case I want to unroot and return to plain stock.
My case:
(I've just rooted my Atrix. I didn't unlock it)
I've followed the "manual" procedure proposed by BriefMobile.
I can essentially understand (more or less) the commands listed (mount, remount, cp, install, chmod 6755, flash...)
What I'd like to understand better is what changes does the command
Code:
fastboot flash preinstall root.img
Does it just copy new files? Or does it copy (and replace) files on the phone?
(In the second case I'm afraid I made a mistake in not backing them up before running that command...)
Thanks in advance for your help.
Putting it in Windows terms (because Android is Linux), root is like having administrator privileges on your computer. It allows you to modify any system files that would normally be kept locked down. It also allows you to run applications, such as SetCPU, which can directly control hardware (in this case CPU frequency/speed and voltage) and low-level system files. Root in Android is comprised of two main files: the "su" binary (which is the command that applications use to invoke a request to do something with root privileges) and the SuperUser.apk (SuperUser app that's in the app drawer). The SuperUser app exists to prompt you whenever an application asks for root permission. So if you go into the terminal and type a low-level command, you'll see something like, "You do not have permission to do this". But if you type "su" before the command, it will run if you hit "Allow" on the SuperUser request.
Get it?
Product F(RED) said:
....
Get it?
Click to expand...
Click to collapse
Thanks Product F(RED) .
Yes I got it.
I already knew what rooting means in general terms.
What I really asked (sorry if I wasn't clear enough) is what does the root "physically" change on the phone.
According to your answer I assume it just adds the "su" binary and the "SuperUser" app (apart from changing some permission on some system folders) and that it doesn't replace any "stock" system file.
I also assume that these new files are extracted from the "root.img" (or "preinstall.img") files flashed by the fastboot command.
Is it so?
I was a little confused because I saw in some other forum a reference to some "stock" files wiped out in the /preinstall/app/ folder by the root process, mining the reversibility of the procedure (in case of no previous full system backup).
sphere314 said:
Thanks Product F(RED) .
Yes I got it.
I already knew what rooting means in general terms.
What I really asked (sorry if I wasn't clear enough) is what does the root "physically" change on the phone.
According to your answer I assume it just adds the "su" binary and the "SuperUser" app (apart from changing some permission on some system folders) and that it doesn't replace any "stock" system file.
I also assume that these new files are extracted from the "root.img" (or "preinstall.img") files flashed by the fastboot command.
Is it so?
I was a little confused because I saw in some other forum a reference to some "stock" files wiped out in the /preinstall/app/ folder by the root process.
Click to expand...
Click to collapse
Pretty much, yes, you're adding those two files (as well as another called BusyBox that allows other files to run, but this you can install after you root). The scenario I'm describing is that you're on a stock ROM and you just rooted your phone for the first time.
Though fastboot is present on every phone, using it to flash those two files seems to be unique to your phone because rooting methods vary from phone to phone. But basically the two most common methods are:
1. You flash a custom recovery from your computer if your phone's bootloader is not locked, and then you can flash the root files (su/SuperUser.apk) to the ROM from there or just flash a custom ROM that includes them.
or
2. You use fastboot/adb/some third-party method to root the stock ROM on your phone from your computer, then you install a custom recovery, and then you can flash custom ROMs/kernels/etc.
That /preinstall/app folder seems to be unique to your phone, but if I had to guess, it has something to do with deleting preloaded bloatware that comes with the phone. Because out of the box you can't, but once you have root permissions, you can go to that folder with a file manager to delete the APKs or use something like Titanium Backup to do it.
Product F(RED) said:
Pretty much, yes, you're adding those two files (as well as another called BusyBox that allows other files to run, but this you can install after you root). The scenario I'm describing is that you're on a stock ROM and you just rooted your phone for the first time.
Though fastboot is present on every phone, using it to flash those two files seems to be unique to your phone because rooting methods vary from phone to phone. But basically the two most common methods are:
1. You flash a custom recovery from your computer if your phone's bootloader is not locked, and then you can flash the root files (su/SuperUser.apk) to the ROM from there or just flash a custom ROM that includes them.
or
2. You use fastboot/adb/some third-party method to root the stock ROM on your phone from your computer, then you install a custom recovery, and then you can flash custom ROMs/kernels/etc.
That /preinstall/app folder seems to be unique to your phone, but if I had to guess, it has something to do with deleting preloaded bloatware that comes with the phone. Because out of the box you can't, but once you have root permissions, you can go to that folder with a file manager to delete the APKs or use something like Titanium Backup to do it.
Click to expand...
Click to collapse
Thanks again Product F(RED).
Things are clearer now.
I wasn't aware of the installation of "BusyBox" (I found it in my phone in the folder /osh/bin/)
I think the root method I used (BriefMobile) is the type 2. I didn't install a custom recovery as I'm not interested yet in flashing custom ROMs/kernels/etc.
So, to summarize...
The basic root methods (no unlock) consists in
1) install the "su" binary
2) install the "busybox" binary
3) install the "superuser.apk" app
4) change some r-w permissions
In my case (probably) the root method also wiped out some preloaded bloatware file in the /preinstall/app folder but that's not essential (unless Moto makes a check for the presence of those files before an OTA update).
They usually do check (and will fail) because OTA's are like patches; not really replacements for the whole /system/ partition. Never take an OTA when you're rooted, especially because they can do things like update and lock your bootloader, among other things. It's safer to wait until rooted versions pop up in the development section for your phone.
After rooting my .28 TFP, I noticed that the directory (system/xbin) contains much less files than before (only 4 files.)
I'm having some problems with some root apps especially patching apps. Could this be the problem?
Can I copy binary files from my MB855 rooted Ginger Bread phone to the same directory?
there's a busybox app on the market, I think this has the programs you are missing. (or rather, it installs the latest versions for you). Try that first.
tshoulihane said:
there's a busybox app on the market, I think this has the programs you are missing. (or rather, it installs the latest versions for you). Try that first.
Click to expand...
Click to collapse
Thank you. It worked. Root apps that did not use to work before are now working.
A couple of bugs I have noticed after installing busybox, though.
-some root apps that used to work in the background now have to be started manually.
-Superuser app does not show the prompt message and gives root access to root apps without prompt.
-The system files were mounted as RW and not mounted back to RO. I was unable to do it myself :-(
Any advice?
Hmmm... Try re-installing the superuser apk (and let it update the su binary if it wants to).
For /system as RO - reboot. It may be that you are trying to re-mount it with the wrong options. If it comes up as RW after reboot, something odd is going on.
[Q] How to make system apk ("adb push xy.apk /system/app") persistent through reboot?
First regarding my environment: I have Cyanogenmod 10.1 (self-built) on my Samsung I9300 Int., but I assume the question applies to every android version (I'm new to android development and flashing custom firmwares to my phone, but I have thorough experience with other embedded devices and gnu/linux):
I'm currently modifying a system apk (specifically LockClock.apk), which comes with CM10.1. From time to time, I "adb push" a modified version of the apk to my /system/app. (When the app works), it works without problems until the phone is restartet. After the reboot, the application does no longer appear to be installed (though the modified apk is still present in /system/app). I have to "adb push" the apk again, to make it work again. Is there a way to make the app permanently installed after an "adb push"?
Thank you very much
Nico
AW: [Q] How to make system apk ("adb push xy.apk /system/app") persistent through reb
Meanwhile, I found part oft the solution myself: when manually removing the apk (adb shell rm /system/app/LockClock.apk) before pushing the new version, it will persist through a reboot.
Can someone explain this to me? And is there maybe another/better way of doing this?
Did u fixed permissions after pushing it to system/app folder?
set permissions to rw-r--r--
I succesfully updated my Samsung Galaxy S3 from Android 4.2.2. to 4.3 after rooting my Phone.
However, SuperSU doesn't work anymore, giving the message "If you upgraded to Android 4.3 you need to manually re-root".
I cannot find an answer in the forums here on XDA developmers.
Can anyone help me?
Thanks in advance,
Been answered loads of times known issue go to settings/Developer options/root access tick Apps and ADB reboot
tallman43 said:
Been answered loads of times known issue go to settings/Developer options/root access tick Apps and ADB reboot
Click to expand...
Click to collapse
I already tried that on my own. Didn't work. SU still tells me that I need to update the SU binary. Manual re root. And I AM rooted! I even wiped EVERYTHING and started over. no go. So, I'm guessing that I need to manual re root. I'll search for that binary where ever that is Oh, I went to the latest SlimBean build #2 for 4.3.1 after CM 10.1.3 and CM 10.2 refused to install on my d2usc. Now CM's Rom Manager won't work, SU doesn't work, anything that needs root access no work mahn! On the good side, everything else works fantastic, except PIE control. But I bet that has something to do with root access, so no great surprise there. I am enjoying every minute of these problems!
Rooted 4.3 and installed SuperSU
morwit99 said:
I already tried that on my own. Didn't work. SU still tells me that I need to update the SU binary. Manual re root. And I AM rooted! I even wiped EVERYTHING and started over. no go. So, I'm guessing that I need to manual re root. I'll search for that binary where ever that is Oh, I went to the latest SlimBean build #2 for 4.3.1 after CM 10.1.3 and CM 10.2 refused to install on my d2usc. Now CM's Rom Manager won't work, SU doesn't work, anything that needs root access no work mahn! On the good side, everything else works fantastic, except PIE control. But I bet that has something to do with root access, so no great surprise there. I am enjoying every minute of these problems!
Click to expand...
Click to collapse
I had similar problem. Here is what I did -
1. Download CF-Auto-Root-d2att-d2uc-samsungsghi747 from autoroot.chainfire.eu.
2. Unzip
3. Use ODIN in the package to root.
4. Install ROM Manager.
5. Install SuperSU(Chainfire) from Play Store.
6. Open SuperSU and update SU binary. I saw a message to disable KNOX. I did it:highfive:
7. Install CWM Touch.
Then I installed other apps that need SU - Triangle Away, Titanium Backup. These apps worked fine for me. I went ahead and froze bloatware.
** Credit goes to all those hardworking folks who stay ahead in the game **
Same problem here
After updating to 4.3 my SU does not work, I have tried all I have internatinal model if any info please post
otto68 said:
After updating to 4.3 my SU does not work, I have tried all I have internatinal model if any info please post
Click to expand...
Click to collapse
if you have supersu or super user already than just download update-supersu from http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip and flash it through the recovery mode( custom recovery preferred).
xprivacy / reboot to recovery
In my case I was getting false alerts as xprivacy has blocked system access. (eg was with AdAway) Cleared those apps in XPrivacy and all worked find then.
Also you can try to go into recovery and the try to reboot. You may get message to reinstate/fix SU.
cbmk said:
I had similar problem. Here is what I did -
1. Download CF-Auto-Root-d2att-d2uc-samsungsghi747 from autoroot.chainfire.eu.
2. Unzip
3. Use ODIN in the package to root.
4. Install ROM Manager.
5. Install SuperSU(Chainfire) from Play Store.
6. Open SuperSU and update SU binary. I saw a message to disable KNOX. I did it:highfive:
7. Install CWM Touch.
Then I installed other apps that need SU - Triangle Away, Titanium Backup. These apps worked fine for me. I went ahead and froze bloatware.
** Credit goes to all those hardworking folks who stay ahead in the game **
Click to expand...
Click to collapse
You rock, I had re-rooted my updated Android 4.3 but my SuperSU was not usable anymore. Redownloaded it, allowed it to update SU Binary, disabling Knox, and viola! Root galore
suyash1629 said:
if you have supersu or super user already than just download update-supersu from ...LINK REDACTED.. and flash it through the recovery mode( custom recovery preferred).
Click to expand...
Click to collapse
that fixed it for me..thanks :good:
Tried all these steps on the new 4.3 MK6 ROM. Does not work for me. I cant find the Root access option itself in developer options. I already tried flashing CF-Autoroot multiple times after factory reset, using odin. I CWM still says binaries outdated and SuperSU doesn't work work even after updating from play store. Later i tried flashing supersu via the recovery mode. Still no success. Any suggestions?
Edit:
Another factory reset and flash did it. I don't know how. But it is fixed now.
By following your step, my superuser icon is gone...
Stuck in ODIN
Everytime I try to root S3 LTE via ODIN with CF auto root, it gets stuck there, need some help please, have had to use kies's recovery tool 3 times today because of that
i dont have this function
tallman43 said:
Been answered loads of times known issue go to settings/Developer options/root access tick Apps and ADB reboot
Click to expand...
Click to collapse
Hi, I dont have this function in my phone, nowhere, please help me?
fragiepacino said:
Hi, I dont have this function in my phone, nowhere, please help me?
Click to expand...
Click to collapse
Tapping on Build number till it says Developer Options Activated/Enabled, press back and you will see Developer Options in the list.
no
tallman43 said:
Tapping on Build number till it says Developer Options Activated/Enabled, press back and you will see Developer Options in the list.
Click to expand...
Click to collapse
the root function in the developers section, nowhere i can tick it
fragiepacino said:
the root function in the developers section, nowhere i can tick it
Click to expand...
Click to collapse
Sorry I thought you wanted to know how to get into developer settings....This thread is from 2013 i don't have S3 anymore if your trying to get root to work just follow some of the other suggestions posted.:good:
fragiepacino said:
the root function in the developers section, nowhere i can tick it
Click to expand...
Click to collapse
Here you don't have the "root access" setting ?
Sent from my GT-I9300 using XDA Free mobile app
s3 i9305 supersu binary problem
cbmk said:
I had similar problem. Here is what I did -
1. Download CF-Auto-Root-d2att-d2uc-samsungsghi747 from autoroot.chainfire.eu.
2. Unzip
3. Use ODIN in the package to root.
4. Install ROM Manager.
5. Install SuperSU(Chainfire) from Play Store.
6. Open SuperSU and update SU binary. I saw a message to disable KNOX. I did it:highfive:
7. Install CWM Touch.
Then I installed other apps that need SU - Triangle Away, Titanium Backup. These apps worked fine for me. I went ahead and froze bloatware.
** Credit goes to all those hardworking folks who stay ahead in the game **
Click to expand...
Click to collapse
—------------------------------------------------------
I know this is an old problem and has been answered many times, i have read all thepossible ways to fix it and i have tried, over and over but I'm missing something.
Please help.
I rooted with Supersu, it worked for 2days then stopped. Now all the root apps can't work and i have tried everything to make it work, to no avail. Here is a copy of my Root hecker:
Root access not properly configured or granted.
Superuser Application Status
Installed: SuperSU by Chainfire - version 2.46
System Files Status
Standard Location
Command: ls -l /system/xbin/su:
Result: -rwxr-xr-x root root 66916 2015-04-17 00:03 su
Analysis: Root access IS correctly configured for this file! Executing this file can grant root access! Root user ownership is present and setuid attribute is not present.
Standard Location
Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Alternative Location
Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
User Account Status
Error: stderr: [-] connect ui: Timer expired, stdout: null, exit_value: 1
Optional: ADB Shell User Status
Non-Root Shell User
Setting stored in /default.prop and configured as: ro.secure=1
Additional: System Environment PATH Status
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
_----------------------
So my device is rooted, but i don't have permission. Tried to copy .su file from xbin to bin, not possible.
Uninstalled reinstalled, unrooted rerooted, reinstalled SuperSu from playstore.
Made sure no double superuser programs running.
Got rid of Knox.
Tried to custom install Supersu update, says invalid certificate.
I believe if i can copy the .su file in \xbin to \bin the permissions wil be there. Bought Rootbrowser but error when copying. Or give permission on file SetUID.
Can't run Bootbox cause didn't install before root stopped working. Also Titanium backup stopped working now.
Any ideas how to fix? Don't want to factory reset. Can't be to difficult to fix.
PS. If this post is i wrong place please advise where itshould be.
Thanks
S :good:
cbmk said:
I had similar problem. Here is what I did -
1. Download CF-Auto-Root-d2att-d2uc-samsungsghi747 from autoroot.chainfire.eu.
2. Unzip
3. Use ODIN in the package to root.
4. Install ROM Manager.
5. Install SuperSU(Chainfire) from Play Store.
6. Open SuperSU and update SU binary. I saw a message to disable KNOX. I did it:highfive:
7. Install CWM Touch.
Then I installed other apps that need SU - Triangle Away, Titanium Backup. These apps worked fine for me. I went ahead and froze bloatware.
** Credit goes to all those hardworking folks who stay ahead in the game **
Click to expand...
Click to collapse
I can't find my phone as one of the packages. I have an Alcatel phone.
root my mobile but didn't get access
rooted my phone micromax a116, all proccess done wel as shown in tutorials. But root checker says that "root access is not properly installed on this device". Please tell me what to do?
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.