yashsingh1/xdaforums huggingface dataset:
[OnePlus 9 Pro] EtherealRemnant:
As I have said, it does change on my 9. I can confirm with 100% certainty that I was able to change my target back to O2 after flashing the 9 Pro ROM to my 9 and having it change to IN for the target. My multi-target 11.2.10.10 MSM flipped that target back. The TMO target behaves in strange ways. Like for example if you have the TMO target in the settings.xml, you cannot use multi-target, the drop-down box disappears to choose the target. This is only a problem with TMO - EU, O2, and IN all work fine (in fact I have been meaning to make an all in one MSM that can flash any of the three, I just have been busy with my fiancé so I haven't gotten to it). Keep in mind that I have had struggles even making MSMs that can flash TMO devices despite these MSMs working on the other variants. Something is just different with them.
[OnePlus 9 Pro] TheGhost1951:
Thanks for the input.....may you and your fiance's be blessed by the Lord...
[OnePlus 10 Pro] Xpid3r:
Stuck in Bootloop

Urgently Needed Vbmeta.img, Vbmeta_System.img, Vbmeta_vendor.img of Stock OOS.12.A16 Firmware
[OnePlus 10 Pro] dlads:
Extract it from a firmware..you can grab these online...extract payload.bin and use Fastboot enhance to extract the images.
[OnePlus 10 Pro] Xpid3r:
payload.bin is not working for A.16.. it doesn't support incremental
[OnePlus 10 Pro] dlads:
I have the full zip..

You've not stated what model you have.

If it's the EU device then yes it is widely available..
[OnePlus 10 Pro] yot2703:
OOS12 A16

NE2213

Enjoy :)
[OnePlus 10 Pro] Xpid3r:
thanks but i needed it for 2215
[OnePlus 10 Pro] Tilde88:
there is a full update of A.16? is it available for NE2215? hook me up
[OnePlus 10 Pro] the_rooter:
The 2215 isn't the eu version like he stated he has, but I have the 2215 and à16
[OnePlus 10 Pro] centifanto:
2215 is NA, and yes I have A16 as well. OxygenUpdater is still on A15
[OnePlus 10 Pro] DenisPDA:
Used A15 Payload_dumper

3.39 MB file on MEGA

mega.nz
[OnePlus 10 Pro] Xpid3r:
A15 Payload Dumper is not working
[OnePlus 10 Pro] Xpid3r:
Well Thanks for your Support

Fixed the Device By Rolling back to A.13 and formatting Data,

All data lost
[OPPO Find X5 Pro Questions & Answers] SpottedEagle:
What is real-name authentication and how do I activate it without id number ?

Or where do I get Id number?
[OPPO Find X5 Pro Questions & Answers] Canuck Knarf:
Are trying to register for developer ...?
[Samsung Galaxy A20 Questions & Answers] x7174nx:
I have Samsung Galaxy A20 phone, stock firmware started lagging terribly after upgrading to One UI 3.1, so I decided to install Lineage OS (I've tried some custom roms like Sakura Project previously so I'm familiar with the process) and Gapps Pico (Arm64) for Android 11 which I have on my phone. I already had TWRP installed, with its help I performed data formatting and formatting of the Dalvik Cache, Cache, Data, Internal Storage and System partitions, after which I installed an archive with Lineageos 18.1 and Gapps to install, the installation went without errors and I pressed the reboot button, after which my phone, after a message from Samsung that I lost my warranty (already a common message, had it since rooting my device) and pressing the Power button to continue booting, just either turns off, or does not show the image.

I tried to force restart the phone (if it is still on) by pressing both the Volume Down and Power buttons for ~20 seconds and the phone indeed rebooted, showed the same warning again and the image is black again. I can't get into recovery by pressing the power button and volume up, nothing happens (or the screen is just black, I'm unsure about it), just the usual pressing/holding of the power button does nothing. I'm not sure if there is an image or if the phone just refuses to turn on, I don't have a suitable cable to bring the image to the computer screen. When the screen is black and I plug in the power cable, there is no vibration, which usually indicates that charging has started, also the screen does not show a charging indication (a circle with a lightning and a percentage usually), but if I perform hard reboot (I believe that's what it's called when you hold Power + Volume Down buttons) it shows me white circle and just a lightning icon which usually indicates bad connection, I guess, so when the cable is plugged in I cannot reboot using Power and Volume Down at all for some reason, it just shows me bad power connection indicator. Also, I cannot perform hard reboot when the cable is plugged in, it shows me that circle with a lightning for a split second and that's it.

I can assume that it's an unofficial Lineageos rom specifically for the Galaxy A20, which I downloaded from Sourceforge. What can I do to check the operability and preferably fix this failure?
[Samsung Galaxy A20 Questions & Answers] x7174nx:
Lmao, solved it by doing some kungfu, with the cable unplugged did the Volume Down + Power thing and then plugged the cable in and as quick as human being can be I held Volume Up + Power to get into TWRP and from there I was able to reboot into download mode and flask stock firmware using Odin (v 3.14 in my case)
[Samsung Galaxy A20 Questions & Answers] mrgspeed:
im having exact same problem but unable to use your mentioned kongfu method, unfortunately :(

so i force restart with vol down and power button hold power button while cable is not connected and then what exactly ? i tried to attach cable fast again and press and hold vol up and power but doesn't seem to be able to go to twrp
[Samsung Galaxy A20 Questions & Answers] x7174nx:
This solution is so random and illogical that I'm not sure how applicable it is for the rest, I found out that it works by trying every way possible, I thought I bricked my phone forever. Although it was 2 years ago, I still kinda recall the process.

First, you hold the Volume down + Power buttons to start turning on the phone (because in my case just Power button on itself did not work at all), and as soon as you hear a vibration response indicating that your phone has turned on, you immediately connect it via a cable to the PC (make sure you have Samsung USB driver installed).

As soon as it starts turning on, you hold the Volume up + Power buttons to get into the bootloader. I found out that it is not necessary to use this combination when the phone is turned off completely, you can still boot into the bootloader during the boot process, just like with the BIOS on PC. So it's like a combo of turning your phone on with the Volume down + Power buttons, not letting it to turn off by plugging in a USB cable, and then quickly booting into the bootloader with the Volume up + Power.

If you're the lucky one, you'll boot into the TWRP and will be able to nuke your system partitions and install a stock firmware (I used samfw.com as it has the most recent firmware for my A20)
[Samsung Galaxy A20 Questions & Answers] mrgspeed:
thank you for the explanation , i ended up opening phone and disconnecting battery (i dont recommend doing this , it can easily damage phone).
[Upgrading, Modifying and Unlocking] masrani:
Friends

am a new member. I have tytyn ii and i just got it upgraded to wm 6.1 thru my dealer but since the time i have upgraded the response has slowed down both on the button as well on the touch screen.

can any one please advise as to how to come off this problem.

Am in the Middle east just in case this would help.

thanks ..
[Upgrading, Modifying and Unlocking] showaco:
There's many cooked roms that are very responsive listed in the kaiser forum.
[General Questions and Answers] gienes:
Hello,

I would like to ask if anyone knows how I could possibly root Doogee X95. I tried swapping boot.img generated in Magisk, but that does nothing and also swapped vbmeta.img to some other blank file.
[General Questions and Answers] xXx yYy:
Patching vbmeta isn't required to root a phone's Android.
[General Questions and Answers] xXx yYy:
Look inside here:

Easy Method To Root Doogee X95 Using Magisk [No TWRP needed]

Here in this guide, we will help you to flash the magisk to root Doogee X95. Read our step by step guide properly! Who doesn't want to get the most of his

www.getdroidtips.com
[General Questions and Answers] gienes:
Thanks for the answer, but I've already done that.
[Samsung Galaxy S9+ Questions & Answers] doka.ua:
Hello, colleagues,

I've bricked Samsung S9+ (SM-G965F). The story is the following:

1. I rooted it with LineageOS 19.1, but after some time of use decided to back it to original firmware

2. Using https://github.com/samloader/samloader I downloaded original firmware for my country (SEK, G965FXXUHFVG5)

3. And using this instruction - https://techbeasts.com/how-to-unroot-samsung-galaxy-s9-and-s9-plus/ - tried to restore original firmware

4. After this phone did not reboot, stucked with white "Samsung" word on the black screen

The error, I guess, was on step (3) above - phone probably was not official and when (too late!) I looked at https://www.sammobile.com/samsung/galaxy-s9-plus/firmware/ I got that, probably, I was need the most widely used European firmware G965FXXUHFVG4 instead of ...FVG5 and, having phone responsive, tried to repeat step (3).

At the end of this procedure, Odin said "RQT_CLOSED !!" and soon reported failed update, while phone stuck in "Downloading... Do not turn off target..." state in 1-2 pixels before the end of progress bar. Now, if I try to boot it, it shows exclamation sign and a message "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software" (of course, Smart Switch do not help - it says something about "plugin lost connection" or something like).

Since I tried to write wrong firmware, I then decided, using the following procedure - https://technastic.com/samsung-pit-file-download/ - to repartition it using PTI file according to instructions. It did not help - situation the same, Odin reports "RQT_CLOSED" and phone stucks in 1-2 pixels before the end of progress bar.

Now is the question - whether it's possible to revive the phone? Any comments, suggestions are highly welcome.

Thank you.
[Samsung Galaxy S9+ Questions & Answers] butchieboy:
You can still flash firmware with Odin from that Emergency screen. Just do button combo for download mode if you get that screen again, flash away. Just make sure you are using correct formware
[Samsung Galaxy S9+ Questions & Answers] doka.ua:
Thanks for the suggestion. To be more precise - are you about this way? - https://www.droidwin.com/create-samsung-combination-firmware-flash-it-via-odin/ Why I'm asking - I don't see in Odin nothing about 'Combo', there is my screen:

View attachment 5710855

Thank you
[Samsung Galaxy S9+ Questions & Answers] butchieboy:
Just use stock firmware
[Samsung Galaxy S9+ Questions & Answers] doka.ua:
I'm sorry for misunderstanding. When I use samloader to download firmware, in fact I get enc4 file, which need to be decrypted and result is Zip archive with 5 files inside - BL, AP, CP, CSC and HOME_CSC. So, four of them I can specify in Odin configuration - BL, AP, CP and either CSC or HOME_CSC. When you say 'stock firmware', what exactly do you mean? Some single file of those mentioned above or something else? I will appreciate if you can give more details. Thank you!
[Samsung Galaxy S9+ Questions & Answers] butchieboy:
Samsung Galaxy S9+ Firmware Download SM-G965F Free Download

Samsung Galaxy S9+ Firmware Download SM-G965F Free Download ⭐ Official and fast update ⭐ Max speed and free download ⭐ Best Samsung Galaxy website

samfw.com
[Samsung Galaxy S9+ Questions & Answers] butchieboy:
Download firmware. Extract, place AP in AP spot in odin and so on with other files
[Samsung Galaxy S9+ Questions & Answers] doka.ua:
Thanks a lot, firmware from this site helped, now I'm in. The difference was in CSC files, while other were the same. Thanks again, appreciate your help.
[Samsung Galaxy S22] kinglb1:
i brought a galaxy s22-s901u1 off of Ebay about a month ago that was a live demo mode model, imei numbers all zeros. i read a post saying it is easier to replace the mother board in the phone to get it up and running. my question is will a s22-s901b (crs) O2C works in the U.S.A on any network been doing a lot of reading and cannot seem to find the answer. Thanks the phone is from Czech Republic
[Android Head-Units] Wahash-Man:
I would like to update the firmware but I have no idea what device it is. It is on Android 12.

Also when a gamepad is connected, it does not work as it is supposed to, the triangle button opens the radio app, the start button turns off the screen and I want to remove that. Any ideas? View attachment 5710717View attachment 5710719
[Android Head-Units] Wahash-Man:
Bump
[General Questions and Answers] gonene1:
Hi

I have a s20 ultra, the original OS\firmware was for Brazil.

I flashed a new original ILO CSC firmware from sam-mobile, used patched odin and changed csc to ILO with SamFw_FRP_Tool

After flashing I added and logged in to my google account and samsung account on the phone.

Now the Play Store is missing.

It does not show in the APPS (at settings) or as an available google service for the device.

what can I do?

Flash another firmware? do something else?
[General Questions and Answers] Droidriven:
Download a copy of PlayStore apk for your specific hardware architecture(CPU) then install the apk.
[General Questions and Answers] gonene1:
Tried that already.

Is says installed when finished and there you can choose OPEN.

But nothing opens and it's like nothing changed.

PS: The option "reset" in settings is also missing.

Took the phone to a local service lab and they worked on it for 2 days already but could not fix the problem. still they are optimistic.

They say that probably something went wrong with the flashing process, but i suspect that it might be something to do with EDM policy, software is installed on the phone but can not be accessed.

I hope the service lab will fix it.
[General Questions and Answers] Droidriven:
B

Boot into recovery mode and wipe the cache partition but do not factory reset.
[General Questions and Answers] gonene1:
Tried to wipe cache partition.

What I did notice, is that in my phone's recovery mode, there is no "wipe data\factory reset" line.

I wish I did a nandroid backup before the update, but i said to myself that this is a new phone and i have no data on it, so there's nothing to lose.

I suspect that only if someone could contribute such a backup of his own original nand, it might fix the problem.

But i am not sure if it is indeed possible to go back to an older boot loader this way.
[General Questions and Answers] Droidriven:
An older firmware will probably have a lower binary version and Samsung has things in place to prevent flashing a lower binary. Downgrade isn't possible unless the downgraded firmware has a binary that is equal to the binary of the currently installed firmware.
[General Questions and Answers] Privacydroid:
You dont need playstore, get aurorastore instead, or fdroid.

auroraoss.com
[General Questions and Answers] gonene1:
S20 Ultra with official firmware should have play store.

If it is missing then it was probably a problem with the flash, or wrong firmware or security, no reason to use a play store alternative, all reason for fixing the base problem.

I am trying to figure out what went wrong and how to fix it.
[General Questions and Answers] gonene1:
Updating...

I found out what was wrong with my phone.

I was sold a phone which is a demonstration managed by knox phone.

Knot would not let the phone have Play Store or the ability to reset it.

This is something that can not be changed unless you root the phone and kill knox.

Knox at first start sends the IEMI of the phone to the server, and since the IEMI is on a list , knot controls it. no way to remove the IMEI from the list since it's in samsung's servers not on the personal device.

I returned the phone to the seller today and received a refund.
[General Questions and Answers] Droidriven:
Better luck next time.
[General Questions and Answers] hfalk4:
hello

I got some digital maps yesterday. And I wont them on my Run.GPS on my Omnio phone. the maps is the type: garmin topo 1:50000 and it is from Norway. I wonder how I shall install the maps on my omnio phone and intgrate it with the Run.GPS?
[Samsung Galaxy Tab A series Questions & Answers] RFZ:
Hey,

I've installed https://xdaforums.com/t/rom-lineageos-14-1-samsung-galaxy-tab-a-7-0-sm-t280-gtexswifi.4158061/ on a SM-T280 that has TWRP 3.2.1-1 recovery installed, using TWRP zip install.

It had been rooted before with SuperSU, so I wanted to root it again with SuperSU (I have reasons for not trying Magisk).

I've tried SuperSU v2.82 and v2.78 from https://xdaforums.com/t/recovery-ro...amsung-galaxy-tab-a6-sm-t280-sm-t285.3475381/ also by installing the zip in TWRP.

When the zip installs, it chooses systemless root. The logs seem fine, no errors, it patches the boot partition.

However, the tablet won't boot. It stays in the "Galaxy Tab A6" screen forever.

When I restore a backup of the previous boot partition, it boots fine again. So I guess it produces a bad boot image when trying to patch it.

Am I missing something obvious here or should it work that way?
[Samsung Galaxy Tab A series Questions & Answers] lewmur:
Try this link.
[Samsung Galaxy Tab A series Questions & Answers] RFZ:
Thx, I'll try it, but I don't understand it.

It requires me to download and flash a kernel (boot.img) at the end. This will overwrite any changes the SuperSU installer made to the boot partition during its install. And if I understand system-less root correctly, it will essentially undo everything the installer did. Also, one kernel can't just run any Android version - usually it's tied to a specific Android version? 🤔

I'll report if it works. If it does, someone needs to explain to me how.
[Samsung Galaxy Tab A series Questions & Answers] RFZ:
Didn't work. To be fair, even https://xdaforums.com/t/recovery-ro...amsung-galaxy-tab-a6-sm-t280-sm-t285.3475381/ mentions this step (I kinda missed it).

Instead of freezing at "Galaxy Tab A6" it boot-loops. It even enumerates on USB after 20s of booting and provides adb, but shell commands available are limited. It doesn't even know `ls`. 10s later it reboots.

As said before, I do not understand this procedure. My impression was that systemless root only modifies the kernel / boot.img. So flashing another boot.img after that seems strange.
[Samsung Galaxy Tab A series Questions & Answers] lewmur:
At what point did it fail? Did you boot to TWRP recovery after flashing it. IOW, before doing anything with SU?
[Samsung Galaxy Tab A series Questions & Answers] RFZ:
What I did:

I booted TWRP and restored a boot.img I backuped yesterday (working LineageOS).

I rebooted to confirm it works. It did.

I booted into TWRP, copied "SR1-SuperSU-v2.78-SR1-20160915123031.zip" and "boot.img" (extracted from "supersu_2.78_SR1_systemless_boot_t280.tar") to the device.

Then installed "SR1-SuperSU-v2.78-SR1-20160915123031.zip" (install zip) and installed "boot.img" as "boot".

Then I rebooted.

Now it shows "Galaxy Tab A6" for 30s and the reboots. Over and over again.

I watched it many times, then booted TWRP again, restored the backup boot.img and it is back.
[Samsung Galaxy Tab A series Questions & Answers] lewmur:
The only thing I see that doesn't match the instructions is restoring the backup boot.img prior to installing SR1.
[Samsung Galaxy Tab A series Questions & Answers] RFZ:
Sure. But the instructions ask me to replace my entire boot partition with a static file I downloaded from the internet. Everything I did to the boot partition before is meaningless.

Clearly the kernel in the patched boot.img is not designed for the Android Version LineageOS 14.1 uses. You can't just boot any android with any random kernel, right? 🤔
[Samsung Galaxy Tab A series Questions & Answers] lewmur:
By your own reasoning, you can't use just any boot.img with what superSU file you're installing. You have to use the one TWRP installed. All I know is that every time someone reports a boot loop it is because they failed to follow the EXACT steps in the instructions.
[Samsung Galaxy Tab A series Questions & Answers] RFZ:
My guess is that whoever wrote these instructions knew that the SuperSU install script isn't compatible with the device and will corrupt its boot partition. He probably fixed it or rooted it manually on his own and provided a rooted version of his boot.img instead. He still asks you to perform the regular setup as it not only will corrupt the boot partition but also install SuperSU.apk to the data partition.

However, this means it will only work with the Android version he used when he created the boot.img. So probably the most recent available stock ROM when the instructions were written. But not Android 7.1.
[Samsung Galaxy Tab A series Questions & Answers] lewmur:
That may be true but you won't get an answer here. Post the question in that thread. But the dev may well have move on to a later device. The 280 dates back to 2016.
[Samsung Galaxy Tab A series Questions & Answers] RFZ:
Yep, confirmed my theory. I compared the original LineageOS 14.1 boot partition (from my backup) with the one the SuperSU installer creates that won't boot at all using a Hex-Editor. The one SuperSU installer created is missing an additional 0x200 bytes header that the original one had. I simply copied the first 0x200 bytes from the original into the one SuperSU installer created, removed the last 0x200 bytes of the image so the size fits, and flashed it.

And it works.

So I guess the SuperSU installer works with every Android Version on the SM-T280, but you have to add the additional 0x200 bytes from the original partition. (Probably also something one could simply patch in the SuperSU installer)

I've attached the image that works with LineageOS 14.1 on the SM-T280 and SuperSU installer 2.78.

Procedure is the same as:

1) Install SuperSU 2.78.zip in TWRP

2) Flash attached image (extracted from zip) to "boot" using TWRP

EDIT:

removed the attached image. See https://xdaforums.com/t/recovery-ro...sm-t280-sm-t285.3475381/page-13#post-87442015
[Samsung Galaxy Tab A series Questions & Answers] lewmur:
Glad you got it working. Did you post this info in the other thread? That is probably where someone else would look for the info.
[Samsung Galaxy Tab A series Questions & Answers] RFZ:
Not yet. I will try to fix the SuperSU installer and also try it with SuperSU 2.82. Supplying a boot.img is really not the best idea and a fixed installer would be a far better solution.

It's just an additional offset of 0x200 when writing the modified image. Can't be hard to fix. I'll look into it tomorrow.

Edit: Posted a patched SuperSU installer here:

https://xdaforums.com/t/recovery-ro...sm-t280-sm-t285.3475381/page-13#post-87438849

Didn't work for 2.82 though, just for 2.78 🤔

Edit: Got it working for 2.82 too, see link above.
[Motorola Edge 30 Ultra / Motorola Moto X30 Pro] uses0ap:
With the announcement of the global version of the Edge 30 Ultra, can we expect custom rom support for this device?

I'm not very knowledgeable in the Motorola space. Looking for a OnePlus alternative since all their new devices are held up with MSM tool auth woes.
[Motorola Edge 30 Ultra / Motorola Moto X30 Pro] Janly:
The edge 30 ultra is not limited, there is stock firmware, but if you customize the Rom, you have to wait for the kernel to open source, about 3 months later, and then you need to be adapted by a developer
[Motorola Edge 30 Ultra / Motorola Moto X30 Pro] Ginz:
I know somebody is working on LineageOS for the Ultra
[Android Q&A, Help & Troubleshooting] 200Volts:
I have a Galaxy S9 Android 10 that was a corporate phone with Blackberry UEM client loaded. I'm trying to reset the phone with ODIN and stock f/w, but not having any success.

I assume Dev Option USB debugging is off since phone reset due to too many pw attempts (it starts, but hangs at UEM login screen).

Phone connects to ODIN, tried just AP, all f/w, all f/w without "home" CSC, NAND flash, etc.

Right after ODIN start, it either stops w/error or ODIN hangs with one dot on progress bar.

Thanks