yashsingh1/xdaforums huggingface dataset:
[Onetouch Idol 3 General] Unjustified Dev:
Used mobile q went back to L. Booted twrp via fastboot captured ota from ./data/data/com.tcl.fota/.fotadownload/update.zip took out bootloader update and flashed zip.
[Verizon LG G5 Questions & Answers] eversonnc:
The G5 doesn't give the option in the Home screen settings to loop the home screens. The current home screen layout is to only swipe left. Are there any fixes out there or any updates planned to fix this?
[Verizon LG G5 Questions & Answers] nicx25:
Download LG Home 4.0 from LG Smart World App. It has the home screen looping option.
[Verizon LG G5 Questions & Answers] PROcede:
Or any 3rd party launcher usually has these options. Nova Launcher can do it.
[Verizon LG G5 Questions & Answers] andyroidking:
With the new UX-5.0 they changed quite a bit and dropped some other things... Like someone said you can install LG Home 4.0 (it is from the G4).
[Nexus 6P Q&A, Help & Troubleshooting] kclive:
I just got my N6P and am coming from the N6 and I have to say I love this phone. I unlocked and rooted my N6P right away. I am no stranger to root and custom Roms. Right now I am on the stock ROM because something is throwing me off a little.

What is the deal with the vendor images? The N6 didn't have them (at least you didn't have to mess with them when you flashed a ROM). My question is this, do you have to flash a vendor image in fastboot each time you flash a ROM? I want to flash some Roms, but until I know more about the vendor images I am holding off on any flashing.
[Nexus 6P Q&A, Help & Troubleshooting] nathanchance:
You only need to flash the vendor image once per new build number. So say you are on a ROM with build XXXXXX and you are updating to YYYYYY. You still flash the ROM then the YYYYYY vendor image. If there is another ROM you want to try on YYYYYY, you don't have to flash the YYYYYY vendor image again.

The vendor image files are a bunch of proprietary binaries and drivers that allow your phone to run properly. These vendor files were originally in /system on all previous Nexus devices but starting with the Nexus 9, they were moved to their own partition, /vendor. Super convenient for ROM developers since they no longer have to include those files from the factory images; instead, people can just flash the images directly from Google.
[Nexus 6P Q&A, Help & Troubleshooting] kclive:
Thank you for your reply. That makes sense. I appreciate it very much.
[Nexus 6P Q&A, Help & Troubleshooting] Heisenberg:
That might not be entirely accurate. Layers installs to the vendor partition, and I believe some aspects of gapps might too. It's best just to flash the vendor whenever flashing a ROM to ensure there's no residual data that could cause problems.
[Nexus 6P Q&A, Help & Troubleshooting] nathanchance:
Yes, I'll give you that. Just not strictly necessary but it is good practice :)
[Nexus 6P Q&A, Help & Troubleshooting] Heisenberg:
I'd totally define it as being necessary, not flashing the vendor is very much like dirty flashing one ROM over another. Plus, it's things like failing to flash the vendor that cause bogus bug reports in ROM threads and waste everyone's time.
[Nexus 6P Q&A, Help & Troubleshooting] SlimSnoopOS:
Some gapps packages may install to /vendor? Do you have any info on what packages or types of files from gapps package would get installed in /vendor?
[Nexus 6P Q&A, Help & Troubleshooting] Heisenberg:
I honestly don't know, I believe I read it somewhere but I can't remember where.
[Nexus 6P Q&A, Help & Troubleshooting] SlimSnoopOS:
No worries, I'm sure one of us will stumble on it soon enough
[Nexus 6P Q&A, Help & Troubleshooting] DJBhardwaj:
Looking at the installer script in OpenGapps, nothing gets added to the /vendor partition. Google apps are installed onto the system, while vendor is a list of proprietary blobs.
[Nexus 6P Q&A, Help & Troubleshooting] Heisenberg:
Yeah I looked at the same thing just before. We can disregard that portion of what I said, the information I read was obviously wrong.
[Nexus 6P Q&A, Help & Troubleshooting] fresnogamer:
Is it necessary to flash vendor images when using the stock ROM from Google then rooting after clean flash it?

Thanks!
[Nexus 6P Q&A, Help & Troubleshooting] SlimSnoopOS:
Nope. Flashing vendor is only required when switching to a different security update. The root and/or clean flash process does not touch the /vendor partition.
[Nexus 6P Q&A, Help & Troubleshooting] fresnogamer:
Thank you for the info.
[Sprint LG G5 Questions & Answers] eurominican:
Is it possible to enable free hotspot on this device, like through modifying APN settings?
[Sprint LG G5 Questions & Answers] Wr3ckd90:
As far as i can tell no i already got my MSL and looked
[Sprint LG G5 Questions & Answers] djxn40:
No way to edit because they are greyed out?
[Sprint LG G5 Questions & Answers] husyk:
I got Easytether Pro free courtesy of Amazon a few years back on Android, I use it to take my PC (USB) and tablet (bluetooth) online using instructions listed below.

http://www.mobile-stream.com/easytether/android.html
[Sprint LG G5 Questions & Answers] DOBBY0:
is this free?
[Sprint LG G5 Questions & Answers] husyk:
Its $10 atm.

https://play.google.com/store/apps/details?id=com.mstream.etpc&hl=en
[Sprint LG G5 Questions & Answers] Toyeboy:
Wireless hotspot works on G5 with this app then? Can you confirm?
[Sprint LG G5 Questions & Answers] hugehead83:
Sprint LG G5 with EasyTether here. Can confirm it works well, however it is not a true "hot spot" as if your phone was unlocked. It will only tether with USB or Bluetooth to one other device.
[Sprint LG G5 Questions & Answers] Toyeboy:
Oh okay thanks guess I'll have to wait for root as I need wireless tether.
[Sprint LG G5 Questions & Answers] RavenFB:
I can VERY highly recommended Klink. It's USB tether, but most important of all is that it completely masks your tethered device's data as your mobile's. It's also for clients available for Windows, Mac, and Linux.
[Sprint LG G5 Questions & Answers] adu1982:
Just tried foxi, kinda of....turned it on while i was on wifi and it does make a hotspot. Cant test full way as my g5 is not activated yet. My g3 works great still, tether and all, on stock rooted. Might activate it and try and if not just go back to my lg g3. Don't use tether too much, but i want the option. It Is my ☎.
[Sprint LG G5 Questions & Answers] jbofae13:
Sharing data lte from Sprint LG G5 to other devices

I know this is going to sound silly but how do I tether to share the unlimited LTE data from my Sprint LG G5 to a disconnected Samsung Galaxy S6 and also is there an ability to broadcast hotspot or tether somehow to a Sony Bravia Smart TV to watch Netflix? Apologies for a question that's probably extremely redundant to you guys but I'm a bit of a novice to all this stuff
[Nexus 6P Q&A, Help & Troubleshooting] kclive:
When I go to the page to sign up for beta testing it shows my Nexus 6 and not my Nexus 6P. Is there any way to fix this or am I just stuck with flashing the images online?
[Nexus 6P Q&A, Help & Troubleshooting] DJBhardwaj:
Go to https://play.google.com/settings

Check that your 6P's visibility is checked. And then try again.
[Nexus 6P Q&A, Help & Troubleshooting] kclive:
I went there and made sure the 6p was the only device checked, then when I went to the beta test signup site it said I have no eligable devices. Any ideas?
[Nexus 6P Q&A, Help & Troubleshooting] DJBhardwaj:
Is the primary Google account same on the 6P, that you're using to sign up for Android Beta Testing?
[Nexus 6P Q&A, Help & Troubleshooting] kclive:
Yes, it is my only Google account.
[Nexus 6P Q&A, Help & Troubleshooting] DJBhardwaj:
Okay. Try removing and re-adding the Google account ?

I am sorry, slowly getting out of clues here. But there is no harm trying. Just curious, have you ever flashed your 6P with a custom ROM etc?
[Nexus 6P Q&A, Help & Troubleshooting] kclive:
I will give that a try. Yes, I am now running PureNexus.
[Nexus 6P Q&A, Help & Troubleshooting] kclive:
The only way I was able to get the download for the beta program was to add a new gmail account, but at least I finally got it working. Thanks for all of you help.
[T-Mobile Samsung Galaxy S 5] Slikrik0300:
After I had no success myself I went to un-locker.com and after 2 days they come and say they can't unlock.it either. Can someone tell me why this is so difficult? I know it's an older phone but it shouldn't be this complicated. I would appreciate anyone's help. BTW very new here and looming forward to getting to know at least some of you.

Slikrik030
[T-Mobile Samsung Galaxy S 5] Stratis1978:
That's odd...
[T-Mobile Samsung Galaxy S 5] justinxfan:
just saying... it's not a good idea to publicly post your IMEI everywhere....
[Galaxy S 5 Q&A, Help & Troubleshooting] noname1981:
I installed stock ROM on my phone. Everything was working fine but then it started to lag. After lagging for a bit it just froze up. The background went black and the phone became unresponsive. I cant get it to turn on in recovery or down load mode. The way it froze makes me wonder if the phone will ever restart. Is there anything I can do to get it into download mode or recovery even though its completely dead?

Samsung s5 sm-g900w8 Canada

Telus

Thanks
[T-Mobile LG V10 Android Development] GROGG88:
TWRP continued from the work of [MENTION=3505796]KAsp3rd[/MENTION].

​

Instructions:

Marshmallow:​

Refer HERE

If you are already running twrp in marshmallow then simply flash any recovery updates using the image install function within twrp.

If you are already updated to the official marshmallow update from T-Mobile then you must wait for a root fix and this cannot be flashed from fastboot commands!!

Lollipop:​

Your bootloader must be unlocked prior to attempting installation.

Option 1: Flash using fastboot.

Option 2: Flash in previous installed version of TWRP.

Download:

Marshmallow

md5: 368f665abed83d839feaa14f5d975e7e

Lollipop

md5: b9ab4ac5b57b26c044db0f7be9ce1e5a
​

Previous versions may be found in the original posting HERE.

Changelog:

3.0.2-0 Marshmallow​

05/01/16:

(REVISION) exfat enabled for testing

Device tree has been rebuilt and USB is operational for mtp, adb, and usb-otg.

INITIAL:

Recovery updated to v3.0.2-0

Kernel updated to Marshmallow

Fake epoch disabled in kernel

3.0.1-0 Lollipop​

Fake epoch set for my device in the kernel (you will most likely experience incorrect date/time)

DST is now functional

Known issues:

The status bar is displayed in the 2nd screen area. (I have no plans on pursuing screen adjustment)

Time is not saved from Android to Recovery. Fake epoch time has been disabled in the kernel resulting in a year of '1971'. (The only way I've found of fixing this is with a custom fake epoch for each device based on build date. That simply is not going to happen...)

(Re)Sources:

Device tree is available HERE.

Compiled using twrp_omni 6.0 branch available HERE.

Kernel source is available HERE.

Get superSU from [MENTION=631273]Chainfire[/MENTION] HERE.

Please report all issues on my github so I can track them HERE.

Special thanks:

[MENTION=3505796]KAsp3rd[/MENTION] [MENTION=3176005]TheJesus[/MENTION] [MENTION=2614663]shabbypenguin[/MENTION] [MENTION=912474]Dees_Troy[/MENTION] [MENTION=4878287]_that[/MENTION] [MENTION=2638973]bigbiff[/MENTION] [MENTION=1924950]helicopter88[/MENTION] [MENTION=4316709]savoca[/MENTION] [MENTION=2684188]autoprime[/MENTION] and anyone I've forgotten.
[T-Mobile LG V10 Android Development] GROGG88:
Reserved...
[T-Mobile LG V10 Android Development] JDBarlow:
Just downloaded gonna check it out. Thank you
[T-Mobile LG V10 Android Development] xtremelora:
Thank You...
[T-Mobile LG V10 Android Development] ZDeuce2:
Thank you sir

Common sense isn't all that common
[T-Mobile LG V10 Android Development] mataflakitas:
Thanks
[T-Mobile LG V10 Android Development] siraltus:
EDIT: Nevermind.
[T-Mobile LG V10 Android Development] nobreak1970:
So far so good. Thanks!
[T-Mobile LG V10 Android Development] BoiBundy:
Thank you, thank you
[T-Mobile LG V10 Android Development] Airtioteclint:
[MENTION=3667193]GROGG88[/MENTION] v3.0.2-0 is out fyi.
[T-Mobile LG V10 Android Development] GROGG88:
When sources are updated I will update the build, but you can see here that they remain at 3.0.1:

https://github.com/TeamWin/Team-Win-Recovery-Project/commits/android-6.0
[T-Mobile LG V10 Android Development] siraltus:
We will need an update to support the 20e bootloader from the Marshmallow update released today - hope you can help!
[T-Mobile LG V10 Android Development] sikander3786:
Yes. I am looking for MM compatible TWRP also. Will be great to see as soon as possible.
[T-Mobile LG V10 Android Development] GROGG88:
I updated to MM today, so I am currently working on it...
[T-Mobile LG V10 Android Development] siraltus:
Thank you VERY MUCH. :D
[T-Mobile LG V10 Android Development] NYLimited:
Thank you!

Maybe with MM we can get the date/time correct in twrp.. (keeping fingers crossed) :)
[T-Mobile LG V10 Android Development] GROGG88:
The time is always correct for me... :laugh:

Seriously, the MM kernel source does not have any changes to fake epoch. Everyone will continue to suffer with 'grogg' time.
[T-Mobile LG V10 Android Development] scloutkst:
MM

How is MM treating you on your device? And, thank you for all your work. We all appreciate it.
[T-Mobile LG V10 Android Development] GROGG88:
Full wipe and running just fine so far.
[T-Mobile LG V10 Android Development] Airtioteclint:
It seems that we're in the same boat with the tmo g5. Luckily team codefire has made progress. Hopefully we can benefit from it as well.

https://youtu.be/Zlieyd9CP7Q

[MENTION=2684188]autoprime[/MENTION]
[T-Mobile LG V10 Android Development] NYLimited:
Since both devices are by LG, possibly with some of the same questions/problems to deal with, some collaboration might indeed benefit both...
[T-Mobile LG V10 Android Development] scloutkst:
Holy **** you got marshmallow TWRP already that was insanely fast
[T-Mobile LG V10 Android Development] sabresfan:
Installed great. Thank you.
[T-Mobile LG V10 Android Development] Airtioteclint:
You flashed it to official marshmallow successfully? I tried, and still got the fail command.
[T-Mobile LG V10 Android Development] sanjsrik:
I have a dumb question...

If we have the current rooted (in my case) lollipop ROM, can we flash and use this recovery? Or, is it only going to work with marshmallow? I seem to remember that the recovery is agnostic of the ROM, but the ROM requires a certain version of recovery before the ROM can be flashed.

Yes, I've been doing this a long time, just thought it best to ask first before doing.

Thanks in advance.
[T-Mobile LG V10 Android Development] scloutkst:
This is a legit question.i have been wondering the same thing. I've been doing this a few years, but I believe the rom has to have a compatible recovery. So I'm thinking it would be mm only roms. If that is the recovery you had. I believe this is because the recovery houses the kernel or has its own kernel. Not exactly sure. I'm sure someone else with better knowledge can confirm our suspicions.
[T-Mobile LG V10 Android Development] sabresfan:
No lollipop
[T-Mobile LG V10 Android Development] geeserver:
My bootloader is unlocked.

It's failing for me also

target reported max download size of 536870912 bytes

sending 'recovery' (33712 KB)...

OKAY [ 0.961s]

writing 'recovery'...

FAILED (remote: unknown command)

finished. total time: 0.977s
[T-Mobile LG V10 Android Development] sikander3786:
Won't work with MM bootloader for now. Nobody has a solution yet. Can't downgrade to 5.1.1 after flashing MM either.
[T-Mobile LG V10 Android Development] scloutkst:
Losing the ability to downgrade sounds kind of apple-esque to me
[T-Mobile LG V10 Android Development] sikander3786:
It would be better to lose the ability to downgrade like you said. It is worse with LG. You try to downgrade, it lets you downgrade, and then the phone doesn't turn on. Brick! So it is not kind of apple-esque. :)
[T-Mobile LG V10 Android Development] siraltus:
The recovery must be mated to the bootloader, not the ROM. If you have the LL bootloader, you install the LL version of the recovery, same with MM, they must match.
[T-Mobile LG V10 Android Development] scloutkst:
Damn. What in the hell were they thinking with this setup? Is it just a soft brick?
[T-Mobile LG V10 Android Development] sikander3786:
Hard brick. No download mode, no LG logo, no life whatsoever. And it can't be un-bricked easily either. Professional skills needed for removing the EMMC, programming it and re-soldering to the PCB. So yes, not a smart move by LG. Sounds like they want to punish the end users who try to downgrade LOL.
[T-Mobile LG V10 Android Development] scloutkst:
Damn. Thanks for nothing LG. Glad I asked around before I made the jump to MM yet.
[T-Mobile LG V10 Android Development] sanjsrik:
Thank you for the explanation. So, since I have lollipop installed, does that mean my version of twrp is only for lollipop? What I'm confused about is what's the order of flashing a new version of twrp versus marshmallow which seems imminent at this point as siraltus seems to have a marshmallow ROM he's working on.

What confuses me is do I first flash the new twrp and then the ROM? Or, can I flash the ROM with the version of twrp I have currently and then go back and update twrp afterward?
[T-Mobile LG V10 Android Development] GROGG88:
At this point obtaining recovery/root with marshmallow is being worked on by many people. Reliable answers to your questions are not available at this time.
[T-Mobile LG V10 Android Development] sanjsrik:
Thank you.
[T-Mobile LG V10 Android Development] siraltus:
A "ROM" in XDA terms is just one partition - the system partition. That contains the Android operating system.

The phone actually has something like 40 partitions, such as bootloader, system, data (where apps are installed), cache, the keystore, and a bunch of other hidden partitions that contain very important, low-level stuff that the phone needs to work. A KDZ file contains ALL of those partitions and when upgrading from Lollipop to Marshmallow, all of those partitions must be updated TOGETHER, or the phone will at best behave erratically or at worst brick completely.

So, in our case, we must first flash the KDZ to update ALL OF THE PARTITIONS, INCLUDING ALL THE HIDDEN SYSTEM ONES to Marshmallow, and then flash TWRP, and then SuperSU to attain root. The problem right now is that once we flash the Marshmallow KDZ, we lose the old way of flashing TWRP via fastboot. We are currently trying to find a new way to flash TWRP, which will then allow us to install SuperSU to regain root.

And yes, because TWRP is like a tiny version of Android, it contains a kernel that must be compatible with the phone's bootloader - so if your phone has the Lollipop bootloader, you must use TWRP that was built for Lollipop, and for the Marshmallow bootloader, you must use the Marshmallow build of TWRP. You can't mix-and-match.
[T-Mobile LG V10 Android Development] sanjsrik:
best. Answer. Ever.
[T-Mobile LG V10 Android Development] setool3:
i agree
[T-Mobile LG V10 Android Development] sabresfan:
So assuming root is obtained with marshmallow then those of us with LP twrp could flash MM rooted ROM when available then hopefully use flashify to update to MM twrp.
[T-Mobile LG V10 Android Development] siraltus:
No, because an MM ROM will not boot without the MM bootloader, unless it was heavily modified (risky business, look at the Korean ROM port). You must have everything MM to run an MM ROM reliably.
[T-Mobile LG V10 Android Development] sabresfan:
Thank you for clarifying this.
[T-Mobile LG V10 Android Development] scloutkst:
This was a fantastic and very understandable explanation for us laymen. Thank you.
[T-Mobile LG V10 Android Development] giggock:
After update to MM , root gone and try to unlock bootloader. Unlock bootloader finished but stuck with TWRP error.

"fastboot flash recovery twrp_3.0.1_v10_mm.img"

"fastboot boot twrp_3.0.1_v10_mm.img"

I got an error all the times.What should i do?
[T-Mobile LG V10 Android Development] nymica:
You should read and wait. Everyone is waiting, codefire is working on a solution for the g5 that we're hoping to be able to use or adapt if needed
[T-Mobile LG V10 Android Development] xRECKSx:
Can I install this if I have no plans on MM roms?
[T-Mobile LG V10 Android Development] toastido:
Has anyone tried this? (my own idea, i don't want to root/flash twrp, but I want to help):

go into dev options, enable oem unlock, then...

adb reboot bootloader
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot flash recovery twrp_3.0.1_v10_mm.img

Note the 'flashing unlock' *AND* 'flashing unlock_critical' steps. Reasoning:

usage: fastboot [ <option> ] <command>

commands:
update <filename> Reflash device from update.zip.
flashall Flash boot, system, vendor, and --
if found -- recovery.
flash <partition> [ <filename> ] Write a file to a flash partition.
flashing lock Locks the device. Prevents flashing.
[COLOR="Red"] flashing unlock Unlocks the device. Allows flashing
any partition except
bootloader-related partitions.[/COLOR]
flashing lock_critical Prevents flashing bootloader-related
partitions.
[COLOR="red"]flashing unlock_critical Enables flashing bootloader-related
partitions.[/COLOR]
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked.
erase <partition> Erase a flash partition.
format[:[<fs type>][:[<size>]] <partition>
Format a flash partition. Can
override the fs type and/or size
the bootloader reports.
getvar <variable> Display a bootloader variable.
boot <kernel> [ <ramdisk> [ <second> ] ] Download and boot kernel.
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ]
Create bootimage and flash it.
devices [-l] List all connected devices [with
device paths].
continue Continue with autoboot.
reboot [bootloader] Reboot device [into bootloader].
reboot-bootloader Reboot device into bootloader.
help Show this help message.

options:
-w Erase userdata and cache (and format
if supported by partition type).
-u Do not erase partition before
formatting.
-s <specific device> Specify device serial number
or path to device port.
-p <product> Specify product name.
-c <cmdline> Override kernel commandline.
-i <vendor id> Specify a custom USB vendor id.
-b <base_addr> Specify a custom kernel base
address (default: 0x10000000).
-n <page size> Specify the nand page size
(default: 2048).
-S <size>[K|M|G] Automatically sparse files greater
than 'size'. 0 to disable.
[T-Mobile LG V10 Android Development] GROGG88:
I tried both some time ago. Neither command is recognised. I also used 'fastboot oem unlock-critical' to no avail. That command is recognised, but fastboot commands are still broken.
[T-Mobile LG V10 Android Development] sinistersands:
Folks, after updating to the MM recovery, ADB no longer seems to see the device in recovery. Of course I was very "intelligent" and decided to wipe the existing system partition so I can't boot and report whether adb works on that side of things. Any ideas?
[T-Mobile LG V10 Android Development] GROGG88:
Yes, flash a system.img and test ADB operation of your system.
[T-Mobile LG V10 Android Development] sinistersands:
So, it works just fine in system. But in TWRP it's still a no-go.

I've tried ADB sideload and also mounting different partitions, which hasn't worked. I checked to make sure my adb was up to date as well so that's not the issue. For the time-being I can install ROM's using microSD, but it might be worth investigating for those who don't have that luxury.
[T-Mobile LG V10 Android Development] siraltus:
That's because you're running a MM kernel (in the MM TWRP) on LP bootloader. They need to match.
[T-Mobile LG V10 Android Development] sinistersands:
Gotcha! And I'm guessing that if I flash an MM bootloader, I won't be able to flash TWRP back on, correct?
[T-Mobile LG V10 Android Development] siraltus:
Yeah, that's the current catch. G5 devs are working on this, once they figure it out we will be able to use their solution.
[T-Mobile LG V10 Android Development] sinistersands:
Got it. Well, at least we've got MicroSD for the time being ?. Thanks for your help gents!