yashsingh1/xdaforums huggingface dataset:
[XDA Assist] nobodyph:
So as title says my SystemUI.apk is missing im using a proscan PLT8801K android ver 4.1.1 kernel ver 3.0.8 i rooted with kingoroot everything was working fine then i deleted some apps to make space from xposed and rebooted now SystemUI.apk and navbar are missing been trying to find a way to fix but cant seem to find one so any help or ideas i could try would be helpful.
[XDA Assist] Primokorn:
Hi,

You've asked in the correct section: http://xdaforums.com/showthread.php?p=63897521&postcount=13010

so I'll close this thread.
[Nexus 6P Q&A, Help & Troubleshooting] SurenSeven:
Ok I really derped hard. I use the *#*#4636#*#* menu to change my network type between 2G,3G and LTE as needed. The one under Cellular Network Settings doesn't work all the time as it chooses the selected type as 'preferred' whereas the service menu forces it.

I don't know why I did it, I went to the 3 dot menu in the hidden service menu and chose "Select radio band" and clicked on USA band which was the first option. [DO NOT TRY THIS ,THERE'S NO WAY TO REVERT]. I'm not in the US and now I've lost signal reception on my phone and since then I've flashed the radio image numerous times from the bootloader, even flashed my bootloader,radio,boot image,cache,system all over to no use. I am not getting any signal on my phone. I had done the same once on my Nexus 5 but don't remember what I did to fix it. I'm still trying everything I can think of. A full factory reset didn't help either. The SIM card is fine,I tried it on another phone. Please help.
[Nexus 6P Q&A, Help & Troubleshooting] y2whisper:
maybe try flashing an older image. and then see? Also check the nexus 6 forums, I believe someone did something similar and i assume found a fix.
[Nexus 6P Q&A, Help & Troubleshooting] sayazs:
Were you ever able to figure out how to fix this? I ran into the same issue.
[Nexus 6P Q&A, Help & Troubleshooting] chichu_9:
If you are on Verizon, select Band 6 on that Menu & let your phone sit for 10 minutes so that it register on the network again with new settings.
[Nexus 6P Q&A, Help & Troubleshooting] SurenSeven:
Check this http://xdaforums.com/showpost.php?p=64083667&postcount=14

I ended up replacing my device from my retailer.
[AT&T Samsung Galaxy S 5] sk8chkn:
Hello friends,

I have seen many forums regarding this issue, but none have been able to assist me so I decided I should create my own...sorry for the clutter.

After a failed attempt to OTA update my rooted SM-G870A (I know I know, sometimes it worked for me), I decided to unroot to allow for the update. After uninstalling my SU, I rebooted to find that I have soft bricked my phone (I think). The whole boot goes through, but will settle infinitely upon the At&t white boot screen. I have left it going for 20 minutes or so, to no avail. The screen has begun to overheat from the brightness of the white screen.

So, I decided to attempt to flash the official firmware from sammobile with Odin, but unceasingly fell victim to this error:

<ID:0/005> Added!!

<ID:0/005> Removed!!

<ID:0/004> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/004> Odin v.3 engine (ID:4)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> SingleDownload.

<ID:0/004> aboot.mbn

<ID:0/004> NAND Write Start!!

<ID:0/004> FAIL! (Auth)

<ID:0/004>

<ID:0/004> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

I haven't been able to get around this fail, but I suspect it is a kernel issue. I also don't believe it is an issue with the .md5 because I downloaded it from the most trustworthy source of firmware.

Beside that matter, I've seen NUMEROUS forums that claim if the boot is able to get past Samsung startup, but gets frozen at the boot animation, then it is just a simple matter of factory resetting and clearing cache partitions. However, multiple attempts at this has not solved the issue. I am at a loss here, what may be causing these errors? Thanks in advance! :cool:
[AT&T Samsung Galaxy S 5] Muunia:
I've been having the same issue, I haven't been able to get anything to work. Anyone have some ideas on how to fix this?
[AT&T Samsung Galaxy S 5] Sgt.CM:
Start by following Note #4 in the below post.

http://xdaforums.com/att-galaxy-s5/general/how-to-update-to-g870aof2-5-0-keeproot-t3161733

Then google how to unroot s5 active and don't take short cuts. Follow all directions as spelled out for you.

Hope this helps.
[AT&T Samsung Galaxy S 5] sk8chkn:
I've talked to a professional, and he told me that there is no lollipop version of the S5 Active's firmware that exists on the internet. Therefore, until someone leaks such a file, there is no way to recover this phone. I've had to use a spare that was laying around. All we can do is wait, maybe someday they'll release the firmware we need onto sammobile.com. It may take months, or it may never happen. You should look into getting a replacement like I did, hope for the best.

-AE
[AT&T Samsung Galaxy S 5] Sgt.CM:
Ok. You need to flash back to the rooted version you were on (OF2 or OF3) to fix the soft brick. Then if you don't want to stay with root, follow the 5.1 unrooted update below:

http://xdaforums.com/att-galaxy-s5/general/how-to-update-to-g870aactive-modeloj3-5-t3247843

or try the update first. If you are bricked and can't unbrick you have nothing to lose.
[X Style (Pure) General] ankushgautam:
As motomaker is not present in india and we are stuck with only two colour options, so to theme your moto x style you can order a skin form www.gadgetshieldz.in for around 640 inr and change the looks of your phone completely.. I am posting the pics as an image says many words itself

You can order the same or other textures from www.gadgetshieldz.in

Cheers
[X Style (Pure) General] dvsk69:
Wow this is nicely done. Does that make the phone a little slippery?
[X Style (Pure) General] ankushgautam:
Yes it does a bit.. But it doesn't feel like the phone will fall down any second...
[Nexus 6P Accessories] endigo85:
I will be reviewing two white cases that I bought for my aluminum Nexus 6P.

Ultra-thin Protective Shock-proof Soft Case Cover (First 5 photos)

Link: http://r.ebay.com/sNSxZC

Quality

: This is a matte TPU. The cutouts for the headphone jack, camera, flash and laser autofocus are spot on. The volume and power buttons are covered but work well. It adds some thickness (1.5-2 mm) that I wasn't a fan of considering how large this phone is already. While this case should provide some drop protection, the bottom is mostly uncovered and therefore unprotected. The case overall very flimsy, has noticeable wiggle room, and actually comes off a little too easily.

Color/design

: The camera bar is colored black on all the different color options. It also has a smoother texture than the rest of the case. There is a nice leather-like design down the middle, which really enticed me originally. The white looks great on the aluminum phone.

Feel

: The case definitely adds grip (the white area has a rough Saffiano leather-like feel) but also bulkiness of a TPU case. Since it's so flimsy and not a snug fit, it doesn't give off a premium feel. I also don't like that the camera area is black personally.

Overall, I do not recommend this case.

Slim Frosted Matte Hard PC Case Cover (Last 4 photos)

Link: http://r.ebay.com/EDVjsi

Quality

: This is essentially identical to the snap-on hard cases from Spigen and Ringke. The fit is very snug with perfect cutouts for all areas. The plastic used here is stiffer than the Kugi slim hard case, so you'll need a credit card to remove the case. The bottom of the case was chipped slightly--barely noticeable. Don't expect much drop protection, only scratch protection.

Color/design

: I love snap-on cases so I am being biased here. However, the unique aspect of this case is that it doesn't have the sandpaper coating that some hard cases have, which is good since the white versions of those love to pick up stains. This case has a soft-touch rubber feel, which so far has failed to attract stains.

Feel

: Wonderful to hold. Adds the much needed grip to the Nexus 6P. Note this case adds more grip than what Ringke and Spigen have offered in the past. It barely feels like you have a case on the phone since it adds barely any bulk. Also love that it has no silly branding anywhere.

Overall, I recommend this case for what you pay for is considerably lower than the branded versions.
[Verizon LG G3] roirraW "edor" ehT:
Reserved 1.
[Verizon LG G3] roirraW "edor" ehT:
Reserved 2.
[Verizon LG G3] roirraW "edor" ehT:
I just had the black screen reboot issue rebooting from TWRP after restoring a nandroid.

This further eliminates:

10. Any ROM.

11. The kernel.

Added to OP.
[Verizon LG G3] h_10:
What ROM and bootstack are you using. I just know what I experienced. My booting to black screen issues started when I flashed Xdabbeb's ROM and 35B bootstack. Before I was on stock 35B unrooted and didn't have any problems.

Running xdabbeb's 2.0 Rom, I had constant issues with booting. It was really bad on cold boots. I like to charge my phone overnight with power off. I find that it helps save battery life. Every morning, it would take me a couple of tries to finally boot. I tried reflashing rom and bootstack. I redownloaded both, flashed and still had issues.

Finally I flashed Jasmine 9.1 but only on 24B bootstack and I have had no issues. Ever boot from cold, reboot, to and from recovery has had no issues. I was going to flash 35B bootstack to run with Jasmine but at this point, I don't want to mess with it. My phone is running great, no need to tempt fate.

I know you are not finding any root causes for your booting problem. But for me, it was clearly my phone, xdabbeb's rom, and 35B bootstack. Those 3 did not play well together at all.
[Verizon LG G3] roirraW "edor" ehT:
Look at the documentation I linked to.
[Verizon LG G3] bulletbeef:
Thank you for giving this issue some focus, i would not exactly rule out kernel/rom, using jasmines or skydragon 35b rom on my device does not cause the boot issue, also fulmics rom doesn't do it as often as cloudy 2.5. if you flash the kernel from fulmic over cloudys rom,, it improves the reboot problem. Keeping in mind that the original kernel used in cloudy rom will reliably give the issue on every cold boot.

Is there anybody running a non-verizon rom that does not have this issue, if so could you post your root/recovery method?

based of my reading, and i could be wrong, the issue is with running lollipop on a kitkat boot-loader that may be causing the issue, yet again i can be very wrong about all of this.
[Verizon LG G3] roirraW "edor" ehT:
You're welcome.

It you look at the linked documented specifics of the tests, you'll see that I had 70 consecutive reboots with no issue at all while I was on the KitKat bootloader while running on Lollipop.

In order to do process of elimination tests, you have to change very discreet things between tests. This results in a lot of reboots, relatively minor changes between tests, and occasional backups in TWRP.

It's the closest to a "controlled environment" that I can produce.

I'm not about to add even more variables to the mix with using CM or international stock based ROMs when I was able to produce the problem with statistical reliability on a VS98535B stock based ROM.

Thanks anyway.

[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 36B_00 5.0.2

[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 36B_00 5.0.2

DEBLOAT SCRIPTS

and copies of all the files they remove

[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
[Verizon LG G3] bulletbeef:
Oh i see, i didnt realise that all tests done were on 35b. My device does not hav the issue at all on vzw stock roms only the d855 based roms and aosp i have the issue.

Thanks again and please dont abandon research on the issue.
[Verizon LG G3] roirraW "edor" ehT:
No sweat, you're welcome. We'll see, after a while the tediousness of the testing wears me thin plus I achieved my main goals which was to eliminate certain things which had been rumored by some to be causing it to be worse: the 35B bootstack.

I might actually add Xposed and G3TweaksBox to the list of things eliminated because I had 40 reboots (from memory) without a problem while G3TweaksBox was installed and at least I think 20-30 of those with G3TweaksBox's app data restored the same as it was in the first 30 reboots during my initial setup when I was able to reproduce the issue consistently, so I don't really think Xposed or modules have to do with it either.
[Verizon LG G3] xtermmin:
My observations:

I've never had this issue on my daily driver setup, SkyDragon 2.0.1 (yes, I prefer KK) running 12B bootstack with Xposed (G3Tweaksbox, App Ops, others).

A few days after xdabbeb's ROM was released, I wiped my device, installed the 35B bootstack, and then the xdabbeb ROM. Without doing any additional customization or setup (before I even installed any additional apps), the black screen reboot issue happened every single time I rebooted my G3, requiring a battery pull.

Due to that and the lack of a compatible G3Tweaksbox at the time, I wiped my device, flashed the 12B bootstack again, and restored my SD2.0.1 backup. Have yet to encounter the black screen reboot issue again.
[Verizon LG G3] DeanGibson:
Data point

I bought my first VS985 in August 2014, and I've never seen this. I was rooted (w/ stock recovery) from 10B through 23C, and then reverted to 100% stock.

The other VS985 has never seen it either, but it's less than a month old.
[Verizon LG G3] roirraW "edor" ehT:
I did have the Reboot black screen issue happen once tonight with the Quick Reboot app. If I resume any testing of my own I'll probably do separate test runs off the Xposed and Quick Reboot methods in case there's some difference. Last times I had tried reproducing the issue I was only bothering to try the Xposed method. It's also possible this "one off" occurred as part of what we consider the normal rate of this happening, since we still expect this to happen some no matter what we do due to our overall previous experience of this happening at least some on this phone.
[Verizon LG G3] davidstjohn1:
I'm not sure if this was discussed or not but I'm just going to throw it out there, I can tell on the vibration when its rebooting whether or not it's going to boot to a black screen! If it's going to boot to a black screen it'll be a short vibration, if it's going to boot normally it will be a longer vibration. Have you noticed this?

---------- Post added at 05:50 AM ---------- Previous post was at 05:49 AM ----------

I am thinking it might be a hardware or twrp issue
[Verizon LG G3] roirraW "edor" ehT:
That's interesting regarding the vibration, thanks for the info.

Hardware, yes, that's one of the things that has remained a possibility.

TWRP no. As I indicated in my test details, I went through 70 consecutive reboots without failure (and I had TWRP installed the whole time).
[Verizon LG G3] davidstjohn1:
Well i have noticed a significant difference in the vibration duration when closely watching it go through the the process. Also it has happened to me using cm 12.1 on a regular basis as well.
[Verizon LG G3] tmord1:
I have a vs985 (total of 3 all together-counting replacements for the casing crack) . I never had this problem until recently, now it happens very frequently. For me it seems to have started since I started flashing bootstacks. I am a novice, but I am wondering if there is a subtle change in the partitions that is left behind by changing the bootstack? I have tried a factory reset. But still have this issue. Very strange as it just started recently. I have never done an internal sd wipe... Was wondering if that can be done and if it would help? Any thoughts?
[Verizon LG G3] roirraW "edor" ehT:
Did you take a look at the details of my testing? I did 70 tests in a row without a problem, both after and before being able to replicate the problem by changing the things I detail. Flashing KDZs and TOTs changes the same things as the bootstacks - actually more than the boostacks. The only exception is the bootloader (aboot.img) and Download mode (laf.img) partitions, which are kept at an older version in order to still be able to get into TWRP, and to be able to flash any KDZs and TOTs you want.

JasmineROM and SkyDragon change most of the same partitions, and either always have, or have since at least v2 or v3 of both.

I'm sorry if I'm a bit harsh, but it's been speculated so many times that it's the boostacks. Please everyone stop spreading rumors and only report what you have strong evidence for that you tested. That's one of the reasons I did these tests to begin with to show all the things that it can't be. Between items 9 and 10 in the first post, I posted that I did something very common, after which the problem started happening a lot more predictably. I'm not reporting what it was because in order to be at least 99% sure, I need to narrow it down further so that more rumors and speculation aren't spread.

I am not looking for further guessing/speculation in this thread. If you want to do an extended, detailed series of tests and post your results here, you're more than welcome.

Again, I'm sorry for being harsh but hearing the same things over and over being rumored without real evidence is really tiring.
[Verizon LG G3] clapper66:
I hope we can find a fix for this issue! Good thing the G3 has a removable battery or this problem would be even more annoying. For my G3 this problems seems to happen more when I try select restart and happens less when I just pick power complete off then power back on. Also this has happened while flashing CM nightlys. I select install update, and my G3 powers down then black screens, and then I pull the battery and boot into TWRP manually and the CM updates starts to install automatically. To avoid this issues as much as I can I usually just select soft reboot in the menu. Either way I am glad no matter what devolves found a way to bypass the boot loader and install TWRP. I Don't think I would still have my G3 is there was no way to run AOSP Roms :)

Here is a question I have.

Does this happen on other G3 models or just the VS985?

Just wondering :)

Also on back Friday I bought a MOTO 3 for a backup for $10 at best buy so I may have to try doing some test with my G3 and see what the results are!
[Verizon LG G3] roirraW "edor" ehT:
You can also hold down the power button for like 10 seconds I think, to force shut it off. I don't know the answer regarding if it happens to other G3 variants.
[Moto E Q&A, Help & Troubleshooting] Euroned:
I Have XT1021 on UK network and had lollipop updated onto it, but this had caused slow down problems, so I unlocked the bootloader and tried a kitkat ROM. Using fastboot and minimal abd, I dl a kitkat rom but mistakenly for XT1022! This still seemed to work ok except with text and internet, but calling or being called connected but the earpiece and microphone didn't work.

Since then I have been trying to find a UK working kitkat ROM that i can install using abd and fastboot!

Can anyone help please!?

Thanks very much.

Neil
[Nexus 6P Q&A, Help & Troubleshooting] dia_naji:
To my understanding doze goes into a deep sleep when the phone is off. If i tether will doze still be active ?
[Nexus 6P Q&A, Help & Troubleshooting] 640k:
your post makes no sense. if your phone is off, the OS isn't running, therefore Doze isn't running (and neither is tethering). if you run hotspot, your phone will be (heavily) active and Doze will NOT kick in.
[XDA Assist] XDA Visitor:
Recently I noticed that there is a bluish tint on the top of the lock screen and a greyish tint on the bottom of the lock screen of my Galaxy S6 no matter what lock animation is set. Can anyone help me?

Thanks
[XDA Assist] Droidriven:
Hello,

Welcome to XDA.

That seems to me to be a hardware issue, not software, if that is the case then XDA will not be able to help you, that would have to be done by you or a repair shop.

Try posting your question in the forum linked below on the odd chance that you have software issues instead of hardware issues.

http://xdaforums.com/android/help

Register an XDA account to post and reply in the forums. Good luck.
[Desire 820 Themes and Apps] sandeep saxena:
:fingers-crossed:

Hey guys

There is viper4android with Material design.

Requirments:

Rooted d820 and busybox installed

Download link:-:

https://drive.google.com/file/d/0BwE2tEyxFtHBQVVwWTF3ZjVjSXM/view?usp=docslist_api

Installation-

Flash the downloaded zip in twrp recovery.

No need of selinux mod changer app..etc.
[Desire 820 Themes and Apps] Oel:
Works fantastic on european single version 820n with Lollipo.

Thank You!
[Desire 820 Themes and Apps] sandeep saxena:
Update the the download link, redownload and flash the zip..in this no need of selinux mod changer app uninstall the selinux app and flash the zip
[Desire 820 Themes and Apps] Oel:
Works realy good, also in standby modus. Thanks a lot bro!
[Desire 820 Themes and Apps] rikkerd:
app did stop working for me after a while, this is what i did

If the app stops adjusting the sound and your music is playing at stock config:

1.a use a program like the task killer from avc anti virus and shut down viper4android /alternative just reboot

1.b it should restart and when opening the viper4android menu your music should show a noticeable difference

1.c if it doesn't restart immediatly this step won't work => go to 2

2.a open the menu on the right top corner and uninstall the driver

2.b open the menu on the right top corner and press "check update" this will bring you to a 2 options website.

2.c Installing the 2.3 update did help me immediatly(altough you might wanne reboot)
[Desire 820 Themes and Apps] sharky_004:
Thanks
[Desire 820 Themes and Apps] iXaidyiu:
Will there be any conflicts between BoomSound and v4a?
[Desire 820 Themes and Apps] nilaydani:
Any one using https://xdaforums.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
[Desire 820 Themes and Apps] thorn_pl:
Sorry, this file is infected with a virus

Only the owner is allowed to download infected files.
[General Questions and Answers] rodjacksonx:
Just bought the Asus ZenPad S 8 Z580C (2GB/32GB version), and am liking it, but just discovered that Asus seems to have a nasty habit of limiting the number of users on their devices to only two. It's a really, really disappointing limitation. So, a few questions for the experts here:

Am I mistaken in that, and just missed the option to expand the number of users, or is two-users-only an actual built-in limitation Asus has decided to force on their customers?

Has anyone who has rooted the device tried expanding the maximum number of users? Does the device handle 3 or 4 (or more) users without too much trouble?

Is my only choice to get around it to root the device and manually make the change? (Seems like overkill, and I'm more likely to just return the thing if that's the only option.)
[Nexus 6P Q&A, Help & Troubleshooting] trama09:
I have the Anker PowerPort 2 that has a max of 2.4 amps per port and a Nekteck USB Type C to Type A cable (that's tested and approved by Benson). When trying to charge, the max mA that I've seen is around 1550mA.

Why is that? I was expecting around the max of ~2400,mA
[Nexus 6P Q&A, Help & Troubleshooting] BillyTheRatKing:
I actually ordered this exact combo on Amazon, curious to test it myself.

Are you using Ampere to measure? If so, before plugging in the cable, you need to note the discharging rate (some negative mA). Then plug in the phone and note the charging rate. You have to add the two numbers together to get the actual amperage from the charger because Ampere can only measure the overall system in/out amperage. So if you were doing something really intensive and plugged into a slow charger, you may see it say "Charging" but have a negative number!