Windows api writefile failed your device is probably not on this port + видео обзор

Windows api writefile failed your device is probably not on this port

Новые темы необходимо создавать только в корневом разделе! В дальнейшем они будут обработаны модераторами.

Обсуждение Lenovo Tab 4 10
Windows api writefile failed your device is probably not on this portLenovo Tab 4 TB-X304L 10 LTE
Обсуждение » | Клуб любителей фирмы Леново »

Windows api writefile failed your device is probably not on this port

В теме нет куратора. По вопросам наполнения шапки обращайтесь к модераторам раздела через кнопку Windows api writefile failed your device is probably not on this port под сообщениями, на которые необходимо добавить ссылки.

Вопрос к другим владельцам, нет ли проблем с воспроизведением видео в приложении youtube в 720? А конкретно через непродолжительное время 5-10 минут черный экран, но звук продолжает идти? Чиста кэша, заводской сброс ничего не дали. В сервисе как на зло ошибка себя не проявила. Прошивку обновляли до последней

Windows api writefile failed your device is probably not on this port

Вопрос к другим владельцам, нет ли проблем с воспроизведением видео в приложении youtube в 720? А конкретно через непродолжительное время 5-10 минут черный экран, но звук продолжает идти? Чиста кэша, заводской сброс ничего не дали. В сервисе как на зло ошибка себя не проявила. Прошивку обновляли до последней

Есть и 32 гига версия с 3G

Ютуб глючит и на моих Леново Йога. Причём на 3-й больше, чем на 2-й

Хотите скзать по старому продавливать ногтем чтобы спружинил или подцеплять и тянуть ногтем? Я думал, что не просто там слева от разьема отверстие. Хорошо, что не стал ковырять дабы не испортить.

Друзья, собираюсь купить данный аппарат (TB-X304L), подскажите пжлст:

1. Не тормозит ли он в режиме 5-10 вкладок браузера и ютуб 720p (без игр)?
2. Есть ли проблемы по звуку из динамиков?
3. Много ли вшитых не нужных приложений?
4. Хорош ли WiFi?

Бегло покрутил его в руках в магазине, выбирал среди Huawei Mediapad T3 10 LTE и Samsung Galaxy Tab E 9.6 SM-T561N. Выбор пал на Lenovo из за звука, ибо критично.

Добрый день аппарат хороший сам его купил недавно все работает хорошо и Wi-Fi и модем единственное что пока прошивок на него нет а так аппарат хороший.

Windows api writefile failed your device is probably not on this port Baibus, спасибо. К сожалению редактировать свое сообщение пока возможности нет, повторю с правильными ссылками. (те были укорочены в недопустимая ссылка)
Стекла там же где и планшет нет. С Китая не получится, таможня с почтой России не успеют до выходных отработать, а на выходных уже дарить буду. Пока что присмотрел такой чехол и такое стекло.

Источник

[Howtos] Debrick Nexus 6p stuck in EDL (9008) mode.

Silverdace

Senior Member

Windows api writefile failed your device is probably not on this port

caiejay

Senior Member

Holymsophy

Member

Windows api writefile failed your device is probably not on this port

burakcuhadaroglu

Member

Windows api writefile failed your device is probably not on this port

hjmrox

Senior Member

Windows api writefile failed your device is probably not on this port

hjmrox

Senior Member

Hi, I’m also facing the same issue as you.

The reset is done after QFIL completes (need to set an option in configuration menu for the reset). The phone disconnects but connects back as QDloader still
The sad part is, I had intermittent access to bootloader, but after all these steps to try fix the phone, I cannot boot the phone to bootloader at all

Vaseag

Senior Member

olmos2

Member

Delete Thread here pls. WHERE IS F. FILE

nexus6p_fix_bricked.zip

rais.asif786

Senior Member

ncc8uetou5et

Member

My phone went into EDL 9008 mode.

How it got there: I was using the navigation. Then i had to call someone. So i let the navigation run in background and made a call. Inside the call everything froze and i was not able to turn on the phone by long pressing the power-button.

When i connect it to my computer i get this in dmesg:

usb 3-2: new high-speed USB device number 9 using xhci_hcd
usb 3-2: New USB device found, idVendor=05c6, idProduct=9008, bcdDevice= 0.00
usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 3-2: Product: QHSUSB__BULK
usb 3-2: Manufacturer: Qualcomm CDMA Technologies MSM
qcserial 3-2:1.0: Qualcomm USB modem converter detected
usb 3-2: Qualcomm USB modem converter now attached to ttyUSB0

I have important data on the phone that i need. If i understood right, then this howto is for reflashing the phone and when you reflash it, then you loose all your data. This is useless for my case where the data is the most important think now.

ncc8uetou5et

Member

llcoolr

Senior Member

please any one provide new link for file

Similar threads

Windows api writefile failed your device is probably not on this port

Windows api writefile failed your device is probably not on this port

Windows api writefile failed your device is probably not on this port

Windows api writefile failed your device is probably not on this port

Windows api writefile failed your device is probably not on this port

Windows api writefile failed your device is probably not on this port

Windows api writefile failed your device is probably not on this port

Top Liked Posts

there are too many people have bricked their device. so here is the guide on how to debrick your device.

Windows api writefile failed your device is probably not on this port

4 unlocked phone using fastboot commands to erase sbl1

5 erase your sbl1 with dd commoand not recommended

(Replace COM5 with whatever port shows in device manager)

you need to execute this from cmd prompt or powershell (in powershell prepend with an & character) while in the directory of the recovery images, notably the ‘prog_emmc_firehose.mbn’

If you get this to succeed, you’ll see this message:

10-20 seconds while plugged in until the port refreshes in device manager, then quickly try again.

Once you get into ‘sahara mode’ (this might be totally incorrect terminology), you can either execute this, which is what QFIL runs next:

(same rules as the last command apply)

OR, you can refresh in the MiFlash utility, and attempt to flash through there. I believe these two commands fail in the same manner when they fail, and I believe I will get a MiFlash success here soon if I keep trying:

I am having the same issue recently. My device froze while I was using it and have not turned on since. It gets detected as Qualcomm HS-USB QDLoader 9800 (COM3) in device manager when I connect it to PC. Tried flashing the rom provided by @tenfar using MiFlash, couldn’t receive hello packet. Tried flashing the same with QFIL, it ran for a while and ended up with this error:

What does this mean? Is my device beyond recovery? :crying:

My device is now occasionally reverting to a normal bootloop instead of the EDL mode where the device doesn’t respond to anything except the QFIL tool. I was able to boot into recovery, flash TWRP, and attempt the ‘core downgrade’ method. I flashed a few of those modified images, the EX kernel, and actually booted into android twice! I signed in both times and actually started downloading apps/receiving text messages, but then the phone froze and returned to the EDL state. I have not been able to get it to boot back into recovery (I want to try to flash different images from the other fix thread) for 48 hours now, leaving it plugged in the entire time, attempting every 12 hours or so.

If you did not enable developer mode/unlock bootloader before your phone bricked itself, you are kind of screwed unless you can get very lucky and boot into android once, unlock it, then let it crash again.

Источник

[GUIDE] Unbrick X82x Le Max 2, Factory Restore, Reset, Qualcomm HS-USB QDLoader 9008

AhmadSant

Senior Member

Teky Friend

New member

alexvallem

Member

Windows api writefile failed your device is probably not on this port

valy_cta

Senior Member

Naqeeb`

New member

piocool

Member

Total to be tansferd with

23:06:00: INFO: Sending

23:06:00: INFO: TARGET SAID: ‘Binary build date: Apr 15 2016 @ 14:22:44’

23:06:00: INFO: TARGET SAID: ‘Chip serial num: 308822721 (0x126842c1)’

23:06:00: INFO: TARGET SAID: ‘Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke ‘

23:06:00: INFO: TARGET SAID: ‘Calling usb_al_bulk_set_zlp_mode(TRUE) since ZlpAwareHost=’1»

23:06:00: INFO: TARGET SAID: ‘Calling hotplug_poll_device(‘UFS’)’

_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| ‘__| ‘__/ _ \| ‘__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|

Writing log to ‘C:\Users\Admin\AppData\Roaming\Qualcomm\QFIL\port_trace.txt’, might take a minute

Log is ‘C:\Users\Admin\AppData\Roaming\Qualcomm\QFIL\port_trace.txt’

Download Fail:FireHose Fail FHLoader Fail rocess fail
Finish Download

Phone is detected as Qualcomm HS-USB QDLoader 9008 COMXX.

Windows api writefile failed your device is probably not on this port

valy_cta

Senior Member

Total to be tansferd with

23:06:00: INFO: Sending

23:06:00: INFO: TARGET SAID: ‘Binary build date: Apr 15 2016 @ 14:22:44’

23:06:00: INFO: TARGET SAID: ‘Chip serial num: 308822721 (0x126842c1)’

23:06:00: INFO: TARGET SAID: ‘Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke ‘

23:06:00: INFO: TARGET SAID: ‘Calling usb_al_bulk_set_zlp_mode(TRUE) since ZlpAwareHost=’1»

23:06:00: INFO: TARGET SAID: ‘Calling hotplug_poll_device(‘UFS’)’

_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| ‘__| ‘__/ _ \| ‘__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|

Writing log to ‘C:\Users\Admin\AppData\Roaming\Qualcomm\QFIL\port_trace.txt’, might take a minute

Log is ‘C:\Users\Admin\AppData\Roaming\Qualcomm\QFIL\port_trace.txt’

Download Fail:FireHose Fail FHLoader Fail rocess fail
Finish Download

Phone is detected as Qualcomm HS-USB QDLoader 9008 COMXX.

Adaptive123

New member

I have no idea how to get past this problem! Thanks in advanced

06:39:02: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.

06:39:02: ERROR: function: sahara_main:854 Sahara protocol error

06:39:02: ERROR: function: main:265 Uploading Image using Sahara protocol failed

Download Fail:Sahara Fail:QSaharaServer Fail rocess fail
Finish Download

EDIT, SOLUTION: I turned phone off (power,vol+,vol-) then started flash again.

Adaptive123

New member

Windows api writefile failed your device is probably not on this port

valy_cta

Senior Member

piocool

Member

Holding combination of buttons +/- & Power is cousing windows sound of disconnecting/reconnecting device.

Whole log attatched

Attachments

Windows api writefile failed your device is probably not on this port

Windows api writefile failed your device is probably not on this port

Windows api writefile failed your device is probably not on this port

Windows api writefile failed your device is probably not on this port

valy_cta

Senior Member

hivham12

New member

byshakram

Senior Member

RP3VU

Member

Fixed!
This was the hardest brick i ever recovered. Took only four days.
Learned a ton, unfortunately broke the display in the end but it’s super cheap.
Now i regret tossing a bricked x829 a few month ago. Could probably be recovered too.

Gesendet von meinem HTC Desire 310 mit Tapatalk

Hi, I hard bricked my device yesterday and I’m not able to bring it alive. I flashed the software via FlashOne and the phone just started vibrating and the screen doesn’t show anything. Now I have problem even with drivers and I can’t flash it again. It’s still in the mode to flash and I’m not able to change it even by holding power button for 2 minutes. How did you fixed your phone?

Holding combination of buttons +/- & Power is cousing windows sound of disconnecting/reconnecting device.

Whole log attatched

tony770101

Member

Hi, I hard bricked my device yesterday and I’m not able to bring it alive. I flashed the software via FlashOne and the phone just started vibrating and the screen doesn’t show anything. Now I have problem even with drivers and I can’t flash it again. It’s still in the mode to flash and I’m not able to change it even by holding power button for 2 minutes. How did you fixed your phone?

RP3VU

Member

piocool

Member

Hi, I hard bricked my device yesterday and I’m not able to bring it alive. I flashed the software via FlashOne and the phone just started vibrating and the screen doesn’t show anything. Now I have problem even with drivers and I can’t flash it again. It’s still in the mode to flash and I’m not able to change it even by holding power button for 2 minutes. How did you fixed your phone?

tony770101

Member

AhmadSant

Senior Member

Similar threads

Windows api writefile failed your device is probably not on this port

Windows api writefile failed your device is probably not on this port

Top Liked Posts

Windows api writefile failed your device is probably not on this port

Hi all,
After reading on letv.re that some people managed to brick their devices and were looking for a fix, I started to check more and more about the issue. What happened to some was that the phone would switch itself off and enter into Qualcomm Recovery Mode and would be seen when connected to a computer as “Qualcomm HS-USB QDLoader 9008”. For others, by flashing wrong files the phone would end up in the same state. Luckily a fix had been found, and it was shared by ParasiTe_RemiX.

Keep in mind that if your phone goes by itself in the QDLoader mode, it’s better to try some combinations below before flashing it using this method:
1) Keep the power button pressed for about 2 minutes, or
2) Keep the power button + Vol up pressed for about 2 minutes, or
3) Keep the power button while connecting the phone to a wall charger, or
4) Bring the phone into a bright light and press the power button (or power button + Vol up) for about 2 minutes, or
5) Keep the phone charging for more than 24 hours and repeat all the steps above.
If nothing works and you are willing to fix it and you’ll give up all your files, then this fix is for you. Or if you have flashed some wrong files and there is no Fastboot, nor Recovery, this is to be followed. Or if you want to reset your phone to a “factory state”, this is the way to go, and by that I mean if you want to check that your fingerprint sensor is working, or you have some other issues, it’s good to revert it this way.

IMPORTANT – YOU WILL LOSE ALL YOUR FILES ON THE PHONE, PHOTOS, MUSIC, APP DATA, INTERNAL STORAGE WILL BE WIPED.

So if your phone is in this Qualcomm Recovery mode, you can just connect it to the computer, and jump to step 3, if not, and you simply want to flash it, start from step 1.

To exit the Qualcomm Recovery mode, keep the Power Button pressed for about 1 minute or until the phone will vibrate and restart into system.
That’s it. More info you will find in FlashOne program, actually it’s almost like I’ve described it here.
You will be reverted to a «dev» version of the phone, somewhere with April build date. Keep in mind that it’s EUI 5.6 and the kernel is different than EUI 5.8. Update it to latest EUI with stock recovery and then install the custom recovery of your choice.
Most of the guys install a recovery for 5.6 on EUI 5.8 or vice versa and then they get the blue LED. That’s why you should read the instructions for each recovery and make sure you know which one you’re flashing.

Источник

Windows api writefile failed your device is probably not on this port

Сбой активации iPhone после сброса iOS 11 на заводские настройки
iPod: 5 | iPhone: 4s, 5, 5s | iPad: 2, 3, 4, Mini, Mini2, Mini3, Air

Windows api writefile failed your device is probably not on this port

Если судьба устройства неизвестна, если в устройстве присутствуют любые проблемы, то оно в зоне риска. Любые обновления используете на свой страх и риск.

Обновлено 17.10.19
Появился откат с помощью МacOS Mojave или выше, а также Linux (Xubuntu 19.10 и Mint 20).
С помощью Windows или виртуальных машин решений не существует.
Первая информация. Сбой активации. (от dex1m)

С помощью Vieux возможен обход проблемы на устройствах:
iOS 10.3.3: iPhone 5s, iPad Air, iPad Mini 2 (кроме iPad4.6);
iOS 8.4.1: iPhone 5, iPhone 4s, iPad 2, iPad 3, iPad 4, iPad Mini 1, iPod 5;
iOS 6.1.3: iPhone 4s, iPad 2 (кроме iPad2.4).

С помощью StableA7 и LeetDown возможен обход проблемы на устройствах:
iOS 10.3.3: iPhone 5S, iPad Air, iPad mini 2, iPad mini 3.

С помощью iOS-OTA-Downgrader возможен обход проблемы на устройствах:
iOS 10.3.3: iPhone 5s, iPad Air, iPad Mini 2, iPad Mini 3;
iOS 8.4.1: поддержка устройств с процессором 32-бит;
iOS 6.1.3: iPhone 4s, iPad 2 (кроме iPad2.4).

После прошивки или после сброса контента и настроек последуют стандартные шаги регистрации, одним из которых будет активация устройства. При активации происходит опрос комплектующих и сравнение их номеров с официальной базой Apple. Если в устройстве по разным причинам не совпадает техническая информация (udid, s/n, imei, mac-address и прочее) с официальной базой Apple, то устройство останавливается на шаге активации. Проблема не решается ни прошивкой, ни полным сбросом настроек, ни восстановлением через DFU, а в iTunes вы получаете ошибку 0xe8000013 или ошибку «iPhone не удалось активировать, так как не удалось получить с него информацию об активации».

Чтобы избежать проблем, внимательно изучайте инструкции и используйте операционные системы, указанные авторами скриптов.

С момента появления скриптов мы наблюдаем их странное поведение в некоторых случаях. Откат прошивок осуществляется в полном соответствии с правилам, но при этом возникают разные проблемы. Можно много раз пытаться откатить устройство и получать ошибки, но вдруг ни с того ни с сего эта же система может сработать.
Скорее всего, дело может быть в драйверах usb, проблемном соединении с интернетом или с самими серверами (спасибо Speci@list за разъяснение), которые используются скриптом.

Все действия выполняете на свой страх и риск.

Источник

[GUIDE] Unbrick X82x Le Max 2, Factory Restore, Reset, Qualcomm HS-USB QDLoader 9008

Windows api writefile failed your device is probably not on this port

D_Heroic_One

Senior Member

FreeJoin4

New member

I’ve problem with fastboot and I can’t using it. And any version rom can’t install always gives an error «failed to update! Cause: corrupted».
There are those who have solved this problem, please guide me
x829 (was?) and win10 comp

UPD: it fix any other comp

Similar threads

Windows api writefile failed your device is probably not on this port

Windows api writefile failed your device is probably not on this port

Top Liked Posts

Windows api writefile failed your device is probably not on this port

Hi all,
After reading on letv.re that some people managed to brick their devices and were looking for a fix, I started to check more and more about the issue. What happened to some was that the phone would switch itself off and enter into Qualcomm Recovery Mode and would be seen when connected to a computer as “Qualcomm HS-USB QDLoader 9008”. For others, by flashing wrong files the phone would end up in the same state. Luckily a fix had been found, and it was shared by ParasiTe_RemiX.

Keep in mind that if your phone goes by itself in the QDLoader mode, it’s better to try some combinations below before flashing it using this method:
1) Keep the power button pressed for about 2 minutes, or
2) Keep the power button + Vol up pressed for about 2 minutes, or
3) Keep the power button while connecting the phone to a wall charger, or
4) Bring the phone into a bright light and press the power button (or power button + Vol up) for about 2 minutes, or
5) Keep the phone charging for more than 24 hours and repeat all the steps above.
If nothing works and you are willing to fix it and you’ll give up all your files, then this fix is for you. Or if you have flashed some wrong files and there is no Fastboot, nor Recovery, this is to be followed. Or if you want to reset your phone to a “factory state”, this is the way to go, and by that I mean if you want to check that your fingerprint sensor is working, or you have some other issues, it’s good to revert it this way.

IMPORTANT – YOU WILL LOSE ALL YOUR FILES ON THE PHONE, PHOTOS, MUSIC, APP DATA, INTERNAL STORAGE WILL BE WIPED.

So if your phone is in this Qualcomm Recovery mode, you can just connect it to the computer, and jump to step 3, if not, and you simply want to flash it, start from step 1.

To exit the Qualcomm Recovery mode, keep the Power Button pressed for about 1 minute or until the phone will vibrate and restart into system.
That’s it. More info you will find in FlashOne program, actually it’s almost like I’ve described it here.
You will be reverted to a «dev» version of the phone, somewhere with April build date. Keep in mind that it’s EUI 5.6 and the kernel is different than EUI 5.8. Update it to latest EUI with stock recovery and then install the custom recovery of your choice.
Most of the guys install a recovery for 5.6 on EUI 5.8 or vice versa and then they get the blue LED. That’s why you should read the instructions for each recovery and make sure you know which one you’re flashing.

Источник

Видео

ОКНО ВЫБОРА ФАЙЛА - C++ WINAPI ЧАСТЬ #7

ОКНО ВЫБОРА ФАЙЛА  -  C++ WINAPI ЧАСТЬ #7

Что делать если не отображаются порты COM и LPT? Возвращаем порты COM и LPT на место!

Что делать если не отображаются порты COM и LPT? Возвращаем порты COM и LPT на место!

ИМПОРТ И ЭКСПОРТ В ФАЙЛ - C++ WINAPI ЧАСТЬ #6

ИМПОРТ И ЭКСПОРТ В ФАЙЛ  -  C++ WINAPI ЧАСТЬ #6

Как открыть порты. Подробная инструкция. Настройка роутера и Firewall

Как открыть порты. Подробная инструкция. Настройка роутера и Firewall

100{c8630058720f0e9cb2fce87f9e6f86c046784f1cb6da531a8c0265a40d497078} FIX The file is possibly corrupt. The file header checksum does not match the computed checksum

100{c8630058720f0e9cb2fce87f9e6f86c046784f1cb6da531a8c0265a40d497078} FIX The file is possibly corrupt. The file header checksum does not match the computed checksum

Разработка приложений с помощью WinAPI. Урок 3 чтение и запись в файл

Разработка приложений с помощью WinAPI. Урок 3 чтение и запись в файл

Windows Native API - Roger Orr [ACCU 2019]

Windows Native API - Roger Orr [ACCU 2019]

[6] Уроки по WinAPI?! - Дочерние окна.

[6] Уроки по WinAPI?! - Дочерние окна.

Advanced I/O - CreateFile, WriteFile, ReadFile, CloseHandle

Advanced I/O - CreateFile, WriteFile, ReadFile, CloseHandle

ДОБАВЛЯЕМ МЕНЮ - C++ WINAPI ЧАСТЬ #2

ДОБАВЛЯЕМ МЕНЮ  -  C++ WINAPI ЧАСТЬ #2
Поделиться или сохранить к себе:
Добавить комментарий

Нажимая на кнопку "Отправить комментарий", я даю согласие на обработку персональных данных, принимаю Политику конфиденциальности и условия Пользовательского соглашения.