Related
Ok, hope I don't get too much heat over this, my old device was a Samsung with unlocked bootloader, so everything was easily flashed.
Anyway, as to the best order of things, I'm still on AT&T 4.2.2 pre camera update, so I easily rooted with with pwnmymoto. I have Xposed installed with a few modules.
For the unlock steps -looks like this is the best guide: http://forum.xda-developers.com/showpost.php?p=51363645&postcount=394 and using: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-c
Q: Is my recovery from pwnmymoto "stock" as it needs to be for unlocking process?
Can I just uncheck/disable the modules I have with xposed, or do I need to delete the framework? (which sounds like the only way is to use RSD to install the original ROM?)
Should I also unfreeze any files? (I think I only froze the one's related to motorola OTA)
My intent is to get to 4.4.2, and I know it's optimal to remove things from pwnmymoto (I know unlocking will wipe everything but my ROM), so probably after I've installed TWRP and rooted, to flash the file for AT&T 4.4.2 http://forum.xda-developers.com/moto-x/general/-t2688009 or does it need to be incremental, as I'm on 4.2 (i.e flash 4.2 camera update, then 4.4, etc.) -sorry if I seem a bit confused
Thanks in advance! any and all help is very much appreciated!
Hopefully not too many questions -if any has the best suggestion for any, would be great
M973 said:
Hopefully not too many questions -if any has the best suggestion for any, would be great
Click to expand...
Click to collapse
Just to be clear if you eant 4.4.2 stock use the xposed framework disabler, it said leaving the modules was ok according to the link you posted. I don't know personally.
But honestly if your unlocking the bootloader then just go to 4.4.2 first then unlock since you'll lose everything. I believe bootloader unlock wipes the system parition too. I don't know for sure.
drago10029 said:
Just to be clear if you eant 4.4.2 stock use the xposed framework disabler, it said leaving the modules was ok according to the link you posted. I don't know personally.
But honestly if your unlocking the bootloader then just go to 4.4.2 first then unlock since you'll lose everything. I believe bootloader unlock wipes the system parition too. I don't know for sure.
Click to expand...
Click to collapse
I think 4.4.2 isn't fully released yet OTA for AT&T, so it would be flashing to stock and taking each OTA in sequence to 4.4 I think? I believe the framework disabler is a zip that needs to be flashed, so that would only be after I have a custom recovery.
I just don't want to mess up anything, want to make sure I have the right recovery for unlocking, and that I've disabled anything that could cause an issue.
Edit: from the pwnmymoto thread, Jcase writes: "In the process we remove stock recovery, so OTAs will not be a worry."
I guess that means i don't have stock recovery?
Edit: I was thinking I needed stock recovery, I guess I just need fastboot which is what I have?
I just want to make sure, if anyone has unlocked from pwnmymoto
Thanks
M973 said:
I think 4.4.2 isn't fully released yet OTA for AT&T, so it would be flashing to stock and taking each OTA in sequence to 4.4 I think? I believe the framework disabler is a zip that needs to be flashed, so that would only be after I have a custom recovery.
I just don't want to mess up anything, want to make sure I have the right recovery for unlocking, and that I've disabled anything that could cause an issue.
Edit: from the pwnmymoto thread, Jcase writes: "In the process we remove stock recovery, so OTAs will not be a worry."
I guess that means i don't have stock recovery?
Edit: I was thinking I needed stock recovery, I guess I just need fastboot which is what I have?
I just want to make sure, if anyone has unlocked from pwnmymoto
Thanks
Click to expand...
Click to collapse
np problem bro, happy rooting! may the flash be ever in your favor
Title pretty much sums it all. I've an XT1058 with unlocked bootloader running stock rooted Kitkat 4.4. I want to update to stock 4.4.2 to try and use the new screen mirroring feature with my Chromecast (AFAIK, I need to be at least on 4.4.1, right?). Is there a way not to lose the unlocked bootloader and/or the root when I flash the update?
Similar question: Do I have to go back to stock (i.e., unrooted, locked) before I flash 4.4.2, or can I flash it over my current stock ROM?
Thank you all in advance.
Deivid85 said:
Title pretty much sums it all. I've an XT1058 with unlocked bootloader running stock rooted Kitkat 4.4. I want to update to stock 4.4.2 to try and use the new screen mirroring feature with my Chromecast (AFAIK, I need to be at least on 4.4.1, right?). Is there a way not to lose the unlocked bootloader and/or the root when I flash the update?
Similar question: Do I have to go back to stock (i.e., unrooted, locked) before I flash 4.4.2, or can I flash it over my current stock ROM?
Thank you all in advance.
Click to expand...
Click to collapse
If you have unlocked the bootloader, there is no fear of "losing" it. Bootloader unlocking is permanent, so even if root is lost, you can simply re-flash TWRP and re-root. Disclaimer: I'm sure you do know the difference between unlocking the bootloader (permanent), and using one of the write-protect-disable exploits (like MotoWpNoMo - which is NOT permanent and would be lost if upgraded to 4.4.2), but I wanted to point this out just in case. If you are indeed bootloader-unlocked, you will have a "WARNING BOOTLOADER UNLOCKED" screen appear upon boot. Again, I apologize if this is redundant...
If you want to take the OTA to 4.4.2, you would need to flash back stock recovery, un-do any mods you have made to /system, and disable Xposed (if installed). This could be complicated if you aren't sure what mods you may or may not have made...
There is no 4.4.1 for the Moto X - we skipped straight from 4.4 to 4.4.2. I'm not sure which version was the first to support Chromecast, however.
It would be easiest to "go back to stock" rather than trying to figure out how to un-do any modifications you may or may not have made. Additionally, it is preferable to flash the entire stock 4.4.2 SBF (which will erase ALL of your data - backup anything you need first), rather than trying to retain the userdata and just flash /system. Issues can arise if you try to retain your userdata.
My advice (for what its worth) is to follow the instructions in the Return to Stock thread to flash the ENTIRE STOCK 4.4.2 SBF for YOUR carrier. This will return you to 100% stock with no root. You WILL retain your unlocked bootloader so afterwards, you can simply flash TWRP, and re-root your phone.
By going this route, you minimize any potential problems that might arise by trying to take the OTA, or by flashing the SBF without erasing userdata.
If you have any questions or need clarification, let me know.
Good Luck
samwathegreat said:
If you have unlocked the bootloader, there is no fear of "losing" it. Bootloader unlocking is permanent, so even if root is lost, you can simply re-flash TWRP and re-root. Disclaimer: I'm sure you do know the difference between unlocking the bootloader (permanent), and using one of the write-protect-disable exploits (like MotoWpNoMo - which is NOT permanent and would be lost if upgraded to 4.4.2), but I wanted to point this out just in case. If you are indeed bootloader-unlocked, you will have a "WARNING BOOTLOADER UNLOCKED" screen appear upon boot. Again, I apologize if this is redundant...
If you want to take the OTA to 4.4.2, you would need to flash back stock recovery, un-do any mods you have made to /system, and disable Xposed (if installed). This could be complicated if you aren't sure what mods you may or may not have made...
There is no 4.4.1 for the Moto X - we skipped straight from 4.4 to 4.4.2. I'm not sure which version was the first to support Chromecast, however.
It would be easiest to "go back to stock" rather than trying to figure out how to un-do any modifications you may or may not have made. Additionally, it is preferable to flash the entire stock 4.4.2 SBF (which will erase ALL of your data - backup anything you need first), rather than trying to retain the userdata and just flash /system. Issues can arise if you try to retain your userdata.
My advice (for what its worth) is to follow the instructions in the Return to Stock thread to flash the ENTIRE STOCK 4.4.2 SBF for YOUR carrier. This will return you to 100% stock with no root. You WILL retain your unlocked bootloader so afterwards, you can simply flash TWRP, and re-root your phone.
By going this route, you minimize any potential problems that might arise by trying to take the OTA, or by flashing the SBF without erasing userdata.
If you have any questions or need clarification, let me know.
Good Luck
Click to expand...
Click to collapse
Thank you very much for the thorough and detalied reply! I'll follow your advice and report back.
Also, as a follow up question (actually, more like checking I got your reply right): Given that I do have the bootloader permanently unlocked, all I need to root 4.4.2 is flashing back TWRP and hit the root option? (I know you said exactly that, but I got lost after reading al the PIE tethered root threads, so just wanted to make sure that is for locked bootloaders, and not my case).
Thanks again!
Deivid85 said:
Thank you very much for the thorough and detalied reply! I'll follow your advice and report back.
Also, as a follow up question (actually, more like checking I got your reply right): Given that I do have the bootloader permanently unlocked, all I need to root 4.4.2 is flashing back TWRP and hit the root option? (I know you said exactly that, but I got lost after reading al the PIE tethered root threads, so just wanted to make sure that is for locked bootloaders, and not my case).
Thanks again!
Click to expand...
Click to collapse
You are correct. Nothing in the PIE thread is relevant to us with unlocked bootloaders.
Worked like a charm!
I actually in the same situations as the OP, EXCEPT my bootloader is locked and I used a couple of jcase's methods to get my root, so no TWRP. Would the same instructions still apply? What would be the best way to backup things?
NameLessThugZero said:
I actually in the same situations as the OP, EXCEPT my bootloader is locked and I used a couple of jcase's methods to get my root, so no TWRP. Would the same instructions still apply? What would be the best way to backup things?
Click to expand...
Click to collapse
Actually, nothing about your situation is similar to the OPs since you don't have unlocked bootloader....or do you mean the situation is similar in that you want to be able to use chromecast?
Regardless, nothing in this thread is relevant to you. The 4.4.2 bootloader is impervious to any known write-protect-disable exploits, so if you DO update to 4.4.2 you will PERMANENTLY lose write-protect. The only option once on 4.4.2+ is to use tethered root such as PIE, which does not disable write protect, does not allow writing to /system, and any and all changes are lost upon reboot. You must then re-connect to PC, and re-run the exploit to gain root again.....not very pretty....
The ONLY option for you (besides bootloader unlock) if you want to retain write-protect-disable and persistent Root, is to follow the advice in this thread: http://forum.xda-developers.com/moto-x/moto-x-qa/upgrade-4-4-root-t2822191
And heed the warnings!!! One simple / innocent mistake will result in either a brick, or PERMANENT loss of write-protect-disable. Take extreme caution.
Good Luck
samwathegreat said:
Actually, nothing about your situation is similar to the OPs since you don't have unlocked bootloader....or do you mean the situation is similar in that you want to be able to use chromecast?
Regardless, nothing in this thread is relevant to you. The 4.4.2 bootloader is impervious to any known write-protect-disable exploits, so if you DO update to 4.4.2 you will PERMANENTLY lose write-protect. The only option once on 4.4.2+ is to use tethered root such as PIE, which does not disable write protect, does not allow writing to /system, and any and all changes are lost upon reboot. You must then re-connect to PC, and re-run the exploit to gain root again.....not very pretty....
The ONLY option for you (besides bootloader unlock) if you want to retain write-protect-disable and persistent Root, is to follow the advice in this thread: http://forum.xda-developers.com/moto-x/moto-x-qa/upgrade-4-4-root-t2822191
And heed the warnings!!! One simple / innocent mistake will result in either a brick, or PERMANENT loss of write-protect-disable. Take extreme caution.
Good Luck
Click to expand...
Click to collapse
I guess I was trying to be too concise, sorry. I know I dont want to go the safestrap route because of time and complexity, nor do I want to do anything with chromecast(which I forgot was mentioned, my bad). I did however plan to use PIE as soon as I heard about it. The route I was simply going to take was just to flash stock 4.4.2 SBF, then apply PIE( which I know isnt permanent after a hard reboot) since I knew that would be to safest way to get root without screwing up stuff. That said, cant this method work just as well? And sure I have to worry about getting SuperUser Xposed up and running again, which I believe has been posted about already, in the comments. But i think that would be all unless Im missing something else.
NameLessThugZero said:
I guess I was trying to be too concise, sorry. I know I dont want to go the safestrap route because of time and complexity, nor do I want to do anything with chromecast(which I forgot was mentioned, my bad). I did however plan to use PIE as soon as I heard about it. The route I was simply going to take was just to flash stock 4.4.2 SBF, then apply PIE( which I know isnt permanent after a hard reboot) since I knew that would be to safest way to get root without screwing up stuff. That said, cant this method work just as well? And sure I have to worry about getting SuperUser Xposed up and running again, which I believe has been posted about already, in the comments. But i think that would be all unless Im missing something else.
Click to expand...
Click to collapse
Sure! If you don't mind losing write-protect-disable forever, and having to re-root each time you reboot, go for it! I highly suggest you follow the instructions in the "Return to Stock" thread (in general sub-forum) to flash the entire 4.4.2 SBF for YOUR carrier. This will give you bone-stock 4.4.2, and will erase everything. Back up anything important first. Then you can follow the instructions in the PIE thread.
The suggested method is highlighted in red in your post above. You CANNOT use the method listed in THIS thread, because you cannot flash custom recovery unless you have unlocked bootloader.
I -think- PIE will work with Titanium Backup (confirm that first), so you can probably back-up anything that you can't just re-install from the play store and restore it afterwards. Copy everything you want to keep from the internal storage (pictures, etc.), because they will be erased as well.
That's pretty much it. I don't think you've missed anything, but keep in mind that bootloader unlock (and the 4.4 exploits) are both far superior to PIE as far as usability and persistence. You'll have to try and reboot as seldom as possible.
Good Luck!!! :good:
EDIT: Keep in mind also that once you update to 4.4.4, PIE will NOT WORK, and you will LOSE ROOT FOREVER (unless another exploit is released, which is unlikely at best).
samwathegreat said:
Sure! If you don't mind losing write-protect-disable forever, and having to re-root each time you reboot, go for it! I highly suggest you follow the instructions in the "Return to Stock" thread (in general sub-forum) to flash the entire 4.4.2 SBF for YOUR carrier. This will give you bone-stock 4.4.2, and will erase everything. Back up anything important first. Then you can follow the instructions in the PIE thread.
The suggested method is highlighted in red in your post above. You CANNOT use the method listed in THIS thread, because you cannot flash custom recovery unless you have unlocked bootloader.
I -think- PIE will work with Titanium Backup (confirm that first), so you can probably back-up anything that you can't just re-install from the play store and restore it afterwards. Copy everything you want to keep from the internal storage (pictures, etc.), because they will be erased as well.
That's pretty much it. I don't think you've missed anything, but keep in mind that bootloader unlock (and the 4.4 exploits) are both far superior to PIE as far as usability and persistence. You'll have to try and reboot as seldom as possible.
Good Luck!!! :good:
EDIT: Keep in mind also that once you update to 4.4.4, PIE will NOT WORK, and you will LOSE ROOT FOREVER (unless another exploit is released, which is unlikely at best).
Click to expand...
Click to collapse
Sweet, thanks for your help. Ill check on the TB thing. Ill update if I need any other help.
NameLessThugZero said:
I guess I was trying to be too concise, sorry. I know I dont want to go the safestrap route because of time and complexity, nor do I want to do anything with chromecast(which I forgot was mentioned, my bad). I did however plan to use PIE as soon as I heard about it. The route I was simply going to take was just to flash stock 4.4.2 SBF, then apply PIE( which I know isnt permanent after a hard reboot) since I knew that would be to safest way to get root without screwing up stuff. That said, cant this method work just as well? And sure I have to worry about getting SuperUser Xposed up and running again, which I believe has been posted about already, in the comments. But i think that would be all unless Im missing something else.
Click to expand...
Click to collapse
Keep in mind, that PIE itself isn't as good of root as using SlapMyMoto & MotoWpNoMo together.
On the X there are two parts needed for effective Root. 1. Root Exploit, and 2. Write Protection Dis-abler.
PIE is a root Exploit. It exploits a vulnerability to grant root access. It does not address Write Protection.
Write Protection on the X prevents proper access to /system or the like. Some apps wont be able to create new files in the protected folders, and any changes made to existing files (including, but not limited to, App installs, file modifications, deletions, renames, etc) are not permanent and are lost at power off/on. This is also why PIE root is lost at power off/on.
In the past (4.4 and below days) SlapMyMoto was the Root Exploit, and MotoWpNoMo was the write protection dis-abler. Once thought to be permanent, the exploit used by MotoWpNoMo was plugged in 4.4.2 making it not work. Write protection becomes re-enabled, and there is no new exploit to disable it.
Why do I mention this? In reading the various threads, especially the Pie thread, there appear to be special instructions to install XPosed when write protection is enabled that you'll need to keep in mind, as well as info on how to re-root and get Xposed working again if you do power off/on. Because write protection is enabled, there are some apps and hacks that may not work. Some of the Tethering tricks for example.
Unlocking the bootloader gets around this. Once you unlock the bootloader, you can always install a custom recovery (like TWRP) and root from there. In the process, write protection becomes disabled. There is no need to wait on a vulnerability in the code to be exploited to gain root and disable write protection.
I wanted to flash my ROM to the stock ROM to remove any possible malware.
If I flash to a custom ROM will the Malware be removed?
Not really sure if I have actual Malware, but want to do it just in case. It's one of those random numbers showing up on the data usage screen.
Regardless, I want to act as if it were a virus or malware. Will flashing to a Custom ROM get me the results I am looking for?
Just return the device to stock via flashing the stock images. During that process you can command to erase user data and in the end you will have a phone like it came out the box.
Is that like a nomral factory reset?
I was trying to do this. http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
The link for the firmware was broken.
Sp00ns said:
Is that like a nomral factory reset?
I was trying to do this. http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
The link for the firmware was broken.
Click to expand...
Click to collapse
Look for your firmware here.
http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347
XT1049
Could not find my rom, but I found it here
iKrYpToNiTe said:
Yes please Safestrap Recovery
Click to expand...
Click to collapse
(Can't post directly there with less than 10 posts.
So this, Safestrap recovery, is only if your already rooted, right? I would be following "For unlocked users" instructions if I have never done anything to my phone. It is a late 2013 version I think it may have an OTA 4.4 update, though not sure if that applies since its not rooted or anything.
The instructions say "1. Boot into TWRP 2.7 factory reset then install the rom."
But I need root access to install twrp?
I suppose using the ROM for my phone with the instructions form he thread I was looking at before (linked in prior post) will be a bad idea.
Since I have done nothing to my phone (i think an ota update to 4.4.2), can't I simply do a custom image recovery and have it be okay?
This thread seems to suggest i can just us RS LITE and boot the recovery image I pulled from the other thread using RSDLITE.
Would that work out? Should I, Can I, use the safestrap or unlocked image from here (iKryptonites thread)? I wasn't able to find my rom in the other links you posted, though else were it was hinted that I could use a sprint rom.
With a locked bootloader and no root, you have no reason to think about custom recoveries, SafeStrap, and ROMs.
If you want to upgrade to 4.4.4, flash this http://www.filefactory.com/file/63sfruck3srr/REPW_XT1094_4.4.4_KXE21.187-L2.24_cid6_CFC.xml.zip in RSD Lite.
If you want to stay on 4.4.2, flash this http://www.filefactory.com/file/6ra...A20.16-1.24-1.12-12-release-keys-cid6.xml.zip in RSD Lite.
I would recommend flashing 4.4.2 (if that's what is currently on your phone) then check out Sunshine to see if it will unlock your bootloader. If you need instructions on how to use RSD Lite, use Google. Do not try to downgrade the firmware on your phone.
nhizzat said:
With a locked bootloader and no root, you have no reason to think about custom recoveries, SafeStrap, and ROMs.
If you want to upgrade to 4.4.4, flash this http://www.filefactory.com/file/63sfruck3srr/REPW_XT1094_4.4.4_KXE21.187-L2.24_cid6_CFC.xml.zip in RSD Lite.
If you want to stay on 4.4.2, flash this http://www.filefactory.com/file/6ra...A20.16-1.24-1.12-12-release-keys-cid6.xml.zip in RSD Lite.
I would recommend flashing 4.4.2 (if that's what is currently on your phone) then check out Sunshine to see if it will unlock your bootloader. If you need instructions on how to use RSD Lite, use Google. Do not try to downgrade the firmware on your phone.
Click to expand...
Click to collapse
Okay, got it thanks. All i Wanted to do was just flash my phone into anything for the afore mentioned reasons
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 rooted my VZW XT1096 via the mofo method. I was thinking that after I flashed my system with a rooted system I would be able to flash a custom recovery and then flash a ROM. There's a CM12.1 build for the Victara but I don't know how to flash it.
Also, it seems like you can only flash IMG files and not zips with mofo.exe. This makes things very difficult because I haven't seen any ext4 system ROMs out there.
jsbenson said:
I rooted my VZW XT1096 via the mofo method. I was thinking that after I flashed my system with a rooted system I would be able to flash a custom recovery
Click to expand...
Click to collapse
Did you read my noob guide? If you had, you would see that root doesn't unlock your bootloader and you need an unlocked bootloader to flash a custom recovery.
There is a link to my noob guide in the OP of the MoFo support thread on the paid software forum.
jsbenson said:
Also, it seems like you can only flash IMG files and not zips with mofo.exe.
Click to expand...
Click to collapse
Correct. Your bootloader is locked and you have no way of unlocking it - you cannot install a zip b/c you don't have a custom recovery and you can't have a custom recovery unless your bootloader is unlocked.
jsbenson said:
This makes things very difficult because I haven't seen any ext4 system ROMs out there.
Click to expand...
Click to collapse
Did you read the OP of the MoFo thread before you purchased? There are custom images for the XT1096 and links to them in the OP of the MoFo thread.
Also, this is your only option if you have an XT1096. So it is this or nothing.
JulesJam said:
Did you read my noob guide? If you had, you would see that root doesn't unlock your bootloader and you need an unlocked bootloader to flash a custom recovery.
There is a link to my noob guide in the OP of the MoFo support thread on the paid software forum.
Correct. Your bootloader is locked and you have no way of unlocking it - you cannot install a zip b/c you don't have a custom recovery and you can't have a custom recovery unless your bootloader is unlocked.
Did you read the OP of the MoFo thread before you purchased? There are custom images for the XT1096 and links to them in the OP of the MoFo thread.
Also, this is your only option if you have an XT1096. So it is this or nothing.
Click to expand...
Click to collapse
I was a little confused so I wanted to make sure I wasn't missing anything. Thanks for the info. I'll read through the posts again.