yashsingh1/xdaforums huggingface dataset:
[HTC 10 Questions & Answers] bynarie:
This stupid, ugly error message is due to a non-stock kernel. As long as you're running a stock kernel, this shouldnt show up (atleast for me). I am currently running Viper10 2.7.0 and it doesnt show that message on startup. Now, if i go and flash elementalx kernel, that message will be displayed. The way to get rid of this is to either download a modified aboot image or modify it yourself via hex editor. There are simple instructions on how to do this for the htc m9, here on XDA. I dont have a link, but a quick search should be able to find it. Another thing you can do is download a modified aboot image from the link in the previous post and download the corresponding stock aboot image of the same version and use a program like "Beyond Compare" to load up both files and do a side by side comparison. It will show you exactly what was modified. Basically it comes down to just erasing the message in a hex editor and reflashing. Please exercise EXTREME CAUTION if choosing to do this. Aboot is a CRITICAL partiton which contains the bootloader. I would imagine if aboot gets flashed improperly or is hex edited incorrectly, the device is toast. Good luck!
[HTC 10 Questions & Answers] lacxp:
Hi All,

I just S_OFFed with LOCKED bootloader my WWE HTC 10, converted to US Unlocked (cid: BS_US001 / mid: 2PS650000) and restored the latest firmware using ruu I downloaded from HTC US website. I also have that red message when I start my phone up. Is it okay when I'm using stock rom without root?
[HTC 10 Questions & Answers] dd66:
https://xdaforums.com/htc-10/development/bad-sprouts-hidden-red-text-aboots-t3397548

Just read it carefully: high risk of bricking ur phone...
[HTC 10 Questions & Answers] lacxp:
It does not bother me, I'm just curious whether is there US unlocked htc 10 that is not a dev phone? Like on cid BS_US001 I can't disable "Usage and error reporting" because it says " Notwithstanding the above statement, this is a test device and HTC's property. By using this device, you understand and agree...." blablabla. Is there other cid for US Unlocked (what cid US citizens have?) , but not dev/ HTC property one ??
[HTC 10 Questions & Answers] dd66:
sorry but the highest level of my competencies is reached...I don't know...
[HTC 10 Questions & Answers] lacxp:
Thanks anyway :)
[HTC 10 Questions & Answers] SteveO_:
Hi dd66,

for WWE - BUILD 2.28.401.9 this works..

CID: HTC__001 ( + HTC__034, HTC__A0, HTC__J15, HTC__M27, HTC__016, HTC__002)

MID: 2PS620000

https://xdaforums.com/showpost.php?p=70428139&postcount=233

Cya
[HTC 10 Questions & Answers] afuller42:
Theres a app in your system called udove.apk. Delete that and that's the forced error reporting.
[HTC 10 Questions & Answers] matthewacbroad:
This happens when i flash custom kernel. Using both stock marshmallow and Nougat

My video even shows it.

[youtube]k9sjmRC20ps[/youtube]
[HTC 10 Questions & Answers] afuller42:
Completely normal behavior.
[HTC 10 Questions & Answers] dumitresc:
My HTC was stuck in this screen.. HTC logo, red text and restart over and over again.. any suggestion?
[HTC 10 Questions & Answers] papinho:
Hi. Did you install SuperSU?

I had the same problem with this boot loop today when I flashed BETA-SuperSU-v2.74-2-forceencrypt. I just reflashed with SR5-SuperSU-v2.82-SR5-20171001224502 following this guide https://xdaforums.com/htc-10/how-to...-off-radio-t3373025/post66714156#post66714156

I hope this helps.
[HTC 10 Questions & Answers] SEXA:
MY HTC DESIRE 10 PRO show that red lines devolopement purposes only etc and it is rebooting again and again and cant open my phone.HELP ME BROS??
[Galaxy Note 4 Q&A, Help & Troubleshooting] umby75:
Hi, trying to flash the twrp through Odin I got the message you can see in attachment

I tried to toggle the flag in Reactivation Lock but I was unable to do it because the flag presents again.

Searching on the web you can see that the best solution should be the deleting of Samsung account, hard reset and reactivation of Samsung account.

But I don't want the factory reset.

Do you have any suggestion?

Sent from Note 4 device - Rome - Italy
[Off-topic] Duc Viet:
Mod edit: Not job posting allowed in forum.

Post here following the rules.

http://xdaforums.com/market/jobs
[Verizon Galaxy Note 4 Q&A, Help & Troubleshooting] kushy04:
I've unlocked my bootloader and verified that it is rooted via Root Checker. That is all I did thus far, before that my note 4 was virgin unmodified in any way. How can I safely upgrade from 5.0.1 to 5.1.1... or should I update to 6.0? I want to install a custom ROM. Also if I wanted to go back to any stock ROM, can I just flash it via odin without any issues now that my phone is set to Developer mode? is there a different version I need to use or can I still use the following thread?

http://xdaforums.com/note-4-verizon/development/firmware-firmware-kernel-modem-recovery-t2942937

On a side note, I tried to flash 5.0.1 stock and 5.1.1 stock from the link above... it simply failed when trying to flash it... see pic below

I've been out of the loop for rooting, it's been some years since I've rooted an android device, so any and all relevant advice/info would be appreciated... Thanks in advance...
[Nexus 6P Q&A, Help & Troubleshooting] CryNickSystems:
Hey guys,

just yesterday I got my phone back from repair (I cracked my screen, nothing was working then).

Here is a photo of my old screen, which had a hole right below the upper loud speaker:

I think it might be that the drop broke the sensor, and not the repair itself?!?

Using an app like this: https://play.google.com/store/apps/details?id=com.tigermonster.proxfinder shows that my sensor is constantly detecting something.

I'm not using any screen protectors or anything

For now I rooted my device and disabled the sensor by installing the xposed framework and then using http://repo.xposed.info/module/com.mrchandler.disableprox

Strangely enough, yesterday, like 3h after I got my phone back I called someone and everything, including the sensor was working perfectly! :eek:

Can anyone show me a picture of such a proximity sensor? Do you guys think a fix like in this video shown: https://www.youtube.com/watch?v=HPHsianYnqo, putting a piece of paper behind the proximity sensor could work?
[Nexus 6P Q&A, Help & Troubleshooting] Heisenberg:
You never ended up showing any images of the phone before/after the repair but if you have a screen protector fitted to the screen and it doesn't have a little cutout on the right just below the top speaker then the protector is constantly tripping the proximity sensor.
[Nexus 6P Q&A, Help & Troubleshooting] CryNickSystems:
Thanks for your answer. Like I said, I am not using any screen protectors.

Here's an image of my old screen:

http://imgur.com/ufNSseD

I don't think it has anything to do with that damage now tbh, because it was working well yesterday. I guess maybe the connector loosened itself?

Which one here in the pictures to step 6 is the proximity sensor? https://de.ifixit.com/Teardown/Nexus+6P+Teardown/51660
[Nexus 6P Q&A, Help & Troubleshooting] CryNickSystems:
Thanks for the info about the position of the sensor - I'll definitely do that when I'm going to disassemble my phone (which is gonna take a while since I'm waiting to receive a new rear housing from a seller in the US).

I'm planning to disassemble as little as possible, so I'm hoping it's easy to access the proximity sensor (but guessing by the pictures it should be).
[Nexus 6P Q&A, Help & Troubleshooting] hawkswind1:
Good luck. Hope you can fix it by cleaning it. Make sure to have some thermal compound on hand to replace the old stuff when you disassemble.
[Nexus 6P Q&A, Help & Troubleshooting] CryNickSystems:
Hey one more quick question:

Do you think it's possible to remove the motherboard without removing the battery?

I guess that the problem is that the proximity sensor is either too close to the screen, or too far away (like there's some small gap between the proximity sensor and the screen). I will probably have to remove the motherboard if it's the former (if it's the latter I can just put something like a pice of paper at the back of the rubber).
[Nexus 6P Q&A, Help & Troubleshooting] hawkswind1:
You won't need to remove the battery to remove the main board. You'll just have to unplug it.
[Nexus 6P Q&A, Help & Troubleshooting] CryNickSystems:
Alright, thanks. I am wondering about another thing: Why are there two holes for the light and proximity sensor on the backside of the phone? I was planning to try and first stick some piece of paper on top of that rubber plastic to get the sensor closer to the screen. Why the holes?

Ty.
[Nexus 6P Q&A, Help & Troubleshooting] hawkswind1:
I don't know which type of proximity sensor this is, IR, led, electromagnetic etc. But all proximity sensors I know of have two "eyes" One eye emits ir, led, or electromagnetic field, the other eye looks for a change in the return field. I think you'll find a scratched, smashed return eye. Or debris lodged in the sensor housing. Use a magnifying glass and excellent lighting.

If you shine a bright flashlight at the sensor through the screen can you see anything blocking the eyes? Doesn't matter I guess, you'd have to disassemble to get it out of the way anyways.

---------- Post added at 09:43 PM ---------- Previous post was at 09:16 PM ----------

It looks like the prox sensor comes covered in a rubber cover. In this pic the rubber is there:

https://d3nevzfk7ii3be.cloudfront.net/igi/SQfQ23vhRFsvbJJT.huge

In this pic they removed the rubber to expose the prox sensor:

https://d3nevzfk7ii3be.cloudfront.net/igi/eDldW3bJmHSbQEYF.huge

I suspect the rubber could be missing, lost during repair. Or perhaps installed wrong.
[Nexus 6P Q&A, Help & Troubleshooting] CryNickSystems:
I did what you asked: There is no light coming out on the back of the phone if that's what you meant.

Anyway, I'll have to wait until I receive my replacement back housing and then I'll try my best to repair the sensor. I hope the rubber is just misaligned.
[Nexus 6P Q&A, Help & Troubleshooting] CryNickSystems:
Alright - so I did have time today to disassemble my phone (got the replacement housing last week).

I noticed that there was no rubber part on top of the light and proximity sensor, as well as on the device above the two (i don't know what that is).

What I did is that I had a small tube like this one: https://sc01.alicdn.com/kf/HTB1hBgwKVXXXXcvXpXXq6xXFXXXY/8mm-small-clear-plastic-PC-pipe-TUBE.jpg which I painted black and put it on top of the approximity sensor.

Everything is working well again (there were some lints on the display right below where the proximity sensor is located, that's probably why it stopped working from one day to another).

I guess the main function of the rubber is to protect the sensor against dust and lints.

I also am very mad at myself for having forgotten to take out the NFC antenna from the old housing before replacing it, so I had to open my phone again after I did already close it (and now there are slight traces of an opening - again :( )

But apart from that everything's fine now and I hope it'll stay this way.
[Nexus 6P Q&A, Help & Troubleshooting] hawkswind1:
Glad you got it fixed! And yeah, unfortunately it's nearly impossible to remove the back cover without leaving dings at the injection site. When I put on my new top and bottom rear covers I removed most of the glue. So next time I can remove them without much trouble.
[Nexus 6P Q&A, Help & Troubleshooting] nickfuzz:
I am having similar problems. I just traded for a nexus 6P and everything works great except for the proximity sensor. The 6p was just OTAed to 7.0 and I only unlocked it and installed TWRP. No other changes and no root (yet).

There is no screen protector on the device.

When I make a call, the screen stays on. The screen turns off as soon as I cover the proximity sensor. The screen then does not come back on until the call is completed. I downloaded a bunch of proximity apps, including Proximity Sensor Finder. Proximity Sensor Finder (and others) report that sensor detects Far (5cm or more) and Near (value of 0 cm when the sensor is covered). The sensor doesn't seem to identify intermiate values. The odd thing is that the sensor doesn't seem to reset. If I cover the sensor (value of 0 cm) and remove my hand, the sensor continues to read 0 cm.

Does this sound like a hardware or software issue? The device appears to detect both the near and far states, but doesn't return to far after the sensor is uncovered. Thanks for any help.
[Nexus 6P Q&A, Help & Troubleshooting] nickfuzz:
Solved the problem. I downgraded to MM and the proximity sensor problem persisted, so I figured it was a hardware issue.

I took apart the 6P and the there were signs that repair had been performed. The screen was probably replaced previously. The little rubber gasket covering the proximity sensor was missing, just as the OP described. I cut a blue-colored straw and placed it over the proximity/light sensor. Works perfect!
[Nexus 6P Q&A, Help & Troubleshooting] CryNickSystems:
I need to bump this thread cause a few days ago I started having the same problem that nickfuzz describes.

Now I've got my opened phone in front of me and tried putting a pice of a black straw around the two sensors, but that does not help. It reports 5.0 cm and if I cover the sensor it stays at 0.0 cm :(

Can anyone give me an advice about what to do now? :(

Update:

The light sensor is also not working properly: It is reporting way too less lightness, and tends to report 0 lux when I'm not directly holding the phone under a lamp (for instance).
[Nexus 6P Q&A, Help & Troubleshooting] CryNickSystems:
After 5 hours of trying I somehow managed to at least get the sensor to always report 5.0 cm. That's better than constantly reporting 0.0 cm.

I put a piece of a wide straw (there are different sizes, you know) around the hole board on which the two sensors (light & proximity) sit on. I guess this is a bad idea.

I am now trying to get this rubber gasket from somewhere, but I guess I'll have bad luck since I'd have to buy a defective nexus 6p from which I could take it from :(

UPDATE:

Can anyone tell me why the screen is painted black on the inside, right where the proximity sensor is located? I scraped off the paint and painted it over with a black pen. That must be the reason why the proximity sensor is always reporting 5.0 cm (which doesn't make much sense, because at some point it would have to detect something if it's not broken).
[Nexus 6P Q&A, Help & Troubleshooting] CryNickSystems:
Can you tell me if you put the straw around both sensors and their "chassis" (that black thing they sit on), or did you put the straw only around the sensors (i.e. on top of the chassis)?

I still need to find a way to fix my sensors :(
[Nexus 6P Q&A, Help & Troubleshooting] CryNickSystems:
I tried to use some electric tape and put it on top of the sensors with two small circles cut in, but eventually I figured that the problem actually lies in the black paint on the inside of the screen.

I removed that paint a few weeks ago and I couldn't paint a new black paint on it that is not too thick, so I am stuck with a sensor consequently reporting 5cm.

I did try to use an Edding.
[Nexus 6P Q&A, Help & Troubleshooting] Colchiro:
I had the same issue with the proximity sensory and a new 6P, but fixed it with this: https://play.google.com/store/apps/details?id=com.mobiledirection.proximitysensorreset&hl=en

Everything was still good after uninstalling that app too.
[Nexus 6P Q&A, Help & Troubleshooting] CryNickSystems:
Thanks for your reply. The problem for me definitely is related to a hardware issue, my black coating that I scratched off a few weeks ago and repainted on friday is simply too thick.

I don't know how to get a black coating that is as thin as the original one. And I think using electrical tape with two holes in it is perfect as a replacement for the original rubber gasket.
[Android Apps and Games] iKeramat:
For The Moment No One Is allowed To Use My S Health files For His ROM Without My Permissions!

Installation Guide:

Just Flash It With Custom Recovery(TWRP V.3.0 Recommend)

Feature:

-All Things Like S6 Lollipop S Health

Bugs:

There is a no BUG

Download Link:

Link

XDA:DevDB Information

S Health, App for all devices (see above for details)

Contributors

m.h.k.jahromi

Version Information

Status: Stable

Created 2016-08-11

Last Updated 2016-08-15
[Honor 5X Questions & Answers] Bentis:
After an emui updater I lost my magnifier app how can I get it back can someone help me out please
[Honor 5X Questions & Answers] DigiGoon:
Maybe Honor removed it from that update, you can ask someone to pull out the apk of magnifier from their /system. :D :D :)
[Sprint LG G2] kevinhack:
Hello, I'm not sure where to post this but I really need your guys' help. I have an LG LS980 (spr) and the screen doesn't work. The touch screen does however. I've managed to install Mobizen and can mirror my screen to my phone. I also have droid@screen working as well. I have USB Debugging enabled.

Software info:

Version: 5.0.2

Kernal: 3.4.0

Build: LRX22G

Version: LS980ZVH

It is not rooted. It is completely stock. Right before my screen broke it was rooted on 4.4, I TOT'd back to ZV7 (I think, whatever the first release was lol) then updated it, foolishly.

Anyway, I do not remember if I can TOT without my screen working.

And even if I can, I'll need to re-enable USB debugging without a functional screen.

-----

Would like to root it on anything 4.4 or higher.

----

How should I go about doing this. Please help as I would like to use my G2 rooted again.
[Galaxy S3 Neo Themes and Apps] iKeramat:
For The Moment No One Is allowed To Use My S Health files For His ROM Without My Permissions!

Installation Guide:

Just Flash It With Custom Recovery(TWRP V.3.0 Recommend)

Feature:

-All Things Like S6 Lollipop S Health(V1.0)

-All Things Like Note 7 Marshmallow S Health(V2.0)

Bugs:

There is a no BUG

Download Link:

Download Link_V1.0

Download Link_V2.0

Tested In S3 Neo(i9300i)

But You Can Test In Any Device!

If You Liked My Work, Do Not Forget To :good:Thank:good: ;)​
[Galaxy S3 Neo Themes and Apps] iKeramat:
n7 mm s health added:)
[Galaxy S3 Neo Themes and Apps] Albe96:
[emoji14] [emoji12] This Is Available On Play Store For All
[Galaxy S5 Mini Q&A, Help & Troubleshooting] hedgegee:
Hello

When i use the ODIN file it flashes and passes but it is not installed? It just boots up in stock recovery. I have the G800F. Can anybody help?

It's this one i try to install. http://xdaforums.com/galaxy-s5-mini/orig-development/recovery-twrp-3-0-0-t3313775
[Galaxy S5 Mini Q&A, Help & Troubleshooting] another343:
Download Flashify from the Play store and flash the IMG :good:
[Galaxy S5 Mini Q&A, Help & Troubleshooting] lfom:
What ROM?

If you want to stay on stock, you must disable security updates and Knox or it may revert recovery to stock, I guess. At least in first lollipop versions with 1GB kernel. If you don't just boot to recovery after flashing recovery.
[Galaxy S5 Mini Q&A, Help & Troubleshooting] hedgegee:
I am writing a guide - i got it to work thanks guys :)
[Galaxy S5 Mini Q&A, Help & Troubleshooting] blob_:
would be great if you could post just the steps, I got the same issue :-/
[Galaxy S5 Mini Q&A, Help & Troubleshooting] hedgegee:
http://xdaforums.com/galaxy-s5-mini/general/guide-install-twrp-custom-roms-g800f-t3439853
[Galaxy S5 Mini Q&A, Help & Troubleshooting] blob_:
"the powering down" on my S5mini (F) could only be accomplished by ripping out the battery :-/

but I got it to work :)
[HTC Desire Eye] modaifallah:
I'm not a newbie but still not a 'developer' I barely made ROMs. I'm willing to give my time to port cyanogenmod or at least an AOSP that can base to the rest of the AOSP roms. What are the steps mainly?

M8 is actually very similar with our device, what are the modifications needed to make the base rom from M8 work?
[HTC Desire Eye] Arun.Gunupudi:
I too asked [MENTION=1909979]xxoo[/MENTION]perminixx same qsn about porting m8 CM ROM to our eye......

But she told that it also might need SSD and takes more time...
[HTC Desire Eye] modaifallah:
I love everything about my Desire EYE except its lack for ROMs. I had Galaxy S3 before it which is an old device from 2012 yet it has every ROM you can imagine to date! It has Cyanogenmod MM since MONTHS. [MENTION=5729420]xXminiWHOOPERxX[/MENTION] is an awesome developer, she gives much of her time and effort to port ROMs to our device, but she can't have all of the development alone. That's too much on a single person. If she can teach both of us how to port from M8 AOSP ROMs and post kernels for Sense and GPE roms to complete her guide the device now has at least three developers working on the device.
[HTC Desire Eye] TahirZX:
I'd love to learn porting Roms and test them as well.
[HTC Desire Eye] JuanArg:
She posted a pretty straightforward guide on porting from m8 to desire eye. Even though it's meant for sense roms, it might be of help. Here's the link http://xdaforums.com/desire-eye/general/guide-porting-htc-msm8974-devices-t3416014
[HTC Desire Eye] modaifallah:
[MENTION=5729420]xXminiWHOOPERxX[/MENTION] 's guide is for Sense and GPE ROMs..

?
[XDA Assist] F8X:
Ok so before i wiped my data, InApp purchases for ALL apps was via Lucky Patcher , but tbh i forgot how i did it , i would be thankful if someone can tell me how , cause its a pain in the ass to patch every single app ??.
[XDA Assist] malybru:
Mod Edit

Or , you could just BUY the apps.

lucky patcher is deemed warez:

6. Do not post or request warez.

If a piece of software requires you to pay to use it, then pay for it. We do not accept warez nor do we permit members to request, post, promote or describe ways in which warez, cracks, serial codes or other means of avoiding payment, can be obtained or used. This is a site of developers, i.e. the sort of people who create such software. When you cheat a software developer, you cheat us as a community.

malybru

Senior Moderator
[G4 Q&A, Help & Troubleshooting] dragon884:
Hello All,

I know there have been a lot of touchscreen issues with the G4 in 2015 but is it still happening for some users? The touch screen issue i have been having is very intermittent and only occurs when you wake the devices up. So when you wake the device no touch input is detected. I can tap any where and it will not register any touches. I will then put the device back to sleep and wake it up again, then it'll work normally.

Not sure if this is normal but is anyone else having this issue? Should i be concerned or RMA the device or is this more of a software bug?

I can use all the diagnostics test tools and it'll pass since the issues is not lagging or missed touches.

Thanks all!
[G4 Q&A, Help & Troubleshooting] jinderation:
Try to reflash the firmware via lgup or lg flashtool
[G4 Q&A, Help & Troubleshooting] clitheroe1:
I have this problem too but it seems more random than just when the screen wakes up and has occurred while I've been in the middle of doing something on my phone. It's simple to solve by turning the screen off and back on again but it's very annoying when it happens.
[G4 Q&A, Help & Troubleshooting] dragon884:
Yeah, that sounds really annoying....Wonder if it's a bug. Going to try a reflash and retry. Hopefully it'll solve it.
[Galaxy S6 Q&A, Help & Troubleshooting] Angiiie:
Hi lads i have a few questions recently i boughr a new s6 and ive tried to take a night photos with pro mode because i had before a meizu mx4 wich was absolutley amazing at shooting stars etc so i tried the same with the s6 but every photo i take it makes some pink overlay like i would use a filter or something... any help? im also giving a pictures of what its doing.. thanks.View attachment 3839843
[Galaxy S6 Q&A, Help & Troubleshooting] kadabra12:
Same here... with 10 second shutter and 800 ISO

Inviato dal mio SM-G920F utilizzando Tapatalk
[Galaxy S6 Q&A, Help & Troubleshooting] KingSLAyyeR:
There is already a thread regarding this issue:

http://xdaforums.com/galaxy-s6/general/galaxy-s6-camera-pink-tint-purple-flare-t3109199