Search results

The latest version that was posted recently is working fine, no warning message. Xfinity_Stream_6.3.2.002-HDMI_MOD.apk

It's been awhile since that happened, so I don't remember details beyond what I posted above. Did you try to downgrade and you're stuck in a bootloop?

I think you're right about that. I ended up unbricking my unit after about 6 hours of messing with it. I flashed everything from the 3.3 set (including userdata.img) EXCEPT the "Staging Blob" ... that I used a 5.0 version from the zip in this thread. When it rebooted it went straight to this...

Incredibly I was able to get it working again. I flashed everything from the 3.3 image including userdata.img, but kept the blob file from 5.0 ... it booted and immediately started downloading 5.0 from the internet, so I let it finish. Sure enough I'm back up and running 5.0. Needless to say...

Just an update, I can boot TWRP now, but only after flashing the blob and boot.img from inside the OTA zip. I can get into Sideload mode but the zip fails, probably because of the different versions of boot.img and the blob. (and without those the unit won't boot anything except Fastboot)

If they'd post the full 5.0.2 image it would probably help. In my case I'm stuck with a bricked Shield because 3.3 won't boot, and I have no way to go back to 5.0

I have a very similar problem. I tried to flash a 2015 Shield that previously had 5.0.2 with the 3.3 Factory image. All I get is a black screen now. I can still get the Fastboot menu to come up but that's it.

---------- Post added at 03:38 PM ---------- Previous post was at 03:37 PM ---------- [/COLOR] That's the exact same image that I tried previously <see my output log in my previous post> ---------- Post added at 03:41 PM ---------- Previous post was at 03:38 PM ---------- That one...

I also tried that method, still no dice. Just getting a black screen: C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot Hacked-twrp-3.0.2-darcy.img downloading 'boot.img'... OKAY [ 0.364s] booting... OKAY [ 0.000s] finished. total time: 0.364s After a few minutes still black...

I flashed TWRP, but can't seem to get it to load. I'm using the one from here: https://forum.xda-developers.com/shield-tv/development/recovery-twrp-shield-android-tv-2017-t3545544

That's in OTA format, not individual .image files I can flash with Fastboot. Right now I can't boot into the full OS, only Fastboot works.

It won't boot after flashing the full 3.3 image set ... that's why I wanted to try 5.0 .... perhaps something changed going from "M" to "N" ... and its preventing the downgrade. See others with the issue here...

Does anyone know if it's possible to flash this via Fastboot? I tried to downgrade a 2015 Shield TV from 5.0 to 3.3 to get DRM working again for the HDHomeRun Green app, and it won't boot now. I can get to the Fastboot menu but that's it. Of course Nvidia hasn't posted the 5.0 image for the...

Amen to that!!! :)

LOL ... The Dinc! I remember being an early rooter of that device and having to spam a button to create a race condition just to get in ... those were the days. ;) PS Forbes just wrote an article calling the 6P the best smartphone currently available on any platform. *winning*

The Fi dialer doesn't play nicely with layers from what I experienced, I think that's why it's an option and not baked in.

This is a direct link: https://dl.google.com/dl/android/aosp/angler-mdb08m-factory-dbc17940.tgz You have to backup anything you want to save first if you go back to pure stock via your computer.

How about flashing the "M" Vendor image via fastboot. If that doesn't work I would backup and take it back to stock first. Great guide here: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 Full M factory image here...

Did you do step 1 correctly? Install instructions: 1. Wipe data,system,cache,dalvik cache from twrp 2. Flash PureNexus rom zip 3. Flash PureNexus Arm64 Gapps (advanced wipe, check boxes for data, system, cache and dalvik)

It does, scroll to the bottom of the list, on the right side.

Just a quick note to say the 11/13 build is running great! Beans had the best ROM by far for the Note 3 and I'm SO psyched I picked a new phone that he's developing for. :D btw, if it helps anyone else, I had applied the Domination layers while I had the Google Fi dialer installed, and it...

Ah, that's good to know. The release notes seemed to indicate that you had to use the new partial firmware with this 6.x version.

To anyone running 6.x, how is your 4G reception with the new firmware? The reason I ask is the stock N900VVRUEOF1 firmware that this is based on has gotten a lot of bad feedback from what I've found. I'm currently on 5.1.1 running in the stock slot and reception and battery life are...

For what its worth I was able to dirty flash 5.1.1 over 5.0.1 (no MultiSystem) and everything is ok. The only thing I had to do was clear data on the weather widget since it's a different version than what I had originally. I should add it does feel quite a bit faster that 5.0.1 ... not sure...

FYI, the MD5 sum is incorrect in the downloads list of the announcement post for 5.1.1 ... it's correct in androidfilehost http://i.imgur.com/vu6KHpm.png

I should add, in case it isn't perfectly clear for everyone, the factory reset done performed in the final step DOES wipe your virtual SD card. I didn't think it would and of course lost everything. Shame on me for not backing it up first. The good news is the ROM has been running great. :)

Two things I've been looking for that I can't seem to find, just wanted to see if I'm blind, or they just don't exist. 1. Is there anyway to change the grid with the included TW launcher ... like to 5x5 instead of 4x4? 2. Is there anyway to change the animation when you're switching between...

correct ... I'm running v2 with NC2 and it works just fine.

Sweet! I'm a huge fan of the 1.x series! hsbadr, have you noticed much of a difference running the NC4 kernel with this? I don't mind upgrading since 1.x has been a daily driver for a long time. (KILLER battery life with working deep sleep)

One is themed and one is a port. I suggest reading the first post, it's all in there.

1.8 from this thread ... it does deep sleep and has the S5 look.

I'm still on the 1.x version of this rom and it deep sleeps just fine ... killer battery life.

Here's my current 2.0 setup ... this rom rocks!

I have the same thing ... the good news is it only shows up in a few apps ... XDA being one that comes to mind. On another note I discovered a newer version of "Watch On" in the Galaxy Essentials somewhat hidden app, it seems to have better functionality then the one cooked into the ROM. This...

Yeah, that works, I guess i'm just used to it either being the left most screen, or a swipe up from the bottom. For now I'll just use an app shortcut till I come up with something better (xposed or gravity box hack perhaps)

So 2.0 is completely amazing so far ... one thing I'm wondering is how you guys are launching Google Now with the included launcher? It's not in the recent apps screen like it normally is.

I JUST finished getting 1.3.2 all setup perfectly ... I'll live with it if there's no way to hack the settings.db file (should be a way though) ---------- Post added at 01:52 AM ---------- Previous post was at 01:24 AM ---------- Ok, I was FINALLY able to fix it by editing...

Somewhat related to this, I somehow ended up with an extra set of the "extra" 4 toggle icons: I'm pretty sure I know what table that needs to be edited in settings.db, but I'm having a hard time making the change. (my sql command skills aren't the best) Is there a toggles revert zip...

Ah, that I can do. :)

hmmmm, not seeing WallpaperChooser in TitaniumBackup in the list of apps.

I see the same thing. Looks like Notifications and Ringer Volume are linked.

I'll give that a shot. I'm on 1.1.1 debloated in the stock slot, with the updated S5 launcher you posted if it helps.

I'm on the stock slot as well (forgot to mention that)

I'm actually on the hsbadr firmware (hybrid nc2/nc4 from the OP)

That totally makes sense... in this case I'm not running any. (I'm sure Samsung has their own something going on though)

I have this one loaded now, will report back tomorrow on results. :)

Which app? Maybe I can try an app to see if the behavior is any better.

I wish it was the tequila ;) It just seems to be some kind of wake from deep sleep issue ... I'm on 1.1.1 debloated at the moment. When 1.2 drops maybe I'll try the full and slowly clean it up until I find the culprit.

I have a new one for you guys, haven't seen it mentioned before. For some odd reason my alarms aren't going off in the morning. It seems like the process can't "wake" the phone out of the deep sleep that it's in. If I hit the power switch it will suddenly wake up and then try to fire the...

Nice!!!!