yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S23 Ultra] Guyinlaca:
No. Every firmware and update has CSCs built in. It doesn't revert the software, it just activates features specific to your carrier (based on SIM). It's a partition of sorts.
[Samsung Galaxy S23 Ultra] xda-eh:
1) So when one switches from carrier one to carrier two, what happens to all the past updates that are associated with carrier one?

2) If the SIM card is removed and a new one isn't inserted (for instance if one's upgading to a new phone), will the future updates be "generic"? (Obviously when the old phone is in one's home with a wifi connection.)
[Samsung Galaxy S23 Ultra] Guyinlaca:
1. Each U1 software update contains all US carrier CSC partitions. If you update from A7 to A8, and change SIM cards, you'd remain on A8, but the CSC partition switches to the new carrier. There is never any rolling back, merely switching from one partition to another.

2. If you remove the SIM, your phone updates using the previously set CSC. If you used a T-Mobile SIM, it stays on TMO. The default CSC on U1 is XAA and there's little reason to go back to it, though it can be done with certain tools.
[Samsung Galaxy S23 Ultra] xda-eh:
Thank you.
[Google Pixel 7 Pro] gnulab:
Hi,

I am using Chromium v. 111 as my browser on Pixel 7 Pro. One day, it just won't display any websites anymore. The error message is "Aw, Snap"

These are the steps I had taken:

close all tabs

clear cache

clear user data

reset network setting

uninstall AdGuard

uninstall Chromium

reinstall the latest Chromium

What steps am I missing?

Chrome, Firefox works fine on this Pixel 7 Pro (even with AdGuard activated), I gather there is nothing wrong with the network settings.

The same version of Chromium is installed on my other phone (Samsung S21) and it works fine. This means the Chromium is good to use.

Appreciate for any hints.
[Google Pixel 7 Pro] simplepinoi177:
did you try earlier versions, from APK Mirror (or the like if it's not found there)? just to confirm if it's a latest version issue...
[Google Pixel 7 Pro] gnulab:
Thanks for the heads up.

Not sure why but the version I downloaded doesn't work on Pixel 7 Pro but the same version works fine on Samsung S21
[Google Pixel 7 Pro] simplepinoi177:
So did an earlier version work now on the P7P?

If it's a "Aw Snap" message for all websites, I wonder if it's some kind of "resolving" network type issue or if some issue on the "hosts" file is interfering...You said you were employing AdGuard -- but you already troubleshooted it with other browsers and/or removing it. Maybe it doesn't like Android 13 firmware update (whichever you are) and/or the recently updated Play System update. Might be worth sending a bug report to the devs for Chromium giving them a heads up on the issue.
[Google Pixel 7 Pro] lector007:
i have the same problem with chromium (build nr 1111) on pixel 7 pro, but not on all the websites. One that always crashes is github
[Google Pixel 7 Pro] azoller1:
Yeah I get this too with bromite or chromium. Nothing works, aw snap always. But brave works fine, it's annoying.
[General Topics] benhall847:
Software Download - Ulefone

Software Download,Support

www.ulefone.com

Hey everyone,

I just wanted to help spread the word that there is an official Android 12 ROM for Ulefone Power Armor 13.

This was not publicly announced anywhere as far as I know.

Your phone will NOT receive an automatic update for this (at least as far as my experience goes).

The only way to currently upgrade to the ROM is via the SP Flash Tool.

The only reason I know about this ROM is because I just happened to be looking through their website.

Find it here!

Software Download - Ulefone

Software Download,Support

www.ulefone.com

Edit:

I should note - if you do a full wipe & flash this ROM, it WILL flash you a new IMEI number

This IMEI number will be the same IMEI number for everyone running this ROM fully wiped.
[General Topics] Benovite:
I keep getting an "incorrect scatter file format" error when attempting to flash using SP. Either I'm doing something wrong or they messed it up. 😐
[General Topics] benhall847:
What SP Flash Tool version are you using?

I flashed with SP Flash Tool v5.2216

Another tip - move the ROM folder inside the SP Flash Tool folder.
[General Topics] Benovite:
Oh gosh you name it. I went thru numerous versions, some antiquated, some supposedly being the latest versions. Definitely used v5.22, probably twice if not more.

Thanks for the tip about moving the ROM folder. I figured the solution might have to do with the placement of the ROM folder or the SP flash tool folder(possibly both on C: drive) but I just kept on getting the same annoying error message. I'm gonna take your advice right now as a matter of fact. Hopefully it'll work for me as I'm assuming it did for you.

Incidentally, you probably know this already...about the wireless update section having the ability to apply updates 'locally' as well. Tried that a couple of times but no go. Just before you replied I was gonna try the old 'update from recovery mode' but I'd rather try your approach.

Here we go(again!) 👍
[General Topics] Benovite:
Ok.... I'm back. What's it been, over 4 hours since my last post? but in truth I can't claim to have been pulling my hair out for that long. Maybe 2 and a half lol.

>Alternate response: Wow. That was not fun. I somehow managed to boink my phone to seemingly do nothing but start in Fastboot mode.

**But wait, let me give credit and thanks where it's due to benhall. That little tidbit of advice that practically Everyone neglected to divulge about putting the ROM folder in the SP flash folder- a crucial step btw- was the key to getting Android 12 on my PA13. So ben, thank you very much. My deadened eyes sparkled when instead of constantly seeing 'stop feeding me this trash', the little balls of processing hope began-a-spinning to indicate that, yes Virginia, put that dang ROM folder in the SP folder. Again, never saw that in any instructions or any god-awful video that some people made to show how it's done, but instead irritate beyond belief because of their insistence of loud techno music as they talk, or babies yelling in the background while - ok I'm stopping. It was stressful to say the least because I knew I was almost there.

ANd to be fair I actually ended up watching (again) that one video that Ulefone condones on YouTube with the silent Asian (?) guy speeds thru the steps using that client sp thingy with the PDF instructions that Ulefone pushes. I tried SP v5.22 and 6.22 for that matter, but they just weren't working for me. Most likely entirely my fault, but I finally went back to square one with what they suggested and I went over that video again and again and finally....it took!

So, Android 12. It's big, had to reduce the display size because everything is Huge. Visually appealing, nice to get an update.

Funny thing is, sorta like benhall, I happened upon Android 12 in Ulefones Google Drive folder(just bored snooping around). But I was like Whoa we got 12¿?¡!😃 Googled for a quick sec, found this thread cause like the man said it hasn't been mentioned or reported about at all it's so new. If you know you know.
[General Topics] benhall847:
Hey man glad I could help!

Yeah I tried that just out of a hunch & it worked for me haha.

Same thing on my end - no tutorials anywhere mention to do that.
[General Topics] Benovite:
I've had mostly Samsung phones before I recently got the Uley. Sammy's are easier to flash with Odin compared to Mediatek's SP tool, all good tho.

Btw I don't know what camera app you prefer using (stock or 3rd party) but for what it's worth after many tries I've settled on SnapCamera version 8.7.8. The stock cam app is ok, still checking out the new goods with A12, but SnapCamera has a ton of flexibility as far as manual camera controls. Panorama resolution sucks compared to stock panorama res but the ton of other abilities makes up for it.
[General Topics] benhall847:
You can use TTSLex to remove the announcement from Google Phone - Call Recording

(it announces to everyone on the phone call that you're recording them when you start recording..)

FIRST -

In Settings > Security > Google Play Protect > Disable google play protect (this makes installing things google doesnt like work better. I've found it doesnt work as good if you have this enabled before beginning these steps)

Steps I used to remove the announcer

1. Open the Google Phone APK inside Google Play - uninstall/downgrade to the stock version of the app.

2. Open Google Phone - Make a phone call (someone has to actually pick up the phone) - record the phone call (it will be announced that the phone call is being recorded)

3. Download TTSLex

4. Set TTSLex as your phone's text to speech.

5. Open the App Info of Google Phone - force stop

6. I forget if this step is correct or not.. - delete storage/cache for Google Phone apk

(if this doesnt work, try again & skip step #6)

7. Update the Google Phone APK before opening it.

8. Make a phone call & record the phone call - enjoy no more announcer <3

Android Auto - Screen2Auto APK for mirroring your screen onto android auto! (movies/tv shows/youtube on car screen)

Steps -

1. Open Android Auto via Google Play store & confirm its downgraded/uninstalled to the stock APK.

2. Download AAAD

GitHub - shmykelsa/AAAD

Contribute to shmykelsa/AAAD development by creating an account on GitHub.

github.com

3. Using AAAD - install Screen2Auto

(they only give you 1 free install per month, ive tested them all on this ROM - Screen2Auto is the best to use.)

4. Update Android Auto & enjoy! <3

Pro tip for Screen2Auto - if you go to Screen2Auto > Other Settings > Alternative touch enabled > Profile 2 (Poco)

This allows you to use the touch screen of your car to control your phone while mirroring your screen.

(pause/play videos from car screen)

I also disable the Screen2Auto > Settings Launcher > S2A Launcher

But you could play with it & enable that if it suits you better than me.

(gives you a launcher page for launching apps from Screen2Auto - customize which apps are shown on the launcher etc..)
[General Topics] I opus l:
Hey all, thank you for the info on Android 12. I'm kind of out of the game with updating, ROMs, and rooting. I've been running stock 11 rooted since I've gotten this phone. I actually backed everything up and tried to update with Android 12 stock rom yesterday. I haven't messed with spflash since I've had my Armor 7. For some reason I cannot get this to work. I'll tried the Linux sp version, but gave up on that quick and grabbed my wife's win notebook. I downloaded all the drivers, latest adb, tried different cords, made sure it's in the same folder but couldn't get it to go. I know it's something very basic but I can't get past the bar on the bottom of spflash being red and then timing out after a minute or 2.

Would someone be kind enough to post an imbecilic like walkthrough for me? I got that itch to mess with it and mediatek is just a pain in the ass. Well hopefully thank you in advance.
[General Topics] dbholte:
Any idea if there is a non eu rom?
[General Topics] I opus l:
They keep their updates on drive so this might get flagged, but here's the link

Non-EU version - Google Drive

drive.google.com

If you go to ulefone's website, go to support, then software downloads, scroll to the power armor 13. The nonEU folder will be in that under the Android 12 folder.
[General Topics] Benovite:
After first watching a few very annoying walk-thru videos on how to flash a Ulefone I eventually went back to the video link they provided and used the SP flash version they advised, and it worked(go figure right?). Granted there's no audio and the guy briskly goes thru it, you just gotta slow that sucker down, hit pause and rewind to fully and correctly grasp what's happening. And as was mentioned above, and I think you got this part, the importance of putting the rom folder in the SP flash folder.

Also make sure you're either using the stock charging/data cable or something very close to it(ie. no cheap stuff). Here's the video Ulefone says to follow and the one that eventually got me to successfully flash Android 12:
[General Topics] P4ND3R550N:
Hi. I have turned off the phone and put the correct scatter file and the first file also and also scanned the port and it says in SP flash tool that it is a success. The next step is pressing "Start all" without having the cable connected in the phone right but still in the laptop? And then when it has done the pc memory checksum to 100% i just connect the cable in the phone and it will start flashing right?
[General Topics] nonenal:
i messed around a lot, with a cheap cable. nothing worked right. then i used the usb-c to usb-c cable that came with the phone and it worked on the first try!
[General Topics] Kyr4l:
does anyone knows if it's possible to upgrade from stock android 11 to 12 without losing user data ?
[General Topics] erg12:
It's great that you're sharing this information! Upgrading to a new Android version can bring new features and improvements to your device. For those who are interested in updating their Ulefone Power Armor 13 to Android 12, using the SP Flash Tool is a common method for manually flashing ROMs onto MediaTek-based devices.

It's important to note that when manually updating firmware or ROMs, there is a risk involved, and users should follow the instructions provided by the manufacturer carefully to avoid potential issues. Additionally, users should ensure they have a backup of their data before attempting any firmware updates.

If users have any concerns or questions about the process, reaching out to Ulefone's customer support or community forums could be helpful for guidance and assistance.

Thanks for sharing this information with the community!
[General Topics] @kitokit:
Does anyone have a different link for the update? I can't access the link, bad gateway...
[General Topics] vacumjh:
Well you have to do a factory reset. There is no work around. What you can do is use Google backup and backup your apps, data, pictures, etc., and after that, update it then when you go through the initial setup, it will ask you if you want to restore your backup. https://9apps.ooo/
[General Topics] P7uis:
If you email them asking for the tools and firmware/rom at service@ulefone.com they will rather quick send you the needed tools and roms.
[General Topics] MrJodroid:
Does anyone have a link to the rom file that's still online and thrustworthy? Ulefone support doesn't seem to answer my email.
[Moto Z3 Play Questions & Answers] O2 mini:
Long time member of XDA,first time actually needing to root a phone.

I successfully unlocked the bootloader of my 64Mb dual sim XT1929-8 (EU variant I believe).

Previously unused phone, I all I did was attempt to install Magisk

Installation

The Magic Mask for Android

topjohnwu.github.io

now it won't boot but can I still start the standard recovery/bootloader.

Where did I go wrong?

This was my config before flashing:

I then followed the Magisk instructions, using a boot.img file from BECKHAM_RETAIL_8.1.0_OPWS28.70-56-8_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip for the patch.

I chose the retail one because the phone was still on firmware 8.1.0, rather than use the EU variant, as the only file available for that was version 9.0. This was the output:

The phone gives the black bootloader unlocked disclaimer, then the blue motorola logo with the Verity overlay. The overlay goes away but then nothing changes further. I guess this is a bootloop?

Looking at the following helpful posts, https://xdaforums.com/t/firmware-8-1-official-moto-z3-play-beckham.3805433/post-78404153

https://xdaforums.com/t/links-to-fi...ay-beckham-all-variants.3935355/post-79673160

I tried applying the unpatched boot.img. And I tried applying it to boot_a:

But no difference in behaviour.

I notice the recovery screen says Baseband: <not found>

I don't know why that would be gone if all I did was replace the boot partition.

This is now the output of getvar:

I'm curious also why slot-retry-count:_a would decrement from 7 to 6 ?

I thought I would ask on here before trying too many random things.

Surely it can't be too hard to reverse the flash of a single file.
[Moto Z3 Play Questions & Answers] O2 mini:
TL;DR : I found the isssue myself - The firmware image I chose wasn't compatible with my stock rom even though it was for the same hardware.

~~~

Just to help anyone else with this issue in the future:

I installed Lenovo 'Rescue and Smart Assitant' and jumped through their account registration hoops.

It reflashed the entire phone with the RETEU rom upgraded to Android 9 and got it running again.

Of course it was not rooted, but this time Magisk instructions worked - using the boot.img file from the RETEU image.

I still had the following error during install:

But the phone booted and is successfully rooted.
[Redmi Note 10S] jacksolo:
Hi, I'm having problems updating redmi note 10s to latest version.

I just bought the redmi note 10s a few days ago and it comes with MIUI 12.5.16.0 RKLMIMX so I think it's the global version.

I went to about phone section and tried to search for the latest MIUI version but it can't find anything and then I tried to download the official MIUI 13 update package but one of this messages apears "Can't verify update. Couldn't verify update package." or "Can't verify update. Can't flash this stable ROM."

As far as I know the latest version is MIUI 14

What can I do to update to the latest version?
[Redmi Note 10S] NOSS8:
Try with the V13.0.6.0.SKLMIXM then V13.0.8.0.SKLMIXM,etc.progressively.

Stable Beta	Recovery	V14.0.2.0.TKLMIXM
[Redmi Note 10S] jacksolo:
I tried but it did not work, any of the images work :(
[Redmi Note 10S] NOSS8:
Try with this rom

XM Firmware Updater

The ultimate script that provides firmware packages for Xiaomi devices.

xiaomifirmwareupdater.com

Choose INCREMENTAL UPDATE
[Redmi Note 10S] jacksolo:
I tried but this happened :(
[Redmi Note 10S] NOSS8:
You are almost a year late in updating.

The solution would be to unlock the bootloader, update and lock it.
[Redmi Note 10S] jacksolo:
I turn off mobile data and WiFi and then changed the region from Mexico to Russia, after that I rebooted the device and turn on mobile data and WiFi and check for new updates and it found the 13.0.13 miui update, I installed the update and then I was able to update to miui 14 from the official package.

Thank you @NOSS8 :D
[Redmi Note 10S] NOSS8:
Glad for you, forgot to mention that:rolleyes:, 3 threads same problem:(.

What's funny is that where I mentioned this method it doesn't work and where I forgot it works.:ROFLMAO:
[Redmi Note 10S] tpajarillo:
I have the same problem, the only case being is that the phone is pre-owned or a secondhand phone, upon purchase, I noticed that the phone was a bit slow or lag even without any application installed on it. I tried updating the miui version but all it shows is 'Can't connect to the network'. I am stuck on 12.5.16.0, what can I do?
[Redmi Note 10S] tutibreaker:
update using miflash, you get the firmware and millions of tutos in youtube
[Redmi Note 10S] NOSS8:
Only if the bootloader is unlocked.
[OnePlus 10 Pro] FreezyExp:
Anyone know how to enable it? I have not found a way yet.
[Google Pixel 6 Pro] HankMcCoyX:
Hello all, I ended up flashing back to the January update (the last update I did) to get my phone fixed. At the beginning of this process the active slot was B.

I downloaded the latest March Update and PT 34.0.1 and ended up with a brick. Did some googling and saw that PT 34.0.1 would cause FAILED (Sparse file is too large or invalid) errors (This is the error I had) and the way to resolve it is to go back to 33.0.3.

I did that and tried to redo the update and it still failed. I redownloaded the factory image and it continued to fail. I tried to flash a few times more.

At this point I tried to flash the Jan update and it kept failing.

I switched slots to slot A to see if it would boot and it failed.

I then flashed the Jan update to slot A and it finally booted.

Now in the middle of this process I decided to swap cables and it didn't help. I think I swapped cables when I tried to flash the March update the last time.

When I switched slots to A and tried to flash Jan the 1st time using 33.0.3 using the new cable it failed.

So I went back to the original cable and it went through.

So in summary:

PT 34.0.1 + March Update + Final Working Cable Failed.

PT 33.0.3 + March Update + Final Working Cable Failed. (A Few Times)

PT 33.0.3 + March Update + New Cable Failed

PT 33.0.3 + Jan Update + New Cable Failed

Switched Slots wouldnt boot.

PT 33.0.3 + Jan Update + New Cable Failed

PT 33.0.3 + Jan Update + Final Working Cable (The Original Cable) Worked.

Now what I have not tried is flashing PT 33.0.3 + March Update + Final Working Cable to a slot that had not been ruined by the initial PT 34.0.1 + March Update.

At this point I'm super gun shy about even attempting it. Does anyone have any input on how to get a working flash of the March Update to complete knowing the above situation?

Just additional info: my first flash of Android 13 was to both slots, and ever since then I only updated the active slot.

Thanks!
[Google Pixel 6 Pro] simplepinoi177:
It

definitely

is running PT r34...it's a established notorious issue on the Pixel 7 forums...

We've been successfully able to update to March firmware using r33.0.3.

Is your cable USB-C? Going all the way back to Pixel 2, whenever there's USB issues, usually running a USB-A to a 2.0 slot works when others don't...
[Google Pixel 6 Pro] Dataman100:
Yikes!! This is terrifying! Going to stick with 33.0.3 until there's a good reason to change.
[Google Pixel 6 Pro] HankMcCoyX:
Thing is I tried PT 33.0.3 over and over again and kept failing... but I didn't try 33.0.3 + March + the other slot.

.

Since I finally got it working again not sure if I wanna try PT 33.0.3 + March to my working slot.

Any way to try it on Slot B since it's already borked?

Thx
[Google Pixel 6 Pro] HankMcCoyX:
Thing is in the past using an old PT would also screw ya, and now the latest PT is a bad PT?

It's crazy!
[Google Pixel 6 Pro] Dataman100:
Looking over on the P7P forums, it looks like they're saying to only use 33.0.3 for the March update, so some people have gotten it to work.
[Google Pixel 6 Pro] HankMcCoyX:
The final working cable I started and ended with was USB A to C. Somewhere in the middle I tried a C to C, but the A to C also failed to fix Slot B.
[Google Pixel 6 Pro] simplepinoi177:
That's concerning -- about your Slot B -- if anything happens and an update or flash fails and/or phone fails to boot up, there's a good chance you'll get hard bricked because of it (although it seems you'll have access to bootloader/fastboot mode, so maybe all wouldn't be lost). I suggest you speak with @badabing2003 about how to correct and/or address a corrupted inactive slot -- while there may be others more knowledgeable on the AVB slot set up (because he references them a bunch), he is currently very active and speaks on the issue a lot; due to him developing the PixelFlasher.
[Google Pixel 6 Pro] HankMcCoyX:
Thx for the suggestion!
[Google Pixel 6 Pro] fil3s:
I easily updated to march update with Android flash tool.
[Google Pixel 6 Pro] pa.pn2:
So it's recommended to use the older 33 version of SDK or is it save to use 34.1?

If there are problems, why don't they remove it?
[Google Pixel 6 Pro] Lughnasadh:
Use 33.0.3. It is not safe to use 34+.
[Google Pixel 6 Pro] HankMcCoyX:
So I contacted @badabing2003 on @simplepinoi177 's advice and one of @badabing2003 's suggestions was that adb --kill-server was possibly needed when switching from PT 34.0.1 to PT 33.0.3, even though I'm fairly sure I did reboot windows during the process but perhaps I'm forgetting when I did that during my many flash tries.

At any rate, this morning I was able to flash the January update back to slot B, and then I decided to take a chance and flash the March update later in the day and it all went fine.

Many thanks to @simplepinoi177 and @badabing2003 !
[Google Pixel 6 Pro] anonymouseli:
do you still have it? if so could you please share it with me.