Note: The Pace and Stratos should can use same recovery as well,I only have Stratos/Verge to test.The Verge(Launched only in China only) with AMOLED Display need to use separated Recovery.
For Stratos,Download EVEREST Image
For Verge,Download QOGIR Image
Source:
Pace: https://github.com/mauronofrio/android_device_huami_huanghe-twrp
Stratos:https://github.com/TingyiChen/android_device_huami_everest-twrp
Verge:https://github.com/TingyiChen/android_device_huami_qogir-twrp
Download:
Pace: https://androidfilehost.com/?fid=1322778262904021226
Stratos: https://www.androidfilehost.com/?w=files&flid=283426
Verge(AMOLED Variant): https://www.androidfilehost.com/?w=files&flid=283425
Known issue:
On Verge(qogir):
MTP Not working
Screen not responding sometimes
Screen is rotated
On Stratos(Everest):
Unknown
(NEED REPORT)(I doubt same as Verge)
On Pace:
I Dont know
Not having it
Should same as Stratos/Verge
Reserved
a little laggish on selection, and some weird electric jittering
will verify with PACE and post back, thanks !!!
1immortal said:
a little laggish on selection, and some weird electric jittering
Click to expand...
Click to collapse
I doubt it is caused by kernel?Cause Amazfit CPU is MIPS not normally ARM
TingyiChen said:
Note: The Pace and Stratos should can use same recovery as well,I only have Stratos/Verge to test.The Verge(Launched only in China only) with AMOLED Display need to use separated Recovery.
For Pace/Stratos,Download EVEREST Image
For Verge,Download QOGIR Image
Source:
Stratos:https://github.com/TingyiChen/android_device_huami_everest-twrp
Verge:https://github.com/TingyiChen/android_device_huami_qogir-twrp
Download
Pace/Stratos: https://www.androidfilehost.com/?w=files&flid=283426
Verge(AMOLED Variant): https://www.androidfilehost.com/?w=files&flid=283425
Click to expand...
Click to collapse
On Pace touchscreen doesn't work, but this one does using Pace's 2.6.3.1 zImage: https://mega.nz/#!hwIjFCiY!qc3sT2YD9uFCe86GPbX9VXL_LQRfHwwe1VfBtxCbrD0
Testing on Pace. Perhaps I am ding something wrong, but I still getting stock recovery.
My steps:
- adb shell reboot bootloader
- [email protected] ~/Downloads $ sudo fastboot flash recovery twrp-everest-3.2.3-20181006.img
target reported max download size of 67108864 bytes
sending 'recovery' (9680 KB)...
OKAY [ 0.650s]
writing 'recovery'...
OKAY [ 1.705s]
finished. total time: 2.355s
- fastboot reboot
- adb reboot recovery
Still getting "No commands" message from stock recovery.
At this PACE is WOS2.
TingyiChen said:
Note: The Pace and Stratos should can use same recovery as well,I only have Stratos/Verge to test.The Verge(Launched only in China only) with AMOLED Display need to use separated Recovery.
For Pace/Stratos,Download EVEREST Image
For Verge,Download QOGIR Image
Source:
Stratos:https://github.com/TingyiChen/android_device_huami_everest-twrp
Verge:https://github.com/TingyiChen/android_device_huami_qogir-twrp
Download
Pace/Stratos: https://www.androidfilehost.com/?w=files&flid=283426
Verge(AMOLED Variant): https://www.androidfilehost.com/?w=files&flid=283425
Click to expand...
Click to collapse
Paxy said:
Testing on Pace. Perhaps I am ding something wrong, but I still getting stock recovery.
My steps:
- adb shell reboot bootloader
- [email protected] ~/Downloads $ sudo fastboot flash recovery twrp-everest-3.2.3-20181006.img
target reported max download size of 67108864 bytes
sending 'recovery' (9680 KB)...
OKAY [ 0.650s]
writing 'recovery'...
OKAY [ 1.705s]
finished. total time: 2.355s
- fastboot reboot
- adb reboot recovery
Still getting "No commands" message from stock recovery.
At this PACE is WOS2.
Click to expand...
Click to collapse
Code:
fastboot boot recovery_name.img
Saratoga79 said:
Code:
fastboot boot recovery_name.img
Click to expand...
Click to collapse
Tnx. Yap, I can confirm that Pace boot recovery but touchscreen is not working.
Paxy said:
Tnx. Yap, I can confirm that Pace boot recovery but touchscreen is not working.
Click to expand...
Click to collapse
Use the one I attached in a previous post.
TingyiChen said:
Note: The Pace and Stratos should can use same recovery as well,I only have Stratos/Verge to test.The Verge(Launched only in China only) with AMOLED Display need to use separated Recovery.
For Pace/Stratos,Download EVEREST Image
For Verge,Download QOGIR Image
Source:
Stratos:https://github.com/TingyiChen/android_device_huami_everest-twrp
Verge:https://github.com/TingyiChen/android_device_huami_qogir-twrp
Download
Pace/Stratos: https://www.androidfilehost.com/?w=files&flid=283426
Verge(AMOLED Variant): https://www.androidfilehost.com/?w=files&flid=283425
Click to expand...
Click to collapse
You can't unify pace and stratos tree, they have different partitions sizes, i sent you a pull request to fix flip screen on verge
This one is for pace: https://www.androidfilehost.com/?fid=1322778262904021226
What is the gain from using TWRP on Stratos?
Enviado de meu SM-G950F usando o Tapatalk
@TingyiChen you are the best!
I had 2 wishes: a real stable custom rom with fast updates for my santoni and custom rom for my pace. You made both possible! Many thanks!
(also thanks for your help @Saratoga79)
Anyone who tried TWRP on his watch, just check your SN (Serial Number) on Settings>About or just using adb, as it seems to be deleting (null value) your SN.
Code:
adb shell getprop ro.sn.serial_numbers
If you don't get an output like this, you lost your SN.
Code:
123456789ABCDE
Stay tuned for restore method.
Saratoga79 said:
Anyone who tried TWRP on his watch, just check your SN (Serial Number) on Settings>About or just using adb, as it seems to be deleting (null value) your SN.
If you don't get an output like this, you lost your SN.
Stay tuned for restore method.
Click to expand...
Click to collapse
You using a pace?
Oliver3321 said:
You using a pace?
Click to expand...
Click to collapse
Yes, I do. It happened in Pace.
New releases by @mauronofrio already fixed the bug.
Saratoga79 said:
Yes, I do. It happened in Pace.
New releases by @mauronofrio already fixed the bug.
Click to expand...
Click to collapse
ok bro
How to unlock boot loader (verge).
How do I access the TWRP what do I have to press to access it.
Related
As you know, CM Recovery is useless for now. So i make Twrp Recoveries for our device.
It works on any kernel with extract_elf_ramdisk utility (it's built in mostly all kernels for custom ROMs, but I am not sure).And don't forget, that you are doing on your own risk, I am not responsible for bricked devices, acid rains or thermonuclear war.
Known Issues
-Nothing.
Installation:
Download z3fotatwrpv5
- Extract z3fotatwrpv5.img and place it to the root of your internal SD-card
- Type su and grant root access
- Type
Code:
dd if=/sdcard/z3fotatwrpv5.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
- Reboot to recovery to test if it works (if not, try again and check if you are doing it correctly).
Warning
- Don't flash it on stock roms. It will work on custom roms.
Download:
http://www97.zippyshare.com/v/25vBjwMU/file.html
Old Links
Z3fotatwrp- http://www.mediafire.com/download/batu9oc2hzx8d4p/z3fotatwrp.rar
Z3fotatwrpv2- https://www.mediafire.com/?f1pyuh2ac4ucmmd
Z3fotatwrpv3- https://mega.co.nz/#!FswhhLBT!SOBMiNuq6A9waYU8E7YeVVWr-39MCN01OSPYHzqOoeo
Z3fotatwrpv4- https://mega.nz/#!Bl5iTA4Y!j7hkGF5Gk4HT_COW0Gb4O_LCdC8rtX1KJouzkuMAb3U
Z3 DUAL TWRP 2.8.7.0
Many thanks to @rodrigoger for creating this image! https://www.dropbox.com/s/czwgrjjv7g29mpq/z3dualfotatwrpv4.img?dl=0
Some info:
Sony Xperia devices don't have recovery partition. Instead of this in custom kernels is used recovery-in-boot conception with two-stage boot (ramdisk-recovery is packed inside main ramdisk). And there is partition called FOTAKernel that is used for installing official FOTA (firmware-over-the-air) updates. After unlocking your bootloader it partition becomes redundant, because you cannot use OTA function anymore. So it may be used for storing recovery ramdisk. And this very useful future was implemented by a xda member, he developed utility extract_elf_ramdisk (it is merged to almost all kernels for Sony devices), it extracts recovery ramdisk from FOTA partition instead of using regular one from boot image. So even after updating or changing your kernel or ROM you don't lose your current recovery!
BTW, I don't own any of this work, recoveries are not compiled by me.
Update Z3FotaTWRPV5 (TWRP 3.0.0-0)
What's new in 3.0.0-0:
Completely new theme - Much more modern and much nicer looking (by z31s1g)
True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
SuperSU prompt will no longer display if a Marshmallow ROM is installed
Update exfat, exfat fuse, dosfstools (by mdmower)
Update AOSP base to 6.0
A huge laundry list of other minor fixes and tweaks
Great work, works fine. Ill have to apply theme due to the fact it does not go full screen lol
Sent from my Xperia Z3 using XDA Free mobile app
Works fine....thx
Odoslané z Xperia Z3 pomocou Tapatalku
TigerrrRawr said:
When installing from external SD the path needs to be corrected to /storage/sdcard1/z3fotatwrpv2.img. The path you posted is for internal SD.
Thanks for creating this image!
Click to expand...
Click to collapse
I'm sorry. I was pensive while i was writing this.
Can you not just go into Fastboot and flash recovery with this file instead of method listed above?
Many thanks
Markieboy said:
Can you not just go into Fastboot and flash recovery with this file instead of method listed above?
Many thanks
Click to expand...
Click to collapse
No, because sony phones do not have a recovery partition
Most xperia recoveries are either in system or in the boot.img, this is the exception
Im a bit confused now, as i swear i flashed 2.8.4.0 and then Cyanogen recovery that way .... ??????
I'm rooted with unlocked bootloader using the exploit so have DRM keys backed up. UK GSM Unbranded
Markieboy said:
Im a bit confused now, as i swear i flashed 2.8.4.0 and then Cyanogen recovery that way .... ??????
I'm rooted with unlocked bootloader using the exploit so have DRM keys backed up. UK GSM Unbranded
Click to expand...
Click to collapse
2.8.4.0 ?
But you cannot flash a recovery in fastboot like on other phones. Cyanogenmod recovery is a boot img is that is flashed to the boot partition on fastboot, hence the code
Code:
fastboot flash BOOT boot.img
Its a kernel not a recovery, but recovery is incorporated in it.
gregbradley said:
2.8.4.0 ?
But you cannot flash a recovery in fastboot like on other phones. Cyanogenmod recovery is a boot img is that is flashed to the boot partition on fastboot, hence the code
Code:
fastboot flash BOOT boot.img
Its a kernel not a recovery, but recovery is incorporated in it.
Click to expand...
Click to collapse
So you can not do:
Code:
fastboot flash recovery fotakernel.img
?
Edit:
Turns out you can.
Verbato said:
So you can not do:
Code:
fastboot flash recovery fotakernel.img
?
Edit:
Turns out you can.
Click to expand...
Click to collapse
That's strange, as the OP says sony phones do not have a recovery partition to flash to... You may be able to
Code:
fastboot flash FOTAkernel fotakernel.img
Markieboy said:
Im a bit confused now, as i swear i flashed 2.8.4.0 and then Cyanogen recovery that way .... ??????
I'm rooted with unlocked bootloader using the exploit so have DRM keys backed up. UK GSM Unbranded
Click to expand...
Click to collapse
Which Nightly Version do u use? It must work. Give me your terminal's screenshot.
gregbradley said:
That's strange, as the OP says sony phones do not have a recovery partition to flash to... You may be able to
Code:
fastboot flash FOTAkernel fotakernel.img
Click to expand...
Click to collapse
Code:
$ fastboot flash FOTAkernel z3fotatwrpv2.img
sending 'FOTAkernel' (10728 KB)...
OKAY [ 0.353s]
writing 'FOTAkernel'...
FAILED (remote: Command not allowed)
finished. total time: 0.356s
Code:
$ fastboot flash recovery z3fotatwrpv2.img
sending 'recovery' (10728 KB)...
OKAY [ 0.353s]
writing 'recovery'...
OKAY [ 0.719s]
finished. total time: 1.072s
Well, what do you know, turns out the command really is:
Code:
fastboot flash recovery fotakernel.img
Verbato said:
Code:
$ fastboot flash FOTAkernel z3fotatwrpv2.img
sending 'FOTAkernel' (10728 KB)...
OKAY [ 0.353s]
writing 'FOTAkernel'...
FAILED (remote: Command not allowed)
finished. total time: 0.356s
Code:
$ fastboot flash recovery z3fotatwrpv2.img
sending 'recovery' (10728 KB)...
OKAY [ 0.353s]
writing 'recovery'...
OKAY [ 0.719s]
finished. total time: 1.072s
Well, what do you know, turns out the command really is:
Code:
fastboot flash recovery fotakernel.img
Click to expand...
Click to collapse
I stand corrected, but that is a new one to me.
EDIT
After talking with some devs it seems we are both correct...
It's both true
Fota IS the recovery partition, but the recovery trigger does nothing to make S1 boot from it...
So it's perfectly possible to store the recovery on the fota partition and trigger the boot to it from there with a small change in the init.
and reading the message
I can conclude fastboot does not know FOTAkernel, but assumes it to be 'recovery'
Click to expand...
Click to collapse
So basically your command is flashing to the FOTAkernel partition because fastboot does not recognise it... Schrodinger's cat... we are both correct and both wrong at the same time.
Sources Please?
hey I was wondering about the sources you used to compile this, I've tried by building with cm breakfast and omni's branch of android bootable but I get multiple errors..
Code:
bootable/recovery/gui/resources.hpp:48: error: undefined reference to 'gr_getMaxFontHeight'
bootable/recovery/gui/resources.hpp:48: error: undefined reference to 'gr_getMaxFontHeight'
bootable/recovery/gui/scrolllist.cpp:205: error: undefined reference to 'gr_clip'
bootable/recovery/gui/scrolllist.cpp:315: error: undefined reference to 'gr_noclip'
bootable/recovery/gui/resources.hpp:48: error: undefined reference to 'gr_getMaxFontHeight'
bootable/recovery/gui/resources.hpp:48: error: undefined reference to 'gr_getMaxFontHeight'
bootable/recovery/gui/console.cpp:198: error: undefined reference to 'gr_maxExW'
bootable/recovery/gui/resources.cpp:186: error: undefined reference to 'gr_freeFont'
Any help please?
I am running the latest CM12 nightly.
Can I fast boot flash the recovery and not worry about my system bricking?
Yes, it's working without any issues. Using fastboot flash recovery on twrp 2.8.5.0. It's great not to use that CM-Recovery.
Any chance we can get 2.8.5.0 for FOTA ? Stock recovery for CM12 Sucks but 2.8.4.0 does not play well with flashing CM12 Roms
Ignore as I just saw your edited OP. You may want to update your title
Sent from my Xperia Z3 using XDA Free mobile app
HaoZeke said:
hey I was wondering about the sources you used to compile this, I've tried by building with cm breakfast and omni's branch of android bootable but I get multiple errors..
Code:
bootable/recovery/gui/resources.hpp:48: error: undefined reference to 'gr_getMaxFontHeight'
bootable/recovery/gui/resources.hpp:48: error: undefined reference to 'gr_getMaxFontHeight'
bootable/recovery/gui/scrolllist.cpp:205: error: undefined reference to 'gr_clip'
bootable/recovery/gui/scrolllist.cpp:315: error: undefined reference to 'gr_noclip'
bootable/recovery/gui/resources.hpp:48: error: undefined reference to 'gr_getMaxFontHeight'
bootable/recovery/gui/resources.hpp:48: error: undefined reference to 'gr_getMaxFontHeight'
bootable/recovery/gui/console.cpp:198: error: undefined reference to 'gr_maxExW'
bootable/recovery/gui/resources.cpp:186: error: undefined reference to 'gr_freeFont'
Any help please?
Click to expand...
Click to collapse
Recoveries are not compiled by me.
Mattadome02 said:
I am running the latest CM12 nightly.
Can I fast boot flash the recovery and not worry about my system bricking?
Click to expand...
Click to collapse
I haven't tried this yet. You can flash this with my codes.
BREAKING NEWS:
Huami took down the files from my hoster because of "alleged copyright infringement". I got a notice and an information that the files have been deleted, as well as that any further copyright infringement will lead to termination of the account and possible legal activities.
UPDATE 23-06-2017:
I updated the files to version 1.3.3a and reuploaded them to a different fileshare. (Let's see if they will be taken down again...)
UPDATE:
This is a new conversion method based on the techniques I used in my PACEfied installer. It will install the official Huami English firmware 1.3.3a with all features and OTA enabled. It will, however, NOT lock your bootloader. So, you have some time to evaluate, if you like the official ROM, or prefer to go to the PACEfied ROM.
NOTE: AS SOON AS YOU RECEIVE AND INSTALL AN OFFICIAL OTA AFTERWARDS, YOUR BOOTLOADER WILL BE LOCKED AND YOU WILL NOT BE ABLE TO SWITCH BACK.
ATTENTION: THIS METHOD ONLY WORKS FOR WATCHES WITH UNLOCKED BOOTLOADER (Huami started locking in official firmware 1.2.13 / 1.3.2b and upwards).
INSTALLATION:
This method uses the same installation procedure as PACEfied. Please find all information here: https://gitlab.com/Neuer_User/PACEfied_AmazFit/wikis/permanent-install
Downloads:
OFFICIAL ENGLISH FIRMWARE 1.3.3a: https://app.box.com/s/3io4m4zk7775x3vp80yw19l52slk6sxs
NOTE:
It is recommended that you factory reset the watch after installation, as data from other ROMs may lead to force closes of apps. You can do this either by unpairing the watch or in the settings / device menu of the watch.
DISCLAIMER:
While this method is pretty safe, there is a chance that you may brick your watch (so far no case known). YOU DO THIS ON YOUR OWN RISK. I am not responsible for any damages, psychological problems or wars emerging out of you converting your watch.
With the help of Neuer I was to flash my smartwatch with US Image!
I had some problems regarding android drivers while running fastboot and adb steps, this is how I solved them:
if fastboot is not detecting your device just download/install Google USB Driver at:
https://developer.android.com/studio/run/win-usb.html
Follow this guide on how to install the driver:
http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/3/
Neuer_User said:
Hi guys
...
fastboot boot Amazfit-mod-recovery.img
...
Click to expand...
Click to collapse
After booting into the modded recovery, adb was not detecting my smartwatch. All that i had to do was to go to "Step 35" of the previous guide and install the "Android Composite ADB Interface" driver and everything started to work again with ADB.
Big thanks to Neuer for his amazing hard work and patience! He did it! Also big thanks to everyone that provided useful information for this to work.
The instructions are good.
Model is now A1612.
ROM Version is now 1.3.0n
I cannot switch from Mi to KM.
Hi all,
Big thanks to Neuer_User for his hard work!
Just a quick question for those who have converted into english: does sync work and in which app (strava or mifit)?
Thanks.
It works perfectly. Thank you very much Neuer.
Great work Neuer_User you are now officialy a Amazfit Legend!!
May i suggest the next person to attempt this does a video tutorial and uploads it to youtube. Kudos to all those who have contributed in one way or another.
Another XDA Headline
I've an error during update, do you have any hint:
Code:
C:\Downloads\convert_to_eng>adb push boot.img.gz /sdcard/
7573 KB/s (5575879 bytes in 0.719s)
C:\Downloads\convert_to_eng>adb push system.img.gz /sdcard/
7713 KB/s (189626362 bytes in 24.009s)
C:\Downloads\convert_to_eng>adb push flash_eng_version.sh /sdcard
/
267 KB/s (547 bytes in 0.002s)
C:\Downloads\convert_to_eng>adb push md5s.txt /sdcard/
45 KB/s (94 bytes in 0.002s)
C:\Downloads\convert_to_eng>adb shell reboot bootloader
C:\Downloads\convert_to_eng>fastboot devices
0123456789 fastboot
C:\Downloads\convert_to_eng>fastboot boot Amazfit-mod-recovery.im
g
downloading 'boot.img'...
OKAY [ 0.436s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 1.403s
Thank you so much. it worked perfectly.
Can you make a tutorial movie ?? Im not very good whit fastboot. Tks
perritos said:
I've an error during update, do you have any hint:
C:\Downloads\convert_to_eng>adb push boot.img.gz /sdcard/
7573 KB/s (5575879 bytes in 0.719s)
C:\Downloads\convert_to_eng>adb push system.img.gz /sdcard/
7713 KB/s (189626362 bytes in 24.009s)
C:\Downloads\convert_to_eng>adb push flash_eng_version.sh /sdcard
/
267 KB/s (547 bytes in 0.002s)
C:\Downloads\convert_to_eng>adb push md5s.txt /sdcard/
45 KB/s (94 bytes in 0.002s)
C:\Downloads\convert_to_eng>adb shell reboot bootloader
C:\Downloads\convert_to_eng>fastboot devices
0123456789 fastboot
C:\Downloads\convert_to_eng>fastboot boot Amazfit-mod-recovery.im
g
downloading 'boot.img'...
OKAY [ 0.436s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 1.403s
Click to expand...
Click to collapse
That is no error. You just need to continue with the next step. You should be recovery now and need to start adb.
Neuer_User said:
That is no error. You just need to continue with the next step. You should be recovery now and need to start adb.
Click to expand...
Click to collapse
That's ok
Now my amazfit is in English version.
Thanks very much
Great job!!
Flawless instructions. Worked beautifuly.
I'd have made a video but was paranoid enough that something might go wrong that I didn't want to be distracted during the process. Anyway, the instructions are so clear I'm not sure someone needs the video. So long as adb/fastboot is set up properly, all will go fine.
Perfect, it works for me.
Flashed, rebooting.........
All ok thanks my friends!
Just to inform, during the procedure I have had a problem, after
"fastboot boot Amazfit-mod-recovery.img"
I have had an error message, but I move on because after adb shell I was root "#"
Thank you very much Great Job
Thanks you very much
I apply and all is ok
Thanks you again
took the plunge, all good... top work!
Thanks, guys, for all the positive feedback. I'm happy to hear it is working.
Presumably after flash we can delete these pushed files from SD card to free up storage space?
Sent from my HUAWEI NXT-L29 using XDA Free mobile app
Thank you ! Done ! It's all right !
Just a question : We can't get 24-hour clock instead AM/PM ?
{
"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
Hi everyone, I recently ported postmarketOS to the Moto G6.
I do not recommend installing this if the device is your daily driver. Not much works besides the screen. This is more of a proof-of-concept.
https://wiki.postmarketos.org/wiki/Motorola_Moto_G6_(motorola-ali)
If you would like to try it, you can follow the instructions here for "motorola" and "ali" : https://wiki.postmarketos.org/wiki/Installation_guide
Kernel source: https://github.com/msm8953-mainline/linux
Updates
6/3/2020:
64-bit support has been added, thanks to the work of the the RevengeOS project.
11/21/2022:
Firmware has been added (meaning things like wifi and GPU acceleration are now working)
The RevengeOS kernel has been replaced by a recent Linux fork (version 5.18.3)
A patch has been submitted to upstream Linux to add initial support for our device (only the PVT2 variant)
Uclydde said:
Hi everyone, I recently ported postmarketOS to the Moto G6.
I do not recommend installing this if the device is your daily driver. Not much works besides the screen. This is more of a proof-of-concept.
https://wiki.postmarketos.org/wiki/Motorola_Moto_G6_(motorola-ali)
If you would like to try it, you can follow the instructions here for "motorola" and "ali" : https://wiki.postmarketos.org/wiki/Installation_guide
Kernel source: https://github.com/Uclydde/kernel-msm/tree/lineage-16.0
Click to expand...
Click to collapse
Does wifi work?
vibraniumdroid said:
Does wifi work?
Click to expand...
Click to collapse
no
MarlonBrZ said:
no
Click to expand...
Click to collapse
It's still pretty cool though! We're seeing some development on a device I though was dead.
On the wiki it states:
"As of 8/10/2021, the Moto G6 is able to boot the msm8953 mainline kernel fork. It works fairly well, with features like display, touchscreen, and wifi working."
Where do I find that kernel and how do I install it. If I could get wifi to work this could actually be quite useful.
JPutz said:
On the wiki it states:
"As of 8/10/2021, the Moto G6 is able to boot the msm8953 mainline kernel fork. It works fairly well, with features like display, touchscreen, and wifi working."
Where do I find that kernel and how do I install it. If I could get wifi to work this could actually be quite useful.
Click to expand...
Click to collapse
Have you found a way yet?
I've seen many repos named msm8953, but had no clue it was for this device, I'll look up my browser history and post back here if I find any helpful instructions.
adhamnasr said:
Have you found a way yet?
I've seen many repos named msm8953, but had no clue it was for this device, I'll look up my browser history and post back here if I find any helpful instructions.
Click to expand...
Click to collapse
GitHub - brunorolak/kernel_motorola_msm8953
Contribute to brunorolak/kernel_motorola_msm8953 development by creating an account on GitHub.
github.com
This is the most up to date kernel we use, I have no Idea how you can implement it for postmarketos tho.
I remember seeing that blurb mentioning how it was working better on the mainline kernel and assumed they literally meant the mainline Linux kernel.
I assume that is the case, or maybe their own tree they are calling "close to mainline":
(Close to) Mainline - postmarketOS
wiki.postmarketos.org
In any case, I haven't tried installing PostmarketOS in a while, so I've no idea the actual status.
Any progress on this? Would love to have another mobile Linux device besides my Pinephone!
J-Mizzle said:
Any progress on this? Would love to have another mobile Linux device besides my Pinephone!
Click to expand...
Click to collapse
Yes, I've submitted an update to postmarketOS to use a close-to-mainline fork of the Linux kernel for our device.
Also, firmware support has been added, meaning that things like wifi and GPU acceleration are now working.
However, the display backlight isn't working, as well as several other things like audio, battery data, and camera.
adhamnasr said:
Have you found a way yet?
I've seen many repos named msm8953, but had no clue it was for this device, I'll look up my browser history and post back here if I find any helpful instructions.
Click to expand...
Click to collapse
Mainline kernel development for all devices with this SoC is happening here: https://github.com/msm8953-mainline/linux
vibraniumdroid said:
Does wifi work?
Click to expand...
Click to collapse
With the most recent update, now it does. You'll need to enable firmware when installing postmarketOS.
Uclydde said:
Yes, I've submitted an update to postmarketOS to use a close-to-mainline fork of the Linux kernel for our device.
Also, firmware support has been added, meaning that things like wifi and GPU acceleration are now working.
However, the display backlight isn't working, as well as several other things like audio, battery data, and camera.
Mainline kernel development for all devices with this SoC is happening here: https://github.com/msm8953-mainline/linux
With the most recent update, now it does. You'll need to enable firmware when installing postmarketOS.
Click to expand...
Click to collapse
I thought this was for the Moto G6 Play. I'm far less excited now. Good progress for those with the normal G6.
J-Mizzle said:
I thought this was for the Moto G6 Play. I'm far less excited now. Good progress for those with the normal G6.
Click to expand...
Click to collapse
You can find the Moto G6 Play's forum here: https://forum.xda-developers.com/c/moto-g6-play.8553/
By the way, the G6 Play has some postmarketOS support - but not from me. Here's the wiki page for it: https://wiki.postmarketos.org/wiki/Motorola_Moto_G6_Play_(motorola-aljeter)
Uclydde said:
You can find the Moto G6 Play's forum here: https://forum.xda-developers.com/c/moto-g6-play.8553/
By the way, the G6 Play has some postmarketOS support - but not from me. Here's the wiki page for it: https://wiki.postmarketos.org/wiki/Motorola_Moto_G6_Play_(motorola-aljeter)
Click to expand...
Click to collapse
Yes, I've got both those pages bookmarked. For some reason I failed to notice I ended up in the G6 forum vs the G6 Play. The Play variant doesnct seem to get much attention Android development. I follow PostmarketOS' Mastodon account as well as a handful of device maintainers and the G6 Play doesn't seem very active. I've got a Pinephone and have been considering picking up a OnePlus 6(T) as a more powerful alternative.
Hello, I tried to install this using
pmbootstrap init and pmbootstrap install to setup the installation with xfce4 and the commands from the wiki
it installs /system successfully but i can't boot to it and booting to boot.img fails, what can I do?
Code:
[20:49:45] DONE!
[email protected]:~$ pmbootstrap flasher flash_rootfs
[20:50:02] (native) flash rootfs image
[20:50:07] (native) install android-tools
< waiting for any device >
(bootloader) is-logical:system: not found
Sending sparse 'system' 1/2 (519524 KB)
OKAY [129.331s]
Writing 'system' OKAY [ 6.951s]
Sending sparse 'system' 2/2 (456977 KB) OKAY [114.314s]
Writing 'system' OKAY [ 6.170s]
Finished. Total time: 264.514s
[20:54:53] NOTE: chroot is still active (use 'pmbootstrap shutdown' as necessary)
[20:54:53] DONE!
[email protected]:~$ pmbootstrap flasher boot
[20:55:29] (rootfs_motorola-ali) install device-motorola-ali
[20:55:37] (rootfs_motorola-ali) install postmarketos-mkinitfs
[20:55:41] (rootfs_motorola-ali) mkinitfs postmarketos-qcom-msm8953
[20:55:51] (native) boot postmarketos-qcom-msm8953 kernel
[20:55:51] (native) install android-tools
Sending 'boot.img' (10858 KB) OKAY [ 2.589s]
Booting FAILED (remote: '')
fastboot: error: Command failed
[20:55:56] NOTE: The failed command's output is above the ^^^ line in the log file: /home/t/.local/var/pmbootstrap/log.txt
[20:55:56] ERROR: Command failed (exit code 1): (native) % fastboot --cmdline boot /mnt/rootfs_motorola-ali/boot/boot.img
[20:55:56] See also: <https://postmarketos.org/troubleshooting>
now i can't even mount '/system' through twrp (invalid argument) xd, please help
to the lack of information i got, i've thought i could install it overwriting a android custom rom i was using (Lineage 19.1, arm64)
gabriela-fazoli said:
Hello, I tried to install this using
pmbootstrap init and pmbootstrap install to setup the installation with xfce4 and the commands from the wiki
it installs /system successfully but i can't boot to it and booting to boot.img fails, what can I do?
Code:
[20:49:45] DONE!
[email protected]:~$ pmbootstrap flasher flash_rootfs
[20:50:02] (native) flash rootfs image
[20:50:07] (native) install android-tools
< waiting for any device >
(bootloader) is-logical:system: not found
Sending sparse 'system' 1/2 (519524 KB)
OKAY [129.331s]
Writing 'system' OKAY [ 6.951s]
Sending sparse 'system' 2/2 (456977 KB) OKAY [114.314s]
Writing 'system' OKAY [ 6.170s]
Finished. Total time: 264.514s
[20:54:53] NOTE: chroot is still active (use 'pmbootstrap shutdown' as necessary)
[20:54:53] DONE!
[email protected]:~$ pmbootstrap flasher boot
[20:55:29] (rootfs_motorola-ali) install device-motorola-ali
[20:55:37] (rootfs_motorola-ali) install postmarketos-mkinitfs
[20:55:41] (rootfs_motorola-ali) mkinitfs postmarketos-qcom-msm8953
[20:55:51] (native) boot postmarketos-qcom-msm8953 kernel
[20:55:51] (native) install android-tools
Sending 'boot.img' (10858 KB) OKAY [ 2.589s]
Booting FAILED (remote: '')
fastboot: error: Command failed
[20:55:56] NOTE: The failed command's output is above the ^^^ line in the log file: /home/t/.local/var/pmbootstrap/log.txt
[20:55:56] ERROR: Command failed (exit code 1): (native) % fastboot --cmdline boot /mnt/rootfs_motorola-ali/boot/boot.img
[20:55:56] See also: <https://postmarketos.org/troubleshooting>
now i can't even mount '/system' through twrp (invalid argument) xd, please help
to the lack of information i got, i've thought i could install it overwriting a android custom rom i was using (Lineage 19.1, arm64)
Click to expand...
Click to collapse
Reinstall stock with partitons commands
Hello.
I have the same problem as @gabriela-fazoli .
I have reinstalled stock as advised by @brunogroa but even after this I get the same error as shown above.
Do I need to install lk2nd maybe?
If I do then can someone please advise as to how I compile it.
I am using debian 11 and have installed the required dependencies including:
gcc-arm-none-eabi
device-tree-compiler
build-essential
I do not know what is meant by "Replace TOOLCHAIN_PREFIX with the path to your tool chain." when issuing the make command ie: make TOOLCHAIN_PREFIX=arm-none-eabi- <SoC>-secondary
Also is <SOC> meant to be replaced with sdm450-motorola-ali
I am a major newb when it comes to cross compiling.
Thank you for any assistance. I am very excited to give PostmarketOS a whirl on the G6.
Cheers
Bill
For any one else who might have issues compiling lk2nd I can highly recommend this website:
GCC Cross-Compiler - OSDev Wiki
wiki.osdev.org
Have compiled successfully using above instructions and the following make command:
make TOOLCHAIN_PREFIX=~/opt/cross/bin/arm-none-eabi- msm8953-secondary
Haven't tried it yet but fingers crossed.
No good.
I installed lk2nd with the following response:
fastboot flash boot lk2nd.img
(bootloader) is-logical:boot: not found
Sending 'boot' (288 KB) OKAY [ 0.178s]
Writing 'boot' (bootloader) Image not signed or corrupt
OKAY [ 0.028s]
Finished. Total time: 0.208s
Click to expand...
Click to collapse
Couldn't get lk2nd to boot though with Volume-Down pressed at varying intervals.
Then did the following:
[email protected]:~/pmbootstrap$ pmbootstrap flasher flash_rootfs
[10:33:14] (native) flash rootfs image
[10:33:16] (native) install android-tools
(bootloader) is-logical:system: not found
Sending sparse 'system' 1/3 (522136 KB) OKAY [ 19.229s]
Writing 'system' OKAY [ 5.087s]
Sending sparse 'system' 2/3 (517848 KB) OKAY [ 18.848s]
Writing 'system' OKAY [ 4.920s]
Sending sparse 'system' 3/3 (135789 KB) OKAY [ 4.943s]
Writing 'system' OKAY [ 1.128s]
Finished. Total time: 54.896s
[10:34:11] NOTE: chroot is still active (use 'pmbootstrap shutdown' as necessary)
[10:34:11] DONE!
[email protected]:~/pmbootstrap$ pmbootstrap flasher boot
[10:34:23] (rootfs_motorola-ali) install device-motorola-ali
[10:34:28] (rootfs_motorola-ali) install postmarketos-mkinitfs
[10:34:30] (rootfs_motorola-ali) mkinitfs postmarketos-qcom-msm8953
[10:34:38] (native) boot postmarketos-qcom-msm8953 kernel
[10:34:38] (native) install android-tools
Sending 'boot.img' (10858 KB) OKAY [ 0.397s]
Booting OKAY [ 0.587s]
Finished. Total time: 0.993s
[10:34:39] You will get an IP automatically assigned to your USB interface shortly.
[10:34:39] Then you can connect to your device using ssh after pmOS has booted:
[10:34:39] ssh [email protected]
[10:34:39] NOTE: If you enabled full disk encryption, you should make sure that osk-sdl has been properly configured for your device
[10:34:39] NOTE: chroot is still active (use 'pmbootstrap shutdown' as necessary)
[10:34:39] DONE!
Click to expand...
Click to collapse
It then reboots and shows the blue screen with the yellow Motorola 'M' and Powered By Android in white at the bottom.
Then it does nothing else.
I hold the power button in and it does the reboot loop thing but without the blue Motorola screen.
I can get into fastboot and TWRP without problem.
Any ideas?