Related
Has anyone gotten Adfree android to work on the my touch slide 3G?
I either get a reboot or error about writing to hosts
Sent from my T-Mobile myTouch 3G Slide using XDA App
Faud said:
Has anyone gotten Adfree android to work on the my touch slide 3G?
I either get a reboot or error about writing to hosts
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
See this post:
http://forum.xda-developers.com/showthread.php?t=664532
Ignore the installation commands, you need to boot in to recovery and push the hosts file to /system/etc/ on the phone.
Adfree works fine. The reason it doesn't work on slide has nothing to do with the app. The hosts file goes in /system/etc/ and since we don't have r/w access to /system, the app can't do what's its supposed to do. It works great I used it the whole time I had a G1, its just cus your phone isn't PROPERLY rooted. Neither is anyone elses til we get that SPL...
Til then you gotta adb push the file thru recovery...
I dunno if you know this, but adfree temporarily d/l's the hosts file to your sdcard, then deletes it when its done. But since it couldn't replace the file on my slide, it left it on the sdcard! All you gotta do is run the app and wait for it to error out, then go get the file and put it on your pc and adb push to /system/etc...
-BMFC
Sent from my ROOTED myTouch3G Slide
bmfc187 said:
its just cus your phone isn't PROPERLY rooted. Neither is anyone elses til we get that SPL...
Click to expand...
Click to collapse
Actually, its rooted just fine (you can run anything you want as uid 0). The SPL security has nothing to do with root.
It is like saying you don't have the proper key to a door just because after you open it there is a guard standing there not letting you in to the next room.
Just being picky...
i think what he meant is that with all the other phones most of us have had we had an SPL to flash once we had done the original tweaks(or before on some phones) so as of right now i agree that the phone is not rooted properly yet as i don't have full control over the phone whenever i want, i want to be able to mv stuff to system partition from android terminal
just being picky...
could anyone please post the actual commands? im new to adb and wold really appreciate the help adfree is the entire reason i even rooted
among others but it was the number one
adb push hosts /system/etc
-BMFC
Sent from my ROOTED myTouch3G Slide
thank you so very much
Other than removing a few of the stock apps, this is one of the things I'm looking forward to rooting for, I loved it on my G1.
With all of the folks having so much trouble rooting this sucker though, I may wait awhile.
it said this
' failed to copy 'hosts' to '/system/etc': Permission denied '
and if i type su it asks for a password and if i try to run in root it says that production models wont run in root
but i rooted and have the superuser permissions apk installed and has granted me permission to other things
ParkerOviedo said:
it said this
' failed to copy 'hosts' to '/system/etc': Permission denied '
Click to expand...
Click to collapse
Were you booted in to recovery with /system mounted?
i was able to figure it out
i never tried typing su into the adb shell after i rooted
i got the prompt on my device and accepted it now i have full permissions
well it accepted the command and it pushed the host file to /system/etc but it still isnt disabling ads |:<
ParkerOviedo said:
well it accepted the command and it pushed the host file to /system/etc but it still isnt disabling ads |:<
Click to expand...
Click to collapse
same thing happened to me. but as falken mentioned before, you have to make sure the system is mounted before running the command. so..
boot into recovery.
go to 'partitions'.
select 'mount /system'.
run adb command "adb push hosts /system/etc".
reboot system.
*you might wanna might wanna be sure the comp sees the device in recovery before running the command via "adb devices". i do this before i do any adb'ing.
*be sure the hosts file is in the root of your sdk directory, otherwise your command will vary.
poetik517 said:
same thing happened to me. but as falken mentioned before, you have to make sure the system is mounted before running the command. so..
boot into recovery.
go to 'partitions'.
select 'mount /system'.
run adb command "adb push hosts /system/etc".
reboot system.
*you might wanna might wanna be sure the comp sees the device in recovery before running the command via "adb devices". i do this before i do any adb'ing.
*be sure the hosts file is in the root of your sdk directory, otherwise your command will vary.
Click to expand...
Click to collapse
All I get is "failed to copy 'hosts' to '/system/etc': Permission denied"
And yes my Phone is Rooted..
I did everything above. do I have to be in su or something...
Can you not do this on the stock rom. Do I have to flash one of the other roms to be able to push to System...
jnight666 said:
All I get is "failed to copy 'hosts' to '/system/etc': Permission denied"
And yes my Phone is Rooted..
I did everything above. do I have to be in su or something...
Can you not do this on the stock rom. Do I have to flash one of the other roms to be able to push to System...
Click to expand...
Click to collapse
You need to have flashed the engineering rom so you have a root shell in recovery.
Does the Hosts file even block ads?
droctii said:
Does the Hosts file even block ads?
Click to expand...
Click to collapse
Yup, and it makes the internet soo much faster. Adfree works fine as is if you add the rw overlay
dumfuq said:
Yup, and it makes the internet soo much faster. Adfree works fine as is if you add the rw overlay
Click to expand...
Click to collapse
BINGO! Thanks!!!
This was created when we didn't have S-OFF yet.
If you have S-OFF or /system overlay script you won't need to go through all the steps simply download adfree android.
I know most of you will be able to do this. But I believe that it might not be as easy for the beginners. So here is a little walk through.
!NEEDs ROOT!
1. Download Adfree Android
2. Wait for it to determine local hosts then click on download and install hosts.
Now it will try to replace /system/etc/hosts but fail (it should reboot the phone but it didn't reboot mine)
4. go to adb and reboot your phone into recovery (with power on+volume down OR the command: "adb reboot recovery")
5. Open up the recovery-windows (start recovery-windows (make sure your in the right directory))
6. mount your system and sdcard you might be able to just use mount and mount everything but I've mounted them serperatly.
Here's how: "adb shell mount /system" next "adb shell mount /sdcard"
7. Now we're going to put it in the etc directory where it should be: "adb shell cp /sdcard/hosts /system/etc"
8. reboot the phone ("adb reboot")
That should remove most of the adds.
I know it's explained on a really low level of knowledge but I wanted to make it accessible for all of you.
Only the needed codes:
Code:
1. adb reboot recovery
2. start recovery-windows
3. adb shell mount /system
4. adb shell mount /sdcard
5. adb shell cp /sdcard/hosts /system/etc
6. adb reboot
has it the option to only block browser ads? when I tried it time ago it couldn't. I don't like to block the app ads
No it removes the adds everywhere. It simply blocks the links to adds. it doesn't actually remove them. they are still being called but they just don't show up.
Hi,
I have this very same problem for a long time now, with the constant reboots etc.
Followed your steps, but after the reboot, as soon as I press the button to update the hostfile, it reboots my phone
Thanks anyway...
PirateNL said:
Hi,
I have this very same problem for a long time now, with the constant reboots etc.
Followed your steps, but after the reboot, as soon as I press the button to update the hostfile, it reboots my phone
Thanks anyway...
Click to expand...
Click to collapse
Do you have root access?
Have you checked if the hosts file is at the root of your SD?
A good guide, if a little misplaced, but another option is the /system overlay.
JonasDroid said:
Do you have root access?
Have you checked if the hosts file is at the root of your SD?
Click to expand...
Click to collapse
Yes and yes
where is the most recent hosts file? I'm using a vibrant and it says it worked, but of course, it doesn't. And it doesn't copy the hosts file to my sdcard either ? odd
Hello ,
Finally I got Adfree working
Ok it's not perfect because app continue to reboot the phone after updating the hosts file ,
and we need to copy it manually in recovery mode but it better than nothing
Thank you very much JonasDroid for this little How to .
PS:
For me step 5
JonasDroid said:
Code:
5. adb cp /sdcard/hosts /system/etc
Click to expand...
Click to collapse
was
Code:
adb shell cp /sdcard/hosts /system/etc
Bye.
Yeah indeed its adb shell cp thx for letting me know
Sent from my Legend using XDA App
Can you link me the apk of adfree? I can't download the app from my phone
BTW it's 'ADs" single d
short for advertisment (notice the single d?)
Fixed that English is not my main language
Sent from my Legend using XDA App
JonasDroid said:
5. Open up the recovery-windows (start recovery-windows (make sure your in the right directory))
Click to expand...
Click to collapse
Can't get "start recovery-windows" to work. What is the "right directory"?
Things seems to have worked for me without that portion. Many thanks, I will now change my review in the market for that app from one star to three stars. If they include a note describing this problem upfront I may bump it up further.
It could simply be called start recovery (depending on where you got your rooting tools)(if you've got the from The Unlockr you'll need the -windows)
If you have S-OFF or if you use an /system overlay script these steps aren't needed. (It was created when we didn't have S-OFF for our legends yet.)
Anyone having problems with adfree scripts on Legend since Froyo update? Neve had a problem witha rooted 2.1, but have lots of problems since rooted Froyo 2.2
It seems HTC may have some service which is checking for modifications to symlinks etc.
When I run adfree in my S-off CM7, i get an java.io.EOFException.
Someone else having this?
I had some problems at first, but reinstalling adfree android from market seemed to help. No problem now with CM7 (01/03 from ali ba) and s-off.
adfree no block ads!
Hi,
i install the adfree on my legend with 2.2 with sense.
i did download the host from the app all work ok got a message say it was success install and need to restart the phone.
i did it but still get all the ad like before on all apps.
pls help!
Have you followed the steps? (explained in first post)
Note that you should have a rooted legend (if you don't know what that is then you don't have one)
Psneuter exploit is working on IS, but because /system is locked on s-on phones, we can't copy su and superuser.apk into /system, apps required root access can't work.
The following procedure uses psenuter exploit to gain adb shell root, and then copy su (without privilege control ) and busybox into /sbin (which is on rootfs and in the global PATH list) to gain root access for apps.
The procedure:
1. Unzip the attached .zip into a directory (like c:\adb)
2. Open a command prompt and cd to the directory where you extracted the .zip (like cd \adb)
3. run pushroot.bat (simply type pushroot)
4. adb shell /data/local/tmp/getroot
5. adb shell
6. you are now in # prompt. Type /data/local/tmp/pushroot
You have to redo steps 4,5,6 once you reboot your phone.
The procedure will have all apps gaining root access.
!!USE ON YOUR OWN RISK!!
Known working programs: Root explorer, Titanium backup, gscript lite, trasproxy 2.04, ...
Some apps check existence of su in /system/xbin , and reject to proceed if the su binary is not exist (like transproxy 3.08). For this kind of apps, this procedure won't help.
Nice but old news mate...
Sent from my HTC Incredible S using XDA Premium App
Good job...thanks
Thanks for writing this up, might quell the thirst for S-OFF a little longer
/system/ is writeable btw, if you remount it, but after reboot everything u done will be changed to the way it were before.
so a temp root in xbin is possible also, only it will be gone afterwards (atleast i never tried this, but should work also...)
Yes. /system could be remount in rw with root. However, the files you wrote will be gone after you remount ro, and then you won't be able to copy the same filename into the same location again before next reboot ( I don't know why, actually!!). This is why I put su in sbin instead of /system/xbin.
thanks to your files 非常感谢你的工作。
Does anyone know whether steps 4, 5 and 6 can be run from the device itself?
Can I put these commands into some sort of script and run it everytime I need temp root or would I need to do this from a computer every time?
faf said:
Does anyone know whether steps 4, 5 and 6 can be run from the device itself?
Can I put these commands into some sort of script and run it everytime I need temp root or would I need to do this from a computer every time?
Click to expand...
Click to collapse
I believe you can do it from a terminal emulator but haven't got the chance to try it myself though.
Sent from my HTC Incredible S using Tapatalk
pushroot error
c:/adb>adb shell ln /data/local/tem/busybox /data/local/tmp/cp
Link failed File exists
and
c:/adb>adb shell /data/local/tmp/getroot
mmap<> failed. operation not permitted
Why??THX....
itandy said:
I believe you can do it from a terminal emulator but haven't got the chance to try it myself though.
Sent from my HTC Incredible S using Tapatalk
Click to expand...
Click to collapse
Definitely, this is the way to go.
Unfortunately, the root exploit I know could run on device itself, including
rageagainstthecage (ratc) and local root exploit (hotplug) both failed on IS.
The solution will be nearly perfect if we can get temp root on IS without a computer link.
Any input will be welcome.
sky1212 said:
pushroot error
c:/adb>adb shell ln /data/local/tem/busybox /data/local/tmp/cp
Link failed File exists
and
c:/adb>adb shell /data/local/tmp/getroot
mmap<> failed. operation not permitted
Why??THX....
Click to expand...
Click to collapse
Please then type adb shell.
If you see # but not $, do
cd /data/local/tmp
rm ./cp
ln busybox cp
./pushroot
Then you finished the install.
If you see $, please do all over again.
You can also add ShootMe (screen capture app) and SetCPU to the list of working apps. SetCPU will only allow you underclock for now due to the kernel, but it is a nice touch if you are worried about battery life. Adfree doesn't appear to work
l0st.prophet said:
You can also add ShootMe (screen capture app) and SetCPU to the list of working apps. SetCPU will only allow you underclock for now due to the kernel, but it is a nice touch if you are worried about battery life. Adfree doesn't appear to work
Click to expand...
Click to collapse
Adfree is working for me. Are you getting some type of error message?
MetaMorph, screenshot and MyBackup Root are also working.
I had to mount system, then push su to /system/xbin. Then install BusyBox Installer from Market.
No erro, still got the ads. I've tried rebooting & rerooting, still no luck
l0st.prophet said:
No erro, still got the ads. I've tried rebooting & rerooting, still no luck
Click to expand...
Click to collapse
What site/app are you going to so I can see if I get the ads.
the anti-ads actually tries to modify the current host file... which is not allowed in your state as far as i know
what you can do is replace it by pushin it to the right spot
but after reboot gone,but sure u know
Adfee is working for me, you can also add Droidwall.
@eddycyf, did you test adfree with apps? Since it aint working for prophet...
Sent from my HTC Incredible S using XDA Premium App
Mhm AdFree isnt working for me. The App states that everything is okay, and that my hosts file is up to date, but I see ads everywhere.
But I am kinda happy now, because i can use Titanium Backup
Another S-Off script that was sent to me by coremark. Successfully s-off my device and supercid.
http://firewater-soff.com/
Thanks to @coremark.
After gaining S-off on a fully stock device using Firewater + temproot, what is the easiest method for permanent rooting?
Since due to S-off full access is granted to all partitions, is it possible to install the su binary and superuser / superSu apk to the /system partition without flashing a custom recovery? For example by using "adb push" or a root file manager?
Where can I get a su binary? Should I extract it from superSu / superuser recovery ZIP package?
Could anyone walk me through the steps?
edorner said:
After gaining S-off on a fully stock device using Firewater + temproot, what is the easiest method for permanent rooting?
Since due to S-off full access is granted to all partitions, is it possible to install the su binary and superuser / superSu apk to the /system partition without flashing a custom recovery? For example by using "adb push" or a root file manager?
Where can I get a su binary? Should I extract it from superSu / superuser recovery ZIP package?
Could anyone walk me through the steps?
Click to expand...
Click to collapse
I'm afraid you'll need a custom recovery for this. The /system write protection is implemented in kernel (the kernel doesn't sync changes to the actual block device and keeps them in RAM) and S-OFF is completely orthogonal to this. To work around it, you'd need a custom kernel (which is not feasible at the moment since HTC haven't released the full source tree yet, unfortunately) or the wp-mod hack (which I would be afraid of using, to be honest).
Also, why avoid custom recovery when you're already S-OFF and you can flash the stock recovey anytime?
koniiiik said:
The /system write protection is implemented in kernel (the kernel doesn't sync changes to the actual block device and keeps them in RAM) and S-OFF is completely orthogonal to this.
Click to expand...
Click to collapse
You are right, that makes sense.
But then how is this possible (if it is at all)? -> http://forum.xda-developers.com/showthread.php?t=2339056
(Pls check out the 2nd post from member "Indirect".)
AFAIK the One has the exact same kind of /system write protection as the 901s. Doesn't it?
Just out of curiosity, why would you be afraid to use wp-mod? Unknown / unpublished source? Bad feedback from users?
edorner said:
You are right, that makes sense.
But then how is this possible (if it is at all)? -> http://forum.xda-developers.com/showthread.php?t=2339056
(Pls check out the 2nd post from member "Indirect".)
AFAIK the One has the exact same kind of /system write protection as the 901s. Doesn't it?
Click to expand...
Click to collapse
To be honest, no idea. All I do know is that on my phone the write protection works the way it does and I don't really see a feasible way around it. Also, I haven't tried these exact steps. It's possible that adb remount does some extra work or something. Moreover, I'm not sure about the adb shell chmod ... command – that would require root, wouldn't it? But since I haven't tried it, I can only guess.
If you don't mind trying it, I'd be interested in the results.
edorner said:
Just out of curiosity, why would you be afraid to use wp-mod? Unknown / unpublished source? Bad feedback from users?
Click to expand...
Click to collapse
The way I understand wp_mod works is that it monkey-patches the running kernel's filesystem driver to skip the check for the /system partition. In other words, it rewrites the code of the running kernel in-memory. This by itself is reason enough to be extremely careful around such code as it has potential for a major disaster. Missing the right memory location by any nonzero number of bytes can result in the kernel doing practically anything (most likely a crash).
Now, to make matters worse, these seem to be only a few binary versions of the kernel module and people seem to just take a binary compiled for one kernel, modify the version information within the file to make it match other kernels and load it on a completely different kernel. This, to me, is borderline insane, considering that the kernel binaries depend on the version of the kernel, used compiler and even compiler flags used when building.
Again, though, I haven't actually looked at the module's source code; can't say I'm suffering from a surplus of free time and I'm also not *that* interested in it. Most likely it's written in a robust enough way to have a high chance of success. (This seems to be backed up by anecdotal evidence – the thing appears to work for people, which is a small wonder for me.) All of the above is actually just my interpretation of stuff I read in some threads here on XDA-developers and I haven't even tried to confirm it myself.
Still, for me, using the recovery for any such changes is a sufficient and acceptable workaround, since I don't need to modify /system that often.
Wow! Thanks for the exhaustive expanation about WP-mod!
If you don't mind trying it, I'd be interested in the results.
Click to expand...
Click to collapse
Well I am also a bit skeptical about this solution. So I am not sure I will be brave enough to try it
But if I do decide to give it a try, I will post the results here, I promise.
edorner said:
Well I am also a bit skeptical about this solution. So I am not sure I will be brave enough to try it
But if I do decide to give it a try, I will post the results here, I promise.
Click to expand...
Click to collapse
As far as @Indirect's post goes, that should be risk-free – either it does work, or it doesn't do anything. I don't see how it could harm your phone. Worst case, you end up with a /system/xbin/su binary that doesn't work due to wrong privileges (or owner information), in which case you should be able to just remove it and start over.
koniiiik said:
As far as @Indirect's post goes, that should be risk-free – either it does work, or it doesn't do anything. I don't see how it could harm your phone. Worst case, you end up with a /system/xbin/su binary that doesn't work due to wrong privileges (or owner information), in which case you should be able to just remove it and start over.
Click to expand...
Click to collapse
Ah, I see. In that case I will definitely try it!
Truth is I am still an Android noob, I used ADB maybe on two occasions so far, and did not have the time yet to properly check out the documentation for these particular commands.
One more question:
If I understand correctly, Firewater (when used together with the temproot) will also unlock your bootloader. Do you think the apps in /data/preloadwill be deleted in this case too? (I.e. does it do a factory wipe like the unlock process via HTCDev?)
If so, how do I restore the apps? Do I simply copy the APK's back to /data/preload with a root file manager, and that's it?
IIRC Helium backup is not really perfect for the purpose, because it is unable to restore those apps to /data/preload, and puts them to the standard app path. Is this what you remember, too?
edorner said:
One more question:
If I understand correctly, Firewater (when used together with the temproot) will also unlock your bootloader. Do you think the apps in /data/preloadwill be deleted in this case too? (I.e. does it do a factory wipe like the unlock process via HTCDev?)
If so, how do I restore the apps? Do I simply copy the APK's back to /data/preload with a root file manager, and that's it?
IIRC Helium backup is not really perfect for the purpose, because it is unable to restore those apps to /data/preload, and puts them to the standard app path. Is this what you remember, too?
Click to expand...
Click to collapse
No idea, I haven't used firewater, but my guess would be that it won't wipe anything…
As for backing up /data/preload, you can for example use temproot to get access to the directory, copy it somewhere on your sdcard and adb pull it. In case it gets wiped, you can just push it back again and voilà. It's going to require some shell-fu, however.
Alternately, you can just download my ZIP of the latest stock ROM and extract it, it contains the latest /data/preload.
And yes, just copying the APK files into /data/preload should suffice *– Dalvik and its package manager is intelligent enough to detect something has changed in there and perform any installation steps necessary. If it doesn't work right away, a reboot should fix things.
Edorner. It won't wipe. I tried it already.
Sent from my GT-I9305 using XDA Premium 4 mobile app
koniiiik said:
As far as @Indirect's post goes, that should be risk-free – either it does work, or it doesn't do anything. I don't see how it could harm your phone. Worst case, you end up with a /system/xbin/su binary that doesn't work due to wrong privileges (or owner information), in which case you should be able to just remove it and start over.
Click to expand...
Click to collapse
So, as promised, I tried the "adb remount" command on my device and it did not work.
Code:
adb remount
remount failed: Operation not permitted
However "mount -o remount,rw -t ext4 /dev/block/mmcblk0p38 /system" in root shell (acquired by temproot) worked like a charm And the modifications to /system performed afterwards turned out to be permanent. So in the end I was able to gain root without using a custom recovery.
Based on my experiences, I created a guide which summarizes all the steps necessary to S-OFF and root a completely stock device without using HTCDev unlock and custom recoveries.
I investigated a bit as to why "adb remount" would not work, and found two interesting topics on XDA about the issue:
[2013.05.24][ROOT] adbd Insecure v1.30
Can't get ADB Root Access in certain ROMs?
In short, "adb remount" is only available if the ADB daemon is run in "insecure" mode in a particular ROM. And unfortunately our stock ROMs seem to use secure ADB.
edorner said:
So, as promised, I tried the "adb remount" command on my device and it did not work.
Code:
adb remount
remount failed: Operation not permitted
However "mount -o remount,rw -t ext4 /dev/block/mmcblk0p38 /system" in root shell (acquired by temproot) worked like a charm And the modifications to /system performed afterwards turned out to be permanent. So in the end I was able to gain root without using a custom recovery.
Based on my experiences, I created a guide which summarizes all the steps necessary to S-OFF and root a completely stock device without using HTCDev unlock and custom recoveries.
I investigated a bit as to why "adb remount" would not work, and found two interesting topics on XDA about the issue:
[2013.05.24][ROOT] adbd Insecure v1.30
Can't get ADB Root Access in certain ROMs?
In short, "adb remount" is only available if the ADB daemon is run in "insecure" mode in a particular ROM. And unfortunately our stock ROMs seem to use secure ADB.
Click to expand...
Click to collapse
Fantastic guide, I just read it and wow.
Also, good to know that particular procedure disables the write protection. I'll have to investigate this sometime, because just now I tried and found out that on my device, the changes to /system are rolled back as soon as I remount /system read-only again. Maybe if I left it read-write all the time, they would persist as well...? I'll have a closer look at this later.
koniiiik said:
Fantastic guide, I just read it and wow.
Also, good to know that particular procedure disables the write protection. I'll have to investigate this sometime, because just now I tried and found out that on my device, the changes to /system are rolled back as soon as I remount /system read-only again. Maybe if I left it read-write all the time, they would persist as well...? I'll have a closer look at this later.
Click to expand...
Click to collapse
Thanks
Hm... Strange...
Instead of manually remounting /system as "ro", I simply rebooted the device. (What can I say, I am hopelessly lazy ) After the reboot I checked the permissions of /system by issuing the "mount" command without any parameters. It showed that it was remounted using the original settings:
Code:
/dev/block/mmcblk0p38 /system ext4 ro,noatime,data=ordered 0 0
So in theory, rebooting instead of manually remounting as "ro" should not make any difference. But who knows
After the reboot, I checked the changes I made to /system previously, and fortunately they did not disappear. (su was still there, I could successfully copy it, and execute it.)
Since then, I've performed a couple more reboots and at least one full shutdown-startup cycle as well. And I still have not lost any changes.
Please let me know if you find something out! I am very interested.
Hey all
I'm having some trouble getting r/w access back on system on my 5803 on .726 firmware.
I have root and working recovery, just no r/w on system. Every time I check system access in terminal it sits at "ro" and not "rw"
I had full access in Kitkat, but when I flashed Lollipop I seemed to have lost r/w access. I have tried updating my recovery, RICDefeat, and byeselinux, all to no avail.
I feel like I'm busy missing something completely obvious, but I can't for the life of me figure out where I'm going wrong. Can any of you fine souls help?
Can you enable r/w acces using adb?
Open command line window, type adb shell (with device connected in debugging mode), then su, then mount -o remount,rw /system.
Don't know if this works for Lollipop, but I do see other users struggling to get full r/w permissions with the latest LP firmware.
Cheers.
chris5s said:
Can you enable r/w acces using adb?
Open command line window, type adb shell (with device connected in debugging mode), then su, then mount -o remount,rw /system.
Don't know if this works for Lollipop, but I do see other users struggling to get full r/w permissions with the latest LP firmware.
Cheers.
Click to expand...
Click to collapse
It seems that I can enable that way, but it doesn't persist after a reboot. And mounting system in recovery doesn't seem to do anything either. If I try run certain things in recovery it seems like they don't really work. I can change recoveries and ROM, but things like debloating scripts don't seem to work. It's quite strange.
Can you use Script Manager from Play Store to run a script at boot to enable root access? Not the best solution but may work?
Peace
chris5s said:
Can you use Script Manager from Play Store to run a script at boot to enable root access? Not the best solution but may work?
Peace
Click to expand...
Click to collapse
I suppose I could, but that's not gonna solve my problem with flashing things in recovery
Still struggling with this :/
Download this file, run .bat and ready. No need to restart.
https://mega.co.nz/#!tcEDFD4I!hrpQZxmq2Af8BFUS-ciCYBGVpEJ1LvVn_nLb2SYqAWc
pedro5148 said:
Download this file, run .bat and ready. No need to restart.
https://mega.co.nz/#!tcEDFD4I!hrpQZxmq2Af8BFUS-ciCYBGVpEJ1LvVn_nLb2SYqAWc
Click to expand...
Click to collapse
Thanks for the suggestion, but it doesn't work.