OK, so I have a rooted I9300 and for some reason for the last few weeks I cant update the subinary and titanium wont get root access.
I did many google searches, tried a few thing eg (http://forum.xda-developers.com/showthread.php?t=1900217) , tried rooting again (even though I know Im rooted but nothing works.
So the next thing I want to try is to unroot my phone and root again.
My question is, because I cant access titanium to back everything up,
is there a way to unroot WITHOUT losing all apps and data?
Thanks a lot in advance.
Make nandroid backup and restore apps using titanium when your phone are rooted again.
Use MybackupPro to backup messages/contacts/bookmark/system setting/bookmarks.
Sent from my GT-I9300 using xda app-developers app
Uninstall super su via Google Play and reinstall .
jje
Cant use nandroid. It needs busybox which requests root access.
JJEgan said:
Uninstall super su via Google Play and reinstall .
jje
Click to expand...
Click to collapse
Tried it- it wont uninstall but go back to an earlier version.
Reinstalled the latest version and Im getting the same message.
Root checker app says "This device does not have proper root access".
...just re-root it? Assuming you used CF-Root and will be flashing it again, when CWM runs again and installs the SuperSU ZIP, /system/xbin/su will get overwritten (and get set with the correct permissions).
Else, if whatever reason you don't want to do that, if you have CWM recovery installed, just mount /system, and using ADB delete /system/xbin/su, /system/app/Superuser.apk, /system/bin/.ext and install CWM-SuperSU-v0.96.zip again.
If you don't have CWM, you can use a kernel with an insecure adbd (Perseus kernel has this for Jellybean ROMs, and earlier Siyah and GalaxSih kernels have this for ICS) and delete /system/xbin/su and /system/app/Superuser.apk. You'll have to manually install SuperSU from the ZIP.
qwerty12 said:
...just re-root it? Assuming you used CF-Root and will be flashing it again, when CWM runs again and installs the SuperSU ZIP, /system/xbin/su will get overwritten (and get set with the correct permissions).
Else, if whatever reason you don't want to do that, if you have CWM recovery installed, just mount /system, and using ADB delete /system/xbin/su, /system/app/Superuser.apk, /system/bin/.ext and install CWM-SuperSU-v0.96.zip again.
If you don't have CWM, you can use a kernel with an insecure adbd (Perseus kernel has this for Jellybean ROMs, and earlier Siyah and GalaxSih kernels have this for ICS) and delete /system/xbin/su and /system/app/Superuser.apk. You'll have to manually install SuperSU from the ZIP.
Click to expand...
Click to collapse
I tried rooting again- didn't change anything.
I do have CWM.
Tried using ADB, but it requests root access and fails to get it...
tomerstern said:
I do have CWM.
Click to expand...
Click to collapse
Good, ADB will be running as root in CWM by default. Boot into recovery mode, go to mounts and storage, and select Mount /system.
If you don't already have ADB setup and the correct drivers installed (if you already have Kies installed then you have the drivers installed). do the following. You can check, if you wish, by seeing when you connect your phone in recovery - you should have a SAMSUNG Android ADB Device under SAMSUNG Android Phone or an Android Debugger Bridge device in Device Manager. If not:
Download http://dl.google.com/android/repository/platform-tools_r14-windows.zip and extract the three files adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll to a place of your choosing
install the drivers: http://www.mediafire.com/?2243ouw1701zp8l (Extracted from Kies_2.5.0.12094_27_11.exe)
disconnect and reconnect your phone
Go to the folder where you have adb installed in the Command Prompt, and run "adb shell". Run the following commands:
Code:
rm /system/app/Superuser.apk
chattr -i /system/xbin/su [in case Survival Mode is turned on in SuperSU]
rm /system/xbin/su
rm /system/bin/su [ignore this one if it throws an error]
rm -r /system/bin/.ext
That should unroot your phone.
Go to "Install ZIP from sdcard" and choose to install a zip from the internal sdcard.
Exit out of the root shell (Ctrl+C or, alternatively, "exit" and you'll be sent back to the command prompt) on your computer and download the SuperSU ZIP.
Go back to the command prompt and type this "adb push " (including the space) and drag the CWM-SuperSU-v0.96.zip onto the command prompt window, add a space and type "/data/media". You should have something like "adb push <path to CWM-SuperSU-v0.96.zip> /data/media"
This should put the SuperSU ZIP onto the root of your internal memory card. Choose go back on your phone and select to install a ZIP from the internal memory card again. You should see CWM-SuperSU-v0.96.zip. Install it, reboot, update SuperSU from the Play Store and run SuperSU from the app drawer. You should get a prompt asking you to update the su binary. Do so.
Grab Android Terminal Emulator on the Market, and run "su". If all went well, SuperSU should ask you for permission. Grant it and if the $ turned into a # and the command "id" says uid=0 (root) then you're rooted!
OK, Im really sorry and embarrassed to say that I got confused with my tab 10.1.
I Do not have CWM installed.
Tried installing it now and could not. I stay on odin mode and I dont get the CWM menu...
I guess at this stage when my root is screwed I cant install CWM anymore.
What can I do now?
Thanks again and sorry for the confusion..
tomerstern said:
Tried installing it now and could not. I stay on odin mode and I dont get the CWM menu...
I guess at this stage when my root is screwed I cant install CWM anymore.
Click to expand...
Click to collapse
Flashing CF-Root should always get you CWM as it's done through ODIN, which does not care if your phone is rooted or not. When you're flashing CF-Root, make sure the auto reboot option remains ticked. If your phone doesn't boot into CWM after ODIN reboots it, then take note of the following:
Chainfire said:
- NOTE: Sometimes the device does *not* boot into recovery mode and root your device. Just do the entire procedure again if this happens. If it still will not install root and such, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, pull the battery, and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
Click to expand...
Click to collapse
qwerty12 said:
Go to the folder where you have adb installed in the Command Prompt, and run "adb shell". Run the following commands:
Code:
rm /system/app/Superuser.apk
chattr -i /system/xbin/su [in case Survival Mode is turned on in SuperSU]
rm /system/xbin/su
rm /system/bin/su [ignore this one if it throws an error]
rm -r /system/bin/.ext
Click to expand...
Click to collapse
OK, Im now in the mounts and storage folder insider CWM.
ADB interface is installed on device manager.
II dont understand what to press and where to run these commands.
tomerstern said:
OK, Im now in the mounts and storage folder insider CWM.
ADB interface is installed on device manager.
II dont understand what to press and where to run these commands.
Click to expand...
Click to collapse
Under the mounts and storage option, select mount /system. It will change to "unmount /system" if selected correctly.
The commands are run from an "adb shell" session, which you can get to by doing this:
Extract those three ADB files from that platform-tools ZIP to a folder somewhere (I chose C:\adb out of randomness). Open that folder and while holding down the shift key, right-click a blank, white area in the folder and select "Open command window here". You can then type "adb shell", which will allow you to run those commands.
qwerty12 said:
Good, ADB will be running as root in CWM by default. Boot into recovery mode, go to mounts and storage, and select Mount /system.
Click to expand...
Click to collapse
There isnt mount system there. I see unmount system.
I see mount data, preload etc.
OK, that's fine, you may move on to running those commands.
Two problems:
1. running "chattr -i /system/xbin/su"
resulted in a "chatter not found" message.
2. Trying to push the su zip resulted in this message: "error: device not found".
tomerstern said:
"chattr -i /system/xbin/su"
Click to expand...
Click to collapse
If rm worked on /system/xbin/su, then ignore it as you don't need it anyway.
2. Trying to push the su zip resulted in this message: "error: device not found".
Click to expand...
Click to collapse
Reconnect the phone and try again?
not working after numerous attempts.
Can I Start the phone and move the zip file manually with a micro sd cable? If not, what else?
tomerstern said:
Can I Start the phone and move the zip file manually with a micro sd cable? If not, what else?
Click to expand...
Click to collapse
That should be fine
moved it to internal memory and after shutdown, power+home+volume up wont take me to cwm anymore but to android system recovery.
Why? How do I get back to cwm? Install it again with Odin?
BY THE WAY, I can still see supersu is installed on my device. Does it mean what we did did not work?
OK, I can confirm this method works
I just installed the zip of the supersu and now Ive got full root privileges.
The reason I couldnt get into cwm was that for some reason I get a short android upgrade each time I boot up. This upgrade deletes cwm. Thats why I found out that I need to install CWM and then immidiately press power-volume up-home, before i let the device power up.
I want to give a big thanks to qwerty12 for the help and much needed patience.
Related
I have a moto droid, rooted mine the normal way with update.zip and adb but my mom has a eris and wants wifi tether and a faster rom with working youtube app
Can i just download the rooting file update her phone then download rom manager to install recovery image? i dont feel like setting up adb on her computer. i want to flash it to the newest ota rooted rom that is on this site.
bL33d said:
I have a moto droid, rooted mine the normal way with update.zip and adb but my mom has a eris and wants wifi tether and a faster rom with working youtube app
Can i just download the rooting file update her phone then download rom manager to install recovery image? i dont feel like setting up adb on her computer. i want to flash it to the newest ota rooted rom that is on this site.
Click to expand...
Click to collapse
Sure, put your sdcard in your computer, or connect it to your computer with the USB cable and mount the sdcard. Download the PB00IMG.zip with root, flash_image, and recovery.img. Shut the phone down, and then do the VOL DOWN+Power ON to flash PB00IMG to the phone. Once done flashing, go in to the android market and download a terminal emulator. Type these commands:
su
after su, phone should change from sh-3.2$ to sh 3.2#
mount -o rw,remount /dev/block/mtdblock3 /system
cp /sdcard/flash_image /system/bin
chmod 755 /system/bin/flash_image
flash_image recovery /sdcard/recovery.img
If you do that, it should allow you to do it without adb on the computer. Just remember to type the 5 commands in the terminal emulator.
I just talked to devs and they told me that It can be done, Just download the rom Manager and install the recovery from there without using adb at all.
You just have to install the root rom first, then you should be able to use the rom manager to install the recovery img, which in my opinion the clockworkmod recovery is a lot better than the RA recovery which is listed in the rom.
thanks guys seemed like it was doable but wanted to double check here first.
Evening Folks,
Hoping someone can help. I've been trying to install a custom rom onto my mini pro (Any custom rom!). Done a lot of reading and have managed to root my phone but am now stuck when trying to install xrecovery and CWM.
I've put xrecovery, busybox, chargemon and the cwm zip file onto my sdcard. I've been trying to move busybox, chargemon and xrecovery to the /system/bin directory using Super Manager. But it keeps telling me I do not have enough space, even tho I have 150mb internal space free on the phone. As far as I can tell the three files I need to move are less than 1mb and I've deleted just about everything I trust myself to delete.
ALong the way I managed to muck up the google acount password and ended up resetting the phone to the factory defaults, so there is nothing on it. Currently the only downloaded apps are Root Checker, Super Manager and SuperUser.
So I'm hoping one of you fine chaps, and chapetts, is going to be able to point out the stupid mistake I'm making.
I have to escape sooon, so will not be able to reply util tomorrow. Thanks in advance.
SteveG
You realise the /system partition is seprate from the /data partition, so internal free space does not mean free space on the system partition. And did you remount the system partition yet? (This command in terminal emulator: mount -o remount,rw /system) Or you could simply use root explorer and save lots of trouble figuring out the terminal.
i would advise you to install xrecovery via aais, it is quite simple; download aais and put on your sd, download terminal emulator from the market (needs root, you are rooted you say so that is fine) type the commands:
su (start superuser, click allow)
cd sdcard/aais
sh install.sh (now you see the menu)
type 0 for installing xrecovery. phone will reboot and you're done. Download cwm for recovery.zip from xda and install cwm via xrecovery, now you can install custom roms.
ruifung said:
You realise the /system partition is seprate from the /data partition, so internal free space does not mean free space on the system partition.
Click to expand...
Click to collapse
Ah, no I didnt realise that. Anyway I can tell how much space in the system partition? Any reason why it should be full after a factory reset? If it is full, any suggestions?
ruifung said:
And did you remount the system partition yet? (This command in terminal emulator: mount -o remount,rw /system) Or you could simply use root explorer and save lots of trouble figuring out the terminal.
Click to expand...
Click to collapse
Nope, didnt realise I had to do this, , can you explain why?. Before I do anything else?
Ameijer said:
i would advise you to install xrecovery via aais, it is quite simple; download aais
Click to expand...
Click to collapse
From the market? Hehe, I didnt know what this was so I googled it. Found myself at the Association of Archaeological Illustrators and Surveyors. Strangley enough very little about Android on their website.
Ameijer said:
and put on your sd, download terminal emulator from the market (needs root, you are rooted you say so that is fine) type the commands:
su (start superuser, click allow)
cd sdcard/aais
sh install.sh (now you see the menu)
type 0 for installing xrecovery. phone will reboot and you're done. Download cwm for recovery.zip from xda and install cwm via xrecovery, now you can install custom roms.
Click to expand...
Click to collapse
If I do this where does the xrecovery file need to be for the install?
Thanks for replying guys. You have givne me some suggestions for the way forwards.
SteveG
AAIS is an automatic installer for xrecovery, sorry..was not clear enough apparently. You can find it here on xda (xrecovery automatic installation script or something like that) and works like a charm! No need to copy files yourself, run the script and you'll have xrecovery, afterwards install cwm via xrecovery..simple as that
AAIS did the trick (Although I had to use a magnifyng glass to use the terminal emulator. Currently waiting for the rom to finish installing.
Thanks for your help
I need help to fix my tab,
I've been running pershoots OC kernel with task's roms for several months with no problems and i've been keeping up to date with each version with out any problems.
I just rebooted my tab today and now suddenly out of the blue, the screen shows static and corrupted rbg lines after a few seconds of the samsung logo. And now it is stuck like this after repeatedly trying to turn my device on. I can get into CWM recovery but i dont a restore file on it because i moved them off my tab to my PC to save space.
Is there anyway to move the files back on to the tab to restore it or maybe move the stock kernel so i can flash it and see if that fixes it?
If you don't care about the data in your tab (all your apps and the /sdcard partition), you could try returning to stock via Odin. Here is a good guide (is the last part "Re-“Stocking” Yer System…"): The Guide
Other option (I recommend this one) is adb, in cwm just push the files you want to flash to the /sdcard .
Thanks! I'll try by android debug bridge and see if i can figure this out..
I have adb installed and it works but when i push the zip to /sdcard/ it doesnt show up on CWM install zip from sdcard menu option, i also tried to push it to /mnt/sdcard/ and the files doesnt show up.
I'm at a loss here the cmd prompt doesnt give any errors after the zip transfer
Mercatorn said:
I have adb installed and it works but when i push the zip to /sdcard/ it doesnt show up on CWM install zip from sdcard menu option, i also tried to push it to /mnt/sdcard/ and the files doesnt show up.
I'm at a loss here the cmd prompt doesnt give any errors after the zip transfer
Click to expand...
Click to collapse
Are you mounting the partition? My guess is you forgot to do it.
Enter the follow commands (one by one) in the terminal (cmd prompt):
Code:
adb shell
Code:
mount /data
Code:
exit
Code:
adb push fileyouwanttoflash.zip /data/media
Now the file should be in /sdcard, just install it from cwm.
If at the moment you're trying to choose the zip from sdcard you get an error telling you "Couldn't open directory" and "No files found", reboot cwm.
Other way to do it is in cwm (so you don't have to do the "adb shell" and "adb mount")
In cwm, choose "install zip from sdcard", then "choose zip from sdcard", then "+++++Go Back+++++"
And from your cmd promt:
Code:
adb push fileyouwanttoflash.zip /sdcard/
Now, flash the file from cwm. (Again, if there's some error, reboot cwm).
I am very new to the android world, seeing as I am a recent iOS convert. However, I am still struggling with all the terminology and technicalities of android and require assistance (perhaps a lot! :cyclops.
I have managed to root my G2 (VERIZON MODEL) but am stuck there. I do not know how to install CWM or TWRP, nor install any custom ROMs like CM or Gummy.
So will anyone be kind enough to guide me through the process? Thank you.
P.S.
I have searched through the threads in this forum regarding installing custom ROMs and am still confused.
from this thread here
http://forum.xda-developers.com/showthread.php?t=2449670
first download twrp for your device, http://techerrata.com/file/twrp2/g2vzw/openrecovery-twrp-2.6.3.3-g2vzw.zip
plug the phone to the computer, make sure u have usb debugging on in developer settings of phone
since you are already rooted, place that file recovery img to the IOROOT folder.
once done, rename the recovery file to recovery.img
one done, CONTROL + SHIFT + RIGHT CLICK, OPEN COMMAND PROMPT HERE
then type this
adb push recovery.img /data/local/tmp/recovery.img
adb shell
(IF YOU DONT SEE A # prompt on your phone, type su in the command prompt to get it then allow it on phone. once thats done then contine onto next step blow.)
cd /data/local/tmp
dd if=/data/local/tmp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
exit
adb reboot recovery
once its complet just reboot the phone and you should have twrp installed!
once twrp is installed, you can dl the verizon version of paranoid android here
http://downloads.codefi.re/houstonn/kitkat/G2/PA/vs980/pa_g2-4.0-ALPHA-20131205-vs980.zip
and
http://www.androidfilehost.com/?fid=23252070760973599
dl the file, drag the files to the phone, dont place into any folder though.
to install, go to the ioroot folder again, control shift right click open prompt again, type adb reboot recovery
phone should reboot to recovery, go to settings, then select USE RM-F instead of formatting, then go to wipe, advance, select dalvik cache, system, data, and cache. IMPORTANT DO NOT SELECT INTERNAL STORAGE!!!
then swipe to wipe
then go to install then install the paranoid android download first, once its installed, hit the back button on the botom right, then install the GAPPS, then reboot the device your done.
Or you could just download the recovery.img that u choose, and flash it using the app called "Flashify". Easiest way by far and works perfectly for me everytime, using both TWRP and CWM whenever I need.
Once you have that done, installing a ROM such as GUMMY is fairly simple since it usually has the instructions right there in the OP of the thread. Pretty straightforward.
expertzero1 said:
from this thread here
http://forum.xda-developers.com/showthread.php?t=2449670
first download twrp for your device, http://techerrata.com/file/twrp2/g2vzw/openrecovery-twrp-2.6.3.3-g2vzw.zip
plug the phone to the computer, make sure u have usb debugging on in developer settings of phone
since you are already rooted, place that file recovery img to the IOROOT folder.
once done, rename the recovery file to recovery.img
one done, CONTROL + SHIFT + RIGHT CLICK, OPEN COMMAND PROMPT HERE
then type this
adb push recovery.img /data/local/tmp/recovery.img
adb shell
(IF YOU DONT SEE A # prompt on your phone, type su in the command prompt to get it then allow it on phone. once thats done then contine onto next step blow.)
cd /data/local/tmp
dd if=/data/local/tmp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
exit
adb reboot recovery
once its complet just reboot the phone and you should have twrp installed!
once twrp is installed, you can dl the verizon version of paranoid android here
http://downloads.codefi.re/houstonn/kitkat/G2/PA/vs980/pa_g2-4.0-ALPHA-20131205-vs980.zip
and
http://www.androidfilehost.com/?fid=23252070760973599
dl the file, drag the files to the phone, dont place into any folder though.
to install, go to the ioroot folder again, control shift right click open prompt again, type adb reboot recovery
phone should reboot to recovery, go to settings, then select USE RM-F instead of formatting, then go to wipe, advance, select dalvik cache, system, data, and cache. IMPORTANT DO NOT SELECT INTERNAL STORAGE!!!
then swipe to wipe
then go to install then install the paranoid android download first, once its installed, hit the back button on the botom right, then install the GAPPS, then reboot the device your done.
Click to expand...
Click to collapse
So I take it that I put the "ioroot10" file into my phone over the USB, then extract the files of the TWRP file, then place the extracted TWRP file inside of the ioroot10 file? Also, I did the control+shift+right click, but there is not OPEN COMMAND PROMPT option. Sorry for all the questions..
dlee96 said:
So I take it that I put the "ioroot10" file into my phone over the USB, then extract the files of the TWRP file, then place the extracted TWRP file inside of the ioroot10 file? Also, I did the control+shift+right click, but there is not OPEN COMMAND PROMPT option. Sorry for all the questions..
Click to expand...
Click to collapse
no, you place the recovery.img to the ioroot10 folder, ioroot10 stays on your computer.
control + shift + right click = open command window here
Just use flashify its free n so much easier
the definition of open: “mkdir android ; cd android ; repo init -u git:// android.git.kernel.org/platform/manifest.git ; repo sync ; make" gansta mic drop
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.