yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] andygold:
Just wanted to share some info in case anyone else has this issue.

First P7P was highly defective. Video issues, connectivity issues, fingerprint issues, upload speed issues and a few more. Phone went back to Verizon after they sent me a replacement. I couldn't get the new phone to connect to the network, so I brought it to the local Verizon store. Guy pulls the SIM out of the old phone and places it into the new phone, and everything then seemed to work. I had assumed the new phone would connect via the eSIM, but I was totally wrong. Dummy me! Now I know

So, new phone seems to work until the first time I call a business number. Rings once and then hangs up. I can call my house and other cellphones no problem, but not certain business numbers. Can't even call *611 or #832 as both come up as "invalid number". Many, many hours of customer service at the tier 1 level doesn't fix the issue. Factory reset, clearing network connections, cache, safe mode, refreshing network and towers, nothing helps. Finally they connect me to tier 2 who thinks it may be a pSIM issue. She had me remove the SIM, and she tries to set up the phone on the eSIM. no luck, as Verizon states the IMEI number for slot 2 is not listed in Verizon's database. She puts in a ticket to get that number added, which is supposed to take a few days. She also told me that the SPAM settings (even though I'm making outgoing calls) had been problematic. She also said that some of the call filtering settings at Verizon's end can cause this, but neither seems to be my issue.

I head down to the local store and ask for a new SIM. I had asked for a new one when I got the replacement phone but the Verizon guy just put my old one into the new phone. Be advised, tier 2 says that the stores are told to never use the old SIM, and to always place a new one. Old SIMs can bring along old problems into the new phone! Well, I guess the store doesn't follow company policy.

So, getting back to the story... Today when I go in and request a new SIM, the guy says that my old SIM, which has a black stripe at the top, could be the issue as black stripe Sims supposedly have been having issues for a while now, and they've been replacing them with Sims that are totally white, with no black stripe. Why the guy 2 weeks ago put the used, black stripe, SIM back in, who knows....

This seems to have fixed the issue, as the phone numbers that I couldn't call, now work, including 611, *611, & #832.

Now, the only issue I'm having is that every time I've turned this new phone off, the color palette reverts to factory stock when the phone turns back on. My selected color palette (Settings/ Wallpaper & Style/Wallpaper Colors) still has a checkmark on it (greens in my case), and appears to be the selected, active colors, but the phone is using the factory stock blue color palette. My old phone kept the greens even after a restart, so I don't know what other issue is going on with this new phone. It's not a deal breaker, but there's something still not right.
[Android Software/Hacking General [Developers Only]] Chakka1:
Are there any updates on the Amazon Fire 10.1 operating with the OS7.3.2.6? The OTA will not turn off using the Fire toolbox 30.2.
[Xiaomi Poco X3 NFC Questions & Answers] EvilKain:
Hello there,

I dont know what Iam doing wrong, but I dont get it managed to flash twrp on my Xiaomi.

I attached what the console says.

I can see the device in fastboot mode, but it dont flash if I give the command for it.

Could someone please help me?

Thanks.
[Xiaomi Poco X3 NFC Questions & Answers] NOSS8:
INSTALLATION:

1. Download the TWRP image file to your PC.

2. Put your device into fastboot.

3. Type the following command to flash the recovery:-

Code:

fastboot flash recovery "name_of_recovery.img"

4. On installation of TWRP , to boot the recovery do:-

Code:

fastboot boot "name_of_recovery.img"

The device will automatically reboot into TWRP, and you will have TWRP as your permanent recovery!
[Xiaomi Poco X3 NFC Questions & Answers] EvilKain:
Thanks for your answer.

Until 3. I have done already.

But on my older phones there was something Happening on the Phone itself.

But I will try step 4.
[Xiaomi Poco X3 NFC Questions & Answers] EvilKain:
Worked like a charm. Thank you.
[Google Pixel 7 Pro] andygold:
If anyone has been following my P7P saga, with the issues and problems.... Here's another question.

Currently my slot 2 eSIM is not recognized by Verizon's database, even though this phone was purchased directly from Verizon. There's a ticket that's been put in to have the slot 2 IMEI number entered into Verizon's database to fix this particular issue.

I had been having issues with my pSIM, so Verizon was going to switch me over to the eSIM to troubleshoot the pSIM, but couldn't due to slot 2 IMEI not being recognized.

I got a new pSIM today, and that seems to have fixed my calling issues. There the possibility that they may however switch me over to the eSIM in a few days...after my S2 IMEI is recognized by the system.

My question is... Are both pSIM & eSIM equivalent in all ways? Is it beneficial to be using one or the other? Basically, do I lose out on any feature(s) by having any particular one? Verizon tells me that only one can be active at any time as per my current contract. I could get both activated if I want to pay for it, for reasons of traveling to other countries for example.
[Google Pixel 7 Pro] blackhawk:
Interesting. A sim card is superior as if it fails it doesn't total the phone. It can also be remotely configured as well as transferred to another phone; very nice if you have a backup phone as I do. Takes the carrier out of the setup loop. You simply slam the sim into the phone you want to use that day. Of course the carrier would love you to have a $eparate sim for each device. The manufacturer likes to save money with no physical sim with the knowledge if the esim fails out warranty it effectively totals the phone.

It's funny how they claim it's 70% more efficient but the last couple generations of smart phones generally have huge batteries and poorer SOT🤣

Reminds me of Intel and MS; Intel builds more powerful hardware while MS compliments it with more overhead. Net result is little user gain.
[Google Pixel 7 Pro] 96carboard:
That's not right.

esim just means that the data is transferred to the phone and its data/functionality is stored in the device's flash memory. This does NOT add any additional points of failure, since if the flash memory or some of the relevant circuitry fails, it will take out the phone whether you are using esim or psim.

What it comes down to is PURELY a matter of convenience. If you travel a lot, it can be more convenient to have the psim slot available to drop in a local sim. If you don't travel a lot, it can be more convenient to keep a psim in case you need to switch to another phone in an emergency. You need to think about what is more convenient FOR YOU and make the decision accordingly.

One additional piece of info; the routines that load the esim from the carrier are implemented in closed source binaries, part of gservices. If you don't trust those binaries, then you might want to avoid esim altogether. Mostly this applies to google-free AOSP distributions, like grapheneos (although they do have the option of installing gservices and esim).
[Google Pixel 7 Pro] blackhawk:
^That's not right...^

The esim chipset mounts on the mobo on older phones. You are correct that it was integrated into at least the newer Qualcomm SOC's.

View attachment 5812751

Regardless it takes away end user options that only a sim card provide.

Lol, better security for the carrier...
[Google Pixel 7 Pro] jaseman:
Esim is still NOT ready for mass adoption!!!!

Psim all the way for many, many reasons!
[Google Pixel 7 Pro] blackhawk:
I love my sim and expandable storage slots... and the options they give me. Been blowing off the new Samsung flagships for years now because they are less functional. The S23U is an expensive dud too.
[Google Pixel 7 Pro] LLStarks:
Esim is generally better until you have to read out a 30 character EID to a support person. Usually persists through a factory reset too.

If you need to do a lot travelling or network testing, having physical sims might be better until esim MEP is enabled.
[Google Pixel 7 Pro] 96carboard:
In other words, I was dead on.
[Google Pixel 7 Pro] blackhawk:
Oh yes, you were magnification.

Unfortunately a psim is still more desirable...
[Google Pixel 7 Pro] EtherealRemnant:
I dig the eSIM. Annoys the hell out of me having to pull my phone out of my case to install a pSIM and I don't have to wait for the pSIM to come in the mail. Plus with all the carriers offering free eSIM trials, I could easily go 5-6 months of the year with free service for data and $5 plan for minutes and texts on my pSIM or a second eSIM (if they ever re-activate eSIM MEP, pissed that they removed it since it was working fine for me) as I upgrade yearly.
[Google Pixel 7 Pro] OzBoy1:
In my experience it comes down to the telco, some are great with esims others are truly horrendous. I have no experience with Verizon so can't help you directly. Before swapping I would get some clear answers from Verizon about the differences between each sim but more importantly the support systems in place if the esim goes wrong. I am OS at the moment had my phone stolen got a new one and my provider can't seem to get the old esim onto the new phone. It's been over 2 weeks and 32 hours of my time, so make sure you have really robust understanding of how Verizon supports esims. Good luck whichever way you go.
[Google Pixel 7 Pro] christopher68369:
For myself I'm happier with having a physical sim card. I switch between my iphone 14 pro max and pixel 7 pro. I broke the screen on my p7p so I tried to use the esim since that's all you can use for newer iPhones now and with Verizon you need your current phone in order to do the switch on Verizon's website. Long story short I spent an hour chatting with someone and because I couldn't see the code they sent to the p7p to activate the 14 pro max I had to go to a store and show them my license. Than I spent another hour for them trying to activate the iPhone with esim . It was quite the pain in the butt compared to a physical card that you can just switch with another device until you get a replacement device
[Google Pixel 7 Pro] joewoo:
Same guys going at each other rofl
[Google Pixel 7 Pro] supermansaga:
eSim is much better on iPhone/iOS than on Android 13. I have spent countless and unnecessary hours to fix T-Mobile prepaid eSim issues: redownloading, reading back IMEI/EID number to customer reps, error issues between re-installation of operating systems, etc.

I heard Android 14 would fix this.
[Google Pixel 7 Pro] lowik2:
Ofc my both sim providers dont do esim.

one question , so p7p accepts 2 esims and one psim ?
[Google Pixel 7 Pro] supermansaga:
I think three esims, except only one of them could be active. Iphone can have two esims active, even if from the same carrier. A lot of catching up to do for Android 14
[Google Pixel 7 Pro] Ducter:
I have both a psim and esim, both on T-Mobile and there's constantly a significant difference between signal strength between the two. Psim simply gets better reception somehow, to the point the esim ceases to function.View attachment 5858349
[Google Pixel 7 Pro] supermansaga:
with each security update, it appears the eSim would be treated as associated with the older device. And you need to redownload it or reach out to customer service. At least that's my exp as prepaid customer. Maybe it's diff for postpaid who could manage this on their own
[Mogul, XV6800 General] bones20:
Hi Guys,

I am lately seeing this issue. When I receive international calls, I dont see the plus code (011) in the callerid anymore. Also, these numbers dont get identified from my phone book who have the numbers with the plus codes (011).

thanks
[Google Pixel 4 Questions & Answers] Sanman99:
(edit: is my device bricked? it won't load Android now, but is in fastboot

also should i have updated Android first?

i'm thinking of keeping it stock at this point, or maybe finish rooting if possible.)

copied below is what i put in Command Prompt

and then tried downloading adb and fastboot again

i downloaded a fresh factory image for my version

and followed these instructions

How to root the Google Pixel 4 or Pixel 4 XL with Magisk

Looking to root your Google Pixel 4 or Pixel 4 XL? Here's how to unlock the bootloader and root the latest 2019 Pixel smartphones!

www.xda-developers.com

here's what i did:

fastboot flash boot "C:\path\magisk_patched-25200_NVE3j.img"

target reported max download size of 268435456 bytes

sending 'boot' (65536 KB)...

OKAY [ 2.199s]

writing 'boot'...

FAILED (remote: Failed to write to partition Not Found)

finished. total time: 2.348s

adb reboot bootloader

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

error: device '(null)' not found

C:\adb>

C:\adb>fastboot reboot fastboot

usage: fastboot [ <option> ] <command>

commands:

then i got the latest platform-tools, because i had installed some other ADB and Fastboot from XDA in an installer with some Google Drivers.

fastboot flash boot "C:\path\magisk_patched-25200_NVE3j.img"

Sending 'boot_a' (65536 KB) OKAY [ 2.355s]

Writing 'boot_a' (bootloader) Image missing OS version

OKAY [ 0.424s]

Finished. Total time: 3.129s

I also downloaded drivers from Google but i'm not sure how to install the DLL file until the device is out of Fastboot?

I tried using the menu to boot to Recovery. Didn't work.

In Device Manager, should i select Android Bootloader Interface to update to this driver?

Or wait until i can select it as a normal Android device after if it's possible to boot it normally?

And what about the website Flash.Android.com? could that get me to stock safely? but not rooted.
[Google Pixel 4 Questions & Answers] V0latyle:
If the next thing you did was

then ADB wasn't running. Use fastboot devices to ensure your PC sees your phone before flashing

Correct syntax is adb reboot fastboot/bootloader/recovery

The way it works is like this:

<tool> <command> <instruction> <options>

where:

<tool> is what you are instructing to send the command to the device: ADB for Android system or recovery, fastboot for bootloader or fastbootd

<command> is what you want the device to do, i.e.: devices / reboot / flash / boot / erase / etc:

devices tells the tool to display connected ADB devices

reboot tells the device to reboot, can provide instruction for what mode you want it to reboot into, example: adb [B]reboot [/B]bootloader

flash can only be used in fastboot, tells the bootloader to flash the specified partition with the specified image, example: fastboot [B]flash [/B]boot <path to boot image

boot tells bootloader to immediately load the specified image without flashing, example: fastboot [B]boot [/B]TWRP.img

erase tells the bootloader to wipe the device; if no partition is specified, this will wipe user data. Use with extreme caution. Example: fastboot [B]erase [/B]data

<instruction> is the details for the command you're giving: adb reboot bootloader, fastboot flash boot <path to image>, fastboot boot <path to image>

<options> include details that may be necessary for various operations, example: fastboot update image-redfin-buildnumber.zip -w --skip-reboot --slot=all --force (this tells the bootloader to update using the specified update package, to wipe data, to not automatically reboot when done flashing, to flash both slots, and to ignore any baseband/bootloader requirements

<option> and <command> can be switched, for example: fastboot --skip-reboot --slot=all --force -w update image-redfin-buildnumber.zip

It's always important to make sure you're using the latest ADB platform tools.

What happened after you successfully flashed the patched image?
[Google Pixel 4 Questions & Answers] Sanman99:
thanks for the quick reply

and extensive yet clear

Yes i did: Fastboot Devices

and it shows the serial number

So when i tried flashing

It didn't flash though, did it? Does that look like it flashed?

When it took 2 or 3 seconds for a 64megabyte file from my computer, isn't on the phone itself.

And said: Image missing OS version

I checked online and other users have the same problem.

I'm stuck in Fastboot. I'm downloading Android SDK Studio and updated the USB Driver again.

I can't get into Recovery or the OS.

Enter reason: error boot prepare

when trying Recovery

I'm wondering if I should get GrapheneOS or if LineageOS is up to date on Pixel 4. I might not want to tinker as much anymore. I still might use the usual apps, but at least utilize root.

Should i be using a different USB cable/cord maybe?

I don't know if I have an OEM USB-c.
[Google Pixel 4 Questions & Answers] V0latyle:
When it says OKAY, that means it successfully flashed.

What version of Magisk are you using and where did you download it from?

You are using boot.img, not bootloader.img, right?

You're using the correct firmware for your phone (flame)?

It's starting to sound like you might be using the wrong image. Try reflashing the stock boot image (unpatched).

One step at a time, I think fixing this should be pretty easy.

It's worth a try. Are you using a USB A to C cable, or just C to C? If you're using a C to C cable, try using A to C.

Also, I don't know if you've noticed, but I do have a guide for rooting your device here. Check out the "Initial Root" section to make sure you're doing everything right.
[Google Pixel 4 Questions & Answers] Sanman99:
tried the (unpatched) factory boot image now

with a different USB cable (both are USB-A to USB-C)

C:\path>fastboot flash boot "C:\path\oriole-tp1a.221005.002-factory-f28b656e\oriole-tp1a.221005.002\image-oriole-tp1a.221005.002\boot.img"

Sending 'boot_a' (65536 KB) OKAY [ 1.627s]

Writing 'boot_a' (bootloader) Image missing OS version

OKAY [ 0.506s]

Finished. Total time: 2.465s

Yes i followed the steps

Here is what i originally did

Yes i downloaded a Magisk apk from the guide I mentioned which links to Github

and i updated the app after opening it

then patched the Boot.img and copied to my computer

I'm reading your thread now, which directed to this

https://xdaforums.com/t/guide-pixel-4-flame-unlock-bootloader-update-root-pass-safetynet.4443465/

Yes i downloaded the correct Factory image

I had enabled USB Debugging

and

yep i did the

fastboot flashing unlock

and this is where the problem happened

(well unrelated, i didn't rename the patched-boot.img)

fastboot flash boot <drag and drop master root.img here>

as i copied the output...it took like 2 seconds and gave that message saying something about the OS version

and i can't get ADB working...

Should I have used the PixelFlasher tool?

I don't know what went wrong or what to do now. As I said, some others have had this same error.

i just tried again with fastboot from the SDK directory

C:\Users\path\AppData\Local\Android\Sdk\platform-tools>fastboot flash boot "C:\Users\path\Downloads\oriole-tp1a.221005.002-factory-f28b656e\oriole-tp1a.221005.002\image-oriole-tp1a.221005.002\boot.img"

Sending 'boot_a' (65536 KB) OKAY [ 1.617s]

Writing 'boot_a' (bootloader) Image missing OS version

OKAY [ 0.491s]

Finished. Total time: 2.457s
[Google Pixel 4 Questions & Answers] V0latyle:
It's hard to say exactly where you're going wrong. Did you mess with vbmeta at all? You should get no error messages when flashing the original boot image.

Have you tried to boot even after getting the error message?

Pixel Flasher is useful, but it's very important that you understand how everything works under the hood, because the tool just automates what we'd otherwise have to manually do, and the tool can't necessary fix problems.
[Google Pixel 4 Questions & Answers] Sanman99:
(edit: you were right. it wasn't the right Flame image at all. it was Oriole.)

i don't know what vbmeta is.

I can't boot into anything but fastboot.

If I go on the Flash.Android.com website, should i flash to Android 12?

wait...what if it wasn't a Pixel 4 image

is there another that has tp1a.221005.002 ?

how can i check which one this is?

i know you said check if it says Flame

i know i was in the list for Pixel 4 flame when i was about to download

but i typed Ctrl+F and to search the right code

this is what i downloaded

https://dl.google.com/dl/android/aosp/oriole-tp1a.221005.002-factory-f28b656e.zip

---

ok.... here's Flame

https://dl.google.com/dl/android/aosp/flame-tp1a.221005.002-factory-f91d46b5.zip

so i just have to flash the Boot.img from this

and then patch it again, right?
[Google Pixel 4 Questions & Answers] V0latyle:
Yeah, that's a pretty common problem.

Don't worry about it

Do you mean bootloader? What do you see on the screen? Any error message at the bottom?

Just update to the latest version, if you haven't already.

Yes - since the Pixel 3, Google has started using what are called common system images, where the core system build is exactly the same across the entire range of phones. That makes updates much easier, because instead of having to rebuild firmware every month with the source Android update, they can just update the system image, while device specific partitions such as /product, /system_ext, /vendor_boot etc can be updated periodically.

The downside to this is that the updates can be confusing...because the build number is almost exactly the same for every phone, from the Pixel 7 all the way down through the Pixel 4a (since the 4 / 4XL are no longer supported)

As an example, the latest 4a build number is TQ1A.230105.001, and it's exactly the same for the 4a 5g, 5, 5a, and 6a. The Pixel 6, and 6 Pro are TQ1A.230105.002, and the 7 / 7 Pro are TQ1A.230105.001.A2. So there's minor differences there but for the most part the system images are very similar.

As long as it's for the Pixel 4 (flame) it should be OK. The factory images are named in this fashion: device-buildnumber-factory-hash.zip, so yours should be flame-TP1A.221005.002-factory-f91d46b5.zip

Yeah that's the wrong one

Yep

Yes. Just to make absolutely sure we are on the same page, when you download the file, you'll have the original zip (using barbet for my wife's phone as an example)

View attachment 5812273

Extract this to its own folder, which will have another folder inside it with the bootloader image, radio image, scripts, and the system update:

View attachment 5812283

Extract the "image-sunfish.tp1a.221005.002.zip" to its own folder:

View attachment 5812285

In this folder will be the various images for the system update; the one you need is boot.img:

View attachment 5812289

To get running again without root, just flash this:

fastboot flash boot <drag and drop the boot.img here>

Yep...once you're booted into Android, copy the same boot.img to your phone, making sure to delete any old ones, then patch it in Magisk, copy the magisk-patched_25200-xxxxx.img back to your PC, then flash it the same way you did the boot image.
[Google Pixel 4 Questions & Answers] Sanman99:
yeah yeah sorry i didn't reply

and thanks so much for the explanation

i was busy setting up my phone

but realized GrapheneOS isn't supposed to have root anyways

so now i have to decide if I want a custom ROM or just Stock with root, or maybe GrapheneOS and whether to put Google services on it and a bunch of apps defeating its purpose in some ways

flashing the phone went very smoothly. Then i put GrapheneOS on it.

if you have any advice about which ROM to do, i'd appreciate it

lots of features are built into Stock now anyways

in that case, i'd just reflash the Magisk patched boot image and then lock the bootloader in settings again?

or i have to reinstall Stock entirely

maybe Android Flash Tool and not that Flash.Android.com

i've done this for multiple phones over the years but i guess i've never understood it thoroughly

i can check for a guide....(and follow it carefully lol)

awesome help. this saved me a bit of stress today.