yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] alecxs:
doubt you will find proper factory loader for Snapdragon 480 however worth a try there are some nokia loaders in repo, so you could try generic unlocking

GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)

Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :) - bkerler/edl

github.com
[OnePlus 10 Pro] Jordanrnd:
Hello,

Anyone try a gsi rom on the OP10 Pro ?
[OnePlus 10 Pro] Bliszcur:
where did you find it?
[OnePlus 10 Pro] Jordanrnd:
I check with treble app and choose all rom available on gsi github
[OnePlus 10 Pro] Twiggy000b:
I have yet to try it but the phh gsi aosp one has fixes for booting snapdragon 8 gen 1.
[OnePlus 10 Pro] dlads:
Search the A/B ROMs on xda... There's a pixel experience one that looks promising
[OnePlus 10 Pro] AndyYan:
Way back...

https://xdaforums.com/t/gsis-on-op10pro.4395953/

Not a good experience though, I can't quite get the overlay and 2K resolution to work consistently, let alone common bugs like VoLTE and FP.
[OnePlus 10 Pro] dlads:
Yea I think this is the problem with treble, the concept was nice but each device needs it's own support, having one image for every device is a problem in itself
[OnePlus 10 Pro] AndyYan:
This being a OnePlus "x Pro" flagship, I'm sure it'll get device-specific ROMs shortly. Me working with PHH to boot on it is more to clear the way for other more obscure SM8450 devices.
[OnePlus 10 Pro] dlads:
If he'll work with you on the specifics then great.... Problem for me with treble is what I've said above.. If you ask a question in that forum it's swallowed almost immediately, so for an end user it's not exactly intuitive or even helpful in a traditional ROM owner/flasher sense of the word..

Information for specific devices simply doesn't exist. So it becomes a minefield for the end user.

Could be done a lot better, that's why so many people just don't bother with them.
[OnePlus 10 Pro] AndyYan:
I myself am also the type who doesn't care about all the specifics - even on my daily driver with GSI, I leave VoLTE and some other problems unfixed. Also, I don't actually own that OP10Pro, I just had it briefly.

An actual owner/user here might care, but before he figures out (or finds out he can't fix everything), I bet a device-specific ROM would've already come out. A rare case/device where running a GSI isn't worth the trouble, if you ask me.
[OnePlus 10 Pro] dlads:
Yea i agree, it's just a shame as the content is actually there, I could live without certain things myself. Volte I'm not overly fond of tbh..

I just find the whole thing more troublesome to just get info on treble ROMs.

I had a P20 Pro prior to the 8 pro and GSI ROMs would have been a god send so I'm sure there are a tonne of people out there who could use them..

I'd hope that it would be clearer but it's been so long now that I doubt that'll ever happen..

It's good you're working with pph. I hope that info you gather will be useful to others
[OnePlus 10 Pro] bhammler:
I've tried to flash the latest phhusson

AOSP 12.1 v413 ​

It's booting up, but you can't call someone (connection is dead). IMS Network is not supported. And no fingerprint and no auto brighness. Not usable right now
[OnePlus 10 Pro] dlads:
I can't comment mate. I think you're very brave. You should make a thread based on your experience..

Document the crap out of it.

Share the hell of it.

This is needed for every OnePlus 10 pro owner, do it
[OnePlus 10 Pro] bhammler:
it's very easy: don't use GSI right now ;-)
[OnePlus 10 Pro] Twiggy000b:
Aww dang. I really want some customization here. Having to restart everyday cause slow downs suck
[General Questions and Answers] AndenAnderson:
Hi

I'm searching for a replacement for an expensive paid system where customers/people when they phone my number are welcomed with a voice-message, and then after I get the call.

In this system I can also set opening hours. When closed the system simply plays a "we're closed now" if customers call outside of the operating hours.

Therefore I'm searching for an app which can do something like this - does it exist? I dont know which term they could be under.

Regards
[Wing, P4350 Herald Upgrading] zeheres:
Hey there,

since I'm new to the community I hope I'm not doing it wrong :)

I will receive my new Herald within the next days and now I'm seeking for all the stuff I will need then.

1. Hard-Spl. I don't get it. What is it? Is it some kind of firmware update or whatever? The ROM's thread says that I would need SPL 4 or later to successfully finish the Update but I can't find that SPL application in version 4+ :/

2. http://xdaforums.com/showthread.php?t=437385 - http://www.evolvers.net/Herald_Roms/Version 7.7/ => I'd like to use that ROM. But I'm not too sure whether to use Manilla2D or Omnia.

3. What if I needed to send my device back for warranty reasons. Is there some way to flash back the standard Win Mobile 5.0?

I hope I will get your attention!

Regards,

Chris
[Wing, P4350 Herald Upgrading] zeheres:
Hey,

thanks for all the information. Was very helpful. I decided to you the ROM from that link. Should work, shouldn't it?

The only thing I don't get is how to get to SPL4+ :/ I heared of different methods of SPLing. Like Hard SPL and USPL. Can you bring light into that cave?

Cheers.
[Wing, P4350 Herald Upgrading] itbmd:
Hey there,

Your link goes to the Open Touch thread. The link I'm referring to, is this one:

http://rapidshare.de/files/38148213/HardSpl_WM6.rar.html

As I said, I was NOT able to flash directly from stock to OTP. I tried many methods, and Canonyang was the only one that worked for me. After I successfully flashed to CY, then I was able to flash to OTP without issue. But in theory yes, any Herald rom's should work fine.

In regards to IPL/SPL, my wing is from September 2007, and I had IPL/SPL both above 4. I had NO WAY to verify this before flashing. When I initiated the flash for CY, and the wing rebooted, it was THEN I saw my IPL/SPL versions. I'm sure yours will be at least v4.

Actually as I write this to you, I remember a critical step I forgot to tell you. You need to Application Unlock your device as well. This is probably what I was missing in my failed attempts. After I did that, then the CY flash worked. I got that information, from this link:

http://xdaforums.com/showthread.php?t=356295

So I would suggest following the steps there first, then trying the link earlier to flash to CY, then flash to anything else. This is the procedure that worked for me. Good luck!
[Wing, P4350 Herald Upgrading] zeheres:
Hey there and thanks again for that bunch of information :)

What does that mean then? I do not have to HardSPL my phone? But still, would you mind telling my step by step (And I really mean step by step^^) how to HardSPL a device? I really do not want to brick my phone directly at the beginning.

Oh and what should I rather be using, SoftSPL or HardSPL?

Cheers.
[Wing, P4350 Herald Upgrading] itbmd:
Hey there,

Sorry but I just flashed my device less than a week ago as I mentioned. I don't have many of the answers you ask, because I'm asking them myself. I don't know the diff between Hard vs. Soft SPL.

The file I linked you to earlier, is a hardspl, as denoted by its filename "HardSpl_WM6". It hardspl flashes to the canonyang rom. It was then I saw the IPL/SPL versions, and then was able to flash to other roms.

FYI, I was concerned about bricking my device as well. But during the roughly 5 hours I was trying to flash it correctly, every time the flash failed, it did NOT brick. It just errored on the pc, and the Wing itself just restarted and went back to the stock TMobile rom. It never actually bricked. Make sure you do the application unlock though; I think that's a step that people may not do and could cause it to brick. Good luck.
[Samsung Galaxy A51 5G Questions & Answers] BloodyFruitDestroyer:
I want to root my phone with Magisk, so, following the instructions here:

I enabled OEM unlocking on my SM-A516B (European, not US or Canada and it's running the latest offical software (Android 12)) and rebooted to download mode via adb (goes to a "fastboot" mode when I select bootloader mode from recovery mode), but I don't see any option to unlock the bootloader. The English text on the screen says only:

Downloading...
Do not turn off target
Do not disconnect the USB cable during the software update!
Volume Down Key + Side key for more than 7 secs
:Cancel (restart phone)

There is also some Korean text, a DID code and a barcode. Holding volume up does nothing.

I'd seriously appreciate any ideas on how to proceed!
[Samsung Galaxy A51 5G Questions & Answers] BloodyFruitDestroyer:
So I found the solution for myself: I don't want to go to the download mode, but instead hold valume + and - and plug in a USB cable.
[General Questions and Answers] samualrosenberg@protonmai:
Hi Guys,

If this is in the wrong place forgive me. I am looking for a stock from for the above phone but can only find XT2173-1/2 and not 3. Is anyone able to point me in the right direction?

Thank you
[General Questions and Answers] art99:
Have a look at this site:

https://mirrors.lolinet.com/firmware/moto/cofud/official/

You have to find out which version you need with the following command: fastboot getvar all
[Samsung Galaxy S21+] Frostyb:
Hi XDA, first time poster and I could not find a similar thread with the answers I was looking for, if that thread exists I apologize!

So basically I started a job in a retail phone shop a few months back. We have a drawer in store that has a bunch of old demo units in there that, once they have been removed from display, just sit there unused. There is phones in there from almost 10 years ago. They are never given back or requested back, nor are they logged in any way.

Well I noticed there was an almost perfect condition S21+ in there so I asked my manager if we could use it as a sales incentive and he replied saying the phones are useless because of the software on them. I said I was pretty sure you could remove the retail software and use it as a normal phone and he said if I can do that and get it working, I can take the phone for myself.

Well, I took it home and did some digging / experimenting. The phone has a proper IMEI already, you can put a SIM into the phone and it registers to the network. The problem is, the phone has security restrictions on data sharing and it does not have the playstore on it and there is no factory data reset option in the settings, nor in recovery mode.

I have tried flashing a stock firmware on using Odin which I thought worked, however when the phone restarts and you go through set up, Samsung Knox pops up and installs settings which forces the phone to set up in retail mode again with the same restrictions as previous (no play store, factory reset etc).

Any idea how to get around this issue? I would have thought flashing stock software would be the obvious work around but something on the phone forces it to install on retail mode every time.

Any advice on this is much appreciated.
[Samsung Galaxy S21+] BloodyFruitDestroyer:
Have you tried following the steps in a video such as this?

DO THIS COMPLETELY AT YOUR OWN RISK! I AM NOT RESPONSIBLE IF ANYTHING GOES WRONG, INCLUDING BUT NOT LIMITED TO BRICKING YOUR DEVICE, GETTING A VIRUS OR STARTING A LITERAL WAR.

Everything i was able find on the subject was kind of sketchy-looking (probably because doing this without permission would probably be illegal) so I included a warning.
[Samsung Galaxy S21+] Frostyb:
Thanks for the reply!

So I also came across this same video on the subject last night, it seems to be a workaround for bypassing Knox but I couldnt find any further info on what kind of state that leaves the phone in after, if it can still get official updates and such or if it triggered to eFuse that causes you to lose access to Samsung Pay and other official apps.

I'm aware this is at my own risk, the phone will sit in a drawer if I cant figure it out any way so no harm no foul as far as I can see. I've thought about rooting the device (I know this will trigger the eFuse) but I cant find any info on if that would get around the specific issue I'm having of Knox forcing the phone to install in retail settings or not so do not want to go down that road just yet.
[Samsung Galaxy S21+] BloodyFruitDestroyer:
I'd say that the Knox workaround would probably (do not quote me on that) leave you with un-tripped Knox (=e-fuse intact) if it even still is. Even if Knox would be tripped, you would still most likely be able to get software updates. But because you said that you have already used Odin successfully on the device, that would lead me to believe that OEM unlocking might already be on in which case there probably isn't any more to lose by rooting the device. On a rooted device there are instructions o WikiHow on how to remove the Knox , but I haven't personally tested them. If I were you, I'd check with a Knox warranty checker app or through recovery mode, etc

whether the e-fuse is already triggered before continuing with anything.

And if I confused you, feel free to ask anything!
[Samsung Galaxy S21+] BloodyFruitDestroyer:
With the root approach you would also have to worry about passing Safety Net, but that'll only be relevant if you decide to go with that path.
[Samsung Galaxy S21+] Frostyb:
Interesting, I may give the workaround a shot when I get home later then.

So I have used Odin but it was with official firmware obtained through Frija and, according to reading, that does NOT trip the eFuse. I did turn on OHD in dev options but from what I can tell, the fuse is only tripped when you load an unofficial image onto the device which I havent done yet. I can check when I get home by booting into recovery mode and checking the warranty line AFAIK it will say either 1 or 0 indicating if it's been tripped or not.

So my issue with rooting is I dont know if I root, will the phone still install in the retail setup that it does currently. I know I can run apps or code to remove Knox once rooted, but I dont know if then just reinstall firmware and it will be back to default like I want, or if I'll then need to figure out how to get the playstore loaded, if the security issues persist etc. Also as far as I can tell to root, I need to install Magisk on the device first to alter one of the image files, then move that file back to the PC to flash with Odin, and I'm not sure I can do that with the retail settings enabled.
[Samsung Galaxy S21+] BloodyFruitDestroyer:
I am interested in how this develops. Please keep me updated with the warranty byte status and whether the workaround is successful!
[Samsung Galaxy S21+] Frostyb:
So quick update on this: none of the workaround videos on youtube seem to be capable of doing anything. They all rely on being able to connect to Wifi then get around the device before Knox settings apply, however on my build as SOON as you connect to wifi, it immediately starts applying knox settings and cannot be skipped.

I am wondering if this is because the version of software I flashed on using Odin was the most recent firmware, being android 12, and most of these workarounds are for android 11? Is it safe to locate the original firmware for the S21+ somewhere and flash that on to the device instead do you think?

Also the eFuse is still currently in tact.
[Samsung Galaxy S21+] BloodyFruitDestroyer:
You could flash an older Android version, but if and only if it has the same bootloader version as the current one, otherwise it won't work and might even brick your device. I am unsure though if the downgrade would help but if the bootloader versions match, you can try!

On SamMobile.com you can see older versions of firmware. Just check the bootloader version before flashing!
[Samsung Galaxy S21+] Frostyb:
So this may seem like a dumb question but how do I check to make sure the bootloader version matches?
[Samsung Galaxy S21+] BloodyFruitDestroyer:
It's most likely as simple as comparing the bootloader filenames between the Odin flashable files for the old and new software. I could verify whether that's the case if you send the filenames for both bootloader files here. (The file that goes into the BL slot in Odin)
[Samsung Galaxy S21+] Frostyb:
So the first image is of the current firmware that successfully flashed to my device via Odin.

The second is firmware from August 2021 that is on a build of Android 11. You can also see by the file modification dates.
[Samsung Galaxy S21+] BloodyFruitDestroyer:
What were your exact model and region again? Probably won't matter, please wait a minute
[Samsung Galaxy S21+] Frostyb:
SM-G996B

Region is Ireland (CSC is MET)
[Samsung Galaxy S21+] BloodyFruitDestroyer:
Yeah, it seems like the current bootloader is version 4 while the Android 11 one is version 3 so these versions seem, unfortunately, incompatible.
[Samsung Galaxy S21+] razercortex:
Hi there, I can help you out! I have some experience with Samsung.

So first off, I take it this is an Exynos model? Snapdragons require the use of a paid service to get an unlock.

It seems you've flashed stock firmware before but it didn't work out due to Knox. Did you flash all the files including the CSC (wipe all data) file? Also, you could try flashing TWRP and that would trip Knox, at which point Knox is disabled due to detecting system modifications or it will try to rollback your modifications.
[Samsung Galaxy S21+] BloodyFruitDestroyer:
So the only thing I personally can think of to get rid of the problem is going the TWRP route, but this will trip the Knox warranty byte to 0x1, so think about it. There might be someone more experienced than me that might be able to help without tripping Knox, but this is right now the only thing I can personally suggest to fix the problem.

Edit: It seems like someone more experienced appeared while I was writing this! Sweet!
[Samsung Galaxy S21+] razercortex:
Are you able to enable developer options? If so, you might be able to use ADB commands to disable the Retail Mode app. I doubt they're enabled though.
[Samsung Galaxy S21+] Frostyb:
Dammit, so it seems I'm stuck on Android 12 and there is no way to get back to a previous version then I take it?
[Samsung Galaxy S21+] BloodyFruitDestroyer:
With official firmware, I'd be pretty certain that you can't. By the way, please look at the latest messages as there is someone else with fresh ideas here, too.
[Samsung Galaxy S21+] Frostyb:
I'm not sure if its Exynos or Snapdragon.

Yes I flashed the official firmware with CSC file, I have not tried flashing with TWRP yet (unsure what that is to be honest).

In regards to your developer options question, yes I can enable dev options on the phone, but the issue isnt removing the retail mode application, I actually k ow the code to remove that. The main issue is when the device is flashed and you go through the setup stage, as soon as you connect to Wifi (which you cannot skip) Knox immediately kicks in and starts applying settings, and the phone sets up in retail mode without playstore and restrictions on changing settings or privacy sharing.

The crossroads I'm at is somehow bypassing Knox during set up, so that the phone sets up like a regular stock phone. All the work around videos have ways of enabling ADB then running CMD through the PC and removing Knox before it can do anything but I can't do that because in the videos they can connect to wifi and go back a step before Knox kicks in, on my device Knox kicks in immediately after connecting to wifi and you cant stop it.
[Samsung Galaxy S21+] razercortex:
TWRP is TeamWin Recovery Project (it's a custom recovery). My hypothesis is that Knox will be disabled if it detects custom modifications to the phone, but that's yet to be tested. You can flash it here https://xdaforums.com/t/recovery-unofficial-twrp-for-galaxy-s21-exynos.4241935/, just follow the guide and it should work
[Samsung Galaxy S21+] BloodyFruitDestroyer:
Even if it doesn't work, there'll be a chance to root the device using TWRP and with root privileges you can likely remove Knox deployment. Do note that installing TWRP does trip the Knox warranty bit to 0x1 = warranty invalid, tampered with. But that is kind of the goal here, as that might alone disable the deployment.
[Samsung Galaxy S21+] Frostyb:
Hmmm Interesting.

Sorry if I seem ignorant but is there any downsides to using this? I know triggering Knox means you lose certain functions of the phone but if I've read up correctly you can get the majority of the functionality back? The biggest one for me would be still being able to use banking apps.

Thanks for the help on this by the way!
[Samsung Galaxy S21+] razercortex:
Most banking apps check Safetynet, not Knox, so as long as Safteynet passes, you should be able to use most banking apps. Even if you couldn't, just use the mobile site ;)
[Samsung Galaxy S21+] razercortex:
Knox is used in Secure Folder, Samsung Pay, Samsung Health, some MDM deployments, Samsung Pass, and that's pretty much all I could think of. If you don't need access to any of these apps (or any others that need Knox untripped), you should be fine. Worst that could happen is you get a new phone, which isn't a problem considering that this phone is unusable in the first place.
[Samsung Galaxy S21+] razercortex:
I would just recommend you keep your current phone or get a new one for everyday use and I would just keep this one as a spare or development phone for you to fiddle with.
[Samsung Galaxy S21+] Frostyb:
See the goal is to make this my new phone if possible haha!

Okay so because I'm a bit ignorant, if I'm understanding that guide correct I need to put the TWRP file in the AP slot in Odin, the other file in USERDATA and leave the other slots blank? And do I do this from a stock firmware yes?

The other part I dont understand is the step "flash magisk apk"...
[Samsung Galaxy S21+] razercortex:
I mean, it's understandable that you want to use this as your new phone, but I'm not sure you'd want to do that...

Regardless, yes, the TWRP file should go in the AP slot, the vbmeta_disabler file in USERDATA. Then, you can reboot to recovery by using the button press.
[Samsung Galaxy S21+] Frostyb:
Okay so I have followed all the steps now I just need to flash magisk apk in TWRP but I'm not sure what that means exactly?
[Samsung Galaxy S21+] razercortex:
It means you need to download the magisk.apk to your phone, rename magisk.apk to magisk.zip, and flash it.
[Samsung Galaxy S21+] Frostyb:
Okay so I have successfully flashed the device with TWRP and installed Magisk and have root access. However Samsung Knox still kicked in during set up phase and booted the phone in to retail mode like it did previously. I have tried removing Knox via TWRP by deleting the folder for Knox but it didn't seem to work.
[Samsung Galaxy S21+] razercortex:
Check /system in TWRP
[Samsung Galaxy S21+] Frostyb:
I did that, Knox was totally removed from it. I even downloaded Titanium Backup to remove anything related to Knox.

I decided to do the process from the start and take some pictures. This shows me doing a full factory data wipe from inside TWRP -> Deleting the Knox folder inside TWRP (before setting up device) -> device saying its protected by Knox still somehow despite it supposed to have been deleted -> Knox installing its services anyway.

There seems to be something somewhere that is triggering a full redeployment and installation of Knox from cloud servers that I need to locate and get rid of but if it's not in the Knox folder I have no idea where to look.
[Samsung Galaxy S21+] razercortex:
Well, there's not much I can do to help you further since I don't have the device, sorry!
[Samsung Galaxy S21+] BloodyFruitDestroyer:
You've probably already tried this, but can you disable retail mode from within the app?

Also try to remove the app through TWRP.