yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] Droidriven:
No, telling them you have a different phone isn't going to work. Your phone actually identifies itself to the network based upon a combination of hardware and software information that the network detects or receives from the device remotely, their job on the other end is to set their network up to provide service to the identified device and to identify the device and the service as yours. If you tell them that you have a Pixel 4 and they configure the network on their end to make VoLTE work with Pixel 4 then VoLTE more than likely will not work on your device because the system thinks you have Pixel 4 hardware and software when you actually don't. That is like asking a car parts store for a starter for a Ford engine when you actually need a starter for a Nissan engine, they'll give you what you ask for but it doesn't mean the Ford starter will actually work on the Nissan engine.

Trying to trick them into enabling VoLTE probably won't work, if their system does not offer VoLTE support for your hardware itself, you will not be able to use VoLTE.

It basically boils down to this, control of whether VoLTE will work for you or not is completely in their hands, not yours, it is all done from their end, there isn't really anything you can do from your end.

If you want to use VoLTE on their network, then you need to get a device that is compatible with their VoLTE service and is actually supported by their network.

Even if you find a shortcut to make VoLTE work, somehow, someway, you will not be satisfied with the end result.
[General Questions and Answers] healerdan:
I think you are missing the part where I am using (in this example) programming and hardware from a pixel 4. this is only partly a hardware problem, but there's not as wide an array of different hardware types as you seem to think. a cursory search shows my device utilizes a snapdragon 855, and an X50 modem. The Oneplus 6T, which is permitted on AT&T's network utilizes the exact same hardware. The difference between the two phones is that Oneplus was ready to pay AT&T to check their software engineer's work.

If you want a car analogy it would be more like... I purchased an after market starter which has the same bolt& spindle pattern, and electrical configuration BUT when I connected everything ford's on-board diagnostics refused to start using a non-ford component. In this scenario, I have already done the starter installation and software patch, and know that these two things are operating as they should. I am now reaching out to the modder's forum to see if anyone knows of any other checks the OBD does to verify the starter which I should take into account while designing my patch before I turn on my car.

See first response - the communications hardware is the same between my phone and other phones on their whitelist.

VoLTE is just like any other communications protocol, it requires both devices to be able to communicate, and is a matter of both software and hardware. The thing that is lacking in my case is software, not hardware. and as the guide which I linked previously shows the software can be altered.

This seems to be getting at what I'm actually asking. I'm trying to see what other items are involved in the "handshake" between my device and the network which might cause a flag. do you know what the "combination of hardware and software information" which the carrier's network uses to identify my phone would be, specifically?
[General Questions and Answers] Droidriven:
Actually, my car analogy was accurate, I don't think I explained why as well as I could have. The hardware/software differences that I'm referring to equate to the differing parts having the same purpose and same function but having differening bolt patterns the same as a Ford/Nissan starter sharing the same purpose and function but have differing bolt patterns.

Yes, another device might share the same hardware components and be approved but that doesn't necessarily mean that there is cross compatibility because the two devices have other differences that come into play.

When I say "if they support your hardware", I am not referring to ONLY the radio hardware, I mean the whole device being different hardware, which means differences in kernel also because kernel and hardware are very closely related which comes into play because these components also play a part in identifying the device remotely. Using a kernel from another device won't work either because the "other" hardware differences between the devices would cause the kernel from another device to brick your device.

You can modify software and you can emulate software but emulation at the hardware level isn't really feasible for android.

Some of the "handshakes" that identify your device come from things that if you modify them to make the network see your device as a different device, it may cause your device to lose functionality, other parts are illegal in certain places so they can't be discussed here.

It is such a rabbit hole that it is just all around more sensible to just use a device that is compatible without modifying. If you want to use VoLTE on AT&T, you'll have more success by playing their game because they hold the cards.
[General Questions and Answers] blackhawk:
AT&T Digital Resources & Answers - Community Forums has Sunset

The AT&T community forum has been sunset, we have compiled the list of new resources that you can use to find answers to any AT&T related question.

forums.att.com

List of supported unlocked phones and services available:
[Touch Diamond, MDA Compact IV Themes and Apps] Hind1:
I researched this previously and found a fix, but I recently hard reset my device and forgot how to fix. After a page has loaded in opera, if I rotate the device, it will rotate, return to portrait mode, and then minimize. Opera is still in in the task manager and I can return to it, still in portrait mode. The previous fix was a registry edit that had something to do with removing a title bar or something.

If I have missed the thread please let me know.

Thanks in advance,

- Hind1
[Touch Diamond, MDA Compact IV Themes and Apps] lude219:
the registry fix that you're referring to basically shows the clock on the title bar. A minor nuisance is that it blocks the battery status. If someone can find a fix for this (that doesnt require a clock blocking the battery status), that'll be awesome!
[Touch Diamond, MDA Compact IV Themes and Apps] Hind1:
I agree, that would be pretty awesome, but the fix I am referring to would fix the problem of Opera closing when rotated into landscape mode.
[Touch Diamond, MDA Compact IV Themes and Apps] tumolo:
I am having the exact same problem. Someone Help.
[Touch Diamond, MDA Compact IV Themes and Apps] StyL3-Ivan:
u just have to install the default HTC Diamond volume adjuster cab will solve it
[Touch Diamond, MDA Compact IV Themes and Apps] tumolo:
do you happen to have a link or can you send me a file for the original. My smart self didnt back up any of my original files before I customized everything. Thanks
[Touch Diamond, MDA Compact IV Themes and Apps] StyL3-Ivan:
http://xdaforums.com/showpost.php?p=2536734&postcount=2

Download from swtos. [ Volume Control Diamond (reboot after installation) ]
[Touch Diamond, MDA Compact IV Themes and Apps] tumolo:
You guys are the best. Thanks for the help
[Android Apps and Games] E1e5en:
Link: NewYear Postcard

Genre: Puzzle.

Description:

Indirect control puzzle platformer. You need to help the Christmas tree decorations get to the New Year tree. To create a New Year postcard and save it on your device!

Advertising in the game: You can see that an advertisement has been added to the Android version of the game, but you can only see it if you want to (the “Say ”Thank you"button). There will be no banners or before/during/after the level.

​

Have a good game! =)

View attachment 5495487
[Samsung Galaxy Tab S7 FE] Awesomeslayerg:
Hey everyone,

UPDATE: WORKS WITH ANDROID 13! You can now use the more stable verison!!

Thanks to the people at github, yujincheng08 , updated one of the github commits and was finally able to root this device.

How to unlock:

Should be the same as any other samsung device. Follow my S6 Lite guide.

How to root:

1. Download the firmware for your your tablet, i dont know if i can link the sites but you can google it. (frija is recommended and is the fastest)

2. Extract only the AP portion of the firmware.

3. Open up the AP portion with 7-zip or winrar

4. extract the boot.img.lz4 out of the AP file

5. Download Lz4 https://github.com/lz4/lz4/releases to your pc corresponding version.

6. Extract the LZ4 to the same area where the boot.img.lz4 is

7. Open command prompt in that folder and then do

lz4 boot.img.lz4 boot.img

8. Download this magisk version from github

Release Magisk v24.3 · topjohnwu/Magisk

For those coming from v24.1, check the full changelog for changes introduced in v24.2. [General] Stop using getrandom syscall [Zygisk] Update API to v3, adding new fields to AppSpecializeArgs [App...

github.com

9. Extract the app-release.apk

10.. Connect your tablet and put it in your downloads folder

11. Install it via th My Files or use a file explorer.

12. Move the boot.img into the tablet and use the magiks that you just installed and patch it using that .

13. Move the magisk_patched version back to your pc, rename it to boot.img and create a tar version of it (i used 7-zip)

14. Open up odin , put your device to download mode and then patch the AP using the boot.tar you just created.

15. It should reboot, wait a few seconds and it may reboot a couple times. Then it may ask you to factory reset and just reset.

16. Once you setup your tablet again, connect your pc and do all that usb setup agagin and then move that app-release.apk again.

17. Youre gonna have to install the app-release again but uninstall the magisk already installed on your device first then install it via the apk

18. It should say additional setup required so do that, reboot and you should have root!
[Samsung Galaxy Tab S7 FE] derrickdroid:
Has anyone else tried this guide?? Not trying to brick my new tablet so would like to know if it works for anyone! Thanks in advance!
[Samsung Galaxy Tab S7 FE] ahrmakrm1235:
https://github.com/topjohnwu/Magisk/suites/4781599968/artifacts/133467701

This site is don't work. Can you share this file?
[Samsung Galaxy Tab S7 FE] 1987tlz:
Thanks for the notice. Just rooted my device successfully using the latest Magisk build from the master branch. Works great!

@ahrmakrm1235 The github artifacts link will only work if you are logged into Github (create a new account if need to, it is free).
[Samsung Galaxy Tab S7 FE] zriw:
first time rooter here. do you mind specifying what you mean by opening command prompt in the folder? i extracted the contents of the Lz4 application into the folder containing the boot file. when I open command prompt, i drag that folder there and then enter the code, but it's not doing anything.
[Samsung Galaxy Tab S7 FE] ahrmakrm1235:
Thank you so much. I success to root sm-t733
[Samsung Galaxy Tab S7 FE] Flaccthehawk:
Use 7zip zs, free and works just like 7zip , easier method than the lz4 extract.
[Samsung Galaxy Tab S7 FE] zriw:
@Flaccthehawk I'm going to try it out now and see if it makes a difference. If not, I'll edit and add pictures or a screen recording of what I'm doing wrong.

Edit: I did everything correctly, but I'm having trouble flashing the tar file. It keeps failing. I've already tried updating to the latest odin version of 3.14 & I know the firmware is correct because I downloaded it using frija. Any suggestions? I've attached what the error looks like below and my tablet in download mode in case there's an issue there.
[Samsung Galaxy Tab S7 FE] 1987tlz:
In step 13 when creating the tar file for the boot image, what did you use for this? Did you use 7-zip? And did you select the tar option in the archive option in 7-zip (or another program)? Note that it must be a proper tar file. If the file created is a zip or 7z file, it won't work even if you rename the output file as a tar file.

Can you open the tar file using 7zip. Provide a screenshot of what is displayed here. Also within 7-zip after opening the tar file, click into File - Properties and provide a screenshot of this also.

FYI: I actually removed root for now. I noticed the battery was draining a lot quicker than before with Magisk (I did a clean format/flash too when rooting the device). Removing root, battery life is back to normal.
[Samsung Galaxy Tab S7 FE] imjizho:
I'm new here, do I need to unlock bootloader before process this?
[Samsung Galaxy Tab S7 FE] 1987tlz:
Yes, the bootloader needs to be unlocked. Note that the device will be erased when unlocking the bootloader so backup any data that you need before doing so.
[Samsung Galaxy Tab S7 FE] zriw:
@1987tlz Yes, I used 7zip to to open the boot file and selected tar as you can see here.
[Samsung Galaxy Tab S7 FE] imjizho:
Thank you so much, success to root (SM-T735).
[Samsung Galaxy Tab S7 FE] imjizho:
Hi again, I have problem about SafetyNet test failed (basicIntegrity -, ctsProfile -, evalType BASIC), also I cannot enable MagiskHide (after I enable and back to Magisk home, it's change back to disable). Does it possible to bypass SafetyNet test and enable MagiskHide?

Many Thanks :)
[Samsung Galaxy Tab S7 FE] 1987tlz:
@zriw It wasn't clear from the screenshots, but for the file patched by Magisk, did you rename this to boot.img? Once the file is named as boot.img, then you create the tar file as boot.img.7z. Now you should be to flash it again using Odin.

@imjizho It looks like you are not using a recent version of Magisk, as MagiskHide doesn't exist anymore. On the latest release, Zygisk needs to be enabled and then you can enforce and configure the DenyList.

For passing SafetyNet, the latest version of this module will do the job:

GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk

Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix

github.com
[Samsung Galaxy Tab S7 FE] imjizho:
All done! Thanks a lot @1987tlz

I found that the problem occurred when I try to hide the Magisk app, it will installed previous version and cannot change back when restore.
[Samsung Galaxy Tab S7 FE] Typhoon_Master:
Can others confirm the battery drain with root?

Rooting was the first thing i did with the tablet, i have no reference if it is really draining the battery.

//edit:

removing some bloatware (netflix, chrome, and so one) lead me to a bootloop
[Samsung Galaxy Tab S7 FE] derrickdroid:
Im not finding bootloader unlock and am not sure if i have done it correctly on this samsung device.

This is what i have done,

1.Settings>About Tablet>Software Information

2.Tap Build Number repetitively until Developer Settings Enabled

3.Settings>Developer Options

4. Turn OEM Unlocking on

Is this all there is to it? I feel like im missing something.

*** EDIT

Found that if holding both volume down and volume up while plugging the tablet into my PC i was able to find more options to bootloader unlock as well as warnings. After accepting those it did a factory reset. I hope this is all i needed to do.
[Samsung Galaxy Tab S7 FE] derrickdroid:
Thank you, i have successfully achieved root!
[Samsung Galaxy Tab S7 FE] derrickdroid:
Have you tried freezing the bloatware apps with Titanium Backup located in the Play Store?
[Samsung Galaxy Tab S7 FE] drishya10101:
Can you please provide the updated link for magisk? Seems like the link you provided is broken.
[Samsung Galaxy Tab S7 FE] Typhoon_Master:
Thanks, why didn't I think of that?

Please read further in the thread ...
[Samsung Galaxy Tab S7 FE] ThoBlu:
Hi,

I followed the instructions, but after flashing the Magisk Canary patched boot.img with Odin, I got a bootloop. So I flashed the original boot.img and the tablet worked again. Any suggestions?
[Samsung Galaxy Tab S7 FE] cl0we:
Hi guys, I got stuck in a boot loop and tried flashing the original firmware but still can't get past the bootloop. Any ideas on what I can do?
[Samsung Galaxy Tab S7 FE] ThoBlu:
Prepare Odin with the untouched boot.bin in a .tar file. Disconnect the device from your pc. In bootloop press an hold the powerbutton for about 10 seconds and the tablet will shut down. Then press an hold volume up an down and connect the tablet to the pc. The tablet starts in download mode and you can flash the untouched boot.bin. After this, your tablet will start again.
[Samsung Galaxy Tab S7 FE] zriw:
I managed to get a pass from Odin by using not only the AP file but the other files included when extracting the firmware as well. However, when my tablet reboots it doesn't erase to factory settings. I factory reset it manually and didn't get the error which is apparently supposed to show up that says I'm running unofficial samsung software. I also redownloaded magisk to see if it would prompt me to complete the root, but it didn't. The flash worked but didn't show up on my device, so how do I fix this?
[Samsung Galaxy Tab S7 FE] Trevaryn:
I have tried rooting my tablet like 3 times now and i keep getting "this tablet is not running samsung official software". Could i pay someone to just do it for me lol
[Samsung Galaxy Tab S7 FE] derrickdroid:
I have noticed my Magisk app has a notification of an app update, can i update it and still have root?

Screenshot with version info
[Samsung Galaxy Tab S7 FE] ThoBlu:
Finally, I rooted my Tablet. New Magisk 24.1 works.

Happy rooting
[Samsung Galaxy Tab S7 FE] hjam88:
I keep getting

<ID:0/009> RQT_CLOSE !!

And on the device it shows

Custom binary boot blocked by oem lock
[Samsung Galaxy Tab S7 FE] ThoBlu:
You forgot the OEM Unlock.
[Samsung Galaxy Tab S7 FE] discomilk:
I keep getting a bootloop saying my data partition is damaged, is there something I'm missing? Neutralized vbmeta? Something else maybe?

Edit: Nevermind, I'm an idiot. That was all apart of the plan

Magisk up and running with root, thanks for the guide. next time I'll read each and every word :D
[Samsung Galaxy Tab S7 FE] noahthedominator:
Thank you for the guide.

Using the instructions I have rooted my tab s7fe.

For those who were also confused like I was.

Use this to download firmware. Wifi S7FE in the states should be model Number SM-T733 and XAR for code.

GitHub - zacharee/SamloaderKotlin

Contribute to zacharee/SamloaderKotlin development by creating an account on GitHub.

github.com

2. Using Magisk 24.1 worked fine. Upon installation from Odin I hate to reset tablet again.

3. Opening magisk again I was prompted that magisk needed an update and would automatically reboot.

Clicking OK quickly updated magisk, and rebooted my device. (I did not have to uninstall / reinstall. Magisk seemed to figure it out on its own.)
[Samsung Galaxy Tab S7 FE] MoonRule:
@zriw Same! I did everything right and it still failed on me. Wonder what we did wrong​
[Samsung Galaxy Tab S7 FE] fred767676:
Thank you for the great HoTo. Everything works fantastic. Best regards fred.
[Samsung Galaxy Tab S7 FE] derrickdroid:
Can't seem to get Magisk to update through the app. Any suggestions?
[Samsung Galaxy Tab S7 FE] mrindependent:
I don't usually root my samsung devices but currently only have my pixel 6 pro and s21 Ultra which doesn't need to rooted and then I have this. I guess its just the nerd in me but it really bothers me that I dont have any devices rooted lol. I have a few questions for those who have rooted yours. first, if rooted do all of the Samsung features still work? Like the secure folder and all? Also, are there any real benefits in root ing this tab? Whey did you guys root and what magisk apps or root- only features do you use on this"special edition" tab ? I alway seem to buy the tablet that ends up getting the least amount of support or becomes obsolete or outdated the quickest. a traded in my tabs S5 e for this. So bummed there are no custom roms and I know that by now if there aren't any that s not a good sign... and that we don't have android 12 Yet...there is no reason for that. So far it seems like the extra letters (Fe) are just like the "a" they add to the pixels, etc. and its just like the cheaper version. Anyways thank you!
[Samsung Galaxy Tab S7 FE] derrickdroid:
I have noticed a large increase in battery drain when the tablet is idle after rooting... I now have to turn off the tablet when I am done using it otherwise when I go to use it the following day it needs to be charged.

As of right now with no custom roms I'm not sure if rooting was even worth it because it hasn't changed the way I use the tablet. I am weary of doing any kind of modifications because we don't have a recovery and I have been out of the root game since the Samsung S4. So I'm not even sure what kind of things I could do with root access. I almost want to get rid of it and go back to stock so I can get updates from Samsung.

Is rooting android devices dieing or is it just Samsung devices?
[Samsung Galaxy Tab S7 FE] jac0b:
Does this work on the T-738U?
[Samsung Galaxy Tab S7 FE] ThoBlu:
Just follow the instructions and use Magisk 24.1 or 24.3.
[Samsung Galaxy Tab S7 FE] Yevgen.A:
1) Root gives you Adaway hosts override, Magisks modules, youtube vanced, LP => no google ads in the apps, system r/rw. I am mostly use root to remove bloatware and ads

2) check your battery usage by app. Root should not be the cause.
[Samsung Galaxy Tab S7 FE] Yevgen.A:
Did anyone tried TWRP flashing?
[Samsung Galaxy Tab S7 FE] ghms@3204:
Spen still working :3?
[Samsung Galaxy Tab S7 FE] strifej:
I'm still on A11 on my FE but have the A12 update ready to install. Does root work fine on A12 One UI 4.1 as well?
[Samsung Galaxy Tab S7 FE] Awesomeslayerg:
Yep you can download the Normal stable github verison!
[Samsung Galaxy Tab S7 FE] coolblood2:
Does this root work with the T-Mobile version? I have one on backorder coming and would love to root it!
[Samsung Galaxy Tab S7 FE] Yevgen.A:
SM-T733, yes, it works
[Samsung Galaxy Tab S7 FE] timg11:
Step 9. "Extract the app-release.apk"

What is app-release.apk? I can open the Magisk-v24.3.apk, but there is no file contained within called "app-release.apk". The Github page has "stub-release.apk" available. Is that the same thing?

Or is "app-release.apk" just a generic shorthand for Magisk-v????.apk, whatever the current version is?

Edit: I successfully completed the process using only Magisk-v24.3.apk, so the "shorthand" explanation seems to be correct.
[Samsung Galaxy Tab S7 FE] amgreenhawk:
Can I use Magisk v23 instead to patch and flash?
[Samsung Galaxy Tab S7 FE] Aethera:
Yes
[Samsung Galaxy Tab S7 FE] amgreenhawk:
Thanks.
[Samsung Galaxy Tab S7 FE] Vuura:
When using Odin to attempt to patch the AP with the boot.tar, it gets stuck on file analysis. Has anyone else had this problem ? Cables are brand new, usb port is proven reliable. Odin version is 3.14.4. USB debugging is on, and bootloader is unlocked. Any comments or suggestions would be greatly appreciated.
[Samsung Galaxy Tab S7 FE] fict:
anyone have tried gsi roms?
[Samsung Galaxy Tab S7 FE] t0urista2:
I could successfully root my TAB S7 FE (SM-T733) with the procedure described in this post.

Everything works well, pen included

Android 12

firmware : T733XXU1BVH4_T733OXM1BVH4_EUX

Magisk 25.2

Odin3_v3.14.4

lz4_win64_v1_9_4
[Samsung Galaxy Tab S7 FE] avemt1:
Newest update, and I'm just getting a boot screen with a download DID: (16 digit alpha-numeric number) barcode. I tried the unbrick method, but it says "An error has occurred while updating the device software." The device would not load, and it just shows the error screen. After a bit of research and looking, I found out that Frija downloaded the wrong firmware. It downloaded the firmware for SM-G965F no the SM-T773.

How do I fix this?