yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] quiestbml:
Glad I'm not the only one trying to do this.

So, I did a ton of research into this. The SC9820e does in fact support unused bands. The bands that are locked/unlocked are controlled by NVRAM and possibly the modem firmware itself (but I think it's just codes in NVRAM). Nobody has figured out how to enable bands on Spreadtrum devices, BUT...

The firmware source code for the SC9820 happens to live in a public Github account... including the modem firmware, signing keys, uncompiled debugging apps, and several previously-unreleased Spreadtrum development tools.

Access it all here: https://github.com/yonglongliu?tab=repositories

As far as I can tell, everything required to figure out how to unlock bands on the QIN 1S+ is available in that repository, but I have no experience with coding or android development so I'm not gonna be able to do anything with it. Best of luck!
[Android Q&A, Help & Troubleshooting] throwaway019299292:
Hello, Spreadtrum/Unisoc seem to use the same secret code *#*#83781#*#*. You can enable and disable bands there. Thanks to the help of this article. https://www.journeybytes.com/how-to-check-compatible-4g-lte-bands-in-spd-phones/
[ASUS ZenFone 8] Tom100%:
I just did a quick test of how well the stock Asus camera, GCam and Open Camera handle shots taken at night: I downloaded the GCam APK from XDA: GCam_8.1.101_Wichaya_V1.1 and the Open Camera from F-Droid onto my Zenfone 8. I took the same shot of the exterior of my apartment block, including trees and greenery, with all three cameras.

I used normal and night modes with the Asus and GCam and Normal and DRO modes with the open camera and then compiled all the shots into a layered Photoshop file so that I could easily compare them.

The Asus night mode gave a much better result than the normal mode. The shadows had slightly more detail and much more color information than the normal mode. But they are aggressively sharpened and have a somewhat processed look.

The GCam normal and night modes had more color and slightly more detail in the shadows than the Asus night mode. They have much less sharpening than the Asus picture and so don't show as much detail, but they have a more natural appearance.

I wish I could turn down the sharpening of the Asus pictures, and turn up the sharpening of the GCam pictures. Unfortunately the Asus camera does not have a way to turn down the sharpening in either the Photo or Pro modes.

There is a setting in GCam to increase sharpening but it's not intuitive and I haven't messed with it yet.

The Open Camera gave really poor results in night and DRO modes, so soft and grainy that it's not something I'd ever use.

I've attached a detail from the Asus and GCam night mode shots and the DRO OpenCamera shot.

This was just a quick and simple test entirely for my own satisfaction, and the results of course are subjective. I'm now going to experiment with the GCam > Advanced > Ram Patcher >Sharpness setting and see If I can increase the sharpening and get a result somewhere between the the softer GCam default and the Asus overprocessed look...
[ASUS ZenFone 8] Tom100%:
Mod edit: @Tom100% Thread closed as duplicate of

https://xdaforums.com/t/asus-gcam-and-opencamera-night-shots-compared.4315513/

Please review the XDA Forum Rules with special emphasis on rule no. 5 and post only ONCE! If you want to edit the title of a thread, so just edit the title but don't post a new thread.

Regards

Oswald Boelcke

Senior Moderator

I just did a quick test of how well the stock Asus camera, GCam and Open Camera handle shots taken at night: I downloaded the GCam APK from XDA: GCam_8.1.101_Wichaya_V1.1 and the Open Camera from F-Droid onto my Zenfone 8. I took the same shot of the exterior of my apartment block, including trees and greenery, with all three cameras.

I used normal and night modes with the Asus and GCam and Normal and DRO modes with the open camera and then compiled all the shots into a layered Photoshop file so that I could easily compare them.

The Asus night mode gave a much better result than the normal mode. The shadows had slightly more detail and much more color information than the normal mode. But they are aggressively sharpened and have a somewhat processed look.

The GCam normal and night modes had more color and slightly more detail in the shadows than the Asus night mode. They have much less sharpening than the Asus picture and so don't show as much detail, but they have a more natural appearance.

I wish I could turn down the sharpening of the Asus pictures, and turn up the sharpening of the GCam pictures. Unfortunately the Asus camera does not have a way to turn down the sharpening in either the Photo or Pro modes.

There is a setting in GCam to increase sharpening but it's not intuitive and I haven't messed with it yet.

The Open Camera gave really poor results in night and DRO modes, so soft and grainy that it's not something I'd ever use.

I've attached a detail from the Asus and GCam night mode shots and the DRO OpenCamera shot.

This was just a quick and simple test entirely for my own satisfaction, and the results of course are subjective. I'm now going to experiment with the GCam > Advanced > Ram Patcher >Sharpness setting and see If I can increase the sharpening and get a result somewhere between the the softer GCam default and the Asus overprocessed look...
[Moto G7 Questions & Answers] maybeme2:
Hi Guys

I bricked my phone because I did something wrong. I need help.

I have a rooted Moto g7 (river) running android pie.

I decided to upgrade it to android 10.

1. I downloaded the latest android 10 version from:

lolinet mirrors - firmware, software, iso etc.

lolinet mirrors - powered by h5ai

mirrors.lolinet.com

2. created new C:\adb2021 folder in laptop

obtained latest adb/fastboot from

https://developer.android.com/studio/releases/platform-tools

unziped the zip contents into the new C:\adb2021

3. Connected by cable and turned on phone

4. In a CMD prompt on W10 went to in C:\adb2021

5. adb reboot bootloader

was successful

6. I then ran

fastboot flash partition gpt.bin

fastboot flash bootloader bootloader.img

fastboot flash modem NON-HLOS.bin

fastboot flash fsg fsg.mbn

fastboot erase modemst1

fastboot erase modemst2

fastboot flash dsp adspso.bin

fastboot flash boot boot.img

fastboot flash dtbo dtbo.img

fastboot flash system system.img_sparsechunk.0

fastboot flash system system.img_sparsechunk.1

fastboot flash system system.img_sparsechunk.2

fastboot flash system system.img_sparsechunk.3

fastboot flash system system.img_sparsechunk.4

fastboot flash system system.img_sparsechunk.5

fastboot flash system system.img_sparsechunk.6

fastboot flash system system.img_sparsechunk.7

fastboot flash system system.img_sparsechunk.8

fastboot flash system system.img_sparsechunk.9

fastboot flash system_b system_b.img_sparsechunk.0

fastboot flash system_b system_b.img_sparsechunk.1

fastboot flash system_b system_b.img_sparsechunk.2

fastboot flash vendor vendor.img_sparsechunk.0

fastboot flash vendor vendor.img_sparsechunk.1

fastboot flash vendor vendor.img_sparsechunk.2

fastboot flash oem oem.img

fastboot flash oem_b oem_other.img

fastboot erase carrier

fastboot erase DDR

fastboot flash logo logo.bin

patched_boot.img

fastboot reboot

Problem:

The phone rebooted but is stuck on the

"your device has been unlocked and can't be trusted" screen.

Rebooting just brings me back to this same screen.

I can get to the Android Recovery screens but don't know what to do there.

The fastboot commands I listed above were originally designed for installing android 9. I now see I should have included fastboot flash system system.img_sparsechunk.10

When in the recovery screen "Flastboot Flash mode" I tried to issue from the laptop

C:\ADB2021>adb reboot bootloader

I get

error: no devices/emulators found

Please help. This is my main phone.

How do I recover?

Thanks.
[Moto G7 Questions & Answers] maybeme2:
I tried factory reset. And then reboot but it still only goes to the "this device is unlocked....." and stays there.

I really need help.
[Android Software/Hacking General [Developers Only]] theproman23:
Mod edit: @theproman23 Thread closed as duplicate of

https://xdaforums.com/t/porting-from-verizon-to-att.4314451/

Please review the XFA Forum Rules with special emphasis on rule no. 5 and post only ONCE! If you're unhappy with the location of your thread, simply report it and get it moved to your desired location instead of creating a new thread. Thanks for your cooperation.

Regards

Oswald Boelcke

Senior Moderator

I have a Galaxy S20+ 5G and I recently ported my number over to ATT from Verizon and everything seemed to working fine with the exception of VM and few other things. After being on numerous calls and chats with ATT tech support they suggested I perform a factory reset which definitely didn't fix anything. I found the following thread and followed the instructions and I still can't seem to get the Verizon Software off my phone:

https://xdaforums.com/t/g986u-and-g986u1-firmware-links-and-flashing-discussion-here.4054629/

I've used different versions of the ATT user data file and no matter what I do the carrier software version on my phone still reads VZM. I know the flashing process worked as I now boot to a Samsung screen as opposed to the Verizon one. I'm sure I'm missing something but after 12 straight hours of trying to fix this I'm running out of things to try. Any help you can provide will be much appreciated.

PS I read something about the carrier info. being locked to the phone but the phone is definitely unlocked as it works for calls and texts using my ATT sim.
[Android Software/Hacking General [Developers Only]] blackhawk:
You can request the carrier not send you updates to that device. Disable on their end.

This is what I've been using for 2 years.

Package Disabler

The only NON-root solution that let’s you disable any unwanted packages that come pre-installed / installed with your phone / tablet.

www.packagedisabler.com
[Android Software/Hacking General [Developers Only]] theproman23:
Thanks but I'm not sure I understand how to connect what you're saying with my ask. Are you saying there's no way to get rid of this carrier software and replace it with the ATT one?
[Android Software/Hacking General [Developers Only]] blackhawk:
My bad... skim reading badly again🤣

The AT&T update app is just as bad as the Verizon one.

AT&T bloatware sucks. I use their texting app, the rest is package blocked.

If your phone's running fast, stable and fulfilling its mission... let it be. AT&T updates can break your phone.

Yeah the factory reset just wasted time more than likely.

Not sure your variant's hardware is compatible with AT&T firmware. Carrier phones can have different hardware as speced by that carrier as the major carriers and Samsung are partnered to the bone.
[Android Software/Hacking General [Developers Only]] theproman23:
So that's the problem I still don't have VM and the ATT tech support claims that it's because it's a Verizon provided phone and that they can't guarantee that all features will work which just seems like a cop out on their part. My wife has a iPhone 12 and everything works just fine for her and the rep claimed that Apple phones are easily interchangeable between carriers and that Androids always have problems which again seems like a BS explanation.
[Android Software/Hacking General [Developers Only]] blackhawk:
I never use VM...or call waiting anymore.

Found this:

verizon phone now att-can't set up voice mail | AT&T Community Forums

I moved Galaxy S3 from Verizon to ATT. All works except I can not set up voice mail. The "1" key apparently is still trying to call Verizon. I have tried calling the 800 number to set up voice m...

forums.att.com

There's a way if that doesn't work. Anytime a tech tells you to do a factory reset for a settings or usage issue they are either inept, blowing you off or both.

Try advance tech support. Eventually you'll get someone who knows what they're doing.
[Android Software/Hacking General [Developers Only]] theproman23:
Thanks, unfortunately it doesn't look like there's any sort of resolution on that thread. I'll try calling ATT again.
[Xiaomi Mi 10T Lite Questions & Answers] tze_vitamin:
First image when you turn your phone says Redmi, I fond slash screen MI.img, but don't know how to change it.

Phone is rotted.

I google but didn't find nothing secure.

This is image that I want

And when I go to oFox, what to choose?

Or is there any other way to change it in root file explorer? Or is it it that for boot IMG?
[Xiaomi Mi 10T Lite Questions & Answers] NOSS8:
.\fastboot flash logo name .img

Worked on all my Xiaomi.
[General Questions and Answers] nepires:
Duplicate thread. Original: https://xdaforums.com/t/firmaware-stock-rom-of-xgody-mate-30.4315507/
[General Questions and Answers] Deleted member 1890170:
This thread is duplicate to this

https://xdaforums.com/t/firmaware-stock-rom-of-xgody-mate-30.4315507/#post-85435251
[Nook Touch General] nmyshkin:
What fun! Windows 10 and the NST :)

I find that I cannot negotiate ADB access via USB any longer. I don't know when that started, but it looks like maybe sometime in June. These events are displayed in the Device Manager when accessing "Portable Devices":

Driver Management has concluded the process to add Service WUDFWpdFs for Device Instance ID SWD\WPDBUSENUM\_??_USBSTOR#DISK&VEN_B&N&PROD_NOOK_SIMPLETOUCH&REV_0100#7&22272E47&0&3012440020143004&0#{53F56307-B6BF-11D0-94F2-00A0C91EFB8B} with the following status: 0.

Device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_B&N&Prod_NOOK_SimpleTouch&Rev_0100#7&22272e47&0&3012440020143004&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b} was not migrated due to partial or ambiguous match.

Last Device Instance Id: SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_B&N&Prod_NOOK_SimpleTouch&Rev_0100#3014760074133009&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}

Class Guid: {eec5ad98-8080-425f-922a-dabf3de3f69a}

Location Path:

Migration Rank: 0xF000FFFF0000F102

Present: false

Status: 0xC0000719

Device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_B&N&Prod_NOOK_SimpleTouch&Rev_0100#7&22272e47&0&3012440020143004&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b} requires further installation.

It's not beyond belief that the spate of major updates to Windows 10 recently trashed my ability to access the device via ADB/USB. The question is: how to fix it?

On the NST I have the following:

service.adb.tcp.port -1

persist.adb.tcp.port 0
[Nook Touch General] Renate:
All that stuff indicates that the NST is presenting as UMS.

Have you used UsbView.exe to see what interfaces are being presented?

Have you looked at sys.usb.config, sys.usb.config?

That stuff with adb.tcp is only for ADB over TCP (WiFi).
[Nook Touch General] nmyshkin:
Mmm....is that in your signature (NOT)?

And this is where?

I should have added that none of my three NST/G devices is connecting properly now (other than as USB file transfer devices) whereas all were formerly able to negotiate USB debugging and ADB.
[Nook Touch General] Renate:
UsbView.exe is the venerable Microsoft utility, to be found here: https://ftdichip.com/wp-content/uploads/2020/07/usbview.zip

You can also look in Windows Device Manager (devmgmt.msc), especially in "View > Devices by Connection"

Either OmapLink.exe or ImxLink.exe (in sig) will show you if ADB is showing (err, conditional upon the driver being loaded?)
[Nook Touch General] nmyshkin:
This is the result from omaplink (green dot for ADB, black for UMS):

Waiting for bootloader or Fastboot or ADB...
ADB version: 01000000, payload: 4096, type: device
uid=0(root) gid=0(root)

In DeviceManager/Devices by Connection, the Nook shows up as a USB composite device.

And I've attached a screencap from usbview.
[Nook Touch General] Renate:
Well, OmapLink/ImxLink found your rooted device.

You do have only one Android plugged in?

What part of ADB is not working?

What version adb.exe are you using?

If the version is stone age it goes by VID/PID and it doesn't know about B&N.

C:\>adb version
Android Debug Bridge version 1.0.41
C:\>adb devices
12345678

Version is not that critical, but should at least be in the high 30's.

(For UsbView you want to click on the device so that you see interesting things in the right panel. But we're past that step.)
[Nook Touch General] Renate:
Wait, are you talking about UMS not working, not ADB?

Oh, don't tell me that you use UMS?

The NST presents two drives but there may not be anything mounted.

Run Disk Manager (diskmgmt.msc) and see if there are drive letters but nothing inside them.
[Nook Touch General] nmyshkin:
This is the result from omaplink (green dot for ADB, black for UMS):

Waiting for bootloader or Fastboot or ADB...
ADB version: 01000000, payload: 4096, type: device
uid=0(root) gid=0(root)

In DeviceManager/Devices by Connection, the Nook shows up as a USB composite device.

And I've attached a screencap from usbview.

Unless I am transferring a library book with ADE I like to keep UMS turned off since it locks you out of interacting with the screen while debugging...which now isn't happening for some unknown reason.

I try to do most file transfers wirelessly to save wear and tear on the USB jack.

So, yes, I am talking about ADB. "Device not found" is all I get now. I'll check on the version later today but I don't see why a version which was working just fine before should suddenly stop. Unless its Windows' fault.
[Nook Touch General] Renate:
Ah, ok.

It's definitely a problem with your adb.exe

OmapLink/ImxLink can find your device, connect and even do shell commands (id).

Those programs, unlike AdbSync, do not go through the ADB port 5037 of adb.exe like a normal ADB client does.

If you actually have adb.exe connected OmapLink/ImxLink won't be able to connect to the already connected device.

So this all means tht your WIndows drivers are fine.

You might have had a few copies of adb.exe and one of them got deleted or the PATH changed or a backup restored the wrong one or...

Also, there was that old C:\Users\Person\.android\usb_adb.ini file which was used by old versions of adb.exe

But you don't want/need that anymore, so forget that I mentioned it!
[Nook Touch General] nmyshkin:
ADB version is 1.0.31 (Minimal ADB and Fastboot)

Just to see, I connected up my regular non-Nook tablet and ADB saw the device right away. So the issue is definitely with the NST or the interface of the NST with Windows.

I actually do have that usb_adb.ini file, but again, why work with everything else and "suddenly" stop working with the NST?

When UMS is turned off, I do see the two "empty" drives (internal and sdcard) in Windows when I connect via USB.
[Nook Touch General] Renate:
Marshmallow came out in October 2, 2015.

That had ADB version 1.0.32

That was the first public release that eliminated vendor white-listing that was changed in November 21, 2014.

I could tell you how to fix the adb_usb.ini, but you really should just update a half decade or so.
[Nook Touch General] nmyshkin:
Huh.

So I updated Minimal ADB and Fastboot to v.1.43 which is ADB version 1.0.39. And it worked right away. I still don't see why the previous version just stopped working with the NST. Like so much else in life, it makes no sense.

Anyway now I have another issue, for this version came with a genuine Windows installer and my previous version was a "dump into the folder of your choice and set up the paths". I'm wondering if it's safe to just delete that entire folder now (probably have to clean up the path statement too...). Ugh.
[Nook Touch General] Renate:
Once upon a time, adb.exe and fastboot.exe were completely standalone.

Now they require AdbWinApi.dll, AdbWinUsbApi.dll

They also require:

api-ms-win-crt-private-l1-1-0.dll
api-ms-win-crt-runtime-l1-1-0.dll
api-ms-win-crt-stdio-l1-1-0.dll
api-ms-win-crt-convert-l1-1-0.dll
api-ms-win-crt-string-l1-1-0.dll
api-ms-win-crt-environment-l1-1-0.dll
api-ms-win-crt-filesystem-l1-1-0.dll
api-ms-win-crt-time-l1-1-0.dll
api-ms-win-crt-utility-l1-1-0.dll
api-ms-win-crt-heap-l1-1-0.dll
api-ms-win-crt-locale-l1-1-0.dll
api-ms-win-crt-math-l1-1-0.dll
api-ms-win-crt-multibyte-l1-1-0.dll

But these should already be found in the Windows "downlevel" directories.

There's no need to be adding to PATH for every little thing.

If you are invoking adb/fastboot from the command line, you might consider using doskey:

Regedit HKCU\Software\Microsoft\Command Processor AutoRun=\wherever\my-autorun.bat

doskey /macrofile=\wherever\my-aliases.txt

adb=C:\some-sort-of-path\adb.exe $*
fastboot=C:\some-sort-of-path\fastboot.exe $*

Edit: I forgot the arguments ($*).

If you are invoking adb/fastboot from a bat or makefile just put the full path in some define.
[OnePlus Nord 2 5G] NinadPalekar:
Hello guys

Can anyone share games.apk here for OP Nord 2 device..I had accidentally deleted the app & now im unable to launch Pro gaming mode.

Thanks in advance..cheers!
[OnePlus Nord 2 5G] Jivyanshu:
Facing the same issue!! You got any solution for it?
[OnePlus Nord 2 5G] NinadPalekar:
Yes got it from some random youtuber description!
[OnePlus Nord 2 5G] HofaTheRipper:
Here is my apk:
[OnePlus Nord 2 5G] NinadPalekar:
Hello guys,

Parallel app & clone app not supporting to OP Nord 2.

Any other alternatives for Whatsapp or other app?

Cheers!!
[OnePlus Nord 2 5G] Pouic:
Apparently this is a known bug for now of the Clone App according to all the many posts in the OnePlus forums , I think we'll have to wait the next OTA for them to resolve this :(
[OnePlus Nord 2 5G] NinadPalekar:
Cool thanks for the update!
[Samsung Galaxy A40 ROMs, Kernels, Recoveries, & Ot] physwizz:
physwizz_kernel a40_R_v3.0

Stable version

For OneUI 3.1 or GSI

@physwizz

-Most securities disabled

-CPU Governors: conservative, ondemand, userspace, powersave, interactive, performance.

-Interactive is default governor

-SE linux enforcing

-CPU overclocked and underclocked

-Big: 312 - 2080

-Little: 208 - 1690

-GPU: 343 - 1300 without custom dtbo

-Low battery drain

-lz4 compression default on zram

-mtp for GSIs(from topser99)

-works with stock dtbo.img

Use stock dtbo.img from your baseband (not your kernel or your ROM)

Installation

1. Upgrade or install Android R

2. Install kernel from TWRP

3. Install Magisk for root

4. Reboot

GitHub

physwizz - Repositories

physwizz has 284 repositories available. Follow their code on GitHub.

github.com
[Honor View 10 Questions & Answers] break0x90:
hi to all,

i need to connect this phone by cable to TV. I'm looking for info about this kind of connection but i think to understood that the phone has usb-c 2.0 connector and using usb-c to hdmi cable doesnt works. It's right ?

Is there any way to connect this phone by cable without using devices like chromecast ? maybe an MHL adaptor ?

thanks !
[ASUS ZenFone 8 Flip] MystikMan97130:
Hello, can I have a RAW firmware for the Asus Zenfone 8 Flip ZS672KS. I would like to create root apps for study but I'm afraid to do something stupid and it won't start anymore. Thank you in advance, I also have the Zenfone 7 Pro ZS671KS I found for it but I cannot find for the 8 Flip.
[ASUS ZenFone 8 Flip] Oswald Boelcke:
@MystikMan97130 Sir, I've changed the prefix to "Question". Please don't change it back. Thanks for your cooperation.

Regards

Oswald Boelcke

Senior Moderator
[ASUS ZenFone 8 Flip] KAS995:
I downloaded the raw firmware and have it on my system I'd probably need to put it on Gdrive and send it over
[ASUS ZenFone 8 Flip] MystikMan97130:
Oh good, thanks, i waiting your link
[ASUS ZenFone 8 Flip] MystikMan97130:
My phone is locked in QDLOADER after Android 12 update can you send me Raw firmare please?
[ASUS ZenFone 8 Flip] Ak0monoper:
Would you be able to send me a link to the raw firmware as well please?
[ASUS ZenFone 8 Flip] KAS995:
Sorry for the wait... Took me a while to recover the files I lost in my operating system but managed to get everything back... Should have the raw data by the end of the day. I know how stressful your situation can be so if I don't get back to you by the end of the day. Do not hesitate to spam message me. Lol on this occasion I won't mind better I'm reminded that way
[ASUS ZenFone 8 Flip] MystikMan97130:
Hello, is upload link is ready?