yashsingh1/xdaforums huggingface dataset:
[Verizon LG V10] Eliminater74:
Let me explain something all you people, First fastboot commands.. LG perilously left out the main fastboot commands.. When you get the source code of the the bootloader where the fastboot lies at,

there is a configure script with all well known fastboot commands.. you have to by hand uncomment the commands you want to enable.. or leave them all disable to have a dummy fastboot which LG has done.

except for the stupid commands.. Im just laying a basic picture for you peepz, I am a developer and I have the h901 T-MObile.. But I and others have given up on it all together.. you cant get any custom roms to work

on it well since MM release.. Camera wont work and blue wont work.......... LG has tighten down their security and blobs................

So I went out and bought me a HTC 10 which I love and develop on now.......... I will never again in my life buy another LG..........

I have had 4 LG phones in the past, 2 are flagships....... Never again............

as for you unlocking your bootloader.. you wont.. you cant.. there is no code in your bootloader that allows you to unlock it. you need something like the G3 had that bumps the signed image with

LG sig thats uses 8bit encryption............

and I have personally bricked over 3 V10's.. First one by mistake. the next 2 on perpus for testing......

anyhow.. Anti ROLL back will brick your device.. and if you think you can flash something else like a T-Mobile image.. you will brick your device........

So be carefull...............................

thats all I will say......................
[Verizon LG V10] alvinator94:
Wow thanks for the info and the fair warning, its much appreciated. For the record I have flashed other devices softwares onto here and worked on getting their fastboots to replace mine. You as a developer should understand that there is no can't or it wont happen (besides the KNOX security lol). It can and will happen, and when it does I'll let you know. Seriously though thank you for the help. Please let your dev friends know that this bounty is out here.
[Verizon LG V10] Eliminater74:
I know what the source code looks like for fastboot.. and I know what LG did.. and I know your verizon device bootloader does not even have the OEM command to unlock it.

it was left out.. only way your getting images though that bootloader is though a Signed by LG 8bit encryption........ And sorry, I just dont believe you flashed another bootloader on your device and it worked..

unless LG only added the anti-roll back to everyone but you. and if you could that easy flash another bootloader on your device that wasnt made for your device, then you would already have a unlocked bootloader

and that would also mean your device doesnt check for the 8bit encryption sigs.................. So sorry, unless you can show me. I dont believe that............

But yur right. nothing is impossible.. Look at my sig, Bottom says, Where The Impossible Becomes The Possible.....

When I had my G3, Nothing thought 3ghrz was possible.. they said I would never get it done.. I got 3ghrz stable with GPU at 700mhz Stable...............
[Verizon LG V10] alvinator94:
I wish I had done that lol, I'm talking about things such as getting a tmobile fastboot on there, or getting a specific piece of software on there that wasn't supposed to be like a different recovery (stock of a variant). But I'm in the same boat and hear you loud and clear. Love the sig.

But today, for everyone to know, I will begin my testing again. Add me on hangouts if you wanna talk and DEV it. alvisleet@gmail.com
[Verizon LG V10] Eliminater74:
I personally wanna, give you full props for what your trying to do.. and I hope you do it. I really do.... cause I still have my v10.. and I love that device.. Might give it to my 17yr old daughter........

but I stopped developing on it because I wanted to do some real work.. not spend a year trying to get something to work.. I heard news today that the G5 got cam to work.

which means.. we at T-Mobile should be able to use the same method they used to get cam to work..

If you PM me I can give you a link to a hangouts channel that I have alot of v10 owners in for dev talk............

But in all.. Good work.. and Dont let anyone talk you into giving up.. I gave up cause I wanted to Dev.. I got tired if playing around with it.

but in all.. V10 is a great device..................................

BTW: I have made some kdz that allow kdz twrp into our device............... good for bypassing fastboot and other things.
[Verizon LG V10] joshw0000:
Not to bust your bubble but unfortunately you're no closer to unlocking the bootloader. I got excited last year when I figured out how to enable OEM unlock on the G4. I assume you're zero'ing the LAF Partition which worked on the G4, G5, and pretty much all LG devices prior to those? We found that (in my thread) a year ago and the G4 is no closer to an unlock today.

http://xdaforums.com/showthread.php?t=3170556
[Verizon LG V10] alvinator94:
Thanks for letting me know. What steps did you guys try with this after you found it? And yeah thats right.
[Verizon LG V10] joshw0000:
We tried all the same fastboot commands that you did after selecting Enable OEM Unlock (unlock, flash recovery, etc). Unfortunately nothing worked.
[Verizon LG V10] alvinator94:
Those commands are literally missing from the aboot.img (the fastboot on the phone)

I opened up both our aboot.img and tmobiles aboot.img. You can see here, the tmobile one being the one with more fastboot commands, what is missing from ours compared to theirs. I was able to replace my aboot.img with tmobiles aboot.img but me being a dumba$$ didn't realize until after the fact that that would brick my phone. So now I have to send it off for a new one. RIP.
[Verizon LG V10] nostang3:
When enabling the TMO option and getting the Smart Settings option on verizon. Did anyone figure out how to set 'My Place'? It doesn't show up under Location like it says in the smart settings dialog popup when I try to turn on a setting.
[Verizon LG V10] emdroidle:
I'm actually targeting a different V10 version, but this looks like it has been one of the more active threads on breaking the bootloader. Here are not one, but two reports of V10 KDZ files being rather more compatible between devices than expected. The approach of flashing a complete H901 KDZ file seems rather plausible. I've written a utility which should remark KDZ files so they successfully install on the "wrong" device.

I'm cautiously optimistic about this approach, but it is risky and I don't have a spare V10 available if I brick a device.

Do you (or anyone else) have links to the pre-MM H901 KDZ files? From examining KDZ files it is pretty clear KDZ files include the entire bootloader. If the H901 Marshmallow bootloader strips out the important bootloader commands, why not simply downgrade to the earlier bootloader and use that as your development basis? Is the problem that the 10c or 10f KDZ files need to be found?
[Verizon LG V10] kaluna00:
Any new movement or good news on this one?
[Verizon LG V10] emdroidle:
I have not yet met with success, but I'm continuing to do experiments and generating interesting observations. I can confirm the SD card 9008 debrick method works for my device just fine. This strongly suggests the method will work for any LG V10 device as long as you generate an appropriate image beforehand (simply run that command on your phone and you have a viable method to debrick).

I've confirmed booting from SD card does in fact load all of the bootloader stages off of the SD card. Wiping the aboot area on the SD card caused my phone not to boot at all from the SD card. Seems "rpm" is involved with vibration since if it was okay my phone would vibrate if I pressed power, but it wouldn't even do that if rpm was wiped. Meanwhile it is pretty clear the *bak areas are completely ignored. LG likely uses those for development and could have provided a fallback for shipped devices, but didn't. I am not impressed.

"raw_resources" is either not verified or else is only conditionally loaded well after the other bootloader stages. Having a modified "raw_resources" didn't prevent booting from SD card.

Merely replacing the bootloader stages will not work. Seems the H901 bootloader looks at something else to confirm it is on an H901 before completing its boot process. Replacing all the bootloader areas on a SD card wouldn't allow my phone to boot. Most likely the bootloader checks something in one of "fsg", "DDR", "encrypt", "rct", "misc", "drm", "sns", "mpt", or "fau" before completing boot. I'm guessing it is checking something in "misc", but this is only a guess. Next I need to try wiping those areas on an SD card image individually and see which ones prevent booting.

So additional observations, but no success yet.

I'm wondering if perhaps "dirty santa" could be adjusted to work for the V10. Doesn't really sound like it though, sounds like they got their hands on a debugging version of the bootloader and are replacing the bootloader, haven't seen anything like that for the V10.
[Verizon LG V10] 666syco:
Wow crazy Verizon v20 with a unlocked bootloader and we're still on rooted 5.1.1 wow that pissed me off but is nice to see that they got past the BS set to block them.

Sent from my XPOSED V10
[Verizon LG V10] alexanderzhang:
hi,emdroidle

can i do the SD card 9008 debrick method with .img made by your kdztool? I don't have a backup image because H961N can't root on 6.0.
[Verizon LG V10] emdroidle:
I had hopes the images produced would work for that, but it got disproven. :( If we learn more about the workings of the bootloader it may become possible, but it is not yet possible. Right now the only reliable way to create images is to have a rooted device and run `dd if=/dev/block/mmcblk0 of=/dev/block/mmcblk0 bs=4096 count=262144` with a >=32GB micro-SD card in the slot.
[Verizon LG V10] alexanderzhang:
OK, thank for your rely, can i user the img for H901 to get download work and then try LGUP use a H961n kdz/tot hex model to H901?
[Verizon LG V10] alvinator94:
If I have someone willing to kill their device could you, me, and another programmer/dev get together on this? Sidenote I've achieved temp root through dcow. Doesn't mean much though lol.
[Verizon LG V10] emdroidle:
Is English a second language for you? I'm trying to figure out exactly what you mean since small differences do matter, but I'm guessing what you're thinking hasn't been confirmed to work. I hope a strategy along those lines will work, but nothing is working yet.

I was figuring this was roughly how things were going to work. We try bouncing things off each other until we get confident enough to try something plausible enough to run on a device.

My experimentation failed to get the results I was looking for. This seems to suggest the SD card recovery is only loading the bootloader stages off the SD card; everything else appears to be loaded off the internal flash no matter what. "raw_resources" is either not verified or else loaded exclusively from on-board.

[MENTION=3920245]alvinator94[/MENTION] sounds like you're more capable with IDA than I am at this point. Any chance you can figure out how the bootloader stages figure out what type of device they're running on? Appears the OS may be telling the bootloader what device and version it thinks it is running on by writing that at offset 0x7000-0x7040 of the "misc" area, this may be part of how they communicate.

More or less I hope for a "Dirty Santa"-type approach only instead of using a debug bootloader, using the H901 bootloader.

A big question now is, how is LG Electronics going to react to "Dirty Santa"? Will they unlock bootloaders across the board for V10, V20 and G5 as they did when "Bump" came out? Will they merely unlock bootloaders for V20 and G5? Will they try something nastier?

Alas, at this point I'm considering exit strategies. :(
[Verizon LG V10] alvinator94:
Have you seen this thread? http://xdaforums.com/android/software-hacking/root-tool-dirtycow-apk-adb-t3525120/ also I will look into it with IDA tomorrow or later tonight at some point. I've got a dinner to go to. At this point I'm just waiting for the DirtySanta stuff to come through honestly.
[Verizon LG V10] alexanderzhang:
[MENTION=6984210]emdroidle[/MENTION], Sorry, My English is terrible. Your understand is right. Now I am thinking try to flash a N961N KDZ If I can write a modified H901 img on SD card and boot to download mode.
[Verizon LG V10] emdroidle:
The DirtyCow from the V20 thread should work fine on the V10. I'm pretty sure DirtySanta though will not work on the V10. DirtySanta is apparently a debug version of the Qualcomm 820 bootloader. I'd guess someone left LG with an engineering device in their pocket and simply sold it as a normal phone, but someone on XDA found it and the development image was taken advantage of.

We don't have a debugging bootloader, but we do have the freely unlockable H901.

This is similar to what I was trying. Installing the H901 bootloader onto a SD card, disabling the on-board bootloader (`dd if=/dev/zero of=/dev/block/mmcblk0p4` don't do this unless you're prepared to recover!) and seeing whether mine would boot from the SD card. Bad news is it didn't work, see above.

My guess is it was only loading the bootloader stages off the SD card and the H901 bootloader figured out my device wasn't a H901 and then halted. At which point the question is, how does the H901 bootloader identify whether it is on a H901 or not? The data in "misc" (/dev/block/mmcblk0p25) looks suspiciously likely to be used for this purpose, but it might need a bunch of modifications for the H901 bootloader to accept it. I suspect when Android boots LG's software writes the Android software version and device name to offset 0x7000 of misc and the bootloader checks that; as such this would also require modification of the startup files to avoid writing that area or overwriting it after every boot.
[Verizon LG V10] alexanderzhang:
What about using a 5.1 backup img from H961N? Can I boot to download mode after write the fist gigabyte to SD card from the backup?
[Verizon LG V10] emdroidle:
This is pretty well exactly what has been shown to work on any. Take any V10 and a SD card of 32GB or 64GB and run the command `dd if=/dev/block/mmcblk0 of=/dev/block/mmcblk1 bs=4096 count=262144`. After this if you nuke sbl1, you can simply insert this SD card and the phone will boot even though the bootloader has been damaged.

Few key points here, "bs=4096" simply tells `dd` to use 4KB blocks, this size is generally the optimum for transferring large amounts of data, "count=262144" is simply the number of 4KB blocks in a gigabyte. On the V10 the internal eMMC flash is /dev/block/mmcblk0, and the SD slot is /dev/block/mmcblk1.

I suspect copying about 105MB would generate a sufficient image, but haven't taken the time to confirm this (the entirety of the bootloader is in the first 105MB).

I'm pretty sure it will not. DirtySanta was mostly a few developers getting really lucky by getting their hands on an engineering device which should never have been seen in the wild. :(

Figuring out why the H901 bootloader won't run on other V10s seems the best approach we've got right now.

EDIT: Jan 2: I've learned some interesting things from asking questions about "Dirty Santa". I've discovered one of my educated guesses above is apparently wrong, though it doesn't will change the situation and our needs much.

Dirty Santa only replaces the aboot image (/dev/block/mmcblk0p9). I had been guessing the secondary portions of the bootloader were probably verified by hashes contained in the sbl1 area, but this would make replacing only aboot impossible. Yet this has now been done successfully. As such I must now conclude the secondary areas are verified by signatures, rather than hashes.

Unfortunately this really doesn't change our situation very much. This does though suggest the phone-type verification is in aboot, and merely replacing aboot may be the right strategy. At which point we've back to, how does the H901 aboot confirm whether or not it is running on a H901?
[Verizon LG V10] lowkeyst4tus:
Can someone pm me 2 versions of twrp? One for unlocked bootloader & and one for locked bootloader.. I might be able to get it to work via fastboot but can't find twrp for vs990 anywhere.. lambo352@gmail.com
[Verizon LG V10] fastjohnson:
No offense you guys but once you get the bootloader unlocked and achieve root theres still no development for this device. The original ROM is better than the custom ROMs. Nobody built anything good for this device but I'm sorry to say it but your kicking a dead dog. Nothing good is going to come of your efforts.
[Verizon LG V10] Dr. Righteous:
JUST being able to uninstall the CRAPWARE the service providers push on you is a win if you did nothing else.

I loved the phone when I first got it but with subsequent updates the phone's performance has gotten worse. I was able to disable 100% much of the crapware initially but that went away with updates. Breaking bluetooth audio ruined one of the best features of this phone for

me since I love to stream music in the house and in the garage. Verizon won't own up to it and keeps telling me it is something I've done or my BT devices. What a load of sh*t. This was an expensive phone when we purchased it and I could have gotten much better performance from a cheap phone.
[Verizon LG V10] Akhayev:
I tried your way but I have just one seetings util , and when i open it it gives me this:
[Verizon LG V10] Kenposcholar:
RIP

RIP VS990 development
[Verizon LG V10] nobodywasishere:
I found a VS990 in an electronic recycling bin. Works okay-ish but there's so much potential to this device... read through everyone's replies, and a lot of you tried stuff I was thinking about. I'm not sure where to go from here, or if it's even worth it. :(
[Verizon LG V10] datashifter:
I still have mine, with a ZeroLemon extended battery. Perfect condition, too. I'd like to do something with it, as the camera is great for what the phone is...
[Verizon LG V10] OnceAMatrixMan:
LOVED my V10 to the day it just died (chip issue I read somewhere). The G7 can't hold the V10's jock.
[HTC 10 Questions & Answers] stonew5082:
Aside from the stickers which don't interest me, will themes look different on the 10? Or exactly the same as on the m8, m9?

I was particularly interested in the 'switches' in settings, the Quick Tiles, and the contacts/dialer.

I've only seen video of the stickers so far. Not a single reviewer seems to have tried a theme and then moved around the UI.
[HTC 10 Questions & Answers] 5m4r7ph0n36uru:
The UI has changed quite a bit. The strings menu now comes in the known and nearly stock Android look and contact pictures on the list view of the respective App are round instead of squares to name some of them.
[HTC 10 Questions & Answers] stonew5082:
Well I was sad to get a reply on reddit from a dude with the phone saying the themes don't change the colors/switches in the settings menu. See here:

https://www.reddit.com/r/Android/comments/4hi77y/just_got_my_htc_10/
[HTC 10 Questions & Answers] King p1n:
Wish themes changed things like status bar icons, I'm not a big fan of Sense Wifi icons lol

Yes petty but im way too used to stock.

Regardless HTC's theme engine as I thought, looks lackluster in comparison to say Touchwiz's, which changes more elements of the UI e.g. menu's, notifcation tray etc
[HTC 10 Questions & Answers] stonew5082:
there is some hope that layers themes can be made for this phone though. We shall see
[HTC 10 Questions & Answers] King p1n:
Was there layer themes on the m9?
[HTC 10 Questions & Answers] stonew5082:
Well [MENTION=1050103]sykopompos[/MENTION] said this a while back in the google+ layers community...

"If any of you run across marshmallow OEM roms (not nexus or Android one, these are aosp) or get one for your device (I know the g4 has one out there), post them up.

Make a dump of the system, if you don't know how, just ask (be prepared to use adb)

Since layers works on stock marshmallow natively, it should work on any OEM marshmallow rom (besides cm obviously) and chances are high that the resources might be different and themes could be made/modified to work with these OEM Roms.

We are only interested in marshmallow Roms though since they will have full native support and the changes Google made in marshmallow.﻿"
[HTC 10 Questions & Answers] King p1n:
Hopefully somebodys needs to get him a dump!
[HTC 10 Questions & Answers] stonew5082:
So we need to get a system dump, give it to him, and hope it looks promising

EDIT: what [MENTION=5366632]King p1n[/MENTION] said lol
[Galaxy S6 Accessories] Shaneee:
Has anyone got one or used one before? I was planning on getting one for my S6. The reviews on their site and the video seems really cool.

https://www.intoroglass.co.uk/product/galaxy-s6-glass/
[Galaxy S6 Accessories] KennethHau:
it is really cool. They even have a lifetime warranty :p i cracked my tempered glass (from another brand, not intoro) after dropping it for th 6th time :/ Was planning on buying a new tempered glass. Maybe ill try this one :p
[Galaxy S6 Accessories] Rakcoon:
Not too fond of companies that offer lifetime warranty. They charge you for shipping and handling which costs around $10 each order. Not really lifetime warranty when you have to pay 50% of product cost.
[Galaxy S6 Accessories] thundastruck:
Only 2mm thick? Sounds cool. The ones I can get are all 3mm thick.
[Verizon Galaxy Note 4 General] djquestt:
Can someone please create a thourough start to finish guide on converting, rooting, recovery, and rom installations?

listen im no noob but im no mater either ive been rooting since the original TMO G1 and it has gotten very complex on top of that ive missed alot since i got my note 4 retail (out of the game) anyways someeone please compile a step by step list of what to do and where to find the neccasary files. and in what order.

please and thank you
[Verizon Galaxy Note 4 General] refusedchaos:
For BL unlocking follow this

For rooting

If staying on stock:

Boot into download mode (VOL-DOWN + HOME + POWER) and flash twrp-3.0.2-0-trltevzw via ODIN (MAKE SURE YOU UNCHECK AUTO-REBOOT!!!).

Battery pull phone and then boot straight into recovery (VOL-UP + HOME + POWER) to finish the recovery install process or else it will install the default android recovery.

Then flash the Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P kernal via recovery.

Then flash the BETA-SuperSU-v2.71-20160331103524 via recovery.

Reboot.

If going to a different rom, you should just be able to flash the rom via recovery and get right in. But results may very, check the forums.
[Verizon Galaxy Note 4 General] djquestt:
thank you very much i was a little frustratrated because it seems like the info is very fragmented
[Verizon Galaxy Note 4 General] mlcampbe:
Can someone please tell me where I have gone wrong.

I have gotten temproot via kingroot installed and was able to get the unlocker to run and I can see that the device is now a developer device. I am trying to get root to work but not having any luck.

I follwed the instructions at http://xdaforums.com/note-4-verizon/general/guide-noobs-guide-to-perm-root-twrp-t3360883 and had problems in step 8 when trying to run super-sume. I ran it successfully for stage 1 but then it hung when trying to run stage 2. However, I was able to move on to step 9 and install TWRP and the emotion kernel. I have done a full reset and tried a 2nd time but still no luck in getting permament root access.

Root checker shows no root access and superSU is installed but shows no su binary installed.

If I run SuperSUME-Pro then it shows the device is wrte=protected

It seems I can run kingroot again to gain temp root access but not perm root access.

Any ideas on how to proceed from here?
[Verizon Galaxy Note 4 General] Sizzlechest:
Install SuperSU from TWRP. Does that work?
[Verizon Galaxy Note 4 General] anrichardson:
If you Developer mode and twrp but no root, then what you need to do is install emotional kernel from twrp and reboot device then boot back into twrp and install SuperSU zip and reboot device you should be fine.