HELP!
I need your help to get my Smartwatch running properly. By mistake I bought a Amazfit 2S in the Chinese language and I have been trying to convert it to English. I did run the commands mentioned in the below video, but it messed up the setup in my watch. Now I ONLY have the watch (see picture) and all other functionalities have disappeared.
Now my watch only shows the clock and no other functionality. Every time I press the ON button I get the message "Unfortunately launcher has stopped." When I press the tick mark then I continue to get the same message in an endless loop. If I don't do anything then the the Smartwatch returns to the watch mode in app. 10 seconds.
I hope someone can help me.
I'm not allowed to post link
MaherSaqib said:
HELP!
I need your help to get my Smartwatch running properly. By mistake I bought a Amazfit 2S in the Chinese language and I have been trying to convert it to English. I did run the commands mentioned in the below video, but it messed up the setup in my watch. Now I ONLY have the watch (see picture) and all other functionalities have disappeared.
Now my watch only shows the clock and no other functionality. Every time I press the ON button I get the message "Unfortunately launcher has stopped." When I press the tick mark then I continue to get the same message in an endless loop. If I don't do anything then the the Smartwatch returns to the watch mode in app. 10 seconds.
I hope someone can help me.
I'm not allowed to post link
Click to expand...
Click to collapse
Those commands will only work for Amazfit Pace, on newer devices will not work.
If you want English language, you need to 1. unlock the bootloader and 2. flash Stock US firmware for your Stratos. Everything you need is here in the forum.
Meanwhile, you can set back your device into chinese:
Code:
adb shell setprop persist.sys.language zh
adb shell setprop persist.sys.country CN
adb reboot
Saratoga79 said:
Those commands will only work for Amazfit Pace, on newer devices will not work.
If you want English language, you need to 1. unlock the bootloader and 2. flash Stock US firmware for your Stratos. Everything you need is here in the forum.
Meanwhile, you can set back your device into chinese:
Code:
adb shell setprop persist.sys.language zh
adb shell setprop persist.sys.country CN
adb reboot
Click to expand...
Click to collapse
Thanks a lot. You saved my day
Can you plz post a link to the instructions for a layman to convert from Chinese to English?
I have tried this several times and it always get stuck with the last command.
************************
C:\Users\kcv269\Desktop>adb devices
List of devices attached
adb server is out of date. killing...
* daemon started successfully *
9a402c2f device
C:\Users\kcv269\Desktop>ADB shell reboot bootloader
C:\Users\kcv269\Desktop>fastboot devices
C:\Users\kcv269\Desktop>fastboot reboot
< waiting for device >
When I restart CMD
********************************
C:\Users\kcv269\Desktop>adb shell reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
C:\Users\kcv269\Desktop>fastboot getvar all
< waiting for device >
Related
This is a copy of the comment I made in the [Help] topic, figured I would make a separate post since that thread is a mess. Anyway, credit for the method is to krytikul and evelpotatoman. I am not responsible for any damage/unwanted results/house fires. Use at your own risk yada yada.
Without furher ado, here is my tutorial for those who want working SuperSU on their MDZ-16-AB Mi Box 3. Warning: since the bootloader isn't unlockable yet, you will have to connect a laptop to run some commands EVERY TIME YOU BOOT UP THE MI BOX. If you do not connect to run the specified commands YOUR DEVICE WILL BOOTLOOP, it won't even be able to boot in unrooted state. Luckily, this doesn't apply to waking up from standby mode, so as long as you keep your Mi Box plugged in and don't power it off, you'll be fine.
You will need:
A USB male to male cable (I made one myself soldering two cable plugs together)
Mi Box Marshmallow userdebug firmware ROM (this guide will not work if you are already on Nougat test build)
SuperSU installation files
The ability to use adb on your computer
The steps:
Put the downloaded userdebug firmware ROM on a FAT32 formatted drive.
Enable developer options on the Mi Box. This can be done in your settings, find "About" and then click on "build" 7 times to enable the developer options. It will confirm you've done this with an on-screen toast notification.
Connect the Mi Box to your computer and check if a device comes up when typing "adb devices" in command prompt. If not, wait for the Mi Box to display a dialogue confirming you want to allow adb on this computer.
Type "adb reboot recovery" to put the Mi Box in recovery mode. Once in recovery, unhook the cable and plug in your usb, click "Apply update from EXT" then "Update from udisk" and select MiBOX3_USA_once_r454.zip, then just let the update do it's thing.
Reboot the device. Once we're back, see if the box is still under adb devices.
Now run these commands:
Code:
adb root
adb remount
adb disable-verity
adb reboot
The device will reboot. Once it's rebooted, run these commands to disable OTA updates (otherwise it will immediately update to an unrootable firmware
Code:
adb root
adb remount
adb shell pm disable com.google.android.gms/.update.SystemUpdateService
adb shell pm disable com.google.android.gms/.update.SystemUpdateService$ActiveReceiver
adb shell pm disable com.google.android.gms/.update.SystemUpdateService$Receiver
adb shell pm disable com.google.android.gms/.update.SystemUpdateService$SecretCodeReceiver
adb shell pm disable com.google.android.gsf/.update.SystemUpdateActivity
adb shell pm disable com.google.android.gsf/.update.SystemUpdatePanoActivity
adb shell pm disable com.google.android.gsf/.update.SystemUpdateService
adb shell pm disable com.google.android.gsf/.update.SystemUpdateService$Receiver
adb shell pm disable com.google.android.gsf/.update.SystemUpdateService$SecretCodeReceiver
adb reboot
Wait for the device to reboot. Now we've disabled OTA updates we can install SuperSU. Unzip the SuperSU installer and run the installer BAT script. When the script is done, it will seem as if the device is bootlooping. From now on, this will happen EVERY TIME THE DEVICE BOOTS. If you do not connect to run the specified commands YOUR DEVICE WILL BOOTLOOP, it won't even be able to boot in unrooted state. Below are the steps you should perform to get your device to boot in SuperSU-rooted state.
While the bootanimation is running, keep executing "adb devices" until your device is in the list.
Once the Mi Box is in the adb devices list, type "adb root" and press enter. your device will be disconnected from adb again.
Keep executing "adb devices" again until the Mi Box reappears. When it's there, type "adb shell setenforce 0"
All these steps are performed while the bootanimation is playing. The device will boot shortly after the last command is executed. Be patient as it can take a while for the device to re-enter the adb devices list.
thanks. all works fine
maybe i'd try this.
but is there a way also to undo the rooting without reflashing the firmware? or is there also a script to undo or remove the root?
Hey guys;
hope you are all doing great, I need your help.
I have Oreo on my device and I really need to have permission to change my stupid launcher. I hate the original one.
does anybody know how to give this permission to my device when I have Oreo?
you know? before Oreo there were a lot of problem with device and wifi.
But all gone with Oreo, and now I don't have any admin Permission.
please help.
thanks a lot.
arashdan89 said:
Hey guys;
hope you are all doing great, I need your help.
I have Oreo on my device and I really need to have permission to change my stupid launcher. I hate the original one.
does anybody know how to give this permission to my device when I have Oreo?
you know? before Oreo there were a lot of problem with device and wifi.
But all gone with Oreo, and now I don't have any admin Permission.
please help.
thanks a lot.
Click to expand...
Click to collapse
N o Can Do!!
Final answer.......
The link to google drive is dead can someone plz repost
LgPWN'd said:
The link to google drive is dead can someone plz repost
Click to expand...
Click to collapse
Won't do you much good if your mdz-16-ab is not on a MM build
Uart
bigtalker said:
Won't do you much good if your mdz-16-ab is not on a MM build
Click to expand...
Click to collapse
I have decided to go a different route...
Ordered a uart rig
LgPWN'd said:
I have decided to go a different route...
Ordered a uart rig
Click to expand...
Click to collapse
Good luck wid dat!
I'm happy to tell you magisk and twrp on mdz-16-ab is possible. And I managed to do this. It need a small hack on u-boot. I need someone who have this device to do more tests for this method.
Hi. I have a Amazfit Stratos with stock CN firmware 2.0.34.2 and I can't seem to get it to boot into fastboot mode. Whenever I run "adb shell reboot bootloader" in CMD, the watch just reboots normally. The watch is recognized by my computer in device manager. Just trying to unlock the bootloader. Any ideas what I could try?
Thanks!
vinny13 said:
Hi. I have a Amazfit Stratos with stock CN firmware 2.0.34.2 and I can't seem to get it to boot into fastboot mode. Whenever I run "adb shell reboot bootloader" in CMD, the watch just reboots normally. The watch is recognized by my computer in device manager. Just trying to unlock the bootloader. Any ideas what I could try?
Thanks!
Click to expand...
Click to collapse
How about this? adb shell reboot fastboot
If that doesn't work, then try this. https://forum.xda-developers.com/sm...tches/amazfit-boot-fastboot-directly-t3546829
What does the code below do?
Code:
adb shell
reboot bootloader
You can always use manual mode, as it's explained in Anox link.
Hi guys sorry for the delayed response. Tried both suggested ADB commands and attempted a handful of times to manually enter fastboot mode (according to instructions in link) and in each case it just reboots normally. Is there a debug mode setting that needs to be toggled beforehand or something?
I've also tried using the Huami Amazfit Tool app to reboot it into fastboot mode and it still reboots normally.
vinny13 said:
Hi guys sorry for the delayed response. Tried both suggested ADB commands and attempted a handful of times to manually enter fastboot mode (according to instructions in link) and in each case it just reboots normally. Is there a debug mode setting that needs to be toggled beforehand or something?
I've also tried using the Huami Amazfit Tool app to reboot it into fastboot mode and it still reboots normally.
Click to expand...
Click to collapse
Fastboot mode should always be accessible.
That tool & others basically use the same command to access fastboot mode.
The manual method is supposed to be the last resort. I now have no idea, sorry.
Have you found a solution yet? I have exactly the same problem.
Gavros7 said:
Have you found a solution yet? I have exactly the same problem.
Click to expand...
Click to collapse
If
Code:
adb shell reboot bootloader
does not work for you due to some reason, you can do it manually only: it uses the buttons and need some tries because it's tricky. It is the same process as Pace, search forum or YouTube for more info.
lfom said:
If
Code:
adb shell reboot bootloader
does not work for you due to some reason, you can do it manually only: it uses the buttons and need some tries because it's tricky. It is the same process as Pace, search forum or YouTube for more info.
Click to expand...
Click to collapse
@vinny13 Did you solve your problem?
I have exactly the same problem.
When I try "adb shell reboot bootloader" the answer that appears is "- exec '/ system / bin / sh' failed: Permission denied (13) -
using port = 5555 "
Manually I've tried over 70 times and I don't know what else to do to get into this FastBoot ...
I think I was drawn!
Thanks for any help.
alexsouza said:
@vinny13 Did you solve your problem?
I have exactly the same problem.
When I try "adb shell reboot bootloader" the answer that appears is "- exec '/ system / bin / sh' failed: Permission denied (13) -
using port = 5555 "
Manually I've tried over 70 times and I don't know what else to do to get into this FastBoot ...
I think I was drawn!
Thanks for any help.
Click to expand...
Click to collapse
Using the button trick is the only way you have to enter into fastboot.
Saratoga79 said:
Using the button trick is the only way you have to enter into fastboot.
Click to expand...
Click to collapse
Thanks for your response, @Saratoga79. Has anyone seen any cases that the watch does not enter Fastboot or the button? I say this because the operating system of the clock was always crashing ... Now the only screens that appear to me are "A" and "No Command".
I will keep trying the button method. I confess it has been over 90 times.
Hello, I have an Amazfit Stratos (details attached as a screenshot from AmazMod app) and I have a problem entering fastboot (I want to unlock the bootloader and start having fun with the watch )
What I've already tried:
- standard ADB mode, the watch is recognized and seen in ADB, but when I enter adb shell reboot fastboot - it just reboots back to the usual OS...
- the All In One Tool available on XDA - the same issue - watch is recognized but when I click reboot to fastboot - it just boots up normally...
- manual method described on the forum and shown on youtube - the issue is, when the screen goes dark I'm supposed to wait 4 seconds before releasing the power key - and my watch shows up the Amazfit logo after 2 seconds - the whole bootup process is different than on the video - I've been at it for 2 hours and did not manage to get it to fastboot once
- I've also tried using the AmazMod app - there's a section there that allows you to send direct commands to the watch shell - I've tried reboot fastboot and the watch also reboots back to the standard OS
- I tried the method with adb kill-server / adb start-server / adb wait-for-device and then rebooting the watch (method found on the forum as well) - no cigar.
I'm getting desperate - I wanted the stratos mostly because of the awesome job devs do making it better - now I'm left with the stock watch and to be honest I think Huawei Watch GT would be better for my needs if I'm comparing stock vs stock...
Did anyone have any similar issues?
Anyone? Getting desperate and still no solution in sight...
AmazMod widget also has a "Reboot to fastboot" option, but it is the same as the adb command, I think you are using the wrong command, the correct one is:
Code:
adb shell reboot bootloader
and not "reboot fastboot". Manually always works too, if watch turns on (you can see Amazfit logo) and button isn't broken.
Yeah I've tried both reboot fastboot and reboot bootloader with the same non result
maslosky said:
Yeah I've tried both reboot fastboot and reboot bootloader with the same non result
Click to expand...
Click to collapse
You must use exactly the same commands as I wrote, "adb reboot bootoloader" does not work.
ADB method just causes the watch to reboot regularly... Nobody is able to help?
If the adb command doesn't work for some weird reason, then the only way is doing it manually. It is very trick, but it works. You may want to flash a stock ROM first, as it is the only explanation why "adb shell reboot bootloader" does not work for you...
I do have a stock rom since I haven't been able to unlock bootloader (because I can't enter fastboot) - manual entry is not working, as I've mentioned my watch is acting differently than the watch presented in the YouTube video... I'm stuck
Did you try to facttory reset yet?
Code:
adb reboot wipe
OK so I finally managed to get the watch to fastboot mode, manual method is still not working, but after a factory reset and TOTAL removal of ALL adb drivers (total wipe of any adb/fastboot drivers from Win10) - it finally worked using the All In One Tool from the forum. This can be closed now. Thanks for all the suggestions - I'm not sure if the factory wipe helped or the Win10 drivers wipe - but it works I'm on to bigger and better things
maslosky said:
OK so I finally managed to get the watch to fastboot mode, manual method is still not working, but after a factory reset and TOTAL removal of ALL adb drivers (total wipe of any adb/fastboot drivers from Win10) - it finally worked using the All In One Tool from the forum. This can be closed now. Thanks for all the suggestions - I'm not sure if the factory wipe helped or the Win10 drivers wipe - but it works I'm on to bigger and better things
Click to expand...
Click to collapse
Can u elaborate on thr driver's removal?
Never actually got it done, But see the last post for a workable solution.
Hi all.
The basics:
Device Samsung Galaxy Tab A SM-T295 android 9 PC WIN 7 PRO
Trying to do this >> https://www.xda-developers.com/change-sms-limit-android/
Started this >>> https://www.xda-developers.com/install-adb-windows-macos-linux/
Got this:
I have the USB DEBUGGUNG turned on.
I get the COMMAND WINDOW open
I enter "adb devices" and I get a result
list of devices attached
Enter again and it doesn't show a serial number.
If command
Code:
adb devices
doesn't bring up any device, then an USB connection isn't successfully established. Read here how to fix it.
If device got successfully connected you get its serial-number entering command
Code:
adb shell getprop ^| grep ro.boot.serialno
jwoegerbauer said:
If command
Code:
adb devices
doesn't bring up any device, then an USB connection isn't successfully established. Read here how to fix it.
If device got successfully connected you get its serial-number entering command
Code:
adb shell getprop ^| grep ro.boot.serialno
Click to expand...
Click to collapse
OK. Since running "adb devices" returned "list of connected devices",, that would seem to indicate that the adb did start.
But as a test I will do the following from the other thread:
Type in cmd
adb kill-server
adb start-server
Click to expand...
Click to collapse
A lot of that other thread seems to be directed at LINUX users and the thread starter was working on a rooted device which I do not have.
Going to do this
run cmd as Administrator
Click to expand...
Click to collapse
too.
This looks promising so after the above I will try it:
it's so easy, just turn off your android device, then hold down both "Volume Down" key and "Power" at the same time, wait a few seconds till it start in recovery mode, done.
now type adb devices, and you'll see your device.
Click to expand...
Click to collapse
Back later
Cut_Right_Sharpening said:
OK. Since running "adb devices" returned "list of connected devices",, that would seem to indicate that the adb did start.
But as a test I will do the following from the other thread
Back later
Click to expand...
Click to collapse
OK.
Got this from everything except going into recovery mode.
C:\Users\790W7\Downloads\TAB A Stuff\platform-tools_r29.0.6-windows\platform-too
ls>adb kill-server
C:\Users\790W7\Downloads\TAB A Stuff\platform-tools_r29.0.6-windows\platform-too
ls>adb server
C:\Users\790W7\Downloads\TAB A Stuff\platform-tools_r29.0.6-windows\platform-too
ls>adb shell getprop ^| grep ro.boot.serialno
error: no devices/emulators found
Click to expand...
Click to collapse
Cut_Right_Sharpening said:
OK. Since running "adb devices" returned "list of connected devices",, that would seem to indicate that the adb did start.
This looks promising so after the above I will try it:
it's so easy, just turn off your android device, then hold down both "Volume Down" key and "Power" at the same time, wait a few seconds till it start in recovery mode, done.
now type adb devices, and you'll see your device.
Back later
Click to expand...
Click to collapse
Ok this is what I got in recovery mode on the Tab A
https://drive.google.com/open?id=1SCYtbrZKnnfrkNVP34S-H9Jq0SQHSYqj
Still getting this from the CMD WINDOW
C:\Users\790W7\Downloads\TAB A Stuff\platform-tools_r29.0.6-windows\platform-too
ls>adb shell getprop ^| ro.boot.serialno
error: no devices/emulators found
C:\Users\790W7\Downloads\TAB A Stuff\platform-tools_r29.0.6-windows\platform-too
ls>
Click to expand...
Click to collapse
@Cut_Right_Sharpening
Is the device shown with a yellow exclamation mark in the Windows device manager when in recovery mode? If so then look inside device's build.prop file - it's located in directory /system:
ro.adb.secure mut be set to 0
and
ro.debuggable must be set to 1
to allow the device gets ADB accessed in both the recovery mode and the normal mode.
BTW:
Wondering why the hell you started the device in recovery mode to access it via ADB? Noone does so, me included.
jwoegerbauer said:
@Cut_Right_Sharpening
Is the device shown with a yellow exclamation mark in the Windows device manager when in recovery mode? If so then look inside device's build.prop file - it's located in directory /system:
ro.adb.secure mut be set to 0
and
ro.debuggable must be set to 1
to allow the device gets ADB accessed in both the recovery mode and the normal mode.
BTW:
#1 Wondering why the hell you started the device in recovery mode to access it via ADB? Noone does so, me included.
Click to expand...
Click to collapse
#1 Because that was one of the suggestions by this guy https://forum.xda-developers.com/member.php?u=5498377 in the thread I was sent to by the first poster.
Yes, The SM-T295 has the exclamation mark.
If so then look inside device's build.prop file - it's located in directory /system:
ro.adb.secure mut be set to 0
and
ro.debuggable must be set to 1
to allow the device gets ADB accessed in both the recovery mode and the normal mode.
Click to expand...
Click to collapse
With WHAT????
@Cut_Right_Sharpening
This is my last post here: Honestly, I have no lust telling you how to successfully run ADB - this may do others here.
What you should know:
1.
Especially for Samsung devices a device-relevant USB driver for Windows OS provided by Samsung Co.Ltd. exists. Hint: Install the one that matches your device, don't further on make use of the obscure one you've already installed.
2.
ADB needs neither the device to be rooted ( unless you want to perform system relevant operations such as modifying system properties ) nor to be run as Administrator nor something else.
3.
Running Android in recovery mode only is useful if you want to perform system maintenance operations, such as
a) reboot system
b) apply update from SD card
c) apply update from cache
d) wipe data/factory reset
e) backup user data
f) restore user data
Note that on stock recovery the ADB utility only registers that the device is connected. When you try applying adb shell or any other thing you'll get an error: it only accepts adb push commands to the device.
Good luck.
jwoegerbauer said:
@Cut_Right_Sharpening
This is my last post here: Honestly, I have no lust telling you how to successfully run ADB - this may do others here.
Good luck.
Click to expand...
Click to collapse
Well, The link to the Drivers may someday be very useful.
I am going to change the thread line to indicate I have given up. There may be people that have the knowledge to do this, but I suspect Google has been working overtime to make it nearly impossible without rooting and I am not ready to go that far.
Should someone else stumble on this thread, it looks like my solution is going to be HitEmUp APP . Not exactly a fully automatic Bulk mailer, but I think it will work for what I want as long as I stay under the 30 SMS/30Minute limit.
Hello everyone, hope you're fine,
Unfortunately, I had bad luck and utterly smashed my device display (Samsung Galaxy A72) which has a PIN to unlock the device access.
My problem here is that I'm unable to accept the authorization for adb connection, just can't touch the accept popup (which I suppose is "being displayed" on the broken screen).
There is by any chance, a way to send a touch signal using the adb prompt?
The current status when I try any command except the
Code:
$ adb devices
is:
Code:
$ adb shell
adb: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
In case I can get this resolved, the next steps would be to try to send the adb input keyevent accordingly in order to unlock it by PIN.
Thx in advance to anyone who is able to help
Note: I'm using Linux or Mac, so MS Windows wouldn't help too much.