Firefox OS Architecture and Collaboration Opportunities w/ Asa Dotzler – XDA:DevCon 2014

We were privileged to host many presentations … more

Unofficial Android 4.4 Lands on Three Mediatek Devices

For the last few years, devices with MTK systems-on-chip haven’t received much … more

MultiImagePicker Library for Multiple Image Selection

App developmentcan be done in more than a handful of ways. You can write every single … more

Shoot Troubles, Not Users w/ Alex Boag-Munroe – XDA:DevCon 2014

In presenting the various sessions from XDA:DevCon 2014, weve mainly … more

Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

Why do people need write protection disabled when they boot into system?

OP Cozume

23rd February 2014, 04:55 AM   |  #1  
OP Account currently disabled
Thanks Meter: 89
 
423 posts
Join Date:Joined: Jan 2014
More
From all I am reading, Android disables write protection when you boot into recovery and any changes that you make in recovery stick when you boot into system. And if you have root access, you can make changes to system in recovery.

So what advantages are there to having write protection disabled when you boot into system? Why can't you make any changes you want while in recovery? Isn't that safer anyhow? Do some apps need write protection disabled to run?
23rd February 2014, 03:56 PM   |  #2  
Junior Member
Thanks Meter: 3
 
21 posts
Join Date:Joined: Apr 2011
Quote:
Originally Posted by Cozume

From all I am reading, Android disables write protection when you boot into recovery and any changes that you make in recovery stick when you boot into system. And if you have root access, you can make changes to system in recovery.

So what advantages are there to having write protection disabled when you boot into system? Why can't you make any changes you want while in recovery? Isn't that safer anyhow? Do some apps need write protection disabled to run?

I don't have a technical response or even very good response, but I do have an example of why you need access to the write protection.

I use AdAway to block advertising on my phone. (The ethics of doing this are up for debate, but lets leave that to another venue)
AdAway needs root access and the ability to modify the hosts file on the phone, which is a system protected file (for good reason). If write protection is on, then AdAway fails to modify the phone's hosts file and the ad blocking does not take place. With write protection off, AdAway is successful an my browser screen is far less cluttered when surfing.
I set the app to notify me when updates are available, but not to automatically apply the updates. Then I manually reboot to recovery and update my hosts file via AdAway. After I get the successful update I reboot normally and use my phone in the regular non-recovery mode.
23rd February 2014, 06:54 PM   |  #3  
OP Account currently disabled
Thanks Meter: 89
 
423 posts
Join Date:Joined: Jan 2014
More
Quote:
Originally Posted by _Boondock_

I use AdAway to block advertising on my phone. (The ethics of doing this are up for debate, but lets leave that to another venue)
AdAway needs root access and the ability to modify the hosts file on the phone, which is a system protected file (for good reason). If write protection is on, then AdAway fails to modify the phone's hosts file and the ad blocking does not take place. With write protection off, AdAway is successful an my browser screen is far less cluttered when surfing.

I set the app to notify me when updates are available, but not to automatically apply the updates. Then I manually reboot to recovery and update my hosts file via AdAway. After I get the successful update I reboot normally and use my phone in the regular non-recovery mode.

Ok, but that is my point - you can do it in recovery and in fact it is safer to do it in recovery. Stock android disables write protection when you boot into recovery.
23rd February 2014, 09:08 PM   |  #4  
Senior Member
Thanks Meter: 112
 
1,045 posts
Join Date:Joined: Jun 2010
So we don't have to boot into recovery everytime we modify system.

Sent from my XT1053 using XDA Premium 4 mobile app
23rd February 2014, 09:56 PM   |  #5  
OP Account currently disabled
Thanks Meter: 89
 
423 posts
Join Date:Joined: Jan 2014
More
Quote:
Originally Posted by c19932

So we don't have to boot into recovery everytime we modify system.

Right, for convenience sake. But what I am asking is it ever necessary to have write protection disabled when you boot into system? Meaning, is there anything that you would need it for that booting into recovery to make the changes wouldn't work?
23rd February 2014, 10:06 PM   |  #6  
cartmenicus's Avatar
Recognized Contributor
Flag British columbia
Thanks Meter: 1,970
 
2,899 posts
Join Date:Joined: Nov 2011
Donate to Me
More
Quote:
Originally Posted by Cozume

Right, for convenience sake. But what I am asking is it ever necessary to have write protection disabled when you boot into system? Meaning, is there anything that you would need it for that booting into recovery to make the changes wouldn't work?

You can't make changes to the system part I on with out write protection being disabled. Jcases method is a hacked recovery that when selected from fastboot boots you into a disabled system and you make your changes then reboot normally.

Sent from my XT1058 using Tapatalk
24th February 2014, 04:29 AM   |  #7  
Senior Member
Thanks Meter: 134
 
716 posts
Join Date:Joined: Mar 2011
The only time I need write protection off is if/when I'm making changes to /system or make changes to or add an Xposed module.

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes