Develop Bugs

[Q] help me ! nexus 7 2013 wifi only with usb mf-190s via OTG

This is my usb log. Plz help me!
PPP Widget version 1.3.3
USB_ModeSwitch log from Tue Oct 01 17:36:52 ICT 2013
Raw args from udev: 1-1/1-1:1.0
Using top device dir /sys/bus/usb/devices/1-1
----------------
USB values from sysfs:
manufacturer HSPA,Incorporated
product HSPA WCDMA Technologies MSM
serial MF190SVIED010000
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /data/data/de.draisberghof.pppwidget/app_tmp/19d2.2000
! matched. Reading config data
devList 1:
config: TargetVendor set to 19d2
config: TargetProductList set to 0001,0002,0015,0016,0017,0031,0037,0052,0055,0061,0063,0064,0066,0091,0108,0117,0128,0157,0177,1402,2002,2003
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1
Command to be run:
usb_modeswitch -I -W -D -s 20 -u -1 -b 1 -g 2 -v 19d2 -p 2000 -f $cB
Verbose debug output of usb_modeswitch and libusb follows
(Note that some USB errors are to be expected in the process)
--------------------------------
Reading long config from command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 1.2.7 (C) Josua Dietze 2012
* Based on libusb0 (0.1.12 and above)
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x19d2
DefaultProduct= 0x2000
TargetVendor= 0x19d2
TargetProduct= not set
TargetClass= not set
TargetProductList="0001,0002,0015,0016,0017,0031,0037,0052,0055,0061,0063,0064,0066,0091,0108,0117,0128,0157,0177,1402,2002,2003"
DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
QuantaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
BlackberryMode=0
PantechMode=0
MessageEndpoint= not set
MessageContent="5553424312345678000000000000061e000000000000000000000000000000"
MessageContent2="5553424312345679000000000000061b000000020000000000000000000000"
MessageContent3="55534243123456702000000080000c85010101180101010101000000000000"
NeedResponse=1
ResponseEndpoint= not set
InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode enabled
Use given bus/device number: 001/002 ...
Looking for default devices ...
bus/device number matched
searching devices, found USB ID 19d2:2000
found matching vendor ID
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Skipping the check for the current configuration
Using interface number 0
Using endpoints 0x01 (out) and 0x81 (in)
USB description data (for identification)
-------------------------
Manufacturer: HSPA,Incorporated
Product: HSPA WCDMA Technologies MSM
Serial No.: MF190SVIED010000
-------------------------
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Reading the response to message 1 (CSW) ...
OK, response successfully read (13 bytes).
Trying to send message 2 to endpoint 0x01 ...
OK, message successfully sent
Reading the response to message 2 (CSW) ...
OK, response successfully read (13 bytes).
Trying to send message 3 to endpoint 0x01 ...
OK, message successfully sent
Reading the response to message 3 (CSW) ...
Response reading got error -32
Device is gone, skipping any further commands
Bus/dev search active, referring success check to wrapper. Bye.
ok:busdev
--------------------------------
(end of usb_modeswitch output)
Checking success of mode switch for max. 20 seconds ...
Reading attributes ...
Reading attributes ...
Reading attributes ...
Reading attributes ...
Waiting for device file system (5 sec.) ...
Reading attributes ...
Mode switch has completed
Mode switching was successful, found 19d2:0108 (HSPA,Incorporated: HSPA WCDMA Technologies MSM)
Device class of first interface is ff
Now checking for bound driver ...
No driver has bound to interface 0 yet
Module loader is /system/bin/insmod
Trying to find and install main driver module "option"
Checking for active driver path: /sys/bus/usb-serial/drivers/option1
Driver not active, try to find module "option"
Can't find module "option"
Existing path found:
No way to use driver "option"
- try falling back to "usbserial"
Module "usb_serial" not found, can't do more here
Driver binding did not work for this device
All done, exiting

Rooting with linux

Tried a few methods for getting root, none of which worked. I'm running a d851 with d85120g software. Ubuntu as my desktop. Here's a step by step pulled from various sources.
1. Put your phone in developer mode. Go to settings-->about phone. Click on build 8ish times until you see "you're a developer"
2. Go to settings-->developer options-->enable USB debugging
Now we need the desktop to recognize the phone
3. In your favorite text editor, you'll need to create a text file named /etc/udev/rules.d/51-android.rules
4. Copy this line into the file and save it:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666", GROUP="plugdev"
(Source here)
5. In a terminal:
Code:
sudo chmod a+r /etc/udev/rules.d/51-android.rules
6.
Code:
sudo service udev restart && sudo killall -9 adb
6a. Get this file and
Code:
sudo chmod a+r ./qcdlcomm.py
from that directory. (Source)
Next steps are modified from here.
7. Download and extract the zip file: http://bit.ly/1Ln9FKB .
7a. Move qcdlcomm.py to wherever you extracted the above file.
8. Connect your phone. At some point you can choose your USB connection type. Reports state it only works with PTP mode (v. MTP), but I didn't try MTP.
9. Terminal:
Code:
adb devices
You should see your phone listed. Then, in the same directory as the files from step 7:
10.
Code:
adb push ./busybox /data/local/tmp && adb push ./UPDATE-SuperSU-v2.46.zip /data/local/tmp
Now you want to get in download mode.
11. Unplug and turn off your phone, then hold volume up as you plug the cable back in. You should see "download" or something on the screen.
Next steps taken from here.
12.
Code:
ls /dev/ttyUSB*
Make note of the devices. You'll try the highest device number first in a few steps.
13.
Code:
sudo rmmod cdc_acm && sudo rmmod usbserial
You'll get an error if there's anything else using usbserial. If so, sudo rmmod that module, then rerun
Code:
sudo rmmod usbserial
14.
Code:
sudo modprobe usbserial vendor=0x1004 product=0x633e
15.
Code:
sudo python ./qcdlcomm.py /dev/ttyUSB*< ./root
Replace the device with the output from step 12. Something should happen here. (BTW, at some point the phone screen says "flashing firmware" or something. There's a progress bar. It never moves past 0%"
16. Type "LEAVE" at the hash prompt that's left. At this point, your phone may not reboot. If not, type "exit" (or ctrl+c) and disconnect your phone. Then reconnect the phone.
17.
Code:
ls /dev/ttyUSB*
again. You may have lost a usb device. If so, repeat:
18.
Code:
sudo python ./qcdlcomm.py /dev/ttyUSB*
with the next highest device from above.
19. Type "LEAVE" again. Device should reboot. You should have root.
Some of this from memory, so if anyone has any suggestions, LMK. Hope this helps someone.

Good
Sent from my SM-G361H using Xposed Modules

These instructions killed my phone....
All steps went absolutely fine, except that the phone refused to boot. After the fact I found other, similar, instructions that also tell you to push and run lg_root.sh.

slow64 said:
These instructions killed my phone....
All steps went absolutely fine, except that the phone refused to boot. After the fact I found other, similar, instructions that also tell you to push and run lg_root.sh.
Click to expand...
Click to collapse
Well, I just got a new d851. This process was still harder than it should be. I had trouble at step 15; it never dropped me back to back to a hash prompt. I had the scary task of battery pulling/ctrl+c in the middle of the flash a couple of times, but no bricking. Also noticed a typo in my instructions, which took me a while to figure out. Those instructions wouldn't have worked as I originally posted them. Anyway, it worked again. Purple drake still didn't work, and there STILL doesn't appear to be an easy way to root on linux.

nola mike said:
Well, I just got a new d851. This process was still harder than it should be. I had trouble at step 15; it never dropped me back to back to a hash prompt. I had the scary task of battery pulling/ctrl+c in the middle of the flash a couple of times, but no bricking. Also noticed a typo in my instructions, which took me a while to figure out. Those instructions wouldn't have worked as I originally posted them. Anyway, it worked again. Purple drake still didn't work, and there STILL doesn't appear to be an easy way to root on linux.
Click to expand...
Click to collapse
I notice my product ID differs from yours. Is this unimportant? I have been really wanting to get root on this for a while now, and this is the most promising looking aggregation of all available information I've found so far.

Don't know why the product ID would be different (at least the vendor ID should be the same). What's your dmesg/lsusb output? It uses the ID to create the udev rules in step 4, so you'd need it correct there. In step 14 I don't know if it would work if you left the vendor info out and just did a modprobe usbserial.

nola mike said:
Don't know why the product ID would be different (at least the vendor ID should be the same). What's your dmesg/lsusb output? It uses the ID to create the udev rules in step 4, so you'd need it correct there. In step 14 I don't know if it would work if you left the vendor info out and just did a modprobe usbserial.
Click to expand...
Click to collapse
I was thinking I'd just substitute my ProdID in the necessary locations.
dmesg:
Code:
[11036.082260] usb 3-2: new high-speed USB device number 10 using ehci-pci
lsusb:
Code:
[~]$ lsusb | grep LG
Bus 003 Device 010: ID 1004:631d LG Electronics, Inc. Optimus Android Phone (Camera/PTP Mode)

Sounds good, keep us updated.

Well, just got my third d851, running v30e firmware. Now doesn't work, getting stuck at step 15. When I plug in in download mode, the phone switches to the "firmware update" screen before I do anything. This is the dmesg output.
Code:
[ 6277.744082] usb 1-1: new high-speed USB device number 28 using ehci-pci
[ 6277.893938] usb 1-1: New USB device found, idVendor=1004, idProduct=633a
[ 6277.893944] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 6277.893948] usb 1-1: Product: LGE Android Phone
[ 6277.893950] usb 1-1: Manufacturer: LG Electronics Inc.
[ 6277.893953] usb 1-1: SerialNumber: LGD8511199581b
[ 6277.894874] usbserial_generic 1-1:1.0: Generic device with no bulk out, not allowed.
[ 6277.894890] usbserial_generic: probe of 1-1:1.0 failed with error -5
[ 6277.895019] cdc_acm 1-1:1.0: ttyACM0: USB ACM device
[ 6277.900634] usbserial_generic 1-1:1.2: The "generic" usb-serial driver is only for testing and one-off prototypes.
[ 6277.900638] usbserial_generic 1-1:1.2: Tell [email protected] to add your device to a proper driver.
[ 6277.900641] usbserial_generic 1-1:1.2: generic converter detected
[ 6277.900827] usb 1-1: generic converter now attached to ttyUSB0
[ 6534.787683] usb 1-1: USB disconnect, device number 28
[ 6534.791136] generic ttyUSB0: generic converter now disconnected from ttyUSB0
[ 6534.791175] usbserial_generic 1-1:1.2: device disconnected
[ 6550.456114] usb 1-1: new high-speed USB device number 29 using ehci-pci
[ 6550.605565] usb 1-1: New USB device found, idVendor=1004, idProduct=633a
[ 6550.605571] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 6550.605574] usb 1-1: Product: LGE Android Phone
[ 6550.605578] usb 1-1: Manufacturer: LG Electronics Inc.
[ 6550.605581] usb 1-1: SerialNumber: LGD8511199581b
[ 6550.606530] usbserial_generic 1-1:1.0: Generic device with no bulk out, not allowed.
[ 6550.606559] usbserial_generic: probe of 1-1:1.0 failed with error -5
[ 6550.606720] cdc_acm 1-1:1.0: ttyACM0: USB ACM device
[ 6550.612943] usbserial_generic 1-1:1.2: The "generic" usb-serial driver is only for testing and one-off prototypes.
[ 6550.612948] usbserial_generic 1-1:1.2: Tell [email protected] to add your device to a proper driver.
[ 6550.612951] usbserial_generic 1-1:1.2: generic converter detected
[ 6550.613624] usb 1-1: generic converter now attached to ttyUSB0

Lumia 950 XL Dual Sim having problem flashing need help.

Hello everyone I recently got a Lumia 950 XL from B&H not knowing that I ended up with one from Mexico no big deal but id like to have the Reset Protection on the phone since that's a US only feature. So I look up my phone on the back of it an such and so on. And I try this one code that suppose to change my product code which didn't work I try even my original code of my device and nothing happen just errors. this what ive done. Mine a RM-1116 and product number 059X5P5 I wanted to put on my device a US code of 059X505 since there both RM-116 then I put this code down as followed try both as a test.
"C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool\thor2.exe" -mode uefiflash -ffufile C:\ProgramData\Microsoft\Packages\Products\RM1116_1078.0038.10586.13080.15285.033372_retail_prod_signed.ffu -skip_flash -productcodeupdate 059X5P5
"C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool\thor2.exe" -mode uefiflash -ffufile C:\ProgramData\Microsoft\Packages\Products\RM1116_1078.0038.10586.13080.15285.033372_retail_prod_signed.ffu -skip_flash -productcodeupdate 059X505
But both didn't work. I ended up with a huge error. If I could get some help on this or more clarification of what im doing wrong please help im not a coder just ran into this code from a different forum I belong too. here the log off my error below.
Process started Mon Apr 25 08:58:17 2016
Logging to file C:\Users\Daniel\AppData\Local\Temp\thor2_win_20160425085817_ThreadId-232.log
Debugging enabled for uefiflash
Initiating FFU flash operation
WinUSB in use.
isDeviceInNcsdMode
Normal mode detected
Rebooting to the normal mode...
Resp from NCSd {"id":7,"jsonrpc":"2.0","result":null}
[THOR2_flash_state] Switching to flash mode
Detecting UEFI responder
HELLO success
Lumia Boot Manager detected
Check status of battery
State of charge 69, charging current 71
Protocol version 2.6 Implementation version 2.48
Booting to FlashApp
Reboot to FlashApp command sent successfully.
Verifying that device is online
Device is online
Detecting UEFI responder
HELLO success
Lumia Flash detected
Protocol version 2.41 Implementation version 2.75
[THOR2_flash_state] Pre-programming operations
Disable timeouts
Get flashing parameters
Lumia Flash detected
Protocol version 2.41 Implementation version 2.75
Size of one transfer is 2363392
MMOS RAM support: 1
Size of buffer is 2359296
Number of eMMC sectors: 61071360
Platform ID of device: Microsoft.MSM8994.P6211.2.1
Async protocol version: 01
Security info:
Platform secure boot enabled
Secure FFU enabled
JTAG eFuse blown
RDC not found
Authentication not done
UEFI secure boot enabled
SHK enabled
Device supports FFU protocols: 0015
Subblock ID 32
[THOR2_flash_state] Device programming started
Using secure flash method
CoreProgrammer version 2015.06.10.001.
Start programming signed ffu file C:\ProgramData\Microsoft\Packages\Products\RM1116_1078.0038.10586.13080.15285.033372_retail_prod_signed.ffu
FfuReader version is 2015061501
Send FlashApp write parameter: 0x4d544f00
Perform handshake with UEFI...
Flash app: Protocol Version 2.41 Implementation Version 2.75
Unknown sub block detected. Skip...
DevicePlatformInfo: Microsoft.MSM8994.P6211.2.1
Unknown sub block detected. Skip...
Unknown sub block detected. Skip...
Supported protocol versions bitmap is 15
Secure FFU sync version 1 supported.
Secure FFU async version 1 supported.
Secure FFU sync version 2 supported.
Secure FFU async version 2 supported.
CRC header v. 1
CRC align bytes. 4
Get CID of the device...
Get EMMC size of the device...
Emmc size in sectors: 61071360
CID: Hynix, Size 29820 MB
Start charging...
Requested write param 0x43485247 is not supported by this flash app version.
Start charging... DONE. Status = 0
ConnSpeedEcho: Elapsed= 0.221000, EchoSpeed= 30.54, Transferred= 7077918 bytes
Get security Status...
Security Status:
Platform secure boot is enabled.
Secure eFUSE is enabled.
JTAG is disabled.
RDC is missing from the device.
Authentication is not done.
UEFI secure boot is enabled.
Secondary HW key exists.
Get RKH of the device...
RKH of the device is 427D8FD5A7F227820D5B11BF8C6F7670C0A0622CC61BA95AAEE18F7517FC0B77
Get ISSW Version...
ISSW Version: 291
Thu Nov 19 16:02:20 EET 2015 ;ISSW v0291; rg0; OS; DNE; KCI 1318; ASIC 899x;
Get system memory size...
Size of system mem: 3145728 KB
Read antitheft status...
Reset Protection status: Disabled
Reset Protection version: 1.1
Send backup to RAM req...
Unable to parse FFU file. File open failed
programming operation failed!
Unable to parse FFU file. File open failed, Error code: 2
Operation took about 34.00 seconds.
FFU_PARSING_ERROR
THOR2 1.8.2.18 exited with error code 2228224 (0x220000)

same

maliksantika said:
same
Click to expand...
Click to collapse
you can ask for help in telegram group.its called "LumiaWOA" join it and ask there

Sahara fail!! help! tried EVERYTHING!

Hi, i just bricked my phone and now it shows the ZUK logo briefly and then the screen goes black and the led keeps on.
i tried the whole cable trick (connecting the black and the green cable) and now the whole device's screen is black and when i try to flash a rom with QFIL i get this (log file attached):
Validating Application Configuration
Load APP Configuration
COM:10
SAHARA:True
SAHARA:C:\zuk\prog_emmc_firehose_8996_ddr.elf
SEARCHPATH:C:\zuk
RAWPROGRAM:
rawprogram0.xml
PATCH:
patch0.xml
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8x26
VALIDATIONMODE:0
RESETAFTERDOWNLOAD:False
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
ENABLEMULTISIM:False
Load ARG Configuration
Validating Download Configuration
Image Search Path: C:\zuk
RAWPROGRAM file path: C:\zuk\rawprogram0.xml
PATCH file path:C:\zuk\patch0.xml
Programmer Path:C:\zuk\prog_emmc_firehose_8996_ddr.elf
Process Index:0
Start Download
Program Path:C:\zuk\prog_emmc_firehose_8996_ddr.elf
Binary build date: May 13 2015 @ 14:41:37
QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files\Qualcomm\QPST\bin\QSaharaServer.exe -p \\.\COM10 -s 13:C:\zuk\prog_emmc_firehose_8996_ddr.elf 'Current working dir: C:\Users\edoardo\AppData\Roaming\Qualcomm\QFIL
Sahara mappings:
2: amss.mbn
6: apps.mbn
8: dsp1.mbn
10: dbl.mbn
11: osbl.mbn
12: dsp2.mbn
16: efs1.mbn
17: efs2.mbn
20: efs3.mbn
21: sbl1.mbn
22: sbl2.mbn
23: rpm.mbn
25: tz.mbn
28: dsp3.mbn
29: acdb.mbn
30: wdt.mbn
31: mba.mbn
13: C:\zuk\prog_emmc_firehose_8996_ddr.elf
01:47:56: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
01:47:56: ERROR: function: sahara_main:854 Sahara protocol error
01:47:56: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
yes, i tried putting the folder in C:/ and name it like zuk. and i do have the windows drivers installed. when i open Device manager i get: "Qualcomm HS-USB QDLoader 9008"
can anybody help me???

ok, i managed to solve the problem: the thing was that i was changing cable when i got the phone on qfil mode. i managed to remove the bridge between the two cables without removing the cable and flashing. it worked!

QPST v2.7.460
Try this. The new version fixed the sahara error. I tried myself and its working.
http://www.androidbrick.com/download/download-latest-qualcomm-flasher-qfil-qpst-2-7-460/

edulus91 said:
Hi, i just bricked my phone and now it shows the ZUK logo briefly and then the screen goes black and the led keeps on.
i tried the whole cable trick (connecting the black and the green cable) and now the whole device's screen is black and when i try to flash a rom with QFIL i get this (log file attached):
Validating Application Configuration
Load APP Configuration
COM:10
SAHARA:True
SAHARA:C:\zuk\prog_emmc_firehose_8996_ddr.elf
SEARCHPATH:C:\zuk
RAWPROGRAM:
rawprogram0.xml
PATCH:
patch0.xml
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8x26
VALIDATIONMODE:0
RESETAFTERDOWNLOAD:False
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
ENABLEMULTISIM:False
Load ARG Configuration
Validating Download Configuration
Image Search Path: C:\zuk
RAWPROGRAM file path: C:\zuk\rawprogram0.xml
PATCH file path:C:\zuk\patch0.xml
Programmer Path:C:\zuk\prog_emmc_firehose_8996_ddr.elf
Process Index:0
Start Download
Program Path:C:\zuk\prog_emmc_firehose_8996_ddr.elf
Binary build date: May 13 2015 @ 14:41:37
QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files\Qualcomm\QPST\bin\QSaharaServer.exe -p \.\COM10 -s 13:C:\zuk\prog_emmc_firehose_8996_ddr.elf 'Current working dir: C:\Users\edoardo\AppData\Roaming\Qualcomm\QFIL
Sahara mappings:
2: amss.mbn
6: apps.mbn
8: dsp1.mbn
10: dbl.mbn
11: osbl.mbn
12: dsp2.mbn
16: efs1.mbn
17: efs2.mbn
20: efs3.mbn
21: sbl1.mbn
22: sbl2.mbn
23: rpm.mbn
25: tz.mbn
28: dsp3.mbn
29: acdb.mbn
30: wdt.mbn
31: mba.mbn
13: C:\zuk\prog_emmc_firehose_8996_ddr.elf
01:47:56: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
01:47:56: ERROR: function: sahara_main:854 Sahara protocol error
01:47:56: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
yes, i tried putting the folder in C:/ and name it like zuk. and i do have the windows drivers installed. when i open Device manager i get: "Qualcomm HS-USB QDLoader 9008"
can anybody help me???
Click to expand...
Click to collapse
The same happened to me it was fixed by unlocking the bootloader again as this happens when the bootloader is relocked in my case while flashing a zui based custom rom

QFIL Sahara Error
spandu500 said:
The same happened to me it was fixed by unlocking the bootloader again as this happens when the bootloader is relocked in my case while flashing a zui based custom rom
Click to expand...
Click to collapse
My Phone IS Bricked. Automatically vibrates and blinks led with short 10-12 second interval. I have managed to get it as Qloader 9008 on pc but unable to flash using QFIL or Mi Flash tool.
Please Help!!!!

ChetanLokhande said:
My Phone IS Bricked. Automatically vibrates and blinks led with short 10-12 second interval. I have managed to get it as Qloader 9008 on pc but unable to flash using QFIL or Mi Flash tool.
Please Help!!!!
Click to expand...
Click to collapse
Well first press the vol up and power button until the the led blinks leave it immediately
If successfully done then the boot logo should flash and then the led would stop blinking
If the led still blinks try again
If the led stops blinking the go ahead
Hold the vol up and down button simultaneously and plug it to pc
It should then boot into fastboot
From there unlock it and you're good to go

edulus91 said:
Hi, i just bricked my phone and now it shows the ZUK logo briefly and then the screen goes black and the led keeps on.
i tried the whole cable trick (connecting the black and the green cable) and now the whole device's screen is black and when i try to flash a rom with QFIL i get this (log file attached):
Validating Application Configuration
Load APP Configuration
COM:10
SAHARA:True
SAHARA:C:\zuk\prog_emmc_firehose_8996_ddr.elf
SEARCHPATH:C:\zuk
RAWPROGRAM:
rawprogram0.xml
PATCH:
patch0.xml
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8x26
VALIDATIONMODE:0
RESETAFTERDOWNLOAD:False
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
ENABLEMULTISIM:False
Load ARG Configuration
Validating Download Configuration
Image Search Path: C:\zuk
RAWPROGRAM file path: C:\zuk\rawprogram0.xml
PATCH file path:C:\zuk\patch0.xml
Programmer Path:C:\zuk\prog_emmc_firehose_8996_ddr.elf
Process Index:0
Start Download
Program Path:C:\zuk\prog_emmc_firehose_8996_ddr.elf
Binary build date: May 13 2015 @ 14:41:37
QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files\Qualcomm\QPST\bin\QSaharaServer.exe -p \\.\COM10 -s 13:C:\zuk\prog_emmc_firehose_8996_ddr.elf 'Current working dir: C:\Users\edoardo\AppData\Roaming\Qualcomm\QFIL
Sahara mappings:
2: amss.mbn
6: apps.mbn
8: dsp1.mbn
10: dbl.mbn
11: osbl.mbn
12: dsp2.mbn
16: efs1.mbn
17: efs2.mbn
20: efs3.mbn
21: sbl1.mbn
22: sbl2.mbn
23: rpm.mbn
25: tz.mbn
28: dsp3.mbn
29: acdb.mbn
30: wdt.mbn
31: mba.mbn
13: C:\zuk\prog_emmc_firehose_8996_ddr.elf
01:47:56: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
01:47:56: ERROR: function: sahara_main:854 Sahara protocol error
01:47:56: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
yes, i tried putting the folder in C:/ and name it like zuk. and i do have the windows drivers installed. when i open Device manager i get: "Qualcomm HS-USB QDLoader 9008"
can anybody help me???
Click to expand...
Click to collapse
can you resolve this ?

darthvader0235 said:
Try this. The new version fixed the sahara error. I tried myself and its working.
http://www.androidbrick.com/download/download-latest-qualcomm-flasher-qfil-qpst-2-7-460/
Click to expand...
Click to collapse
same problem with this

Use this QPST version. it will solve your problem.
Download QPST > http://www.androidbrick.com/download/download-latest-qualcomm-flasher-qfil-qpst-2-7-460/

Sahara fail
Good Morning people.
The QPST 2.7.460 show this problem :
13: C:\Program Files\Qualcomm\QPST\bin\K33-b36_S150_161114_ROW_QPST\SW\prog_emmc_firehose_8937_ddr.mbn
01:47:56: ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.
01:47:56: ERROR: function: sahara_main:924 Sahara protocol error
01:47:56: ERROR: function: main:303 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
Device: LENOVO K6 PLUS dual chip k53b36

fernando_gomes29 said:
Good Morning people.
The QPST 2.7.460 show this problem :
13: C:\Program Files\Qualcomm\QPST\bin\K33-b36_S150_161114_ROW_QPST\SW\prog_emmc_firehose_8937_ddr.mbn
01:47:56: ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.
01:47:56: ERROR: function: sahara_main:924 Sahara protocol error
01:47:56: ERROR: function: main:303 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
Device: LENOVO K6 PLUS dual chip k53b36
Click to expand...
Click to collapse
same problem

AymenDe7 said:
same problem
Click to expand...
Click to collapse
Try to minimise the directory names..... I had the exact same problem and this solved it.

sahara fail
JashanjotSidhu said:
Try to minimise the directory names..... I had the exact same problem and this solved it.
Click to expand...
Click to collapse
Problem continue

fernando_gomes29 said:
Problem continue
Click to expand...
Click to collapse
Try to start the download immediately as soon as device goes in EDL mode.
Select all the files in QFIL before entering EDL and just click Download when the device goes in EDL.

Sahara fail 2
JashanjotSidhu said:
Try to start the download immediately as soon as device goes in EDL mode.
Select all the files in QFIL before entering EDL and just click Download when the device goes in EDL.
Click to expand...
Click to collapse
I´ve tried another way, the messenger is:
Start Download
COM Port number:4
Switch To EDL
Download Fail:Fail to find QDLoader port after switch
Finish Download

i just switched to win 7 from win 10.. i feel win 7 is better than win 10 when it comes to flashing & stuff

Sahara fail 2
I got it, I installed an old QFIL,

Solved
The solution is very simple: just boot into fastboot mode and reboot edl (if using custom rom) and as soon as it enters click the download button on qfil. Have to be a little fast but works everytime.

BishalSC said:
The solution is very simple: just boot into fastboot mode and reboot edl (if using custom rom) and as soon as it enters click the download button on qfil. Have to be a little fast but works everytime.
Click to expand...
Click to collapse
How do you enter EDL through fastboot?

Shinichi Kudo said:
How do you enter EDL through fastboot?
Click to expand...
Click to collapse
Using the following commands...
fastboot -i 0x2b4c oem reboot-edl

Nokia lumia 822 - error : Unable to find boot able device , press any key to shutdown

Hello ,
I have a Nokia Lumia 822 with me here , and since 2 days i am trying to fix it .
ERROR ( Unable to find a bootable device : press any key to shutdown )
I have already tried WDRT , WP Internals , doesn't work ( WDRT -Unkown Error , WP Internals gives security Header error ).
With Thor2 , can't flash FFU file . ( I got the FFU from WDRT downloaded RM-845 package in C:/ProgramData)
It's give me an Error RDC file not found. I tried flashing partitions separately but Nothing works until i have this RDC file.
Now where do i get it ? I have dumped FFU via Thor2 , and i do have PLAT , GPT , MAIN OS , MMOS , UEFI , TZ . I dont see any RDC named file here.
Kindly help me any one here.
P.S , I have Following list of files.
WINSECAPP
UEFI
SBL1
SBL2
SBL3
RPM
PLAT
MAIN OS
MMOS
GPT
GPT0
GPT1
EFIESP
DATA
just missing the RDC file and HEX i guess.

I don't know anything about this, but this seems relevant. https://forum.xda-developers.com/chef-central/windows-phone-7/replace-rdc-t3277506/page1
Sent from my Moto G (5S) Plus using Tapatalk

RoshanX said:
Hello ,
Kindly help me any one here.
Click to expand...
Click to collapse
Try to install EFIESP.bin partition from another phone, using WPinternals.
I unbricked lumia 530 flashing the EFIESP.bin from custom ROM of lumia 830.
Unfortunately, after, the phone cant upgrade to windows mobile 10 or hard reset. Sad face appear. Is stuck on wp 8.1.

augustinionut said:
Try to install EFIESP.bin partition from another phone, using WPinternals.
I unbricked lumia 530 flashing the EFIESP.bin from custom ROM of lumia 830.
Unfortunately, after, the phone cant upgrade to windows mobile 10 or hard reset. Sad face appear. Is stuck on wp 8.1.
Click to expand...
Click to collapse
Thank you for your participation , I tried it it , and also tried flashing UEFI paritition , but it gives me an error(see below)
[21:44:40.362] D_MSG : Initiating flash of partition image operations
[21:44:40.362] D_MSG : WinUSB in use.
[21:44:40.380] D_MSG : Using programming of partition image method
[21:44:40.380] D_MSG : isDeviceInNcsdMode
[21:44:40.381] D_MSG : isDeviceInNcsdMode is false
[21:44:40.381] D_MSG : Detecting UEFI responder
[21:44:40.382] D_MSG : HELLO success
[21:44:40.474] D_MSG : Lumia Flash detected
[21:44:40.474] D_MSG : Protocol version 1.18 Implementation version 2.2
[21:44:40.475] D_MSG : Disable timeouts
[21:44:40.476] D_MSG : Get flashing parameters
[21:44:40.567] D_MSG : Lumia Flash detected
[21:44:40.568] D_MSG : Protocol version 1.18 Implementation version 2.2
[21:44:40.568] D_MSG : Size of one transfer is 2363392
[21:44:40.568] D_MSG : Size of buffer is 2359296
[21:44:40.568] D_MSG : Number of eMMC sectors: 30535680
[21:44:40.568] D_MSG : Platform ID of device: Nokia.MSM8960.P5219.3.2.1
[21:44:40.568] D_MSG : Async protocol version: 01
[21:44:40.569] D_MSG : Security info:
[21:44:40.569] D_MSG : Platform secure boot enabled
[21:44:40.569] D_MSG : Secure FFU enabled
[21:44:40.569] D_MSG : JTAG eFuse blown
[21:44:40.569] D_MSG : RDC not found
[21:44:40.569] D_MSG : Authentication not done
[21:44:40.569] D_MSG : UEFI secure boot enabled
[21:44:40.570] D_MSG : SHK enabled
[21:44:40.570] D_MSG : Device supports FFU protocols: 0031
[21:44:40.571] D_ERR : getGpt failed. Error code 12 h
[21:44:40.572] D_ERR : Cannot flash partition image. Write the RDC into the device or use open/RnD HW & SW
[21:44:40.584] D_MSG : Operation took about 0.00 seconds.
[21:44:40.585] D_ERR : THOR2 1.8.2.18 exited with error code 84214 (0x148F6)

I said WPinternals. Capisci?
Anyway, be carefull to not accidentaly click OK when windows will ask to format partition, if you put your phone in mass storage mode. I bricked lumia 640xl that way.

augustinionut said:
I said WPinternals. Capisci?
Anyway, be carefull to not accidentaly click OK when windows will ask to format partition, if you put your phone in mass storage mode. I bricked lumia 640xl that way.
Click to expand...
Click to collapse
Didn't work either. i double checked.
What i need over here i guess is either the RDC , or either the HEX file.
I have seen people generating msimage.mbn via GPT dump
But how do i get the hex file ?! or the RDC ?

WPinternals. Is this? https://forum.xda-developers.com/windows-10-mobile/windows-phone-internals-2-2-t3713157