Related
i have been experiencing some force closes and random restarted, is there a program that can tell me what caused it or what app caused the error.
Not really a simple way to troubleshoot that. Did you do a full wipe prior to flashing whatever ROM you're running? Trying booting into recovery and wiping dalvik/cache, that can fix plenty of small issues.
bluephi1914 said:
i have been experiencing some force closes and random restarted, is there a program that can tell me what caused it or what app caused the error.
Click to expand...
Click to collapse
yes, logcat will show you, but you have to kinda know what you're looking for. There are some logcat apps on the market or you can logcat through ADB.
Also, random app FCs aren't all that weird, BUT if you are getting them consistently you could very likely fix it by fixing permissions in recovery.
If you fix perms and the issues persist, feel free to pull a logcat of the app crash, and either PM me the .txt file or link it here via pastebin.com. I am no expert but I could try to help. But again, fix perms first, that'll probably work.
bluephi1914 said:
i have been experiencing some force closes and random restarted, is there a program that can tell me what caused it or what app caused the error.
Click to expand...
Click to collapse
Yes, there is a way but it requires a bit of technical knowledge. Assuming you have the motivation, acquiring the knowledge shouldn't be an issue.
If you're familiar with how to use ADB (Android Debug Bridge), this program allows you to access a log Android creates on the device where all applications output errors, debug, warning and verbose information.
From the command line, you'd run, adb logcat or adb shell logcat. If you prefer to have a bit of a GUI, run ddms which is also packaged inside the Android SDK.
There is an Android application called aLogCat for free in the Android Market which offers a GUI on the device for viewing this information. Feel free to also try this method and see which works best for you.
Essentially, this log will contain a lot of information. HTC coders seem to lean on the side of outputing a lot of information.
This log is real time, it will scroll as the applications output information. The best way to find the FC is to trigger the FC and immediately look in logcat for the details. They should be flagged by E, for error, followed by some type of name convention for the application. There will generally be anywhere from 5-15 lines of output in logcat when an application force closes.
Once you're able to locate the FC error output in logcat, feel free to post back up here and we can attempt to give some feedback.
Understand, sometimes the issue is the result of the application developer's poor coding or not being able to forsee a potential error. Other times, the solution is as simple as wiping dalvik-cache or wiping the application's settings causing it to start again from scratch.
Hope that helps! Good luck!
joeykrim said:
Yes, there is a way but it requires a bit of technical knowledge. Assuming you have the motivation, acquiring the knowledge shouldn't be an issue.
If you're familiar with how to use ADB (Android Debug Bridge), this program allows you to access a log Android creates on the device where all applications output errors, debug, warning and verbose information.
From the command line, you'd run, adb logcat or adb shell logcat. If you prefer to have a bit of a GUI, run ddms which is also packaged inside the Android SDK.
There is an Android application called aLogCat for free in the Android Market which offers a GUI on the device for viewing this information. Feel free to also try this method and see which works best for you.
Essentially, this log will contain a lot of information. HTC coders seem to lean on the side of outputing a lot of information.
This log is real time, it will scroll as the applications output information. The best way to find the FC is to trigger the FC and immediately look in logcat for the details. They should be flagged by E, for error, followed by some type of name convention for the application. There will generally be anywhere from 5-15 lines of output in logcat when an application force closes.
Once you're able to locate the FC error output in logcat, feel free to post back up here and we can attempt to give some feedback.
Understand, sometimes the issue is the result of the application developer's poor coding or not being able to forsee a potential error. Other times, the solution is as simple as wiping dalvik-cache or wiping the application's settings causing it to start again from scratch.
Hope that helps! Good luck!
Click to expand...
Click to collapse
YOU HAVE GOT TO BE KIDDING ME... LOL as soon as i typed "adb logcat" at the command prompt in windows, the screen immediately fills up... and like you said its real time so it doesn't stop.
When "ADB logcat" is typed how far does this log go back. I think i typed it about 5-10 minutes after the restart....or random hot reboot. was this to long ???
Most of the lines begin with D/ or I/ or or V/ didn't see any E .... but im currently scrolling back through all of the output in the CMD screen, i had to unplug the phone to get it to stop scrolling.
il Duce said:
yes, logcat will show you, but you have to kinda know what you're looking for. There are some logcat apps on the market or you can logcat through ADB.
Also, random app FCs aren't all that weird, BUT if you are getting them consistently you could very likely fix it by fixing permissions in recovery.
If you fix perms and the issues persist, feel free to pull a logcat of the app crash, and either PM me the .txt file or link it here via pastebin.com. I am no expert but I could try to help. But again, fix perms first, that'll probably work.
Click to expand...
Click to collapse
typing "ADB logcat" from the command prompt in windows doesn't give me a .txt file does it?
bluephi1914 said:
typing "ADB logcat" from the command prompt in windows doesn't give me a .txt file does it?
Click to expand...
Click to collapse
Try to use the Fix Permissions Opinion in the Rom Manager App! That May Help...
Here's a Screenshot...
PMGRANDS said:
Here's a Screenshot...
Click to expand...
Click to collapse
Ok.. downloaded ROM Manager and ran Fix Permissions. Hopefully that will fix any issues that I had.
bluephi1914 said:
YOU HAVE GOT TO BE KIDDING ME... LOL as soon as i typed "adb logcat" at the command prompt in windows, the screen immediately fills up... and like you said its real time so it doesn't stop.
When "ADB logcat" is typed how far does this log go back. I think i typed it about 5-10 minutes after the restart....or random hot reboot. was this to long ???
Most of the lines begin with D/ or I/ or or V/ didn't see any E .... but im currently scrolling back through all of the output in the CMD screen, i had to unplug the phone to get it to stop scrolling.
Click to expand...
Click to collapse
D is debug, I is Information, V is verbose and E is Error. All FC messages will start with E although, sometimes other logcat information will help make the FC easier to understand. I usually gather them all around a specific FC and narrow it down as I go.
I don't recall the buffer limit size to logcat, but it is generally best to grab the logcat as soon as the FC issue occurs, that way the issue will be closest to the end of the buffer. This makes it easier to locate and less likely to be pushed out of the buffer.
bluephi1914 said:
typing "ADB logcat" from the command prompt in windows doesn't give me a .txt file does it?
Click to expand...
Click to collapse
no, by default it updates the screen in real time, to have it dump to a text file, adb logcat > logcat.txt . you might need to hit cntrl+c to stop it as it will continue to write in real time to the log file until you exit. the exit command is cntrl + c to kill the process, same as exiting.
Hope that helps arm you with another skill!
edit: in the last month since i originally posted my first answer, i found an application on the market, which is essentially a GUI for logcat called aLogCat. the developer open sourced his code and the application started in 2009. seems to work very well.
source code: http://code.google.com/p/alogcat
pls help my phone is rooted n sometime my phone switch off without any notification is there any problem
attaripatel said:
pls help my phone is rooted n sometime my phone switch off without any notification is there any problem
Click to expand...
Click to collapse
You should try to wipe cache and Dalvik cache in recovery.
If the issue persists, try to re-flash the kernel.
If that does not help, try to flash the whole ROM again.
If that does not help either, it could be a "bad" app.
Maybe you can get a hint to the cause of the shut down/restart in the last_kmsg file.
You can grab the last kmsg (kmsg = Kernel Message / the kernel log buffer)?
If you haven't rebooted since the crash, grab a terminal editor and enter the following:
Code:
su
cat /proc/last_kmsg > /mnt/sdcard/last_kmsg
Kmsg is continuously overwritten, so you need to extract last kmsg as soon as the issue/crash occurs.
Crash => reboot with long press Power button => grab last kmsg.
Just have a look at the last_kmsg.txt file and you may recognize what was going on shortly before the crash.
If the phone crashes next time:
1. Reboot the phone with long press power button.
2. As soon as the phone is up, start Terminal Editor app (e.g. Terminal Emulator from Play store).
3. Type the code from above. That will grab the last kernel message and saves it into "/mnt/sdcard/last_kmsg".
4. Open/read/copy last_kmsg examine yourself and/or post here again and ask for help.
Good luck !
very difficult to understand
It_ler said:
You should try to wipe cache and Dalvik cache in recovery.
If the issue persists, try to re-flash the kernel.
If that does not help, try to flash the whole ROM again.
If that does not help either, it could be a "bad" app.
Maybe you can get a hint to the cause of the shut down/restart in the last_kmsg file.
You can grab the last kmsg (kmsg = Kernel Message / the kernel log buffer)?
If you haven't rebooted since the crash, grab a terminal editor and enter the following:
Code:
su
cat /proc/last_kmsg > /mnt/sdcard/last_kmsg
Kmsg is continuously overwritten, so you need to extract last kmsg as soon as the issue/crash occurs.
Crash => reboot with long press Power button => grab last kmsg.
Just have a look at the last_kmsg.txt file and you may recognize what was going on shortly before the crash.
If the phone crashes next time:
1. Reboot the phone with long press power button.
2. As soon as the phone is up, start Terminal Editor app (e.g. Terminal Emulator from Play store).
3. Type the code from above. That will grab the last kernel message and saves it into "/mnt/sdcard/last_kmsg".
4. Open/read/copy last_kmsg examine yourself and/or post here again and ask for help.
Good luck !
Click to expand...
Click to collapse
very difficult tounderstand pls give me sugestion what i can dosimply to avoid this
Good evening all.. Just looking for some help if possible. I absolutely love Remix OS and I am really enjoying it so far. I have a dell inspirion 3000 11 inch 2 in 1 laptop. Everything works like a champ and its super smooth. I've installed to my hard drive with a window 10 dual boot. My issue is this: It will randomly just freeze, no matter what I am doing. browsing the web, looking at settings, watching a video, etc. It just freezes and then i have to hold the power button down to reboot. (is there a shortcut key or something to try to kill a task or is the power button the only option?) does anyone else have this issue? I've tried the latest update and that seemed to make it worse, so i downgraded but it still happens from time to time.
Any help or advice would be wonderful.
If you're using a Nvidia GPU, it's most probably a nouveau driver issue that will be fixed in the next kernel update.. Most probably in the next 1-2 updates.
@Dieseltown it's hard to say what causes the freeze, but we can try to find out:
1. You can go to Settings > Experimental Features > Enable ALT-F1 terminal console
2. When the freeze happens, press ALT-F1.
If it successfully switches to console then go to step 3. if not go to step 6.
3. Enter
Code:
logcat
and take a picture showing the output (it will take some time before it reaches the end of the log)
Instead of that you can press CTRL+C to terminate logcat and then request the logcat to be saved in a file by entering:
Code:
logcat > /sdcard/logcat.txt
Wait some time - 1 minute should be enough. Then press CTRL-C again.
4. Enter reboot -p (not just reboot because this tends to fail more).
5. Start the PC again go to your personal data directory and send us the logcat.
6. If the above isn't possible, then do step 3. right after bootup, but only do the save to file part. Don't press ctrl-c after requesting logcat file - press ALT-F7 instead to switch back to GUI and use your device until it freezes. The logcat will be saved through all device uptime.
Then reboot and get the logcat file uploaded.
Sent from mobile
Vioner said:
@Dieseltown it's hard to say what causes the freeze, but we can try to find out:
1. You can go to Settings > Experimental Features > Enable ALT-F1 terminal console
2. When the freeze happens, press ALT-F1.
If it successfully switches to console then go to step 3. if not go to step 6.
3. Enter
Code:
logcat
and take a picture showing the output (it will take some time before it reaches the end of the log)
Instead of that you can press CTRL+C to terminate logcat and then request the logcat to be saved in a file by entering:
Code:
logcat > /sdcard/logcat.txt
Wait some time - 1 minute should be enough. Then press CTRL-C again.
4. Enter reboot -p (not just reboot because this tends to fail more).
5. Start the PC again go to your personal data directory and send us the logcat.
6. If the above isn't possible, then do step 3. right after bootup, but only do the save to file part. Don't press ctrl-c after requesting logcat file - press ALT-F7 instead to switch back to GUI and use your device until it freezes. The logcat will be saved through all device uptime.
Then reboot and get the logcat file uploaded.
Sent from mobile
Click to expand...
Click to collapse
I had the freezing issue (because of nouveau) before and the problem is that all the system freezes that ALT+F1 doesn't work anymore
@modaifallah please read my signature
Back to the thread: His GPU is intel.
Sent from mobile
Thanks for your help so far.. I actually reinstalled the newest, from the torrent instead of OTA. No issues as of yet, but will try your guide when and if I do, then will follow up.
Downgrade to Remix OS 3.0.102 and freezing problem is gone, and az screen recorder is working fine to. Gpu driver on latest mesa Remix OS is buggy
- Simple and safe installer;
- Installs stock and offers to install Customization Package (optional);
- Can be used to flash other ROMs that use "flash_rom.sh";
- Can be used to fix bricked devices with unlocked bootloader.
DISCLAIMER: You are using the provided files by your own risk, although I have tested the installation I am not responsible for any damage or data lost if you decide to use them.
Click to expand...
Click to collapse
Compatible with macOS/Linux (tested on High Sierra and Ubuntu 16.04) or Windows. Requires unlocked bootloader!
The script will check for requirements, and will only continue if everything is fine. If you are on Windows, make sure the drivers are working correctly before starting: open Device Manager and put watch in fastboot mode then check if it is detected correctly, or you can use the provided "checkdrivers_win.cmd" to do this and check if watch's bootloader is unlocked. If you get any errors then probably drivers aren't installed properly, and you should fix this before starting.
PS: If you are on Windows, make sure fastboot driver is working properly using the directions above. If the driver seems to be installed correctly (no question mark on the device) then try disabling or uninstalling your antivirus temporary. Avast is known to cause problems with USB drivers.
Current version installs firmware 2.6.2.0 (WOS2 = Watch OS 2.0) on Pace, and can be used to fix a bricked watch, simply put it in fastboot mode manually *before* starting the script. Make sure you try to do this with a Pace watch or provide the correct ROM in the "rom" folder, otherwise it will brick your device.
PS: During the ROM installation, when watch is in Recovery Mode, it will display a triangle with an exclamation mark and the text "no command", it's expected! Simply follow the instructions provided by the script.
- How to run on Linux
Go to the folder with the uncompressed files in terminal and run "sudo bash amazeflash.command" (Linux requires root access to fastboot), then follow instructions.
- How to run on macOS
Go to the folder with the uncompressed files in Terminal and run "bash amazeflash.command", or simply double-click "amazeflash.command" then follow instructions. PS: Decompress the 7z file with Keka or TheUnarchiver to preserve file permissions.
- How to run on Windows
Go to the folder with the uncompressed files in command prompt and run "amazeflash_win.cmd" or simply double-click "amazeflash_win.cmd" (you may not see the file extension in some cases), then follow instructions.
Use the same procedure if you want to run the custom package installation script after you successfully flashed the ROM, it will prompt to install modded files or revert to stock versions. Be aware the reverting to stock version may not work if you want to apply OTA to update later, it's recommended that you flash stock version again and don't apply the Customization Package.
For more info, please refer to the included "readme.txt" file.
Some remarks:
- Customization Package includes WearSettings, NewWearSport and HuamiWatchFaces with improved support and voice prompts in English.
- If watch is *not* on firmware 2.x yet (it means *any* 1.x firmware) then probably you want to do a factory reset first and then use the installer (it works even if watch shows QR code).
- If watch already have firmware 2.x, then no need to factory reset first a priori...
- On stock ROM in English, the "About" section in Settings causes it to crash, it works in Chinese and if the Customization Package is installed.
- After a Factory Reset, language will revert to Chinese, you can set it back to English with these adb commands (you can use copy and paste, a Windows batch script is provided too):
Code:
adb wait-for-device
adb shell setprop persist.sys.language en
adb shell setprop persist.sys.country US
adb reboot
You can buy me a coffee or cheesecake (please, no beers ), Paypal address for donations: lfomartins[at]aim.com
Or most common cryptocoins here: https://freewallet.org/id/87331be5
PS: there is no fee free option to transfer money to my country, you must use "pay for goods and services". But don't worry, you will only be charged for the amount you send. Thanks!
This was only possible because of the modded recovery image provided by @Neuer_User:
https://forum.xda-developers.com/smartwatch/amazfit/tutorial-unbrick-huami-amazfit-t3547300
In the above post you can find details on how to put Pace or Stratos manually in fastboot mode. It's tricky and very hard to do, but it works.
*************************
Latest Version v1.2 - firmware 2.6.2.0
- Installer will NOT run anymore if root is detected (this can happen if watch has other custom ROMs) and only install via fastboot/recovery (safer).
- amazefls.log now won't be erased every time you run the installer script, but store all flash history for debugging.
Download link:
https://mega.nz/#!9OJ0mIqA!QgnX9f675VbZI9ECx__ScnHtgHTAdRa1fldWtZdVR9U
SHA1SUM: E941FD472C626872707C06065177DC728BA64FB6
*************************
Old versions
v1.1 - * Link removed, please use v1.2 *
SHA1SUM: 0CB3FB554A397B53C1E739586E98C2FF8C1FCE0C
- Updated to firmware 2.6.2.0
- Updated support for EN
Firmware Changelog (translated using Google Translator)
- Added World Cup event reminder function, need to upgrade to the latest mobile phone App, and set a reminder in the live World Cup page
- Added virtual rabbit mode to support running, indoor running, outdoor riding, cross-country running, open in Sports Settings > Motion Control
- Added Heart Rate Interval to Reserve Heart Rate Mode, App> My> My Info> Heart Rate Interval Settings
- Added data items such as sectioning speed and section speed to support running, trail running, walking, outdoor cycling and other sports
- Occurrence of abnormal heart rate output after optimising Bluetooth heartbeat disconnection
- Repair the lock screen second hand display of the third party dial
- Fixed several bugs
Thanks to @Saratoga79 for sharing the system dump! You rock, dude!
v1.01 - * Link removed, please use v1.2 *
SHA1SUM: 47D0777F599586A63D293E592B6770D7FE77982A
- Fixed AmazeCustom installer for both Win and Mac when run separately;
- Moved all scripts to main folder for easier access and simplified maintenance;
- Moved all Windows binaries to pgm folder to simplify future updates;
- Added Windows script to set language to EN (needed after a factory reset/unpair).
v1.0 - * Link removed, please use v1.2 *
SHA1SUM: 64205E4D683B388E8C087FCF49B20FE6FDEA8235
- Initial Release
Thanks to @ingraynieris and @chincheang for testing and @1immortal for support.
Manual Installation
Requirements
- Pace watch (A1602 or A1612);
- Unlocked booloader (unlockamazfit.com - read carefully the warning, doing this will void watch's warranty!);
- adb, fastboot and drivers installed correctly;
- 40% battery or more, read English and pay attention!
******************************************
DISCLAIMER: You are using the provided guide by your own risk, although I have tested the commands I am not responsible for any damage or data lost if you decide to use it.
******************************************
This is an installation guide, if you have never used adb or fastboot, then please don't try to do this. Commands should be typed in terminal/prompt/whatever you use to do adb commands.
In the end of this guide, you should have a watch with stock WOS2, so OTAs should work. Do not modify any system files if you want to apply future OTA updates, not even get root access, it may break stock updates.
Unpack the compressed 7zip file from the link at some place you have at least 1GB of free space and adb/fastboot access, then change to this directory to begin. Commands below are for Windows, macOS and Linux users should change the backslash ('\') to normal slash ('/'), hit ENTER/RETURN after each line (duh!).
If you are trying to fix a bricked devices, make sure it's in fastboot mode and that the computer detects the device, then start from step #3.
1. Connect the watch to computer using USB cable, then:
Code:
adb devices
2. If you see your device listed, type:
Code:
adb shell reboot bootloader
3. Check if device is recognized correctly (on Windows, open Device Manager and check if you see a device in fastboot mode or similar), then type:
Code:
fastboot getvar all
4. If you see "unlocked: yes", you can continue. Reboot into temporary root/Recovery:
Code:
fastboot boot Amazfit-mod-recovery.img
5. Watch should show a triangle with an exclamation mark, it's in Recovey mode and it's normal, do not panic! Then make sure you have root now:
Code:
adb root
6. Then push files to watch:
Code:
adb push rom\boot.img /data/media/0/
adb push rom\md5s.txt /data/media/0/
adb push rom\system.img /data/media/0/
adb push rom\flash_rom.sh /data/media/0/
If it fails, try:
Code:
adb push rom\boot.img /sdcard/
adb push rom\md5s.txt /sdcard/
adb push rom\system.img /sdcard/
adb push rom\flash_rom.sh /sdcard/
7. Take a deep breath and then (after the first command, you should see a "#" only, indicating root prompt):
Code:
adb shell
cd /data/media/0
sh flash_rom.sh
or use "cd /sdcard" if you have copied the files to this directory instead.
8. Wait until it says "Finished", then type:
Code:
reboot
9. To set English language after booting (stock CN WOS2 has some bugs, i.e. About in settings crash, some watchfaces show Chinese names when screen is locked, etc):
Code:
adb wait-for-device
adb shell setprop persist.sys.language en
adb shell setprop persist.sys.country US
adb reboot
Thanks for your rom, have seen it on fb to great work!
Verstuurd vanaf mijn ONEPLUS A5000 met Tapatalk
Thank you for your great work!
Is it possible to install custom GPS.conf files? Will it break OTA updates?
xaametz said:
Thank you for your great work!
Is it possible to install custom GPS.conf files? Will it break OTA updates?
Click to expand...
Click to collapse
You're welcome. I am glad you like it.
Yes, you can install a custom gps.conf the same way you do with any other ROM (root, remount, push, fix permissions, reboot), but my personal experience is that GPS is much better on 2.6.1.0, no need to change anything. I cannot guarantee it will not break OTA, may or may not work as it's not a file that is used in stock firmware, but any modification to /system can cause problems. Anyway, with AmazeROM you can always flash stock later if you need it for future updates.
lfom said:
You're welcome. I am glad you like it.
Yes, you can install a custom gps.conf the same way you do with any other ROM (root, remount, push, fix permissions, reboot), but my personal experience is that GPS is much better on 2.6.1.0, no need to change anything. I cannot guarantee it will not break OTA, may or may not work as it's not a file that is used in stock firmware, but any modification to /system can cause problems. Anyway, with AmazeROM you can always flash stock later if you need it for future updates.
Click to expand...
Click to collapse
Thank you. I'll try it without custom config.
Enviado desde mi STF-L09 mediante Tapatalk
Hi,
Minor problem with the script that installs the customised apk's: You seem to have forgotten to replace "adb" with "$adbcmd" and "fastboot" with "$fbcmd".
Thanks for all the effort you have put into the scripts!
R.
Eeg.
superbert1969 said:
Hi,
Minor problem with the script that installs the customised apk's: You seem to have forgotten to replace "adb" with "$adbcmd" and "fastboot" with "$fbcmd".
Thanks for all the effort you have put into the scripts!
R.
Eeg.
Click to expand...
Click to collapse
True, thanks for reporting. There is a problem in the Windows installer as well, it doesn't work if you run it without command line arguments, it will be fixed in the next release.
I just made some quick an dirty adaptations in order to get the custom script running. Unfortunately, I'm now stuck with an unwilling fastboot (maybe it's because I'm still on "El Capitan" --> I'm considering upgrading, but first have to make a recent backup).
Though-luck for now, I'm stuck with a watch that has some Chinese notifications (at least for the time being).
superbert1969 said:
I just made some quick an dirty adaptations in order to get the custom script running. Unfortunately, I'm now stuck with an unwilling fastboot (maybe it's because I'm still on "El Capitan" --> I'm considering upgrading, but first have to make a recent backup).
Though-luck for now, I'm stuck with a watch that has some Chinese notifications (at least for the time being).
Click to expand...
Click to collapse
I have updated the installers, please check them. I am sorry for the trouble.
Hi,
You don't have to excuse yourself at all...
I just tried the new version, and it works perfectly fine now (even on my Mac).
I really appreciate the effort you're putting into AmazeROM
@lfom: HELP!
Unfortunately this installer crashs my Pace.
In the past I have used PACEfied and PACEficator custom ROM and the installers works always perfect.
But this one fails in some steps but continues and ends with an "ok" and now I see only the "A" logo before the boot animation.
Attached the whole CMD output.
I hope the Pace is not bricked. ADB devices shows the Pace, but no other commands (e.g. "fastboot reboot bootloader") are working.
Got the same problem, it crashed my PACE too, was running PACEficator Project before, now it keep having luncher has stopped error.
Installer stopped on fastboot and unable to boot to recovery anymore
fastboot boot Amazfit-mod-recovery.img
downloading 'boot.img'...
FAILED (remote: ED: The command is not allowed.)
finished. total time: 0.012s
Edit: after search the forums, I unpair and re-pair my PACE and the watch is working now. however, I am not sure should I still install this ROM on my watch anymore.
@Diginix @thomsontam Did you check you have an unlocked bootloader? If yes, you should be able to put watch in fastboot mode and flash the ROM again. It seems that the installer detected root and went ahead with the installation, but the watch crashed and it did not finish. If it's locked and you have a valid serial number, you should be able to unlock it using the same code as before. If not, please contact me via Telegram: http://t.me/lfomartins
@lfom
I had an unlocked bootloader until PACEficator 2.6.0.12. I didn't checked it after update to PACEficator 2.6.1.0
Root was definitely existing and working.
I have my serial nr. and the unlock code.
But what commands should I try now?
This doesn't work:
adb shell reboot bootloader
- exec '/system/bin/sh' failed: No such file or directory (2) -
using port=5555
Click to expand...
Click to collapse
My backlight is always on and shows the Amazfit "A". I hope the battery is charging.
@Diginix You have broken file system. You should be able to put the watch in fastboot manually. It is very hard to achieve but it works. Then check if bootloader is unlocked and try to flash it again. If you have problems, contact me on Telegram.
I have no Telegram and need ready for use commands please.
Your checkdrivers_win.cmd doesn't provide any hope.
btw: adb+fastboot was proper installed and works in the past perfect with the installer of other custom roms.
Edit: I will try this steps.
Edit2: My Pace can't be turn off as in the youtube video is shown. It always shows the "A" and backlight is on.
As it seems fastboot isn't reachable. But I will try some different delays at pressing the button and plugin it on PC.
@Diginix checkdrivers_win.cmd is useless now with a bricked device. You can turn the watch off by pressing and holding the button. Keep the watch connected to the computer and then press button again to turn it on, then count up to 4 (more or less) after the screen goes on again and release the button. If you see the battery icon you have released the button too early, if you see the A logo then you released too late. You have to release at the exact time to show the screen with Fastboot and ForceErase, then press button briefly once to enter fastboot. Keep the watch connected to the computer all the time, it's easier this way.
Now I'm in fastboot!
But "fastboot devices" doesn't prompt any device.
What to do with your ROM files?
Hi!
I installed and I'm using adb and fastboot on Mac, it works perfectly adb, but with fastboot it does not detect the clock. But if I try on my OnePlus 6, I detect both adb and fastboot the Mac. How can I do? Thank you
All, I have found a solution to get this P-WAL-107-ELC-02 unlocked and usable!
Original post:
I acquired a used Outcome Health (Contextmedia) Wallboard. There have been other posts previously about unlocking the 10 and 13inch tablets, but the steps and procedures used did not work with this wallboard.
The model number is P-WAL-107-ELC-02, and is similar to the item found here: https:// fccid.io/ 2AI6X-PWALELC
It is running on Android 4.4.4
I can open the "secret" configuration menu built into the app, but all the functions are password protected. I've had no success accessing the default android settings menu either. If you close the app, it launches again immediately, and the status bar seems to be locked down so that it can't be expanded.
EDIT: I've tried using a USB keyboard, and used the settings hotkey but no luck with this either. Using the home button pushes a message at the bottom of the screen "Override Launch." I also tried generic passwords in the various menus, but nothing has worked so far.
Any suggestions or experience with these items is greatly appreciated, thank you!
Click to expand...
Click to collapse
Disclaimer:
This is a collection of the methods that worked successfully in my case. I am assuming anyone using this has an understanding of the use of ADB and shell commands. If not, please do your research to better understand the use of the command line, otherwise you may cause more damage then actual repair. Perform the actions followed at your own risk.
Rebooting into safe mode and removing contextmedia applications:
With the help of information in this thread: https://forum.xda-developers.com/android/help/android-4-4-4-context-media-10-tablet-t3670769 I got it working.
With the wallboard connected to the pc, I restarted the device and repeatedly pressed the power button until it finished booting and it started in safe mode! I was able to open the android settings, uninstall the contextmedia app and the zygote app, access dev options and enable debugging.
Connected to the PC and in debugging mode run the following to remove the synop and the remainder of the contextmedia applications.
adb reboot root //Worked in my case, confirmed root access.
adb shell
[email protected]:/ $ su //Root permissions in shell
[email protected]:/ # rm data/dalvik-cache/[email protected]@[email protected]
[email protected]:/ # rm data/dalvik-cache/[email protected]@[email protected]
[email protected]:/ # rm -r data/data/com.contextmediainc.system.synop
After that, it should let you simply uninstall or disable everything else.
With that removed, you should be able to install any compatible launcher (I used nova launcher at the time of writing this) with the adb install commands.
Flashing TWRP recovery and installing open Gapps:
I finally got a working TWRP recovery using the TWRP_2.8.7.0_RK32.img, using the method show here https://blog.matt.wf/flash-your-recovery-image-via-adb-shell-on-android/
Generic RK32 with SDcard - http://www.freak-tab.de/abdul_pt/TWRP/Generic/TWRP_2.8.7.0_RK32_SDcard.img
Generic RK32 with Unified Storage - http://www.freak-tab.de/abdul_pt/TWRP/Generic/TWRP_2.8.7.0_RK32_DATAMEDIA.img
Turns out the manufacture is Rockchip and the series is an rk3288.
Flash your recovery image via adb shell on android
JANUARY 16, 2017
//edit: You need a rooted device for this kind of flashing
Hi, ever wondered about how you can flash a recovery.img via adb shell?
A lot of posts suggest flashing it via fastboot. Well my ****ty Samsung phone is not detected by fastboot. Then there is the option to install a dubious binary file which is called flash_image.. thank u internet!
Well damn I have the recover.img whats so hard to use dd and flash it with a single shell command? For those who don't know much about linux commands here we go;
Enable your USB debugging bridge in switch via adb to the terminal:
./adb shell
Then you should be able to find your recovery partion with:
DEV=$(ls /dev/block/platform/*/by-name/recovery); echo $DEV
that should output something like this:
/dev/block/platform/7824900.sdhci/by-name/recovery
If this is the case you only have to put the recovery.img on your sd-card or the internal storage and you are one command from flashing:
dd of=$DEV if=/external_sd/recovery.img
Thats it! No binaries you have to install. No ****ty fastboot udev rules :S
You can enter into your new recovery system with:
./adb reboot recovery
Click to expand...
Click to collapse
With that, I could flash the gapps from the recovery and now the play store and services are working seamlessly. With the exception of the home and recent buttons not doing anything, this one is completely usable now.
Install SuperSu if you want to maintain permanent root on the device!
Download links:
Generic RK32 with SDcard - http://www.freak-tab.de/abdul_pt/TWRP/Generic/TWRP_2.8.7.0_RK32_SDcard.img
Generic RK32 with Unified Storage - http://www.freak-tab.de/abdul_pt/TWRP/Generic/TWRP_2.8.7.0_RK32_DATAMEDIA.img
Nova Launcher - https://nova-launcher.en.uptodown.com/android
SuperSu - https://supersu.en.uptodown.com/android
Recovery Reboot - https://apkpure.com/recovery-reboot/gt.recovery.reboot
Droid Hardware Info - https://droid-info.en.uptodown.com/android
Open Gapps - Platform: ARM Android: 4.4 Variant:Nano - https://opengapps.org/
No suggestions, but what a cool find. I'm surprised that hospitals use Android smart TVs! Or is it a giant tablet?
Sent from my LM-V350ULM using Tapatalk
jwrezz said:
No suggestions, but what a cool find. I'm surprised that hospitals use Android smart TVs! Or is it a giant tablet?
Sent from my LM-V350ULM using Tapatalk
Click to expand...
Click to collapse
It seems more like a giant tablet. I saved it from the dumpster hoping it could be turned into a nice web surfing machine for the garage.
slaysher62 said:
It seems more like a giant tablet. I saved it from the dumpster hoping it could be turned into a nice web surfing machine for the garage.
Click to expand...
Click to collapse
That would be awesome.
Sent from my LM-V350ULM using Tapatalk
bump
How often do I click the power button when it is booting, to get into safe mode? It just keeps going back to the home screen for me. Also, which USB did you have connected to the PC while doing this?
I am having the same issue
Any further update or progress on this from anyone? This would be perfect for a garage (or wherever) media center.
Any idea where I can find the recovery file? I tried to obtain one via TWRP and no luck.
I was able to install nova laucher and delete the files in data using adb shell. I'm just stuck at the recovery image part.
---------- Post added at 01:11 AM ---------- Previous post was at 12:20 AM ----------
Freak-tab .de website is down. Can someone please send me the image recovery file? Thanks in advance.
slaysher62 said:
bump
Click to expand...
Click to collapse
I'm able to get mine to the Recovery System but I cant run adb shell as I get exec '/system/bin/sh' which is no root. But I can't get into Safe Mode. I have the 32" Wallboard too but mine is ELC-01. What power button combo did you use to get into Safe Mode?
Plug in power and then just mash the power button? When do you stop mashing it?
Mash it as you plug in power and keep mashing?
Plug in power as you hold the power button down?
Stop mashing when it flickers or the screen is white?
Can’t get in to the settings.
ttiimmmmyy said:
How often do I click the power button when it is booting, to get into safe mode? It just keeps going back to the home screen for me. Also, which USB did you have connected to the PC while doing this?
Click to expand...
Click to collapse
Can’t get into settings. Tried the power button variations, with and without mini usb plugged in to the pc.
Wallboard
There are some typos in the original post commands. I wasn't having any luck with the "rm" commands to remove "zygote" and "sysop" apps, so I used the "ls" and "cd" commands to see what the file names were.
Removing the second file should be "[email protected]:/ # rm data/dalvik-cache/[email protected]@[email protected]" , the third should be "[email protected]:/ # rm -r data/data/com.contextmediainc.system.sysop"
When you type the command "DEV=$(ls /dev/block/platform/*/by-name/recovery); echo $DEV" you'll get an output, type that output into the next command. ex: dd of="output of previous command".
If you just drop the TWRP onto the USB mass storage drive that appears when you connect the tablet, it will be in "/sdcard" folder. The final command will be something like: dd of="output of previous command" if=/sdcard/RK32.img. If you don't have root access it will tell you "permission denied", so make sure you use the command "su" after "adb shell".
Lastly, I accidentally found that when I performed a factory reset via TWRP recovery menu that the Home button started working. It may also work via the settings menu, but I didn't try it that way.
Anyway, hats off to OP for posting this as it gives use to these massive android tablets.
The secret password is cat10dog
Kinda stuck...
Hey Slaysher62. I'm kinda stuck. Was wondering if you could help me out. I have a few of these due to our hospital just not needing them anymore and telling me I could either keep them or throw them away. I've tried for weeks to replicate your success but I feel like I'm missing a few steps. If you could Message me or something that'd be great.
Thanks,
Pinball Wizard
slaysher62 said:
All, I have found a solution to get this P-WAL-107-ELC-02 unlocked and usable!
Original post:
Disclaimer:
This is a collection of the methods that worked successfully in my case. I am assuming anyone using this has an understanding of the use of ADB and shell commands. If not, please do your research to better understand the use of the command line, otherwise you may cause more damage then actual repair. Perform the actions followed at your own risk.
Rebooting into safe mode and removing contextmedia applications:
With the help of information in this thread: https://forum.xda-developers.com/android/help/android-4-4-4-context-media-10-tablet-t3670769 I got it working.
With the wallboard connected to the pc, I restarted the device and repeatedly pressed the power button until it finished booting and it started in safe mode! I was able to open the android settings, uninstall the contextmedia app and the zygote app, access dev options and enable debugging.
Connected to the PC and in debugging mode run the following to remove the synop and the remainder of the contextmedia applications.
adb reboot root //Worked in my case, confirmed root access.
adb shell
[email protected]:/ $ su //Root permissions in shell
[email protected]:/ # rm data/dalvik-cache/[email protected]@[email protected]
[email protected]:/ # rm data/dalvik-cache/[email protected]@[email protected]
[email protected]:/ # rm -r data/data/com.contextmediainc.system.synop
After that, it should let you simply uninstall or disable everything else.
With that removed, you should be able to install any compatible launcher (I used nova launcher at the time of writing this) with the adb install commands.
Flashing TWRP recovery and installing open Gapps:
I finally got a working TWRP recovery using the TWRP_2.8.7.0_RK32.img, using the method show here https://blog.matt.wf/flash-your-recovery-image-via-adb-shell-on-android/
Generic RK32 with SDcard - http://www.freak-tab.de/abdul_pt/TWRP/Generic/TWRP_2.8.7.0_RK32_SDcard.img
Generic RK32 with Unified Storage - http://www.freak-tab.de/abdul_pt/TWRP/Generic/TWRP_2.8.7.0_RK32_DATAMEDIA.img
Turns out the manufacture is Rockchip and the series is an rk3288.
With that, I could flash the gapps from the recovery and now the play store and services are working seamlessly. With the exception of the home and recent buttons not doing anything, this one is completely usable now.
Install SuperSu if you want to maintain permanent root on the device!
Download links:
Generic RK32 with SDcard - http://www.freak-tab.de/abdul_pt/TWRP/Generic/TWRP_2.8.7.0_RK32_SDcard.img
Generic RK32 with Unified Storage - http://www.freak-tab.de/abdul_pt/TWRP/Generic/TWRP_2.8.7.0_RK32_DATAMEDIA.img
Nova Launcher - https://nova-launcher.en.uptodown.com/android
SuperSu - https://supersu.en.uptodown.com/android
Recovery Reboot - https://apkpure.com/recovery-reboot/gt.recovery.reboot
Droid Hardware Info - https://droid-info.en.uptodown.com/android
Open Gapps - Platform: ARM Android: 4.4 Variant:Nano - https://opengapps.org/
Click to expand...
Click to collapse
Help with recovery
Recently acquired 3 of these 32-inch screens at first I wasn't able to get into safe mode but I deleted everything off the sd card and restarted the screen after that spamming the power button worked and I was able to get the app uninstalled and Nova launcher installed but what I'm having an issue with is getting TWRP to install also I noticed mine isn't a RK3288 its a RK3188
I've tried to flash all the TWRP RK3188 recoveries I could find but none of them work just puts the screen into a boot loop until removing power and restarting
any update from android 4.4
was anyone able to get any operating system installed on this besides andriod4.4? trying to decide if I am going to just use the screen and install a new mini board to install android 10 or chrome os
---------- Post added at 07:41 PM ---------- Previous post was at 07:36 PM ----------
to get to the secret menu . power on "tablet", wait till the program is running . you will see a logo close to the bottom right hand corner. keep pressing it until the menu pops up. to get into the actual settings I can't remember what it was called but I should be something like device admin or such on the right hand sign. click it. it will ask for password ( cat10dog ) from there you should be able to follow the instructions above
Uit232b-u03
Thought I'd chime in; I have one of these wallboards, model # UIT232B-U03, nominally equipped with an RK3188. Here's what I've found:
Misc. Device Info
RIL Ver: KitKat ril-rk29-dataonly v3.3.00
Build No.: Z05-outform-32-B4.21-20160324
Build Fingerprint: rockchip/rk3188/rk3188:4.4.4/KTU8Q/eng.root.20151208.162319.eng/test-keys
Board / Chipset: rk30sdk / RK30board
As you might notice from the Build Fingerprint, this model appears to be running an engineering build of Outcome/ContextMedia's KitKat ROM; this screen was pulled from a working clinic, but USB debugging was already enabled and connecting via adb shell automatically dumps you into a root shell. There's nothing more you need to do to gain that access.
The device info (courtesy of Droid Info) references three different RK chips in a few places: RIL Ver. (rk29); board & chipset (rk30); and everywhere else (rk3188, specifically). I don't know what to make of that. Maybe something to do with it being an engineer build? Could be an engineering sample board, too -- I need to check for that info.
Personalization
As mentioned, it looks like this unit (and maybe other UIT2xx-xxx revisions) appears to come pre-rooted with USB debugging already enabled. There's no need to authorize any given machine on the tablet when connecting over ADB for the first time, either. If you still want/need to access the system settings, three-finger-tap on the application logo in the bottom-right of the screen (tapping multiple times will just cause a credits list to pop up). The password to leave the application for the Android system settings is cat10dog, as has been noted elsewhere.
Before I loaded anything new, I went ahead and factory reset it to see what it looked like. Upon doing so, the only system application was Zygote -- it looks like it's a modified version which is serving as the "launcher" for this tablet, and which forcibly reloads the application whenever it is closed for whatever reason. From factory reset, it will launch into a first-time setup screen, where it looks like you can configure the application and get connected to wifi/ethernet and download the remaining system apps (this is my impression; I didn't go through with it, but I imagine the application will want to verify a license or something). Uninstalling the modified Zygote seems to not kill the first-time setup screen (makes sense -- it's meant to stay resident and likely has everything it needs loaded into RAM at the time), but you can install Nova Launcher 5.3 (last version to support KitKat 4.4.4) and then Zygote fully disappears and you won't get bothered about setup anymore. (I have no idea what happens if you remove Zygote and then don't install a launcher. You can probably still connect over ADB, but I've never seen a launcher-less Android.) Other apps can be installed at this time, too.
As noted elsewhere, the Home and Recents soft buttons still do not work. I'm not 100% sure, but I think that's something stuffed in the ROM itself and may not be configurable (maybe through the commandline?). But, you can just use the Back button to go back to the home page at any point.
I have not had any success installing TWRP: It turns out, despite the chip being labeled in all ways as an RK3188, it is in fact a lower-specced RK3188T (1.4Ghz top speed). Every version of TWRP for the RK3188 I've tried has resulted either in a bootloop (unplug from power and plug back in to return to system), or a black screen, or the TWRP splash screen but which never progresses beyond that step. (This reminds me, I need to check on the black screen instances to see if the recovery executable is running at all, and what happens when I try to manually start it.)
On the off-chance anyone has a TWRP build for the RK3188T for me to try, I'd definitely appreciate it! Or indeed any ARMv7-based build, if I'm just going to be blindly loading recoveries to see what happens. (If anyone has any advice for debugging the recovery loading process, I'm rather a noob at this and could use any information about where to look for logging info, or to make it output a log at all if it doesn't by default.)
OH, and uh... if anyone has a stock version of the recovery partition, could you send it to me? I didn't back it up before writing over it...
Other than not getting to install TWRP and get all experimental with ROMs, it is usable in its current state as an old-but-servicable, pre-rooted-for-your-convenience-no-supersu-required, massive Android tablet. Too bad Pocket Camp requires Android 5 since a few builds ago...
Edits for grammar, spelling, extra info.
theugly_bear said:
was anyone able to get any operating system installed on this besides andriod4.4? trying to decide if I am going to just use the screen and install a new mini board to install android 10 or chrome os
---------- Post added at 07:41 PM ---------- Previous post was at 07:36 PM ----------
to get to the secret menu . power on "tablet", wait till the program is running . you will see a logo close to the bottom right hand corner. keep pressing it until the menu pops up. to get into the actual settings I can't remember what it was called but I should be something like device admin or such on the right hand sign. click it. it will ask for password ( cat10dog ) from there you should be able to follow the instructions above
Click to expand...
Click to collapse
device configuration and also just to clarify what he meant was tap on that flower looking logo repeatedly until you get the secret device configuration then on top right corner theres 3 lines select network settings and it should ask for a password which is cat10dog
And now I'm stuck
If anyone could give me direction/etc to get past where I'm at, I'd appreciate it.
I bought one of these bad boys from an auction and thankfully found this post and started the task of customizing it. I got to the point to where I deleted the apps listed, all through adb reboot recovery (used Generic RK32 with SDcard).
However, on reboot, it didn't go into recovery and had the Context Health splash to a nature backdrop and an Error: Wallboard not installed message. USB debug wasn't persistent, and trying everything that worked previously, I can't seem to get into Safe Mode, and I haven't found any other ways to get into Settings.
I did find the "reset" hole on back, which otherwise functions as a hardware 'Volume Up', but have yet to find any [Boot to Recover] methods involving only Volume Up and Power that work.
Any ideas of things to try?
Thank you
Update 1: Still no luck overall, but somewhat of progress, I hope: Plugging in the DC automatically boots up everything. If I hold down the hardware volume up/reset while adding power AND have USB plugged in, I get a listing in Device Manager; however, the screen stays black. Otherwise, as far as getting my PC to notice it, this is the only means to do it. There is no connection when powered on normally, rather I plug in USB before or after providing power. Also, spamming the power button while booting in order to get into Safe Mode had worked initially. Now doing it causing a freeze on the second or third splash screen refresh.
So I have recently acquired a bunch (50+) of these 32" screens. They were pre-rooted as @dwkindig had mentioned. I was able to remove all of the Context media apps and unlock the functionality as a basic android tablet pretty quickly. Threw Nova launcher on it and they work great. Has anyone had success in getting anything above Android 4.4 on these? I have a ton and can pull any files that would be of help to do some digging here, so please let me know. I would love to at least get Lollipop on these so that Android Webview could be upgraded and I could use the Wallpanel app for dashboard use on these. Any suggestions or help I can offer?