Database Users

my p10 lite bricked [unbrick how-to]

<how-to unbrick>(TRY THIS AT YOUR OWN RISK)
this method is useful for was-lx2j,and "can boot stock rom" but "Almost apps not found".
1 )back to your stock recovery using
Code:
fastboot flash recovery RECOVERY.ing
2 )In huawei firmware finder,open the proxy server
3 )follow the proxy server's instraction
(POINT:USE THE LINK TO YOUR LAST STOCK FIRMWARE'S FULLOTA CHANGELOG)
exemple:my stock firmware's version before flashing custom rom and bricking is WAS-LX2JC635B175,so I choose it
Code:
Instructions.
1. Enter a link to the changelog of firmware in the "Firmware for install" field and click "Set".
2. Click the button "Register for update". Registration takes place by IP address.
3. After registration, you need to change your DNS address to 81.177.139.39. Dont forget save your original dns settings for restore it later. (You can change it in network settings, router settings or setup like proxy without port in hisuite).
4. Go to Huawei Updater in phone or go to HiSuite and press check update. After that you should get update.
5. After install dont forget to reset the dns settings to the original state.
4 )reboot your p10lite to huawei erecovery (or boot system)
5 )press "download ~"and update your system(or do a system update)
6 )go to stock recovery and do a factory reset
7 )DONE! reboot to system and phone will successfully booting!!!!!!
any questions,reply to this therd or PM me
<oliginal OP:↓>
edit:MY PHONE WAS FULLY UNBRICKED!!!
THX FOR ALL ADVICE!!!
my p10 lite (WAS-LX2J) was bricked...
1)I flashed a lineage unofficial build.
2)I flashed vendor as dd command from twrp shell.
3)I tested the rom
4)I wanted to back to stock rom,so I flashed system.img,cust.img,boot.img from stock firmware using huawei update extractor and fastboot.
5)I wanted to flash vendor but fastboot says command not allowed.
6)reboot to twrp and flash stock vendor as dd,but it fails(partition broken)
now,my p10 lite bricked...
Anyone has solution or twrp backup(system,cust,vendor,boot)???
any answer is welcome....
sorry for my bad english

Can you still get into TWRP? If you go into wipe, advanced, if you select something there you have the option to fix or repair that file system. I would be guessing if I knew what you needed to select though. Any risk is down to you.
Maybe that will fix your error? I have to sometimes do this to the 'data' file system to be able to boot lineageOS.
If you do manage to restore stock filmware successfully please share your steps on the p10 lite forum.

stonedpsycho said:
Can you still get into TWRP? If you go into wipe, advanced, if you select something there you have the option to fix or repair that file system. I would be guessing if I knew what you needed to select though. Any risk is down to you.
Maybe that will fix your error? I have to sometimes do this to the 'data' file system to be able to boot lineageOS.
If you do manage to restore stock filmware successfully please share your steps on the p10 lite forum.
Click to expand...
Click to collapse
yes,I can get into twrp so I repaired filesystem.
I fixed filesystem:vendor and system.
I wiped all data
still bricked

Find out from the OP on this thread if there is a Service firmware for your device. Hopefully you'll be able to fix your device with a service firmware.

miz_pimp said:
Find out from the OP on this thread if there is a Service firmware for your device. Hopefully you'll be able to fix your device with a service firmware.
Click to expand...
Click to collapse
Yes I already saw it but my phone was not found…
but my phone unbricked by another method!!!
thx for your advice
sorry for my bad english

hayabusa2yk said:
Yes I already saw it but my phone was not found…
but my phone unbricked by another method!!!
thx for your advice
sorry for my bad english
Click to expand...
Click to collapse
You have c635 or c719?
I have backups was-lx2jc635b174 hw/jp. Without data and system.

rambik33 said:
You have c635 or c719?
I have backups was-lx2jc635b174 hw/jp. Without data and system.
Click to expand...
Click to collapse
yes,and firmware is same!
thx very much!
I unbricked my phone,but sadly my phone's frp unlocked…
so i'm happy if you send backup!
sorry for my bad english

hayabusa2yk said:
yes,and firmware is same!
thx very much!
I unbricked my phone,but sadly my phone's frp unlocked…
so i'm happy if you send backup!
sorry for my bad english
Click to expand...
Click to collapse
https://yadi.sk/d/8bBC7la-3Pwv8T

rambik33 said:
https://yadi.sk/d/8bBC7la-3Pwv8T
Click to expand...
Click to collapse
thx very much!!!

Hey, I have the same phone and problem (I tried to installl a lineageos). I want to go back to stock rom.
Where can I get the files for this, thanks! (stock recovery, imgs, firmware etc)

mount_E said:
Hey, I have the same phone and problem (I tried to installl a lineageos). I want to go back to stock rom.
Where can I get the files for this, thanks! (stock recovery, imgs, firmware etc)
Click to expand...
Click to collapse
you can download it with huawei firmware finder!
here:xda
If you want help,contact me at PM so I'll help you...

[TWRP][FULL BACKUP]HUAWEI Y7 trt-lx1, trt-lx3

As i was able to flash the custom recovery ( see HERE ) on my TRT-LX1, i thought i would share my full TWRP backup.
Use at own risk !
This backup contains : aboot, boot, cust, firmware, product, recovery,system,vendor, version (if needed other files can be provided but with those ones you should be able to restore your system backup)
TWRP BACKUP : TRT-LX1 : https://androidfilehost.com/?fid=962187416754455038
Also the TRT-LX3 can be found here : https://mega.nz/#!Bd5W3ALI!cJ_3F5pISoyGChrw-p1hrD87H-_0z62VExSL9D3zb8c
Btw, if other backups are available for other Y7 models, feel free to share here as a restore point

i tried on my system but it restarted twice then i had to factory reset the device and now i cant get past the emui getting started page because it restarts endlessly. Any help?

Hi. Do you have the /data/hw_init/ folder ? please

dany0808 said:
Hi. Do you have the /data/hw_init/ folder ? please
Click to expand...
Click to collapse
As far as i can see there is no hw_init folder in data.
The only init folder is in system/etc

Thank you bro so far so good :good:

dang... Everything works but headset, had the same issue with the headset on another backup.

ashd999 said:
dang... Everything works but headset, had the same issue with the headset on another backup.
Click to expand...
Click to collapse
Did your headset worked before ?
Do you have a LX1 ?
Perhaps the headset restore is in another sub-partition. Should look into that.
EDIT : tested with headset and works flawless

raystef66 said:
Did your headset worked before ?
Do you have a LX1 ?
Perhaps the headset restore is in another sub-partition. Should look into that.
EDIT : tested with headset and works flawless
Click to expand...
Click to collapse
No I'm on LX2 its not your backup thats the problem but something I probably messed up before somehow :/
Yes headset worked on stock rom until I bricked it.

ashd999 said:
No I'm on LX2 its not your backup thats the problem but something I probably messed up before somehow :/
Yes headset worked on stock rom until I bricked it.
Click to expand...
Click to collapse
Yeah i see now that you were the one that bricked the LX2.
Did you used all of my backup to restore ? And how did you ? With the twrp ? Just to know for the record

raystef66 said:
Yeah i see now that you were the one that bricked the LX2.
Did you used all of my backup to restore ? And how did you ? With the twrp ? Just to know for the record
Click to expand...
Click to collapse
Yes I used your backup after trying this one https://mega.nz/#!Bd5W3ALI!cJ_3F5pISoyGChrw-p1hrD87H-_0z62VExSL9D3zb8c
Yours works the best for my model, and yes I restored with TWRP.

ashd999 said:
Yes I used your backup after trying this one https://mega.nz/#!Bd5W3ALI!cJ_3F5pISoyGChrw-p1hrD87H-_0z62VExSL9D3zb8c
Yours works the best for my model, and yes I restored with TWRP.
Click to expand...
Click to collapse
Alright, noted !
Btw, the other backup is for the LX3 and as someone would do a restore with it, just check all but not the .img (like system.img, vendor.img...) ones. These are not necessary to check as the other ones contain all necessary data. Just saying
My backup, the TRT-LX1 just contains the ones you'll need. You can check all by default, or less if you want a selected part to restore.

I have brick my huawei y7
Hello, good afternoon, I have downloaded your backup of the LX3 which is my phone model of the Y7 but I only have the TWRP where I can access. I have tried copying the extractable file from the backup as well as extracting the files and putting them in the root folder, but the files only come out in the file manager mode and when I want to restore, I do not get any file to restore. I personally think I'm doing it wrong because I'm not a genius in this restore backups because I've never done it but now that I have the opportunity to recover my phone I would like to know how to use it and leave it to my Huawei Y7.

Dbustaman3 said:
Hello, good afternoon, I have downloaded your backup of the LX3 which is my phone model of the Y7 but I only have the TWRP where I can access. I have tried copying the extractable file from the backup as well as extracting the files and putting them in the root folder, but the files only come out in the file manager mode and when I want to restore, I do not get any file to restore. I personally think I'm doing it wrong because I'm not a genius in this restore backups because I've never done it but now that I have the opportunity to recover my phone I would like to know how to use it and leave it to my Huawei Y7.
Click to expand...
Click to collapse
Take a test backup with TWRP. That will give you the right folder name to place the lx3 backup into.
When restoring, you can check all. But don't check the img's. It's not needed. Don't know if you should check the efs. Better don't. Just try out

do you have modem.img backup or efs backup please

ADB-1 said:
do you have modem.img backup or efs backup please
Click to expand...
Click to collapse
Here you go : https://forum.xda-developers.com/general/general/twrp-huawei-y7-trt-lx1-boot-modem-t3738465

Do you have custom rom for trt-lx1? For example, lineage os?

ree

TRT-L21A
do u have any backup or roms for trt-l21a?

hi how did you restore the backup. im using trt-lx3 and accidentally wiped the OS
Hi how did you restore the backup. Im using trt-lx3 and accidentally wiped the OS off of the devices using twrp
---------- Post added at 09:59 PM ---------- Previous post was at 09:51 PM ----------
Hi i accidentally wiped my os off of the phone using twrp, was wondering if u can explain how to install. sorry im still a bit new to rooting and these things

Huawei y7 trt lx2 0 openline
hi anyone here knows hot to openline this devices?
please help me, if rooting can solve my problem?
i will appreciate your help
thanks in advance

[FIX] Fix for missing LTE+ (4.5g) and VoLTE after unlocking H815TR models with UsU

* At the very beginning, I'd like to tell that I only have H815TR model. I don't know if there is any other variant(s) of G4 which supports VoLTE. If your device supports it, and VoLTE is missing for you too, after taking full backup, you may try as well but use the cust file from your backup you took before UsU'ing your device. I can say there is no risk(s) for like losing your imei, or hard brick etc.
This guide is only for Nougat stock/stock based(do not try on stock based roms until I update the thread. Someone reported something goes wrong w/ stock based roms) rom(s) and H815TR model. Why it is only for TR variant is that I do only have cust partition from TR model. Also, why this is for stock rom is that I've just found out a way to make them working and haven't tested with any other rom(s). As soon as I test, I'll add information about them and let you know.
Basically, here we do have 2 choices:
The first option
Use stock boot image with stock Nougat modem and the latest Lollipop baseband.
The second option (which I recommend)
Use stock Nougat modem and baseband with UsU kernel
The first way:
Download
Stock boot image
Stock modem image
Cust image
Latest UsU compatible baseband
Backup your boot image [optional but recommended]
Launch a command promt/powershell/terminal on your PC
Connect your phone to your PC and type following commands
adb reboot bootloader
fastboot erase boot
fastboot flash boot stock-nougat-boot-berkantkz.bin
fastboot erase modem
fastboot flash modem stock-nougat-modem-berkantkz.bin
fastboot erase cust
fastboot flash cust cust-berkantkz.bin
Disconnect your device, pull out the battery, and boot into TWRP
Flash "H815_UsU_baseband_flash-in-twrp.zip" and reboot
Skip to common steps
The second way:
Download
Stock modem image
Cust image
Latest UsU compatible boot image
Backup your boot image [optional but recommended]
Launch a command promt/powershell/terminal on your PC
Connect your phone to your PC and type following commands
adb reboot bootloader
fastboot erase boot
fastboot flash boot <downloaded-image-name>.img
fastboot erase modem
fastboot flash modem stock-nougat-modem-berkantkz.bin
fastboot erase cust
fastboot flash cust cust-berkantkz.bin
fastboot reboot
Skip to common steps
In common:
After your device boots up;
Go to mobile networks (hold down the mobile data icon in quick toggles)
Click on "Acces Point Names"
Open the menu and click on "Restore default settings"
Go back and enable VoLTE.
See the attachments for proof that proves it does work with UsU'd G4
Thanks:
@steadfasterX (for his suggestions, helps, and everything! You owe him for having an unlocked G4 w/ everything working!)
All should be fine now. Check both of them. Should you need any help, feel free to ask. I'll try to do my best. Please do not forget to leave me a thanks. That makes me happy :fingers-crossed:
Also, here I must inform you that if you had rooted your device with any root manager such as SuperSU, Magisk etc, you have to flash it again to have root access again. You have to do this since we erase and re-write boot images w/o changes those are required for root manager(s) to work.
Additional about VoWiFi (root required):
As @steadfasterX claimed and confirmed VoWiFi to work, use the commands below to enable it (I've personally tested but didn't work for me. It may depend on the operator and maybe the wifi you connected)
adb shell
su
setprop persist.dbg.wfc_avail_ovr 1

Thanks for the fixe !
I have the same problem with my LG H815 EUR since i got v29a. No lte+ "4g+" just lte "4g".
When i'm on v20i Fr i got the lte+ "4g+".
H815 EUR, Bootloader unlock, Root with magisk. I already check my APN and is fine French operator "Free".
Someone have tips?

xenouch said:
Thanks for the fixe !
I have the same problem with my LG H815 EUR since i got v29a. No lte+ "4g+" just lte "4g".
When i'm on v20i Fr i got the lte+ "4g+".
H815 EUR, Bootloader unlock, Root with magisk. I already check my APN and is fine French operator "Free".
Someone have tips?
Click to expand...
Click to collapse
Open a shell with root privileges and paste here the output of
Code:
ls /cust

Awesome fix! Verizon G4 VS986 also supports VoLTE and it is not working. VS986 only has stock MM or L available at the moment as all other roms do not work correctly. What would be the steps to get VoLTE working?

berkantkz said:
Open a shell with root privileges and paste here the output of
Code:
ls /cust
Click to expand...
Click to collapse
Code:
p1:/ $ su
p1:/ # ls /cust
OPEN_COM cust_group_mapping.cfg open_path_mapping.cfg
client_id.xml cust_path_mapping.cfg userdata_files.cfg
cust.ubid lost+found
p1:/ #
This is the result

fates13 said:
Awesome fix! Verizon G4 VS986 also supports VoLTE and it is not working. VS986 only has stock MM or L available at the moment as all other roms do not work correctly. What would be the steps to get VoLTE working?
Click to expand...
Click to collapse
Have you UsU'd your device? If so, did you take full backup before UsU'ing it?
xenouch said:
Open a shell with root privileges and paste here the output of
This is the result
Click to expand...
Click to collapse
The config files are available for you.
When you go Access point names, do you see an APN whose name contains ims and which is not selectable?

berkantkz said:
Have you UsU'd your device? If so, did you take full backup before UsU'ing it?
The config files are available for you.
When you go Access point names, do you see an APN whose name contains ims and which is not selectable?
Click to expand...
Click to collapse
No juste have my 2 Free Apn and have the same on v20i Fr... Very strange problem.

berkantkz said:
Have you UsU'd your device? If so, did you take full backup before UsU'ing it?
The config files are available for you.
When you go Access point names, do you see an APN whose name contains ims and which is not selectable?
Click to expand...
Click to collapse
Yup I have a backup but there is no cust.bin. I checked the MM KDZ for VS986
and there is no cust partition there either.

xenouch said:
No juste have my 2 Free Apn and have the same on v20i Fr... Very strange problem.
Click to expand...
Click to collapse
Well, before flashing my backup cust partition, i wasn't able to use 4.5g either. After flashing it, 4.5g started to work. Although you currently have the configs, it doesn't work for you. It seems yeah as you said a bit strange. I get 4.5g on both stock M and N.
Can you check if you have a cust.bin inside stock v20i kdz/tot file?
fates13 said:
Yup I have a backup but there is no cust.bin. I checked the MM KDZ for VS986
and there is no cust partition there either.
Click to expand...
Click to collapse
Well, find someone who uses stock and take full backup using SALT. When you see that cust.bin is generated, it's okay to cancel the operation. Grab that cust.bin and flash it to your device using
Code:
fastboot erase cust
fastboot flash cust cust.bin
Then the same thing. Go to APNs and reset to default.

berkantkz said:
Well, before flashing my backup cust partition, i wasn't able to use 4.5g either. After flashing it, 4.5g started to work. Although you currently have the configs, it doesn't work for you. It seems yeah as you said a bit strange. I get 4.5g on both stock M and N.
Can you check if you have a cust.bin inside stock v20i kdz/tot file?
Well, find someone who uses stock and take full backup using SALT. When you see that cust.bin is generated, it's okay to cancel the operation. Grab that cust.bin and flash it to your device using
Then the same thing. Go to APNs and reset to default.
Click to expand...
Click to collapse
Keep in mind that only the models which have a gpt compatibility for the h815 will work like that. Only those have a cust partition. All others have a carrier partition so you may need to adjust the guide for those accordingly..
As another hint: it is important that the users use their own version of the cust/carrier partition and not yours for the TR. It contains only stuff for your country and carrier!
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Keep in mind that only the models which have a gpt compatibility for the h815 will work like that. Only those have a cust partition. All others have a carrier partition so you may need to adjust the guide for those accordingly..
As another hint: it is important that the users use their own version of the cust/carrier partition and not yours for the TR. It contains only stuff for your country and carrier!
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Yeah, that's why I'm asking if they've cust partition. I don't know about carrier partition since you know I don't have it.
Yeah, I know. See above what I said for VS986.

berkantkz said:
Yeah, that's why I'm asking if they've cust partition. I don't know about carrier partition since you know I don't have it.
Yeah, I know. See above what I said for VS986.
Click to expand...
Click to collapse
Yea I just wanted to make it easy to identify
SALT GPT compatibility h811 means carrier
SALT GPT compatibility h815 means cust
Sent from my LG-H815 using XDA Labs

berkantkz said:
Well, before flashing my backup cust partition, i wasn't able to use 4.5g either. After flashing it, 4.5g started to work. Although you currently have the configs, it doesn't work for you. It seems yeah as you said a bit strange. I get 4.5g on both stock M and N.
Can you check if you have a cust.bin inside stock v20i kdz/tot file?
Well, find someone who uses stock and take full backup using SALT. When you see that cust.bin is generated, it's okay to cancel the operation. Grab that cust.bin and flash it to your device using
Code:
fastboot erase cust
fastboot flash cust cust.bin
Then the same thing. Go to APNs and reset to default.
Click to expand...
Click to collapse
Yes i have 2 cust.bin. This is what i have inside

xenouch said:
Yes i have 2 cust.bin. This is what i have inside
Click to expand...
Click to collapse
Well, this most likely seems like an apk file. Do you have carrier partition inside the kdz as steadfasterX told above? Maybe carrier is used for your device.

berkantkz said:
Well, this most likely seems like an apk file. Do you have carrier partition inside the kdz as steadfasterX told above? Maybe carrier is used for your device.
Click to expand...
Click to collapse
No i dont have any carrier.bin. This rom is for H815 EUR.
I use "LG-H815_Official_v29A_keepsTWRP-LAF.zip" and no cust.img inside. Inside the "LG-H81520G-Flashable.COMPLETE.zip" i have the cust.img.
When i flash the v29a i do full wipe. I extract v29a KDZ/TOT to compare.

xenouch said:
No i dont have any carrier.bin. This rom is for H815 EUR.
I use "LG-H815_Official_v29A_keepsTWRP-LAF.zip" and no cust.img inside. Inside the "LG-H81520G-Flashable.COMPLETE.zip" i have the cust.img.
When i flash the v29a i do full wipe. I extract v29a KDZ/TOT to compare.
Click to expand...
Click to collapse
Open the cust image inside LG-H81520G-Flashable.COMPLETE.zip file with 7-zip and paste a screenshot, please.

This is the link for extracted v29a and v20p. Thanks to SteadfasterX.
http://leech.binbash.it:8008/stock/LG/h815/
Im at work i put screenshots After.
---------- Post added at 05:35 PM ---------- Previous post was at 05:01 PM ----------
The cust.img inside the v20g zip

xenouch said:
This is the link for extracted v29a and v20p. Thanks to SteadfasterX.
[url]http://leech.binbash.it:8008/stock/LG/h815/[/URL]
Im at work i put screenshots After.
---------- Post added at 05:35 PM ---------- Previous post was at 05:01 PM ----------
The cust.img inside the v20g zip
Click to expand...
Click to collapse
Well, I've downloaded the cust image from here and it seems okay to me.
What can I suggest you to is that if you're saying it was working on V20i Fr, extract cust.bin from that V20i, and flash it using
Code:
fastboot erase cust
fastboot flash cust cust.bin
Check what's inside that cust extracted from v20i. It should be similar to the ones I added as screenshot.
Edit: I downloaded V20i France version to see. It is the same with which I said looks like an apk file. Maybe it's due to the extractor we use. I remember steadfasterX saying that the other kdz extractors don't extract well than SALT's inbuilt extractor.
I'll try to extract with SALT and see again.

steadfasterX said:
Keep in mind that only the models which have a gpt compatibility for the h815 will work like that. Only those have a cust partition. All others have a carrier partition so you may need to adjust the guide for those accordingly..
As another hint: it is important that the users use their own version of the cust/carrier partition and not yours for the TR. It contains only stuff for your country and carrier!
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
I flashed the carrier partition from my Lollipop stock backup before UsU and it didn't work. I then extracted the carrier partition from 2BA MM KDZ for VS986, flashed it, removed VoLTE from my phone package on Verizon.com, added it back on, and it is now working! Not sure which of those steps got it working but I'm extremely happy as it was annoying losing data every time I made a phone call. Thanks!

fates13 said:
I flashed the carrier partition from my Lollipop stock backup before UsU and it didn't work. I then extracted the carrier partition from 2BA MM KDZ for VS986, flashed it, removed VoLTE from my phone package on Verizon.com, added it back on, and it is now working! Not sure which of those steps got it working but I'm extremely happy as it was annoying losing data every time I made a phone call. Thanks!
Click to expand...
Click to collapse
Could you please provide me/us the carrier partition for me to share it here for the others who suffers from missing VoLTE?
Please pm me your Google Mail address. I'll let you make changes on my drive folder where I uploaded files for H815.

[URGENT] Need some help with weird crash

Hi, I'm using a huawei p10 Lite rooted with twrp Recovery. by mistake, I wipe the recovery partition of twrp while i was in twrp. Now i can't use the recovery or fastboot, and my smartphone seems to be "unauthorized" in the adb device's list.
My last try was download and install stock firmware, i think this may repair recovery and kernel partition, but i can't move to microsd card because (i think) is upper than 4GB, and don't let me copy the folder dload.
PD: I can boot the custom rom without problems, but i can't use recovery or fastboot
need some help please!!
thanks
Edit: I fixed with anohter update.app with less than 4GB (3.6 GB)

u have rooted your phone? so i think it's possible to "dd" the recovery back.
e.g.
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0pxx
Click to expand...
Click to collapse
(i don't know which partition is for recovery, so i put "xx" in it)
are u on emui5 or emui8?
and please remove your "question" feature in your post. that's maybe the reason why nobody post an answer ...

Sorry, I forgot to say that i fixed it. I found another rebrand firmware of 2.6 GB, solve it.
Thanks anyway for the answer!

[FIRMWARE][skipjack] TicWatch C2 Dump image

Guys who are using TicWatch C2:
I dumped all the image from the device which are required for the OTA in case someone need it, Chinese version only, PWDS.190212.008.
Chinese version only, PWDS.190212.008 and PWDS.190618.001.A1.
https://mega.nz/#F!4kE2zAoS!uoi8jZ0y_7k0dXJccd9LmA
Anyone who own a global version could also share with it here to save other's device.
Required images for OTA:
aboot.img
cmnlib.img
modem.img
rpm.img
tz.img
boot.img
keymaster.img
recovery.img
sbl1.img
system.img
vendor.img
How to flash:
0. extract the zip file.
1. fastboot flash <image_name> <image_name>.img

I hope someone can share the international version, thanks guys

THIS IS MY TWRP BACKUP OF MY TICWATCH C2 INTERNATIONAL ANDROID 8.0 OWDS.181126.001
https://www.mediafire.com/file/c6cuj...CKUPS.rar/file
This is my stock copy, I backed up everything TWRP allowed me to, just in case.
I installed the Ticwatch C2 rom, and I'm getting pretty solid battery life, but I'm not able to update to PIE, since I get an error as I mentioned, even when I flash back to stock, and lock the bootloader, so we're confined to custom roms from now on, or to TWRP backups of PIE.
So if someone has a TWRP, or a stock firmware backup of some sort of PIE for the ticwatch c2, that would be amazing.

Syndor said:
THIS IS MY TWRP BACKUP OF MY TICWATCH C2 INTERNATIONAL ANDROID 8.0 OWDS.181126.001
https://www.mediafire.com/file/c6cuj...CKUPS.rar/file
This is my stock copy, I backed up everything TWRP allowed me to, just in case.
I installed the Ticwatch C2 rom, and I'm getting pretty solid battery life, but I'm not able to update to PIE, since I get an error as I mentioned, even when I flash back to stock, and lock the bootloader, so we're confined to custom roms from now on, or to TWRP backups of PIE.
So if someone has a TWRP, or a stock firmware backup of some sort of PIE for the ticwatch c2, that would be amazing.
Click to expand...
Click to collapse
That might because the OTA script check more than only boot, system or vendor partition, and that leads to the exception.

simonsmh said:
That might because the OTA script check more than only boot, system or vendor partition, and that leads to the exception.
Click to expand...
Click to collapse
What else does it check for, can we fix it ?

Syndor said:
What else does it check for, can we fix it ?
Click to expand...
Click to collapse
You should be able to get the error report and see which partition doesn't pass verification from the recovery log. Also I updated the list of images that OTA required.

Syndor said:
THIS IS MY TWRP BACKUP OF MY TICWATCH C2 INTERNATIONAL ANDROID 8.0 OWDS.181126.001
Click to expand...
Click to collapse
Link that you provided is not working, could you fix it please? My watch do not want to boot with custom fw

maximzinchuk said:
Link that you provided is not working, could you fix it please? My watch do not want to boot with custom fw
Click to expand...
Click to collapse
I'll reupload when I get home
---------- Post added at 05:57 PM ---------- Previous post was at 05:06 PM ----------
Here you go:
TWRP BACKUP OF MY TICWATCH C2 INTERNATIONAL ANDROID 8.0 OWDS.181126.001
https://mega.nz/#!WthVGKIa!XoeOFs0HK28D4SdHJGpPxXO3xytf-djePefB4DvwAsc

Anyone has a backup of the international version yet? one that would allow me to OTA?

Well you guys plz remember to backup before trying custom roms

Anyone can share how to dump image ? I own a Chinese ver C2, and want to do a backup before flashing international FW.
THX

V_tunes said:
Anyone can share how to dump image ? I own a Chinese ver C2, and want to do a backup before flashing international FW.
THX
Click to expand...
Click to collapse
I use dd under TWRP recovery. You can also use TWRP backup.
As some users report incompatible of international build. Also there is no Pie rom for our global C2.
Can you read Chinese? If you just want to use Google play, use this:
https://github.com/simonsmh/ticwatch-googleify

simonsmh said:
I use dd under TWRP recovery. You can also use TWRP backup.
As some users report incompatible of international build. Also there is no Pie rom for our global C2.
Can you read Chinese? If you just want to use Google play, use this:
https://github.com/simonsmh/ticwatch-googleify
Click to expand...
Click to collapse
Yes, I'm Chinese. So the things I can do is unlock BL first, then boot into TWRP to backup, flash TWRP, Magisk & install the github module, right ?
Thanks again.

V_tunes said:
Yes, I'm Chinese. So the things I can do is unlock BL first, then boot into TWRP to backup, flash TWRP, Magisk & install the github module, right ?
Thanks again.
Click to expand...
Click to collapse
Yes exactly.

simonsmh said:
Yes exactly.
Click to expand...
Click to collapse
Hi I tried to install the module from MagiskManager on the watch, it says not a Magisk module.

V_tunes said:
Hi I tried to install the module from MagiskManager on the watch, it says not a Magisk module.
Click to expand...
Click to collapse
解压后，将里面的文件用zip

simonsmh said:
解压后，将里面的文件用zip
Click to expand...
Click to collapse
感谢回复，我安装这个module后重启，手表无法进行操作，不能打开应用列表，下滑也反应，感觉几秒手表会自己闪一下。

[No message]

你得重置手表重新配对
1. twrp双清
2. 刷magisk
3. 立即紧接着刷模块
4. 开机使用wear OS国际版配对

simonsmh said:
你得重置手表重新配对
1. twrp双清
2. 刷magisk
3. 立即紧接着刷模块
4. 开机使用wear OS国际版配对
Click to expand...
Click to collapse
感谢，弄好了。可以连接国际版wear os和上play store，但过了一会儿就不稳定了。4个边缘无法滑动，手表闪烁。