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.
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.
Hi all, I was wondering if it would be less of a hassle to keep my BL unlocked Moto X stock until Lollipop OTA comes out OR if it might actually be harder to install recovery, root, etc when 5.0 is on the phone? IIRC KK made some changes that caused hassles on rooting, recovery install for some phones. I have Dev Edition, thanks
Although lollipop is making it difficult to root, you would still be able to unlock your BL on lollipop. Since it appears you don't have a need to root right now, I would just wait until lollipop. The reason to wait is if you install a recovery or freeze apps, you won't be able to install OTA until you restore stock recovery etc.
As long as you have an unlocked / unlockable BL, you will always be able to install a custom recovery / root.
PsychoKilla666 said:
Hi all, I was wondering if it would be less of a hassle to keep my BL unlocked Moto X stock until Lollipop OTA comes out OR if it might actually be harder to install recovery, root, etc when 5.0 is on the phone? IIRC KK made some changes that caused hassles on rooting, recovery install for some phones. I have Dev Edition, thanks
Click to expand...
Click to collapse
it depends.
With an unlocked bootloader we should continue to be able to flash a custom recovery, and custom rom.
However, there are several unknowns right now, including when will we see Lollipop for the X? Which variant of the 2013 X (Dev vs ATT vs VZW vs Sprint, etc) will get it first? When will soak tests start? When will the carriers finally push it, etc?
Then we don't know how hard or easy it will be to root. At first a custom kernel was needed to root Lollipop, but now it seems Chainfire has found away around that http://www.androidpolice.com/2014/1...w-to-root-lollipop-without-a-modified-kernel/ Until we see L on a 2013 X, we wont know for sure.
In any case, its always less hassle to keep your phone STOCK if you want to take an OTA. The OTA's need stock recovery on the phone in order to install. Also, diverting from stock can mean changes which will cause the OTA's pre-flash validation checks to fail, and the OTA to not install.
US Cellular is STILL on 4.4.2 lol 5.0 seems a hundred miles away still. Glad I'm unlocked, rooted and stock (Xposed Gravitybox) best combo IMHO.
Hey guys, I just finished downgrading from Lollipop .6 back to 4.4.4 on the Pure Edition (US) and upgrading to 22.21.11. I couldn't update to .11 from .6. I have a some questions now that my whole process is complete...
1 - Is their a way to root the Pure Edition that would allow me to take future OTAs without needing to downgrade next time? If so, I am wanting to root my phone again, where is the safer root method? I used CF-Auto Root when I rooted back in November.
2- Or is the downgrade/upgrade always going to be necessary on Lollipop on the Moto X (2014)?
3- Can one make an unrooted custom recovery nandroid image by booting to the custom recovery from adb? If so, what is the procedure? I would like to make a nandroid of my phone before I root it, so I can have that custom image to flash back to if I need to update Lollipop the same way again.
Thanks for all your help guys! I really appreciate it! Merry Christmas!
I've searched and found variations on these questions in other posts, but I didn't come across any pertaining quite to my situation, so I wanted advice before I do something wrong and brick my phone.
I have a Sprint Moto X, unlocked & rooted, running 4.2.2 (I think pre-camera update). I'd like to upgrade to stock Sprint Lollipop (when it comes out) & stay unlocked & rooted.
My understanding of the steps that need to be taken:
1. Unroot my device
2. Re-lock my device
3. Flash TWRP and boot to recovery
4. Flash stock Sprint Lollipop
5. Unlock, then re-root device
Is any of this extraneous, or am I leaving anything out? Do I need to upgrade to KitKat before going to Lollipop?
I also have Xposed installed and I have tweaked the PRL on my device ... this shouldn't complicate the upgrade, right?
Relocking is useless, and unless you know what you're doing, flashing stock updates in custom recovery shouldn't be done. You don't necessarily need to unroot either, just make sure all stock system files are still in place.
Sent from my Moto X
imnuts said:
Relocking is useless, and unless you know what you're doing, flashing stock updates in custom recovery shouldn't be done. You don't necessarily need to unroot either, just make sure all stock system files are still in place.
Sent from my Moto X
Click to expand...
Click to collapse
i have a sprint X and if i am going to update this is how i have allways done it with no issues at all.
you can leave your bootloader unlocked that is no a issue. but i always take OTA's and you cant take a OTA with a modded system. so i allways just flash my stock firmware package. that way it removes my custom recovery. Root, and all Xposed changes. Then i take the OTA and just reinstall TWRP, then SuperSU then what ever else you want.
this is the safest way i have found to update, the nice thing about Unlocked Sprint phones is we can easily Root are phones via TWRP and SuperSu.
just my .02 you can do it how ever you like but this is how i am going to do it when the OTA finally comes out if it ever does.