[Firmware][Titan][Original] Update Bootloader and Modem 10/03/2017 (Mini-Package) - G 2014 General

Code:
/*
* Your warranty is (probably; this is official) now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Package
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will simply laugh at you.
*/
I uploaded all packages I found on the official servers! - More may follow (I'am really busy these days)
Version Info
MBM Version: 48.87
Modem Version: MSM8626BP_1032.3116.99.00R
FSG Version: TITANBP_FSG_01.33.00R
This will only update your Bootloader and Modem! Your System and Recovery won't be touched!
How to install
Open the back cover and check which Moto G 2014 version you have
Download the right package: https://www.androidfilehost.com/?w=files&flid=159972
Unpack the zip-File
Make sure you have installed the necessary drivers
Connect your Moto G 2014 with your computer. Either in fastboot or with usb debugging enabled
Start install.bat or if you want to type in manually (you need adb and fastboot):
Tick the "Thanks" Button if it worked
Code:
(adb reboot bootloader)
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
For FAQ look at gregor160300 great work: https://forum.xda-developers.com/moto-g-2014/general/bootloader-update-t3060007
The full Firmware you can find here: http://www.filefactory.com/folder/c6cdedc45a775d27/
XDA:DevDB Information
Titan Updatescript and Files Bootloader and Modem 10/03/2017 (Mini-Package), Device Specific App for the Moto G 2014
Contributors
LDAP98
Version Information
Status: Stable
Created 2017-03-10
Last Updated 2017-06-01

Reserved

Can it fix the gps fix problem?
and there are disadvantages? I heard from some people they could not install roms because of updated bootloader

Spieletips said:
Can it fix the gps fix problem?
and there are disadvantages? I heard from some people they could not install roms because of updated bootloader
Click to expand...
Click to collapse
If you flash the files maching you location you shouldn't experience any disadvantages. Read the FAQ mentioned in the first post. I can't say if it fixes the gps problem, cause I didn't had any problems. Theoretically you can't loose.
Regards

Do you have any changelog of the bootloader?
Why should I update if currently all custom roms support order bootloaders?

PsyClip-R said:
Do you have any changelog of the bootloader?
Why should I update if currently all custom roms support order bootloaders?
Click to expand...
Click to collapse
Sorry I didn't found anything. I only wanted to provide these files to those people who want to test the newer version.
Some people reported better performance especially the scrolling performance. Until now Im not sure if it's only placebo.

In the xt68 folder are 5 zips which i use?

luisbucobo said:
In the xt68 folder are 5 zips which i use?
Click to expand...
Click to collapse
It depends on where you life

@LDAP98 bro now I have 48.83 bootloader and I've Indian model device so, which one (file zip) should download instead of five (file zip) ?
I guess I should download 2nd zip file.. Its right?
EDIT : Thanks for this awesome guide.. Finally I was updated my bootloader 4883 to 4887
Thanks mate!
Sent from my Moto G 2014 using Tapatalk

I am a bit confused by the naming of the ZIP files:
Does RETDE match for a german titan? (because i assume RETDE refers to Detail DE aka the country code for germany?)
Just want to be sure before flashing.

Arokhaerr said:
I am a bit confused by the naming of the ZIP files:
Does RETDE match for a german titan? (because i assume RETDE refers to Detail DE aka the country code for germany?)
Just want to be sure before flashing.
Click to expand...
Click to collapse
RETDE could be also installed on a other titan. But to use services in Germany RETDE is the right one.
Regards

Thank you for the quick reply, flashing in a moment. ^^
EDIT: Worked, thanks again! ^^

Thnx bro! It really helped me!

Related

[UPDATE][Index][Guide][XT10XX] Update to Lollipop

Alright, so I decided to make a thread trying to make it easier for people to find guides so they can easily upgrade to Lollipop. Forums seems a bit messy.
Special thanks to @rolgar20 for helping me out with my XT1063
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
[UPDATE] If you own a XT1063/64 device, flash this updated lollipop stock rom found here, thanks to @KennyWuLee
[Prerequisites]
First things first, you MUST be using stock 4.4.4 firmwares for your model, or the model you want to update via stock recovery.
CUSTOMS RECOVERY LIKE TWRP O CWM WON'T WORK.
If you never unlocked bootloader, jump to step 5
Note: You can flash the firmware from another model (ex. flash XT1064 on XT1063) to run the specific OTA for that software, though is NOT RECOMMENDED
Download Motorola Drivers for Windows
Take a look at the stock firmwares (Links down)(thanks to @lost101) and download the file meant for your model.
New Links http://motofirmware.com/files/category/38-titan/ (Download 21.85.17 for XT1063 and XT1064, thanks to MotoFirmware)
Download adb/fastboot files
Note: You can skip this step following THIS guide (thanks to @Shawn5162)
Unzip both stock firmware and fastboot in the same folder, shift+right click on the screen and click on "open command prompt from here" and run these commands one by one
Code:
fastboot.exe flash logo logo.bin
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash system system.img_sparsechunk.0
fastboot.exe flash system system.img_sparsechunk.1
fastboot.exe flash system system.img_sparsechunk.2
fastboot.exe flash system system.img_sparsechunk.3
fastboot.exe flash modem NON-HLOS.bin
fastboot.exe erase modemst1
fastboot.exe erase modemst2
fastboot.exe flash fsg fsg.mbn
fastboot.exe erase cache
fastboot.exe erase userdata
Boot your device, then download and copy to internal sdcard the OTA file FOR YOUR MODEL from the following links below
XT1063 Global Single Sim Version
[OTA] Moto G 2014 XT1063 v22.11.6 Android Lollipop (thanks to @Taimur Akmal / @KennyWuLee )
XT1064 Consumer Cellular (US Single Sim)
[OTA] Moto G 2014 XT1064 v22.11.6 (thanks to @surenzxx)
Power off your device and get into fastboot mode, then choose "Recovery"
A broken android logo should appear, press and hold VolUP+VolDwn, then press and release the power button
Recovery options should appear, select "Choose update from sdcard" and use your ota file.
Wait until it finishes upgrading and voilá, you have Lollipop (Note: Updating takes about 5-10mins and the first boot almost the same time)
UPDATE: The new 22.11.6 Lollipop OTA can be found here for XT1063 thanks to @KennyWuLee and @Taimur Akmal, just flash it via stock recovery with a clean stock lollipop firmware. (If update fails, flash stock Kitkat, boot, flash 1st OTA, boot, flash 2nd OTA and you're done....)
There's a guide for XT1068 using a XT1063 firmware
XT1068
Lollipop 2-Sim Working with XT1063 OTA (thanks to @luisjoseb)
Rooting Lollipop
XT1063 - XT1068
Check the CF-AutoRoot website and look for your model at the end.
Code:
Just unzip the file, boot your phone into fastboot mode (power + vol dwn for about 3 seconds) and open root-windows.bat
Note: Tested on XT1063 and it gets stuck in bootloop (maybe I'm doing something wrong?)
Edit: Bootloop issue is partually fixed. Sometimes it loops 2-3 times and after 5-10mins it boots normally.
XT1064
XT1064 Lollipop Root (thanks to @savoca)
Good to see everything essential like Upgrading to Lollipop 5.0 & Rooting Lollipop 5.0 in a single thread :thumbup:
HOW CAN I DOWNGRADE from lollipop aws to kitkat glb and then again upgrade to Lol gib
Hi, I had originally an xt1063 Blur_Version.21.11.17.titan_retuglb.retuglb.en.US
yesterday I flashed Blur_Version.21.11.17.titan_retuaws.retuaws.en.US
And then upgrade to Lollipop retuaws.retuaws.en.US
But CF Auto root does not work (shows waiting for device)
I installed TWRP 2801 recovery and flashed SuperSU. But before it, I tried flashing xt1064 root.img. It makes the root checker to show my device as xt1064 and supersu was not working fine. So, I unroot using SuperSu, the binary files are deleted, but supersu remains the same.
I then today found retuglb.retuglb.en.US OTA, but I cannot downgrade to Blur_Version.21.11.17.titan_retuglb.retuglb.en.US.
HOW CAN I DOWNGRADE?
Flash the stock firmware through fastboot commands (those shown above, use those fastboot files, not mfastboot). It will say boot downgraded but it's fine. You won't be able to lock the bootloader again though, but you can flash stock xt1063 then update to lollipop.
Isn't stock recovery enough?
Quick question: do I have to flash the stock firmware and apply OTA zip? I am pretty much stock+twrp+root+xposed. If I uninstall xposed and flash the stock recovery, will I not be able to OTA from within the ROM?
The phone is now prompting me for OTA every now and then. This is 1064 model.
If you got the official update via ota and you have a custom recovery, update just won't work. Xposed doesn't work on Lollipop, it's not ART compatible yet. You should at least flash the stock recovery.img via fastboot to succesfully update, but in my opinion you should clean install the stock firmware before updating.
Is lollipop on our moto g showing the same problems that N5 users have been reporting? Especially the WiFi problems. I have no idea yet as it's not rolled out here in the UK yet.
Lollipop on the n5 works flawlessly. The n5 users complaining about bugs, including the WiFi bug, don't know how to install it properly. By properly I mean via fastboot, 1 image at a time. They dirty flash, or use scripts, and then complain that things aren't working properly.
---------- Post added at 03:47 PM ---------- Previous post was at 03:45 PM ----------
As for it working on the moto g, I'm not sure because my wife hates change and won't install the ota
Could a mod please move this to the Android Developer section? I think it fits better there.
it does not work
appears installation aborted :crying::crying:
jonh.solis said:
appears installation aborted :crying::crying:
Click to expand...
Click to collapse
What's your model? Are you sure you're using the correct OTA for your system software?
savnex said:
What's your model? Are you sure you're using the correct OTA for your system software?
Click to expand...
Click to collapse
i have 21.11.24.tita_retla_ds.retla.en.01
jonh.solis said:
i have 21.11.24.tita_retla_ds.retla.en.01
Click to expand...
Click to collapse
It won't work because you're trying to apply an update for the XT1063 retglb using a retla firmware.
You'll have to flash stock firmware for XT1063 retglb then apply the OTA, though I wouldn't recommend that.
savnex said:
It won't work because you're trying to apply an update for the XT1063 retglb using a retla firmware.
You'll have to flash stock firmware for XT1063 retglb then apply the OTA, though I wouldn't recommend that.
Click to expand...
Click to collapse
Hi I'm using CC 21.11.23.titan_ccaws.AWSCC.en.US cc (XT1064)
I have flashed it with MotoFlash3.2 with Blur_Version.21.11.17.titan_retuaws.retuaws.en.US and tried to use Blur_Version.21.11.17.titan_retuaws.retuaws.en.US (Lollipop) to update it says fail at "/system/app/3c_main.apk" has unexpected contents. Installation aborted.
Any suggestions thanks?
EDIT* I think I figured it out. First you have to unlock bootloader with Motorola website then you can flash with Motoflash with Blur_Version.21.11.17.titan_retuaws.retuaws.en.US. Then download the Blur_Version.21.11.17.titan_retuaws.retuaws.en.US and update files in recovery. Hopefully this all works.
is there no ETA fot the official update (update by phone) of Lollipop? Thanks
I install the OTA, now all good just mi internet mobile dosen't work, it's stuck on GSM only no EDGE o 3G
HTroX said:
I install the OTA, now all good just mi internet mobile dosen't work, it's stuck on GSM only no EDGE o 3G
Click to expand...
Click to collapse
There are still some bugs on those OTA files, they were meant for a soak test even though Motorola said it's official. Earlier today, I had no volume when making or receiving calls. I went back to KitKat and now I'm waiting for an official release (no date yet, afaik)
savnex said:
There are still some bugs on those OTA files, they were meant for a soak test even though Motorola said it's official. Earlier today, I had no volume when making or receiving calls. I went back to KitKat and now I'm waiting for an official release (no date yet, afaik)
Click to expand...
Click to collapse
How i go back to kitkat? Thanks...
HTroX said:
How i go back to kitkat? Thanks...
Click to expand...
Click to collapse
Follow the guide from steps 2 to 4
savnex said:
Follow the guide from steps 2 to 4
Click to expand...
Click to collapse
Can i just flash the stockfirmware? i have the lock the bootloader. 'Cause mu phone is new...

Lollipop on XT1053 (System Dump)

#include <std/disclaimer.h>
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modificiations, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
Click to expand...
Click to collapse
WARNING ! THIS DOES NOT UPDATE YOUR BOOTLOADER, so its safe to flash it until official OTA comes !
Download : *Oops ! I've been contacted by Motorola Support Forums to remove this !*
Instructions to flash :
1. Reboot to bootloader
2. flash the files
3.Factory Reset (Optional, but recommended)
4. enjoy
If the stock ota comes , make sure you flash back to Stock 4.4.4 BEFORE you take the OTA since the bootloader is not updated.
OR... if you prefer using TWRP instead of flashing...
Download : *Oops ! I've been contacted by Motorola Support Forums to remove this !*
Instructions :
1.Download the file
2.Extract it
3.put the file into internal sdcard > TWRP > backups
4. reboot into recovery
5. Wipe Data (Optional but HIGHLY RECOMMENDED !)
6. go back to main menu and click Restore
7. select the backup above
8. enjoy
REMEMBER to flash back stock files before accepting any OTAs ! i am not responsible for anything !
Wow thanks.
I have a xt1052 retail GB thats on cm12 nightly with twrp. Can i just wipe and flash this to get stock lollipop in the meantime?
i.e. no extra steps like going back to stock 4.4.4 or anything.
Cause the first download is just the system and boot. But does the boot update my stock bootloader to the lollipop xt1053?
---------- Post added at 12:31 PM ---------- Previous post was at 12:29 PM ----------
And what is the second download? the full stock xt1053 ota?
stealtheye said:
Wow thanks.
I have a xt1052 retail GB thats on cm12 nightly with twrp. Can i just wipe and flash this to get stock lollipop in the meantime?
i.e. no extra steps like going back to stock 4.4.4 or anything.
Cause the first download is just the system and boot. But does the boot update my stock bootloader to the lollipop xt1053?
Click to expand...
Click to collapse
Try the twrp backup.
1. Download from above link.
2. Extract the folder and paste it on you phone in TWRP/BACKUPS.
3. Reboot in recovery and wipe data.
4. Restore the backup.
5. Reboot
6. Report back if this works.
You can backup your current system incase something goes wrong.
Sent from my Moto X using XDA Free mobile app
Good luck with this, as flashing "only certain parts" to a newer level has shown to be problematic in the past.
If this is not updating GPT.BIN and the parts impacted by Motoboot.img then, thankfully, flashing the full SBF to revert to 4.4.4 would be possible to fix any issues.
This is likely the least dangerous way to experiment with this leak. Given that most will restore it via TWRP, a backup and restore is all you'd need to get back to stock. Far better than converting your phone to BR version. Not sure why you'd need to SBF back to stock.
I was able to update mi moto x to lollipop!
moto x 1052 uk
used the twrp metod, i haven't flashed super su, I will try after the configuration is finish on the phone!
Thanks!
EvilDragonEX said:
Download : *Oops ! I've been contacted by Motorola Support Forums to remove this !*
Click to expand...
Click to collapse
And with that, thread closed

[ROM+KERNEL+TWRP][Ticwatch Pro(Catfish)(Catshark-4G)]+[Ticwatch C2(Skipjack)[9Aug20]

-[Ticwatch Pro 4G/LTE (EU) (Catshark)-PWDD.190617.059]-[30-5-2020]
- [Ticwatch Pro 2020 (Catfish-Ext)-PMP2.191203.001]-[22-6-2020]
- [Ticwatch Pro (Catfish)-PWDD.190617.074]-[09-8-2020]
#############################
- [Ticwatch Pro 4G/LTE (USA) (Catshark)-PWDD.190617.032]-[DISCONTINUED]-
-[Ticwatch C2 (Skipjack)-PWDS.190618.001.B4]-[DISCONTINUED]
-[Ticwatch E2 (Tunny)-PWDS.190618.001.B3]-[DISCONTINUED]
#############################
Code:
****Disclaimer****
[COLOR="Red"][B]WARNING: IMPROPER FLASHING MAY POTENTIALLY BRICK YOUR DEVICE. SO PLEASE PROCEED AT YOUR OWN RISK. ME OR ANY OTHER DEVELOPER MENTIONED IN THIS POST WILL ASSUME NO RESPONSIBILITY FOR THIS. I accepts no responsibility for any damage to your device. Please read the instructions and notes before flashing anything[/B][/COLOR]
IF YOU LIKE MY WORK AND WANT TO BUY ME A COFFEE
DONATE-ME-HERE​
###################
REQUIREMENTS
###################
- Ticwatch Pro, Ticwatch Pro 4G, Ticwatch Pro 2020 Ticwatch C2 and Ticwatch E2 ONLY INTERNATIONAL VERSION. It may also work on Chinese version too but I haven't test it personally.
- An unlock bootloader, working driver and working adb/fastboot
- You can download ADB/FASTBOOT from here Download: ADB/FASTBOOT
- Custom recovery TWRP- (Se download section below)
###################
HOW TO FLASH- STEPS
###################
(FOLLOW EITHER THE INSTRUCTIONS FROM MEGA FOLDER OR THE STEPS BELOW)
- Download the latest ROM, latest vendor, latest Magisk and busybox - (Everything are include in the MEGA folder)
- Attach your watch to your PC and enable USB Debugging from settings menu. Ensure adb/fastboot is working. Please Google and see "how to enable debugging from settings menu".
- Extract the vendor folder and go inside the folder (Here you will find vendor.img and twrp.img + other files)
(You have to flash the vendor image and format userdata and cache)
- Boot your watch into fastboot/bootloader mode by applying the following code.
Code:
- adb devices
- adb reboot bootloader
- fastboot flash vendor vendor.img
- fastboot format userdata OR fastboot erase userdata
- fastboot format cache OR fastboot erase cache
- fastboot boot NAME-OF-THE-TWRP.img (Se the name of the twrp.img)
- Now move the ROM, Magisk and busybox to your watch.
- Flash the ROM and reboot. If you prefer root then
- Flash busybox and finally Magisk (IMPORTANT flash ROM, then Busybox and Magisk in this order)
NOTE
- When rebooting your watch, IF a Prompt come up and asking about installing twrp bla.bla then un-mark both lines/ then click on DO Not Install
- Let your device boot up, then connect your watch to your phone and finish the initial setting
- Open Magisk Manager and go to settings and set Automatic Response to Grant, Uncheck updates and Superuser notifications to None
- Reboot and enjoy
###################
ROM AND KERNEL FEATURES-
See latest changelog here
###################
DOWNLOAD
[DECRYPTION KEY]
Code:
iZbWXMs8vabDW1szJz1hgg
OPTIONAL
TO INSTALL KERNEL CONTROL APP WEAR OS
Code:
- Download the KernelAudiutor4Wear.apk from above link and move it to your adb folder.
- adb devices
- adb install KernelAudiutor4Wear.apk
MAGISK/BUSYBOX/APP-KERNEL-CONTROL
DOWNLOAD LATEST MAGISK FROM HERE
DOWNLOAD LATEST BUSYBOX FROM HERE
KERNEL CONTROL APP WEAR OS
###################
BACK TO STOCK ROM
See Mega folder for Stock images
Code:
[[B]DECRYPTION KEY[/B]]
iZbWXMs8vabDW1szJz1hgg
[B][SIZE="4"]STEPS[/SIZE][/B]
- fastboot flash aboot aboot.img
- fastboot flash boot boot.img
- fastboot flash recovery recovery.img
- fastboot flash vendor vendor.img
- fastboot flash system system.img
- fastboot format userdata OR fastboot erase userdata
- fastboot format cache OR fastboot erase cache
- fastboot reboot
##############################
Source/GitHub
##############################
-Source
-Source
-Source
###################
IF YOU LIKE MY WORK AND WANT TO BUY ME A COFFEE
DONATE-ME-HERE
###################
Special thanks to:
If you can, donate and respect all the devs and enjoy
@Maxr1998 Big thanks for giving me knowledge and your great work for Asus Zenwatch_3 and your great github guide.
@topjohnwu for his great effort (Magisk)Thank you so much
@SuperR.R for the great kitchen
@YashdSaraf for the busybox (I edit a bit to make it work for Ticwatch-pro)
Sultan Al Sawaf for his patch
Mobvoi, Google and Qualcomm for providing us the kernel source.
Please always support devs and others (soon).
/*
* Your warranty is now void.
* I am not responsible for bricked devices, bootloop and dead SD cards,
* YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Click to expand...
Click to collapse
Download : TWRP For Catshark 4G/LTE
Source Device Tree: Device Tree For Building TWRP
###############################
###############################
How to get the Gpay back...
1-https://pastebin.com/HKV7cj7H
2-https://forum.xda-developers.com/smartwatch/other-smartwatches/rom-kernel-t3821013/page172
3-https://www.youtube.com/watch?v=UKxGfNxRjo4&t=320s
4-https://forum.xda-developers.com/showpost.php?p=79637148&postcount=1720
Be aware for this in future....19 April 2020
https://mobile.twitter.com/topjohnwu/status/1245956080779198464
Very happy! Really looking forward to.
waiting English rom for China version
janjan said:
IF YOU LIKE MY WORK AND WANT ME TO CONTINUE, THEN BUY ME A SHOT OF WHISKY
DONATE ME HERE
DONATE-ME​Special thanks to:
If you can, donate and respect all the devs and enjoy
@Maxr1998 Big thanks for giving me knowledge and your great work for Asus Zenwatch_3 and your great github guide.
@topjohnwu for his great effort (Magisk)Thank you so much
@superR for the great kitchen
Ticwatch and Google for providing kernel source.
Please always support devs and others (soon).[/SIZE][/B]
Contributors
janjan, JANJAN
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
Version Information
Status: Stable
Stable Release Date: 25/7/2018
Click to expand...
Click to collapse
Sorry, where do you take the original Kernel and ROM source code? I didn't find them.
Thanks in advance
vietdh said:
waiting English rom for China version
Click to expand...
Click to collapse
I wait too, and there are no references, the same the Chinese version.
Where references I burn from impatience
---------- Post added at 12:40 PM ---------- Previous post was at 12:37 PM ----------
alucard_24 said:
Sorry, where do you take the original Kernel and ROM source code? I didn't find them.
Thanks in advance
Click to expand...
Click to collapse
We wait for the reference while they are absent
ready for up ROM
alucard_24 said:
Sorry, where do you take the original Kernel and ROM source code? I didn't find them.
Thanks in advance
Click to expand...
Click to collapse
3.18-oreowear-dr works fine.
tempter_alex said:
I wait too, and there are no references, the same the Chinese version.
Where references I burn from impatience
---------- Post added at 12:40 PM ---------- Previous post was at 12:37 PM ----------
We wait for the reference while they are absent
Click to expand...
Click to collapse
Uploading soon.
vietdh said:
ready for up ROM
Click to expand...
Click to collapse
Hehe need to upload source and fix some issues first. Will be up soon.
janjan said:
3.18-oreowear-dr works fine.
Click to expand...
Click to collapse
So no official source code has been released by TicWatch.
Thanks
What is that? No firmware?
alucard_24 said:
So no official source code has been released by TicWatch.
Thanks
Click to expand...
Click to collapse
https://android.googlesource.com/kernel/msm.git/+/android-msm-catshark-3.18-oreo-wear-dr
have no idea why they call it catshark
tag project branch device
android-wear-8.0.0_r0.24 kernel/msm android-msm-catshark-3.18-oreo-wear-dr Catfish
janjan said:
https://android.googlesource.com/kernel/msm.git/+/android-msm-catshark-3.18-oreo-wear-dr
have no idea why they call it catshark
tag project branch device
android-wear-8.0.0_r0.24 kernel/msm android-msm-catshark-3.18-oreo-wear-dr Catfish
Click to expand...
Click to collapse
Thank you very much
Thanks for your rom,
and this is the wear os global version? Not the china vwersion?
I want a global version but I have a china version ticwatch pro
Have one of these being delivered soon. Things specific to the device (like dual screens) still will work?
jinhaihan said:
Thanks for your rom,
and this is the wear os global version? Not the china vwersion?
I want a global version but I have a china version ticwatch pro
Click to expand...
Click to collapse
Yes. Global version..based on stock imsges
3dux said:
Have one of these being delivered soon. Things specific to the device (like dual screens) still will work?
Click to expand...
Click to collapse
Yes. Everything is working. TWRP, Kernel and ROM. I am going to upload everything today. Working to get the source up and update my GitHub.
Can someone please help me in finding the steps to unlock the bootloader for TicWatch Pro Chinese version.
janjan said:
Yes. Global version..based on stock imsges
Yes. Everything is working. TWRP, Kernel and ROM. I am going to upload everything today. Working to get the source up and update my GitHub.
Click to expand...
Click to collapse
Hahaha it is perfect!! I will flash it in some days later, and If work fine I will donate
oh , can it get ota update?
manishsoni7689 said:
Can someone please help me in finding the steps to unlock the bootloader for TicWatch Pro Chinese version.
Click to expand...
Click to collapse
Enable ADB in the Developer Settings
Once done connect your watch to your computer and do "adb reboot bootloader"
THIS WILL RESET YOUR WATCH:*Once in fastboot mode type "fastboot oem unlock" (if you already have an unlocked bootloader you can skip this)
I am new to xda.
How do I download twrp and rom?
The links are broken to me.
I have a Ticwatch Pro Chinese version. I would like to flash a international ROM.
otto_naka said:
I am new to xda.
How do I download twrp and rom?
The links are broken to me.
I have a Ticwatch Pro Chinese version. I would like to flash a international ROM.
Click to expand...
Click to collapse
We wait, we wait. We wait for))))

[2018-09-08][ROM][OFFICIAL][7.1.2]MIUI Fastboot Flashable Zip Project

{
"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"
}
UPDATE! URGENT! IMPORTANT! PLEASE READ!​
PLEASE READ THIS ANNOUNCEMENT!!!​
May I present to you, The Xiaomi Redmi 5A Fastboot Flashable Zip Project!​
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Click to expand...
Click to collapse
Introduction
At first, I only planned to release a Flashable Zip of the persist disk image. I had sensor problems so this was my main goal. I then started to think “Hmm.. why don’t I just bundle it all together since I already had ideas for this project anyway”. Voilà, this is how this project came to life!
Project's main aim
This project is mainly for those who want to return to stock MIUI firmware without flashing (MiFlash Tool) with PC (currently/ doesn't have a PC). Each and every one of the disk images provided with MIUI's Fastboot Firmware will be available here individually in a highly compressed Flashable Zip format.
REQUIREMENTS
TWRP (MANDATORY!)
Unlocked Bootloader (ALSO MANDATORY!)
Bugs
1. Unable to flash system-signed.zip and userdata-signed.zip [FIXED] *V9.5.10.0.NCKMIFA
2. Unable to flash boot-signed.zip and firmware-update.zip [FIXED] *V9.6.2.0.NCKMIFD
Features
Highly compressed disk images
Example: system.img 3.0GB --> 0.9GB!
Installation
Just flash zip in TWRP!
Changelog
2018-09-08
2.1 Third Update
Based on latest MIUI V9.6.4.0.NCKMIFD Fastboot Firmware
- Fixed updater-script weird characters issue ("FX TextEdit" app problem)
- Brought back userdata-signed.zip with original fastboot firmware contents in it
- New zip signing method (Should work with TWRP "Verify Zip Signature")
- Fixed boot-signed.zip and firmware-update.zip ERROR: 6 issue
- Tested updater-script one by one (Should work now without ERROR: 6 issue)
Previous Changelogs:
2018-08-23
2.0 Second Update
Based on latest MIUI V9.6.2.0.NCKMIFD Fastboot Firmware
- Used some images from recovery firmware to reduce release time
- Switched system-signed.zip to set_metadata format
- Fixed major flaw in big flashable zips (Small tmpfs size, disk image not fully extracted and failed to flash)
- Removed tmpfs resize usage in big flashable zips
- Switched userdata-signed.zip to format partition only
- Combined adspso.bin, cmnlib64.mbn, cmnlib.mbn etc. to firmware-update-signed.zip
2018-08-03
1.0 Initial Release
Based on latest MIUI V9.5.10.0.NCKMIFA Fastboot Firmware
Click to expand...
Click to collapse
Download
1. V9.6.4.0.NCKMIFD
https://www.mediafire.com/folder/zpwzd4ld2f8n4/V9.6.4.0.NCKMIFD
2. V9.6.2.0.NCKMIFD
https://www.mediafire.com/folder/8ow4pcxqi3zb3/V9.6.2.0.NCKMIFD
3. V9.5.10.0.NCKMIFA
https://www.mediafire.com/folder/8mcd8fg4zb4kh/V9.5.10.0.NCKMIFA
XDA:DevDB Information
[2018-09-08][ROM][OFFICIAL][7.1.2]MIUI Fastboot Flashable Zip Project, ROM for the Xiaomi Redmi 5A
Contributors
Growtopia Jaw, ezrawk
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
Version Information
Status: Stable
Current Stable Version: 7.1.2
Stable Release Date: 2018-09-08
Created 2018-08-08
Last Updated 2021-05-06
Flashable zip contents and it's usage
boot-signed.zip
This zip contains MIUI's stock bootloader image. Flashing this will restore your boot partition to stock.
cache-signed.zip
This zip contains MIUI's stock cache image. Flashing this will restore your cache partition to stock.
*Cache partition is normally used to store temporary TWRP/ Android OS files.
cust-signed.zip
This zip contains MIUI's stock vendor image. Flashing this will restore your vendor partition to stock.
*This is actually the vendor partition for Xiaomi phones. It stores your phone's proprietary drivers for your phone's hardware like display drivers, Open GL, sound drivers and more..
firmware-update-signed.zip [v2 and above only]**
This zip contains MIUI's stock adspso.bin, cmnlib64.mbn, cmnlib.mbn etc. images. Flashing this will restore the below mentioned image's partition to stock.
*Images contained in this flashable zip:
adspso.bin
cmnlib64.mbn
cmnlib.mbn
devcfg.mbn
emmc_appsboot.mbn
keymaster.mbn
lksecapp.mbn
mdtp.img
NON-HLOS.bin
rpm.mbn
sbl1.mbn
splash.img
tz.mbn
These images are originally distributed with MIUI's official recovery zip. I decided to include them here is because it is more easy to release for the project and it will save a lot of time preparing it for a release than manually converting each and every fastboot images to raw disk image format and then highly compressing it.
These images will be available in each and every release of MIUI's recovery zip. All of the images in this zip are required to be flashed when you upgrade/ downgrade a release or it may introduce bugs like Wi-Fi not working in your MIUI ROM.
mdtp-signed.zip [v1 only]*
This zip contains MIUI's stock mdtp image. Flashing this will restore your mdtp partition to stock.
*According to @mirfatif's thread, this partition contains files for "boot verification and Qualcomm SafeSwitch technology to lock and track theft phones".
misc-signed.zip
This zip contains MIUI's stock misc image. Flashing this will restore your misc partition to stock.
*From my understanding from several sources, this partition contains CID (Carrier and Region ID), USB configuration settings and several hardware settings related files.
persist-signed.zip
This zip contains MIUI's stock persist image. Flashing this will restore your persist partition to stock.
*This particular partition is what most users have problem from. It contains sensor driver files. (If you have problems like proximity sensor/ rotate screen not working, this is the zip you need to flash).
recovery-signed.zip
This zip contains MIUI's stock recovery image. Flashing this will restore your recovery partition to stock.
*THIS IS NOT TWRP! THIS IS MIUI'S STOCK RECOVERY! FLASHING THIS WILL REMOVE YOUR TWRP!
*Everyone using custom ROM should already/ must know this partition (Stop using custom ROM if you don't know what this partition is for! :silly:
splash-signed.zip [v1 only]*
This zip contains MIUI's stock splash image. Flashing this will restore your splash partition to stock.
*This partition contains an image file.. Yep, an image file.. But for what? Well, the screen you first see when you turn on your phone duh! (The MIUI logo) Not the bootanimation!
system-signed.zip
This zip contains MIUI's stock system image. Flashing this will restore your system partition to stock.
*Everyone should know this.. This is where the ROM's main files are located. Android OS's main partition like Android Nougat, Oreo, Pie etc.
userdata-signed.zip
This zip contains MIUI's stock data image. Flashing this will restore your data partition to stock.
*This is also a must know partition.. This is where most of your apps, images and games are stored. It is also where the OS's permanent cache a.k.a dalvik/ ART (Android Runtime) are stored.
*v1 only: It means that this flashable zip is only available in V9.5.10.0.NCKMIFA and it has been integrated into firmware-update-signed.zip in the next release and above.
**v2 and above only: It means that this flashable zip is only available in V9.6.2.0.NCKMIFD and above. It is not available in v1.
ANNOUNCEMENT
After about 3 years, I finally had the time to update this project. This project has been discontinued and download links will still be available but I'm not sure if those flashable zips still works. I no longer own a Xiaomi Redmi 5A and I'm unable to test if those flashable zips still works. Please use it at your own risk and I will occasionally be online to check on comments in this thread but I might not be able to assist you on your problem.
Thank you.
Spoiler: Previous Announcements
Once again, project has been updated to MIUI V9.6.4.0.NCKMIFD! Other than that, there are flaws in the previous release (again). I tested each and every one of the zip before releasing. These zips should work this time (hopefully).
I will halt this project as my Microsoft Azure Free Subscription has expired (30 days). I rely on cloud virtual machine to get these things done. I don't have a PC at home and it will be very hard to release project updates without a PC. Currently I use my phone (Xiaomi Redmi 5A) for all of the work (even when writing this post). Every single release that I've released are possible because of Microsoft Azure. I can't do things without it.
To make up for my mistakes, I've added two things to this release:
1. Brought back userdata-signed.zip (Actual files in it)
2. New zip signing method (Should now work with TWRP's "Zip Signature Verification" Yay!)
I spent a two days preparing this (From yesterday and at about 1 a.m. in the morning to 9 a.m.) with both tired and sleepy mode...
I will be flashing this zips to prove that it's working (Will provide screenshots also!)
Well, that's all for now.
Thank you all for understanding!
Wow you made it a whole package. Man you didn't have to put my name on the contributors, the credit goes all to you!
Nevermind, you should be in the contributor lists because the sparked idea came from you! You can also contribute to this project if you have any ideas! As they say, Ideas spark better with more people working together than people who work on their own!
Eemmmm...
What's the different with official recovery firmware from bigota miui?
It's the same stock firmware, right?
Azocke5531 said:
Eemmmm...
What's the different with official recovery firmware from bigota miui?
It's the same stock firmware, right?
Click to expand...
Click to collapse
Yes, you are right but.. Some of the disk images in official fastboot firmware are unavailable in official recovery firmware (Example: persist).. And some people may prefer to only download a single disk image. Some people also may have limited Internet quota and try to save every single MB if they can..
Another reason is that some disk image can't be written in MiFlash tool (Example: persist).. Some people will accidentally delete/ corrupt the partition and so far till now, I've found no article online about how to fix Xiaomi Redmi 5A persist partition/ sensors
can i ask something? this is for minimalize the storage used? or what?
fikriwirahman said:
can i ask something? this is for minimalize the storage used? or what?
Click to expand...
Click to collapse
It's the same as official firmware (unmodified & clean) but it is highly compressed to save Internet quota especially for those who have limited Internet quota
Example: normal recovery firmware zip = 1 GB+
This project zip = many choices (you can download it individually)
system.img = 0.9 GB (normal is 3GB if uncompressed)
userdata.img = 0.2 GB (normal is 2.9 GB if uncompressed)
Growtopia Jaw said:
Yes, you are right but.. Some of the disk images in official fastboot firmware are unavailable in official recovery firmware (Example: persist).. And some people may prefer to only download a single disk image. Some people also may have limited Internet quota and try to save every single MB if they can..
Another reason is that some disk image can't be written in MiFlash tool (Example: persist).. Some people will accidentally delete/ corrupt the partition and so far till now, I've found no article online about how to fix Xiaomi Redmi 5A persist partition/ sensors
Click to expand...
Click to collapse
Ok, now I understand
About standalone bootloader zip, is that contain a locked or unlocked bootloader?
Azocke5531 said:
Ok, now I understand
About standalone bootloader zip, is that contain a locked or unlocked bootloader?
Click to expand...
Click to collapse
This zip only contains boot image. Your question about "locked and unlocked bootloader" is totally unrelated to the boot image zip.
About locked/ unlocked bootloader, that is only changed (locked/ unlocked) in Mi Unlock Tool (which is the tool you used to unlock your phone in the first place). Only this tool, fastboot and manual terminal command input can change the unlock/ locked state.
Long story short, unlock/ lock bootloader is NOT the same with bootloader image (boot image). Boot image is just a partition. Unlock/ locked state is a state whether your phone's bootloader is unlocked or not.
Great work
Growtopia Jaw said:
This zip only contains boot image. Your question about "locked and unlocked bootloader" is totally unrelated to the boot image zip.
About locked/ unlocked bootloader, that is only changed (locked/ unlocked) in Mi Unlock Tool (which is the tool you used to unlock your phone in the first place). Only this tool, fastboot and manual terminal command input can change the unlock/ locked state.
Long story short, unlock/ lock bootloader is NOT the same with bootloader image (boot image). Boot image is just a partition. Unlock/ locked state is a state whether your phone's bootloader is unlocked or not.
Click to expand...
Click to collapse
A little correction:
boot partition is kernel partition, boot.img is kernel image file.
bootloaders:
PBL (primary bootloader), SBL(secondary bootloader)/XBL(extesible bootloader), aboot/appsboot (OEM bootloader), abootbak (OEM bootloader backup?)
Unlocking bootloader usually done to aboot and abootbak, abootbak partition may contains excactly the same image as aboot partition.
--------------------------------------------------------------------
Could someone with unlocked BL Redmi 5A dump the aboot and abootbak partitions, and share them here please?
They're main "ingredients" to unlock BL instantly without permission, only needs to enter EDL mode.
(Going to figure out if Redmi 5A's SBL/XBL will accept officially unlocked aboot from another Redmi 5A or if it needs more works).
r6680jc said:
A little correction:
boot partition is kernel partition, boot.img is kernel image file.
bootloaders:
PBL (primary bootloader), SBL(secondary bootloader)/XBL(extesible bootloader), aboot/appsboot (OEM bootloader), abootbak (OEM bootloader backup?)
Unlocking bootloader usually done to aboot and abootbak, abootbak partition may contains excactly the same image as aboot partition.
--------------------------------------------------------------------
Could someone with unlocked BL Redmi 5A dump the aboot and abootbak partitions, and share them here please?
They're main "ingredients" to unlock BL instantly without permission, only needs to enter EDL mode.
(Going to figure out if Redmi 5A's SBL/XBL will accept officially unlocked aboot from another Redmi 5A or if it needs more works).
Click to expand...
Click to collapse
Yep, that's pretty much a very detailed explanation. Totally forgotten about the word "kernel" :silly: was looking for that word actually
--------------------------------------------------------------------
Didn't see that coming.. You can't unlock your Redmi 5A officially? Update info please..
Growtopia Jaw said:
Yep, that's pretty much a very detailed explanation. Totally forgotten about the word "kernel" :silly: was looking for that word actually
--------------------------------------------------------------------
Didn't see that coming.. You can't unlock your Redmi 5A officially? Update info please..
Click to expand...
Click to collapse
I'm still waiting halfway (about 180 hours).
Yours unlocked?
Would you dump the two bootloader partitions (aboot and abootbak) and upload them here?
r6680jc said:
I'm still waiting halfway (about 180 hours).
Yours unlocked?
Would you dump the two bootloader partitions (aboot and abootbak) and upload them here?
Click to expand...
Click to collapse
I'm unlocked but why stop halfway?
Growtopia Jaw said:
I'm unlocked but why stop halfway?
Click to expand...
Click to collapse
not stopping halfway, it's like a backup plan, just in case after 360h of waiting and end up failed to unlock.
r6680jc said:
not stopping halfway, it's like a backup plan, just in case after 360h of waiting and end up failed to unlock.
Click to expand...
Click to collapse
Try waiting after 360 hours first. I'll try to prepare and provide you the backup if it really does fail to unlock.
Last time when I took a backup from someone, the backup contains some kind of device information from his phone (I accidentally wiped a partition and requested backup from him). I was using a custom ROM at that time (It doesn't have any problems with security thingy). Then, I decided to return back to MIUI because graphics performance is bad in custom ROM (I can't even open Real Racing 3. It keeps force closing). After flashing MIUI and the backup, I rebooted the phone. Then, it suddenly says "This device is associated with an existing account. For security reasons, you need to enter password to verify the device." This is what it looks like:
I recommend you to wait for the period to finish first. If it really really doesn't work, you can try it out with your method.
Download links needs to be updated they are offline =x
jasonhelene said:
Download links needs to be updated they are offline =x
Click to expand...
Click to collapse
Sorry about that, the hosting provider is currently moving all the website on their server manually. It'll be months probably.. I'll post a temporary link to the downloads ASAP.
Thank you

[Aljeter] [03rd June 2019] TWRP 3.3.1-0 Moto G6 Play

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.​
PHP:
* Your warranty is now void.
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
Changelog For 3.3.1-0
Fix selinux issues during formatting - dianlujitao
Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
Add option to uninstall TWRP app from /system - Dees_Troy
Create digest for subpartitions - bigbiff
Install Guide:
For non rooted and rooted phones
Requirements
Unlocked bootloader
Fastboot drivers installed on PC
Brain
Download https:// drive .google.com/file/d/1-1MQqE42zIoLnqbYx-JTRQtVtnIV85Rt/view?usp=sharing (Remove space)
Put phone into fastboot mode (hold vol down + power button)
Connect phone to PC
Open a command prompt where you have fastboot and the TWRP image file located
Type the following in command prompt:
PHP:
fastboot flash recovery twrp-3.3.1-0-aljater.img
Note: For Windows 10 users who use the powershell and not cmd
The command will become:
PHP:
./ fastboot flash recovery recovery.img
Note: Test if it works in the JETER variant (I do not have that device, I have the ALJETER variant)
XDA: DevDB Information
twrp, Tool/Utility for the Moto G6 Play (Aljeter)
Contributors
TWRP Team
Me
Version Information
Status: Stable
Stable Release Date: 2019-06-03
Created 2019-06-03
Last Updated 2019-06-03
So this will allow flashing of A/B roms?
kwiksi1ver said:
So this will allow flashing of A/B roms?
Click to expand...
Click to collapse
I am not bad Moto G6 Play as the Moto G6 only have a / Vendor type A partition, you can also install custom rom (GSI) from an image file.
In the same way, I will try to compile a TWRP that supports the partition / vendor as a defect so that a custom roms GSI installation can be performed from a zip file.
Thread cleaned!
Kanged work must be addressed by developer himself using the report button or contacting any Mod. Future public posts will be cleaned again and users will be addressed.
Thank you
Will this TWRP be available on unofficialtwrp.com/
Do you know if there will ever be a official TWRP for Moto G6 Play?
I ask because I have enough experience to follow guides, but not enough to be security smart, which is ironic as I want a custom ROM to move away from Googles spying and bloat.
DulfaGreyny said:
Will this TWRP be available on unofficialtwrp.com/
Do you know if there will ever be a official TWRP for Moto G6 Play?
I ask because I have enough experience to follow guides, but not enough to be security smart, which is ironic as I want a custom ROM to move away from Googles spying and bloat.
Click to expand...
Click to collapse
To install a Custom ROM you do not need an build official TWRP , because in my opinion the cell phone should go better with the 64bit architecture and thus the device would be more useful, but since currently there is no support for the device itself, you can try installing a GSI ROM, apparently everything works, in LineageOS 16 Moto Actions do not work.
Don't use this.. yes it works, because the developer made sure of it, but this isn't the developer,
This guy was kindly helped by the developer and then stole that developers work. Then turned around and posted it here, risking all of your devices since he has no clue about it, just for a little attention.
Nice guy right?
If it seems like he's talking gibberish, it's cause he is. He has no clue how any of this works. But yes an official is in the works. In the meantime, thank god this guys an idiot and didn't erase his footsteps, suck it Allan
Alan1231999 said:
To install a Custom ROM you do not need an build official TWRP , because in my opinion the cell phone should go better with the 64bit architecture and thus the device would be more useful, but since currently there is no support for the device itself, you can try installing a GSI ROM, apparently everything works, in LineageOS 16 Moto Actions do not work.
Click to expand...
Click to collapse
I have installed custom roms before and as starkiller2 pointed out you make no sense. My question was about the security and quality control of what you have offered -which for all I know could be invasive or broken. Hence I was seeking some kind of verification of legitimacy; which you have given me albeit the opposite of what you may have intended.
It appears that some concern is shared by starkiller2 -thanks
I maintain my stance that Allan can choke on it
Give a link to twrp 3.3.1 I can not download
bronislav808 said:
Give a link to twrp 3.3.1 I can not download
Click to expand...
Click to collapse
That's because it was stolen work bud.
Why is this thread even up? @mods
Kuntitled said:
Why is this thread even up? @mods
Click to expand...
Click to collapse
When I tried taking my first guide thread down a mod told me they don't remove posts for archival purposes or something like that. Might be different though for the situation involved with this thread though
Kuntitled said:
Why is this thread even up? @mods
Click to expand...
Click to collapse
The mods were supposedly "investigating" it but never did anything. And Allan's ***** ass disappeared

Categories

Resources