So, yeah, this is one of those "tester" phones that I recieved to do a review about, and there are a few things I am not clear about now that the Pixel XL has been out for awhile..
- I haven't gotten any OTA updates at all, and still on October security files; am I missing anything?
-not sure which "factory" version I should use as a fall back in case of a disaster
-not sure if I have to "upgrade" to a different build before I root and flash TWRP
Its actually kind of nice just keeping the phone pure stock so far, but I know its only a matter of time before the custom roms and tweaks start to show up, and, we all know how important it is to have a "fall back" plan, in case of a disaster..
Thanks to anyone who has the same situation, and has figured out how to move forward.. :good::good:
Still using my Shamu as my DD, but would like to get the Pixel XL to that point too!
wase4711 said:
So, yeah, this is one of those "tester" phones that I recieved to do a review about, and there are a few things I am not clear about now that the Pixel XL has been out for awhile..
- I haven't gotten any OTA updates at all, and still on October security files; am I missing anything?
-not sure which "factory" version I should use as a fall back in case of a disaster
-not sure if I have to "upgrade" to a different build before I root and flash TWRP
Its actually kind of nice just keeping the phone pure stock so far, but I know its only a matter of time before the custom roms and tweaks start to show up, and, we all know how important it is to have a "fall back" plan, in case of a disaster..
Thanks to anyone who has the same situation, and has figured out how to move forward.. :good::good:
Still using my Shamu as my DD, but would like to get the Pixel XL to that point too!
Click to expand...
Click to collapse
I got the same build number when i bought phone from best buy. I was able to unlock bootloader and root.
Edit: just unlock bootloader and then flash full factory image using adb and fastboot tools..
i've unlocked the bootloader, but not rooted or twrped yet, since there is really nothing to flash yet..
which image did you flash?
thanks
I downloaded the play services update from all mirror and it now gives the option to check for updates, you'll find the appropriate play services in my screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Pixel XL using XDA-Developers mobile app
I have the same version of play services as in your screenshot, and when I go into dev options/about/check for updates, it says no updates available...weird
still no update for me, very strange
Related
I just clicked on software update/check for update in the 'About Phone' section of my settings. I've never clicked it before. It said new firmware required. So I let it download the new software. Then it said charge battery before updating, and then it let me choose when to resume the update. I chose 3 hours. So I'm on stock Android 2.3.3. Gingerbread XWKE7 . What will it update to? I'm a bit worried now, is it going to wipe stuff? Everything's working good so I don't 'need' to update, but it would be nice to. Can I cancel the update? Only thing I can see is 'resume update'.
If you are from london uk. I think the OTA(over the air) version is gingerbread 2.3.4. I do not think it is a wipe device firmware but just to be safe, back it up via kies if your phone is not rooted otherwise use titanium backup if your phone is rooted.
Trust me I would go with the update. Some improvements. I wish we could update
For sure it is NO WIPE version.
Thanks guys, it's a relief it didn't wipe anything.
This is what I got. I thought it might also update Android but it hasn't. What benefits can I expect from the updated Gingerbread XWKF3?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Roman5 said:
Thanks guys, it's a relief it didn't wipe anything.
This is what I got. I thought it might also update Android but it hasn't. What benefits can I expect from the updated Gingerbread XWKF3?
Click to expand...
Click to collapse
Can you request a mod move this to Q&A please, it has nothing to do with themes or apps
and why have you made two threads?
your duplicate thread
i have reported this one...
Darkside Agent said:
Can you request a mod move this to Q&A please, it has nothing to do with themes or apps
and why have you made two threads?
your duplicate thread
i have reported this one...
Click to expand...
Click to collapse
Oh look, it's the voluntary forum policeman.
I made a duplicate thread because I wasn't sure which forum to post it in and I panicked a bit last night so needed a fast answer. OK?
Noticed my Android OS is using almost 1gb of which doesn't seem right.
https://m.imgur.com/p1bAilv,XvmBuaw
Any ideas?
Edit 3: Updating will fix this properly.
Edit 2: That didn't fix it...
Edit: I've seemed to "fix" it. From my reading it is a background service trying to do a seamless update in the background. I disabled "com.qti.service.colorservice" using titanium backup and restore and it seems my background data usage has stopped. No negative consequences so far but it may prevent seamless updates. Another fix would probably be updating to the latest patch version...
Idk but I hope you get an answer... Been killing my battery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also seems to hit Wi-Fi...
for me the issue did not go away until I did a factory reset
danw_oz said:
for me the issue did not go away until I did a factory reset
Click to expand...
Click to collapse
That would make sense if he was on stock but if he's using Titanium Backup his phone is rooted and might have other modifications. Flashing the latest factory image or if he's on a custom ROM doing a clean flash of the ROM would probably be the best idea under the circumstances.
jhs39 said:
That would make sense if he was on stock but if he's using Titanium Backup his phone is rooted and might have other modifications. Flashing the latest factory image or if he's on a custom ROM doing a clean flash of the ROM would probably be the best idea under the circumstances.
Click to expand...
Click to collapse
It has been a while but I'll reply so anyone else who comes will know. My state before and after was the same. All that changed was my OS version. Flashed the flash-all.sh after removing the -w, flashed the April bootloader (so no boot signing stuff, not the safest or recommended thing), booted TWRP, flashed twrp, flashed supersu, and then rebooted. No other mods besides adaway.
Are you on stock, rooted or unlocked bootloader? I had the same issue on stock (unlocked bootloader) where it was trying download an update repeatedly. I had to actually flash a custom rom to make it stop. Verizon did credit me back for the data it used.
Feel free to read my forum post there and try those steps. - https://community.verizonwireless.com/message/1500910#1500910
Don't ask me how I know but this is a backdoor to access your device. Be careful!
paulJW said:
Don't ask me how I know but this is a backdoor to access your device. Be careful!
Click to expand...
Click to collapse
downloading the security update(s) is a backdoor in?
Riiiight
y2grae said:
downloading the security update(s) is a backdoor in?
Riiiight
Click to expand...
Click to collapse
he said dont ask him how lol
I had to factory reset before this stopped
Hi there,
I have an issue with my S-Pen. it suddenly have stopped working with my device.
I own a N976B Note.
I guess it is an issue with the firmware, because the stylus is recognized on my other devices and the other styluses are not recognized on my note.
To help you understand the history i want to sum up some steps.
1. my phone had a t-obile branding, witch i wanted to remove, so i flashed another csc rom to get rid of that. (back in 2020)
2. After some annoyance by advertisement and the wish to get root and a custom rom, i installed Dr.Ketan Rom and was pretty satisfied, but the hassle with manual updates was a draw back, so i decided to roll back to complete stock to get OTA.
3. After some huslte and some rookie mistakes by trying to install a n975 stock rom on my device, i figured it out and flashed the matching rom. but now the stylus or the digitizer seems to be corrupted. the firmware version is not recognized by the phone. see the screenshot below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After some attempts to get it running again, i installed the very stock rom for my phone several times. (N976BXXS7FUI1)
I even checked "re-partition" and flashed with the matching pitfile in odin.
But there still no luck.
do you guys have some tips?
big thanks in advance!
greeting
Play with it. Spen's can be ornery as mules, once you get it going you're good.
They don't like being neglected for months.
My stock one was neglected. Took a couple days of playing with and then boom it stated charging like nothing ever happened.
Until it shows it's taking a charge it will do nothing. It will play dead.
Try clearing the system cache, reset network, pray to the pagan gods, play with it more... in and out, etc. Try enabling multiple spens, try disabling same... don't cross your spens, use the one for the 10+
Guess it just needs a good fk to get it going
I have 2 10+'s, both stock* and both run very well. Loading custom roms isn't needed, can kill desirable features and makes troubleshooting** much more difficult. That said if you're back on a stock rom the spen and associated hardware/firmware/software are likely good... it's just showing you who's boss. Play with it at least once a day, it will likely perk up in a week and stop it's wallflower act.
*with a package disabler and heavily optimized. I never update if it's running fast and stable; many apps are still running on their factory load as well. One 10+ is running on Pie, one on Q.
**Do Not enable power management. Make sure you didn't disable a needed parent/dependency apk! Do not ever, ever load Android 11 or higher, the kiss of death. Of course I could be mistaken, but probably not...
Is it just me or is this by design? Very weird
Not just you, not sure what googleeeee is smoking lately
wrecklesswun said:
Is it just me or is this by design? Very weird
Click to expand...
Click to collapse
Where is it reporting as SD1A.210817.015.A4? In Settings/About? Any other details such as what country you're in and what carrier you're using? Anything else you can tell us - are you rooted or applied OTA or factory image manually?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Mine is exactly what I flashed
USA, in Settings About, Build Number, Fi, Rooted, Flash three time manually from here
https://dl.google.com/dl/android/aosp/raven-sq1d.211205.017-factory-bf3da4b2.zip
Here
this build appears to be raven-sd1a.210817.015.a4
https://dl.google.com/dl/android/aosp/raven-sd1a.210817.015.a4-factory-bd6cb030.zip
wrecklesswun said:
Here
Click to expand...
Click to collapse
Are you using a custom kernel?
Can you check the hash of the full .017 firmware zip you downloaded and compare it to the hash shown on the website? (I check it after every time I download a full image zip, or an OTA zip)
minus case insens they match
BF3DA4B26554D84F99EAAD9837330C7D757F7D31442397EF89A98307D169D96A
bf3da4b26554d84f99eaad9837330c7d757f7d31442397ef89a98307d169d96a
no custom kernel
curious to know which is the one to apply for google FI or t-mobile or ATT (you'd think i'd know this working for TMO
wrecklesswun said:
curious to know which is the one to apply for google FI or t-mobile or ATT (you'd think i'd know this working for TMO
Click to expand...
Click to collapse
It was always my impression to use the one that makes sense for the region and carrier you use, i.e. US Carrier, but at least one knowledgeable person in the P6P section said the A1 is the correct one. I haven't had problems with the US Carrier one on AT&T (.017). My wife's phone isn't rooted and she hasn't gotten the December OTA. I mainly leave well enough alone on her phones since some things I've done on all her old phones (which is always the same phone as what I have, to make it easier for me to give her tech support) have given her unwanted surprises.
Oh yeah - you could always try the Official Google Android Flash Tool and see if you get any different results.
so is the 16.a1 correct or 17 for us carriers?
wrecklesswun said:
so is the 16.a1 correct or 17 for us carriers?
Click to expand...
Click to collapse
I don't have any better answer than my reply #12. Since the .017 says "US Carriers" on the page with the list of firmware, that's the one I use.
Hello guys, I just got this phone upgrading from my OP5T and I used to flash roms and kernels with TWRP, I see things have changed and I would not like to destroy my phone. I have always liked
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
trying new roms and messing with my phone, would really like to be able to flash Nameless or PE. I have seen that if you get the TMobile variant things get a little tricky with firmwares and phone versions. I got my SIM unlocked and I already have my unlock file to unlock my bootloader. Havent done that because I dont really know if my ROM flash would work.
Do I need to unlock my bootloader?
Can I already flash my ROM files directly from adb or do I need to convert my phone to EU with TSM?
I have seen that people mess with modules that I need to backup, is this only needeed to convert to EU version or would I need this for Nameless
?
Do I flash firmwares via fastboot/adb or do they come with local updates? Which I do not have because of TMO.
I have already asked a couple questions in the forum but I need to clarify myself with ROM flashing and prerequerisites with my 2127 version. I would really appreciate some help about this, Ive never tried getting help from forums and looks like this phone community is pretty active.
Go to the Nameless thread and follow the instructions to the letter and you will be fine!
TheGhost1951 said:
Go to the Nameless thread and follow the instructions to the letter and you will be fine!
Click to expand...
Click to collapse
Is it really that easy? I do not have to do anything else before because of TMO?
Jalpe_ said:
Is it really that easy? I do not have to do anything else before because of TMO?
Click to expand...
Click to collapse
No, just make sure you follow every step in sequence. Read the instructions a couple times to make sure you fully understand everything. Like are you suppose to be on Android 11 or 12 as an example.