yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 4 Q&A, Help & Troubleshooting] nr-thunder:
Short Answer: The Note 4 won't be beaten by new phones. Only if you are willing to sacrifice 2 features. The pen, and the removable battery. But for the next 2 to 3 years, it will stand alone on the throne.

Swapped the battery in the beginning of the year, because it died down with some shutdowns after 2 years of usage. No Shutdown since then, I have low SOT but still got 3 days instead of 2 before (910F). Just imagine having a phone with a fixed battery, you would either have to live unhappy with it or buy a new phone. The display is absolutely fine, no AMOLED aging problems yet.

It got a fine camera, 4k video, QHD Display, fast processing power and UI, good battery life, and a pen. That's so far stuff the note 4 has, and isn't worse than recent phones in a considerable amount in any of the things it does.

I crave for an even bigger display (something like 6 - 6,4 inch with 16:9), dual sim (with the bands I need), small bezels, and durable design on the edges (no bent display). I mean man, i dropped the note 4 so many times. The metal frame got damaged like it should, and the display hasn't broken yet.

Future Galaxy Notes won't get bigger in my opinion (Samsung using 2:1 ratio, only good for movies), and even after the note 7 disaster, removable batteries are going to be even less common (like no flagship phones have them anymore).

My only hope are smaller asian companies. But even Xiaomi (who are not small in any way, but they show to have the guts and put money into development of innovative phones like the Mi Mix), won't introduce an integrated pen and removable battery design just like that. Who knows, maybe in 5 years it may be different. When phones are just a display at the front, and you have to be different because they all have become the same concerning the design (lg g6 = s8 design, or like all the sharp aquos and the mi mix).

By the way, I use the dr. Ketan rom. Main Reason: With UC Browser (you can use a custom background, like a black picture. Bugless black browsing experience), and the official samsung theme manager, I got a close to complete black UI.
[Galaxy Note 4 Q&A, Help & Troubleshooting] triplex76:
on s8 you can set the navigation bar to be static and black and you will get the same as hardware buttons with the plus of the force touch home button.

nobody used to the hardware button will get any difference in using them.

to understand what i'm saying just give a look at the antutu benchmark ... you will see the black bar.just imagine the black bar with buttons.no difference

you can adjust even the ratio to be 16/9 so...if you want you can get advantages from the infinity display otherwise not
[Galaxy Note 4 Q&A, Help & Troubleshooting] Vybramo:
Still its amoled. After half year of using u will have different collors on display on Button spot. But i dont understand why samsung use just only 4gb of ram on latest CPU ... Most of application eat around 700mb and 8gb will be nice to have on flagship.

I using my note 4 as navigation but s8 rly sux with screen ratio + edges for it.

I thinking about upgrade to oneplus 3t but night shots its imported for me alot + battery life where is samgung s7 edge for now best choice.
[Galaxy Note 4 Q&A, Help & Troubleshooting] DarkGuyver:
Even by current standards the Note 4 is still a very good device. Especially if you have the Exynos variant.
[Galaxy Note 4 Q&A, Help & Troubleshooting] SEVENEDGE:
If the Note 4 had the S7 Edge Camera, fingerprint scanner and Ip68 resistance, it would be Samsung King.
[LG V20 Questions & Answers] kilakoust:
I've searched far and wide for an answer to my problem and I've returned with nothing. It's been almost 24 hours without my phone and I think I'm losing it. I've downloaded and tried LGUP (alongside Uppercut), LG FlashTool 2014, LG Bridge, LG DLLs, etc and nothing has worked to flash my phone to stock with the KDZ. The closest I've gotten it to work is with LGUP but stupid me, I managed to edit the buildprop before it went self destruct and changed the device identifier to a Google Pixel XL and LGUP refuses to cooperate. Any help is appreciated. Please. :good: :confused: :( :( :( :( :( :(

I've managed to get into fastboot. I'm sure I can do something from here but idk what to put. Any help is appreciated once again

[IMG="LGUP"]https://gyazo.com/20db6e9b45e02b0b01277fe190eddd2f[/IMG]
[LG V20 Questions & Answers] Critical Detox:
My guess is that you're rooted considering you've edited the build.prop? Why not enter recovery and flash a stock rom?
[LG V20 Questions & Answers] Lumince:
Can you not get into TWRP?? I believe its the same way as everyone else..\

Hold the volume down button and the power button and as soon as you see the LG logo left go of the power button and press it again. This manual step is a pain in the arse, but it will get you there eventually. Since youre rooted, you also get the "This device is corrupted screen" yes? The LG logo popup you are looking for is right before that.

What I do for easy and fast access is this. I keep the back cover off and hold the volume down button for ease. I hold the power button, let go, and press it again and ususally that first try doesnt work. As soon as I see the corrupt screen I take the battery out very quickly and put it back in and repeat the process. After a few tries the LG logo will hang before the corrupt screen and that gives you the time you need to let go of the power button and then hold it again until the factory reset screen comes up. Just hit yes twice... It will go into TWRP.
[LG V20 Questions & Answers] cbissa18:
Wow a yeah later and this helped me. my superv20 mod took a poop for no reason at all and i couldn't boot or get into recovery for what ever reason but this key combo if done twice worked to get me into recovery.
[LG V20 Questions & Answers] Lumince:
I'm glad that this helped you out. Getting into recovery with root was always a pain.
[LG V20 Questions & Answers] cbissa18:
yeah not sure why, its like it doesnt stick smh. but it does you just have to toy with it....
[LG V20 Questions & Answers] Lumince:
Well with the corrupt screen, it seems that the time frame that would allow you into Recover/TWRP is shorted. So pulling the battery after trying usually gave me more than enough time to boot into it. Probably not the best for the phone though xD
[Remix OS for PC] Skyshadow101:
Hello! I have just installed Remix OS on my PC. I am trying everything I can to boot into the kernel line, so I can use the vga command, since the resolution of the screen is terrible. I can't figure it out though, and no websites seem to show how.

Anyone mind telling me how to boot it?

I am booting into Remix through a USB and not a Hard Disk.

Thanks! :)
[Remix OS for PC] mitchell4you:
When the boot options show... hit "tab" key

goodluck
[Remix OS for PC] Skyshadow101:
That doesn't work for me. When I press tab, nothing happens. All I can do is Boot a Selection, edit a selection, and boot the GRUB command line.

Please help!
[Remix OS for PC] Skyshadow101:
Anyone...please?
[Google Pixel XL Questions & Answers] LoliSmith:
I want to update everything except leave the bootloader on 7.1. Will this work?
[Google Pixel XL Questions & Answers] 5.1:
Why would you leave the 7.1 bootloader? As long as you're unlocked, you can flash the whole factory image...

Cheers...
[Google Pixel XL Questions & Answers] LoliSmith:
Because Verizon. I want to be able to relock but not lose the ability to unlock again.
[Google Pixel XL Questions & Answers] aholeinthewor1d:
You should do some reading. It doesn't work like that. If you ever lock your bootloader you will never be able to unlock it again. No reason to lock it anyways.
[Google Pixel XL Questions & Answers] LoliSmith:
I don't think you are correct. If you leave the bootloader on 7.1, you should be able to unlock it again using depixel8.

Where has anyone done what I am proposing to do - upgrade everything but the bootloader to 7.1.1 and leave the bootloader on 7.1? No one has done it. So no one knows.
[Google Pixel XL Questions & Answers] humdrum2009:
im pretty sure you have to manually relock the bootloader,so updating to 7.1.1 shouldn't matter.

They cant relock your bootloader through software is what i was told by depilxel 8 developer.

I am updating to 7.1.1 right now just to get back to factory state need google support.

cant be reached on most custom roms.

No current stock rooted roms exist,so fresh start is needed.
[Google Pixel XL Questions & Answers] bobby janow:
As soon as you update to 7.1.1 and you are locked, you will not be able to unlock again with depixel8. I don't care if you have a bootloader from 2 years ago. You probably should decide once and for all if you want the device secure and locked or unlocked. Otherwise at some point you will be in a pickle.
[Google Pixel XL Questions & Answers] spotmark:
There's always a way to find out. Let us know how it goes. :p
[Google Pixel XL Questions & Answers] toknitup420:
You should not be locking you're bootloader if it's not necessary. And depixel8 pushes stuff to system in order to enable allow oem unlocking. These things may not work on newer systems regardless of the bootloader version.
[Google Pixel XL Questions & Answers] aholeinthewor1d:
Your OP implies you can update everything else except the bootloader leaving you free to lock and unlock whenever you want which is 100% not true. There are new threads about this every week all the info is there. If you are on 7.1 you can unlock with dePixel8. Yea technically you could relock and unlock again ONLY while on 7.1 but there is 0 reason to. If you aren't 100% stock when locking you are going to have issues. Also if you're phone installs an OTA while you have the bootloader locked then you are 100% screwed and won't be able to unlock again. Either unlock it and never lock it again or don't bother. You're making something very simple overly complicated.
[Google Pixel XL Questions & Answers] LoliSmith:
Has anyone done this without updating the bootloader or are you just speculating?

What are you basing this on? Has anyone every updated everything except the bootloader and then relocked or are you just speculating?
[Google Pixel XL Questions & Answers] LoliSmith:
So people have done this before? Updated everything but the bootloader and then relocked? Or are you just speculating?

I never take OTAs so that isn't an issue for me.
[Google Pixel XL Questions & Answers] aholeinthewor1d:
You can't.. it doesn't work like that. Go ahead and try if you want. There are countless threads about the bootloader. With all the knowledgeable​ people here do you think they somehow just overlooked something so simple? There are 5 bootloaders total actually. Once you install 7.1.1 you will not be able to unlock again. Multiple people have told you this but you seem to not believe anyone so go ahead and prove us wrong.
[Google Pixel XL Questions & Answers] LoliSmith:
So people have done this before? Updated everything but the bootloader and then relocked? Or are you just speculating?

It's a simple question. Either people have actually done this before, or you are just speculating.

But has anyone updated everything but left the bootloader on 7.1?
[Google Pixel XL Questions & Answers] LoliSmith:
Again, there is a difference between updating everything to 7.1.1 and updating everything except the bootloader. Huge difference.
[Google Pixel XL Questions & Answers] aholeinthewor1d:
Again. You can't.
[Google Pixel XL Questions & Answers] LoliSmith:
You've tried? Anyone else has tried?

So are you saying if I leave the bootloader on 7.1 and update everything else the phone won't work?
[Google Pixel XL Questions & Answers] aholeinthewor1d:
There is more than one bootloader which is what you are not understanding. There are 5. No one is certain exactly what 7.1.1 changed but if you flash any part of it (not just the bootloader) then you won't be able to unlock again.
[Google Pixel XL Questions & Answers] LoliSmith:
Why does that make a difference?

I am on the original bootloader, never updated anything.
[Google Pixel XL Questions & Answers] aholeinthewor1d:
Do it.
[Google Pixel XL Questions & Answers] LoliSmith:
I have asked you several times how you know this but you refuse to answer. You are just speculating.

Others have updated the bootloader, I haven't.

I am not asking for people to speculate. I am asking if anyone has done it.
[Google Pixel XL Questions & Answers] LoliSmith:
Again, do you know if anyone has done it or are you just speculating?

Also, is there a list with the identifiers for the various bootloader versions?
[Google Pixel XL Questions & Answers] spotmark:
It appears that nobody has tried it, so at this point, you're probably going to have to give it a shot and let us know how it goes.
[Google Pixel XL Questions & Answers] mac796:
You started 2 threads on the same question. These guys took time out of there day to answer you, they have no reason to lie to you. If you already know the answer to your question then why keep asking?
[Google Pixel XL Questions & Answers] LoliSmith:
Um, yeah in different forums, lol!! What is your point dude?

No one has answered my question at all. People are speculating.

WTF? Why are you bringing up lying? Ridiculous.

WTF AGAIN. Dude, move on. You aren't contributing anything here, you are just trolling.
[Google Pixel XL Questions & Answers] mac796:
No one is speculating, if you relock it successfully on 7.1 and you don't brick it. You have a 80 percent chance it is going to take the update on its own even with the automatic updates off. And it will never be unlocked again
[Google Pixel XL Questions & Answers] LoliSmith:
LOL!! You totally just made that number up. Stop. I am not some dumb ass who can't spot when people make things up.
[Google Pixel XL Questions & Answers] LoliSmith:
That's all that is happening here along with made up statistics. I asked for facts, if you don't have any (and you don't) don't bother answering.
[Google Pixel XL Questions & Answers] mac796:
Your correct number is made up far as I'm concerned it's going to be 100 percent. The facts are the people it has happened to in the threads. And the warnings from the dpixdl8 maker. There are tons of threads on this. And what you want to do even if it worked would be a huge inconvenience. All in the name of safety your going to Lock and relock your pixel. Who wants to go through wiping there phone all the time. You might as well keep it locked, or buy a Google version and not worry about it. I apologize for getting involved in this thread. Your right I should have stayed out
[Google Pixel XL Questions & Answers] LoliSmith:
Yep, if you don't have anything helpful to say, it is best to not post.
[Google Pixel XL Questions & Answers] bobby janow:
Lovely comment, that really added to the thread. Whether or not anyone here on XDA has done what you are trying to do, let's look at some empirical evidence. Don't you think that would have been well known by now? That is not speculation, that's a fact. So therefore you can assume that either someone tried it and failed or that no one was stupid enough to try knowing that either it would brick their $700 device or cause them great effort to recover. The developers of Depixel8 would certainly have made that known to the users. But in fact they stated at 7.1.1 you cannot unlock the bootloader whatsoever. Not that if you kept the old bootloader you could still unlock.

How would you do it? Unlock, extract the image, flash everything except the bootloader then relock the device? Don't some images require an updated bootloader in order to function and flash correctly?

So stop denigrating the users trying to help and go ahead and do it. You can always start another thread, "Bricked XL with a locked bootloader HELP" Bring on the popcorn, that should be a fun one to watch.
[Google Pixel XL Questions & Answers] LoliSmith:
You need to stop trolling.

No, most people think like you.

Actually, they did not disclose the exploit as far as I know. Did they disclose it? No one else seems to know what the exploit is.

They stated after you took the OTA you couldn't unlock or after you flashed everything to 7.1.1. They have never addressed what I proposed.

Not just aboot, I wouldn't flash keymaster either. Bootlocker sounds ominous but so far, no info on what that is exactly.

That was my question originally, did you even read the OP? If you could answer it, now THAT would be helpful.

Stop trolling or stop responding. You aren't helpful at all.

No one on this thread has been helpful at all, they are just speculating.
[Google Pixel XL Questions & Answers] LoliSmith:
Haven't bricked a single device and I have effed around with lots of them with locked bootloaders. Helped many people unbrick too.

I've got a lot of experience with motorolas, samsungs and nexi. Just starting to get to know my Pixel. It has been sitting in its box since early December. Time to play.
[Google Pixel XL Questions & Answers] LoliSmith:
I have a 32GB Pixel that I got from Best Buy on Cyber Monday for $275 with tax and upgrade fee. And they gave me a $100 gift card too, so really, it ended up being $175 since I used the $100 BB gift card to buy gas cards.
[Google Pixel XL Questions & Answers] superchilpil:
This was a fun read.

OP, either flash the full update whilst staying unlocked or stay on 7.1 and lock and unlock all you want.

It's an either/or situation.

Since this is a HTC device at heart not flashing a bootloader can break things or even soft brick your device otherwise they wouldn't make a NEW bootloader. It was this way for the HTC Rezound where I would make Firmware packages for people who wanted to flash different firmwares either to use a different version of Android or change the radio. Which required flashing the whole package and not just the radio.

The software is built to work together and using mix matched software will most likely break things. It's common sense.
[Google Pixel XL Questions & Answers] bobby janow:
Trolling you say? Do you post this stuff in front of a mirror? What is your objective other than to troll everyone here?
[Google Pixel XL Questions & Answers] LoliSmith:
I like to live dangerously, lol!

The more I read up on it, the more I am realizing that. Guess I should head on over to the M10 threads.

When you say require, what happens if you try to selectively flash? Do you get an error?

It's definitely not common sense. With motorola, samsung and nexus devices, you can selectively flash. Sounds like it may be different on an HTC device but if so, that isn't a matter of common sense it is just how it was designed. Could have just as easily been designed differently.
[Google Pixel XL Questions & Answers] LoliSmith:
There you go again.
[Google Pixel XL Questions & Answers] aholeinthewor1d:
The exploit used by dePixel8 is documented all over the internet. Do some research this thread is pointless.
[Google Pixel XL Questions & Answers] LoliSmith:
I didn't find it and others on the Pixel thread didn't know what it was either. If you can point me to it, that would be helpful.

Just looked again, and I don't see the details. Closest I can come is this and if they are low level bootloader exploits, then not flashing aboot and likely keymaster and maybe bootlocker should work to keep your device lock/relockable.

http://www.securitybsides.com/w/page/112154857/BsidesSeattle2017

PixelDust - Breaking the Google Pixel

Speaker: Jon Sawyer - [MENTION=2376614]jcase[/MENTION]

Abstract:

The Google Pixel, the successor to the Nexus line of Android phones, was released October 20th 2016. The Pixel was a new era mobile device, and was billed as a security rival to the iPhone. Unlike the Nexus line, not all were bootloader unlockable. Three carriers chose to limit the ability to unlock the bootloader, Verizon in the USA, EE in the UK, and Telus in Canada.

This talk will cover the three low level bootloader vulnerabilities we found and exploited during the first week of Pixel release. These vulnerabilities were given high severity ratings by Qualcomm and Google.

We ultimately publicly unlocked the bootloader of the locked Pixel variants, by releasing the "dePixel8" tool.
[Google Pixel XL Questions & Answers] jcase:
I don't believe it was publicly documented really, if someone did so I'm interested in seeing their take on it.

I actually cut most of the details of dePixel8 out of it. I did discuss other exploits.
[Google Pixel XL Questions & Answers] jcase:
No it doesnt, it doesnt push anything to system
[Google Pixel XL Questions & Answers] LoliSmith:
Do you know what keymaster.img and bootlocker.img are? aboot.img is the bootloader and keymaster as best I can tell is something to do with this:

https://source.android.com/security/keystore/

but I don't know what bootlocker.img is.

I have a Verizon Pixel that I unlocked with depixel8. What I would like to do is leave aboot and any other bootloader related files (keymaster?, bootlocker?) on 7.1 and flash the radios, kernel, system, recovery, etc. to 7.1.1. You can do selective flashing like that on motorolas that is as long as the bootloader and partition table are on the same version and as long as you don't try to downgrade the bootloader/partition table.

It may not be possible on an HTC/Pixel, but I was going to try it.
[Google Pixel XL Questions & Answers] jcase:
Yes i do know what they are.

I dont see why you want to selectively flash, considering the bugs we found in aboot alone, I suggest you update the full stack.

RE: Moto, the flashing individual parts isnt necessarily tied to an OEM, you can do it on many HTC as well. Entirely possibly non matching firmware to harm any device. Rarely is there a reason to do this, and in general its not smart.
[Google Pixel XL Questions & Answers] LoliSmith:
What are they? I mean at a high level. I am not looking for any detailed description of how they work, just what they are.

I want to be able to lock and relock the bootloader and I was thinking if I leave the bootloader on 7.1, then I can do that if I flash everything else to 7.1.1 (except aboot and probably keymaster and maybe bootlocker too).

I also just want to see how these phones work with regards to selective flashing compared to the manufacturers I am familiar with.

Because the bootloader is exploitable and then my phone would be insecure?

We did it on the Moto X 2014 when the bootloader was locked but there was an exploit called MoFo. As long as we left the bootloader and partition table on the earlier version that was exploitable, we could upgrade everything else and still use the exploit to get root.

Thanks.
[Google Pixel XL Questions & Answers] jcase:
Trustzone applets,bootlocker doesnt do anything, its essentially dead code as far as im aware.

If you want to lock it, just flash stock and lock it. Don't expect depixel8 to work to unlock it again unless you use completely stock firmware from one of hte compatibility builds.

You can selectively flash, just hope you dont hit an incompatibility, it could brick your phone (this applies to all OEMs, including moto).

I'm aware of mofo, it was a 'wrap around' bug, that allowed them to flash system partition while telling the bootloader it was flashing cache. Good friend of mine found the bug. Such a bug wouldnt do any good on pixel, as google validates the system partition on locked devices.
[Google Pixel XL Questions & Answers] bobby janow:
Could, would you be able to tell us what differentiates the Google version from the Verizon version that allows or disallows unlocking? Lots of theories, nothing definitive.
[Google Pixel XL Questions & Answers] jcase:
Yes, the phone reaches out to google servers, google tells it if it can be unlocked or not