Related
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!
frenchie007 said:
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!
Click to expand...
Click to collapse
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
frenchie007 said:
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!
Click to expand...
Click to collapse
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.
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.
kwyrt said:
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.
Click to expand...
Click to collapse
Thanks for clarifying that. I stand corrected.
kwyrt said:
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.
Click to expand...
Click to collapse
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!
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.
640k said:
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.
Click to expand...
Click to collapse
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!
What are the benefits of s-off over just unlocked boot loader
by unlocking bootloader u can root ur device, can flash custom recovery & custom roms on ur android device....
shad0wboss said:
What are the benefits of s-off over just unlocked boot loader
Click to expand...
Click to collapse
I don't have this particular device but I will tell you the general information and you can work with that.
About Bootloader(Unlocked Bootloader):
The bootloader is like a BIOS of your PC. It is the thing that is powered on and verifies all hardware and is responsible for making connection with the hardware. This can either be unlocked or locked. When you have a locked bootloader you can still root (if an exploit is available). You can even install a recovery or custom rom if an exploit is available (like BUMP was). What was it doing? Signing the images for your so the locked bootloader will think it is the OEM image. In most of the cases this is not so happy. Usually you can't flash a recovery or a custom rom or stuff like that with a locked bootloader. Some OEM's provide websites to unlock the bootloader (with the cost of losing warranty; well not really). This is the case of Sony, HTC. Some Oem's don't provide this.
About S-off:
What does S-off mean? Security off. Your device will come with S-ON always unless it's a Dev edition (correct me if I am wrong). What this does is it doesn't leave you to do very advanced operations related to the EMMC (the Nand chip). You can't flash a bootloader you wish or stuff like that. Update radio partition. In some cases system partition is also secured so you can't flash a custom ROM. By S-off you get full control of your device but if a mistakes occurs you will end up with a hard-bricked device.
Peace. Hope you understood.
neutrondev said:
I don't have this particular device but I will tell you the general information and you can work with that.
About Bootloader(Unlocked Bootloader):
The bootloader is like a BIOS of your PC. It is the thing that is powered on and verifies all hardware and is responsible for making connection with the hardware. This can either be unlocked or locked. When you have a locked bootloader you can still root (if an exploit is available). You can even install a recovery or custom rom if an exploit is available (like BUMP was). What was it doing? Signing the images for your so the locked bootloader will think it is the OEM image. In most of the cases this is not so happy. Usually you can't flash a recovery or a custom rom or stuff like that with a locked bootloader. Some OEM's provide websites to unlock the bootloader (with the cost of losing warranty; well not really). This is the case of Sony, HTC. Some Oem's don't provide this.
About S-off:
What does S-off mean? Security off. Your device will come with S-ON always unless it's a Dev edition (correct me if I am wrong). What this does is it doesn't leave you to do very advanced operations related to the EMMC (the Nand chip). You can't flash a bootloader you wish or stuff like that. Update radio partition. In some cases system partition is also secured so you can't flash a custom ROM. By S-off you get full control of your device but if a mistakes occurs you will end up with a hard-bricked device.
Peace. Hope you understood.
Click to expand...
Click to collapse
Thanks!
Things is, i was more concerned about the practical info about this device specifically because I have read that with just bootloader unlocked, the roms that i'll be able to flash will only change the visual and not so much with the kernel etc. I don't understand why people would choose to S-OFF for this device for other than just relocking the bootloader.
shad0wboss said:
Thanks!
Things is, i was more concerned about the practical info about this device specifically because I have read that with just bootloader unlocked, the roms that i'll be able to flash will only change the visual and not so much with the kernel etc. I don't understand why people would choose to S-OFF for this device for other than just relocking the bootloader.
Click to expand...
Click to collapse
Sorry I can't really help you with that information I don't know if you can flash a Custom kernel with S-on. Never had a sony. Someone will help you out soon.I hope.
i'l bump this question up then :/
I think S-off is a term unique to HTC devices. Its the equivalent of an unlocked bootloader
tonysunshine said:
I think S-off is a term unique to HTC devices. Its the equivalent of an unlocked bootloader
Click to expand...
Click to collapse
yes but nth to lose on HTC except warranty (still subject to which svc ctr tho) while on Sony, losing DRM keys (w/o backup) are like downgrading ur phone full capabilities.
monx® said:
yes but nth to lose on HTC except warranty (still subject to which svc ctr tho) while on Sony, losing DRM keys (w/o backup) are like downgrading ur phone full capabilities.
Click to expand...
Click to collapse
Is there a way to root without losing keys? I have Z3 LTE D6603 atm.
Sorry if it's a dumb question, I'm new here. And also new to sony rooting, which seems much more complex than my old Nexus 5 lol
tonysunshine said:
I think S-off is a term unique to HTC devices. Its the equivalent of an unlocked bootloader
Click to expand...
Click to collapse
Not really, you can flash kernels, roms ( aosp roms etc ) with unlocked bootloader, S-off gives you other stuff like changing mid, cid, sim unlock, downgrading/upgrading bootloader, converting to full GPE or dev edition, unlocking bootloader without need of HTC, flashing splash image, custom bootloaders, even converting to Windows ( if available of course ) locking it instead of re-locking it, restoring it to full stock state ( which is not possible without S-off ), simply put your device has no limits with S-off on HTC.
Anyway S-off isn't really needed unless you care for the things above ( if Sony even has S-off ), Sony has poor development so S-off isn't even needed or unlocking bootloader since basically all you get is aosp roms, stock alike roms are flashable with locked bootloader as far as I remember.
Sent from my HTC One M8 using Tapatalk
Hello, i have a retail xt1097, its already updated to marshmallow, dont really need to be root forever but i need at least temporal root to do some one-time minor changes, such as install my desired launcher as system, led for battery, hostfile and such.
The problem is i dont want to unlock the bootloader untill warranty expires (still 7 months of warranty) so the question is if any app/exploit, can temp root this device, under MM.
*Tryed searching and i found kingoroot does the trick but im not sure if it will work on MM, i cant mess up bricking phones now because im not be able to repair them since weather its hot, people overload powerlines and electricity drops all the time and makes my pc suddently power off.
Any advice? Thanks guys
As far as I know root isn't possible with locked bootloader.
There has been quite a bit of discussion (I think most of what I read was on other forums) about Motorola's warranty policy for unlocked bootloaders: it seems that from what people have experienced they will still honor the warranty if it is strictly a hardware problem. I bought my phone used but with over a year of Moto Care remaining, which the original owner transferred to me. He (the original owner) had already unlocked the bootloader, but the Moto Care is still shown as active and valid on my account, even though I don't even have stock rom anymore. Just to be safe I would definitely (if possible) re-flash stock rom prior to making any warranty claim.
Hmm makes sense, then can i unlock BL, root, do my things, then unroot, flash stock recovery and relock? is that posible? does it need a custom kernel too? im ok with the stock rom just need few one-time tweaks...
Unless you really use Moto Voice a lot I would just install the newly released CM14.1, and if you ever need warranty work try to reflash stock beforehand. Otherwise, flash twrp, root, etc.... That is covered in the general section, probably linked to some of the stickies at the top of the page. I'm not sure if it will work for you to make system modifications and then try to relock bootloader. I think part of relocking the bootloader includes flashing the stock rom, which would undo any changes you have made.
Okay, so I may ask quite a dumb question, because I do not want to proceed to soft/hard brick my device
but I am not too dumb, So far I have rooted and flash many sony devices and one Asus + Mi device
I did research on HTC, learned about S-off, will be glad to google futher or watch youtube vid that is not in english to follow/learn the correct way
So just that It won't be hard to explain me
Just that, I have HTC Desire 626s T-Mobile device,
and it is sim locked, But bootloader unlocked,
What I want end result is, I prefer having a custom rom, with google play compatibility and without bloatware, so maybe CM roms are best, with root functionality, and I do not care much about Security, but keeping it off seems better,
There are just soo many tools out there, to unlock boot loader, flash twrp, and ROMs
So I'm confused, as some threads have title like for AT&T, Sprint, I don't know if those will work for me, if I flash/follow Sprint's instruction for T-Mobile device that I own, I may end up bricking a device which is not much in development right now
So is there any proper way/thread/method/video/guide I may follow from start to end with either custom or stock(with bloatwares removed) ROM with SIm Unlocked, S-off, and Root
Can you simply explain what are advantages by unlocking the bootloader, waiting 14 days (why 14?) ?
I just wanted to replace the stock Android 7 with Oreo 8, but in most of the guides it looks like the boot loader must be unlocked.
Can one explain to me the technical reason for that?
Thnx
The bootloader must be unlocked so you can flash recovery and do a lot from there. The main reason you'd want it unlocked is for root or custom roms, or even Android P semi GSI
_Hinnie_ said:
The bootloader must be unlocked so you can flash recovery and do a lot from there. The main reason you'd want it unlocked is for root or custom roms, or even Android P semi GSI
Click to expand...
Click to collapse
Thank you Hinnie,
so far as I understand, if I would use a custom rom, the bootloader unlocked is mandatory...
But why one need to wait for 14 days?
The 14 days time is from Lenovo itself. Every company has different policy in terms of deciding duration for unlocking bootloader.
_maxim_ said:
Thank you Hinnie,
so far as I understand, if I would use a custom rom, the bootloader unlocked is mandatory...
But why one need to wait for 14 days?
Click to expand...
Click to collapse
So, that the user has the option to cancel the process of unlocking, in these 14 days.
It's for safety purpose, coz once the bootloader is unlocked, one can customise (or destroy) everything from system files to IMEI to making phone a brick.
With great power comes great responsibilities
So, there are various pros & cons of unlocking bootloader.
But, nothing will be damaged until you follow the steps or guidelines provided for the various processes. Just read & read & implement once you are almost 90% sure that it will not harm your data or device.
And most important always remember to keep backups
Happy Flashing !!