yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] Bradco:
Y don't understand with this files :

Airplane might be ic_signal_airplane_enable.xml and disable

c_portrait_from_auto_rotate and to_auto_rotate

I do exactly the same as for other files and when I restart after flashing I have the system error stopped

I can flasher several times where I have to do it in one go ?
[Android Q&A, Help & Troubleshooting] Bradco:
Have you information about the diferences between this two files ?

ic_portrait_from_auto_rotate.xml and ic_portrait_from_auto_rotate animation.xml

ic_portrait_to_auto_rotate.xml and ic_portrait_to_auto_rotate_animation.xml
[Android Q&A, Help & Troubleshooting] Tulsadiver:
This is an animated icon is all I know.
[Android Q&A, Help & Troubleshooting] Bradco:
I ask you the question because when I add a png that corresponds to a file xml type

Ic_qs_bluetooth_off or ic_qs_bluetooth_on

Ic_qs_mobile_off or ic_qs_mobile_white

it works

But when I add a png which correspond to

Ic_portrait_from_auto_rotate.xml and ic_portrait_from_auto_rotate_animation.xml

I name the png ic_portrait_from_auto_rotate.png

when I reboot after flashing the system whas stop

I have to restore
[Android Q&A, Help & Troubleshooting] xchocolattax:
Hi.

I am new on this forum and I don't know if I posted this question right, so sorry for this.

I have this Samsung Galaxy Fame GT-S6810P of my brother's and he got it to charge and after he turned it on, the phone started to bootloop.

I first tried to get into recovery mode and it doesn't work, so I tried to flash the firmware, but this didn't work too.

When I get into recovery, I can't acces that menu with "wipe data" option. It shows me only:

-- init-recovery...

Done init-recovery

# MANUAL MODE #

--Appling Multi-CSC...

Applied the CSC-code : VNN

Succesfully applied multi-csc

And it shows the android dead picture with the red triangle.

ht tp:// imgur. com/i8j Ll7j

What anything else I could try?

Thanks for your time!
[LineageOS News & Discussion] abe s lolipup:
anyone please build or consider any theme engine for 14.1 [emoji19] [emoji19] [emoji19] [emoji19] [emoji19] feeling bored without theme make it fast hope you were fix it and giving ypu a advance [emoji12] THANKS[emoji4]

Sent from android by LØNDROID AbE
[LineageOS News & Discussion] TheDXDan:
substratum is what i use, it requires root though
[LineageOS News & Discussion] DragonSpitz:
Does lineage support substratum?
[LineageOS News & Discussion] TheDXDan:
Using it on my ONE M8 With lineage OS 14.1.

It does support it
[LineageOS News & Discussion] MJPollard:
It supports it if the developer has taken the time to incorporate the necessary changes into it. Official LineageOS doesn't support it "out of the box."
[LineageOS News & Discussion] Pasindu88:
They added the OMS commit in build tree 2 months ago. But it's still in code review. Not merged yet.

https://review.lineageos.org/#/q/theme
[LineageOS News & Discussion] ZeroPoke:
Assuming you can build your own ROM. You can cherry pick all the commits in OMS7 topic and should get you going. I was going to do this my self for my device. But I found out you cant switch build makers so easy anymore :(
[Amazfit] Neuer_User:
Huami started to lock the bootloader of the Amazfit watch in their official release 1.2.13 and 1.3.2b onwards.

If you want to keep the possibilty to flash custom software on your watch, DO NOT UPGRADE TO THESE VERSIONS. You will not be able to flash any other firmware afterwards.

PACEfied firmware is safe, and does NOT lock your bootloader.

UPDATE 14.07.17:

We have heard several times now via inofficial sources that Huami is working on an official bootloader unlocking service. So far, we, however, have no official information here.

On the other hand, Olivier (french developer on xda) has spent a significant amount of time to understand the unlocking process and we have succeeded to successfully unlock two watches. We are currently in the process of setting up a (free) unlocking web service, allowing individual xda users to unlock their watches for private usage (and accepting loss of warranty from Huami).

In case, Huami may ever come out with their service, we will stop our service, as we do not want to compete with Huami here, just filling the gap if Huami doesn't move forward with their unlocking service.

Please give us some time (we expect 2-3 weeks) to setup the unlock service.

UPDATE 7.08.17:

The unlock service is live now. Head over to https://xdaforums.com/smartwatch/amazfit/tutorial-unlock-bootloader-warning-void-t3654011, if you want your bootloader unlocked!
[Amazfit] scrubber:
Fastboot oem unlock

And the command to unlock the bootloader does not work?*

Fastboot oem unlock
[Amazfit] Neuer_User:
No, neither does

fastboot flashing unlock

I wouldn't expect Huami to put efforts into locking the bootloader and at the same time making it that easy to unlock it again. This is no coincidence. They saw our work and reacted. That's what happened. Very sad :(
[Amazfit] scrubber:
Perhaps we need to find the Fastboot oem command, they can be different for different devices

https://www.xda-developers.com/how-to-discover-hidden-fastboot-commands/
[Amazfit] Neuer_User:
Well, the strings dump shows that the "oem unlock" command seems to exist, but it indicates that an unlock code is necessary, probably based on the serial number of the watch:

strings dump extract:

oem:
unlock
serial no length is null
magic_serialno:%s
, len:%d
%02x
uncrypted_str_serialno:%s
Unlocked code sucess
Unlocked code is error
Unsupport oem cmd
FAILED: The command is not recongized
[Amazfit] Neuer_User:
So, we have three possibilities:

We find the method on how the code is calculated based on the serial of the watch

We find the location, where u-boot stores the variable, if the device is locked or not (EDIT: I would expect that in the Misc partition.)

We just reflash the old bootloader (easiest, but only temporary until next OTA update)
[Amazfit] scrubber:
Drop me stock ota 1.2.11c and 1.2.13
[Amazfit] Neuer_User:
You will only need the bootloaders (rest of the OTA is just modified apks). I will send them both (old and new one) to you via PM. It would be necessary to disassemble and understand the new bootloader (the old one does not have any OEM commands and also did not read the serial no at all, instead displayed always a dummy serial).

The serial is stored on the misc partition, so the bootloader now needs to read this partition. That's why I believe they probably stored the lock/unlock flag also there. We just need to know which byte.

Of course, if there were someone with a functioning unlock code, he could dump his misc partition before and after unlocking. That would make it pretty clear :D
[Amazfit] Cracklydisc:
so I now have no way to flash a stable version starting from 1.2.13?
[Amazfit] zbuh:
It's safe to update 1.3.2b ? English version
[Amazfit] Neuer_User:
No, also locks bootloader. But there is a good chance that we can unlock or reflash the bootloader, if someone wants to switch firmware later.
[Amazfit] barciol:
I also have this problem. I accidentally updated my Amazfit to the latest version official rom. Now I wanted to upgrade to PACEfied, but the bootloader is locked.

Do you have any ideas how to unlock it?
[Amazfit] powerforward:
Hi neur_user will I be losing the interval timer and countdown timer app that I installed in pace 1.3.1m rom if update it to 1.3.2b since you said it is bootloader locked? And can you still install developers app in 1.3.2b?
[Amazfit] Neuer_User:
Instalation of additional apps like those timer apps should still work.
[Amazfit] Neuer_User:
I have an idea how we can unlock the bootloader. In the weekend I will see if I can post a tutorial.
[Amazfit] FalconFour:
Well, I don't know what I could gain by flashing PACEified FW on my watch... all I've really been looking for is working notifications from my phone to the watch. I'm coming from wearing a Samsung Gear Live that's now worn-out, and it integrated into my life by bringing notifications to my wrist. The Amazfit was perfect for fitness, runtime, and notifications -- but notifications have never worked despite all my hacking and flashing (originally came with Chinese ROM). My saga so far is detailed here: https://www.reddit.com/r/amazfit/comments/61w4ga/most_notifications_not_coming_through_facebook

I flashed the English ROM to it tonight, and proceeded to OTA it (because newer is better, right?). The update failed as I still had the Chinese recovery on it. When it failed, I decided to try intercepting the update bundle before it rebooted. I succeeded, by kicking it into Fastboot mode using the power-button trick, then I pulled the 1.3.2b update.zip file through the "mod recovery". That file is here: https://mega.nz/#!nIBDhLrR!7nQlWsn-TF4bsMNBSaTOfimY-vo-Z2R3dSavrDp1wsA

I fixed my recovery with help of another thread, and OTA'd again to success - the darn thing took a good solid 10 minutes to run the ~33MB update! The progress bar hung the longest (~2 mins each) near the "w", "c", and at the end of "watch" in the message about not powering off the watch. Rather surprising, and wasn't sure if it hung due to my mods or what it was doing...

Hopefully this helps someone interested in looking into how the bootloader gets locked (IDK if Amazfit expected someone to intercept this, being as it's near impossible to intercept except with a MitM on WiFi), perhaps in exchange for some help with these notifications?
[Amazfit] Cracklydisc:
I'm stuck in 1.2.13 dev, if u want i can test the unlock ;)
[Amazfit] Neuer_User:
OK, will prepare it today and send it to you.
[Amazfit] barciol:
I also want test the unlock. Please contact with me ;)
[Amazfit] Neuer_User:
Just to clarify: Technically, it is not "unlocking" the bootloader. It just reflashes the old one (which did not have the locking function). That implies that the "unlocked" bootloader will only stay "unlocked" until you install the next official OTA update (which again flashes the locked bootloader). If you move to PACEfied, then that is ok, as PACEfied certainly does not lock your bootloader.
[Amazfit] Cracklydisc:
I assumed this way :)
[Amazfit] rbanaco:
Oh I accidentally also locked my bootloader... =/

I always get an error in fastboot and in adb "adbd cannot run as root in production builds"... how to flash the old bootloader without unlocking?
[Amazfit] Neuer_User:
So, guys, seems we got some bad news. Huami also patched the kernel, so that the exploit I was using to gain temporary root (what I wanted to use to reflash the old bootloader) does no longer work. We need to wait and see if a new exploit in the Android kernel will be found and then adapt that to the Amazfit.

For the time being, there is no method known to reflash the old bootloader.

As an alternative, if someone understands how the bootloader calculates the unlock code, we could calc the code ourselves. But that will be a very difficult analysis...
[Amazfit] Cracklydisc:
You think can i get the code used by update.zip file? How can the update write the boot partition?
[Amazfit] _Desconhecido__:
I acident update the Chinese version ? ,now its not possible instal the inglese ROM or a inglês tradution ???
[Amazfit] Neuer_User:
If you are now on 1.2.13 or 1.2.13e then there is currently no chance.
[Amazfit] Neuer_User:
What do you mean 'code used by the update.zip'? The update.zip contains the new (locked) bootloader, which does contain the program code to calculate the unlock code. But that means, someone would need to disassemble and understand the bootloader, which is a huge amount of work and needs special knowledge.

The update.zip can write all partitions and also the bootloader.
[Amazfit] _Desconhecido__:
I have 1.2.13e ?
[Amazfit] Javier.D:
I have also installed 1.2.13e version by error

How can we help finding the unlock code?

Could it be possible to modify the next OTA when it's released, translate it as PACEfied, and install it as if it was the original one, although the bootloader is locked?
[Amazfit] Neuer_User:
No. You cannot modify an OTA and install it.

There are currently three possible approaches for us:

Find the method how the unlock code is calculated.

Find a new root exploit to gain temporary root.

Get into the USB boot mode of the chip ("EDL" mode, "Deep flash mode", ...)
[Amazfit] MrSpeedy1:
Hello,

Because with me PACEfield is always frozen, I'm back to cn_0.9.50. Here everything works. How can I see which bootloader is present?
[Amazfit] clyphox:
Well I (like an idiot) just updated my 2 week old vanilla watch..

I was very much looking forward to running pacified (so I could "actually" customize some screens hopefully and try to extract HR data to my own API or similar..)

Well I just checked with fastboot and yes.. I am locked out grr..

I liked haumi alot more when I thought they were going to let me customise my hardware and own my data.

...anyways.. I don't know android all that well but I'll have a bash at compromising this when I'm back from my holidays (3 weeks) :laugh:

Thanks for this t
[Amazfit] Oliver3321:
hi，I'm on 1.2.14 dev can I unlock or flash back my bootloader?
[Amazfit] 1immortal:
currently not.
[Amazfit] Neuer_User:
Currently not. Sorry. Thanks to Huami blocking our efforts :(
[Amazfit] Esburri:
Hi

My watch is with 1.3.1m firmware.

I should not update to 1.3.2b right?

Thanks
[Amazfit] 5tormChild:
No, you shouldn't, if you want to use [MENTION=2750664]Neuer_User[/MENTION]'s PACEfied ROM.

If you want to stay on the 'official' path, and be able to update your watch's firmware through OTA, then you can.

I have 1.3.2b ATM, and I like it a lot, it's 100% English, no missing parts, but I liked PACEfied just as much, because it had features at least a month before the official USA firmware.

So I just locked my bootloader intentionally by installing the latest OTA (I need a daily driver, and 1.3.2b seems to be just perfect for this purpose), but I'm sure [MENTION=2750664]Neuer_User[/MENTION] and a few others will find the way to unlock the bootloader.
[Amazfit] soares34:
Any News?

i´ve locked the bootloader... 1.231e

Thanks
[Amazfit] Oliver3321:
so sad... waiting for good news:)
[Amazfit] Jappse:
I recieved mine with ROM version 1.3. App shows, "ROM version 1.3.0n". Am i screwed for the time being? :(
[Amazfit] 5tormChild:
As you can see, 1.3.2b has locked bootloader, yours is a lot older - 1.3.0n is the original USA firmware.

I don't want to say (write) that read at least a few posts before you post something... Heck, I just did that. :D
[Amazfit] Jappse:
Thanks for the advice. Since this thread is only a couple of pages I read them all. Must have missed that part that stated that my ROM 1.3.0n is an older version than the current 1.2.13 or 1.2.13e. Really easy to understand :P

So what are the benefits of the pacefied rom besides earlier access to CN builds? I read the ROM page but there are too many pages for me to go through. Mind do quick recap? Cheers
[Amazfit] Neuer_User:
Quick recap:

HUAMI LOCKS BOOTLOADER IN 1.2.13 AND 1.3.2b (taken from the title of the post :D )

The 1.2.xx line is the Chinese firmware and the 1.3.x fw is the English firmware. Both firmware lines have been locked by Huami starting from the above mentioned releases.
[Amazfit] 5tormChild:
1.3.2b is the first really usable FW for the Amazfit Pace (USA version), but it locks the bootloader, so you won't be able to flash PACEfied as of now. I like 1.3.2b, because it's fully in English, stable, and I'll get the OTA updates. The Android app of this FW-variant syncs with Strava (I hate MiFit and MiDong, which comes with the Chinese FW).

Let your watch update itself to 1.3.2b - that's the easy way -, or flash PACEfied (not PACIfied or PACEfield as someone wrote :laugh:) to keep up with the cutting edge.

BTW, the title of this topic mentions 1.3.2b, as @Neuer_User mentions.
[Amazfit] Oliver3321:
hi If I have root,how can i flash back?
[Amazfit] Renandrs:
My watch is being updated when i turn it on... is there a way to cancel that?

P.S: i can turn it off before the process completes

---------- Post added at 10:32 PM ---------- Previous post was at 10:31 PM ----------

My watch is being updated when i turn it on... is there a way to cancel that?

P.S: i can turn it off before the process completes
[Amazfit] Neuer_User:
No, If the update has already been downloaded and the install process started, there is nothing you can do.
[Amazfit] Pintomd:
Language

Hello,

At 1.2.13 is it possible to change language to english? Or is it Blocked too?
[Amazfit] [Jaco69]:
Yes, you can use adb

Inviato dal mio LG-H815 utilizzando Tapatalk
[Amazfit] tiberalex:
How to change language to English with ADB and the new locked firmware?
[Amazfit] 5tormChild:
I don't know if root needed or not (if needed, then you're doomed with a locked bootloader), but here ya go:
[Amazfit] Neuer_User:
adb shell setprop persist.sys.language en
adb reboot

But Huami has not everything translated. You will experience force closes.

EDIT: Hmm, haven't see the reply from @5tromChild :)
[Amazfit] tiberalex:
At the moment it's working...

I will let you know.

Thanks!!!
[Amazfit] thedodo:
my problem is, that my watch is on developer edition but my app is stable and I idiot dev-opt out.. so my app is for stable and my watch is dev... and Iam unable to opt back in....
[Amazfit] cagalle:
Xiaomi's phones can be unlocked sending an email to Xiaomi, why they don't give this option to the Amazfit owners? Or at least add more languages to the official firmware. [MENTION=2750664]Neuer_User[/MENTION] any hope for us?
[Amazfit] Valvoerden:
OTA Update Center could be a solution for change the rom?
[Amazfit] mso07:
Thanks for all efforts neuer_user.

Anyway to unlock bootloader from those updated 1.2.13 ? any hope??

thanks
[Amazfit] Neuer_User:
Sorry. Huami did a good job locking down the watch. ?

It is a major effort to find a way. I still have some hopes, but it will take a long time and the chances are not very high.
[Amazfit] equipo_a:
1. This does not make any verification if what you upload is an update or a downgrade, only executes the update.zip script

2. You can now sign an update.zip to update the amazfit with a custom rom. You just have to figure out how to do it with this system.

I see lots of possibilities, hopefully together with Neuer_User and members of the XDA forum we can get
[Amazfit] Neuer_User:
Yes, more or less agreed. It only validates the archive and then executes the script.

I don't agree on that. You need to sign the update.zip with the official Huami key (which you do not have). The recovery is not accepting any update.zips, if they are not signed with the official key.

If you want to try, just upload an update.zip from one of my PACEfied releases (use the full install). It will not work. :(
[Amazfit] zappomax:
So if I buy an AmazFit now (may be from GearBest), probably i get one with the new firmware onboard and there isn't any chance to flash a custom rom or the translation in my language??
[Amazfit] equipo_a:
Yes, yesterday we tried with several modified versions, without success ...
[Amazfit] Neuer_User:
That's why I need to flash a modified recovery to allow flashing my update.zips.

The watch currently is pretty well protected against flashing any non-Huami firmware.
[Amazfit] Zeljko1234:
They should, at least, offer official bootloader unlock with loosing warranty.

Moto is doing that. You want to be developer/tester/flasher... you can but do not expect us to fix your phone if you brake it. Fair enough. Only problem is if phone get broken unrelated to the flashing. But that's the risk.

Sent from my Moto X Force
[Amazfit] ichanz:
is been a month, but still no news from huami for unlocking.. :(
[Amazfit] alekos panagulis:
But I see an international Amazfit on GearBest. People who wants the English language could buy that version and just stick with official firmware. Am I wrong?

Edit: it costs only 110 euros. It seems pretty fair to me.

Inviato dal mio FRD-L09 utilizzando Tapatalk
[Amazfit] zazou41:
Advances the unlocking in 1.3.2b?
[Amazfit] zappomax:
No, you are right but anyway the custom rom is a better choice.
[Amazfit] Accidd:
Can someone point the current differences between American and Chinese version on locked bootloaders?

I have chinese version 1.12.15 with en lang set from adb but FC in settings. Of course chinese wont fix it so im wondering about switching to US watch. I heard US firmware is behind chinese but how much and which features are in CN and not in US?
[Amazfit] eremeya:
In not sure what the differences are but if you have an unlocked bootloader I would recommend just installing the PACEfied ROM.
[Amazfit] andree182:
I don't want to flash the device with locked bootloader to have a look at this, but I reckon the amazfit team ignores the kernel security updates. Thus existing local root expolit for 3.10 kernels could work. Unlocking the bootloader from there could be doable, or even superfluous (it doesn't seem that dm_verity or partition encryption are in enabled).
[Amazfit] Neuer_User:
If you know a working root exploit, please tell me. Huami closed the latest exploit, which I used to gain initial root for dumping the rom. Only one left that I know is Drammer, but that may not at all work in a mips device, and it's rather complicated to gain root by this way, if possible at all.

I'm more or less waiting for a new exploit to show up.
[Amazfit] andree182:
Hmm, I didn't think such low-key watch will have such attention from devs - seems that xiaomi takes it seriously then (which is both good and bad.. :) ).

So what about dirtycow? Or stagefright (fixed in LMY48I, but the fw is LMY47D)?

I didn't find the kernel source that's used, nor the defconfig - do we have it somewhere (I asked in a gitlab ticket too, sorry :) )?

Unless the bootloader is obfuscated, perhaps we could find the code responsible for calculating the unlock code, esp. if it's just modified u-boot. Obviously the bootloader is not on the mmc device, so some SPI NOR? In any case, I couldn't even find a dump of the OTA image so far (and don't want to risk downloading it on the watch)...
[Amazfit] Neuer_User:
Dirtycow was closed in the kernel end of December, stagefright very long time ago. Dirtycow used to work till about March for the amazfit. Then it was closed.

I can send you the bootloader. It is on the mmc. I have no experience reading assembler code. Maybe some u-boot dev can find the algorithm to calculate the unlock code from the watch serial.
[Amazfit] andree182:
Shame... thanks for the info!

Ah, I see now, it's before the 1st partition (of course...). It would be more helpful if you really could share what you know so far about the internals, seems like you understand it deeply after the few months you've been maintaining the rom stuff.

But of course, you can send the locked bootloader too. I expect you already tried to figure out how is the bootloader locked from android? Is it done from the kernel (by switching some simple flag in ROM?), or does the userspace stuff flash a completely new (locked) bootloader?
[Amazfit] Neuer_User:
The ota flashes a new bootloader. The new bootloader reads a "locked/unlocked" flag somewhere (my guess: from the misc partition) and the serial of the watch (which is also on the misc partition). The kernel is not involved, as far as I know.

Depending on the locked status, the bootloader allows the fastboot commands or not.

There is an unlock command, which requires a code. I expect that to be somehow calculated from the serial of the watch. It can be a simple algorithm or, in the worst case, a cryptographically signed hash. The validation logic is in the bootloader, so if someone can reverse engineer it from the binary bootloader, this could be the way. But that requires an experienced person for that.
[Amazfit] Accidd:
They should do same method as for Xiaomi phones. Amazefit app should bind Xiaomi account to watch and then you could request unlock permission and unlock using mi Unlock tool for phones.

Wysłane z mojego MI 5 przy użyciu Tapatalka