Related
Can the Moto X bootloader be unlocked? I ask this because from what I understand (correct me if I'm wrong), the bootloader must be unlocked in order to flash custom ROMs. Also, I'm aware that there's a Developer Edition of the Moto X that has an unlocked bootloader. This question is for the standard Moto X, not the Developer Edition. Thanks!
- Shadowz1218
Shadowz1218 said:
Can the Moto X bootloader be unlocked? I ask this because from what I understand (correct me if I'm wrong), the bootloader must be unlocked in order to flash custom ROMs. Also, I'm aware that there's a Developer Edition of the Moto X that has an unlocked bootloader. This question is for the standard Moto X, not the Developer Edition. Thanks!
- Shadowz1218
Click to expand...
Click to collapse
AFAIK, there are some models can not be bootloader unlocked, the AT&T, Verizon, Nextel Mexico. Others are bootloader unlockable.
yghrv said:
AFAIK, there are some models can not be bootloader unlocked, the AT&T, Verizon, Nextel Mexico. Others are bootloader unlockable.
Click to expand...
Click to collapse
Unfortunately, I have Verizon Wireless. I was originally planning on switching carriers in order to get a Nexus 5, but when I heard about the Moto X being $150 off for Cyber Monday, I thought I'd look into it. Must you have an unlocked bootloader in order to flash a custom ROM or can it still be done? The ability to flash a custom ROM is a must have for me.
Shadowz1218 said:
Unfortunately, I have Verizon Wireless. I was originally planning on switching carriers in order to get a Nexus 5, but when I heard about the Moto X being $150 off for Cyber Monday, I thought I'd look into it. Must you have an unlocked bootloader in order to flash a custom ROM or can it still be done? The ability to flash a custom ROM is a must have for me.
Click to expand...
Click to collapse
Well, in order to flash a ROM, you'll need to have a recovery capable of doing so. In order to flash a recovery, you'll need an unlocked bootloader. Ergo...
The only reason bootloaders get unlocked is so that custom recoveries can be installed. Not just to flash, but also for backing up. Stock recovery doesn't really do anything but factory reset.
Shadowz1218 said:
Unfortunately, I have Verizon Wireless. I was originally planning on switching carriers in order to get a Nexus 5, but when I heard about the Moto X being $150 off for Cyber Monday, I thought I'd look into it. Must you have an unlocked bootloader in order to flash a custom ROM or can it still be done? The ability to flash a custom ROM is a must have for me.
Click to expand...
Click to collapse
rockingondrums said:
Well, in order to flash a ROM, you'll need to have a recovery capable of doing so. In order to flash a recovery, you'll need an unlocked bootloader. Ergo...
The only reason bootloaders get unlocked is so that custom recoveries can be installed. Not just to flash, but also for backing up. Stock recovery doesn't really do anything but factory reset.
Click to expand...
Click to collapse
You can root and flash roms without an unlocked bootloader. Look at the Development thread, there are root/recovery options for 4.2.2 and 4.4. There isn't much development happening. If anything we're probably going to get stock based roms for the most part.
Shadowz1218 said:
Unfortunately, I have Verizon Wireless. I was originally planning on switching carriers in order to get a Nexus 5, but when I heard about the Moto X being $150 off for Cyber Monday, I thought I'd look into it. Must you have an unlocked bootloader in order to flash a custom ROM or can it still be done? The ability to flash a custom ROM is a must have for me.
Click to expand...
Click to collapse
Out of curiosity, why is the ability to flash a custom ROM a must-have? I felt that way at first, but many Moto X users (including myself) now believe that a combination of root, Xposed and GravityBox is enough.
Shadowz1218 said:
Unfortunately, I have Verizon Wireless. I was originally planning on switching carriers in order to get a Nexus 5, but when I heard about the Moto X being $150 off for Cyber Monday, I thought I'd look into it. Must you have an unlocked bootloader in order to flash a custom ROM or can it still be done? The ability to flash a custom ROM is a must have for me.
Click to expand...
Click to collapse
Then get a VZW developer edition.
chaoslimits said:
You can root and flash roms without an unlocked bootloader. Look at the Development thread, there are root/recovery options for 4.2.2 and 4.4. There isn't much development happening. If anything we're probably going to get stock based roms for the most part.
Click to expand...
Click to collapse
Well I know root is certainly possible, but how do you flash a rom on the Moto X without using a recovery such as CWM or TWRP?
rockingondrums said:
Well I know root is certainly possible, but how do you flash a rom on the Moto X without using a recovery such as CWM or TWRP?
Click to expand...
Click to collapse
safestrap.
charlie-n said:
safestrap.
Click to expand...
Click to collapse
There's no safestrap for 4.4 yet, correct?
Sent from my XT1060 using xda app-developers app
You can try root http://forum.xda-developers.com/showthread.php?t=2538896
Sent from my XT1060 using XDA Premium 4 mobile app
charlie-n said:
safestrap.
Click to expand...
Click to collapse
But isn't safestrap that weird hack that leaves the original system alone and just sticks another install on the device? I wanted to get a vzw S4 until I learned I'd be stuck with the original bloated OS installed along the one I want (if I'm understanding it correctly)
rockingondrums said:
But isn't safestrap that weird hack that leaves the original system alone and just sticks another install on the device? I wanted to get a vzw S4 until I learned I'd be stuck with the original bloated OS installed along the one I want (if I'm understanding it correctly)
Click to expand...
Click to collapse
Pretty much
sent by wireless transmission
charlie-n said:
safestrap.
Click to expand...
Click to collapse
If you can flash a custom ROM with said "safestrap," what's the point of having an unlocked bootloader? What can you do with an unlocked bootloader that you can't do without one?
Shadowz1218 said:
If you can flash a custom ROM with said "safestrap," what's the point of having an unlocked bootloader? What can you do with an unlocked bootloader that you can't do without one?
Click to expand...
Click to collapse
You can flash other versions on your phone. I unlocked my bootloader and flashed the Verizon version, just because. I came from a Latin American version of the phone.
RagnaParadise said:
You can flash other versions on your phone. I unlocked my bootloader and flashed the Verizon version, just because. I came from a Latin American version of the phone.
Click to expand...
Click to collapse
I don't quite understand what you mean by "flashing other versions on your phone." My question is what's the advantage of having an unlocked bootloader. Also, are there any disadvantages of flashing a custom ROM with a safestrap?
Shadowz1218 said:
I don't quite understand what you mean by "flashing other versions on your phone." My question is what's the advantage of having an unlocked bootloader. Also, are there any disadvantages of flashing a custom ROM with a safestrap?
Click to expand...
Click to collapse
Normally, it's to allow you to flash a custom recovery, so that you can flash the plethora of zips you can find. The disadvantage with safestrap is what I said above: It's a hack that leaves the original OS on the phone, just sitting there taking up space. You know how the S4's only came with 9 GBs free on the 16 GBs? Well, if I bought a verizon one, I'd have to safestrap CM or whatever on to the phone, so I'd be left with the original TW hog and then lose more space to CM. I mean, if you can deal with that then you're golden. But it is still a disadvantage. And I wouldn't do it (which is why I ended up not buying the S4, even though I really wanted it).
rockingondrums said:
Normally, it's to allow you to flash a custom recovery, so that you can flash the plethora of zips you can find. The disadvantage with safestrap is what I said above: It's a hack that leaves the original OS on the phone, just sitting there taking up space. You know how the S4's only came with 9 GBs free on the 16 GBs? Well, if I bought a verizon one, I'd have to safestrap CM or whatever on to the phone, so I'd be left with the original TW hog and then lose more space to CM. I mean, if you can deal with that then you're golden. But it is still a disadvantage. And I wouldn't do it (which is why I ended up not buying the S4, even though I really wanted it).
Click to expand...
Click to collapse
So if I want to replace the original OS with another ROM I'd have no choice but to unlock the bootloader and use a custom recovery? Also, is it possible that an OTA update could break the safestrap, or stop it from working anymore?
Ok, rather than this unnecessary back and forth, if you have Verizon and "flashing custom ROMS is a must for me" like you say then just get the Verizon Developer Edition which has an unlocked bootloader and be done with it.
LordLugard said:
Ok, rather than this unnecessary back and forth, if you have Verizon and "flashing custom ROMS is a must for me" like you say then just get the Verizon Developer Edition which has an unlocked bootloader and be done with it.
Click to expand...
Click to collapse
I was simply trying to understand if there's any practical advantage of having an unlocked bootloader vs. using other methods such as a safestrap. If I can get a custom Moto X at a discounted price on a 2-year contract, I'd much rather go that route instead of paying the retail price for a Developer Edition.
Due to some work-related reason, I can't have a rooted Moto X.
I start to think about what I can do without root. If I understand it correctly, if I have an unlocked boot-loader, I will be able to install TWRP and flash the apps that need the root access. Is this true?
If so, is hashcode's safestrap a viable option? Yes I'd have to waste some space. But the ROM slot I added will be essentially flash-able via TWRP.
Can anyone comment if this will work?
Thanks
AT&T Moto X's cannot be bootloader unlocked.
The idea of SafeStrap, I think, is to create another slot. This does not require an unlocked boot-loader, does it?
Okay, got a strange question here. I plan on going from the N5 to the unlocked GSM MotoMaker Moto X version. All I want is root with stock recovery (don't really care for a custom recovery, plus I'd like to still receive OTAs). Can I unlock the Moto X bootloader, load TWRP recovery (instead of flash), and then install SuperSU? Or do I *have* to flash TWRP to achieve root?
correct me if im wrong, but I think you can "unlock the Moto X bootloader, load TWRP recovery (instead of flash), and then install SuperSU".
or
use one of the methods in the original android development section to achieve root.
c19932 said:
correct me if im wrong, but I think you can "unlock the Moto X bootloader, load TWRP recovery (instead of flash), and then install SuperSU".
or
use one of the methods in the original android development section to achieve root.
Click to expand...
Click to collapse
Yes, I've looked at those threads. However, in 4.4, a backdoor needs to be introduced in order to maintain root. I'd rather not have to do that and I don't mind unlocking bootloaders. This will be my first, non-Nexus device in awhile, so I just wanted to make sure I can just unlocked the bootloader, load a custom recovery, flash SuperSU and then just have root.
TheCuban said:
Yes, I've looked at those threads. However, in 4.4, a backdoor needs to be introduced in order to maintain root. I'd rather not have to do that and I don't mind unlocking bootloaders. This will be my first, non-Nexus device in awhile, so I just wanted to make sure I can just unlocked the bootloader, load a custom recovery, flash SuperSU and then just have root.
Click to expand...
Click to collapse
Just unlock your boot loader, flash twrp recovery and finally flash supersu and you're good to go. Ota's can not be accepted and flashed with root or custom recovery on the moto
Sent on my Moto X
flashallthetime said:
Just unlock your boot loader, flash twrp recovery and finally flash supersu and you're good to go. Ota's can not be accepted and flashed with root or custom recovery on the moto
Sent on my Moto X
Click to expand...
Click to collapse
Thanks! That's what I thought! I didn't know that root removed the ability to accept OTAs?
TheCuban said:
Thanks! That's what I thought! I didn't know that root removed the ability to accept OTAs?
Click to expand...
Click to collapse
On the moto yes, nexus devices are a different beast
Sent on my Moto X
Hi I am planing my first root and I am honestly a little confused. I am on TMobile with 4.4 KitKat (Moto X).
I understand how to unlock the Bootloader and that I need to install TWRP before I can activate SU.
I am just not sure about the bugs (if any) with TWRP and what version to use.
The reason for my concern is on the TWRP website the Moto X is not listed as a supported device.
Is this video Tutorial still valid - is this how to do it with 4.4 KitKat?
And is this the latest version that works (what are the known bugs)?
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!
I had a Moto X that I unlocked via the China seller, and it's being replaced because it's bricked. is there a way to put roms on a locked device? or can I unlock the bootloader again for cheap? I paid roughly 40 dollars for it last time.
jcase has a thread for using an exploit to root your phone without unlocking the bootloader. It can be found here:
http://forum.xda-developers.com/moto-x/orig-development/root-write-protection-bypass-motox-t2444957
NOTE: Please read the entire jcase link so you understand the risk/process!
Is there a reason why you want a custom ROM? It's certainly your choice, and respectable but if you're looking for minor tweaks to make it look different you may just want to try the GravityBox module with the Xposed Framework. That way you can just worry about rooting your phone, and then tweaking everything else to your liking after that.
I enjoy PA pie along with halo, PA has the best pie controls in my opinion. So it seems they sent me a moto x on 4.4.2, is my only option pie root than using safestrap? Or what is the best way to go about putting a ROM on this?
ovismos said:
jcase has a thread for using an exploit to root your phone without unlocking the bootloader. It can be found here:
http://forum.xda-developers.com/moto-x/orig-development/root-write-protection-bypass-motox-t2444957
NOTE: Please read the entire jcase link so you understand the risk/process!
Is there a reason why you want a custom ROM? It's certainly your choice, and respectable but if you're looking for minor tweaks to make it look different you may just want to try the GravityBox module with the Xposed Framework. That way you can just worry about rooting your phone, and then tweaking everything else to your liking after that.
Click to expand...
Click to collapse
^^^
scottshebs said:
^^^
Click to expand...
Click to collapse
You'll need a way to get a custom recovery running to install the ROM. TBH, I have a Dev Edition VZW Moto X, so all I do is unlock my bootloader.
Having that being said it looks (from what I read!) like Safestrap allows you to use a custom recovery, in addition of making nandroids and such. From what you're telling me, it pretty much looks like the way to go.
ovismos said:
You'll need a way to get a custom recovery running to install the ROM. TBH, I have a Dev Edition VZW Moto X, so all I do is unlock my bootloader.
Having that being said it looks (from what I read!) like Safestrap allows you to use a custom recovery, in addition of making nandroids and such. From what you're telling me, it pretty much looks like the way to go.
Click to expand...
Click to collapse
Would the 4.4.2 pie root work? It says it does not disable write protection and it is a tethered root.
Right. And safestrap won't work on 4.4.2.
So no, unless you unlock the bootloader again, you won't be able to flash a custom rom or recovery unfortunately.
scottshebs said:
Would the 4.4.2 pie root work? It says it does not disable write protection and it is a tethered root.
Click to expand...
Click to collapse
It doesn't look like it.
http://forum.xda-developers.com/moto-x/moto-x-qa/att-moto-x-rooting-long-term-effects-t2854742
From KidJoe in that post:
"As for safestrap, I don't use it since I have a Dev Edition and unlocked my bootloader. There are some threads and discussions over on Rootzwiki.com BUT you will need to be rooted with write protection disabled to use SafeStrap... Since you are now on 4.4.2, you can't disable write protection, so safestrap is out. "
So I think customer recovery is out unless you get a bootloader unlocked. And without custom recovery, you wouldn't be able to do a custom ROM.
You can still root the stock ROM though! That's what the PIE method will do. Don't think that will give you custom recovery.
Also, you want TowelPieRoot. Not either individually. That will give you root, but not disabled write protection. So mostly it's only useful for certain apps to be used.
KJ said:
Right. And safestrap won't work on 4.4.2.
So no, unless you unlock the bootloader again, you won't be able to flash a custom rom or recovery unfortunately.
Click to expand...
Click to collapse
Beat me to it.
ovismos said:
Beat me to it.
Click to expand...
Click to collapse
So I'm basically ****ed. Any possible way to downgrade to 4.4?
KJ said:
Also, you want TowelPieRoot. Not either individually. That will give you root, but not disabled write protection. So mostly it's only useful for certain apps to be used.
Click to expand...
Click to collapse
scottshebs said:
So I'm basically ****ed. Any possible way to downgrade to 4.4?
Click to expand...
Click to collapse
Downgrading is a dangerous thing on the X... It can easily end up in a brick, or other issues... Or a brick later.
No one who knows how this phone works ever recommends downgrading.
So no.... You are out of luck right now.
You can try the Middleman again... Or wait for a Possible exploit maybe being released, sometime.
But most advise not to upgrade either until this exploit that maybe will come out comes out. In vase 4.4.4 is incompatible with it.
It will also cost you money though.
---------- Post added at 03:17 PM ---------- Previous post was at 03:11 PM ----------
BTW, mixing the dangerous on its own downgrading with slapmymoto and safestrap is a definite recipe for disaster.
scottshebs said:
So I'm basically ****ed. Any possible way to downgrade to 4.4?
Click to expand...
Click to collapse
Not the parts that matter when it comes to disabling write protection on a locked boot loader phone, and certainly not safely for the rest of the Roms.
Rather than retype...
KidJoe said:
No.
For ALL Developer Editions Moto X, and some carrier editions (Like T-Mobile, Sprint, Rogers and others), Motorola freely gives away the BootLoader Unlock codes when requested On Motorola's Web SIte. In the case of the Non-Developer Editions, it voids their warranty to request the code. However, for some carriers (like ATT, Verizon and republic Wireless in the USA) motorola does not give out the unlock code.
So when you get your X, try to get the unlock code from Moto's web site. Then....
If you can get the code, and unlock the bootloader, you can root and disable write protection no matter what ROM is on your phone.
If you can NOT unlock your bootloader, and you are on 4.4.2 you can use TowelPieRoot to root (but write protection is still enabled).
If you can NOT unlock your bootloader, and your are on 4.4.4 you can not root.
If you can NOT unlock your bootloader, and by some miracle your phone is still on 4.4 (aka 4.4.0) or below, you can look at SlapMyMoto and MotoWpNoMo to root and disable write protection. HOWEVER, once you upgrade you will lose write protection, and be subject to the above conditions on rooting depending on your ROM version
And no, if you are on 4.4.4 you can NOT fully downgrade to 4.4.2 or lower. If you are on 4.4.2 you can NOT fully downgrade to 4.4 (aka 4.4.0) or lower! If you try, you will likely brick your phone or set it up to brick with future OTA's.
EDIT: And if Moto's web site doesn't give out your bootloader unlock code, you MIGHT have a chance using the China Middleman (see the thread in the general section). If its available and you can purchase that way, you can then unlock your bootloader exactly as if you got the code from Moto's own web site and follow any instructions as if you got the code from moto. The only difference is where you got the code, and how much it cost.
If you decide to go the China Middleman route, see -> http://forum.xda-developers.com/moto-x/general/china-middleman-t2751177/post52648309
Click to expand...
Click to collapse
oh and about safestrap, it needs write protection disabled to install. Something that can only be done on 4.4.0 and 4.2.2 with camera fix Roms if you have a locked boot loader
KidJoe said:
Not the parts that matter when it comes to disabling write protection on a locked boot loader phone, and certainly not safely for the rest of the Roms.
Rather than retype...
oh and about safestrap, it needs write protection disabled to install. Something that can only be done on 4.4.0 and 4.2.2 with camera fix Roms if you have a locked boot loader
Click to expand...
Click to collapse
****
So if I towelpieroot I could use xposed for the time being?
scottshebs said:
****
So if I towelpieroot I could use xposed for the time being?
Click to expand...
Click to collapse
Seems people have trouble getting Xposed to work. Read through that thread about it.