Hello guys! I am new with the AHD and I wanted to know if its sure to update to stock KitKat with Motorola software, Im asking because I want to root my phone and install a ROM, but in the rooting tutorial it doesn't say a thing about if its safe to update or not
The Atrix HD is supposed to get the Kit Kat update sometime this quarter.
You probably will not be able to update to the official kit kat using Over-The-Air (OTA) unless you are running a stock ROM with stock recovery.
To install a custom ROM, you should root and unlock your bootloader. Remember, unlocking the bootloader will void your warranty.
To follow up what audit13 said, you will most likely need to flash your phone back to complete stock in order to be able to update to the official KitKat upgrade when it is released later this quarter. The good news is that, with an unlocked bootloader, it's a fairly painless process.
quasihellfish said:
To follow up what audit13 said, you will most likely need to flash your phone back to complete stock in order to be able to update to the official KitKat upgrade when it is released later this quarter. The good news is that, with an unlocked bootloader, it's a fairly painless process.
Click to expand...
Click to collapse
+1 for an unlocked bootloader; however, unlocking will probably void any remaining warranty.
I unlocked my bootloader about a week after I got my Atrix HD. I used it for a week to make sure it was functioning properly, hardware-wise, and then started flashing custom ROMs.
Related
So here's the deal, I unlocked my T-Mobile Moto X bootloader through Motorola's website about a year ago or so. I also rooted and didn't bother updating afterwards to anything since I had everything working perfectly for me. Now I need to update my 4.2.2 Moto X to 4.4.3 (or really anything >=4.3 just so I can use my Moto 360 that'll be arriving soon).
My question is, with an unlocked bootloader, rooted, TWRP 2.6.3.1, Xposed-installed Moto X, can I go ahead and flash a stock 4.4.3 ROM (for example from here: http://forum.xda-developers.com/moto-x/development/rom-stock-flashable-t-mobile-t2773675) and just call it a day?
I've been reading past threads and stuff to get back into the loop, but I just can'f find anything to answer me the simple question of updating an unlocked+rooted 4.2.2->4.4+ while keeping root. Just the simple question of, if I get a stock 4.4 image and flash it on my phone, will everything be okay?
I no longer have the passion and interest to constantly be fiddling with kernels, ROMs, and little hacks with my phone like I used to with my OG Droid and, to a lesser extent, with my Galaxy Nexus (plus I feel like it's gotten significantly less easy since those OG days).
I know (i.e. 90% sure) that one way to do what I want (kinda) is RSDLite/manually go back to stock without root on 4.2.2 and then accept the OTA, but certainly it has to be easier than that right? What happened to the days where I can just find a new Gingerbread ROM for my Froyo Droid and just flash it right then and there? Now everything is "go back to stock and do these convoluted steps."
(I'm sorry I'm ranting, I'm just really tired at the moment haha)
Thank you all, hopefully, for the help!
If you don't care about retaining your data, grab the 4.4.3 fxz and unzip it. Follow the directions for returning back to stock here: http://forum.xda-developers.com/moto-x/general/ref-complete-moto-x-guides-information-t2603358 but replace the files to be flashed with the files from the 4.4.3 fxz. Not sure where you got the idea that you need to go back to stock. Word of caution, once on 4.4.3 there's no going back to an older version.
I have the same question as the OP, on unlocked rooted 4.2.2 ATT Moto X, can i flash a custom 4.4.4 and keep root?
RGNDI said:
I have the same question as the OP, on unlocked rooted 4.2.2 ATT Moto X, can i flash a custom 4.4.4 and keep root?
Click to expand...
Click to collapse
You can take the ota but you need the stock recovery. Since you are unlocked you will not lose your unlocked-ness(lol) if you take an ota. But you do need to be completely stock: no su, no custom recovery, etc etc. But once you upgrade to 4.4.3 getting root back is as simple as flashing the appropriate version recovery again and then flashing supersu.
1ad_m12 said:
You can take the ota but you need the stock recovery. Since you are unlocked you will not lose your unlocked-ness(lol) if you take an ota. But you do need to be completely stock: no su, no custom recovery, etc etc. But once you upgrade to 4.4.3 getting root back is as simple as flashing the appropriate vision recovery again and then flashing supersu.
Click to expand...
Click to collapse
OK thanks, but cant I just Flash a Rooted Stock 4.4.4 over 4.2.2? Thats a more to the point question
RGNDI said:
OK thanks, but cant I just Flash a Rooted Stock 4.4.4 over 4.2.2? Thats a more to the point question
Click to expand...
Click to collapse
Yeah that would work as long as your radio is compatible with the rom. The rom you shared earlier should be fine. Just don't downgrade to anything pre 4.4 as that can cause issues because of partition sizes (or so I've heard). But after that I wouldn't take any OTA's cause your bootloader would be incompatible with the OTA and possibly cause a brick. If I were you I'd revert to stock and take the long way to 4.4.3 just so I can get the OTA for when Android L comes out. In fact thats what I plan on doing if the Sunshine bootloader unlock is successful. But if you don't care about that then everything should be fine.
I have an xt1053 with unlocked bootloader, root, and TWRP. When Lollipop is released for moto x, will I lose all that and have to unlock again? What are the risks of updating?
Maybe, probably, who knows. I make it a point to never accept OTAs. Within a day or two devs will capture it, work it over, and release a version that is safe to flash. Just be patient one it's released.
OTA will always break root so you have to re-root. It does not relock your bootloader so you don't have to re-unlock.
If you have an unlocked bootloader there's usually no reason to avoid OTA. only those who have root with locked bootloader avoid OTAs since they risk not getting back root. Unlocked means you can flash custom recovery which means you can get root back.
BUT: You should always revert to stock recovery before taking OTA. doing it while carrying custom recovery will at the very least result in failed OTA, or worse.... So just revert to stock, take ota and thereby losing root, flash custom recover, flash superSU and have root back.
* So obviously this means you shouldn't take OTA unless you have the appropriate stock recovery on hand to flash back to stock.
xt5300 is an HP Pavilion Notebook PC. I think you mean xt1053.
dtg7 said:
xt5300 is an HP Pavilion Notebook PC. I think you mean xt1053.
Click to expand...
Click to collapse
Doh! That's what happens when I don't get sleep. Edited to fix. Ty
Hello Developers!
Here I will put forth instructions required for successful upgrade to lollipop. (These instruction are based on my own experience. I have been using Sony Xperia and Nexus phone for quite a while and I have flashed lot of roms. I may not have much experience in developing but definitely lot of experience in flashing! )
So, motorola has officially put up release notes here: https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/102639
So the questions that are bugging most people are:
1. When will the OTA be available in particular country?
2. Will I be able to smoothly able to upgrade and gain root access on Android L?
For first question: I really can't help you there. It depends on motorola. Android upgrades are rolled out region by region. So OTA will hit your phone when it is available in your region.
Second question:
To answer that, let us first consider few things.
New bootloader:
The very first note on release notes put out by Motorla says that: You cannot downgrade to a previous software version after installing this update. It means that new bootloader has been included in the update which does not allow downgrading.
ART runtime:
Android L uses new Android Runtime (ART). Some applications have not yet been optimized for ART and have problems with ART. To make sure the apps which you require daily work fine with ART, read the changlog given by its developer. If it has not yet been optimized then request the developer to optimize it for ART. If I am not wrong tools to develop apps using ART were released when Google released L preview. So you can expect many apps have been already optimized for ART.
When will the upgrade fail and when will it won't?
1. Locked/Unlocked bootloader:
If you have locked/unlocked bootloader but HAVE NOT CUSTOMIZED or HAVE NOT MESSED WITH RECOVERY AND KERNEL partition then don't worry. OTA upgrade will definitely hit your phone and you will be able to smoothly upgrade to L.
2. Modified kernel/recovery partition and root:
If you have rooted your moto g then it means you unlocked your bootloader, flashed a custom recovery and flashed the superuser binary. In this case you won't be able to upgrade to android L. According to few article I have read, you have to be completely stock before update. Completely as in you shold have never rooted your phone or flashed a custom kernel. Even if you have unrooted after rooting or flashed a stock kernel/recovery after flashing custom kernel/recovery is NOT allowed for Android L upgrade.
3. Unstable internet connection while downloading OTA.
Unstable connection might corrupt the OTA upgrade file. Make sure you have stable internet connection while downloading OTA.
Considering all these there you are in one of the following scenarios:
1. Locked/unlocked bootloader with no customizations to any partitions:
Don't worry. You won't face any problems with OTA upgrade. Just make sure all your apps work fine on ART.
2. Unlocked bootloader with stock/custom rom and sotck/custom kernel with root or unrooted after root:
You will need to flash official kitkat firmware. Official firmware images for Moto G 2014 are located here: http://sbf.droid-developers.org/phone.php?device=36
Then you can upgrade via OTA.
3. Unlocked bootlaoder, root but do not want to lose root priviliges:
Then you will need to wait till developers modify new custom roms based on android L. Then you can flash those by following their instructions. To root stock android L build, a custom kernel is required and also according to chainfire the system.img will be need to be patched. So it is not possible to root sotck android L unless motorola release kernel sources and some developer pathces the system.img.
I have no experience in handling/using/modifying carrier locked phones. So I cannot help you with those.
I WOULD HIGHLY RECOMMEND NOT TO FLASH STOCK/CUSTOM LOLLIPOP ROM OF DIFFERENT MOTO G VARIANT.
Enjoy and happy flashing!
Nice info, thanks!
Also: you need 850 MB of available space or the OTA update will refuse to download.
Thanks man!
It the only thing you did is unlock boot loader and no more... And do the ota update, might boot loader stay unlocked?
El_Froz said:
Thanks man!
It the only thing you did is unlock boot loader and no more... And do the ota update, might boot loader stay unlocked?
Click to expand...
Click to collapse
Yes it will stay unlocked.
Any disadvantage in unlocking boot loader other than voiding the warranty? We will still get future OTA updates?
__________________
Sent from my LIFE PLAY using Tapatalk Pro.
Trekker56 said:
Any disadvantage in unlocking boot loader other than voiding the warranty? We will still get future OTA updates?
__________________
Sent from my LIFE PLAY using Tapatalk Pro.
Click to expand...
Click to collapse
Yes. I have confirmed this by chatting with motorola assistant.
AD9295 said:
Yes. I have confirmed this by chatting with motorola assistant.
Click to expand...
Click to collapse
I know about the warranty.
What about future OTA updates?
Trekker56 said:
I know about the warranty.
What about future OTA updates?
Click to expand...
Click to collapse
I said "YES"! You will get the future OTA updates. Make sure that you don't mess with the partitions in any way. I have confirmed this by chatting with motorola assistant.
AD9295 said:
I said "YES"! You will get the future OTA updates. Make sure that you don't mess with the partitions in any way. I have confirmed this by chatting with motorola assistant.
Click to expand...
Click to collapse
Thanks. Good to know.
-------------------------
axl409 said:
Hey, this seems the right thread to ask.
I'm not so hyped about lollipop (doesn't see all these big changes), but sooner or later I will upgrade of course.
My plan on upgrade is when some custom rom with lollipop will come out.
So my questions are:
-will I be able to flash a lollipop rom from my rooted Moto g with philz recovery and stock/custom kernel?
-do I have to upgrade (somehow) the bootloader or the recovery? And if I have, do I need to return to stock KitKat and then upgrade to official lollipop and then unlock bootloader again and flash recovery again?
Thanks for your answers!
Click to expand...
Click to collapse
Well waiting for lollipop custom rom is actually the best solution yet!
You need following things to upgrade to lollipop:
New bootloader
Recovery compatible with that bootloader
Kernel comatible with lollipop rom which you want to flash
New baseband (radio)
And system and data partition image
When a developer creates a flashable zip, it generally includes:
System and data partition image
Kernel
So before flashing that lollipop rom. You just need to flash
New bootloader
Recovery
Baseband(radio)
Then from recovery you can flash the zip file.
Your bootloader needs to be unlocked to do all this.
Only problem is, it takes time for motorola to release factory images like google releases for nexus phones.
So you will need to wait till some developer captures OTA, extract all the partition images and share it online. (Make sure the uploaded partition images are of the same moto g variant which you have)
axl409 said:
Hey, this seems the right thread to ask.
I'm not so hyped about lollipop (doesn't see all these big changes), but sooner or later I will upgrade of course.
My plan on upgrade is when some custom rom with lollipop will come out.
So my questions are:
-will I be able to flash a lollipop rom from my rooted Moto g with philz recovery and stock/custom kernel?
-do I have to upgrade (somehow) the bootloader or the recovery? And if I have, do I need to return to stock KitKat and then upgrade to official lollipop and then unlock bootloader again and flash recovery again?
Thanks for your answers!
Click to expand...
Click to collapse
Actually it is easier to flash official kitkat images and update to lollipop with ota update. Then you can flash any custom lollipop rom just by following rom developer's instruction. It will be easier.
Thanks for this thread Bro.
-------------------------
axl409 said:
Thanks a lot @AD9295!
So, I was searching around for returning stock, because you said in the end I'll have to and also because I want to be prepared in time!
I found the thread "restore to stock" and in the end, there's written this at q18 (I made a screenshot).
It's good to do this even if I have philz recovery? Will I get the update or I need to flash also the stock recovery? I know there's written, but it's cool? Or maybe something could go wrong?
Click to expand...
Click to collapse
If you are using rooted custom rom:
Flash the complete official kitkat image. images are located here:
http://sbf.droid-developers.org/phone.php?device=36
If you are just using rooted stock rom then follow the instruction in response to that q18. You do need to flash stock recovery as mentioned there. That's what is meant by returning to "stock".
-------------------------
axl409 said:
No I'm just rooted, and of course have installed some apps that need root.
So in order to restore stock I should:
- uninstall the root apps
- do the q18 (but where I found the stock recovery image?)
- waiting for the ota lollipop upgrade that will update all (bootloader, recovery, radio, system and data).
Am I correct?
And then from lollipop do again root and install future lollipop compatible recovery.
Click to expand...
Click to collapse
Yes you are correct. the zip files located here: http://sbf.droid-developers.org/phone.php?device=36 contain all the official .img files. You can download it from there (I understand file size is large but it's worth downloading coz you will always be able to return to stock even if you mess up your phone pretty badly ) or you can ask on forum
-------------------------
AD9295 said:
I said "YES"! You will get the future OTA updates. Make sure that you don't mess with the partitions in any way. I have confirmed this by chatting with motorola assistant.
Click to expand...
Click to collapse
What benefit gives just unlocking and not rooting?
Hey guys does anyone have step-by-step guide on how i can root this phone? I am not able to find a guide for XT1053 (T-Mobile) on 4.4.4. Specifically I want to install a 5.0 rom because I'm tired of waiting for the update. Any help will be appreciated;
stuntman2128 said:
Hey guys does anyone have step-by-step guide on how i can root this phone? I am not able to find a guide for XT1053 (T-Mobile) on 4.4.4. Specifically I want to install a 5.0 rom because I'm tired of waiting for the update. Any help will be appreciated;
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x/general/ref-complete-moto-x-guides-information-t2603358
You'll have to unlock the bootloader. No way around it.
Should I be nervous about unlocking the bootloader?
Didn't my Samsung phone come with it already unlocked?
Should you be nervous? Google the pros and cons then decide for yourself.
No phone nor tablet comes with an unlocked bootloader.
I have an XT1053 and just recently unlocked the bootloader through the Motorola site. I waited until now because my original warranty just expired and knew that unlocking the bootloader would void my warranty. I wanted to unlock the bootloader under 4.4.4 because I didn't know if there would be any problems once Lollipop was offered as an update. The unlock process went very smoothly and took only a few minutes. You probably already know that unlocking wipes your phone, so be prepared to reinstall apps and other files. I have not rooted yet because I'll probably wait to do that after the Lollipop OTA comes around. Even then, I may not root because I'm really pretty happy with the phone as it is. For me, unlocking the bootloader was just of way of preserving the future option to root.
stuntman2128 said:
Hey guys does anyone have step-by-step guide on how i can root this phone? I am not able to find a guide for XT1053 (T-Mobile) on 4.4.4. Specifically I want to install a 5.0 rom because I'm tired of waiting for the update. Any help will be appreciated;
Click to expand...
Click to collapse
Go to YouTube and search for qbking77 channel on how to unlock bootloader moto 2013.. Step by step tutorial with video
Sent from my XT1053 using XDA Premium 4 mobile app
mac1996 said:
Go to YouTube and search for qbking77 channel on how to unlock bootloader moto 2013.. Step by step tutorial with video
Sent from my XT1053 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
unlocking bootloader isn't a problem. I mainly want to know how i can put a custom recovery (prefer CWM because i've had it on previous phone). That way i can straight up install a custom rom that is already rooted without rooting stock. I just really want 5.0 really tired of 4.4.4
stuntman2128 said:
unlocking bootloader isn't a problem. I mainly want to know how i can put a custom recovery (prefer CWM because i've had it on previous phone). That way i can straight up install a custom rom that is already rooted without rooting stock. I just really want 5.0 really tired of 4.4.4
Click to expand...
Click to collapse
Do you have fastboot?
if yes, go to your phone bootloader.
Connect to your computer by USB.
Type the following in cmd. (place your recovery img file in fastboot directory)
fastboot flash recovery (your recovery name).img
Sent from my XT1053 using XDA Free mobile app
Check the sticky threads. There's only a year and halfs worth of information available to you here and all over the rest of the internet.
stuntman2128 said:
unlocking bootloader isn't a problem. I mainly want to know how i can put a custom recovery (prefer CWM because i've had it on previous phone). That way i can straight up install a custom rom that is already rooted without rooting stock. I just really want 5.0 really tired of 4.4.4
Click to expand...
Click to collapse
At any point after unlocking the bootloader... To flash recovery, did you do the following...
Start the phone in Fastboot/Bootloader mode.. then from the PC type...
mfastboot flash recovery YourRecovery.img
mfastboot reboot-bootloader
Follow onscreen directions to use vol down key and highlight recovery, then use vol up to select/enter recovery. Once in recovery you can reboot the phone and proceed with whatever you want.
Failure to reboot-bootloader and entering recovery immediately after flashing recovery (i.e. doing something else first) can result in the recovery not sticking.
4.4.4
a year old post by dray_jr says the following:
4.4 to 4.2.2 Pre Cam will Brick
4.2.2 Post Cam to 4.2.2 Pre Cam will Brick.
4.4.2 to to anything will Brick
4.4 to 4.2.2 Post Cam you are ok
Click to expand...
Click to collapse
can someone explain this to me? I got my phone around august 2014, it came with 4.4.3 and right now I'm on 4.4.4.
If I use the motorola website and follow their bootloader unlock steps am I fine? will I have any brick issues stated from the quote above?
Thread
Nevermind guys, found the perfect thread for 4.4.4 root!
Thread: http://forum.xda-developers.com/moto-x/moto-x-qa/step-step-instructions-unlocking-t2649738
Final question: I don't have to install supersu root if i install CM12 once i get into TWRP recovery am i correct? (since cms come rooted)
Would flashing a JB kernel (and only the kernel) work to root it as described here?: http://forum.xda-developers.com/crossdevice-dev/sony/guide-xperia-kitkat-4-4-4-rooting-t3003520
Completely different phone. What works on one does not always apply to another. If it worked on the Moto X, don't you think someone would've tried and documented it s sometime in the last 18 months?
nhizzat said:
Completely different phone. What works on one does not always apply to another. If it worked on the Moto X, don't you think someone would've tried and documented it s sometime in the last 18 months?
Click to expand...
Click to collapse
Of course its a different phone, but since the Moto X also came with JB stock, I was just wondering whether the same method would work for the ones who are stuck with 4.4.4 and no root.
And no, I don't think that every method has been tried already. the Razr I JB root with a locked BL for example only happened, cause I asked jcase nicely if he could code an app that uses an exploit. So, many times, without asking nothing will happen...
dagoban said:
Of course its a different phone, but since the Moto X also came with JB stock, I was just wondering whether the same method would work for the ones who are stuck with 4.4.4 and no root.
And no, I don't think that every method has been tried already. the Razr I JB root with a locked BL for example only happened, cause I asked jcase nicely if he could code an app that uses an exploit. So, many times, without asking nothing will happen...
Click to expand...
Click to collapse
I don't proclaim to know the ins and outs of all things android, but I do know this.. Just because a phone has android 4.4.4 doesn't mean its the same 4.4.4 with the same exact flaws and vulnerabilities, susceptible to the same exact root processes. Its why an exploit to root one phone, often doesn't work to root another.
In the case of the Moto X with a locked bootloader, JCASE has come out with many processes exploiting vulnerabilities for Android and the Apps on the Moto X to not only root it, but disable its write protection. As new OTA's have patched an exploit, he came out with other ways.
Starting wth 4.4.2, the vulnerability in the bootoader to disable write protection has been patched.
Jcase's Sunshine tool works on the X with 4.4.3 and lower, and only SOME with 4.4.4. It needs temp root first, etc. For whatever reason, we don't have a way to even temp root the 2013 X on 4.4.4 enough to allow Sunshine to do its work. And despite being asked many times, Jcase pretty much said in the Sunshine discussion threads that v3.0 wont have Moto X 4.4.4 support (unless he changed his mind and I missed it). Yet sunshine and its root processes, etc work on other phones (HTC) with 4.4.4.
But back to the thread you link...
On the X, due to its security measures, with a locked bootloader, you can only flash the Moto signed ROM for your phone. Nothing else. Because of this, you can't flash a custom recovery. To flash items, we use mFastboot and RSDLite. They need the img files, or bin files. If we make our own, they wont be signed, so they wont flash to a phone with a locked bootloader. And you can't package them into a flashable ZIP because stock recovery looks for the Moto digital signature (which we don't have and can't fake), and you can't install TWRP/CWM/Philz/etc to flash that way. So if you manage to pull the JB kernel out of the Moto SBF file, you wont be able to flash it.
Due to write protection on the 2013 X, any changes made to /System and a few other places, will be lost at power off/on. In other words, if you do manage to flash it (or push via adb), it wont stick due to write protection.
We've seen people try and manipulate their phone by trying to DOWNGRADE their ROM. Well, this doesn't work either. GPT.BIN (partition table), and Motoboot.img (bootloader, TZ, and a few other things) get in the way. Even on an X with an Unlocked bootloader, you can't downgrade these parts. Enough who attempted this have ended up bricking their phone immediately, or with later taking an OTA. Sure you can try to flash just system.img, and while that has less risk for bricking, people who have tried this were still not able to use the older Root Exploits (that worked if you hadn't upgraded already). People have tried flashing everything but GPT.BIN and MotoBoot.img. Again, it didn't help with rooting. Not to mention with a missmatched system.img or other parts, features on the phone may not always work properly (going Settings -> Security comes to mind), and you are at risk of bricking should you take an OTA update.
Since that process exploits a vulnerability, and its out there (so the vulnerability is in the public), I'm sure if it worked or was possible, JCASE, Beaups, or others would have put something together.
Now, back on topic of the XT1053... it has an Unlockable bootloader. Unlocking the bootloader disables write protection, and allows you to flash non-moto stuff. So unlocking the bootloader, flashing TWRP, reboot bootloader, enter TWRP and root, is quick, easy, effective, and doesn't rely on vulnerabilities on the phone to be exploited so patches/updates haven't got in the way. Plus you don't have to wait for someone to find them and create a repeatable process.
I got my MotoX about a year ago, non-dev edition on VZW. I installed Hashcode's SafeStrap custom recovery and flashed Kryptonite's "stock" 4.4.2 rom to the stock slot. That satisfied me for the time being and I lost track of current development on the Moto X.
I've been itching for a change though and a software update is just the fix. Since I haven't kept up thoug, I really don't know how to go about it. I've been reading about the options but I don't know where my phone stands. Can I go the CM11-> CM12 route with Safestrap even though my bootloader is locked? Or do I need to use SunShine to unlock my bootloader and install a different custom recovery? And do I need to revert to stock to stock at any point? I'm pretty comfortable with all of this, I just need some nudging in the right direction.
llsmith said:
I got my MotoX about a year ago, non-dev edition on VZW. I installed Hashcode's SafeStrap custom recovery and flashed Kryptonite's "stock" 4.4.2 rom to the stock slot. That satisfied me for the time being and I lost track of current development on the Moto X.
I've been itching for a change though and a software update is just the fix. Since I haven't kept up thoug, I really don't know how to go about it. I've been reading about the options but I don't know where my phone stands. Can I go the CM11-> CM12 route with Safestrap even though my bootloader is locked? Or do I need to use SunShine to unlock my bootloader and install a different custom recovery? And do I need to revert to stock to stock at any point? I'm pretty comfortable with all of this, I just need some nudging in the right direction.
Click to expand...
Click to collapse
If you NEVER took the 4.4.4 OTA you might want to consider unlocking your bootloader via "Sunshine" Then you can flash CM or anything you want with a real recovery and not safestrap. Just know that unlocking your bootloaer on a reatail device will void your warranty.
Travisdroidx2 said:
If you NEVER took the 4.4.4 OTA you might want to consider unlocking your bootloader via "Sunshine" Then you can flash CM or anything you want with a real recovery and not safestrap. Just know that unlocking your bootloaer on a reatail device will void your warranty.
Click to expand...
Click to collapse
Right, my phone has never seen 4.4.4. So I'm going to go ahead and use Sunshine to unlock my boot loader as the first step. The warranty I'm not too concerned about.
I guess the next question is how do I go about replacing safestrap with TWRP? Is it the same as installing TWRP from stock?
llsmith said:
Right, my phone has never seen 4.4.4. So I'm going to go ahead and use Sunshine to unlock my boot loader as the first step. The warranty I'm not too concerned about.
I guess the next question is how do I go about replacing safestrap with TWRP? Is it the same as installing TWRP from stock?
Click to expand...
Click to collapse
You should be familiar with flashing a custom recovery via adb if you have used TWRP on other devices. Once you have the bootloader unlocked you would need the correct recovery image of TWRP for the Moto X and then in bootloader mode use the command "fastboot flash recovery 'recovery.img'" where 'recovery.img' is the exact name of the file. If it flashed and it works properly then you could flash CM12 and Safestrap should be gone if you followed the flashing directions exactly. Don't forget to make a Nandroid of your current setup before you begin! Factory Resetting the device would be crucial if jumping from one ROM to another so it kind of takes care of itself.