Database Develop

Newest SBF file

I remember having to delete a line during the sbf process for SlapMyMoto, with the new 4.4.2 sbf file will this be necessary again?

http://forum.xda-developers.com/showthread.php?t=2603358
This guide can answer your questions better, or look in the locked bootloader threads.
But if you are on 4.4.2 now and not rooted, you're out of luck. You can't do it. You can possibly downgrade, tho it can lead to a brick if not done completely properly.
If you are already rooted before updating to 4.4.2, depending how you upgraded, you will have root....but read/write is enabled and can't currently be disabled on 4.4.2. So any root changes you make will be gone if you hard reboot or power off the phone.
Read up for more info.
Sent from my cell phone telephone....

kj2112 said:
http://forum.xda-developers.com/showthread.php?t=2603358
This guide can answer your questions better, or look in the locked bootloader threads.
But if you are on 4.4.2 now and not rooted, you're out of luck. You can't do it. You can possibly downgrade, tho it can lead to a brick if not done completely properly.
If you are already rooted before updating to 4.4.2, depending how you upgraded, you will have root....but read/write is enabled and can't currently be disabled on 4.4.2. So any root changes you make will be gone if you hard reboot or power off the phone.
Read up for more info.
Sent from my cell phone telephone....
Click to expand...
Click to collapse
As you saw from my other thread, I'm on rooted 4.4.2 with read/write enabled. Is it safe flash the 4.4.2 SBF back to stock or is that considered a downgrade? I read going back to stock is recommended before unlocking the bootloader.
Thanks

kj2112 said:
http://forum.xda-developers.com/showthread.php?t=2603358
This guide can answer your questions better, or look in the locked bootloader threads.
But if you are on 4.4.2 now and not rooted, you're out of luck. You can't do it. You can possibly downgrade, tho it can lead to a brick if not done completely properly.
If you are already rooted before updating to 4.4.2, depending how you upgraded, you will have root....but read/write is enabled and can't currently be disabled on 4.4.2. So any root changes you make will be gone if you hard reboot or power off the phone.
Read up for more info.
Sent from my cell phone telephone....
Click to expand...
Click to collapse
I'm unlocked now, I wanted to go through RSD for my problem but ended up pulling the needed files and flashing what I needed through fastboot.

EvanVanVan said:
As you saw from my other thread, I'm on rooted 4.4.2 with read/write enabled. Is it safe flash the 4.4.2 SBF back to stock or is that considered a downgrade? I read going back to stock is recommended before unlocking the bootloader.
Thanks
Click to expand...
Click to collapse
You can't be on 4.4.2 with a locked bootloader, rooted with write protection disabled. If you are, you're the first and only one on here.
I think we're miscommunicating a bit.
I am sure what you have is root.....with write protection enabled. As is the issue with 4.4.2. Meaning, if you hard reboot, you lose all root changes. Correct?
But no, you don't need to do anything to unlock the bootloader. Your phone will be wiped during the process. You'll have to flash custom recovery and root after. Then install all your apps again.
Sent from my cell phone telephone....

[Q] Black screen after trying to root, did i hard bricked my moto x?

Hey guys,
So i was interested in installing a custom rom im my moto x and started by trying to root it.
Every thing was going fine, but after i placed the unlock code via CMD, i've got an error during the root process and my phone just died. Now all that i've got is a black screen, no matter if I try to hard reset or anything.
Any idea?
tl;dr my phone just died in the root process, wtf can i do?

Unlock code? Root process?
Which model do you have? Which version of Android was it on? What exactly were you doing or using to root or unlock?

Which model you have used ?

I have a x1058, it was on android 4.4.2 and was using a tutorial from a brazilian guy, wich involved downloading adb and fastboot scripts and run them trough cmd.

You will need to be far more specific in what commands you did, if any...and the specific errors.
Only way we'll know what's happened.

It may be of some help if you post the tutorial you followed and say exactly at what step things went wrong.
Sent from my Moto X using Tapatalk Pro

monzillo said:
I have a x1058, it was on android 4.4.2 and was using a tutorial from a brazilian guy, wich involved downloading adb and fastboot scripts and run them trough cmd.
Click to expand...
Click to collapse
The XT1058 has a locked bootloader, so I hope that tutorial didn't have you try to downgrade your ROM in order to use SlapMyMoto/MotoWpNoMo to root and disable write protection.
SlapMyMoto/RockMyMoto/etc, used on 4.4 and lower, involved downgrading the rom to use an exploit in 4.2.2 to gain root. But with 4.4.2 you can't downgrade the rom safely, without risk of bricking your phone anymore. Additionally, 4.4.2 closed the exploits used by SlapMyMoto/RockMyMoto to gain root, and the exploit used by MotoWpNoMo to disable write protection.
As others have suggested, post a link to the turtorial, and any error messages you saw while running the scripts.
Also, try booting into bootloader/fastboot mode. Can you get there? What version bootloader does it say you are on? I believe 30.B4 is 4.4.2 and 30.71 is 4.4 and 4.2.2 w/camera fix. If you have 30.B4, then your only fix might be using RSDLite to flash the 4.4.2 SBF for your carrier, or mFastboot to individually flash all parts of 4.4.2 on your phone, and then forget about rooting unless Moto's web site gives out the bootloader unlock code for your phone.

4.2.2 to 4.4 Root Nightmare

So here is where I am at...
Initially I had a Moto X 4.4 on VZW. I downgraded to 4.2.2, ran RockMyMoto then ran MotoWPNoMo.
Rooted with Write Protection Off. Reflashed the Camera Update. Ran SlapMyMoto, took the 4.4 update and finished the 4.4 root steps.
I went like this for quite a while then decided to install SafeStrap and the 4.4.2 rooted rom.
Had issues and flashed back to 4.2.2 - this is where I am at now. If I run RockMyMoto I get
System is not write protected...
Executing step 3...
If I install SuperSu I get "binaries not installed."
I can confirm that Write Protection is off but I don't know if I am rooted.
What do I need to do to get back to 4.4 rooted with Write Protection off? If I run SlapMyMoto what OTA will I get... 4.4 or 4.4.2?
Please Help!

HTC-OH_SNAP said:
So here is where I am at...
Initially I had a Moto X 4.4 on VZW. I downgraded to 4.2.2, ran RockMyMoto then ran MotoWPNoMo.
Rooted with Write Protection Off. Reflashed the Camera Update. Ran SlapMyMoto, took the 4.4 update and finished the 4.4 root steps.
I went like this for quite a while then decided to install SafeStrap and the 4.4.2 rooted rom.
Had issues and flashed back to 4.2.2 - this is where I am at now. If I run RockMyMoto I get
System is not write protected...
Executing step 3...
If I install SuperSu I get "binaries not installed."
I can confirm that Write Protection is off but I don't know if I am rooted.
What do I need to do to get back to 4.4 rooted with Write Protection off? If I run SlapMyMoto what OTA will I get... 4.4 or 4.4.2?
Please Help!
Click to expand...
Click to collapse
Stop right there. If you ota to 4.4.2, very very good chance you will be bricked.
Its very common knowledge and there's posts in nearly every thread about this.
The advice most give is simple....don't downgrade from 4.4.2.... ever. Unless you have a few hundred bucks laying around for a new phone.
So, now you have already. So you need to tread extremely lightly. I would not alter a single thing now, until you do lots if research and figure out how, and if, you can get back to 4.4.2. Rooting would be my last concern at this point. Learning exactly what wrong moves can brick my phone would be my only priority.
I would help, but I am one who says never downgrade from 4.4.2. Period. So I've never researched the who process of downgrading against this advice. One thing is for sure DO NOT TAKE AN OTA.
There's a good chance you can get back to 4.4.2 somehow....but not by ota.... So chances are root and 4.4.2 will never happen now. In fact, you may be stuck exactly with what you have now.
Read up and see what choices you now have....before you do a thing.
Good luck!!!!
---------- Post added at 05:37 PM ---------- Previous post was at 05:35 PM ----------
First step is to figure out if you ever had the 4.4.2 boot loader on your phone. If you did not....for sure....then you should still be safe.

kj2112 said:
Stop right there. If you ota to 4.4.2, very very good chance you will be bricked.
Its very common knowledge and there's posts in nearly every thread about this.
The advice most give is simple....don't downgrade from 4.4.2.... ever. Unless you have a few hundred bucks laying around for a new phone.
So, now you have already. So you need to tread extremely lightly. I would not alter a single thing now, until you do lots if research and figure out how, and if, you can get back to 4.4.2. Rooting would be my last concern at this point. Learning exactly what wrong moves can brick my phone would be my only priority.
I would help, but I am one who says never downgrade from 4.4.2. Period. So I've never researched the who process of downgrading against this advice. One thing is for sure DO NOT TAKE AN OTA.
There's a good chance you can get back to 4.4.2 somehow....but not by ota.... So chances are root and 4.4.2 will never happen now. In fact, you may be stuck exactly with what you have now.
Read up and see what choices you now have....before you do a thing.
Good luck!!!!
---------- Post added at 05:37 PM ---------- Previous post was at 05:35 PM ----------
First step is to figure out if you ever had the 4.4.2 boot loader on your phone. If you did not....for sure....then you should still be safe.
Click to expand...
Click to collapse
Let me clarify something... I did not take the 4.4.2 OTA. I was on 4.4, installed safestrap and flashed the 4.4.2 rooted stock ROM. Does flashing in safestrap affect the boot loader? How can I determine which boot loader I have? I still have write protection off just no root.

HTC-OH_SNAP said:
Let me clarify something... I did not take the 4.4.2 OTA. I was on 4.4, installed safestrap and flashed the 4.4.2 rooted stock ROM. Does flashing in safestrap affect the boot loader? How can I determine which boot loader I have? I still have write protection off just no root.
Click to expand...
Click to collapse
I've always had an unlocked boot loader.....all I know about locked methods and whatnot I've read here.
So maybe try asking in the ROM thread if it updates boot loader?
You just want to be sure before anything else.
Don't want to see you or anyone with a brick.

kj2112 said:
I've always had an unlocked boot loader.....all I know about locked methods and whatnot I've read here.
So maybe try asking in the ROM thread if it updates boot loader?
You just want to be sure before anything else.
Don't want to see you or anyone with a brick.
Click to expand...
Click to collapse
The Safestrap process, and installing a proper safestrap rom does not update the phone's bootloader. I think it also doesn't touch the GPT.BIN.
I know you haven't had experience with Safestrap, so think of it as kind of a Host OS/Guest OS setup, or if it was a PC then kind of like a Virtual PC setup where you could have a PC running real Windows 7 on your C drive that you boot too, plus having Windows 8 in a virtual PC and the Virtual PC's image file being stored on your "D drive". Installing W8 in the virutal PC doesn't touch the W7 "host" os, or its boot partition, etc. (its not 100% exactly the same, but that is the best analogy I can come up with at the moment).
---------- Post added at 06:35 AM ---------- Previous post was at 06:02 AM ----------
HTC-OH_SNAP said:
Let me clarify something... I did not take the 4.4.2 OTA. I was on 4.4, installed safestrap and flashed the 4.4.2 rooted stock ROM. Does flashing in safestrap affect the boot loader? How can I determine which boot loader I have? I still have write protection off just no root.
Click to expand...
Click to collapse
re: safestrap affecting the bootloader, no, it does not. At least if you are using a ROM made for safestrap, and properly follow the process.
To determine the bootloader version, boot the phone to bootloader mode it should show the version number. I believe 30.B4 is 4.4.2 and 30.71 is 4.4 and 4.2.2 w/camera fix. As @kj2112 has mentioned, If the bootloader has been updated to 4.4.2, do NOT attempt to downgrade. However when using safestrap properly, its different.
As for the error at step 3... apparently it is common for those who had once used MotoWpNoMo to disable write protection, then trying to run though the SlapMyMoto process.
The actual process for getting a working Safestrap setup is the same for all Moto X's, however the Safestrap roms, and possibly the installer, are model specific... So, for example, if you have a Verizon X with locked bootloader, you could still follow [GUIDE] Republic Wireless Moto X KitKat 4.4.2 Root, Safestrap, TWRP, and MotoWpNoMo but using the Verizon specific SBFs, SafeStrap and Safestrap Roms instead of the ones for T-Mobile and RW linked in that thread (like on steps 1b, 3a, 5a, 6b).
Because of that, I'll point you to -> http://forum.xda-developers.com/showpost.php?p=52401229&postcount=30 as it is the quickest link I can find to a work around for slapmymoto if you've already disabled write protection with MotoWpNoMo.
I'm sure if you took the time to read every post in the SlapMyMoto thread or the entire MotoWpNoMo thread you will likely find discussions about your situation and a fix. For example: Post 349 through 357 of the MotoWpNoMo thread is a user having the same issue, but later says it was due to the SlapMyMoto file being the older 0.5c version rather than 1.0.
I'm sorry, I'm just not good with RockMyMoto/SlapMyMoto/MotoWpNoMo/etc and Safestrap as I have an unlocked bootloader, so I never had to mess with them to root and disable write protection.

how do i spf back to 4.2.2?

coolguy71261 said:
how do i spf back to 4.2.2?
Click to expand...
Click to collapse
This is someone's thread with their particular issue. If we start helping you in this thread with your issue....that is called thread hijacking.
You need to ask in a thread relevant to your issue, or start a new thread.
However.....since we don't know anything about your situation or your issue.....advice is hard to give.
You can probably start here tho.... http://forum.xda-developers.com/showthread.php?t=2603358
If that doesn't help, you need to make your own thread. And be as specific as possible with the details. But only start a thread if searching comes up with nothing and no existing threads match your issue.
Just some XDA etiquette.
Good luck.
And sorry to OP for off topic.

If you rooted with rockmymoto and took write protection off. You'll still have it so the only process you'll need to do is slapmymoto on 4.4. Safestrap will work with 4.2.2 and 4.4. If you want root stay there don't go to 4.4.2
MOTO X

KidJoe said:
Great Advice
Click to expand...
Click to collapse
Ok... so here is how the whole thing ended.
Checked my Bootloader - it was still 30.71.
Verified I still had Write Protection off.
Ran SlapMyMoto 1.0.
Took the OTA (From 4.2.2 it is still 4.4 and NOT 4.4.2)
Ran the ADB Shell Commands.
Installed SuperSu from the Play Market, and...
Rooted 4.4 with Write Protection Off.
Thanks!

Having some issues want to restore

I'm running 4.4 on first gen moto x. I am rooted with jcase method (back when it was script only..lol) I have a loss of battery life. I use to be able to run all day and come home with 40ish %.. I've ran a tad over 9 hours today and I'm at 18%. I have had touch screen issues off "center" for example.. If I'm googleing something and I click on first one pops up I may click on the 2nd or 3rd.. I'd I'm on Facebook and I click "like" it at click on the link.. I am thinking of fxzing my phone back to stock and erase it all. But my concern is 1. If it pulls update before I can stop it, is there a root out for it yet? 2nd, I have not had to root my 4.4 is there an easier way now?
Thanks for the help!!
Slapped my Moto

If you're on 4.4, why not use Sunshine to unlock your bootloader? That way, you don't have to worry about your first or second question.
To answer your questions:
1. It won't and even so, you have to choose to install the update.
2. TowelPieRoot.
I highly suggest you pony up the $25 to unlock your bootloader though.

I'm on Verizon..last I knew it was unlockable..
Edit: OK...nvm done a bit of research...this is awesome.. Only issue I'm having is I try to download sunshine and it basically says its corrupt.
Slapped my Moto

OK another ?. I did the su shine unlock and tried to install CM11 and bootlooped so I had to reinstall stock...trying to do root I remember I need reflash 4.2.2 and use slapmymoto etc to regain root then take 4.4 update... But I don't think its out what if I take 4.4.4 will I still have root?!
I've also seen u can use towlpieroot but once u reboot, u lose it...is there a perm solution?
Sent from my XT1060 using xda premium

If you unlocked your bootloader you just flash twrp and it roots for you. Hopefully you didn't brick by flashing a lower firmware.
You can just use the Verizon fxz in the general section to update to 4.4.4 and then root with twrp. You are unlocked, no exploits or towel pie or slapping. Just root forever
Sent from my XT1060

xpsychox said:
OK another ?. I did the su shine unlock and tried to install CM11 and bootlooped so I had to reinstall stock...trying to do root I remember I need reflash 4.2.2 and use slapmymoto etc to regain root then take 4.4 update... But I don't think its out what if I take 4.4.4 will I still have root?!
I've also seen u can use towlpieroot but once u reboot, u lose it...is there a perm solution?
Sent from my XT1060 using xda premium
Click to expand...
Click to collapse
If sunshine properly unlocked your bootloader, you shouldn't have any issues rooting, no matter what ROM you have on your phone.
Once you unlock your bootloader, you do not need to use SlapMyMoto/RockMyMoto or the like, nor do you need MotoWpNoMo.
If you get 4.4.2 or higher on your phone do NOT downgrade!!!
PIE and TowelPieRoot only work on 4.4.2, it does not work on 4.4.4. And it is only a temp root, as with a locked bootloader on 4.4.2 and up, you can't disable write protection.
IF you've used Sunshine to unlock your bootloader then, To ROOT Once you unlocked your bootloader, Download the latest TWRP Recovery from -> http://teamw.in/project/twrp2/234 (under the Download-Fastboot heading) and the latest SuperSU from -> http://download.chainfire.eu/supersu or the latest CWM / TWRP / MobileODIN installable ZIP from http://forum.xda-developers.com/showthread.php?t=1538053 and use them while following the instructions in this post -> http://forum.xda-developers.com/moto-x/moto-x-qa/step-step-instructions-unlocking-t2649738

KidJoe said:
If sunshine properly unlocked your bootloader, you shouldn't have any issues rooting, no matter what ROM you have on your phone.
Once you unlock your bootloader, you do not need to use SlapMyMoto/RockMyMoto or the like, nor do you need MotoWpNoMo.
If you get 4.4.2 or higher on your phone do NOT downgrade!!!
PIE and TowelPieRoot only work on 4.4.2, it does not work on 4.4.4. And it is only a temp root, as with a locked bootloader on 4.4.2 and up, you can't disable write protection.
IF you've used Sunshine to unlock your bootloader then, To ROOT Once you unlocked your bootloader, Download the latest TWRP Recovery from -> http://teamw.in/project/twrp2/234 (under the Download-Fastboot heading) and the latest SuperSU from -> http://download.chainfire.eu/supersu or the latest CWM / TWRP / MobileODIN installable ZIP from http://forum.xda-developers.com/showthread.php?t=1538053 and use them while following the instructions in this post -> http://forum.xda-developers.com/moto-x/moto-x-qa/step-step-instructions-unlocking-t2649738
Click to expand...
Click to collapse
Deffinatly good to know..but kind of sucks cu now I won't have a nandroid back up..been using safestrap..lol
Sent from my XT1060 using xda premium
Edit: I already ran slapmymoto and m WP is killed long ago (like 4 months ago) so it's done and gone.. I'm thinking of takeing the 4.4.4 but I want root and only temp root is what I found... unless you know of something I don't?

xpsychox said:
Deffinatly good to know..but kind of sucks cu now I won't have a nandroid back up..been using safestrap..lol
Sent from my XT1060 using xda premium
Edit: I already ran slapmymoto and m WP is killed long ago (like 4 months ago) so it's done and gone.. I'm thinking of takeing the 4.4.4 but I want root and only temp root is what I found... unless you know of something I don't?
Click to expand...
Click to collapse
You used MotoWPNoMo to disable write protection. If you upgrade to 4.4.2, you'll likely keep root which was provided by SlapMyMoto, but the vulnerability being exploited by MotoWpNoMo was patched, so write protection will be re-enabled.
On 4.4.2 and up, the only way to disable write protection is unlocking the bootloader.
The Vulnerabilities used to gain root via SlapMyMoto on 4.4, and Pie, TowelPieRoot on 4.4.2 are patched in 4.4.4, and there is no root on 4.4.4 unless you unlock the bootloader and flash a custom recovery to root.
That being said. If you have NEVER upgraded to 4.4.4, you could try Sunshine to unlock your bootloader. Its $25, but it checks if your phone is compatible before it charges you. This thread discusses it -> http://forum.xda-developers.com/moto-x/general/request-help-exploit-moto-x-bl-t2828471
And in case you missed the many posts/threads... Once on 4.4.2 or up, DO NOT DOWNGRADE or attempt to downgrade!!!! You will end up with a Brick!! (So this means if you have 4.4.4, you can't downgrade to 4.4.2 or 4.4 to try and use the older exploits/processes.)

that's actually what i did.. lol, thanks though.

[Q] XT1053 4.4.4 Root?

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.