yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S7 Edge Questions and Answers] squallz506:
Thank you! Is there any way to remove it completely? I'd rather not have two square inches of useless bloatware in my notification shade.
[Samsung Galaxy S7 Edge Questions and Answers] jtw_111:
I don't think there is, unfortunately :\
[Sprint LG G3] Kasual52e:
CyanogenMod is a free, community built distribution of Android which greatly extends the capabilities of your phone.

[IMG="CyanogenMod Logo"]http://cyanogenmod.org/wp-content/themes/cyanogenmodv3/images/logo.png[/IMG]

#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* CyanogenMod members or anyone else on this website is
* not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the
* alarm app failed. Please do some research if you have
* any concerns about features included in the products
* you find here before flashing it! YOU are choosing to
* make these modifications, and if you point the finger
* at us for messing up your device, we will laugh at you.
* Your warranty will be void if you tamper with any part
* of your device / software.
*/

This is a nightly build of CM for the LG G3 on Sprint (ls990).

All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review.

If you want to help out follow the building guide and then submit a patch to our Gerrit instance.

Installation Instructions:

*NOTE*: You must be Bump'd for this to work. This requires flashing via custom recovery *TWRP* for "ls990”.

1. Download this ROM and 6.0 GApps (recommended Open GApps here). You are going to need to use the Marshmallow ones, this is 6.0)

2. Put both on Internal Storage

3. Reboot into recovery

4. BACKUP CURRENT ROM

5. Factory Reset/Wipe if not already on CM13

6. Flash CM13 (no need to wipe System)

7. Flash GApps 6.0

8. Reboot

9. wait... wait... wait...

10. Profit

To get root/SU, enable Developer Options and change "Root Access" options.

Nightly builds *http://get.cm/?device=ls990.*

Working:

Almost everything

Known issues:

Bluetooth for some users

NFC – not working at the moment

??? - list any others and I will try to get them working as I have time

@invisiblek does most of the work for this device series, much more credit goes to him than me, I just focus on the ls990.

CyanogenMod Blog

CyanogenMod Wiki

CyanogenMod Community

CyanogenMod Forums

CyanogenMod Google+

CM Download Page for ls990
[Sprint LG G3] mjjcb:
Been on this for a month, and it's without a doubt more stable than anything else I've tried on MM. Some things don't work, like NFC, but they don't work on any current rom. It never shuts down randomly like others I've tried and keep up with. Nice job. I'll take stability over glitchy features every time.
[Sprint LG G3] Disillusioned:
Got No SIM Card detected on this build, trust its because of baseband version.

Has anyone got CM13 and CM12 baseband dumps?

Any solution to No SIM Card?
[Sprint LG G3] allanlgz:
Been trying official build since they came out, cannot get LTE. Only 3G. I am on ringplus if it helps.. I am on newest lollipop baseband from zvc. Tried editing apn.config xml, airplane mode, changing network modes. All I get is 3G. I did find by flashing an apn fix for ringplus I get lte but for carrier it says Digital roaming instead of aprint.. Is it my device or is it the rom?

Lte works fine on stock lg roms. Everytime i flash TOT back to stock i have to do an rtn reset to get lte back though it gets stuck on 3g. Did clean flash btw every nightly wiping internal,system, data dalvik and cache
[Sprint LG G3] Kasual52e:
Try to do a full wipe and flash again. I haven't had any problems with it detecting my SIM. Worst case flash to stock ensure everything works and then flash back to CM.

In general mine stays on Domestic Roaming but that depends on how you are connected to the network. Every once in a while mine will show Sprint. Also you don't need to wipe prior to flashing nightlies unless you are experiencing issues.
[Sprint LG G3] golpeen420:
Been flashing the nightlies since day one of release, and this by far the most stable, fast, overall amazing MM rom I've seen. Smooth as silk even with the stock kernel
[Sprint LG G3] jesus.sea:
flashed last nightly, almost all apps force close, rom is unusable, flashed twice. And no GSM signal
[Sprint LG G3] syndre:
are you sure you have a LS990?
[Sprint LG G3] jesus.sea:
Yep!, it was my bad, i was coming from fulmics and had adaptive storage enabled, that was causing the force closes, i guess a problem with teh encryption, just set to forget the storage and everything was OK with the apps.

For the signal issue i had to flash the GSM patch and worked again.

i'm on LS990 using GSM Network on Mexico
[Sprint LG G3] billbowers:
Really enjoying the ROM. Thanks for this.

One question... I'm on sprint ls990 and my data speeds have dropped. Considerably. Is there a fix for this, or something I didn't do on my end when flashing? Thanks.
[Sprint LG G3] pwlamb79:
Great ROM! No issues with nightly updates at all. Best ROM I have used on this phone..clean flashed with bumpd TWRP...looking forward to new updates..Thanks!!
[Sprint LG G3] l_4Fhit_l:
Are there any running issue for those using this ROM on the current build besides whats posted? I'm getting horrible dropped calls on RR.
[Sprint LG G3] Jguff5:
Anyone figure out how to get SuperSU updated?
[Sprint LG G3] Kasual52e:
You might try updating your PRL and see if that helps at all.
[Sprint LG G3] Saadssk94:
gsm sim not working any fix?
[Sprint LG G3] l_4Fhit_l:
I think that might have worked! Thanks man
[Sprint LG G3] Srambo217:
Anyone else getting a force close with their Clock app when their alarm goes off? My alarm still works, but I'm worried it'll close itself and make me late for work.
[Sprint LG G3] Srambo217:
Ok, fixed the clock issue by freezing the Clock app and redownloading it from the Play Store.

I've noticed I can't make any in-app purchases with this ROM. I wiped my cache/davlik and flashed a newer version of GApps which didn't work, I then installed a newer apk of Google Play Services and that caused a force close issue, I wiped everything, reflashed the new version of GApps and now I'm back to square one. Not sure what I can do from this points, any ideas?

Edit:Figured it out! Lucky Patcher was messing my store connection up somehow. Froze it via Titanium Backup, cleared the data/cache from the Play Store app, and now everything is working.
[Sprint LG G3] allanlgz:
Anybody have the issue of their display being too dim?

On lowest brightness, display is barely visible even in complete darkness. Highest brightness is fine for indoor but outdoor its too dim

Yes, adaptive brightness is off. I am on LS990, latest 3/19 nightly. Did not have this problem on stock, brightness was fine both at lowest and highest.
[Sprint LG G3] Kasual52e:
Setting > Display & lights > Brightness level is set to what you want

Setting > Display & lights > Adaptive brightness is disabled

Setting > Display & lights > LiveDisplay > Display mode is set to Off

One of those three should do it for you.
[Nexus 7 (2013) Q&A] noahvt:
Hi,

Recently, I installed ubuntu touch on my device and thought that it used an image so I tried to rm -rf / to remove it but now my entire tablet is jacked up:/ Here are the problems:

Device doesn't boot into any rom (yes I have flashed the factory images and they don't boot either)

Fastboot and recovery both work fine but no matter what rom i use it always hangs on the bootanimation with no logcat and the only thing that appears on my computer is unable to mount nexus 7

Does anyone know how I can fix this?
[Nexus 7 (2013) Q&A] k23m:
I think I have a (untested) solution but first please post the output of the following commands:

fastboot oem device-info

fastboot getvar all

fastboot oem gpt-info​
[Nexus 7 (2013) Q&A] k23m:
Please boot to TWRP and run these:

adb shell mount > twrp.txt
adb shell blkid >> twrp.txt
adb shell fdisk -l /dev/block/mmcblk0 >> twrp.txt
adb shell cat proc/partitions >> twrp.txt
adb shell head /sys/block/mmcblk0/device/* >> twrp.txt
adb shell cat /tmp/recovery.log >> twrp.txt
adb shell ls -la /dev/block/platform/msm_sdcc.1/by-name/ >> twrp.txt

Then attach twrp.txt here.

The next step is risky so we have to do a full eMMC backup first.

download p0.zip from my files

save it on a 32GB+ ExFAT formatted flash drive

boot TWRP

attach OTG adapter with the drive

'install' the p0.zip - it will image your entire N7 eMMC to the root folder of the flash drive

A smaller drive may work but it all depends on what was stored on your N7. A few gigs will image in around 15 minutes.
[Nexus 7 (2013) Q&A] noahvt:
Here is the twrp.txt file: View attachment 3679730
[Nexus 7 (2013) Q&A] k23m:
Thanks. It looks like a 4GB drive for backup will do. The data partition was TRIM-ed during wipe and is full of zeroes which compress nicely :)

/data | /dev/block/mmcblk0p30 | Size: 27047MB Used: 102MB Free: 26812MB Backup Size: 102MB
[Nexus 7 (2013) Q&A] noahvt:
I used a 16gb drive and the backup should be almost done

EDIT: it's done, do I have to upload this image for the next step?
[Nexus 7 (2013) Q&A] k23m:
No, it's your backup. Just verify it, uncompress it on your PC, see if it's now 32GB big.

We have identical Hynix eMMCs and I imaged mine in working condition. I did it with with erased boot, cache, system and userdata, so the compressed 32GB image size is remarkably small - just 53MB and I will upload it for you to do the reverse dd operation.

But we need to pause and wait for forum's opinions. This method has never been tried on N7 I think, it may kill the bootloader completely and then only JTAG can rescue your N7. Perhaps there is a safer fix for the problem. So let's wait a day or two for posts from other users, OK?
[Nexus 7 (2013) Q&A] k23m:
Please use TWRP or extract from the image and upload only the small mmcblk0p4 partition for inspection...

/dev/block/platform/msm_sdcc.1/by-name/persist
/dev/block/mmcblk0p4
[Nexus 7 (2013) Q&A] noahvt:
Here is the partition: Persist
[Nexus 7 (2013) Q&A] k23m:
This is it - the partition is erased - wow - your easy and safe way out of 'rm -rf /' :laugh:

TWRP does not care about /persist but your OS is freaking out on it. The files/folders are still there but they need to be

undeleted

. I suggest you try this first, otherwise I will clone my /persist for you. Cloning it does have some minor privacy implications but more importantly this partition holds calibration and preset data for your N7's HW components and might slightly impact their performance I suspect.

Tell me if you want my mmcblk0p4.
[Nexus 7 (2013) Q&A] noahvt:
Yeah lol, I'm happy that's the only thing that got nuked lol I cancelled the operation soon enough to not wipe out the bootloader or other partitions xD can you send me your persist partition?
[Nexus 7 (2013) Q&A] k23m:
OK...

copy the 2 files to the root folder of a flash drive

boot TWRP and connect OTG with the drive

'install' p4-restore.zip

Then boot your OS :fingers-crossed:
[Nexus 7 (2013) Q&A] noahvt:
It worked! Thanks a lot man!
[Nexus 7 (2013) Q&A] k23m:
Cheers!

I will add your Hynix to our collection (of OK eMMC).
[One (M8) Q&A, Help & Troubleshooting] rockfordpi:
This is an ATT version phone I rooted this phone a couple of days ago with TWRP. However, I had to use adb to enter fastboot as it would not go to fastboot using power/volume keys. Actually, it never shows a fastboot screen, even in adb, so it may have been going into fastboot all along and I just could not see it.

So, instead of leaving well enough alone, I RUU'ed (newest ATT version from HTC site) it to try to get fastboot to work normally (it still works, I just can't see it on screen). Now, I can't get rooted again. FWIW, I did make a backup with TWRP before RUU'ed. Regardless, there is nothing on this phone I need to keep, I just want to root it before I start using it.

Any help is greatly appreciated...

Here is my unlock sequence. Note what happens if I try to flash TWRP immediately after unlock. I have to CTRL C and Reboot phone.

C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash unlockt

oken unlock_code.bin

target reported max download size of 1826414592 bytes

sending 'unlocktoken' (0 KB)...

OKAY [ 0.110s]

writing 'unlocktoken'...

(bootloader) unlock token check successfully

OKAY [ 0.012s]

finished. total time: 0.125s

C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recover

twrp30m8.img

^C

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot bootloader

Now when I try to flash TWRP, I get :

C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recover

twrp30m8.img

target reported max download size of 1826414592 bytes

sending 'recover' (20022 KB)...

OKAY [ 1.884s]

writing 'recover'...

(bootloader) signature checking...

FAILED (remote: signature verify fail)

finished. total time: 2.611s

C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 3.19.0.0000

(bootloader) version-baseband: 4.0.U605611@50319A

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 4.28.502.2

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno:

(bootloader) imei:

(bootloader) imei2: Not Support

(bootloader) meid: 00000000000000

(bootloader) product: m8_ul_ca

(bootloader) platform: hTCBmsm8974

(bootloader) modelid: 0P6B12000

(bootloader) cidnum: CWS__001

(bootloader) battery-status: good

(bootloader) battery-voltage: 0mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: 7f8e91a3

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.089s

C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot devices

HT445####### fastboot

C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot reboot

rebooting...

finished. total time: 0.013s
[One (M8) Q&A, Help & Troubleshooting] Mr Hofs:
Fastboot flash recover is wrong, it should be :

Fastboot flash recovery < see the Y there.

:)
[One (M8) Q&A, Help & Troubleshooting] rockfordpi:
Same Results:

C:\s>fastboot flash recovery twrpm8.img

target reported max download size of 1826414592 bytes

sending 'recovery' (14818 KB)...

OKAY [ 1.438s]

writing 'recovery'...

(bootloader) signature checking...

FAILED (remote: signature verify fail)

finished. total time: 1.976s

C:\s>

C:\s>fastboot flash recovery twrp30m8

error: cannot load 'twrp30m8'

C:\s>fastboot flash recovery twrp30m8.img

target reported max download size of 1826414592 bytes

sending 'recovery' (20022 KB)...

OKAY [ 1.889s]

writing 'recovery'...

(bootloader) signature checking...

FAILED (remote: signature verify fail)

finished. total time: 2.616s

C:\s>
[One (M8) Q&A, Help & Troubleshooting] Mr Hofs:
Bad download then, see how the sizes of the file are different when you flash it again. At least the command is correct now. Re-download the recovery file and try again.

:)
[One (M8) Q&A, Help & Troubleshooting] rockfordpi:
Already tried that, but tried again. First below is my result before I downloaded new twrp and the second one is my result after I re-downloaded image

C:\s>fastboot flash recovery twrp.img

target reported max download size of 1826414592 bytes

sending 'recovery' (20022 KB)...

OKAY [ 1.896s]

writing 'recovery'...

(bootloader) signature checking...

FAILED (remote: signature verify fail)

finished. total time: 2.625s

C:\s>fastboot flash recovery twrp.img

target reported max download size of 1826414592 bytes

sending 'recovery' (20022 KB)...

OKAY [ 1.899s]

writing 'recovery'...

(bootloader) signature checking...

FAILED (remote: signature verify fail)

finished. total time: 2.625s

C:\s>
[One (M8) Q&A, Help & Troubleshooting] Mr Hofs:
Try the HTC_fastboot adb package. It's posted several times here on xda.
[One (M8) Q&A, Help & Troubleshooting] rockfordpi:
Still no luck, same error (see below). This worked flawless before I flashed the latest ATT RUU.

Is it possible phone is still not unlocked or would I be getting that far if it was still locked?

Question. This phone is AT&T (more details in getvar above) but at the end of the contract, AT&T sent me code to unlock the SIM. Now, the SIM I am using is on a T-Mobile MVNO (TING). Since they SIM unlocked the phone, would I be able to and would there be any advantage/risk to trying to flash the Stock RUU for HTC unlocked/developer. It is a higher software version than the ATT version I flashed (twice).

C:\FB>htc_fastboot flash recovery twrp.img

sending 'recovery' (20022 KB)... OKAY

writing 'recovery'... (bootloader) signature checking...

FAILsignature verify fail

FAILED (remote: signature verify fail)

Execution time is 3(s)
[One (M8) Q&A, Help & Troubleshooting] rockfordpi:
Any other ideas? I can't see bootloader screen, but it appears I can access and do all bootloader functions in adb.

I would really like to be able to eliminate locked bootloader as the issue, is there anything else I can flash or try that might let me know if bootloader is still locked. I can get results from getvar and fastboot devices.

I also have an image of the phone saved from TWRP before I flashed the RUU, but seems no way to get that image back. I am not opposed to purchasing S-off if that will for sure help me.
[One (M8) Q&A, Help & Troubleshooting] joikep:
Try to flash a lower version of TWRP and see if that helps: https://dl.twrp.me/m8/twrp-2.8.7.0-m8.img.html
[One (M8) Q&A, Help & Troubleshooting] rockfordpi:
Already tried two previous versions :(
[One (M8) Q&A, Help & Troubleshooting] rockfordpi:
OK, lets try this a different way. IF one were to try to flash TWRP to M8 AND the bootloader was NOT UNLOCKED, what error message would one get?

Would there still be a response from adb getvar and fastboot devices IF the bootloader were locked?

Trying to eliminate potential issues one at a time

Is there a more appropriate forum for me to post the question?
[One (M8) Q&A, Help & Troubleshooting] rockfordpi:
OK, we can close this one out. I did want to post my solution, just in case anyone else had a similar error.

Long Story a little bit shorter, on my HTC one M8, the error:

sending 'recovery' (11976 KB)... OKAY

writing 'recovery'... (bootloader) signature checking...

FAILsignature verify fail

FAILED (remote: signature verify fail)

Was due to a locked bootloader. Because, for some reason I can't see the bootloader on my phone, I could not see the lock status, so I was having to do EVERYTHING via ADB. The problem was, when unlocking the bootloader there is screen on the phone that asks you to confirm yes or no if you want to unlock it. I could not see that screen and the instructions I was reading left that out (It was a good assumption that if one was trying to unlock one would know to say YES. LOL). So, I was missing that step. When I found that step, even though I could not see it on screen, I just blindly pushed volume down and then power to select. At that point it unlocked and allowed me to flash twrp 3.0.

Still do not know WHY I can't see the bootloader screen. I wonder if for some reason the colors are off in my bootloader screen and all the words are the same color as the background or it is trying to redirect that output somewhere else.

but at this point I am going to live with it as trying to fix it is what got me in here in the first place.
[One (M8) Q&A, Help & Troubleshooting] foosee:
Hi,

I have the same problem phne always reboot in fastboot menu.

The status is also RELOCKED after fashing stock ROM RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined.exe

But I'm not able to user adb : device not found.

Fastboot seems working but not adb

Someone have an idea to help me ?

Many thanks
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
The top post is in regards to getting signature verify fail message when flashing custom recovery. So I don't see how it's the "same problem".

Be careful about saying "same problem" without giving any specific information about your actual problem, or device details. From my experience, I've seen many dozens of times where folks say they have the "same problem" and when prompted for more info, we find there are many many differences.

Did the RUU flash successfully, or were there any error messages?

Also, please do fastboot getvar all, and post the results (delete IMEI and serial number before posting) so we can see more info about the phone.

This is normal and expected. You can't use adb when in bootloader. And you can't use fastboot and adb simultaneously. Meaning, when one works, the other will not work, by definition.

Fastboot = only works in bootloader fastboot mode

adb = only works within OS, or alternately will work in custom recovery TWRP

If you issue the command fastboot devices, you should find that it works.

It is also not clear what you are trying to use adb to do (what commands?).
[Samsung Galaxy S7 Edge Questions and Answers] yvibes:
I have the wifi set to stay on while the phone sleeps (which is how it comes out the box). However, for some reason... Every time I lock my phone the wifi disconnects and tells me "no Internet connection found". I have to then click on my wifi and manually connect it back and it starts working again. It's this happening with anyone else?
[Samsung Galaxy S7 Edge Questions and Answers] niqqelele:
try to roll back to the Lollipop DHCP Client. Settings-> Developer Options-> Use legacy DHCP client.
[Xperia Z1 Q&A, Help & Troubleshooting] Inceptic:
Hello i wanna upgrade my Z1 im on 5.1.1 fw .236 rooted Bootloader locked i serach good mods for camera and Z5 addonds sound (Clear phase etc.) I Found timeshift and 4K, i see camera 2.0 mods etc but which one is the best? ;)
[HTC One X+] coal686:
Guide to HTC Device Forums (Please Read before Posting)

Please visit the linked thread prior to posting:

Device Forum Rules (Please Read before Posting)

In this thread, we will provide a short Q&A for your stay on this forum. Please read thoroughly and act accordingly. While most that is needed to know is pointed out in the Forum Rules, history shows that some points of these rules are not...

xdaforums.com
[MDA II, XDA II, 2060 General] djmmusta:
My device is it a himalaya or alpine : orange spv m1000
[MDA II, XDA II, 2060 General] Rudegar:
himalaya but if it have wifi it's alpine
[MDA II, XDA II, 2060 General] djmmusta:
Thanks

Thank you very much may friend :)
[General Questions and Answers] joao_araya:
11/013/2016 17:13:40 - INFO - Selected Bundle for SonyEricson Xperia Play (R800i). FW release : 4.0.2.A.0.58. Customization : Enhanced

11/013/2016 17:13:40 - INFO - Preparing files for flashing

11/013/2016 17:13:51 - INFO - Please connect your device into flashmode.

11/014/2016 17:14:00 - INFO - Device connected in flash mode

11/014/2016 17:14:01 - INFO - Opening device for R/W

11/014/2016 17:14:01 - INFO - Reading device information

11/014/2016 17:14:01 - INFO - Phone ready for flashmode operations.

11/014/2016 17:14:01 - INFO - Opening TA partition 2

11/014/2016 17:14:01 - INFO - Current device : R800i - CB5A1HAUL3 - 1247-6176_R9D - 1245-8821_4.0.2.A.0.69 - WORLD-1-8_4.0.2.A.0.69

11/014/2016 17:14:01 - INFO - Closing TA partition

11/014/2016 17:14:01 - INFO - Start Flashing

11/014/2016 17:14:01 - INFO - Using an unofficial loader

11/014/2016 17:14:01 - INFO - Processing loader_unlocked.sin

11/014/2016 17:14:01 - INFO - Checking header

11/014/2016 17:14:01 - ERROR - Processing of loader_unlocked.sin finished with errors.

11/014/2016 17:14:01 - INFO - Ending flash session

------------------------

I'm trying to downgrade my Xperia Play (.69 to .58 / .42), because my current version does not support root, do not unlock the bootloader ... and whenever I try to do, this error appears: "red line" . Can someone help me?

- It is a downloaded version of the official: XperiFirm

- I have all the drivers installed

- About my Xperia Play:

Model: R800i

Android version: 2.3.4

Baseband: -66

Kernel: 2.6.32.9-perf SEMCUser@SEMCHost #1

Version Number: 4.0.2.A.0.69