Amazfit Stratos - Looping Startup - Amazfit

When I try to access the fastboot of my Stratos Amazfit it is no longer recognized by the computer. Can someone help me?
It is looping at startup and does not turn on.
I need help getting my watch back.
Thank you in advance.
[email protected]

I'm having the same thing.
It gets to the point of optimizing apps, then starts over. (Repeats nonstop)
Mine was precipitated by installing an apk with android commander.
The apk was supposed to contain a Doctor Who watch face.
Thanks.

tiltawurl said:
I'm having the same thing.
It gets to the point of optimizing apps, then starts over. (Repeats nonstop)
Click to expand...
Click to collapse
Try this using adb (command line), it will erase all data on watch and restart, no requirements besides adb:
Code:
adb reboot wipe

lfom said:
Try this using adb (command line), it will erase all data on watch and restart, no requirements besides adb:
Code:
adb reboot wipe
Click to expand...
Click to collapse
It takes the command and "does something."
One time when it rebooted after the wipe, it only had "total 30" apps to optimize.
Another time, "total 18" apps to optimize.
Still, however, rebooted itself while "launching apps," getting back to its original "total 44" apps to optimize and the reboot loop.
I'm not particularly concerned about loss of data, since I've only had the watch a little over a month,.
Voiding the warranty (rooting) would not be acceptable, since my last resort would be sending it back to Amazfit for reset.
Thanks.

tiltawurl said:
It takes the command and "does something."
One time when it rebooted after the wipe, it only had "total 30" apps to optimize.
Another time, "total 18" apps to optimize.
Still, however, rebooted itself while "launching apps," getting back to its original "total 44" apps to optimize and the reboot loop.
I'm not particularly concerned about loss of data, since I've only had the watch a little over a month,.
Voiding the warranty (rooting) would not be acceptable, since my last resort would be sending it back to Amazfit for reset.
Thanks.
Click to expand...
Click to collapse
You must use the command when it finishes updating apps or it will not work (it will erase all data and restart watch), if you are on Windows:
Code:
adb wait-for-device & adb reboot wipe
If you are on macOS/Linux:
Code:
adb wait-for-device; adb reboot wipe
Other than this, other options require unlocking bootloader, what voids warranty.

Amazfit support sent me a reset tool that worked perfectly.

tiltawurl said:
Amazfit support sent me a reset tool that worked perfectly.
Click to expand...
Click to collapse
dude, can u write e-mail of Amazfit support or something?
i have same problem with my new Stratos 3, commands doesnt help me...(

still hope to resolve this =(

tiltawurl said:
Amazfit support sent me a reset tool that worked perfectly.
Click to expand...
Click to collapse
Can you please share this woderful tool to the community?
Thx in advance!

Related

Bootloop After Messing With Greenify and NoBloat

I rooted and installed custom recovery on my HDX7 using the HDX Toolkit according the the given instructions. After a few days I decided to uninstall recovery and moved the TWRP backup to external storage. I hadn't installed any custom roms or created any rom slots. I had no problems for days until these changes I made last night.
I uninstalled towelroot, reading that it was safe to do so. I installed a flashlight app. I installed Greenify and auto-hibernated some some third-party apps - including ES FileManager and Safestrap, which I considered safe since I had already uninstalled recovery. I installed NOBLOAT and disabled (not uninstalled) a few other processes and preinstalled Amazon apps as well. I also turned WIFI off before shutting down.
The device is now stuck at the second splash screen with the animated white and gold Kindle Fire logo. The screen is also slightly dimming and brightening repeatedly. I can't get into safe-mode/ recovery mode. I looked up what I was disabling but think I goofed using NoBloat and Greenify and screwed myself by uninstalling recovery.
What should I do and how? Will uninstalling nobloat, greenify and flashlight through adb RENABLE the disabled and hibernated apps and revert to previous settings? I have the TWRP stock rom backup on my computer! Can I flash that if nothing else works?
I'd appreciate the help and instruction, thank you.
Segue2 said:
...
What should I do and how? Will uninstalling nobloat, greenify and flashlight through adb RENABLE the disabled and hibernated apps and revert to previous settings? I have the TWRP stock rom backup on my computer! Can I flash that if nothing else works?
I'd appreciate the help and instruction, thank you.
Click to expand...
Click to collapse
Did you try hard reset? Press power button for more than 20 sec. Your kindle should then restart itself hopefully without bootloop. I was once messing with rooted stock fire OS trying to add one app to system apps (live wallpaper support I think), after restart I get neverending bootloop, but I was able to get out of this by doing hard reset, then Safestrap showed again and I was saved.
If you can manage reverse all your changes on system through adb, good for you, but without installed Safestrap ... well, maybe someone with better skills can manage you through this ...
I have tried but hard resets aren't working.
Can you still access it through ADB?
EncryptedCurse said:
Can you still access it through ADB?
Click to expand...
Click to collapse
No, looks like I am having trouble getting adb access. Command adb devices is returning nothing. Windows is recognizing the Kindle, however, but only as a portable device. Definitely had adb access before (established to use the HDX Toolkit). Now, I am wondering whether I disabled adb support on the kindle at some point beforehand.
On a sidenote, I just unplugged and reconnected the usb cable a few times and was able to hit the lockscreen for a few seconds before falling back into the bootloop. I have been able to repeat this.
I have tried to follow GSLEON3's steps, http://forum.xda-developers.com/showthread.php?t=2588608&page=8, to regain ADB access. I haven't had any luck - windows keeps recognizing it as a portable device. Any other suggestions for driver installation?
Again, occasionally the lock screen comes up. It was up long enough for me to swipe open and see my installed apps on the carousel, at one point, before falling back into the bootloop!
I'll keep reading and trying to establish ADB, but I have a question. Given that I have only rooted and disabled some processes, without any other serious modifications (no build prob edit, no new partitions, no roms, no custom recovery anymore) do you think a factory reset would be safe at some point if I can't get adb access?
Segue2 said:
I have tried to follow GSLEON3's steps, http://forum.xda-developers.com/showthread.php?t=2588608&page=8, to regain ADB access. I haven't had any luck - windows keeps recognizing it as a portable device. Any other suggestions for driver installation?
Again, occasionally the lock screen comes up. It was up long enough for me to swipe open and see my installed apps on the carousel, at one point, before falling back into the bootloop!
I'll keep reading and trying to establish ADB, but I have a question. Given that I have only rooted and disabled some processes, without any other serious modifications (no build prob edit, no new partitions, no roms, no custom recovery anymore) do you think a factory reset would be safe at some point if I can't get adb access?
Click to expand...
Click to collapse
From what you're saying, a factory reset does sound sensible but I honestly don't want to guide you in the wrong direction.
EncryptedCurse said:
From what you're saying, a factory reset does sound sensible but I honestly don't want to guide you in the wrong direction.
Click to expand...
Click to collapse
doing a factory reset do not believe will remove something from system files if that is where he has pushed itand may cause complications. I do know from personal experience a factory reset with xposed framework gets really nasty really fast.I would keep trying to get ADB back...once you see it on your PC in any mode you must go to your device and device managers and uninstall all drivers. and reboot PC. Do not plug your device back in 2 PC till you have installed correct drivers
if nothing has been pushed to system and you have not install xposed framework...greenify will work with and without it I'm not sure about nobloat. Hdx signature bypass module requires xposed...did you attempt gapps installation? but if you know those two things for sure and for sure nothing pushed to system files you are safe to do a factory reset under factory recovery. The opposite button combination for recovery will result in safe mode boot...
more information?
jimyv said:
doing a factory reset do not believe will remove something from system files if that is where he has pushed itand may cause complications. I do know from personal experience a factory reset with xposed framework gets really nasty really fast.I would keep trying to get ADB back...once you see it on your PC in any mode you must go to your device and device managers and uninstall all drivers. and reboot PC. Do not plug your device back in 2 PC till you have installed correct drivers
if nothing has been pushed to system and you have not install xposed framework...greenify will work with and without it I'm not sure about nobloat. Hdx signature bypass module requires xposed...did you attempt gapps installation? but if you know those two things for sure and for sure nothing pushed to system files you are safe to do a factory reset under factory recovery. The opposite button combination for recovery will result in safe mode boot...
more information?
Click to expand...
Click to collapse
Thanks.
I did not install Xposed nor GAPPS. The only system modifications to device were 1) manual update to stock firmware 13.3.2.4. 2) Towelroot 3) Super SU 4) Safestrap, which is no longer installed 5) Disabled OTA updates using HDX Toolkit and 6) Greenify and Nobloat to disable 3rd party and system apps.
I havn't pushed anything else to system.
I am currently on Ubuntu trying to get adb access. I am NOT familiar with linux but I have gotten JDK and Android SDK installled. Still, no access and no device id number listed. Should I go back to windows and try again?
Also, I can't get into safe mode. And one more question - is it normal that the HDX can only be powered off while unplugged? If I plug in any power it automatically turns on and starts bootloop.
Segue2 said:
Thanks.
I did not install Xposed nor GAPPS. The only system modifications to device were 1) manual update to stock firmware 13.3.2.4. 2) Towelroot 3) Super SU 4) Safestrap, which is no longer installed 5) Disabled OTA updates using HDX Toolkit and 6) Greenify and Nobloat to disable 3rd party and system apps.
I havn't pushed anything else to system.
I am currently on Ubuntu trying to get adb access. I am NOT familiar with linux but I have gotten JDK and Android SDK installled. Still, no access and no device id number listed. Should I go back to windows and try again?
Click to expand...
Click to collapse
well it definitely would not hurt anything to try Windows again don't bother with a factory cable does not apply to this device we do not have the proper tools / softwareware
you might do a little reading over in toolkit thread at last few pages anyway I do not believe that you will get negative effect from just having OTA block with a factory reset. personally a factory reset per stock recovery that would be my next option.. as long as you know the only thing that has been pushed to system is su, and no xposed framework.
you may even have to re disable OTA updates.
remember plug in your device. Allow it to boot as far as it will boot if you can get it to boot into the running system that would be great just do not attempt to unlock it if that what crashes it. Go to Device Manager and uninstall all drivers for your device.
unplug it from PC and reboot PC. Then install correct ADB drivers and reconnect
jimyv said:
well it definitely would not hurt anything to try Windows again don't bother with a factory cable does not apply to this device we do not have the proper tools / softwareware
you might do a little reading over in toolkit thread and that you till the thread at last few pages anyway I do not believe that you will get negative effect from just having OTA block with a factory reset. personally a factory reset per stock recovery that would be my next option.. as long as you know the only thing that has been pushed to system is su, and no xposed framework.
you may even have to re disable OTA updates.
remember plug in your device. Allow it to boot as far as it will boot if you can get it to boot into the running system that would be great just do not attempt to unlock it if that what crashes it. Go to Device Manager and uninstall all drivers for your device.
unplug it from PC and reboot PC. Then install correct ADB drivers and reconnect
Click to expand...
Click to collapse
Ok, thank you. I will try fresh installs on Windows again, then. I did read an interesting tip by GSLEON3 about having a copy of cmd.exe in the sdk folder, which I didn't try.
Also, I can't get into safe mode. And one more question - is it normal that the HDX can only be powered off while unplugged? If I plug in any power it automatically turns on and starts bootloop and won't turn off, even on wallcharger.
lol
Segue2 said:
I will try fresh installs on Windows again, then. I did read and interested tip by GSLEON3 about having a copy of cmd.exe in the sdk folder, which I didn't try.
Also, I can't get into safe mode. And one more question - is it normal that the HDX can only be powered off while unplugged? If I plug in any power it automatically turns on and starts bootloop.
Click to expand...
Click to collapse
yes and personally I find it annoying as hell. The HDX does not charge powered off unless it is completely dead and it only charges for a few seconds and as soon as it has enough power to power up it powers up. completelynormal for this device
---------- Post added at 12:09 PM ---------- Previous post was at 11:47 AM ----------
Segue2 said:
Ok, thank you. I will try fresh installs on Windows again, then. I did read an interesting tip by GSLEON3 about having a copy of cmd.exe in the sdk folder, which I didn't try.
Also, I can't get into safe mode. And one more question - is it normal that the HDX can only be powered off while unplugged? If I plug in any power it automatically turns on and starts bootloop and won't turn off, even on wallcharger.
Click to expand...
Click to collapse
there are a couple of minimal adb and fast root utilities around XDA that's all I use...have you been able to get into stock recovery?
to enter SafeMode on thor...
hold power and volume down until grey logo cycles at least twice release power and continue to hold volume down until device completely boobs. if it works it should stay booted and allow you to uninstall third party apps it should say safe mode in left lower corner
jimyv said:
yes and personally I find it annoying as hell. The HDX does not charge powered off unless it is completely dead and it only charges for a few seconds and as soon as it has enough power to power up it powers up. completelynormal for this device
---------- Post added at 12:09 PM ---------- Previous post was at 11:47 AM ----------
there are a couple of minimal adb and fast root utilities around XDA that's all I use...have you been able to get into stock recovery?
to enter SafeMode on thor...
hold power and volume down until grey logo cycles at least twice release power and continue to hold volume down until device completely boobs. if it works it should stay booted and allow you to uninstall third party apps it should say safe mode in left lower corner
Click to expand...
Click to collapse
Ok, good to know about the power.
Yes, I have used the Minimal Adb and Fastboot utility before and couldn't get access.
I can get into stock recovery for a factory reset.
I can not get into SafeMode. It ends up booting to the lockscreen for a second or two before falling back into bootloop - sometimes flashing the lockscreen again.
okay well I do believe you have run out of options..in a nutshell you are looking at a replacement device anyway so you should be on the go for a factory reset
So, I tried establishing ADB in Windows and Ubuntu again with no luck. I went ahead with the factory reset. Now, it is just flashing the lockscreen repeatedly without the kindle fire logo bootloop.
Thank you for the help but I guess there is nothing more to be done?
by
Segue2 said:
So, I tried establishing ADB in Windows and Ubuntu again with no luck. I went ahead with the factory reset. Now, it is just flashing the lockscreen repeatedly without the kindle fire logo bootloop.
Thank you for the help but I guess there is nothing more to be done?
Click to expand...
Click to collapse
nope you are out of options before you got to the factory reset.apparently something was done to the system that nobody knew about. Or there is a hardware problem anyway.you can try to hold the power for over 20 seconds or another factory reset but sounds like you need to give Amazon a call anyway you might have had a bad unit. Because nothing you described in above paragraphs should have gotten you to this point.
Segue2 said:
... I installed NOBLOAT and disabled (not uninstalled) a few other processes and preinstalled Amazon apps as well.
Click to expand...
Click to collapse
Well, I think this is the main reason for your problems. In the past, when there was no alternatives I run modified FireOS + gapps from cpajuste and after a while I find that running all this amazon bloatware consuming so much memory and cpu power, so I did the same, installed greenify, some utility to disable running background services, through another utility (I dont remember the name) disabled several amazon apps I didnt use ... I was trying to make more space for running google tools ... Ofcourse I didnt do changes on stock rom, only on extra slot always with backups in case something went wrong. And it always did. FireOS is sure not your typical Android - at some point we all learn this.
So after several mostly not successfull experiments with disabling amazon apps (fireos ends in bootloop, or didnt start at all) i decided to give up and later when alternatives from ggow was available I completly switch to his rom and (not using amazon services at all) I am happy with his Nexus 2.0.2 till today.
So from my point of view you disables some (one or more) critical process which fireos really really need to complete startup sequence and thus bootloop you are experiencing. Without safety net (safestrap + using extra slot) there is not much to do, unless you somehow gain adb access, but this is now probably not an option after factory reset you did...
jeryll said:
Well, I think this is the main reason for your problems. In the past, when there was no alternatives I run modified FireOS + gapps from cpajuste and after a while I find that running all this amazon bloatware consuming so much memory and cpu power, so I did the same, installed greenify, some utility to disable running background services, through another utility (I dont remember the name) disabled several amazon apps I didnt use ... I was trying to make more space for running google tools ... Ofcourse I didnt do changes on stock rom, only on extra slot always with backups in case something went wrong. And it always did. FireOS is sure not your typical Android - at some point we all learn this.
So after several mostly not successfull experiments with disabling amazon apps (fireos ends in bootloop, or didnt start at all) i decided to give up and later when alternatives from ggow was available I completly switch to his rom and (not using amazon services at all) I am happy with his Nexus 2.0.2 till today.
So from my point of view you disables some (one or more) critical process which fireos really really need to complete startup sequence and thus bootloop you are experiencing. Without safety net (safestrap + using extra slot) there is not much to do, unless you somehow gain adb access, but this is now probably not an option after factory reset you did...
Click to expand...
Click to collapse
the loop he was in would not allow him ADB either ,something was done here other than what has been stated whether it was known or not.
correction I also use greenify it on all my devices. And to be able to do anything to system you must have had exposed framework installed....in which case I would have never have recommended a factory wipe. as stated several times already. simply hibernating a few apps even hibernating a few apps ( which is about all you can do without framework) would have not gotten him here. he had to have permanently removed something from system or permanently disabled iteither way without knowing exactlywhat service he appy that too it would be a guessing game even with adb.in short like you said lesson learned for another person that bothers to read this thread not to tamper with your stock system without safestrap at bare minimum and a backup
I wonder if he has had any luck with ADB now that he is no longer in a perpetual boot loop. May be able to come up with a reenable command for system apps? Su should still be in systemat least the binaries will be in case the app wasn't. And I think in this case it would be better if the app was not in system but the binaries remained since he cannot get into the OS he will not be able to grant permission..but without. su command should work still
Thanks for the input. Wiithout a doubt, lessons learned here. At the very least, I never should have uninstalled Safestrap even if I wasn't planning on doing anything else to the system. I have the TWRP backup of my rooted stock, but with no way to use it now - useless.
I must have disabled some critical app or combination of apps that lead to the conflict, despite the care I thought I was taking. As far as Xposed framework goes, I never installed it manually. Maybe it is packaged in with one of those apps? The other thing I wondered about was whether disabling wireless could have led to a conflict. Using the Toolkit has been reported to lead to a bug where the system can crash when trying to enable wifi without first enabling bluetooth.
Either way, all I had to do was leave safestrap alone, just in case. F.
All of your help and feedback has been appreciated!
Wow. Well, I have adb access. After mutliple unsuccessful attempts on Windows and Linux, I was able to fire up an old MacBook and established an adb connection in 10 minutes. Unbelievable! The list of installed packages doesn't show any third party packages. Can I push and install Safestrap through adb to get my backups up and running? Whar is the correct syntax for those commands? I have already got a replacement on the way, but I would like to try to bring this one back and unroot. On second thought, maybe I should just leave it?

Encryption error

I have a rooted tmobile lg v10, and I just tried to encrypt it using full disk encryption in settings. Right after I started the encryption the white screen with the green android shows up for about 1 second then the tmobile boot picture showed up and stayed there until I removed the battery. All my data is still here and my phone is exactly the same as when I started the encryption process. Any way to fix this?
You have a backup? If so go to your backup and delete your finger prints on it then try it all again
I have a titanium backup of apps. Would it work if I just disabled fingerprints?
No go into settings and delete all of the fingerprints. As a security measure they persist through encryption and a factory reset.
Removed my finger prints. Still doesnt encrypt my phone. Just sits at the same screen.
Are you completely stock? Rooted? Twrp?
You need to kill root first. Run this in terminal emulator:
pkill -KILL daemonsu
Then go through the encryption process.
See if that works.
blubyu87gt said:
You need to kill root first. Run this in terminal emulator:
pkill -KILL daemonsu
Then go through the encryption process.
See if that works.
Click to expand...
Click to collapse
the author did not reply so I guess it did work
shotguns10 said:
I have a rooted tmobile lg v10, and I just tried to encrypt it using full disk encryption in settings. Right after I started the encryption the white screen with the green android shows up for about 1 second then the tmobile boot picture showed up and stayed there until I removed the battery. All my data is still here and my phone is exactly the same as when I started the encryption process. Any way to fix this?
Click to expand...
Click to collapse
a_petrov303 said:
the author did not reply so I guess it did work
Click to expand...
Click to collapse
Haha yeah hopefully so! I haven't tried it on some of the 5.1.1 or 6.0 though.
I also have a rooted LG V10 and yes for encryption you have to do this (done on my phone) :
http://forum.xda-developers.com/g4/general/howto-encrypt-decrypt-phone-rooted-t3200256
I haven't tried it

Ulefone T1 - any lineageos development?

[email protected],
just bought myself an Ulefone T1 from aliexpress and I am wondering if there is any lineageos development out there for this phone? Is anybody planning to develop for this?
cheers
JohnnyT
Stay tunned. The phone is new and development will yet. Dont worry is a great phone and Ulefone is better than yesterday.
https://www.needrom.com/category/ulefone/t1-ulefone/
It will hardly receive official updates, let alone custom ROMs (same fate as the 96% of MediaTek devices out there).
any update . i just bought this phone from banggood. my asus zenfone 3 wifi is failing. so needed something to fill the gap
Finally received my t1 after 11 weeks of waiting!!
Everything works fine apart from the battery usage which is a round 10% per hour on standby with no usage!!
FOLLOW-UP
Following lots of research found that Whatsapp was still trying to verify the phone thru SMS and was draining the battery. Uninstalled and re-installed Whatsapp and verified by manually entering SMS pin.
Now appears to running okay at just over 2% per hour battery drain with bluetooth and GPS set on.
i think i got a thud. reboots when connected to 5g wifi and sometimes when doing stuff on the phone. what a POS phone. never again ulefone!
I am very happy with my T1. High performance, loads of RAM and storage in a decent looking dual SIM package for a very reasonable price tag. First official OTA update yesterday. Also there are rumors about 8.0 upgrade till end of the year.
JohnnyT
Alicklee said:
i think i got a thud. reboots when connected to 5g wifi and sometimes when doing stuff on the phone. what a POS phone. never again ulefone!
Click to expand...
Click to collapse
Mine does occasional reboot. I think its when my mail app is in 'recent apps'. When I clear recent apps. The phone seems more stable, but it's early days.
If anyone finds a fix, please post to the group.
I had my first ota update so that was a plus although it didn't solve the rebooting or activate the 'so called' second camera.
Pickles871 said:
Mine does occasional reboot. I think its when my mail app is in 'recent apps'. When I clear recent apps. The phone seems more stable, but it's early days.
If anyone finds a fix, please post to the group.
I had my first ota update so that was a plus although it didn't solve the rebooting or activate the 'so called' second camera.
Click to expand...
Click to collapse
Do you have yours rooted and your bootloader unlocked? I am getting the update prompt but being unlocked and rooted I'm not sure it will take the update. Some phones tend to brick. Also all of a sudden I am having an issue with "android process.media has stopped" Can't figure out what's causing it but since it started the device has become quite laggy
Mine is not rooted. Its still as out of the box. I have rooted previous phones but find that some of the apps I want to use won't run on rooted phones, like certain banking apps. I don't know if the restarts are an Android 7.0 symptom or hardware/software based. There are so many different views on this it's almost impossible to figure out the causes. For me I keep trying different app and phone settings in the hope that something eventually solves the issue. Maybe a future firmware update will sort it. I live in hope (but don't hold your breath). More likely a new phone will be acquired at some point!
by any chance any of you have gps problems in waze or maps????
Pickles871 said:
Mine is not rooted. Its still as out of the box. I have rooted previous phones but find that some of the apps I want to use won't run on rooted phones, like certain banking apps. I don't know if the restarts are an Android 7.0 symptom or hardware/software based. There are so many different views on this it's almost impossible to figure out the causes. For me I keep trying different app and phone settings in the hope that something eventually solves the issue. Maybe a future firmware update will sort it. I live in hope (but don't hold your breath). More likely a new phone will be acquired at some point!
Click to expand...
Click to collapse
you need to proper root with magisk. and only use magisk, not other super user apps.
with magisk hide you can cheat banking apps or any app thinking the phone is not rooted.
nieXas said:
you need to proper root with magisk. and only use magisk, not other super user apps.
with magisk hide you can cheat banking apps or any app thinking the phone is not rooted.
Click to expand...
Click to collapse
Thats useful to know. Many thanks
Made Lineage 14.1 work on my Ulefone T1 (adb shell hacked)
Hi everyone,
i've been digging around for the last few weeks on my T1 and now i've finally made it boot. I dont know exactly what is working and what not but i can tell WLAN is NOT working for now! The kernel repo at my github was not working so i used the stock one. You may download it as well as the TWRP recovery i made alongside the ROM. But you need to wipe /data partition so all user data is lost in the process. Also while TWRP needs a reboot after wiping /data step 2 & 3 may need to be repeated once. For now i was not able to flash and boot the recovery (working on it) but it can be booted into as follows (when booted into the stock system):
UPDATE: Made it work - it's booting without hacking via ADB-Shell. The parts marked --- obsolete --- are not needed any more.
1.) Disable OEM-Lock in Developer-Options (google if necessary how to do that)
2.) Reboot and keep the upper volume button button pressed until it booted into recovery. If the "no command" screen is displayed, press the power and upper volume button together once again and you shuld reside in the stock recovery. Use it to reboot into fastboot (bootloader).
3.) In fastboot mode, while beeing in the same folder as the downloaded files, type the following:
Code:
fastboot boot recovery.img
4.) Wait for TWRP to boot up and enter the following (within the same folder):
Code:
adb push lineage-14.1-*-UNOFFICIAL-t1.zip /sdcard/
5.) Finally you may flash the Lineage zip file in TWRP (if you have wiped your /data partition at least i needed to)
----------------------------------- obsolete -----------------------------------
6.) Let it reboot into system and while displaying the Linage bootanimation (for now) i had to execute a few commands on adb shell. So, with adb installed, you need to enter the following commands in a common linux/windows shell:
adb shell /vendor/bin/nvram_daemon &
adb shell /system/bin/nvram_proximity &
adb shell /vendor/bin/nvram_agent_binder &
adb shell /system/bin/agoldnvram &
adb shell /system/bin/audioserver &
Click to expand...
Click to collapse
I'm not sure if they are all needed but afterwards my T1 bootet up correcty (more or less). Unfortunately a few drivers are missing as it seems while WLAN is not working for now.
http://d0ndroid.janeiskla.de/lineage-14.1-20180928-UNOFFICIAL-t1.zip
and the recovery
http://d0ndroid.janeiskla.de/recovery.img.
----------------------------------- obsolete -----------------------------------
After fixing another few things the only remaining things i found not working are fingerprint & RIL but I'm looking into that right now. The current builds will always be uploaded to:
http://d0ndroid.janeiskla.de/
The sources i used besides the default Lineage ones are on github:
https://github.com/d0n?tab=repositories
Have fun! And let me know if you make progress on your own
Greez,
d0n
Hi d0n22, are you still working with this rom?

Mi A3 Restart

Hi, My Mi A3 keeps restarting. If i stay a while without using the phone it simply restarts and expects sim code to start again. The result is that ithou knowing i'm contantly with the phone shut down. Anyone can help? Thanks
You need to provide a bit more information than that.
Have you flashed anything at all to the device (magisk, twrp, ROM, any kind of mod)
Is it completely stock?
If so it sounds like a software issue and reflashing the stock rom with mi flash tools may help
garylawwd said:
You need to provide a bit more information than that.
Have you flashed anything at all to the device (magisk, twrp, ROM, any kind of mod)
Is it completely stock?
If so it sounds like a software issue and reflashing the stock rom with mi flash tools may help
Click to expand...
Click to collapse
Hi, thanks for the prompt reply. Yes, is just stock ROM. Android 9 plus november security patch. Already did a factory reset and the problem remains. The only uncommon thig i've noticed was an android.process.acore error which i today tried to solve by seaching solutions online. Thanks
jcoelho111 said:
Hi, thanks for the prompt reply. Yes, is just stock ROM. Android 9 plus november security patch. Already did a factory reset and the problem remains. The only uncommon thig i've noticed was an android.process.acore error which i today tried to solve by seaching solutions online. Thanks
Click to expand...
Click to collapse
That's an issue with your contacts and nothing to do with random reboots which may indicate that the update to November sec patch might have caused this issue. Something may have happened when you updated and caused some files to get messed up somehow which is why a factory reset won't work.
That's why it still hasn't fixed the android.process.acore error or the random reboots
As I said in my previous post, reflash the latest rom with mi flash tools and that issue may very well get fixed.
garylawwd said:
That's an issue with your contacts and nothing to do with random reboots which may indicate that the update to November sec patch might have caused this issue. Something may have happened when you updated and caused some files to get messed up somehow which is why a factory reset won't work.
That's why it still hasn't fixed the android.process.acore error or the random reboots
As I said in my previous post, reflash the latest rom with mi flash tools and that issue may very well get fixed.
Click to expand...
Click to collapse
ok. thanks once again
wipe format cache data everything internal storage too( it will delete ALL ypur photos,videos etc.) flash stock rom or any custom rom . i hope it will be solved
jcoelho111 said:
Hi, My Mi A3 keeps restarting. If i stay a while without using the phone it simply restarts and expects sim code to start again. The result is that ithou knowing i'm contantly with the phone shut down. Anyone can help? Thanks
Click to expand...
Click to collapse
How often does it happen? You could try connecting your phone to a PC and keep running "adb logcat" to catch the crash. Also try capturing logcat right after a reboot, it might contain some useful info about the crash.
With root you could get additional info:
Kernel Log:
adb shell su -c dmesg > dmesg.log
Last_kmsg:
adb shell su -c "cat /proc/last_kmsg" > last_kmsg.log
sasukeob said:
wipe format cache data everything internal storage too( it will delete ALL ypur photos,videos etc.) flash stock rom or any custom rom . i hope it will be solved
Click to expand...
Click to collapse
thanks
_mysiak_ said:
How often does it happen? You could try connecting your phone to a PC and keep running "adb logcat" to catch the crash. Also try capturing logcat right after a reboot, it might contain some useful info about the crash.
With root you could get additional info:
Kernel Log:
adb shell su -c dmesg > dmesg.log
Last_kmsg:
adb shell su -c "cat /proc/last_kmsg" > last_kmsg.log
Click to expand...
Click to collapse
thanks
I got the same problem...How do I reflash the latest rom with mi flash tools?
any one tried with Miflash till now? please update your feed back here
---------- Post added at 12:45 PM ---------- Previous post was at 12:28 PM ----------
@garylawwd
A3 have ufs memory and all ufs have different configuration than emmc partitions need to set active partition if you will not set active partition the phone will boot looping or hang on logo and make restarts
Click to expand...
Click to collapse
do you think any problem with this file system (Mi update team is not that dumb) but simply asking
in my case it restarts with boot loops , auto formates it self if you connect charging wire (with erasing mentioned for 15seconds) and fails to restar for 3 time and bootups with welcome language selection screen!
Ended up here because my Mi A3 is becoming increasingly unstable. It rebooted three times around lunch time. I've just installed the May 2020 update and it's already restarted once already
I'm going to have to consider returning it - my mobile is my main business phone too so can't have this level of instability and hassle Sadly a very black mark against Xiaomi. I've recommended their phones to several friends and clients because they were great phones.
Hmm... whilst typing this message it's just restarted 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