Related
I am trying to unlock my HTC Incredible 4G on Verizon to load a new ROM onto it. All of my attempts have failed up to this point, by using the WinDroid v2.3 automated tool. I get the following output during the process:
Code:
Task:
1) WINDROID USERS CHOOSE THIS OPTION!
2) Set CID to SuperCID (11111111) - Requires Root
3) Revert CID to original state (VZW__001) - Requires Root
4) Re-lock the bootloader
5) Install recovery
6) Put phone into temp-root mode
10) Exit
Choose a task: 1
========================
= Step 1: Temp-Root =
========================
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FA************ device
Under "List of devices attached" above, you should see your device
listed (looks like HTXXXXXXXXXX).
Do you see your device (Y/N)? y
Now unlock your device and confirm the restore operation.
By the time you are done reading this sentence, it should be safe to
accept the restore prompt on your device. You should not have a backup
password set on your phone, so leave both password fields empty.
If this process is successful, the script will continue. If not, this
shell will run forever and you must exit by closing this window.
When you see this message, the restore is complete. Your phone will
now reboot to what looks like an unusable state (be patient!). A
status bar will show across the top, but there will be no ring unlock.
This is good! Wait for the script to begin step 2: SuperCID.
========================
= Step 2: SuperCID =
========================
Your phone's CID is being modified to SuperCID. Once complete, your
phone will reboot to the bootloader.
2+0 records in
2+0 records out
1024 bytes transferred in 0.025 secs (40960 bytes/sec)
142 KB/s (1024 bytes in 0.007s)
31 KB/s (1024 bytes in 0.032s)
2+0 records in
2+0 records out
1024 bytes transferred in 0.035 secs (29257 bytes/sec)
< waiting for device >
...
(bootloader) cid: VZW__001
OKAY [ 0.011s]
finished. total time: 0.012s
Just above, you should see (bootloader) cid: 11111111
1) Yes, my cid is 11111111. Keep going.
2) No, my cid is VZW__001. Factory reset and try again.
3) No, my cid is VZW__001. Exit the script.
There are two things I notice here:
1) My phone is not identified as "HTxxxxxxxxxx" but rather "FA**********".
2) It appears to work, with the reading and writing of the files, but then it doesn't work.
One thing that I noticed was that when I go into the bootloader when this does not work, I get the first attachment.
When I go to the "Recovery" option, then I get the second attachment.
It appears that I originally put a ROM or S-off'd and unlocked my phone, but somehow lost the unlock and can't figure out how to fix it.
Any help in figure it out would be appreciated.
Do you know which OTA is currently on the phone? The unlock method depends greatly on which one is installed. Assuming you're on the latest, try this method: http://forum.xda-developers.com/showthread.php?t=2664460 The script looks slightly different than what you've posted above.
junkmail9 said:
Do you know which OTA is currently on the phone? The unlock method depends greatly on which one is installed. Assuming you're on the latest, try this method: http://forum.xda-developers.com/showthread.php?t=2664460 The script looks slightly different than what you've posted above.
Click to expand...
Click to collapse
Thanks for the input.
My device is at the most current OTA: 2.19.605.2 710RD
Android: 4.0.4
Kernel:
3.0.8-01625-g9d06ef9
[email protected] #1
SMP PREEMPT
I tried the link that you pointed to with no success. I got the following error messages:
Code:
/sdcard/cid: cannot open for write: Read-only file system
remote object '/sdcard/cid' does not exist
The system cannot find the file specified.
cannot stat 'cid': No such file or directory
/sdcard/cid: cannot open for read: No such file or directory
rm failed for /sdcard/cid, No such file or directory
Could Not Find C:\Users\Keith\Downloads\cid
I've tried just the straight-forward process of a number of different scripts. I think there is something specific that I am missing.
keithsmessina said:
Thanks for the input.
My device is at the most current OTA: 2.19.605.2 710RD
Android: 4.0.4
Kernel:
3.0.8-01625-g9d06ef9
[email protected] #1
SMP PREEMPT
I tried the link that you pointed to with no success. I got the following error messages:
Code:
/sdcard/cid: cannot open for write: Read-only file system
remote object '/sdcard/cid' does not exist
The system cannot find the file specified.
cannot stat 'cid': No such file or directory
/sdcard/cid: cannot open for read: No such file or directory
rm failed for /sdcard/cid, No such file or directory
Could Not Find C:\Users\Keith\Downloads\cid
I've tried just the straight-forward process of a number of different scripts. I think there is something specific that I am missing.
Click to expand...
Click to collapse
Sorry for the delay in response. Looking again at your screenshot in the OP, you are indeed missing the CID. It should appear between "FIREBALL" and "HBOOT":
I have not dealt directly with that one before, but I would imaging that during temproot, you'll need to recreate the directory. I vaguely recall in a post in this forum on how to manually push a different CID via memory chunk. That might be the best approach to rebuild that area so that you can get going again.
Two questions for the general community:
1. Does anyone know if flashing the RUU will restore the CID?
@keithsmessina - It probably wouldn't hurt to try this anyway. I am guessing it will fail due to lack of CID.
2. Will sending the following command work while phone is in bootloader if the phone is not s-off and the \sdcard\CID directory is missing? What, if any other damage could occur if the \sdcard\CID directory is missing?
Code:
fastboot oem writecid VZW__001
junkmail9 said:
Two questions for the general community:
1. Does anyone know if flashing the RUU will restore the CID?
@keithsmessina - It probably wouldn't hurt to try this anyway. I am guessing it will fail due to lack of CID.
2. Will sending the following command work while phone is in bootloader if the phone is not s-off and the \sdcard\CID directory is missing? What, if any other damage could occur if the \sdcard\CID directory is missing?
Code:
fastboot oem writecid VZW__001
Click to expand...
Click to collapse
Thank you for the suggestions.
1. I tried this, but got the message: "Main version is older." I think I can only do that if my version is lower than the current RUU.
2. I tried the fastboot write, but I got:
Code:
(bootloader) fighter_init_sd, SD card already power on
(bootloader) sdhw_7xxx_open: id=0
(bootloader) sdcc_init_memory_device done
(bootloader) SD clock freq = 19MHz....
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 0.172s]
finished. total time: 0.174s
When I tried: adb devices with the phone at "fastboot USB", I didn't see anything, so I think it failed for that reason. I tried killing adb, removing and reinserting the USB, adn then running adb devices, but still comes up empty.
I'm really at a loss, but appreciate the help from you guys.
I managed to figure out the read-inly access. HTC Sync Manager started each time and grabbed the SD card before the script could do anything. I renamed the HTC Sync Manager to stop it from running. Then I re-ran the script and got:
Code:
2+0 records in
2+0 records out
1024 bytes transferred in 0.002 secs (512000 bytes/sec)
333 KB/s (1024 bytes in 0.003s)
71 KB/s (1024 bytes in 0.014s)
2+0 records in
2+0 records out
1024 bytes transferred in 0.002 secs (512000 bytes/sec)
< waiting for device >
...
(bootloader) cid: VZW__001
OKAY [ 0.010s]
finished. total time: 0.012s
So, I am still not getting the right CID, but progress nonetheless.
Try uninstalling all HTC software rather than renaming it. Also I believe
http://forum.xda-developers.com/showthread.php?t=2664460 does not require the super cid.
From my Chroma Flo
wmuflyer said:
Try uninstalling all HTC software rather than renaming it. Also I believe
http://forum.xda-developers.com/showthread.php?t=2664460 does not require the super cid.
From my Chroma Flo
Click to expand...
Click to collapse
Thank you for that. I don't know how many times I've gone through it, but I finally got that you just have to do step 6 rather than step 1 to get S-Off. I now have S-Off with TWRP.
The next problem that I am running into is getting an error message when trying to flash the pacman fireball ROM:
Code:
This package is for device: fireballx; this device is .
Really appreciate all the help in getting me to this point.
Need to use the modified TWRP. Read the OP carefully it takes a bit of work, it swaps partitions so you have more space for apps.
Edit: OP in the PAC thread.
Sent from my Nexus 5 using XDA Free mobile app
wmuflyer said:
Need to use the modified TWRP. Read the OP carefully it takes a bit of work, it swaps partitions so you have more space for apps.
Edit: OP in the PAC thread.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I realize that I kept running into an issue changing one of the file systems during that first process which meant that only one of them changed: the "Data" filesystem.
The "Internal Storage" filesystem gave me an MTP error, but then said it finished successfully. It stayed as a vFAT filesystem.
I did get Liquidsmooth up and running with PaGapps, but am now looking for a way to resize my partitions, as there isn't much room left to install apps.
People have looked at resizing the partitions but nobody has had any luck. The partition change seems to be the best bet it was set up by MDMower for his CM builds http://mdmower.cmphys.com/cyanogenmod-fireball/ it might give you more information to make the swap. Beeko has stopped work on Liquid Smooth so for current Android 5.x PAC or CM are the choices and they only work with the partition swap. I have PAC on my Fireball but will probably try CM 12.1 soon.
keithsmessina said:
Thank you for that. I don't know how many times I've gone through it, but I finally got that you just have to do step 6 rather than step 1 to get S-Off. I now have S-Off with TWRP.
Click to expand...
Click to collapse
Excellent! Glad you got it done.
junkmail9 said:
Excellent! Glad you got it done.
Click to expand...
Click to collapse
I've managed to swap the partitions and get the Pacman ROM installed, thanks to the instructions you sent me, wmuflyer. No hiccups with the Pacman ROM, it seems to be polished and working flawlessly. Thanks again for all the help, guys! Really appreciate it.
Hi, I have a stock Tablet Z on 10.7.A.0.222
I have successfully unlocked the bootloader via instructions on xperia firmware. However I have been unable to root it or install twrp.
I am a complete noob at this but the tablet is running incredibly laggy as stock so want to refresh it. I was using this guide:
https://www.cyanogenmods.org/forums/topic/xperia-tablet-z-cm14-cyanogenmod-14-nougat-7-0-rom/
In that guide I got to 1b which led me to this guide for installing recovery:
https://www.cyanogenmods.org/forums/topic/install-twrp-recovery-android-using-fastboot/
When i try to do step 6 the tablet shuts off and does not go into bootloader mode where I can flash twrp.
Can someone provide direction on what I need to do differently? I have done various searches on this site and I believe there is not a recovery installed in this firmware version or something and that is preventing me from being able to do this step but I am not sure how I get around that.
cward0625 said:
Can someone provide direction on what I need to do differently? I have done various searches on this site and I believe there is not a recovery installed in this firmware version or something and that is preventing me from being able to do this step but I am not sure how I get around that.
Click to expand...
Click to collapse
Hello!
Look at this thread.
Rootk1t said:
Hello!
Look at this thread.
Click to expand...
Click to collapse
Thanks for the response, I had referred to this guide too but was unable to get this step to work for me->
- Root. Follow Bin4ry root : http://forum.xda-developers.com/show....php?t=1886460
Download : http://forum.xda-developers.com/show....php?t=1886460
Below is what I get in the command prompt when doing the steps. When I tried option 4 for new xperia root it did not work...it just hangs here:
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry =
= (15.06.2014) v36 =
======================================================================
Device type:
0) New Z2 Root Method by cubeandcube (thanks man!)
1) 2014 root (thx jcase for nice pwn binary and xsacha for the exploit)
2) Xperia Root by cubeundcube
3) New Standard-Root (thx Ariel Berkman)
4) New Xperia Root by Goroh_kun (Xperia Z, Xperia V [JellyBean] ...)
5) Old
6) Old-Special (for example: Sony Tablet S, Medion Lifetab)
G) Google Glass Mode (thx Saurik for the ab file)
x) Unroot
Make a choice: 4
Please connect Xperia device with enabled USB-Debugging now to your Computer
Going to copy over some files ...
33 KB/s (442 bytes in 0.012s)
33 KB/s (170 bytes in 0.004s)
13 KB/s (57 bytes in 0.003s)
Starting restore operation, please look on your device and confirm restore!
after that press anykey here in the console
Now unlock your device and confirm the restore operation.
Press any key to continue . . .
After restore is confirmed please look on your device and choose "Service Tests -> Display" in Service menu and WAIT THERE!"
Starting: Intent { act=android.intent.action.MAIN cmp=com.sonyericsson.android.servicemenu/.ServiceMainMenu }
/data/local/tmp/onload.sh ...
Then if I try option 1 instead I get this (although I do not think this is the correct option anyways:
Device type:
0) New Z2 Root Method by cubeandcube (thanks man!)
1) 2014 root (thx jcase for nice pwn binary and xsacha for the exploit)
2) Xperia Root by cubeundcube
3) New Standard-Root (thx Ariel Berkman)
4) New Xperia Root by Goroh_kun (Xperia Z, Xperia V [JellyBean] ...)
5) Old
6) Old-Special (for example: Sony Tablet S, Medion Lifetab)
G) Google Glass Mode (thx Saurik for the ab file)
x) Unroot
Make a choice: 1
Exploit type:
0) xsacha Z2 Tablet Root
1) jcase Z1S Root (make sure to download the pwn binary first from XDA thread!)
Make a choice: 1
Please connect your device with enabled USB-Debugging ...
Copy needed files ...
4106 KB/s (574722 bytes in 0.136s)
6023 KB/s (104576 bytes in 0.016s)
5317 KB/s (2139595 bytes in 0.392s)
72 KB/s (148 bytes in 0.001s)
1024 KB/s (2092 bytes in 0.001s)
4525 KB/s (1109128 bytes in 0.239s)
Beaups and jcase were here
donations may go here, pleaes say what it was for -> [email protected]
Rebooting device, please wait ...
mount: Permission denied
dd: /system/xbin/su: Read-only file system
chown: /system/xbin/su: No such file or directory
Unable to open /system/xbin/su: No such file or directory
ln: /system/bin/su: Read-only file system
dd: /system/app/Superuser.apk: Read-only file system
chown: /system/app/Superuser.apk: No such file or directory
Unable to open /system/app/Superuser.apk: No such file or directory
dd: /system/xbin/busybox: Read-only file system
chown: /system/xbin/busybox: No such file or directory
Unable to open /system/xbin/busybox: No such file or directory
/data/local/tmp/install_tool.sh[39]: /system/xbin/busybox: not found
mount: Permission denied
"If this helped you please consider donating to the original author jcase: http://forum.xda-developers.com/showpost.php?p=53407127&postcount=1004"
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Press any key to continue . . .
Any ideas on what I am doing wrong or what I need to do differently?
I have rooted my phones before and installed different ROMs but something seems to be off here.
cward0625 said:
Thanks for the response, I had referred to this guide too but was unable to get this step to work for me->
Any ideas on what I am doing wrong or what I need to do differently?
I have rooted my phones before and installed different ROMs but something seems to be off here.
Click to expand...
Click to collapse
forget about root. To install TWRP to FOTA or custom ROM, you don't need it.
Proceed with step 7.
Rootk1t said:
forget about root. To install TWRP to FOTA or custom ROM, you don't need it.
Proceed with step 7.
Click to expand...
Click to collapse
thanks a lot, I did that, got lineage installed, worked fine, then when I followed the directions to install gapps and rebooted it just keeps loading twrp and not to lineage. I tried wiping and starting over and getting the same thing. Is there something I need to do differently? I used gapps arm 7.1 neon 20181118
thanks again
cward0625 said:
thanks a lot, I did that, got lineage installed, worked fine, then when I followed the directions to install gapps and rebooted it just keeps loading twrp and not to lineage. I tried wiping and starting over and getting the same thing. Is there something I need to do differently? I used gapps arm 7.1 neon 20181118
thanks again
Click to expand...
Click to collapse
wiping and installing 14.1 did not work, but when i did 15.1 it did. I think I should be set now.
Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
THIS WILL NOT WORK ON AMAZFIT PACE, STRATOS OR STRATOS3
THIS WILL NOT WORK ON AMAZFIT PACE, STRATOS OR STRATOS3
THIS WILL NOT WORK ON AMAZFIT PACE, STRATOS OR STRATOS3
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please make sure you read and understand everything written in the post before flashing it! YOU are choosing to make these modifications and must be sure of what it does.
Click to expand...
Click to collapse
Only for unlocked Bootloader
The unlock system doesn't allow WOS (Watch Operating System) 3.0 ROM versions yet, so you need to use any other valid WOS 2.0 ROM version like 2.6.4.1 or 2.0.43.1.Supported devices: A1801 (Chinese) and A1811 (English)
Properly installed ADB and Fastboot drivers as system wide
Watch battery +40% (50% recommended)
Click to expand...
Click to collapse
For anyone interested on installing Stock/Original English Firmware with OTA updates.
Click to expand...
Click to collapse
[MENTION]Neur_User[/MENTION] for PACEfied, STRATOSfied projects and other stuff
[MENTION]Cracklydisc[/MENTION] for AmazIT, StratOS projects and other stuff
Capara [MENTION]1mmortal[/MENTION] for his great support and collaboration
@Nacken and @To+ for collaborating
Click to expand...
Click to collapse
1. Connect the watch to your PC
2. Unzip the the folder
3. Run flash_US.bat file for English interface (Don't do it as Administrator since is known to cause issues)
4. Wait to the end of the process and don't touch anything
Alternative firmware and OTA installers since v3.2.6.0. Check for More info link of Downloads section.
********************************************************
US Verge 3.2.2.0 Stock Firmware Installer by Saratoga
********************************************************
0. Rebooting adb server
*************************
*****************************
1. Connect the watch to PC
*****************************
*******************************
2. Rebooting to Fastboot mode
*******************************
****************************
3. Checking the connection
****************************
****************************
4. Booting modded recovery
****************************
< waiting for any device >
Downloading 'boot.img' OKAY [ 0.463s]
booting FAILED (status read failed (Too many links))
Finished. Total time: 1.562s
***********************************
5. Waiting connection in Recovery
***********************************
******************
6. Copying files
******************
boot.img: 1 file pushed. 7.1 MB/s (9437184 bytes in 1.267s)
system.img.gz: 1 file pushed. 4.9 MB/s (332793308 bytes in 65.424s)
md5s.txt: 1 file pushed. 0.1 MB/s (91 bytes in 0.001s)
flash_rom.sh: 1 file pushed. 0.4 MB/s (458 bytes in 0.001s)
**************************
7. Firmware installation
**************************
Validating images
boot.img: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 1.651994 seconds, 5.4MB/s
Flashing system.img
210944+0 records in
210944+0 records out
864026624 bytes (824.0MB) copied, 101.353872 seconds, 8.1MB/s
Finished
*******************
8. Removing files
*******************
**************
9. Rebooting
**************
***********************************
10. Changing language to English
***********************************
List of devices attached
d41e250a device
***************************************************
Stock Recovery and Bootloader installation process
***************************************************
********************************
11. Rebooting to Fastboot mode
********************************
***************************
12. Booting temporal root
***************************
< waiting for any device >
Downloading 'boot.img' OKAY [ 0.373s]
booting FAILED (status read failed (Too many links))
Finished. Total time: 1.426s
*******************
13. Copying files
*******************
install_recovery.sh: 1 file pushed. 0.1 MB/s (687 bytes in 0.005s)
recovery.img: 1 file pushed. 2.0 MB/s (16777216 bytes in 8.153s)
u-boot-with-spl-mbr-gpt.bin: 1 file pushed. 2.9 MB/s (964968 bytes in 0.312s)
*****************************
14. Flashing Stock recovery
*****************************
============= STOCK Installer ===============
Done. OTA updates should now work.
*************************
15. Flashing Bootloader
*************************
1884+1 records in
1884+1 records out
964968 bytes (942.4KB) copied, 0.131429 seconds, 7.0MB/s
********************
16. Removing files
********************
***************
17. Rebooting
***************
************
18. Finish
************
Presione una tecla para continuar . . .
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Latest version
Stock US/Global/International Firmware Installer 3.2.7.5 with OTA updates | More Info
Previous versions
Stock US/Global/International Firmware Installer 3.2.7.0 with OTA updates | More Info
Stock US/Global/International Firmware Installer 3.2.6.0 with OTA updates | More Info
Stock US/Global/International Firmware Installer 3.2.5.0 with OTA updates | More Info
Stock US/Global/International Firmware Installer 3.2.4.0 with OTA updates | More Info
Stock US/Global/International Firmware Installer 3.2.3.0 with OTA updates | More Info
Stock US/Global/International Firmware Installer 3.2.2.0 with OTA updates | Mirror | More Info
Stock US/Global/International Firmware Installer 3.2.1.0 with OTA updates | Mirror
Stock US/Global/International Firmware Installer 3.2.0.13 with OTA updates | Mirror
Stock US/Global/International Firmware Installer 3.2.0.7 with OTA updates | Mirror
Click to expand...
Click to collapse
If you like my work you can buy me a beer here
Click to expand...
Click to collapse
Manual Installation Method
Manual Installation Method
Introduction
Here I will explain how to install the firmware using a command window or any other terminal.
The requirements are the ones stated in Post #1.
Unbrick
If your watch is stuck on Amazfit A logo and it doesn't boot, you will need to boot into fastboot manually using the button trick based on this thread:
Watch always connected into PC
Start with same steps of pushing-releasing the button as the video guide
But, when screen goes off, count until "6 mississippis" while screen is off and then release the button, it should be done before Amazfit logo shows
Push the button again to enter fastboot mode
Check fastboot connection as stated on Step #3
5.1 If fastboot devices command doesn't work and you get waiting for device string, that happened to me, disconnect the watch and reconnect to PC again
Now, download and unzip this UNBRICK file, and run UNBRICK_US.bat if you are on Windows PC, or just starting on Step #3 of the manual commands.
Manual commands
On your terminal, go to the path where all the files were unzipped and you are good to go.
Manual command installation
You can copy and paste all needed commands.
Firmware installation
1. Connect the watch to the PC and check the connection with the watch
Code:
[COLOR="Blue"]adb devices[/COLOR]
Output (or similar)
Code:
List of devices attached
9dee1d33 device
2. Reboot in fastboot mode
Code:
[COLOR="blue"]adb shell reboot bootloader[/COLOR]
3. When the watch reboots in fastboot mode, check the connection with the watch
Code:
[COLOR="blue"]fastboot devices[/COLOR]
Output (or similar)
Code:
0123456789 fastboot
4. Boot the modded recovery
Code:
[COLOR="blue"]fastboot boot recovery-mod.img[/COLOR]
Output (or similar)
Code:
downloading 'boot.img'...
OKAY [ 0.426s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 1.303s
5. Wait until you get a triangle with an exclamation mark (!) in your watch
6. Copy the files to the watch (it may take upto a minute)
Code:
[COLOR="blue"]adb push boot.img /data/media/0/
adb push system.img.gz /data/media/0/
adb push md5s.txt /data/media/0/
adb push flash_rom.sh /data/media/0/[/COLOR]
Output (or similar)
Code:
adb push boot.img /data/media/0/
7546 KB/s (9437184 bytes in 1.221s)
adb push system.img.gz /data/media/0/
7194 KB/s (228153632 bytes in 30.969s)
adb push md5s.txt /data/media/0/
88 KB/s (91 bytes in 0.001s)
adb push flash_rom.sh /data/media/0/
297 KB/s (458 bytes in 0.001s)
7. Start Firmware installation (it may take up to 2 minutes)
Code:
[COLOR="blue"]adb shell sh /data/media/0/flash_rom.sh[/COLOR]
Output (or similar)
Code:
Validating images
boot.img: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 0.953804 seconds, 9.4MB/s
Flashing system.img
210944+0 records in
210944+0 records out
864026624 bytes (824.0MB) copied, 89.945101 seconds, 9.2MB/s
Finished
8. We have already installed the firmware, now delete installation files form the watch
Code:
[COLOR="blue"]adb shell rm /data/media/0/boot.img
adb shell rm /data/media/0/system.img.gz
adb shell rm /data/media/0/md5s.txt
adb shell rm /data/media/0/flash_rom.sh[/COLOR]
9. Reboot the watch
Code:
[COLOR="blue"]adb reboot[/COLOR]
10. When the splash screen is passed and the bootanimation starts, set your watch to English language
Code:
[COLOR="blue"]adb shell setprop persist.sys.language en
adb shell setprop persist.sys.country US[/COLOR]
Stock recovery installation process
11. Reboot in fastboot mode
Code:
[COLOR="blue"]adb shell reboot bootloader[/COLOR]
12. Boot temporal root
Code:
[COLOR="blue"]fastboot boot boot-US-adb-root.img[/COLOR]
Output (or similar)
Code:
downloading 'boot.img'...
OKAY [ 0.349s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 1.206s
13. Copy stock recovery files to the watch
Code:
[COLOR="blue"]adb push install_recovery.sh /data/media/0/
adb push recovery.img /data/media/0/[/COLOR]
Output (or similar)
Code:
[100%] /data/media/0/install_recovery.sh
[100%] /data/media/0/recovery.img
14. Run the recovery installation script
Code:
[COLOR="blue"]adb shell cd /data/media/0/; sh install_recovery.sh[/COLOR]
Or if above command doesn't work, do it in 2 commands
Code:
[COLOR="blue"]adb shell cd /data/media/0/
adb shell sh install_recovery.sh[/COLOR]
Output (or similar)
Code:
============= STOCK Installer ===============
Flashing recovery...
4096+0 records in
4096+0 records out
16777216 bytes (16.0MB) copied, 2.461221 seconds, 6.5MB/s
Done. OTA updates should now work.
15 . Delete stock recovery installation files
Code:
[COLOR="blue"]adb shell rm /data/media/0/install_recovery.sh
adb shell rm /data/media/0/recovery.img [/COLOR]
16. Reboot the watch
Code:
[COLOR="blue"]adb reboot[/COLOR]
17. Finish.
Go to Amazfit app and update to latest version.
Some extra useful commands
Wipe dalvik/cache
Code:
[COLOR="blue"]adb shell reboot bootloader
fastboot erase cache
fastboot reboot[/COLOR]
Do a Factory Reset (You will lose all the data in your watch. Unpair the watch from Amazfit app while doing this?
Code:
[COLOR="Blue"]adb shell reboot bootloader
fastboot erase data
fastboot erase cache
fastboot reboot[/COLOR]
Reserved 1
Reserved 1
Thanks for the nice work. Has anyone tried it yet? I want to buy chinese version, so i want to know if this will work?
anaragayevafr said:
Thanks for the nice work. Has anyone tried it yet? I want to buy chinese version, so i want to know if this will work?
Click to expand...
Click to collapse
All excellent! Many users with 4PDA sewed from 1801 to 1811. But not yet updated on OTA to 3.2.0.6
Is it the same method on YouTube which converts 70-80% or this is new?
anaragayevafr said:
Is it the same method on YouTube which converts 70-80% or this is new?
Click to expand...
Click to collapse
This is full official firmware.
Saratoga79 said:
This is full official firmware.
Click to expand...
Click to collapse
I've tried but ... I must have the bootloader blocked because I get this message in step # 4:
********************************************************
US Verge 3.2.0.5 Stock Firmware Installer by Saratoga
********************************************************
1. Connect the watch to the PC
********************************
* daemon not running; starting now at tcp:5037
* daemon started successfully
*******************************
2. Rebooting to Fastboot mode
*******************************
****************************
3. Checking the connection
****************************
****************************
4. Booting modded recovery
****************************
< waiting for device >
downloading 'boot.img'...
FAILED (remote: ED: The command is not allowed.)
finished. total time: 0.023s
***********************************
5. Waiting connection in Recovery
***********************************
Click to expand...
Click to collapse
My Amazfit Verge is A1801 fw. 3.0.13.0
Very thanks
luacu said:
I've tried but ... I must have the bootloader blocked because I get this message in step # 4:
My Amazfit Verge is A1801 fw. 3.0.13.0
Very thanks
Click to expand...
Click to collapse
Yes, unlock the bootloader first.
Saratoga79 said:
Yes, unlock the bootloader first.
Click to expand...
Click to collapse
Ok, unlocked and all OK. Thank you very much for everything.
Te debo una
I just tried to go through the unlock procedure via the website. However it doesn't accept the OS version I point to. What am I missing?
All good
tried and everything is fine , thanks a lot
---------- Post added at 02:49 AM ---------- Previous post was at 02:44 AM ----------
Sash! said:
I just tried to go through the unlock procedure via the website. However it doesn't accept the OS version I point to. What am I missing?
Click to expand...
Click to collapse
you need to use the amazfit pace or stratos watch os version like this 2.6.4.1
Yes, the unlock system doesn't allow WOS (Watch Operating System) 3.0 ROM versions, so you need to use any other valid WOS 2.0 ROM version like 2.6.4.1 or 2.0.43.1.
Hi guys,and after this method of rebranding someone flew update OTA? I have information from the resource 4PDA that update 3.2.0.6 arrives for the owners of the global version, but the OTA I have not yet arrived after the rebranding. The question to the topic starter, at the end of the rebranding procedure, do you need to block the bootloader, as in smartphones?
lanch84 said:
Hi guys,and after this method of rebranding someone flew update OTA? I have information from the resource 4PDA that update 3.2.0.6 arrives for the owners of the global version, but the OTA I have not yet arrived after the rebranding. The question to the topic starter, at the end of the rebranding procedure, do you need to block the bootloader, as in smartphones?
Click to expand...
Click to collapse
I have a global version of the Verge and didn't receive the 3.2.0.6 update yet, so maybe just wait a little more.
Aximal said:
you need to use the amazfit pace or stratos watch os version like this 2.6.4.1
Click to expand...
Click to collapse
Thank you so much!
The unlock code arrived instantly and the flash procedure worked like charm.
Interestingly, the Settings menu title is still in Chinese.
Also, Mi Home, the Maps app and the vo8ce assistant are not there.
Also - quite a pity it is not NFC enabled as advertised back in september.
Going fine until step
echo ***************************
echo 12. Booting temporal root
echo ***************************
fastboot.exe boot boot-US-adb-root.img
Then fastboot refused to make the phone reboot. Have to reboot the phone and manual execute the rest of the commands.
Ota update to 3.2.0.7 install errer
lanch84 said:
Hi guys,and after this method of rebranding someone flew update OTA? I have information from the resource 4PDA that update 3.2.0.6 arrives for the owners of the global version, but the OTA I have not yet arrived after the rebranding. The question to the topic starter, at the end of the rebranding procedure, do you need to block the bootloader, as in smartphones?
Click to expand...
Click to collapse
Update to 3.2.0.6 was a Dev/Beta versión so only few people received the OTA. But it's tested that OTA update from 3.2.0.5 -> 3.2.0.6 worked fine.
apollow2007 said:
Going fine until step
echo ***************************
echo 12. Booting temporal root
echo ***************************
fastboot.exe boot boot-US-adb-root.img
Then fastboot refused to make the phone reboot. Have to reboot the phone and manual execute the rest of the commands.
Click to expand...
Click to collapse
And what was the output of the installer on that step? Well, If at least you managed to install the stock recovery manually you are good to go.
tinn44 said:
Ota update to 3.2.0.7 install errer
Click to expand...
Click to collapse
Do you have the update.zip OTA file on your phone's internal memory or on your watch? Seems to be a around 200MB update.
Btw, did you get any issue when installing stock recovery? OTA update from 3.2.0.5 -> 3.2.0.6 worked fine.
Still no OTA update here.
Saratoga79 said:
And what was the output of the installer on that step? Well, If at least you managed to install the stock recovery manually you are good to go.
Click to expand...
Click to collapse
The output of boot recovery is
downloading 'boot.img'...
OKAY [ 0.349s] FAILED (status read failed (Too many links))
No "booting" message. So I have to manually reboot the watch and re-issue the command again.
May be my laptop environment issue. But I managed to follow up with all the commands manually and finished the flash. The English ROM is much more zippy than the CN rom without the Xiaomi Voice Assistance hogging the CPU. No NFC, Mi Home and map functionality. Not surprise though as those are limited to China market.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
THIS WILL NOT WORK ON AMAZFIT PACE OR AMAZFIT STRATOS
THIS WILL NOT WORK ON AMAZFIT PACE OR AMAZFIT STRATOS
THIS WILL NOT WORK ON AMAZFIT PACE OR AMAZFIT STRATOS
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please make sure you read and understand everything written in the post before flashing it! YOU are choosing to make these modifications and must be sure of what it does.
Click to expand...
Click to collapse
Only for unlocked Bootloader
Supported devices: A1801 (Chinese) and A1811 (English)
Property installed ADB and Fastboot drivers as system wide
Watch battery +40% (50% recommended)
Click to expand...
Click to collapse
For anyone interested on installing Stock/Original Chinese Firmware with OTA updates.
Click to expand...
Click to collapse
@Neur_User for PACEfied, STRATOSfied projects and other stuff
@Cracklydisc for AmazIT, StratOS projects and other stuff
Capara @1immortal for his great support
Click to expand...
Click to collapse
1. Connect the watch to your PC
2. Unzip the the folder
3. Run flash_US.bat file for English interface (Don't do it as Administrator since is known to cause issues)
4. Wait to the end of the process and don't touch anything
********************************************************
CN Verge 3.0.12.0 Stock Firmware Installer by Saratoga
********************************************************
1. Connect the watch to the PC
********************************
*******************************
2. Rebooting to Fastboot mode
*******************************
****************************
3. Checking the connection
****************************
****************************
4. Booting modded recovery
****************************
< waiting for any device >
Downloading 'boot.img' OKAY [ 0.464s]
booting FAILED (status read failed (Too many links))
Finished. Total time: 1.535s
***********************************
5. Waiting connection in Recovery
***********************************
******************
6. Copying files
******************
boot.img: 1 file pushed. 7.3 MB/s (9437184 bytes in 1.232s)
system.img.gz: 1 file pushed. 5.1 MB/s (318817711 bytes in 60.127s)
md5s.txt: 1 file pushed. 0.0 MB/s (91 bytes in 0.002s)
flash_rom.sh: 1 file pushed. 0.2 MB/s (458 bytes in 0.002s)
**************************
7. Firmware installation
**************************
Validating images
boot.img: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 0.924353 seconds, 9.7MB/s
Flashing system.img
210944+0 records in
210944+0 records out
864026624 bytes (824.0MB) copied, 96.290046 seconds, 8.6MB/s
Finished
*******************
8. Removing files
*******************
**************
9. Rebooting
**************
*************************************
10. Changing language to Chinese
*************************************
List of devices attached
d41e250a device
**************************************
Stock recovery installation process
**************************************
********************************
11. Rebooting to Fastboot mode
********************************
***************************
12. Booting temporal root
***************************
< waiting for any device >
Downloading 'boot.img' OKAY [ 0.373s]
booting FAILED (status read failed (Too many links))
Finished. Total time: 1.422s
*******************
13. Copying files
*******************
install_recovery.sh: 1 file pushed. 0.2 MB/s (687 bytes in 0.003s)
recovery.img: 1 file pushed. 2.8 MB/s (16777216 bytes in 5.662s)
*****************************
14. Flashing Stock recovery
*****************************
============= STOCK Installer ===============
Done. OTA updates should now work.
*******************
15. Removing files
*******************
***************
16. Rebooting
***************
************
17. Finish
************
Presione una tecla para continuar . . .
Click to expand...
Click to collapse
* Step 14 may be different for you
Click to expand...
Click to collapse
Latest version
Stock CN/Chinese 3.0.43.0 Firmware Installer with OTA updates | Mirror
Previous versions
Stock CN/Chinese 3.0.29.0 Firmware Installer with OTA updates | Mirror
Stock CN/Chinese 3.0.12.0 Firmware Installer with OTA updates | Mirror
Stock CN/Chinese 3.0.10.0 Firmware Installer with OTA updates | Mirror
Click to expand...
Click to collapse
If you like my work you can buy me a beer here
Click to expand...
Click to collapse
Manual Installation Method
Manual Installation Method
Introduction
Here I will explain how to install the firmware using a command window or any other terminal.
The requirements are the ones stated in Post #1.
On your terminal, go to the path where all the files were unzipped and you are good to go.
Manual command installation
You can copy and paste all needed commands.
Firmware installation
1. Connect the watch to the PC and check the connection with the watch
Code:
[COLOR="Blue"]adb devices[/COLOR]
Output (or similar)
Code:
List of devices attached
9dee1d33 device
2. Reboot in fastboot mode
Code:
[COLOR="blue"]adb shell reboot bootloader[/COLOR]
3. When the watch reboots in fastboot mode, check the connection with the watch
Code:
[COLOR="blue"]fastboot devices[/COLOR]
Output (or similar)
Code:
0123456789 fastboot
4. Boot the modded recovery
Code:
[COLOR="blue"]fastboot boot recovery-mod.img[/COLOR]
Output (or similar)
Code:
downloading 'boot.img'...
OKAY [ 0.426s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 1.303s
5. Wait until you get a triangle with an exclamation mark (!) in your watch
6. Copy the files to the watch (it may take upto a minute)
Code:
[COLOR="blue"]adb push boot.img /data/media/0/
adb push system.img.gz /data/media/0/
adb push md5s.txt /data/media/0/
adb push flash_rom.sh /data/media/0/[/COLOR]
Output (or similar)
Code:
adb push boot.img /data/media/0/
7546 KB/s (9437184 bytes in 1.221s)
adb push system.img.gz /data/media/0/
7194 KB/s (228153632 bytes in 30.969s)
adb push md5s.txt /data/media/0/
88 KB/s (91 bytes in 0.001s)
adb push flash_rom.sh /data/media/0/
297 KB/s (458 bytes in 0.001s)
7. Start Firmware installation (it may take up to 2 minutes)
Code:
[COLOR="blue"]adb shell sh /data/media/0/flash_rom.sh[/COLOR]
Output (or similar)
Code:
Validating images
boot.img: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 0.953804 seconds, 9.4MB/s
Flashing system.img
210944+0 records in
210944+0 records out
864026624 bytes (824.0MB) copied, 89.945101 seconds, 9.2MB/s
Finished
8. We have already installed the firmware, now delete installation files form the watch
Code:
[COLOR="blue"]adb shell rm /data/media/0/boot.img
adb shell rm /data/media/0/system.img.gz
adb shell rm /data/media/0/md5s.txt
adb shell rm /data/media/0/flash_rom.sh[/COLOR]
9. Reboot the watch
Code:
[COLOR="blue"]adb reboot[/COLOR]
10. When the splash screen is passed and the bootanimation starts, set your watch to Chinese language
Code:
[COLOR="blue"]adb shell setprop persist.sys.language zh
adb shell setprop persist.sys.country CN[/COLOR]
Stock recovery installation process
11. Reboot in fastboot mode
Code:
[COLOR="blue"]adb shell reboot bootloader[/COLOR]
12. Boot temporal root
Code:
[COLOR="blue"]fastboot boot boot-CN-adb-root.img[/COLOR]
Output (or similar)
Code:
downloading 'boot.img'...
OKAY [ 0.349s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 1.206s
13. Copy stock recovery files to the watch
Code:
[COLOR="blue"]adb push install_recovery.sh /data/media/0/
adb push recovery.img /data/media/0/[/COLOR]
Output (or similar)
Code:
[100%] /data/media/0/install_recovery.sh
[100%] /data/media/0/recovery.img
14. Run the recovery installation script
Code:
[COLOR="blue"]adb shell cd /data/media/0/; sh install_recovery.sh[/COLOR]
Or if above command doesn't work, do it in 2 commands
Code:
[COLOR="blue"]adb shell cd /data/media/0/
adb shell sh install_recovery.sh[/COLOR]
Output (or similar)
Code:
============= STOCK Installer ===============
Flashing recovery...
4096+0 records in
4096+0 records out
16777216 bytes (16.0MB) copied, 2.461221 seconds, 6.5MB/s
Done. OTA updates should now work.
15 . Delete stock recovery installation files
Code:
[COLOR="blue"]adb shell rm /data/media/0/install_recovery.sh
adb shell rm /data/media/0/recovery.img [/COLOR]
16. Reboot the watch
Code:
[COLOR="blue"]adb reboot[/COLOR]
17. Finish.
Go to Amazfit app and update to latest version.
Some extra useful commands
Wipe dalvik/cache
Code:
[COLOR="blue"]adb shell reboot bootloader
fastboot erase cache
fastboot reboot[/COLOR]
Do a Factory Reset (You will lose all the data in your watch. Unpair the watch from Amazfit app while doing this?
Code:
[COLOR="Blue"]adb shell reboot bootloader
fastboot erase data
fastboot erase cache
fastboot reboot[/COLOR]
Reserved 1
Reserved 1
I tried flashing back from 3.2.0.5 back.
First error at Step 4 when the recovery-mod.img is flashed to boot and the booting failed.
****************************
4. Booting modded recovery
****************************
< waiting for any device >
Downloading 'boot.img' FAILED (status read failed (Too many links))
Finished. Total time: 1.082s
***********************************
5. Waiting connection in Recovery
***********************************
So I have to do manually:
\Verge_Stock_CN_3.0.12.0_Firmware_Installer>fastboot boot recovery-mod.img
Downloading 'boot.img' OKAY [ 0.464s]
booting FAILED (status read failed (Too many links))
Finished. Total time: 1.545s
2nd error is during the flash prompt, ADB exited shell before system flash is completed:
Step 7 no flash system complete message
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell sh /data/media/0/flash_rom.sh
Validating images
boot.img: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 0.952945 seconds, 9.4MB/s
Flashing system.img
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>
Took me a while to re-connect to shell and reissue the flash command.
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell sh /data/media/0/flash_rom.sh
error: device still connecting
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell
error: device still connecting
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell
error: device still connecting
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell
error: device still connecting
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb reconnect
reconnecting c5121c27 [connecting]
Finally able to reconnect to shell
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell
# ls
cache
charger
data
default.prop
dev
etc
file_contexts
flash
fstab.watch
init
init.rc
init.recovery.watch.rc
mnt
proc
res
root
sbin
sdcard
sepolicy
sideload
sys
system
tmp
ueventd.rc
ueventd.watch.rc
# ls data/media/0
Alarms
DCIM
Download
Movies
Music
Notifications
Pictures
Podcasts
Ringtones
WatchFace
boot.img
flash_rom.sh
gpxdata
md5s.txt
system.img.gz
# sh /data/media/0/flash_rom.sh
Validating images
boot.img: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 0.950465 seconds, 9.5MB/s
Flashing system.img
210944+0 records in
210944+0 records out
864026624 bytes (824.0MB) copied, 101.986899 seconds, 8.1MB/s
Finished
After rebooting I am able to receive 3.0.13.0 OTA and install.
apollow2007 said:
I tried flashing back from 3.2.0.5 back.
First error at Step 4 when the recovery-mod.img is flashed to boot and the booting failed.
****************************
4. Booting modded recovery
****************************
< waiting for any device >
Downloading 'boot.img' FAILED (status read failed (Too many links))
Finished. Total time: 1.082s
***********************************
5. Waiting connection in Recovery
***********************************
So I have to do manually:
\Verge_Stock_CN_3.0.12.0_Firmware_Installer>fastboot boot recovery-mod.img
Downloading 'boot.img' OKAY [ 0.464s]
booting FAILED (status read failed (Too many links))
Finished. Total time: 1.545s
2nd error is during the flash prompt, ADB exited shell before system flash is completed:
Step 7 no flash system complete message
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell sh /data/media/0/flash_rom.sh
Validating images
boot.img: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 0.952945 seconds, 9.4MB/s
Flashing system.img
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>
Took me a while to re-connect to shell and reissue the flash command.
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell sh /data/media/0/flash_rom.sh
error: device still connecting
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell
error: device still connecting
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell
error: device still connecting
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell
error: device still connecting
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb reconnect
reconnecting c5121c27 [connecting]
Finally able to reconnect to shell
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell
# ls
cache
charger
data
default.prop
dev
etc
file_contexts
flash
fstab.watch
init
init.rc
init.recovery.watch.rc
mnt
proc
res
root
sbin
sdcard
sepolicy
sideload
sys
system
tmp
ueventd.rc
ueventd.watch.rc
# ls data/media/0
Alarms
DCIM
Download
Movies
Music
Notifications
Pictures
Podcasts
Ringtones
WatchFace
boot.img
flash_rom.sh
gpxdata
md5s.txt
system.img.gz
# sh /data/media/0/flash_rom.sh
Validating images
boot.img: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 0.950465 seconds, 9.5MB/s
Flashing system.img
210944+0 records in
210944+0 records out
864026624 bytes (824.0MB) copied, 101.986899 seconds, 8.1MB/s
Finished
After rebooting I am able to receive 3.0.13.0 OTA and install.
Click to expand...
Click to collapse
Glad you were able to install and update.
May I ask for your Windows version and previous ROM version on watch?
Saratoga79 said:
Glad you were able to install and update.
May I ask for your Windows version and previous ROM version on watch?
Click to expand...
Click to collapse
Windows 10 Pro.
Previous ROM was 3.2.0.5 which was converted from 3.0.13.0.
Stock 3.0.14.0 firmware if you want it.
Great work Saratoga79.
My Verge prompted me for an update this morning, I have stock 3.0.14.0 (zh but set to en) on it if you want a copy.
Hi.
Possible to update the ROM image here to 3.0.29.0?
Flashing back from US to CN rom will have to start update from 3.0.14 all the way to 3.0.29.0
apollow2007 said:
Hi.
Possible to update the ROM image here to 3.0.29.0?
Flashing back from US to CN rom will have to start update from 3.0.14 all the way to 3.0.29.0
Click to expand...
Click to collapse
OP updated with 3.0.29.0 Firmware Installer.
Ayuda!
I have the 1801 version of China. With room 3.0.28 of saratoga, but I constantly get request to update to official 3.0.29. So how do I give an update and do not miss the Spanish language?
Sliv33 said:
I have the 1801 version of China. With room 3.0.28 of saratoga, but I constantly get request to update to official 3.0.29. So how do I give an update and do not miss the Spanish language?
Click to expand...
Click to collapse
My ROM is since a week ago based on 3.0.29.0.
Hello people , I have verge that keeps freezing when receiving several notifications and has sever battery drain. I have factory reset and re-installed the English firmware . But doesn't seem to help.
Will installing the latest Chinese firmware help.
Than I can install the last english os .
Could this help
cetuss4 said:
Hello people , I have verge that keeps freezing when receiving several notifications and has sever battery drain. I have factory reset and re-installed the English firmware . But doesn't seem to help.
Will installing the latest Chinese firmware help.
Than I can install the last english os .
Could this help
Click to expand...
Click to collapse
Not sure but you can give it a try.
For this Version
Can change language Chinese >> English without error
Have anybody any news/information when will be official update from Amazfit for Verge (International version) with integrated Alexa or other voice assistant for the rest of the world costumers like: Europe countries and ect?
Can i use NFC function on A1811 with Chinese stock rom?
I heard there are NFC chipsets in A1811 too
Flashing chinese bootloader on A1811 bricks my watch??
vsc0705 said:
Can i use NFC function on A1811 with Chinese stock rom?
I heard there are NFC chipsets in A1811 too
Click to expand...
Click to collapse
No, you can't, AFAIK, but you can give it a shot. I think there is no NFC, since NFC can't be enabled on CN Firmware. There is a dedicated switch for that in the firmware, but it's reported that NFC doesn't turn on for A1811. for A1801 it does.
vsc0705 said:
Flashing chinese bootloader on A1811 bricks my watch??
Click to expand...
Click to collapse
No, it doesn't.
Saratoga79 said:
I think there is no NFC, since NFC can't be enabled on CN Firmware. There is a dedicated switch for that in the firmware, but it's reported that NFC doesn't turn on for A1811. for A1801 it does..
Click to expand...
Click to collapse
NFC is in Verge http://cn.amazfit.com/verge.html before you post asnwer, check information in official web site - it's easy and no need a lot of time :highfive:
As i know NFC will be available later (if talk about US market), why is not activated in China's version i don't know. As i understand NFC is available only for payment process, so everthing maybe working somehow automatic. I can't explain reasons, but as i mentioned web site and others official source saying that NFC is in Verge (Chinese software) and will be later in International (i guest they mean US market only for this moment)
P.S. This is official Amazfit Verge commercial https://www.youtube.com/watch?v=PydD99xx2dk, look what doing guy in commercial from 34 second, he doing payment. Payment process is doing with NFC, what is meantioned in Amazfit web site So yes chinese version must have NFC available, why is not, need to ask Amazfit, but i guest, cos costumers which flashing Chinese ROM is not from China and maybe somehow by GOS is detecting that is not China country and features is not available. It's nonensese probably you will say, but when please explain me why the same software version for International costumers with Alexa working only in US, i got this software with Alexa, but i can't use Alexa, cos i'm not from US, if say exactly i'm not right now in US... I guest in the say working NFC. But maybe i'm wrong
About A1811 i guest you are right, i did not tried, but probably as i mentioned will not works, cos somehow *probably by GPS) this watch is really smart and detecting what you are not in the same market in which these features working If i understand you wrong, sorry, english is no my primary - national language
xdauser2019 said:
NFC is in Verge http://cn.amazfit.com/verge.html before you post asnwer, check information in official web site - it's easy and no need a lot of time :highfive:
As i know NFC will be available later (if talk about US market), why is not activated in China's version i don't know. As i understand NFC is available only for payment process, so everthing maybe working somehow automatic. I can't explain reasons, but as i mentioned web site and others official source saying that NFC is in Verge (Chinese software) and will be later in International (i guest they mean US market only for this moment)
P.S. This is official Amazfit Verge commercial https://www.youtube.com/watch?v=PydD99xx2dk, look what doing guy in commercial from 34 second, he doing payment. Payment process is doing with NFC, what is meantioned in Amazfit web site So yes chinese version must have NFC available, why is not, need to ask Amazfit, but i guest, cos costumers which flashing Chinese ROM is not from China and maybe somehow by GOS is detecting that is not China country and features is not available. It's nonensese probably you will say, but when please explain me why the same software version for International costumers with Alexa working only in US, i got this software with Alexa, but i can't use Alexa, cos i'm not from US, if say exactly i'm not right now in US... I guest in the say working NFC. But maybe i'm wrong
About A1811 i guest you are right, i did not tried, but probably as i mentioned will not works, cos somehow *probably by GPS) this watch is really smart and detecting what you are not in the same market in which these features working If i understand you wrong, sorry, english is no my primary - national language
Click to expand...
Click to collapse
Yes, I know A1801/CN version has NFC, I managed to enable it and I have done some test with 3th party apps but is not usable out of China.
I meant that A1811/International version has no NFC or lacks "something" as flashing Chinese firmware on it NFC doesn't work.
Saratoga79 said:
Yes, I know A1801/CN version has NFC, I managed to enable it and I have done some test with 3th party apps but is not usable out of China.
I meant that A1811/International version has no NFC or lacks "something" as flashing Chinese firmware on it NFC doesn't work.
Click to expand...
Click to collapse
As i know NFC is not just activated yet, if i understand right, coz now is negotiations are under way with markets (probably with companies, where will work services with NFC or something like is, i don't no details), soon must be everything available. But how i mentioned before, probably will works only in US market (like is with Alexa now). Oh well we will see... i hope update will be very soon and maybe with all ours answers
P.S. NFC is microchip which update will not add to watch, so yes NFC is already in yours device, it's just not activated, there is no option to do that yet Keep patience future will show all features... and keep in mind Verge international version is very new, so what you can see in Chinese version, i 'm sure, i hope will be in international version too, just keep waiting patience
Why not working with Chinese software in international version device (A1811 is for all world, except Asia region, as i understand)? I already write my minds, how they are correct i don't know, but idea that not working for reason, coz watch detect somehow (probably by GPS) that you are not in China for me sounds most probable. Why? You got 3.2.20 software update? What was written in it? Alexa that's right? Where is she? Cos working only in US? Are you in US? No, so probably that's reason why is no available for you NFC with Chinese software... But this is just my mind, maybe i wrote totall nonsenses, but i can't to image another reason why with the same software in one market working Alexa in other no, why can't to be the same with NFC and the same software for different market?
By the way are you sure that in Stock CN/Chinese 3.0.29.0 version already was available/activated NFC for China market too? This is second idea which came to head. I really really don't know how Amazfit made software, i mean how it working, so sorry if i wrote something insane, just lound thinking and trying to understand reason
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
THIS WILL NOT WORK ON AMAZFIT PACE, VERGE OR STRATOS
THIS WILL NOT WORK ON AMAZFIT PACE, VERGE OR STRATOS
THIS WILL NOT WORK ON AMAZFIT PACE, VERGE OR STRATOS
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please make sure you read and understand everything written in the post before flashing it! YOU are choosing to make these modifications and must be sure of what it does.
Click to expand...
Click to collapse
Only for unlocked Bootloader
Supported devices: A1928 (Chinese) and A1929 (English)
Property installed ADB and Fastboot drivers as system wide
Watch battery +40% (50% recommended)
Click to expand...
Click to collapse
For anyone interested on installing Stock/Original English Firmware
Click to expand...
Click to collapse
Multi lingual support
OTA updates
Click to expand...
Click to collapse
@Neur_User for STRATOSfied Rom and other stuff
@Cracklydisc for original script and other stuff
@1immortal for his support
@Jaz, contributors and collaborators in Telegram group.
Click to expand...
Click to collapse
1. Connect the watch to your PC
2. Unzip the the folder
3. Run flash_US.bat file for English interface (Don't do it as Administrator since is known to cause issues).
4. Wait to the end of the process and don't touch anything.
Installation output
*************************************************************
Stratos 3 US 4.2.3.0 Stock Firmware Installer by Saratoga
*************************************************************
0. Restarting adb server
***************************
**********************************
1. Connect the watch to the PC
**********************************
**********************************
2. Rebooting to Fastboot mode
**********************************
******************************
3. Checking the connection
******************************
*******************************
4. Booting modded recovery
*******************************
< waiting for any device >
Downloading 'boot.img' OKAY [ 0.450s]
booting FAILED (status read failed (Too many links))
Finished. Total time: 1.678s
***************************************
5. Waiting for connection in Recovery
***************************************
******************
6. Copying files
******************
boot.img: 1 file pushed. 7.1 MB/s (9437184 bytes in 1.264s)
system.img.gz: 1 file pushed. 5.0 MB/s (438606404 bytes in 84.087s)
md5s.txt: 1 file pushed. 0.0 MB/s (91 bytes in 0.003s)
flash_rom.sh: 1 file pushed. 0.1 MB/s (458 bytes in 0.006s)
**************************
7. Firmware installation
**************************
Validating images
boot.img: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 1.836843 seconds, 4.9MB/s
Flashing system.img
287744+0 records in
287744+0 records out
1178599424 bytes (1.1GB) copied, 156.970842 seconds, 7.2MB/s
Finished
*******************
8. Removing files
*******************
**************
9. Rebooting
**************
**********************************
10. Changing language to English
**********************************
****************************************************
Stock Recovery and Bootloader installation process
****************************************************
********************************
11. Rebooting to Fastboot mode
********************************
****************************
12. Booting temporal root
****************************
< waiting for any device >
Downloading 'boot.img' OKAY [ 0.368s]
booting FAILED (status read failed (Too many links))
Finished. Total time: 1.572s
*******************
13. Copying files
*******************
install_recovery.sh: 1 file pushed. 0.1 MB/s (687 bytes in 0.009s)
recovery.img: 1 file pushed. 1.6 MB/s (16777216 bytes in 10.082s)
u-boot-with-spl-mbr-gpt.bin: 1 file pushed. 2.2 MB/s (894764 bytes in 0.387s)
*****************************
14. Flashing Stock recovery
*****************************
============= STOCK Installer ===============
Flashing recovery...
4096+0 records in
4096+0 records out
16777216 bytes (16.0MB) copied, 1.908566 seconds, 8.4MB/s
Done. OTA updates should now work.
*************************
15. Flashing Bootloader
*************************
1747+1 records in
1747+1 records out
894764 bytes (873.8KB) copied, 0.695597 seconds, 1.2MB/s
*******************
16. Removing files
*******************
***************
17. Rebooting
***************
************
18. Finish
************
Presione una tecla para continuar . . .
Click to expand...
Click to collapse
VERY IMPORTANT:
Don't do a factory reset in fastboot or you will brick the watch. Just run FCT_RST_STOCK.bat or use these commands instead.
Method 1:
Code:
adb reboot wipe
Method 2 (Only if watch is fully booted and you are rooted):
Code:
adb shell am broadcast -a android.intent.action.MASTER_CLEAR
Click to expand...
Click to collapse
Latest Version
Stock US/International/Global 4.2.8.0 Firmware Installer with OTA updates | OTA 4.2.7.0 -> 4.2.8.0 Installer | More info
Previous Versions
Stock US/International/Global 4.2.7.0 Firmware Installer with OTA updates | OTA 4.2.6.0 -> 4.2.7.0 Installer | More info
Stock US/International/Global 4.2.6.0 Firmware Installer with OTA updates | OTA 4.2.5.0 -> 4.2.6.0 Installer | More info
Stock US/International/Global 4.2.5.0 Firmware Installer with OTA updates | OTA 4.2.4.0-> 4.2.5.0 Installer | More info
Stock US/International/Global 4.2.4.0 Firmware Installer with OTA updates | OTA 4.2.3.0-> 4.2.4.0 Installer | More info
Stock US/International/Global 4.2.3.0 Firmware Installer with OTA updates | OTA 4.2.2.1 -> 4.2.3.0 Installer | More info
Stock US/International/Global 4.2.2.1 Firmware Installer with OTA updates
OTA 4.2.0.1 -> 4.2.6.0 Installer | More info
Click to expand...
Click to collapse
If you like my work you can buy me a beer here
Click to expand...
Click to collapse
Manual installation method
Manual installation method
Introduction
Here I will explain how to install the firmware using a command window or any other terminal.
The requirements are the ones stated in first post.
On your terminal, go to the path where all the files were unzipped, or if you are running a Windows OS, just run terminal_cmd.bat and you are good to go.
OTA Installation
Download OTA installer from Post #1 and if you are running a Windows PC, run terminal_cmd.bat, or any other command/terminal window on your PC in the root of the unzipped folder.
Copy the update to the watch
Code:
[COLOR="Blue"]adb push update.zip /sdcard
[/COLOR]
And launch the update
Code:
[COLOR="blue"]adb reboot update[/COLOR]
Wait to the end of the update, and when the watch reboots delete the update file
Code:
[COLOR="blue"]adb shell rm /sdcard/update.zip[/COLOR]
Firmware installation
On your terminal, go to the path where all the Firmware files were unzipped.
You can copy and paste all needed commands.
1. Connect the watch to the PC and check the connection with the watch
Code:
[COLOR="Blue"]adb devices[/COLOR]
Output (or similar)
Code:
List of devices attached
9dee1d33 device
2. Reboot in fastboot mode
Code:
[COLOR="blue"]adb shell reboot bootloader[/COLOR]
3. When the watch reboots in fastboot mode, check the connection with the watch
Code:
[COLOR="blue"]fastboot devices[/COLOR]
Output (or similar)
Code:
0123456789 fastboot
4. Boot the modded recovery
Code:
[COLOR="blue"]fastboot boot recovery_mod.img[/COLOR]
Output (or similar)
Code:
Downloading 'boot.img' OKAY [ 0.450s]
booting FAILED (status read failed (Too many links))
Finished. Total time: 1.678s
5. Wait until you get a triangle with an exclamation mark in your watch
6. Copy the files to the watch (it may take up to a minute)
Code:
[COLOR="blue"]adb push boot.img /data/media/0/
adb push system.img.gz /data/media/0/
adb push md5s.txt /data/media/0/
adb push flash_rom.sh /data/media/0/[/COLOR]
Output (or similar)
Code:
boot.img: 1 file pushed. 7.1 MB/s (9437184 bytes in 1.264s)
system.img.gz: 1 file pushed. 5.0 MB/s (438606404 bytes in 84.087s)
md5s.txt: 1 file pushed. 0.0 MB/s (91 bytes in 0.003s)
flash_rom.sh: 1 file pushed. 0.1 MB/s (458 bytes in 0.006s)
7. Start Firmware installation (it may take up to 4 minutes)
Code:
[COLOR="blue"]adb shell sh /data/media/0/flash_rom.sh[/COLOR]
Output (or similar)
Code:
Validating images
boot.img: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 1.836843 seconds, 4.9MB/s
Flashing system.img
287744+0 records in
287744+0 records out
1178599424 bytes (1.1GB) copied, 156.970842 seconds, 7.2MB/s
Finished
8. We have already installed the firmware, now delete installation files form the watch
Code:
[COLOR="blue"]adb shell rm /data/media/0/boot.img
adb shell rm /data/media/0/system.img.gz
adb shell rm /data/media/0/md5s.txt
adb shell rm /data/media/0/flash_rom.sh[/COLOR]
9. Reboot the watch
Code:
[COLOR="blue"]adb reboot[/COLOR]
10. When the splash screen is passed and the bootanimation starts, set your watch to English language
Code:
[COLOR="blue"]adb shell setprop persist.sys.language en
adb shell setprop persist.sys.country US[/COLOR]
Stock Recovery and Bootloader installation process
11. Reboot in fastboot mode
Code:
[COLOR="blue"]adb shell reboot bootloader[/COLOR]
12. Boot temporal root
Code:
[COLOR="blue"]fastboot boot boot-US-adb-root.img[/COLOR]
Output (or similar)
Code:
Downloading 'boot.img' OKAY [ 0.368s]
booting FAILED (status read failed (Too many links))
Finished. Total time: 1.572s
13. Copy stock Recovery and Bootloader files to the watch
Code:
[COLOR="blue"]adb push install_recovery.sh /data/media/0/
adb push recovery.img /data/media/0/
adb push u-boot-with-spl-mbr-gpt.bin /data/media/0/[/COLOR]
Output (or similar)
Code:
install_recovery.sh: 1 file pushed. 0.1 MB/s (687 bytes in 0.009s)
recovery.img: 1 file pushed. 1.6 MB/s (16777216 bytes in 10.082s)
u-boot-with-spl-mbr-gpt.bin: 1 file pushed. 2.2 MB/s (894764 bytes in 0.387s)
14. Run the recovery installation script
Code:
[COLOR="blue"]adb shell cd /data/media/0/; sh install_recovery.sh[/COLOR]
Output (or similar)
Code:
============= STOCK Installer ===============
Flashing recovery...
4096+0 records in
4096+0 records out
16777216 bytes (16.0MB) copied, 1.908566 seconds, 8.4MB/s
Done. OTA updates should now work.
15. Flash Bootloader
Code:
[COLOR="blue"]adb shell busybox dd if=/data/media/0/u-boot-with-spl-mbr-gpt.bin of=/dev/block/mmcblk0[/COLOR]
Output (or similar)
Code:
1747+1 records in
1747+1 records out
894764 bytes (873.8KB) copied, 0.695597 seconds, 1.2MB/s
16 . Delete stock recovery and Bootloader installation files
Code:
[COLOR="blue"]adb shell rm /data/media/0/install_recovery.sh
adb shell rm /data/media/0/recovery.img
adb shell rm /data/media/0/u-boot-with-spl-mbr-gpt.bin
[/COLOR]
17. Reboot the watch
Code:
[COLOR="blue"]adb reboot[/COLOR]
18. Finish.
Go to Amazfit app and update to latest version.
Ultra Mode Resources
Since this firmware installer, I'm adding a new script to manage Ultra Mode resources.
If rebooting into Ultra mode doesn't work or you just get a black screen, run mcu_US.bat when you are in Smart Mode to fix it. This will update all needed files relating to Ultra Mode.
Manual commands
Open a command terminal window in the root of the installer folder and use:
Code:
[COLOR="Blue"]adb push mcu\. /sdcard/firmware
adb shell mcu_res_upgrade -r /sdcard/firmware -z /sdcard/firmware
adb shell check_mcu_res_upgrade.sh
adb shell rm -r /sdcard/firmware
adb reboot[/COLOR]
Some extra useful commands
Factory Reset
VERY IMPORTANT:
Don't do a factory reset in fastboot or you will brick the watch
You can factory reset your watch by:
Code:
[COLOR="Blue"]adb reboot wipe[/COLOR]
When it's done, the watch will turn off.
Launch pairing QR code
You can use:
Code:
[COLOR="Blue"]adb shell am start -n com.huami.watch.setupwizard/.InitPairQRActivity[/COLOR]
Reboot into Ultra mode
You can reboot into Ultra mode by:
Code:
[COLOR="blue"]adb reboot mcu[/COLOR]
Mio1
Mio1
Thank YOu! YOu are Amazfit lord and our savior
Can YOu make firmware with system zip?
arnisv said:
Can YOu make firmware with system zip?
Click to expand...
Click to collapse
What do you exactly mean?
Stock US/Global/International 4.2.3.0 Firmware Installer with OTA updates
Stock US/Global/International 4.2.3.0 Firmware Installer with OTA updates
Firmware Downloads
Stock US/Global/International 4.2.3.0 Firmware Installer with OTA updates
OTA 4.2.2.1 -> 4.2.3.0 Installer
This installer is for those who are on 4.2.2.1 and didn't get 4.2.3.0 OTA and want to update. Only adb/fastboot drivers are needed, unlocked bootloader is not needed as this is an official update.
Unzip the .zip file and run INSTALL_OTA_US.bat.
OTA Downloads
OTA 4.2.2.1 -> 4.2.3.0 Installer
Changelog
Check attachment.
Hi
Thanks Saratoga I updated 4.2.3.0 only OTA unfortunately wifi in watch still not working :crying:, do you know reason what could be wrong?
Stock US/Global/International 4.2.4.0 Firmware Installer with OTA updates
Stock US/Global/International 4.2.4.0 Firmware Installer with OTA updates
Firmware Downloads
Stock US/Global/International 4.2.4.0 Firmware Installer with OTA updates
OTA 4.2.3.0 -> 4.2.4.0 Installer
This installer is for those who are on 4.2.3.0 and didn't get 4.2.4.0 OTA and want to update. Only adb/fastboot drivers are needed, unlocked bootloader is not needed as this is an official update.
Unzip the .zip file and run INSTALL_OTA_US.bat.
OTA Downloads
OTA 4.2.3.0 -> 4.2.4.0 Installer
Ultra Mode Resources
Since this firmware installer, I'm adding a new script to manage Ultra Mode resources.
If rebooting into Ultra mode doesn't work or you just get a black screen, run mcu_US.bat when you are in Smart Mode to fix it. This will update all needed files relating to Ultra Mode.
Manual commands
Open a command terminal window in the root of the installer folder and use:
Code:
[COLOR="Blue"]adb push mcu\. /sdcard/firmware
adb shell mcu_res_upgrade -r /sdcard/firmware -z /sdcard/firmware
adb shell check_mcu_res_upgrade.sh
adb shell rm -r /sdcard/firmware
adb reboot[/COLOR]
Changelog
Check attachment.
Great post,
Question for Ultra mode. Can i fix ultra mode if i don't have unlocked bootloader? I gor update on regular way, but ultra mode is not working.
maksic.jovan said:
Great post,
Question for Ultra mode. Can i fix ultra mode if i don't have unlocked bootloader? I got update on regular way, but ultra mode is not working.
Click to expand...
Click to collapse
Yes, you can. Just use the commands from the post above or the .bat installer for Ultra Mode resources, and see if that helps.
Sorry Saratoga, I'm lost. Which firmware is newer?
CN 4.0.4.15 or US 4.2.4.0?
Because by the number I think it must be the US, but it's strange that a Chinese product has US firmware newer than the CN one's ?
Mormy said:
Sorry Saratoga, I'm lost. Which firmware is newer?
CN 4.0.4.15 or US 4.2.4.0?
Because by the number I think it must be the US, but it's strange that a Chinese product has US firmware newer than the CN one's
Click to expand...
Click to collapse
CN 4.0.14.5 is from January 17th, US 4.2.4.0 is older.
Hello, I bought in China a stratos 3 and was surprised to find that, unlike what i saw on official webbsites, only chinese language was available. I am then looking for a way to install the international version. It seems this thread can allow me to do it.
I have a question however, what is an unlocked bootloader ?
Thanks in advance.
Thanks
hi
i have problem with ultra mode. I run script but still nothing i got output:
******************************************************************
Stratos 3 US 4.2.4.0 Ultra Mode Resources Installer by Saratoga
******************************************************************
0. Restarting adb server
**************************
********************************
1. Connect the watch to the PC
********************************
******************
2. Copying files
******************
mcu\.\: 3 files pushed. 3.3 MB/s (5697818 bytes in 1.633s)
**********************************
3. Updating Ultra Mode resources
**********************************
res_path=/sdcard/firmware,ziku_path=/sdcard/firmware
res:read byte from file fail,only -1 length
ziku:read byte from file fail,only -1 length
newResVer=0,newZikuVer=0,oldResVer=127,oldZikuVer=17
try to upgrade res
...
...
what i am doing wrong? :/
maksic.jovan said:
hi
i have problem with ultra mode. I run script but still nothing i got output:
******************************************************************
Stratos 3 US 4.2.4.0 Ultra Mode Resources Installer by Saratoga
******************************************************************
0. Restarting adb server
**************************
********************************
1. Connect the watch to the PC
********************************
******************
2. Copying files
******************
mcu\.\: 3 files pushed. 3.3 MB/s (5697818 bytes in 1.633s)
**********************************
3. Updating Ultra Mode resources
**********************************
res_path=/sdcard/firmware,ziku_path=/sdcard/firmware
res:read byte from file fail,only -1 length
ziku:read byte from file fail,only -1 length
newResVer=0,newZikuVer=0,oldResVer=127,oldZikuVer=17
try to upgrade res
...
...
what i am doing wrong? :/
Click to expand...
Click to collapse
And what else after "try to upgrade res"?
That output is normal, don't worry about those fails messages.
If you still have issues, try using another stock watchface in Smart mode and before you reboot into Ultra mode, ensure watch and Amazfit app are correctly connected because I've faced strange Ultra mode behaviour if watch was not connected to the app. Also disable all widgets in Amazfit app before rebooting into Ultra.
My output when installing Ultra mode resources in my CN ROM:
Code:
******************************************************************
Stratos 3 US 4.2.4.0 Ultra Mode Resources Installer by Saratoga
******************************************************************
0. Restarting adb server
**************************
********************************
1. Connect the watch to the PC
********************************
******************
2. Copying files
******************
mcu\.\: 3 files pushed. 2.5 MB/s (5697818 bytes in 2.195s)
**********************************
3. Updating Ultra Mode resources
**********************************
res_path=/sdcard/firmware,ziku_path=/sdcard/firmware
res:read byte from file fail,only -1 length
ziku:read byte from file fail,only -1 length
newResVer=0,newZikuVer=0,oldResVer=129,oldZikuVer=17
try to upgrade res
upgrade res successfully
try to upgrade ziku
upgrade ziku successfully
*********************************
4. Checking Ultra Mode resources
*********************************
/etc/firmware/ui_res.bin /etc/firmware/ziku_res.bin /etc/firmware/mcu_res.desc
verify upgrade file successful
res_path=/etc/firmware/ui_res.bin,ziku_path=/etc/firmware/ziku_res.bin
newResVer=129,newZikuVer=17,oldResVer=127,oldZikuVer=17
try to upgrade res
upgrade res successfully
********************
5. Removing files
********************
***************
6. Rebooting
***************
************
7. Finish
************
Presione una tecla para continuar . . .
Saratoga79 said:
And what else after "try to upgrade res"?
That output is normal, don't worry about those fails messages.
If you still have issues, try using another stock watchface in Smart mode and before you reboot into Ultra mode, ensure watch and Amazfit app are correctly connected because I've faced strange Ultra mode behaviour if watch was not connected to the app. Also disable all widgets in Amazfit app before rebooting into Ultra.
Click to expand...
Click to collapse
complete output:
Code:
******************************************************************
Stratos 3 US 4.2.4.0 Ultra Mode Resources Installer by Saratoga
******************************************************************
0. Restarting adb server
**************************
********************************
1. Connect the watch to the PC
********************************
******************
2. Copying files
******************
cannot stat 'mcu\.': No such file or directory
**********************************
3. Updating Ultra Mode resources
**********************************
res_path=/sdcard/firmware,ziku_path=/sdcard/firmware
res:read byte from file fail,only -1 length
ziku:read byte from file fail,only -1 length
newResVer=0,newZikuVer=0,oldResVer=127,oldZikuVer=17
try to upgrade res
upgrade res successfully
try to upgrade ziku
upgrade ziku successfully
*********************************
4. Checking Ultra Mode resources
*********************************
/etc/firmware/ui_res.bin /etc/firmware/ziku_res.bin /etc/firmware/mcu_res.desc
verify upgrade file successful
res_path=/etc/firmware/ui_res.bin,ziku_path=/etc/firmware/ziku_res.bin
newResVer=127,newZikuVer=17,oldResVer=127,oldZikuVer=17
********************
5. Removing files
********************
***************
6. Rebooting
***************
************
7. Finish
************
Press any key to continue . . .
watch restart and nothing happens. I use default watch face, and it's connected to amazfit app. also i try to reinstall ROM (from option in watch itself). Nothing helps...
Also i get firmware update via Amazfit app, so absolutely everything is original and stock.
maksic.jovan said:
complete output:
Code:
******************************************************************
Stratos 3 US 4.2.4.0 Ultra Mode Resources Installer by Saratoga
******************************************************************
0. Restarting adb server
**************************
********************************
1. Connect the watch to the PC
********************************
******************
2. Copying files
******************
cannot stat 'mcu\.': No such file or directory
**********************************
3. Updating Ultra Mode resources
**********************************
res_path=/sdcard/firmware,ziku_path=/sdcard/firmware
res:read byte from file fail,only -1 length
ziku:read byte from file fail,only -1 length
newResVer=0,newZikuVer=0,oldResVer=127,oldZikuVer=17
try to upgrade res
upgrade res successfully
try to upgrade ziku
upgrade ziku successfully
*********************************
4. Checking Ultra Mode resources
*********************************
/etc/firmware/ui_res.bin /etc/firmware/ziku_res.bin /etc/firmware/mcu_res.desc
verify upgrade file successful
res_path=/etc/firmware/ui_res.bin,ziku_path=/etc/firmware/ziku_res.bin
newResVer=127,newZikuVer=17,oldResVer=127,oldZikuVer=17
********************
5. Removing files
********************
***************
6. Rebooting
***************
************
7. Finish
************
Press any key to continue . . .
watch restart and nothing happens. I use default watch face, and it's connected to amazfit app. also i try to reinstall ROM (from option in watch itself). Nothing helps...
Also i get firmware update via Amazfit app, so absolutely everything is original and stock.
Click to expand...
Click to collapse
What does it happen to you exactly? Blank screen in Ultra? Or what?
1. I would wait for a next OTA update as it will install/update Ultra resources during firmware update.
2. You could unlock the bootloader, warranty will be void, and install an older firmware version and check if after updating to latest version everything works fine.
3. Claim for warranty.
Saratoga79 said:
What does it happen to you exactly? Blank screen in Ultra? Or what?
1. I would wait for a next OTA update as it will install/update Ultra resources during firmware update.
2. You could unlock the bootloader, warranty will be void, and install an older firmware version and check if after updating to latest version everything works fine.
3. Claim for warranty.
Click to expand...
Click to collapse
Watch goes to Ultra mode, but screen does not turn on. I just notice that battery level is different in normal and ultra mode.
That is exactly what i plan to do. wait for update, and it that doesn't help - claim warranty.
Thanks For help.
Hello, when flash a stock rom the booloader is locked like factory watch?