yashsingh1/xdaforums huggingface dataset:
[OnePlus 7 Pro Guides, News, & Discussion] MadHatter01:
Yes this is the one thing that sucks. My bet is they saved a few dollars and downgraded it software wise. Qualcomm most likely charged them less.
[OnePlus 7 Pro Guides, News, & Discussion] steelersmb:
I actually just switched from Verizon to Tmobile and got the new McLaren 5G phone and I will concur and say that sometimes 4G speeds are as fast or faster than anything I've seen on 5G. However, I guess there are other benefits to it such as increased range and signal, we'll see. It's still early on though so I'm hoping it gets better. Not sure I made the right decision by switching to TMobile but I guess I could always go back to Verizon if I need to.
[OnePlus 7 Pro Guides, News, & Discussion] docnok63:
I had a lengthy response going and I was just about to finish when I screwed up and closed the wrong tab in my browser. You can follow my posts starting in this thread: https://xdaforums.com/showpost.php?p=81127347&postcount=40

TL; DR version: From my experience, TMo Nationwide 5G is nothing like the commercials say it is or the drive around that Marques Brownlee had. I've had the phone for four days now and haven't been connected to 5G once. I HIGHLY suggest anyone that has bought this phone or is thinking about it to call TMo and ask to be transferred to their networking department. Figure out exactly where the closest 5G towers are to you and see if they're working. I was told twice that the tower closest to me is 100% working and it's not. It's not even doing LTE speeds.
[OnePlus 7 Pro Guides, News, & Discussion] docnok63:
In the meantime, I uploaded a few APKs to APKMirror from the device starting with Basic Daydream on 6th: https://www.apkmirror.com/apk/oneplus-ltd/
[OnePlus 7 Pro Guides, News, & Discussion] steelersmb:
I have been connected to 5G a lot but the speeds aren't much better than 4G and in some cases worse. However, I think the signal strength does improve.
[OnePlus 7 Pro Guides, News, & Discussion] docnok63:
A you can see, I'm from Memphis. How about you?
[OnePlus 7 Pro Guides, News, & Discussion] steelersmb:
I about 30 minutes north of Atlanta. I've been seeing the 5G signal quite a bit actually.
[OnePlus 7 Pro Guides, News, & Discussion] steelersmb:
Okay, so this is odd and may explain why 5G speeds are no better than 4G. According to TMobile, 5G operates on band 71. You can see that here: https://support.t-mobile.com/docs/DOC-4988

However, today driving home, my phone said it was on 5G but I was on band 66 which is only 4GLTE according to TMobile. So either TMobile is lying about 5G or the phone is not right.
[OnePlus 7 Pro Guides, News, & Discussion] JedixJarf:
tmo 5g can operate on band 2/4/71 afaik, band 4 is a subset of 66 (or the other way around? So if you have 66 you have 4 also.)
[OnePlus 7 Pro Guides, News, & Discussion] docnok63:
Is it real 5G (Band 71), though?

Hmmm, your post made me look it up and Band 66 does actually include Band 4. So perhaps I've been judging TMo too harshly. Maybe they're only mostly lying instead of completely lying.

https://www.phonescoop.com/glossary/term.php?gid=570

https://xdaforums.com/showpost.php?p=81183859&postcount=32
[OnePlus 7 Pro Guides, News, & Discussion] MadHatter01:
Could this be going on?

https://www.fiercewireless.com/5g/t-mobile-says-dynamic-spectrum-sharing-will-require-more-spectrum
[OnePlus 7 Pro Guides, News, & Discussion] techlogik:
5G is all smoke and mirrors for a long time. Stop buying into this marketing hype guys. The chip makers are all over the place, the frequencies used are going to be different, and those maps they have on their website are lies for coverage. I just upgraded to a 7 Pro from a 6T. The 7T is hardly an upgrade for a little more money.

I mean, the 7T is slower than a Samsung S10 plus with the regular 855 processor. And that phone is 1yr old almost.

I might be jumping ship come April when Samsung releases the S11, it is going to shame everything else. They are going to have a 6.7" or larger screen like the S10 5G does...seems common now to have 3 sizes, or go larger like the Note size. Just my two cents.

I agree with others, on the OP8, they need to really step it up. Kind of bored with rooting and only use it for fun and a few tweaks. So even with a Samsung, I would be fine with it likely.

The 90hz screen is a great standard everyone will follow. But otherwise, besides being Dev friendly, OP hopefully doesn't turn into HTC, each version is a small and somewhat useless upgrade. OP camera still sucks. But for the money, it is a great value Oneplus devices.
[OnePlus 7 Pro Guides, News, & Discussion] headcreepz:
5g Tacoma,WA
[OnePlus 7 Pro Guides, News, & Discussion] strictlyphat:
How did u pay almost nothing?
[OnePlus 7 Pro Guides, News, & Discussion] techlogik:
What is ridiculous, live in the 3rd largest metropolitan area in the State of FL, 3mil people. TMobiles map only has Miami with 5g coverage over the next year, the two other largest, Tampa, where I am, and rest of the State have zero coverage. 3rd largest State in the Country by population 21 Million people, and this is TMobiles idea of coverage? Whatever, 5G isn't going to be widespread for years and common on phones...marketing hype.
[OnePlus 7 Pro Guides, News, & Discussion] docnok63:
TMo Jump On Demand program. That was the first of 18 payments.

If I was seeing anything like this, I would've kept the phone.

I drove down to Mississippi to my youngest daughter's house and then my son's house yesterday. Here's what I think about TMo's 5G on the go:

1. I still have never seen Band 71 on the McLaren phone. Oddly enough, about four months ago I saw it on my OP7P at my son's house. It wasn't on either phone yesterday. I saw all Band 2 and Band 66.

2. The OP7P's screen was on the whole time running Google Maps and was at 84% battery when I arrived about 90 minutes later. The McLaren's screen was only on to occasionally check what Band I was on and do a speed test. It was at 82% when I arrived. That's excessive battery drain searching for towers.

3. The speeds were 4G and LTE at best. This is all I'm going to see with this iteration in my area. Perhaps if the merger with Sprint goes through and TMo customers start being able to connect to their 5G mid band towers I'll start seeing decent speeds. I don't need another OnePlus phone doing LTE speeds.

4. SIM Unlocking while on TMo payments is still possible. If I was going to keep the phone, I'd send for the bootloader unlock code from OP.

5. Giving my daughter the option to "upgrade" her OP7P to the McLaren, she summarize my who experience with a simple response, "Nah, I'm happy with my phone." I love my rooted, fully customized OP7P with lots of McLaren features (including the boot animation.....GRRRRRR@TMo!!!!) and I'll be returning the phone next week. I'll be keeping my Pixel 3a XL on Google Fi instead of the McLaren and I won't be missing the cool cord and case.

Screen 1 and 2: Speeds along the way and then at my daughter's

Screen 3: SIM permanently unlocked
[OnePlus 7 Pro Guides, News, & Discussion] CrazyKat8091:
Yes, it does support since SD855 but OnePlus cutting their cost I guess. Because, the Samsung support it since S10. I have Asus RT-AX88U with Gigabit internet and I am ready to use next generation of Wifi6 with 5G devices.
[OnePlus 7 Pro Guides, News, & Discussion] Donnie S:
OnePlus 7T Pro McLaren problem

Can anyone please help me??? I am with T-Mobile and recently upgraded to the OnePlus 7T Pro McLaren and my phone will not roam on other towers when I'm not in TMobile service area but I previously had the Samsung Galaxy S8 and where I live the only carrier that has service is us cellular in which my S8 roamed on their towers no problem but fit some reason my OnePlus will not so not sure how to resolve this issue, possibly change the apn settings or do I need to change the settings, any help would be greatly appreciated...
[General Topics] MartinC#1:
C:\>ntrw_494 write C:\radioROM.nb1 L
NTRW v2.00
Could not open C:\radioROM.nb1 -- The system cannot find the file specified.

The file is there yet it claims it is not...
[Samsung Galaxy Tab A series Guides, News, & Discus] DdDnt:
Hi,

Please help, my tablet SM-T515 got stuck at: teamwin Recovery Project 3.3.1-1 ...blue with black/gray screen, at boot. I can't do anything, it keeps on looping to this screen. If I try to do a Power+VolumeDown it resets the tablet but I can't do anything else, nor entering in Download mode or shut it down. I have no idea how to fix it. Can anyone give me some hints, please ?! PS: I wanted to root it...I might have downloaded on the tablet with ODIN some weird TWRP (I didn't found this post before starting the process from some weird site ...:( ).

Please, help me,

D
[Samsung Galaxy Tab A series Guides, News, & Discus] MossyTC:
[MENTION=10251313]DdDnt[/MENTION] The difficulty in rebooting into Download mode is timing. After triggering a reboot by holding Power+VolumeDown for 7 seconds you need to immediately switch to holding Vol Up + Vol Down then connect the cable.

Alternatively you can wait for the battery to run out, then you can press and hold volume buttons and connect. Should get you into Download mode.

The next steps are

Flash stock firmware via Odin

Reboot into system and turn on USB debugging again in Developer options, verify that OEM unlock is still set

Flash TWRP or Custom ROM via Odin
[Samsung Galaxy Tab A series Guides, News, & Discus] fpozar:
Hey, first of all thanks for the nice guide. I followed it to flash Nexus ROM for my T515 but I messed up the tablet and ended up in the emergency recovery mode. No biggie though, I have flashed back to original stock ROM but I can't seem to find OEM unlock option now in my developer settings (the tablet is still unlocked though, I have to use my power key while turning on to skip the warning screen)

So basically, now I can't figure out why I can't flash the nexus rom but was able to flash official firmware and why I don't have OEM unlock option in my developer settings.

Also, I made a clean install of Windows 10, downloaded the good drivers and used my best type C cord and plugged it directly into the motherboard and not into the front I/O panel, and still no luck with the nexus ROM.

P.S. I'm tagging [MENTION=903232]Magendanz[/MENTION], just in case you find it interesting how odin refuses to flash your Nexus rom. If you want to, I could test the nexus rom on the latest T515 firmware, perhaps the fw refuses to go below the current version I'm on?

P.P.S : added Odin output

<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1303)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 3048 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> param.bin
<ID:0/003> product.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Download mode screen spits out Only official released binaries are allowed to be flashed so I guess it is a matter of bootloader unlocking after all?
[Samsung Galaxy Tab A series Guides, News, & Discus] MossyTC:
[deleted]
[Samsung Galaxy Tab A series Guides, News, & Discus] MossyTC:
[MENTION=7395801]fpozar[/MENTION] There are two problems that I know of that can cause a FAIL on the product.img line in Odin -

USB debugging not turned on

Incomplete boot loader unlock

Looks like option 2.

As Magendanz has said elsewhere -

Update: More from Magendanz, on missing OEM unlock option:

So connect to wifi before doing the Developer options thing, then try the bootloader thing.
[Samsung Galaxy Tab A series Guides, News, & Discus] fpozar:
Yes, I have done the light blue screen long press step.

Now I've held vol buttons while starting the tablet and chose the short click step (the long click step only leads me to locking bootloader again) and entered a bit different looking download mode (the same one you get by using recovery to enter bootloader, but with a bit more colorful text on the sides), but to no avail, the flashing didn't go through and only lead me to emergency recovery. And again, flashing stock worked.

Secondly, OEM trick worked for me, it appeared when I connected to my home network and made it that oem unlock was greyed out and said "oem unlocked".

Tommorrow I'll try to lock the bootloader and unlock it again. It's really weird though because the blue screen part was done correctly it seems (because long pressing leads me to locking).

Bootloader screenshot when entered by volume + and - combination
[Samsung Galaxy Tab A series Guides, News, & Discus] Orite:
I'm a bit confused on what I've been doing wrong and where to proceed from here. These are the steps I've done on my most recent try:

1) Downloaded:

- Samsung Smart Switch

- TWRP 3.3.1.5 .tar.md5

- Magisk (Latest Magisk Manager)

- Odin

- Firmware T510 (XAR-T510XXU1ASEF-20190605151710.zip)

- Multi-disabler

2) Followed Unlock Bootloader from mingkee

3) Installed TWRP recovery via Odin

4) Rebooted back into stock ROM

5) Installed Magisk.apk

6) Using Magisk Manager > Selected AP_T510XXU1ASEF_CL15874928_QB23938566_REV02_user_low_ship_meta_OS9.tar.md5

7) That gave me magisk_patched.tar which I moved over to my desktop

8) Boot back into download mode

9) Flash the magisk_patched under AP, TWRP under BL, and HOME_CSC under CSC

10) Then Odin said it failed

Honestly I was pretty confused by the steps going from guide to guide so I'm not sure where I went wrong.

Also I'm not sure where I'm suppose to be flashing multi-disabler. The guide just said don't forget to install it but I'm not sure at which step I should be installing it via TWRP.

Any help would be appreciated.

Edit:

I tried again going with just steps from [GUIDE]Comprehensive T510 root guide.

I unlocked bootloader > patched the AP file I downloaded > Tried flashing the AP file only using Odin and it gave me an error:

"Only official released binaries are allowed to be flashed"
[Samsung Galaxy Tab A series Guides, News, & Discus] MossyTC:
[MENTION=2954226]Orite[/MENTION] I'm sorry that I haven't been clearer, but I did say to read the relevant guides and read my thoughts below.

In the OP I said

Full details in the Rooting section in the OP.

You should have been following the TWRP Recovery guide for installing TWRP which clearly states at what point to install Multi-disabler.

If you can boot into TWRP you can flash the Multi-disabler zip file. Tap Install then select the zip file. That should fix the problem of not being able to flash via Odin, though you don't need Odin to install Magisk.
[Samsung Galaxy Tab A series Guides, News, & Discus] fpozar:
Update : So today I've reunlocked bootloader again and still got stuck at product.img step. Again, this is all on fresh windows and Odin works on original firmware.

This time, the error message displayed on my tablet is :

SYSTEM REV. CHECK FAIL. DEVICE:2 BINARY:1 (PRODUCT)

I can only assume this is some anti rollback feature similar to what happens on LG devices when you try to flash software older than what you're currently at.

I guess now we wait for dev's confirmation and if anyone else has something smart to say please feel free to join the discussion. I would try and download older official firmware and try to flash nexus while on something older, but my network connection is kinda unstable and it takes hours to download without a paid account.

Just to avoid questions, my method of unlocking followed exactly the link in the OP and method of flashing was following the mini guide on Nexus rom's OP.

EDIT : For all the T515 users, it seems odin isn't allowed (by some security features) to downgrade bootloader, and since Nexus ROM is based on May update for T515, anyone on updates newer than May can't flash the ROM. I found the answer on Galaxy s9 forums so that might be untrue for our device, but I didn't see many of us T515 users talking about custom roms so that might be it, and the error code makes sense.

Thanks again [MENTION=5467906]MossyTC[/MENTION] for trying to help
[Samsung Galaxy Tab A series Guides, News, & Discus] MossyTC:
[MENTION=7395801]fpozar[/MENTION]

Magendanz doesn't explicitly say so in his OPs, but in some of his posts he does suggest matching the kernel versions.

Anyway it looks like you're stuck with stock until there's a newer t515 custom ROM.
[Samsung Galaxy Tab A series Guides, News, & Discus] Orite:
Thank you. I was finally able to figure it out with your response.
[Samsung Galaxy Tab A series Guides, News, & Discus] trashbag1:
Hi, I have seem to messed up my process somehow, this tutorial seems kind of out of place.

When i try moving the multidisabler to my phone, it looks like all my folders and files are encrypted inside twrp and from the mounted drive on my pc.

I tried installing multidisabler using an OTG which worked on twrps side, i then rebooted and launched into OEM. after restarting from OEM android, i now receive a message when trying to do anything involving turning on my tablet "Only Official Release Binary Aloud" I cant do anything with it now. It just Shows that msg and the samsung logo, and then goes away, never booting, never entering recovery.

I tried to google this and it came up with something about knox, which i know nothing about. I really hope i didn't just brick my device.
[Samsung Galaxy Tab A series Guides, News, & Discus] tomdot:
Does unlocking Bootloader on the T510 change Widevine from L1 to L3? This is my only hestitation to bootloader unlock and root
[Samsung Galaxy Tab A series Guides, News, & Discus] MossyTC:
This isn't really a tutorial, more like additional information to help you follow the guides linked in the OP.

You're internal data is encrypted by default by Android, but the version of TWRP we're using can't handle encryption. We get around that by disabling encryption by wiping the data partition as one of the first things we do when TWRP starts up, as per the instructions in Magendanz's threads. Ideally you should have the Multi-disabler zip on your sdcard before flashing TWRP. I have amended the instructions above to suggest as much.

Is your device an SM-T515? You may be having the same problem as [MENTION=7395801]fpozar[/MENTION].

Can you get into Download mode again?
[Samsung Galaxy Tab A series Guides, News, & Discus] MossyTC:
I don't know what will affect Widevine.

I think the bootloader can be relocked, but I can't check right now.
[Samsung Galaxy Tab A series Guides, News, & Discus] fpozar:
The bootloader *can* be locked, I know as I've done it yesterday. In fact, it can be relocked and renlocked as many times as you want. To lock it follow the guide to unlocking but when you enter the light blue menu, holding vol up will lead you to locking and reseting your tab
[Samsung Galaxy Tab A series Guides, News, & Discus] elliwigy:
another guide? lol pretty soon will b only guide threads in here lol
[Samsung Galaxy Tab A series Guides, News, & Discus] lewmur:
"And resetting". That's the problem. You can't relock without resetting and having to start over from scratch.
[Samsung Galaxy Tab A series Guides, News, & Discus] MossyTC:
Yeah, well there are about twelve Galaxy Series A models and the geniuses at xda put them all in one bucket, so lots of Guides in the Guides, News & Discussion section, lots of ROMs in ROMs, Kernels & Recoveries, etc.
[Samsung Galaxy Tab A series Guides, News, & Discus] el7145:
Can someone explain to me why i cant uninstall any system apps even after flashing magisk?

originally i screwed up the flashing twrp steps and inadvertently wiped data before flashing multi-disabler, i thought this mightve triggered system encryption, so i downloaded the stock firmware and flashed back to stock, then format data in stock recovery, then flashed twrp, flashed multi-disabler, formatted data...and i figured with these correct steps id be good

EDIT: it seems i was able to uninstall some system apps using a different file explorer and making sure to mount the system as R/W...oddly titanium backup wasnt able to uninstall any system apps, im gonna have to look into it
[Samsung Galaxy Tab A series Guides, News, & Discus] Lucaraid:
Thanks for your comment! I also wiped data before flashing multi-disabler. Was able to get it to work thanks to your comment.
[Samsung Galaxy Tab A series Guides, News, & Discus] redhonker:
Hi,

I have followed the instruction and the T510 is now rooted with Magisk.

However, the storage appears to be messed up. My Files app can open but Internal storage is completely empty (17.56GB / 128GB). When I tried to create a folder, it will say

"You don't have enough space on internal storage. Delete some files and try again"

I have done the step in TWRP to wipe / factory reset. Then installed Magisk after reboot. What's missing here?

Thanks
[Samsung Galaxy Tab A series Guides, News, & Discus] lewmur:
I blame that on Samsung for lumping all of these totally different tablets under the "Tab A" banner. Not up to XDA to sort out Samsung's mess.
[Samsung Galaxy Tab A series Guides, News, & Discus] thex2:
I'm having, what I believe to be, similar issues. I can't update Google or Google Chrome from the Playstore. In addition, it won't let me install Mozilla Firefox. It did allow me to update all other apps. I'm guessing the other apps were smaller and downloaded to cache instead of storage? After reading your post, I tried going into Files and creating a folder. Access was denied with the message "Failed to create folder". Also, if I open my camera app, it says "Insert an SD card before using the camera" and won't allow me to take any photos.

Bouncing back and forth between all of the guides was a bit difficult for me to follow. There are three places I know I failed, but not sure if it's what's causing my issues:

1. "WARNING - take note of the kernel version of the custom ROM or TWRP you intend to use, e.g. T510XXU2ASI4. Newer bootloader releases will sometimes prevent downgrading, so if you flash a firmware/ROM/TWRP with a later kernel version you may not be able to flash your desired custom ROM without problems, or flashing an older version than you are currently running may trigger anti-rollback mechanisms. Magendanz suggests matching the version exactly." -I wasn't quite sure how to match the bootloader release to the ROM/TWRP T510XXU2ASI4. I used the bootloader that unlocked by default through Samsung Smart Switch.

2. When originally flashing TWRP, I did not deselect "Auto-Reboot" from Odin. This caused another user issues where they had to let their tablet's battery fully die so it could turn off and then restart into the Download screen to reflash TWRP. I luckily didn't run into this issue, but figured out that I forgot to deselect "Auto-Reboot" after I had flashed.

3. "For later versions of TWRP you should wipe the encrypted data partition before flashing TWRP so that TWRP can access the data partition." I didn't know how to wipe the encrypted data partition before flashing TWRP... do I flash TWRP with Odin and then go into TWRP to wipe data and then flash TWRP from within TWRP?

Those are the only places I can see that I went wrong. I currently have an unlocked bootloader, Nexus Custom ROM installed and root through Magisk.

EDIT: Looks like my data is still encrypted. I'm going to reflash. Not sure if that's your issue too or not, but figured I'd share in case it is: https://xdaforums.com/showpost.php?p=80896625&postcount=251

EDIT 2: This fixed my problem: https://xdaforums.com/showpost.php?p=80913879&postcount=254
[Samsung Galaxy Tab A series Guides, News, & Discus] redhonker:
I figured it out that I need to choose format data. There is no button/option with the word "wipe". It would be helpful for the OP to update the text so newbie can understand it.
[Samsung Galaxy Tab A series Guides, News, & Discus] lewmur:
What version of TWRP are you using that doesn't have a "Wipe" button? I've used many of them over the years and have never seen one that didn't.:confused: