Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Learn More

How do I correctly update ZTE Open C

  • 4 ответа
  • 1 имеет эту проблему
  • 1 просмотр
  • Последний ответ от Ralph Daub

more options

Hello. I have a ZTE Open C with unlocked bootloader and a 1.4 build installed. I re-flashed to 1.4 instantly after the phone was delivered. My question is, how do I correctly update it from source without loosing my data? Currently, I'm pulling the latest source from git, doing this: git pull ./repo sync -d And then flash it to the phone using. ./build.sh gecko ./flash.sh gecko Than a change directory to gaia and build/flash it using: make clean && make install-gaia

All flashes okay, without any errors but I still got old build identified in More Information: 20140703092209 instead, the Git commit info is updated: 2014-07-07 f2c11876

Does this mean I'm correctly updating if the git commit info changes? Or something is wrong?

Thanks in advance.

Hello. I have a ZTE Open C with unlocked bootloader and a 1.4 build installed. I re-flashed to 1.4 instantly after the phone was delivered. My question is, how do I correctly update it from source without loosing my data? Currently, I'm pulling the latest source from git, doing this: git pull ./repo sync -d And then flash it to the phone using. ./build.sh gecko ./flash.sh gecko Than a change directory to gaia and build/flash it using: make clean && make install-gaia All flashes okay, without any errors but I still got old build identified in More Information: 20140703092209 instead, the Git commit info is updated: 2014-07-07 f2c11876 Does this mean I'm correctly updating if the git commit info changes? Or something is wrong? Thanks in advance.

Выбранное решение

Ok, I'm answering this question myself as I finally was able to reproduce a wallpaper bug before it got fixed. So yes, in general the Git commit info change means that the system got updated.

Прочитайте этот ответ в контексте 👍 1

Все ответы (4)

more options

Выбранное решение

Ok, I'm answering this question myself as I finally was able to reproduce a wallpaper bug before it got fixed. So yes, in general the Git commit info change means that the system got updated.

more options

Hi ANTONBORODA,

I'm happy to hear that you were successful in manually updating your device, and thanks for sharing this knowledge in the SUMO forums! Welcome to the community, your contribution is very much appreciated.

Please keep in mind that although it can be exciting to test new versions, manually updating the system is not officially supported and can end up bricking the device in some cases.

Please let us know if you have any user-related questions in the future!

Thanks,

- Ralph

more options

@Ralph what was the point of your comment? You posted it 2 days after he answered his own question, and dont really provide any new information? Are you required to respond to all questions, even if you have nothing to add?

more options

Hi svnpenn,

The point of my comment was to express my excitement that ANTONBORODA was able to manually update his device, and to show my appreciation that he shared his findings in the forums.

These support forums are geared towards user-facing issues. This means that development, manual updates, and porting of devices is not usually supported.

This was the second reason for my comment: to set the correct expectations for users with developer-related questions who may come to this thread through Google searches. Users looking for this type of support are more likely to find help in developer-related pages like MDN or StackOverflow.

However, the main reason for replying was to welcome ANTONBORODA to the community and recognize his contribution to the support forums (by sharing his findings). I hope this helps you understand my reasoning.

- Ralph