Okay, I have to ask. Has anyone successfully downgraded a 4.4.4 KitKat Moto X (2013) to a previous firmware version?
I have the XT1058 "ghost" if that matters.
Seriously? This has only been covered nearly everyday since 4.4.2 became available. In other words, the answers are out there if you simply open your eyes or search.
No not possible to downgrade from 4.4.4
Yes, but for every one that claim they did.... 10 others have bricked.
And the ones that say they downgraded OK, may be in for a bad surprise next time they take an ota.
So, don't... Unless you are able to replace it if you need to. ?
Darth said:
Yes, but for every one that claim they did.... 10 others have bricked.
And the ones that say they downgraded OK, may be in for a bad surprise next time they take an ota.
So, don't... Unless you are able to replace it if you need to. ?
Click to expand...
Click to collapse
This is the info I wanted. Thanks.
Hi, my phone is xt1056, BL unlocked, I was fully flashed (enabled all the options in the xml file) the ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml with rsd to upgrade 4.4.4 once.
Then I fully flashed my xt1056 with the xt1060 rom (VZW_XT1060_4.4.2-KXA20.16-1.25.2_CFC_1FF.xml) in rsd. Now the phone is 4.4.2 and no signal, but it is 4.4.2, I can get my SPC with the app SPCUtility.apk.
After get my SPC, I was fully flashed the xt1056 (ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml with rsd to upgrade 4.4.4) again and works well (need to unlock the network again).
It really doesn't help me that you have the Sprint version. The AT&T bootloader can't be unlocked. At least not to my knowledge.
Downgrading with an unlocked bootloader is no different than locked... Extremely dangerous.
And the poster above who downgraded, then upgraded again... I would not take any OTA's going forward. Or you might get an unfortunate surprise.
DarkWolffe said:
It really doesn't help me that you have the Sprint version. The AT&T bootloader can't be unlocked. At least not to my knowledge.
Click to expand...
Click to collapse
If you have 4.4.4 on an ATT device, right its bootloader can not be unlocked at this point.
As for flashing, as many have said IT IS NOT SAFE to downgrade, unlocked and locked bootloader included.
There are parts that are included with 4.4.2 and up that prevent downgrading. Because of this, under certain circumstances when trying to downgrade (like from 4.4.2 to 4.4 or lower, or 4.4.4 to 4.4.2 or lower), you could either brick your phone, or set it up to brick in the future when you take an upgrade.
In the case of some who have bricked by downgrading, flashing the latest (4.4.4 currently) SBF via mFastboot commands, with a few extra steps, has been enough to revive the phone. Other times, not.
For as many stories you might see of "its safe" or "I've done it", a future OTA will likely get them. Plus there are many more who have created "I bricked when trying to downgrade, HELP!!" threads.
A few Examples of bricked while downgrading:
http://forum.xda-developers.com/moto-x/moto-x-qa/xt-1053-to4-4-4-to-4-4-3-prob-wit-t2967182
http://forum.xda-developers.com/moto-x/moto-x-qa/expert-opinion-to-stock-t2944721
http://forum.xda-developers.com/moto-x/moto-x-qa/totally-bricked-t2952064
http://forum.xda-developers.com/moto-x/general/load-os-moto-x-t2942785
(keep looking in the Q&A section, or General section, you'll see lots more of them!)
And why do you think this thread exists? -> http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
I'll quote myself from another thread (in reply to someone that had an Unlocked bootloader)...
KidJoe said:
The moto x is not a nexus device. Unlike gaining S-off on an HTC phone, unlocking the bootloader on a moto x doesn't disable its security checks.
You can't downgrade got.bin and motoboot.img, or their internal components due to the phone's security checks.
People try downgrade by skipping those, BUT too often people brick when attempting this, or taking an OTA update in this state.
When you have mismatched parts on the phone, things don't work (like the issue of going settings-> security kicking you out) and you are at risk for bricking.
Click to expand...
Click to collapse
Again, this info applies whether you have an unlocked or locked bootloader.
So it is suggested you just stick with what is on your phone once you get on 4.4.2 or newer.
KidJoe said:
If you have 4.4.4 on an ATT device, right its bootloader can not be unlocked at this point.
As for flashing, as many have said IT IS NOT SAFE to downgrade, unlocked and locked bootloader included.
There are parts that are included with 4.4.2 and up that prevent downgrading. Because of this, under certain circumstances when trying to downgrade (like from 4.4.2 to 4.4 or lower, or 4.4.4 to 4.4.2 or lower), you could either brick your phone, or set it up to brick in the future when you take an upgrade.
In the case of some who have bricked by downgrading, flashing the latest (4.4.4 currently) SBF via mFastboot commands, with a few extra steps, has been enough to revive the phone. Other times, not.
For as many stories you might see of "its safe" or "I've done it", a future OTA will likely get them. Plus there are many more who have created "I bricked when trying to downgrade, HELP!!" threads.
A few Examples of bricked while downgrading:
http://forum.xda-developers.com/moto-x/moto-x-qa/xt-1053-to4-4-4-to-4-4-3-prob-wit-t2967182
http://forum.xda-developers.com/moto-x/moto-x-qa/expert-opinion-to-stock-t2944721
http://forum.xda-developers.com/moto-x/moto-x-qa/totally-bricked-t2952064
http://forum.xda-developers.com/moto-x/general/load-os-moto-x-t2942785
(keep looking in the Q&A section, or General section, you'll see lots more of them!)
And why do you think this thread exists? -> http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
I'll quote myself from another thread (in reply to someone that had an Unlocked bootloader)...
Again, this info applies whether you have an unlocked or locked bootloader.
So it is suggested you just stick with what is on your phone once you get on 4.4.2 or newer.
Click to expand...
Click to collapse
Perfect answer. Thank you for the clarity.
Related
Informative Thread Google Cached
READ CAREFULLY
WARNING
DO NOT FLASH THE NEW 4.4.2 SBF FIRMWARE UNLESS YOUR CARRIERS FIRMWARE IS AVAILABLE.
FOLKS HAVE FLASHED OTHER CARRIERS FIRMWARE AND AS A RESULT THEY HAVE NO DATA CONNECTION,
YOU CAN NOT DOWNGRADE, SO IF THIS HAPPENS CHANCES ARE YOU'LL HAVE A PHONE THATS UNUSABLE UNTIL AND IF YOUR CARRIERS SBF SHOWS UP.
THERE IS A CHANCE THAT EVEN AFTER YOU FLASH THE CORRECT FIRMWARE, YOUR RADIO SIGNAL MAY NEVER WORK
I will not in any fashion help anyone to upgrade nor downgrade their moto, this thread is for info only. I personally will not take any responsibility for any issues. You own it ., you alone broke it
Motorola bootloader unlocking website https://motorola-global-portal.custh...-your-device-a
WARNING WARNING
DO NOT FLASH ANY OTA 4.4.2 ,OTA ROM OR ANY SUCH MEANS OF UPGRADING WITHOUT HAVING YOUR SPECIFIC CARRIER 4.4.2 SBF FIRMWARE AS A BACK UP
WARNING WARNING WARNING
IF YOU HAVE A LOCKED BOOTLOADER ONLY FLASH YOUR SPECIFIC CARRIERS SBF FIRMWARE, OTHERWISE YOU WILL END UP WITH A HARD BRICKED DEVICE
************************************************** ********
If you Frankenstein a way of downgrading do not post it here, this thread is not about tricks, hacks or any such garbage. This thread is to inform folks in the correct way of maintaining your moto to work. Plain and simple
There's a tremendous amount of firmware flashing which is causing harm to many users phones.
Realize that having a unlocked boot loader moto, regardless if its a DE will also suffer from hard bricks.
Unlocked boot loaders can flash other variants system.img's without to many issues
Modems are a different story, some user report no data with European modems, so I suggest using your specific carriers modems
Stay away from motoboot.img (boot loader) or gpt.bin(partition table) be warned
Remember you and you alone are responsible for any hard bricks
********************************
This is a simple chart what can and can't not be downgraded, Thanks to Dray_jr :thumbup:
the only OTA that can downgrade is 4.4 to 4.2.2 Post Cam
here is what we know right now that might make more sense
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
************************************************** **************
WARNING if you manage to flash back to 4.4 or even 4.2.2 with the new 4.4.2 BOOTLOADER DO NOT UNDER ANY CIRCUMSTANCE ACCEPT ANY OTA, YOU WILL HARD BRICK YOUR DEVICE, PROOF BELOW
Quote
******** "it was running on 4.4.2 software, then i downgrade to 4.2.2. all was fine, but OTA killed it.
So after that, i read that 4.4.2 instaled new bootloader =( that cant be downgraded, and can bricked the phone, it was my mistake =(
So i think i should sent it to Motorola and if i lucky one, they should repair it, or resend new one. or if bad luck i will throw it to the trash =)"*******
Files inside sbf firmware:
Motoboot.img (bootloader)
gpt.bin ( Partition table)
NON_HLOS (modem)
System
Recovery
Bootloaders:
4.4.2 North , Central & South America:
Rogers 30.B4
US Cellular 30.B4
Brazil Retail 30.B4
T-Mobile 30.B4
Sprint 30.B4
Europe:
UK 30.B3
Modems:
Rogers 4.4.2
Stock Recovery:
Rogers Stock Recovery 4.4.w
4.2.2 pre camera boot loader 30.70
4.2.2 post camera bootloader 30.71
Issues:,
Confirmed by Steve x , you can not downgrade bootloader from 4.4.2
WARNING WARNING
The Brazilian phone and central American phones will not have a data connection with the uk or DE firmware, so do not flash any European firmware, be warned
I think the community would benefit if this were a sticky posted as a closed thread:
GoogleCache said:
the only OTA that can downgrade is 4.4 to 4.2.2 Post Cam
here is what we know right now that might make more sense
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
I would be really really careful bro your stealing alot of people work without quoting them by posting this I should know some of this work is mine
Sent from my XT1056 using XDA Premium 4 mobile app
I don't even have this device and know you can't downgrade. Why don't you try reading a little instead of posting.
Sent from my SAMSUNG-SGH-I727
OK stepping hers as this is my work, its people like the op that just make me hate xda, the poster of this thread which was original done by me should be ignored , do not give him the time of , its not worth it, just move on, he knows where he got all the info which is incomplete and he's the reason why I removed it original
Sent on my Gummy running Lenoto X
!!
flashallthetime said:
OK stepping hers as this is my work, its people like the op that just make me hate xda, the poster of this thread which was original done by me should be ignored , do not give him the time of , its not worth it, just move on, he knows where he got all the info which is incomplete and he's the reason why I removed it original
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
THIS^^^^^^
Do not post crap like "well this was in Google cache" when it is clearly posted whose work it is! Credits MUST be posted. also you are only looking for a fight OP by claiming to report every post that disagrees with you or questions your credibility..do not waste moderator's time!
Thread cleaned and closed
Hi, tried searching my answer, but still not clear as to the answer for my situation, im about to purchase the unlock code for my non DE verizon moto x , code is from someone from china. If i upgrade to 4.4.2 while unlocked bootloader, any way back to 4.2.2 post camera update. Thanks
ericizzy1 said:
Hi, tried searching my answer, but still not clear as to the answer for my situation, im about to purchase the unlock code for my non DE verizon moto x , code is from someone from china. If i upgrade to 4.4.2 while unlocked bootloader, any way back to 4.2.2 post camera update. Thanks
Click to expand...
Click to collapse
Yes and No
No you can not flash the complete 4.2.2 PCU package it will fail because you can't downgrade the bootloader
Yes because you can flash everything but the bootloader and it will take but if you accidentally take a OTA. you will brick your device.
but if you are able to unlock your bootloader then why would you want to downgrade. with a unlocked bootloader you will be able to root 4.4.2 with no issues
because when I was on 4.4, I had some battery consumption and heating issues also bluetooth was not perfect, I just wanted to make sure I have a way back To 4.2.2
also, not being able to downgrade the bootloader, in which way does this affect me going back to four point 4.2.2?
Your phone will work fine but like i said if you ever take a ota it will brick your phone
Sent from my XT1056 using XDA Premium 4 mobile app
dray_jr said:
Your phone will work fine but like i said if you ever take a ota it will brick your phone
Sent from my XT1056 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ota will brick, will be able to rsd to 4.4 or 4.4.2 if wanted?
Yup that is correct
Sent from my XT1056 using XDA Premium 4 mobile app
ericizzy1 said:
ota will brick, will be able to rsd to 4.4 or 4.4.2 if wanted?
Click to expand...
Click to collapse
No. Once you start mixing bootloader versions with system file versions (i.e. 4.4.2 bootloader with 4.2.2 system files), RSD Lite won't work. You will have to use a command line and mfastboot.exe to manually flash each partition.
And I actually tried to run 4.2.2 (post camera update) system files with a 4.4.2 bootloader and it would not boot; however, 4.4 system files do work with a 4.4.2 bootloader.
This has actually been discussed at great length and detail in this forum and A LOT of people were bricking their phones playing around with bootloader versions, just like you are talking about doing. At one point there was a sticky dedicated to it, but its since disappeared from the board for some reason.
To put it simply, please don't start mixing bootloader versions with system files. If you like 4.2.2, don't upgrade to 4.4.2. If you are on 4.4, then you can still downgrade to 4.2.2 (post camera update version). Do that and stay there. But if you upgrade to 4.4.2, don't fool around with it and start trying to downgrade. There is no point, and you will likely end up bricking your phone.
It's your phone, so do what you want, but you have been warned (by someone with personal experience by the way). If you do brick it, please don't start another "OMG! HELP ME!! I BRICKED MY PHONE!!" thread. There's plenty of those already floating around here. :good:
So, I did some digging around here, and I am more confused than ever. Here is my quick question (hopefully)
I have an bootloader unlocked xt1058 (ATT branded). I ran a nandroid to flash a new rom, only to discover when i went to restore a nandroid, the system folder did not back up, therefore I do not have a /system folder backup of stock ATT 4.4.2.
What I want to know is: Can I fastboot flash ATT's 4.4 system file only (i know bootloader is not compatable), then take the 4.4.2 OTA? Or will this hard brick my phone?
If i searched the forums correctly, it addresses if your bootloader is locked, but not unlocked.
I am running an AOSP now, so i know my way around fastboot and adb.
Any assistance would be helpful, and a flashable zip of stock ATT 4.4.2 would kick a**
Thanks for the help!
I'm not sure exactly how, cause I never have, or would downgrade......but just be sure you find out exactly how to do it. An unlocked boot loader will not protect you from a brick if something is done wrong. In other words....there are ways to brick for sure....locked or unlocked.
To me its a risky endeavor no matter what the case. Mistakes happen.....and in the case of downgrading from 4.4.2....mistakes can cost you a phone. ?
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
kj2112 said:
I'm not sure exactly how, cause I never have, or would downgrade......but just be sure you find out exactly how to do it. An unlocked boot loader will not protect you from a brick if something is done wrong. In other words....there are ways to brick for sure....locked or unlocked.
To me its a risky endeavor no matter what the case. Mistakes happen.....and in the case of downgrading from 4.4.2....mistakes can cost you a phone. ?
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
Click to expand...
Click to collapse
Yep! Hence the question. I guess the real question is...with an unlocked bootloader, can i flash System and Recovery (Android 4.4), while on Bootloader (Android 4.4.2)
would the safest thing to do to use RSD and flash (which will stop if there is a security issue)?
I'd just wait for the flash able 4.4.2 files.
Why do you want 4.4 anyway? There's not much difference.... Except a few negatives.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
cpetersen2791 said:
What I want to know is: Can I fastboot flash ATT's 4.4 system file only (i know bootloader is not compatable), then take the 4.4.2 OTA? Or will this hard brick my phone?
Click to expand...
Click to collapse
Yes this will brick your phone. If you are on 4.4.2, and downgrade only parts (say system.img), you'll have a version and security mismatch, including the bootloader and GPT.BIN. If you take an OTA in that state you will brick. (at least that is what many of the users who have bricked have done according to the threads I've read... I haven't actually done it first hand as I don't want to deal with a brick).
cpetersen2791 said:
If i searched the forums correctly, it addresses if your bootloader is locked, but not unlocked.
Click to expand...
Click to collapse
This applies for locked and unlocked bootloaders.
cpetersen2791 said:
Any assistance would be helpful, and a flashable zip of stock ATT 4.4.2 would kick a**
Thanks for the help!
Click to expand...
Click to collapse
As soon as the SBF for ATT 4.4.2 leaks out, I'm sure it will be available on -> http://sbf.droid-developers.org/phone.php?device=0
kj2112 said:
I'd just wait for the flash able 4.4.2 files.
Why do you want 4.4 anyway? There's not much difference.... Except a few negatives.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
Click to expand...
Click to collapse
when i ran a "stock" nandroid to test AOSP roms, i failed to back up my system folder, therefore I don't have a Stock ATT OS. I know 4.4.2 was out, but only as OTA, but complete 4.4 was available.
Thanks for all the assistance, i'll wait for the 4.4.2 SBF.
I updated my Motorbike X XT1058 for 4.4.4 (KXA21.12 VZW_XT1060_4.4.4-KXA21.12-L1.26_1FF) and it wanted to do the DOWNGRADE for 4.4.3 or 4.4.2. Some way for that?
The GPT.BIN in 4.4.4 is different from 4.4.3, which is different from 4.4.2, which is different from 4.4.0's.
Motoboot.img is different between 4.4.3 and 4.4.2. 4.4.2's is different from 4.4.0.
These will prevent a complete, successful and safe downgrade of the rom version.
If you've seen all the "don't downgrade or you'll brick" warnings, this is what its talking about.
This ^^^
But a better question is WHY would you want to downgrade?
I did not like because of the modification Verizon
Christian Correia said:
I did not like because of the modification Verizon
Click to expand...
Click to collapse
Well, you really can't downgrade without great risk.
So better to live with it, or try the Chinese seller and unlock your bootloader for a fee. Then you can root, and change things that you can't change without root. Here is a long thread about the unlock code seller...
http://forum.xda-developers.com/showthread.php?t=2751177
Otherwise, there isn't much you can do.
Darth said:
Well, you really can't downgrade without great risk.
So better to live with it, or try the Chinese seller and unlock your bootloader for a fee. Then you can root, and change things that you can't change without root. Here is a long thread about the unlock code seller...
http://forum.xda-developers.com/showthread.php?t=2751177
Otherwise, there isn't much you can do.
Click to expand...
Click to collapse
Actually you can do something that is risk because everything is a risk you can take and you never know what can happen but here it is: you can flash the 4.4.3 or 4.4.2 or 4.4.0 update over the 4.4.4 by using minimal adb flash tool and then just flash the 4.4.2 or desired version over but DO NOT FLASH THE gpt.bin!!!!!!!!That will screw up everything so after you flash everything but the gpt.bin you should do a cmd to reboot then you will be on the downgraded version!!! I'm not responsible for any bricked phones OK I tried this and the it worked for me so yea its a working procedure that YeS is a risky task so be careful!!!!:laugh:
DROID_4_UsEr said:
Actually you can do something that is risk because everything is a risk you can take and you never know what can happen but here it is: you can flash the 4.4.3 or 4.4.2 or 4.4.0 update over the 4.4.4 by using minimal adb flash tool and then just flash the 4.4.2 or desired version over but DO NOT FLASH THE gpt.bin!!!!!!!!That will screw up everything so after you flash everything but the gpt.bin you should do a cmd to reboot then you will be on the downgraded version!!! I'm not responsible for any bricked phones OK I tried this and the it worked for me so yea its a working procedure that YeS is a risky task so be careful!!!!:laugh:
Click to expand...
Click to collapse
First this is an old thread...
Next, skipping gpt.bin and/or motoboot.img(or its components) HAS been a cause for bricks, and when it didn't brick, it caused extra bugs (like trying to go App Drawer -> Settings -> Security kicks you back to settings menu... and some having issues toggling wifi on/off... and some who tried skipping gpt/motoboot when applying the 5.1 update also had speaker phone issues).
For more, see the link in my signature on downgrading..
KidJoe said:
First this is an old thread...
Next, skipping gpt.bin and/or motoboot.img(or its components) HAS been a cause for bricks, and when it didn't brick, it caused extra bugs (like trying to go App Drawer -> Settings -> Security kicks you back to settings menu... and some having issues toggling wifi on/off... and some who tried skipping gpt/motoboot when applying the 5.1 update also had speaker phone issues).
For more, see the link in my signature on downgrading..
Click to expand...
Click to collapse
My mistake you need to flash the 4.4.4 gpt.bin over the 4.4.2 gpt.bin so the device thinks your flashing a 4.4.4 firmware but in reality your flashing the 4.4.2 firmware..I think its easier to use RSD lite to flash the firmware but you need to do a couple of modifications to the 4.4.2 firmware.All you got to do is move the 4.4.4 gpt.bin to the 4.4.2 firmware then flash it if you get the moto.bin error just do the same step as said above with the gpt.bin but with the moto.bin file..Hopefully it worked out for you ?
DROID_4_UsEr said:
My mistake you need to flash the 4.4.4 gpt.bin over the 4.4.2 gpt.bin so the device thinks your flashing a 4.4.4 firmware but in reality your flashing the 4.4.2 firmware..I think its easier to use RSD lite to flash the firmware but you need to do a couple of modifications to the 4.4.2 firmware.All you got to do is move the 4.4.4 gpt.bin to the 4.4.2 firmware then flash it if you get the moto.bin error just do the same step as said above with the gpt.bin but with the moto.bin file..Hopefully it worked out for you ?
Click to expand...
Click to collapse
Not sure why you are quoting me saying "hopefully it worked out..." as I'm not the one trying to downgrade.
I can assure you... mixing GPT.BIN/Motoboot.img parts from one Stock rom, with the GPT.BIN/Motoboot.img of another STOCK rom is not a good idea.. it has been cause for bricks and/or features not working correctly.
To suggest otherwise, without acknowledging the risks, is irresponsible, especially if you take some time to search the forums and see all the posts of people who have either soft or hard bricked their device while trying various processes to downgrade. And especially if you are someone willing to help those who have bricked following your advice.
I did try but no succes
KidJoe said:
Not sure why you are quoting me saying "hopefully it worked out..." as I'm not the one trying to downgrade.
I can assure you... mixing GPT.BIN/Motoboot.img parts from one Stock rom, with the GPT.BIN/Motoboot.img of another STOCK rom is not a good idea.. it has been cause for bricks and/or features not working correctly.
To suggest otherwise, without acknowledging the risks, is irresponsible, especially if you take some time to search the forums and see all the posts of people who have either soft or hard bricked their device while trying various processes to downgrade. And especially if you are someone willing to help those who have bricked following your advice.
Click to expand...
Click to collapse
How can you downgrade from 4.4.4 to 4.4.2? I did try to downgrade the XT1060 Verizon,but it cannot be done,did try all options cut a line here ,edit a line there but still end up with the same 4.4.4 version.The idea i have is to downgrade to 4.4.2 and the use the sunshine to unlock the bootloader and after that to flash any ROM out there ,but never upgrade back to 4.4.4...Any help would be helpful...
Best Regards!
DejanPet said:
How can you downgrade from 4.4.4 to 4.4.2? I did try to downgrade the XT1060 Verizon,but it cannot be done,did try all options cut a line here ,edit a line there but still end up with the same 4.4.4 version.The idea i have is to downgrade to 4.4.2 and the use the sunshine to unlock the bootloader and after that to flash any ROM out there ,but never upgrade back to 4.4.4...Any help would be helpful...
Best Regards!
Click to expand...
Click to collapse
It all depends on what rom you wanna flash if you flash cyanogenmod 12.1 you'll get the Lollipop update if you flash Cyanogenmod 11 you'll get back to kit-kat.
---------- Post added at 05:23 PM ---------- Previous post was at 05:20 PM ----------
DROID_4_UsEr said:
It all depends on what rom you wanna flash if you flash cyanogenmod 12.1 you'll get the Lollipop update if you flash Cyanogenmod 11 you'll get back to kit-kat.
Click to expand...
Click to collapse
But you should know Sunshine developers charge a fee of 25 bucks to unlock and it works but you need to have a pay pal account and enough money for it
DejanPet said:
The idea i have is to downgrade to 4.4.2 and the use the sunshine to unlock the bootloader and after that to flash any ROM out there ,but never upgrade back to 4.4.4...Any help would be helpful...
Best Regards!
Click to expand...
Click to collapse
its documented in the sunshine thread that once 4.4.4 is on your phone its too late. even if you manage to downgrade it without bricking, the parts sunshine relies on will already have been patched and cant be downgraded. so downgrading wont help you to get sunshine to work
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.