Search results

Yes. Just make sure you are patching the boot.img for the version you will be using. If you upgrade to the November patch, make sure you patch the November boot.img and flash that after updating.

I have not done it but according to the instructions, you can restore the stock boot.img via magisk. Alternatively, you can always download the factory image from and extract the boot.img from there. I would think you already have a copy of the stock boot.img on your device and/or PC. Didn't...

Ah, yeah. Custom ROMs will be a whole other beast! I prefer keeping stock these days but rooting for AdAway and Titanium. But surely you will be able to flash updates of custom ROMs a lot easier than this.

Thanks for this by the way. I will try taking the official ota next time. I just assumed it wasn't possible as taking ota when rooted has always been a no-no and seemed counterintuitive. So I always just sideload the ota after flashing the stock boot.img. After thinking about it though, it makes...

It won't really change anything as far as I know. You'll still want to update using the same methods. You won't be able to take an ota update with TWRP installed as TWRP resides in the boot partition. You will still need to return to the stock boot.img before updating and then add TWRP and root.

You can still use an ota image after previously using a factory image. If you updated this time by flashing the full factory images that's fine. You will still be able to sideload the ota image next time.

I can't confirm 100% but as far as I know it should. Doesn't viper have an option to back up your settings just to be safe? The thing about using the ota image is that it's not like flashing a factory image. It's just like taking an ota update. It shouldn't affect your apps or app data.

Here's what I do when I update. 1.) fastboot flash the stock boot.img for your build. 2.) Download the factory image and the ota image for the version you are updating to. 3.) Extract the boot.img from the factory image package and patch via magisk. Then copy the patched boot.img to your PC...

Haha, yeah, might just be the way it's displaying on my phone. They don't look that different. A couple things to maybe try. Maybe try repatching the boot.img. perhaps something went wrong in the patching method? Also, you double-checked that you downloaded the factory image/boot.img that...

slaydog That's where I downloaded mine from (the link you posted). This is what it looks like. Sorry, not on PC at the moment but downloaded on my phone to see the file structure.

Are you guys using the platform tools that you download directly from the factory images page? I only ask because previously I was using a smaller package (just adb/fastboot) even though it was the latest version and I had issues flashing the factory images. After I downloaded the platform tools...

Ahhhhh, so happy right now! Donation incoming. Thanks topjohnwu

I still don't understand why people interested in unlocking the bootloader and/or rooting buy the Verizon version. Just get the unlocked. You know Verizon is gonna lock you out at every step. Not intending to sound rude. I'm genuinely curious. Is it because you get a carrier subsidized...

Just curious if anyone tried to fastboot boot the modified boot.img instead of fastboot flash. I was thinking about the original Pixel XL and how this was the case, though I'm unsure about with magisk. I've never used it, I used SuperSU. But with chainfire retiring, might be time to check out...

I don't believe it will. A factory reset just wipes user data, it doesn't touch the system partition. Only way to undo changes to the system is to restore a backup of the system via TWRP or flash factory images. You can flash the factory images without wiping data though. Edit the...

I think they will still honor warranty for hardware issues. Just because you are rooted and the hardware fails, doesn't make it your fault. About the only way you could permanently brick one of these devices is with a bad bootloader flash. Even then, there are two bootloaders and it may even be...

It's definitely not my favorite looking phone but it's not horrible. And if you are planning on putting a case on the phone, it doesn't really matter anyway.

Yes it is very easy. You just have to install the tools on your computer and download the firmware. Then you run a script and it will install the firmware. All information can be found here: https://developers.google.com/android/images Every release gets posted per device, and they also offer...

Yes you will still have warranty. Just to confirm that this is true with the Pixel 2, I just had a chat with a Google Rep before replying to your question. He confirmed that unless you permanently brick the device (which is nearly impossible), rooting is no problem and will not affect the...

Alyssa clearly stated in that chat that the Verizon version will not be unlocked. She said: "That it will, unless you buy the Verizon version." But as others have said, why even risk it at all? If you want root, buy the unlocked version. Verizon will lock it down like they always do. You...

If I get the Pixel 2 XL I'm going with this case: https://www.spigen.com/collections/google-pixel-2/products/google-pixel-2-xl-case-rugged-armor Have it for my first gen XL and really like it as far as cases go. Adds minimal bulk and has corner protection. Not too bad looking either.

Thanks! Got stuck in a bootloop after flashing the May update. Came here to see if anything had changed and you answered my question before I asked it. :)

Just curious... Were you restoring an RC1 backup with RC2? Or did you make a new backup with RC2 and it wouldn't restore?

fastboot flash boot_a boot.img fastboot flash boot_b boot.img

Thanks. That is what I'm using too. No, I've not heard of this yet. Thank you for pointing it out. I will give it a try. Glad you got it! I am going to try this. I'll update whether or not it works for me too. Edit: Yep, deleting fstab.marlin worked for me too. Last time I did this I used...

Well, at least I know it works now, so I just need to figure out why I'm having trouble. Which TWRP build are you using?

Anyone having trouble rooting NMF26Q? I can do everything but after installing the SuperSU zip via TWRP the app or the binary aren't there. This is the first time I've had any issues rooting this device and I can't figure out why it isn't working. I tried the whole process twice and no luck.

Just having an unlocked bootloader breaks Android Pay on the Pixel. Root or no root.

I haven't seen this mentioned yet, but the stock recovery has an option to mount system. I'm not the smartest with these things, so does anyone have any thoughts on this? Could this be a workaround for needing TWRP to mount system? Any other implications for this? Also, with the current root...

I've ran many custom roms, but I'm not on my Nexus 6. I like the stock rom. I'm happy with just root and custom recovery on my stock setup. Device runs great and I get great battery life. I can use the root apps I want and that's enough for me.

I just got the update today!! Woo!

No, not currently. I don't know if Wugfresh is planning on supporting it at some point or not, but to be fair, the Pixel C isn't a Nexus. And from what I've read about it, until it boots up to Android, it's pretty much a Chromebook/ChromeOS in every way, so I'd imagine it wouldn't be a simple...

Nope, MMB29X hasn't even been added yet. I was just in the NRT checking to see if that update was available and then I saw on the Nexus factory images page that there's already another update.

I believe the force flash mode flashes the stock images individually as opposed to relying on the flash-all.bat script as it notoriously has issues flashing the stock images. I'm pretty sure it's recommended to use force flash mode every time you are flashing factory images using the Return to...

Oh, okay. I wasn't familiar with that error as I normally just do everything manually but I can't keep track of which files I need these days as things are changing too much so I decided to use this, which was nice! My bootloader was already unlocked so I can't comment on that portion of the...

Just used 2.14 to upgrade to the latest factory image and root with the no force encrypt option checked. I didn't see any errors/bugs and my device remains unencrypted.

DU v9.2; 5.0.2 is there a way to separate ringtone and notification volumes? I have my ringer set to the lowest volume but my notifications are playing at full volume or a higher volume. I couldn't find anywhere in the settings to separate them so I can get them to the same level. Any ideas?

Thanks for this, Josh. Finally found some time to start from scratch and flashed this today with the latest pa stock gapps. All is good so far. Happy to be back on DU again!!

Yay!!!! Thank you so much!!

So this really includes custom recovery, or is that a feature to come when custom recovery is available? Edit, nevermind. I overlooked it in the op, but it's as I thought. No custom recovery yet. :(

That's just because of the latest chrome update. I had to restore the previous version from titanium backup to resolve the issue. If you can't get a hold of it, send me a pm and I'll give you the apk. ---------- Post added at 07:33 PM ---------- Previous post was at 07:32 PM ---------- Brace...

Is anyone else having charging issues? I'm having legitimate charging issues to the point where I've only been able to get a full charge once. The full charge may have been prior to root (I'll have to experiment more) but let's face it... This is a nexus. The majority of users are rooters and I...

Republique is a pretty impressive game and it's optimized for tegra.

Have you updated adb to release 21? Your lollipop device requires the latest version if you haven't already done that.

I think regarding HTC, it depends on what's affected. I don't think that they will deny you a hardware warranty just because you unlocked the bootloader and/or rooted. Unlocking the bootloader is a safe process sanctioned by HTC themselves. Well, on HTC devices anyway. Nexus won't require HTCdev...

You should just unlock the bootloader out of the box anyway. Will save you much headache down the road when you decide to do it and already have a bunch of data on your device.

Yes, I did, actually. The odd thing is I've been using the same setup for nearly a year. I might try the factory images when I have some time and start from scratch. Maybe I have some underlying issue that the images will take care of.

It's good to know it's working for you. Thank you for the info! Unfortunately I don't think Poweramp is the issue as I've been using it for nearly a year on du with viper mod. I think the issue runs deeper. :(

Not particularly, it's just what I'm familiar with. I suppose I could check out DSP manager. The settings look a bit different in there so I'll have to play around a bit to get it all figured out. Honestly, I never really considered DSP manager because I was already using viper and it worked...

Before I get started, let me say that I know this is in no way a rom issue, but I'd like to ask my fellow DU'ers a question. Is anyone having issues with the viper4android sound mod on the latest stable? I've been using the mod since n5 release, and on DU for nearly all of that time. For some...