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.
Hi, maybe a noob question but, ever since I rooted my Moto X I cannot enter recovery mode. I believe that when the phone reboots on recovery mode it mounts /system as writable, but I wonder if there's a way to enter recovery mode at all after rooting. I have a locked bootloader on 4.2.2.
detesto said:
Hi, maybe a noob question but, ever since I rooted my Moto X I cannot enter recovery mode. I believe that when the phone reboots on recovery mode it mounts /system as writable, but I wonder if there's a way to enter recovery mode at all after rooting. I have a locked bootloader on 4.2.2.
Click to expand...
Click to collapse
yea you can still boot into stock recovery. just boot to the bootloader via volume down + power, then hit the volume down button only till you select recovery then hit volume up. and there is the stock recovery. enjoy.
You'd have to flash back to the stock recovery. However, I think you lose access to a writable system which leads to setting write protection off for good.
nhizzat said:
You'd have to flash back to the stock recovery. However, I think you lose access to a writable system which leads to setting write protection off for good.
Click to expand...
Click to collapse
i know for a fact you can enter the stock recovery after you root your device. i have done it many times before i flashed TWRP over my stock recovery
also when you root 4.4 you dont change the stock recovery so you should still be able to enter it.
That only applies if you have a Dev Edition or an unlocked bootloader.
nhizzat said:
That only applies if you have a Dev Edition or an unlocked bootloader.
Click to expand...
Click to collapse
well you learn something new every day.
did not know that having a unlocked bootloader would change if you could enter stock recovery after root or not.
thank you for the information.
guess i should of played around with the rooting and stuff before i unlocked my bootloader so i had some more knowledge on locked bootloader processes
nhizzat said:
You'd have to flash back to the stock recovery. However, I think you lose access to a writable system which leads to setting write protection off for good.
Click to expand...
Click to collapse
That's what I was thinking, when I enter to fastboot and select recovery, it just boots to system. I guess I should unlock the bootloader then, I feel a little paranoid not having recovery
detesto said:
That's what I was thinking, when I enter to fastboot and select recovery, it just boots to system. I guess I should unlock the bootloader then, I feel a little paranoid not having recovery
Click to expand...
Click to collapse
depending on what carrier your device is with depends on if you can unlock the bootloader or not.
if you cant unlock it then you can use safestrap here is the link
http://rootzwiki.com/topic/104161-recovery-locked-safestrap-recovery-v365-2013-11-13/
dray_jr said:
depending on what carrier your device is with depends on if you can unlock the bootloader or not.
if you cant unlock it then you can use safestrap here is the link
http://rootzwiki.com/topic/104161-recovery-locked-safestrap-recovery-v365-2013-11-13/
Click to expand...
Click to collapse
I can unlock, I'm on telcel (Mexico) and I already checked the motorola web site. It's just that reading motorola saying I will no longer have warranty is a little harsh and I tried postponing unlocking it as long as I could (or at least until there's a ROM that catches my eye).
I looked into safestrap but it seems not many ROMS support this yet, or am I in the wrong here?
detesto said:
I can unlock, I'm on telcel (Mexico) and I already checked the motorola web site. It's just that reading motorola saying I will no longer have warranty is a little harsh and I tried postponing unlocking it as long as I could (or at least until there's a ROM that catches my eye).
I looked into safestrap but it seems not many ROMS support this yet, or am I in the wrong here?
Click to expand...
Click to collapse
rooting your phone removes stock recovery. it actually hijacks the stock recovery. it is part of the exploit giving you root. SS has worked on many devices even tho it may not say that it is supported. hashcode might be able to change something in SS to make it more compatible for your device if it isn't already.
detesto said:
I can unlock, I'm on telcel (Mexico) and I already checked the motorola web site. It's just that reading motorola saying I will no longer have warranty is a little harsh and I tried postponing unlocking it as long as I could (or at least until there's a ROM that catches my eye).
I looked into safestrap but it seems not many ROMS support this yet, or am I in the wrong here?
Click to expand...
Click to collapse
Technically, you already lost your warranty by rooting the phone. If you can unlock your bootloader, do it. That alone will save your ass more than a custom recovery.
I am running a Verizon Moto X still on 4.2.2. I am rooted. This is NOT the Dev edition. I have plenty of experience with rooting/flashing these phones so back when I first got it the directions on rooting/flashing roms was VERY vague. No one specified you needed the Dev edition to unlock the boot loader. Well I think this came from at one point when I tried to flash TWRP (maybe). Either way, I want to take the OTA update and cannot. Does anyone know how to fix this without doing the RSD, reflash stock method? Here is a picture of what it looks like (thanks for your help in advance):
You should check out the 'Chinese Middleman' thread. If you get the bootloader unlocked you should be able to fix anything.
I can't unlock the bootloader since this is not a Dev edition. Unless something has changed, I'll check it.
You should be able to unlock the boot loader but will not have warranty.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my XT1053 using Tapatalk
shamelin73 said:
You should be able to unlock the boot loader but will not have warranty.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
Even though it's not a Dev edition?
Yes you should be able too.
Sent from my XT1053 using Tapatalk
danman421 said:
Even though it's not a Dev edition?
Click to expand...
Click to collapse
All XT1053s can be unlocked, yes. Additionally, if you follow my advice, you don't NEED to unlock. If one of the commands fails, simply skip to the next as I previously advised, and TRY flashing with RSD Lite after you have run the commands I listed.
If you want to check and make sure fastboot is working, type:
fastboot devices
if you see your phone and it's serial number listed, you fastboot IS properly communicating with your phone.
You do not need to unlock your BL to do any of this...but if you are interested in ROOTING, you will need to.
All I really want to do is make it so my phone can take the update and any future updates. What do you mean as you previously stated?
shamelin73 said:
You should be able to unlock the boot loader but will not have warranty.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
I tried this as I did before and I get "your device does not qualify for bootloader unlocking". All I need to know is how to fix this from someone.
danman421 said:
All I really want to do is make it so my phone can take the update and any future updates. What do you mean as you previously stated?
Click to expand...
Click to collapse
I confused you with a member I had helped previously - sorry. Please disregard the "previously stated" comment.
danman421 said:
I tried this as I did before and I get "your device does not qualify for bootloader unlocking". All I need to know is how to fix this from someone.
Click to expand...
Click to collapse
It does NOT require unlocking the bootloader to flash your carrier's correct ROM. Simply follow the instructions in the "Return to 100% Stock" thread to flash the XT1053 ROM, and you'll be able to take all future updates.
If you DO unlock the bootloader, flash custom recovery, and root your device, you will have to un-do any modifications made before EVERY OTA. If you don't care about root, don't worry about unlocking.
Additionally, if you DO want to unlock, you could try a different browser and make sure you are inputting the unlock data correctly. It is recommended that you copy the unlock data from the command prompt to notepad, remove all spaces and bootloader messages (you ONLY want the code - as one complete string), then copy from notepad into the Unlock website.
And finally, keep in mind that unless you unlock your BL, you will not be able to root and disable write-protect once you update to the latest version.
The real problem here is that you use an "Exploit" to root your device previously. Now you need to return to full stock to restore your partitions to their factory state.
Simply follow the instructions in the Return to stock thread (in general sub-forum), and be sure to flash the LATEST version for your carrier. It should be 4.4.3.
Good Luck.
samwathegreat said:
I confused you with a member I had helped previously - sorry. Please disregard the "previously stated" comment.
It does NOT require unlocking the bootloader to flash your carrier's correct ROM. Simply follow the instructions in the "Return to 100% Stock" thread to flash the XT1053 ROM, and you'll be able to take all future updates.
If you DO unlock the bootloader, flash custom recovery, and root your device, you will have to un-do any modifications made before EVERY OTA. If you don't care about root, don't worry about unlocking.
Additionally, if you DO want to unlock, you could try a different browser and make sure you are inputting the unlock data correctly. It is recommended that you copy the unlock data from the command prompt to notepad, remove all spaces and bootloader messages (you ONLY want the code - as one complete string), then copy from notepad into the Unlock website.
And finally, keep in mind that unless you unlock your BL, you will not be able to root and disable write-protect once you update to the latest version.
The real problem here is that you use an "Exploit" to root your device previously. Now you need to return to full stock to restore your partitions to their factory state.
Simply follow the instructions in the Return to stock thread (in general sub-forum), and be sure to flash the LATEST version for your carrier. It should be 4.4.3.
Good Luck.
Click to expand...
Click to collapse
So if I am reading this correctly, there is no way to keep all of my data and take the update?
danman421 said:
So if I am reading this correctly, there is no way to keep all of my data and take the update?
Click to expand...
Click to collapse
You can attempt to, by either editing the XML in the SBF and removing the line that says "erase userdata", or by skipping the erase userdata if you use the manual method, but either way CAN mess everything up.
You used an EXPLOIT previously. Any time you use an exploit, you should -expect- to have to wipe everything and re-install from scratch if you want to get back to stock in order to be able to take updates. Keep this in mind if you use any exploits in the future.
Hi! This hasn't seemed to spelled out yet..... But many Moto x's can be unlocked, not just dev editions. However, you stated in the opening post that you have a Verizon Non dev, which can not be unlocked. Only way is to pay the "China middleman" (See thread in general with that name).
And personally.... I would stay on 4.2.2 and do the Slapmymoto method to get root and write protection disabled. That is the best root scenario, aside from unlocking the bootloader.
If you update to 4.4.2 or higher, you will have write protection enabled always, and no root, or sorta root with towelroot and pie. But that will limit what you can do.
See the How do I root my phone sticky thread in general for your options.
I should have posted earlier. I ran RSDLite and put the newest version on. I am unrooted. My Moto X is a Sept '13 version the the middleman probably wont work anyways. Its not worth it with this phone, im tired of the rooting, I guess im at that point in my life... Thanks for all your help though guys!
danman421 said:
I am running a Verizon Moto X still on 4.2.2. I am rooted. This is NOT the Dev edition. I have plenty of experience with rooting/flashing these phones so back when I first got it the directions on rooting/flashing roms was VERY vague. No one specified you needed the Dev edition to unlock the boot loader. Well I think this came from at one point when I tried to flash TWRP (maybe). Either way, I want to take the OTA update and cannot. Does anyone know how to fix this without doing the RSD, reflash stock method? Here is a picture of what it looks like (thanks for your help in advance):
Click to expand...
Click to collapse
Pardon my jumping in here late but..
I see a big issue here.
Based on that screen shot, you have boot loader 30.B4, that is NOT the bootloader that comes wtih 4.2.2. Did you mean to type 4.4.2? or do you really have 4.2.2 on there?
If you really had 4.2.2 on your phone with a 30.B4 bootloader, then you had 4.4.2 on there at one point, and downgraded!! You need to be REALLY CAREFUL or you will brick your phone.
You are correct, I was on 4.4.2. My wife's S4 that I just upgraded was on 4.2.2. Sorry for the confusion.
KidJoe said:
Pardon my jumping in here late but..
I see a big issue here.
Based on that screen shot, you have boot loader 30.B4, that is NOT the bootloader that comes wtih 4.2.2. Did you mean to type 4.4.2? or do you really have 4.2.2 on there?
If you really had 4.2.2 on your phone with a 30.B4 bootloader, then you had 4.4.2 on there at one point, and downgraded!! You need to be REALLY CAREFUL or you will brick your phone.
Click to expand...
Click to collapse
Good catch! ?
OP... Perhaps full disclosure of what you have done on the phone would help.
Or is that how it was?
If it's been downgraded to 4.2.2 after being on 4.4.2... As said above.... You could brick now... Especially if you OTA.
I'd tread lightly at this point.
danman421 said:
You are correct, I was on 4.4.2. My wife's S4 that I just upgraded was on 4.2.2. Sorry for the confusion.
Click to expand...
Click to collapse
so based on post # 14 of this post... it appears you are all good now? is that the case? Or do you still need help?
Oh, and if your bootloader is locked (Verizon non-DE), you can't get code from China Middle man, and you are on 4.4.2, you could try TowelPieRoot for rooting, but write protection is enabled so it will be kind of limited (compared to SlapMyMoto/MotoWPNoMO or if you had an unlocked bootloader), and there is no root for 4.4.4.
Yes, that was a good catch. What I did was RSD Lite to 4.4.4 now which reset all my data.
KidJoe said:
so based on post # 14 of this post... it appears you are all good now? is that the case? Or do you still need help?
Oh, and if your bootloader is locked (Verizon non-DE), you can't get code from China Middle man, and you are on 4.4.2, you could try TowelPieRoot for rooting, but write protection is enabled so it will be kind of limited (compared to SlapMyMoto/MotoWPNoMO or if you had an unlocked bootloader), and there is no root for 4.4.4.
Click to expand...
Click to collapse
Correct, I do not need help anymore but thank you.
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.
I looked on Cyanogenmod's website below:
https://download.cyanogenmod.org/?device=shamu
and it just has 1 ROM for Nexus 6. I have Nexus 6 for Sprint. Is there only 1 version of the ROM that works for all carriers ?
My old Galaxy S4 has many different builds for Sprint, ATT, Verizon, etc.... wasn't sure if Nexus has the same set up.
Yes, applies to all N6 variants.
thats because every sgs4 has a different setup for different carriers. we only have one nexus 6, and its the same for every carrier.
simms22 said:
thats because every sgs4 has a different setup for different carriers. we only have one nexus 6, and its the same for every carrier.
Click to expand...
Click to collapse
I didn't have a locked bootloader with Sprint Galaxy S4. If I were to restore the Nexus 6 back to stock to do an OTA update to update everything, then re-root and put a new custom ROM does the bootloader need to be re-locked, or can the factory .img be suffice to do an OTA ?
I'm still trying to learn how to do this as it is much different than the Samsung GS4. I saw there is a Nexus Toolkit by wug fresh. Is there any benefit to doing these processes by adb vs just using this progra which seems easier ?
mikeprius said:
I didn't have a locked bootloader with Sprint Galaxy S4. If I were to restore the Nexus 6 back to stock to do an OTA update to update everything, then re-root and put a new custom ROM does the bootloader need to be re-locked, or can the factory .img be suffice to do an OTA ?
I'm still trying to learn how to do this as it is much different than the Samsung GS4. I saw there is a Nexus Toolkit by wug fresh. Is there any benefit to doing these processes by adb vs just using this progra which seems easier ?
Click to expand...
Click to collapse
you dont use adb for it, you use fastboot. and doung it right vs a toolkit.. toolkits dont teach you anything, and can mess things up.
simms22 said:
you dont use adb for it, you use fastboot. and doung it right vs a toolkit.. toolkits dont teach you anything, and can mess things up.
Click to expand...
Click to collapse
Does the bootloader need to be locked to do OTAs or does the stock ROM with leaving the bootloader unlock suffice for an OTA ?
mikeprius said:
Does the bootloader need to be locked to do OTAs or does the stock ROM with leaving the bootloader unlock suffice for an OTA ?
Click to expand...
Click to collapse
bootloader can be locked or unlocked, it doesnt matter. but i recommend that you keep it unlocked forever, as it can save your phone in certain situations. and having it locked can be the end of your device, in the same situations.
simms22 said:
bootloader can be locked or unlocked, it doesnt matter. but i recommend that you keep it unlocked forever, as it can save your phone in certain situations. and having it locked can be the end of your device, in the same situations.
Click to expand...
Click to collapse
Ok. That's what I was planning on doing once it becomes unlocked. I was going to have it set like my previous GS4 and just toggle custom ROMs from there. When you mention having it locked, are you referring to when people have re-locked the bootloader then had an error flashing the stock custom ROM thus bricking the phone ? That's what worries me. Looks like the security is more stringent on the new Nexus vs. older versions.
mikeprius said:
Ok. That's what I was planning on doing once it becomes unlocked. I was going to have it set like my previous GS4 and just toggle custom ROMs from there. When you mention having it locked, are you referring to when people have re-locked the bootloader then had an error flashing the stock custom ROM thus bricking the phone ? That's what worries me. Looks like the security is more stringent on the new Nexus vs. older versions.
Click to expand...
Click to collapse
i was actually refering to it because of the unlock setting that has to be ticked to unlock. some stock users got caught in a bootloop, then cant boot up to tick the setting, to fix their bootloop. since it cant get unlocked, their phones are a "brick".
simms22 said:
i was actually refering to it because of the unlock setting that has to be ticked to unlock. some stock users got caught in a bootloop, then cant boot up to tick the setting, to fix their bootloop. since it cant get unlocked, their phones are a "brick".
Click to expand...
Click to collapse
Is this what happened to this person below ?:
http://forum.xda-developers.com/nexus-6/help/help-nexus-6-brick-t3227126
Since the stock rom did not have developer options "checked" then the bootloader can't be unlocked ? How can you tick the OEM unlock if it is in a bootloop ?
mikeprius said:
Is this what happened to this person below ?:
http://forum.xda-developers.com/nexus-6/help/help-nexus-6-brick-t3227126
Since the stock rom did not have developer options "checked" then the bootloader can't be unlocked ? How can you tick the OEM unlock if it is in a bootloop ?
Click to expand...
Click to collapse
you cant, thats why i said that you should keep it unlocked.
simms22 said:
you cant, thats why i said that you should keep it unlocked.
Click to expand...
Click to collapse
Ok that makes sense. What is the purpose of having the bootloader come locked in a stock phone then ? What does it actually do ? Prevents root ? I probably took it for granted mine was always unlocked before so all I had to do was worry about flashing the proper carrier ROM
mikeprius said:
Ok that makes sense. What is the purpose of having the bootloader come locked in a stock phone then ? What does it actually do ? Prevents root ? I probably took it for granted mine was always unlocked before so all I had to do was worry about flashing the proper carrier ROM
Click to expand...
Click to collapse
Security.
Security in that if stolen your phone cannot be made to work for someone else...
Someone can (and likely will [emoji14]) correct me if I am wrong... But does little to secure your data...ESPECIALLY if you stay encrypted.
scryan said:
Security in that if stolen your phone cannot be made to work for someone else...
Someone can (and likely will [emoji14]) correct me if I am wrong... But does little to secure your data...ESPECIALLY if you stay encrypted.
Click to expand...
Click to collapse
It does nothing to secure data from remote access, but it will protect data (if set with a password) from physical access, providing they do not know the password. The bootloader being unlocked, with no password on encryption would allow them to flash a custom recovery and pull the data off. This will be decrypted on the fly. So it works in conjunction with Encryption. To secure data from physical access, you need both.
IF your bootloader is unlocked and you have no password, you may aswell not be encrypted