yashsingh1/xdaforums huggingface dataset:
[Sprint Galaxy S 5 Q&A, Help & Troubleshooting] svz235:
Well I have the SM-g900p from sprint flashed over to boost. I had CPE1 already installed. Then I got notification of CPE2 coming out. I did try flashfire but it keeps failing on me for some reason I go to build number and it is still on CPE1.
[Sprint Galaxy S 5 Q&A, Help & Troubleshooting] dieseldeeznutz:
Alright, so it turns out I was mistaken... did I mention I'm somewhat of a noob? Anyway, CPE1 was the original mm6.0.1 build from Sprint, CPE2 is the update. They list it like this in the OTA info: CPE1>CPE2, I guess just to show it's going from cpe1 to cpe2... confused me because I thought they were just different builds for different models and carriers. :silly: So, FlashFire didn't work for the update. I ended up uninstalling Xposed Framework, and unrooting with SuperSU, then tried the OTA, but it gave me the message "Your phone has been altered in an unauthorized way" and wouldn't install the OTA. So I went to sammobil.com , downloaded the latest CPE2 build, flashed it with Odin, then rooted it again, and installed Xposed. Everything went smoothly, I'm on the newest build, rooted again, and no more notification... Yayy!! :laugh:
[Sprint Galaxy S 5 Q&A, Help & Troubleshooting] svz235:
Sweet glad it worked for you mind showing how you flashed the cp2 build from Odin and where you got it from? I also want the notification to go away I am stuck on cp1
[T-Mobile LG V10 Q&A, Help & Troubleshooting] jamarockkid:
im on MM tried to root, but im just keep getting boot loops, red text boot verification failed.
[T-Mobile LG V10 Q&A, Help & Troubleshooting] YrrchSebor:
Did you (re)unlock your bootloader?
[T-Mobile LG V10 Q&A, Help & Troubleshooting] jamarockkid:
No, don't think I did how do i
[T-Mobile LG V10 Q&A, Help & Troubleshooting] YrrchSebor:
I'm sure that's the problem then. Boot into the bootloader and do 'fastboot oem unlock'. Remember it will wipe your data
[T-Mobile LG V10 Q&A, Help & Troubleshooting] jamarockkid:
I went into bootloader but it won't respond
[Pixel C Q&A, Help & Troubleshooting] brando56894:
After using my Pixel daily for 6 months (got the first batch, pre December 25th) and having next to no issues with it (wifi strength sucks, even with Xceed kernel, but it's better than it was), half of my screen decided it wanted to go goofy. I was using it two days ago and everything was working fine, I used it yesterday morning for a few minutes and then plugged it into the Google charger that came with it and let it sit on my couch for a few hours while it was charging. I got on the bus, and pressed the power button to wake the screen and nothing happened. Thinking I had it turned off I held the power button for a few second, and still nothing. So I held it for 30 seconds and when it brought up the bootloader warning the right side of the screen was glitching, same thing happened on the Google logo, boot animation, and continued into Android. I powered it off, hoping it would go away but it didn't. The slight glitch then turned into static "snow" which will then change sporadically based on what I'm doing on the tablet. That area of the screen still works perfectly because touch input works, and when I take a screenshot and view that area of the screen it shows up just as it should. It seems like there is an overlay on the right side of the screen that won't go away. Since it happens from the moment you turn it on makes me think it's a hardware issue but the fact that the screen itself still works perfectly makes me think it's a software issue. I haven't flashed the stock ROM back on it yet or locked it backup yet since I don't have a type c to type a adapter with me, it's still under warranty but I wanted to see if you guys could help me fix it before I sent it back.

TL; DR

[YOUTUBE]u6PWmJrKfFc[/YOUTUBE]
[Pixel C Q&A, Help & Troubleshooting] badwiring:
This just started happening to me today, exactly as you described.
[Pixel C Q&A, Help & Troubleshooting] brando56894:
Interesting. I just RMA'd mine, should be receiving it within the next few days.
[Pixel C Q&A, Help & Troubleshooting] badwiring:
I'm returning mine too. I've determined that it's hardware because when I applied pressure around the edges of the screen I felt something slightly pop into place and then the problem was temporarily corrected. If I apply slight pressure to parts of the screen it happens again.

At this point I've flashed back to stock and I'm in an eternal recovery bootloop that I can't fix because acquiring USB drivers that work is incomprehensively difficult.
[Pixel C Q&A, Help & Troubleshooting] DT39:
Just had mine go as well :crying:
[Pixel C Q&A, Help & Troubleshooting] brando56894:
Oh wow, that sucks. At least I'm not the only one though. I just got my new one a few days ago and all is well so far, hopefully this one won't screw up. RMA process was very smooth.

As for the USB drivers I usually have to install them manually by using the "select driver from a list"
[Pixel C Q&A, Help & Troubleshooting] hugehead83:
Same issue on my first one

Here's my post from the mapping problems to serial # thread.

Google RMA process was fine once I was finally able to get a chat window with them.

Be sure to post to the problem mapping thread to help others!!
[Pixel C Q&A, Help & Troubleshooting] lude219:
Add me to the list. Just went through the RMA process and am now waiting for the replacement to come. I can deal with the wifi issue and the random reboots, but having half of your screen corrupted is unacceptable. I don't even know how this is possible unless some genius at the pixel C team decided that it's cheaper to source half a screen and glue them together.
[Pixel C Q&A, Help & Troubleshooting] brando56894:
It's kinda crazy that I couldn't find this happen anywhere then all of the sudden it's happening to you guys! I'm extremely confused how it happened and what actually went wrong with it.
[Pixel C Q&A, Help & Troubleshooting] pkelly517:
Most likely some latently defective silicon from Nvidia.
[Pixel C Q&A, Help & Troubleshooting] brando56894:
I don't believe so, I think it has more to do with the screen, since it would occasionally correct itself, and even when half the screen was screwed up, screenshots would come out perfectly. It's almost like there's something stuck over the right half of the screen.
[Pixel C Q&A, Help & Troubleshooting] pkelly517:
Of course screenshots would come out perfectly. It's just a memory dump of the video RAM. This is a problem with getting that memory to the display. I think the display driver is part of the SoC. I could be wrong. Maybe it's a cable.

But it seems like a bit in the display driver is never getting enabled.
[Pixel C Q&A, Help & Troubleshooting] badwiring:
I'm fairly certain that it's a physical issue with the screen or the connection to the screen. When I had this issue I saw a visible change when I applied some light pressure around the edges of the screen. At one point it almost felt like something popped into place and the problem went away (then resumed.) Also, if I applied some pressure on the lagging side of the screen I would see some odd behavior as if the connection was fluctuating. I didn't squeeze hard, but it didn't take much.
[Pixel C Q&A, Help & Troubleshooting] SpaceGooner:
I have had TWO Pixel Cs do this now. The first got the dreaded half screen of death after 5 months back in May, and the replacement that Google sent me has just started doing it today after just 3 months. The second device was from a much later batch than the first.

My experience so far makes me think that all Pixel Cs might have this hardware defect - it's just a matter of time before it happens. That's kinda gutting if it's true as for me this is the best tablet out there, and I can't see anything else coming close to replacing it.

About to contact Google for RMA again I guess. Third time lucky maybe...?
[Pixel C Q&A, Help & Troubleshooting] brando56894:
Wow really? That's no good!
[Pixel C Q&A, Help & Troubleshooting] JimForster:
Pixel C Screen Issues

Add me to the list, as of this morning. 8 months old. :mad:

[IMG="Pixel C screen death"]https://goo.gl/photos/utk56shNLCUZAaAR6[/IMG]
[Pixel C Q&A, Help & Troubleshooting] lude219:
what's the serial# of your replacement?
[Pixel C Q&A, Help & Troubleshooting] SpaceGooner:
My second Pixel C's s/n is 61250***** This one has developed the screen problem on the right of the screen

The earlier one I had was 5A230***** This one had the problem on the left side of the screen

I assumed the second one was from a later production batch than the first, but must admit I don't really know that.
[Pixel C Q&A, Help & Troubleshooting] lude219:
According to this http://xdaforums.com/pixel-c/general/mapping-problems-to-serial-t3274660 there still seem to be some issue with the #61250 batch so I'd try for a 3rd time to see if you get a 6202000 one (what i have now). It's stupidly frustrating but the Pixel C is too good to give up now.
[Pixel C Q&A, Help & Troubleshooting] SpaceGooner:
Thanks for the info. Not sure I'll be able to determine what s/n Google sends me next time, but here's hoping I get a good one and that I've just been unlucky so far. I won't be able to RMA until I get home from vacation later in the week anyway. If they send me another Pixel C that develops the half screen problem down the line, I will surely have to get a refund and maybe go for a top end Chromebook (with Google Play of course) next time.
[Pixel C Q&A, Help & Troubleshooting] badwiring:
This issue seems to be popping up more recently. Just a shot in the dark: could this be related to heat? Not heat within the device, but environmental, like if it gets left in a hot car.
[Pixel C Q&A, Help & Troubleshooting] SpaceGooner:
I would say it's a slim possibility it's heat related in my experience. Both the Pixel Cs that I've had have developed this half screen issue without leaving my house. Sure it's been warmer over the last few months as it's Summer, but the temperature in the house has not gone over maybe 26 C at any point.

The only other cause and effect connection I can make is that both my tablets got this issue within two or three weeks of being updated to Nougat. Could Nougat's split screen mode overload one side of the screen hardware somehow? I guess the million dollar question is has this happened to any Pixel Cs while they were still on Marshmallow? Yes I know this may be dumb, so don't flame me - I'm not claiming to be an expert here.

Both these guesses would however account for the sudden increase in screens getting this issue over the last few weeks.
[Pixel C Q&A, Help & Troubleshooting] BaristaBot:
sad to report that this happened to me over the weekend. thought it was something anomalous until i rebooted and saw it happen on the boot screen. i got a google rep on the phone within about 30 minutes of requesting a callback and they set me up a rma which should be here by friday. i give them an a+ for customer service, but i'm disappointed about this issue, and to see it happen to several others makes me worry about my replacement device.

so let's say this issue pops up on the next one i get. how would i go about getting the full refund so i can put my money towards a future device that might have better stability? is that even possible?
[Pixel C Q&A, Help & Troubleshooting] brando56894:
This is really starting to get crazy, because it seems that I'm now ahead of the curve on two hardware failures: first this (I couldn't find anything related to this when it first happened to me two months ago and I searched for days), and secondly the motherboard that was in my home server (AsRock C2750D4I) which I thought was related to a faulty PSU that I had installed a few months prior and two other things had failed in that time period. Now you guys are experiencing it every few days it seems, and there are reports of the motherboards dying all over reddit and reports over at the FreeNAS forums (which is what I had originally bought mine for).

Mine wasn't related to either heat or nougat since mine only leaves the house for a few hours once every few months and IIRC I was running a marshmallow ROM. I flashed it completely back to stock and it still happened.
[Pixel C Q&A, Help & Troubleshooting] SpaceGooner:
Thanks for confirming at least. That blows the Nougat theory out of the water then.

I'm sitting here typing this on my brand new Pixel C number 3 from Google. Hmm... I wonder how many months the screen will last on this one. If it goes the same way as the last two, I'm definitely gonna demand a refund as I can't see Google changing their screen supply chain for any future Pixel Cs. It was always an expensive, niche device so they're probably just hoping to sell off their remaining stocks from here on. They better refund my folio keyboard too.

Got a feeling a top end Chromebook is where I'll be heading next time...
[Pixel C Q&A, Help & Troubleshooting] brando56894:
I'm also thinking the same thing. I'm waiting for one with a detachable screen, but I'll settle for a foldable/flippable one if I have to. I've also considered getting a Surface 3 or 4 and installing Linux on it, since the secure boot key is readably available.
[Pixel C Q&A, Help & Troubleshooting] SpaceGooner:
The unthinkable has actually happened. My THIRD Pixel C from Google has also developed the half screen issue. I have only had this one for 7 days! It was hardly used in all that time and was only charged up twice. Yesterday my wife was using the tablet to do some internet banking on chrome and the problem began again.

While I have really enjoyed using these 3 devices during the good times, there's no way I'm gonna let Google replace this one with a fourth new tablet. I will start the return/refund process once again tomorrow and demand my money back this time as this situation is now officially ridiculous. It pains me to say it but unfortunately I have lost all faith in the Pixel C now.
[Pixel C Q&A, Help & Troubleshooting] OlegNYR:
I'm having the same issue here on a replacement device that just one week old. The first device had screen issue out of the box. Now I'm thinking should I go for 3rd replacement or just take the refund and move on.
[Pixel C Q&A, Help & Troubleshooting] kurze12:
My Pixel C, almost two years old, also had this defect. I received a new device from Google, which lasted three months until the display broke again. Now the guarantee is over. Google doesn't build good hardware, I'm buying an iPad now.
[Android Q&A, Help & Troubleshooting] esutisna:
hi all,

i came here with deeply desperate. i lost video of my wife giving birth.

it happened when i move videos from internal memory to external memory.

suddenly the files in external corrupted. the files name appears gibberish

there are two method i tried for the past 3 days

1. try to recovery from external (micro sd) using MiniTool Power Data Recovery, Wondershare Data Recovery, DRW. since i turned out that sd card have bad sector, the recovery progress stuck in 4%

2. try to recover directly from the phone. i also have issue with this method. since it requires me to the root the phone.

yes, without rooting i still can use software to discover lost data, but the softwares told me if it can discovery much more data if the phone is rooted) . unfortunately i cant find rooting method without flashing the rom. i dont want flash the rom , because if i do so im afraid the moved videos will be more difficult to recover. i also try once click root like framaroot, king root/ kingo root, Wondershare Dr.Fone for Android, none of them succeed rooting my phone (Lenovo Vibe P1 Turbo)

can anyone help me to recovery the file.

or please give me alternative how to root without flashing rom

thanks in advance
[Android Q&A, Help & Troubleshooting] spanit007:
Hello esutisna,

So sad to hear that you lost such a precious data from your device!!!

I know how it feels.

So you have tried many things but still there is no hope.

Now I would like to suggest you an alternative approach using your PC.

It will be best if you have windows.

Go and download Recuva

https://www.piriform.com/recuva

this is the link.

connect your device to the computer and check that your device is connected as media transfer device long for MTP.

Now start and install recuva.

On the desktop, launch the recuva again using the shortcut.

It will ask you to recover file from the path.

Select Media Device.

Then select the type of file you want to recover, in your case it is Video.

Select it and hit recover.

It will work as magic and all your lost data will be recovered.

All though there is a chance that it may not work if you have by mistake format your internal memory of forcefully rebooted the device.

Please tell me how it goes.

I will be happy to help further!!!
[Huawei Y6 Questions & Answers] blue7077:
hi everyone.

i have a Huawei Y6 L21 and i can't use any USSD code!

my build number is: l21c158b130

how can i upgrade or downgrade to any build number to solve my problem?

i tried SCL-L21, C432B150CUSTC432D002 but it fails.

what build number i can downgrade or upgrade to?
[Huawei Y6 Questions & Answers] blue7077:
help meeeeeee

no one is here???
[Wileyfox Swift] ztva:
I tried rooting my Swift and I ended up being stuck in TWRP 2.8.7.1.

All I did was fastboot the TWRP 28.7.1 Image.

I then decided not to do it, so I tried to reboot device.

It keeps putting me into twrp.

Could someone tell me how i get rid of this.

Sorry if the answer is obvious I'm a noob to this.

Greets Louis
[Wileyfox Swift] Dior DNA:
- on which firmware were you (COS12.1 or COS13.0)?

- how exactly did you flash twrp?

You can always revert back to stock by flashing from

cm-12.1-YOG7DAS2FI-crackling-signed-fastboot-07863145a7.zip

or

cm-13.0-ZNH0EAS2NH-crackling-signed-fastboot-2306277a34.zip

as folows:

fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash aboot emmc_appsboot.mbn
fastboot flash hyp hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash tz tz.mbn

fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
[Wileyfox Swift] ztva:
Thanks for the response.

I flashed back to the original recovery and everything works fine.

I'm currently on COS 13.0.

Is there a safe way to root my Swift or get CM running safely.

I've tried a couple of methods on here, but they didn't seem to work.

I also reallly don't want to brick my phone since it's the first decent smartphone I have.

I know the basics like how to use adb and fastboot, but I'd really appreciate some advice on this.

Greets Louis
[Wileyfox Swift] Dior DNA:
There is a separate thread about preparing for and rooting.

Being on COS13 you may want to use TWRP_3.0.2 (to be found separate thread) and flash UPDATE-SuperSU-v2.76 ZIP (to be found in SuperSU trhead) from TWRP.

You can even boot TWRP without the need to flash it with e.g.:

fastboot boot twrp-3.0.2-0.img
[Wileyfox Swift] Gabler:
Hi, I have the same problem. My Swift is blocked on TWRP and it doesn't go into bootloader. How I can to do?
[Nexus 6P Q&A, Help & Troubleshooting] rasikreality:
Hi!

A month ago I bought a second-hand Nexus 6P and I ordered a silver casing because the black color that brought didn't like to me.

When I opened it and change the housing the guarantee was logically lost, and now I wondered if it was worth to root it because I don't lose anything.

I don't want to change the ROM. I'd like flashing MODs to improve sound quality or increase the audio output voltage (I don't know if that's possible).

The problem is that I don't know how to do it with my laptop, which has Windows 10. I have always done on Windows 7 and I know the drivers on Windows 10 are a mess. Also, I don't know how to do things like flashing firmware or RRU through ADB and fastboot so, should I root it?

I would appreciate your help.

Thank you!
[Nexus 6P Q&A, Help & Troubleshooting] Quasar:
You don't lose your warranty when rooting Nexus devices anyway, so even if you hadn't opened your device up it wouldn't have had a problem. There's no mess with drivers on the Windows 10, really. Extract ADB and Fastboot from the Android SDK and follow one of the many guides available in the general section. It's easy enough to unlock and root the device and/or change the firmware too if you had to. Just read the available guides. :)
[Nexus 6P Q&A, Help & Troubleshooting] GallardosEggrollShop:
Exactly! It's very simple. I did have issues with the drivers on my Windows 10 computer but it was a matter of uninstalling and reinstalling them.
[Nexus 6P Q&A, Help & Troubleshooting] Heisenberg:
You have nothing to lose, so why not?! Take a look at my guide, it should have everything you need:

http://xdaforums.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
[Nexus 6P Q&A, Help & Troubleshooting] rasikreality:
Thank you for your replies [MENTION=5585603]Quasar[/MENTION] [MENTION=665632]GallardosEggrollShop[/MENTION] and [MENTION=7514361]heisenberg![/MENTION] Now I have only two questions:

1. System updates by Google support other recoveries apart from Android original recovery (I'd like to install TWRP)?

2. When I unlock the bootloader I'll lose all my data (factory reset)?

Thank you!
[Nexus 6P Q&A, Help & Troubleshooting] Heisenberg:
1. No, other recoveries cannot flash OTA updates. You can't apply an OTA if you're rooted anyway, you need to flash the factory images to update.

2. Yes, unlocking the bootloader completely wipes the device so back up your personal data (photos etc) first.
[Nexus 6P Q&A, Help & Troubleshooting] Eric214:
Plus, in my opinion... It's a Nexus, why would you buy a Nexus if you weren't going to root it? At least to see whats out there and you can always go back to stock if you wish.
[Nexus 6P Q&A, Help & Troubleshooting] galaxys:
Nexus + XDA = Happy Flashing! ;)
[Nexus 6P Q&A, Help & Troubleshooting] rasikreality:
Ok, im going to root my 6P finally, thank you all! Before the start, I want to solve a couple of questions and then I'll root it!

1. How can I update the Nexus stock ROM when I have TWRP? (Firmware, security updates or major updates like Nougat)

2. It's true that when my bootloader is unlocked, every time I boot the phone a message saying that my bootloader has been unlocked appears? In that case, Is it possible to remove permanently?

3. Is necessary make S-OFF like the HTC phones? I've never had a different phone of HTC, this is my first phone that's not an HTC.

Thanks!
[Nexus 6P Q&A, Help & Troubleshooting] Heisenberg:
1. I already answered this question in the post you quoted, you flash the factory images. It's all in my guide that I linked you to earlier.

2. Yes you will have a warning message, and no you can't remove it.

3. S-off is specific to HTC so no need to worry about that.
[Nexus 6P Q&A, Help & Troubleshooting] rasikreality:
I have only one question.

Is it completely necessary to flash regularly new hboot or firmware versions or I can use a non-stock rom with no worries about that?
[Nexus 6P Q&A, Help & Troubleshooting] Heisenberg:
No such thing as hboot, that's only HTC. You need to make sure your bootloader and radio are up to date, and you need to make sure you flash the correct vendor image to suit the ROM.
[Nexus 6P Q&A, Help & Troubleshooting] rasikreality:
Thank you VERY much! I am so lost since I don't have an HTC for first time and it's so good that the only two things I have to keep up to date were bootloader and radio. Only two questions, and sorry for being that heavy ?:

How can I get the latest bootloader and radio (a thread in XDA or something)?

How can I flash them? Will I lose my data every time I need to update them?

Thank you!
[Nexus 6P Q&A, Help & Troubleshooting] Heisenberg:
Have you read my guide that I've mentioned a few times? There are instructions for flashing the bootloader/radio/vendor there. Look in the section for flashing the factory images but only flash those specific files. And my index contains downloads for the factory images, which is where you can get the files you need.

http://xdaforums.com/nexus-6p/general/index-huawei-nexus-6p-t3213583