Related
Hi all, after many attempts to unlock pattern my phone says:
Please enter your google account and password. I´ve attempt enter my google account and password and don´t work..
What i do now? Any idea?
Try this...
So it happens, that my brother locked me out of my own phone :O and i didnt want to wipe, so i searched and searched, until i found this solution which worked flawlessly
Method 1 :
Step 1. Download the Android SDK (http://developer.android.com/sdk/)
Step 2. Make sure to configure the ADB usb interface drivers
Step 3. Plug your G1 into your computer (via usb). (Settings -> Application -> Development -> USB Debugging, must be enabled [it is enabled by default in JesusFreke/CM's releases i think])
Step 4. Open command prompt and enter the following:
Code:
adb -d shell
sqlite3 data/data/com.android.providers.settings/databases/settings.db
update system set value=0 where name='lock_pattern_autolock';
update system set value=0 where name='lockscreen_lockedoutpermanently';
.exit
exit
reboot
Thats it, you'r gh0od :clap:
Method 2 :
Code:
adb -d shell
su
sqlite3 data/data/com.android.providers.settings/databases/settings.db
.header on
.mode column
select * from system;
Now, in the table, find the ID of the two lines called lockscreen.l and lock_pattern, in my case; 3125 and 3126
Code:
update system set value=0 where _id=(replace with your id and remove brackets);
update system set value=0 where _id=(replace with your id and remove brackets);
.exit
reboot
Click to expand...
Click to collapse
Instructions from a slightly dodgy, copyright infringing site, so I copied and pasted them to avoid linking to warez. If you google search for a small part of it, you'll find the original source.
Obviously instructions to be followed at your own risk, since they are for the G1, but I reckon the G2 would be the same (same underlying android code).
If poss, make a nandroid backup first
anon2122 said:
Try this...
Instructions from a slightly dodgy, copyright infringing site, so I copied and pasted them to avoid linking to warez. If you google search for a small part of it, you'll find the original source.
Obviously instructions to be followed at your own risk, since they are for the G1, but I reckon the G2 would be the same (same underlying android code).
If poss, make a nandroid backup first
Click to expand...
Click to collapse
Thanks to u advanced answer...but i make wipe.
Let me first say that I have read every post I could find on this subject and tried them all with no success. I rooted my Aria using the Ubuntu Live CD so I could use Titanium backup and eventually try different roms. My phone is still using the stock rom. I then installed Titanium backup which reports "your system settings will prevent you from restoring applications. to correct this go to your phone's settings, then in "applications" and tick the "unknown sources" check box."
The unknown sources check box is of course not there because I have not been able to successfully run the code for allowing non-market apps.
From terminal in the Ubuntu Live CD with USB cable connected and set to charge only. I tried and got "remount failed: operation not permitted." at the adb remount step.
Linux Code:
sudo su
adb remount
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
echo "update secure set value = 1 where name = 'install_non_market_apps';"|sqlite3 ./settings.db
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
adb reboot
I downloaded the android-sdk_r07 and extracted it to my C drive. From a Windows command prompt, I changed to the sdk\tools folder. Adb devices sees the phone but adb remount fails with "remount failed: operation not permitted."
Windows Code:
adb remount
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
echo update secure set value = 1 where name = 'install_non_market_apps';|sqlite3 settings.db
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
I found a post from attn1 that I have not tried that said:
"Put your phone in recovery mode. Go to advanced>mount system and mount data. Follow steps in post #13 (using the windows or linux code above) in cmd screen and you'll be fine." I am not comfortable in trying this approach as there are not enough specific step details and I don't want brick my phone.
I would really appreciate the correct detailed steps to enable non-market apps using the supplied code either from Windows or the Ubuntu Live CD. Thank you in advance.
You are rooted, so boot into recovery and create a nandroid backup; if something goes wrong when pushing settings.db and you cannot boot, restore your nandroid backup. Then, as attn1 stated, perform the same steps you mention above, but while the phone is in recovery and you have mounted the system and data folders.
winsettr said:
You are rooted, so boot into recovery and create a nandroid backup; if something goes wrong when pushing settings.db and you cannot boot, restore your nandroid backup. Then, as attn1 stated, perform the same steps you mention above, but while the phone is in recovery and you have mounted the system and data folders.
Click to expand...
Click to collapse
Thank you winsettr for your post. It looks like running the commands from recovery did indeed work. Titanium backup no longer reports the "your system settings will prevent you from restoring applications. To correct this go to your phone's settings, then in "applications" error.
However, I expected to see the settings\applications unknown sources check box check box and it is not there. I guess I will have to try side-loading an app to confirm that it will work.
I think that gui option would be part of the rom, a part that AT&T has removed... So yeah, see if side- loading works now.
Sent from my Liberty using XDA App
FYI, I am indeed able to side load now from an .apk copied to the sd card. However, I am not able to install from an internet link. Trying to do so generates a "your phone is not authorized" error message.
Until you get a custom rom running, I wouldn't worry too much. Sounds like you can get any app you want (just download internet apps to sd then install). There may be an additional setting in settings.db but that's beyond my knowledge...
Sent from my Liberty using XDA App
This is only for use on the X10 Mini Pro.
Credits go to nobodyAtall & D4rKn3sSyS for the actual CWM files. Other credits in the README.txt file.
Both version currently use CWM v3.x r5
Windows
Requirements:
Windows PC
USB Cable
Phone driver installed
Android Version 2.1 Stock ROM (2.1.1.A.0.6) (May work on Froyo and Gingerbread ROM's but any custom ROM should have a recovery already installed)
Usage:
You need to set your phone in Debugging Mode.
Connect your phone to your computer
Open up install.bat and follow the instructions inside that.
CWM Usage:
When booting your phone and when the 'Sony Ericsson' letters appear, press and release continuously the 'back' button.
Once you are in the CWM recovery, use the volume keys to navigate upwards / downwards, the 'home' or camera button key to select, the 'back' key to go back.
Last Update:
21-03-2012 v5
Updated Superuser apk and su to version 3.0.7
Replaced SuperOneClick with alternative method
Prefixed relative paths with %~dp0 to complete full paths. This is to combat over zealous group policies. Thanks go to satanselbow
Linux
Requires your phone to be ROOTed but there is now a ROOTer for Linux that can ROOT your phone if not already done. Can be found in this forum.
Requirements:
*nix PC/Laptop
USB Cable
Android Version 2.1 Stock ROM (2.1.1.A.0.6) (May work on Froyo and Gingerbread ROM's but any custom ROM should have a recovery already installed)
Usage:
You need to set your phone in Debugging Mode
Connect your phone to your computer
Open up terminal
Go to the directory it is extracted to
Start the installer by typing "sh cwm-x10minipro.sh"
CWM Usage:
When booting your phone and when the 'Sony Ericsson' letters appear, press and release continuously the 'back' button.
Once you are in the CWM recovery, use the volume keys to navigate upwards / downwards, the 'home' or camera button key to select, the 'back' key to go back.
Last Update:
23-Sept-2011 (v4)
Fixed question about USB Debugging
Fixed permissions on ADB
Links:
Original X10 Mini CWM Thread: http://forum.xda-developers.com/showthread.php?t=1105745
Original X10 Mini Pro CWM Thread: http://forum.xda-developers.com/showthread.php?t=1106146
Changes:
The changes for the latest version are included in the relevant sections above. A more detailed list of changes across all versions is in the CHANGES.txt file that is in the archive file.
Download:
Windows: Download
Linux: Download
Please do not re-host or re-release without permission.
Don't forget if you found this helpful please push the "Thanks" button
copy failed read only file system
is this basically a batch file?
because if so i could port it to linux for you
mopgawka - Did you get the correct mtdblock number. The file would set the system dir as r/w to enable you. The mtdblock number is the number directly after the text mtdblock, in the image below it is 0.
Another question was there an error after the "Getting ROOT rights" text? This was the bit that caused me the most issues.
x10man - Yes it is just basically a batch file. If you want to port to linux then go ahead
ClockWorkMod Recovery Installer for X10 Mini Pro by rect2409.
Requirements and credits are listed in the README.txt file.
Please make sure requirements are met before continuing.
...
..
Для продолжения нажмите любую клавишу . . .
Starting ADB Server if not started.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Getting ROOT rights.
rootsh: permission denied
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Enter the mtdblock number listed "/dev/block/mtdblock? on /system"
Enter mtdblock number: 0
Mount system as R/W.
mount: Operation not permitted
Do you already have a recovery installed? (Y/N):n
Pushing recovery tar file.
failed to copy 'recovery\recovery.tar' to '/system/bin/recovery.tar': Read-only
file system
Pushing chargemon.
failed to copy 'recovery\chargemon' to '/system/bin/chargemon': Read-only file s
ystem
Setting permissions for recovery tar file.
Unable to chmod /system/bin/recovery.tar: Read-only file system
Setting permissions for chargemon.
Unable to chmod /system/bin/chargemon: Read-only file system
Stopping ADB Server.
* server not running *
..
i always rooted
Ok, Currently working on a new version which hopefully fixes your issues.
Thanks I will dl it and take a look later and post the result here
Sent from my U20i using XDA App
how did you root your phone? I also don't have a script called "rootsh". also you can check if you are rooted with "id". many ppl like me are just rooted after entering the shell
also it's better to use "su" when calling commands that have to be done by root: "su - -c 'mount xyz' "
also don't forget the "*" if you check for keyboard inputs (there are people that may miss the key they wanted to push .D)
good luck.
Finnaly! Thank you! Would love to see cwm being imported in the slades kernel, that way we never have to deal with broken files!
Snoopo said:
how did you root your phone? I also don't have a script called "rootsh". also you can check if you are rooted with "id". many ppl like me are just rooted after entering the shell
also it's better to use "su" when calling commands that have to be done by root: "su - -c 'mount xyz' "
also don't forget the "*" if you check for keyboard inputs (there are people that may miss the key they wanted to push .D)
good luck.
Click to expand...
Click to collapse
Yeah I just noticed that i left rootsh in there. Was just something I was playing with.
One thing I hate is Permission Denied error's with adb... Oh fun.
damn. i just did the port and managed to delete the files. DAMN windows temp file thingys anyway tommorow it will be done
TY man u awesome!!!!! thx u all work fine!!!!
rect2409 said:
mopgawka - Did you get the correct mtdblock number. The file would set the system dir as r/w to enable you. The mtdblock number is the number directly after the text mtdblock, in the image below it is 0.
Another question was there an error after the "Getting ROOT rights" text? This was the bit that caused me the most issues.
x10man - Yes it is just basically a batch file. If you want to port to linux then go ahead
Click to expand...
Click to collapse
In linux we used to set the mount point to a variable and then issuing the r/w command. I don't know how you can do this trick in windows.
Code:
mtd=mount | grep system | awk '{print $1}'
echo "Mounting /system rw"
mount -o remount,rw -t yaffs2 $mtd /system
The question about the mount point isnt in the newer version. It just assumes that the system mtdblock is 0.
If it causes a problem in the future I may change it back to selecting the mtdblock number but from all the times I have tried the mtdblock on the x10 mini pro has always been 0.
In windows the answer is just saved as a variable that you assign to the question.
Sent from my X10 Mini Pro using XDA App
Updated with v3.
Just added new way of gaining ROOT access and another check to make sure phone is ROOTed.
EDIT: Oops forgot I had posted last :/ Sorry
3.2.0.0-r3 is old newest is 3.2.0.0-r5
I tried to fix permissions but it's been doing that for almost an hour now... Is that normal, to take that long? Should I remove the battery?
EDIT: Forget it, after looong time waiting, it's finished
EDIT 2: It erased all my preferences! Is that supposed to happen?
I have never had to fix permissions myself so I don't know the process it uses. You could try in the CWM thread where they should be able to help you. Link is http://forum.xda-developers.com/showthread.php?t=1106146
Sorry
quangnhut123 - I don't have that version of CWM and the CWM thread only has r3. If you have r5 then could you give me the files please and will update it.
rect2409 said:
I have never had to fix permissions myself so I don't know the process it uses. You could try in the CWM thread where they should be able to help you. Link is http://forum.xda-developers.com/showthread.php?t=1106146
Sorry
quangnhut123 - I don't have that version of CWM and the CWM thread only has r3. If you have r5 then could you give me the files please and will update it.
Click to expand...
Click to collapse
r5 is the one with multiboot i believe
x10man said:
r5 is the one with multiboot i believe
Click to expand...
Click to collapse
Ahhh. Okay didn't realise that.
Have uploaded a version that includes r5 for the people that have to have the latest... Also kept v3 up as all that has changed is the CWM version.
Looking to setup a new phone I encountered the issue that there is no way from LINE itself to transfer chat, except the very tedious mechanism to ex- and import every single contact chat manually. What's worse, this doesn't work with group chats. The other documented alternative is using Titanium Backup, but this requires root. After some further investigation I finally discovered that the Android Debug Bridge (adb) - which is part of the official Android SDK - offers everything that is needed to backup and transfer LINE to second smartphone. That means it works root-free and without any paid tools. You can use this process either to transfer the data to a new device or to restore it to the same device, for this description I assume you're going to copy it to a new phone.
The short version is, you can use adb to:
Read out android_id
Install an old LINE version that allows adb backups (in LINE < 5.3 android:allowBackup is not set, thus by default true)
Backup LINE app data & LINE sdcard data
Set android_id (on new device), which LINE is checking to validate it's data
Restore LINE app data & LINE sdcard data (to new device)
The long version
Prerequisites
Enable the Email verification for your LINE account. If something goes wrong , you will at least have access to all of your contacts and messages of the last weeks.
You must have ADB working. I'm not going to explain how to install it in detail, you should be able to find Android Developer guides who cover that (e.g. http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/) The rough outline is:
- install Android SDK
- install USB phone drivers from you phone manufacture
- enable (hidden) Developer Mode/USB debug mode on your phones
Furthermore you must have an old line APK, I used LINE 5.1 You should have no issue to find it online in one of the APK archives. As mentioned earlier, the current versions of LINE does not allow ADB backups, like old versions do. Luckily you can install an old version, while keeping the data. Ideally the old LINE versions never runs, so that it has no chance to corrupt your chat-data. However even accidentally running it, didn't have any visible impact on my data, the app closed itself after starting.
For the next steps I assume you have a folder called c:\backup\line to store the backup inside and already containing a file called 'line-old.apk' which - as the name suggests - is your copy of an old line apk.
Backup old phone
) Close/Kill LINE app if it's running, disconnect from WLAN and put into flight mode (to ensure that nothing wants to interact with the LINE app) and connect your old phone via USB cable
------
) Start ADB service:
Code:
adb start-server
Accept access/fingerprint from ADB on your old phone, if you haven't done so already
------
) Create a file called android_id.txt that contains your android_id:
Code:
adb shell settings get secure android_id > c:\backup\line\android_id.txt
You can also use "adb shell settings get secure android_id" to simply show the current android_id value.
------
) Install old LINE Version:
Code:
adb install -r -d c:\backup\line\line-old.apk
-r = reinstall, keep data; -d = allow to install older version
------
) Backup LINE app data (chats) to your PC:
Code:
adb backup -f c:\backup\line\line.ab jp.naver.line.android
You need to click 'allow backup' on your old phone
------
) Backup LINE sdcard data (images, sticker) to your PC:
Code:
adb pull /sdcard/Android/data/jp.naver.line.android c:\backup\line\sdcard
------
) (optional) restore current LINE APK, either by using an APK like in step 4.) or via updating through Google Play store
------
) End ADB service
Code:
adb kill-server
------
) Finished, disconnect your old phone from your PC
Restore to (new) phone:
) Connect your new phone via USB cable
------
) Start ADB service:
Code:
adb start-server
Accept access/fingerprint from ADB on your new phone, if you haven't done so already
------
) Change your new phone android_id to that of your old phone. Replace XXXXXXXX with the value inside c:\backup\line\android_id.txt
Code:
adb shell settings put secure android_id XXXXXXXX
You can use "adb shell settings get secure android_id" to show the current android_id value.
------
) Install old LINE Version:
Code:
adb install -r -d c:\backup\line\line-old.apk
-r = reinstall, keep data; -d = allow to install older version
------
) Upload LINE app data (chats) to your new phone:
Code:
adb restore c:\backup\line\line.ab
Click on your phone to "restore my data"
------
) Upload LINE sdcard data (images, sticker) to your new phone:
Code:
adb push c:\backup\line\sdcard /sdcard/Android/data/jp.naver.line.android
------
) Install current LINE APK, either by using an APK like in step 4.) or via updating through Google Play store
------
) End ADB service
Code:
adb kill-server
------
) Finished, disconnect your new phone from your PC
Final notes
Alternatively to changing the the android_id it used to be - and maybe still is? - possible to erase the settings. I haven't tried this and I can't see any real downsides to reusing the android_id. Considering how easy it is to change, I wouldn't consider it a specially protected property.
Thank you for the very good description!
However, when I try to downgrade current Line 7.3.0 I get an error message:
"c:\backup\line\line-old.apk: 1 file pushed. 5.0 MB/s (23629798 bytes in 4.516s)
pkg: /data/local/tmp/line-old.apk
Failure [INSTALL_FAILED_PERMISSION_MODEL_DOWNGRADE]
c:\tools>adb backup -f c:\backup\line\line.ab jp.naver.line.android
Now unlock your device and confirm the backup operation...
c:\tools>adb pull /sdcard/Android/data/jp.naver.line.android c:\backup\line\sdcard
/sdcard/Android/data/jp.naver.line.android/: 435 files pulled. 0.7 MB/s (1825753 bytes in 2.469s)!"
So the backup file: line.ab only become 42 bytes.
The Failure message semmes to be something new from Android 6 ?
Is there a way to get around this?
kamoj1 said:
Thank you for the very good description!
However, when I try to downgrade current Line 7.3.0 I get an error message:
"c:\backup\line\line-old.apk: 1 file pushed. 5.0 MB/s (23629798 bytes in 4.516s)
pkg: /data/local/tmp/line-old.apk
Failure [INSTALL_FAILED_PERMISSION_MODEL_DOWNGRADE]
c:\tools>adb backup -f c:\backup\line\line.ab jp.naver.line.android
Now unlock your device and confirm the backup operation...
c:\tools>adb pull /sdcard/Android/data/jp.naver.line.android c:\backup\line\sdcard
/sdcard/Android/data/jp.naver.line.android/: 435 files pulled. 0.7 MB/s (1825753 bytes in 2.469s)!"
So the backup file: line.ab only become 42 bytes.
The Failure message semmes to be something new from Android 6 ?
Is there a way to get around this?
Click to expand...
Click to collapse
If u have root the easiest way is
Get old android_id
Backup line with titanium backuo
Put old android_id on new device
Restore line backup
kamoj1 said:
So the backup file: line.ab only become 42 bytes.
The Failure message semmes to be something new from Android 6 ?
Is there a way to get around this?
Click to expand...
Click to collapse
I've looked around and the only way around that message is to uninstall the App. You can uninstall an app and keep it's data with adb, so in theory this should work:
Backup old phone
4) Install old LINE Version:
Code:
adb shell pm uninstall -k jp.naver.line.android
adb install -r -d c:\backup\line\line-old.apk
But fair warning, I haven't tried it myself.
Amazing! Working for me.
Thank you very much for your effort.
Very appreciated.
Hey there, hoping I can get a reply from you in regards to this tutorial.
I had followed everything to the T, made backups and made sure to be careful along the way... upon logging in on my new device, I had to log in via Facebook, wasn't a problem at all, and I was back into my account, however it seems like my chats didn't get moved over at all. On the otherhand, it seems like my stickers were able to be transferred over due to them popping up in my store (unless that's simply due to them being associated with my account).
I'm lucky enough to have root somewhat working (it's slightly broken atm) on my old device, so at least I was able to nandroid backup before attempting to backup/uninstall any data... and am currently attempting to restore back into the backup with hopes that all of my chat data is available as it was before I attempted to transfer.
Currently my root is broken, and cause any backups from TB to show an "insufficient space" error message (unless this is because I am using a PRO apk I found somewhere... maybe I should try another TB apk.
Anyhow, I also ran into the "Failure INSTALL_FAILED_PERMISSION_MODEL_DOWNGRADE" which the above member ran into and used your suggested steps which seemed to work for him.
Waiting on your reply! Thanks ahead of time!
Sounds to me like your data wasn't transferred at all. Stickers are indeed bound to your account and remain with it even if you switch from Android to iOS. Unless you had your old phone connected to the internet and used LINE again, the data should be still on that phone. (LINE is deleting it, if it detects you moved to a second phone (or probably changed the android_id?)).
Anyways, trying to pin down your issue: As part of the first steps, you should have created backup files of your chats (line.ab) and your sd card. Did they end up on your PC? line.ab for me was around 40MB and there are plenty of files in the sdcard folder.
Can this method be used for line lite? what modification in the command should I use?
I want full version of it
Any new and easy way to move all line chat logs/chats along with images from a previous device to a new device?
https://help.line.me/line/android/pc?lang=en
desiregeek said:
Any new and easy way to move all line chat logs/chats along with images from a previous device to a new device?
https://help.line.me/line/android/pc?lang=en
Click to expand...
Click to collapse
I am afraid the solution in the link you provided doesn't allow the back-up of media that are older than a few weeks old (The rest of the chats will be backuped though
It looks like that the push command doesn't have the permissions to write anything on last Android versions like 12
Code:
adb push c:\backup\line\sdcard /sdcard/Android/data/
adb: error: failed to copy 'c:\backup\line\sdcard\jp.naver.line.android\.nomedia' to '/sdcard/Android/data/jp.naver.line.android/.nomedia': remote secure_mkdirs failed: Operation not permitted
adb: error: failed to read copy response
This is the main limit on an unrooted phone, I am trying to see if I can do anything repacking those together into the line.ab file which is possible to be restored but missing the other data.
- 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