Since removing ads from browser and apps was one of the main reasons to root my DX I decided to make this tutorial. Problem is you can't just install AdAway (link) and run it because after a reboot you'll have to do it again. This method is keeping the ads away even after a reboot. Remember that you'll have to update AdAway-hosts files regularly.
All credits go to Yasir Javed Ansari. I only finetuned the method he described a little bit. Because his post is somewhere in another thread it seemed right to make a tutorial for it in the themes and apps section.
First of all you'll need a properly rooted DX with superuser 3.1.3 installed. See here for a zip to install superuser and busybox or here to download a pre-rooted 1.18 stock deodexed rom with superuser and busybux installed provided by infernal77. I'm using this rom on my DX and removed a lot of bloatware with Aroma (link) right after flashing the rom. Credits go to merovig for sharing info about flashable superuser/busybox-zip and Aroma and of course to infernal77 for providing his deodexed stock rom. Although it seems that this method shouldn't be necessary when using a deodexed rom I couldn't get it to work without using the command lines, so I decided to share it anyway.
In settings - power, uncheck 'fast boot'.
Install AdAway from Play Store. Run AdAway (don't download hosts files yet) and go to settings - preferences. Check 'allow redirections' and under 'target hosts file' select '/data/data/hosts'.
Reboot to recovery and then mount /system and mount /data.
While in recovery-mode connect the device to a PC and open a command prompt.
Type:
adb shell
cd system/etc
rm hosts
ln -s /data/data/hosts hosts
Disconnect the device from PC and reboot.
Now you can run AdAway: download files and apply ad blocking.
Done!
Nice one, added to Index.
@op, Good job.
Although my tutorial was word by word the same, apart from maybe few spelling mistakes. ;p
Above is required for Stock Rom which is rooted.
On custom and rooted Rom , you don't need to perform above steps as system is write permitted so running ad away normally works fine.
Regards
Yasir
Sent from my HTC Desire X
Hehe I know, the only thing I added was the /etc
Problem is that when I install for example infernals rooted stock deodexed rom, and then I install AdAway and hosts files, they don't survive a reboot. When I redirect the hosts file to /data/data/hosts AdAway states it can't create the symlink. That's why I still use your method even on a pre-rooted rom.
nightcrow said:
Hehe I know, the only thing I added was the /etc
Problem is that when I install for example infernals rooted stock deodexed rom, and then I install AdAway and hosts files, they don't survive a reboot. When I redirect the hosts file to /data/data/hosts AdAway states it can't create the symlink. That's why I still use your method even on a pre-rooted rom.
Click to expand...
Click to collapse
This symlink method(not mine) is present in ad away FAQs. So credit to the app team.
Sent from my HTC Desire X
Nice guide, first time I'm adfree, even after a reboot
did anyone get it working on desire x... mine still shows ads in apps...
I don't know, after all I'm an amateur, but the problem nightcrow described about how stuff goes back to stock after a reboot is something that happens a lot with the DX's - same thing with the bloatware. I had to remove the bloat apps from a rom.zip and flash that to avoid the problem. Seems to me there is some kind of security built in that goes beyond the norm. Otherwise I don't see why apps like Titanium work to remove apps (even after reboot) for example on most other phones, but not the DX.
Meherzad, I followed the instructions posted by nightcrow and it works for me ... try again, reboot and open an app you know normally has ads to check if it works.
Failed first time (forgot to uncheck fast boot:banghead. Reinstalled and did everything again, now works flawlesly.
ok.. working great......
nightcrow said:
Since removing ads from browser and apps was one of the main reasons to root my DX I decided to make this tutorial. Problem is you can't just install AdAway (link) and run it because after a reboot you'll have to do it again. This method is keeping the ads away even after a reboot. Remember that you'll have to update AdAway-hosts files regularly.
All credits go to Yasir Javed Ansari. I only finetuned the method he described a little bit. Because his post is somewhere in another thread it seemed right to make a tutorial for it in the themes and apps section.
First of all you'll need a properly rooted DX with superuser 3.1.3 installed. See here for a zip to install superuser and busybox or here to download a pre-rooted 1.18 stock deodexed rom with superuser and busybux installed provided by infernal77. I'm using this rom on my DX and removed a lot of bloatware with Aroma (link) right after flashing the rom. Credits go to merovig for sharing info about flashable superuser/busybox-zip and Aroma and of course to infernal77 for providing his deodexed stock rom. Although it seems that this method shouldn't be necessary when using a deodexed rom I couldn't get it to work without using the command lines, so I decided to share it anyway.
In settings - power, uncheck 'fast boot'.
Install AdAway from Play Store. Run AdAway (don't download hosts files yet) and go to settings - preferences. Check 'allow redirections' and under 'target hosts file' select '/data/data/hosts'.
Reboot to recovery and then mount /system and mount /data.
While in recovery-mode connect the device to a PC and open a command prompt.
Type:
adb shell
cd system/etc
rm hosts
ln -s /data/data/hosts hosts
Disconnect the device from PC and reboot.
Now you can run AdAway: download files and apply ad blocking.
Done!
Click to expand...
Click to collapse
have no idea how to write in command prompt
umo4u said:
have no idea how to write in command prompt
Click to expand...
Click to collapse
Windows button+R>Type cmd>enter
It doesn´t works for me...It may wont work because i have superuser v3.2?
Might be but I'm not sure. I'm on 3.1.3 and it works fine. Although getting ADB to work in twrp recovery is a bit of a struggle for now.
What exactly doesn't work for you?
nightcrow said:
Might be but I'm not sure. I'm on 3.1.3 and it works fine. Although getting ADB to work in twrp recovery is a bit of a struggle for now.
What exactly doesn't work for you?
Click to expand...
Click to collapse
you can do same in advanced-> execute command (or maybe shell - do not remember the exact naming)
adb was not working for me, too.
nightcrow said:
Might be but I'm not sure. I'm on 3.1.3 and it works fine. Although getting ADB to work in twrp recovery is a bit of a struggle for now.
What exactly doesn't work for you?
Click to expand...
Click to collapse
Why do you need ADB when you have TERMINAL in twrp. Just wondering
Anyhow, ADB will be fixed soon
Thanks for the tutorial works great with Superuser 3.2. Just to clarify something, should I leave "fast boot" mode off now?
Michael
michpan said:
Thanks for the tutorial works great with Superuser 3.2. Just to clarify something, should I leave "fast boot" mode off now?
Michael
Click to expand...
Click to collapse
I think you can turn it on.
If you'll not access recovery... when you need recovery, turn fast boot off...
Sent from my hTC branded muffin
Related
J Ok so in my never ending struggle against the Evil Eclair/T-Mo/HTC NAND Protection and the Futility of Trying to flash a ROM With the "Supposed AndRoot QuIck Root Method" As well as a fine point from Nbetcher that the Engineering build must be flashed because Android has NAND protection while running. I have devised my own "No PC ROOT Method!!!"
Required Files (Tested For MT3G SLIDE Latest OTA Unrooted Stock)
1.Download Androot From Location of Choosing (I'm Using Version 1.6.2)
2.Download ESPRIMG.zip (ENG build)
3.Download SlideEng-Package.zip
4.Download Custom Rom Of Your Choosing(Mine Is CM 6.1.1 Stable)
5.Download Android Terminal Emulator(From Market)
6.Download Root Explorer Android (Requires Root) (From Market Or Some Place Online)
7.Download File Explorer (Dev:Adao Team)(From Android Market)
8.Download Latest Clockwork Recovery(I Used 2.5.0.1)
*Updated* 1/09/2011 (Thanks to dbzfanatic for links)
dbzfanatic said:
Universal Androot http://forum.xda-developers.com/attachment.php?attachmentid=391774&d=1283202114
ESPRIMG.zip www.4shared.com/file/OsmF_ZD7/ESPRIMG.html
SlideEng-Package.zip http://www.4shared.com/file/sz0VO2TL/SlideEng-package.html
Cyanogen 6.1.1 Stable http://mirror.teamdouche.net/get/espresso/update-cm-6.1.1-Slide-signed.zip
Clockwork Recovery (may be old but will work) http://www.4shared.com/file/KzYHr4U_/update.html
Now people can stop *****ing about links. Everything else can be found on the android market.
Click to expand...
Click to collapse
Please Note I Am NOT The DEV Behind these Apps nor am I Resposible For Any Damages You May Incur To Your Device or Warranty by using this Method! Also Before anyone says I repped someone off remeber I accidentally discovered this using 2 failed methods because they essentially cancel each other out.(The Latter Nbetchers works just not after the AndRoot One)!!!
So...
1st Download/Install all needed files from market( File Manager Android Terminal Emulator)
2nd Download all zip images, Recoveries, Roms, apps from phone browser Directly To SD ROOT(Google em until I get links up on Dev Forum)
3rd. Unzip SlideEng-Package.zip To Root using File Manager or Other Zip Program for android(Andro-Zip Works Well)
4th Change Name of Clockwork to Update.zip(Case Sensative)
5th Install AndRoot And Run Root Me With Install Su & Temp Root/Unroot After Reboot Selected(Or Else You Will Boot Loop)
6th Install And Run Root Explorer then Copy and paste flash_img and mtd0.img to /data/local on android device by multi-select copy then RM R/W in program in upper left on data local folder.
7th IMPORTANT!!! Long Press and hold each copied file and set permissions to allow read and write on both user and the lowest option (I Think Dev or system)
8th Run Android Terminal Emulator and type the following commands verbatim spaces included Pressing enter after each line($ n # will be there provided you follwed all steps if not go back to androot and root again):
$ su
# cd /data/local
# chmod 04755 flash_image
# ./flash_image misc mtd0.img
Now power off and reboot using VOL-DOWN + POWER
It'll reboot into the HBoot Screen and ask if you want to Check ESPRIMG.zip after Verifying it will ask you to flash Select Yes (VOL-UP) And Wait DO NOT POWER DOWN OR TAKE OUT BATTERY!!!
Once its Completed it will ask you to Reboot select no Instead and Go To Recovery
Now Select APPLY Update.zip to flash CLOCKWORK RECOVERY YAY!!! :-D Now We Can Flash a Custom Rom With Root and Even Go As Far As S-OFF!!! But Please Be Sure Its Already On Your Micro SD...
Select Wipe Data Factory Reset by Scrolling with VOL- UP/DOWN or Track Pad and Use Power/Trackpad TO Select.
Now Use Install Zip from SD Card to Install Custom Rom(Flash GApps Second if downloaded and desired if using CM Mod 6.1.1) Now Reboot And Enjoy!!! If you Wanna Flash Anything Else Use Rom Manager From Market and Som Custom Roms to Boot into Clockwork!!! Thanks to all the Devs and their tools and immense knowledge for Making this Possible! Thanks To All The ROM Chefs Too!!!
DeezyFn'Baby said:
6th Install And Run Root Explorer then Copy and paste flash_img and mtd0.img to /data/local on android device by multi-select copy then RM R/W in program in upper left on data local folder
Click to expand...
Click to collapse
Edit:nvm, ill try it when i get my replacement slide.
I don't think the slide needs S-OFF to write to data but I do think it needs root beforehand, or at least shell root.
just to make it easier to anyone flashing this, i would put links to DL's of those files. first thing i noticed when i read. put me off to this method.
btw, this is me trying to help, not ripping on you
dbzfanatic said:
I don't think the slide needs S-OFF to write to data but I do think it needs root beforehand, or at least shell root.
Click to expand...
Click to collapse
I don't think so? If /data couldn't be written to without root or s-off, how would people install apps who never rooted their phones? Where is the system data stored and modified? /data is fully modifiable I'm pretty sure.
I'm willing to admit I could be wrong on that but I thought apps were installed in /data because it was the system calling the package installer not the user.
dbzfanatic said:
I'm willing to admit I could be wrong on that but I thought apps were installed in /data because it was the system calling the package installer not the user.
Click to expand...
Click to collapse
In terms of read/write permissions, the system has the same permissions as the user. The system can't write to /system if the user can't, and vice versa. /data and /cache have no nand protection
MusicMan374 said:
In terms of read/write permissions, the system has the same permissions as the user. The system can't write to /system if the user can't, and vice versa. /data and /cache have no nand protection
Click to expand...
Click to collapse
In the post I did add if I had the time I would post links if not ill do it later to whomever above stated their statement. If you don't want to "Try" it don't and don't comment. It was an accident I found it and I have since replicated my process on 3 slides and it works. The Reason it does is because gaining temporary root inside android even without gaining full being blocked by nand or S-Off can be can be used to modify the permissions of system files while the memory is running tho not the actual NAND itself which I believe S-OFF does... So when I said 6th mount the drive as R/W in root explorer there is an option to remount the drive R/W to allow you to long press the items in that folder and change their permissions then I said unmount to save the permission fix that's what the Temp Root Gained from AndRoot Does.... Now I'm gonna try and update my Original post with links for people who want an esier time doing this like I would have liked and for the. Sarcastic ones so then you can just press the Thumbs Up button ok?
DeezyFn'Baby said:
In the post I did add if I had the time I would post links if not ill do it later to whomever above stated their statement. If you don't want to "Try" it don't and don't comment. It was an accident I found it and I have since replicated my process on 3 slides and it works. The Reason it does is because gaining temporary root inside android even without gaining full being blocked by nand or S-Off can be can be used to modify the permissions of system files while the memory is running tho not the actual NAND itself which I believe S-OFF does... So when I said 6th mount the drive as R/W in root explorer there is an option to remount the drive R/W to allow you to long press the items in that folder and change their permissions then I said unmount to save the permission fix that's what the Temp Root Gained from AndRoot Does.... Now I'm gonna try and update my Original post with links for people who want an esier time doing this like I would have liked and for the. Sarcastic ones so then you can just press the Thumbs Up button ok?
Click to expand...
Click to collapse
Your instructions don't have anything to do with /system I don't know what you are babbling about. I'm not disproving your root method, I was just trying to explain that /data is not nand protected. /system IS nand protected, and without s-off or a r/w overlay you wouldn't even be able to modify the permissions of files in /system, but since your root method has to do with /data it works.
MusicMan374 said:
Your instructions don't have anything to do with /system I don't know what you are babbling about. I'm not disproving your root method, I was just trying to explain that /data is not nand protected. /system IS nand protected, and without s-off or a r/w overlay you wouldn't even be able to modify the permissions of files in /system, but since your root method has to do with /data it works.
Click to expand...
Click to collapse
I'm not babbling I was referring to the first reply but ur probably right about the sys files as I didn't mess with them. But I did obtain root anway all of the files can easily be found by doing a search on the XDA forums and ill add the links when I get to a pc doing this from the android browser is painful...
DeezyFn'Baby said:
I'm not babbling I was referring to the first reply but ur probably right about the sys files as I didn't mess with them. But I did obtain root anway all of the files can easily be found by doing a search on the XDA forums and ill add the links when I get to a pc doing this from the android browser is painful...
Click to expand...
Click to collapse
Yeah, that's why you don't need s off for this to work, which others were saying
Sent from my T-Mobile myTouch 3G Slide
Thanks for posting this method! It worked flawlessly! Had the files and rooted it in about a half hour. Thanks again for this nice work around!
Sent from my ROOTED myTouch 3G Slide using the XDA App
This would make it easier for new folks if you had links next to the items needed for this... you can't just tell others they need this and that with at least a link on where to find it or download it... like having me find a treasure chest without clues or a map just saying haha. good guide though and yes I did read you'll be adding links soon =p
Agreed links would help but if people google the files he mentioned they are all easy to find. Even new folks know how to google =D
Sent from my ROOTED myTouch 3G Slide using the XDA App
Universal Androot http://forum.xda-developers.com/attachment.php?attachmentid=391774&d=1283202114
ESPRIMG.zip www.4shared.com/file/OsmF_ZD7/ESPRIMG.html
SlideEng-Package.zip http://www.4shared.com/file/sz0VO2TL/SlideEng-package.html
Cyanogen 6.1.1 Stable http://mirror.teamdouche.net/get/espresso/update-cm-6.1.1-Slide-signed.zip
Clockwork Recovery (may be old but will work) http://www.4shared.com/file/KzYHr4U_/update.html
Now people can stop *****ing about links. Everything else can be found on the android market.
dbzfanatic said:
Universal Androot http://forum.xda-developers.com/attachment.php?attachmentid=391774&d=1283202114
ESPRIMG.zip www.4shared.com/file/OsmF_ZD7/ESPRIMG.html
SlideEng-Package.zip http://www.4shared.com/file/sz0VO2TL/SlideEng-package.html
Cyanogen 6.1.1 Stable http://mirror.teamdouche.net/get/espresso/update-cm-6.1.1-Slide-signed.zip
Clockwork Recovery (may be old but will work) http://www.4shared.com/file/KzYHr4U_/update.html
Now people can stop *****ing about links. Everything else can be found on the android market.
Click to expand...
Click to collapse
The only thing about 4shared is that it doesn't work right on the stock HTC web browser, since javascript is kinda glitchy on that one. Works fine on froyo/cm6.1.1 with the aosp browser, but for a TRUE pcless method you need direct or mediafire links I think.
I post links because everyone *****es and yet someone still *****es. Those aren't my uploads, I simply posted them so people would stop *****ing. I personally haven't had issues with 4shared even with the stock browser back before I rooted my phone. If you want to reupload them to another hosting site be my guest but like I said, they aren't my uploads.
Stop whining
Here are some direct links for those who complain about the 4Share site.
Oh, and Ill put a gapps link up in thar too. It has the new market, and it works as long as you don't install anything until it finishes restoring. At least it did for me.
That Clockwork link is broken. I'm just sayin' :3
ESPRIMG.zip: http://db.tt/kEvPIyu
SlideEng-package: http://db.tt/n57yN2a
Gapps: http://db.tt/L0SNLhj
EDIT: Clockwork on next page.
supermario12312 said:
Here are some direct links for those who complain about the 4Share site.
Oh, and Ill put a gapps link up in thar too. It has the new market, and it works as long as you don't install anything until it finishes restoring. At least it did for me.
That Clockwork link is broken. I'm just sayin' :3
ESPRIMG.zip: http://db.tt/kEvPIyu
SlideEng-package: http://db.tt/n57yN2a
Gapps: http://db.tt/L0SNLhj
Click to expand...
Click to collapse
thank you for that, not only if that direct link better there mate.. but man the download speed is better ahaha... I already have root but I'm rooting a friends phone ;P then soon a warranty exchange phone for me.
Once I reach recovery... it just sits there with no options or anything...
Thanks goes to #TeamWin for Temp Root
This is For Windows only, if you wish to make it work for linux or mac help your self...
Remember, This is still a Temp Root & any Changes made will be Rest back to stock on a Reboot
It's stable & works 100%
I Personally have not lost Root with this new Method
Q. I thought RW was Fixed?
A. Caused by Deleting an apk / file that was already deleted. Journaling shows it still there!
Keep Track of what you delete, as trying to delete something off system that you alread di hangs the /system into RO state.
Before Using!!HTC Sync Must be Turned OFF
Put the Phone into Charge Mode only ( Not Disk Drive )
USB Debugging Must be Turned on
What's Fixed:
Revamped due to new Method:
~ Superuser Apps now Function
~ If you Lose Root, all you have to do is Open terminal & type SU then type fixit! > No More Rebooting & running the exploit again for R/W on system to get Root back in place
~ Fixed R/O Bug!!
~ R/W is now Forced
~ /system is fully editable now! until reboot that is.
~ Busybox is installed to /vendor/bin
~ hex Edited libext4
~ hex edited libfuse.so
~~ This is the Last Update due to it working & Stable ~~
Download for RW HTC Sensation 4G:
````````````````````````````````````````````````````````````````````````````````````````````
Download for RW HTC Evo 3D:
````````````````````````````````````````````````````````````````````````````````````````````
Download for RW HTC Flyer 16GB/32GB:
````````````````````````````````````````````````````````````````````````````````````````````
Download for RW HTC Evo View:
Q. Is this permanent?
A. no, it's a temp root method..
Q. Will I lose SU Access at some point while running the OS?
A. You might, but open terminal & type fixit to get root back!.
Q. What about apps that need a reboot to use superuser?
A. Use Fast Reboot form the market for app that need a reboot..
Q. Can I push & remove items to system & will it work?
A. Yes, but all changes are reset on a reboot.
Once Downloaded, Unzip & double click on the Run_ME_fre3vo_Root.bat File & Enjoy long lasting Root!
OLD NEWS:
Everyone knows that currently with any temp root, you still lose links to the SU Binary & Busybox links, it's just a matter of time before it happens!!
So after digging around somewhat I found an over sight that HTC might use later for system updates via /vendor/bin, who knows at this point though... Anyways, after amount of time the SU Binary along with busybox links if be in system/bin or /system/xbin gets deleted / removed..
Now, what I did was enable the $Path to /vendor/bin which is in the Sensation export PATH..
Any Calls made from this point either be SU or Busybox don't get deleted nor touched from any App requesting the SU Binary!! I've tested this with alot of apps & the Root sticks in place..
Other than Reboot, it might as well be a Perma-Temp-Root!!
Downloading now!!! Can't wait to test it!
***EDIT***
Rooted perfectly, opened and closed Titanium Backup several times with no force closes or loss of su, Barnacle is perfect, Wireless tether is granted su but the kernel doesn't support it, screenshot gained su also but the screenshots were smeared colors. Drocap2 takes perfect screenies though. Gonna try a few more root apps before bed and play some more when I wake up to verify it lasts.
going to try this now!
Ran the script and no root
script stays on
daemon started successfully :/
eugene373 said:
Thanks goes to #TeamWin for Temp Root!!!
Everyone knows that currently with any temp root, you still lose links to the SU Binary & Busybox links, it's just a matter of time before it happens!!
So after digging around somewhat I found an over sight that HTC might use later for system updates via /vendor/bin, who knows at this point though... Anyways, after amount of time the SU Binary along with busybox links if be in system/bin or /system/xbin gets deleted / removed..
Now, what I did was enable the $Path to /vendor/bin which is in the Sensation & Evo 3D export PATH..
Any Calls made from this point either be SU or Busybox don't get deleted nor touched from any App requesting the SU Binary!! I've tested this with alot of apps & the Root sticks in place..
Other than Reboot, it might as well be a Perma-Temp-Root!!
This is For Windows only, if you wish to make it work for linux or mac help your self...
If you have trouble with the Superuser.apk, uninstall first & reboot then run the .bat file again..
What is installed?
Busybox w/ symlinks
Superuser.apk
SU Binary
Fre3vo
sqlite3
What's Removed?
slackerradio.apk
TMOUS_Navigator.apk
Transfer-pyramid-8.30.0.26-S30.apk
Protips.apk
IdleScreen_Stock.apk
HtcTipWidget.apk
com.htc.TrendsWidget.apk
com.mobitv.client.tmobiletvhd.apk
FusionStockWidget.apk
Stock.apk
So without further ado, the link!
http://www.multiupload.com/LBEYIFVD58
Once Downloaded, Unzip & double click on the Run_ME_fre3vo_Root.bat File & Enjoy long lasting Root!
Last edited by Eugene373; Today at 05:51 AM.
Click to expand...
Click to collapse
Is there any chance u can edit the script or tell me how to edit it so it doesn't remove anything. Thanks.
perfect works great!!! Managed to restore TB! Will try out wifi tethering right now and other su required apps! Thank you! <3
I guess I don't understand.
How is removing anything from /system/app gonna stick?
This worked perfect for me. No problems with it. Wifi tether won't work for me, but barnacle tether works perfectly. Drocap2 is taking perfect screen shots for me as well, where as before the images would be all distorted and what not.
Made some changes to the .bat since I don't necessarily want to disable all of that yet, but it works, this is the longest superuser has worked for me so far on the EVO 3D.
k2buckley said:
This worked perfect for me. No problems with it. Wifi tether won't work for me, but barnacle tether works perfectly. Drocap2 is taking perfect screen shots for me as well, where as before the images would be all distorted and what not.
Click to expand...
Click to collapse
How'd you get Barnacle to work?
EDIT:
Sorry my tablet doesn't read Ad-Hoc >_>
Is anybody able to root the E3D with this method? I tried twice and it failed both times. I will do again by restart my pc and E3D.
urcboss07 said:
Is anybody able to root the E3D with this method? I tried twice and it failed both times. I will do again by restart my pc and E3D.
Click to expand...
Click to collapse
Yeah....First try.
nabbed said:
I guess I don't understand.
How is removing anything from /system/app gonna stick?
Click to expand...
Click to collapse
It won't stick, but after you reboot you run the batch program again and the apps are removed again until your next reboot.
hockeyfamily737 said:
It won't stick, but after you reboot you run the batch program again and the apps are removed again until your next reboot.
Click to expand...
Click to collapse
So, it will not stick as said, right?
Tiffany84 said:
Is there any chance u can edit the script or tell me how to edit it so it doesn't remove anything. Thanks.
Click to expand...
Click to collapse
a .bat file is just a text document that is executed in command prompt. If you are familiar with cmd just open the file in notepad, delete any commands you don't want executed, save.
urcboss07 said:
So, it will not stick as said, right?
Click to expand...
Click to collapse
Not through a full reboot....no you will have to run the batch file again (even says so in the OP). However, the other root methods would crash periodically even without a reboot or would last but not give you access to the majority of your root apps. This is the closest yet to a feasible root solution.
mine doesnt get past daemon started successfully i have usb debugging on
so if i downloaded and installed some apps that require root,
and i reboot, what happens to them ?
they will work after running the bat file again ?
or they will have to be installed again to work properly ?
thanks !
EDIT: i haven't done my due diligence (searching and reading)
but it's 5 am so i'll ask ...
what works for screen capture and for wireless tethering ?
lowetax said:
so if i downloaded and installed some apps that require root,
and i reboot, what happens to them ?
they will work after running the bat file again ?
or they will have to be installed again to work properly ?
thanks !
Click to expand...
Click to collapse
They will work after running the .bat file again. You shouldn't need to uninstall and reinstall them. Super User may need to be uninstalled before running the .bat file again, if it gives you any force closes.
Sent from my PG86100 using XDA App
DISCLAIMER : You attempt the following at your own risk !
I'm not responsible if your phone blows up, bricks, you travel back in time or go bald or something!
Background :
I have the MT2-L05 Mate 2 from China.
When I received my Mate 2 last Thursday, the phone was on 4.2.2
After much hunting and downloading and flashing of ROMS, I managed to finally update to 4.4.2 KitKat.
Great ! I was happy. But I didn't have root access.
After trying and failing to use the various bootloader unlock tools on these forums, I Emailed Huawei, and politely asked them if I could have the 16 digit code for my Mate 2. An hour later an Email arrived with my bootloader unlock code, so I fastbooted, used the code and unlocked the Bootloader.....Cool ! Thanks Huawei, great customer service.
I then went to root my phone, and here the problems started. I tried at least 20 different Root tools, both via phone and over the pc, but no joy.
Nothing worked ! Vroot, Kingoroot, Towelroot, srs root, root genius 1.8.7, etc they all failed.
I was at the point of giving up, when I found a Chinese version of rootgenius 2.0.1.3......I ran it via pc........and Success ! I was finally rooted.
Supersu was installed, the binaries updated fine and all was good with the world. I tried wakelock detector first ( Yeah, I know, I REALLY need more battery life from the Mate 2 ! ), and Supersu asked for permission and it worked no problem.
I then tried to install adaway, and then I ran into problems, I was unable to edit my hosts file....ummm...odd. OK, then I tried to install xposed......Impossible to install.
I then read on these forums to edit build.prop and change a simple setting to get xposed running.......ok, no problem, yet when I edited my build.prop file, it would NEVER EVER save the edits. Weird? what's going on?.......after much searching and much reading I finally found the problem.................
Root Genius 2.0.1.3 :
http://www.shuame.com/root/
The Problem :
The 4.4.2 update adds a file to your System folder called :
set_immutable.list
this file contains :
Code:
/system/bin
/system/build.prop
/system/etc
/system/fonts
/system/framework
/system/isp.bin
/system/lib
/system/ons.bin
/system/usr
/system/vendor
/system/xbin
/system/app/HwLauncher6.apk
/system/app/HwLauncher6.odex
/system/app/systemUI.apk
/system/app/systemUI.odex
Any location listed above is IMPOSSIBE to mount as rw. Every file explorer or emulator you try will tell you it is rw, but it's not.
It's locked down completely...................and it's REALLY annoying.
This is why I could never edit my build.prop or Install Adaway etc..................
But I found a solution...... ( I think ! )..........
The Solution :
I spent the afternoon at work using google translate to find a fix for my problem and found a post from a guy called :
**** wire His Royal Highness Prince czx ( I cannot post the first 4 letters as it will probably be banned....It must be a Google translate error but it made me laugh ! )
His guide never worked for me until I made a few edits and added STEP 4. Then I got it to work.
The Solution :
1, First Root your Phone ( I suggest trying Root Genius 2.0.1.3 from my first post )
2, install busybox (I suggest BusyBox ( Stericson ) as I couldn't get this to work with the Jrummy BusyBox installer )
3, Install Rom Toolbox Pro ( I know it's payware and I tried other programs, but this is the only one that worked for me. I had already purchased ages ago. The free version may contain the following tools too, but I genuinely don't know )
4, open Scripter from Rom Toolbox pro and click " Mount System R/W "
5, open Terminal Emulator from Rom Toolbox Pro
Type: su then press enter
Type: mount -o rw, remount / system then press enter
Type: cd system then press enter
Type: chattr -R -i * then press enter
(On step 5 there is a space between remount forward slash and system and also between i and *)
6, Leave Terminal Emulator open, Hit your Home Button
7, then delete the file :system / set_immutable.list with Root Explorer. Other File managers with root access may work, I haven't tried
If you can not delete it, the above steps haven't worked, I can only suggest you try from step 4 after rebooting your phone.
If you are successful and manage to delete the set_immutable.list file then reboot your phone.
Job Done !
You now have full Root Access.
This has been tested by myself on my MT2-L05, it should work on ALL China Variants and presumably on the US MT2-L03 if this file is included in a 4.4.2 update, but I obviously cannot guarantee this.
I'm also curious as to whether anyone thinks this has left my phone open to exploits by the deleting this file....? Remember, if I have done something stupid by doing this, then so will you if you follow the above!
All I know is Xposed has installed perfectly after finally being able to edit my build.prop file and Adaway is running like a charm.
Feedback very welcome.
4L0M said:
The Solution :
Snip
5, open Terminal Emulator from Rom Toolbox Pro
Type: su then press enter
Type: mount -o rw, remount / system then press enter
Type: cd system then press enter
Type: chattr -R -i * then press enter
(On step 5 there is a space between remount forward slash and system and also between i and *)
Snip
Click to expand...
Click to collapse
I followed your guide, the part I bolded didn't seem to work for me, but after a few attempts I just kept going with the rest of the guide and I was still able to delete the file at the end of the day Thank you so much! I always felt like the root I had with 4.2 was kind of a pseudo root since I was limited by my root access, this is exactly what I needed!
I manage to get root and delete that file. Hooray and thanks! But after editing the build.prop, I still can't get xposed to install. I keep getting this error on the install screen.
scpion said:
I manage to get root and delete that file. Hooray and thanks! But after editing the build.prop, I still can't get xposed to install. I keep getting this error on the install screen.
Click to expand...
Click to collapse
Install xposed 2.5.1, it's the safest option for now and you will not get this error message.
I haven't tried too many xposed apps yet, but wanam works if you want circle battery etc
Experimental features of Greenify work too.
Gravity box Kitkat will not run properly for me.. I suggest you do not attempt to install it at the moment.
Let me know if you find anymore cool xposed modules to try!
4L0M said:
Install xposed 2.5.1, it's the safest option for now and you will not get this error message.
I haven't tried too many xposed apps yet, but wanam works if you want circle battery etc
Experimental features of Greenify work too.
Gravity box Kitkat will not run properly for me.. I suggest you do not attempt to install it at the moment.
Let me know if you find anymore cool xposed modules to try!
Click to expand...
Click to collapse
Thanks dude. Btw does your device support Google search by swiping up from home?
scpion said:
I manage to get root and delete that file. Hooray and thanks! But after editing the build.prop, I still can't get xposed to install. I keep getting this error on the install screen.
Click to expand...
Click to collapse
Same issue for me
janrck said:
Same issue for me
Click to expand...
Click to collapse
Install xposed 2.5.1, it's the safest option for now and you will not get this error message.
Cool xposed apps for 2.5.1 :
wanam kit : adds circle battery, expanded notifications, 4-way reboot menu etc etc
Android L Navbar : adds Android L navbar and Android L shapes Navbar
Both work flawlessly for me and have NEVER crashed once.
Hi, I followed your steps but in the step 5, when i type this : mount -o rw, remount / system it doesnt work.
4L0M said:
DISCLAIMER : You attempt the following at your own risk !
Nothing worked ! Vroot, Kingoroot, Towelroot, srs root, root genius 1.8.7, etc they all failed.
I was at the point of giving up, when I found a Chinese version of rootgenius 2.0.1.3......I ran it via pc........and Success ! I was finally rooted.
Supersu was installed, the binaries updated fine
I then tried to install adaway, and then I ran into problems, I was unable to edit my hosts file....ummm...odd. OK, then I tried to install xposed......Impossible to install.
Click to expand...
Click to collapse
I then read on these forums to edit build.prop and change a simple setting to get xposed running.......ok, no problem, yet when I edited my build.prop file, it would NEVER EVER save the edits. Weird? what's going on?.......after much searching and much reading I finally found the problem.................
/QUOTE]
How was SU installed if you had no rw privs?
vroot, kingroot, kingoroot, kinguser, srs root and rootgenius were created for a select few... it was a side effect of massive social engineering via the internet that they'd leak to so many others who weren't the target.
magicpromise said:
I then read on these forums to edit build.prop and change a simple setting to get xposed running.......ok, no problem, yet when I edited my build.prop file, it would NEVER EVER save the edits. Weird? what's going on?.......after much searching and much reading I finally found the problem.................
/QUOTE]
How was SU installed if you had no rw privs?
vroot, kingroot, kingoroot, kinguser, srs root and rootgenius were created for a select few... it was a side effect of massive social engineering via the internet that they'd leak to so many others who weren't the target.
Click to expand...
Click to collapse
I'm guessing because I could write rw to system folder. Set-immutable-list blocks folders inside system folder, not the basic system folder itself. ie/ system/xbin or system/etc they are blocked. /system on its own isn't.
4L0M said:
I'm guessing because I could write rw to system folder. Set-immutable-list blocks folders inside system folder, not the basic system folder itself. ie/ system/xbin or system/etc they are blocked. /system on its own isn't.
Click to expand...
Click to collapse
yes, and the instructions worked great.
i made a script with it in totalrom and set it to load on boot along with total rom itself to keep a strangle hold on the permissions.
magicpromise said:
yes, and the instructions worked great.
i made a script with it in totalrom and set it to load on boot along with total rom itself to keep a strangle hold on the permissions.
Click to expand...
Click to collapse
Can you please upload the script you made?
You'll make things easy for me, 'cause commands in terminal don't seem to work in my case.
Thank's !
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.
Guys,
I made a post a couple of days ago over on the 5x forums: http://forum.xda-developers.com/nexus-5x/general/passing-safetynet-root-t3307659. With this permissions fix I have Android Pay working without having to enable/disable root in the SuperUser app. Hoping it will work on 6p as well.
Anyone willing to give this a try on the 6p? You would need a stock ROM (or possibly another ROM that previously worked prior to Google's recent change that broke it) with systemless root installed (I'm using 2.67). Basically all you need to do is:
-Run "adb shell"
-From the shell run "su"
-On the # prompt run "chmod 751 /su/bin/"
So far this has worked for me and a couple of others on the 5x (both adding cards and making purchases). Let me know if anyone can confirm that this works on the 6p.
jgummeson said:
Guys,
I made a post a couple of days ago over on the 5x forums: http://forum.xda-developers.com/nexus-5x/general/passing-safetynet-root-t3307659. With this permissions fix I have Android Pay working without having to enable/disable root in the SuperUser app. Hoping it will work on 6p as well.
Anyone willing to give this a try on the 6p? You would need a stock ROM (or possibly another ROM that previously worked prior to Google's recent change that broke it) with systemless root installed (I'm using 2.67). Basically all you need to do is:
-Run "adb shell"
-From the shell run "su"
-On the # prompt run "chmod 751 /su/bin/"
So far this has worked for me and a couple of others on the 5x (both adding cards and making purchases). Let me know if anyone can confirm that this works on the 6p.
Click to expand...
Click to collapse
I just did it with Root Explorer. I changed the permissions for the /su/bin folder to 751. SafetyNet checks are passing now, but I haven't actually tried to purchase anything.
Worked on pure nexus after setting the permissions as suggested.
yep, purenexus, systemless, updated via terminal emu, works fine as of right now.
Worked with Chroma Rom using Root Explorer to change permissions. SafetyNet checks pass. Haven't set up AP yet . Will try that tomorrow.
Worked for me. Was able to pay for groceries.
Not working for me, used skipsoft toolkit to install systemless root.
Edit: Figured it out, still had the xbin_bind folder. Made a zip backup of it and deleted the original, safetynet passes now.
I've been on Pure Nexus 1/09 build with systemless SuperSU 1.61. Never had Android Pay working.
Without doing a clean install,
flashed busybox in TWRP.
Reboot
Made the permission changes using Root Browser.
Reboot
SafetyNet passes.
Installed Android Pay, added card.
Used on soda machine.
PROFIT!!!
Thank you OP for find!
Sent from my Nexus 6P using Tapatalk
i called google and they said it might actually be a syncing issue and that removing the card completely from your account (login web browser and account settings then remove card).
Se7eN43 said:
I've been on Pure Nexus 1/09 build with systemless SuperSU 1.61. Never had Android Pay working.
Without doing a clean install,
flashed busybox in TWRP.
Reboot
Made the permission changes using Root Browser.
SafetyNet passes.
Installed Android Pay, added card.
Used on soda machine.
PROFIT!!!
Thank you OP for find!
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I disabled SuperSU and followed directions. AP accepted my credit card and is set up. Do I leave SuperSU disabled, or can I re-enable?
Odd, no matter what I do, including disabling SuperSU, it doesn't work. Only if I full unroot. Setup is stock OS on Nexus 6P, on the latest 6.0.1 "Q" release. Set permissions to 751...no go. Even tried unrooting, reinstalling the OS, re-rooting, and setting permissions. No dice.
allen099 said:
Odd, no matter what I do, including disabling SuperSU, it doesn't work. Only if I full unroot. Setup is stock OS on Nexus 6P, on the latest 6.0.1 "Q" release. Set permissions to 751...no go. Even tried unrooting, reinstalling the OS, re-rooting, and setting permissions. No dice.
Click to expand...
Click to collapse
Did you delete the /su/xbin_bind folder?
synnyster said:
Did you delete the /su/xbin_bind folder?
Click to expand...
Click to collapse
I did not. I must have missed that step.
EDIT: When I do that, root is no longer detected. The SafetyNet turned green, but Titanium Backup said no root. Sorry, and thanks for the assistance. Any other suggestions?
Are you sure you have systemless root?
100%. I just reinstalled 2.67 via TWRP. I've got it back now. What would you recommend I do? chmod 751 /su/bin/ and remove the xbin_bind folder again? I'm reading on reddit about moving it and symlinking. How were you able to successfully do it? Thanks again!
The contents of xbin_bind are: dexdump, su, wlutil
If deleting that folder also deletes su, then it makes sense as to why root is gone.
allen099 said:
Odd, no matter what I do, including disabling SuperSU, it doesn't work. Only if I full unroot. Setup is stock OS on Nexus 6P, on the latest 6.0.1 "Q" release. Set permissions to 751...no go. Even tried unrooting, reinstalling the OS, re-rooting, and setting permissions. No dice.
Click to expand...
Click to collapse
allen099 said:
100%. I just reinstalled 2.67 via TWRP. I've got it back now. What would you recommend I do? chmod 751 /su/bin/ and remove the xbin_bind folder again? I'm reading on reddit about moving it and symlinking. How were you able to successfully do it? Thanks again!
The contents of xbin_bind are: dexdump, su, wlutil
If deleting that folder also deletes su, then it makes sense as to why root is gone.
Click to expand...
Click to collapse
I'm systemless root with SuperSU 2.66. I deleted xbin_binds after I was rooted. All I did was chmod 751 (I did the same thing via ES File Explorer) and AP works for me.
synnyster said:
I'm systemless root with SuperSU 2.66. I deleted xbin_binds after I was rooted. All I did was chmod 751 (I did the same thing via ES File Explorer) and AP works for me.
Click to expand...
Click to collapse
I'll try again now. Using root explorer. Did you set all files inside of /su/bin to 751? Or just the folder itself.
EDIT: It worked this time! Thanks very much!!
allen099 said:
I'll try again now. Using root explorer. Did you set all files inside of /su/bin to 751? Or just the folder itself.
EDIT: It worked this time! Thanks very much!!
Click to expand...
Click to collapse
Woohoo!
Wow this is amazing. I just made my first android pay purchase on a vending machine. Thanks for finding this method!
Just wish google won't take it from us again though.
For those who are confused, here are my steps for using Android Pay while rooted.
1. I reset my phone to factory defaults by installing all original software.
2. Unlocked the boot loader.
3. Installed TWRP, but kept it read only.
4. Installed Beta Super User 2.67
5. Through Android terminal after entering su and allowing terminal emulator root access:
6. rm -r /su/xbin_bind
7. chmod 751 /su/bin
Android Pay works, root is still active. Thanks all.