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

[Q] Why unlock bootloader on non DE when we have safestrap?

OP frenchie007

3rd July 2014, 11:01 AM   |  #1  
OP Senior Member
Thanks Meter: 17
 
158 posts
Join Date:Joined: Jan 2011
I've safestrapped a rooted 4.4.2 rom on my AT&T locked moto x for quite some time and I can't see any real downsides.
I even had a look to see if it's possible to flash non-stock roms with it and from what I understand it's totally possible.

So my question is: What's the point of unlocking the bootloader on non-DE devices (with, say, the chinese middleman method, which costs about 40-50$), when you can simply bypass the protected /system directory by using safestrap?

If I understand though, the only real limitation is that we have to wait for the sbf of the newer versions of android to be released for our specific device, in order to flash the correct kernels and all. I think.

Please correct my statements as they may be wrong, and thanks for your replies!
3rd July 2014, 03:05 PM   |  #2  
samwathegreat's Avatar
Senior Member
Thanks Meter: 1,774
 
2,025 posts
Join Date:Joined: Apr 2010
Donate to Me
Quote:
Originally Posted by frenchie007

I've safestrapped a rooted 4.4.2 rom on my AT&T locked moto x for quite some time and I can't see any real downsides.
I even had a look to see if it's possible to flash non-stock roms with it and from what I understand it's totally possible.

So my question is: What's the point of unlocking the bootloader on non-DE devices (with, say, the chinese middleman method, which costs about 40-50$), when you can simply bypass the protected /system directory by using safestrap?

If I understand though, the only real limitation is that we have to wait for the sbf of the newer versions of android to be released for our specific device, in order to flash the correct kernels and all. I think.

Please correct my statements as they may be wrong, and thanks for your replies!

Once you have updated your CORE SOFTWARE (and bootloader) to 4.4.2, safestrap is useless. The 4.4.2 bootloader is impervious to known write-protect-disable exploits.

Many people updated to 4.4.2 without reading the consequences and now BL unlock is the ONLY method to achieve Root AND Write-protect-disable.

Additionally, the process is much more streamlined and far less complicated than installing and configuring safestrap. Simply unlock, and flash TWRP. Done.


Also, non-stock-based ROMS (AFAIK) cannot be used with safestrap because as I understand, it uses an "overlay" technique which would not work on a non-stock-based ROM.

Good Luck
The Following User Says Thank You to samwathegreat For This Useful Post: [ View ]
3rd July 2014, 03:38 PM   |  #3  
HeroOfTime's Avatar
Senior Member
Flag Mountain Green
Thanks Meter: 30
 
148 posts
Join Date:Joined: Jun 2010
More
Quote:
Originally Posted by frenchie007

I've safestrapped a rooted 4.4.2 rom on my AT&T locked moto x for quite some time and I can't see any real downsides.
I even had a look to see if it's possible to flash non-stock roms with it and from what I understand it's totally possible.

So my question is: What's the point of unlocking the bootloader on non-DE devices (with, say, the chinese middleman method, which costs about 40-50$), when you can simply bypass the protected /system directory by using safestrap?

If I understand though, the only real limitation is that we have to wait for the sbf of the newer versions of android to be released for our specific device, in order to flash the correct kernels and all. I think.

Please correct my statements as they may be wrong, and thanks for your replies!

Also, using safestrap takes up more space on your device, since you have an underlying core OS (as samwathegreat puts it), essentially meaning that you have two full ROMs on your phone. If you have the 16gb Moto X, that will suck up a good chunk of space (though that's not the end of the world). If you have the 32gb version, you are probably ok. I agree with everything else samwathegreat says though.
The Following User Says Thank You to HeroOfTime For This Useful Post: [ View ]
3rd July 2014, 08:06 PM   |  #4  
kwyrt's Avatar
Senior Member
Flag Columbus
Thanks Meter: 205
 
690 posts
Join Date:Joined: Apr 2011
More
Thought I would add my two cents in here as someone who ran safestrap for a while before getting my bootloader unlocked through the guy in China. First, a small correction, running safestrap doesn’t have to take up much/any more memory as you can flash the ROM to your “stock” slot. As of right now I believe the other slots are not even working. Now, as for why unlock your bootloader, I think there are a number of reasons. Yes, you have an up-to-date ROM on your phone currently, but you are going to be dependent on a dev making a safestrap compatible ROM for any new software releases. This may or may not happen. You are at the mercy of the few devs who are currently doing this. That is probably the biggest reason for me deciding to unlock. Another reason, as samwathegreat stated, is I do not believe you can run AOSP ROMs currently on safestrap. If it works like it did on my old Droid 4, you would need to use something like the kexec exploit to in order to flash custom kernels in order to run an AOSP based ROM. I haven’t seen anyone working on anything like that. The last big reason I can see is safestrap does not seem to be in active development on the Moto X anymore. Numerous other devices have seen safestrap updates recently (including the Droid 4) but not so the Moto X version. I would definitely recommend unlocking. I know I’m glad I did.
The Following User Says Thank You to kwyrt For This Useful Post: [ View ]
3rd July 2014, 11:46 PM   |  #5  
HeroOfTime's Avatar
Senior Member
Flag Mountain Green
Thanks Meter: 30
 
148 posts
Join Date:Joined: Jun 2010
More
Quote:
Originally Posted by kwyrt

First, a small correction, running safestrap doesn’t have to take up much/any more memory as you can flash the ROM to your “stock” slot.

Thanks for clarifying that. I stand corrected.
4th July 2014, 01:37 PM   |  #6  
OP Senior Member
Thanks Meter: 17
 
158 posts
Join Date:Joined: Jan 2011
Thumbs up
Quote:
Originally Posted by kwyrt

Thought I would add my two cents in here as someone who ran safestrap for a while before getting my bootloader unlocked through the guy in China. First, a small correction, running safestrap doesn’t have to take up much/any more memory as you can flash the ROM to your “stock” slot. As of right now I believe the other slots are not even working. Now, as for why unlock your bootloader, I think there are a number of reasons. Yes, you have an up-to-date ROM on your phone currently, but you are going to be dependent on a dev making a safestrap compatible ROM for any new software releases. This may or may not happen. You are at the mercy of the few devs who are currently doing this. That is probably the biggest reason for me deciding to unlock. Another reason, as samwathegreat stated, is I do not believe you can run AOSP ROMs currently on safestrap. If it works like it did on my old Droid 4, you would need to use something like the kexec exploit to in order to flash custom kernels in order to run an AOSP based ROM. I haven’t seen anyone working on anything like that. The last big reason I can see is safestrap does not seem to be in active development on the Moto X anymore. Numerous other devices have seen safestrap updates recently (including the Droid 4) but not so the Moto X version. I would definitely recommend unlocking. I know I’m glad I did.

thanks for making things clearer for me, and everyone for taking the time to answer my question.
as i've got a 2013 model I guess I'll just have to hope that safestrap supported roms will keep being released for the moto x for future updates!
4th July 2014, 02:51 PM   |  #7  
Senior Member
Thanks Meter: 152
 
877 posts
Join Date:Joined: Apr 2008
OP - long story short:

locked bootloader = some dev/hobbyist, etc finding a security flaw in the system that exploits the ability to obtain root (and hopefully system r/w).
  • Requires an adoption rate from other users.
  • Is only as "reliable" as the device is relevant.
  • Exploits have the potential to insert malicious code.

unlocked bootloader/dev edition = "free range" to do whatever you want, regardless of security flaws.
  • Potential to extend the longevity of your device.
  • Rooting methods are common among most devices with DEV Edition/unlocked bootloader option.
  • Permanent.
The Following User Says Thank You to 640k For This Useful Post: [ View ]
4th July 2014, 10:11 PM   |  #8  
OP Senior Member
Thanks Meter: 17
 
158 posts
Join Date:Joined: Jan 2011
Quote:
Originally Posted by 640k

OP - long story short:

locked bootloader = some dev/hobbyist, etc finding a security flaw in the system that exploits the ability to obtain root (and hopefully system r/w).

  • Requires an adoption rate from other users.
  • Is only as "reliable" as the device is relevant.
  • Exploits have the potential to insert malicious code.

unlocked bootloader/dev edition = "free range" to do whatever you want, regardless of security flaws.
  • Potential to extend the longevity of your device.
  • Rooting methods are common among most devices with DEV Edition/unlocked bootloader option.
  • Permanent.

I am quite aware of the difference between locked and unlocked boot loaders. My question was really regarding if safe strapping offered as much as a regular recovery. But thanks for clearing that up as well!

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

Advanced Search
Display Modes