Related
Having successfully semi-rooting my device through pauls root i was trying to install the SDE, i followed all steps correctly and ran the batch file but when rebooting into recovery mode no such menu appeared, i have confirmed root shell access so now i'm wondering if anyone else has had a problem? really would want to get the menu installed. It just seems not to work at all and i've ran the script from both my pc and from the internal device memory but this seems not to have worked, any ideas? Thanks
I followed all paul's instruction but I can't root my 101, I tried SDE script too but I can't see any differcence in recovery
Nadrian,
could you try this for me:
start a cmd.exe, and launch the script from this cmd window.
Do a copy/paste of the execution log and post it here please ?
(to copy paste from cmd, do Alt+space, select "edit", "mark", then select text with mouse, press enter then do a paste here)
Moskiller, you problem is different if you don't have the # prompt when doing Paul's root, could you show me the log of the adb session ?
@letama i'll pm you those tomorrow and thanks for the help!
letama said:
Nadrian,
could you try this for me:
start a cmd.exe, and launch the script from this cmd window.
Do a copy/paste of the execution log and post it here please ?
(to copy paste from cmd, do Alt+space, select "edit", "mark", then select text with mouse, press enter then do a paste here)
Moskiller, you problem is different if you don't have the # prompt when doing Paul's root, could you show me the log of the adb session ?
Click to expand...
Click to collapse
If u explain to me how do it, with pleasure
Sent from my ARCHOS 101G9 using Tapatalk
Moskiller said:
If u explain to me how do it, with pleasure
Click to expand...
Click to collapse
I need all the text in the cmd window with the adb commands and the results.
you can do the copy/paste the same way I explained to Nadrian.
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot
C:\Program Files (x86)\Android\android-sdk\platform-tools>enable_sde
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push zimage /data/
local/tmp
306 KB/s (2655004 bytes in 8.450s)
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push initrd.cpio.l
zma /data/local/tmp
314 KB/s (398045 bytes in 1.236s)
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push abcbox /data/
local/tmp
323 KB/s (277204 bytes in 0.838s)
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell chmod 755 /d
ata/local/tmp/abcbox
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell /data/local/
tmp/abcbox kd_flasher -k /data/local/tmp/zimage -i /data/local/tmp/initrd.cpio.l
zma
Generating KD...
Updating KD (3053305 bytes)...
0
100
It worked when i executed the script through command prompt, but here's the execution log anyway, thanks for the tool and for all help!
My log (Windows XP SP3):
C:\android-sdk-windows\platform-tools>enable_sde.bat
C:\android-sdk-windows\platform-tools>adb push zimage /data/local/tmp
1999 KB/s (2655004 bytes in 1.296s)
C:\android-sdk-windows\platform-tools>adb push initrd.cpio.lzma /data/local/tmp
1776 KB/s (398045 bytes in 0.218s)
C:\android-sdk-windows\platform-tools>adb push abcbox /data/local/tmp
1925 KB/s (277204 bytes in 0.140s)
C:\android-sdk-windows\platform-tools>adb shell chmod 755 /data/local/tmp/abcbox
C:\android-sdk-windows\platform-tools>adb shell /data/local/tmp/abcbox kd_flashe
r -k /data/local/tmp/zimage -i /data/local/tmp/initrd.cpio.lzma
Generating KD...
Updating KD (3053305 bytes)...
0
100
C:\android-sdk-windows\platform-tools>
Even for me, SDE doesn't work (archos 101 G9 8gb)
EDIT: WORKS!
at the fourth attempt it worked (ext4 firmware)! After removing the root and before reboot, the only thing I changed was disconnect the USB cable from tablet (???). ciao
hitman72 said:
at the fourth attempt it worked (ext4 firmware)! After removing the root and before reboot, the only thing I changed was disconnect the USB cable from tablet (???). ciao
Click to expand...
Click to collapse
Weird!
I guess a couple of md5sum could help pinpointing adb push or flash issue.
I'll add that someday.
Thanks for the report!
I accidentally formatted my phone before i installed the rom. Now i need to adp push the rom onto the phone. ADB says the following when i try.
C:\adb>adb -s emulator-5554 push dlx.zip /dlx.zip
failed to copy 'dlx.zip' to '/dlx.zip': Read-only file system
wack0jacko said:
I accidentally formatted my phone before i installed the rom. Now i need to adp push the rom onto the phone. ADB says the following when i try.
C:\adb>adb -s emulator-5554 push dlx.zip /dlx.zip
failed to copy 'dlx.zip' to '/dlx.zip': Read-only file system
Click to expand...
Click to collapse
I just got this:
C:\adb>adb push dlx.zip /sdcard/
1887 KB/s (914054797 bytes in 472.833s)
The file is 900mb. What am I doing wrong?
wack0jacko said:
I just got this:
C:\adb>adb push dlx.zip /sdcard/
1887 KB/s (914054797 bytes in 472.833s)
The file is 900mb. What am I doing wrong?
Click to expand...
Click to collapse
adb push <Rom directory> /sdcard/
Worked once, now no more. I had to re-flash using heimdall, successfully recovered but now can't re-root my phone. Originally had safestrap running like a charm and cant get back to it now.
adb shell confirmed, phone reboots but looks like saferoot is trying to remove temporary files when the phone is rebooting.... see below
Any thoughts? Suggestions?
Thanks - cpiercew
usermbp:saferoot user$ adb shell
[email protected]:/ $ exit
usermbp:saferoot user$ sh ./install.sh
--- Samsung i545 VRUEMJ7 Root ---
--- Based on the CVE-2013-6282 exploit by cubeundcube ---
Waiting for device...
Watch your phone. Unlock it and give permission for the install to run.
Sending files to your device...
2363 KB/s (17804 bytes in 0.007s)
3412 KB/s (104800 bytes in 0.029s)
2208 KB/s (13592 bytes in 0.006s)
3248 KB/s (2139595 bytes in 0.643s)
4732 KB/s (1109128 bytes in 0.228s)
293 KB/s (629 bytes in 0.002s)
Starting rooting program.
ro.build.product=jfltevzw
ro.build.id=JSS15J
selinux enforcing known.
Succeeded in getroot!
Remount success!
Copying files..
Removing temporary files...
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
Rebooting...Please wait.
error: device not found
Waiting for device to re-appear...
Unlock your phone, and when prompted, give SuperSU permission for
'ADB shell' to run.
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
Installing busybox
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
--- All Finished ---
usermbp:saferoot user$
cpiercew said:
Worked once, now no more. I had to re-flash using heimdall, successfully recovered but now can't re-root my phone. Originally had safestrap running like a charm and cant get back to it now.
adb shell confirmed, phone reboots but looks like saferoot is trying to remove temporary files when the phone is rebooting.... see below
Any thoughts? Suggestions?
Thanks - cpiercew
usermbp:saferoot user$ adb shell
[email protected]:/ $ exit
usermbp:saferoot user$ sh ./install.sh
--- Samsung i545 VRUEMJ7 Root ---
--- Based on the CVE-2013-6282 exploit by cubeundcube ---
Waiting for device...
Watch your phone. Unlock it and give permission for the install to run.
Sending files to your device...
2363 KB/s (17804 bytes in 0.007s)
3412 KB/s (104800 bytes in 0.029s)
2208 KB/s (13592 bytes in 0.006s)
3248 KB/s (2139595 bytes in 0.643s)
4732 KB/s (1109128 bytes in 0.228s)
293 KB/s (629 bytes in 0.002s)
Starting rooting program.
ro.build.product=jfltevzw
ro.build.id=JSS15J
selinux enforcing known.
Succeeded in getroot!
Remount success!
Copying files..
Removing temporary files...
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
Rebooting...Please wait.
error: device not found
Waiting for device to re-appear...
Unlock your phone, and when prompted, give SuperSU permission for
'ADB shell' to run.
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
Installing busybox
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
--- All Finished ---
usermbp:saferoot user$
Click to expand...
Click to collapse
I'm assuming the files copied to the tmp directory because of the adb output, but have you checked?
Edit: derp, you said adb shell confirmed.
From reading the install script your phones state shouldn't change before the device is first not recognized (it should still be on and responding to adb commands). So if you can successfully start an adb shell there is no reason the script shouldn't work. Maybe try running the commands manually?
gnubian said:
I'm assuming the files copied to the tmp directory because of the adb output, but have you checked? Also, what happens when you type "adb shell" ? Because from reading the install script your phones state shouldn't change before the device is first not recognized (it should still be on and responding to adb commands).
Click to expand...
Click to collapse
I included the adb shell output, I verified it could connect to the device first. Prior to installing ADB I first installed Kies and drivers, then put adb in my path to ensure it would run properly.
I haven't check the tmp directory, I will but not sure if this would matter as it seems something else is going on. I have a total of three errors that seem to be happening:
1) Removing temporary files
Removing temporary files...
error: device not found
2) When the phone reboots I unlock it immediately but dont get prompted to allow ADB shell to run
Rebooting...Please wait.
error: device not found
Waiting for device to re-appear...
Unlock your phone, and when prompted, give SuperSU permission for
'ADB shell' to run.
/system/bin/sh: /system/xbin/su: not found
3) Installing busybox seems to fail, "su" is not found
Installing busybox
/system/bin/sh: /system/xbin/su: not found
I also get the "all finished" prompt before the phone is finished booting up.
gnubian said:
I'm assuming the files copied to the tmp directory because of the adb output, but have you checked?
Edit: derp, you said adb shell confirmed.
From reading the install script your phones state shouldn't change before the device is first not recognized (it should still be on and responding to adb commands). So if you can successfully start an adb shell there is no reason the script shouldn't work. Maybe try running the commands manually?
Click to expand...
Click to collapse
Good idea, I didn't know that was an option, is there a list of commands I can find somewhere?
- just realized looking in install.sh shows the source. However, still noob'd and don't know how to translate some of the basic shell scripting
cpiercew said:
Good idea, I didn't know that was an option, is there a list of commands I can find somewhere?
Click to expand...
Click to collapse
Edit: i was assuming that was a linux error, not an error in adb shell. It seems the files did not properly copy. Did you check if they are in the tmp folder?
---------- Post added at 08:50 PM ---------- Previous post was at 08:46 PM ----------
[/COLOR]If you give me a minute I can post the commands without the unnecessary scripting that should allow for manual installation.
Edit: don't know why I assumed mac, thought I read it in your post. What are you running?
gnubian said:
I believe you need to install the package that has the su command (not sure about mac, I use linux). Just open the .sh file rather than run it and the commands are in there. Obviously just ignore the echos and such.
---------- Post added at 08:50 PM ---------- Previous post was at 08:46 PM ----------
If you give me a minute I can post the commands without the unnecessary scripting that should allow for manual installation. Google your errors about system/bin/sh and su to find the appropriate package you need for your mac distribution in the meantime.
Edit: don't know why I assumed mac, thought I read it in your post. What are you running?
Click to expand...
Click to collapse
Correct, using a mac
The following are the individual commands. Should let you know exactly when your problems are starting if you enter them manually. I believe the repeated system/xbin/su command is repeated incase the device isn't responding/rebooted yet. So you may only need to enter it once. Sorry the .sh worked for me so I didn't do it this way. Hopefully this sheds more light on your problem.
Remember to run these from the folder that contains the "file" folder.
adb wait-for-device
adb push files/getroot /data/local/tmp/
adb push files/su /data/local/tmp/
adb push files/selinuxoff /data/local/tmp/
adb push files/Superuser.apk /data/local/tmp/
adb push files/busybox /data/local/tmp/
adb push files/install-recovery.sh /data/local/tmp/
adb shell "chmod 0755 /data/local/tmp/getroot"
adb shell "chmod 0755 /data/local/tmp/busybox"
adb shell /data/local/tmp/getroot
adb shell "rm /data/local/tmp/getroot"
adb shell "rm /data/local/tmp/su"
adb shell "rm /data/local/tmp/selinuxoff"
adb shell "rm /data/local/tmp/Superuser.apk"
adb shell "rm /data/local/tmp/busybox"
adb shell "rm /data/local/tmp/install-recovery.sh"
adb reboot
adb wait-for-device
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb shell "/system/xbin/su -c mount -o remount,rw /system"
adb shell "/system/xbin/su -c chmod 6755 /system/xbin/su"
adb shell "/system/xbin/su -c chmod 6755 /system/xbin/daemonsu"
adb shell "/system/xbin/su -c /system/xbin/busybox --install -s /system/xbin"
adb wait-for-device
adb shell "/system/xbin/su -c mount -o remount,ro /system"
gnubian said:
adb wait-for-device
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
Click to expand...
Click to collapse
Please note that all of that is to give the user a chance to notice the SuperSU prompt asking them to give permissions for adb shell.
k1mu said:
Please note that all of that is to give the user a chance to notice the SuperSU prompt asking them to give permissions for adb shell.
Click to expand...
Click to collapse
Thanks for clearing that up. As I said I did not root by manually issuing the commands.
gnubian said:
Thanks for clearing that up. As I said I did not root by manually issuing the commands.
Click to expand...
Click to collapse
Ok, I resolved the issue after going with my hunch the stock verizon GS4 VRUEMK2 build from Surge1223 I had previously recovered from may have been the issue.
I went back into Kies backed up apps, settings and performed a firmware recovery to MK2. Once rebooted and reconfigured - it worked as designed.
For what it's worth, the build I would suggest avoiding if you want to use saferoot or root your phone at all is what I found from Surge1223 on androidforum: SCH-I545_VZW_1_20131212083410_mwx72ql56g_fac.zip
Not a dig on Surge1223, as with anything I use all downloads at my own risk.
Thanks again for the responses, any info I can provide from this that will help anyone else trying to use Saferoot please let me know.
cpiercew said:
Ok, I resolved the issue after going with my hunch the stock verizon GS4 VRUEMK2 build from Surge1223 I had previously recovered from may have been the issue.
I went back into Kies backed up apps, settings and performed a firmware recovery to MK2. Once rebooted and reconfigured - it worked as designed.
For what it's worth, the build I would suggest avoiding if you want to use saferoot or root your phone at all is what I found from Surge1223 on androidforum: SCH-I545_VZW_1_20131212083410_mwx72ql56g_fac.zip
Not a dig on Surge1223, as with anything I use all downloads at my own risk.
Thanks again for the responses, any info I can provide from this that will help anyone else trying to use Saferoot please let me know.
Click to expand...
Click to collapse
FWIW, I don't have an androidforums account. Also, my upload is fine, otherwise it wouldn't flash in Odin. Next time come tell me or comment in my thread about the issues your having with my upload.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
FWIW, I don't have an androidforums account. Also, my upload is fine, otherwise it wouldn't flash in Odin. Next time come tell me or comment in my thread about the issues your having with my upload.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sure - there could have been a few reasons it didn't work.
i am on macosx and installed android studio
the adb and fastboot and driver (kext) for android are broken in such the following ways
1. adb
it is not detecting even virtual machine , tried all the version
when i run ./adb usb or ./adb devices for the first time
it is not showing thing like
Dameon starting up bla bla
and run quietly and freezes
sudo ./adb devices
List of devices attached
*** it freezes i.e keep waiting
sudo ./adb usb
** it freezes and waiting
even
sudo ./adb kill-server
**8 it is freezing and waiting
sudo ./adb start-server
** it is waiting
i have given it all permission
chmod 777 adb
platform-tools Prodesign$ sudo ./adb start-server ** it is waiting
2. fastboot
./fastboot-mac devices
ERROR: could not get pipe properties
HQ65XBS32030 fastboot
fastboot oem get_identifier_token
ERROR: could not get pipe properties
... // i tired a htc android
not a single android in adb pr fastboot is working correctly
there is not adb_usb.ini file in sdk folder of adb also new adb does not uses adb_usb.ini file
also i added that file and device if like 0x1368 even though it is not working
Please help
{
"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 Chinese Firmware
Click to expand...
Click to collapse
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 CN 4.0.13.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 Chinese
**********************************
****************************************************
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 have root):
Code:
adb shell am broadcast -a android.intent.action.MASTER_CLEAR
Click to expand...
Click to collapse
Latest version
Stock CN/Chinese 4.0.22.0 Firmware Installer with OTA updates (Bugged Ultra Mode strings)
Click to expand...
Click to collapse
Previous versions
Stock CN/Chinese 4.0.19.5 Firmware Installer with OTA updates
Stock CN/Chinese 4.0.13.0 Firmware Installer with OTA updates
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 zh
adb shell setprop persist.sys.country CN[/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-CN-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.
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
Mio2
Thanks for your job !
Multi language (french) ?
Hi can you share multi language had which languages
Can someone confirm if Chinese Rom has English included by default?
Sent from my VOG-L29 using Tapatalk
tipu2185 said:
Can someone confirm if Chinese Rom has English included by default?
Sent from my VOG-L29 using Tapatalk
Click to expand...
Click to collapse
Only Chinese. However, you can change language to English using adb commands but you may face some bugs probably.
If you want official English language and others, check Stock/US/International thread for Stratos 3.
where can I find the update.zip?
thanks