Database Develop

[Q]CWM The system cannot find the path specified

I'm having a problem installing CWM on my unit
XPERIA SP C5302 running on stock .205 rooted with towelroot ( this is my first time rooting )
i have my phone connected to my PC with USB Debugging checked
and followed the steps on this thread
but whenever i run the install.bat file and choose the 1st option
i always end up with "The system cannot find the path specified
{
"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"
}
Help please~

help
someone help! im facing the same problem

Hi, go DOS mode in the directory where you extracted the archive .. there is an ADB directory. Steps in this directory the command: adb devices .. if you have an answer with number, then your phone is connected...

Problem is not with the device. It is with the recovery. Retry the download. Some file might be deleted by antivirus or something? Check it out. It can't find a file it is looking for.
PS: Press thanks if I helped you!

Check if you have the ADB directory .. Option 1 uses. Look Attachment

[ROM]MIUI8 6.9.15 Beta Root and Smooth for Redmi 2/2S

Description:
Based on official MIUI8 6.9.15 Beta
Android version 5.0
Add SuperSU root permission"
Presentation：
ROMER：ycjeson
Android version：5.0
Updated：2016-09-21
Available device：Redmi 2/2S
BUG report & about me：
Facebook
Twitter
Google+
Install Method:
Recommend to use King Flasher: http://tfile.kingflasher.com/soft/kingflasher_setup.exe
1. Install King Flasher on your computer and make sure it can access to the internet.
2. Connect your phone to computer with USB cable and open USB debbuging.
How to open USB debbuging: Settings > About device > Tap “BUILD NUMBER” 7 times > Back to Settings > Developer options > Select “USB Debbuging”.
3. Please open King Flasher and choose a ROM you like, then click “Flash”.
{
"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"
}
4. Wait for downloading ROM.
5. After the download finished, King Flasher will flash your phone automaticlly. It will take about 5-10 minutes to finish.
6. Your phone will reboot to the new system when it finish.

[How to] Change (some) Google Apps and Viper 2.7 to Dark Mode [Root Required]

I stumbled across this in the Viper4Android 2.7 thread. It was suggested for activating dark mode for that app, which it does, but I noticed that it also changed the playstore, photos, and chrome (kind of). There may be more but those are the only Google apps that I use beside Drive and messages which already have a dark theme option within the app.
Edit- I forgot about Gmail. It doesn't work for that one, at least not on my end.
This is only confirmed on Stock 6.0.1 firmware.
First you'll need a terminal app. I use Termux.
Open that app and type the following:
Code:
su
Press enter, then type (or copy/paste)
Code:
settings put secure ui_night_mode 2
Press enter, then reboot or type in the terminal
Code:
reboot
And press enter
Once your phone boots back up you should see dark mode on the above mentioned apps and possibly more.
{
"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"
}
Credit to this post by @dpEnd367

Question FLASH GUIDE

{
"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"
}
I posted two Screenshots, One is my current one and the other one is which i want to install, I want to make sure if it is ok to move directly from. Miui a11 to a13, or there will be some other process, it would be great if you guide me with the steps in both cases
Thanks

Yes you can directly move to A13 Custom ROM.
But before you can do that, you have to do the following:
1. Enable Developer Option.
2. Unlock bootloader (OEM unlocking)
3. Create MI account and follow instructions for unlocking request.
3. Wait for one week. Xiaomi will authorize the unlocking.
4. Use the Xiaomi unlock tool.
5. Enable USB debugging.
6. copy the rom.zip in your SDCard.
6. Using ADB , boot to TWRP.
7. from TWRP, install the TWRP recovery image (optional)
8. follow the instructions for flashing A13. Normally you need to wipe DATA partition.

usb connection script

Hello
I am going to write a script that will run another script When the USB device is connected.
I used a rule called 99-my-usb-rule.rules in /etc/udev/rules.d
All the work I did and the error log are all in the attached image file
Can anyone help me?
{
"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"
}

debug your commands/scripts in shell first , to see if they run and do what you want them to.
bash -x ./script.sh ( for detailed debugging )
then running from udev script just like running from crontab
is a very sterile environment unlike a login shell.
do "/usr/bin/env > /tmp/udev-env.txt" from udev script to see what it set and what is not.
vs "env > /tmp/login-env.txt" from a login shell , which would have all sorts of things set besides paths that might be missing etc...
and you are also not specifying any devices ( do you want script to run on all usb device connections? )
lookup udev rules if you want something a bit more specific.
also you do not need /bin/bash if you have shebang #!/bin/bash as first line of your script
just execute your /path/to/script.sh ( make sure it is an executable )