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
Related
It looks like the guys over at Droid-Developers have uploaded the most recent Firmware
http://sbf.droid-developers.org/ghost_rcica/list.php
With the FXZ firmware out for post OTA updates, does this mean we can follow the protocol to install pwnmymoto but not run it, take OTA, run it, then still be able to RSD back to stock?
anotherfiz said:
It looks like the guys over at Droid-Developers have uploaded the most recent Firmware
http://sbf.droid-developers.org/ghost_rcica/list.php
With the FXZ firmware out for post OTA updates, does this mean we can follow the protocol to install pwnmymoto but not run it, take OTA, run it, then still be able to RSD back to stock?
Click to expand...
Click to collapse
Return to stock OTA I believe, but not downgrade.
And lose root in the process
Sent from my XT1060 using Tapatalk
monkespit said:
And lose root in the process
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Gotcha, that makes sense, because you couldnt even install pwnmymoto on the new firmware from stock.
it seems like the best option is to run the safestrap for the time being
anotherfiz said:
Gotcha, that makes sense, because you couldnt even install pwnmymoto on the new firmware from stock.
it seems like the best option is to run the safestrap for the time being
Click to expand...
Click to collapse
or follow the thread for taking the ota and keeping root. Both let you downgrade back to original stock FW because neither touch your BL. I run SS but the other method works just fine as well now. I also flashed the new baseband in SS for call quality. Running smoothly.
jayboyyyy said:
or follow the thread for taking the ota and keeping root. Both let you downgrade back to original stock FW because neither touch your BL. I run SS but the other method works just fine as well now. I also flashed the new baseband in SS for call quality. Running smoothly.
Click to expand...
Click to collapse
You cannot downgrade. Not sure what you're talking about. If you still think you can, list the steps here. I'll do it now.
Keeping root through an OTA and downgrading to earlier firmware are two completely different things. Why don't you clarify.
Sent from my XT1060 using Tapatalk
jayboyyyy said:
or follow the thread for "taking the ota and keeping root." Both let you downgrade back to original stock FW because neither touch your BL. I run SS but the other method works just fine as well now. I also flashed the new baseband in SS for call quality. Running smoothly.
Click to expand...
Click to collapse
1ManWolfePack said:
You cannot downgrade. Not sure what you're talking about. If you still think you can, list the steps here. I'll do it now.
Keeping root through an OTA and downgrading to earlier firmware are two completely different things. Why don't you clarify.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
you mis-read what i was saying. perhaps adding quotations to my earlier post will make more since.
just for further clarification in case you aren't understanding what I meant still.
3 methods to keep root through OTA:
(1) SS
(2) method found under the thread titled something like "keeping root through the OTA"
(3) install pwmymoto without running, take ota, pwnmymoto automatically applies root after taking OTA
methods 1 & 2 allow you to "downgrade" or rather flash the original stock firmware onto the phone because neither methods touch the BL
method 3 does not allow you to do this as the BL has been touched and security parameters set to not allow you to go back to original stock firmware.
1ManWolfePack said:
You cannot downgrade. Not sure what you're talking about. If you still think you can, list the steps here. I'll do it now.
Keeping root through an OTA and downgrading to earlier firmware are two completely different things. Why don't you clarify.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
read the "tutorial for keeping root..." thread also in this section. i think it's believed that pwnmymoto changed something so that when the ota is taken the BL doesn't update, and u can flash the older fxz again to return to that firmware and essentially downgrade. at least from what I've read. not a whole lot of confirmation on it last I checked.
"Keeping root" and "downgrading" again - two vastly different scenarios. Once you take the update, there in no way to downgrade to previous firmware. Go ahead and ask jcase.
Further citation isn't needed, as I read exactly what you wrote.
Sent from my XT1060 using Tapatalk
1ManWolfePack said:
"Keeping root" and "downgrading" again - two vastly different scenarios. Once you take the update, there in no way to downgrade to previous firmware. Go ahead and ask jcase.
Further citation isn't needed, as I read exactly what you wrote.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
A few people are saying here that we can downgrade since the boot loader was not updated using the tutorial given in this same forum....Someone tried "downgrading" to stock firmware as well and it has worked...the key is bootloader prevents the downgrade and it was not touched using the said method...
Sent from my XT1060 using Tapatalk
---------- Post added at 09:49 PM ---------- Previous post was at 09:46 PM ----------
Here is the post I am talking about.... http://forum.xda-developers.com/showthread.php?p=46839681
Sent from my XT1060 using Tapatalk
Let me explain:
If you installed pwnmymoto and did not run it, while stock, then took the update - then maybe you can flash back. Couple guys above claim they did it, who am I to think they're lying. That's not what I'm saying though.
If you didn't install pwnmymoto before updating then no chance. So it depends on how you took the update. If never rooted and took it - nope. Can't downgrade. If you RSD' back to stock unrooted, installed pwnmymoto but didn't run it - you're good taking the update.
I think that's where the confusion lies. I've tried a few ways to downgrade and no dice. Took the gbt.bin from the new update, put it in the old, opened the .XML to change the MD5 (pretty sure I didn't put correct one) repackaged and tried to flash. Failed at gbt.bin. I'm just playing around and seeing if I can get back somehow. I restore web hosting all day and have bricked multiple times on phones. Lol. So I'm not really scared. But even if I did get it to flash back, I'm pretty sure the exploit is patched in the file I'm replacing.
/hugeblockoftext
Sent from my XT1060 using Tapatalk
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.
I am on a Verizon moto x developer edition with an unlocked boot loader, custom recovery installed and I am rooted. I got the notification for the ota update. What if anything will this break?
Sent from my XT1060 using XDA Premium 4 mobile app
First, you need to be on stock recovery for the OTA to attempt to install. Next you need to make sure all your system files and such are present and back to "stock" (i.e. if you did the tethering hacks, renamed or replaced system files, etc, you need to undo that), and you need to un-install Xposed or the OTA will fail when it tries to install.
Since you are Dev with unlocked bootloader, it wont "break" anything, but the new bootloader installed via the OTA prevents downgrading your rom. So if you find an issue with 4.4.2, you're stuck with it, you can't flash back to 4.4. If you loose root, you can still flash custom recovery and install SuperSU to root.
Those with locked bootloader might keep root, but Write Protection gets Enabled again. With an unlocked boot loader, you don't have to worry about this.
Also, if you really want 4.4.2, there is a zip in the android development section with an unofficial sbf. Be very careful with what files you flash, i flashed the zip in RSD lite blindly (my mistake) and spend four hours trying to figure out why i didn't have data or any mobile connection.
-edit-
Also, don't take my word for it but i think you'll still be alright if you don't flash gpt.bin and the bootloader and you should still be able to downgrade.
Ok. Thanks for the info guys. I might just wait until someone puts out the deoxidized 4.4.2 rom. I would flash slim or cm11 but I really like the active display and the touch less controls.
Sent from my XT1060 using XDA Premium 4 mobile app
robwege said:
Ok. Thanks for the info guys. I might just wait until someone puts out the deoxidized 4.4.2 rom. I would flash slim or cm11 but I really like the active display and the touch less controls.
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
For what its worth, I've been running this 4.4.2 rom (the odexed version, deodexed also available) created from a XT1052 image on my VZW/DE XT1060:
http://forum.xda-developers.com/moto-x/development/rom-moto-x-xt1052-t2639724
I did swap out the original build.prop with the Verizon-ized build.prop someone was kind enough to post on page 2 or 3 of that thread. It has been working great for me for the last week! Tethering even works on VZW w/o any extra steps.
robwege said:
I am on a Verizon moto x developer edition with an unlocked boot loader, custom recovery installed and I am rooted. I got the notification for the ota update. What if anything will this break?
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If that's all you've done (haven't modified/deleted/renamed any system files/apps or installed Xposed, etc..) then it's really easy.
Flash the stock recovery back to your phone
install the update
Flash TWRP back to your phone (or not....)
Done.
You won't lose root taking the OTA and flashing recovery back doesn't affect your user data or app installs/configurations.
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
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
?