Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Windows 7 instruction #132

Open
the-Arioch opened this issue Nov 12, 2022 · 6 comments
Open

Windows 7 instruction #132

the-Arioch opened this issue Nov 12, 2022 · 6 comments
Labels
bug Something isn't working

Comments

@the-Arioch
Copy link

Not having SD-card at hands i can not test if the wqhole process would work, but it looks like the main stop point is solved by half-hour in Yandex.

Actually, you probably really do not need to put any STM drivers into the package, according to Microsoft docs you just need to make custom driver description file that imports the stock driver, and there already is a tool to automize it.

  1. https://github.com/pbatard/libwdi/wiki/Zadig
  2. select the device, select the "communication device class" driver
  3. install
  4. run qFlipper
  5. ...profit? hopefully

2022-11-12 22_26_04-Greenshot

2022-11-12 22_20_13-Диспетчер устройств

2022-11-12 22_19_18-qFlipper
@the-Arioch the-Arioch added the bug Something isn't working label Nov 12, 2022
@the-Arioch
Copy link
Author

Also, this green "upgrade" button is misleading now. Why could it not be red or at least amber instead, when it is known in advance upgrade is not possible?

@the-Arioch
Copy link
Author

before i found Zadig i used different tricks trying to install the supplied Bootloader driver. That was probably used by qFlipper later, so the above sequence is not a complete one to work on clean Win7 box.

However, the upgrade mostly went okay. But not quite...
I found a 2GB card and Flipper formatted it to FAT16, then i proceeded.

2022-11-12 23_48_47-qFlipper

761467 [RCY] Firmware Download @Altel0 SUCCESS
761472 [RCY] Correct Option Bytes @Altel0 START
761475 [DBG] Device is not idle, resetting...
761504 [DBG] Device reported transfer size: 1024
761504 [DBG] Bytes uploaded: 128 100%
761504 [DBG] Upload has finished.
761504 [DBG] Option Bytes mismatch @nBOOT0: this: 0x0, other: 0x1
761504 [DBG] Option Bytes mismatch @nSWBOOT0: this: 0x0, other: 0x1
761504 [DBG] Writing corrected Option Bytes...
761504 [DBG] vvv ATTENTION: Ignore errors below until matching closing message. vvv
761505 [DBG] Device is not idle, resetting...
761532 [DBG] Device reported transfer size: 1024
761806 [DBG] Failed to perform control transfer
761806 [DBG] Unable to get device status
761806 [DBG] An error has occurred during download phase
761806 [DBG] ^^^ ATTENTION: Ignore errors above until matching opening message. ^^^
761806 [DBG] vvv ATTENTION: Ignore errors below until matching closing message. vvv
761806 [DBG] ^^^ ATTENTION: Ignore errors above until matching opening message. ^^^
761888 [REG] Device went offline: VID_0x483:PID_0xdf11
762848 [REG] Detected new device: VID_0x483:PID_0x5740
762902 [DBG] Trying serial port FLIP_ALTEL0 at \\.\COM5
762902 [DBG] Using  serial port FLIP_ALTEL0 at \\.\COM5
762906 [RPC] Starting RPC session...
762959 [RPC] RPC session started successfully.
762959 [RPC] (1) System Device Info START
763757 [RPC] (1) System Device Info SUCCESS
763757 [RPC] (2) Storage Info @/ext START
763809 [RPC] (2) Storage Info @/ext SUCCESS
763809 [RPC] (3) Storage Stat @/ext/Manifest START
763862 [RPC] (3) Storage Stat @/ext/Manifest SUCCESS
763873 [RPC] (4) System Get DateTime START
763926 [DBG] Flipper time skew is -1406 milliseconds
763926 [RPC] (4) System Get DateTime SUCCESS
763926 [RPC] (5) System Set DateTime START
763978 [RPC] (5) System Set DateTime SUCCESS
763990 [RPC] Stopping RPC session...
763992 [RPC] Attempting to unload protobuf plugin...
763993 [RPC] Cannot unload protobuf plugin. This is probably OK.
763993 [RPC] RPC session stopped successfully.
763993 [REG] Device went back online
764000 [DEV] Version: 0.70.1 commit: 8d0faae8 radio: 1.13.3
764318 [RPC] RPC session is already running
791906 [RCY] Correct Option Bytes @Altel0 ERROR: Failed to write corrected option bytes: Operation timeout
791907 [DEV] Legacy Update @Altel0 ERROR: Failed to write corrected option bytes: Operation timeout
791907 [BKD] Current operation finished with error: "Failed to write corrected option bytes: Operation timeout"

The Flipper after reboot was displaying "no database found" warning.

This "connect your flipper in upgrade and repair" sounds like insult. Damn you qFlipper, you are the srervicing app, YOU have to do it, or at least you have to take me by hand and lead me step by step what i had to do exactly. Insead you through some technobabble at me and contemplate with interest if i would get out of the trap or not.

Yeah, in the end user would find what it was about, but the shock is already there.
The How-To of "reboot into recovery" should had been immediately available at the error message.

@the-Arioch
Copy link
Author

So i pulled the cable in and out, i did not use https://docs.flipperzero.one/basics/reboot, i am going in "mere user" mode, if smething did not work - turn it off then turn it on and see if the magic fixes it. So i did, pulled USB out and back in.

2022-11-12 23_57_33-qFlipper

Again, user is left alone in winter woods.

The error message could've been clickable, or the "settings" tab could have "fix it" butotn, or there could be an 4th "errors" tab enbled in such cases. Or some another obvious and immediately invokable UI.

As of now, qFlippe smatie teases user noob user "there is an error, i would tell you about it but i would not tell you nothing about it and would see if you can do a thing about it".

This dolphin has a consealed sadistic trait... I see why you love anime style so much...

@the-Arioch
Copy link
Author

the-Arioch commented Nov 12, 2022 •
edited
Loading

So i entered repair mode by the flipper box and would see if the qFlipper would do it.
I am not having much hope, i expect the above sequence just to repeat itself.
Yet i can not help wondering, why qFlipper servincing app could not reboot Flipper into repair mode itself. Tehcnically it can, but it just did not want to provide user with it...

Okay, i was way TOO optimistic. It did not. It crashed.

#129, i feel for you :-)

Сигнатура проблемы:
  Имя события проблемы:	BEX64
  Имя приложения:	qFlipper.exe
  Версия приложения:	1.2.1.0
  Отметка времени приложения:	633c319f
  Имя модуля с ошибкой:	StackHash_f548
  Версия модуля с ошибкой:	0.0.0.0
  Отметка времени модуля с ошибкой:	00000000
  Смещение исключения:	ffffffff00000000
  Код исключения:	c0000005
  Данные исключения:	0000000000000008
  Версия ОС:	6.1.7601.2.1.0.256.48
  Код языка:	1049
  Дополнительные сведения 1:	f548
  Дополнительные сведения 2:	f54850e49fa68d92750e5bd83421dc00
  Дополнительные сведения 3:	9112
  Дополнительные сведения 4:	9112a5a289fc56659f738fc83ecb1cc8

Ознакомьтесь с заявлением о конфиденциальности в Интернете:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0419

Если заявление о конфиденциальности в Интернете недоступно, ознакомьтесь с его локальным вариантом:
  C:\Windows\system32\ru-RU\erofflps.txt

2022-11-13 00_07_18-Total Commander (x64) 9 51 - LLC RPE ''Informatsia-Ekonomika''

@the-Arioch
Copy link
Author 

1951171 [RCY] Timeout with an online device, assuming it is still functional
1951171 [RCY] Set Recovery boot mode @Altel0 SUCCESS
1951171 [RCY] Co-Processor Firmware Download @Altel0 START
1951197 [DBG] Device reported transfer size: 1024
1951198 [DBG] Bytes uploaded: 2 100%
1951198 [DBG] Upload has finished.
1951198 [DBG] FUS appears NOT to be running: Error occurred, Not running.
1951198 [DBG] vvv ATTENTION: Ignore errors below until matching closing message. vvv
1951198 [DBG] Device is not idle, resetting...
1951224 [DBG] Device reported transfer size: 1024
1951498 [DBG] Failed to perform control transfer
1951498 [DBG] Bytes uploaded: 0 0%
1951498 [DBG] End of transmission.
1951498 [DBG] Upload has finished.
1951498 [DBG] Failed to read FUS status
1951498 [DBG] ^^^ ATTENTION: Ignore errors above until matching opening message. ^^^
1951498 [DBG] vvv ATTENTION: Ignore errors below until matching closing message. vvv
1951498 [DBG] ^^^ ATTENTION: Ignore errors above until matching opening message. ^^^
1981521 [RCY] Timeout with an online device, assuming it is still functional
1982388 [REG] Device went offline: VID_0x483:PID_0xdf11
1982626 [REG] Detected new device: VID_0x483:PID_0xdf11
1982654 [DBG] Device reported transfer size: 1024
1982654 [DBG] Bytes uploaded: 32 100%
1982654 [DBG] Upload has finished.
1982655 [REG] Device went back online
1982919 [DBG] Getting Co-Processor (Wireless) status...
1982920 [DBG] Device is not idle, resetting...
1982946 [DBG] Device reported transfer size: 1024
1982946 [DBG] Bytes uploaded: 2 100%
1982946 [DBG] Upload has finished.
1982946 [DBG] Current FUS state: Idle, No error.
1982947 [DBG] Attempting to flash CO-PROCESSOR firmware image...
1982947 [DBG] Sending FW_UPGRADE command...
1982947 [DBG] Failed to open file for USB device
1982947 [RCY] Co-Processor Firmware Download @Altel0 ERROR: Can't upgrade Co-Processor firmware: Failed to initiate installation.
1982947 [DEV] Full Repair @Altel0 ERROR: Can't upgrade Co-Processor firmware: Failed to initiate installation.
1982947 [DBG] Device is not idle, resetting...
1982947 [BKD] Current operation finished with error: "Can't upgrade Co-Processor firmware: Failed to initiate installation."
1982974 [DBG] Device reported transfer size: 1024
1982974 [DBG] Bytes uploaded: 128 100%
1982974 [DBG] Upload has finished.

@the-Arioch
Copy link
Author

Just like in #129 case, the second repair did not report any errors. Hopefully my i-Button would work now, would check tomorrow...

Well, almost.
Do you remember a joke about a programmer and shampoo bottle?
Literally i am now ordered to enter infinite loop, a my flippd thinks it is okay, yet my qFlipper demand me to kill and resurrect it, starting it all over.

2022-11-13 00_14_24-qFlipper

Flipping USB cable worked this time, and it looks like qFlipper no more reports errors. Hopefully.

So, if you thought to scorn me for pulling plugs in the 3rd comment ther above - don't. Literally following instructions would not had worked anyway :-(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@the-Arioch