Stratos - adb swipe - Amazfit

Hello.
Is it possible to send adb swipe command to Stratos? Touch is not working and bootloader is locked but I want to upload trainings before reinstalling ROM. I already tried it but im not sure if im doing sometihng wrong or is it just impossible.

Yes, it works. Try using a remote Android controller app, there are a couple the works (they only require adb).
PS: don't get your hopes high on fixing any hardware issue by reflashing firmware, it is a mith. Unless you flashed the wrong firmware on watch and this caused the problem, reflashing won't help. If watch's bootloader is still locked you should try to contact the seller and get the device replaced Instead...

Related

[Q] how to test touchscreen with adb

Hello, all ROM makers, developers, hackers and advanced users.
I have a problem and hope you can give me some good advice.
Here is my sad story
You can read the full description if you want. Or you can skip it - the main question in the end of this post..
I have bought a new Sony ericsson Live! with walkman (wt19i) phone during my newyear holydays in Prague. It seemd to be working fine.
It is from rev.3, manufacture date 11/49 (mounth/week)
When I came back home and started using it, I saw that after some inactivity period (about couple hours or maybe more) the touch screen, back and menu snsor buttons stops any responsing. Hardware buttons (home, volume, camera, walkman and power) are still working. The system also continues to work as usual, so I can turn it on (but can not slide to unlock), I can hear if somebody calls me (but can not answer). Alarms, notifications and all another functions are still working.
Once or twise it started to work again (by itself, without any actions by me) but after few time the problem repeated. I was very unhappy and sure it was a hardware problem (and of course the Czech warranty does not work in Russia), but now i'm not so sure.
The phone had 4.0.2.A.0.58 firmware (android 2.3.4) from the box. First of all I tried to install SE PC Companion software, connect phone with usb and make factory reset... touchscreen started to work! But soon I saw this problem again.
The next day a new update was released and installed it (firmware .62). My phone was working again, but with the same result after some time.
You shoud know, that simple softreset (or ejecting and inserting battery) has absolutesy no effect on problem. After system starts I can not even unlock it. But flashing a new (or even the same) firmware (with flash tool or SE PCC) makes touchscreen and buttons working for some time. Have no idea why, but installing ROM with CWM (even with full wipe) does not make touch working.
Then I tried to use another custom kernels and ROMs. I unlocked the bootloader with fastboot tool, flashed one of custom ROMs from this forum (pre-rooted and with CWM). Then tried to use CM7.2 ROM... then another kernel and another ROM. Official, official-based, totally unofficial. The problem was with me each time after couple hours
I thought it is because some troubles in lock screen. Tried to install "no lock" app, so my phone did not use lock... but after some time touch freezes in home screen.
I disabled screen off while charging in settings and tried to leave the phone "wired" for some time... actually it worked fine all the time, and when I dicsonnected it it was still working... for couple hours.
I tried to install "no sleep" applications that does not allow CPU and screen to suspend. But it have no influense.
I even flashed CM9.0 ICS (very) beta ROM with the same result.
If it is just hardware problem - why it solves (for some time, but solves) with flashing? If it is a software problem - why it doesnt solve with new kernels and ROMs? My brain is ready to explode.
Now I have only one last idea and ask you to help me.
The question is:
How can I use adb or adb shell comands to get more information about the problem with touch?
I saw there is some log (logcat, stderr) tools, debug tools. I saw working lsmod, dmesg and mount commands in shell.
I think I shoud get all this information when all is ok. And then get it again when touch stops working and then compare, is it a good idea?
Where exactly shoud I see? How to test or get some touch input device info with adb? Is there any item in /dev that i can explore? Or something in dmesg? Where are touch driver located and how can I check if it is working?
I have some basic linux and andriond skills, but have not enought expierence.
I very (VERY) hope somebody can give me any useful advice to continue solving the problem. Where to see, what to do?
Thank you
P.S.: and sorry for mistakes, of course. English is not my native language.
P.P.S.: i am not sure where is the best place for this question: here or in xperia subforums. But I decided that this question is not xperia-specific and can be useful for other people in future.
Anybody? I have Lenovo Yoga B6000 with touchscreen problem and will be good if anyone know how can i test TS through ADB or shell.

Some problems with my Elephone.

Hello, so I changed my screen few weeks ago, and I started to notice that it won't work propelry, in menu or setting it's okay, but when I try to use apps, some of them wont work as it should. For example, i can't take photo in messenger, i can't send good game in Clash Royale. Screen seller sent my some files to update my phone, but I noticed that i can't get into recovery mode, only in factory mode, I tried to do factory reset, OTA update because mine is still 2016-06-08, but it won't update, I also tried flash those files without recovery mode(when you start downloading ant then turning off your phone), but it didn't work. Have any ideas, what it could be?
SliFaZ said:
Hello, so I changed my screen few weeks ago, and I started to notice that it won't work propelry, in menu or setting it's okay, but when I try to use apps, some of them wont work as it should. For example, i can't take photo in messenger, i can't send good game in Clash Royale. Screen seller sent my some files to update my phone, but I noticed that i can't get into recovery mode, only in factory mode, I tried to do factory reset, OTA update because mine is still 2016-06-08, but it won't update, I also tried flash those files without recovery mode(when you start downloading ant then turning off your phone), but it didn't work. Have any ideas, what it could be?
Click to expand...
Click to collapse
Did you replace the screen yourself or was it a kind of Elephone repair ? .. obviously changing a screen is a major kind of thing and (I would assume) it could cause issues if not done properly.
Have you tried to flash the 2016-06-08 Rom in Splash Tools (or a custom ROM) and checking to see if the issue still exists - Im sure if its your screen it would occur on whatever ROM you were using, as its a hardware fault. Thing is if its just a sioftware "glitch"... I would first flash TWRP in flashtools, then flash a ROM from within TWRP and check if the issue still persists.
Obvioulsy if the issue continues once youve tried this I guess your screen is faulty unfortunately
I would recommend using this TWRP version 3.0.2.8. here: https://www.androidfilehost.com/?fid=24727369092696060

[SOLVED] S9+ Fails to Unlock After Latest Pie OTA Update

Hey all,
My phone updated today and ever since I cannot move past the initial lock screen. When unlocked, the UI appears to crash and send me back to the lock screen. My pin code works for turning the phone off, restarting the phone and putting it into emergency mode, which indicates some sort of UI crash.
Because this is a new account I can't post a link to a video of the issue directly, but the YouTube video code is: 8ZhlH-Tt-NU
I have tried the standard fixes like wiping the cache partition and booting into safe mode, but these don't seem to make any difference. Unfortunately I never logged into my Samsung account on this device, so their 'Find My Mobile' service is not an option. I am however signed into my Google account on the device and it does have wifi/network enabled.
The phone is running PPR1.180610.011/G965FXXU2CSA8
On the phones internal memory is a bunch of photos from a recent trip to Japan, I'm a fool for not backing these up sooner but I would hate to lose them.
Has anybody experienced anything like this before, and is there any way for me to get back into the phone, or atleast recover the photos that I took?
Thanks!
Edit:
One potential route out of this I can see is sideloading the same or a subsequent OTA update using ADB to hopefully fix the issue. Unfortunately despite some digging I can't find any updates that will allow installation from: PPR1.180610.011/G965FXXU2CSA8
If anybody has any information on this specific firmware version (Is it beta 3? beta 4? ect.), its installation path and where files relating to it may be listed/hosted it would be appreciated. Also how disasterous would it be to take a mismatched OTA upgrade and modify the metadata to allow it to be sideloaded onto the phone? I assume this would almost certainly break the OS completely but I'm not too sure.
You can try to flash your firmware again with ODIN, but with the HOME_CSC (Important!)
profi_fahrer said:
You can try to flash your firmware again with ODIN, but with the HOME_CSC (Important!)
Click to expand...
Click to collapse
Thanks for the reply Profi I had no idea using HOME_CSC would retain user data. I have tried flashing a few different versions of Pie (wish HOME_CSC) using Odin but with no luck, every time the phone boots I have the same problem. Do you know if there is a sure way to downgrade to Oreo while retaining user data? I have seen a few posts of people attemping this and getting stuck in bootloops, eventually requrining them to factory reset.
To give a final update on this. I attempted the Oreo downgrade, upon reboot the phone was stuck in a bootloop so I updated to Pie again. When the phone booted I tried the pin code as quickly as I could, and after some glitchy graphics on the screen it unlocked. From here I turn on the stay awake while plugged in feature in the developer options and managed to transfer all my data over to PC.
I don't believe it was the firmware changes that actually made any difference, because any further attempts to put my pin in, to remove the pin code for example, failed and cause the same crashing behaviour.
All data is recovered, I have factory reset the phone and all appears to be behaving as normal again. If anybody stumbles upon this with the same issue, all hope is not lost, but unfortunately I was unable to determine a realiable way to overcome it. It seems in this case it was just dumb luck.
Thanks for the assistance.

Face Unlock not working after manual update to .187

after using the dialer menu to update to .187 on my lya-09 i can no longer use face unlock. i deleted the stored faces to see if this would fix it and i can no longer even enroll my face, it just sits at the look directly at the screen part and never goes any further. any ideas?
even after a factory reset i still cannot enrol face. it recognises my face is there but does not prompt me to turn my head like it usually does. i have no idea why
What's the dialer menu update method?
Found it.
djisgod I'm sorry that I can't offer you any help, but if you please keep us posted abot your problem and eventual solution. Thx in advance
It's probably seeing the software as modified and not allowing you to use the secure face unlock feature. Or it's broken by the update which might be why they've delayed it.
I'm not sure it is very strange. Does anybody know which apk or app it is that does the face enrolling so i can try and install a different version?
i have done the update, and face unlock works without any problem for me, but i also have the lya-l29
still no luck with this. i have tried reset to factory settings and reinstalling the firmware. neither work.
and now it has suddenly started working again. lol not sure why it stopped but i am glad its back!
which update file have you used to update your phone?
describe exactly which file you've used to update via dialer menu AND even which model do you use?
I used the update for my phone the lya-09 c432. 9.0.0.187 update file. All is working fine now. Not sure what was going on but face unlock is now working again.

Amazfit Pace (A1612) can't reset, button not working

Hi everyone,
After hours reading posts, I couldn't find answers for my question. So I got an Amazfit Pace second hand, but it doesn't function as normally would.
The problems so far:
-power button not working
-doesn't connect to smartphone
-wifi, bluetooth, and qr code connection not available
-factory reset from watch just do normal reboot
-from PC can't unlock bootloader, can't wipe the data, can't enter fastboot.
The solutions I've tried so far: full dissasebmly the watch: no corrosion, water damage, broken cables. Downloadad adb tools, and do reset with commands like "adb shell reboot bootloader", "adb wipe reboot", and so on, but every time it just reboots normally. I've downloaded the All In One tool, but it didn't work so far.
I've read similar issues, especially with power button, but those users didn't get answers, and I'm kinda lost.
I would be really happy if someone could direct me to to the right thread, or give hints how to solve this problem. It doesn't matter how hard it is, I did similar things with phones, but this watch is really hard for me...
Thank you for reading it!
selyemretek said:
Hi everyone,
After hours reading posts, I couldn't find answers for my question. So I got an Amazfit Pace second hand, but it doesn't function as normally would.
The problems so far:
-power button not working
-doesn't connect to smartphone
-wifi, bluetooth, and qr code connection not available
-factory reset from watch just do normal reboot
-from PC can't unlock bootloader, can't wipe the data, can't enter fastboot.
The solutions I've tried so far: full dissasebmly the watch: no corrosion, water damage, broken cables. Downloadad adb tools, and do reset with commands like "adb shell reboot bootloader", "adb wipe reboot", and so on, but every time it just reboots normally. I've downloaded the All In One tool, but it didn't work so far.
I've read similar issues, especially with power button, but those users didn't get answers, and I'm kinda lost.
I would be really happy if someone could direct me to to the right thread, or give hints how to solve this problem. It doesn't matter how hard it is, I did similar things with phones, but this watch is really hard for me...
Thank you for reading it!
Click to expand...
Click to collapse
Does touchscreen work? If button and touchscreen don't work, it could be related to a wrong firmware flash, i.e. Stratos firmware instead of Pace.
You can do a factory reset with
Rich (BB code):
adb reboot wipe
But if the problem is related to a firmware issue, bad update,... it may not work.
Firmware issues could be solved flashing stock firmware using Cloner Tool, no need unlocked bootloader, if you can enter into deep flash mode with the button trick. Look for the thread in the forum.
If the problem is hardware related, problably it may have no solution.
Saratoga79 said:
Does touchscreen work? If button and touchscreen don't work, it could be related to a wrong firmware flash, i.e. Stratos firmware instead of Pace.
You can do a factory reset with
Rich (BB code):
adb reboot wipe
But if the problem is related to a firmware issue, bad update,... it may not work.
Firmware issues could be solved flashing stock firmware using Cloner Tool, no need unlocked bootloader, if you can enter into deep flash mode with the button trick. Look for the thread in the forum.
If the problem is hardware related, problably it may have no solution.
Click to expand...
Click to collapse
Thank you for the reply, I tried the "adb reboot wipe" code, but it just keeps rebooting normally like a champ. The PC shows previous songs, and trainings. The touchscreen, stopwatch, timer, compass work, so I can navigate in the watch. I tried that method, just to put it in the deep flash mode by holding down the watch button and reboot from the AIO too, but after the screen lit up and waiting 3-4 secs and double press the button, the watch reboots normally.
At this point I would literally pay someone who can help me.
Edit: I ran the
Rich (BB code):
adb logcat
and while it was running a pressed the power button. It registered, but in the log file it was "'á@'á@" or something (maybe) corrupted code. Also it gave errors for the bluetooth. Here is the log file:
Does Alexa works on amazfit pace, or is there a way to use amazfit pace microphone ?????
Thank you very much Saragota.....
Tigerclaw10000 said:
Does Alexa works on amazfit pace, or is there a way to use amazfit pace microphone ?????
Thank you very much Saragota79.....
Click to expand...
Click to collapse
Tigerclaw10000 said:
Does Alexa works on amazfit pace, or is there a way to use amazfit pace microphone ?????
Thank you very much Saragota.....
Click to expand...
Click to collapse
Look for WOS ROM, it has Verge's Alexa support instead of the Chinese voice assistant. Not sure if it will still work with latest Zepp app versions.
Recently, my PACE also had the same symptoms, without me changing anything in it.
I tried to do a factory reset, but it only reboots.
And I wasn't any smart to unpair with Zepp, now I can't do anything with him anymore.

Categories

Resources