Hello guys,
I flashed new touch recovery for my evo 3d gsm
and tried to flash a new room and it always gives me the same error.
I was able to flash the same room before maybe something is bricked
and if I want to factory reset it I get the error format_volume: make_extf4fs failed on /dev/block/mmcblk1p2
could you help me guys? im s off btw
this is what I get if I do fastboot oem boot:
###Calling fastboot with: oem boot###
... INFOsetup_tag addr=0x48000100 cmdline add=0x801E5BE4
INFOTAG:Ramdisk OK
INFOTAG:skuid 0x2A408
INFOTAG:hero panel = 0x940026
INFOTAG:engineerid = 0x0
INFOTAG: PS ID = 0x2
INFODevice CID is not super CID
INFOCID is HTC__102
INFOsetting->cid::HTC__102
INFOserial number: HT1CWV210657
INFOcommandline from head: console=ttyHSL0 androidboot.hardware=
INFOshooteru no_console_suspend=1
INFOcommand line length =590
INFOactive commandline: poweron_status=1 board_shooter_u.disable
INFO_uart3=0 diag.enabled=0 board_shooter_u.debug_uart=0 userdat
INFOa_sel=0 androidboot.emmc=true androidboot.pagesize=2048 skui
INFOd=0 ddt=20 androidboot.lb=0 androidboot.baseband=10.13.9020.
INFO08_2M androidboot.cid=HTC__102 androidboot.batt_poweron=goo
INFOd_battery androidboot.carrier=HTC-GER androidboot.mid=PG8630
INFO000 androidboot.keycaps=qwerty androidboot.dq=PASS androidbo
INFOot.mode=normal androidboot.serialno=HT1CWV210657 androidboot
INFO.bootloader=1.49.1107 zygote_oneshot=off msm_watchdog.enable
INFO=1 console=ttyHSL0 androidboot.hardware=shooteru no_console_
INFOsuspend=1
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOaARM_Partion[6].name=devlog
INFOaARM_Partion[7].name=pdata
INFOaARM_Partion[8].name=radio
INFOaARM_Partion[9].name=adsp
INFOaARM_Partion[A].name=radio_config
INFOaARM_Partion.name=modem_st1
INFOaARM_Partion[C].name=modem_st2
INFOpartition number=13
INFOValid partition num=13
INFOddr_get_size: rank 0 reg = E000
INFOddr_get_size: rank 1 reg = E000
INFOddr_get_size: ddr_size = 1024
INFOTZ_HTC_SVC_SET_DDR_MPU ret = 0
INFOsmem 50006000 (phy 50006000): TZ_HTC_SVC_UPDATE_SMEM ret = 0
INFOTZ_HTC_SVC_LOG_OPERATOR ret = 0
INFOTZ_HTC_SVC_DISABLE ret = 6381568 (0x616000)
INFOjump_to_kernel: machine_id(3358), tags_addr(0x48000100), ker
INFOnel_addr(0x48008000)
INFO-------------------hboot boot time:22768 msec
FAILED (status read failed (Too many links))
finished. total time: 4.424s
and If I flash a rom over fastboot commander it gives me:
###Calling fastboot with: flash zip C:\Users\xxx\Downloads\E3DLight_1.1(1).zip###
sending 'zip' (92395 KB)... OKAY [ 10.185s]
writing 'zip'... FAILED (remote: not allowed)
finished. total time: 10.501s
Hi, well a friend of a friend gifted me an LG L9 Model P778G (Carrier: Personal Telecom Country: Argentina). The only thing that he told me was that he dropped his phone and it didn´t turn on back anymore. I externally charged the battery. The phone doesn´t turn on, sometimes when I connect it to my PC (windows XP) it recognizes it as OMAP4430 but only when battery is not connected (when I connect battery it says unrecognized usb device, when I press Vol+ and Vol- with or without battery it also says unrecognized device. Already tried to flash with LG Mobile Support and KDZ but it says phone not connected. I would like to know how can i get the phone back working and if possible with Jelly Bean (I don´t know if phone had JB or ICS, but of what I almost certain is that it was never modified because it belonged to an old person). Please explain with detail though I'm not used to LG (HTC & Samsung owner) and don't know much of it.Thanks to everyone!
USB connection is unstable, it comes nad goes
philohtc said:
USB connection is unstable, it comes nad goes
Click to expand...
Click to collapse
Hi philohtc, you could read and try thishttp://forum.xda-developers.com/showthread.php?t=2677611
Cheers. Good luck.
BajoPrimate said:
Hi philohtc, you could read and try thishttp://forum.xda-developers.com/showthread.php?t=2677611
Cheers. Good luck.
Click to expand...
Click to collapse
Hi, my device doesn´t turn on at all, the only signal i have is the OMAP driver coming and going and sometimes staying a little while, the LG Mobile Support Tool doesn't see the cellphone, hope you can help me, thanks!
philohtc said:
Hi, well a friend of a friend gifted me an LG L9 Model P778G (Carrier: Personal Telecom Country: Argentina). The only thing that he told me was that he dropped his phone and it didn´t turn on back anymore. I externally charged the battery. The phone doesn´t turn on, sometimes when I connect it to my PC (windows XP) it recognizes it as OMAP4430 but only when battery is not connected (when I connect battery it says unrecognized usb device, when I press Vol+ and Vol- with or without battery it also says unrecognized device. Already tried to flash with LG Mobile Support and KDZ but it says phone not connected. I would like to know how can i get the phone back working and if possible with Jelly Bean (I don´t know if phone had JB or ICS, but of what I almost certain is that it was never modified because it belonged to an old person). Please explain with detail though I'm not used to LG (HTC & Samsung owner) and don't know much of it.Thanks to everyone!
Click to expand...
Click to collapse
I believe you still need to install the fastboot driver again.
Take a look at lelus fastboot script thread here - http://forum.xda-developers.com/showthread.php?p=41768774
Read the part in the thread about installing the drivers and about the original fastboot thread.
That should get you ready to be able to do the offline or online kdz flash
xdrc45 said:
I believe you still need to install the fastboot driver again.
Take a look at lelus fastboot script thread here - http://forum.xda-developers.com/showthread.php?p=41768774
Read the part in the thread about installing the drivers and about the original fastboot thread.
That should get you ready to be able to do the offline or online kdz flash
Click to expand...
Click to collapse
Hi, now the phones stays for a while, but still can't get it recognized at KDZ or LG MST.
PS: when installing fastboot drivers after connecting battery it says an LG Logo should appear on screen but it doesn't, thanks for your support
philohtc said:
Hi, now the phones stays for a while, but still can't get it recognized at KDZ or LG MST.
PS: when installing fastboot drivers after connecting battery it says an LG Logo should appear on screen but it doesn't, thanks for your support
Click to expand...
Click to collapse
Use the fastboot script and flash the ICS Uboot and Xloaders
xdrc45 said:
Use the fastboot script and flash the Uboot and Xloaders
Click to expand...
Click to collapse
Sorry to bother, could you give me links to those files for this model? It's my first LG
philohtc said:
Sorry to bother, could you give me links to those files for this model? It's my first LG
Click to expand...
Click to collapse
It's in the lelus fastboot script, option #4
http://forum.xda-developers.com/showthread.php?p=41768774
xdrc45 said:
It's in the lelus fastboot script, option #4
http://forum.xda-developers.com/showthread.php?p=41768774
Click to expand...
Click to collapse
I selected option 6 because option 4 gaved error
This is my log
Plug USB cable
wait 4 seconds and put battery back in.
waiting for OMAP44xx device...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
reading ASIC ID
usb_write 4
usb_read 81
[* said:
read 0 bytes
NumOfSubblocks: 0x5
Subblock ID: 0x1
Subblock Size: 0x5
CH enabled: 0x7
ROM revision: 0x4
Checksum Subblock: 0x15
CHIP: 4430
IDEN: 2f8a54c5c2fdd39e7dbe73b14991c29b1b9d0ec8
MPKH: 5f4092eccddf90fa43f546adf89508b31b9c74795e9516194c0ea6412fdcb7f6
CRC0: 9c669ad9
CRC1: 682adccf
sending 2ndstage to target... f0030002
usb_write 4
usb_write 4
wait 5-lelelel...
[*] msg size = 4
usb_write 21552
[*] data size = 21552
usb_close
Reopen usb...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
waiting for 2ndstage response...
usb_read 4
usb read = aabbccdd
accepted 2ndstage response
sending image to target...
size = 246272
usb_write 4
usb_write 246272
** Done **
< waiting for device >
sending 'x-loader' (384 KB)...
OKAY [ 0.203s]
writing 'x-loader'...
FAILED (remote: partition does not exist)
finished. total time: 0.219s
sending 'u-boot' (1024 KB)...
OKAY [ 0.531s]
writing 'u-boot'...
FAILED (remote: partition does not exist)
finished. total time: 0.547s
Done
Click to expand...
Click to collapse
philohtc said:
I selected option 6 because option 4 gaved error
This is my log
Click to expand...
Click to collapse
OK so you flashed the JB Uboot and Xloader? I'm not at my PC to see the screen options. Try running the kdz now.
xdrc45 said:
OK so you flashed the JB Uboot and Xloader? I'm not at my PC to see the screen options. Try running the kdz now.
Click to expand...
Click to collapse
This happened when I flashed the JB Uboot and Xloader
< waiting for device >
sending 'x-loader' (384 KB)...
OKAY [ 0.203s]
writing 'x-loader'...
FAILED (remote: partition does not exist)
finished. total time: 0.219s
sending 'u-boot' (1024 KB)...
OKAY [ 0.531s]
writing 'u-boot'...
FAILED (remote: partition does not exist)
finished. total time: 0.547s
Done
-----------------------------------------------------------------
I ran KDZ and got the following as usual:
[R&D Test Tools Log File]
21:58:55 : Launching SW update
21:58:55 : Unpacking KDZ
21:59:12 : KDZ file extraced
21:59:30 : Files were extracted.
21:59:30 : LGMobileDL Load.
21:59:30 : Port = -1
21:59:30 : Connecting to phone
21:59:30 : PHONE WAS NOT FOUND!
21:59:32 : ===FINISHED===
philohtc said:
This happened when I flashed the JB Uboot and Xloader
< waiting for device >
sending 'x-loader' (384 KB)...
OKAY [ 0.203s]
writing 'x-loader'...
FAILED (remote: partition does not exist)
finished. total time: 0.219s
sending 'u-boot' (1024 KB)...
OKAY [ 0.531s]
writing 'u-boot'...
FAILED (remote: partition does not exist)
finished. total time: 0.547s
Done
-----------------------------------------------------------------
I ran KDZ and got the following as usual:
[R&D Test Tools Log File]
21:58:55 : Launching SW update
21:58:55 : Unpacking KDZ
21:59:12 : KDZ file extraced
21:59:30 : Files were extracted.
21:59:30 : LGMobileDL Load.
21:59:30 : Port = -1
21:59:30 : Connecting to phone
21:59:30 : PHONE WAS NOT FOUND!
21:59:32 : ===FINISHED===
Click to expand...
Click to collapse
Run the lesus fastbot script again and select option 1 and make sure the drivers are installed. Then try running option #4 again... If successful then try the offline flash here - http://forum.xda-developers.com/showthread.php?t=2085344
And check out this thread - http://forum.xda-developers.com/showthread.php?p=48834061
xdrc45 said:
Run the lesus fastbot script again and select option 1 and make sure the drivers are installed. Then try running option #4 again... If successful then try the offline flash here - http://forum.xda-developers.com/showthread.php?t=2085344
And check out this thread - http://forum.xda-developers.com/showthread.php?p=48834061
Click to expand...
Click to collapse
It says
waiting for 2ndstage response...
usb_read 4
usb_read got: 0, expected: 4, errno: 31
usb_read got GEN_FAILURE - got: 0, expected: 4, errno: 31
usb_read failed: 31
usb read = 0
unexpected 2ndstage response
< waiting for device >
AND STAYS THERE ??
philohtc said:
It says
waiting for 2ndstage response...
usb_read 4
usb_read got: 0, expected: 4, errno: 31
usb_read got GEN_FAILURE - got: 0, expected: 4, errno: 31
usb_read failed: 31
usb read = 0
unexpected 2ndstage response
< waiting for device >
AND STAYS THERE ??
Click to expand...
Click to collapse
Ok have you tried put the device into S/W mode now and see if it's detected? Power off the device, press and hold the volume (+) up button and connect the USB cable from the PC to the device.
xdrc45 said:
Ok have you tried put the device into S/W mode now and see if it's detected? Power off the device, press and hold the volume (+) up button and connect the USB cable from the PC to the device.
Click to expand...
Click to collapse
I could complete step 4 it sended uboot and xloader but it gaved error when it tried to write them, I dont know when it is in S/W mode though Screen is always black. In the offline method I deactivate the wifi card and get the connection in line error but it doesn't appear the pop-up of the language.
philohtc said:
I could complete step 4 it sended uboot and xloader but it gaved error when it tried to write them, I dont know when it is in S/W mode though Screen is always black. In the offline method I deactivate the wifi card and get the connection in line error but it doesn't appear the pop-up of the language.
Click to expand...
Click to collapse
You can try to run the B2CAppSetup.exe, after opening the app, select you phone model and letting it install the drivers, then unplug and plug the USB cable back in and see what happens.
Edit - Also when you connect the device to your PC when in fastboot mode what does it show up as in the PC's device manager?
xdrc45 said:
You can try to run the B2CAppSetup.exe, after opening the app, select you phone model and letting it install the drivers, then unplug and plug the USB cable back in and see what happens.
Edit - Also when you connect the device to your PC when in fastboot mode what does it show up as in the PC's device manager?
Click to expand...
Click to collapse
Under Android Phone > OMAP4430FastBoot USB Device. Can't see where to select model, apparently is automatic recognition
xdrc45 said:
You can try to run the B2CAppSetup.exe, after opening the app, select you phone model and letting it install the drivers, then unplug and plug the USB cable back in and see what happens.
Edit - Also when you connect the device to your PC when in fastboot mode what does it show up as in the PC's device manager?
Click to expand...
Click to collapse
any idea?
philohtc said:
any idea?
Click to expand...
Click to collapse
I'm not sure yet... We need to get the ICS Uboot and Xloaders to install so that you can get into S/W mode.
I'm trying to research on an answer for you.
These L9 are a real pain in the butt.
---------- Post added 30th March 2014 at 12:06 AM ---------- Previous post was 29th March 2014 at 11:47 PM ----------
philohtc said:
any idea?
Click to expand...
Click to collapse
Run the lelus fasrboot again and flash the JB Uboot and Xloader and show mW the log again
Hi I have a serious problem,
So the other day my lg l9 (P760) die completel. Ii try almost everything but my phone continue to had black screen, won't enter in s/w mode and won't hard reset.
Flash boot have this log at the end:
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
waiting for 2ndstage response...
usb_read 4
usb read = aabbccdd
accepted 2ndstage response
sending image to target...
size = 246272
usb_write 4
usb_write 246272
** Done **
< waiting for device >
sending 'x-loader' (384 KB)...
OKAY [ 0.201s]
writing 'x-loader'...
FAILED (remote: partition does not exist)
finished. total time: 0.208s
sending 'u-boot' (1024 KB)...
OKAY [ 0.528s]
writing 'u-boot'...
FAILED (remote: partition does not exist)
finished. total time: 0.535s
Done
When i put it in usb the device connect and disconect continuosly. Only if i try to boot fastboot with vol+ pressed i can see the devices but the screen still black and after a couple of minute it disconnect. So i can't use the lg mobile tool. I try KDZ off-line and on-line procedure but the sw crah or do not recognize the phone.
Can someone help me please?
Flash with fastboot u-boot and x-loader there are some tutorials for fastboot for our device.
LG L9-P760 /TapatalkVIP 4.7.3 /4.4.4KK AxxionKat 1.4.0 by @Xerdox
Cytrus224 said:
Flash with fastboot u-boot and x-loader there are some tutorials for fastboot for our device.
LG L9-P760 /TapatalkVIP 4.7.3 /4.4.4KK AxxionKat 1.4.0 by @Xerdox
Click to expand...
Click to collapse
Thank you for your answer Cytrus224, but i try to flash with fastbot using this guide (http://forum.xda-developers.com/showthread.php?t=2411265) but flashbot log still the same as the post below.
Can you suggest me something or a better guide?
Thank you
Had same problem yesterday, after changing philz touch to new artas182x twrp by Flashify flashing. Phone stock on LG logo, s/w not working. I used this method found on polish forum
http://forum.android.com.pl/f764/re-lock-bootloader-l9-328381
1. Download omap4boot
2. Download ics u-boot and x-loader.
3. Install fastboot drivers(all tutorials linked in post #1 in upper link)
4. Flash u-boot and x-loader.
5. Now you can turn again phone into s/w and flash stock roms
Sorry for my bad English
LG L9-P760 /TapatalkVIP 4.7.3 /4.4.4KK AxxionKat 1.4.0 by @Xerdox
Cytrus224 said:
Had same problem yesterday, after changing philz touch to new artas182x twrp by Flashify flashing. Phone stock on LG logo, s/w not working. I used this method found on polish forum
1. Download omap4boot
2. Download ics u-boot and x-loader.
3. Install fastboot drivers(all tutorials linked in post #1 in upper link)
4. Flash u-boot and x-loader.
5. Now you can turn again phone into s/w and flash stock roms
Sorry for my bad English
LG L9-P760 /TapatalkVIP 4.7.3 /4.4.4KK AxxionKat 1.4.0 by @Xerdox
Click to expand...
Click to collapse
Doesn't work.. this is the result:
C:\omap4boot-for_optimus-v1.21>fastboot flash x-loader p1.bin
sending 'x-loader' (384 KB)...
OKAY [ 0.200s]
writing 'x-loader'...
FAILED (remote: partition does not exist)
finished. total time: 0.208s
C:\omap4boot-for_optimus-v1.21>fastboot flash u-boot p2.bin
sending 'u-boot' (1024 KB)...
OKAY [ 0.528s]
writing 'u-boot'...
FAILED (remote: partition does not exist)
finished. total time: 0.535s
< waiting for device >
opening device: \\.\COM5
OKAY [ 0.004s]
greeting device for command mode
OKAY [ 0.003s]
identifying device
...serial = 0x42BC4F8
...chip-id = 0x811
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.008s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.007s]
validating files
OKAY [ 0.001s]
switching to download mode
OKAY [ 0.001s]
greeting device for image downloading
OKAY [ 0.002s]
sending programmer
Unexpected packet: 4. Was expecting: 3
FAILED (blank-flash:sahara-transfer-image:send-image:unexpected packet)
there were something wrong in programmer.mbn file
is any one knows what programmer.mbn file contain .
i thought it contain qualcomm msm programmer code and some sdi.img file content.
before adding sdi file it cant start download but after adding some sdi content then phone goes to downloading image but has some packet problem .please help
Mine tooo.......
hiten7236 said:
< waiting for device >
opening device: \\.\COM5
OKAY [ 0.004s]
greeting device for command mode
OKAY [ 0.003s]
identifying device
...serial = 0x42BC4F8
...chip-id = 0x811
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.008s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.007s]
validating files
OKAY [ 0.001s]
switching to download mode
OKAY [ 0.001s]
greeting device for image downloading
OKAY [ 0.002s]
sending programmer
Unexpected packet: 4. Was expecting: 3
FAILED (blank-flash:sahara-transfer-image:send-image:unexpected packet)
there were something wrong in programmer.mbn file
is any one knows what programmer.mbn file contain .
i thought it contain qualcomm msm programmer code and some sdi.img file content.
before adding sdi file it cant start download but after adding some sdi content then phone goes to downloading image but has some packet problem .please help
Click to expand...
Click to collapse
Can u just upload the file in a zip which ur using...ill check that i may help u....
I have the same problem, I was constantly changing roms and never had this problem at most had a bootloop, but that was all. :crying:
I tried with Miflash, blankflash does not work, the only options that remain are to develop the missing files and / or find out who gave him solution for hardbrick moto X and moto G and ask him where he got those files or how made the files?
So, can you tell me... We need to find any solution, the problem is old, I realized when I read the forums and others.
My English is horrible, in fact I do not speak English, I speak Spanish, but I do understand some English
I'm new here
Harsh_1998 said:
Can u just upload the file in a zip which ur using...ill check that i may help u....
Click to expand...
Click to collapse
@Harsh_1998 I have a blankflash zip file but its a older version and I need a newer but Motorola isn't releasing blankflash zip file for Moto X Play and I found it myself and now my device got hard bricked can you see to it I need a blankflash for unbricking my device. Please help!!!!
Hi everyone,
I am having a problem to my moto G xt1032 which i recently updated through OTA. afetr I installed it dies. never turning on. but the led light will blink after i charge a few minutes. but never turn on.
Do anyone have an idea?
please help me.
I would really appreciate and commend.
thank you.
Firstly I flashed it with a xt1033 firmware 4.4.4 which has a dual sim flatform due to I cannot flash it with its own xt1032 firmware. maybe its a corrupt file.
After done flashing with xt1033, the phone work perfectly. it only happens after i recieved the system update from android system update
It is recognized by your PC ?
Sent from my SM-T116 using XDA Free mobile app
Soufiansky said:
It is recognized by your PC ?
Sent from my SM-T116 using XDA Free mobile app
Click to expand...
Click to collapse
Qualcomm HS-USB QDLoader 9008
on device manager
skripton78 said:
Qualcomm HS-USB QDLoader 9008
on device manager
Click to expand...
Click to collapse
Can you try to flash again the stock firmware ?
no display at all. i had try 2 and 15 minute method, even i tried removing and draining the electrons lift on the board no effects.
i cant put to recovery and fastboot mode. but the phone was detected as Qualcomm HS-USB QDLoader 9008. but commands is only waiting for device.
in short, dead.
skripton78 said:
Qualcomm HS-USB QDLoader 9008
on device manager
Click to expand...
Click to collapse
its bricked. you need blank flash files to flash the bootloader again, here try this http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
blank-flash
nk-flash
opening device: \\.\COM11
OKAY [ -0.000s]
greeting device for command mode
OKAY [ -0.000s]
identifying device
...serial = 0x485D868
...chip-id = 0x800 (MSM8226)
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ -0.000s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ -0.000s]
validating files
OKAY [ 0.080s]
switching to download mode
OKAY [ 0.010s]
greeting device for image downloading
OKAY [ 0.000s]
sending programmer
OKAY [ 0.010s]
flashing singleimage
FAILED (blank-flash:sdl-transfer-image:sdl-hello:error reading packet)
C:\Users\khyrt klyetz\Downloads\Compressed\blankflash\blankflash>pause
Press any key to continue . . .
skripton78 said:
nk-flash
opening device: \\.\COM11
OKAY [ -0.000s]
greeting device for command mode
OKAY [ -0.000s]
identifying device
...serial = 0x485D868
...chip-id = 0x800 (MSM8226)
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ -0.000s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ -0.000s]
validating files
OKAY [ 0.080s]
switching to download mode
OKAY [ 0.010s]
greeting device for image downloading
OKAY [ 0.000s]
sending programmer
OKAY [ 0.010s]
flashing singleimage
FAILED (blank-flash:sdl-transfer-image:sdl-hello:error reading packet)
C:\Users\khyrt klyetz\Downloads\Compressed\blankflash\blankflash>pause
Press any key to continue . . .
Click to expand...
Click to collapse
FYI : this is already unlocked : status code 3 last time i'd flashed the firmware.
skripton78 said:
FYI : this is already unlocked : status code 3 last time i'd flashed the firmware.
Click to expand...
Click to collapse
do anyone have? here.