yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S10+ Questions & Answers] AHE_XDA:
So there a few caveats when running an unlocked Samsung handset on XAA firmware; you may or may not get specific features from your Carrier.

So if you use or value one carrier's feature set over the other than flash their firmware and convert your phone from SM-G975U1 to SM-G975U.

In exchange, you'll get the carrier bloat but it is can be disabled and some of it uninstalled.
[Samsung Galaxy S10+ Questions & Answers] Vertig0:
Do you know which features will I lose if I run XAA?
[Samsung Galaxy S10+ Questions & Answers] AHE_XDA:
XAA is the default software that ships with any unlocked USA-specific Samsung device.

You may or may not have access to VoLTE or WiFi Calling.
[Samsung Galaxy S10+ Questions & Answers] Vertig0:
thanks a lot! I have a better understanding now...

Do you know where I can download the firmware for free? so far all the websites I found you have to pay. ex SamMobile ,imei.info
[Samsung Galaxy S10+ Questions & Answers] AHE_XDA:
Absolutely.

This is what I use exclusively:

https://xdaforums.com/galaxy-s9/how-to/tool-frija-samsung-firmware-downloader-t3910584

I attached a screenshot to help you set it up.
[Samsung Galaxy S10+ Questions & Answers] Vertig0:
awesome! now I can finally put my iphone to rest... thanks for all the help.
[Samsung Galaxy Note 9 Questions & Answers] wtd03:
Sometimes i like to use my phone while laying on my side in bed. I hate landscape mode so I turn the phone to portrait mode only.

This works for apps like chrome or the home screen however some banking apps like hanscom Federal Credit union seem to ignore this setting and if you rotate the phone the app still rotates even though the setting is set on the phone.

Would this be a note 9 issue or an issue with the app itself? How can the app override a system setting?
[Google Pixel 3 Themes, Apps, and Mods] Xdevillived666:
I have succeeded in rooting my pixel 3 on Q beta 4 using latest canary after it was announced that the dev figured ut root. You'll have to manually patch the boot image, which some folks don't know yet how to do. Here's the simplified version:

First, you must grab the stock boot image for the current firmware installed on your device

Place the boot image on the phone’s internal storage or SD card

Download the latest Magisk Manager APK and install it on your device

Open “Magisk Manager”

Tap on the “Install” button and choose “Install” again

Select “Patch Boot Image File”

Install Magisk Universal Systemless Interface - Patch Boot Image

Install Magisk Universal Systemless Interface – Patch Boot Image

Navigate to the storage and select your phone’s boot image that you transferred earlier

Let Magisk do the job and patch the boot image

Once patched, copy the “patched_boot.img” file from /sdcard/Download/ to C:\adb on your PC

In the same folder, hold the SHIFT key and right-click on an empty space

Select “Open PowerShell window here”

Install Magisk - Open PowerShell window here

Boot your Android device into Bootloader/Fastboot mode

Connect your phone to the PC

Flash the “patched_boot.img” to install Magisk and root your Android device:fastboot flash boot patched_boot.img

For devices with A/B partition system, use the following commands:fastboot flash boot_a patched_boot.img

fastboot flash boot_b patched_boot.img

Once done, reboot your phone using:fastboot reboot

When your phone boots, open the Magisk Manager and confirm that the installation was successful.
[Google Pixel 3 Themes, Apps, and Mods] zaacc:
do you know if google pay still works?
[Google Pixel 3 Themes, Apps, and Mods] JujuYuki:
I seem to have managed to get GPay to work by using magisk hide on both GPay and the Google Play services, hide magisk manager, disabling usb debugging and the developer settings and clearing the data of Gpay and the Google play Services.

I still need to test if it actually gets to pay and not just a fluke, but it went through the setup of contactless payment for my card (wihle it didn't before disabling usb debugging and the developer settings, where it said I was "rooted or modified in some way"). Will see that soon though, when I try to take he tube to go back from work. I'll update then.
[Google Pixel 3 Themes, Apps, and Mods] philliyxx:
I was unable to patch android q beta 3 image with magisk, can you post your patched one here? --found it on reddit and it worked search similiar to this
[Google Pixel 3 Themes, Apps, and Mods] mdmogren:
I tried this with Beta 5, boots fine after flashing the patched image but not showing as rooted...
[Google Pixel 3 Themes, Apps, and Mods] vonDubenshire:
It works fine on Pixel 3 if you just download the boot.img from the Google website for Beta 5, run Magisk Manager and tell it to make a magisk version of the boot img.

Same as always. Shows rooted for me.
[Nook Touch General] Renate:
This all started out in a Glowlight 4 (7.8", 2019) thread: https://xdaforums.com/nook-touch/general/glowlight-plus-7-8-2019-t3934677

An SD card was soldered to test points on the circuit board of a Glow4 to allow for extra storage.

Since it looks like this same technique should work on Glow2 & Glow3 I've broken the thread out here.

The Glow4 has test points labelled by function and has been tested and proven to work with SD cards.

http://www.temblast.com/blogs/glow4/blog.htm#sdcard

The Glow3 has test points labelled by function and has not yet been tested.

The Glow2 has test points, but they are not labelled by function.

I will try to "wiggle" out the pinout soon.

Since the only difference between the models will only be wiring, I suspect that the bulk of this thread will be on configuration and use.
[Nook Touch General] Renate:
I wiggled the Glow2, the pinout for SD2 is:

TP159 D0

TP160 D1

TP161 D2

TP162 D3

TP163 Cmd

TP164 Clk

TP165 /CD

TP165 VDD

TP167 Gnd

The Glow3, while it's labelled, seems to be on SD3, which is not configured.

I'm still looking at this.
[Nook Touch General] case-sensitive:
Thanks! I look forward learning more about mounting the sdcard and editing fstab etc.

One more question: Does this method have any restriction on the size of the sdcard and how it's formated? Many old(er) android devices with external storage can only take sdcard of size up to 32Gb, and (independent of that) sometimes people are told to format the sdcard using the device itself, but other times we're suppose to format it in advance (fat32? ext4?).

THANKS!
[Nook Touch General] Renate:
This is not so much a method as simply putting in an option that they couldn't be bothered with.

I don't have anything bigger than 16GB on hand.

32GB is the limit for SD 2.0 spec.

Most of the 4GB to 16 GB cards that I have tried are SD 3.0 spec.

You can see this with mmcinfo in uboot.

Formatting things VFAT is only useful if you want to use UMS.

I wouldn't recommend that, VFAT is old and stupid and there are issues with timezones on timestamps.

ext2 is kind of the logical choice.

mkfs.ext2 is included in busybox for formatting.
[Nook Touch General] Renate:
TLDR: This works on the Glow2 & Glow4 relatively easily.

On the Glow3 you'd need to sacrifice the WiFi to make it work. This works on the Glow3, but you need a modified kernel and a hwcfg change.

http://www.temblast.com/blogs/glow2/blog.htm

http://www.temblast.com/blogs/glow3/blog.htm

http://www.temblast.com/blogs/glow4/blog.htm
[Nook Touch General] Renate:
Apparently there is already a default place for external SD cards: /mnt/media_rw/extsd

This has a link from /storage/extsd

Since the directory already exists you don't need to modify /init.rc

If you want to use vfat formatted disks and have them hot swappable you don't even have to modify /fstab.E70Q50

My choice is to use an ext2 formatted disk and since it will be internal and not swappable, I don't need or want vold, the volume daemon.

You need to tweak /fstab.E70Q50 (get rid of any line that mentions "extsd").

/dev/block/mmcblk1p1 /mnt/media_rw/extsd ext2 defaults defaults

You can split the SD card into separate partitions if you want.

You'd have to add some more entries in /fstab.E70Q50 and some mkdirs in /init.rc

For partitioning/formatting cards:

# busybox fdisk /dev/block/mmcblk1
d [color=red]<-- delete partition[/color]
n [color=red]<-- new partition[/color]
w [color=red]<-- actually write the changes[/color]

#busybox mkfs.ext2 /dev/block/mmcblk1p1

Be very careful when you are talking about mmcblk? and mmcblk?p?
[Nook Touch General] Renate:
root@ntx_6sl:/ # df
Filesystem Size Used Free Blksize
...
/mnt/media_rw/extsd 114.4G 20.0K 114.4G 4096
...
root@ntx_6sl:/ # mount
...
/dev/block/mmcblk1p1 /mnt/media_rw/extsd ext2 rw,relatime,errors=continue 0 0
[Nook Touch General] Renate:
On the Glow2 I ran into a hiccup.

I soldered some 30 gauge wire directly to the micro SD card.

The SD2 is there and fine, but the NtxHwCfg (at least on mine) had to be patched.

# dd if=/dev/block/mmcblk0 of=/sdcard/hwcfg skip=1024 count=1

This will get you a 512 byte file.

Look at the byte at hex address 0x4f

For the SD card to work this value must be 0x02 (it was 0x00 on mine)

Be very careful modifying the file and writing it back to the internal SD:

# dd if=/sdcard/hwcfg of=/dev/block/mmcblk0 seek=1024 count=1

Hey! It says "skip" in the first example and "seek" in the second. I warned you!
[Nook Touch General] Renate:
Well, more sloppiness on NTX/B&N's part.

*.rc files are organized by board names

Usually they shovel the files into the ramdisk.

This means that you have bunches of useless files that aren't used by your hardware.

The Glow2 is a E60QD0 board, the Glow3 is a E60QQ0 board, the Glow4 is a E70Q50 board.

The init.<board>.rc file should load the fstab.<sameboard> file.

On the Glow2 (at least mine) they did sloppy copy/paste and the init.E60QD0.rc loads fstab.E60Q50

I edited init.E60QD0.rc to load fstab.E60QD0

(Then made sure that fstab.E60QD0 had the correct contents.)

Likewise, init.<board>.usb.rc is sloppy.

They don't use the approved syntax of ${ro.serialno}, but instead use $ro.serialno

I get tired of the warnings in the console log.

Also, a lot of redundant junk (the VID/PID stuff can be moved to the "on boot" section).
[Nook Touch General] Renate:
If you are using a Glow2 and you just installed the 5.0 update and you had previously modified the hwcfg,

then you will have to set it back to the original version to allow the added SD card to work properly.

See: https://xdaforums.com/showpost.php?p=80114208&postcount=623
[Nook Touch General] Renate:
I had previously said that an SD card and WiFi were not compatible on the Glow3.

It turns out that it's a bit more complicated.

SD2 is the WiFi interface.

SD3 goes to the test points.

The software currently has the WiFi enable/disable switching the SD3 interface, which is wrong.

I've got the hardware itself working

eBR-1A # mmcinfo
Device: FSL_USDHC
Manufacturer ID: 27
OEM: 5048
Name: SD32G
Tran Speed: 25000000
Rd Block Len: 512
SD version 3.0
Clock: 50000000
High Capacity: Yes
Capacity: 31104958464 Bytes
Bus Width: 4-bit
Boot Partition for boot: No boot partition available

Now I just have to fix the software.
[Nook Touch General] Renate:
Ok, so I've patched the kernel to make this work on the Glow3.

This also needs a change to the ntxcfg. You can do that with dd or some other tool.

Is anybody ready for this? Do you have the soldering iron warmed up?

/mnt/media_rw/extsd 28.5G 20.0K 28.5G 4096

I've got to make a version of the image without my stuff in it.

I usually don't like heavily modded images.

The one thing I put in is a rooted adbd.
[Nook Touch General] Renate:
So, who's ready for the glow3?

You need a new kernel.

If you have access to fastboot you can test drive it with "fastboot boot p1mod.img".

Later you can "fastboot flash boot p1mod.img" to make it permanent.

If you don't (and you're brave and have a good recovery) you can "dd if=p1mod.img of=/dev/block/mmcblk0p1"

You will need to patch the NTX hwcfg.

If this is patched but you are still running the old kernel the WiFi will probably not work, but the glow3 will still be functional.

# dd if=/dev/block/mmcblk0 skip=1024 count=1 of=/sdcard/hwcfg
[color=red]Use your favorite hex file editor either on of off the glow3 to change address 0x4f from 0x02 to 0x00.
modfile hwcfg 4f 00[/color]
# dd if=/sdcard/hwcfg seek=1024 count=1 of=/dev/block/mmcblk0

If you have access to the u-boot command line you can do it there instead:

eBR-1A # mmc read 910000 400 1

MMC read: dev # 0, block # 1024, count 1 ... 1 blocks read: OK
eBR-1A # mm.b 91004f
0091004f: 02 ? 00
00910050: 01 ? q
eBR-1A # mmc write 910000 400 1

MMC write: dev # 0, block # 1024, count 1 ... 1 blocks write: OK
eBR-1A #

So, if you get through with all this and reboot it should boot up just fine.

There is a rooted adbd in there so that should not be a problem.

The fstab has been modified to mount your new SD card.

Since that is probably still the original filesystem it will not mount correctly.

You can do an "ls -l /dev/block" and see both mmcblk1 and mmcblk1p1.

You probably noticed that your old /sdcard is empty.

This is an artifact of the fstab not finishing and therefore the nonencrypted is not triggered nor the late_start.

Just do a "start sdcard" and the /sdcard will populate.

So now, just do a "busybox fdisk /dev/block/mmcblk1" to repartition and a "busybox mke2fs /dev/block/mmcblk1p1".

The fstab presumes ext2, a reasonable choice for something used as big storage. If not, just change it.

Reboot and everything should be good.

Good luck.
[Nook Touch General] Renate:
I've been talking about the NTX hardware configuration, but I don't think that I mentioned or released the utility that I use to dump it.

Availible in the signature, there is NtxHwCfg which can dump or compare NTX configurations.

There is a version for Win32 and one for Android.

http://www.temblast.com/android.htm

It's interesting that the B&N updates don't modify the NTX config.

The Glow2 has version 2.5 vs. the Glow3 with 2.8 vs. the Glow4 with 3.1!

So that means that the u-boots all have to be different.

C:\>ntxhwcfg hwcfg3 hwcfg4
0b Version 2.8 3.1
0f Size 65 70
10 PCB E60QQ0 (69) E70Q50 (84)
12 AudioCodec No (0) ALC5672 (6)
14 Wifi RTL8189 (8) RTL8723DS (14)
15 BT No (0) RTL8723DS (8)
17 TouchCtrl neonode_v2 (8) ektf2132 (9)
...
[Android General] imska:
Reserved
[Android General] Exodusnick:
download for linux coming soon ?
[Android General] imska:
Download for Linux is already there.

Download for Mac coming soon (as soon as I figure out how to create a mac-app with a bundled jdk and launchable by click)
[Android General] Exodusnick:
Download for Linux 404 Not Found

https://free-droid.com/

Downlad for Windows yes for Linux no
[Android General] imska:
You're absolutely right, thanks for pointing that out!

Fixed.
[Android General] imska:
Ladies and Gentlemen,

Mac support has landed. You can now download Free-Droid for MacOS.

Depending on your Gatekeeper settings, you might need to launch Free-Droid by right-clicking on it and selecting Open. If it still fails to start, try to start the file called "right-click open" in the same way.
[Android General] godofsalt:
It is out and works with Ubuntu 18.4.2 and a Galaxy S5 (kltedv). Can Take a bit to download and install all of its Binaries .... A bit like Odin look. Similar to Skipsoft, with out a huge amount of reading.

Version 0.6.6 ; build 20190723; Lic-GPL-3.0

keep up the work on this! Seems rather easy to use.

Will keep an eye for updates coming..
[Android General] Broked:
This is beatiful! I wasted probably 2 hours this morning to get a android 9 on my old s5 since i need it for a project, i'm not a complete newby, i rooted and changed rom many time in the last 8 years but i do it every once in a while, so i always have to check for tutorials again and there is alwasy some step that don't go as planned, as today the rom was not installing, was almost ready to give up to not lose more time, saw this, was almost sure this would gone wrong somewhere as all automated stuff while after a couple of clics and 5/10m my s5 was ready with android 9 on it. THIS IS JUST BEATIFUL and great, hope it gain the visibility it deserve!

Really GREAT job!
[Android General] imska:
Ladies and gentlemen,

Support for OnePlus devices has landed.!

Assuming that the bootloader unlock procedure is the same on all OnePlus devices, Free-Droid should work perfectly with them now. Still, any bug report is welcome.

Developed and tested with a OnePlus X (onyx).

Happy flashing to everyone!
[Android General] imska:
Fixed bug when connecting device on the latest release.

Pushing update to the server right now, just restart the application and let it update itself.
[Android General] imska:
Sorry for the server downtime over the last days. Everything is back online again and running.

Update to be released soon with support for nvidia shield tablet (will need testing though).
[Android General] imska:
0.7.3 update released

-Better device detection using a database from here. This should result in less devices not recognized at all. Still, a lot of devices may be recognized, but have no working TWRP or rom known to free-droid.

-a lot of refactoring done in the code

-initial support for NVidia devices. Sould work in theory, but I couldn't test it by myself yet.
[Android General] DKDK99:
Says Device Supported. Then Says "Sorry, I don't know how to work with your device." Samsung Galaxy S5 SM-G900V.
[Android General] imska:
Thanks for reporting this. Maybe you can help me sort this out... The G900V is the Verizon variant if I'm not mistaken. Can you confirm that it *should* work with the official lineageOS for the S5 (klte)? Besides, it would be of great help for me to diagnose and fix the error if you could send me the logs of free-droid. You can hit export logs in the help page of the application and drop the zip either here or send to info@free-droid.com
[Android General] imska:
New update released: 0.7.5

Sony support!

better device recognition

bug fixes
[Android General] liwern:
hope u can add support to install custom rom other than Pie 9.0. Coz I want to install stable version of Xposed.
[Android General] imska:
You already can install any ROM you have downloaded. Just select "use my own ROM" and choose the zip.

But I think you can use magisk and the module called tai chi to install and use xposed stuff
[Android General] Anikscha:
Linux Version

[MENTION=6872152]imska[/MENTION]

Stuck forever at "Welcome Screen" on Ubuntu 16.04 (Xenial fork) :(
[Android General] fxo:
Looks amazing don't have a chance to test it but here are some mirrors:

Windows https://www.mediafire.com/file/1603rruccyef7gv/Free-Droid-WIN-latest.zip/file

Mac https://www.mediafire.com/file/qi64ju4y7108nqc/Free-Droid-MAC-latest.tar.gz/file

Linux https://www.mediafire.com/file/m5hzx7b4xie503o/Free-Droid-LINUX-latest.tar.gz/file
[HTC U Ultra Questions & Answers] usmantahir:
Found the right RUU

The OTA file mentioned wouldnt flash, so i found an RUU of the same variant.

https://androidfilehost.com/?fid=11410963190603866517

It did the job, but seems like this wasn't it for my phone. Seems like a hardware issue to me since it would randomly freeze, even followed by a long-timed vibration till it turned off. So i'll be taking it for repair to a shop.
[General Questions and Answers] whreed:
I am running Android q beta 4 on pixel 3 xl. I am using dnd mode on my phone and wanted to know if I can have the ability to do mute all audio on the phone with notifications and only get them in the watch. When I'm in dnd mode I get no notifications on the watch but get them on the phone silently. If I come out of dnd mode I get them on my watch but I hear the notification noise.

Am I missing something or do I need to do an app exception and override the dnd setting?
[Google Pixel 3 Questions & Answers] levibuko:
Helloguys and gals,

I just got a Pixel 3 and wanted to root it. I followed this guide: https://www.youtube.com/watch?v=BgV1xxkcBk8

I installed the latest TWRP recovery (didn't keep it read only, maybe this was a mistake?). After that I installed Magisk which was followed by a bootloop.

To fix the bootloop I used TWRPs fix bootloop fix which worked. But that makes Magisk undone.

So my Questions is how to install Magisk? Do I need to flash the stock image on both slots and start again? Is the guide outdated? If so, which guide should I follow?

Edit: My phone is still on the update from November 2018.
[Google Pixel 3 Questions & Answers] bafforosso:
On A/B devices there is no dedicated recovery partition anymore, recovery is contained in the boot partition, so if you install Magisk it's advised not to install TWRP on those devices anymore to avoid both modifying the same image, but instead to always fastboot boot when you need to use TWRP.

These are the steps I follow every time I need to factory reset then root my own Pixel 3 :

Boot to bootloader

Flash stock image on current slot

Flash stock image on other slot

Boot the system, enable Developer options and USB debugging

Fastboot boot TWRP image

Backup Boot partition

Flash Magisk

[optional] Flash custom kernel (check flashing order depending on kernel)

Reboot
[Google Pixel 3 Questions & Answers] levibuko:
Allright, thank you for your explanation! I used the stock image and the flash-all.bat to install the stock image. Will it be enough since you are speaking of two different slots? if not, how can i do both slots?

thx in advance
[Google Pixel 3 Questions & Answers] wangdaning:
I run twrp as the devices recovery and have magisk. I would follow the twrp and magisk guides for this device. First boot twrp then use the installer, second reboot, third get to recovery and flash magisk. The boot partition needs to be rebooted before root. It is an initialization thing. Get twrp, reboot, magisk.
[Google Pixel 3 Questions & Answers] tenthousandfeet:
Having a similar issue here. I was rooted till the latest OTA happened a few days ago. Trying to re-root in several different ways, but all result in boot loop.

Methods I've tried:

Extracted boot.img from factory image, patched with Magisk Manager, flashed with fastboot

Fastboot boot twrp-3.3.0-0-blueline.img, installed Magisk-v19.3.zip

Fastboot boot twrp-3.3.0-0-blueline.img, installed twrp-pixel3-installer-blueline-3.3.0-0.zip, rebooted recovery, installed Magisk-v19.3.zip

Any ideas?
[Google Pixel 3 Questions & Answers] bafforosso:
I tinker a lot with my phone so I usually want to have both slots clean flashed when I start back from scratch, not sure that is really necessary, but here are the steps I use for flashing both slots :

fastboot getvar current-slot
./flash-all.sh
fastboot --set-active=x (x being a or b, the other slot than the one you get with the fastboot getvar command)
./flash-all.sh
[Google Pixel 3 Questions & Answers] Ike229:
Exactly the same issue here, no luck. I'm only able to boot if I flash the stock boot.img. However, no root.

---------- Post added at 08:00 PM ---------- Previous post was at 07:52 PM ----------

Exactly the same issue here, no luck. I'm only able to boot if I flash the stock boot.img. However, no root.
[Google Pixel 3 Questions & Answers] wangdaning:
Boot twrp and install it, then reboot to system, then reboot recovery and install magisk. You need to boot system before installing magisk.
[Google Pixel 3 Questions & Answers] tenthousandfeet:
Tried that. No success.
[Google Pixel 3 Questions & Answers] wangdaning:
Only thing I can think is to install an older magisk then let it update. I originally installed 18 something and have just let it update. I do not use google's factory image though, so cannot really help troubleshoot.