Search results

I was wondering if you'd mind sharing the steps you took to build the image. Did you start with the stock TWRP ghost image file then unpack, edit, and repack? Or did you actually make the property changes on the source and build? I unpacked your conversion and compared it to stock and saw...

I haven't encountered or heard of any bugs with 23.3.24, really. There's a thread in the other forum about lost features, but other than that and VoLTE I haven't noticed any differences from 21.11.21. I guess there's always a risk of an root exploit being found and released for an older...

There may be other reasons to stick with 21.11.21 but concerns over VoLTE shouldn't be one. Even before you can use VoLTE with the phone you have to get Verizon to enable it on your account either by calling them or your account page on their website. At least I did when it came out and I...

Same here. With VoLTE on I started getting call drops in places I had never had them before. I have it disabled now.

I more or less followed what Jaocagomez had done with previous stock releases and debloated my running 23.3.24 phone. Not a postable ROM, but a purge of the unneeded stuff. If there is interest I could put together a rough outline of steps but it wouldn't be for the faint of heart. You'd want...

In depth review of Lollipop: http://arstechnica.com/gadgets/2014/11/android-5-0-lollipop-thoroughly-reviewed/

Take a look at the F-Droid repository. There are a few flashlight apps there that might not be on the play store which could work for you.

Too late. Sunshine will not work. You could try going the paypal/imei route.

I'm pretty sure it's been out of soak for about a week now. See this post: http://forum.xda-developers.com/showpost.php?p=56091574&postcount=24 Maybe someone who got the OTA and wasn't part of the soak will chime in to confirm.

I'm on 21.11.21. Just checked for an OTA and it said it had nothin for me. I'm in no rush but it's weird how they roll these things out.

This may be a stupid comment, but are you sure this is the right FXZ link for the Mini? I only ask because I thought the Minis were obakem which is what is in the Ultra/Maxx posting. The link in this thread just has obake which I thought were the Ultras. I looked at the Ultra/Maxx posting and...

The reality is that you won't know for sure until you have it in your hands. However, I know someone who got a Mini recently and it was on 4.4. There is probably a ton of them still out there since it's an 'older' phone.

Is this what you were flashing?

Thanks Topsnake. Does the VZWEntitlementservice.apk rename have to be done with this build? Maybe I'm mis-remembering but I seem to recall only having to do the tethering option / build.prop change the last time or two around. I haven't taken the update yet to test.

Were you trying to just flash the system image, or did you flash older boot as well?

Apparently not. http://forum.xda-developers.com/showpost.php?p=54150949&postcount=561

What build of TWRP 2.7.1.1 do you use? ghost?

If you don't want to be bothered with an app for this, you can also just run the following command in a terminal. Would need to be done every boot, though. su -c "setprop net.tethering.noprovisioning true"

In a terminal window, run getprop ro.boot.write_protect to find out if WP is on. It will return 1 for yes or 0 for no.

Yeah, I think this is how Topsnake's exploit works.

I am currently using 2.7.0.0 found here: http://androidhosting.org/Devs/Dhacker29/MotoX/ Anyone seen a newer msm8960 version, or has anyone tried the latest Moto X ghost version (2.7.1.1) found here: http://techerrata.com/browse/twrp2/ghost

Has anyone gotten the update that wasn't part of the soak test (or downloaded it separately)? Just wondering if they are rolling this out all over yet. I'm holding off until the full release and my phone still says I'm up to date on 4.4.

Since the assumed starting point was stock recovery, I didn't include re-flashing a custom recovery as an essential step. However, can someone confirm whether it's explicitly necessary to re-install SuperSU or app of choice for re-rooting?

Would like to clarify my understanding of the update based upon what I've read from this thread so far. Assumes a starting point of stock 4.4 (19.6.3) & recovery. If one has an unlocked bootloader (either dev edition or via Chinese guy) with root access, WP off, and takes the 4.4.4 OTA update...

A while ago I verified that the stock system images were the same for the Ultra, Maxx, & Mini. But as pointed out there are some subtle hardware differences. For example the smaller form factor of the Mini may have led Motorola to use a different component for the audio. The stock image...

Well, I ended up flashing the system.img file and then rebooting immediately into TRWP and taking a backup. From that I was able to copy it down and extract the contents. Kind of roundabout but it worked. If someone has a more direct method I'd like to know how it can be done.

Is there a way to mount or extract the files within the stock system.img (and other img files)?

There is a long thread on it here, but you might have missed your chance: http://forum.xda-developers.com/moto-x/general/verizon-moto-maker-bootloader-unlock-t2680651

I've had no problems backing up and restoring with 2.7.0.0 on a Droid Mini. However I tried to install a recent CM nightly and it failed because the ro.product.device in TWRP was blank. I edited the CM updater-script to remove the device check and repacked the zip. After that I got it to install.