yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab S8] Wilazn:
It tells you if you click the link and read the specs...

Supported Bands : 5G Bands 28/20/5/8/1/40/41/38/7/78/77, LTE Bands 1/2/4/5/7/8/12/13/17/20/25/26/28/32/38/40/41, 3G/HSPA Bands 5/8/3/2/39​

For 5G, T-Mobile is using band 71 (600 MHz) for low-band, band 41 (2,500 Mhz) for mid-band, as well as faster mmWave in select downtown areas.
[Samsung Galaxy Tab S8] hammody:
I got the 512gb 5G (16gb ram) from Switzerland
[Samsung Galaxy Tab S8] JHCCAZ:
I've been checking the Samsung Shop site, and T-Mobile also. Today I saw that the "Coming Soon" note, as captured above, is now gone for the S8 Ultra 5G. At this time you can order the S8+ 5G from Samsung or from T-Mobile, but only the Wi-Fi version of the S8 Ultra is listed by Samsung (and of course not on T-mobile as they would generally not be selling Wi-Fi devices).

This is disappointing and I hope it's simply a matter of time - but I'm not very optimistic that T-mobile will sign up to carry the Ultra 5G alongside the + 5G, especially after the product-intro excitement has died down.

I think that Samsung was caught unprepared for the level of interest in the S8 Ultra, and this created a backorder delay that is now killing the momentum and the success of the launch. I hope I'm wrong, but I'm now very doubtful that I'll be able to upgrade my T-mobile S7+ to an S8 Ultra.
[Samsung Galaxy Tab S8] Wilazn:
I ended up just getting the S8+ 5G. Can't wait for the ultea 5G anymore. Worse comes worse if they do release it for Tmobile, I'll sell the s8+.
[Samsung Galaxy Tab S8] Wilazn:
You have a link? I want to see what bands are supported. The Korean version doesn't support the bands used by Tmobile here.
[Samsung Galaxy Tab S8] hammody:
https://www.galaxus.ch/en/s1/product/samsung-galaxy-tab-s8-ultra-5g-1460-512-gb-graphites-tablets-18384344?supplier=406802

There you go
[Samsung Galaxy Tab S8] Wilazn:
Damn it doesn't say which band it supports.
[Samsung Galaxy Tab S8] DJJasonK:
Has anyone found out any info on this? Finally bit the bullet and bought the wifi version. Would still like to get the verizon 5g.
[Samsung Galaxy Tab S8] infinitist:
Noticed my wifi version has a fake simcard glued to the mini sd card trays back ... So I looked inside the slot and noticed there's sim pins ready to go as if the WiFi models could just be software I locked and become 5g models .... Anyone else seeing this ? Is this something we can just mod ourselves instead of waiting for the 5g models to restock ?
[Nokia 6.1 (2018) Guides, News, & Discussion] marchnz:
Nokia 6.1 - TA-1050 LineageOS 18.1 install

Note: These use A/B slots.

Thanks to @Raghu varma

Prerequsites:

- Official LineageOS 18.1 https://wiki.lineageos.org/devices/PL2/

- Unofficial TWRP (for) Android 11: https://xdaforums.com/t/unofficial-twrp-3-4-0-0-team-win-recovery-project-nokia-6-1-plate2.4122949/

With TWRP, it must match the Android version being installed.

- Gapps For Android 11 ARM64: https://wiki.lineageos.org/gapps

Install ADB/Fastboot on Windows.

- Unlocked bootloader

- Know how to place phone into download mode (hold power and vol down)

Note: TWRP is NOT installed. We directly boot the TWRP image

FILE

each time TWRP is needed with the following commands:

From ADB in windows:

1. fastboot flash recovery twrp-3.4.0-0-PL2_sprout-11.0-20200909.img (ERRORS OUT - this is OK)

2. fastboot boot twrp-3.4.0-0-PL2_sprout-11.0-20200909.img

Installation procedure for the roms which doesn't comes with gapps

==============

1. Boot in to twrp (phone in download mode)

2. Click on wipe

3. Select format data

4. Type yes

5. Reboot to bootloader

6. Boot in to twrp

7. Select wipe

8. Select advance wipe

9. Select all except sdcard

10. Swipe to wipe

11. Copy rom.zip

12. Flash ROM.zip

11/12 - ADB Sideload LineageOS ROM:

a. In TWRP - Enable ADB Sideload

b. From PC: adb sideload lineage-18.1-20220208-nightly-PL2-signed.zip (Note: NO ERRORS ignore forums)

13. CHANGE SLOT (instructions continue below)

View attachment 5536701

a. In TWRP

Change SLOT:

Menu back to Reboot Options) Example: Refer Image, e.g. Current SLOT is A, change to B)

b. Reboot to TWRP again

c. Via ADB (per steps 11/12) flash

GAPPS

- adb sideload MindTheGapps-11.0.0-arm64-20210920_084011.zip

14. Select wipe

15. Select advance wipe

16. Select all except system vendor SD card and swipe to wipe

17. Reboot system
[Nokia 6.1 (2018) Guides, News, & Discussion] chi70:
I am longer trying to get LOS to my Nokia 6.1 and this procedure is the one I got most success so far.

I installed LOS on different mobiles and tablets before but this Nokia 6.1 PL2 TA-1043 seems to be different and difficult.

The Device is unlocked and adb and fastboot are working:

fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true <<-----
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.001s

I did a stockrom installation from https://nokia-sdm660.github.io/ and bootet both slots until the installation/configuration process started.

Then I started with above procedure.

Poweroff, booted Bootloader

add 1: additional: swipe to allow modifications

Followed till 10

11: I assumed copy from download directory to where adb finds it

12 worked fine

13: change slot -> OK

From there I cannot boot TWRP anylonger. Flasshing MindTheGapps at Point 12 results in unbootable Phone,

it gets into reboot loop.

Questions:

1. Is the slot change needed to install MindTheGapps?

2. If yes (I assume it is needed), any idea what I am doing wrong?

I am running on Linux, doing UNIX'ish OS since 1995 and I am very unused to Windows.

Info:

I accidently bootet TWRP-3.6 once and there no sideload started at all.
[Nokia 6.1 (2018) Guides, News, & Discussion] marchnz:
Hi,

Do not install TWRP.

Note: TWRP is NOT installed. We directly boot the TWRP image

FILE

each time TWRP is needed with the following commands:

From ADB in windows:

1. fastboot flash recovery twrp-3.4.0-0-PL2_sprout-11.0-20200909.img (ERRORS OUT - this is OK)

2. fastboot boot twrp-3.4.0-0-PL2_sprout-11.0-20200909.img

Instructions revised for clarity based on your feedback - Thanks.

I spend hours trying to get LineageOS on my TA-1050. With these steps, I can do it quickly every time.

Dont give up, you will get there!
[Nokia 6.1 (2018) Guides, News, & Discussion] chi70:
I did not install TWRP but now I was able to install LOS 18.1!

I missed the

fastboot flash recovery twrp

before the

fastboot boot twrp

in 13.b.The ones before switching slot worked without.

Anyway, now the setup is running.

Thanks to all for the procedure, LinegaeOS, TWPR...

Christian
[Introductions] Rpger1:
Hello,

I have an old Tablet, Android Marshmellow 6.0.1 and I would like to re-flash the OS, as I am having some issues that don't seem to be solved with a reset. Where do I get a Rom and how do I do it.

Cheers, Rob. Stay Healthy Stay Safe
[Introductions] Badger50:
Welcome to XDA Rob. What type of tablet do you have so we can narrow your search?
[Introductions] Rpger1:
Hello Thank you for the reply, It's an old Polaroid Q1010 Tablet and Keyboard It's like New and like to keep using it for my Reading, and some light google play.

View attachment 5533921
[Xiaomi Mi 11] tyronekndrck:
Mi11 is Best phone I ever had. at&t sent me a old 2010 phone and says my mi11 won't work on the network anymore because it use old 3g. My phone haven't got shut off yet soon will be. My question is, how can I go about changing imei to a different phone. These phones have 5g and volte. It's kind of a scam on AT&T part
[Xiaomi Mi 11] Quietsch:
are you shure your Mi11 is not stolen ? changing IMEI and Mac is a criminal act. I hope nobody is so stupid to help you. If you tell the thuth its better to change your Provider.
[Xiaomi Mi 11] senkrad76:
You just have to enable volte and vowifi. They tried the same with me.

https://www.reddit.com/r/Xiaomi/comments/ft8k27
[Xiaomi Mi 11] shadowstep:
THREAD LOCKED

@tyronekndrck Edit or change of IMEI is illegal in quite a few of countries. Due to this reason, discussions on this subject are not permitted on XDA. As per Rule 9 of the Forum Rules:

Regards,

shadowstep

Forum Moderator
[General Topics] LMFuture:
FAILED: out/target/product/chopin/boot.img

/bin/bash -c "(out/host/linux-x86/bin/mkbootimg --kernel out/target/product/chopin/kernel --

ramdisk out/target/product/chopin/ramdisk-recovery.img --cmdline \"bootopt=64S3,32N2,64N2 andr

oidboot.selinux=permissive androidboot.init_fatal_reboot_target=recovery buildvariant=userdebu

g\" --base 0x40078000 --pagesize 2048 --recovery_dtbo device/xiaomi/chopin-prebuilts/base/dtbo

.img --dtb out/target/product/chopin/dtb.img --os_version 11 --os_patch_level 2021-12-05 --bas

e 0x40078000 --dtb device/xiaomi/chopin-prebuilts/base/dtb.img --dtb_offset 0x07c08000 --pages

ize 2048 --kernel_offset 0x00008000 --ramdisk_offset 0x11088000 --tags_offset 0x07c08000 --sec

ond_offset 0xbff88000 --header_version 2 --output out/target/product/chopin/boot.img ) && (si

ze=\$(for i in out/target/product/chopin/boot.img; do stat -c \"%s\" \"\$i\" | tr -d '\\n'; e

cho +; done; echo 0); total=\$(( \$( echo \"\$size\" ) )); printname=\$(echo -n \" out/target/

product/chopin/boot.img\" | tr \" \" +); maxsize=\$(( 134217728-69632)); if [ \"\$total\"

-gt \"\$maxsize\" ]; then echo \"error: \$printname too large (\$total > \$maxsize)\"; false;

elif [ \"\$total\" -gt \$((maxsize - 32768)) ]; then echo \"WARNING: \$printname approaching s

ize limit (\$total now; limit \$maxsize)\"; fi ) && (out/host/linux-x86/bin/avbtool add_hash_f

ooter --image out/target/product/chopin/boot.img --partition_size 134217728 --partition_nam

e boot --prop com.android.build.boot.fingerprint:\$(cat out/target/product/chopin/build_finge

rprint.txt) --prop com.android.build.boot.os_version:11 )"

Traceback (most recent call last):

File "/mnt/sda1/AndroidSources/PixelExperience11P/out/host/linux-x86/bin/mkbootimg/internal/

stdlib/runpy.py", line 174, in _run_module_as_main

File "/mnt/sda1/AndroidSources/PixelExperience11P/out/host/linux-x86/bin/mkbootimg/internal/

stdlib/runpy.py", line 72, in _run_code

File "/mnt/sda1/AndroidSources/PixelExperience11P/out/host/linux-x86/bin/mkbootimg/__main__.

py", line 12, in <module>

File "/mnt/sda1/AndroidSources/PixelExperience11P/out/host/linux-x86/bin/mkbootimg/internal/

stdlib/runpy.py", line 174, in _run_module_as_main

File "/mnt/sda1/AndroidSources/PixelExperience11P/out/host/linux-x86/bin/mkbootimg/internal/

stdlib/runpy.py", line 72, in _run_code

File "/mnt/sda1/AndroidSources/PixelExperience11P/out/host/linux-x86/bin/mkbootimg/mkbootimg

.py", line 321, in <module>

File "/mnt/sda1/AndroidSources/PixelExperience11P/out/host/linux-x86/bin/mkbootimg/mkbootimg

.py", line 308, in main

File "/mnt/sda1/AndroidSources/PixelExperience11P/out/host/linux-x86/bin/mkbootimg/mkbootimg

.py", line 128, in write_header

struct.error: 'I' format requires 0 <= number <= 4294967295

08:51:11 ninja failed with: exit status 1

It happened when I was trying to build PixelExperience11Plus with a prebuilt kernel. How can I fix it.
[General Topics] Oswald Boelcke:
@LMFuture Thread closed as duplicate of

https://xdaforums.com/t/i-have-an-issue-when-i-was-building-pixelexperience.4400597/

Please review the XDA Forum Rules with special emphasis on rule no. 5 and post only ONCE! Thanks for your cooperation.

Regards

Oswald Boelcke

Senior Moderator
[Android Q&A, Help & Troubleshooting] LMFuture:
FAILED: out/target/product/chopin/boot.img

/bin/bash -c "(out/host/linux-x86/bin/mkbootimg --kernel out/target/product/chopin/kernel --

ramdisk out/target/product/chopin/ramdisk-recovery.img --cmdline \"bootopt=64S3,32N2,64N2 andr

oidboot.selinux=permissive androidboot.init_fatal_reboot_target=recovery buildvariant=userdebu

g\" --base 0x40078000 --pagesize 2048 --recovery_dtbo device/xiaomi/chopin-prebuilts/base/dtbo

.img --dtb out/target/product/chopin/dtb.img --os_version 11 --os_patch_level 2021-12-05 --bas

e 0x40078000 --dtb device/xiaomi/chopin-prebuilts/base/dtb.img --dtb_offset 0x07c08000 --pages

ize 2048 --kernel_offset 0x00008000 --ramdisk_offset 0x11088000 --tags_offset 0x07c08000 --sec

ond_offset 0xbff88000 --header_version 2 --output out/target/product/chopin/boot.img ) && (si

ze=\$(for i in out/target/product/chopin/boot.img; do stat -c \"%s\" \"\$i\" | tr -d '\\n'; e

cho +; done; echo 0); total=\$(( \$( echo \"\$size\" ) )); printname=\$(echo -n \" out/target/

product/chopin/boot.img\" | tr \" \" +); maxsize=\$(( 134217728-69632)); if [ \"\$total\"

-gt \"\$maxsize\" ]; then echo \"error: \$printname too large (\$total > \$maxsize)\"; false;

elif [ \"\$total\" -gt \$((maxsize - 32768)) ]; then echo \"WARNING: \$printname approaching s

ize limit (\$total now; limit \$maxsize)\"; fi ) && (out/host/linux-x86/bin/avbtool add_hash_f

ooter --image out/target/product/chopin/boot.img --partition_size 134217728 --partition_nam

e boot --prop com.android.build.boot.fingerprint:\$(cat out/target/product/chopin/build_finge

rprint.txt) --prop com.android.build.boot.os_version:11 )"

Traceback (most recent call last):

File "/mnt/sda1/AndroidSources/PixelExperience11P/out/host/linux-x86/bin/mkbootimg/internal/

stdlib/runpy.py", line 174, in _run_module_as_main

File "/mnt/sda1/AndroidSources/PixelExperience11P/out/host/linux-x86/bin/mkbootimg/internal/

stdlib/runpy.py", line 72, in _run_code

File "/mnt/sda1/AndroidSources/PixelExperience11P/out/host/linux-x86/bin/mkbootimg/__main__.

py", line 12, in <module>

File "/mnt/sda1/AndroidSources/PixelExperience11P/out/host/linux-x86/bin/mkbootimg/internal/

stdlib/runpy.py", line 174, in _run_module_as_main

File "/mnt/sda1/AndroidSources/PixelExperience11P/out/host/linux-x86/bin/mkbootimg/internal/

stdlib/runpy.py", line 72, in _run_code

File "/mnt/sda1/AndroidSources/PixelExperience11P/out/host/linux-x86/bin/mkbootimg/mkbootimg

.py", line 321, in <module>

File "/mnt/sda1/AndroidSources/PixelExperience11P/out/host/linux-x86/bin/mkbootimg/mkbootimg

.py", line 308, in main

File "/mnt/sda1/AndroidSources/PixelExperience11P/out/host/linux-x86/bin/mkbootimg/mkbootimg

.py", line 128, in write_header

struct.error: 'I' format requires 0 <= number <= 4294967295

08:51:11 ninja failed with: exit status 1

It happened when I was trying to build PixelExperience11Plus with a prebuilt kernel. How can I fix it.
[Asus ZenFone 3 Questions & Answers] advanced_gamerBR:
I've received today from a friend the phone.

It was running stock ROM, bootloader was never unlocked and supposedly everything is stock

Apparently all of sudden the phone wouldn't turn on anymore

It gets stuck on ASUS logo and never turns on

All I could do is access fastboot, however I can't make any changes on the system because USB Debugging was never turned on and also, the phone has a password.

Also, recovery mode won't open

Any ideas on what I could do to fix the phone?
[Windows Mobile Development and Hacking General] GSLEON3:
A few weeks ago I started skining the 5.04 Camera to look like 6.08. That was fairly successful, however the main issue, lag time, was of course not affected. I then started trying to hack AF into the 6.08 Camera version & had issues getting it to function as it relies on some different resources that I could not get functioning concurrently.

So, last night I started playing with a new idea. Renaming & resources from one of the two camera versions allowing for both cameras to be installed, having one called to initialization by a long camera keypress.

Anyone familar with widows mobile (Arm) executables & resource hacking willing to help out on this idea & test it?

Is this something people would like to see in a cooked rom? Would the ability to toggle the camera depending on what you need, Auto-Focus or Speed, be appealing?

It really wouldn't add too much weight to the ROM, as both Camera use primarily the same resources/DLL's. Would having a choice of a macro/micro (AF) mode bee something you'd like to see?
[Windows Mobile Development and Hacking General] Laurentius26:
Hi man,

Realy great what you want to do but to be honest I don't like the camera atm :( cause the front camera isn't working with the 6.8 build (correct me if I'm wrong).

I would rather have both camera's supported on my Kaiser to use this build.

Together with the Opal dialer with videocall enabled that would be a awsom job!

Grtz,

Leo :)
[Windows Mobile Development and Hacking General] GSLEON3:
Great Suggestion!

I have not looked into that at all, My last TYTNII is dead, so I am on a Tilt. If you are willing to give it a test since you have both cameras, I will look into implementing that as well.

BTW, I will be moving this into the Development & Hacking thread soon. I just wanted to start it here to see if any Kaiser users had any camera hacking experience or suggestions.
[Windows Mobile Development and Hacking General] Laurentius26:
I would be glad to help you my friend. :):):)

Please let me know when you have something!
[Windows Mobile Development and Hacking General] GSLEON3:
I have been able to specifically locate the function handling the camera AF uysing IDA Pro, I also see that there appears to be some hard coding of FPS information/limits in the camera executable for the 5.04 Kaiser Camera.

This info is not present within the newer (Opal) camera as far as I can tell & may be a reason why it seems to outperform the Kaiser Stock Camera. There is also no information or AF calls within the Opal Camera executable. Hence, without a complete rewrite of the program I cannot simply integrate AF into the newer camera.
[Windows Mobile Development and Hacking General] GSLEON3:
Lost...

Anyone???

I have tried renaming the resources & creating a new registry tree all to no Avail.

I seem to have enough resources available to operate trhe second camera, however I cannot get it to initialize. Anyone have any suggestions?
[Windows Mobile Development and Hacking General] DupinBJK:
Have you found many functions involved in the AF management, in the old version ? I'm a bit busy with the Dialer, but since we're both using IDA Pro, I may take a look to what you've documented so far in the IDA database... I'm not a big expert in camera apps, but who knows... :)

BJK
[Windows Mobile Development and Hacking General] GSLEON3:
There are about 6 or so references. Both cameras use primarily the same resource files, so it appears to me that the AF function is coded into the executable.

I had pretty much given up on the addition of AF to the new 6.8 camera & had decided it would be easier for a novice like me to just add support for a second camera program.

However, that task is also throwing me at the moment. I have built a new cab, with renamed files & some hacks to point to the renamed files, I have also created a moddified registry tree to co-exist with the one for the OEM camera, yet when I select the newly moddified camera it tries to launch, but won't initialize.

Missing something somewhere...
[Windows Mobile Development and Hacking General] DupinBJK:
No external reference to a shared .dll ?

That's why I asked. It seems a single-threaded apartment issue. If it is an external .dll, maybe it could not be designed for multiple concurrency...

BJK
[Windows Mobile Development and Hacking General] GSLEON3:
When I get a moment I will post what I have found, the differences in the executables & the AF refernces & coding.

It may all be moot however, as I take a look at the Raphael camera, which allegedly has AF as well as a newer camera. We shall see.
[Windows Mobile Development and Hacking General] DupinBJK:
Good, thanks !
[Windows Mobile Development and Hacking General] GSLEON3:
Again, :o need to reiterate that arm executables are not my thing, however, I have hacked the Ralph Camera & it uses the same icons & resource (Mostly) as the Kaiser & Opal.

However when I build a new cab just to see if the AF is working already on the new Fuze ROM Camera I get an unsigned error message.

Can one of you ARM pros give me some insight?
[Windows Mobile Development and Hacking General] GSLEON3:
Fuze Camera is new version & definitely has AutoFocus support!

Works with the existing hacked QVGA .mui & icon files, but when trying to create the cab I still get unsigned error.

Anyone???
[Windows Mobile Development and Hacking General] GSLEON3:
Here is the start of an OEM QVGA package. Exe still won't launch.

Anyone want to take a look? Do I need to resign the app, the exe?

It includes all files & images resized & hacked for QVGA including the .mui files. The exe is throwing me badly though.

The OEM can be found here: http://rapidshare.com/files/159104147/HTC_Camera_6_Fuze_OEM_QVGA.rar

However, it seems the sensorSDK references are giving me the issues. Maybe need to find a way to null them out or default landscape.
[Windows Mobile Development and Hacking General] met3ora:
If I'm understanding correctly, you'd like a switch to use the camera version with AF and the camera version without AF. Correct or am I completely missing something here? If I AM understanding correctly, then I would be all for this, as this would really make the camera on the Kaiser at least sort of useful, as opposed to only usable in certain conditions.
[Windows Mobile Development and Hacking General] DupinBJK:
Sorry for being late...

Have you removed the signature before patching the files ? You have to remove it from each signed file you're going to patch, to be able to use it. I can do it for you, if you wish...

BJK
[Windows Mobile Development and Hacking General] GSLEON3:
YES. That was the original intention of this thread.

BJK, I would be eternally gratefull if you'd do that for me, then I can see if I can find a way to null out or hack a SensorSDK.DLL to aways import the landscape value as a return & maybe see if the results are succesful.
[Windows Mobile Development and Hacking General] volcomnator999:
OT: gsleon03...dude im your neighbor lol...i live in Torrance and im up in PV once in a while.

id like to see this project come true
[Windows Mobile Development and Hacking General] secoseco:
Hi

first, sorry that I interrupt this thread and asking about improvement of frame rate for shooting video throw HTC camera, am have Cruise and has low frame rate in video recording and I think that Kaiser has the same issue, am using the famous camera trick " run camera program, hiding the lens, power off devise and waiting for Sec's, then power on again" which rising the frame rate from 4 to 19 frame/sec in video shooting but with darkens pic, did any one analysis this trick and try to get solution for camera low rate problem or found why 6.08 camera is faster than 5.04

finaly i hope that see this project come true
[Windows Mobile Development and Hacking General] w04g005:
I second that. ist there still any development?
[Samsung Galaxy A70 Questions & Answers] qbatico:
Crear rom 12 sin quitar ni cambiar nada, para el A705-MN

Normal como la hace samsung,

Se puede

Translated by GT:

Create rom 12 without removing or changing anything, for the A705-MN

normal as samsung makes it,

It can
[Samsung Galaxy A70 Questions & Answers] Badger50:
@qbatico

As a courtesy I have translated your thread title and first post. Please take a moment to review XDA Rule #4 again for all of your future posts.

Spoiler content hidden.

Thank you for your cooperation, and best of luck to you with your inquiry.

-Regards: Badger50 FSM
[Samsung Galaxy Note 10+ Questions & Answers] ouosamu:
This is my first question here.

I have SM-N975F. A couple of days ago I installed 12 version of Android (Official Star Wars, OSW) and got a root access with the help of Magisk 24.1. All is good, but one thing: if it is just stock firmware, then I have 256 Gb on board as expected. But after rooting I have only 32 Gb!

Can anybody explain me what happened? Is it possible to fix that problem?

View attachment 5533119View attachment 5533121
[Samsung Galaxy Note 10+ Questions & Answers] LinhBT:
I'm also on A12 ( ONEUI 4) and rooted using Magisk 24.1 and everything seems good here. May be you'd like to take a closer look on all the steps which u did to root the device!