This method works on Redmi note 9s MIUI 11.0.7 (QJWMIXM)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Previously it only show waiting for backup. After applying the fix through ADB (non root method). Android backup works normally. Now I can press backup button to initiate backup to Google Drive.
https://forum.xda-developers.com/mi-8/how-to/guide-google-backup-waiting-to-backup-t3895101
Dexer125 said:
Hello, time to time, many users are facing problem with greyed Backup now button in Google Backup. So here's the solution.
How it looks
ADB solution
What you need
Device specific drivers
ADB
USB Debugging turned on
Procedure
Connect the phone to the PC
Open Command prompt - CMD
Type in console
Code:
adb shell
bmgr run
bmgr backupnow --all
If error "Backup finished with result: Backup Cancelled" pops up, type in console
Code:
bmgr backupnow appdata
and then
Code:
bmgr backupnow --all
When it's finished reboot your phone, Backup now button should be blue and functional
Terminal Emulator solution
What you need
Root
Terminal Emulator
Procedure
Open Terminal Emulator
Type
Code:
su
bmgr backupnow --all
Reboot phone
Backup doesn't work after deleting data/data/com.google.android.gms
There's a new problem after deleting mentioned folder to get GPay working. Unfortunately this breaks Backup. I captured the issue, backup transport path is disabled, you need to reenable it.
Procedure is same but this time, type in console
Code:
bmgr transport com.google.android.gms/.backup.BackupTransportService
Now repeat previous steps.
If I helped, consider buying me a coffee or just hit Thanks button. I appreciate any kind of feedback.
Click to expand...
Click to collapse
Related
Hello,
At the beggining I had SDK Tools Only and everything was ok, after typing adb logcat I got logs. Then I installed ADT Bundle and run eclipse -> DDMS and in logcat tab I got logs. Then I installed a couple of programs to make screencasts. The next day I run eclipse -> DDMS and I got this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
[2013-05-18 08:46:16 - ddms] ADB rejected shell command (getprop): closed
[2013-05-18 08:46:29 - ddms] ADB rejected shell command (logcat -v long): closed
[2013-05-18 08:46:29 - Unexpected error while launching logcat. Try reselecting the device.] closed
com.android.ddmlib.AdbCommandRejectedException: closed
at com.android.ddmlib.AdbHelper.executeRemoteCommand(AdbHelper.java:381)
at com.android.ddmlib.Device.executeShellCommand(Device.java:462)
at com.android.ddmuilib.logcat.LogCatReceiver$1.run(LogCatReceiver.java:110)
at java.lang.Thread.run(Unknown Source)
When I run adb logcat from console I got this message: waiting for device.
adb devices detect my phone
I have windows vista home premium
android 4.1.2
What I did:
- uninstalled SDK Tools Only
- reset adb / unplug and plugin my device
- I tried this one: adb -s emulator-5037 logcat but still waiting for device
- adt bundle - sdk manager -
- windows task manager - there is just one adb.exe running
but still I get waiting for device and the exception in eclipse.
thx in advance
c'mon guys help me out with this
For clarity, my OS is Lubuntu 17.04 (Zesty)
Due to my phone's apparent obscurity, I'm unable to find any resources pertaining to it, so I've been trying to be as 'manual' as I can by unlocking it through fastboot commands. I really want to unlock my phone's bootloader in order to root it and install a custom recovery and then custom ROM.
However, I've run into an issue. Whenever I run 'fastboot oem unlock', as well as most other fastboot commands, I get stuck at an ellipsis('...') and it stays there until I shut off my phone. Ctrl+C and Ctrl+Z can't close it. So far, I've successfully installed ADB and fastboot tools.
For troubleshooting, I have:
- double checked if my device is listed whenever I run either the 'adb devices' command or the 'fastboot devices' command and it is listed for both
- I've set up my udev rules and adb_usb.ini
- changed usb ports/cables
- rebooted my phone and PC many times
- looked for official and unofficial unlocking instructions (to no avail)
If there is anyway you can help me or guide me to a resource which may be of use to me, please do so. It's been a real struggle having such an obscure phone, but it's what I can afford at the moment.
tl;dr: 'fastboot oem unlock' not working. stuck at ellipsis('...'). device is listed under 'adb devices' and 'fastboot devices' command.
Unfortunately, I can't post outside links yet, so please PM me for a link to my dropbox folder containing my .rules, adb_usb.ini, and CPU-Z information.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bolded for skimmers.
Google has made it easy to use ADB in Windows these days, but the ADB commands can only be used in a directory. This a Powershell script for Windows that will download the latest ADB from the Official repositories and install it System-wide or User-Wide, this script will also install latest Google drivers also from from the Official repositories. This script will help to install ADB and the drivers in an easy way. Most ADB installers come in exe format where you cannot see exactly what they do exactly. So I decided to write the whole thing as a Windows Poweshell script.
On my github page you can download the script and you can also find an explanation how to use the script. The big difference to others is that ADB & Fastboot drivers are updated in real time when this tool is used. For the drivers i have to update a link I'll do my best when a new driver comes out to update the link as soon as possible.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Notes:
System-wide: ADB and Fastboot are installed to HOMEDRIVE\ADB directory, and added system-wide path.
HOMEDRIVE=C:\ so in case of the system-wide install option ADB will copy over to C:\ADB
Current user only: ADB and Fastboot are installed to UserProfile\ADB directory, and added path for current user. UserProfile=%SystemDrive%\Users{username} so in case of the Userwide-wide install option ADB will copy over to C:\Users\username\ADB
CMD or Powershell can use ADB and Fastboot from any directory.
If you are using this tool and you having problems leave a comment and I will try to help you
ķANKAN
good evening. i have o problem with the twrp installation.
after unlocking the bootloader with the adb method i tried to install the twrp. at first there was a problem with partition but with no command the twrp will open
.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
the twrp.img is in the platform-tools folder with the same name as the command.
i though thw twrp was installed in the command but it does not open neither in recovery. i tried throug command or by pressing power button and the volupe up.
in addition the phone does open either. i reboot in the fastboot screen.
what is the the mistake and how should i procced?
thank you
poikon5 said:
good evening. i have o problem with the twrp installation.
after unlocking the bootloader with the adb method i tried to install the twrp. at first there was a problem with partition but with no command the twrp will open
.
the twrp.img is in the platform-tools folder with the same name as the command.
i though thw twrp was installed in the command but it does not open neither in recovery. i tried throug command or by pressing power button and the volupe up.
in addition the phone does open either. i reboot in the fastboot screen.
what is the the mistake and how should i procced?
thank you
Click to expand...
Click to collapse
If this phone has A/B partitions this command cannot work.
You must use
Type' fastboot boot twrp.img' without the apostrophes.
The phone will reboot in TWRP after that go to Advanced > Flash Current TWRP.
Or https://forum.xda-developers.com/t/...omi-mi-a3-laurel_sprout.3987759/post-80625495
Hi there,
My device was properly rooted (verified by Root checker).
But after
Code:
adb root
It returns
Code:
adbd cannot run as root in production builds
How to solve it?
Thanks.
Cheers,
Wen
ah! You can try FX file explorer, navigate down to the bottom till you see system root settings
enable it and mount remount the system (root) files without ADB thank you
golanpiyush said:
ah! You can try FX file explorer, navigate down to the bottom till you see system root settings
enable it and mount remount the system (root) files without ADB thank you
Click to expand...
Click to collapse
Thanks.
I tried FX file explorer.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But after superuser in Magisk was granted to it and file "system (root) was remounted, adb root could still not work.
It returns "adbd cannot run as root in production builds".
Actually, this issue was solved by installing and enabling "adbd insecure", but afterwards, the device could no more be recognized by adb.
Device unrecognized by adb after checking "Enable insecure abdb" in "adbd insecure"
Hi there, After installing "abdb insecure" on my rooted device and checking - "Enable insecure abdb"; - "Enable at boot". The device is no more recognized by adb. After - adb shell, it returns - " * daemon not running; starting now at...
forum.xda-developers.com