yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy S7 Questions & Answers] TH3B0SS:
I didn't find out about xposed like 3 weeks after rooting so that coudnt be the issue
[T-Mobile Samsung Galaxy S7 Questions & Answers] officialbambam:
I'm almost 100% sure it's the xposed module you've installed that's causing the boot loops. If I were you, I'd uninstall the xposed module and return to stock and reroot without xposed and I'm certain that's the solution to your problem.
[T-Mobile Samsung Galaxy S7 Questions & Answers] TH3B0SS:
Well like I said during the time I was rooted I didn't install xposed but I'll give it run today when I get home
[T-Mobile Samsung Galaxy S7 Questions & Answers] TH3B0SS:
I can now confirm that it was not the xposed module I'm rooted now for like 2 to 1 mouth with xposed installed
[Moto G 2015 Q&A, Help & Troubleshooting] dcalf9415:
I'm having trouble finding a stock ROM marshmallow ROM for osprey 1540. If someone could point me to a TWRP flashable zip that would be awesome!
[Moto G 2015 Q&A, Help & Troubleshooting] MrTooPhone:
A Stock 6.0.1 ROM for OSPREY 1540 2gb does not currently exist. Some have installed this 6.01 stock ROM successfully. But I do not know if it still works with 1540 since VoLte was added.
[G3 Q&A, Help & Troubleshooting] CesarRaimon:
So I recently bought the Korean LG G3 (F400) and the first thing I did was rooting it, which was a breeze. Of course to root it I needed to install the LG Mobile Drivers, which I did and were working completely fine. Then I decided to take a little risk and attempt to flash CWM recovery (I did not know that I need to unlock the bootloader first or BUMP! the device) and well, flashed it the same way I flash stuff on my previous Samsung phones.

So now, when I try to boot the phone, I get the LG Logo and goes through with the boot animation, but after a little less than a second the boot animation fails and I get a black screen + the LED flashing blue and green and the phone remains like that. I tried factory reset but after I click yes it shows the LG logo then goes into a black screen (without the boot animation) + LED flashing blue and red.

So I tried finally going into download mode and attempting to return it to stock via LG Flash Tools, and like I said before the drivers were installed, but when I connect the phone to the PC it gives the message "Drivers were not successfully installed" and the LG Flash Tools fails to detect the phone. I checked within Device Manager and it says the LGE MTP device "cannot start".

So I'm pretty much stuck with a phone that doesn't boot, can't flash anything via adb or flash tools and no recovery installed. Can anyone suggest anything I can do to get this beast back up?
[G3 Q&A, Help & Troubleshooting] zround:
Try using this method http://xdaforums.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
[Nexus Player Q&A, Help & Troubleshooting] abced123:
I am making this poll becuz I feel like MM is better for the device. I currently have it on 7.0 , and it crashes quite often or requires reboot once a week . Device is used daily for Kodi, youtube and casting .
[Nexus Player Q&A, Help & Troubleshooting] fazbender:
I was rooted on previous versions, tried the earlier roms but returned to leanback/factory as it was easier to use for the rest of the technophobes round here. Much to my surprise after flashing 7.1.1 my lexar 64 GB sd card is plug and play. ( was prompted to format and use on first plug in ) I needed root on MM for SD before. I use Kodi / Netflix a lot and have had zero issues. I also cast spotify regularly and have had a couple unexplained disconnects but overall good results. I have also recently discovered holding the enter button ( big circle center button ) when in kodi on a media file will bring up the context menu . (jarvis 16.1) .
[Nexus Player Q&A, Help & Troubleshooting] killall:
On the latest firmware myself, Kodi crashes after 5 mins or so, really annoying. Came here hoping for a fix.
[Nexus Player Q&A, Help & Troubleshooting] BraianV:
Does anyone found something New on 7.1.1?
[General Questions and Answers] papasmurf357:
I'll try to make this as brief as possible. My phone won't boot up properly! Black screen happens with the LED light flashing blue. I might of bricked it? Last thing i remember was trying to install Hypermax v9 in my phone! I can however access Download mode but not recovery mode. Please help! Thanks in advance
[Google Pixel Questions & Answers] spook2022:
I have a rooted, bootloader unlocked Pixel from Google Play. I am currently on 7.1 (NDE63V) November 5th security patch. I have stock recovery and would like to keep it that way if possible.

Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader? I used adb and boot-to-root for my current root method if it matters.

Many thanks in advance for any assistance. If a thread with the requested info already exists, please feel free to just post a link to it.
[Google Pixel Questions & Answers] quangtran1:
You will lose root, but you can re-root easily enough. Bootloader doesn't relock on its own. Plus, you have the Google Store version, so it's easy to unlock BL anyway. To me, the cleanest and easiest method is to use the flash-all method, with the -w switch removed. Download the 7.1.1 image from the Google developers site and go at it. You can search for 'flash-all google pixel' here or on the web in general to get directions. It's easy as pie.
[Google Pixel Questions & Answers] lightmastertech:
I've got an unlocked Verizon Pixel running the non Verizon stock ROM (I know the bootloader won't relock itself with the non-Verizon ROM, right?). what if you are using a computer that can't use the ./flash-all.sh script? My only 2 computers are a Chromebook (1GB RAM) and a Raspberry Pi 3 (again, 1GB RAM). The flash-all script always gives an error saying it can't allocate enough memory, and with my old Nexus 6P, before I started using Custom ROMs, I'd just extract the image zip and manually flash the .img files inside it. With the Pixel however, there are a lot of img files (aboot.img, apdp.img, etc) and I'm not sure if I should try flashing these or not. I've read a couple less than reliable guides out there that basically said to just flash the same .img files as the Nexus 6P used, but I feel that those other ones are probably their for a reason and might need to be flashed too.

Also, should I flash both _a and _b partitions when updating, or just whichever is active? Seems that there is an _a and _b for almost every single partition on it.
[Google Pixel Questions & Answers] quangtran1:
I have a ChromeBook but I've never used it to fastboot my phones. Sorry but I'll refrain from giving instructions on something with which I'm not familiar. I can say that the bootloader won't relock by itself. And the boot.img image should be all you need. Those points are universal. Also, you can just flash the 7.1.1 OTA, which is only 260mb.
[Google Pixel Questions & Answers] lightmastertech:
If it rooted, and has modified system, doesn't the OTA update method fail?

And I actually use the Raspberry Pi for fastboot. Easier than trying to get my Chromebook's chroot to talk to talk to my phone's bootloader.
[Google Pixel Questions & Answers] njeri123:
Hi

Whats about Flashfire? Can i download the Factory Image, deselect Boot and Recovery in Flashfire and flash it?

After this, can i flash the the SuperSU.zip with TWRP?
[Google Pixel Questions & Answers] bobby janow:
Have you any idea how many threads there are regarding this? How many duplicate posts and the same question about 2 dozen times all in separate threads? And now we have another? Even if you can't search XDA for some unknown reason, here you go.

https://www.google.com/search?q=root+on+unlocked+pixel+7.1.1&ie=utf-8&oe=utf-8

Search terms from your OP ... root. on unlocked pixel 7.1.1

Can we please put an end to this question already?
[Google Pixel Questions & Answers] spook2022:
I went back and read my post again just to make sure I wasn't crazy, and sure enough I couldn't find where I asked how to root 7.1.1...

I did however ask "Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader?" So, posting a Google search on how to root 7.1.1 isn't exactly the help I was after. Regardless of your disgruntled, condescending reply to the whole matter, I did manage to achieve the end result I was originally after.
[Google Pixel Questions & Answers] kyle4269:
As far as I know you can not update without losing root.. You can however update without losing data and reroot just like you did the first time.
[Google Pixel Questions & Answers] bobby janow:
[MENTION=3434691]spook2022[/MENTION] It's just so frustrating to see the same question over and over. It wasn't that condescending, but yes, it was disgruntled. I just like to search for these things myself because I learn a lot along the way. Might take me an hour or so for the answer but then I learned an hours worth of stuff. I do agree though that there should be a sticky like the Heisenberg thread in the n5x forum that gives step by step for everything. One thing I will say that perhaps a few people don't know is that the Pixel and the XL are basically the same regarding root, unlocking and updating. So if you don't find the answers here you might want to head over to that forum. There seems to be a dearth of information here.

Someone suggested that the forums be combined with separate sections for things specific to each device like battery life and display as well as Verizon vs Google brand differences. I originally thought not but I'm changing my mind. Nonetheless, take the frustration from whence it came. I'm sorry I insulted you, that was not my intention. If you found a link to your solution perhaps you can post it for others. There is bound to be a similar question within a day. (oh oh there I go again..)

edit: This is what I was talking about regarding the Pixel vs the XL forums. Anything by Chainfire regarding root is a must read if you are rooted and even if you are not as I am. http://xdaforums.com/pixel-xl/development/root-supersu-t3490156
[Google Pixel Questions & Answers] Konfuzion:
Download the 7.1.1 NMF260 image from Google.

Extract the zip file into the adb folder on the PC.

Edit the flash-all.bat file to remove the -w switch so user data won't be deleted. You'll find this -w switch easily enough.

Put your Pixel into fastboot mode, using either power+volume down or via adb command.

Plug phone to PC if not already done so. Execute the flash-all batch file.

When that's done, you have 7.1.1 on your phone, along with new radio and new kernel. (actually, I'm not sure if Google even put out a new kernel.)

Then you can go back to re-root with whatever method you used previously.
[Google Pixel Questions & Answers] bobby janow:
Why not the OTA coming from 7.1? Stock recovery according to the OP. Why go thru all the hassle unless you want a dirty flash? I know you say reroot after the install. I haven't been rooted in a few months now but I always used to unroot first for some reason before flashing a new image whether it be full image as you describe or an OTA. I'm sure it's not needed at this point, I was always leery of a bootloop. But with an unlocked bl it probably wouldn't matter since you could always recover if needed.
[Google Pixel Questions & Answers] spook2022:
Thank you so much.
[Google Pixel Questions & Answers] lightmastertech:
That right there is why I always unlock my bootloader's and hack Verizon's phones to have unlocked bootloaders. Always great to have the assurance that you can easily fix it if something ever breaks.

Sorry if that's a little off topic.
[Google Pixel Questions & Answers] kyle4269:
He's on 7.1.0...63V..he can't apply the latest ota to 63V..he would have to apply each ota in order of their release.
[Google Pixel Questions & Answers] bobby janow:
I don't believe that to be correct. I think the 7.1.1 is cumulative. I'll double check though and edit later.

edit: You can go directly to the latest without incremental OTA flashes. Just sideload the OTA from recovery. Easy, peasy.

---------- Post added at 03:50 PM ---------- Previous post was at 03:22 PM ----------

I always, always unlocked first thing I did. I even unlocked the unlockable S4 before the VZW firmware update. But lately I've been running locked. I have a banking app that will not run without passing SafetyNet. I know there are a couple of kernels that will bypass that check but I believe they will close that too eventually. The only thing I miss at this point is what you describe above. But the Pixel even from vzw, which I now have with the O update and therefore totally locked for now, is not full of bloat and runs rather well. So although I do root around these threads (no pun intended) it's merely for entertainment now and general knowledge.
[Google Pixel Questions & Answers] kyle4269:
That makes it so much easier then.. Download the latest ota zip from https://developers.google.com/android/ota then you need to flash the 63V boot. Reboot to recovery. Follow the directions on the Google ota site to sideload the ota. Reboot back to Bootloader and flash the twrp boot image to boot.. Reboot to recovery. Install the supersu zip and reboot.. All rooted and to the latest build.
[Google Pixel Questions & Answers] lightmastertech:
Luckily I'm with USAA and they are too slow with adopting new technology, just got chip debit cards 2 months ago, and they'd till don't have Android Pay, lol. If they did start using SafetyNet, I'd use the kernel patch in a heartbeat. It'll be a long time before Google fixes that since there's still a lot of devices that can't use verified boot, and Google doesn't want to become the new Apple, abandoning old device just to suit them.

Wife got the Verizon version of the Pixel as an early Xmas present from my parents, and I wouldn't let the Verizon sales person activate it for fear of getting 7.1.1 before I could unlock bootloader. Wouldn't let wife turn it on for a couple hours till I had the bootloader unlocked and had flashed Google's version of Android to keep Verizon from screwing with it. Viper4Android and all the awesome rooted featured are too good to give up. She'll be really happy when Xposed or custom ROMs start coming out for it cuz even the little features are great, like holding power button with screen off to turn on flashlight. (She's been stuck with locked phones for a while while I've had my Nexus 6P and is glad to finally get a rootable phone).
[Google Pixel Questions & Answers] bobby janow:
Yep, that's about it. Personally I'd reboot right after the OTA flash then go back to bl and do the root process. Probably not needed though.
[Google Pixel Questions & Answers] lightmastertech:
How is that better or different than flashing the full image by using fastboot to flash bootloader and radio (if updated), then using

fastboot update <image>.zip

and leave off the -w to keep it from wiping.

Also, correct me if I'm wrong, but doesn't OTA updates fail if you've modified the system partition, like installing Viper4Android or other mods? I know that flashing the whole system image works no matter what which is why I use that method.
[Google Pixel Questions & Answers] bobby janow:
Believe me I went back and forth multiple times trying to decide. I eventually went with the secure model since I do have my banking app and passwords on the device. Besides that I read a bunch of stuff from Chainfire and he is now if the ilk that if you are doing those things, AP included, why the heck would you compromise that by unlocking and unrooting. So I locked my 5x a month or so ago and really found no downside other than crack flashing kernels and roms. I miss V4A but I got a really good pair of headphones and the sounds is more than acceptable.

That being said, if JCase and company came out with a new depixel8 for the V brand I'd be once again tempted to unlock for no other reason than I could. If I could relock only. I still use my 5x so if I needed a fix I could unlock that once again without a problem. Now if I could unlock my iPhone 6 ...

---------- Post added at 08:20 AM ---------- Previous post was at 08:17 AM ----------

Yes, that is a good point. I do believe that the OTA is less intrusive and only updates that which is needed rather than the whole shebang. Size is smaller too and can be done on a locked bootloader, which obviously is not the issue here. As for flashing the OTA manually I'm not sure about what it does to system mods or if it will load at all. I don't see why it would fail though since the system is being overwritten to some degree and root is being wiped out.
[Google Pixel Questions & Answers] lightmastertech:
I make up for the lowered security by requiring PIN to boot my phone, which (to the best of my knowledge) changes the encryption key and requires my pin to unlock it or access through TWRP even. Someone could still erase my phone, but they won't do my data.

Next update Google releases, I'll try the OTA to see if it does work with modified system, or if it fails.
[Google Pixel Questions & Answers] bobby janow:
I don't believe that to be entirely true. With an unlocked bootloader can't they just boot into bl menu, flash a custom recovery and extract your data via adb? There are ways to bypass the encryption keys as well. With a locked bootloader they can't do that since to do anything would require a full wipe. Not 100% sure on this one but pretty sure.
[Google Pixel Questions & Answers] lightmastertech:
Custom recovery requires my PIN/pattern/password to decrypt instead of using a default decryption key. AFAIK there's no way to bypass this. There was a big issue when Google first started enforcing encryption because TWRP couldn't handle non-default encryption keys.
[Google Pixel Questions & Answers] bobby janow:
https://securityaffairs.co/wordpress/48933/hacking/android-full-disk-encryption.html

Can't you get into bootloader menu with a startup pin? They can't install a custom recovery but they can adb the contents of the sdcard and then brute force the encryption key, right? I'll link you to a great discussion over on the 5x forum. See what you think.

http://xdaforums.com/nexus-5x/help/question-unlocking-bootloader-password-t3391493
[Google Pixel Questions & Answers] robocuff:
adb doesn't work when the device is booted to the bootloader. It only works if the device is booted into the OS and then only if USB debugging is enabled. If you boot the phone to the point of the lockscreen, adb won't work then either. You need to enter your pin, password or pattern at least once before you can use adb and for your data to be available.
[Google Pixel Questions & Answers] lightmastertech:
[MENTION=2659927]bobby janow[/MENTION] What [MENTION=4185912]robocuff[/MENTION] said. As long as you have no accessibility services enabled and have it set to lock until you enter your password, there is no way to have access to adb without knowing the password. Fastboot, AFAIK, does not allow you to pull data from the phone. SD card is locked and encrypted after boot till you put in password, so no access from USB to computer. Short of an exploit (which would also work with a locked bootloader), there's still no way into the phone without the password. Yes, you could eventually brute force the code if you have physical access, but incorrect passwords increase time between attempts and make it infeasible. Even wiping phone requires you to enter previous email and password when you try to set it up again.

Only real benefit of a locked bootloader is preventing someone from customizing the software, which is why Verizon does it.
[Google Pixel Questions & Answers] bobby janow:
Ok let's say someone gets your phone and it's unlocked. They boot to bootloader and want to install a recovery. Password (pin) required. How many guesses would it take? If they do 10,000 attempts they will get it and then your system is compromised. There is no wipe function as far as I know after X attempts. With a locked bootloader even if they guess the password they can't flash a custom recovery and access your data. I do not believe that customization is the reason Verizon locks the bootloader. They do it so they can tell banks that the Verizon Pixel is secure and corporate customers can use it without fear of their data being compromised.

https://www.reddit.com/r/GooglePixel/comments/5af4av/rooting_the_google_pixel_is_it_for_you/
[Google Pixel Questions & Answers] lightmastertech:
True, if your pin is only 4 digits long. PINs and passwords can be up to 17 digits and the pattern.... honestly don't know how to figure out the amount of entropy in a password like that, lol. Still probably a lot. 17 digits PIN means 100,000,000,000,000,000 possible combinations having to guess by hand without using a computer to speed it up, plus the higher you get guessing, the slower you will guess, having to make sure you don't lose your place and more digits to type. If you could guess at 2 seconds per guess without slowing, that's 6,341,950,000 years! Passwords with upper and lower case, numbers, and symbols, up to 17 digits, even more impossibility long to guess.

Point being, assuming you've taken reasonable security measure and used a decent PIN or password, no one is likely to guess your password within even your great-great-great grandkids lifetime. If you're the world's least lucky guy they might guess it first try, tho, lol.

Considering the possible lengths of passwords and forcing you do it without the aid of any computer or supercomputer, short of some currently unknown exploit or bug, I don't see any way that a locked bootloader is more secure than an unlocked one. I'd love to be proved wrong in this so Google could find out and fix whatever possible method of data breach is used, but it seems pretty air tight to me.

If that was all Big Red cared about, a locked bootloader with the option to unlock (and force wipe) would be sufficient, just like what Google does. Although with forced encryption on devices, I think Google does that more so that you can only mess with a phone if you know what you're doing. Some random soccer mom who has never heard the term kernel can't accidentally grant root access to some malware and make Google look bad.
[LeEco Le Pro3 Questions & Answers] TeeDiddyDizzle:
Does the lack of certain lte bands noticeably affect day to day use? I bought a x720 model before realizing the differences. If it does matter, is there anything I can do to fix it? Thanks.
[LeEco Le Pro3 Questions & Answers] zmanfarlee:
what carrier?
[LeEco Le Pro3 Questions & Answers] TeeDiddyDizzle:
Sorry I forgot to mention I'm using T-Mobile.
[LeEco Le Pro3 Questions & Answers] zmanfarlee:
If I am not mistaken the only band you are missing is 12 which should not matter much for the life of this phone unless I am mistaken. Look up if Tmobile uses 12 in your area.

I only have band 4 on my oneplus I think and it doesn't matter in Tampa.... other places it does.

So unless I ma mistaken this only affects futureproofing. Confirm you are only missing band 12 though.
[LeEco Le Pro3 Questions & Answers] TeeDiddyDizzle:
Yeah it seems for tmobile the only missing band is band 12. I'm in California and it doesn't make too big a difference at all so I hope I can deal with it.