Database Develop

[MOD] Adfree System without RW Access to /system

Hey there,
this is my first thread ever created by me in a development forum.
I wanted to share my sollution for a adfree Android system, without unlocking the boatloader to get R/W access to /system.
I did try it on my device, everything went fine, but i will not take any kind of reponsibility for your devices. Also your warranty may be void!
What you need:
- rooted XTZ (i tried it on the 16GB Wifi only version)
- busybox installed
- Android SDK or adb.exe
- patched hosts file, I took mine from my HTC ONE with adaway installed (unzip first)
Click to expand...
Click to collapse
How to do it:
- get a patched hosts file from another device, or use mine (attached)
- put the file on the root of your sd card (so it will be /sdcard/hosts)
- connect your tablet to your PC, make sure usb debuggig is turned on
- launch cmd window, where your adb.exe is located
- entering following commands:
Code:
0. adb shell
1. su
2. stop ric
3. busybox pkill -f /sbin/ric
4. mount -ro remount,rw /system
5. busybox cp -af /sdcard/hosts /system/etc/hosts
- if everything went ok, you should now be able to see all the entries in your /system/etc/hosts file
- sadly you have to update the file if there some new adhosts, but it will remove a lot of annoying ads from all apps and the browser
- the changes are permanent, even at a reboot
Click to expand...
Click to collapse
Just let me know, if you have some kind of questions!
thanks @juanyunis for the [TEMPORAL-FIX] Remount RW /system reboot thread, from which i got some ideas.
Greetings from Germany

I have been using the AdAway app continuously since Google decided to eliminate all ad blocking apps from its Play Store and from my experience, AdAway does not require an unlocked boot loader to work, it only requires root access, and AdAway has no problem installing a hosts file in the /system/etc directory, so I am curious about why you have to go through all that.

The problem is, that if you using vroot like i did, and you doing nothing else, you don't have read write access to /system. So adaway, adfree and whatever can't edit the hosts file. Therefore is my little mod to get it done manually

Havoc2k said:
The problem is, that if you using vroot like i did, and you doing nothing else, you don't have read write access to /system. So adaway, adfree and whatever can't edit the hosts file. Therefore is my little mod to get it done manually
Click to expand...
Click to collapse
after vroot, install SuperSU and then all app ad-blocking apps are working good.

nope sorry, i did it, installed vroot, switched to normal superSU and installed busybox. But there is no RW access, so the ad blocking apps will work, but only to the next systemreboot / userswitch
tried all of them, and tried to manually edit the host file, but without access it will not happen
greetings

Havoc2k said:
But there is no RW access
Click to expand...
Click to collapse
strange thing that with root there is no RW access.

Havoc2k said:
nope sorry, i did it, installed vroot, switched to normal superSU and installed busybox. But there is no RW access, so the ad blocking apps will work, but only to the next systemreboot / userswitch
tried all of them, and tried to manually edit the host file, but without access it will not happen
greetings
Click to expand...
Click to collapse
I have tested and have for several months ran AdAway on my XTZ, on which Vroot was used to gain root access and SuperSU is installed, and AdAway has no problem writing a hosts file to the /system/etc directory even though the permissions for the /system and /system/etc directories are set to read-only. So, because I have no problem with AdAway and you apparently have a problem with AdAway, I believe it is likely there is a flaw in your root access setup. But hey, I could be wrong.

adaway installation on official rom

Has anyone managed to install adaway on any official rom?
The program fails when trying to apply the hosts file.
Yes i have rooted the phone and yes i have granted permisions with supersu to adaway.

revery0 said:
Has anyone managed to install adaway on any official rom?
The program fails when trying to apply the hosts file.
Yes i have rooted the phone and yes i have granted permisions with supersu to adaway.
Click to expand...
Click to collapse
I had it many times. AdAway is working very wele. Maybe you have not full rooted phone. Use MyRoM it is full rotted and AdAway is preinstalled and many others additions.

Hey...
First step is normal root. If you are ready you have to delete the immutable.list on system. Then you can use adaway.
Booth ways need busybox! Install it before you try to delete immutable.
Make it with my tool - easy update and adjust (http://forum.xda-developers.com/asc...eandadjust-t2941186/post56774286#post56774286) or make it manuelly with your PC and ADB.
adb shell
su
mount -o rw,remount /system
cd system
chattr -R -i *
rm –f /system/set_immutable.list
lsattr (to see if it's still there)
On my device with stock Rom it works well!

Thank you, it works like a charm!!!

revery0 said:
Thank you, it works like a charm!!!
Click to expand...
Click to collapse
No problem...
Wich way you have choosed?

Your script, cause command prompt returned an error when trying to change attributes, the reason was that adb hadnt have su permissions and for some reason supersu didnt prompt me to grant them. But with your script supersu prompt me to give adb su permissions and so i did, after that it worked.
Strange dont you think?

revery0 said:
Your util, cause command prompt returned an error when trying to change attributes, the reason was that wasanted su permiadbwasntions and suidnt proe to give it permissions, but when I tried your script then I got the prompt from supersu and itsusupersudidntsupersu..
Sounds strange dont you think?
Click to expand...
Click to collapse
I dont understand you complete. But my batch is working for you, thats fine

Auto correction on swype keyboard sucks.... I edited the previous post

revery0 said:
Auto correction on swype keyboard sucks.... I edited the previous post
Click to expand...
Click to collapse
yeah it corrects way u dont want it .. just turn off auto and leave options to pick..

[Q] Does the S6 root work for Edge?

I was checking out the Root Thread for S6 and realized that my Edge's ROM version matched one on there except for the G925 vs G920. Would that root work on my Edge's similar ROM?

Never EVER try to root your phone unless it meets ALL the requirements! Mine is a SAMSUNG-SM-G925V. Unless that root is developed for a SAMSUNG-SM-G925V, you're taking a chance on bricking your phone. There are things you can do to remove bloatware and improve battery performance, which are a couple of the main reasons for installing a different ROM. I've done it myself and find battery performance has drastically improved. Do some research and you'll find what settings you can change and which apps you can either uninstall or disable. I'm happy with the snappiness and performance of this phone and find with some simple adjustments, it makes this phone even better. We will just have to be patient to see if the bootloader can be unlocked. Who knows when or if that will happen any time soon! Hope that addresses your question.
Sent from my SM-G925V using XDA Free mobile app

MaverickCoast said:
Never EVER try to root your phone unless it meets ALL the requirements! Mine is a SAMSUNG-SM-G925V. Unless that root is developed for a SAMSUNG-SM-G925V, you're taking a chance on bricking your phone. There are things you can do to remove bloatware and improve battery performance, which are a couple of the main reasons for installing a different ROM. I've done it myself and find battery performance has drastically improved. Do some research and you'll find what settings you can change and which apps you can either uninstall or disable. I'm happy with the snappiness and performance of this phone and find with some simple adjustments, it makes this phone even better. We will just have to be patient to see if the bootloader can be unlocked. Who knows when or if that will happen any time soon! Hope that addresses your question.
Sent from my SM-G925V using XDA Free mobile app
Click to expand...
Click to collapse
I didn't realize that was the case and went ahead installing the apk. Bad news, it didn't work. Good news, the app tells you it doesn't work for G925V yet.

mngdew said:
I didn't realize that was the case and went ahead installing the apk. Bad news, it didn't work. Good news, the app tells you it doesn't work for G925V yet.
Click to expand...
Click to collapse
iambugsy said:
I was checking out the Root Thread for S6 and realized that my Edge's ROM version matched one on there except for the G925 vs G920. Would that root work on my Edge's similar ROM?
Click to expand...
Click to collapse
There's been an update. Version 3.2 of the app works fine on current Verizon S6 Edge software. I currently am sitting on one with root.

Berzerker7 said:
There's been an update. Version 3.2 of the app works fine on current Verizon S6 Edge software. I currently am sitting on one with root.
Click to expand...
Click to collapse
That's awesome news, thanks! I'll try it out when I get home today.

Yup - just used the updated APK and it worked like a charm. Went ahead and swapped out King for SuperSU.. that too works great.

How did you swapped king for super su?

furialfil said:
How did you swapped king for super su?
Click to expand...
Click to collapse
Check out the Q&A area of the PINGPONGROOT thread.. its all listed in there. I copied/pasted from it, but it might not transfer the code exactly correct..
http://forum.xda-developers.com/galaxy-s6/general/root-pingpongroot-s6-root-tool-t3103016
Q: I'd like switching to SuperSU, what shall I do?
A: Kinguser does not have a "swtich" function. Follow these steps to do so manually: (if you are not familiar with adb, see this version: http://forum.xda-developers.com/show...&postcount=269)
1. Download supersu.7z and extract it. You will get the files needed to install Supersu.
2. Using adb to push su and busybox (if not installed) to /data/local/tmp.
Code:
adb push su /data/local/tmp
adb push busybox /data/local/tmp
3. Start a su session and run the following commands:
Code:
mount -o remount,rw /system
cat /data/local/tmp/su >/system/xbin/daemonsu && chmod 0755 /system/xbin/daemonsu
cat /data/local/tmp/busybox >/system/bin/busybox && chmod 0755 /system/bin/busybox
daemonsu -d &
Then keep the session running.
4. Open Kinguser, go to Settings -> Root authorization setting -> Remove Root permission. Click to remove root permission. Your su session should be still running.
5. Uninstall Kinguser app.
6. Go back to the su session and run following commands to replace su and cleanup:
Code:
cat /data/local/tmp/su >/system/xbin/su && chmod 0755 /system/xbin/su
busybox chattr -ia /system/bin/ddexe
busybox chattr -ia /system/bin/ddexe_real
cat /system/bin/ddexe_real >/system/bin/ddexe
busybox chattr -ia /system/xbin/ku.sud
rm /system/xbin/ku.sud
rm /system/xbin/pidof
rm /system/xbin/supolicy
7. Install Supersu apk
8. Open Supersu apk to update files.
9. Reboot.

wait a minute so we now have root ?

XTRoRDiNAiRE said:
wait a minute so we now have root ?
Click to expand...
Click to collapse
yes

If your version matches what's in the pingpong root thread then yes. I rooted my S6E a few min ago.

Zmnypit said:
If your version matches what's in the pingpong root thread then yes. I rooted my S6E a few min ago.
Click to expand...
Click to collapse
rooted. has anyone installed TWRP? what's the best way to go about doing that? TWRP manager doesn't list verizon specific s6.
I want to flash the no-deep-sleep fix

I believe you can't install a custom recovery yet as it will trip knox. Might want to go through the posts on the root thread.

Thanks. Yeah sorry it's a bit hard to follow the latest news since there are a thousand threads on all the s6/edge forums talking about the same issue. If the recovery is untouched, do we need to worry about the deep sleep problem? I've read it was caused by recovery.

[q] please help busybox problem

i've accidentally uninstall busybox (don't ask why, long story), now there's no busybox on my z1, but when i'm tring to install busybox using busybox again it always failed, the message "busybox was not sucsess, try to change location to fox the issues". Anyone have the solution for this problem? I'm using xperia Z1 sol23 (japan version), rooted, lockbootloader, no cwm. In my system/ xbin there's some files but no busybox files. I'm tring to copy busybox to xbin but the system wont let me to write in xbin. Help me please... is there any method to install busybox?
Sent from my LG-E988 using Tapatalk

I have that problem too in the latest firmware 5.1.1 (prerooted rom). I wonder if everyone who use prerooted 5.1.1 have this busybox bug. I have used some busybox installer from playstore but the installation failed, telling me to change location of busybox installation. In my case i'm sure I didn't removed the busybox. I installed the rom clean and I also flashed the latest supersu successfully.

Hopefully I can repay xda a little here and maybe help you guys out.
I spent all day downgrading to kitkat and then flashing a pre-rooted 5.1.1 ROM.
I have just finished and root seems ok. I tried to use 'busybox installer' and it failed (it wasnt asking for supersu permission).
I tried 'busybox' from the link below and it installed fine.
Hope this helps
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
EDIT: I'm sure You'd already tried that but I had a problem with busybox installer just minutes before your post, so thought it was worth mentioning what worked for me

[GUIDE][SuperSU]Android Wear system-less root [2.79]

Follow this guide to flash SuperSU on the latest version of android wear for your watch, it should have the same OS compatibility as normal SuperSU and should work all the way upto android 7.1.1
(from PC)
1.Unlock the bootloader if not already unlocked
(Make sure to set up device with phone after unlocking bootloader otherwise no boot!)
Code:
adb reboot bootloader
fastboot oem unlock
2.flash TWRP for your device (REQUIRES read only access to system!, will post working builds in post below)
Code:
fastboot flash recovery recoveryname.img
3.Download SuperSU with busybox YDS included HERE and move it to watch with adb push to /sdcard while TWRP is booted and then install as normal zip
Code:
adb push nameofzip.zip /sdcard/
4.IGNORE SYSTEM NOT INSTALLED Boot watch to system and Now your root apps from 5.1 should work perfect. THERE WILL BE NO SUPER SU APP, IT HAS NOT BEEN PORTED TO ANDROID WEAR
REMEMBER squashfs is read only even with root so don't bother trying to modify system files like the build.prop.
If you would like to modify system use any Linux distro and unsquash the system then resquash it (will make guide if enough interest)
If you would like to change pixel density perform this command in either adb shell or a terminal emulator:
Code:
wm density <dpi>
Please leave thanks if it helped!

Feel free to submit links to twrp for squashfs watch with model name, codename and original developer's name
Will add them to this post
THESE ARE THE ONLY BUILDS THAT WILL WORK UNTIL TWRP IS UPDATED!
I DID NOT CREATE ANY OF THESE BUILDS!
LG G Watch dory (courtesy of @rbox)
LG G watch R lenok

In regards to Busybox on Rails, I compared the link provided and Google Play (which I assume is latest), they are the same versions. Is there a trustworthy place to find the old version suggested?
Not sure if I will need it, just covering my bases. Upgrading to 6.0.1 tonight.
Thanks.

First post and Thanks to you!!!
This is my first post in the community, i thank you all for all you do! I have successfully rooted lg g watch with android 6.0.1 build mec23d using your method. busy box pro installed after uninstalling superuser.

OfficerJimLahey said:
In regards to Busybox on Rails, I compared the link provided and Google Play (which I assume is latest), they are the same versions. Is there a trustworthy place to find the old version suggested?
Not sure if I will need it, just covering my bases. Upgrading to 6.0.1 tonight.
Thanks.
Click to expand...
Click to collapse
Oh I thought it was an older version will edit that as the latest did not work On 5.1.1 wear but I guess it those on 6.0.1

itsthamessenger said:
This is my first post in the community, i thank you all for all you do! I have successfully rooted lg g watch with android 6.0.1 build mec23d using your method. busy box pro installed after uninstalling superuser.
Click to expand...
Click to collapse
Glad I could help! I was not aware the busybox pro worked on wear is it the one by stericson?

Xmaster24 said:
Glad I could help! I was not aware the busybox pro worked on wear is it the one by stericson?
Click to expand...
Click to collapse
Yes it is!

itsthamessenger said:
Yes it is!
Click to expand...
Click to collapse
Thanks for the info will add to post

Unless I am missing something, system access is needed for the LG G Watch.
Tried with TWRP 3.0.0 and 2.8.7, SuperSU 2.65 flash was successful in spite of /system not mounting (notice was given in red letters), rebooted, with same result across both versions:
Code:
[email protected]:~$ Build/android-sdk-linux/platform-tools/adb uninstall eu.chainfire.supersu
Failure [DELETE_FAILED_INTERNAL_ERROR]
[email protected]:~$ Build/android-sdk-linux/platform-tools/adb install Downloads/BusyBox%20On%20Rails_5.1.74_apk-dl.com.apk
1087 KB/s (2287614 bytes in 2.053s)
pkg: /data/local/tmp/BusyBox%20On%20Rails_5.1.74_apk-dl.com.apk
Success
[email protected]:~$ Build/android-sdk-linux/platform-tools/adb shell
[email protected]:/ $ su
/system/bin/sh: su: not found
127|[email protected]:/ $
Looks like SuperSU is not even bothering with system-less mode:
http://pastebin.com/T7k0cWHv

OfficerJimLahey said:
Unless I am missing something, system access is needed for the LG G Watch.
Tried with TWRP 3.0.0 and 2.8.7, SuperSU 2.65 flash was successful in spite of /system not mounting (notice was given in red letters), rebooted, with same result across both versions:
Click to expand...
Click to collapse
Huh I used a modified version of the latest TWRP from a member that allowed the system to be mounted read only as squashfs is a read only file system ie. The system image has to be rebuilt to make changes. I assumed that since supersu is now system less it those not require system access but maybe it those but I really didn't see the use of mounting it read only as it cannot make any changes to system. Will edit thread thanks for info. Link to squashfs twrp above
It is strange though the other poster managed to root without system access.

Xmaster24 said:
Huh I used a modified version of the latest TWRP from a member that allowed the system to be mounted read only as squashfs is a read only file system ie. The system image has to be rebuilt to make changes. I assumed that since supersu is now system less it those not require system access but maybe it those but I really didn't see the use of mounting it read only as it cannot make any changes to system. Will edit thread thanks for info.
Click to expand...
Click to collapse
The third time I flashed to get the log, I attempted to mount /system as read only, since it didn't mount properly otherwise. The onscreen messages looked the same anyway...successful flash, but could not mount /system. And upon leaving TWRP, it warned that no OS was installed. Nothing different for all intents and purposes.
Thanks, I will try your TWRP and report back.
UPDATE:
Your TWRP made all the difference:
Code:
[email protected]:~$ Build/android-sdk-linux/platform-tools/adb uninstall eu.chainfire.supersu
Success
[email protected]:~$ Build/android-sdk-linux/platform-tools/adb shell
[email protected]:/ $ su
[email protected]:/ #
Thank you!

OfficerJimLahey said:
The third time I flashed to get the log, I attempted to mount /system as read only, since it didn't mount properly otherwise. The onscreen messages looked the same anyway...successful flash, but could not mount /system. And upon leaving TWRP, it warned that no OS was installed. Nothing different for all intents and purposes.
Thanks, I will try your TWRP and report back.
UPDATE:
Your TWRP made all the difference:
Thank you!
Click to expand...
Click to collapse
No problem guess SuperSU those require system access to work it seems to be for SE Linux patching and also the build.prop

Xmaster24 said:
<snip>
4.Boot to system and open Busybox on rails app and install busybox
<snip>
Click to expand...
Click to collapse
Thanks for this guide! Rooted AOK :good:
This Step 4 is to install Busybox on Rails onto the phone? or Watch?

drewski_1 said:
Thanks for this guide! Rooted AOK :good:
This Step 4 is to install Busybox on Rails onto the phone? or Watch?
Click to expand...
Click to collapse
Welcome and watch the whole process only requires pc and watch no phone involved. My modified supersu installer should have installed busybox on Rails app to the watch

Xmaster24 said:
Welcome and watch the whole process only requires pc and watch no phone involved. My modified supersu installer should have installed busybox on Rails app to the watch
Click to expand...
Click to collapse
got it. thanks again!!

Highly recommend everyone to get invisiblek's kernel its top notch gets rid of the horrible lag of 6.0.1's kernel And is fully supported by my root method so even better!

Sent from my GT-S5830i using XDA Free mobile app

Where do supersu and busybox get installed
Xmaster24 said:
Welcome and watch the whole process only requires pc and watch no phone involved. My modified supersu installer should have installed busybox on Rails app to the watch
Click to expand...
Click to collapse
Since the new wear has a read only system, where do the supersu and busybox get installed?

ganovim said:
Since the new wear has a read only system, where do the supersu and busybox get installed?
Click to expand...
Click to collapse
SuperSU is now system less if you haven't been following it recently so system access is not required also bits of supersu are stored in the kernel disk and others just at /data. Busybox is stored with the SU mounted image to /su/xbin once installed via the app

/moved to specific lg g watch thread