I just got the 4.4.2 update from claro in chile. But I have not installed it yet. My phone is on 4.2.2 at the moment. The bootloader is unlocked. It is rooted using rockmymoto. What I want to know is what do I need to do to get it ready for the 4.4.2 upgrade? I assume I need to unroot it? Also I have lucky patcher installed and I odexed my system, will this be a problem? Will I be able to get root in 4.4.2?
AGISCI said:
I just got the 4.4.2 update from claro in chile. But I have not installed it yet. My phone is on 4.2.2 at the moment. The bootloader is unlocked. It is rooted using rockmymoto. What I want to know is what do I need to do to get it ready for the 4.4.2 upgrade? I assume I need to unroot it? Also I have lucky patcher installed and I odexed my system, will this be a problem? Will I be able to get root in 4.4.2?
Click to expand...
Click to collapse
There are threads on this in the general folder as well as this folder.
What I don't understand is why you had to root using rockmymoto if your bootloader is unlocked? Why didn't you just flash a custom recovery like TWRP and install SuperSU to root?
Do you have the 4.2.2 post camera update installed?
Cozume said:
There are threads on this in the general folder as well as this folder.
Click to expand...
Click to collapse
I have read various topics in both of the forums on it. But I wanted to be 100% sure of what path I need to follow to be sure I don't brick my phone. 1 thing that had me worried is that I odexed my system with lucky patcher... does this mean I am going to have to flash my firmware back to stock before I can do this?
Cozume said:
What I don't understand is why you had to root using rockmymoto if your bootloader is unlocked? Why didn't you just flash a custom recovery like TWRP and install SuperSU to root?
Click to expand...
Click to collapse
Because I rooted it a month before I unlocked the bootloader.
I still currently have stock recovery though.
Cozume said:
Do you have the 4.2.2 post camera update installed?
Click to expand...
Click to collapse
As far as the post camera update, not sure. My camera version is 3.1.41.2.
AGISCI said:
I have read various topics in both of the forums on it. But I wanted to be 100% sure of what path I need to follow to be sure I don't brick my phone. 1 thing that had me worried is that I odexed my system with lucky patcher... does this mean I am going to have to flash my firmware back to stock before I can do this?
Click to expand...
Click to collapse
That is certainly the safest way to go from all I have read as any system mods could potentially cause a problem. The problem that another poster here had is that the only firmware that is posted for the Claro Chile is the precamera update. He was looking for the postcamera firmware.
http://forum.xda-developers.com/showthread.php?t=2649806
And no one could help him find it. I don't think you can take the OTA if you are on the precamera firmware. Perhaps you can PM the OP in that link and see if he is knowledgeable about Claro chile firmware.
Cozume said:
That is certainly the safest way to go from all I have read as any system mods could potentially cause a problem. The problem that another poster here had is that the only firmware that is posted for the Claro Chile is the precamera update. He was looking for the postcamera firmware.
http://forum.xda-developers.com/showthread.php?t=2649806
And no one could help him find it. I don't think you can take the OTA if you are on the precamera firmware. Perhaps you can PM the OP in that link and see if he is knowledgeable about Claro chile firmware.
Click to expand...
Click to collapse
How can I tell if I am on the pre cam or post cam? Also is there a link that talks about what teh pre cam and post cam does or changed?
AGISCI said:
How can I tell if I am on the pre cam or post cam? Also is there a link that talks about what teh pre cam and post cam does or changed?
Click to expand...
Click to collapse
Go to Settings->About Phone->System Version. What does it say?
139.12.35.ghost_row.AmericaMovil.en.CL
Sent from my Nexus 7 using Tapatalk
AGISCI said:
139.12.35.ghost_row.AmericaMovil.en.CL
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
From the version numbers here:
http://sbf.droid-developers.org/phone.php?device=0
As best I can tell 139.12.35 is the post camera update. The problem is that no one has a copy of the stock firmware posted anywhere that anyone can find.
If that's the case flashing this firmware will not brick me then correct?
Sent from my Nexus 7 using Tapatalk
You say you rooted the phone a month before you unlocked the bootloader. If this is the case then your phone should have been wiped clean as unlocking the bootloader performs a full wipe of the phone.
So something does not add up/make sense.
Steve-x said:
You say you rooted the phone a month before you unlocked the bootloader. If this is the case then your phone should have been wiped clean as unlocking the bootloader performs a full wipe of the phone.
So something does not add up/make sense.
Click to expand...
Click to collapse
I rooted it twice actually. After I unlocked the bootloader it was erased just like you said, and I rooted again using the same method from the first time.
AGISCI said:
If that's the case flashing this firmware will not brick me then correct?
Click to expand...
Click to collapse
Which firmware?
This is from dray_jr on the thread in the Moto X General forum:
the only OTA that can downgrade is 4.4 to 4.2.2 Post Cam
here is what we know right now that might make more sense
4.4 to 4.2.2 Pre Cam will Brick
4.2.2 Post Cam to 4.2.2 Pre Cam will Brick.
4.4.2 to anything will Brick
4.4 to 4.2.2 Post Cam you are ok
http://forum.xda-developers.com/showthread.php?t=2635366&highlight=brick&page=5
You are in quite a unique situation here actually... since there is no stock image that you can go back to. If there was a 4.4 SBF I would have suggested to flash then take the 4.4.2 update. However, it seems as if there was no 4.4 roll out/update for your carrier at all. So this 4.4.2 carrier update would be more than a simple patch from 4.4 to 4.4.2, it would probably end up removing root since you are going from JB to KK.
Your best bet if you want it now is to do the following...
I AM NOT RESPONSIBLE FOR YOUR ACTIONS OR BRICKING YOUR DEVICE
1) Did you make a backup before you messed with anything in the system? If you didn't, then you have to go through the manual process of making sure that it is as clean as a normal stock image.
2) Do you have the original recovery? If not, find a recovery file for your carrier and flash that.
3) Attempt to flash the OTA in the standard recovery.
But honestly, the safest thing to do is to wait until your 4.4.2 SBF is released, that way you can flash it in RSD Lite, preventing a brick as much as possible.
mastarifla said:
But honestly, the safest thing to do is to wait until your 4.4.2 SBF is released, that way you can flash it in RSD Lite, preventing a brick as much as possible.
Click to expand...
Click to collapse
Who releases the sbf? Motorola? Because it looks like the problem is that no one can find the sbf for the 4.2.2 postcamera update for their carrier.
I guess I will have to wait then. I can't afford to brick my phone. I captured the update and pulled it with adb so if anyone needs it I will be able to upload it.
Sent from my Nexus 7 using Tapatalk
Cozume said:
Who releases the sbf? Motorola? Because it looks like the problem is that no one can find the sbf for the 4.2.2 postcamera update for their carrier.
Click to expand...
Click to collapse
Skrilax_CZ maintains the website where the SBF's are stored. Motorola only releases the Developer Edition images to the public, as far as I know. So I believe that this website hosts either his own custom made zips, or he has someone supplying him with insider Moto images (or he works there?).
Personally I think he has a tool to automate this process once he has the firmware loaded onto the phone (if he doesn't have the images already), basically he is adb copying files from the dev partition of his phone and compiling a MD5 hash for each file, then zipping it all up in a nice package to flash with the insider Moto tool RSD Lite (or using manual flash, if you like to live dangerously )
mastarifla said:
Skrilax_CZ maintains the website where the SBF's are stored, as far as I know, Motorola only releases the Dev edition images to the public. So I believe that this website hosts either his own custom made zips, or he has someone supplying him with insider Moto images (or he works there?).
Personally I think he a tool to automate this process once he has the firmware loaded onto the phone (if he doesn't have the images already), basically he is adb copying files from the dev partition of his phone and compiling a MD5 hash for each file, then zipping it all up in a nice package to flash with the insider Moto tool RSD Lite.
Click to expand...
Click to collapse
Thanks! So if you know someone with a stock phone who has never modded or rooted, theoretically you could pull the files from the dev partition of their phone? The trick is getting it into a package that works with RSD Lite?
---------- Post added at 08:56 PM ---------- Previous post was at 08:55 PM ----------
mastarifla said:
Motorola only releases the Developer Edition images to the public, as far as I know.
Click to expand...
Click to collapse
So those of us with Dev Eds should stick to flashing the factory images we get from Motorola directly?
Cozume said:
Thanks! So if you know someone with a stock phone who has never modded or rooted, theoretically you could pull the files from the dev partition of their phone? The trick is getting it into a package that works with RSD Lite?
---------- Post added at 08:56 PM ---------- Previous post was at 08:55 PM ----------
So those of us with Dev Eds should stick to flashing the factory images we get from Motorola directly?
Click to expand...
Click to collapse
Theoretically yes, but in practice it is much harder. Every manufacturer stores their particular data in different partitions on the phone. You have to manually look through the bin files (with a hex editor) in order to determine which are the correct ones. This is even more difficult because most of the information is encrypted. So unless you have insider knowledge or want to compare values in a hex editor, I would strongly suggest you stay away from attempting to make your own files, it can lead to very easy bricks.
I have a XT1053 Unlocked GSM phone (T-Mobile), and the SBF T-Mobile firmwares are the only thing I am going to be flashing, don't flash other regions firmware unless you are certain that it works. IE. let everyone else try it and potentially brick their phone before you end up doing the same thing.
Oh and before I forget, hitting the thanks button works too by the way
mastarifla said:
Theoretically yes, but in practice it is much harder. Every manufacturer stores their particular data in different partitions on the phone. You have to manually look through the bin files (with a hex editor) in order to determine which are the correct ones. This is even more difficult because most of the information is encrypted. So unless you have insider knowledge or want to compare values in a hex editor, I would strongly suggest you stay away from attempting to make your own files, it can lead to very easy bricks.
Click to expand...
Click to collapse
no, I would never try it; I am just trying to understand what the differences are between the various ways for me to brick my device, lol!
mastarifla said:
I have a XT1053 Unlocked GSM phone (T-Mobile), and the SBF T-Mobile firmwares are the only thing I am going to be flashing, don't flash other regions firmware unless you are certain that it works. IE. let everyone else try it and potentially brick their phone before you end up doing the same thing.
Click to expand...
Click to collapse
but if I have a Dev Ed, shouldn't I be flashing the factory images I received from Motorola?
mastarifla said:
Oh and before I forget, hitting the thanks button works too by the way
Click to expand...
Click to collapse
I know I tried but they limit you to 8 thanks a day and I already used mine up for today! I will come back tomorrow and hit the button, promise. I am very good about that. So good that I use up all my thanks quickly. So odd they do that here, but they do.
Cozume said:
but if I have a Dev Ed, shouldn't I be flashing the factory images I received from Motorola?
Click to expand...
Click to collapse
Yes you should, however it is widely known that the T-Mobile version and the Developer Edition have the exact same hardware/firmware (XT1053), actually I think they may have the exact same software build as well, though I am not sure on that one... if they receive the same OTA update that the T-Mobile version receives, that leads me to believe its the same ROM.
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.
Please help! Need .sbf or system img & recovery img of Sprint 4.4.4!
Thank you!
Please post questions in the Q&A section
Thread moved
Sprint 4.4.4 sbf hasn't been released yet I'm afraid.
KJ said:
Sprint 4.4.4 sbf hasn't been released yet I'm afraid.
Click to expand...
Click to collapse
When do you think we can expect the sbf to be out? The update was out a long time back. Is the sbf uploded by developers or by Motorola itself?
abhishekpujar said:
When do you think we can expect the sbf to be out? The update was out a long time back. Is the sbf uploded by developers or by Motorola itself?
Click to expand...
Click to collapse
While the SBF's for the Developer Editions are released by Moto, the other SBF's are not. Instead, they are "leaked" to the internet. Therefore we really don't know. Its whenever the person leaking the file gets their hands on it, and it makes its way to the net.
Many don't realize that http://sbf.droid-developers.org/ is neither owned, nor operated, nor sponsored by Moto.
If you have an unlocked bootloader, you can go here http://forum.xda-developers.com/moto-x/development/roms-stock-roms-t2499594 and flash the 4.4.2 ROM link, which is a flashable zip for twrp. Once you wipe and flash that you can accept the 4.4.4 ota, which should fix your problem. If you're locked, you just need to wait to get the sbf.
mxc42 said:
If you have an unlocked bootloader, you can go here http://forum.xda-developers.com/moto-x/development/roms-stock-roms-t2499594 and flash the 4.4.2 ROM link, which is a flashable zip for twrp. Once you wipe and flash that you can accept the 4.4.4 ota, which should fix your problem. If you're locked, you just need to wait to get the sbf.
Click to expand...
Click to collapse
I hope you realize if he was already on a 4.4.4 firmware from any carrier and does what you've told him to do.... Boom... Instant brick.
Please be careful about what advice you give, especially with the easily brickable moto x. I'm sure you don't want to cause anyone to brick. That would be a real drag. ?
KJ said:
I hope you realize if he was already on a 4.4.4 firmware from any carrier and does what you've told him to do.... Boom... Instant brick.
Please be careful about what advice you give, especially with the easily brickable moto x. I'm sure you don't want to cause anyone to brick. That would be a real drag. ?
Click to expand...
Click to collapse
If you read through the linked post you would find out that the 4.4.2 zip I told him to flash to doesn't include the bootloader and can be safely flashed from 4.4.2. I've done it successfully and it saved me from waiting for the sbf.
@MystaWright please don't flash 4.4.2 if you were on a higher version already. If you do, you will likely destroy your device, or at least have some serious issues. ?
mxc42 said:
If you read through the linked post you would find out that the 4.4.2 zip I told him to flash to doesn't include the bootloader and can be safely flashed from 4.4.2. I've done it successfully and it saved me from waiting for the sbf.
Click to expand...
Click to collapse
I actually flashed the twrp recovery and downloaded the 4.4.4 sprint Rom in the development section and flashed that and I'm up and running now. Thanks for the concern and advice.
Already softbricked. Would flash the 4.4.4 rom (zip) from the link if I had a way to get the file on the device.
mxc42 said:
If you read through the linked post you would find out that the 4.4.2 zip I told him to flash to doesn't include the bootloader and can be safely flashed from 4.4.2. I've done it successfully and it saved me from waiting for the sbf.
Click to expand...
Click to collapse
Right, but the bootloader and gpt.bin would then be mismatched and when in that state, taking OTA has bricked the phone more often than not.
So its VERY RISKY suggesting that.
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
?
I have new Verizon Moto X Dev Edition. Messed up. Thought it was already on 4.4.2. Not, it's on 4.2.2. Unlocked bootloader and installed twrp and rooted. Wanting to update it to 4.4.2. Thinking from reading that I need to get back to stock recovery for OTA update if that is possible over wifi since phone is not activated yet. Can't find 4.2.2 stock recovery and not sure if that is what I need to do anyway. Is that what I need to do and/or is there a better way? Thanks
dukeoid said:
I have new Verizon Moto X Dev Edition. Messed up. Thought it was already on 4.4.2. Not, it's on 4.2.2. Unlocked bootloader and installed twrp and rooted. Wanting to update it to 4.4.2. Thinking from reading that I need to get back to stock recovery for OTA update if that is possible over wifi since phone is not activated yet. Can't find 4.2.2 stock recovery and not sure if that is what I need to do anyway. Is that what I need to do and/or is there a better way? Thanks
Click to expand...
Click to collapse
Well I too have a Dev Edition but is SIM-Unlocked so it isn't Verizon.
If all you want to do is update, you could install Custom ROM although you will lose Motorola's Active Display, Always Listening etc...
If you want complete stock and have to reflash TWRP and root your phone, you will need to flash the stock firmware using fastboot or a utility.
Finally found 4.2.2 . When trying RSD fail at gpt bin, also fails there with manual flashing. Any ideas?
Edit...Finally got it. Different version of 4.2.2 did it.
Alecegonce101 said:
Well I too have a Dev Edition but is SIM-Unlocked so it isn't Verizon.
Click to expand...
Click to collapse
Um, all VZW Moto Xs are SIM-unlocked.
dukeoid said:
Finally found 4.2.2 . When trying RSD fail at gpt bin, also fails there with manual flashing. Any ideas?
Edit...Finally got it. Different version of 4.2.2 did it.
Click to expand...
Click to collapse
I hope it wasn't the pre-camera 4.2.2....or you might be in a tough spot now.... Risking a brick. ?
---------- Post added at 10:09 AM ---------- Previous post was at 10:08 AM ----------
Unless the first firmware was also pre camera... Then you're OK.
dukeoid said:
I have new Verizon Moto X Dev Edition. Messed up. Thought it was already on 4.4.2. Not, it's on 4.2.2. Unlocked bootloader and installed twrp and rooted. Wanting to update it to 4.4.2. Thinking from reading that I need to get back to stock recovery for OTA update if that is possible over wifi since phone is not activated yet. Can't find 4.2.2 stock recovery and not sure if that is what I need to do anyway. Is that what I need to do and/or is there a better way? Thanks
Click to expand...
Click to collapse
dukeoid said:
Finally found 4.2.2 . When trying RSD fail at gpt bin, also fails there with manual flashing. Any ideas?
Edit...Finally got it. Different version of 4.2.2 did it.
Click to expand...
Click to collapse
Taking OTA's is incremental, so if you are the initial shipping 4.2.2 you need to take the first 4.2.2 w/camera OTA, then the 4.4 OTA, then the 4.4.2 OTA... a real time waster and pain in the rear.
Best way... Grab the SBF for the version you want to be on, and flash it... i.e. you mention going to 4.4.2, so... grab the 4.4.2 SBF and flash it.
Since you have a Dev Edition, why not just go to 4.4.4? it has a few bug fixes, and is stable. For me and many others its no worse than 4.4.2 as far as performance and battery.
Once you arrive on the ROM you want, you can flash TWRP and root.
KidJoe said:
Best way... Grab the SBF for the version you want to be on, and flash it... i.e. you mention going to 4.4.2, so... grab the 4.4.2 SBF and flash it.
t.
Click to expand...
Click to collapse
OTA'ed to 4.4.2. But for future reference you can skip versions and SBF to the one you want??
dukeoid said:
OTA'ed to 4.4.2. But for future reference you can skip versions and SBF to the one you want??
Click to expand...
Click to collapse
Yup! ?
As long as it's not a lower version.
dukeoid said:
OTA'ed to 4.4.2. But for future reference you can skip versions and SBF to the one you want??
Click to expand...
Click to collapse
OTA = Incremental. Only patches the changed/updated parts.
SBF/FXZ = "all inclusive" or "image files".. and overwrites entire partitions/parts.
So yes. You can just flash the newer SBF file. (As @Darth said... as long as the SBF you are flashing is NEWER than the version on your phone... i.e. NEVER DOWNGRADE)