[ROM][Safestrap][XT1060] Stock Rooted Vzw 140.45.5 KitKat

14459 Views 40 Replies 10 Participants Last post by KrYpToNiTe, Mar 4, 2014

KrYpToNiTe

Discussion Starter · Nov 23, 2013 (Edited by Moderator)

3

*** DISCLAIMER ***

I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE! OR IF YOU LOSE ANY DATA, ITS CALLED BACK IT UP BEFORE HAND!

Word to the wise if you don't know how to use RSDLite to restore your phone then leave this thread now please! There is a reason I didn't post this on XDA, I will not attempt to dumb this down anymore. You need to backup everything on your internal storage before you install this, because to switch back to 4.2.2 you will have to RSD back to stock. This needs to be flashed to the STOCK SLOT and the KitKat Kernel and Baseband needs to be flashed for it to work. YOU'VE BEEN WARNED!

Okay this is a stock unmodified rooted rom of the KitKat OTA with full Safestrap functionality except for restoring back to 4.2.2. Of the 3-4 different test I did, I still haven't been able to restore a 4.2.2 backup it goes into a bootloop. So for me I rsd'd back to the factory 139.10.53 sbf or 139.15.1 sbf if your on the camera OTA. Then reroot with pwnmymoto/rockmymoto, reinstall safestrap and restore your 4.2.2 backup. So far I've been running this all day, no issues have surfaced besides some apps not being available for KitKat yet. Also while writing this I switched to ART runtime, and so far everything is still functioning great! You will need to have the phone drivers installed to get this working so go here and download and install them. https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/94931/p/30,6720,8696

Instructions to install this rom follow every step...

1. You need to be rooted on 4.2.2 with Safestrap installed

2. Boot into Safestrap Recovery

3. Factory Reset the STOCK Slot in Safestrap

4. Flash the rom zip to the STOCK Slot (this will take a couple minutes)

5. Once the rom has finished flashing reboot to Bootloader within Safestrap

6. Unzip the "Moto X Kernel and Radio Flasher.zip"

7. Open the extracted folder and find the FlashMyMotoX.bat and run it

8. Plug your Moto X via usb cable into your computer the phone should say usb connected now

9. Choose option 6 within the FlashMyMotoX utility then hit enter it will flash the KitKat Kernel

10. Once it finishes get back to the options and choose option 7 this will flash the KitKat Baseband

11. Once it finishes succesfully unplug your usb cable and reboot the phone

12. Enjoy KitKat!

Downloads: DO NOT repost links on other forums, link them to this thread!

Rom: https://www.dropbox.com/s/s8z8hzt8gto6obh/140.45.5-KitKat-Verizon-Safestrap.zip

Utility: https://www.dropbox.com/s/n9an1ok4p7ft607/Moto%20X%20Kernel%20and%20Radio%20Flasher.zip

Thanks to Hashcode for Safestrap, and jcase for root, without them this wouldn't be possible!

See less See more

Reactions: 2

21 - 40 of 41 Posts

dspolen

· #21 · Dec 3, 2013

Yea....ummmm? You see what happened was...I was running the program as administrator. Once I ran it normal. It went ok and booted right up. Haha. Thanks for your response and thanks for the ROM!

KrYpToNiTe

Discussion Starter · #22 · Dec 3, 2013

dspolen said:
Yea....ummmm? You see what happened was...I was running the program as administrator. Once I ran it normal. It went ok and booted right up. Haha. Thanks for your response and thanks for the ROM!

No problem I figured it was something to do with flashing the kernel, because it won't boot without it, glad you figured it out!

redhonker

· #23 · Dec 6, 2013

Hi,

hashcode said safestrap does not work on 4.4. Since we are overwriting stock ROM, does it mean after this we won't have ability to update safestrap?

Thanks

KrYpToNiTe

Discussion Starter · #24 · Dec 7, 2013

redhonker said:
Hi,

hashcode said safestrap does not work on 4.4. Since we are overwriting stock ROM, does it mean after this we won't have ability to update safestrap?

Thanks

By installing the rom you're technically still on the 4.2.2 bootloader and filesystem this only flashes the /system partition, safestrap's main hijack files aren't in the /system partition. So technically we should be able to upgrade safestrap if and when hashcode updates it, I won't know for sure until that time comes though.

mercado79

· #25 · Feb 18, 2014

Still find it strange that this thread has so little activity. Worse yet, the OP has only logged one "like"!

@kryptonite, thanks for the ROM. It's very much appreciated. Fingers crossed that there'll be an updated version once 4.4.2 is released for the VZ Moto X.

Sent from my Moto X

anotherfiz

· #26 · Feb 18, 2014

I am about ready to move back to 4.2.2. The bluetooth issues and battery life disappoint me so much. 4.4.2 better come quick , and be amazing.

KrYpToNiTe

Discussion Starter · #27 · Feb 26, 2014

mercado79 said:
Still find it strange that this thread has so little activity. Worse yet, the OP has only logged one "like"!

@kryptonite, thanks for the ROM. It's very much appreciated. Fingers crossed that there'll be an updated version once 4.4.2 is released for the VZ Moto X.

Sent from my Moto X

Your welcome! As soon as the sbf for 4.4.2 is dropped I will start working on it. It might take a couple days after that before I release it, my focus at the moment is working on finishing up development on a computer application I've been working on right now.

Reactions: 1

iNate71

· #28 · Feb 28, 2014 (Edited by Moderator)

deleted

mercado79

· #29 · Feb 28, 2014

KrYpToNiTe said:
Your welcome! As soon as the sbf for 4.4.2 is dropped I will start working on it. It might take a couple days after that before I release it, my focus at the moment is working on finishing up development on a computer application I've been working on right now.

Not sure if this is useful to you, but I just saw this posted on XDA. At the very least, I hope this means the sbf is on the way soon!

Verizon Moto X (Retail) 4.4.2 firmware added to the Moto X Restore Utility. If you just want the firmware itself you can find it on sbf.droid-developers.org when it updates or grab it at http://batakang.com/ftp/MOTOX/LatestVZWFirmware.zip

Sent from my Moto X

iNate71

· #30 · Mar 1, 2014

KrYpToNiTe said:
Your welcome! As soon as the sbf for 4.4.2 is dropped I will start working on it. It might take a couple days after that before I release it, my focus at the moment is working on finishing up development on a computer application I've been working on right now.

Just to clarify--you can't install this ROM while I'm on 4.4 stock rooted already, right? You said to install it while I'm on 4.2.2--however, if you used SlapMyMoto--you're using 4.2.2's bootloaders as well.

KrYpToNiTe

Discussion Starter · #31 · Mar 1, 2014

iNate71 said:
Just to clarify--you can't install this ROM while I'm on 4.4 stock rooted already, right? You said to install it while I'm on 4.2.2--however, if you used SlapMyMoto--you're using 4.2.2's bootloaders as well.

Why would you want to install this on a 4.4 stock rooted, you would be flashing basically the same thing you already have? This rom is the stock rooted 4.4 but for people like me who are still on either 4.2.2 versions. I haven't took a single update yet I'm still on the factory shipped pre-camera update bootloader!

KrYpToNiTe

Discussion Starter · #32 · Mar 1, 2014

mercado79 said:
Not sure if this is useful to you, but I just saw this posted on XDA. At the very least, I hope this means the sbf is on the way soon!

Sent from my Moto X

Thanks man, yes that's the sbf file I was looking for it has been added to site I've been looking at. I will probably start working on this monday if I'm finish debugging my application I've been been working on for the past two weeks.

Reactions: 2

iNate71

· #33 · Mar 1, 2014

KrYpToNiTe said:
Why would you want to install this on a 4.4 stock rooted, you would be flashing basically the same thing you already have? This rom is the stock rooted 4.4 but for people like me who are still on either 4.2.2 versions. I haven't took a single update yet I'm still on the factory shipped pre-camera update bootloader!

I dunno. Lol. I wanted to start using Safestrap. I've never used it before--figured I should get my bearings. Hehe.

mercado79

· #34 · Mar 1, 2014

KrYpToNiTe said:
Thanks man, yes that's the sbf file I was looking for it has been added to site I've been looking at. I will probably start working on this monday if I'm finish debugging my application I've been been working on for the past two weeks.

Awesome. Good luck with the "real" work!

Sent from my Moto X

mercado79

· #35 · Mar 3, 2014 (Edited by Moderator)

@KrYpToNiTe: I just posed this question on XDA (in regards to creating an updated script for the new 4.4.2 files), but wanted to get your take (this is what I went with, but I'm curious if I should go back and reflash or not):

The original root method wrote the boot.img to both boot and recovery partitions. Your script does exactly that. However, with the latest root version, we were keeping stock recovery (I thought). So... I'm planning to skip that line (the second one below) from the batch file. Make sense?

fastboot flash boot 164.55.2-KK-boot.img
fastboot flash recovery 164.55.2-KK-boot.img

anotherfiz

· #36 · Mar 3, 2014 (Edited by Moderator)

Keep them both. , all things about the original batch file remain consistant =D the BL is still kept safe with safestrap.

boot.img contains the kernel and ramdisk, critical files necessary to load the device before the filesystem can be mounted. Recovery.img is what contains recovery and we are not flashing that

KrYpToNiTe

Discussion Starter · #37 · Mar 3, 2014

mercado79 said:
@KrYpToNiTe: I just posed this question on XDA (in regards to creating an updated script for the new 4.4.2 files), but wanted to get your take (this is what I went with, but I'm curious if I should go back and reflash or not):

The original root method wrote the boot.img to both boot and recovery partitions. Your script does exactly that. However, with the latest root version, we were keeping stock recovery (I thought). So... I'm planning to skip that line (the second one below) from the batch file. Make sense?

fastboot flash boot 164.55.2-KK-boot.img
fastboot flash recovery 164.55.2-KK-boot.img

The new root method requires you to use MotoWpNoMo to bypass write protection since they patched the vulnerability that allowed us to flash the boot.img to the recovery partition to bypass write protection in the 4.4 bootloader. But I haven't ran the MotoWpNoMo on mine because I haven't had time to decompile PwnMyMoto to see if it will work once write protection is disabled. Since I am still on the factory bootloader and whenever I have to rsd I go back to that version and use PwnMyMoto to root. So I still have to flash the boot.img to the recovery partition to bypass write protection.

I've already tested one build of the 4.4.2 update but had an issue with a failed permission, hopefully I will have a solid build by tonight or tomorrow.

anotherfiz

· #38 · Mar 3, 2014

KrYpToNiTe said:
The new root method requires you to use MotoWpNoMo to bypass write protection since they patched the vulnerability that allowed us to flash the boot.img to the recovery partition to bypass write protection in the 4.4 bootloader. But I haven't ran the MotoWpNoMo on mine because I haven't had time to decompile PwnMyMoto to see if it will work once write protection is disabled. Since I am still on the factory bootloader and whenever I have to rsd I go back to that version and use PwnMyMoto to root. So I still have to flash the boot.img to the recovery partition to bypass write protection.

I've already tested one build of the 4.4.2 update but had an issue with a failed permission, hopefully I will have a solid build by tonight or tomorrow.

I am running on 4.2.2 post camera OTA BL using MotoWpNoMo, safestrapped from there and running 4.4.2 . injected kernel / baseband using your batch file, edited to add the 4.4.2 portions.

mercado79

· #39 · Mar 3, 2014 (Edited by Moderator)

anotherfiz said:
Keep them both. , all things about the original batch file remain consistant =D the BL is still kept safe with safestrap.

boot.img contains the kernel and ramdisk, critical files necessary to load the device before the filesystem can be mounted. Recovery.img is what contains recovery and we are not flashing that

I get that. That's why I'm skipping the step where the script said flash boot.img to recovery. I'm only flashing boot.img to the boot partition.

KrYpToNiTe said:
The new root method requires you to use MotoWpNoMo to bypass write protection since they patched the vulnerability that allowed us to flash the boot.img to the recovery partition to bypass write protection in the 4.4 bootloader. But I haven't ran the MotoWpNoMo on mine because I haven't had time to decompile PwnMyMoto to see if it will work once write protection is disabled. Since I am still on the factory bootloader and whenever I have to rsd I go back to that version and use PwnMyMoto to root. So I still have to flash the boot.img to the recovery partition to bypass write protection.

I've already tested one build of the 4.4.2 update but had an issue with a failed permission, hopefully I will have a solid build by tonight or tomorrow.

Exactly what I figured. I already ran MotoWpNoMo/SlapMyMoto and so, no flashing of boot.img to recovery partition for me!

I've done that and loaded up the latest Eclipse 3.2.1 which is 4.4.2-based. No problems thus far. Looking forward to your stock 4.4.2 though!

mercado79

· #40 · Mar 4, 2014 (Edited by Moderator)

For anyone that's been monitoring this thread waiting for the update, a new thread was created.

http://rootzwiki.com/topic/116025-romsafestrapxt1060-stock-rooted-vzw-164552-kitkat-442/

Reactions: 1

21 - 40 of 41 Posts

This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.