I am using jcase's method of rooting form 4.4 down to 4.2.2 and back to 4.4 with a stock VZW Moto X.
I am trying to get some clarification on finishing on the first set of processes.
I have followed all the instructions for the first part successfully. I have Root and have disabled WP.
I was about to take the next step and "restore to the 4.2.2 Camera update" but this confuses me.
1) Will I lose root and WP?
2) Is this necessary to proceed to a rooted 4.4?
From jcase:
"First you must use MotoWPNoMo, if you haven't then you will need to. Use RockMyMoto to gain root, then use MotoWPNoMo, and then restore to the 4.2.2 Camera update."
bump
slingblade01 said:
bump
Click to expand...
Click to collapse
You will lose root but not wp off. That's exactly what you want. No root but wp off since the root method for 4.4 is different. So yes you want to restore back to 4.2.2 after root and wp off.
Sent from my XT1060 using Tapatalk
I have a Verizon Moto X non-developer edition on Android 4.4 that I rooted using SlapMyMoto 0.5c. It will loose root rights (e.g. can't run Titanium Backup) periodically. I get root again with a reboot but that is annoying.
I know that SlapMyMoto 1.0 is now available. Will running the whole SlapMyMoto process with the 1.0 files fix this? Is there a simpler way to keep root rights?
It should not lose root randomly sounds like something is wrong I would return to the 4.22 camera update and reroot your device and see if that fixes your issue
Sent from my XT1056 using XDA Premium 4 mobile app
With all the talk about downgrading causing bricks, I wanted to make sure that I had the right steps for rooting my Sprint XT1056 which is currently running 4.4 (30.B2 Bootloader):
1. Flash Android 4.2.2 Blur_Version.139.14.1.ghost_sprint.Sprint.en.US (is this the "Camera Update" version?) using RSD Lite
2. Use RockMyMoto and MotoWPNoMo
3. Reflash Android 4.2.2 Blur_Version.139.14.1.ghost_sprint.Sprint.en.US using RSD Lite
4. Use SlapMyMoto
5. Flash Android 4.4 Blur_Version.143.44.8.ghost_sprint.Sprint.en.US using RSD Lite (can I do this, or do I need to wait for my phone to download an OTA?)
6. Finish SlapMyMoto
Once the Sprint 4.4.2 OTA arrives, would taking it brick my phone if I've done this root method?
ahecht said:
With all the talk about downgrading causing bricks, I wanted to make sure that I had the right steps for rooting my Sprint XT1056 which is currently running 4.4 (30.B2 Bootloader):
1. Flash Android 4.2.2 Blur_Version.139.14.1.ghost_sprint.Sprint.en.US (is this the "Camera Update" version?) using RSD Lite
2. Use RockMyMoto and MotoWPNoMo
3. Reflash Android 4.2.2 Blur_Version.139.14.1.ghost_sprint.Sprint.en.US using RSD Lite
4. Use SlapMyMoto
5. Flash Android 4.4 Blur_Version.143.44.8.ghost_sprint.Sprint.en.US using RSD Lite (can I do this, or do I need to wait for my phone to download an OTA?)
6. Finish SlapMyMoto
Once the Sprint 4.4.2 OTA arrives, would taking it brick my phone if I've done this root method?
Click to expand...
Click to collapse
Forget slapmymoto or any root hack if you can unlock your boot loader. Slapmymoto has been untested AFAIK with the new 4.4.2 firmware. With any hack that involves bootloaders and system downgrades IMO will result in hard bricks , especially our moto x.
Sent on my Gummy running Lenoto X
ahecht said:
With all the talk about downgrading causing bricks, I wanted to make sure that I had the right steps for rooting my Sprint XT1056 which is currently running 4.4 (30.B2 Bootloader):
1. Flash Android 4.2.2 Blur_Version.139.14.1.ghost_sprint.Sprint.en.US (is this the "Camera Update" version?) using RSD Lite
2. Use RockMyMoto and MotoWPNoMo
3. Reflash Android 4.2.2 Blur_Version.139.14.1.ghost_sprint.Sprint.en.US using RSD Lite
4. Use SlapMyMoto
5. Flash Android 4.4 Blur_Version.143.44.8.ghost_sprint.Sprint.en.US using RSD Lite (can I do this, or do I need to wait for my phone to download an OTA?)
6. Finish SlapMyMoto
Once the Sprint 4.4.2 OTA arrives, would taking it brick my phone if I've done this root method?
Click to expand...
Click to collapse
well depending on your warranty standing you could just unlock your bootloader and install a customer recovery and SUPERSU it is alot eaiser.
ethier choice here is a link to my guide
http://forum.xda-developers.com/showthread.php?t=2603358
if you decide to go the hard way here are some links for you
Blur_Version.139.14.1.ghost_sprint.Sprint.en.US(Sprint 4.2.2 Camera update)
http://sbf.droid-developers.org/download.php?device=0&file=18
i would recommend just using the OTA with upgrading from 4.2.2 to 4.4 when doing the SlapMyMoto root exploit
as for 4.4.2 when ever us Sprint user get it in order to take the OTA you will have to flash a complete stock 4.4 firmware and then take the OTA because if you dont your phone will get stuck in a bootloop.
as of right now the only way to root 4.4.2 is with a unlocked bootloader.
flashallthetime said:
Forget slapmymoto or any root hack if you can unlock your boot loader. Slapmymoto has been untested AFAIK with the new 4.4.2 firmware. With any hack that involves bootloaders and system downgrades IMO will result in hard bricks , especially our moto x.
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
I'd prefer not to unlock and instavoid my warranty. I'm not going to send my phone back if I screw up the software, but I'd like the warranty to be there if my USB port or power button stops working.
Sent from my XT1056 using Tapatalk
ahecht said:
I'd prefer not to unlock and instavoid my warranty. I'm not going to send my phone back if I screw up the software, but I'd like the warranty to be there if my USB port or power button stops working.
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
I understand.
Sent on my Lenoto A2109 tablet
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.