Related
So im a noob. I rooted my gs3 when i got it. I added the wifi button and mobile hotspot. Now i want to update my phone to the newest build. I froze kies and SDM to prevent any OTA updates so I wouldnt mess anything up or lose root.
Does skipping builds cause any issues?
Can I update in a way where I wont lose my info?
If that is not possible (saving info) How do I update without losing root? (can you point me to a video)?
Since there is no stock image for mb1 yet, you'll have to go to the lk3 build first. You can do so by flashing the stock lk3 image with Odin (you can find the files in development). From there you can take the ota. There may be images that allow you to keep root while going from LG1 to lk 3 but I'm not sure
If you already have root then I believe all you have to do is flash a 4.1.2 rom via custom recovery...I may be wrong though so double check the guides over in the gs3 development stickies.
Surge1223 said:
If you already have root then I believe all you have to do is flash a 4.1.2 rom via custom recovery...I may be wrong though so double check the guides over in the gs3 development stickies.
Click to expand...
Click to collapse
He could do that but it would only update the system and data partitions. The other partitions and firmware will still be out of date and that could cause some potential problems, especially if its a jump from ICS to JB
What do you mean like radio, rpm and kernel?
Yes and any others. There are I think 12 or so partitions total, but I'm not smart enough to know what they do (except for the three or four that get backed up with a nandroid such as system and data)
Edit: better link showing a table of the 23 sg3 partitions and labeling their functions.
http://forum.xda-developers.com/showthread.php?t=1892901
gingi999 said:
So im a noob. I rooted my gs3 when i got it. I added the wifi button and mobile hotspot. Now i want to update my phone to the newest build. I froze kies and SDM to prevent any OTA updates so I wouldnt mess anything up or lose root.
Does skipping builds cause any issues?
Can I update in a way where I wont lose my info?
If that is not possible (saving info) How do I update without losing root? (can you point me to a video)?
Click to expand...
Click to collapse
I read your rooted, make sure your phone's bootloader is unlocked to.....
stripped apart rebuilt with Clean Rom&XdaTechnology!!!
Hey,
Need some help here and not sure what's gone wrong, I've managed to root and flash custom ROM's before, but for some reason, my S7 now will not let me flash the BL file when trying to restore a stock ROM.
I can flash AP, CP and CSC with no problems, but trying to flash the BL file it gets half way and then the box at the top just goes red and says FAIL!
I've tried wiping everything from TWRP, installing custom ROM's and so forth to try and then restore from - phone is UK on BT Mobile and usually I use the XEU stock rom to reset.
The problem is, I have no carrier signal or IMEI information (I've tried the SIM in a different phone and it's working fine) so I can only presume it's something to do with the BL flash?
Any help is really appreciated!
Ok, well, hours of playing I found a SM-G930F combination firmware to flash (COMBINATION_FA60_G930FXXU2ARA2_BoxWares) - this has gotten me into FACTORY BINARY and lots of factory test / setting modes - phone now has it's IMEI number back AND I was able to receive a call from my girlfriends phone...
This seems to be running on Marshmallow 6.0.1 but obviously is not usable as an OS - so I need help to uprade firmwares in the correct order as trying to flash to 7 or 8 just fails in Odin and I can't seem to install TWRP recovery either from this.
I'm on BT Mobile (I used XEU before without issue - until recently!) so presume that's still the correct version...
Thanks!
Before I say anything DO you have a backup of your EFS folder do that first
Assuming you can only flash the binary 2 combination file firmware ,Samsung has recently updated their bootloader to not allow downgrades , you can only flash Nougat firmware from this year
Hey, I actually found that from some random spanish forum late last night... so I now have the combination rom with a useless (daily) front end / homescreen running android 6.0.1 but believe the bootloader is locked (from the nice little red error messages on startup) to a more recent version.
Supposedly I should be able to flash a `current` stock firmware then... but cannot seem to flash an AP file over this Combination rom install....
I did manage to download APKInstaller and install Kingroot (TWRP flash does not work - you cannot get into recovery anymore) and some other android apps (phone / sms / messenger) so have limited functionality but better than none for now.
No backups.
Boot into download mode , flash only the Sboot ( unzip the tar and make tar with only sboot) from any recent stock rom .
in AP put TWRP , untick the auto reboot.
when it passes( unplug phone ) hold the volume done , home power button till phone reboots (screen goes off) , quickly press volume up ,home and power button , you should be in TWRP
The combination firmware do not allow recovery modifications , it will just go in bootloop
OK, I'll try that when I get home later... lets say it works, what is my course of action then?
I still think I won't be able to flash a rom from Odin just by installing TWRP, so what actions do I need to take in TWRP? complete format ?
Thanks!
In TWRP make a backup of the EFS and Baseband partitions , copy to memory card .
I learned it the hard way , I ended up buying a second S7 with broken LCD so I can use the board
No box or tool can patch the certificate once you on Nougat as of yet
then you can go back to download mode and flash the AP ,CP ,CSC and phone should boot up , Leave the BL
Managed to get into stock recovery somehow (wasn't working before) and can see options for ADB sideloading etc again so that's something I guess lol
Presumably, if I can flash the boot file then twrp, I can then install a custom rom (i originally went from 7.0 up to 8 with Pixel Experience and Lineage, before things went tits up)
I'm guessing it'll be a case of formating data / wiping cache and installing the custom rom - assuming the BL is running 7.0 - or am i going to need to try and flash everything again via Odin (unsuccessful so far and only rom that will install is Combination)? also what about the CSC file...?
The only reason I'm in this predicament is because one of the custom roms somewhere (or google) screwed my IMEI settings, but Combination has brought those back.
you should be able to install any stock firmware from March 2018 onwards without any problems
Hmm ok so the network things I'm on T-Mobile and not BT Mobile lol (presumably because of the EUR flash) not sure if this will have implications when it comes to billing etc (BT bought out EE/T-Mobile but are different businesses still).
So does anyone have a working link to the XEU firmware? XEU-G930FXXS2DRC3-20180329132652 seems to be the filename... I can only find crap sites with 4kb downloads unless you pay $10-$20 lol
Success - in the absence of an upto date firmware from March for XEU - I found and installed the EUR one - BL everything went straight in and I've booted to setup screen now \o/
In Greek.... OK so hopefully I can just change language and wait for the XEU to surface (or is it OK to use the EUR? I have IMEI everything so looking good so far!)
I will probably flash Pixel Experience again unless someone recommends another over this?
Dreamz2k said:
Success - in the absence of an upto date firmware from March for XEU - I found and installed the EUR one - BL everything went straight in and I've booted to setup screen now \o/
In Greek.... OK so hopefully I can just change language and wait for the XEU to surface (or is it OK to use the EUR? I have IMEI everything so looking good so far!)
I will probably flash Pixel Experience again unless someone recommends another over this?
Click to expand...
Click to collapse
As someone said before.. Flash TWRP using ODIN; boot to twrp and make a backup of the EFS partition ONLY. Store the backup in the SD card and then copy it to the pc/dropbox/Drive/whatever. There are no guaranties that you wont loose the IMEI again if you attempt to flash the custom rom again. Then If you want to be on a completely stock rom, reflash the rom using ODIN. If you want to backup the baseband too, do the same procedure again but select only the baseband partition (untick the others)
To download stock roms you can use either the SamFirm tool (google search it.. it is on XDA) or Updato (site). Both of them provide really fast download speeds as there are no caps, and they are free. The files are downloaded straight from Samsung servers.
Sent from my SM-G930F using Tapatalk
Dreamz2k said:
Success - in the absence of an upto date firmware from March for XEU - I found and installed the EUR one - BL everything went straight in and I've booted to setup screen now \o/
In Greek.... OK so hopefully I can just change language and wait for the XEU to surface (or is it OK to use the EUR? I have IMEI everything so looking good so far!)
I will probably flash Pixel Experience again unless someone recommends another over this?
Click to expand...
Click to collapse
i guess i have the same problem like u....cant flash anything...just the combination file like u.....i have the stockrom from march but i cant flash this!! Odin does "Set partition" an do nothing!...
what can i do?
Hello everyone, looking for advice in how to return to factory firmware. First, a few bullets to condense the information, then an expanded explanation below. Any assistance would be appreciated.
TL : DR
-Xfinity Mobile GS8+, SM-G955U
-Phone boots and works fine
-When device was still on Nougat, the Oreo beta firmware update.zips were floating around
-Downloaded and installed via factory recovery said update.zips in succession
-Stuck on pre-release build, want to get back to official Verizon Firmware and receiving OTAs
-Current Build: R16NW.G955USQU2CRAD
-Desired Build: G955USQS5CRI4 (Verizon, 09.11.18)
-Tried flashing CRI4 package manually via Odin, Odin said no
-A few hours of Googling and reading through forums as etiquette demands I try first has led me to post this, never not been able to find a fix in the forums
-Plz help, will PayPal/GooglePay/whatever you a 12-pack of beer or whatever to whoever gets me back to factory
Things I've Tried:
-Factory reset
-Odin
-Smart Switch
-OTA
So I have a Galaxy S8+ purchased through Xfinity Mobile. I wasn't able to get into the Oreo beta officially offered through the Samsung Program, but there were update.zips floating around that allowed you to migrate to the pre-release builds. The samsung.firmware.science link above was relatively straightforward - pick your model, it had the latest official build, download an update.zip, and profit.
As the beta program progressed and various more final builds were released, these builds provided additional successive update.zips, until ultimately resting on what was the final version, build number R16NW.G955USQU2CRAD, which I am on currently. I use various forms of Package Disabler and had until recently kept a lot of Samsung's bloat disabled, including the OTA services. Note this only disables them and keeps them from running, not actually remove them from the phone.
Anyway, being an old ROM crackhead from back in the day when aftermarket ROMs actually provided significant software improvements over the garbage that OEMs ship on their phones, I don't like OTA updates that often because I prefer to factory reset after each update - the updates usually make the phone feel sluggish, which may be placebo, but here we are. In light of all the recent Android security vulnerabilities, despite not doing dumb stuff on my phone I figured it was time to go ahead and OTA to get the newest security patch. The issue is that my phone does not recognize any new OTAs despite being on a firmware build from January 2018.
I'm familiar with Odin, figure no big deal, grab the newest build for Verizon (Xfinity Mobile runs on Verizon towers, there's currently a Verizon sim in the device, and Xfinity Mobile builds seem to be entirely absent) and try to flash G955USQS5CRI4 dated 09.11.18. Verified through redundant sources this is, in fact, the latest Verizon build for the S8+.
Lo and behold, it doesn't work. Contacted Samsung regarding possible solutions, their chat agent wasn't very helpful, directed me to a local authorized repair store, who said they may or may not be able to flash it back with Samsung's software, and it requires what may be a two hour diagnostic that checks every possible thing it can on the device, and if it's not an official build, they will tell me to **** off, not withstanding the fact that the guy mentioned that the software from time to time glitches and crashes. My experience with flashing firmware makes me wary of what would happen during a system flash if the software crashes.
Anyway, for those of you who bothered to read past the TLR and embrace my dissertation, I've been out of the flashing game for a while, and because flashing factory firmware via Odin was my go to in the past, I'm not up to date on fixes for obscure issues. A few hours of Googling and reading through forums and I'm not anywhere closer than where I started, and I'd rather fix this myself rather than go to a store and potentially pay them for something that is "out of warranty."
Any ideas would be much appreciated, would gladly PayPal/Google Pay/Whatever someone a 12-pack of beer/$ to someone who can help me get this thing back to factory firmware.
Thanks in advance for any help.
From looking at your odin log almost looks like nothing was flashed, usually you will see abl.elf, modem, system.img, etc.... in the log while it's being flashed; After it checked the MD5 and started flashing it almost immediately closed it looks like but see no errors.
*After looking again I notice it says (success 0/fail 1) so it did not flash anything. Also make sure you are using the newest odin to flash
My suggestion, try flashing without USERDATA; When I flash I flash:
BL/AP/CP/CSC_OYM and not the HOME_CSC and never UserData
If that doesn't work try odin to G955USQU2CRC5 (Verizon 4/18) and then from there update to the latest update.
bmxmike said:
From looking at your odin log almost looks like nothing was flashed, usually you will see abl.elf, modem, system.img, etc.... in the log while it's being flashed; After it checked the MD5 and started flashing it almost immediately closed it looks like but see no errors.
*After looking again I notice it says (success 0/fail 1) so it did not flash anything. Also make sure you are using the newest odin to flash
My suggestion, try flashing without USERDATA; When I flash I flash:
BL/AP/CP/CSC_OYM and not the HOME_CSC and never UserData
If that doesn't work try odin to G955USQU2CRC5 (Verizon 4/18) and then from there update to the latest update.
Click to expand...
Click to collapse
Thanks for the response. I'm downloading the CRC5 file from Updato, and while the download speed is fluctuating, it's averaging around 50 KB/s with an ETA around 22~ hours. Is there a faster method to download this? I have a 300 Mb/s connection, so there's no bottleneck.
I'll try those steps in Odin, but can you expand on the reasoning so I understand the underlying mechanics? I was using the CSC_OYM and not the HOME_CSC, but why does this make a difference? Why never use USERDATA?
zerofighter1 said:
Thanks for the response. I'm downloading the CRC5 file from Updato, and while the download speed is fluctuating, it's averaging around 50 KB/s with an ETA around 22~ hours. Is there a faster method to download this? I have a 300 Mb/s connection, so there's no bottleneck.
I'll try those steps in Odin, but can you expand on the reasoning so I understand the underlying mechanics? I was using the CSC_OYM and not the HOME_CSC, but why does this make a difference? Why never use USERDATA?
Click to expand...
Click to collapse
I'm saying I have never flashed USERDATA as I've never seen it packed in most the roms I download, only other thing they have included is MAYBE a pit file for repartitioning. As for CSC:
Home_CSC: Flash the firmware without wiping the data (if you just want to update the ROM)
CSC: Flash the firmware along with a complete wipe including data (mostly used in cases like bricked phones or Go-Back-To-Stock situations)
I would try reflashing in download mode doing what I suggested and make sure that only reboot, nand erase, and f. reset are the only things checked.
As for downloads my suggestion is google try this:
site:androidfilehost.com G955USQU2CRC5
or
G955USQU2CRC5 filetype:zip (basing on the fact the roms I've downloaded all are zip format)
I think you can search from within the site, not sure. If you can find it always try download off filehost atleast I do because better speeds.
bmxmike said:
As for downloads my suggestion is google try this:
site:androidfilehost.com G955USQU2CRC5
or
G955USQU2CRC5 filetype:zip (basing on the fact the roms I've downloaded all are zip format)
I think you can search from within the site, not sure. If you can find it always try download off filehost atleast I do because better speeds.
Click to expand...
Click to collapse
https://forum.xda-developers.com/att-galaxy-s8+/how-to/g955u-stock-g955usqu2crc5-odin-files-t3773033
I managed to find this under AT&T SM-G955U thread, is this of any significance? Okay to flash?
zerofighter1 said:
https://forum.xda-developers.com/att-galaxy-s8+/how-to/g955u-stock-g955usqu2crc5-odin-files-t3773033
I managed to find this under AT&T SM-G955U thread, is this of any significance? Okay to flash?
Click to expand...
Click to collapse
Should have mentioned, the reason I'm asking is there is a discrepancy between the file size from Updato and this file - Updato file is 3.6~ GB and the one in this thread is 3.12~ GB.
No telling could be way it was compressed or files inside, like I said the rims I usually download don't include a USERDATA tar so maybe one has one and the other doesn't.
Have you tried again with what you have now?
There's been plenty of times I've tried to flash something to where I sometimes have to do it 3-5 times cause I over look something like under options (especially with resetting Odin cause when I do that it automatically enables partitioning for some reason). Also try a different USB cable, cause there should be something in Odin logs to lead you to problem; ex:
1 > 2 = This error usually means lower version Bootloader
Couldn't open file on XXXX: = Usually means partitioning was selected but no partition table given
Also if nothing else try flash in cosmey, I have yet to flash a v5 BL so I can't give you a this is what you need to do because my USB port is not working, but I've flashed from v1 to v3 in cosmey and have never had a issue with software only User Error (I'm trying to find a way to update from partycyborg to the same as you without Odin but cant because of my BL)
bmxmike said:
No telling could be way it was compressed or files inside, like I said the rims I usually download don't include a USERDATA tar so maybe one has one and the other doesn't.
Have you tried again with what you have now?
There's been plenty of times I've tried to flash something to where I sometimes have to do it 3-5 times cause I over look something like under options (especially with resetting Odin cause when I do that it automatically enables partitioning for some reason). Also try a different USB cable, cause there should be something in Odin logs to lead you to problem; ex:
1 > 2 = This error usually means lower version Bootloader
Couldn't open file on XXXX: = Usually means partitioning was selected but no partition table given
Also if nothing else try flash in cosmey, I have yet to flash a v5 BL so I can't give you a this is what you need to do because my USB port is not working, but I've flashed from v1 to v3 in cosmey and have never had a issue with software only User Error (I'm trying to find a way to update from partycyborg to the same as you without Odin but cant because of my BL)
Click to expand...
Click to collapse
Hey sorry, I've been busy working and haven't had the time to get back to this. I'm going to try this today and I'll get back to this post with an update.
Since people have trouble getting the boot images, here is my GoogleDrive folder containing stock boot images for Nokia 8 TA-1004 (NB1). Versions uploaded as follows:
2018 patches: October, November, December
2019 patches: January, February, March, April, May, Juni, July, August, September, October
2020 patches: January, April, July
You can root the images via Magisk manager and then flash the rooted versions as needed, or flash them directly to restore stock.
GoogleDrive link:
https://drive.google.com/drive/folders/1S5LkbSWECQN2GzKbGOSLZwSAM8238DXb
Palaryel said:
Since people have trouble getting the boot images, here is my GoogleDrive folder containing stock boot images for Nokia 8 TA-1004 (NB1). Versions uploaded as follows:
2018 patches: October, November, December
2019 patches: January, February, March, April, May, Juni, July, August, September, October
2020 patches: January, April, July
You can root the images via Magisk manager and then flash the rooted versions as needed, or flash them directly to restore stock.
GoogleDrive link:
https://drive.google.com/drive/folders/1S5LkbSWECQN2GzKbGOSLZwSAM8238DXb
Click to expand...
Click to collapse
Thank you kindly. :good:
Should I uninstall magisk and flash both slot_a and b with a stock img or is it enough with a or b?
iMaterial said:
Thank you kindly. :good:
Should I uninstall magisk and flash both slot_a and b with a stock img or is it enough with a or b?
Click to expand...
Click to collapse
Depends on what you want to do exactly. If you purely wanna go stock again, check your current active slot (fastboot getvar current-slot), reflash it to the proper version and then flash the other slot with a stock image thats one version lower than the current slot (as each OTA update does install to the opposite slot and swaps active slots on reboot).
If you want to be able to receive OTA updates it still might fail (generic error "Installation Problem") depending on what you did with root. If that is the case you'll have to reflash completely via NOST (but in most cases you can do so without erasing user data, hence keeping your apps/settings).
Palaryel said:
Depends on what you want to do exactly. If you purely wanna go stock again, check your current active slot (fastboot getvar current-slot), reflash it to the proper version and then flash the other slot with a stock image thats one version lower than the current slot (as each OTA update does install to the opposite slot and swaps active slots on reboot).
Click to expand...
Click to collapse
Ahh ok, so it switches slot for updates, so it has redundancy if the new boot doesn't work. Makes a lot of sense.
I flashed slot a with the current and the b with the one before, but I'm getting "installation problem" when trying for the july SP OTA.
iMaterial said:
Ahh ok, so it switches slot for updates, so it has redundancy if the new boot doesn't work. Makes a lot of sense.
I flashed slot a with the current and the b with the one before, but I'm getting "installation problem" when trying for the july SP OTA.
Click to expand...
Click to collapse
Something you did as root screwed up the system partition (using Adaway withotu systemless hosts enabled in Magisk will do that for example).
Your only option now is to actually reflash everything with NOST (if you want to keep user data uncheck the "Erase user data" box before flashing). After the flash your system should update without any issues (will update 3-4 times, takes a while). In case you reflash like this and it doesn't want to update, the only option is to reflash again while deleting all user data, apply all updates and the re-root.
NOST download:
Code:
https://tmsp.io/fs/xda/nb1/tools/nost/NOST-v0.6.exe
Stock image (NB1-5150-0-00WW-B05):
Code:
https://tmsp.io/fs/xda/nb1/firmware/NB1-5150-0-00WW-B05.qlz
Palaryel said:
Something you did as root screwed up the system partition (using Adaway withotu systemless hosts enabled in Magisk will do that for example).
Click to expand...
Click to collapse
So basically, if I want to keep getting the OTAs, I can do TWRP on one slot, but I shouldn't ROOT? Hmmpf, I wish we had LaOS.
iMaterial said:
So basically, if I want to keep getting the OTAs, I can do TWRP on one slot, but I shouldn't ROOT? Hmmpf, I wish we had LaOS.
Click to expand...
Click to collapse
Actually the rooting process itself isn't whats hindering the OTAs (as long as you restore the original boot images before the OTA). Its what you do with root.
Since I only use 2 apps which require root (Adaway and Titanium Backup) I found out that what has disabled me to use OTAs before was Adaway modifying the hosts file (which as I've said before you can avoid by enabling systemless hosts in Magisk - after I started using that option getting OTA updates was without problems). Having TWRP will require you to manually reflash it every time before installing an OTA (not really a big issue considering the phone is getting an OTA once every 3 months now).
Honestly HMD did quite some **** with this phone by not updating it to support Treble (considering the Hardware specs the phone is quite usable even today). I'm considering getting a Pixel 4a (or 5) once its available in the EU, I'm getting sick of HMDs carelessness.
Palaryel said:
Actually the rooting process itself isn't whats hindering the OTAs (as long as you restore the original boot images before the OTA). Its what you do with root.
Since I only use 2 apps which require root (Adaway and Titanium Backup) I found out that what has disabled me to use OTAs before was Adaway modifying the hosts file (which as I've said before you can avoid by enabling systemless hosts in Magisk - after I started using that option getting OTA updates was without problems). Having TWRP will require you to manually reflash it every time before installing an OTA (not really a big issue considering the phone is getting an OTA once every 3 months now).
Honestly HMD did quite some **** with this phone by not updating it to support Treble (considering the Hardware specs the phone is quite usable even today). I'm considering getting a Pixel 4a (or 5) once its available in the EU, I'm getting sick of HMDs carelessness.
Click to expand...
Click to collapse
Ach so! Leider! Yeah the phone is smooth as a rocket and I got it new in a box for €149 and I hate BIG clunky phones and not having 16:9 / 16:10 screen so. Flashing TWRP a few times a year wouldn't be a problem and I don't use Adaway, but greenify and file explorer Root. I do most of my backups via TWRP. Bleh! Es ist sehr wahnsinnig!
iMaterial said:
Ach so! Leider! Yeah the phone is smooth as a rocket and I got it new in a box for €149 and I hate BIG clunky phones and not having 16:9 / 16:10 screen so. Flashing TWRP a few times a year wouldn't be a problem and I don't use Adaway, but greenify and file explorer Root. I do most of my backups via TWRP. Bleh! Es ist sehr wahnsinnig!
Click to expand...
Click to collapse
Actually I forgot about File Explorer, which I also use in root mode. Also nothing Greenify does should actually compromise the system partition in away that prevents updates. But like I said, with this phone its a bit tricky, I've never been able to pinpoint the exact issue thats doing so. For OTAs to work seamlessly the phone has to be reverted to stock (unroot, stock recovery, stock hosts, unchanged system partition, etc), but apparently theres something more to it since at times even after flashing everything back to stock the updates would fail (in which case only a full revert to stock, including user data fixed the issue).
Also, what you wrote about big, clunky phones: thats exactly the reason I'm thinking about Pixel 4a/5, theyre both under 6'', hence relatively small and perfectly usable with one hand. Nowadays its become the trend to go 6,5+'' for flagships which I'm not really fond of.
Does somebody have that latest and last stock MR for October 2020 (00WW_5_16A) ?
Someone please help me.
"Fastboot devices"
(My device show up)
But after that, I can't enter any command.
It says Waiting for device.
My device show up in fastboot device as well as in Manage Devices in settings as Fastboot.
My Sp is October 2020.
I root my phone last July SP, bit lost root access after update.
Can somebody post the link to the latest Full OTA October 2020? Thanks
How to check your current security patch level. I want to root my phone, bootloader already unlock
Please someone help me
My current bulid no is
00WW_5_15G
Which image i use in above list
So now that I am rooted a can no longer receive OTA updates. Also, being a Sprint\Tmo device, I don't have "Local Upgrade" option.
Can someone tell me how I would now go about updating my device?
Do I simply wait for A11-based rom?
Do I need to remove magisk\modules in order to re-enable OTA?
Any help is appreciated.
I was actually about to ask this very question myself, the local update is missing on mine too, so that didn't change when you rooted? Maybe you can flash one of the stable releases they came out with recently? My question was would the global version work for our tmobile branded devices.
Also wondering wtf is up with tmobile cutting features out of the updates like shelf that dropped in July.
There is a guide to switch to global firmware.
It seems straight forward.
I would rather not.
If there was a stock rom image that we could simply flash via magisk or twrp, the process would be far simpler.
My guess is that for the method above to work, we will need to wait for A11 source code to drop.
Afterwards, we will likely see full A11 roms that we can use.
Ideally we would wipe system, data, cache. Flash rom. Wipe data again. Reboot.