yashsingh1/xdaforums huggingface dataset:
[Verizon LG G3] phr00t:
I got an LG G3 that came packaged with 35B (5.1.1), and nothing seemed to be working to get TWRP installed. I couldn't use LG Flash Tools to downgrade using the "TOT" method, because it'd stop with an "no ks version" error. I finally found something that works, and I'm now running AICP (nice ROM) with TWRP installed!

The trick is to follow these instructions (make sure you use VS985 components for our Verizon LG G3s, not D855):

http://xdaforums.com/lg-g3/help/help-secure-boot-error-trying-to-boot-t3054977

Overwrite aboot.img (12B version) & recovery (TWRP image) using dd commands via an adb shell, after rooting with KingRoot, while Android is running. I then used adb commands to reboot into recovery, and volia! I was in! I had AICP on my internal card, and the 12b bootstack, which I flashed in that order.

After seeing AICP successfully boot, I went back and flashed the 35B bootstack. Success!

Stock images (aboot 12B etc.): http://xdaforums.com/verizon-lg-g3/general/reference-stock-img-files-t2966958

Bootstacks: http://xdaforums.com/verizon-lg-g3/development/xdabbeb-s-vs980-2-0-0-t3231279

KingRoot: http://xdaforums.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
[Verizon LG G3] roirraW "edor" ehT:
Great news for you and others. Thanks for sharing!
[Verizon LG G3] fast69mopar:
Well, i tried to follow this step by step and I ended up with a black screen after reboot. My G3 would power up, blue and green led's would flash like normal, I could hear the sounds being made by pressing the power button and touching the screen just like everything went as planned except for a black screen. My PC still recognized my device when Android was running and it was still detected when I entered download mode. I could see the device driver installation window popup on my PC and I could see my G3 in my Device Manager as well. I am a little unsure about what went wrong but I am doing my research to see if I can solve this problem. The good thing about the whole situation, I was able to use LG FLashTools 2014 to KDZ back to 35B which is what I was running at the beginning of this process. The software flash just finished and so did "Android is starting" so I will set this thing back up and try again once I find out what went wrong and why I received the black screen afterwards. If anyone can provide any input as to what my have happened or if there was something I missed I would appreciate it.
[Verizon LG G3] phr00t:
Weird... this is what I did (nothing more):

1) Pick a ROM I wanted to use. I went with AICP nightly for VS985 (MM 6.0.1). Put that ROM zip to be flashed by TWRP on your internal memory.

2) Put the 12B bootstack on internal memory.

3) Put the 12B aboot.img & latest TWRP img on internal memory.

4) Root with KingRoot

5) Open up an "adb shell" and use "su" to get a root shell.

6) Use dd commands (like in the original post's link) to zero, flash aboot & the recovery image to their proper partitions.

7) Use "adb reboot recovery" to boot into TWRP

8) Factory reset

9) Flash ROM (AICP etc.)

10) Flash 12B bootstack (not 100% sure needed, but whatever)

11) Wipe cache/dalvik (not 100% sure needed, but whatever)

12) Reboot & profit!

After seeing successful boot, I did go back into TWRP & flash the 35B bootstack, just to have the latest stuff that still does work.

I *did* have one oddity where my screen went black, but NOTHING was responsive (not even the LED). Phone just appeared completely dead -- no response to anything. I pulled the battery, and it booted up fine. Hasn't happened again...
[Verizon LG G3] fast69mopar:
It was weird indeed. I flashed the 35B KDZ to return to stock after the screen went black. I was already on the stock 35B OTA that I received back in October. I was already rooted with Kingroot and had already removed Kingroot with SuperUser in its place. Was that something that was different between us maybe? Were you on the stock 35B, unrooted, before you started the process? Like I said, I was already rooted. Don't know if it makes a difference or not. Since I was able to flash back to stock after the mishap I will be trying it again here shortly when I get back in from of my Laptop. I am fully stock right now and my software status is official. I will do the process over again starting with a fresh template. I'll edit my post with an update after I'm finished. Thanks for the response and for the guide.
[Verizon LG G3] phr00t:
I was on a "fresh", unrooted flash of the 35B KDZ after some previous failed attempts to get TWRP installed. Then, I started my steps listed above. I didn't swap out KingRoot to SuperSU (since I knew it'd just be overwritten when AICP gets installed). Just needed root to flash aboot & recovery.
[Verizon LG G3] evohog:
What command did you run to flash the twrp img, in the other link with the commands of says he used flashify but you used terminal to flash yours. Thanks.
[Verizon LG G3] jimtom1948:
It works.

New here, also with VS985 35b. LG Flash tool kept giving me failed previous flash on every attempt to downgrade to 10b. Saw this and using the same aboot.img and bootstack.zip that you used, I used terminal emulator to update and it worked first time. I just had to remember to use VS985 components including twrp. Everything is now running, and am so thankful. My first G3, previously rooting and playing with Samsung S4. Again, thank you for your incredible work.
[Verizon LG G3] evohog:
You mind giving m the exact commands you used and the order you did everything in? Got a little confused going from thread to thread to get everything downloaded. Think I read too much.lol confused myself
[Verizon LG G3] jimtom1948:
Evohog

1) Started on this site and downloaded:

Stock image (aboot.img 12b)

bootstack (12b) down the page in downloads.

This is important because the instruction page is for D855 and you need VS985 aboot and bootstack. This was what initially confused me.

2) I then went to the page that says follow these instructions.

Here I downloaded oversharpening fix flashable zip and a twrp recovery for VS985.

You will want to substitute VS985 aboot and bootstack for the D855 in his writeup.

3) I followed the rest of his tutorial, very carefully typing the commands into terminal emulator. (I haven't got my linux machine ready for adb yet.

4. Shut down the phone. rebooted into recovery (You can use flashify settings to reboot into recovery, or the buttons on back of the phone after shutdown.

5. It worked, I was in twrp. Flashed the oversharpening and the 12b bootstack.

Hope this helps.
[Verizon LG G3] evohog:
One last question, where in the commands it says "block/name/a boot" so I enter vs985 where it says name or do I enter name. I'm so rusty,it's been a couple years since I've even rooted anything. Thanks again for the hand holding.
[Verizon LG G3] jimtom1948:
Evohog

If you are talking about the commands that you type into the terminal emulator, you enter them just as they are written, except for what is in quotes. Don't change them. Good Luck.
[Verizon LG G3] johnny567:
Hey guys, Tried this and now im hard bricked. Could anyone give me a hand? I have everything posted here.

http://xdaforums.com/verizon-lg-g3/help/kdz-restore-t3315170/post65328929#post65328929
[Verizon LG G3] jimtom1948:
johnny567

I was successful twice with this method. The third time, it bricked so hard I couldn't even get into download mode. After a ton of reading, I found a recommendation in

verizon-lg-g3/general/restore-verizon-to-stock-t2827878/page24 no. 236 by jhtrades 1 at the bottom of his recommendation (ALT METHOD #2).

http://xdaforums.com/verizon-lg-g3/general/how-to-hardbrick-guide-using-test-t3276928. I followed along starting with step 6, no wire, and somehow got the phone back to a version of verizon with a problem in the bootloader. At least, I was able to get into download mode and did a KDZ to 10b. After that everything was back on track.

I am not absolutely sure if this will work for you, or exactly sure what I did, but it's the best I can come up with. All I remember at the time, was it seemed complicated. Good luck and hope you get it back and working.
[Verizon LG G3] johnny567:
It doesnt seem to be working for me. It is pulling up as the Qualcomm 9008 and i have tried with and without wire. It keeps failing and I end up with the error "No response from the device. Check PMIC first and if still boot problem replace AP." I noticed that I have a vs985k. Do you think that could contribute to the failure?
[Android General] Thalarajacse:
Hi dev,

Any body tell me how to create android spy app[emoji2] [emoji2]

Any doubt or help please PM me.
[Android General] Perseus:
Against XDA rules.

Closed.
[JASJAR, XDA Exec, MDA Pro ROM Development] Timeshell:
I have a new issue with my backlight. I didn't really see anything scanning a search on backlight so I'm hoping someone has seen this before and can help.

I just got a new 3200mah battery. Ever since I started using it, after turning off the device, I go back to it, press the power button or backlight button and while the screen itself comes on, the backlight does not. No light at all. I also often find that the screen is on already when I open the phone (which might explain why my battery is sometimes finding itself dead in a matter of a couple hours).

Please, if you are familiar with this can you offer some direction?

Thanks
[JASJAR, XDA Exec, MDA Pro ROM Development] Timeshell:
Wrong title on this thread

Ooops...sorry for the double post.
[Droid Turbo 2 Android Development] Arasthel:
<IMPORTANT>: PLEASE DON'T USE THIS RECOVERY, USE XADRO'S INSTEAD

This recovery has become outdated and can't do some prop checks to assure that flashable files are meant for kinzie. Please use @xadro's Kinzie TWRP instead. It's updated, has bugfixes and may be official soon :)

</IMPORTANT>

Hi everyone!

Yesterday, after being helped by [MENTION=4630246]Hashbang173[/MENTION], I was able to build Moto X Pure recovery. I was planning to add the flip screen flag to make it compatible with the X Force, but after trying it out on my device the problem was gone, I didn't have to modify anything, just build the recovery as if it were a normal Pure X version.

Screenshot:

Download:

So here you have a link to the fixed recovery: recovery-2.8.7.0.img (MEGA)

Support:

I'm not an active AOSP/CM/TWRP developer and I don't have lots of time to fix stuff. I'm sharing this because it works for me, but don't expect any bugfixes from me or to take resposibility if anything goes wrong. It's unofficial for a reason.

I hope you all enjoy it!
[Droid Turbo 2 Android Development] Arkaknio:
Thank you very much sir!
[Droid Turbo 2 Android Development] BladeRunner:
Very nice and just in time; my Force is sitting in my mailbox right now. I'll flash this later this evening and report back.
[Droid Turbo 2 Android Development] rodrigoger:
Amazing! Testing right now!!!

Enviado de meu XT1580 usando Tapatalk
[Droid Turbo 2 Android Development] Jaocagomez:
so much needed, will make rooting easier.

thanks for your effort.
[Droid Turbo 2 Android Development] BladeRunner:
Everything that I've tried seems to be working so far. Haven't attempted to restore a backup yet.
[Droid Turbo 2 Android Development] rodrigoger:
I just did and worked, easy like a piece of cake!
[Droid Turbo 2 Android Development] MuyKurioso:
System reboot

Whenever i press the Reboot-System it just gets stuck. Is this normal, or something's wrong with my device?
[Droid Turbo 2 Android Development] Arasthel:
It works fine for me.

The same happened to me when using the Pure X recovery we had until now. I can't say what the problem might be. Maybe you should try [MENTION=3928411]Xadro[/MENTION] 's recovery, as he did build it from scratch for this device.
[Droid Turbo 2 Android Development] rodrigoger:
I'm using [MENTION=3928411]Xadro[/MENTION]'s version. It works perfectly.

Enviado de meu XT1580 usando Tapatalk
[Droid Turbo 2 Android Development] Arasthel:
Updated first post with a warning. Please don't use this recovery anymore, please flash Xadro's TWRP recovery instead.
[T-Mobile Samsung Galaxy S6] Droidmissionary:
Was wondering if anyone has a picture of the default tmobile s6 build.prop specifically the device. Name section. I recently flashed arrow rom in the unified development . I am now having issues running apps like mint and wonder if because it switched my device name if that is why. Ty in advance
[T-Mobile Samsung Galaxy S6] tocirah1:
Here ya go.
[Lava Iris 504Q] harshpreets63:
Features

1.SIM 2 3G WORKING. NOW ITS DUAL 3G - FIRST FOR MT6582

2. Beautiful MIUI 7 - Global beta

3. Online themes,wallpapers,ringtones,etc..

4. More Battery Efficient,Smooth

5. Extra Reboot Options

6. Modded dialer , settings , In Call UI and new File manager

7. Good Camera Quality

8. All Unwanted/chinese MIUI apps Removed

9. Play Store working

10. Modded launcher

11. Based on 6.1.21 Global beta [4.4.2 based]

12. Dirac HD working

*****And Much More*****

---Installation instructions---

You must have twrp

Reboot to twrp

wipe menu-> preflash wipe option

Install ROM zip from sd card

Reboot

Please Hit thanks/like ,if you think my ROMs make your Phone UI better

Credits:-

BATSILOS(INEW V3 DEV)

MEEEE

Download Link

https://drive.google.com/file/d/0B26H9lJd3tLSQW1aSlZ1eVFyOHM/view

Screenshots:-

View attachment 3630125View attachment 3630126View attachment 3630127
[Lava Iris 504Q] anmolkakkar:
Link not working! Can you please re-share?
[Lava Iris 504Q] harshpreets63:
sorry for problems u faced.........

links updated............enjoy.....hit like ...
[Lava Iris 504Q] Preshak:
Please Tell me

1.how to root (kingoroot or iroot).

2. Provide cwm or twrp .

3.how to check if my bootloader is locked ot not.

4.Rom looks amazing.
[Lava Iris 504Q] zender_dj:
link not working please reshare this rom
[Lava Iris 504Q] RaviP6182:
Link not working, can you please re-share?
[Lava Iris 504Q] jacky03:
link please,very well
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] jedisurfer:
Qi doesn't seem to work well through my case (Verus Damda Slide which also houses 2 credit cards). Wondering if anyone has used the Powermat PMA and if that charges through cases better? Thanks
[Android Q&A, Help & Troubleshooting] venkatesh00:
The phone comes with all the GAPPS except that Google play services and i need it to sync my Clash of Clan account.

My phone is rooted

I have tried:

Installing it from Play store:

Installing it manually from downloading by playstore: App not installed.

Installing old signed version: App not installed.

It also have android recovery i tried to install the whole GAPPS package but the it shows the signature verification error.

I dont have a custom recovery no idea how to install it.

let me know to change custom rom step by step in lava iris x9
[Android Q&A, Help & Troubleshooting] Manu46:
⚀ root your device by kingoroot (link below)

⚀ download and install root explorer (link below)

⚀ download 'google play games.apk' (link below)

⚀ create a folder 'PlayGames' and copy the downloaded apk inside it

⚀ copy the folder 'PlayGames' into the 'system/app' directory by root explorer

⚀ set the folder permission 'rwxr-xr-x'

⚀ set the apk permission 'rw-r--r--'

⚀ reboot your lava iris x9.

⚀ enjoy google play games.

Downloads

⚀ KINGOROOT- https://root-apk.kingoapp.com/kingoroot-download.htm

⚀ ROOT EXPLORER- https://mega.nz/#!uZclSZBC!kkZxhEWI2qel6x3cbw4UWAjIPVj6Gn3sWEgTjnt2xFU

⚀ GOOGLE PLAY GAMES- https://mega.nz/#!nRtBkZBJ!D6o3sFp6ArVin8470e72Mh2VPdR4y8C8aORDcIQxy2o

it worked fine for me

im not responsible it anything goes wrong in your case

Good Luck
[Android Q&A, Help & Troubleshooting] arlitoisolis:
⚀ set the folder permission 'rwxr-xr-x'

⚀ set the apk permission 'rw-r--r--'

how can i do this?
[Shield Android TV Q&A, Help & Troubleshooting] themystical:
Tried the USB audio out to a couple of external DACs and both have pops and clicks. It appears like the Shield up samples everything to the max capability of the DAC up to 192k. This causes random unlocking of the signal to the DAC causing the pops and clicks. It also prevents the transmission of bit perfect audio to the DAC.

Does anybody know of a way to switch off up sampling in the Shield so that it plays the native sampling rate of the source? Is there some way of "conning" the Shield during the USB handshake?
[Shield Android TV Q&A, Help & Troubleshooting] themystical:
Response from Nvidia customer service:

We're sorry, unfortunately there is no option for Manual control upsampling or downsampling with External Digital to Analog Converter on Shield Android TV.

Any help appreciated!
[Shield Android TV Q&A, Help & Troubleshooting] rbinary:
Thanks for posting this. I have similar issues using a NAD D3020 amp as my DAC. If there's constant audio it's fine, but whenever the SHIELD idles for a bit the next sound (e.g. scrolling through menus) is a loud crackle/pop.
[Shield Android TV Q&A, Help & Troubleshooting] themystical:
This is sorted now with the 3.0 update. It is now possible to select 192k or 44.1k audio output through settings.
[Shield Android TV Q&A, Help & Troubleshooting] AngelHeart:
Hi all,

I just saw this thread about USB DAC. My problem is slightly different.

Indeed, FW 3.0 just improved USB DAC compatibility within Android. Still, a new problem arises within Kodi.

With 2.1 FW, I could use my Rega DAC (it is passthrough compatible). AC3 and DTS were sent to my AV receiver perfectly (passthrough working under Kodi).

With 3.0, I can no longer use my Rega DAC under Kodi. Passthrough is not functional within Kodi. I have ugly white/pink noise instead.

So now I'm left with no possibility to let my DAC passthrough the audio to my receiver. This is really boring since my receiver has no USB in, and requires my DAC to passthrough via optical cable.

Good news is improved compatibility under Android system : my other high-end DAC now works with 3.0 (impossible under 2.1) although it is not passthrough compatible.

So my question : what's wrong with the 3.0 update related to USB device or audio passthrough within Kodi ?

Anyone with a hint or solution ? Thanks by advance.
[Shield Android TV Q&A, Help & Troubleshooting] krazystuff:
First post here, I had a related issue where I had to modify audio_policy.conf in order to get DTS to passthrough to receiver via the TV's optical connection (Shield to TV to Receiver). That problem was related to the TV's EDID not reporting DTS capability, even though it technically works (probably omitted due to licensing fees). Anyway, in \system\etc\audio_policy.conf, there was also a setting for USB passthrough. You may be able to manually enter the formats to passthrough instead of relying on "dynamic", which relies on polling the device what it supports. (requires root access to edit this).
[Shield Android TV Q&A, Help & Troubleshooting] AngelHeart:
Thanks for advice.

I'll check this and come back after rooting my SATV :)
[Shield Android TV Q&A, Help & Troubleshooting] AngelHeart:
settings

Hi,

I've not been able to root my device, since root is difficult to perform with 500gb version added to 4K TV (TWRP not compatible).

Still, seems like USB passthrough is set to "2". Apparently "0" means disabled whereas "1" is activated (correct me if I'm wrong)

So, do I have no choice except from root ? If you have any clue about this, could you please keep me in the know ?

Thanks in advance,
[Shield Android TV Q&A, Help & Troubleshooting] bbqdrew:
Pops and clicks

I just put in a Turtle Beach Audio Advantage Micro II USB Analog & Digital Audio Adapter. Works just fine like people are saying but when no audio is going on the led on the Micro II goes off. Then when there is anything, even system sounds it kicks on the LED turns on and my speakers pop loud. Has anyone figured a fix or is this just USB audio. And is an HDMI audio puller a better solution for simple stereo 2.1 setup? Or does that pop too?
[Shield Android TV Q&A, Help & Troubleshooting] bbqdrew:
OK. Think i found a temp fix. When using USB DAC direct to an analog source it kept popping because it was sending live signal to hot amp every time USB DAC would come back from standby. SO how to keep DAC from sleeping when no sound was live, I installed VirtualHere USB Server From the TV Play store. Checked always as this was only USB device i had plugged in. Then went to setting and only checked Start On Boot. Since then after full restart DAC stays on, LED stays lit and sound is always on. No more pops.
[X 2014 Q&A, Help & Troubleshooting] JarJarWinks:
Hello there, my Moto X 2014 is just over a year old and I am facing this unusual premature burn in across the length of the display.

This should not happen so early and the Moto Service Centre is quoting Rupees 15000 ($250 approx) to replace it for me. :/

I am extremely unhappy with this issue and would like some help.

Thanks in advance!

https://drive.google.com/file/d/0B0zJB_FYnkDBZUFKLURhOVVFeWM/view?usp=sharing

https://drive.google.com/file/d/0B0zJB_FYnkDBOTM5bk9GajdYWFk/view?usp=sharing

EDIT - The pictures aren't too clear (Taken with my Nexus 7) so I'll try to upload clearer ones when the sun rises tomorrow.
[Android Q&A, Help & Troubleshooting] tim687:
I have been started building a rom for the Huawei Ideos S7 a couple of days ago. The first build of the rom (based on another source) did not work.

And this rom (based on PAC-ROM) is not building due to an error:

build/core/package.mk:234: recipe for target '/media/android/source/cm10.1/out/target/common/obj/APPS/Trebuchet_intermediates/src/R.stamp' failed
make: *** [/media/android/source/cm10.1/out/target/common/obj/APPS/Trebuchet_intermediates/src/R.stamp] Segmentation fault (core dumped)
make: *** Waiting for unfinished jobs....

/media/android/source/cm10.1/out/target/product/s7/pac_s7-ota-eng.android.zip doesn't exist!

The rom is based on Android 4.2.2 (CM-10.1)

I tried Googling this issue, but I didn't find anything.

Could anyone help me out with this issue?

Thank you in advance,

Tim
[Sprint LG G3] blkdimnd:
I was running Bare-Bum on my Sprint LG G3 for a while, but have noticed some bad GPS issues.

I decided to flash back to stock to see if the would fix the issue, but I have run into another problem.

After following the steps HERE I was back at stock but was unable to activate the phone on Sprint, using the handsfree/auto activation.

I noticed that the following were reset/different in the About Phone/Status menu:

Phone Number - Not correct

MIN - Not correct

MEID HEX- Not Correct

MEID DEC - Not Correct

I was able to use my MSL number to set the Phone Number and MIN, but I still can't register the phone with Sprint.

Can any one tell me how to change the MEID? I'm hoping that that will allow me to get the phone working on Sprint.

Thanks in advance.
[Sprint LG G3] blkdimnd:
[SOLVED]

Well I fixed my issue.

After flashing back to Stock I rerooted the phone and restored my backup of BearBum.

Got it all working. Now to figure out how to get back to stock without having the above issue...
[Sprint LG G3] andrewwm:
Flash back to stock and do a PROFILE update and PRL update.

Edit: try this too "##UPDATE#

or

##SCRTN#

or the biggie - which fixes bootani and Wifi calling

##RTN# - requires your MSL. "
[Sprint LG G3] j83holmes:
I have this same issue and now I need help. can you tell me what you restored or are you willing to share your solution?
[Sprint LG G3] stickwithme:
I'm having this problem too. I followed the directions to revert to stock, exactly. None of the dialer codes work. PRL and Profile updates both give errors. I can factory reset in settings, but it just takes me back to the beginning, still no codes or activations work.

---------- Post added at 08:52 PM ---------- Previous post was at 08:48 PM ----------

How were you even able to do that? My MSL is all zeroes. The CDMADevTerm tool says my SPC does not exist (???).