Hi
1. Install NewKingRoot
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
2.Install Busybox
https://play.google.com/store/apps/details?id=stericson.busybox
3. Install Terminal Emulator for Android
https://play.google.com/store/apps/details?id=jackpal.androidterm&hl
4.Install Mount system rw
https://play.google.com/store/apps/details?id=com.blogspot.superthomaslab.mountsystemrorw&hl
5. Install Replace_Kinguser_with_SuperSU-v2.4
http://www.mediafire.com/download/x1efi7ev6nf3mvd/Replace_Kinguser_with_SuperSU-v2.0.zip
-Install KingRoot
-Install Busybox
-Instanll Mount system and open, click mount /system RW
-Open Replace_Kinguser_with_SuperSU-v2.4 Extracted folder "mrw" to the internal storage of your device
-Open Terminal emulator and write code.
su
sh storage/emulated/0/mrw/root.sh
-open supersu manually.
-Update su binary normal, then manually reboot.
Your devices root
Test: 30.1.A.133
You actually need not to install SuperSU after installing Kingroot (not KingoRoot), there is a built-in one, but he Kingroot one have no option for modifying the apps.
You could just simply click "get now" to root your phon.
AlgebraTheBard
owned devices:
Sony Xperia M5 dual (recent)
ZTE Nubia Z7 mini (backup)
Motorola RAZR XT910 custom
He wants some applications SuperSu. I shared information purposes Thanks, clerical error
algebrathebard said:
You actually need not to install SuperSU after installing Kingroot (not KingoRoot), there is a built-in one, but he Kingroot one have no option for modifying the apps.
You could just simply click "get now" to root your phon.
AlgebraTheBard
owned devices:
Sony Xperia M5 dual (recent)
ZTE Nubia Z7 mini (backup)
Motorola RAZR XT910 custom
Click to expand...
Click to collapse
If you root with dodgy kingroot you must change kinguser to supersu as kinguser does not give the same root access permissions as supersu does and will cause problems...
Good to know, thanks to Aidy Lucas.
AlgebraTheBard
owned devices:
Sony Xperia M5 dual (recent)
ZTE Nubia Z7 mini (backup)
Motorola RAZR XT910 custom
[email protected] said:
If you root with dodgy kingroot you must change kinguser to supersu as kinguser does not give the same root access permissions as supersu does and will cause problems...
Click to expand...
Click to collapse
@[email protected]
When you say kingroot is dodgy, can you go straight to SuperSU?
I would love that without unlocking my bootloader if possible.
icstm said:
@[email protected]
When you say kingroot is dodgy, can you go straight to SuperSU?
I would love that without unlocking my bootloader if possible.
Click to expand...
Click to collapse
There's a zip you flash via recovery probably other ways too, it removes all the kingroot/kinguser files and replaces them with supersu for proper root access. Really don't see the point in buying a Xperia device for the camera ect then unlocking the Bootloader and losing it yes I know there's a workaround for the z ranges but bet it's not as good as the real drm keys
Does this root the Sony Xperia M5 (E5653)?
Dreamer62 said:
Hi
1. Install NewKingRoot
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
2.Install Busybox
https://play.google.com/store/apps/details?id=stericson.busybox
3. Install Terminal Emulator for Android
https://play.google.com/store/apps/details?id=jackpal.androidterm&hl
4.Install Mount system rw
https://play.google.com/store/apps/details?id=com.blogspot.superthomaslab.mountsystemrorw&hl
5. Install Replace_Kinguser_with_SuperSU-v2.4
http://www.mediafire.com/download/x1efi7ev6nf3mvd/Replace_Kinguser_with_SuperSU-v2.0.zip
-Install KingRoot
-Install Busybox
-Instanll Mount system and open, click mount /system RW
-Open Replace_Kinguser_with_SuperSU-v2.4 Extracted folder "mrw" to the internal storage of your device
-Open Terminal emulator and write code.
su
sh storage/emulated/0/mrw/root.sh
-open supersu manually.
-Update su binary normal, then manually reboot.
Your devices root
Click to expand...
Click to collapse
Can anyone advise whether this works on the SONY M5 (E5653), as sold here in Thailand?
Thanks!
Max
[email protected] said:
There's a zip you flash via recovery probably other ways too, it removes all the kingroot/kinguser files and replaces them with supersu for proper root access. Really don't see the point in buying a Xperia device for the camera ect then unlocking the Bootloader and losing it yes I know there's a workaround for the z ranges but bet it's not as good as the real drm keys
Click to expand...
Click to collapse
@[email protected]
The problem is that the only way I know if via recovery and there is no custom recovery yet for this phone... I was not planning on unlocking the bootloader, but I do want a rooted phone.
I can confirm this method.
Works like a charm.
Not too difficult to do, all though I do like the "one click" magic
Hello, and thank you for the guide. I have some questions that I would like someone to address please.
1. After installing KingRoot, do I have to run the app and go through the rooting process? Or i just install it and follow the other steps?
2. mount /system RW says 'your device may not be rooted or is not compatible'
3. You say '-Open Terminal emulator and write code.
su
sh storage/emulated/0/mrw/root.sh'. However, when I type su, it says SU not found.
Thank you in advance all.
You didn't root your phone.When you install KingRoot you have to open the app and click on Root,you may have to try several times until you are abel too root it,just keep trying for me it took three times to make it work,for some up to 7 times,but when it's rooted it will show you the message that your phone is rooted and then you can follow the rest guide...
Sent from my E5603 using XDA-Developers mobile app
Hello, thank you very much for your reply. I did as you said and now I have SuperSU and kinguser is no longer there. I have one more question, if you dont mind. Is it OK if I remove Purify and SuperBattery now?
PS: I got a bit anxious while installing SuperSU, as it asked to delete other superuser apps, i said OK, and it stuck at 'supersu uninstalling'. However, I restarted the phone and everything was OK.
pren22 said:
You didn't root your phone.When you install KingRoot you have to open the app and click on Root,you may have to try several times until you are abel too root it,just keep trying for me it took three times to make it work,for some up to 7 times,but when it's rooted it will show you the message that your phone is rooted and then you can follow the rest guide...
Click to expand...
Click to collapse
omrtpsycho said:
Hello, thank you very much for your reply. I did as you said and now I have SuperSU and kinguser is no longer there. I have one more question, if you dont mind. Is it OK if I remove Purify and SuperBattery now?
PS: I got a bit anxious while installing SuperSU, as it asked to delete other superuser apps, i said OK, and it stuck at 'supersu uninstalling'. However, I restarted the phone and everything was OK.
Click to expand...
Click to collapse
Yes you can remove those apps...
Sent from my E5603 using XDA-Developers mobile app
Are the steps applicable to M5 Dual E5663 build 30.1.B.1.55 ?
Help
Dreamer62 said:
Hi
1. Install NewKingRoot
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
2.Install Busybox
https://play.google.com/store/apps/details?id=stericson.busybox
3. Install Terminal Emulator for Android
https://play.google.com/store/apps/details?id=jackpal.androidterm&hl
4.Install Mount system rw
https://play.google.com/store/apps/details?id=com.blogspot.superthomaslab.mountsystemrorw&hl
5. Install Replace_Kinguser_with_SuperSU-v2.4
http://www.mediafire.com/download/x1efi7ev6nf3mvd/Replace_Kinguser_with_SuperSU-v2.0.zip
-Install KingRoot
-Install Busybox
-Instanll Mount system and open, click mount /system RW
-Open Replace_Kinguser_with_SuperSU-v2.4 Extracted folder "mrw" to the internal storage of your device
-Open Terminal emulator and write code.
su
sh storage/emulated/0/mrw/root.sh
-open supersu manually.
-Update su binary normal, then manually reboot.
Your devices root
Test: 30.1.A.133
Click to expand...
Click to collapse
Support Firmware
• 30.1.A.1.55 ?
Hello but can anyone confirm if this method is just for root or also onlocks bootloader? I just want root access and don't want to lose my DRM keys!
Thank you
Works also on 30.1.A.1.55
Osorio_117 said:
Support Firmware
• 30.1.A.1.55 ?
Click to expand...
Click to collapse
Yes, just did it and worked on first try.
confirming its method to be root has been a success and should be noted that when executing commands from the internal memory of the folder mrw also be done through the external memory
Code:
su
sh sdcard1/mrw/root.sh
screenshot :fingers-crossed:
Alzatan said:
Hello but can anyone confirm if this method is just for root or also onlocks bootloader? I just want root access and don't want to lose my DRM keys!
Thank you
Click to expand...
Click to collapse
It works and you wont lose your DRM keys!!!
Related
A Work in progress.
DISCLAIMER!
This Document ONLY applies to Acer Iconia A100 devices. For info on upgrading from HC to ICS you can look HERE to see the method I used to upgrade from stock HC 3.2 GEN2 to ICS (Note: This was before the general ICS release. It works on OTA update also) Then follow these directions to get to CWM with Custom ROM.
I'm writing this because we STILL don't seem to have a single clear set of instructions. So here is my attempt at getting one started. Please feel free to point out errors, or help us build a set of directions. I'm not trying replace anyones documentation or take credit for anything. All the info in these directions can already be found here in various posts.
Thanks to Vache, Civato, ZeroNull, Euclid's Brother, Ptesmoke, abliss, aznmode, eew245, crossix, Icewyng, toyface, PG101, Smokku and Everyone else for all the Work an Insight.
ROOT
To root ICS Leaks you need to use mempodroid(info & file here). Eew245 wrote up instructions (on applying mempodroid on A100 to obtain a root shell). ZeroNull also has made a basic script found here that will root the device for you if you prefer.
I use the method outlined by Eew245. You can use your own "su" and "busybox" binaries if you saved them. This method provides full permanent root.
I suggest you install superuser.apk and busybox installer after rooting. Superuser.apk will provide access control for superuser and busybox installer will allow you to update busybox. I also recomend installing terminal emulator(don't forget to configure it to use /system/xbin/sh after you install busybox).
UNLOCK
ZeroNull has made an easy to use package with instructions here If you don't have the Android SDK installed ZeroNulls method works fine. However if you want to use your own platform-tools you will need to modify the scripts first.(Just change the path for adb. Otherwise it will try to look for adb in the scripts working directory instead of platform-tools).
Pic of Bootloader warning about unlocking from Acer
PIC HERE
Lock Unlock Icons from same bootloader screen.
PIC HERE
Note: If you miss the window of oportunity running the script or unlock commands the first time. You DON'T need to rerun the whole script. The a200 bootloader is already installed. You just need to fastboot reboot bootloader again from your console, THEN you can use the vol keys and home to unlock the bootloader. BUT do what ever you feel safest doing and just pay attention and be careful. (Here I'm referring to the waiting too long after the script boots recovery into unlock mode. If you wait too long it times out and you can't choose unlock until you fastboot reboot bootloader again.)
RECOVERY
(make sure you have installed the a200/unlocked bootloader first. You will see a message at the top of the screen that says (UNLOCK MODE) when bootloader is showing it's message at boot.)
Here is the message I'm referring to PIC HERE
NOTE: When installing a Custom Recovery at some point you have to rename /etc/install-recovery.sh or remove it. I would recomend you rename it to install-recovery.sh.bak. You should do this before doing "adb reboot bootloader" otherwise when you try to reboot into recovery from ROM manager you will get a dead android because cwm will be overwriten with the old recovery(and you don't want that). If you DO get a dead android carefully read the directions again. Q. Why didn't I put this in a step? A. Because I dont want people to brick a device so I want to make sure they are paying attention before I tell them to rename a file that will keep the system from fixing recovery if they mess up.
Using Acer Recovery Installer 2.99 Beta(NOT MARKET VERSION)
=======================================
Download .apk enable non-market installers. Run installer, enjoy.
The Acer Recovery Installer 2.99 Beta is found HERE
Using ADB/Fastboot to flash CWM
============================
Use the steps found HERE(obviously don't re-root, unlock, just follow the other parts.
Or you can also use A100 TWRP recovery v2.1.0+ I have not tried it yet. It looks nice, has touch screen functionality, I think it uses a different backup format or something though. I'm not sure and have not had time to read up on it yet.
NOTE: Read my note above about /etc/install-recovery.sh
FLASH FROM CWM
==============
If you used ADB/Fastboot method you will need a way to reboot into CWM. ROM manager or bootloader reboot thingie will work for this.
If you installed Acer Recovery Image you can use it the app to boot into CWM.
CWM 5.5.0.4 uses the Volume Up/Down Toggle to navigate the menu and a short click of the power button to select things. Be careful about what you choose to do in CWM.
MAKE A BACKUP!!
===============
If you have just installed a custom recovery NOW would be a GOOD time to make a backup with CWM.
To Install a Custom ROM
===============
(BE CAREFUL. MAKE SURE The ROM you choose to install DOESN'T have a bootloader.blob and/or /recovery folder inside. Otherwise it could overwrite your CWM)
Just put the .zip file on an SD card and put it into the device. Use ROM Manager or Acer Recovery Installer
More to come, and I will add some pics showing what various screen look like when I'm able.
"I suggest you install superuser.apk and busybox installer after rooting. Superuser.apk will provide access control for superuser and busybox installer will allow you to update busybox. I also recomend installing terminal emulator(don't forget to configure it to use /system/xbin/sh after you install busybox)."
So ZeroNull says to not update busybox ...you say to update it...is there really a problem if you update it??
cheeb said:
"I suggest you install superuser.apk and busybox installer after rooting. Superuser.apk will provide access control for superuser and busybox installer will allow you to update busybox. I also recomend installing terminal emulator(don't forget to configure it to use /system/xbin/sh after you install busybox)."
So ZeroNull says to not update busybox ...you say to update it...is there really a problem if you update it??
Click to expand...
Click to collapse
i +1 the question what will break if i update busy box?
cheeb said:
"I suggest you install superuser.apk and busybox installer after rooting. Superuser.apk will provide access control for superuser and busybox installer will allow you to update busybox. I also recomend installing terminal emulator(don't forget to configure it to use /system/xbin/sh after you install busybox)."
So ZeroNull says to not update busybox ...you say to update it...is there really a problem if you update it??
Click to expand...
Click to collapse
I don't know if this helps or makes things worst, but I have updated busybox after using Zeronull's root script on pretty much every ICS leak, CM9, and Flexreaper without any issues at all. I always read that warning, but ignored it because I need a more complete busybox version for certain tasks I run on my tablet.
NoSudo said:
A Work in progress.
Using ADB/Fastboot to flash CWM
============================
Use the steps found HERE(obviously don't re-root, unlock, just follow the other parts.
Click to expand...
Click to collapse
Just a little tip. Actually same thread post#28 uses very simple method thanks to mapaz04 to flash the recovery.
Great job though!
I did almost the same in my native language.
cheeb said:
"I suggest you install superuser.apk and busybox installer after rooting. Superuser.apk will provide access control for superuser and busybox installer will allow you to update busybox. I also recomend installing terminal emulator(don't forget to configure it to use /system/xbin/sh after you install busybox)."
So ZeroNull says to not update busybox ...you say to update it...is there really a problem if you update it??
Click to expand...
Click to collapse
I have not used ZeroNulls root method. So I am not sure why he says that. I think his script MAY just use the su and busybox in place in /data/local/ or something(not sure havnt D/L the package to figure it out). You CAN setup su and busybox in the correct locations WITHOUT an issue in ICS.
I use the "hard" method which is very simple. I KNOW you can remove the /data/local/tools copy afterwords doing it by hand.
An Explanation:
The reason you have to push su, mempodroid, busybox, and a mount script to /data/local/ is because you can get write access to it WITHOUT su. Then you run mempodroid which does a little magic and tricks system into thinking a shell was started by root. This drops you into the # prompt(temp). Then you mount /system(still using the files from /data/local). Then you copy the files to the correct path inside /system. Once you chmod su and run it you get root becase su is a special kind of executable. It's what is called an SUID application. As long as the permissions are correct to allow you read/exec access to both su and busybox. You no longer need /data/local/tools. At this point you CAN update busybox and su if you like.
P.S. You can also use your OLD su and busybox for the whole thing. I saved my old su and busybox and always just reuse them then update.
If you want to understand more I would suggest reading up on what SUID is all about and also learn about Unix file permissions.
I can confirm that: rooting,bootloader unlock and change on the recovery can be made with OTA update.
Nice work!
gertjanad said:
Nice work!
Click to expand...
Click to collapse
Thanks, and a bump to keep the info around the first page.
Added to bump it back up so people can find it.
Is there a kernel that allows overclocking yet
Sent from my A100 using XDA
I have not played with OCing, I honestly don't see a need.
I know cwm 5.5.0.x has an Overclock menu so I'm guessing yes you can. But I am not familiar enough with the device/cpu to know how the multipliers etc are to be configured, nor do I experience lag or performance issues that would cause me to desire lowering battery efficiency and increase heat for faster performance.
Though I am familiar with the process on PCs both jumpered and jumperless.
Up!
Hello every one
First of all. I have a problem I can not delete the basic device software note I have root authority
II. Was installed busyBox but I can not install it and when the installation device works Risterat What problem
read about write system protection.
tutos are available on this forum (wp_mod.ko file to push in system/lib/modules, and run a command on the phone with a terminal app)
#su
insmod system/lib/modules/wp_mod.ko
if im speaking chinese, dont try
but as you tried to change partitions before having write protection removed, you wont be able to do it without a restart until you reflash your rom (clean install)
fabulous69 said:
read about write system protection.
tutos are available on this forum (wp_mod.ko file to push in system/lib/modules, and run a command on the phone with a terminal app)
#su
insmod system/lib/modules/wp_mod.ko
if im speaking chinese, dont try
but as you tried to change partitions before having write protection removed, you wont be able to do it without a restart until you reflash your rom (clean install)
Click to expand...
Click to collapse
Excuse me, I hope if they do not understand you, and my heartfelt thanks for the quick feedback if possible, a simple explanation for the action steps
i think you shouldn't try to do it...
a bad understanding of a Tutorial, and you could make your phone bug.
Follow These Steps....
muhamadalani said:
Excuse me, I hope if they do not understand you, and my heartfelt thanks for the quick feedback if possible, a simple explanation for the action steps
Click to expand...
Click to collapse
Quoted from Step 2 Here,
http://forum.xda-developers.com/desire-816/general/guide-vm-htc-desire-816-root-how-to-t2862470 ,
2. Hopefully you were able to successfully install custom recovery and root.
Now this part is a bit tricky. Even with root HTC is stopping us from writing to system. For this we need to apply the wp_mod.ko module.
Download it here: http://forum.xda-developers.com/show....php?t=2707378
Copy this file to the root of your internal storage.
Now download Terminal Emulator from play store, run it and enter the following commands (you only need to do this once):
su
insmod /sdcard/wp_mod.ko
Once you do this go into a root explorer app and mount /system as R/W. Copy the wp_mod.ko file to /system/lib/modules
Now go to /system/etc and find install-recovery.sh. Open it with a text editor and add a new line at the end with the following:
insmod /system/lib/modules/wp_mod.ko
Reboot! If all went well the wp_mod module will run at boot every time so you won't have to do it manually each time!
Congratulations, you now have a fully rooted Desire 816!
jayblaze406 said:
Quoted from Step 2 Here,
http://forum.xda-developers.com/desire-816/general/guide-vm-htc-desire-816-root-how-to-t2862470 ,
2. Hopefully you were able to successfully install custom recovery and root.
Now this part is a bit tricky. Even with root HTC is stopping us from writing to system. For this we need to apply the wp_mod.ko module.
Download it here: http://forum.xda-developers.com/show....php?t=2707378
Copy this file to the root of your internal storage.
Now download Terminal Emulator from play store, run it and enter the following commands (you only need to do this once):
su
insmod /sdcard/wp_mod.ko
Once you do this go into a root explorer app and mount /system as R/W. Copy the wp_mod.ko file to /system/lib/modules
Now go to /system/etc and find install-recovery.sh. Open it with a text editor and add a new line at the end with the following:
insmod /system/lib/modules/wp_mod.ko
Reboot! If all went well the wp_mod module will run at boot every time so you won't have to do it manually each time!
Congratulations, you now have a fully rooted Desire 816!
Click to expand...
Click to collapse
Thank you
Unfortunately, I could not do a thing did not work the way and I do not know why:crying::crying::crying:
Was setting up my device for a replacement ended up keeping it, Before I attempt anything, I want to make sure I'm not still rooted.
I currently wiped all storage options (including internal) Will I have to root my device again? Or is there another way to get twrp on the device? Maybe thru adb????
To check if you are rooted you could use app like: https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
or you could open up adb, enter adb shell (by writing adb shell) and asking for SU access
by writing: su
into the shell.
If you wiped internal, cache, data, you should still have root as you did not touch your system partition.
To install TWRP you can get it here: http://forum.xda-developers.com/lg-g3/orig-development/recovery-twrp-touch-recovery-2-8-2-0-t2966129
extract the downloaded zip, and flash with flashify or manually by entering the commands provided in the thread.
NatusVincere said:
or you could open up adb, enter adb shell (by writing adb shell) and asking for SU access
by writing: su
into the shell.
Click to expand...
Click to collapse
I get the message '/system/bin/sh: su: not found'
tarroyo said:
I get the message '/system/bin/sh: su: not found'
Click to expand...
Click to collapse
Which means that you have no root access. You could confirm it with the app I recommended in post above or one of many apps available on google play for that.
To root your device again you could use: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
You also have other root methods available, I personally used Purple Drake method.
NatusVincere said:
To check if you are rooted you could use app like: https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
or you could open up adb, enter adb shell (by writing adb shell) and asking for SU access
by writing: su
into the shell.
If you wiped internal, cache, data, you should still have root as you did not touch your system partition.
To install TWRP you can get it here: http://forum.xda-developers.com/lg-g3/orig-development/recovery-twrp-touch-recovery-2-8-2-0-t2966129
extract the downloaded zip, and flash with flashify or manually by entering the commands provided in the thread.
Click to expand...
Click to collapse
NatusVincere said:
Which means that you have no root access. You could confirm it with the app I recommended in post above or one of many apps available on google play for that.
To root your device again you could use: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
You also have other root methods available, I personally used Purple Drake method.
Click to expand...
Click to collapse
Thanks for your help. I rooted successfully using this method way easier then purpledrake http://forum.xda-developers.com/lg-...lg-devices-t3129197/post61208412#post61208412
Finally i found a method to install Xposed framework on K4 note (I am on S152 ROW version) :victory::cyclops: Requisites:-
1. Rooted Phone
2. Busybox
3. Terminal Emulator
4. Xposed zip and installer apk files
5. SuperSu and not Kinguser
Here are the steps:-
1. Download the Zip file from here: [url]https://drive.google.com/file/d/0B7DMgItCtbjhY2hwQlM0dWdVVlE/view?usp=sharing[/URL]
2. Extract it into your phone's internal storage using any of the file manager (Though i prefer ES)
3. Install busybox from the folder and open it. Click on install and let it install the lib files.
4. Now copy the installer.bin file and xposed-sdk22-arm64.zip to root of your internal storage.
5. Now install terminal emulator and open it.
Type su and enter and allow SuperSu permission and then it will show '#' instead of '$'.
6. Now type sh /sdcard/installer.bin and press enter. (Note:- If it fails to install, rename the xposed.zip file in the root folder with xposed-vsdk.zip and installation should go through. Thanks @Ondipuli for this suggestion.)
7. It will ask whether to install Xposed or not. Press 1
Wait for the process to finish and then it will say install is successful.
8. Reboot the Phone. It might seem it is stuck at boot but give it some time(5 mins). Then it will start optimizing the apps and let it finish with that.
Now open xposed app and Voila! Xposed is installedEnjoy Xposing!!Credit goes to Razor Beam from youtube...
Hit Thanks if i helped:fingers-crossed::fingers-crossed:..
Dear Bro, I Installed several times but never ever this installer.bin file ever used. And every time I got succeded. Via Flashfire 0.24
ramisumi said:
Dear Bro, I Installed several times but never ever this installer.bin file ever used. And every time I got succeded. Via Flashfire 0.24
Click to expand...
Click to collapse
Bro, this method is for those who don't want to install flashfire to flash xposed or for those who simply cant get xposed working through Flashfire(I myself was unable to install it through flashfire).
Though flashfire is recommended, sometimes it fails to flash the zip on some devices and that is a known issue. Chainfire is working on the solution.
It works great. Thanks, but at first installer.bin doesn't detect xposed zip file, as the installer search for a file xposed-v*, then i renamed zip file as xposed-vsdk like that & it installed perfectly.
Sent from my Lenovo A7010a48 using XDA Premium 4 mobile app
Ondipuli said:
It works great. Thanks, but at first installer.bin doesn't detect xposed zip file, as the installer search for a file xposed-v*, then i renamed zip file as xposed-vsdk like that & it installed perfectly.
Sent from my Lenovo A7010a48 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes its true. I also tried but renaming is useful or I have xposed zip already i flashed with flashfire. That also worked with this installer.bin. But as it is provided zip is not installing without renaming or the otherr copy.
Ondipuli said:
It works great. Thanks, but at first installer.bin doesn't detect xposed zip file, as the installer search for a file xposed-v*, then i renamed zip file as xposed-vsdk like that & it installed perfectly.
Sent from my Lenovo A7010a48 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ramisumi said:
Yes its true. I also tried but renaming is useful or I have xposed zip already i flashed with flashfire. That also worked with this installer.bin. But as it is provided zip is not installing without renaming or the otherr copy.
Click to expand...
Click to collapse
Actually, for me it installed without the need of renaming. But still if you guys say so, I will edit the post and mention the need to rename the zip if it's not working by default.
Thanks..
Worked for me after renaming. Thanks.
Virus0044 said:
Worked for me after renaming. Thanks.
Click to expand...
Click to collapse
I am glad it did!
Krishnas096 said:
Finally i found a method to install Xposed framework on K4 note (I am on S152 ROW version) :victory::cyclops: Requisites:-
1. Rooted Phone
2. Busybox
3. Terminal Emulator
4. Xposed zip and installer apk files
5. SuperSu and not Kinguser
Here are the steps:-
1. Download the Zip file from here: https://drive.google.com/file/d/0B7DMgItCtbjhY2hwQlM0dWdVVlE/view?usp=sharing
2. Extract it into your phone's internal storage (Though i prefer ES)
3. Install busybox from the folder and open it. Click on install and let it install the lib files.
4. Now copy the installer.bin file and xposed-sdk22-arm64.zip to root of your internal storage.
5. Now install terminal emulator and open it.
Type su and enter and allow SuperSu permission and then it will show '#' instead of '$'.
6. Now type sh /sdcard/installer.bin and press enter. (Note:- If it fails to install, rename the xposed.zip file in the root folder with xposed-vsdk.zip and installation should go through. Thanks @Ondipuli for this suggestion.)
7. It will ask whether to install Xposed or not. Press 1
Wait for the process to finish and then it will say install is successful.
8. Reboot the Phone. It might seem it is stuck at boot but give it some time(5 mins). Then it will start optimizing the apps and let it finish with that.
Now open xda installer app and Voila! Xposed is installedEnjoy Xposing!!Credit goes to Razor Beam from youtube...
Hit Thanks if i helped:fingers-crossed::fingers-crossed:..
Click to expand...
Click to collapse
[email protected]:/ $ su
[email protected]:/ # sh /sdcard1/installer.bin
sh: /sdcard1/installer.bin: No such file or directory
127|[email protected]:/ # sh /sdcard1/installer.bin
sh: /sdcard1/installer.bin: No such file or directory
127|[email protected]:/ # '$'.
k_shell/10161:17229: $.: not found
127|[email protected]:/ #
Plz help how to install
Help
executed installer.bin then pressed 1 but after that it shows cant create folder
PLEASE HELP**
In terminal window it is saying :
k_shell/10259:12535: sh/sdcard/installer.bin: not found
i did rename xposed-sdk22-arm64.zip into xposed-vsdk.zip but it still saying failed . what should i do now ?
shanky_x said:
PLEASE HELP**
In terminal window it is saying :
k_shell/10259:12535: sh/sdcard/installer.bin: not found
i did rename xposed-sdk22-arm64.zip into xposed-vsdk.zip but it still saying failed . what should i do now ?
Click to expand...
Click to collapse
Are you trying this method on Lollipop or Marshmallow. If so then on what version(Build no).
Sorry for the late reply. I am a student and i am not able to come online on xda regularly.
Permission ?
Hi,
I try this method, follow every steps, but it tell me this:
mount: Operation not permitted
/sdcard/installer.bin[25]: can't create /test.txt: read-only file system
Error: Busybox is not installed
I'm rooted under SuperSu, Xposed installer is installed, same as Busybox (by install the lib file too)
Can i get some help please.
Thnx BUT...
OK the first time I tried it did not work so I renamed the xposed package to xposed-vsdk.zip but it did not install the zip so xposed did not recognize or find it. So I when online and downloaded the latest sdk22 (sdk22=lollipop). I renamed it and it worked so I think you should update the master zip with the latest xposed zip.
BTW This also this works on Kindle Fire HD 8 cuz FlashFire doesn't support it.
shanky_x said:
PLEASE HELP**
In terminal window it is saying :
k_shell/10259:12535: sh/sdcard/installer.bin: not found
i did rename xposed-sdk22-arm64.zip into xposed-vsdk.zip but it still saying failed . what should i do now ?
Click to expand...
Click to collapse
Your command is missing " "(space)
The correction command is
sh /sdcard/installer.bin
Enjoy
chitranjn_k said:
[email protected]:/ $ su
[email protected]:/ # sh /sdcard1/installer.bin
sh: /sdcard1/installer.bin: No such file or directory
127|[email protected]:/ # sh /sdcard1/installer.bin
sh: /sdcard1/installer.bin: No such file or directory
127|[email protected]:/ # '$'.
k_shell/10161:17229: $.: not found
127|[email protected]:/ #
Plz help how to install
Click to expand...
Click to collapse
may be the installer.bin is in sdcard, not sdcard1
can i install on any device using this method actually I have mobile which has android 5.1.1 and arm 32bit system can i install frame work using this technique
Rename the file txt at the place of bin.then try
shanky_x said:
PLEASE HELP**
In terminal window it is saying :
k_shell/10259:12535: sh/sdcard/installer.bin: not found
i did rename xposed-sdk22-arm64.zip into xposed-vsdk.zip but it still saying failed . what should i do now ?
Click to expand...
Click to collapse
Ans:-Give space after sh. (sh /sdcard/installer.bin)
atif ahmad said:
can i install on any device using this method actually I have mobile which has android 5.1.1 and arm 32bit system can i install frame work using this technique
Click to expand...
Click to collapse
No. You cannot. The script and the xposed apk inside the zip file are for arm64 so it wont be possible. Don't try it and brick your device.
About the only reason I root my phone is to install AdAway. I'd prefer to not modify the system partition to help make OTA's easier to get and to allow Android Pay to work. AdAway has a flashable .zip file that preps the hosts file to use the systemless root structure that comes along with SuperSU. Unfortunately, that script depends on being able to access the /data partition inside of TWRP which isn't going to happen any time soon on the HTC 10. Fortunately, it is easy for us to manually replicate what the flashable .zip is trying to do.
This isn't a detailed how-to, but more of a set of guidelines. Don't blame me if your phone explodes.
Root the phone with the latest SuperSU.
Download the AdAway_systemless_hosts_v2.zip file from the Unofficial AdAway thread.
Extract the files from inside the zip. We are only interested in two files in the support folder.
Connect the phone to your PC and turn on file transfer mode.
Copy "hosts" and "0000adaway.script" that you just extracted to the internal storage of your phone.
Use a program file Root Explorer to move "hosts" into /su/etc and move "0000adaway.script" into /su/su.d (this probably could have been done with ADB push, but I got permission errors when I tried it that way and I'm impatient and lazy).
Chmod 0755 /su/su.d/0000adaway.script (I used a root shell on the phone via ADB)
Install AdAway (I used the link in the Unofficial AdAway thread.)
Reboot the phone.
Run AdAway like normal. By default it should use /system/etc/hosts which is what you want.
If something doesn't work, figure out why and fix it. I'm happy to answer questions to the best of my ability.
AdAway works without problems here, with simple press activate button.
starbase64 said:
AdAway works without problems here, with simple press activate button.
Click to expand...
Click to collapse
Yup
Sent from my HTC 10 using Tapatalk
starbase64 said:
AdAway works without problems here, with simple press activate button.
Click to expand...
Click to collapse
Yes, but it modifies the /system partition unless you do the trick in OP. If I'm correct, you will have problems with OTA updates and Google Pay if you let AdAway directly modify the hosts file on /system.
Now that TWRP can access /data, can we just flash the zip?
goodtimes50 said:
Now that TWRP can access /data, can we just flash the zip?
Click to expand...
Click to collapse
Yes, you can. I downloaded that zip and apk from the Unofficial AdAway thread linked above. Booted into TWRP, flashed the newest betaSuperSU2.74-2-forceencrypt (not related to this, just so I'd be on the latest version), then the AdAway_systemless_hosts_v2.zip, rebooted and installed the apk and let it run. Rebooted. Showing hosts location as /system32/etc/hosts as the OP says is a good thing, and both files mentioned are in their correct places per Root Browser. [emoji106]
Sent from my HTC 10 using XDA-Developers mobile app
Sorry that it doesn't completely match the thread here but I think my question could fit in here anyway.
Do I suggest correctly that with systemless root, systemless AdAway and the stock recovery OTAs should be fully usable? Since there's no other modification to /system then.
bmwbasti said:
Sorry that it doesn't completely match the thread here but I think my question could fit in here anyway.
Do I suggest correctly that with systemless root, systemless AdAway and the stock recovery OTAs should be fully usable? Since there's no other modification to /system then.
Click to expand...
Click to collapse
I believe that is correct. There hasn't been a new OTA for my phone yet so I can't verify. However, when I do the check for new software it tells me no new updates (as opposed to the message about the files system being corrupt). I believe Android Pay should also work. I have it installed and added a new card, but I haven't tested making a purchase yet.
Thanks for the guide.
My device is rooted, but I didn't found su folder in anywhere when I use Root Explorer with root access, does anyone tell me how to get su folder and make AdAway work?
Fix for AdAway.
matif525 said:
Thanks for the guide.
My device is rooted, but I didn't found su folder in anywhere when I use Root Explorer with root access, does anyone tell me how to get su folder and make AdAway work?
Click to expand...
Click to collapse
Your device may use su, & still not have an su folder (at all) that is used for hosts file (ie systemless root). Just do this..
Download... Terminal emulator.
https://play.google.com/store/apps/details?id=jackpal.androidterm
Open terminal
Then enter these commands.. "Quote"
su
mount -orw,remount /system
rm /system/etc/hosts
ln -s /data/data/hosts /system/etc/hosts
mount -orw,remount /system
Now open AdAway go to preferences and select option to " Target hosts file"
Select /data/data/hosts
Enjoy..
If you still have ads in apps do this!!!
githyanki said:
Open the 3 dot menu in adaway, chose log DNS request. Enable TCP dump.
Open the app with ads, when ad loads, go back to adaway, and open log.
Long press any entries and chose black list.
Profit
Click to expand...
Click to collapse
All credit where credit is due. I just shared what I read else where.
Read here for more details..
https://github.com/AdAway/AdAway/issues/770
&
http://forum.xda-developers.com/showthread.php?t=2190753&page=143#post68988079
There is a known issue in HTC devices involves S-off. If the above doesn't solve this for you message here I'll follow. Or pm me. I work wierd hours be patient.
Rom Maximus 3.0.0 ( Android 7 ).Any instruction don't works,adaway no blocked ads.
regarding su folder to move files to
FreydNot said:
About the only reason I root my phone is to install AdAway. I'd prefer to not modify the system partition to help make OTA's easier to get and to allow Android Pay to work. AdAway has a flashable .zip file that preps the hosts file to use the systemless root structure that comes along with SuperSU. Unfortunately, that script depends on being able to access the /data partition inside of TWRP which isn't going to happen any time soon on the HTC 10. Fortunately, it is easy for us to manually replicate what the flashable .zip is trying to do.
This isn't a detailed how-to, but more of a set of guidelines. Don't blame me if your phone explodes.
Root the phone with the latest SuperSU.
Download the AdAway_systemless_hosts_v2.zip file from the Unofficial AdAway thread.
Extract the files from inside the zip. We are only interested in two files in the support folder.
Connect the phone to your PC and turn on file transfer mode.
Copy "hosts" and "0000adaway.script" that you just extracted to the internal storage of your phone.
Use a program file Root Explorer to move "hosts" into /su/etc and move "0000adaway.script" into /su/su.d (this probably could have been done with ADB push, but I got permission errors when I tried it that way and I'm impatient and lazy).
Chmod 0755 /su/su.d/0000adaway.script (I used a root shell on the phone via ADB)
Install AdAway (I used the link in the Unofficial AdAway thread.)
Reboot the phone.
Run AdAway like normal. By default it should use /system/etc/hosts which is what you want.
If something doesn't work, figure out why and fix it. I'm happy to answer questions to the best of my ability.
Click to expand...
Click to collapse
Hi there, ive got a mate 8, not sure if this adblocker will work on it but i want to try it out anyway. Ive unzipped the file but which folder in su do i move the files to? screenshot of the folders i have in su