Related
Hi all, made an account in anticipation of my night spent mucking around with my new Galaxy S4 i9507. I had been reading about people who have had success and some who have had less success with getting custom ROMs on their devices. None said what methods they used, so I decided to compile together what I did today.
UPDATE 3/6/14
I installed a snapshot of CM 11 (KitKat) onto my device with little issues. I'll update this guide with the links to that firmware, and also update the existing links because of changes CyanogenMod made to how they aggregate their S4 devices now. They are treating them all as derivatives of 'jftle', so basically one firmware fits all devices, including the i9507! (even if not official yet).
Please read the bottom of this post if you wish to install KitKat on your device.
CUSTOM FIRMWARE ON SAMSUNG GALAXY S4 i9507 - Aus/HK
Tonight I have managed to root the device's stock firmware (I have the Australian Optus/Virgin device); install ClockworkMod Recovery on the stock firmware, and then use it to install CyanogenMod 10.2.0 (jfltexx) on the device.
If you're looking to root this device, I found that by treating it essentially as an international i9505 I was able to fulfil all three of the things I mentioned above.
UPDATE: THIS WILL VOID YOUR WARRANTY AND RESULT IN 'KNOX WARRANTY VOID 0x1' BEING DISPLAYED WHEN YOU ENTER DOWNLOAD MODE ON THE DEVICE. PLEASE BE SURE YOU ARE OKAY WITH THIS HAPPENING BEFORE TRYING THIS FOR YOURSELF. AS IT STANDS, KNOX CANNOT BE RESET, IT IS AT A HARDWARE LEVEL.
[ROOT i9507]
Using Chainfire's guide to CF-Auto-Root in the Galaxy S 4 i9505 Original Android Development section of this forum; I was able to root my device despite it being an i9507. Being a new user, I wasn't sure exactly what things to test out whether the root worked/was permanent, but I did install AdBlock Plus and it asked me for Superuser privileges, then proceeded to work. I also restarted the device and tested whether the root was still present; it was.
[INSTALL CLOCKWORKMOD]
I decided to install CyanogenMod as I have heard from friends that have it; and read online about it being one of the more stable custom ROMs available. It has been a while since I last owned an Android device! So, continuing with my theme of treating this device as being an international i9505, I obtained CM 10.2.0, a stable release of the jfltexx CM, based on from their website (as of December 2013, this was the most recent). Their custom installer app on Windows did not support my phone, so I had to use their guide for manual installation.
Their guide contained steps to installing ClockworkMod Recovery as well as the ROM installation. Following the guide, I installed it without a hitch. When rebooting the phone from ClockworkMod, it prompted me about the fact that the phone may reflash its own recovery tool, but this did not happen. Once again, a success.
[INSTALL CYANOGENMOD]
The last task was to install CM. This was quite an endeavour as I decided to use someone else's Windows 8 laptop (being the only Windows device I had access to at the time) and I forgot how much of a struggle it can be! Again, I used CM's guide to installing 10.2.0 (which by the way is Android 4.3.1, whereas the stock firmware is bloated and heavy at 4.2.2). This went off without a hitch once I reminded myself how the ADT works. I also did as CM suggested and installed the Google Apps pack alongside the ROM.
So, currently this is where I'm at. The device boots and reboots fine. Some users in certain threads had issues with loading 4.4 (KitKat) ROMs or custom ROMs that they didn't allude to the names of, so I don't know if they were having issues with CM or not. There are other threads, but that was the one that kickstarted my attempts to get this all to work. Their issues with the custom ROMs seemed to be related to the 4.4 ROM not recognising the modem of the i9507; I'm not sure why this is but the i9507 was made specifically for Australian/Hong Kong networks so perhaps 4.4 has not been updated yet or something of the like. Anyway, on 4.3.1, or CM 10.2.0, my SMS, calling, and internet are working fine (it displays Virgin Mobile as my carrier). My 4G reception is somewhat iffy in this town (or in particular my house), and the reception seems to be switching between 3G and H so whether that is indicative of 4G not working, I'm not sure. LTE is definitely checked in the settings, however, and my area does have 4G, but my parents' iPhone 5Ss sometimes do not have 4G in this house either. I'll report back tomorrow after having tested the phone for a day to see if the 4G does activate.
As it stands, however, the phone seems to be functioning well. Oddly the Settings report that the phone is an i9505, I assume that's normal as I'm using a ROM for that particular phone!
[CONCLUSION]
So, I hope that anyone who has been looking for a way to remove the carrier/Samsung bloat from their i9507 device will have a good time using the guides I've used. I followed them to the letter and I had no issues.
DISCLAIMER: I had no troubles, but that's not to say you won't either. Please be careful, as you may potentially risk affecting your phone negatively. I'm simply telling you what I did, not giving you a 100% correct and flawless guide that will work no matter what.
Also if you're looking for a 4.4 ROM then you might be out of luck, least till some dev or coder takes notice of this device's existence and helps out to develop a specific way of rooting this phone/installing custom ROMs for this phone. Overall though, it seems to all work fine so perhaps the 4.3.1 CM isn't such a bad thing.
If you try this and want the original firmware back on your phone, use this link. I believe that OPS is the Australian firmware, the other one is for Hong Kong. So, for the second link, HK is Hong Kong, and the one without is for Aus.
UPDATE 3/6/14
I've successfully managed to install a Nightly build of CM 11, based on KitKat. Read my latest post in this forum for more info. I essentially found that upgrading from within the phone itself caused a number of issues so I did a fresh flash. Please note that such a flash of a new OS wipes all personal data but not things like images, videos, etc. I lost all my contacts, SMS, browsing history, apps etc. But my Gallery, Downloads folder, etc remained intact.
I followed my guide to flashing the phone again, but I used a Nightly build of CM 11, based on KitKat. As I write this, there are actually stable versions of CM that you can use in place of the CM 10.2.0 I used in the above guide. If you follow those steps but use this firmware you'll find no issue. Feel free to use CM's guide, but don't, under any circumstances, forget to flash Google Apps to your phone!!!
If you need a hand or want a question answered, feel free to post here and I'll do my best to help you out. Thanks!
kaiserwatson said:
Hi all, made an account in anticipation of my night spent mucking around with my new Galaxy S4 i9507. I had been reading about people who have had success and some who have had less success with getting custom ROMs on their devices. None said what methods they used, so I decided to compile together what I did today.
Tonight I have managed to root the device's stock firmware (I have the Australian Optus/Virgin device); install ClockworkMod Recovery on the stock firmware, and then use it to install CyanogenMod 10.2.0 (jfltexx) on the device.
If you're looking to root this device, I found that by treating it essentially as an international i9505 I was able to fulfill all three of the things I mentioned above.
[ROOT i9507]
Using Chainfire's guide to CF-Auto-Root in the Galaxy S 4 i9505 Original Android Development section of this forum; I was able to root my device despite it being an i9507. Being a new user, I wasn't sure exactly what things to test out whether the root worked/was permanent, but I did install AdBlock Plus and it asked me for Superuser privileges, then proceeded to work. I also restarted the device and tested whether the root was still present; it was.
[INSTALL CLOCKWORKMOD]
I decided to install CyanogenMod as I have heard from friends that have it; and read online about it being one of the more stable custom ROMs available. It has been a while since I last owned an Android device! So, continuing with my theme of treating this device as being an international i9505, I obtained the latest stable release of the jfltexx CM from their website (it was the most recent stable release at the time, may be out of date by the time you get to doing this yourself). Their custom installer app on Windows did not support my phone, so I had to use their guide for manual installation.
Their guide contained steps to installing ClockworkMod Recovery as well as the ROM installation. Following the guide, I installed it without a hitch. When rebooting the phone from ClockworkMod, it prompted me about the fact that the phone may reflash its own recovery tool, but this did not happen. Once again, a success.
[INSTALL CYANOGENMOD]
The last task was to install CM. This was quite an endeavour as I decided to use someone else's Windows 8 laptop (being the only Windows device I had access to at the time) and I forgot how much of a struggle it can be! Again, I used CM's guide to installing 10.2.0 (which by the way is Android 4.3.1, whereas the stock firmware is bloated and heavy at 4.2.2). This went off without a hitch once I reminded myself how the ADT works. I also did as CM suggested and installed the Google Apps pack alongside the ROM.
So, currently this is where I'm at. The device boots and reboots fine. Some users in certain threads had issues with loading 4.4 (KitKat) ROMs or custom ROMs that they didn't allude to the names of, so I don't know if they were having issues with CM or not. There are other threads, but that was the one that kickstarted my attempts to get this all to work. Their issues with the custom ROMs seemed to be related to the 4.4 ROM not recognising the modem of the i9507; I'm not sure why this is but the i9507 was made specifically for Australian/Hong Kong networks so perhaps 4.4 has not been updated yet or something of the like. Anyway, on 4.3.1, or CM 10.2.0, my SMS, calling, and internet are working fine (it displays Virgin Mobile as my carrier). My 4G reception is somewhat iffy in this town (or in particular my house), and the reception seems to be switching between 3G and H so whether that is indicative of 4G not working, I'm not sure. LTE is definitely checked in the settings, however, and my area does have 4G, but my parents' iPhone 5Ss sometimes do not have 4G in this house either. I'll report back tomorrow after having tested the phone for a day to see if the 4G does activate.
As it stands, however, the phone seems to be functioning well. Oddly the Settings report that the phone is an i9505, I assume that's normal as I'm using a ROM for that particular phone!
[CONCLUSION]
So, I hope that anyone who has been looking for a way to remove the carrier/Samsung bloat from their i9507 device will have a good time using the guides I've used. I followed them to the letter and I had no issues.
DISCLAIMER: I had no troubles, but that's not to say you won't either. Please be careful, as you may potentially risk affecting your phone negatively. I'm simply telling you what I did, not giving you a 100% correct and flawless guide that will work no matter what.
Also if you're looking for a 4.4 ROM then you might be out of luck, least till some dev or coder takes notice of this device's existence and helps out to develop a specific way of rooting this phone/installing custom ROMs for this phone. Overall though, it seems to all work fine so perhaps the 4.3.1 CM isn't such a bad thing.
If you try this and want the original firmware back on your phone, use this link or this one. I believe that OPS is the Australian firmware, the other one is for Hong Kong. So, for the second link, HK is Hong Kong, and the one without is for Aus.
If you have any questions, please feel free to ask. I'll post later tomorrow when I've tested the phone for a day to see if it's still working, and to see if the 4G/LTE does actually work. Fingers crossed nothing goes wrong in the meantime!
Click to expand...
Click to collapse
I've had my i-9507 rooted for about a month now with foxhound rom, also on the optus variant.
One thing i've noted is, its next to impossible to update the MODEM for it.
I think because our latest modem for this variant is the one we have stock. And new updates haven't been put in terms of modem specifically for our variant yet.
We should keep this thread stickied for Australian OPTUS GT-i9507 discussion.
OR open up a sub forum for it.
kaiserwatson said:
I'll post later tomorrow when I've tested the phone for a day to see if it's still working, and to see if the 4G/LTE does actually work. Fingers crossed nothing goes wrong in the meantime!
Click to expand...
Click to collapse
Firstly, thank you for creating this complete description of your experiences with customising the i9507.
Secondly, just wanted confirmation that you do now have the pesky "KNOX WARRANTY VOID: 0x1" displayed when your device is in Download mode, right?
Lastly, any updates, issues? All still working, including 4G/LTE?
Hey sorry its been more than a day, I've been swamped with work, that Christmas time feel.
I do have the Knox 0x1, which I assume means my warranty is void. There's conjecture as to whether that will actually affect warranty for this device in Australia, as I've read up on the Knox system but i think the ACCC would have serious issues with this system actually affecting the warranty. But yes, it would seem my warranty is void, let's hope the phone lasts two years!
I have been able to access 4G, the phone says 4G or LTE, sometimes switching between the two. Again, the reception in the town I'm currently staying in is pisspoor so I can't say for certain whether the antenna/modem is fully functioning to the degree it would be on the stock firmware, but I can definitely access the Optus 4G network.
One issue I did have was that I sent an SMS then immediately turned my screen off, 40 minutes later the message was still 'sending'. I have recreated the same scenario but I haven't been able to get it to happen again, perhaps just a weird tower-side quirk. I know people were having issues with the modem and the phone sleeping but this doesn't seem to be related. Overall I'm really happy with how this has all gone. My battery life has been increased by at least 40% and the phone is so much faster. Very pleased.
kaiserwatson said:
Hey sorry its been more than a day, I've been swamped with work, that Christmas time feel.
I do have the Knox 0x1, which I assume means my warranty is void. There's conjecture as to whether that will actually affect warranty for this device in Australia, as I've read up on the Knox system but i think the ACCC would have serious issues with this system actually affecting the warranty. But yes, it would seem my warranty is void, let's hope the phone lasts two years!
I have been able to access 4G, the phone says 4G or LTE, sometimes switching between the two. Again, the reception in the town I'm currently staying in is pisspoor so I can't say for certain whether the antenna/modem is fully functioning to the degree it would be on the stock firmware, but I can definitely access the Optus 4G network.
One issue I did have was that I sent an SMS then immediately turned my screen off, 40 minutes later the message was still 'sending'. I have recreated the same scenario but I haven't been able to get it to happen again, perhaps just a weird tower-side quirk. I know people were having issues with the modem and the phone sleeping but this doesn't seem to be related. Overall I'm really happy with how this has all gone. My battery life has been increased by at least 40% and the phone is so much faster. Very pleased.
Click to expand...
Click to collapse
That occurs because the modem signal cuts out after you switch your phone off, or lock it.
This issue can be resolved by updating our modems, but with our current variant we can't update it yet apparently, until the correct new modem for our specific variant has been released.
Hi guys,
I thought I would also post here.
I have the optus 9507 and I tried a couple of different kitkat 4.4 roms. They all worked perfectly except for the fact that they lost data completely as soon as the phone went to sleep. the weird thing is, the phone showed 0 bars but i could take calls just fine, just had data issues.
i tried the slimkat rom and the echoe rom with the same issue
i went back to stock firmware, rooted, ran a debloat script i found on xda, removed a bunch more apps, then unrooted again because i need to run good for enterprise for work.
im getting decent battery life with the debloated stock rom but i would like to move to 4.4 if theres a rom that works. ive been watching the optus and sammobile site hoping there will be a newer modem for the hk version because i think optus will take their time releasing 4.3 for this model.
kaiserwatson said:
Hi all, made an account in anticipation of my night spent mucking around with my new Galaxy S4 i9507. I had been reading about people who have had success and some who have had less success with getting custom ROMs on their devices. None said what methods they used, so I decided to compile together what I did today.
Tonight I have managed to root the device's stock firmware (I have the Australian Optus/Virgin device); install ClockworkMod Recovery on the stock firmware, and then use it to install CyanogenMod 10.2.0 (jfltexx) on the device.
......
Click to expand...
Click to collapse
Thanks for your experience sharing,
I also started with Cyanogen and shared about the same experience.
Just didn't know the Knox thing before I started.. should had read up more before doing it.
So you did the Recovery with Heimdall also? What has made you switch to the customized Rom camp
kaiserwatson said:
Hey sorry its been more than a day, I've been swamped with work, that Christmas time feel.
Click to expand...
Click to collapse
Hey, no worries at all, anyone who works weekends can take all the time they need...
But yes, it would seem my warranty is void, let's hope the phone lasts two years!
Click to expand...
Click to collapse
Yea, I've done some reading also and you're right, it seems to be all conjecture, I really doubt handset warranty refusal can be based on the KNOX Warranty chip. I think the Samsung Enterprise Security Group VP explains it well here.
Overall I'm really happy with how this has all gone. My battery life has been increased by at least 40% and the phone is so much faster. Very pleased.
Click to expand...
Click to collapse
Great to hear, based on this I can ge ahead and 'burn out' my eFuse, happy in the knowledge that my Knox warranty has gone to a good cause. :fingers-crossed:
---------- Post added at 08:49 PM ---------- Previous post was at 08:40 PM ----------
opelcalibra said:
then unrooted again because i need to run good for enterprise for work.
Click to expand...
Click to collapse
I can only assume your "enterprise for work" has nothing to do with KNOX, right? Coz that option would be closed for you now...
CuriosityBrah said:
That occurs because the modem signal cuts out after you switch your phone off, or lock it.
This issue can be resolved by updating our modems, but with our current variant we can't update it yet apparently, until the correct new modem for our specific variant has been released.
Click to expand...
Click to collapse
That odd message not sending was the only issue I've had with this sort of thing; I can still download things, receive messages and calls just fine while my phone is sleeping, how do you know if the modem signal is cutting off? Perhaps it's just a selective thing, not sure. Don't know how to test if it's happening to me because it doesn't seem to be, lol.
opelcalibra said:
I have the optus 9507 and I tried a couple of different kitkat 4.4 roms. They all worked perfectly except for the fact that they lost data completely as soon as the phone went to sleep. the weird thing is, the phone showed 0 bars but i could take calls just fine, just had data issues.
Click to expand...
Click to collapse
Hey mate if you check the forum that I linked to the Knox issue; someone on there posted a fix for sound/WiFi issues post-Knox voiding, maybe that fix'll work for you. Sorry I can't link you to the exact post but it was about 10-20 pages in.
opelcalibra said:
i went back to stock firmware, rooted, ran a debloat script i found on xda, removed a bunch more apps, then unrooted again because i need to run good for enterprise for work.
im getting decent battery life with the debloated stock rom but i would like to move to 4.4 if theres a rom that works. ive been watching the optus and sammobile site hoping there will be a newer modem for the hk version because i think optus will take their time releasing 4.3 for this model.
Click to expand...
Click to collapse
Yeah I reckon they'll take ages, they have pretty much left everyone who's getting this phone in the next couple of months in the dark because of the (as I can tell) severe lack of devs etc in Aus who have Samsung phones and are willing to hack them to the ****. I wish I could help out somehow, but I don't have the time to learn so I figured I'd help out by putting up my experiences. I'm still learning as I go haha.
As for your KitKat problem, I have read that 4.4 didn't do so well in terms of battery life and bloat, what are your reasons for wanting to go to it? I wanted the most recent build also but I figured that if they're still having issues with it then it was better to go with something I knew would work (ie. 4.3.1).
phileasx said:
Thanks for your experience sharing,
I also started with Cyanogen and shared about the same experience.
Just didn't know the Knox thing before I started.. should had read up more before doing it.
So you did the Recovery with Heimdall also? What has made you switch to the customized Rom camp
Click to expand...
Click to collapse
I followed the Windows process on the CM wiki to the letter, so yeah I did the Heimdall also.
Mate legitimately I went from my stock firmware taking up so much space on the hard drive to the real lightweight CM, seeing as I haven't bought a micro SD yet that was a big deal. Also battery life was a major reason for me buying the S4 so to be able to further improve it is just hella.
siganid said:
Hey, no worries at all, anyone who works weekends can take all the time they need...
Yea, I've done some reading also and you're right, it seems to be all conjecture, I really doubt handset warranty refusal can be based on the KNOX Warranty chip. I think the Samsung Enterprise Security Group VP explains it well.Great to hear, based on this I can ge ahead and 'burn out' my eFuse, happy in the knowledge that my Knox warranty has gone to a good cause. :fingers-crossed:
Click to expand...
Click to collapse
In Australia I think we're pretty good. Funny that Samsung and Optus have given us this nice present and it's only a matter of time before someone cracks it open and remains above the warranty voiding
I have read that Knox may be software-based, which would make sense, and maybe it's a matter of time before someone cracks that too. Hehe.
Go ahead, post here if you have any issues and I'll see if I can help you out. What ROM would you be planning on using? A 4.3.x one?
kaiserwatson said:
I followed the Windows process on the CM wiki to the letter, so yeah I did the Heimdall also.
Mate legitimately I went from my stock firmware taking up so much space on the hard drive to the real lightweight CM, seeing as I haven't bought a micro SD yet that was a big deal. Also battery life was a major reason for me buying the S4 so to be able to further improve it is just hella.
Click to expand...
Click to collapse
Welcome to the rom flashing side
After read up more, I realize Odin is a more popular method for Galaxy S4 flashing,
Besides that, Stock rom battery life should also be all right. Samsung did quite some efforts to make the software user friendly.
Anyway, the Bloatware chunk are really irritating have to say.
because i cant keep still i have flashed my phone again lol.
i flashed the official CM 11 (4.4.2) and gapps for kitkat and all is working awesome so far.
no issues with losing signal when going to sleep. seems very fast. right now im happy with it.
Could someone please find new links for the original software posted in the OP?
Links are dead, would be greatly appreciated! =)
Also, Opelcalibra, you have no issues with network/signal on CM 4.4.2 with the Optus i9507?
I better give it a try then lol
RE: Signal issues
Hi,
I also have the AU i9507 Opus S4, I flashed the Omega based 4.4.2 KitKat (i9505 version) and had wifi problems (Greyed out) I tried various fixes and went back to 4.3 based Omega, this had its problems with cell signal being lost when locking the mobile.
I fixed this by going into settings and experimented with mobile networks i.e. Settings, more networks, mobile networks, network mode and tried all 4x options with (for me at least) the GSM ONLY option selected, great rom and worth losing the 4g which is very patchy in my part of Melbourne.
D
Anyone else had any sort of success rooting this phone without tripping Knox.
Also, is it just me, or does it suck pretty hard that we Aussies get stuck with an inferior version of a phone? (Snapdragon 600 in the I9507 vs the 800 in the other international versions)
Update
Hi
Just wondering if anyone has an update on this? Success or otherwise...
One of the main reasons I'm looking to root is to boost volume levels - I find the volume to be way too low. Does anyone know of a way to do that without rooting? Of course I'd like to remove bloatware but could live with it if volume was fixed.
Thanks in advance.
thestuntman80 said:
Anyone else had any sort of success rooting this phone without tripping Knox.
Also, is it just me, or does it suck pretty hard that we Aussies get stuck with an inferior version of a phone? (Snapdragon 600 in the I9507 vs the 800 in the other international versions)
Click to expand...
Click to collapse
Hey bro, no one has cracked without tripping Knox yet because as far as I can tell it's a phone specific fix/hack. So, because our phone is a different and 'rare' model, I doubt that the major heads in the Knox-proofing scene (CF comes to mind) will have the time to make a fix for the knox trip. So for now, either suffer in your jocks (QQ) get a different phone (uh, not likely) or wait for the minute chance that someone actually cares about Aussies )
As for your second point, yeah, it does suck. We get shafted with all sorts of things like prices, release dates, localization...the list goes on. Unfortunately the people who make these ploys know we're desparate and will pay the exorbitant prices anyway :/
jameshef said:
Hi
Just wondering if anyone has an update on this? Success or otherwise...
One of the main reasons I'm looking to root is to boost volume levels - I find the volume to be way too low. Does anyone know of a way to do that without rooting? Of course I'd like to remove bloatware but could live with it if volume was fixed.
Thanks in advance.
Click to expand...
Click to collapse
Hey mate, the rooting was probably the easiest part of the whole situation. You can follow my guide in the OP if you're having trouble. Just be aware about the warranty issues etc because your audio issue may be hardware related rather than software? Is the volume issue in the headphones or the speaker? Some apps may not utilise the phones full volume and also be sure to go into the settings of the phone and make sure the volume limiter is turned OFF. This **** me to tears for the longest time but once I figured out what the issue was, all good!
The only thing I'd say is just make sure its not a hardware issue because you don't want to root your phone, find out that it wasn't a software issue, take your phone into Samsung and have them tell you that your warranty is voided because you rooted. Obviously that's a worse case scenario but just be on the safe side.
I hope I helped you guys!
kaiserwatson said:
Hey mate, the rooting was probably the easiest part of the whole situation. You can follow my guide in the OP if you're having trouble. Just be aware about the warranty issues etc because your audio issue may be hardware related rather than software? Is the volume issue in the headphones or the speaker? Some apps may not utilise the phones full volume and also be sure to go into the settings of the phone and make sure the volume limiter is turned OFF. This **** me to tears for the longest time but once I figured out what the issue was, all good!
The only thing I'd say is just make sure its not a hardware issue because you don't want to root your phone, find out that it wasn't a software issue, take your phone into Samsung and have them tell you that your warranty is voided because you rooted. Obviously that's a worse case scenario but just be on the safe side.
I hope I helped you guys!
Click to expand...
Click to collapse
I'm fairly certain it's a software issue. I've done a fair bit of reading on it and the low volume is a very common complaint about the S4. My volute limiter is turned off - thanks for that tip though!
I'm going to try to root this weekend. I really hope that it works and I don't have any issues with reception dropping when the phone goes to sleep! Feels risky.
I've changed my firmware from Optus to XSA, but am still on 4.2.2, how do I upgrade now?
Kies says I have the latest release.
has anyone got links to newer modem files for this phone? been given one to update it to 4.4, but i know from experience that doing so without at least a 4.4 GSM modem, it wont behave right.
to the people without working wifi after updating: flash the Ktoonz kernel, he has a fix for that.
Hi All,
I recently updated to the new official 4.3 update from optus in order to update my baseband etc.
Then i immediately updated to the i9505 Goldeneye 4.4.2 rom. Ran a ebloat script to get rid of alot of the extras and its running very nicely.
Since updating the modem I get 4g at home which i never did before.
optus rom here
http://www.sammobile.com/firmwares/3/?download=27109
flashed via odin (will lose root and custom recovery). re-root and install recovery after flashing this room.
goldeneye rom here
http://forum.xda-developers.com/showthread.php?t=2313469
obviously this will flag knox, mine was flagged long ao
I haven't used my OnePlus One in several months since I got my Nexus 6. I've been meaning to sell my OPO, but got lazy about it. Now I can't be, and I need money for rent. A friend/co-worker who's in serious (in my opinion) need of a new phone wants to buy it off me.
My OPO was on LiquidSmooth 4.4.4 but obviously it's out of date, so I tried to update it. I tried once before to update it with a 5.1 ROM, but it kept failing. I remember there was something about the firmware or baseband version that needed to be flashed to go from KK to LP, but it was several months ago, and I can't remember what exactly it was. And for the life of me, I can't find it.
I tried to find what it was, and in my searching I found that CyanogemMod Official 13 had a built-in baseband updater. So that's what I tried. TWRP version was/is 2.8.7.0. Maybe that was the problem?
Anyway, CM13 (the most recent snapshot) installed, seemingly fine, but it won't recognize my SIM card. I try reinstalling it, and it still won't recognize the SIM. Moreover, it doesn't even detect a cell signal (it should, as all cell phones in the US are required to have 911 emergency access, even if you're not actually paying for phone service). And then it starts rebooting. Not a bootloop, because it boots. Then a few minutes later, it reboots. Continuously.
So I try a different ROM. The latest Resurrection Remix (I have it on my Galaxy S4 and it works fine). Same thing.
The even weirder thing is that I figure I should just restore my latest nandroid, but it's not there. In fact, nothing's there. Nothing visible through TWRP's file manager or backups. Not even old pictures, which I didn't delete. I didn't delete any storage (because I wanted my backup, just in case, duh). But TWRP still shows that there's 26GB available. So obviously, there's something there. I just can't see it. My fault for not saving the nandroid elsewhere, but Humpty Dumpy has already fallen.
I have Wugfresh's toolkit (yeah, yeah, I know...), and tried restoring it to stock, and it won't do it.
I've used ADK in the past, but it has been way to long for me to remember specifics, and it has apparently been updated with the newer Android versions. Obviously, I've looked at the sticky thread about restoring your OPO to stock, but it hasn't been updated in a while. So I'm worried about using those instructions. I've looked up youtube videos, and they're all too old as well. I'm also worried that I'd be using the wrong version of ADK. I'm not scared of using ADK, as long as the instructions are correct and clear. I'd be using Windows 8, if that matters.
So what I'm asking (begging) for is instructions on how to make this phone work properly again. Quickly. I've tried doing the research myself, and haven't found my solution. I'd keep at it, but time is getting short, and I can't afford that. Literally. I can't afford the hours spent (it's 1am and my the office closes at 4pm), and I can't afford being late on my rent. A couple weeks ago I spent way too much up in Phoenix to go see Guns N' Roses (at least I got a kickass T-shirt). Entirely my fault. Also my fault for not realizing how desperate my financial situation was about to be, and for waiting to ask for help until now. And I'm not going to ask to borrow money. I just can't.
Finally, and I know it's taboo to ask "what's the best ROM?", because I've answered that question myself with "there isn't one - try them out for yourself and find which one's best for you". But as I said, I'm out of time., and I haven't been keeping up with what's going on with OPO's development. My friend is not like us. His phone's a LG cheapo POS from years ago that's on 4.1JB. He uses it for calls, texts, and podcasts. He doesn't need root, or even custom recovery for that matter. In fact, I'd prefer if it didn't have root (although custom recovery might be nice, just in case). So if I can get this damn thing working properly again, what'd be a good ROM for my firend? OPO's official Oxygen? Are they still updating it? Stability is the primary concern, but if there's something that gets regular (and stable) updates, that'd be good too. With an updater that's built-in, simple, and wouldn't need and XDA forumite to do it for him. Because it'd be nice that he could get updates with Google's security patches. But since he's still using a 4.1 phone, he's obviously not all that concerned about that issue. But still, that'd be nice.
Thank you (fingers crossed).
Hi,
I'm thinking about buying this phone at this moment (Black Friday). My question is : is it worth buying considering this model has been received 2 major updates? I think Samsung update policy is to release only 2 big updates for their models. This model was launched with Nougat, now is running with Oreo and, presumably, will end with Pie. Is this correct?
Thanks
Wrong one major update 7.1 to 8.0 I believe it will get 9.0 but not sure.
Personal I pass on the ab but I got the ab+ version.
It been a very good phone.
mchlbenner said:
Wrong one major update 7.1 to 8.0 I believe it will get 9.0 but not sure.
Personal I pass on the ab but I got the ab+ version.
It been a very good phone.
Click to expand...
Click to collapse
According to many websites, it's very very likely this phone will have Pie. But the question is if that version will be the last one (not eligible for Android Q). It's well-known that Samsung do not care mid/low range models regarding upgrades (other than security patches).
Another question: does this phone still have the annoying FRP Lock protection? I would like to root the phone, but this protection is a pain in the ass. My old Galaxy Grand prime still has it.
Thanks again
If you want to root it you will lose the warranty... but then you can install a costume rom P,Q,etc...
Robert978 said:
If you want to root it you will lose the warranty... but then you can install a costume rom P,Q,etc...
Click to expand...
Click to collapse
I think if I flash the stock ROM with Odin I will recover the warranty, right? I have already rooted my old Galaxy. The problem is the root access when the FRP Lock protection is still present.
When you root the phone, if you have configured any Google account (needed for Play Store), the phone does not boot when is rebooted (the bootloader detects an 'unofficial' firmware installed). In order to bypass it (and reboot your phone when is needed), you need to remove all your Google accounts first and therefore this is a PITA. So my question (to rooted users) is if this protection is still present, and if so, if there is a way to get rid of it.
Thanks.
Robert978 said:
If you want to root it you will lose the warranty... but then you can install a costume rom P,Q,etc...
Click to expand...
Click to collapse
Hi,
I'm reading about rooting in this forum and I have realized that this model is not easy to root, specially if you already are in Oreo (very likely if I buy now the phone). I have found several threads about this question but it's not clear what is the 'best guide'. Also I have found the following tutorial HERE.
Can you elaborate a bit?
Thanks
Boblo said:
Hi,
I'm reading about rooting in this forum and I have realized that this model is not easy to root, specially if you already are in Oreo (very likely if I buy now the phone). I have found several threads about this question but it's not clear what is the 'best guide'. Also I have found the following tutorial HERE.
Can you elaborate a bit?
Thanks
Click to expand...
Click to collapse
There's already a pretty good guide here on how to install a custom recovery and root this phone made by @corsicanu. I followed it just about a week ago when my phone was 5 days old and I had no problem whatsoever. I had OREO 8.0 and I was super scared about my phone being locked since I had never listened to that before. This phone is really worth it. Size, display and performance is 10/10 for me. On the contrary, the main camera is below average. I have yet to found a good version of the gcam since all I have tried are not working properly. My last device was a Xiaomi MI A2, but it only lasted two weeks. The reasons to replace the MI A2 are bad display outdoors, too big of a phone, super bad adio quality (headphone wise) plus no headphone jack, low lasting battery and no NFC. I swear to you there are very low options that are as packed as this galaxy a8 2018. It cost me 290€ on a retail store so I'm super happy.
catalem said:
There's already a pretty good guide here on how to install a custom recovery and root this phone made by @corsicanu. I followed it just about a week ago when my phone was 5 days old and I had no problem whatsoever. I had OREO 8.0 and I was super scared about my phone being locked since I had never listened to that before. This phone is really worth it. Size, display and performance is 10/10 for me. On the contrary, the main camera is below average. I have yet to found a good version of the gcam since all I have tried are not working properly. My last device was a Xiaomi MI A2, but it only lasted two weeks. The reasons to replace the MI A2 are bad display outdoors, too big of a phone, super bad adio quality (headphone wise) plus no headphone jack, low lasting battery and no NFC. I swear to you there are very low options that are as packed as this galaxy a8 2018. It cost me 290€ on a retail store so I'm super happy.
Click to expand...
Click to collapse
Thanks. Is THIS GUIDE? And is your system stable with no important bugs?
Other than that... unlike older Galaxy models I cannot recover my warranty when the device is rooted, right? I have read that the warranty bit is changed, the bootloader detects an 'unofficial' firmware and there is no way to avoid this.
Regards
Boblo said:
Thanks. Is THIS GUIDE? And is your system stable with no important bugs?
Other than that... unlike older Galaxy models I cannot recover my warranty when the device is rooted, right? I have read that the warranty bit is changed, the bootloader detects an 'unofficial' firmware and there is no way to avoid this.
Regards
Click to expand...
Click to collapse
It is indeed. Flashing and rooting your device does not make it less stable. My galaxy a8 is working like a charm. I don't have my phone rooted but I have had it and the only problem for me is I have always a notificacion shown saying device is in danger, you must restart. Unlike some other devices, samsung smartphones are not able to be reverted. Once you trip knox, there's no going back. Even if you flash back an original ROM with ODIN, the phone will still known its been modified.
catalem said:
It is indeed. Flashing and rooting your device does not make it less stable. My galaxy a8 is working like a charm. I don't have my phone rooted but I have had it and the only problem for me is I have always a notificacion shown saying device is in danger, you must restart. Unlike some other devices, samsung smartphones are not able to be reverted. Once you trip knox, there's no going back. Even if you flash back an original ROM with ODIN, the phone will still known its been modified.
Click to expand...
Click to collapse
Thanks again. Where did you see that warning? Is it annoying? Can you hide it?
And a last question: I suppose you know the FRP Lock protection. With this guide, is the FRP Lock protection gone forever?
On a side note, I still have my old Galaxy Grand Prime (2015 model) rooted, with TWRP 3 installed and the Knox counter has the value 0x0 (not tripped). So it seems new models like the A8 have a reinforced protection against hacking...
Hello XDA!
First of all, long time lurker, but infrequent poster here. My phone is an Asus ROG Phone 5s Pro running stock and non-beta software and is not rooted. I am reaching out to see if anyone on here who has more technical savvy than me (which is probably most of y'all) can help me figure out how to reinstall a fresh factory image on my Asus ROG Phone 5s Pro or can offer any other possible solutions for my issue.
The reason I am wanting to do this is because I recently installed a software update from Asus that seems to have a persistent issue that is a pretty major problem to me. The issue is that whenever I reboot the phone and plug in headphones and audio plays, but it stutters and BLASTS out of the headphones (multiple sources tried, even happens with system notification sounds). This only happens with wired headphones and never with Bluetooth. I had this happen to me once for less than a half a second and my ears were persistently ringing for about 3+ hours after this and I am certain that it damaged my hearing to a small degree. Because of this I no longer trust to use any headphones with the phone and this is a huge bummer because I use wired headphones A LOT.
I have tried to factory reset the phone several times already and the issue persists through without any restoring of anything during setup (in fact it won't recognize the backup that it created the day before the factory reset), but the issue is still present. I contacted Asus customer support (for which lets just say I have strong feelings on) and explained the issue and they want me to RMA the phone for a hardware issue.
I really do not wish to do this as this means I will have to either switch phones a few times which is always incredibly time consuming or be without a phone for an estimated period of up to 10 days if I do the RMA. I also disagree that this is a hardware issue because of two things: 1) if it were a hardware issue then I would think that the problem would be constant and not happen just once after each reboot and I would think that doing something in the software, i.e. a reboot, wouldn't consistently recreate the problem. Thus I am trying to find a way to "restore" the operating system of this device to see if I can solve what I believe to be a software issue that shouldn't require any RMA.
I have seen that posts that linked official files from Asus before, such as the "AsusUnlock_1.0.0.7_210127_fulldpi.apk" found in the OP of the "Install any custom ROM on ROG Phone 5 / 5s (GSI)" thread here in this very forum. Is anyone aware of any officially sourced files for stock software/firmware for this phone and a process through which I could reinstall it?
I am also open to thoughts and other possible options to consider.
Also I will give bonus points to anyone who can help me figure out how to fix the issue where my Google backup by this very same phone won't restore its own Google backup when going through the setup and can help me restore it. It does recognize a different Google backup for a tablet that is set up for my child to use, so it is not an issue with the restore being completely broken.
Thanks in advance for anyone willing to try and lend a hand.
Hi, here you can find stock firmwares make sure you got for right region.
ROG Phone 5s Pro | Gaming Phones｜ROG - Republic of Gamers｜ROG Global
Fueled for winning by the latest Qualcomm® Snapdragon® 888+ 5G mobile platform, ROG Phone 5s Pro launches your mobile gaming experience into the next dimension. With an unbelievably responsive 360 Hz native touch-sampling rate, the 144 Hz / 1 ms display brings you the smoothest ever viewing...
rog.asus.com
Yeah, just for additional info for anyone who finds this. I've also been working with ASUS customer support. I was given two links on flashing official firmware:
Unofficial guide on flashing - https://www.asus.com/support/FAQ/1009748/
Official firmware images - https://rog.asus.com/phones/rog-phone-5s-pro-model/helpdesk_bios (same as previous comment above; thanks Teddy)
When I asked why my version is newer than any they currently have listed on the site I was told that it "could be a preview release given directly by Google" (I doubt this as this appeared as an official OTA by Asus that had very specific patch notes to this phone in it) and that because my version is newer than any listed on their site would result in trouble if I tried to flash the newest version listed, but an older firmware than what is currently installed and that I should still just RMA my phone.
For reference my current firmware is RKQ1.210303.002.WW_Phone-18.1220.2201.186 and the latest firmware listed on their site at the time of this writing is WW-18.1220.2111.164.
Great phone (aside from the hearing damage), but utterly useless support.
Still open to thoughts and ideas though if anyone still has any.
You can "downgrade" your firmware by doing a RAW flash directly to version you need OR to any lower version and then install the official ASUS version you want manually. Also need to disable OTA updates to avoid being updated to the latest automatically.
Having the device checked for hardware issues is probably the best idea however.
Andrologic said:
You can "downgrade" your firmware by doing a RAW flash directly to version you need OR to any lower version and then install the official ASUS version you want manually. Also need to disable OTA updates to avoid being updated to the latest automatically.
Having the device checked for hardware issues is probably the best idea however.
Click to expand...
Click to collapse
Could you provide more info on this "downgrade" via "a RAW flash"? Is there a guide or something that will give more info about this?
I think I might be screwed though for the RMA. Customer service says apparently its a Taiwan version and cannot be serviced in the USA and has to be sent to via Taiwan RMA and the page they gave me seems to indicate there are no service centers for ROG Phones; see https://www.asus.com/support/service-center/taiwan#.
Short rant is that I literally spent hours and I mean HOURS (if not possibly days) of my time with Asus customer service and searching online trying to find a US version with US warranty and ultimately getting nowhere and deciding to go with the one I have now. Four months in to a $1700 phone and basically I am stuck with a dangerous headphone jack and no option to fix it other than maybe what you mentioned, Andrologic.
Today has not been kind.
ChrisMills83 said:
Could you provide more info on this "downgrade" via "a RAW flash"? Is there a guide or something that will give more info about this?
I think I might be screwed though for the RMA. Customer service says apparently its a Taiwan version and cannot be serviced in the USA and has to be sent to via Taiwan RMA and the page they gave me seems to indicate there are no service centers for ROG Phones; see https://www.asus.com/support/service-center/taiwan#.
Short rant is that I literally spent hours and I mean HOURS (if not possibly days) of my time with Asus customer service and searching online trying to find a US version with US warranty and ultimately getting nowhere and deciding to go with the one I have now. Four months in to a $1700 phone and basically I am stuck with a dangerous headphone jack and no option to fix it other than maybe what you mentioned, Andrologic.
Today has not been kind.
Click to expand...
Click to collapse
There are links to download RAW images along with guides in the help thread pinned to the top of this forum. You should find what you need there. The RAW's come include flash scripts that does it all for you.
Just curious for opinions while this thread is still going:
Does anyone lean towards my issue being a hardware problem or something else (and if you could be specific and suggest something for me to try about it)?
The reason why I ask is because I personally feel like this is an issue with when the headphone jack initializes output or something because it only ever blasts audio after a reboot and I any audio plays. After it stops and plays again the levels seems to return to normal. I can also reliably make this happen the same way every single time. Finally (and somewhat conspiratorially), the update I installed just before this started to happen had patch notes that included "optimized audio parameters."
My appreciation in advance for any thoughts and insights.
Just as the subject mentions. Curious if it's just me?
Nada. No update. And when I mentioned this on their forum, they deleted the post.
I even tried the thing where you remove the SIM and search for updates then. Didn't make any difference.
Searching with Sammoblie and Frija, only the carrier version(A536U) from Xfinity/Comcast has gotten it in the US.
I don't have it either, what bothers me most is that 13 was released for older A phones including lower priced models already. Is it possible that because this is an enterprise phone (at least in the USA) it requires more time for testing?
pj1980 said:
I don't have it either, what bothers me most is that 13 was released for older A phones including lower priced models already. Is it possible that because this is an enterprise phone (at least in the USA) it requires more time for testing?
Click to expand...
Click to collapse
What bothers me was how quickly Samsung deleted my post on their forum after I asked about this.
It's been like 6 weeks since the same phone in other countries was given this. It's quite annoying.
snark.shark said:
What bothers me was how quickly Samsung deleted my post on their forum after I asked about this.
It's been like 6 weeks since the same phone in other countries was given this. It's quite annoying.
Click to expand...
Click to collapse
Samsung's discussions has a sticky at the top that updates happen whenever (edit: or at least it did before). And that's definitely how it goes for all their devices.
Even Samsung flagships go through silly stuff for updates and Android versions so its not A53 only.
The A53 unlocked has carrier apps on it so its tied to the carrier testing. Why will US carriers release Android 13 for older devices before newer? No idea but that's how their testing is going. They have some reason.
Really, you will get it when you get it. If you just think it won't show up until the year 2721 then it should be easier for you lol.
Its frustrating I know for unlocked to be dependent on carriers. But, waiting, it will at least probably have less bugs so that's fine enough. A buggy device isn't fun at all.
edit: Also A52 appear to be doing better than the A53 in getting Android 13 and listed as Enterprise. So, I don't think Enterprise has anything to do with it.
edit: The end result appears to be what Samsung's sticky said which is updates happen when they happen.
Samsung promised 4 years of updates for this phone so they have about 3 more years to give us android 13.
tmeader said:
Just as the subject mentions. Curious if it's just me?
Click to expand...
Click to collapse
3 Days ago, my phone suddenly shut itself off, and then stuck itself in a bootloop and would not boot again. It's a Samsung A53 5G (ATT&T) running android 12 one UI version 4.1 at the time. After booting into safe mode and wiping application config data, it still would not come out of safe mode until I factory reset it and connected it to a wifi network.
Finally after all of this BS, I got it to boot normally, but then, as if by magic, my phone was running Android 13 UI Version 5.0!
WTF!?
So I spent an entire day recovering my bank accounts, cashapp, applications, and various accounts, and chalked this pain in the ass up to the game...
And then this morning, it ****in' happened again.
I'm done with Samsung. This phone has been a $500 piece of **** since day 1. It's not even 3 months old yet. Samsung has gone from the most badass manufacturer of android devices, straight to the bottom of the abyss in terms of quality.
The Bloatware they send with these devices now should be unlawful. The amount of YOUR resources they use to track every single thing you do, every place you go, every dollar you spend is unfathomably creepy and discomforting.
Do yourself a favor and get comfortable with 12. because 13 is an even bigger piece of ****, and in my case, it has totally wrecked my phone twice in 3 days now.
Do yourself an even bigger favor, and throw your samsung into the bottom of the ocean and go buy yourself an IPhone. I'm really sad about the way Samsung has turned out. I'm even more sad about the way Android has gone down the drain. And Google has turned into the world's most powerful creepy stalker with Facebook a close 2nd.
I think if people actually new just how intrusive these tech companies have become, they'd stop using them altogether. There needs to be new and better privacy regulations and trackers and spywares and metadata miners and these 'ad targeting' programs and applications should be illegal.
ImMrMyagiLafAtMe said:
3 Days ago, my phone suddenly shut itself off, and then stuck itself in a bootloop and would not boot again. It's a Samsung A53 5G (ATT&T) running android 12 one UI version 4.1 at the time. After booting into safe mode and wiping application config data, it still would not come out of safe mode until I factory reset it and connected it to a wifi network.
Finally after all of this BS, I got it to boot normally, but then, as if by magic, my phone was running Android 13 UI Version 5.0!
WTF!?
So I spent an entire day recovering my bank accounts, cashapp, applications, and various accounts, and chalked this pain in the ass up to the game...
And then this morning, it ****in' happened again.
I'm done with Samsung. This phone has been a $500 piece of **** since day 1. It's not even 3 months old yet. Samsung has gone from the most badass manufacturer of android devices, straight to the bottom of the abyss in terms of quality.
The Bloatware they send with these devices now should be unlawful. The amount of YOUR resources they use to track every single thing you do, every place you go, every dollar you spend is unfathomably creepy and discomforting.
Do yourself a favor and get comfortable with 12. because 13 is an even bigger piece of ****, and in my case, it has totally wrecked my phone twice in 3 days now.
Do yourself an even bigger favor, and throw your samsung into the bottom of the ocean and go buy yourself an IPhone. I'm really sad about the way Samsung has turned out. I'm even more sad about the way Android has gone down the drain. And Google has turned into the world's most powerful creepy stalker with Facebook a close 2nd.
I think if people actually new just how intrusive these tech companies have become, they'd stop using them altogether. There needs to be new and better privacy regulations and trackers and spywares and metadata miners and these 'ad targeting' programs and applications should be illegal.
Click to expand...
Click to collapse
That's not the experience of most people. Since you bring up Apple as if that will help you avoid this when it can happen there too: https://myphotoyear.com/ios-16-update-goes-wrong/
Its just a fact of life.
More or less it could be improved or solved by multi-OS versions at the same time (such as dual boot on a computer), slower major OS versions, etc. This is not how Google or Apple thinks though.
To add, you can of course improve loss of data by using system backup and also backing up your stuff separately. Though Android still isn't perfect there.
Of course, if you see an update, avoiding updating for some months might also help though not ideal.
edit: For instance you could have used the Samsung restore which may be presented on first use setup or even manually done in Settings > Accounts and Backups > Restore which will restore much if you used the online backup or backup to sd card. Some apps and data will be missing if apps don't support it, etc. Unfortunately, it seems to only offer one backup at least online so any backup on the account since might have destroyed it.
edit: using that and backing up to sd card includes 10GB of stuff on my phone whereas the online is suggested as 2GB (it backs up files and also eg debug built from source apps). So, if you want the best, it may be what you should do from now on. Then restore it if need be. Still, up to apps to support backup individually. Make sure to run it weekly or something.
Also, I know you're pissed about that. Try not to be pissed with me lol. Thanks.
I'm thinking we're in for weeks, or months, more wait. We haven't even gotten a January Security Update.
Just received the Android 13 (One UI 5.0) update last night on my unlocked phone. Also includes the Jan 2023 security update. Looks like they just made the January cutoff
Hmm I have unlocked a53 on t mobile, I checked for updates today and it said there were none.
I received the update today for Android 13 including dual sim support.
I been checking my A53 unlocked running on Visible every week since Christmas for an update. Today it found the Android 13 UI 5.0 update. downloading it now.
How is the new version? any bugs found?
ok, once my phone updated and rebooted now I am no longer connecting to 5G. I've rebooted a few times and nothing has changed. I'm stuck back on 4G.
tmeader said:
Just received the Android 13 (One UI 5.0) update last night on my unlocked phone. Also includes the Jan 2023 security update. Looks like they just made the January cutoff
Click to expand...
Click to collapse
5 days after your post (6 since you got the update), with daily checking, and it's still a No for me.
My A53 arrived this morning and upon turning it on, my device had a lot of firmware updates waiting for me. I just updated to Android 13 not too ago along with January's Security patch.
I happen to live in the US, use T-Mobile, and I'm using the international version with dual SIM support.
snark.shark said:
5 days after your post (6 since you got the update), with daily checking, and it's still a No for me.
Click to expand...
Click to collapse
Another 3 days...
Still no Android 13 update.
I may wind up going to the Samsung service location in my area. This is ridiculous.
snark.shark said:
Another 3 days...
Still no Android 13 update.
I may wind up going to the Samsung service location in my area. This is ridiculous.
Click to expand...
Click to collapse
They do rollouts on top of things.
You could of course use a sim from a different carrier that has the upgrade available and do it that way. Might just get it immediately or still not. Then switch back. That is a possible workaround.
Of course, if you see a signed image for download for Android 13 for your carrier. That might work too even though it still is a wait for it to show up that way.
I don't know if there's any other way here because of the CSC. It would be interesting to know if a Samsung service shop would do it for you. I can't imagine they would.
Received the update today. Seems to run faster.