Android OS Forum banner
21 - 40 of 41 Posts

·
Android Phablet Enthusiast
Joined
·
56 Posts
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!
 

·
Registered
Joined
·
92 Posts
Discussion Starter · #22 ·
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!
 

·
Registered
Joined
·
92 Posts
Discussion Starter · #24 ·
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.
 

·
Registered
Joined
·
60 Posts
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
 

·
Registered
Joined
·
92 Posts
Discussion Starter · #27 ·
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.
 

·
Registered
Joined
·
60 Posts
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
 

·
Developer Knight
Joined
·
542 Posts
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.
 

·
Registered
Joined
·
92 Posts
Discussion Starter · #31 ·
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!
 

·
Registered
Joined
·
92 Posts
Discussion Starter · #32 ·
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.
 

·
Developer Knight
Joined
·
542 Posts
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.
 

·
Registered
Joined
·
60 Posts
@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
 

·
Android Apprentice
Joined
·
111 Posts
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
 

·
Registered
Joined
·
92 Posts
Discussion Starter · #37 ·
@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.
 

·
Android Apprentice
Joined
·
111 Posts
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.
 

·
Registered
Joined
·
60 Posts
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.

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!
 
21 - 40 of 41 Posts
Top