[Q] Flashing Verizon 4.4.2 Keep Root - Moto X Q&A

Is there any way to flash the update manually without flashing the bootloader, and perhaps thus keep write protection off while enjoying 4.4.2?

titanshadow said:
Is there any way to flash the update manually without flashing the bootloader, and perhaps thus keep write protection off while enjoying 4.4.2?
Click to expand...
Click to collapse
please search before posting this question has been asked many times in the Q & A section and there is also a thread in the General section all about the 4.4.2 OTA for locked bootloaders below is the link
http://forum.xda-developers.com/moto-x/general/verizon-4-4-2-ota-discussion-locked-t2664444

Related

[Q] Back-ups When Rooting

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.

Newest SBF file

I remember having to delete a line during the sbf process for SlapMyMoto, with the new 4.4.2 sbf file will this be necessary again?
http://forum.xda-developers.com/showthread.php?t=2603358
This guide can answer your questions better, or look in the locked bootloader threads.
But if you are on 4.4.2 now and not rooted, you're out of luck. You can't do it. You can possibly downgrade, tho it can lead to a brick if not done completely properly.
If you are already rooted before updating to 4.4.2, depending how you upgraded, you will have root....but read/write is enabled and can't currently be disabled on 4.4.2. So any root changes you make will be gone if you hard reboot or power off the phone.
Read up for more info.
Sent from my cell phone telephone....
kj2112 said:
http://forum.xda-developers.com/showthread.php?t=2603358
This guide can answer your questions better, or look in the locked bootloader threads.
But if you are on 4.4.2 now and not rooted, you're out of luck. You can't do it. You can possibly downgrade, tho it can lead to a brick if not done completely properly.
If you are already rooted before updating to 4.4.2, depending how you upgraded, you will have root....but read/write is enabled and can't currently be disabled on 4.4.2. So any root changes you make will be gone if you hard reboot or power off the phone.
Read up for more info.
Sent from my cell phone telephone....
Click to expand...
Click to collapse
As you saw from my other thread, I'm on rooted 4.4.2 with read/write enabled. Is it safe flash the 4.4.2 SBF back to stock or is that considered a downgrade? I read going back to stock is recommended before unlocking the bootloader.
Thanks
kj2112 said:
http://forum.xda-developers.com/showthread.php?t=2603358
This guide can answer your questions better, or look in the locked bootloader threads.
But if you are on 4.4.2 now and not rooted, you're out of luck. You can't do it. You can possibly downgrade, tho it can lead to a brick if not done completely properly.
If you are already rooted before updating to 4.4.2, depending how you upgraded, you will have root....but read/write is enabled and can't currently be disabled on 4.4.2. So any root changes you make will be gone if you hard reboot or power off the phone.
Read up for more info.
Sent from my cell phone telephone....
Click to expand...
Click to collapse
I'm unlocked now, I wanted to go through RSD for my problem but ended up pulling the needed files and flashing what I needed through fastboot.
EvanVanVan said:
As you saw from my other thread, I'm on rooted 4.4.2 with read/write enabled. Is it safe flash the 4.4.2 SBF back to stock or is that considered a downgrade? I read going back to stock is recommended before unlocking the bootloader.
Thanks
Click to expand...
Click to collapse
You can't be on 4.4.2 with a locked bootloader, rooted with write protection disabled. If you are, you're the first and only one on here.
I think we're miscommunicating a bit.
I am sure what you have is root.....with write protection enabled. As is the issue with 4.4.2. Meaning, if you hard reboot, you lose all root changes. Correct?
But no, you don't need to do anything to unlock the bootloader. Your phone will be wiped during the process. You'll have to flash custom recovery and root after. Then install all your apps again.
Sent from my cell phone telephone....

EU XT1052 OTA, some guidance please?

Hi there, I have a stock retail EU Moto X (XT1052) and this morning I got the notification that there was a system update.
My phone is 100% factory so my bootloader is locked and I am not rooted, but I know how to unlock and root
My question is if I unlock and root would the OTA be useful to devs here? if so where and how to I capture the update and considering how may other users have reported issues with battery life etc what is the best method to return back to 4.4.2?
Thanks guys
dr_strangetrick said:
Hi there, I have a stock retail EU Moto X (XT1052) and this morning I got the notification that there was a system update.
My phone is 100% factory so my bootloader is locked and I am not rooted, but I know how to unlock and root
My question is if I unlock and root would the OTA be useful to devs here? if so where and how to I capture the update and considering how may other users have reported issues with battery life etc what is the best method to return back to 4.4.2?
Thanks guys
Click to expand...
Click to collapse
Well, first this is already being discussed here (as well as some info regarding the changes / battery life in the new update):
http://forum.xda-developers.com/moto-x/general/moto-x-g-e-4-4-4-kitkat-rollout-t2805645
You can feel free to read through that thread, and address any questions, concerns, and/or comments there.
Second, other users have already been kind enough to share all of the OTA files, so that would be unnecessary. A kind offer, however. :good:
OK, thanks
I must admit I did not see anything about the EU 1052 OTA but I suppose after waiting so long I could have missed it
Cheers
If you have the OTA file to share (you can only pull it off your phone if you are rooted), it wont hurt, even if someone else has shared it.
Just make sure you say exactly what phone it is for (carrier and model).
If you do unlock your bootloader and root to get the file, just remember you'll need to flash stock recovery back on your phone to take the OTA (please use the stock recovery from the ROM currently on your phone... If you don't have it, visit http://sbf.droid-developers.org/phone.php?device=0 download the SBF that matches what is on your phone, and unzip it. the stock Recovery.IMG is inside it)
OK, I've got the Blur_Version.161.44.16.ghost_row.Retail.en.GB.zip
I have taken a quick look around but I can't see anything, is there a specific OTA thread I can add to? if not which is the best section to add to?
Thanks
dr_strangetrick said:
OK, I've got the Blur_Version.161.44.16.ghost_row.Retail.en.GB.zip
I have taken a quick look around but I can't see anything, is there a specific OTA thread I can add to? if not which is the best section to add to?
Thanks
Click to expand...
Click to collapse
The link I posted for you in Post # 2 would be the best place for it. That is where the 4.4.4 roll-out discussion is taking place, and it is also where all of the other OTAs have been posted. That one IS already in there, though.

[Q] Need Sprint 4.4.4 Stock Image

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.

Can I flash any rom from 4.4.2 NCE?

Ok this might sound like a dumb question but I'm just being overly cautious to not brick my device.
I'm on build 4.4.2 NCE stock, I'm rooted with towelroot, and I have the safestrap recovery working. Can I just flash any rom now, such as lollipop roms, or am I only able to flash 4.4.2 kitkat roms or roms with [NCE] in the name? To my understanding 5.0 cant be rooted and we cant downgrade from 5.0 to 4.4.2 due to a locked bootloader or something like that.
I already have a nandroid backup created in safestrap and I have flashed dozens of roms before on my s3. Say for example if I wanted to flash the unified cm12 rom which is 5.1 lollipop http://forum.xda-developers.com/gal...ent/rom-cyanogenmod-12-1-android-5-1-t3066252
Would that be a bad idea or would it work just fine?
Also, I'm supposed to flash in the stock slot in safestrap since romslots don't work right?
Larrymoses said:
Ok this might sound like a dumb question but I'm just being overly cautious to not brick my device.
I'm on build 4.4.2 NCE stock, I'm rooted with towelroot, and I have the safestrap recovery working. Can I just flash any rom now, such as lollipop roms, or am I only able to flash 4.4.2 kitkat roms or roms with [NCE] in the name? To my understanding 5.0 cant be rooted and we cant downgrade from 5.0 to 4.4.2 due to a locked bootloader or something like that.
I already have a nandroid backup created in safestrap and I have flashed dozens of roms before on my s3. Say for example if I wanted to flash the unified cm12 rom which is 5.1 lollipop http://forum.xda-developers.com/gal...ent/rom-cyanogenmod-12-1-android-5-1-t3066252
Would that be a bad idea or would it work just fine?
Also, I'm supposed to flash in the stock slot in safestrap since romslots don't work right?
Click to expand...
Click to collapse
DO NOT FLASH ANY CM ROMS. You have a locked bootloader and it will not work. Stick with the 4.4.x roms in the development threads here in the AT&T forum. DO NOT FLASH 5.0 roms unless you upgrade to 5.0 through Muniz "update to 5.0 and keep root" thread which can be found in the "General section"
dirtydodge said:
DO NOT FLASH ANY CM ROMS. You have a locked bootloader and it will not work. Stick with the 4.4.x roms in the development threads here in the AT&T forum. DO NOT FLASH 5.0 roms unless you upgrade to 5.0 through Muniz "update to 5.0 and keep root" thread which can be found in the "General section"
Click to expand...
Click to collapse
i'm now on 5.0 through Muniz's method,and i want to flash CM 12,will it OK or not?
No. You have locked bootloader. Read about your device or you'll end up with an expensive paper weight. This forum is filled with tons of info. Just click the search button.
dirtydodge said:
No. You have locked bootloader. Read about your device or you'll end up with an expensive paper weight. This forum is filled with tons of info. Just click the search button.
Click to expand...
Click to collapse
a million thanks to you!!

Categories

Resources