Moto X DE rooted. VZW native tether hack. Replaced the "warning unlocked bootloader" message. The rest is stock. Is the 4.4.2 update worth it? I don't see anything that appears to be much different from 4.4
I have a Dev X and pretty much in the same boat as you.... Unlocked, Rooted, changed logo.bin, but I'm using Wifi Tether for root app rather than the entitlement apk hack.
I took the OTA when it hit my phone. I can't say that I notice anything really different after the upgrade. No negative impacts at least.
It was easy to take because I was basically stock... just flash stock recovery back on, and take the OTA. Since it sounds like you did the entitlement apk replacement, you'd need to undo that.
I didn't lose root, and write protection stayed disabled (due to unlocked bootloader). So I just had to reflash my custom logo.bin, and I haven't put custom recovery back on, I don't need to right now. Only issue would be, if I do find a bug that wasn't there in 4.4, I can't downgrade now due to the bootloader update.
KidJoe said:
I have a Dev X and pretty much in the same boat as you.... Unlocked, Rooted, changed logo.bin, but I'm using Wifi Tether for root app rather than the entitlement apk hack.
I took the OTA when it hit my phone. I can't say that I notice anything really different after the upgrade. No negative impacts at least.
It was easy to take because I was basically stock... just flash stock recovery back on, and take the OTA. Since it sounds like you did the entitlement apk replacement, you'd need to undo that.
I didn't lose root, and write protection stayed disabled (due to unlocked bootloader). So I just had to reflash my custom logo.bin, and I haven't put custom recovery back on, I don't need to right now. Only issue would be, if I do find a bug that wasn't there in 4.4, I can downgrade now due to the bootloader update.
Click to expand...
Click to collapse
You don't have root unless you put the custom recovery back on there.
Sent from my Dev Edition Moto X
KidJoe said:
Only issue would be, if I do find a bug that wasn't there in 4.4, I can downgrade now due to the bootloader update.
Click to expand...
Click to collapse
Not to nag, but probably important to correct... you CAN'T downgrade now.
Updated last night. I did it cause I wanted to be on latest and greatest, plus I think the camera does take better low-light pictures now.
Schaweet said:
You don't have root unless you put the custom recovery back on there.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
No, you'll keep root after taking the update. You do not need to reinstall TWRP to have root. Root is root, a recovery is a recovery. If you lost root, you'd need to install a recovery that allows you to install root, but you don't lose root from taking the OTA.
cw18306 said:
Moto X DE rooted. VZW native tether hack. Replaced the "warning unlocked bootloader" message. The rest is stock. Is the 4.4.2 update worth it? I don't see anything that appears to be much different from 4.4
Click to expand...
Click to collapse
Not much different, you can always update everything but motoboot and gpt so you can still downgrade if you don't like...
http://forum.xda-developers.com/moto-x/development/xt1060-164-55-2-unofficial-fxz-unlocked-t2659682
FWIW, The only things I notice are that USB OTG works in 4.4.2 and static in bluetooth headphones when using wifi is gone.
Schaweet said:
You don't have root unless you put the custom recovery back on there.
Click to expand...
Click to collapse
I beg to differ. Root Explore, Greenify, Wifi Tether for Root... all work, as do going into system and renaming files, and downloading/installing the hosts file in AdAway from BigTinCan.com (which survive power off/on, so helps to tell me write protection is still disabled).
On an unlocked bootloader, once you have rooted, you can use whatever recovery you like.
Now, for LOCKED bootloader on the X which are rooted via RockMyMoto or SlapMyMoto without using MotoWPNoMo, you might need to keep that "recovery trick" in place so you can boot with write protect disabled. In that case you would loose the ability to boot with write protect disabled (which makes root useless) when you put stock recovery back on, but that is different and doesn't "unroot" you.
---------- Post added at 10:19 AM ---------- Previous post was at 10:18 AM ----------
Mike7143 said:
Not to nag, but probably important to correct... you CAN'T downgrade now.
Click to expand...
Click to collapse
You are right. that is a Typo that I need to fix!!!
cw18306 said:
Moto X DE rooted. VZW native tether hack. Replaced the "warning unlocked bootloader" message. The rest is stock. Is the 4.4.2 update worth it? I don't see anything that appears to be much different from 4.4
Click to expand...
Click to collapse
It took me about an hour to do the update because I am a novice and had to do a bunch of stuff first but I did it and my phone is back to its current state...except now I am using the xposed wifi tether instead of the hack (And the xposed one is better). So it was worth it just to have the latest and get rid of that wifi mod that i never liked to begin with. Apparently the upate makes battery life better but my battery life was already awesome considering I came from Gnex. So I guess the question is why not update? If you know what you are doing it shouldnt take 5-10 minutes.
from what people are saying it seems 4.4.2 makes a huge difference for battery life, i don't have it yet on my xt1058 so i can't say for sure...
Yeah I really only root for the tether hack and tibackup. Both of which I've used less and less since I got this phone. I've never had any issues with the phone and battery life is awesome so I'll probably just wait for some more feedback on the update before I go through the hassle of doing it.
How do you get rid of the unlocked bootloader message? Just flashing logo.bin?
jawest12 said:
How do you get right of the unlocked bootloader message? Just flashing logo.bin?
Click to expand...
Click to collapse
Yes replacing logo.bin. the logo.bin's I made for 4.4 work on 4.4.2 too.
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
CartlandSmith said:
If you are rooted and locked on 4.4 using SlapMyMoto and MotoWPNoMo, can you downgrade to 4.2.2 and use PwnMyMoto then RockMyMoto then SlapMyMoto 0.5c to get the "recovery trick" back? Or is the ability to do that gone once you have used MotoWPNoMo?
Click to expand...
Click to collapse
I am not sure since I have a Dev Edition with an unlocked bootloader, so I never used them... only read about them.
KidJoe said:
Yes replacing logo.bin. the logo.bin's I made for 4.4 work on 4.4.2 too.
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
I am not sure since I have a Dev Edition with an unlocked bootloader, so I never used them... only read about them.
Click to expand...
Click to collapse
Thank you for the response. Where can I download your logo.bin to flash?
tcrews said:
No, you'll keep root after taking the update. You do not need to reinstall TWRP to have root. Root is root, a recovery is a recovery. If you lost root, you'd need to install a recovery that allows you to install root, but you don't lose root from taking the OTA.
Click to expand...
Click to collapse
For a n00b,,,,,English please?!
jawest12 said:
Thank you for the response. Where can I download your logo.bin to flash?
Click to expand...
Click to collapse
See the "edit" section of Post #150 in this thread -> Moto X Boot Logos The post also has info how they were made and a link to a zip that contains a little more than 25 LOGO.BIN files, and matching BMP's so you can see what they look like first (or use to flash clogo if you have never unlocked your bootloader). they do include the 0-3% battery indication too.
I'm using Logo-prettydev2.png.bin included in the zip file.
PennyKnight said:
For a n00b,,,,,English please?!
Click to expand...
Click to collapse
Moto X Developer Edition only....as this thread title states a DE model.
The OTA doesn't remove ROOT. You need the stock recovery to install the OTA so you have to flash the stock recovery.img back to the phone to install the OTA. Once the OTA is done.....you do NOT need to install TWRP or any other recovery to have root. You never lost root.
All of this is assuming you had previously installed TWRP to root a Moto X Developer Edition (DE) and want the OTA to 4.4.2.
tcrews said:
Moto X Developer Edition only....as this thread title states a DE model.
The OTA doesn't remove ROOT. You need the stock recovery to install the OTA so you have to flash the stock recovery.img back to the phone to install the OTA. Once the OTA is done.....you do NOT need to install TWRP or any other recovery to have root. You never lost root.
All of this is assuming you had previously installed TWRP to root a Moto X Developer Edition (DE) and want the OTA to 4.4.2.
Click to expand...
Click to collapse
Also for noobs, how do I flash the stock recovery?
Also, does flashing stock recovery erase any data? (Like messages/pictures/etc..? If not, what actions actually erase this data... I feel like I never know)
Sent from my XT1060 using xda app-developers app
zackiv31 said:
Also, does flashing stock recovery erase any data? (Like messages/pictures/etc..? If not, what actions actually erase this data... I feel like I never know)
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
No. Flashing Recovery does NOT erase data. Using RSDLite to flash an entire SBF/XML file (without editing it) will erase data.. or giving the following command via PC with your phone in fastboot mode will erase data... mfastboot erase data
KidJoe said:
I have a Dev X and pretty much in the same boat as you.... Unlocked, Rooted, changed logo.bin, but I'm using Wifi Tether for root app rather than the entitlement apk hack.
It was easy to take because I was basically stock... just flash stock recovery back on, and take the OTA. Since it sounds like you did the entitlement apk replacement, you'd need to undo that.
How do I undo the entitlement apk. I tried to reverse it but messed it up.
Not good at that stuff.
Thanks
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Related
Hi,
Does anyone know where I can find the stock recovery for the Sprint Moto X? I have TWRP right now and I want to prepare for the Kit Kat update.
Its my understanding that I will need to fastboot flash the stock recovery to take the update. I don't have much faith that a flashable 4.4 rom will happen anytime soon.
Any help would be appreciated.
Sent from my XT1056 using Tapatalk
No one?
Sent from my Nexus 7 using Tapatalk 4
Well, you could consider visiting -> http://sbf.droid-developers.org/ghost/list.php See if there is a copy of the ROM your phone is currently on... If so, download it and unzip it.
And since you have TWRP installed, I'm going to say you've unlocked your bootloader, and likely rooted.. That also might impact the install of 4.4. Did you remove any bloat, mess with system files, or freeze any apps with something like Titanium Backup? That too can impact the install of 4.4.
If you're interested take a look at -> http://forum.xda-developers.com/showthread.php?t=2536735
KidJoe said:
Well, you could consider visiting -> http://sbf.droid-developers.org/ghost/list.php See if there is a copy of the ROM your phone is currently on... If so, download it and unzip it.
And since you have TWRP installed, I'm going to say you've unlocked your bootloader, and likely rooted.. That also might impact the install of 4.4. Did you remove any bloat, mess with system files, or freeze any apps with something like Titanium Backup? That too can impact the install of 4.4.
If you're interested take a look at -> http://forum.xda-developers.com/showthread.php?t=2536735
Click to expand...
Click to collapse
Is the link with the sbf files for consumer devices only? I have a dev edition on its way and thought I read if you flash the non dev sbf you will also install security stuff for non dev edition devices you don't want. Thanks in advance!
KidJoe said:
Well, you could consider visiting -> http://sbf.droid-developers.org/ghost/list.php See if there is a copy of the ROM your phone is currently on... If so, download it and unzip it.
And since you have TWRP installed, I'm going to say you've unlocked your bootloader, and likely rooted.. That also might impact the install of 4.4. Did you remove any bloat, mess with system files, or freeze any apps with something like Titanium Backup? That too can impact the install of 4.4.
If you're interested take a look at -> http://forum.xda-developers.com/showthread.php?t=2536735
Click to expand...
Click to collapse
I did uninstall some apps, but not much. My plan was to reinstall the factory recovery, then factory reset before accepting the ota.
This being my first Moto device, I'm not really familiar with all this .sbf stuff. Are you saying the stock recovery would be part of it?
Sent from my XT1056 using Tapatalk
MichaelMcEntire said:
I did uninstall some apps, but not much. My plan was to reinstall the factory recovery, then factory reset before accepting the ota.
This being my first Moto device, I'm not really familiar with all this .sbf stuff. Are you saying the stock recovery would be part of it?
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
The stick recovery can be found in the sbf zips
Sent on my Moto X
Travisdroidx2 said:
Is the link with the sbf files for consumer devices only? I have a dev edition on its way and thought I read if you flash the non dev sbf you will also install security stuff for non dev edition devices you don't want. Thanks in advance!
Click to expand...
Click to collapse
There was talk/speculation that when flashing the Dev edition with "non-dev" SDF/FXZ files you'd revert to a "consumer"/Locked device. I am not aware of that being confirmed as 100% true.
When I first got my Dev X, I rooted with RockMyMoto and ran for a week or so before unlocking the bootloader. At the time unlocking the boot loader voided the warranty and I wanted to make sure there were no issues before voiding the warranty. To prep for Kit Kat, I did flash it back using the only 4.2.2 SBF out there, that was for the "consumer" devices. It didn't hurt. I was still able to unlock my boot loader.
At this point, Moto does have the KK dev edition SBFs available for request on their web site if you don't trust using other SBF's. But they do appear to be the same as the "non-dev" sbf files.
---------- Post added at 02:29 AM ---------- Previous post was at 02:18 AM ----------
MichaelMcEntire said:
I did uninstall some apps, but not much. My plan was to reinstall the factory recovery, then factory reset before accepting the ota.
This being my first Moto device, I'm not really familiar with all this .sbf stuff. Are you saying the stock recovery would be part of it?
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
Factory reset will not restore any apps you removed from the phone (i.e. if you deleted the APKs).
SBF and FXZ files are firmware files for Moto. RSDLite is the tool to fully flash an SBF or FXZ file.
The thread I linked earlier (said if you are interested... read...) has several options to return to stock, and explains options for using RSDLite to flash a full SBF/FXZ, as well as mfastboot to flash only parts of the ROM file, which will get you back to stock.
Most of the Moto updates perform checks for files, and specific versions of files before installing. If they don't match stock, or files it expects to be there are missing, the OTA wont install, or get the phone stuck in a boot loop.
Guys,i have Retail 1058 Moto X with unlocked Bootloader,TWRP(latest and rooted) and i want to upgrade to 4.4.2!
Some guys already received the 4.4.2 brazilian update via OTA,and extracted the zip file,but,since im on custom recovery,the OTA doesnt reboot the phone into stock and go straight to TWRP,therefore,doesnt conclude the update,and keep restarting!
Since i need the phone,i did a factory reset via TWRP just to get things going!
But,i want to upgrade to 4.4.2!
Is there a way to do that?remove TWRP ou something else?
I've seen some people saying that i need to flash the 4.4 img which it is inside the zip but,i dont have that zip anymore!
Thx in advance!
msespindola said:
Guys,i have Retail 1058 Moto X with unlocked Bootloader,TWRP(latest and rooted) and i want to upgrade to 4.4.2!
Some guys already received the 4.4.2 brazilian update via OTA,and extracted the zip file,but,since im on custom recovery,the OTA doesnt reboot the phone into stock and go straight to TWRP,therefore,doesnt conclude the update,and keep restarting!
Since i need the phone,i did a factory reset via TWRP just to get things going!
But,i want to upgrade to 4.4.2!
Is there a way to do that?remove TWRP ou something else?
I've seen some people saying that i need to flash the 4.4 img which it is inside the zip but,i dont have that zip anymore!
Thx in advance!
Click to expand...
Click to collapse
if you take the 4.4.2 update you will loose root and wont be able to get it back till who knows when.
but you need to flash your phone back to 100% stock just like you did when root your device but instead of using the 4.2.2 CU firmware use the 4.4
here is all the firmware for the Moto X
http://sbf.droid-developers.org/phone.php?device=0
your device is a Att model so you should be able to flash the ATT 4.4 firmware but im not 100% sure but maybe you will find your carrier listed there.
dray_jr said:
if you take the 4.4.2 update you will loose root and wont be able to get it back till who knows when.
but you need to flash your phone back to 100% stock just like you did when root your device but instead of using the 4.2.2 CU firmware use the 4.4
here is all the firmware for the Moto X
http://sbf.droid-developers.org/phone.php?device=0
your device is a Att model so you should be able to flash the ATT 4.4 firmware but im not 100% sure but maybe you will find your carrier listed there.
Click to expand...
Click to collapse
yeah,i know,aware of loosing root,but,mine is retail,and i've found the brazilian retail one(Blur_Version.143.44.8.ghost_row.Brasil.en.BR)!
How do i revert back to stock?never done that before!
Thx for the help so far buddy
msespindola said:
yeah,i know,aware of loosing root,but,mine is retail,and i've found the brazilian retail one(Blur_Version.143.44.8.ghost_row.Brasil.en.BR)!
How do i revert back to stock?never done that before!
Thx for the help so far buddy
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2446515
there are two ways in this guide i like the manual way. but your choice make sure you read everything because if you do this wrong you can brick.
dray_jr said:
http://forum.xda-developers.com/showthread.php?t=2446515
there are two ways in this guide i like the manual way. but your choice make sure you read everything because if you do this wrong you can brick.
Click to expand...
Click to collapse
Okay buddy,will take a look when i get home from work!
One questiona buddy managed to get the fastboot img for me,if i just flash the stock recovery img and then try to update will it work?
msespindola said:
Okay buddy,will take a look when i get home from work!
One questiona buddy managed to get the fastboot img for me,if i just flash the stock recovery img and then try to update will it work?
Click to expand...
Click to collapse
idk i dont like to doing things half way there have been way to many bricks lately.
If he has an unlocked bootloader, why would he not be able to get root back?
I thought when the bootloader was unlocked you had free reign over the device. Shouldn't he be able to upgrade to 4.4.2 and use SU and TWRP to get root back? I don't get why he wouldn't be able to do that.
Flash 4.4.2
Flash TWRP via mfastboot
Install SU zip via TWRP
Boot
Install SU app
What am I missing?
Sent from my Dev Edition Moto X
Schaweet said:
If he has an unlocked bootloader, why would he not be able to get root back?
I thought when the bootloader was unlocked you had free reign over the device. Shouldn't he be able to upgrade to 4.4.2 and use SU and TWRP to get root back? I don't get why he wouldn't be able to do that.
Flash 4.4.2
Flash TWRP via mfastboot
Install SU zip via TWRP
Boot
Install SU app
What am I missing?
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
this is why i dont read on my phone i miss crap anyway if you flash 4.4.2 yes you can flash the 4.4 TWRP and then SuperSU with a unlocked bootloader.. sorry for my miss read thanks for the catch
dray_jr said:
idk i dont like to doing things half way there have been way to many bricks lately.
Click to expand...
Click to collapse
Schaweet said:
If he has an unlocked bootloader, why would he not be able to get root back?
I thought when the bootloader was unlocked you had free reign over the device. Shouldn't he be able to upgrade to 4.4.2 and use SU and TWRP to get root back? I don't get why he wouldn't be able to do that.
Flash 4.4.2
Flash TWRP via mfastboot
Install SU zip via TWRP
Boot
Install SU app
What am I missing?
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
Thx guys, I'll do this later, thx for the awesome responses
Sent from my XT1058 using xda app-developers app
dray_jr said:
idk i dont like to doing things half way there have been way to many bricks lately.
Click to expand...
Click to collapse
Can someone else please chime in on this? I have a Dev Edition VZW Moto X, and when the 4.4.2 update is finally available, I want to know what to do. My phone is unlocked & rooted with TWRP installed. Can I just flash the factory recovery and then take the OTA? Or do I have to revert to 100% stock? If I only flash stock recovery and take the OTA, data won't be wiped, will it? That is the big reason I would like to avoid going back to 100% stock if I can.
NPOA556 said:
Can someone else please chime in on this? I have a Dev Edition VZW Moto X, and when the 4.4.2 update is finally available, I want to know what to do. My phone is unlocked & rooted with TWRP installed. Can I just flash the factory recovery and then take the OTA? Or do I have to revert to 100% stock? If I only flash stock recovery and take the OTA, data won't be wiped, will it? That is the big reason I would like to avoid going back to 100% stock if I can.
Click to expand...
Click to collapse
My hope is that someone on here will repackage the OTA for us to sideload. That would be the best case scenario.
If not, I think you just need a stock recovery, but I could be wrong. I've seen someone say you need to flash stock system as well. I have the same questions as you if we don't get a side loadable zip.
Sent from my Dev Edition Moto X
Schaweet said:
My hope is that someone on here will repackage the OTA for us to sideload. That would be the best case scenario.
If not, I think you just need a stock recovery, but I could be wrong. I've seen someone say you need to flash stock system as well. I have the same questions as you if we don't get a side loadable zip.
Click to expand...
Click to collapse
It's not the end of the world if I have to wipe data and restore everything from TiBu, but it's still a PITA I would like to avoid if possible. More importantly, I don't want to run into any issues when installed the update. So if there is any question as to whether stock recovery alone is sufficient for the update to install properly, I will probably go back to full stock to be safe. I guess I have some time to let smarter people figure it out, since there is no update for VZW yet.
NPOA556 said:
It's not the end of the world if I have to wipe data and restore everything from TiBu, but it's still a PITA I would like to avoid if possible. More importantly, I don't want to run into any issues when installed the update. So if there is any question as to whether stock recovery alone is sufficient for the update to install properly, I will probably go back to full stock to be safe. I guess I have some time to let smarter people figure it out, since there is no update for VZW yet.
Click to expand...
Click to collapse
What I've read is you need to go back to stock recovery and also make sure any /system files are unchanged. For example I renamed my old exchange apk's (in /system/app) when I put in the new ones from the nexus 5 on 4.4.2, so I would need to name those files back.
NPOA556 said:
It's not the end of the world if I have to wipe data and restore everything from TiBu, but it's still a PITA I would like to avoid if possible. More importantly, I don't want to run into any issues when installed the update. So if there is any question as to whether stock recovery alone is sufficient for the update to install properly, I will probably go back to full stock to be safe. I guess I have some time to let smarter people figure it out, since there is no update for VZW yet.
Click to expand...
Click to collapse
I'm sure some nice developer will help us along.
What have you done to take you off of stock?
I just have custom recovery and xposed. Xposed shouldn't cause any issues.
Sent from my Dev Edition Moto X
Schaweet said:
I'm sure some nice developer will help us along.
What have you done to take you off of stock?
I just have custom recovery and xposed. Xposed shouldn't cause any issues.
Click to expand...
Click to collapse
I guess nothing, other than TWRP, Xposed, and obviously root. I have seen several people say that you have to unroot before installed an OTA, but I don't know if that applies to the Dev X or just the standard version. A lot of people seem to indicate that you have to go back to stock, so I just want to clarify what is really required.
NPOA556 said:
I guess nothing, other than TWRP, Xposed, and obviously root. I have seen several people say that you have to unroot before installed an OTA, but I don't know if that applies to the Dev X or just the standard version. A lot of people seem to indicate that you have to go back to stock, so I just want to clarify what is really required.
Click to expand...
Click to collapse
Good questions. I'm not sure. We certainly root differently than a non Dev edition. They might have some files modified that we don't have to modify. Also, I wonder is going to stock recovery will unroot us.
I guess we wait and stay patient.
Sent from my Dev Edition Moto X
Surely there must be a way to flash updates through TWRP?
I want to grab one of these
http://sbf.droid-developers.org/phone.php?device=0
and flash it through TWRP. Anyone know if this is possible?
Wouldn't mind 4.4.2 right now on my dev ed, to see if my bluetooth problem gets fixed.
Unfortunately you can not take the ota if
1- you have custom recovery
2- root
3- changed any system file
It will bootloop
Clearing data is always required after any ota
The only hope you have is if someone decides to take that factory image and runnit through kitchen to make it a flashable zip. You will also need the updated modem from either 4.4 or 4.4.2 to prevent system settings from fc ing
This goes for any moto, retail and or developer edition
You may also attempt to flash the sbf firmware and remove the delete userdata from the XML but no guarantee that you will not have issues
Hope that helps
Sent on my Gummy running Lenoto X
To take an ota you must be stock. Meaning everything. As long as you haven't flashed an updated bootloader you can just flash system.IMG and recovery.IMG from the sbf your phone is currently on you can take an ota. A successful ota does NOT require a data wipe.
---------- Post added at 04:08 PM ---------- Previous post was at 04:04 PM ----------
finalarcadia said:
Surely there must be a way to flash updates through TWRP?
I want to grab one of these
http://sbf.droid-developers.org/phone.php?device=0
and flash it through TWRP. Anyone know if this is possible?
Wouldn't mind 4.4.2 right now on my dev ed, to see if my bluetooth problem gets fixed.
Click to expand...
Click to collapse
You cannot flash any of those through twrp! If you want to flash 4.4.2 you need to fastboot the system.IMG and boot.IMG and you will need to wipe your data. If you choose this route you will not be able to take the ota when its available you'd have to wait for the sbf file to be released and update through house of moto, rsd, or fastboot.
flashallthetime said:
Unfortunately you can not take the ota if
1- you have custom recovery
2- root
3- changed any system file
It will bootloop
Clearing data is always required after any ota
...
Click to expand...
Click to collapse
some questions.. and comments...
I agree with #1. You must have STOCK recovery for an OTA to install properly. And #3, because the OTA generally has a file list with check sums to compare against what is on your device to make sure all required files are there and the correct version/size/etc before it will start to install.
#2 I have a question on as I've not had an issue with this unless the root process makes changes to system files (thus causing a problem for #3). I've lost root taking an OTA, but that is it.
Then again, I have a Dev X with unlocked bootloader, and I don't know enough about RockMyMoto, SlapMyMoto, etc was of rooting the X, except that initially they replaced the recovery partition with an image that when selected/booted allowed write to system, etc. This would cause issue with #1 (no longer have stock recovery on the recovery partition), but not sure what, if any system files get touched or altered from stock.
Finally, you mention clearing data being required... This would wipe you back to factory defaults and remove your apps/data. I don't believe its "required" but rather just suggested as it can make the device run smoother after the update is done.
---------- Post added at 05:01 PM ---------- Previous post was at 04:59 PM ----------
msespindola said:
Guys,i have Retail 1058 Moto X with unlocked Bootloader,TWRP(latest and rooted) and i want to upgrade to 4.4.2!
Some guys already received the 4.4.2 brazilian update via OTA,and extracted the zip file,but,since im on custom recovery,the OTA doesnt reboot the phone into stock and go straight to TWRP,therefore,doesnt conclude the update,and keep restarting!
Since i need the phone,i did a factory reset via TWRP just to get things going!
But,i want to upgrade to 4.4.2!
Is there a way to do that?remove TWRP ou something else?
I've seen some people saying that i need to flash the 4.4 img which it is inside the zip but,i dont have that zip anymore!
Thx in advance!
Click to expand...
Click to collapse
Depends on how you rooted.
If you've downloaded the SBF file for the ROM on your device (if you don't have it, see if its available from -> http://sbf.droid-developers.org/phone.php?device=0 ), you can unzip it, and fastboot flash the stock recovery from it onto your device, take the OTA, and then later fastboot flash TWRP back on and install SuperSU again to root.
This assumes you did NOT touch any system files the update will check for prior to running/installing. If you did touch system files, edit build prop, removed/renamed any APK's... then fastboot flash recovery and system before taking the OTA
So I am planning on rooting my Verizon Moto Maker locked bootloader Moto X running 4.4 before the 4.4.2 OTA gets pushed and I want to safely stay rooted. Here is what I am planning on doing and please correct me if I am wrong or doing things unnecessarily:
1) Save my custom wallpaper using these instructions:
How to Pull Custom Wallpaper
2) Root using Slap My Moto method
- here it the 4.4 OTA if 4.4.2 has already come out by the time I do this
Verizon 4.4 OTA
3) Make an EFS b/u
4) Install Titanium b/u and make a post-root b/u
5) Use Titanium b/u to freeze MotorolaOTA so that the 4.4.2 OTA won't be pushed to my device
- will freezing MotorolaOTA stop the OTA from being downloaded or will it just stop the notification popup?
6) Uninstall Motorola Device Manager from my PC so that it won't try to upgrade my phone's OS every time I connect my phone to my PC
- is there any way to stop MDM from checking for updates without uninstalling it?
- will I lose the Motorola drivers for my Moto X if I uninstall MDM?
Also when am I supposed to wipe my dalvik cache wrt back ups and rooting? Am I supposed to clear any other cache or data anywhere along the way?
Then after I root, I can selectively flash the 4.4.2 update:
Slap My Moto Page 150
Important Warning Before Flashing 4.4.2 Page 15
System.img, boot.img, non-hlos.bin and fsg.mbn
Cozume said:
So I am planning on rooting my Verizon Moto Maker locked bootloader Moto X running 4.4 before the 4.4.2 OTA gets pushed and I want to safely stay rooted. Here is what I am planning on doing and please correct me if I am wrong or doing things unnecessarily:
1) Flash TWRP and boot into it to make a pre-root nandroid b/u
- I know the custom recovery won't stick when I reboot, just doing it to make a pre-root b/u
- is this necessary as long as the sbf firmware is available?
2) Root using Slap My Moto method
3) Make an EFS b/u
4) Install Titanium b/u and make a post-root b/u
5) Use Titanium b/u to freeze MotorolaOTA so that the OTA won't be pushed to my device
- will freezing MotorolaOTA stop the OTA from being downloaded or will it just stop the notification popup?
6) Uninstall Motorola Device Manager from my PC so that it won't try to upgrade my phone's OS every time I connect my phone to my PC
- is there any way to stop MDM from checking for updates without uninstalling it?
- will I lose the Motorola drivers for my Moto X if I uninstall MDM?
Also when am I supposed to wipe my dalvik cache wrt back ups and rooting? Am I supposed to clear any other cache or data anywhere along the way?
Also, I can't hit the thanks button anymore today but if you help me I will come back tomorrow and hit it, I promise!
Click to expand...
Click to collapse
Flashing twrp while having a locked boot loader? Idk
Sent on my Gummy running Lenoto X
flashallthetime said:
Flashing twrp while having a locked boot loader? Idk
Click to expand...
Click to collapse
Thanks for pointing that out. I read that on a site about backing up that I could do that if I wasn't rooted, but it didn't specify I had to have an unlocked bootloader to do it.
Seriously I am thanking you but I hope you see it from the point of noobs like me, too. I really am reading and trying but that very basic point went over my head. There is so much to try to absorb when you are learning that sometimes the very basic stuff gets missed.
And I am trying to learn both unlocked and locked bootloader methods and not always keeping it straight in my head.
Cozume said:
Thanks for pointing that out. I read that on a site about backing up that I could do that if I wasn't rooted, but it didn't specify I had to have an unlocked bootloader to do it.
Seriously I am thanking you but I hope you see it from the point of noobs like me, too. I really am reading and trying but that very basic point went over my head. There is so much to try to absorb when you are learning that sometimes the very basic stuff gets missed.
And I am trying to learn both unlocked and locked bootloader methods and not always keeping it straight in my head.
Click to expand...
Click to collapse
well good! you're on the right track. 3 best pieces of advice here:
1. Search first
2. Read alot (yes even some long threads with several pages)
3. Then Q & A is here for you.
Glad you're being safe with your exepnsive device, some noobs usually shoot first ask questions later.
Cozume said:
Thanks for pointing that out. I read that on a site about backing up that I could do that if I wasn't rooted, but it didn't specify I had to have an unlocked bootloader to do it.
Seriously I am thanking you but I hope you see it from the point of noobs like me, too. I really am reading and trying but that very basic point went over my head. There is so much to try to absorb when you are learning that sometimes the very basic stuff gets missed.
And I am trying to learn both unlocked and locked bootloader methods and not always keeping it straight in my head.
Click to expand...
Click to collapse
Flashing a custom recovery always requires a unlocked boot loader, On a more serious note, I would wait for the Verizon ota to arrive and see how folks manage to root their phones, if its possible?
Sent on my Gummy running Lenoto X
flashallthetime said:
On a more serious note, I would wait for the Verizon ota to arrive and see how folks manage to root their phones, if its possible?
Click to expand...
Click to collapse
I want to do it now in case the exploit is closed forever in 4.4.2. Then if someone comes up with a new way to root 4.4.2, I can unroot, revert to stock and take the update then, right?
Cozume said:
I want to do it now in case the exploit is closed forever in 4.4.2. Then if someone comes up with a new way to root 4.4.2, I can unroot, revert to stock and take the update then, right?
Click to expand...
Click to collapse
No, wait and see what happens, it makes sense flash 4.4.2 now, it won't make any difference now or later, second point is, you can not flash the 4.4.2 sbf firmware as Verizon's version is not available why?,your boot loader is locked, you not flash any sbf with a locked. boot loader, you can ONLY flash your specific carriers sbf firmware. Read please. I have 6 months of moto x experience behind me, been here from day 1
Sent on my Gummy running Lenoto X
My advice. Root it now, wait it out. If they can't come up with an exploit for 4.4.2, sell your phone, get a developer edition then you can do whatever you want.
MotoX Developer Edition went from German 4.4.2 to Great Britain 4.4.2 to T-Mobile 4.4.2 no problem. Fastboot FTW!
SymbioticGenius said:
My advice. Root it now, wait it out. If they can't come up with an exploit for 4.4.2, sell your phone, get a developer edition then you can do whatever you want.
Click to expand...
Click to collapse
yeah, but it will cause me great sadness to sell my beautiful wood backed baby!!!
flashallthetime said:
it won't make any difference now or later
Click to expand...
Click to collapse
well, yes it would because if I take the OTA then I won't be rooted unless someone finds an exploit for 4.4.2 and I will never be rooted if someone doesn't.
flashallthetime said:
i
, second point is, you can not flash the 4.4.2 sbf firmware as Verizon's version is not available why?,your boot loader is locked, you not flash any sbf with a locked. boot loader, you can ONLY flash your specific carriers sbf firmware.
Click to expand...
Click to collapse
I am getting confused now. If I stay on 4.4 rooted and something happens to my device, can I or can't I flash the sbf for Verizon 4.4 with a locked bootloader to restore my device?
Maybe I wasn't clear but my plan is to root on 4.4 and stay there by freezing MotorolaOTA, which is the app that installs the updates and sends the annoying message. I was going to stay on 4.4 rooted and not upgrade to 4.4.2 unless someone can come up with a way to root it with a locked bootloader.
Cozume said:
yeah, that is my plan. But it will cause me great sadness to sell my beautiful wood backed baby!!!
Click to expand...
Click to collapse
Go for it root it now, I have no idea which sbf firmware you can flash that won't brick your device and I guess we'll see you back with the developer edition. Did you read my previous post? Is Verizon's or at&t 4.4.2 firmware available? Not last time I checked. Locked bootloaders can not flash any sbf firmware only your specific carriers sbf firmware can be flashed
Sent on my Gummy running Lenoto X
flashallthetime said:
Go for it root it now, I have no idea which sbf firmware you can flash that won't brick your device and I guess we'll see you back with the developer edition. Did you read my previous post? Is Verizon's or at&t 4.4.2 firmware available? Not last time I checked. Locked bootloaders can not flash any sbf firmware only your specific carriers sbf firmware can be flashed
Click to expand...
Click to collapse
Did you read my previous post:
My Previous Post
My plan is to NEVER flash 4.4.2 unless someone can root 4.4.2. Then I would unroot and take the OTA, not flash anything. Can't I unroot on 4.4 and take the OTA?
Cozume said:
Did you read my previous post:
My Previous Post
My plan is to NEVER flash 4.4.2 unless someone can root 4.4.2. Then I would unroot and take the OTA, not flash anything. Can't I unroot on 4.4 and take the OTA?
Click to expand...
Click to collapse
No one knows yet for sure what and will not work for the 4.4.2 ota, you'll just have to wait. Probably the only way is keep the 4.4 boot loader while running the 4.4.2 system only but its all speculation until the ota comes out
Sent on my Gummy running Lenoto X
flashallthetime said:
No one knows yet for sure what and will not work for the 4.4.2 ota, you'll just have to wait. Probably the only way is keep the 4.4 boot loader while running the 4.4.2 system only but its all speculation until the ota comes out
Click to expand...
Click to collapse
I am not planning on taking the 4.4.2 OTA. The whole point of freezing MotorolaOTA is to block the OTA.
I have the RW version and unlocked with the China man... My question is once I take the OTA will it relock my bootloader?? And if I relock it can I use the same code to unlock it again? And last can I still use the sbf file on this phone or must I manually flash the partitions? Thanks guys
Sent from my XT1049 using xda app-developers app
No it will not relock it it. Once the flags are triped there is no going back to locked. Just relocked
Sent from my XT1058 using xda app-developers app
I've been wondering this too. The last phone I had (Google Galaxy Nexus) was unlocked and rooted running CM 10.1 and then CM 11 so it never received the OTA's. But mine and my wife's Moto X Developer Editions are both unlocked and rooted but running stock 4.4.2.
As I understand it we'll still receive OTA's correct? Once we do there is a chance they will lock back up and we'll lose root correct? The reason I say chance is because both phones are setup through Titanium to "attempt" to keep root and I know it doesn't always work.
I'm assuming the bootloader gets relocked? If it does how do we go about unlocking and rooting them again? Will the codes we got from Motorola work or do we need to go through the entire process of unlocking then rooting?
Sorry for the newb questions. Like I said, every phone I ever unlocked and rooted I put custom ROMs on them so I never got the OTA's.
Yeah I've read about it going to relock if I do it.. But can a ota update relock it.. And if it did.. Will my code still work.
Sent from my XT1049 using xda app-developers app
Yes, you can flash using either RSDLite or fastboot/mFastboot
If you do relock your bootloader, yes the same code will work to unlock it later.
And... already said here -> http://forum.xda-developers.com/showpost.php?p=51363645&postcount=394
[*]Taking future OTA's will not re-lock your bootloader, however you will need to have stock recovery on your phone, and revert any modified system files, i.e. get back to "stock" or nearly stock, in order to install OTA's, just like those with Developer Edition phones have to do. (this is due to the OTA updates containing a manifest file that lists files and their "check sums" it looks for on your phone before it starts. If they are not on your phone, or the ones on your phone don't match the expected check sum, the OTA install will fail.)
[*]Flashing with RSDLite will not re-lock your bootloader
[*]Only manually re-locking via the relock process (moto has on the Dev Edition web site, it is fastboot oem lock ) will re-lock your bootloader.
Click to expand...
Click to collapse
So, I'd need to reinstall all the bloatware that came on the phone originally? That's pretty much all I took off the phone was all of Verizon's crap that I'll never use nor have any interest in. The only other thing I did was edit the navigation keys out using the build.prop, but that's easy enough to turn back on. My phone as well as my wife's are stock aside from the removal of the bloatware and taking the nav keys out of my phone.
Thanks kid. I've just read mixed messages about bricking my device from ota updates and sbfs. Thanks again.
Sent from my XT1049 using xda app-developers app
The Tallest said:
So, I'd need to reinstall all the bloatware that came on the phone originally? That's pretty much all I took off the phone was all of Verizon's crap that I'll never use nor have any interest in. The only other thing I did was edit the navigation keys out using the build.prop, but that's easy enough to turn back on. My phone as well as my wife's are stock aside from the removal of the bloatware and taking the nav keys out of my phone.
Click to expand...
Click to collapse
When it comes to taking OTA's, yes.
Inside the OTA is a manifest file. It contains a list of files and their check sums it expects to be on your phone. If the files are missing, or the check sum for a particular file doesn't match (because you've replaced or altered the file), the OTA will fall. Because of this, you must be "stock" (or as close to stock as possible). Any bloat you deleted, needs to be put back. Any files you altered (like build.prop) need to be reverted. Any apps you froze with Titanium Backup or the like, may need to be unfrozen.
Apps disabled via the phone's Settings -> Applications -> [select app] -> [disable] can remain disabled and should not impact the update.
---------- Post added at 06:04 AM ---------- Previous post was at 05:58 AM ----------
kicker22004 said:
Thanks kid. I've just read mixed messages about bricking my device from ota updates and sbfs. Thanks again.
Sent from my XT1049 using xda app-developers app
Click to expand...
Click to collapse
Yes, there are some cautions and warnings about bricking... They usually relate to if you've taken 4.4.2 and try to downgrade your rom to 4.4 or lower. Or if you flash only parts of a rom using mFastboot and get into a state when you have "mixed" versions on your phone...
Due to changes in the bootloader included with the 4.4.2 Update, under certain circumstances when trying to downgrade from 4.4.2 to 4.4 or lower, you could either brick your phone, or set it up to brick in the future when you take an upgrade. So it is suggested you just stick with what is on your phone once you get on 4.4.2.
KidJoe said:
When it comes to taking OTA's, yes.
Inside the OTA is a manifest file. It contains a list of files and their check sums it expects to be on your phone. If the files are missing, or the check sum for a particular file doesn't match (because you've replaced or altered the file), the OTA will fall. Because of this, you must be "stock" (or as close to stock as possible). Any bloat you deleted, needs to be put back. Any files you altered (like build.prop) need to be reverted. Any apps you froze with Titanium Backup or the like, may need to be unfrozen.
Apps disabled via the phone's Settings -> Applications -> [select app] -> [disable] can remain disabled and should not impact the update.
---------- Post added at 06:04 AM ---------- Previous post was at 05:58 AM ----------
Click to expand...
Click to collapse
Well damn, I'm kind of screwed then as I deleted all those dumbass Verizon apps that I have no use for and didn't bother making backups of any of them. I'll have to check the "Apps" folder and see if the .apk files are still there so that Google Play can redownload them at some point.
I don't even think the backup I made via TWRP has them. Although I think Motorola's website does have the system image so I can probably just reflash that when the next OTA comes out.
The Tallest said:
Well damn, I'm kind of screwed then as I deleted all those dumbass Verizon apps that I have no use for and didn't bother making backups of any of them. I'll have to check the "Apps" folder and see if the .apk files are still there so that Google Play can redownload them at some point.
I don't even think the backup I made via TWRP has them. Although I think Motorola's website does have the system image so I can probably just reflash that when the next OTA comes out.
Click to expand...
Click to collapse
TWRP.. then you have an unlocked bootloader? If so, you do have the option to flash the SBF to revert to stock, or unzip it and just mfastboot flash system.img onto your phone, because you can always re-root later.
KidJoe said:
TWRP.. then you have an unlocked bootloader? If so, you do have the option to flash the SBF to revert to stock, or unzip it and just mfastboot flash system.img onto your phone, because you can always re-root later.
Click to expand...
Click to collapse
Yes, my boot loader is unlocked. That's good to know that I can do that, thanks.
Wait... Did I miss read that... You can flash sbf in TWRP?? sorry but I've been on Gnex and haven't had a moto since the droid x... Things have changed a bit.
Sent from my XT1049 using xda app-developers app
kicker22004 said:
Wait... Did I miss read that... You can flash sbf in TWRP?? sorry but I've been on Gnex and haven't had a moto since the droid x... Things have changed a bit.
Sent from my XT1049 using xda app-developers app
Click to expand...
Click to collapse
Yes, you miss read.. I was saying that he could just flash the SBF (implying RSDLite) or unzip it and mfastboot flash "part"
because being unlocked he could still root afterwards
OK that's what I thought. Thanks again for the info..looks like I'll sit tight with my unlocked bootloader until RW gets 4.4 update.
Sent from my XT1049 using xda app-developers app
Hello all,
I am on a stock rooted 4.4 rom (verizon). I just used the Sunshine bootloader unlock and I'm curious about the best way to get to 4.4.4.
Should I:
a. Revert back to JB and just take all the OTAs?
b. Or is there a way to just flash 4.4.4 with a custom recovery?
Another question is that once I get to 4.4.4, the unlocked bootloader will still be there and I can put a custom recovery and just flash SuperSU right?
The final question is do I even want to update from 4.4 to 4.4.4, nothing really changed right? Would you do it or just wait for Android L?
Thanks!
streetlightman said:
I am on a stock rooted 4.4 rom (verizon). I just used the Sunshine bootloader unlock and I'm curious about the best way to get to 4.4.4.
Should I:
a. Revert back to JB and just take all the OTAs?
Click to expand...
Click to collapse
No. First I would make a nandroid of your stock rooted 4.4.
Then, if you want to keep your data, flash the 4.4 stock recovery and unroot. You said you are on a stock system, but make sure you disable the Xposed installer (not just install it but disable it) if you installed it and revert any changes to your system that you made including unfreezing any apps before you take any OTAs.
Once you have done all of that, I would just let the OTAs do the rest.
If you don't want to keep your data, you can flash the 4.4.4 sbf using RSDLite.
streetlightman said:
The final question is do I even want to update from 4.4 to 4.4.4, nothing really changed right?
Click to expand...
Click to collapse
A lot changed including the camera improvements.
Wansanta said:
No. First I would make a nandroid of your stock rooted 4.4.
Then, if you want to keep your data, flash the 4.4 stock recovery and unroot. You said you are on a stock system, but make sure you disable the Xposed installer (not just install it but disable it) if you installed it and revert any changes to your system that you made including unfreezing any apps before you take any OTAs.
Once you have done all of that, I would just let the OTAs do the rest.
If you don't want to keep your data, you can flash the 4.4.4 sbf using RSDLite.
A lot changed including the camera improvements.
Click to expand...
Click to collapse
Thanks for the reply. I don't care too much about my data so I wouldn't mind SBfing back to JB. The reason I'd rather do that is because i can't remember what apps I froze (deleted) and I removed the updater APK so it wouldn't annoy me. Would reverting back to JB affect the unlocked bootloader? It shouldn't right?
streetlightman said:
Thanks for the reply. I don't care too much about my data so I wouldn't mind SBfing back to JB. The reason I'd rather do that is because i can't remember what apps I froze (deleted) and I removed the updater APK so it wouldn't annoy me. Would reverting back to JB affect the unlocked bootloader? It shouldn't right?
Click to expand...
Click to collapse
What is the point of downgrading to jelly bean?
If you froze apps, they will show up in titanium backup as frozen. If you deleted system apps, you are not stock. So what you are running is a rooted 4.4 that is not stock b/c you deleted system apps. You can flash 4.4.4 without having to remember the changes you made. Then you can flash TWRP and reroot using SuperSU.
You can't downgrade anyways. Unless you want a paperweight. Not even sbfing will do it. Sorry brother. I'm only telling you this for your own good. Please listen.
Download the 4.4.4 sbf, unzip it, flash the contents in bootloader. You can find a guide in the General subforum.
ryanzurlo88 said:
You can't downgrade anyways. Unless you want a paperweight. Not even sbfing will do it. Sorry brother. I'm only telling you this for your own good. Please listen.
Click to expand...
Click to collapse
Depends on what you are trying to downgrade.
Wansanta said:
Depends on what you are trying to downgrade.
Click to expand...
Click to collapse
So your saying... That I have a vzw Dev ed moto x. 4.4.4. I can take it and downgrade it to 4.4.2 and then flash the gsm 4.4.2? I just use it on WiFi only anyways. Cause I'm trying to get the stock moto x firmware with no carrier bloatware. Right now the vzw has 9 bloatware apps. I have the att 4.4.4 ROM right now with only 4 bloatware apps. I want no bloatware WITHOUT using tb and others
ryanzurlo88 said:
So your saying... That I have a vzw Dev ed moto x. 4.4.4. I can take it and downgrade it to 4.4.2
Click to expand...
Click to collapse
Yes, you can downgrade to the 4.4.2 system. If you try to flash the 4.4.2 bootloader or partition table, it will fail. But you can downgrade to the 4.4.2 system. Once upgraded the bootloader and partition table are not downgradeable but if you try to flash them you will get a failure, not a brick. As long as you have an unlocked bootloader and can get to bootloader mode, you don't have a brick.
ryanzurlo88 said:
and then flash the gsm 4.4.2?
Click to expand...
Click to collapse
I don't know anything about trying to flash the XT1053 system to a XT1060 device.
ryanzurlo88 said:
Cause I'm trying to get the stock moto x firmware with no carrier bloatware. Right now the vzw has 9 bloatware apps.
Click to expand...
Click to collapse
I just remove those via Titanium Backup. Which ones do you want removed and I can tell you if I have removed them and what happened when I did.
You only need the TiBU PRO key if you are freezing apps, not removing apps.
Well like I said I have att moto x rom on a vzw moto x. I just want the straight plain ROM with no tinkering
ryanzurlo88 said:
Well like I said I have att moto x rom on a vzw moto x. I just want the straight plain ROM with no tinkering
Click to expand...
Click to collapse
The att system has carrier bloat, too. Do you mean the XT1053 - Tmobile/unlocked GSM system?
Yeah. I'm waiting on an sbf/fxz for it. Unless you've found it?
ryanzurlo88 said:
Yeah. I'm waiting on an sbf/fxz for it. Unless you've found it?
Click to expand...
Click to collapse
The latest official sbf for the XT1053 is 4.4.3 unless someone made an unofficial fxz for it.
http://sbf.droid-developers.org/phone.php?device=0
ryanzurlo88 said:
Yeah. I'm waiting on an sbf/fxz for it. Unless you've found it?
Click to expand...
Click to collapse
A lot of talk lately about downgrading being ok on 4.4.2 or higher.....and well there can be a very particular way to do it, without downgrading the bootloader....there are many ways to make a mistake and end up with a brick. This warning seems to be missing from some of the downgrade talk I've been seeing around.
The veterans of this device and XDA will always flat out say no....You can't downgrade. Why? Because if we try to guide anyone through downgrading, or advise them they can.....mistakes happen, and we don't want to be partially responsible for anyone destroying their device.
So, best (aka safest) advice, is to wait for the files you need. Then flash them fairly risk free.
Or try to downgrade.....but know the risks. ?
---------- Post added at 11:18 AM ---------- Previous post was at 11:16 AM ----------
If anyone disagrees.....ask these people how downgrading went for them...
https://www.google.ca/search?redir_...ed+xda+site:forum.xda-developers.com&hl=en-US
?