yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] jawonder:
So i don't see Note 20 Ultra 5G N986U1 . I see Note 20 Ultra SM N986U and Note 20 Ultra 5G SM N9860.
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] ifly4vamerica:
Yep that's what I used. If the first set of I structions from reddit don't work just use the second method.

Probably best not to derail this thread anymore. If you still can't get it from those instructions PM me. Not sure how much help I can be though as that second set of I structions worked for me first try.
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] jawonder:
You use SM 986U ?. that's the one in list without 5G ?. I used SM 986U but it didn't work , when I went back yo timing it was showing "Edit device fingerprint active". My device is showing as SM N986U . how do i remove and go back to original prop ?.
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] ifly4vamerica:
All that information is in the instructions I linked ..

Go back and do the second method that was in the reddit link.
[Xiaomi Mi 9 Accessories] apoklyps3:
has anybody found a 3rd party cable able to charge turbo the MI9 ?

I'm interested in getting a longer cable as the original one is extremely short.

Got a usb-A to usb-C 200cm PZOZ 5A a long time ago from aliexpress, but tested it now and it does't even do fast charging with the 27W adapter, letalone turbo :(
[Xiaomi Mi 9 Accessories] leledumbo:
Baseus has several 100W 200cm cables, but they're PD compatible instead of QC 4.0 actually and the head are both USB C. So you'll need a USB C >=27W adapter as well.
[Xiaomi Mi 9 Accessories] apoklyps3:
I already have the 27W charger, but it has an A type USB port on it.

don't think xiaomi uses QC4.0 provided by qualcomm
[Xiaomi Mi 9 Accessories] Dariusdd:
The original 27W charger included with the CN version of the phone is actually using QC3.0, it's still within that spec. Maybe that will narrow it down?
[Xiaomi Mi 9 Accessories] leledumbo:
Yes, Xiaomi's 27W charger has USB A connector.

Don't think when 1st party data is available: https://www.qualcomm.com/media/documents/files/quick-charge-device-list.pdf
[Xiaomi Mi 9 Accessories] kinak:
I used Baseus Cable. Support Turbo Charge with Xiaomi and Huawei. Not support with fast charging Samsung and other
[Google Pixel 5 Questions & Answers] nico22320:
Hi,

Someone have try EdXposed on pixel 5 or other Android 11 devices ?
[Google Pixel 5 Questions & Answers] roweboat56:
Yes I've installed it, though not many modules working or useful for Android 11 sadly.
[Google Pixel 5 Questions & Answers] nico22320:
What version of EdXposed have you install ? Sandhook or other ?

What are steps for install ?

Thanks
[Google Pixel 5 Questions & Answers] p0tato112:
Hi, can someone help me? I have edxposed on Android 11 and a few of the modules that I have work fine - including one for jasipatcher, one to enable a debug menu in the camera app and a few more. Recently I tried to download a few modules from the modules section of edxposed manager that disable flag_secure so that I can take screenshots in apps like Netflix. However, none work, not after restarting the phone, just generally don't. I tried several different ones and not a single one does anything. Is there any additional thing I need? If Xposed wont work then how do I disable flag_secure? Thank you
[Google Pixel 5 Questions & Answers] swangjang:
It's probably because those modules aren't updated to be compatible with android 11.
[Google Pixel 5 Questions & Answers] p0tato112:
Oh, I forgot to say here: I got it to work. I don't know why it suddenly started working, maybe it's because I got a magisk module called liboemcrypto.so disabler and restarted, but either way it's fine now.
[Xiaomi Poco X3 NFC Questions & Answers] atifnr:
Where can I get Poco X3 firmwares to flash custom ROMs , I mean only the firmware and not the whole ROM to whom I have to flash via fastboot.
[Xiaomi Poco X3 NFC Questions & Answers] veimus:
https://sourceforge.net/projects/nitrogen-project/files/surya/11.0/firmware+vendor/
[Xiaomi Poco X3 NFC Questions & Answers] pnin:
You could also try the following:

.
[Xiaomi Poco X3 NFC Questions & Answers] yuri0r:
I hope this does not count as necro bumping but how can I tell the difference between Europe and Global version?

my model number is M2007J20CG but I could not figure out the rest.
[Xiaomi Poco X3 NFC Questions & Answers] ThatDamnFrog:
From what I've heard..., the EUROPE version is a custom rom based on MIUI and is debloated.
[Xiaomi Poco X3 NFC Questions & Answers] yuri0r:
so I can flash either firmware? the only thing I know for certain is that I don't have the Indian version (my X3 was a present)
[Xiaomi Poco X3 NFC Questions & Answers] jeryll:
install Orange fox recovery, boot into it, look at the initial screen, find out the row with text fingerprint: there you can see your actual fw and QJGMIXM is what you should look for and flash firmware with tag QJGMIXM (or whatever you'll see there on your phone)
[Xiaomi Poco X3 NFC Questions & Answers] pnin:
Just to clarify this: ThatDamnFrog seems to be confusing the custom Xiaomi.eu ROM with the European version of the official MIUI stock ROM.

The European official ROM (marked with a QJG

EU

XM code) is different from the real MIUI global ROM (which has a QJG

MI

XM code).
[Xiaomi Poco X3 NFC Questions & Answers] ThatDamnFrog:
Oh yeah my bad...sorry for that one @yuri0r
[General Topics] Piauf:
is there a way to reset or to avoid the password on bsquare login page, cause i have locked it somehow and dont know how to enter to it cause i dont remember the password...

Also maybe someone knows the standart password for this thing,cause it might fit?

Thanks.
[Advantage X7500, MDA Ameo ROM Development] Tuco:
hi all,

I have used the function tries but perhaps I have read too much,

like making in order to pass from spl1.2 sp to 3.5

thanks,
[Advantage X7500, MDA Ameo ROM Development] Tuco:
ok all resolving..
[Advantage X7500, MDA Ameo ROM Development] MrBond007:
How to downgrade SPL from 3.5 - 1.2???
[Advantage X7500, MDA Ameo ROM Development] sergiopi:
click here :)
[Advantage X7500, MDA Ameo ROM Development] MrBond007:
Thank you :)
[Advantage X7500, MDA Ameo ROM Development] MrBond007:
By the way, I have some questions about Bluetooth.

My device HTC X7500: ROM ver AP 4.0 Platinum, Radio ver 1.50, SPL 3.5 by Olinex.

I have paired my device to BlackBerry 8100. BB 8100 send file to my device is ok, but my device could'n send file to BB 8100...?

Sorry...my english is not good. Thanks
[Advantage X7500, MDA Ameo ROM Development] Tuco:
also I have had the problem, I have resolved with MoBlue
[Advantage X7500, MDA Ameo ROM Development] cottinghamm:
Other than trying to re-flash AP4 (which doesn't want to work between my PC and Athena) is there another way to go from 1.2 to 3.5 ?

The CMonex tool for going the other way is really easy, is there one to upgrade ?
[Moto G7 Play Questions & Answers] andyhoy:
Money. $$$$$$$$$$$$$$$$$$$$$$

I need HELP in de-soft-bricking my Moto Play G7 and installing the /e/ project (or perhaps other Linux-based build), and I am willing to PAY for tech support to walk me through it (ideally via Skype or Zoom platform). Here are a few more specifics:

I bought a used Moto G7 Play that was updated by a developer from Android 9 to Android 10. I followed tutorials to unlock the phone and install TWRP via ADB but ran into problems, as far as I can tell, due to the Motorola A-B slot issue (it says "No bootable A/B slot, failed to boot Linux, falling back to fastboot" when I try to reboot). I can no longer recover the phone to Android or reset it to "factory" settings via the bare-bones Android and Motorola phone menus, but I remain able to issue commands via ADB / USB and also navigate to the G7's bootloader menus by using the buttons on the side of the phone. As for my PC platforms, I am running Win 10 (with ADB) but I also have Ubuntu running (so I could format SD cards to ext4 if that would help), and I have Android studio installed (not as if I know what to do with it), if that would be of any help. As far as I can tell, ADB and the Motorola USB drivers are working fine, and I USUALLY get positive indication when I type "adb devices", and I can always get the phone to acknowledge that the USB is connected/disconnected.

I don't know if this will help, but as I try to do the ADB sideload for copy-partitions.zip, this is where things don't work, as my Moto G7 play screen says:

Finding update package…

Opening update package…

Verifying update package…

E:footer is wrong

Update package verification too 0.2 s (result 1).

E: Signature verification failed

E: error:21

Installation aborted.

From there, it seems I can't go on to flash the TWRP image. Any ideas how I can work past these problems? Let me know how I can contact you via the forum and we can work $omething out. I'm guessing that this is a fast fix for someone who knows what they are doing. I'm sick of google and don't want to accept defeat! Thanks, -Andrew
[Moto G7 Play Questions & Answers] maw1:
Try the motorola rescue assistant

When it not workling download for your device the firmware
[Moto G7 Play Questions & Answers] xtermmin:
Instead of flashing TWRP, have you tried just booting TWRP w/o flashing?

fastboot boot twrp.img
[Moto G7 Play Questions & Answers] Exinu:
I ran into some problems with my Moto G7 Play; I didn't softbrick it, but several things fought back, so I'll pass along what may get you back on track. First of all, I cannot use Linux to connect via fastboot, so I had to use a Mac, you can use your Windows box. Secondly, TWRP does not officially have a version for the G7 Play. I used an unofficial one from an XDA forum member HERE. It only offers a black screen unless you flash dtmo.img. I didn't want to flash dtmo.img, so I just used the black screen and used adb commands to install Lineage (and /e/) via TWRP command line.

The steps are pulled from another XDA posting showing how to use TWRP command line:

1. Connect the phone in fastboot mode to the PC, run fastboot devices to make sure it is connected.

2. Type: fastboot set_active b

Then: fastboot boot <your_recovery.img>, e.g. fastboot boot twrp.img

<phone will reboot, the screen will be black>

<wait to Windows new device sound>

3. Type: adb shell

twrp wipe cache << will not work on Moto G7 Play, but won't hurt anything.

twrp wipe dalvik

twrp wipe system

twrp wipe data <- NOW YOUR DATA WILL BE REMOVED, SO MAKE A BACKUP BEFORE!

twrp sideload

adb sideload <location_of_your_ROM.zip>, e.g. adb sideload C:\lineage-xyz.zip

IF THE TWRP commands do not work and hang saying something about "starting TWRP", I discovered by looking at the log in /tmp that /sdcard is encrypted. You will need to unencrypt /sdcard and I'm not sure how to do that without recovery; I'm sure there is way, though.

If I were you, I would see if you can flash LineageOS (or lineageOS + microG) with this method to get your phone back working, then you can move on to /e/. Note that if this works, you will have a recovery program available (the standard Lineage recovery), which has some basic tools. You CAN ONLY load Lineage-signed roms with this recovery. So if you want to switch from lineage to /e/ or to lineage+microG, you will need to use the twrp method above to switch to the other rom. Then you can use the lineage or /e/ recovery to install lineage or /e/ updates from the same publisher.

Also, if you install stock lineage, don't use a bleeding edge version. Pick one from mid-October so if you decide to switch to /e/ or Lineage+microG you will not be downgrading because they don't make nightly builds. It probably won't hurt since downgrading a week probably has few changes, but just in case.

Hope this helps.
[Moto G7 Play Questions & Answers] andyhoy:
I tried the Motorola Device Manager tool. Not sure if I made a good backup to begin with, and now I try to open the tool it doesn't seem to do anything.
[Moto G7 Play Questions & Answers] andyhoy:
Tried that... It says it FAILED.

C:\adb>fastboot boot twrp.img

downloading 'boot.img'...

OKAY [ 0.427s]

booting...

FAILED (remote failure)

finished. total time: 1.054s
[Moto G7 Play Questions & Answers] Exinu:
I think you may have several issues that need to be fixed one step at a time. First, I think you have an old fastboot if it doesn't recognize the set_active command. Go to this link: https://developer.android.com/studio/ and scroll down to the section labeled "Command Line tools only" and download the command line tools. Make sure you are in that directory in Windows so you are running the newer version and not the old version installed. If you run "fastboot --help" you should see set_active as an option.

Next, where did you get the TWRP? Go to the link I provided, which has a (black screen) TWRP that I have used and it works. Start from there and see how things proceed.
[Moto G7 Play Questions & Answers] Exinu:
The command-line tools download should not require any installation; at least, the Mac version did not. Unzip the file to your desktop. Then open a command prompt which should open in c:\Users\your_user . Enter "cd Desktop" to change to the Desktop folder, then cd <foldername> to change into the folder you unzipped the files into. Windows will sometimes unzip a folder into a second folder, so you may need to cd <foldername> once more. In any case, enter "dir" to make sure you see files like fastboot.exe, adb.exe, etc.

In Windows, when you type a command it will first look to your current directory and run the exe file that exists there, if it exists. If it does not, then it starts looking for the command in your %PATH% environment variable. That's why you need to "cd" to the tools directory: when you run "fastboot", you want it to run fastboot.exe in that directory, and not the old fastboot.exe that is installed somewhere on your system.

It sounds like you haven't worked with the command line much; I suggest you go through some tutorials on basic command line usage for both Windows and Linux; it will make tinkering with computers and phones much easier. And set_active is not a DOS/Windows command, it is parameter you are passing to fastboot.exe to tell it what action you want it to do; it just also calls these actions "commands". So when you typed c:>set_active, you told Windows to find a file called set_active.exe and run it. That file does does not exist, so it did not work.

Quick note: the Unix command line will not run a command from the current directory for multiuser security reasons; you need to specify the current directory (dot) and a slash on the command like this: ./fastboot

This will also work with DOS/Windows, but usually the backslash is used instead of the forward slash, for very old historical reasons.
[Moto G7 Play Questions & Answers] Exinu:
You are getting close. Your fastboot entry is a little off. It should be >fastboot boot <filename.img>. If the twrp img file is not in the current directory, you will need to provide the full path.
[Moto G7 Play Questions & Answers] andyhoy:
OK, so that was a head-slapping "duh" moment on my end (using fastboot filename.img instead of fastboot boot filename.img). However, now that I've entered the right command I'm still having problems. As you indicate in your post above, the "fastboot boot" command did initiate the sequence, and the screen did go black, however, one of the screens that it went to only said "bad key" at the upper left hand corner.

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp-dirtyport-g7play.img

downloading 'boot.img'...

OKAY [ 0.575s]

booting...

FAILED (status read failed (Too many links))

finished. total time: 1.580s
​

As for my phone screen, it goes black and cycles saying "bad key" a few times, and after a few attempts it reverts to the Bootload logs screen, giving the same message it did that I started with.

Start Up Failed​

Your device didn't start up successfully.

Use the Software Repair Assistant on computer

to repair your device.

Connect you device to your computer to get

the Software Repair Assistant.
​

AP Fastboot Flash Mode (Secure)

No bootable A/B slot

Failed to boot Linux, falling back to fastboot

Fastboot Reason: Fall-through from normal boot mode

USB Connected
​
[Moto G7 Play Questions & Answers] andyhoy:
OK, I after the "dirtyport" image didn't work, I went out on a limb and tried to flash a different img file, (first doing the set_active b command), typing:

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp-moto-g7-play-channel-android-10.img

downloading 'boot.img'...

OKAY [ 0.496s]

booting...

OKAY [ 0.178s]

finished. total time: 0.679s
​

It briefly flashed the Moto screen and then went black. After this, with the black screen, it seemed like it was able to the "adb shell" command, although it seemed to not be able to take the TWRP commands:

C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell

* daemon not running; starting now at tcp:5037

* daemon started successfully

channel:/ # twrp wipe cache

Unable to find partition for path '/cache'

Done processing script file

channel:/ # twrp wipe dalvik

Failed to mount '/data' (Invalid argument)

Done processing script file

channel:/ # twrp wipe system

E:Error with wipe command value: 'system'

Done processing script file

channel:/ # twrp wipe data

Failed to mount '/data' (Invalid argument)

Done processing script file

channel:/ # twrp sideload

C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload lineage-17.1-20201129-nightly-channel-signed.zip

Total xfer: 1.00x
​

After this point it went back to the "bad key" and return to the Bootloger logs screen.

I'm assuming at this point if there is a failure in the TWRP command sequence (as suggested above) I shouldn't expect the latter commands to work. I also attempted to use the moto g7's built-in recovery menu that is available from pushing and holding the power and upper volume button. When I tried to "apply update from ADB" using the phone to initiate the effort, and then typed, C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload lineage-17.1-20201129-nightly-channel-signed.zip, the phone screen read as follows:

Supported APR: 3

Stopping adbd...

Now send the package you want to apply to the device with the "adb sideload ,filename"...

Finding update package...

Opening update package...

Verifying update package...

E: failed to verify whole-file signature Update package verification took 45.2 s (result 1).

E: Signature verification failed

E: error: 21

Installation aborted.
​
[Moto G7 Play Questions & Answers] andyhoy:
Even though I was getting errors after the "WIPE" command, it seems like the adb shell is bringing about a linux-esque terminal of the channel image and I can see the files/directories. Using the LS command it seems that the folders you are mentioned are empty, with the exception that there is no "dalvik" directory:

C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell

channel:/ # twrp

TWRP openrecoveryscript command line tool, TWRP version 3.3.1-0

Allows command line usage of TWRP via openrecoveryscript commands.

Some common commands include:

install /path/to/update.zip

backup <SDCRBAEM> [backupname]

restore <SDCRBAEM> [backupname]

wipe <partition name>

sideload

set <variable> [value]

decrypt <password>

remountrw

fixperms

mount <path>

unmount <path>

print <value>

mkdir <directory>

reboot [recovery|poweroff|bootloader|download|edl]

See more documentation at https://twrp.me/faq/openrecoveryscript.html

channel:/ # ls

acct config etc init.rc init.recovery.usb.rc persist plat_service_contexts res sideload tmp vendor_file_contexts vndservice_contexts

bin d external_sd init.recovery.hlthchrg.rc license plat_file_contexts postinstall root storage twres vendor_hwservice_contexts

bugreports data file_contexts.bin init.recovery.mksh.rc mnt plat_hwservice_contexts proc sbin sys ueventd.rc vendor_property_contexts

cache default.prop firmware init.recovery.qcom.rc odm plat_property_contexts product sdcard system usb_otg vendor_seapp_contexts

charger dev init init.recovery.service.rc oem plat_seapp_contexts prop.default sepolicy system_root vendor vendor_service_contexts
​

Here are the directory contents:

channel:/ # cd data

channel:/data # ls

channel:/data # cd /

channel:/ # cd cache

channel:/cache # ls

channel:/cache # cd /

channel:/ # cd system

channel:/system # ls

channel:/system # cd /

channel:/ # cd dalvik

/sbin/sh: cd: /dalvik: No such file or directory
​
[Moto G7 Play Questions & Answers] Exinu:
When you went into recovery mode, was it Motorola's stock recovery or LineageOS's recovery (with the Lineage logo (the three circles))?

In any case, at least you have a working recovery. Error 21 simply means that the signature is on the firmware file is not what it was expecting. If you have a Motorola recovery, then it expects a Motorola-signed firmware. If it is the Lineage recovery, then it will only flash Lineage-signed firmware.

Your TWRP sideload command sure looks like it worked when it loaded the firmware, but if it had worked, you would have LineageOS recovery and it would say current slot: a. I don't remember if the stock Motorola recovery displays the current slot. When you tell fastboot to set_active b, it sets the current slot to b and then when you install the firmware it installs the firmware to slot a.
[Moto G7 Play Questions & Answers] andyhoy:
Exinu,

It looks like the fastboot set_active b command worked, in that my phone acknowledged it did, and the command prompt seemed to indicate the same. As for the phone screen, the Moto splash screen that flashed quickly (probably less than 1 second) did not have any hint of Lineage logo. I tried repeating the process and saw the logo a total of 3x. It was the C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp-moto-g7-play-channel-android-10.img command that got me there (the "dirtyport" image you suggested didn't work) and it was before the attempt to flash the lineage image.

However, as for the ADB SHELL commands that you recommended, it didn't seem like they were doing what one might expect. Subsequent to the attempted TWRP commands in the shell, I tried to sideload the lineage system but it would not take, saying "bad key" on the upper LH side of the screen.

Is it possible that prior image flashing attempts have left some incompatible clutter on my phone (perhaps visible by means of exploring other folders or folder names via the ADB SHELL)? I've been working with Raspberry PI's and PC based OMV / Nextcloud servers in recent months and perceive that new installs seem inclined to revert to old files on occasion if not thoroughly formatted.
[Moto G7 Play Questions & Answers] Exinu:
One thing I forgot to mention: since you are installing Lineage, you can use the Lineage recovery to install it. TWRP is only necessary for /e/ or other roms that do not have their own recovery. Try "fastboot boot" but specify the lineage recovery file.
[Moto G7 Play Questions & Answers] Exinu:
Also, now that I review things again, I may have used this TWRP instead of the "dirty port" version. I don't know if it will make a difference, but it might be worth a try. Sorry, I guess I have too many irons in the fire right now and got it mixed up. Scroll down to abou t the third or forth comment and there is a google drive link. You just need the recovery.img. Do not flash the dtmo.img, just fastboot/boot the recovery image: https://xdaforums.com/t/recovery-tw...y-custom-recovery-kernel-source-code.3933680/