yashsingh1/xdaforums huggingface dataset:
[Redmi Note 9 Questions & Answers] ayushshrivastav:
Thanks man, it worked!

Do you also happen to know the command for "power button locks instantly" in adb?

My phone locks after 5 seconds of pressing the power button, and I can't seem to find which adb shell setting I have to tinker with.
[Redmi Note 9 Questions & Answers] Aleksandar123123:
bro im in computer science 1st year and now i feel like im android developer, thank you , this should work for everyone
[Redmi Note 9 Questions & Answers] Satbeginner:
Hi, thanks!!

Worked for me on my Xiaomi Note 9T running the EU version 12.0.7.0 :-)

Thanks,

Leo
[Redmi Note 9 Questions & Answers] spiral mind:
On a MAC use ( ./adb shell ) instead of ( adb shell )command. Worked on my Xiaomi Redmi Note 9T. Thanks dude!!!
[Redmi Note 9 Questions & Answers] mrakovuki:
PLEASEE HELP, i did all this and when i put the code in it says something like camillion and a dolar sign and idk what to do next. when i just exit the application it does nothing. ( im using a Note 10 but theres no other tutorial for that model) pls help!!!!!
[Redmi Note 9 Questions & Answers] mrakovuki:
also im using a note 10 but this is the only tutorial online
[Redmi Note 9 Questions & Answers] Noor_ul_Hafeez:
Just logged into XDA to say thanks to you. You are a life saver i was thinking about changing my device... It is perfect now . It no longer turns on by itself when raise to wake is disabled. I wish xiaomi was smarter than u lol😁😁😍😍
[Redmi Note 9 Questions & Answers] wolfskate:
To anyone with Xiaomi phone that could not turn off the "Raise To Wake Up" feature,

THE COMMAND LINE WORKS!

I have the Poco X3 GT with the exact same issue

Just follow the instruction given and it will solve the issue.

I can't thank you enough logan3103
[Redmi Note 9 Questions & Answers] mohsenghq:
Tnx it's worked for me
[Redmi Note 9 Questions & Answers] mohsenghq:
TNX guys worked for me
[Redmi Note 9 Questions & Answers] amitrin:
I just executed this and it worked. Great help, thx.
[Redmi Note 9 Questions & Answers] limovsky_70:
I have to buy a new phone after the A51 dies, and the option was POCO M5 with this issue of the wake up screen. Made the steps using the instructions and work like charm. Thank you guys!
[Redmi Note 9 Questions & Answers] Carcharoth_KSP:
Hi, just letting this here to help the next guy with a more detailed info, for dummies if you like ;)

I bought two Xiaomi POCO M5 from the official Xiaomi "store", after all the updates to MUI 14.0.1 one had the "Rise to wake" always on, no matter who many times you activate or deactivate this feature, reboot the phone... the phone always turned on when you move it, but the other phone works perfectly.

OG tutorial by @logan3103 I just put extra info working on W10

1- Activate developers options on your phone.

For this you have to open Settings>About phone and tap on MIUI Version for about 7-10 time (it will notify you that the developer mode will be activated if you keep tapping).

Now you go back to settings>adittional settings > Developer Options.

Activate:

USB Debugging

USB Debugging(Security settings) For this last one you have to be logged in your MI account (just go to settings>Xiaomi Account and log in "with google", for simplicity).

2- Download and install "Universal ADB Drivers" from "clockworkmodDOTcom"

Download "SDK Platform tools" from "developerDOTandroidDOTcom" (called "ADB files" on OG tutorial).

Extract the "SDK Platform tools" files.

3- Open CMD as an administrator (just to be sure) on the directory where you have extracted the "SDK Platform tools" or "move" yourself using MS-DOS commands to the directory with "adb.exe, AdbWinApi.dll, ...... " inside of it.

4-Connect your phone with a USB cable

Select File transfer Android/Auto on the phone prompt.

5- In the CMD window, enter the following commands:

adb devices

You should get a prompt on your phone to allow (or deny) USB Debugging. Allow it and re enter on command prompt the "adb devices" command.

Now you should see your phone serial number (this means everything is working).

adb shell

settings put secure wake_gesture_enabled 0

exit

Close the CMD window.

"Eject" the phone from windows (like it is a USB drive), if it fails to eject the phone open W10 task manager>details look for adb.exe and kill the process, try ejecting it one more time.

Remove the USB lead.

For security deactivate both debug options on the phone, then deactivate developer mode

And that`s all. Your phone screen should stay locked when you move it at this point.

Hope this helps you.
[Android Q&A, Help & Troubleshooting] s4goa:
They say, that unfortunately, a majority of new Unisoc (Spreadtrum) chips have bootloaders that cannot be unlocked without a key, which is not provided by the SoC manufacturer, and is beyond the control of the ODM. Many low-end Android smartphones are powered by such chips, and the end result is that root is impossible on those devices, i.e. ZTE Blade A5 2019, Doogee N10, etc. (Unisoc SC9863A)

Some have obtained the source code of the U-boot bootloader used on those devices, however, the algorithm for the key verification is stored on the Trusted Execution Environment, which means it cannot be extracted (the TEE is a SecureEnclave-like device, with no possible direct access to it's memory or storage, besides de-capping it and reading the bits with an electron microscope) -- more info here: https://source.android.com/security/trusty

However, Spreadtrum actually does verify the whole boot process, meaning that booting a modified binary is impossible. If you change the boot partition, it will infinitely reboot with a black screen and vibration. If you leave the boot as-is, but change system, it will get to the splash screen and then reboot. etc.

It genuinely does cryptographicaly verify the signature and hash of every partition. Which is great for security, in theory, unless the OS has preloaded spyware, but the secureboot process prevents you from removing it.

Been there, and I didn't even realised the cause.

MTK is quite good, but it's becoming worse in the perf/$ ratio, i.e. the SC9863A is a octa core A55 chip at 1.5GHz, while similar MTK devices are dual core A7 at 1.2 GHz. The architecture improvements alone are excellent, not mentioning the extra cores and higher clock speed.

The key is most certainly not the same, because I doubt they would go through the trouble of doing actual secure boot verification, and storing the data in the TEE, and just have the same key. Additionally, the U-boot code I obtained lies to the user about commands not being found, if the command doesn't contain a valid unlock key. :(
[Android Q&A, Help & Troubleshooting] CG_Tech:
there is a dedicated thread on hovatek forum for rooitng this chipset
[Android Q&A, Help & Troubleshooting] s4goa:
that thread on hovatek is thrilling...
[Android Q&A, Help & Troubleshooting] TrenchFullOfSlime:
Hovatek forums indicate you need a PAC or FDL file to do anything unless you buy extra hardware. Can anything be done for a vendor that hasn't released either? Even a temproot exploit like mtk-su is fine, if it works on Android 9.
[Android Q&A, Help & Troubleshooting] s4goa:
those El-Cheapo phones are simply not supported well by hackerdom.
[Android Q&A, Help & Troubleshooting] Skorpion96:
if we can port mtk-su to this processor or create a new temp root we are done
[Android Q&A, Help & Troubleshooting] lepusang:
You cant port mtk-su. The sercuity exploit is a defect built into the CPU. A CPU is made up on millions of transistors , A transistor is a switch (On/Off) , Creates a workload that targets the switch would normally return no to yes is very difficult n can very easily destroy the CPU by creating a internal short. NOTE The device manufacturer can help provide a bootloader key if request
[Android Q&A, Help & Troubleshooting] Skorpion96:
i know that mtk-su can't be ported but maybe we can use the source of mtk easy su and the cve-2015-1474 to make a working app
[Android Q&A, Help & Troubleshooting] Noobiemada:
Can it really be done? I have a ZTE blade vantage 2 and I'd love to root it if possible.
[Android Q&A, Help & Troubleshooting] Skorpion96:
I just tried a zip to enable fastboot on the axon mini on my zte blade A5 2019, it flashes, fails because model is different but it is not a signature error meaning that it has the same signature. So signature is the same for every zte, now I'm asking zte Italy to help me getting the unlock file or the signature itself which is the same since or I will flash the file directly or I will sign it and flash. I hope they will help.

Useless try, they refused to help because of their policy
[Android Q&A, Help & Troubleshooting] R41N MuTT:
Went out and bought an m8l plus to try it. This is the first time I've ever dealt with a unisoc sc9863a. I was optimistic about it at first, but now I'm doubtful

*Update* found modified fastboot folder and did the following. Unlocked bootloader, about to try to root with magisk. Root achieved with magisk. Made copy of firmware, moved boot_a to phone and patched with magisk. Flashed patched boot_a with adb. Currently deleting system apps. Root is go. This is unisoc sc9863a blu m8l Android 11
[Android Q&A, Help & Troubleshooting] R41N MuTT:
Found this. Can't post the link, but I'll c&p the text:

Open the modified_fastboot folder, right-click then select Open in Terminal

Test detection using

Code:

./fastboot devices

Get Identifier Token using

Code:

./fastboot oem get_identifier_token

You should get an output like

Identifier token:

XXXXXXXXXXXXXXXXXXXXXXXX

OKAY [ 0.019s]

finished. total time: 0.019s

Copy out the Identifier token

Run this command ; replace XXXXXXXXXXXXXXXXXXXXXXXX with your Identifier token

Code:

./signidentifier_unlockbootloader.sh XXXXXXXXXXXXXXXXXXXXXXXX rsa4096_vbmeta.pem signature.bin

You should have an output like

Identifier sign script, ver 0.10

1+0 records in

1+0 records out

50 bytes copied, 0.000257562 s, 194 kB/s

Identifier sign successfully

You should also see a signature.bin file in the modified_fastboot folder

Finally, run this command

Code:

./fastboot flashing unlock_bootloader signature.bin

You should get a prompt on the device asking you to push a volume button to confirm unlock, do so

You should now have an output like

downloading 'unlock_message'...

OKAY [ 0.001s]

unlocking bootloader...

Info:Unlock bootloader success! OKAY [ 85.787s]

finished. total time: 85.788s

Reboot the device using

Code:

./fastboot reboot

Your bootloader should now be unlocked

They request you log in and register in exchange for the modified fastboot folder
[Android Q&A, Help & Troubleshooting] luridphantom:
you can get the modified Fastboot folder anywhere, used that trick to bl unlock all my blu and wiko phones
[Android Q&A, Help & Troubleshooting] MD.SAFIN:
It succeeded ....but. when i try

fastboot flash recovery recovery.img

It says

Sending recovery... (Size shows in KB)

Then says writing recovery... Fot infinity 😕....

I ported custom twrp recovery using hovatek's automatic unisoc twrp porting guide....have any solution? I also tried to flash twrp by spd research tool and it stuck at probably 95/97 percent
[Android Q&A, Help & Troubleshooting] Sacktreter:
fastboot oem get_identifier_token

Give only back the Serial Number in hexadecimal

Put your SN of your Device in a Hexeditor and change the view to Hexview

when you compare you will see its the SN

I show you the output of my Device, it's an blackview A70 Smartphone. This device is my favorite victim, because it is stubborn as a donkey.

d:\android\blackview\a70>fastboot oem get_identifier_token
(bootloader) identifier token:

(bootloader) 334b3032384137304545413037313431

(bootloader) 37

okay [ 0.031s]
finished. total time: 0.031s

(the number above in a phantasy number)

Interesting is, here are 3 lines (bootloader)

1. is title

2. is first part of SN

3. is 2. Part of SN

yes the length of the SN of this device is 17 characters. In this case you have to put line 2 and line 3 together to build the number.

If you dont do that, not success with unlock.

for example, this is my SN read with

fastboot devices

3K028A70EEA071417

fastboot oem get_identifier_token

334b3032384137304545413037313431

37

the difference is only binary and hex view
[Android Q&A, Help & Troubleshooting] Azaze666:
on 4pda someone rooted this device, Unfortunately he is banned on xda. on attachments posts about root
[Android Q&A, Help & Troubleshooting] mkgama:
Hola tengo un zte blade a5 2020. tengo un archivo pac del mismo pero no puedo extraer el archivo boot.img para poder rouut con magis. me e pasado toda lanoche intentando descomprimirlo y NADA cuando descomprimo con el mismo celular sale error y tampoco en cuentro el archivo boot.img alguien me ayuda a encontrarlo . porfa
[Android Q&A, Help & Troubleshooting] Azaze666:
It can't be rooted by magisk, follow my guide:https://xdaforums.com/t/zte-blade-a5-2019-2020-etc-root-guide.4612391/
[OnePlus 7 Pro Questions & Answers] hacktek:
Has anyone seen this? I have the t-mobile version and I think I've tried literally everything but I can't get wifi to work over 192 Mbps in OOS or HOS (on either 5 Ghz or 2.4 Ghz). The only thing that fixes it is going to some ASOP based rom but all of them have some game breaking thing I hate (Havoc didn't feel smooth, Pixel Experience has laughable battery drain, some other I don't remember the fingerprint sensor stopped working out of the blue, etc).

What I've tried:

- msm tool to 9.5.3 global version

- fastboot flash all partitions

- updating it to 10.0.2, factory reset

- updating it to 10.3.3, factory reset

- flashing with msm tool twice in a row

- updating to Hydrogen OS using local upgrade

- wipe cache from stock recovery

- wipe cache from twrp

- both locked and unlocked bootloader

- configuring with and without the sim card on pretty much every version I've tried

Oh and outside of the phone I've already tried:

- 2 different routers at home

- 1 router somewhere else (all different brands)

- connecting the OP7 to another phone running as hotspot

- connecting another phone to the OP7 running as hotspot and that other phone ALSO got 192 Mbps

Is there anything else to try? This is driving me crazy. Friend of mine also got a branded version and just converting it to the international version fixed it for him. The only difference is that I waited for t-mo bootloader unlock, he didn't.

It's clearly not a hardware issue otherwise AOSP roms wouldn't work...

Any ideas?
[OnePlus 7 Pro Questions & Answers] Tardeaux:
I can't say I've paid much attention to my wifi link speed, but I just checked and I'm connected at 240Mbps on a 5ghz AC connection. Not much better, but I'm not particularly close to the router either.

This is on OOS 10.3.3 with Kirasakura kernel, which includes customizations to the WLAN driver. Might be worth checking out.
[OnePlus 7 Pro Questions & Answers] IlD4nX:
Stock phone (OB16 now), on my AC 5GHz network, using AVM solutions, max speed is 855Mbps almost stable; of course if I switch to my N 2.4Ghz repeater max speed is around 250Mbps
[Amazfit] Sacob:
hey,

my amazfit pace "dieded" and i've decided to upgrade to the newest version, stratos 3.

After my initial setup i realized that i can't get into the settings menu, I have a crash. factory reset but keeps the same. is there a way to fix this? I'm on 4.2.0.1 but i can't find updates.

Also, the vibration makes a loud noise. is that normal? i want to set the level to low but i can't access the menu.

what can i do?

Best regards!
[Amazfit] Saratoga79:
It's a known bug on that fw version. Look for Stratos 3 US firmware thread for OTA installer to update to latest 4.2.6.0
[Amazfit] Dark Legend:
Keep in mind that 4.2.6.0 is buggy af
[Amazfit] winni21:
4.2.5.0 is the best choice FTM
[Amazfit] Sacob:
I'm on 4.2.6.0. Any known problems? It's working fine here
[JASJAR, XDA Exec, MDA Pro General] szpaner6:
Can somene give me the .cab file with the HTC TASK MANAGER ?

Thanks:)
[JASJAR, XDA Exec, MDA Pro General] unapproachable2kx:
It took me 5 seconds to Use Search button over here and find it! Please do it the next time..

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

Have a good day!
[Sony Xperia XZ1 Compact Questions & Answers] acolburn3:
I'm about to get an XZ1 Compact and I'm interested in exploring its files. I understand Windows, but Android's terminology is new to me. I'm unsure whether I understand correctly how Android works. Is this right?:

(1) When turned on, a small OS (the "bootloader") powers on, and its objects call

(2) objects in the "recovery partition," which in turn

(3) call the files and objects in the main partition which power the actual Android OS.

To change files in the main partition ("flashing ROM") either the new files' API's must match those in the previous OS or else files in the recovery partition also need to change ("be customized"). Similarly, changing the recovery partition requires either the same API calls from the bootloader or else changing the bootloader ("unlocking" it).

Is all that right? Does this mean doing something like installing TWRP (from the command line on my desktop, where I already have Android Studio and the Android SDK tools) means I have to "unlock" the bootloader too? [Is there a suggested web site or reference, besides this forum, with good info to teach me what I need to know to understand bootloaders, recovery partitions, custom ROMs, etc.?}

Thanks!

Al C.
[Sony Xperia XZ1 Compact Questions & Answers] Ephesus:
Hi AI C,

What you described is basically how it works, although the bootloader decides what partition to load the operating system from. The recovery is located in the recovery partition and the bootloader can start it up the same way as an operating system and it allows users control over certain aspects of the phone such as wiping partitions and modifying the currently installed Android.

Here is a site that describes some of the terms:

https://trendblog.net/guide-to-android-rooting-custom-roms-apps/

In order to modify your Android operating system and flash a custom ROM you need to unlock the bootloader as the locked bootloader will only boot your stock firmware (Android OS) that came with your phone.

---------- Post added at 05:28 PM ---------- Previous post was at 05:22 PM ----------

The XZ1 compact is not the easiest device to learn these things with as Sony has locked certain parts of the OS using DRM (digital rights management) which requires a couple extra steps when unlocking the bootloader. Without these DRM keys the camera does not work.

Additionally not all XZ1 compacts bootloader's can be unlocked.

Check this PDF for instructions to unlocking the bootloader and backing up DRM keys:

https://xdaforums.com/xperia-xz1-co...-exploits-temp-root-to-backup-t3795510/page39

If you have any specific questions I'm happy to help.
[Sony Xperia XZ1 Compact Questions & Answers] acolburn3:
Your explanation makes perfect sense, and those look like really useful links. Thank you for taking the time to respond so thoughtfully. I'd read about the camera issues. Although some folks describe solutions (XperiFix?), I don't think I need Android 10 enough to want to risk flashing it yet. In the meantime, do installing a different recovery (TWRP?) or rooting the device require unlocking the bootloader, too?

p.s. If the answers to those questions are in the links you gave me, I'm perfectly OK being told "go read them!" :)
[Sony Xperia XZ1 Compact Questions & Answers] Ephesus:
The short answer is yes. You need to unlock the bootloader in order to root and install a custom recovery.

The long answer is that there is a workaround using the Temp-Root solution provided by J4nn: https://xdaforums.com/xperia-xz1-compact/development/devonly-exploits-temp-root-to-backup-t3795510

that is used to root the phone temporarily so that the DRM keys can be backed up. When you use the magisk version version of the exploit that is linked in the first post you have root access until you reboot the phone.

If you want to get root back you need to connect it to your computer using ADB (android debugging bridge) and send the commands again. Additionally it only works with a few certain android oreo based stock firmwares.

So it is not exactly a workable solution.

I have not heard of XperiFix before. The thread I linked by J4nn and the previous PDF I mentioned is the way that I bootloader unlocked my device and made sure I still have a working camera, although other methods might exist.

I'm glad I could help.
[Moto Z Questions & Answers] DanielC4:
My phone is a Moto Z xt1650-03. I am trying to replace the motherboard of my Moto Z xt1050-03, with another motherboard of the same model. However I can't find a xt1650-03 motherboard for sale. I only find the xt1650-01 and xt1650-02 available.

Will one of those two boards (xt1650-01 or xt1650-02) be compatible with my phone ? I need your opinions to know if I can buy it to repair my phone.

If so, which of the 2 options should I you buy?

Thank you very much :laugh:
[Moto Z Questions & Answers] MarcY50:
xt-1650-01

The xt1650-02 version definitly won't work as it is for the z force which has a different camera. The xt1650-01 board likeley works as a lot of sellers sell motherboards which are compatible with the xt1650-01 and xt1650-03. So the motherboard is likly compatible.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] G0ldengirl68:
..even after a complete reset.

Is there anyone around that might help me figure out if it's "done for" or it can be fixed? I've tried other apps to make sure it was just the app, and also, the wifi is very good. I tried in different rooms, and the one where my router is. Very, small apartment. I've had the Kindle for about 4 years, never had an issue until a few days ago. I've only used it to read on, books from Amazon, or Overdrive libraries. Did do some searches with Silk. I did reinstall my Google Playstore that has always work great (the 4 apk files).

Would so appreciate any ideas/thoughts on what it could be that's going wrong. I select the app from the store (also tried from Amazon store) and it just keeps loading. I've set it down and let it go for a few, nothing at all, no error message, nothing :( Hate for it to just have gone belly up since I don't think 4 years is that long to have one.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] G0ldengirl68:
solved: For whatever reason, it just downloaded, and installed so who knows ;) It's working. I don't see where to mark "solved" so left this message ;)
[OPPO Reno 10x Zoom Questions & Answers] van_helsing_80:
Bluetooth v5 introduced a feature named dual audio, through which audio can be played from a single phone to two different speakers/headphones connected over Bluetooth.

Where is this feature in our phone? Even the recent update ColorOS 7.1, this feature is still missing!

please let me know if this feature is available.

Samsung already has the feature

Realme has.......sort of a similar feature
[OPPO Reno 10x Zoom Questions & Answers] moozer:
Sorry, I don't use BT audio, but is this of any help?
[OPPO Reno 10x Zoom Questions & Answers] van_helsing_80:
The option you are showing is the feature to connect multiple devices via Bluetooth, which is support to 5 at the same time with possibility of different Bluetooth profiles and I know about this.

Dual Audio feature means to share same Bluetooth profile of "Media Playback" to 2 devices at the same time.

I've tried, but our phone, as of 31st July, still doesn't support sharing Media Playback profile with 2 devices. It will switch the device, if i tend to change it, keeping the profile locked on to just 1 device.

On the other hand, I've tried testing the Samsung's feature and it shares the same profile with 2 different speakers. Bluetooth v5 has the capability to support this by default. Thus, its up to OPPO to provide the software support to it.
[OPPO Reno 10x Zoom Questions & Answers] moozer:
Like I said...I don't use it, but thought that might have helped.