востановление поврежденных голов +/ damage head unit repair

parsec82 · Ср мар 02, 2016 1:06 pm

audijiJQ писал(а):flashit -a 6200000 -e 1000

ok i have used this line but when i start the unit work for about 10-20 sec and will freeze and on the terminal i see this:

--> SAM is initialized
..initializing addon "SSSMonitor" ...ok
..initializing channel "HostAgent" ...ok
..initializing channel "MonitorService" ...ok
..initializing channel "IntegrityService" ...ok
..initializing channel "AliveService" ...ok
..initializing channel "AudioMatrixService" ...ok
..initializing channel "PhoneService" ...ok
..initializing channel "BSSService" ...ok
[t(p) usr/bin/PSSBSSProcess 213046 3 11 782547b4]
..initializing channel "NetAccessService" ...ok
..initializing channel "SIMService" ...ok
amd_poll: 186 DQ7 polling Timeout
(devf t2::f3s_aCFI_v2write:250) over poll waiting for write completion at 3fb0025c, size 12
(devf t2::f3s_ext_write:195) fs0p3 bad H[06] P[1E8] # 00000C # 00000000
(devf t2::f3s_file_create:110) fs0p3 error -1
amd_poll: 186 DQ7 polling Timeout
(devf t2::f3s_aCFI_v2write:250) over poll waiting for write completion at 3fb00268, size 12
(devf t2::f3s_ext_write:195) fs0p3 bad H[07] P[1E8] # 00000C # 00000000
(devf t2::f3s_file_create:110) fs0p3 error -1
amd_poll: 186 DQ7 polling Timeout
(devf t2::f3s_aCFI_v2write:250) over poll waiting for write completion at 3fb00274, size 12
(devf t2::f3s_ext_write:195) fs0p3 bad H[08] P[1E8] # 00000C # 00000000
(devf t2::f3s_file_create:110) fs0p3 error -1
[t(p) usr/sbin/devf-generic 12290 2 11 8066bc8]
[t(c) usr/bin/PSSBSSProcess 213046 1 11 7033519a]
amd_poll: 186 DQ7 polling Timeout
(devf t2::f3s_aCFI_v2write:250) over poll waiting for write completion at 3fb00280, size 12
(devf t2::f3s_ext_write:195) fs0p3 bad H[09] P[1E8] # 00000C # 00000000
(devf t2::f3s_file_create:110) fs0p3 error -1
amd_poll: 186 DQ7 polling Timeout
(devf t2::f3s_aCFI_v2write:250) over poll waiting for write completion at 3fb0028c, size 12
(devf t2::f3s_ext_write:195) fs0p3 bad H[0A] P[1E8] # 00000C # 00000000
(devf t2::f3s_file_create:110) fs0p3 error -1
amd_poll: 186 DQ7 polling Timeout
(devf t2::f3s_aCFI_v2write:250) over poll waiting for write completion at 3fb00298, size 12
(devf t2::f3s_ext_write:195) fs0p3 bad H[0B] P[1E8] # 00000C # 00000000
(devf t2::f3s_file_create:110) fs0p3 error -1
amd_poll: 186 DQ7 polling Timeout
(devf t2::f3s_aCFI_v2write:250) over poll waiting for write completion at 3fb002a4, size 12
(devf t2::f3s_ext_write:195) fs0p3 bad H[0C] P[1E8] # 00000C # 00000000
(devf t2::f3s_file_create:110) fs0p3 error -1
amd_poll: 186 DQ7 polling Timeout
(devf t2::f3s_aCFI_v2write:250) over poll waiting for write completion at 3fb002b0, size 12
(devf t2::f3s_ext_write:195) fs0p3 bad H[0D] P[1E8] # 00000C # 00000000
(devf t2::f3s_file_create:110) fs0p3 error -1
[t(p) usr/sbin/devf-generic 12290 2 11 8066bc8]
[t(c) usr/bin/PSSBSSProcess 213046 1 11 7033519a]
amd_poll: 186 DQ7 polling Timeout
(devf t2::f3s_aCFI_v2write:250) over poll waiting for write completion at 3fb002bc, size 12
(devf t2::f3s_ext_write:195) fs0p3 bad H[0E] P[1E8] # 00000C # 00000000
(devf t2::f3s_file_create:110) fs0p3 error -1
amd_poll: 186 DQ7 polling Timeout
(devf t2::f3s_aCFI_v2write:250) over poll waiting for write completion at 3fb002c8, size 12
(devf t2::f3s_ext_write:195) fs0p3 bad H[0F] P[1E8] # 00000C # 00000000
(devf t2::f3s_file_create:110) fs0p3 error -1
amd_poll: 186 DQ7 polling Timeout
(devf t2::f3s_aCFI_v2write:250) over poll waiting for write completion at 3fb002d4, size 12
(devf t2::f3s_ext_write:195) fs0p3 bad H[10] P[1E8] # 00000C # 00000000
(devf t2::f3s_file_create:110) fs0p3 error -1
amd_poll: 186 DQ7 polling Timeout
(devf t2::f3s_aCFI_v2write:250) over poll waiting for write completion at 3fb002e0, size 12
(devf t2::f3s_ext_write:195) fs0p3 bad H[11] P[1E8] # 00000C # 00000000
(devf t2::f3s_file_create:110) fs0p3 error -1
amd_poll: 186 DQ7 polling Timeout
(devf t2::f3s_aCFI_v2write:250) over poll waiting for write completion at 3fb002ec, size 12
(devf t2::f3s_ext_write:195) fs0p3 bad H[12] P[1E8] # 00000C # 00000000
(devf t2::f3s_file_create:110) fs0p3 error -1
amd_poll: 186 DQ7 polling Timeout
(devf t2::f3s_aCFI_v2write:250) over poll waiting for write completion at 3fb002f8, size 12
(devf t2::f3s_ext_write:195) fs0p3 bad H[13] P[1E8] # 00000C # 00000000
(devf t2::f3s_file_create:110) fs0p3 error -1
[t(p) usr/sbin/devf-generic 12290 2 11 806334e]
[t(c) usr/bin/PSSBSSProcess 213046 1 11 7033519a]
amd_poll: 186 DQ7 polling Timeout
(devf t2::f3s_aCFI_v2write:250) over poll waiting for write completion at 3fb00304, size 12
(devf t2::f3s_ext_write:195) fs0p3 bad H[14] P[1E8] # 00000C # 00000000
(devf t2::f3s_file_create:110) fs0p3 error -1
amd_poll: 186 DQ7 polling Timeout
(devf t2::f3s_aCFI_v2write:250) over poll waiting for write completion at 3fb00310, size 12
(devf t2::f3s_ext_write:195) fs0p3 bad H[15] P[1E8] # 00000C # 00000000
(devf t2::f3s_file_create:110) fs0p3 error -1
amd_poll: 186 DQ7 polling Timeout

slav · Сообщение **slav** » Ср мар 02, 2016 2:10 pm

Looks like hardware problem.

Tschako · Ср мар 02, 2016 5:15 pm

It needs acouple of restarts to rebuilt the efs-persist (fs0p3) partition automaticaly...

parsec82 · Ср мар 02, 2016 7:51 pm

ok for a couple of reboot but today i think the unit are rebooted aproximately 30 times
but the error "fs0p3 error -1" are normal?

---
amd_poll: 186 DQ7 polling Timeout
(devf t5::f3s_aCFI_v2write:250) over poll waiting for write completion at 3f580484, size 12
(devf t5::f3s_ext_write:195) fs0p3 bad H[34] P[1D2] # 00000C # 00000000
(devf t5::f3s_file_create:110) fs0p3 error -1

Tschako · Чт мар 03, 2016 10:50 am

in that case it looks like a hardware damage in the flash memory area. Extract an efs-persist image from an other 3G unit and try to flash it directly.
If flashit tool reports some memory errors, the flash a damaged and you at the end of the repair...

The extraction of the image file is quiet simple and I descripyed it a couple of pages ago in that thread.

Keep attention to flash only in emergency (developer) mode directly after restart.

parsec82 · Чт мар 03, 2016 11:33 am

i have on my hard drive a backup make with a script, of an unit.
i have the 3 files
fs0.dump
fs1.dump
fs4.dump

are possible to use this files for recovery this unit?
there is a special comand for flash this file directly on the unit?

Tschako · Чт мар 03, 2016 3:07 pm

You need the fs0p3 flash image from another 3G Unit as yours. You can extract it with a binary editor from the whole fs0 image dump.
The fs0p3 (efs-persist) image starts at 0x06200000 and ends at 0x07efffff

zloybob · Сб мар 12, 2016 11:21 am

Добрый день.
Пытаюсь воскресить MQB MIB1, подвисает после загрузки

Сделал
flashit -v -x -a 0x00540000 -e 1000
Запускается в emergency и прошивает все блоки, но потом как он начинает что-то копировать из бекапов, вылетает с ошибкой как у товарища выше
amd_poll: 161 DQ5 set, program error
(devf t2::f3s_aCFI_v2write:250) over poll waiting for write completion at 2b504d34, size 5
(devf t2::f3s_ext_write:202) fs0p1 bad H[3D6] P[1A8] # 000005 # 00000000
(devf t2::f3s_file_append:555) fs0p1 error -1
amd_poll: 161 DQ5 set, program error
(devf t2::f3s_aCFI_v2write:250) over poll waiting for write completion at 2b504d3c, size 5
(devf t2::f3s_ext_write:202) fs0p1 bad H[3D7] P[1A8] # 000005 # 00000000
(devf t2::f3s_file_append:555) fs0p1 error -1
amd_poll: 161 DQ5 set, program error
(devf t2::f3s_aCFI_v2write:250) over poll waiting for write completion at 2b504d44, size 5
(devf t2::f3s_ext_write:202) fs0p1 bad H[3D8] P[1A8] # 000005 # 00000000
(devf t2::f3s_file_append:555) fs0p1 error -1
amd_poll: 161 DQ5 set, program error
(devf t2::f3s_aCFI_v2write:250) over poll waiting for write completion at 2b504d4c, size 5
(devf t2::f3s_ext_write:202) fs0p1 bad H[3D9] P[1A8] # 000005 # 00000000
(devf t2::f3s_file_append:555) fs0p1 error -1
amd_poll: 161 DQ5 set, program error
(devf t2::f3s_aCFI_v2write:250) over poll waiting for write completion at 2b504d54, size 5
(devf t2::f3s_ext_write:202) fs0p1 bad H[3DA] P[1A8] # 000005 # 00000000
(devf t2::f3s_file_append:555) fs0p1 error -1

Полностью перелил с другой бошки efs-system и efs-persist, всё проходит без ошибок, но только с ключём -d (erase)

Если делаю
echo dummy > /HBpersistence/DeveloperMode
то получаю ошибки как выше
Но если я туда пишу не dummy, то всё ок.
Я так понимаю при записи dummy запускается что-то из-за чего и проиходят ошибки.
В чём может быть проблема?

congo · Ср мар 16, 2016 10:43 pm

@parsec82 what is the unit, from which model car.
efs-persist can be taken from the firmware that the car was first installed (the P ones not the K) and some but no all K ones.
I have it for:
3GB_MU9302_P0020
3GB_MU9304_K0260
3GH_MU9308_K0257_5
3GH_MU9308_K0257_6
3GP_MU9411_P0066

eprst · Сб мар 19, 2016 4:57 pm

Приветствую, имеется Q5 2009 HNav_EU_K0022_2_D1, стоит 9307, по запарке вставил 900 прошивку от 3Gp 9498 , обновленние прошло не полностью, отменить не получилось - после перезагрузки ММИ грузилась частично, теперь она решила что она 9498 и не принимает 9307

Nobody_Knows · Сб мар 19, 2016 5:07 pm

eprst писал(а):Приветствую, имеется Q5 2009 HNav_EU_K0022_2_D1, стоит 9307, по запарке вставил 900 прошивку от 3Gp 9498 , обновленние прошло не полностью, отменить не получилось - после перезагрузки ММИ грузилась частично, потом через зеленку была попытка залить 257 прошивку через эменжерси, теперь она решила что она 9498 и не принимает 9307(фото в приложении), разобрал подпоялся - запустил терминал, вот лог терминала (в приложении), команду boot_1c0000 не принимает, точнее принимает, только толку от нее в моем случае ноль, как и в эмерджи - зеленое окно потом красное (в приложении), команда flashit пишет не извесна ей...
подскажите как оживить?

Green Menu -> SWDL -> Ignore region and Variant ставим галку, выходим из зеленки. ГОЛОВУ НЕ ПЕРЕЗАГРУЖАЕМ. Вставляем SD с прошивкой от 3G (любую, но лучше ближе по номеру к родной). Входим в режим обновления, выбирыаем "Определенный пользователем" и ставим галки в пункте MuIOC , чтобы в итоге напротив него было "Y", а не "S" или "N". Обновляемся. Если прокатит - хорошо. Если нет - пишите в ЛС - обсудим решение вопроса.

eprst · Сб мар 19, 2016 5:42 pm

я пробовал так, после нажатия старт доунлоад - ничего не происходило... мми просто зависала и все... от версии прошивки в слоте ни чего не менялось... после этого уже было эмеджерси и т.д

eprst · Сб мар 19, 2016 11:10 pm

решено

eprst · Вс мар 20, 2016 11:39 am

может по логу кто подскажет?

IPL: Audi 3G 9308 (SH7785) / QNX 6.3.0 [PL_qnx_ipl-3g_9308-sh7785_07412A, built 2007/10/09_12-19-44_UTC]
CPU: SH7785 (>= 5th cut, clk mode 20), 792MHz
RAM: 512 MB (probed, DBCONF=e30002)
FLASH: Spansion S29GL512N: 512 sectors x 256K
FPGA: PL_MMI3G_FPGA_9308_D1_08492A

(0ms)
*** emergency FPGA loaded!
*** Old-fashioned mark found on IFS @0x1c0000: .zero=0x3000001d
starting image @1c0000 ...

Startup: PL_qnx_startup-sh7785_08362A, built 2008/09/02_07-53-12_UTC

RAM : 256 MB @0x08000000
FLASH: 128 MB @0x00000000

System page at phys:0800a000 user:0800a000 kern:8800a000
Starting next program at v88046840
------------------------------------------------------
Welcome to QNX 6.3.2 (RL_qnx_os_632_PSP3_08124A) MMI3G Audi EMERGENCY SETUP 9308 D1 09034A
starting pci driver
*** init FPGA registers ***
starting dev-ipc for IOC
initialize IPC Driver
starting network driver
starting atapi driver - setup device /dev/cam0
starting devc-pty
Path=0 - XILINX MMI3G_8
target=0 lun=0 CD-ROM(5) - FJ-TEN DVD-ROM DV-04FT1 Rev: 1423
Path=1 - XILINX MMI3G_8
target=1 lun=0 Direct-Access(0) - TOSHIBA MK4036GA Rev: TA15
starting flash driver
starting SDCard driver
Unable to access "/dev/io-net/en5" (2)
starting with no network driver
===========================================================
Emergency IFS is started. Emergency app tries to restore
the application.
===========================================================
49169 running /usr/bin/devg-NVTIRM
DMA is Disabled
dma disabled, interrupt thread priority = 100
49171 running /sbin/io-media-nvidia
49172 running /usr/sbin/io-display
49173 running /usr/apps/MMI3GEmergencyApp
===========================================================
Emergency shell started, fix your system and restart again
===========================================================
discplayer_init: IN
nvidia_render_manager_init: IN
INvmRenderManager::GetNvmRenderManager (&pRenderManager);
er = pRenderManager->Init(oConfig);
# Fpga header is not 0x4744482e (0xffffffff)!
App FPGA valid 0
Emergency FPGA valid 1

EmergencyApp-MMI3G: version 21.29.1642, date of build 14.01.2009
pRenderManager->Open()
nvidia_render_manager_init: OUT
discplayer_init: OUT
discplayer_init
discplayer_init: IN
nvidia_render_manager_init: IN
nvidia_render_manager_init: OUT
discplayer_init: OUT
dvdtrackplayer_init
discplayer_init: IN
nvidia_render_manager_init: IN
nvidia_render_manager_init: OUT
discplayer_init: OUT
dvdnavigator_init
created navigator control point with 8249288
mixer_init: IN
mixer_init: OUT
NvTRACELEVEL set to 3 (Level Info)
nVAudio_init: IN
nvidia_render_manager_init();
nvidia_render_manager_init: IN
nvidia_render_manager_init: OUT
nVAudio_init: OUT
installing audio decoders
installing video decoders
nVAudio_init: IN
nvidia_render_manager_init();
nvidia_render_manager_init: IN
nvidia_render_manager_init: OUT
nVAudio_init: OUT
OnIpcGetCaptureUnitSourceCount
Number of displays: 6
Number of layers: 9
Graphics init was successfull: DisplaySize is 800x 480
OnOff: process IPC event 177 198
SWDL: startUpdate HW index 177, variant 9498
OnOff: phase Scan metainfo
We have to erase the FPGA, init the FPGA persistence and delete the orphaned headers (if there are any).
OnOff: phase Erase
OnOff: Progress 000
dev_fd == 10
devctl returned 0
arrayinfo.unit_size 262144
calling devctl with erase struct:
status: 0
offset: 0x40000
limit: 0x40000
devctl(10,-2146694912,xx,12,0) returned 0OnOff: Progress 100
FPGA info header @SWDL V1@
FPGA info version 1
FPGA info variant 9498
FPGA info HW index MU 21
FPGA info region <noRegion>
FPGA info step 0
FPGA info HW index IT 0
FPGA info ignore region/variant 1
FPGA info loop 0
FPGA info repeat 0
FPGA info CRC 3be9dd76
SWDL: Stopping EFS driver!
slay: Unable to find process 'checkPersistence'
result of running command stop_efs_driver.sh is 0
SWDL: Starting EFS driver (automount)!
(devf t1::f3s_recover_boot:141) fs0p1 boot P[E0] U: 58
result of running command start_efs_driver.sh is 0
/HBpersistence/SWDL not found!
(devf t1::f3s_recover_boot:141) fs0p2 boot P[138] U: 50
/HBpersistence/SWDL not found!
(devf t1::f3s_recover_boot:141) fs0p3 boot P[1B3] U: 74
/HBpersistence/SWDL not found!
/HBpersistence/SWDL not found!
/HBpersistence/SWDL not found!
/HBpersistence/SWDL/update.txt doesn't exist
Don't use update.txt
SWDL: Mount from medium 3 (0)
OnOff: variant 9498
OnOff: DeviceName MU9498
Src: Medialauncher is running
Src: mount failed. Retry once in 1 s
Src: Medialauncher is running
Src: mount failed (medium unavailable 2)
SWDL: mount failed
SWDL: Mount from medium 4 (1)
Src: Medialauncher is running
Src: mount failed. Retry once in 1 s
Src: Medialauncher is running
Src: mount failed (medium unavailable 2)
SWDL: mount failed
SWDL: Mount from medium 5 (2)
Src: Medialauncher is running
Src: mount failed. Retry once in 1 s
Src: Medialauncher is running
Src: mount failed (medium unavailable 2)
SWDL: mount failed
SWDL: Mount from medium 2 (3)
Src: mount from CD OK
Src: mount OK
SWDL: mount OK
SWDL: open metainfo /metainfo2.txt
SWDL: open finished (9389)
OnOff: FileAccess for continues!
OnOff: Current file access type: read
SWDL: read finished (9389, 0)
SWDL: parse metainfo
SWDL: check next subdir
SWDL: CheckNextSubDir 1
SWDL: open metainfo /metainfo2.txt
SWDL: open finished (19921)
SWDL: read finished (19921, 0)
SWDL: parse metainfo
SWDL: check next subdir
SWDL: CheckNextSubDir 2
SWDL: open metainfo /metainfo2.txt
SWDL: open finished (22490)
SWDL: read finished (22490, 0)
SWDL: parse metainfo
SWDL: check next subdir
SWDL: CheckNextSubDir 3
SWDL: open metainfo /metainfo2.txt
SWDL: open finished (92291)
SWDL: read finished (92291, 0)
SWDL: parse metainfo
SWDL: check next subdir
SWDL: CheckNextSubDir 4
SWDL: No medium left!
OnOff: error No medium!!!

eprst · Вс мар 20, 2016 1:20 pm

флешит тоже не помог

# flashit -a 40000 -e 1000
*** erasing ... |
*** verifying ... |
(devf t2::f3s_recover_boot:238) fs0p1 boot P[E0] U: 58
(devf t2::f3s_recover_boot:238) fs0p2 boot P[138] U: 50
(devf t2::f3s_recover_boot:238) fs0p3 boot P[1B3] U: 74
#
getdip
close
IPL: Audi 3G 9308 (SH7785) / QNX 6.3.0 [PL_qnx_ipl-3g_9308-sh7785_07412A, built 2007/10/09_12-19-44_UTC]
CPU: SH7785 (>= 5th cut, clk mode 20), 792MHz
RAM: 512 MB (probed, DBCONF=e30002)
FLASH: Spansion S29GL512N: 512 sectors x 256K
FPGA: PL_MMI3G_FPGA_9308_D1_08492A

(0ms)
*** emergency FPGA loaded!
*** Old-fashioned mark found on IFS @0x1c0000: .zero=0x3000001d
starting image @1c0000 ...

Startup: PL_qnx_startup-sh7785_08362A, built 2008/09/02_07-53-12_UTC

RAM : 256 MB @0x08000000
FLASH: 128 MB @0x00000000

System page at phys:0800a000 user:0800a000 kern:8800a000
Starting next program at v88046840
------------------------------------------------------
Welcome to QNX 6.3.2 (RL_qnx_os_632_PSP3_08124A) MMI3G Audi EMERGENCY SETUP 9308 D1 09034A
starting pci driver
*** init FPGA registers ***
starting dev-ipc for IOC
initialize IPC Driver
starting network driver
starting atapi driver - setup device /dev/cam0
starting devc-pty
Path=0 - XILINX MMI3G_8
target=0 lun=0 CD-ROM(5) - FJ-TEN DVD-ROM DV-04FT1 Rev: 1423
Path=1 - XILINX MMI3G_8
target=1 lun=0 Direct-Access(0) - TOSHIBA MK4036GA Rev: TA15
starting flash driver
starting SDCard driver
Unable to access "/dev/io-net/en5" (2)
starting with no network driver
===========================================================
Emergency IFS is started. Emergency app tries to restore
the application.
===========================================================
49169 running /usr/bin/devg-NVTIRM
DMA is Disabled
dma disabled, interrupt thread priority = 100
49171 running /sbin/io-media-nvidia
49172 running /usr/sbin/io-display
49173 running /usr/apps/MMI3GEmergencyApp
===========================================================
Emergency shell started, fix your system and restart again
===========================================================
discplayer_init: IN
nvidia_render_manager_init: IN
INvmRenderManager::GetNvmRenderManager (&pRenderManager);
er = pRenderManager->Init(oConfig);
# Fpga header is not 0x4744482e (0xffffffff)!
App FPGA valid 0
Emergency FPGA valid 1

EmergencyApp-MMI3G: version 21.29.1642, date of build 14.01.2009
pRenderManager->Open()
nvidia_render_manager_init: OUT
discplayer_init: OUT
discplayer_init
discplayer_init: IN
nvidia_render_manager_init: IN
nvidia_render_manager_init: OUT
discplayer_init: OUT
dvdtrackplayer_init
discplayer_init: IN
nvidia_render_manager_init: IN
nvidia_render_manager_init: OUT
discplayer_init: OUT
dvdnavigator_init
created navigator control point with 8249288
mixer_init: IN
mixer_init: OUT
NvTRACELEVEL set to 3 (Level Info)
nVAudio_init: IN
nvidia_render_manager_init();
nvidia_render_manager_init: IN
nvidia_render_manager_init: OUT
nVAudio_init: OUT
installing audio decoders
installing video decoders
nVAudio_init: IN
nvidia_render_manager_init();
nvidia_render_manager_init: IN
nvidia_render_manager_init: OUT
nVAudio_init: OUT
OnIpcGetCaptureUnitSourceCount
Number of displays: 6
Number of layers: 9
Graphics init was successfull: DisplaySize is 800x 480
OnOff: process IPC event 177 198
SWDL: startUpdate HW index 177, variant 9498
OnOff: phase Scan metainfo
We have to erase the FPGA, init the FPGA persistence and delete the orphaned headers (if there are any).
OnOff: phase Erase
OnOff: Progress 000
dev_fd == 10
devctl returned 0
arrayinfo.unit_size 262144
calling devctl with erase struct:
status: 0
offset: 0x40000
limit: 0x40000
devctl(10,-2146694912,xx,12,0) returned 0OnOff: Progress 100
FPGA info header @SWDL V1@
FPGA info version 1
FPGA info variant 9498
FPGA info HW index MU 21
FPGA info region <noRegion>
FPGA info step 0
FPGA info HW index IT 0
FPGA info ignore region/variant 1
FPGA info loop 0
FPGA info repeat 0
FPGA info CRC 3be9dd76
SWDL: Stopping EFS driver!
slay: Unable to find process 'checkPersistence'
result of running command stop_efs_driver.sh is 0
SWDL: Starting EFS driver (automount)!
(devf t1::f3s_recover_boot:141) fs0p1 boot P[E0] U: 58
result of running command start_efs_driver.sh is 0
/HBpersistence/SWDL not found!
(devf t1::f3s_recover_boot:141) fs0p2 boot P[138] U: 50
/HBpersistence/SWDL not found!
(devf t1::f3s_recover_boot:141) fs0p3 boot P[1B3] U: 74
/HBpersistence/SWDL not found!
/HBpersistence/SWDL not found!
/HBpersistence/SWDL not found!
/HBpersistence/SWDL/update.txt doesn't exist
Don't use update.txt
SWDL: Mount from medium 3 (0)
OnOff: variant 9498
OnOff: DeviceName MU9498
Src: Medialauncher is running
Src: mount failed. Retry once in 1 s
Src: Medialauncher is running
Src: mount failed (medium unavailable 2)
SWDL: mount failed
SWDL: Mount from medium 4 (1)
Src: Medialauncher is running
Src: mount failed. Retry once in 1 s
Src: Medialauncher is running
Src: mount failed (medium unavailable 2)
SWDL: mount failed
SWDL: Mount from medium 5 (2)
Src: Medialauncher is running
Src: mount failed. Retry once in 1 s
Src: Medialauncher is running
Src: mount failed (medium unavailable 2)
SWDL: mount failed
SWDL: Mount from medium 2 (3)
Src: mount from CD OK
Src: mount OK
SWDL: mount OK
SWDL: open metainfo /metainfo2.txt
SWDL: open finished (9389)
OnOff: FileAccess for continues!
OnOff: Current file access type: read
SWDL: read finished (9389, 0)
SWDL: parse metainfo
SWDL: check next subdir
SWDL: CheckNextSubDir 1
SWDL: open metainfo /metainfo2.txt
SWDL: open finished (19921)
SWDL: read finished (19921, 0)
SWDL: parse metainfo
SWDL: check next subdir
SWDL: CheckNextSubDir 2
SWDL: open metainfo /metainfo2.txt
SWDL: open finished (22490)
SWDL: read finished (22490, 0)
SWDL: parse metainfo
SWDL: check next subdir
SWDL: CheckNextSubDir 3
SWDL: open metainfo /metainfo2.txt
SWDL: open finished (92291)
SWDL: read finished (92291, 0)
SWDL: parse metainfo
SWDL: check next subdir
SWDL: CheckNextSubDir 4
SWDL: No medium left!
OnOff: error No medium!!!

Vlasoff · Вс мар 20, 2016 1:53 pm

eprst писал(а):Приветствую, имеется Q5 2009 HNav_EU_K0022_2_D1, стоит 9307, по запарке вставил 900 прошивку от 3Gp 9498 , обновленние прошло не полностью, отменить не получилось - после перезагрузки ММИ грузилась частично, потом через зеленку была попытка залить 257 прошивку через эменжерси, теперь она решила что она 9498 и не принимает 9307(фото в приложении), разобрал подпоялся - запустил терминал, вот лог терминала (в приложении), команду boot_1c0000 не принимает, точнее принимает, только толку от нее в моем случае ноль, как и в эмерджи - зеленое окно потом красное (в приложении), команда flashit пишет не извесна ей...
подскажите как оживить?

Вы на всех форумах решили спамить?)
вам нужен Ipl режим, потом уже команды вводить.
А вообще непонятно что вы хотите, прошить в 3гп или восстановить в 3г..

сейчас голова ждёт в слоте флешку с прошивкой 900 от 3gp.
что бы сделал я - флешитом переписал все 6 областей, от нужной прошивки. Но будьте очень аккуратны, все на ваш страх и риск. Если нет понимания что делаете - отдайте людям кто понимает что происходит.
вообще терминал спасет, если есть понимание работы Qnx. Лечить устройство сообщениями с форумов это полный авантюризм с вашей стороны.. Вводя бездумно команды уложите голову наглухо.

eprst · Вс мар 20, 2016 2:06 pm

для начала попробовать так? - карта с прошивкой 257 в слоте №1
FlashIt -d -a -f 40000 /mnt/sdcard10t11/MU9308/fpga/41/default/systemFPGA.hbbin

Vlasoff · Вс мар 20, 2016 2:23 pm

Все 6 областей. Это вторая

eprst · Вс мар 20, 2016 3:54 pm

т.е все эти?
0x00000000 ipl 63264 из 262144 (256kb)

0x00040000 fpga 746472 из 786432 (768 кб)

0x00100000 fpga em 746472 из 786432 (768 кб)

0x001C0000 ifs em 4666284 из 6029312 (5888кб 5мб)

0x00780000 ifs-root 36866456 из 50855936 (49664кб 48мб)

0x03800000 efs ext 23068672 из 58720256 (57344кб 56мб)

eprst · Вс мар 20, 2016 4:08 pm

пока не получается записать...