Search results

I'd wager the kernel offset is different from the RAZR i but I have no working knowledge of finding it for new devices. Best of luck!

All I wanted was my monthly security updates. I won't complain until June 1st when I don't get a May update ;)

Definitely could be done in a custom image. You can turn off the cap keys from doing things by commenting out lines in /system/usr/keylayout if I recall from my XT912 ROM, then in /system/framework/framework-res.apk there was a values.XML where you could turn off their backlight(s) as well. In...

For now, yeah.

Whatever happens please report your findings back here! I'm curious how well the XT1225 CM12.1 works on your device.

You made sure there was no spaces right? I have made that mistake before, to be honest.. AAAAAAA BBBBBBB CCCCCC Should Be AAAAAAABBBBBBBCCCCCC

Found this in another thread: http://www.emui.com/plugin.php?id=unlock&mod=detail

I've been watching, biding my time for an opportunity to help. *Batman*

Uh nope. You'd need the kernel in the boot.img and that wouldn't flash on a locked device.

That's the idea! I'd wait on a fully written guide /or video first ;) The important thing to note is you must be on 4.4.4

It does now, it looks like ;)

I'll make sure he does! :D

Care to try with the unrooted image (through Mofo) to see if it boots?

Assuming the secure version wasn't increase with a bootloader/partition table upgrade, they should be (in theory).

IF YOU UPGRADED TO 5.1 ALREADY THIS IS NOT FOR YOU EDIT: See the post by firstEncounter! http://forum.xda-developers.com/showpost.php?p=61749727&postcount=6 Downloads: tldr; If Lollipop can run without Lollipop bootloader/partition table then you can have rooted Lollipop and keep ability...

They cannot be tampered with, or they cannot be flashed through the signature check, which is what verifies the integrity of the file as well. Mofo, however, does not verify signature for obvious reasons. Where this particular file popped up is hard to say.

Looking for a tester on 4.4.4 firmware w/ Mofo license. Hit me up in a PM. This is for getting rooted lollipop running / reserving ability to downgrade back to 4.4.4 EDIT: Found some, thanks!

Assuming one is still on 4.4.4, they should be able to flash the lollipop modem/boot/recovery through fastboot and let Mofo flash a rooted lollipop system image... in theory.

This is affecting non-rooted stock devices. There isn't a clear thing to disable, anyway. Edit: Mines gone away on its own Edit 2: Nope. Still here.

Happening here too. T-Mobile S6 Edge

It is locked by FRP (Factory Reset Protection, I assume) which is required by California Law and is the "Device Protection" you've probably heard of. There is supposed to be a way to disable it on devices its just supposed to be on by default. Source...

Got everything to run correctly, but now its stuck at the bootlogo (the blue M and Powered by Android). Anybody else run into this? AT&T. EDIT: Looks like someone else did! I didn't flash RSD before either. OTA to 4.4.4 apparently is not the same as RSD. Weird! This worked!

Well that's a shame, that may very well be it. Soon enough SamMobile or Kies should be able to fix that brand new phone :(

Kies3 still says unsupported even after its update today. Emergency Firmware recovery would probably fix you, if it was supported. What did you do to break it?

Use something like Nova Launcher if you want to do that.

2 hours 37 min SoT. Good cell signal all day too. Never dropped off LTE. And stronger speeds than my Nexus 6. Weird!

No.

That's not how WiFi calling works. You will see a notifications and its not enabled by default because you need to set an E911 address. Plus, you'll see a notification at the top if it actually worked in this build, which it could possibly but it seems like its not finished yet. This build has...

Yup!

So there's two options to go for here, and one seems more "User Friendly" and doesn't require a GNU/Linux based OS running on a desktop or VM. The one I was going for was the one you described: Option 1 - Get temporary WP disabled somehow, as some users have claimed. Make changes, but before...

That was the idea behind this. But it doesn't seem like WP is even temporarily lifted. Feel free to play around with it.

Found someone :)

You think the exploit dev hasn't tried remounting /system as RW? I mean, if it works that's great, but I'd wonder why they haven't said this already.

Completely stock unrooted, never unlocked on 5.0.1. I'm also using a stock Moto 360. Therfreeze happens when it wants to, when I'm not using the phone. I don't usually notice until I next check my phone and the lock button doesn't unlock my phone, then I look at my Moto 360 and see that its...

I'm glad to see I'm not the only one seeing these problems. Where's our 5.0.2 to fix it? Happens to me almost once a day now.

Motorola has exclusively used FedEX for all of my orders.

So others can I see I screen-capped it.

Yes at 0:14 in the video pause it and you'll see the model information.

You are welcome to live in your own delusions there... they used a variant NOT SOLD FROM VERIZON and it works on Verizon. Whether its not a "true fact its a review unit from T-Mobile" its still a Non-Verizon sold Nexus 6 working on Verizon. I don't want to argue, and I won't be responding...

Their unboxing clearly has a T-Mobile return manual inside and on the box it mentions TMO where the S/N and IMEI are.

Apparently this hasn't been reposted enough times, this is a T-Mobile Review Unit: http://www.droid-life.com/2014/10/31/nexus-6-working-on-verizon-out-of-the-box/

Post-Wildfire

They don't even carry 32/64GB iPhone's in store normally...

I had to reset the watch to get it to connect, and for good measure made sure bluetooth discovery was on (and the Moto 360 is not already paired).

Android Wear with my Moto 360 is consistently killing my T-Mobile Xperia Z3's battery life every day. Yesterday it used over 35% of the total battery, topping out Screen-On time in the battery listings. This morning it has already killed 28% and its barely 11AM. Is anyone else experiencing the...

I couldn't order a Nexus 4, it kept going down over and over until it sold out so... in my eyes it did >.>

No problems with Nvidia SHIELD streaming in the same setup. This is hardwired the same as the PS4... quite low enough latency to play and "should" work fine. However, 1 second input lag and disconnects no matter how strong the WiFi signal for the Z3. I don't think my connection is the problem...

They run out of stock FAST! I couldn't get a Nexus 4 in time, went within minutes.

PS4 is hard-wired. WiFi is AC. Even 10 feet from the router its completely unplayable. 1 SECOND of lag at least and disconnects. Nvidia SHIELD runs perfect without a hitch... streaming 720p as well from my Desktop computer with the same situation as the PS4. There is something wrong with...

Yeah that's definitely an international (or possibly just BR) version of the DROID Turbo!