yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] robbbzilla:
It shouldn't matter where you bought it. It is a warranty replacement issue. I don't know where you live but in certain countries and states there are lemon laws. Your device is defective after numerous attempts to fix it. At this point they should replace the entire device under warranty.

I would try to get a replacement. You have nothing to lose.
[Google Pixel 7 Pro] EtherealRemnant:
I do find it interesting that this is the first defective phone I've had since the UTStarcom PPC-6700 I got in 2006 that had a defective SD card reader. I've had some HTCs with varying degrees of poor quality LCDs (yellow tints - I remember going to the Sprint store and having them open up like 4 Evo 4Gs before we found a white screen) but those were a case of different suppliers, not actual issues.

Pixels definitely have higher than normal reports of issues relative to other phones. When I went to uBreakiFix the girl who helped me actually said they have more problems with Pixels than other devices.
[Google Pixel 7 Pro] EtherealRemnant:
Yeah we will see. I gotta wait for it to act up more than it currently is though. Some random brightening and dimming is unlikely to be a big deal to them.
[Google Pixel 7 Pro] Medic1933:
Mr. Broken Record chiming in here but hold them to the fire on this one. Google makes entirely too much revenue to be as ludicrous as they have become with replacing their own lemons. 2 repairs more than warrants a replacement. It took some doing, but I got a replacement without getting a repair because it's unacceptable on a phone this new with no user damage. Literally just keep opening cases with reps. The right one will eventually replace it. Takes a lot of time and energy, but if a company can't be accountable to it's consumers with manufacturer defects, then they don't deserve your money next go 'round. I'll get off my soap box now haha. I believe you can get a new one though and I wouldn't let them get away with not making this right. Your carrier didn't make the phone, they did and something is clearly wrong with yours. It's on them.
[Google Pixel 7 Pro] robbbzilla:
Who knows what manufacturer Google is using. All we know is it is made in China.

In my personal opinion I think Google should use Samsung to make their next phone. Heck it has a Samsung screen, modem, and Google designed Samsung processor. They might as well go all the way.

I think it also has something to do with the amount of phones produced. The larger the production run and money given to the manufacturer the more the manufacturer probably does a better job. Just a guess?

Heck, even Apple has lemons. I have seen a lot of bad screens on certain devices and other issues. It just happens and it seems more and more like quality control is left to the customer rather than the factory.

Just keep at it. You deserve a working phone. Then you can decide what to do with it.

I remember buying a Pixel 4xl pre order. The first one shipped to me was stolen out of the box even though the outer box had not been tampered with. The second device had a screen issue and finally the third was good. It was a real headache with customer service but in the end I got a decent Pixel. In my experience if you get a defective unit no amount of repairs will help. Replacement is the only thing that will work.
[Google Pixel 7 Pro] EtherealRemnant:
Yeah I'm just not really wanting to put in the effort. I don't have the patience I used to. Would just be easier to write off any future Pixel purchases, which I was planning to do as long as they use Samsung modems anyway.
[Google Pixel 7 Pro] Medic1933:
I completely understand that. I just hate it for you and know how frustrating it can be. It's better priced than a lot of flagships, but certainly not a cheap device. Then you had to cover the cost of transportation on 2 separate occasions when they should have just made it right. I hope your screen decides to start behaving or they go back to Qualcomm next gen (they won't haha). Best of luck with it!
[Google Pixel 7 Pro] asj0422:
My screen did the same damn thing. The edge started flickering and then showing lines and then things went green.

I got mine from Amazon, and I *****ed enough that they sent me an advance replacement for it. It seems like this is an ongoing issue with the p7p series.

Maybe another class action should be underway...
[Google Pixel 7 Pro] asj0422:
I really like pixel's software, but they have to fix this hardware **** if they want to be taken seriously. Between this and the camera glass shattering, I hope they sort out the pixel 8 and we don't have to deal with this **** again.
[Google Pixel 7 Pro] jaseman:
So far my P7P has been great. But I did send back an "A" series Pixel a few years ago because it was junk. I have had far, far more positive experiences with every phone I have ever owned with the best ones being from OnePlus and Motorola (from years past on the Moto's). If Google doesn't get their hardware in order I may be compelled to go back to OnePlus, or heaven-help-me Samsung. I hate Samsung's Bixby and other redundant shovelware apps, but they do make good hardware. ADB AppControl to the rescue for ALL Android phones! So I'll wait and see what comes with Pixel 8 before making any decisions.
[Google Pixel 7 Pro] EtherealRemnant:
I definitely didn't expect this thread to grow as much as it has. Hopefully your new phone ends up being fine. It's crazy that this is happening so early in the life of these devices.
[Google Pixel 7 Pro] Superguy:
I'm going to have to take mine in. I'm having freezing problems a lot in Firefox and the screen cuts out in games and Firefox. Sometimes it goes all black, sometimes all yellow. I've been hitting it on my hand to "wake" it up, but then system processes start to crash.

I'm going to pull my data off tonight when I get home from work and take it over tomorrow to get fixed. Hopefully I can get them to replace both the screen and the motherboard, making it practically a new phonel.

I gotta say, I like the openness of the phone and I like it as a whole, but these hardware problems are a real pain. I've never had hardware problems like this. I would definitely think twice before buying another Pixel down the road.
[Google Pixel 7 Pro] EtherealRemnant:
Well it's pulsing the brightness every so often (auto is off). Come on man, I just need it to last 9 more days...

There is definitely some kind of short that's affecting the panel and slowly killing it. That's the only thing that would explain it.
[Google Pixel 7 Pro] ProtoKun7:
I had this exact issue with mine too: occasional green flicker when the screen was off (AoD), random streaks, later on also the screen turning completely off, all exacerbated by heat. In my experience I had to go to an EE store (UK) which is listed as an authorised repair centre. They apparently use a company called SBE for the actual repair and they tried to claim fractures on the digitiser (couldn't get anybody to show me any proof of this) and quoted me almost £200 to repair it. Instead I took it back and had to just RMA the whole device. This was all despite the phone being in great condition otherwise with no drops or dents or anything. Wasted several days on that whole thing, all told. One day wasted handing it in at the EE store and getting absolutely nowhere and overall I reckon if I'd been able to arrange an RMA on the same day I would have saved an entire week.

The EE people in-store seemed nice enough but the people they forward it to seem really dodgy based on that. Despite confirmation it was under warranty and going to a Google Authorised Repair centre, SBE Ltd tried to charge me for it. I don't see what's to be gained from that, as if it's confirmed to be a warranty repair I imagine they would communicate with Google if they needed to be reimbursed, so I feel like the only reason to charge me would be to try and double dip.

(I got a text a few days afterwards asking me to rate my experience. I would have rated it a hard zero but my text wouldn't go through. I think because I'm not on EE's network it couldn't communicate to the short code properly.)
[Google Pixel 7 Pro] Superguy:
Why 9 more days?

Just got mine back. I'm thinking now's a good time to dump it, but I have to fix the camera glass first. Does the factory warranty transfer with the sale?

One good think about the UBIF shop I've used - they don't care about rooting. Just warned be that it could be a problem if I send it back unless I can wipe it somehow at that point. Still warrantied it despite the camera glass being cracked. Said Google would consider that physical damage if I sent it in.

After using my OP9 for the last week, I may just use that for a while longer until something else I want comes out.

Last Pixel I'll ever buy.
[Google Pixel 7 Pro] EtherealRemnant:
I can't pick up my S23 Ultra until Friday and I don't have another device that has eSIM so I would be without access to my 2FA codes for that period of time.

Google doesn't care about rooting either. It doesn't void the warranty at all. One great reason to have a Pixel.

I would use my OP9 if it had eSIM + pSIM or dual pSIM but OnePlus decided to screw US customers that year.

I don't know that this will be my last Pixel ever but it will be my last if Google continues to use Samsung modems unless Samsung magically catches up to Qualcomm at some point.

I'm pretty sure the warranty on the Pixel is not transferrable.
[Google Pixel 7 Pro] mosi hd2:
So sad, to see many people experiencing this issue. I'm experiencing too.

But I have a workaround for it. Just install android 13 beta 3.2. It doesn't solve the issue completely but it will be much better.
[Google Pixel 7 Pro] mosi hd2:
I've reported this issue in android issue tracker system. hope they fix it.

Google Issue Tracker

issuetracker.google.com
[Google Pixel 7 Pro] Kf1st:
Just to throw my .02 in. I had the same flickering screen issue after about 2 months with my GoogleFI P7Pro. Google replaced the screen and the 2nd one went out about 3 weeks later. Then the next one went out in a month. They replaced the phone 3 weeks ago and so far so good.

For some reason I think this issue has to do with a case being on the phone. Something to do with torsional force being applied to it. I switched cases on my newest phone and I'll see how it goes. I noticed on the 3 previous ones that once the flickering started if I removed the case and laid the phone flat(very useful to have a phone you can't pick up, btw. lol) it wouldn't flicker anymore. The moment I picked it up and twisted the top of the phone it would flicker and go black. Something to think about.
[Google Pixel 7 Pro] dodgebizkit:
This
[Google Pixel 7 Pro] dodgebizkit:
It came back from repair a few weeks ago and it looks like this-

The only difference is that it no longer switches off the screen completely.

I have now requested a replacement phone.
[Google Pixel 7 Pro] EtherealRemnant:
That's just absurd. I can't believe that all of these panels are defective. More than likely there's a short somewhere that seems to be somewhat common and if that's the case, it's just a matter of time until the majority of them fail and Google has to do yet another egg on their face announcement of a repair program...
[Google Pixel 7 Pro] dodgebizkit:
I am in the process of getting the phone replaced, but I've also just updated to this month's fw and early signs say that miraculously it may have fixed the problem .. I'm not holding my breath though.
[Google Pixel 7 Pro] dodgebizkit:
It definitely did seem to have solved the issue but I've seen some flickering again today so I'm taking no more risks, I'm getting my handset replaced.
[Google Pixel 7 Pro] EtherealRemnant:
Well I have needed to be able to test a device with eSIM and pSIM to see if running the same network causes data loss so maybe I should just switch and see what I see.
[Google Pixel 7 Pro] Faveer:
Hey dear, I noticed streaks on my OLED screen, and it turned green. Contacted support got a Pixel screen replacement from uBreakiFix in an hour. Pleased with the outcome.
[Google Pixel 7 Pro] EtherealRemnant:
Well my Pixel 7 Pro's third screen finally failed today. Very inopportune time too as my S24 Ultra's screen is terrible and I need to exchange it but I need a phone to be able to Uber back after the exchange so I guess I'll be spending an hour at Best Buy setting up the bare minimum on my exchange...

I've been using the Pixel off and on this whole time since my last screen replacement in early 2023 and it's been fine. Hasn't been dropped or anything. In fact I used it to go pick up my S24 Ultra on release day...
[Google Pixel 7 Pro] IronSkillet:
This p7p has had a screen replacement and within 3 months it has a defective display.

The issues described here are similar to the observation I have made.

In the search for insight on the cause, the best guess to a common cause is the stress exerted by any case.

The screen and or frame seems to have a design flaw. This somehow causes a very similar fault pattern.

Since removing the case the defects seen to have stopped worsening... Two weeks .

For the first month I had no case for the p7p,

Then within a month of case exposure the screen seems to have taken permanent damage.

The screen will be replaced with the warranty provided by the repair, the next display will live precariously,.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] pipin18:
When i try to enter fastboot i am not getting the logo but just the word "fastboot". My poco f3 works perfectly but will not enter the fastboot mode with the logo. When i connect to the pc it is not recognised in this mode. I would be grateful if anyone can advise how to get it back to normal.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] bozinsky73:
New fastboot logo is the orange FASTBOOT word. So it is already normal. If it's not recognized it may be a problem with drivers, usb cable, debug authorization/permissions.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] johnr64:
Hi,

I have had my F3 for 13 months and Fastboot and windows can still be temperamental, my PC has 10+ usb sockets.

As bozinsky73 Suggested installing the correct drivers and maybe a different USB-C lead might help, you could try running MiFlash and then select the drivers tab and then Install, as some XDA users have had success with this.

I have tried 3 different (Aliexpress) Silicone coated leads and these cause my PC to flag up "unknown device" when in FASTBOOT, i also have 2 leads that look like the most cheapest ones out there and these work OK, even thou some times i still have to switch to another USB socket on my PC.

I run 3 different versions of windows on 3 different partitions that run, Win 7, Win 10 and Win 11 and i am still faced with the same issue regardless of the windows version.

I hope you sort it.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] pipin18:
Thanks for the replies and solved it with a new cable. I was using the cable that came with the phone but obviously must have damage somewhere. Thanks anyway.
[Realme 8] droidx8:
Hey, I've tried (and failed) to flash TWRP on my Realme 8, and I ran into a big problem:

The device boots up into the stock ROM, but the touchscreen is unresponsive and I can't figure out a way to power off the phone. I've tried to push the power button for up to a minute, i've tried going into recovery (vol+ and power button), tried adb (the PC is unauthorized, so it didn't work). Got a USB-C adapter to plug my mouse into the phone, but it wasn't recognized.

What can i do to power it off? I believe i could reflash the stock firmware after powering it off.

Thanks for any help!
[Realme 8] ethical_haquer:
Try to force a reboot by holding power and volume down.
[Realme 8] ace2nutzer:
Right, at least 2 buttons needs to be pressed for SoC reset, try them all, you'll find the right one.
[Nokia 1 Guides, News, & Discussion] aiSanaul:
So, after trying more than a few methods I finally gained root on my TA-1066. 😴😪

If you also wanna root, here is how: 👇

To Root Nokia 1 (TA-1066) (Pie - Android 9) (Dual SIM)​

What you're gonna need:​

Working PC, 💻

Some Packet Data, 🌐

Some knowledge of ADB & Fastboot commands, 😴

Some storage space for storing Back Up of your phone, 💿

and a Working Brain 🧠🤣

WARNING!! ☠​

I am not responsible for anything goes wrong to your phone by following the steps mentioned in this method. So, please do anything with care and if you don't know what is this, simply Stay away! 🤐​

Make a Backup Of your phone's Data:​

Please make a Back Up of your data stored in your phone tp a safe place in your PC or somewhere in a disk. So, if anything goes wrong you can retrive it back from there.

Now Follow these steps:-​

Download attached ⬇

boot.img

& keep it in your phone, we'll use it later.

Root boot.img using Magisk:

Download Magisk v25.2 from here.

Install Magisk app and open it.

Tap Install.

click Next.

click Select and Patch a File.

Select

boot.img

that you downloaded.

click Let's Go. (let the process complete)

Now rooted boot image will be stored in Download folder of your phone, move it your PC.

Install adb and fastboot into your PC​

Download the setup file from here.

Unzip and Run it as Admin.

Tap Next until it installs.

Enable developer options and turn on USB Debugging​

Goto Settings > System > Advance > About phone > Tap on Build number 7-8 times.

Go back and Tap Developer options > (scroll down) Turn On USB debugging.

Now connect your phone to your PC using USB Data Cable.

A prompt will appear asking permission, Tick Always allow from this computer and Tap OK.

View attachment 5806599

Let the USB Data Cable connected and follow below steps.

In your PC open CMD and start typing these commands:​

Confirm that your device is connected:

adb devices

View attachment 5806587

get your serial number by entring this command:

adb shell getprop ro.serialno

calculate md5 of the serial number using this site: https://passwordsgenerator.net/md5-hash-generator/

it'll look something like this D4423199AC65U1237C86D0E6BBF65243M

Reboot to bootloader:

adb reboot bootloader

Unlock using key (md5code=md5 of your serial number):

fastboot oem key md5code

Reboot and Turn on OEM Unlocking:

Settings > System > Advance > Developer options > Turn on OEM Unlocking

Reboot to bootloader:

adb reboot bootloader

Open Device Manager in your PC and follow this video below:

after doing as in video open CMD and type:

fastboot flashing unlock

Quickly press Volume Up button of your phone to unlock flashing.

Flash patched/rooted boot image. (boot.img = patched boot.img path in your PC)

fastboot flash boot boot.img

Reboot your phone to system.

fastboot reboot

Congratulations your Nokia 1 is now ROOTED!! Enjoy!!​

Hit thanks button if you liked the process. 😉

Feel free to ask any query. 😊

​

CREDITS​

Method taken from

this

thread by @androidlover5842 , some changes made by me.​

Thanks @Snoop05 for ADB and Fastboot.​

Thanks @savadam for video tutorial.

and Me 😁​
[Networking] Alfa90:
I have an old Galaxy GT-I9070 with LOS18.1 and gnirehtet (reverse tethering) that spawns a dummy0 interface together with its tun0 (used by default by gnirehtet). I suspect this dummy0 is what allow a few messaging apps to connect properly via reverse tethering. My Galaxy A5 (SM-A520F) has equally LOS18.1 and gnirehtet, but does not spawn a dummy0 interface when connected, so most of the apps work but the messaging ones don't. Is there a way to replicate the GT-I9070 configuration so that also the A5 can automatically spawn a dummy0 interface connected to tun0? (both devices are rooted)
[Introductions] Elia68:
Ciao a tutti e grazie mille per avermi accolto.... Siete una bella comunità, continuate così!

Mod translation: Hello everyone and thank you so much for welcoming me.... You are a beautiful community, keep it up!
[Introductions] Badger50:
Greetings, and welcome to XDA. As a "one time" courtesy, I have translated your first 2 posts. All members are required to post in English as

stipulated by XDA Rule #4:

Spoiler content hidden.

Thank you for your cooperation, and enjoy your stay on XDA.

-Regards: Badger50
[Introductions] Elia68:
Hi...I wrote and posted in English but evidently, the automatic google translator must have translated back into Italian when I pasted my post...sorry, it won't happen again, I'll be more careful....
[General Questions and Answers] James_Watson:
On an AVD on Android 9.0, the stock Camera app said "Insert an SD card before using the camera".

Hi,

I created an AVD on API Level 28(Android 9.0). But when I tried to take a photo, the stock Camera app said "Insert an SD card before using the camera". So, I failed to take any photos at all.

View attachment 5806581

In fact, in the AVD settings, there is a Studio-managed SD card for this AVD.

Could I have the Camera app on this AVD work without an SD card?

I have cleared storage of the camera app. But it doesn't work yet.
[General Questions and Answers] James_Watson:
The version or detailed info about the Android Emulator and API Level 28 system image I used are as below.

View attachment 5808371

View attachment 5808373

Was the issue caused by some defect of the Android Emulator or the system image?

Btw, does this AVD on your PC have the same issue, too?
[General Questions and Answers] James_Watson:
At last, I found that the issue was caused by that x64 system image. Use the above x86 system image instead even if your host is a 64-bit version of Windows.
[LG V35 Questions & Answers] qwerlloyd:
Any solution to this?!

and what firmware I gotta use that is compatible 🥺 (solved- via partition dl)

lgup version used:

1.16, 1.14, lgup dual

View attachment 5807413
[LG V35 Questions & Answers] cmrntnnr:
Give Partition Download a go instead of Upgrade.
[LG V35 Questions & Answers] qwerlloyd:
thanks it works
[LG V35 Questions & Answers] qwerlloyd:
can I ask another question?! Sir

if it's possible to update directly from Android 8 to Android 10?!

or I will download the latest Android 9 first and update to that firmware before updating to latest android 10 firmware?!

thanks in advance
[LG V35 Questions & Answers] cmrntnnr:
I have not tried going directly from 8 to 10 so do not know.
[LG V35 Questions & Answers] qwerlloyd:
I will try it, first update to the latest pie firmware available on lg-firmware site.

then If possible update to Q 😁
[LG V35 Questions & Answers] qwerlloyd:
and last question sir what the best variant between this:

open_kr vs Lg u+ vs Kt vs Skt?!
[LG V35 Questions & Answers] cmrntnnr:
OPEN_KR is what is recommended. You should follow cloud's instructions to localize. If you are in NA, I have an NA OP image ready to flash.
[LG V35 Questions & Answers] qwerlloyd:
thanks sir,

Is it possible to crossflash NA OP from Korean?! just for future reference Sir ☺️.
[LG V35 Questions & Answers] cmrntnnr:
No, there is a size mismatch. You should read cloud's thread on localization for instructions. There is a link to a customized OP for NA if that is the localization you need.
[LG V35 Questions & Answers] qwerlloyd:
noted sir thanks
[Nothing Phone 1] dreas74:
Hi Guys,

Unfortunately, the stock camera app is not the best cam app and takes only average photos. so, I investigated which cam app is better, in my opinion, and makes better photos.

In my experience, the LMC Gcam app, with a fitted XML, makes good pics. I don´t know if I can share telegram links here. you can find more infos and Cam apps in the "Nothing Phone Photography" group on telegram.

{Mod edit: Link removed}

What I am still missing, is how can I start an alternative cam app by double-pressing the power button. If someone has a solution for that, please let me know.

What are your experiences and findings about the camera?

Regards

dreas