So I'll be getting a Verizon Moto X soon and I plan to root via SlapMyMoto. My question is this: If my device ever needs to be serviced for warranty or resold at a later date, will I be able to unroot with ease back to 100% stock 4.4 without a trace of the rooting? The process is so convoluted that I worry it breaks certain things and I won't be able to switch back to pure stock. Has anyone tried this?
"100% stock without a trace of rooting"... No. You can easily flash back to the stock 4.2.2 image, But the system write protect that "WpNoMo" disables, does not revert back (meaning, the system wp will remain disabled). So, it will be nearly indistinguishable from stock, but a trained expert could easily detect it (a single command sent over adb will tell you wp is off).
Sent from Nexus 7
I was wondering the same thing. I rooted my 32g VZW Moto with Slap 1.0, but just received my Dev Edition from the $100 off sale. My plan is to return the original back to stock and sell. Will the stock recovery return when flashing back to 4.2.2? I wanna make sure the buyer can upgrade OTA and whatever like stock.
trrubicon06 said:
I was wondering the same thing. I rooted my 32g VZW Moto with Slap 1.0, but just received my Dev Edition from the $100 off sale. My plan is to return the original back to stock and sell. Will the stock recovery return when flashing back to 4.2.2? I wanna make sure the buyer can upgrade OTA and whatever like stock.
Click to expand...
Click to collapse
This. For all practical purposes, will the phone pass a warranty test and be resellable to act like a normal phone with OTA updates and the like?
trrubicon06 said:
Will the stock recovery return when flashing back to 4.2.2? I wanna make sure the buyer can upgrade OTA and whatever like stock.
Click to expand...
Click to collapse
Yes it will. Like stock depends on whether or not you disabled write protection completely.
gerodive said:
This. For all practical purposes, will the phone pass a warranty test and be resellable to act like a normal phone with OTA updates and the like?
Click to expand...
Click to collapse
I believe the answer is yes because the 4.4 OTA tripped the counter.
nhizzat said:
Yes it will. Like stock depends on whether or not you disabled write protection completely.
I believe the answer is yes because the 4.4 OTA tripped the counter.
Click to expand...
Click to collapse
What does that mean? Apologies for my relative ignorance in this field.
gerodive said:
What does that mean? Apologies for my relative ignorance in this field.
Click to expand...
Click to collapse
From what I've read, the 4.4 OTA trips the flash counter within the bootloader as if you had flashed something yourself manually. What I gathered from that is there's no way to distinguish a previously rooted Moto X from a completely stock Moto X with the 4.4 OTA.
That's good to hear. So I'll be able to root 4.4, unroot, and get whatever the newest OTA is (probably 4.4.2) without any issue?
gerodive said:
That's good to hear. So I'll be able to root 4.4, unroot, and get whatever the newest OTA is (probably 4.4.2) without any issue?
Click to expand...
Click to collapse
when ever you want to go back to stock you just need to download the stock firmware and flash it via RSD Lite or Fastboot and then take the OTA
Related
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 just got notified of the of a update to 4.4.2 for my Sprint Moto X. Is there any reason not to accept it? What are the benefits?
Thanks.
Puzzlegal said:
I just got notified of the of a update to 4.4.2 for my Sprint Moto X. Is there any reason not to accept it? What are the benefits?
Thanks.
Click to expand...
Click to collapse
Note: i have a vzw DE. If i recall correctly Sprints Bootloaders can be unlocked, have you done this?
Benefits include mostly under the hood stuff, supposedly fixed some battery drain issues that were in 4.4. I took it on my DE and am happy with it.
Keep in mind:
1. It is impossible to downgrade the bootloader after the 4.4.2 OTA, thus making it difficult to return to a full stock 4.4.
(you can downgrade flash the system from 4.4, but if you are on system 4.4 and bootloader 4.4.2 any future OTA will fail unless you first flash back to system 4.4.2)
2. If your bootloader is locked and you have rooted with the exploit provided by Jcase (slapMyMoto + MotoWPNoMo) the 4.4.2 ota will re-enable WriteProtect, meaning you cannot change the system files. This makes much of Root access pointless, though users report that Xposed modules will survive a "soft-reboot". If your Bootloader is unlocked, you may disregard this. Unlocked BL devices can be rooted at any time with a custom recovery, and unlocking the Bootloader will disable WriteProtection.
Before taking the OTA be sure to undo any changes to system (tether hacks, systemUI changes, disable xposed) or even flash the stock 4.4 system before taking the OTA to be safe (flashing system only will not erase your data or apps, though if you want to be 100% sure, just SBF back to stock 4.4 first).
Thanks.
I have not unlocked my boot loader. Sprint gadgets can be unlocked, but it voids the warranty. I may do that after the warranty expires, but don't plan to do so until then. So I haven't rooted, either. I assume that I can still do both, at the expense of listing the warranty, after updating.
Sounds like I'd probably get more benefit than not from upgrading.
Broke phone sending it back to moto.. Trying to install the update but it fails .. Thinking because of root so going to try the factory reset and see if that will unroot and let 4.4.2 install
doitinthedirt said:
Broke phone sending it back to moto.. Trying to install the update but it fails .. Thinking because of root so going to try the factory reset and see if that will unroot and let 4.4.2 install
Click to expand...
Click to collapse
If you used SlapMyMoto you should already know that it is not compatible with 4.4.2 - did you even read the relevant threads? Most likely you have modified something in /system OR you have custom recovery installed. Both of these issues are well documented here and will prevent you from accepting ANY OTA update.
A factory reset probably won't help, but if you follow the instructions in the "Return to Stock" thread (and flash the ENTIRE stock SBF for YOUR carrier) it will probably fix you right up.
It is irresponsible to flash things without knowing the consequences and then 'send it back to moto'. This results in higher prices for all of us, and encourages the OEMs to lock the devices down TIGHT.
samwathegreat said:
If you used SlapMyMoto you should already know that it is not compatible with 4.4.2 - did you even read the relevant threads? Most likely you have modified something in /system OR you have custom recovery installed. Both of these issues are well documented here and will prevent you from accepting ANY OTA update.
A factory reset probably won't help, but if you follow the instructions in the "Return to Stock" thread (and flash the ENTIRE stock SBF for YOUR carrier) it will probably fix you right up.
It is irresponsible to flash things without knowing the consequences and then 'send it back to moto'. This results in higher prices for all of us, and encourages the OEMs to lock the devices down TIGHT.
Click to expand...
Click to collapse
Thanks for the info.. but give the ben of doubt. the phone was dropped by my brother and the glass is broke. the phone works fine. and is currently working perfect on 4.4 rooted with slapmymoto and wipemymoto
I have the replacement phone here now and it came with 4.4.2 and I want to experiment with the old broke one before sending it back. I want to know what I can do and cannot do with 4.4.2 using Pie root and Towelroot, but try on the broke phone first, that's why I need to change from a good working 4.4 root to 4.4.2
Peace
doitinthedirt said:
Thanks for the info.. but give the ben of doubt. the phone was dropped by my brother and the glass is broke. the phone works fine. and is currently working perfect on 4.4 rooted with slapmymoto and wipemymoto
What I have the replacement phone here now and it came with 4.4.2 and I want to experiment with the old broke one before sending it back. I want to know what I can do and cannot do with 4.4.2 using Pie root and Towelroot, but try on the broke phone first
Peace Saw
Click to expand...
Click to collapse
Ok, that makes more sense I guess.
Yes if you want to experiment, download the entire 4.4.2 SBF for Verizon (that is your carrier, right?)
It is this one: http://sbf.droid-developers.org/download.php?device=0&file=841
Follow the instructions in the Return to Stock thread. Everything you need is there - all the tools, binaries, and drivers.
Once you have flashed the SBF, you will be on STOCK 4.4.2 and you can experiment all you want!
Good Luck
samwathegreat said:
Ok, that makes more sense I guess.
Yes if you want to experiment, download the entire 4.4.2 SBF for Verizon (that is your carrier, right?)
It is this one: http://sbf.droid-developers.org/download.php?device=0&file=841
Follow the instructions in the Return to Stock thread. Everything you need is there - all the tools, binaries, and drivers.
Once you have flashed the SBF, you will be on STOCK 4.4.2 and you can experiment all you want!
Good Luck
Click to expand...
Click to collapse
I've downloaded the ota and its on the phone now, can i flash this
doitinthedirt said:
I've downloaded the ota and its on the phone now, can i flash this
Click to expand...
Click to collapse
Nope. Not unless you have STOCK recovery, and an unmodified /system - which it appears you do not.
Just follow my previous instructions and flash the entire stock SBF (NOT the OTA). This will fix you right up in about 4 minutes...
So here's the deal, I unlocked my T-Mobile Moto X bootloader through Motorola's website about a year ago or so. I also rooted and didn't bother updating afterwards to anything since I had everything working perfectly for me. Now I need to update my 4.2.2 Moto X to 4.4.3 (or really anything >=4.3 just so I can use my Moto 360 that'll be arriving soon).
My question is, with an unlocked bootloader, rooted, TWRP 2.6.3.1, Xposed-installed Moto X, can I go ahead and flash a stock 4.4.3 ROM (for example from here: http://forum.xda-developers.com/moto-x/development/rom-stock-flashable-t-mobile-t2773675) and just call it a day?
I've been reading past threads and stuff to get back into the loop, but I just can'f find anything to answer me the simple question of updating an unlocked+rooted 4.2.2->4.4+ while keeping root. Just the simple question of, if I get a stock 4.4 image and flash it on my phone, will everything be okay?
I no longer have the passion and interest to constantly be fiddling with kernels, ROMs, and little hacks with my phone like I used to with my OG Droid and, to a lesser extent, with my Galaxy Nexus (plus I feel like it's gotten significantly less easy since those OG days).
I know (i.e. 90% sure) that one way to do what I want (kinda) is RSDLite/manually go back to stock without root on 4.2.2 and then accept the OTA, but certainly it has to be easier than that right? What happened to the days where I can just find a new Gingerbread ROM for my Froyo Droid and just flash it right then and there? Now everything is "go back to stock and do these convoluted steps."
(I'm sorry I'm ranting, I'm just really tired at the moment haha)
Thank you all, hopefully, for the help!
If you don't care about retaining your data, grab the 4.4.3 fxz and unzip it. Follow the directions for returning back to stock here: http://forum.xda-developers.com/moto-x/general/ref-complete-moto-x-guides-information-t2603358 but replace the files to be flashed with the files from the 4.4.3 fxz. Not sure where you got the idea that you need to go back to stock. Word of caution, once on 4.4.3 there's no going back to an older version.
I have the same question as the OP, on unlocked rooted 4.2.2 ATT Moto X, can i flash a custom 4.4.4 and keep root?
RGNDI said:
I have the same question as the OP, on unlocked rooted 4.2.2 ATT Moto X, can i flash a custom 4.4.4 and keep root?
Click to expand...
Click to collapse
You can take the ota but you need the stock recovery. Since you are unlocked you will not lose your unlocked-ness(lol) if you take an ota. But you do need to be completely stock: no su, no custom recovery, etc etc. But once you upgrade to 4.4.3 getting root back is as simple as flashing the appropriate version recovery again and then flashing supersu.
1ad_m12 said:
You can take the ota but you need the stock recovery. Since you are unlocked you will not lose your unlocked-ness(lol) if you take an ota. But you do need to be completely stock: no su, no custom recovery, etc etc. But once you upgrade to 4.4.3 getting root back is as simple as flashing the appropriate vision recovery again and then flashing supersu.
Click to expand...
Click to collapse
OK thanks, but cant I just Flash a Rooted Stock 4.4.4 over 4.2.2? Thats a more to the point question
RGNDI said:
OK thanks, but cant I just Flash a Rooted Stock 4.4.4 over 4.2.2? Thats a more to the point question
Click to expand...
Click to collapse
Yeah that would work as long as your radio is compatible with the rom. The rom you shared earlier should be fine. Just don't downgrade to anything pre 4.4 as that can cause issues because of partition sizes (or so I've heard). But after that I wouldn't take any OTA's cause your bootloader would be incompatible with the OTA and possibly cause a brick. If I were you I'd revert to stock and take the long way to 4.4.3 just so I can get the OTA for when Android L comes out. In fact thats what I plan on doing if the Sunshine bootloader unlock is successful. But if you don't care about that then everything should be fine.
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
?