Database Develop

BACK TO WEAR 1.5 FROM 2.0(COMPLETE GUIDE) and ELIMINATE THE PERSISTENT UPDATE NOTIFIC

Hello everyone,
Some Italian guys asked me for this guide because they did not find anything complete and detailed. Thanks to the XDA members' publications I could put together the pieces and write it down. I apologize for my English but I'm not very good, especially for technical terms. I hope I can help someone.
BACK TO ANDROID WEAR 1.5 FROM 2.0(COMPLETE GUIDE)
1. Download the software ADB installer 1.4.3 from this link compatible with Windows 10: http://uploadboy.com/tsp1bpbe9gtj/1082/zip
From here you can download an older version 1.3 for Windows 7: https://forum.xda-developers.com/showthread.php?t=2588979
2. Open the .exe file already downloaded with administrator privileges and follow the installation procedure to install the drivers
3. Download the three image files of the build "M1D65H" (boot, recovery, system) that you find here: https://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
4. Insert the files into the folder that created the ADB Installer that is normally the path "c:\adb"
5. Download tool "WinDroid Toolkit" from here (some antivirus swapping it for threat and eliminating it, in this case turn it off momentarily) :
https://forum.xda-developers.com/devdb/project/dl/?id=17244
6. Start with administrator privileges "WinDroid Toolkit"
7. Follow the instructions for installing the drivers required by the tool and select the model of the clock
8. Activate developer options on the clock: (Settings> System) by clicking "build number" repeatedly until unlocking the menu that will be among the main options
9. In the developer options menu, activate the "debug ADB"
10. Turn off the clock
11. With the clock off, hold down the physical key and in the meantime repeatedly tap your finger on the screen from minute 55 to 25 until the watch has entered the mode fastboot
12. Connect the clock to PC usb port via cable and charging base
13. Now "WinDroid Tool" should recognize the clock and below you will see that the "Offline" script becomes "Fatboot"
14. Click on "Unlock Bootloader" and proceed by accepting the various message from the tool
15. A confirmation message appears on the clock display, click on the right arrow and then on the central button to continue
Now the bootloader of the clock is unlocked and we can continue to install the three previously downloaded files. Close "Windroid Tool"
16. In the "adb" folder at the "c:\adb" path, click on a drop-down menu at any point in the chain and right-click and shift at the same time. Click on "Open command window here"
17. In the newly opened window, give the following commands one at a time and wait for each one to complete the operation:
1) fastboot -w
2) fastboot flash boot M1D65H_boot.img
3) fastboot flash recovery M1D65H_recovery.img
4) fastboot flash system M1D65H_system.img
Finally, to restart the clock, use the following command:
5) fastboot reboot
N.B. Before pairing the watch on the cellphone again remove the link, inside the Android wear app, clock and uninstall and reinstall the app.
Finished!
ELIMINATE THE PERSISTENT UPDATE NOTIFICATION
1. Download the .zip file containing the custom recovery and root to this address:
http://www.mediafire.com/file/qllnc7...+R+Utility.zip
2. Unzip the .zip file and insert the "twrp-3.0.0-0-lenok+squashfs.img" file into the "c:\adb" folder
3. In the Clock Developer Options menu, activate the "Debug ADB" (to enable them to follow the procedure above)
4. Connect the clock to the pc via the cable and charging base
5. Open "WinDroid Tool", go to the "Commands" tab and click on "push file". Select the file "SR1-SuperSU-v2.78-SR1-20160915123031.zip", wait for the procedure to complete and disconnect the clock from the PC.
6. Turn off the clock
7. With the clock off, hold down the physical key and in the meantime crawl your finger repeatedly on the screen from minute 55 to minute 25 until the clock has entered fastboot mode
8. Connect the clock to the pc
9. In the "adb" folder at the "c: \ adb" path, click on a drop-down menu at any point in the chain and right-click and shift at the same time. Click on "Open command window here"
10. In the window just open, give the following command and wait for the completion:
-) fastboot flash recovery twrp-3.0.0-0-lenok+squashfs.img
11. From the clock using the arrows and the confirmation button down to start the "recovery mode"
12. Accept the warning message and after selecting the language click on "install" and select, with the touchscreen, the .zip file "SR1-SuperSU-v2.78-SR1-20160915123031.zip", wait for the procedure to complete.
13. Restart the system and wait for the clock to turn on.
14. In the previously opened command window, give the following commands one at a time and wait for them to complete and complete:
1) adb shell
2) su
3) pm disable com.google.android.gms/.update.SystemUpdateService
4) pm disable com.google.android.gsf/.update.SystemUpdateService
Finished!

Many thanks riccardo423
I have managed to rollback my lg g watch r to android wear 1.5 AND suppress those pesky update notifications using your guide. I noticed your mediafire link to the custom recovery file is broken. There is an alternative download at http://www.mediafire.com/file/qllnc77jtdqxtdl/Lg+Watch+R+Utility.zip (posted by Dettofatto in a previous xda thread) which also contains the two additional required files.
Luigino1

Hello, thanks for inserting a working link. I've modified the text of the guide by entering your link. I'm glad to have helped you.
Riccardo423

For step 3 if I click the link it says the post does not exist. Anyway here's where I found the images if anyone needs it: https://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
BTW: Thank you for the complete guide, step by step, i was able to go back to 1.5 and disable the persistent notification thank you very much!

Hi, thank you for inserting the working link. I'm glad to have helped you. Riccardo423

After downgrade from 2.0 to 1.5, I don't received Facebook messenger notifications on watch. Other notifications work fine (Gmail, sms etc). Anyone know what's going on?

Hi I have never had this problem I think I can depend on your Facebook app. Which version of Facebook and which cell phone?

Latest version of Facebook app from Google store. Phone - Samsung Galaxy S6 with Latest Marshmallow updates

szczurx said:
Latest version of Facebook app from Google store. Phone - Samsung Galaxy S6 with Latest Marshmallow updates
Click to expand...
Click to collapse
You've already tried uninstalling and reinstalling the app?
The app wear permissions are unlocked for notifications?

Android wear app reinstalled twice. Even made watch factory reset. On Phone in settings/apps, Android Wear app have permissions for everything possible

Thanks for this Riccardo ( or grazie, from a fellow italian )!
Can't believe I managed to do the entire procedure without making a mess of it, lol. Everything appears to be working again, I'm so happy! Really hated AW 2.0. Hope the notification does not come back, I'll keep an eye out for it in the coming days.

hello, can anyone answer me why these commands dont work
pm disable com.google.android.gsf/.update.SystemUpdateService
and why superSu crashes on watch

Thank you Riccardo423 for great manual, it works great for my watch. No AW2 anymore!

riccardo423 said:
3. Download the three image files of the build "M1D65H" (boot, recovery, system) that you find here: https://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
charging base
Click to expand...
Click to collapse
Noob question: why the "M1D65H" versión? Is the last with AW 1.5? The NXG47C version is for 2.0?

LionheartSilver said:
Noob question: why the "M1D65H" versión? Is the last with AW 1.5? The NXG47C version is for 2.0?
Click to expand...
Click to collapse
Yes, it's the last AW1.5 version. However, perhaps it was due to something I didn't made correctly during the downgrade but this M1D65H version had not a good battery performance on my watch (battery was drained in less than 40 hours).
It's why I have used the M1D64Y version which is perfect in terme of battery performance (>48 hours) and applications responsiveness.

pidobeuliou said:
Yes, it's the last AW1.5 version. However, perhaps it was due to something I didn't made correctly during the downgrade but this M1D65H version had not a good battery performance on my watch (battery was drained in less than 40 hours).
It's why I have used the M1D64Y version which is perfect in terme of battery performance (>48 hours) and applications responsiveness.
Click to expand...
Click to collapse
Really? ... hmmm i see.... mine has always lasted less than 40 hrs... did you install any mod for the watch? core enablers or smth?

LionheartSilver said:
Really? ... hmmm i see.... mine has always lasted less than 40 hrs... did you install any mod for the watch? core enablers or smth?
Click to expand...
Click to collapse
Nothing specific, just installed the basic factory image + root . I have installed about 16 apps (including Watchmaker with a quite "sophisticated" watchface, wear messenger, WearMail, Wear Battery stats, Feel the Wear, Runtastic, ...) but mainly I have deactivated Google Fit which is a true battery killer app on both the Smartwatch and the Smartphone!.

mediafire link is dead (twrp) - please, reupload it!

Thanks so much for this, it worked perfectly! So great to have my watch back!

Hi, I have problem connecting in ADB mode to PC - when I plug in craddle nothing is happening Win10 not even play a sound, not trying to find drivers etc. Is it connected with new version NXG47C/LENOKZ22b ??
In fastboot mode there is green "secure boot" enabled, lock state - locked and bootloader in Z22b version. Is it possible to connect ADB in this case? Im stucked witn AW2 and there is nothing I can do for now Please help.

Question Screen bug After change refresh rate

Hi everyone i recently installed google pixel on my redmi note 10 pro. problem I activated the 90 hz mode via an application (setedit) which allows you to change all kinds of parameters on your phone. the problem being that it did not work so I restart my phone is the screen bug and flickers I do not see anything more. so i would like to find a way to control my phone via my pc to be able to activate the 60 or 120 hz by default so that my phone come back as before without resetting it would you have any solutions?

If you have TWRP installed just dirty flash system to override setedit modifications

If you're using linux on pc & have adb enabled on phone then connect phone to pc & run scrcpy on terminal

If the refresh rate is too high, click on the Advanced button or Advanced settings link and then click on the Monitor tab. Here is also where you can change back your primary monitor to 1 if 2 gave you a blank screen. Also, you can uncheck the extend my desktop option.

[email protected] said:
If you're using linux on pc & have adb enabled on phone then connect phone to pc & run scrcpy on terminal
Click to expand...
Click to collapse
I try this method but i didn't work .
I finnally reset m'y phone

Miui 13 said:
I try this method but i didn't work .
I finnally reset m'y phone
Click to expand...
Click to collapse
Didn't work? We can interact with phone using mouse on pc screen right?

[Guide] [One UI 3] How to boot into recovery in One ui 3 & above without a pc and root access

Reboot Your Device Into Recovery Mode
There are multiple ways to reboot an Android device into recovery mode. But after the latest OneUI 3.0 update, Samsung does not allow booting into recovery without connecting your phone to a PC with a USB-C cable. Here's a solution to easily reboot to recovery.
The steps mentioned can be applied to boot into both the stock recovery as well as a custom recovery if you have one installed.
Reboot to recovery without root access and without connecting your phone to Laptop/Pc.​
Download & Install LADB - Local ADB shell from playstore or download it directly from here.
Open Settings > About Phone and tap on the “Build number” field 7 times. This will enable “Developer Options.”
Go to Settings > System > Developer Options and enable “USB debugging” and “Wireless debugging.”
Open the LADB app. It will show a “Pairing information” dialog.
Open the recent apps screen. Press and hold on the app’s icon and tap “Split Screen” to open LADB in split-screen multitasking view.
On the bottom half, open Settings. Go to System > Developer Options > Wireless debugging. Tap on “Pair device with pairing code.” You’ll see a “Pair with device” dialog pop-up.
Copy the 6 digit “Wi-Fi pairing code” and paste it into the “pairing code” box in LADB. Copy the 5 digit port number from the IP address (the 5 numbers after the colon) and paste it into the “Port” box in LADB.
Hit “OKAY” in LADB and you should hopefully see text that says "Hello World”
Enter "reboot recovery"
And done now your phone will automatically reboot to recovery.
Note :
You can even try out different adb commands like deblooting system apps, allow permissions to apps like macdriod, system ui turner, etc and many more other adb commons without root and without a PC. (tested on Galaxy M30s)
Thanks to the developer of LADB
For downloads and other instructions : Click here

Reserved..

thanks .. good tut and very useful

Power off, then hold volume up and bixby button till recovery comes up. Works without a pc or cable.
realbbb
Moldly Going

realbbb said:
Power off, then hold volume up and bixby button till recovery comes up. Works without a pc or cable.
realbbb
Moldly Going
Click to expand...
Click to collapse
It's for users without root and pc

razs.originals said:
It's for users without root and pc
Click to expand...
Click to collapse
Power off, then hold volume up and bixby button till recovery comes up works for root, no-root, pc, or no-pc. It does not matter what version of OneUI.
realbbb
Purely Board

realbbb said:
Power off, then hold volume up and bixby button till recovery comes up works for root, no-root, pc, or no-pc. It does not matter what version of OneUI.
realbbb
Purely Board
Click to expand...
Click to collapse
Okay it might be working that way for you but many users reported that without connecting USB they aren't able to boot into recovery
recovery mode in android 11 one ui 3.1
Guys anybody know that how to go recovery mode in android 11 ( one ui 3.1 )
r2.community.samsung.com

Will this let me unlock bootloader?

Question Redmi note 10S not recognized MiUnlock

I own a Redmi note 10S having the MIUI EEA 13.0.5.0 installed on it.
I need or to downgrade toward the 12 or to upgrade with a Global 13.0.8.0.
To do that I have to unlock the bootloader.
I have tried to unlock my phone following the Guide
"Complete Guide to Unlocking the Bootloader: Announcement, Troubleshoot and Tips"
Xiaomi Community
new.c.mi.com
Completely performed the "Step 1: Phone" phase
But I am stuck into "Step 2: PC" phase
I downloaded and launched the "Mi unlock" program, version 6.5.406.31
Updated the driver with settings option --> "click the button to install the drive"
Obtained the confirmation
"Mi USB driver installation
Installed drivers successfully"
But the program is still locked into
"Not connected to the phone" screen.
Note: With Phone into Fastboot mode the OS Windows 10, under device manager identify the phone with the icon
"Other device" --> "Andorid" with the Yellow Triangle with Exclamation Point inside
In addition with the Phone in Fastboot mode there is a continous OS disconnect and reconnect sound of the system.
An attempt has been made to solve the problem following the indication in
Mi unlock/USB keeps connecting/disconnecting
I was wondering if anyone experience the same. I want to unlock my bootloader but everything I connect my phone (in fastboot) to PC I hear windows connecting and 2 seconds after that disconnecting in loop. Mi unlock therefore doesn't see my...
forum.xda-developers.com
* Disabled the signature enforcement --> Achieved by enabling the operating system Test Mode through Power Shell
* Download and installed the driver Redmi Note 10S - Mediatek Driver
without improvement
NOTE: the verification has been performed with both Intel and AMD systems.
Then the following attemp has been performed:
(following the information reported in
)
Installed --> adb-setup-1.4.3
With the smartphone normally running, it is identified with its numbering by means of
PowerShell --> "adb device" command
But anyway, after swith into Fastboot mode the phone is still not recognized by the software.
Thanks for any help you can give me

wrong drivers
https://dl.google.com/android/repository/usb_driver_r13-windows.zip --> install those with device manager once "android" appears

Thnanks for your help, but it does not working
Smartphone in fastboot mode, connected to pc by usb, open device manager
Select "Android" under "other device", Right click, update driver, find driver into pc
Select the folder "usb_driver_r13-windows"
but the system provide the error on the installation phase: Unable to install Android - Cannot find drivers for your device

quite odd, surely you are using the wrong versions of drivers

Yeah I know that the installed (and the driver that I try to install) are the wrong one.
But I cannot understand which is the correct one.

[TOOL][WINDOWS] ADB & Fastboot++ | February 2023
NFO: • Versions: Installer, Portable & ADBKit • Android Debug Bridge & Fastboot updated to latest v1.0.41 (Version 34.0.0-9570255, February 2023) Features: • Installation Folder chooseable (Installer) • Desktop & Start Menu Shortcuts (Installer)...
forum.xda-developers.com

Thanks, now it is recognized in fastboot mode

Deleted

How to rescue data from my 9T Pro

So while walking it slipped out from my hand and hit the lower left corner.. The screen didnt even work anymore (after removing the glas, it was clear why, as the connector is lower left corner).
Good thing is, I have adb debugging enabled and my keys are known.. So I can access adb shell and various commands..
My problem is: It rebooted and now, the important stuff is NOT mounted.. Also via scrcpy or MonkeyRemote, I cannot send any touch event... Its not reacting at all.. Honestly, I dont know what it is doing, but its quite busy writing for ever logs in logcat, that the sensors have errors (which is no wonder).
So I tried various "adb shell input XXX", but its not working at all..
Tried to connect a mouse via normal usb-c hub, but I dont know if I would need an OTG cable or if it would even work.
DrFone and some other software, already wants the money, before unlocking anything.. And I would be Ok, if it would be 5-10€.. But buying the whole thing for 1 test, is a big no.
So my status:
adb shell working.
scrcpy at least showing a screen
phone is not reacting on anything else, besides the lockscreen to wake it up.. volume keys are also kinda ignored.
I tried the adb shell input stuff from stackoverflow, but nope.
Can I boot in any recovery thing and mount sdcard there? Does scrcpy work there?
What he heck is my phone even doing?? If I connect another phone in lockscreen and use scrcpy, I can also wake it up normaly.. So probably not only the screen got dmg while flying :/
Most annoying things: It has alarms going off all the time, as I can only snooze them -.-
Is there no command, to unlock it from adb/terminal? I know the damn pin
When I run top, the top most things are sufaceflinger and logd (between 2-15). So its not like sth is always at 100% cpu load..

So little status update:
all adb shell input XXX are simple not working, as Xiaomi needs another setting for that.. Which I cannot activate, without screen.
I will try a manual keyboard at home..
Is there a way, to root it with adb only? Would help me alot..

MIUI security center requires you bonded MI account to enable adb input commands in developer options. scrcpy has OTG mode and can emulate HID device.

scrcpy also didnt work, without that stupid setting set to be true/1.
Tested with my old Mi6. When I enabled the option in dev-settings, it worked fine.
But I was able to unlock it with a keyboard plugged in (+ mouse). Looks like the CPU also has some issues, as everything is slow-motion..
So I just tried, what do I need to press on the Mi6 -> then did it on the Mi9.
"hitting space -> pin -> enter", "hitting space -> pin -> enter".
But was able to rescue all my data + turn off the alarms.
PS.: I then tried to enable this setting, for inputs, but you need to have a SIM cart inserted, to activate it
PPS.: Oh.. Now I got you.. I have to enable this option in scrcpy.. OMG Will test that now
PPPS.: Yeah, with that otg mode, the keyboard and mouse would have also worked.. Well, for the next time I know it

alecxs said:
MIUI security center requires you bonded MI account to enable adb input commands in developer options. scrcpy has OTG mode and can emulate HID device.
Click to expand...
Click to collapse
Ok, thanks - that was missing

If you figure out the command line to enable it from adb settings put global I am very grateful

alecxs said:
If you figure out the command line to enable it from adb settings put global I am very grateful
Click to expand...
Click to collapse
Ok, so I dumped all settings and props to files:
Code:
adb shell settings list global > global.txt
adb shell settings list secure > secure.txt
adb shell settings list system > system.txt
adb shell getprop > props.txt
then searched for adb, usb and similar butfound only the following:
SETTINGS GLOBAL:
adb_enabled=1
adb_wifi_enabled=0
verifier_verify_adb_installs=1
GETPROP:
persist.security.adbinput=1
persist.security.adbinstall=1
(My phone: Mi 11 Lite 5G NE, MIUI 13)
That is, eg ADB can be enabled/disabled as settings global adb_enabled
However, ADB Input is not in settings but as persistent prop persist.security.adbinput and it can be only manipulated by Magisk - and by TWRP but on the old devices where System is not read-only
IMO, it would be theoretically possible on the Mi 9T Pro, but not if display is broken where TWRP cannot be used (I doubt there is anything like scrpy that works for TWRP)

zgfg said:
Ok, so I dumped all settings and props to files:
Code:
adb shell settings list global > global.txt
adb shell settings list secure > secure.txt
adb shell settings list system > system.txt
adb shell getprop > props.txt
then searched for adb, usb and similar butfound only the following:
SETTINGS GLOBAL:
adb_enabled=1
adb_wifi_enabled=0
verifier_verify_adb_installs=1
GETPROP:
persist.security.adbinput=1
persist.security.adbinstall=1
(My phone: Mi 11 Lite 5G NE, MIUI 13)
That is, eg ADB can be enabled/disabled as settings global adb_enabled
However, ADB Input is not in settings but as persistent prop persist.security.adbinput and it can be only manipulated by Magisk - and by TWRP but on the old devices where System is not read-only
IMO, it would be theoretically possible on the Mi 9T Pro, but not if display is broken where TWRP cannot be used (I doubt there is anything like scrpy that works for TWRP)
Click to expand...
Click to collapse
Btw (sorry, OT for the originally reported problem), Netflix cannot be fooled (DRM) to display over scrcpy, only subtitles are displayed on the PC
YT works fine (although without sound - I will try with sndcpy), and strcpy properly recognizes landscape orientation, hence window on the PC can be stretched over the whole monitor
Edit: On the other PC I tried, audio works fine with scrcpy

zgfg said:
However, ADB Input is not in settings but as persistent prop persist.security.adbinput and it can be only manipulated by Magisk - and by TWRP but on the old devices where System is not read-only
Click to expand...
Click to collapse
Nice! I was curious because I don't have Mi account. Although I didn't have this property, just set it from resetprop anyway and it worked!
We can set it from magisk patched boot.img ramdisk/overlay.d/custom.rc systemless. or just add it in init.rc directly.
Code:
on boot
setprop persist.security.adbinput 1