yashsingh1/xdaforums huggingface dataset:
[Verizon LG V10] macandlinuxuser:
Yes

It should work. I had a good 1/2 hour conversation with the local sales rep, in Fort Lauderdale. He said all the new Android phones are unlocked. We also discussed rooting. His phones are rooted. He said not to root until the Knox counter is not tripped.

---------- Post added at 03:48 PM ---------- Previous post was at 03:42 PM ----------

No unlockingg or rooting required.
[Verizon LG V10] ultrma:
Here is my story.

I am using Cricket wireless and bought a Verizon version LG 10 from Best Buy. It's a unlocked phone by default. This phone dose support LTE band 2, 4, 12 (Not sure 17) that compatible with ATT. But there is an issue when you use it in GSM/LTE mobile carrier.

By default the network type is set to "Global". This allows you to talk, text under GSM network (HSPA+, 3G), not in LTE network. If you switch the network type to "LTE/CDMA", you are able to connect to 4G LTE network, but you cannot talk or send text message.

Is there anyone who knows how to have voice, text with LTE network at the same time? Thanks
[Verizon LG V10] rlivin:
Deleted
[Verizon LG V10] miguel72389:
Will not get 4g LTE

I purchased an unlocked verizon lg v10 and when i plugged in my sim i realized it will not get 4g lte only HSPA+, LTE will display here and their but will disappear and change over to H. I hope someone can fix this or else i think ill be getting a different device.

---------- Post added at 04:08 AM ---------- Previous post was at 03:55 AM ----------

I have the same problem and cant seem to resolve it, were you able to get this fixed???
[Verizon LG V10] tanked89:
Its because i belive tmo uses a band that verizon doesnt to run its lte service I'm trying to trade. If root comes maybe someone will be able to assit damn verizon
[Verizon LG V10] Lazybumx:
yes it works with t-mobile, i am using verizon v10 on t-mobile right now, i disable most of verizon apps on the phone. also set up the apn for t-mobile in order to get data. the only annoying part left is that the phone tell you the sim is not from verizon everytime you restart, but that can easily swipe away just like any other notification.
[Verizon LG V10] tanked89:
You get lte speeds?
[Verizon LG V10] tanked89:
Anyone tried this or seen this?
[Verizon LG V10] tanked89:
If we can root we can change software to allow this phone to work on mobile bands I believe. Any word on root? Any luck anyone anywhere?
[Verizon LG V10] joeminati:
Now that root is possible, how does this affect unlocked base bands or menu options?
[Verizon LG V10] proplayer44:
Anyone know how to unlock LTE using Verizon on another provider?
[Verizon LG V10] Boris1M:
Not sure if it helps, but V10 does LTE on some providers with no unlocking or anything like that.

I am in Lithuania right now, and put a local SIM in it (3 Euros for 350 min/5000 SMS/1GB + unlimited Facebook and Whatsapp sure beats what Verizon charges for international roaming!). First day it was only picking up 3G or H+. Today though, I've noticed that it switched to 4G LTE, and Speedtest shows it pumping 60+MB/s, which is better than what I've seen on Verizon...
[Verizon LG V10] sambo989:
the USA is a big old mess

Boris.

aside from the prospect of hillary or donald becoming president... many are looking to leave the usa, in desire. not sure how many will actually pull the trigger and do it.

verizon, tmo and att, sprint, don't play well with each other. They use different bands. even if the phone is capable of using the proper band, big evil verizon locks it down somehow.

stinks really.

And i believe there is bandwidth throttling for sure. in the usa.
[Verizon LG V10] Boris1M:
They always say they will, but they never do...

Having said that, the phone seems to do LTE on other networks just fine. And at least Verizon has a network in the US that actually works where I need it, which is more than can be said about T-Mo...
[Verizon LG V10] wwazman:
Hello all.. new and late to the party.. I just picked up a LG v10 the other day, not quite realizing it was a Verizon phone, but pleased with it's size and ability once I plugged my sim in and away it went. Then I ran into issues, the 4g/lte and also Tmobile pretty much recognizing it as a "roaming" phone, albeit with a authorized sim.. kinda akin to a grump saying "Allright, I'll let you in, if I HAVE to... but NO BENEFITS!" ..oh and also the phone itself will NOT let me tether AT ALL.. bummer... waiting for either a root solution or a answer if I can flash the tmobile image to this phone and get it working? ....

in the meantime I thought I would try to help some people with some solutions that seem to be working a bit better for me at least..

1st Step is download an app on Google Play so I can monitor the ACTUAL network speed and status, and that is

"2G 3G 4G LTE Network Monitor" by Sun Light.

(Notes:) since I'm on Family Mobile (T-Mobile variant) I had to crack a few skulls to get things working right and to tell the phone to stop seeking cdma.. you may have to, if you reboot it, tell it to manually use the Network Select and put it on the Tmobile or other correct network...

2nd step is go to Settings - More - Mobile Networks - SYSTEM SELECT - change NETWORK MODE to LTE/GSM/UMTS

3rd step, still in this section, LTE/GSM/UMTS Settings - Network Submode - LTE/Legacy 3Gpp multi

4th step (might want to do this earlier) is to change your APN settings. I used the guide here: https://bestmvno.com/apn-settings/simple-mobile-apn-settings/

Go to Settings - more - mobile networks - access point names - and make a new one for Simple Mobile or whatever you want to call it. (works as of 8-2-2017)

APN: simple

MMSC: http://smpl.mms.msg.eng.t-mobile.com/mms/wapenc

Authentication Type: NONE (BE SURE TO SELECT THIS! This actually DID make a difference for me, don't just leave it blank)

APN type: default, supl, mms, admin (you could add fota - firmware over the air - if you wanted to but crossover users shouldn't imo) .. the main difference here is we are adding another setting "Admin" under apn type. for whatever reason (and I'm not *as* technical when it comes to phone software - I'm still learning ) it seems to stay on 4g longer.

Save and reboot. On reboot, go back into Network Select and select Tmobile LTE as the network, let it choose it....wait.. and should come up LTE. For a while at least, and depending on your signal and the area.

Good luck!
[Verizon LG V10] comk4ver:
Thank you for this! It does work just like you indicated. But, it does drop out again... Literally, two minutes afterwards. It was indicated that verizon is blocking the phone on purpose.
[Verizon LG V10] comk4ver:
Sorry for the double post but I can't add pictures to a post once I hit submit. I'm including pictures from the official T-mobile site that could be useful to someone.
[Verizon LG V10] wwazman:
Not sure if it's Verizon s software on this very locked phone or what.. I know when I try to run ussd code on T-MOBILE'S end it would say (audibly as a call that did not go through) "sorry but your access has been restricted to non TMobile customers roaming on this network." (Ie, f.u.) .. so afaik T-Mobile sees the phone as a stranger (I always had to enter my pin when I checked voicemail) even though it would seemingly tersely allow it on the network. Just not at full speed. I finally sold it and got the h901.. ..I do miss the quality actually!! I had crystal clear on the vs990 on TMobile.. more muffled on the 901.. go figure.

Wwazman
[MTCB Android Head Units Q&A] Lucacolon19:
Hello, I have a stereo Pumpkin and worked perfect. Today I wanted it on and stays on and the logo will not start.

And I tried pressing the reset button and disconnect the car battery and remains unchanged.

I leave a video demonstration of what it does.

https://onedrive.live.com/redir?resid=89B58453255521EC!446&authkey=!AKyOfVlhPymibcg&ithint=video%2cmp4

I await your response.

Cheers
[MTCB Android Head Units Q&A] u.r.rible:
Try to enter the recovery model, then choose the "recovery system from back up". The Pumpkin has uploaded a instruction video on YouTube. I am new here, can't post a link. You can search "KD Android Headunit Recovery mode update instruction". :cool:
[MTCB Android Head Units Q&A] nleitao:
That requires he already have a backup...
[MTCB Android Head Units Q&A] dark alex:
I guess your Unit is of MTCB-Type. I will move this thread to the new section probably you will get some help there.
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] Dedline:
Anyone ever been trying to flash the stock OG5.TAR through ODIN and had it fail, then sayd Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again. I can not get a rom or stock tar to flash and work after having other issues.

Also tried flashing twrp again, then going into recovery and flashing Sac23's Rom, and get this error:

symlink: some symlinks failed

E: Error executing updater binary in zip '/external_sd/Note_5_Sac23_Port_V2.1.zip'

Error flashing zip '/external_sd/Note_5_Sac23_Port_V2.1.zip'

and says Failed.
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] jhill110:
A little more info such as did you check md5 after downloading the stock tar?

Whats your current version of Android?

What other if any mods have you done?

You can try the stock rom by tx_dbs_tx here:

http://xdaforums.com/showthread.php?t=3176288

Read the OP carefully.

If that works then go here:

http://xdaforums.com/showthread.php?t=2956667

and flash one of the three awsome bug free roms.
[Fire Android Development] Awesomeslayerg:
NOTE THIS ROOT ONLY WORKS WITH FIRE OS 5.0.1 AND ONLY THE HD 7 NOT THE 10 OR 8

WE HAVE GAINED ROOT!!!

Thanks to [MENTION=6289000]jkchr1s[/MENTION] for the help and the windows bat file, [MENTION=2511007]csolanol[/MENTION] for actually finding the root, and [MENTION=4375260]diegocr[/MENTION] as well as the [MENTION=631273]Chainfire[/MENTION] SuperSu for the root binaries!!

Heres a video for you guys who need help:

https://www.youtube.com/watch?v=ux-2b3X3BlI&feature=youtu.be

[YOUTUBE]ux-2b3X3BlI[/YOUTUBE]

Just download the zip file from this link and remember to use a windows/linux device for now.

Mediafire Mirror #1

For windows hit install.bat and follow trough the steps

For Linux run it through the linux command prompt

2nd way to root:

1. Download supers from chain fires website https://download.chainfire.eu/696/supersu/

2. Download [MENTION=5749760]ggow[/MENTION] custom recovery or [MENTION=1926811]cnso[/MENTION]al Twrp

http://xdaforums.com/amazon-fire/orig-development/twrp-recovery-t3242548

http://xdaforums.com/amazon-fire/orig-development/recovery-cyanogen-recovery-2015-11-04-t3240726

3. Place the recovery image in the same folder as adb and fastboot.

4. Put your fire in fastboot mode

5. Boot into the custom recovery via "fastboot boot <recoverimsgename>.img.

6. You should be in the cynogen recovery (Or twrp depending on which recovery you downloaded_

7. Then pick adb sideload, and select it and manually install drivers. If you're too lazy just place su in your SD card and flash the zip from there.

8. Adb sideload supersu and you'll get root!!

REMEMBER WE ARE NOT LIABLE IF YOUR TABLET IS BRICKED!!!

I have also left the boot.img tool as well as the modified versions of the boot.img files just incase if anyone else wants to probably dig deeper and explore more about the boot.img file
[Fire Android Development] amazinglarry311:
Have you tried adding the su binary to /sbin in the ramdisk, and editing default.prop to ro.secure=0?
[Fire Android Development] rbheromax:
just adding it to /sbin wont solve this. you would have to add all the selinux info for it also and then also manage to start the su daemon.

ro.secure=0 is already inside the attached boot.img above, doesn't seem to help
[Fire Android Development] jkchr1s:
If we have r/w to the filesystem, take a look at the root script in this LG package: http://xdaforums.com/lg-g3/general/guide-root-method-lg-devices-t3129197

Do you think this method would work?
[Fire Android Development] Vlasp:
Lol wow! Seems to be sparked by my discovery of this new root method! Anyhow, [MENTION=6289000]jkchr1s[/MENTION] might be on to something.

---------- Post added at 11:12 AM ---------- Previous post was at 11:10 AM ----------

I'll try it!

EDIT: DON'T DO IT! IT CONTAINS LG DEVICE SPECIFIC THINGS AND IT COULD BRICK YOUR DEVICE. GOOD THING I LOOKED AT THE INSTALL.BAT BEFORE I TRIED IT!
[Fire Android Development] jkchr1s:
I don't mean to run the root.bat file, look at the root script. It copies SuperSU binaries, adds a su service, and chcon's the necessary files.
[Fire Android Development] Vlasp:
Yeah, but we are going to have to change the device specific stuff (if it matters for our device).
[Fire Android Development] Awesomeslayerg:
I have updated the thread!! Thanks [MENTION=6289000]jkchr1s[/MENTION] for the clear steps and [MENTION=4375260]diegocr[/MENTION] for helping out and giving us r/w ability.
[Fire Android Development] Vlasp:
This will work for rooting this device now.
[Fire Android Development] diegocr:
Someone is root .............

With boot.img
[Fire Android Development] csolanol:
I adapted the guide and u know what?. I am root!!!

Did all the steps by hand and SuperSu is working, i can make su in adb shell.

I can't write a guide right now, i have to go out of the house but this is done guys.
[Fire Android Development] jkchr1s:
What do you mean? KingRoot says it failed booting with the boot-firestarter.img
[Fire Android Development] Vlasp:
yeah, sorry. only the tutorial will work.
[Fire Android Development] Awesomeslayerg:
Dosent work?
[Fire Android Development] jkchr1s:
Sorry, I'm not seeing a guide or tutorial on that link. That's a link to KingRoot.
[Fire Android Development] csolanol:
Just for those of you that wanna root it just now:

Files needed and a boot.img to apply with fastboot boot boot.img:

https://www.dropbox.com/s/nurzm8q3pqx2v4z/root_fire.zip?dl=0

Unzip the attachment and push the files directory contents to /data/loca/tmp using adb

Example: adb push Superuser.apk /data/local/tmp/

adb push su /data/local/tmp/

...

and then do the follwing in adb shell:

mkdir /system/app/SuperSU

chmod 0755 /system/app/SuperSU

chcon u:object_r:system_file:s0 /system/app/SuperSU

cp /data/local/tmp/Superuser.apk /system/app/SuperSU/SuperSU.apk

chmod 0644 /system/app/SuperSU/SuperSU.apk

chcon u:object_r:system_file:s0 /system/app/SuperSU/SuperSU.apk

mkdir /system/bin/.ext

chmod 0755 /system/bin/.ext

chcon u:object_r:system_file:s0 /system/bin/.ext

cp /data/local/tmp/su /system/xbin/su

chmod 0755 /system/xbin/su

chcon u:object_r:system_file:s0 /system/xbin/su

cp /data/local/tmp/su /system/bin/.ext/.su

chmod 0755 /system/bin/.ext/.su

chcon u:object_r:system_file:s0 /system/bin/.ext/.su

cp /data/local/tmp/su /system/xbin/daemonsu

chmod 0755 /system/xbin/daemonsu

chcon u:object_r:system_file:s0 /system/xbin/daemonsu

cp /data/local/tmp/su /system/xbin/sugote

chmod 0755 /system/xbin/sugote

chcon u:object_r:zygote_exec:s0 /system/xbin/sugote

cp /data/local/tmp/supolicy /system/xbin/supolicy

chmod 0755 /system/xbin/supolicy

chcon u:object_r:system_file:s0 /system/xbin/supolicy

cp /data/local/tmp/libsupol.so /system/lib/libsupol.so

chmod 0644 /system/lib/libsupol.so

chcon u:object_r:system_file:s0 /system/lib/libsupol.so

cp /system/bin/sh /system/xbin/sugote-mksh

chmod 0755 /system/xbin/sugote-mksh

chcon u:object_r:system_file:s0 /system/xbin/sugote-mksh

cp /system/bin/app_process32 /system/bin/app_process32_original

chmod 0755 /system/bin/app_process32_original

chcon u:object_r:zygote_exec:s0 /system/bin/app_process32_original

cp /system/bin/app_process32 /system/bin/app_process_init

chmod 0755 /system/bin/app_process_init

chcon u:object_r:system_file:s0 /system/bin/app_process_init

rm /system/bin/app_process

rm /system/bin/app_process32

ln -s /system/xbin/daemonsu /system/bin/app_process

ln -s /system/xbin/daemonsu /system/bin/app_process32

touch /system/etc/.installed_su_daemon

chmod 0644 /system/etc/.installed_su_daemon

chcon u:object_r:system_file:s0 /system/etc/.installed_su_daemon

Once all is done you need to fastboot boot boot.img again to establish proper perms to the new files. Actually we can't change ownership of files to root from adb.

Run this command in adb shell:

/system/xbin/su --install

Then reboot and voila! you are root.

Sorry for text format by chrome doesn't allow me to format it as code...
[Fire Android Development] Vlasp:
[MENTION=2511007]csolanol[/MENTION] said it does...
[Fire Android Development] csolanol:
Proof [emoji12] View attachment 3527438
[Fire Android Development] Awesomeslayerg:
chown 0.0 /system/app/SuperSU gives me operation not premitted
[Fire Android Development] csolanol:
Yup, i edited the post to delete that line. That ownership change will be applied when you reboot from fastboot with the custom boot.img again. Note the end of the post.
[Fire Android Development] KLit75:
Thanks. Damn i thought that'd get it done. But when i fastboot boot cm recovery it still says "waiting for device". Never struggled like this before. But youve given me a lot of good info that im sure will get me there.

Im a mac user and this pc is crawling so just opening a web page can take ages never mind trying to download files and waiting for a reboot.

Thanks ill look further into it.
[Fire Android Development] sd_shadow:
You used the full filename?
[Fire Android Development] KLit75:
I did. But sort of irrelevant because my pc just isnt communicating via fastboot. I tried fastboot getvar product and its still just waiting for device. What puzzling is the root batch is able to get the kindle into fastboot. I even tried using that just to go to fastboot then switch to another command window and fastboot cm recovery. And of course i did it manually with volume/power buttons. Even threw in my fastboot but still nothing.
[Fire Android Development] sd_shadow:
Shouldn't matter but did you boot to fastboot mode, then connect to the usb cable?
[Fire Android Development] KLit75:
So i was able to fastboot with my mac. Getvar product reveals FORD BUT after giving the command fastboot boot <recovery> it hangs on "downloading boot. Img"

I assume everythings ok because dnt think anythingvwas sent to kindle but anyone know whats going on? I didnt use the root script. Just tried ggow recovery
[Fire Android Development] sd_shadow:
it's not a boot.img https://www.androidfilehost.com/?fid=24269982086987951
[Fire Android Development] sandman512:
I know this is a big request, any chance of someone making a video on the second root process? While I have read the steps, I am not sure on how to do certain things. FWIW, I am so used to flashing ROMS on my phone and not familiar with doing it this way. Thanks!
[Fire Android Development] Xeddicus:
Well crap: Ran the script, it rebooted into fastboot and windows tried reinstalling the drivers. That failed and now it's gone from ADB and stuck in fastboot. PC won't detect it now even and can't reboot tablet. Reinstall the ADB drivers? Edit: Held the power down for long enough, it's seems to be booting..yay.... Ok, so now why does the script kill my ADB setup... lets try again later...

Media Device was checked in USB connections. Unchecked it and Windows tried to reinstall again and killed ADB once more, reinstalled the drivers and ADB is working with media device unchecked now. I'm guessing that was the issue?

It seems it WAS, but then it got the lock screen bit and couldn't find the device to push the files. I give up for now. Going to brick it at this rate with my luck... still showing up in ADB, at least.
[Fire Android Development] jdock:
I have successfully rooted my new fire. Some notes about my issues that may help someone:

1. had to follow the process in this thread: http://xdaforums.com/showpost.php?p=63642822&postcount=8 to get adb to see my fire.

2. The script tells you how to enable adb on the Fire when you run it, in case you don't know how... of course, by the time I ran it I had already been through that :)

3. After the first fastboot, my computer didn't automatically recognize the device which I found out the hard way when I pressed any key. When I re-ran the script, this time I unplugged it and plugged it back in at this point, and made sure it showed up in "adb devices" (run in another window) before continuing with the script.

4. When it went into the second fastboot, my computer didn't recognize it again but I accidentally hit a key in the wrong window so the script continued and failed again. I re-ran the script and got errors because SuperSU was already there, but of course this isn't a problem and the rest went without incident.

---------- Post added at 03:35 AM ---------- Previous post was at 03:32 AM ----------

If you're using windows, it may be helpful to view your device manager in "by connection" mode. I noticed that in fastboot, the device manager entry turned into some unrelated cell phone. ADB can't communicate with fastboot so that's not a problem. And as I said above, I also had to unplug and plug the fire each time it booted back up in order to get adb to see it at that point.
[Fire Android Development] csolanol:
Actually the easiest way to root this device is using a custom recovery.

Download TWRP.

Download SuperSU

If you download these files on the computer upload them to the device internal memory or to the sdcard.

Reboot your device in bootloader mode: Turn off the device and start it with power and Vol+ pressed.

Connect your device to the computer and confirm that you can see it typing fastboot device in a cmd window.

Once you see your device boot it with this command: fastboot boot TWRP_Fire_recovery.img (be sure that you are in the same path as the img file).

Device will boot in TWRP recovery, just flash SuperSU zip and reboot.

You are done.

Note: You can get all the power of busybox installing Stericson Busybox from PlayStore.
[Fire Android Development] jco23:
I dunno know. That one-click bat file is pretty darn easy.

For me though, I ran the "install Google play store" script prior to root. Everything worked out perfectly.
[Fire Android Development] csolanol:
Yeah but people is getting in troubles with drivers after rebooting. So this way you only need a fastboot reboot and it's done.
[Fire Android Development] sandman512:
I understand everything but this:

Once you see your device boot it with this command: fastboot boot TWRP_Fire_recovery.img (be sure that you are in the same path as the img file)
[Fire Android Development] csolanol:
Should be this way:

Once you see your device, type this command: fastboot boot TWRP_Fire_recovery.img.

Enviado desde mi Nexus 5 mediante Tapatalk
[Fire Android Development] sandman512:
Ok, thanks.
[Fire Android Development] sd_shadow:
my video 2015 Fire: Booting TWRP, Rooting, Installing Gapps

[YOUTUBE]RIqmpnhh1Hs[/YOUTUBE]
[Fire Android Development] Xeddicus:
That did it. Thanks!

[MENTION=5933283]Awesomeslayerg[/MENTION] May want to add a note to the bat file/OP to unplug the Fire and plug it back in if it vanishes from Device Manager between steps.
[Fire Android Development] topcaser:
Hi, I use Nova as my standard launcher. If I want to add the pure calendar widget, I will be ditected to the Fire's settings page instead to the widget's setting page. Is there a workaround for this?

Gesendet von meinem KFFOWI mit Tapatalk
[Fire Android Development] niphoet:
I have the same issue adding a widget in Action Launcher. Guess we'll have to wait for a CM/AOSP Rom.
[Fire Android Development] zelet:
To get widgets to work you have to move your launcher to system.
[Fire Android Development] topcaser:
Ok, just another question. Again and again I get after launching Tapatalk the message whether I want to turn on location tracking (Don't know, whether this is the right english word) since Tapatalk want to track it. Is it possible to deactivate this, since this is very annoying.

Gesendet von meinem KFFOWI mit Tapatalk