yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note I717] visa0kr:
Please help me (_ _!)

Hello darkspr1te and every1

My E160L 16Gb using ICS stock rom HOME_E160L.UH24.1821_CL966093_REV02_user_low_ship.tar.md5. I also rooted it by using Tegrak Kenel .

The app com.android.phone kept force closing, i searched on Google and some1 said that use "Rom manager" app to Fix Permission

After Fix permission done, i reboot my phone and found out the Menu+Back buttons were not working anymore

So i tried to reflash rom via Odin, but those still not work.And then i tried to re-partition+PDA. But i couldn't find the PIT file for e160l , then i used PIT file for N700. Odin said Success 1, fail 0

But after that, i found out it was no longer able to Start,couldn't enter Recovery mode, Download Mode (3 buttons).There was no such the signal of life @@.

All i saw in Devices manager was "Qualcomm HS-USB Diagnostics 9025". I installed driver for it too.

I did follow ur Instructions,Installed Python 2.7.3 on C:\Python27.

But failed in next step - "Windows Based BACKUP of partitions and bootloaders".

When i ran cmd (also tried running as administrator), and started the Backup.bat, it said

F:\Brixfix-2-1\Brixfix-2-1>backup.bat

"Please install Python2.7 before running this tool

"Root/Rooted device required"

"Pulling partition Table, creating partition0.bin"

Traceback (most recent call last):

File "..\getpartbin.py", line 53, in <module>

mbr()

File "..\getpartbin.py", line 9, in mbr

f = open("partition0.bin", 'rb')

IOError: [Errno 2] No such file or directory: 'partition0.bin'

"Pulling Bootloaders"

'adb' is not recognized as an internal or external command,

operable program or batch file.

'adb' is not recognized as an internal or external command,

operable program or batch file.

'adb' is not recognized as an internal or external command,

operable program or batch file.

...........

...........

I'm so confusing now. Any suggestion ? Please help me

P/s I have TeamViewer , u can check my work via TeamViewer if u wanna then.

그리고....님은 한국 사람이세요?

ㅠ ㅠ
[AT&T Samsung Galaxy Note I717] RussianBear:
Since your device is bricked, you can't back it up. You need a healthy back up from a working phone.
[AT&T Samsung Galaxy Note I717] darkspr1te:
Just run brixfix.
[AT&T Samsung Galaxy Note I717] funkym0nk3y:
darkspr1te, is it possible to repair LG via this method ? I have an optimus g which will be detected as QHUSB_DLOAD if i break any of the following partitions

SBL1, SBL2, SBL3, RPM, TZ

I have access to jtag and can provide any info you are looking for.
[AT&T Samsung Galaxy Note I717] paranoxxx:
here is results when i run $ dmesg :
[AT&T Samsung Galaxy Note I717] darkspr1te:
Please edit your post, either with [ code] or pastbin
[AT&T Samsung Galaxy Note I717] paranoxxx:
http://pastebin.com/wxs4MYmm
[AT&T Samsung Galaxy Note I717] aehlayel:
Hi Guys,

I'm facing the f006 05c6 issue on my Lenovo K910 phone. It runs a 8974 Qualcomm chipset.

I was wondering what i'd need to modify to be able to restore my phone using the debricking tool..

I'd appreciate any help on this.

Thanks!
[AT&T Samsung Galaxy Note I717] haim3307:
i have no adb nor fastboot and no recovery also! all i got to is to a lot of drives opend by QPST!

all of the guides tell me to get to download mode then move the frimware then head to install but i dont have recovery! im on 4.2.2 so i cant get to fastboot!

is there another way getting to fastboot or to flash recovery from those drives i got from qpst?

thanks anyway!
[AT&T Samsung Galaxy Note I717] darkspr1te:
What device? You gotta give more info than that.
[AT&T Samsung Galaxy Note I717] haim3307:
NUBIA Z5S MSM8974

i installed wrong recovery how can i get the old brick recovery back from the state?
[AT&T Samsung Galaxy Note I717] darkspr1te:
Research first, each device has different partition, find that,then we need the file to boot the device so to speak, aka the hex file. Read back through the thread , all required info is there.
[AT&T Samsung Galaxy Note I717] darkspr1te:
I will do a write up this weekend on what needs to modded for other devices.
[AT&T Samsung Galaxy Note I717] afaneh92:
Thanks I will upload bootloader files and modified files to github to compare between devices.
[AT&T Samsung Galaxy Note I717] ONYXis:
Hi, darksprite.

I have an Amazon Fire HDX (threads about our "bricks" is there http://xdaforums.com/showthread.php?t=2795602&page=4)

We can put our devices in 9008 qdloader (but haven’t file rawproxram0.xml and patch.xml for qpst)

I tried your tool (part of it) to switch in 9006 but got error

onyxis@onyxis-P35-DS3:~$ perl qdload.pl -pfile MPRG8974.bin -lfile 8974_msimage.mbn -lreset
Requesting SoftwareVersion...
Failed to get software version

May be I can modify something in this perl script to recognize our device? Thank you.
[AT&T Samsung Galaxy Note I717] afaneh92:
[MENTION=4864296]darkspr1te[/MENTION] I have uploaded all my changes to github here

any suggestion for my previous post.
[AT&T Samsung Galaxy Note I717] darkspr1te:
Welldone, you have done all.the mods i would suggest. Has it worked is the next question.
[AT&T Samsung Galaxy Note I717] darkspr1te:
Just a thought, are the sectors for writing sbl1/2/3 correct for the device, thats one area i knew needed automatic and updating,
[AT&T Samsung Galaxy Note I717] afaneh92:
I think the start location of partions is correct but that is not my problem.

the process stop at

Executing file...
Failed to get response.
execute failed

If HEX/MBN uploaded correctly, please allow for short delay and re-run brixfix to continue the debricking session, a screen showing device options may appear, close this new screen
mohammad@ubuntu:~/brix$

device still on Bus 001 Device 027: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

not in sd mode I think it 05c6:9025 and if I change it manually from script nothing write to device.

maybe these lines not for my device.

DEVICEID=/dev/disk/by-id/usb-Qualcomm_MMC_Storage-0\:0

DEVICE=`ls -lah /dev/disk/by-id/ | grep usb\-Qualcomm_MMC | head -n 1 | awk '{ print $11 }' | sed 's/\..\/..//'`
[AT&T Samsung Galaxy Note I717] darkspr1te:
Have you tried running the qdload.pl file manually ?

have you tried other hex files?

can you give me the output of dmesg when the phone is connect (last few lines will do, no whole output) and then again after running qdload.pl

darkspr1te
[AT&T Samsung Galaxy Note I717] afaneh92:
yes.

yes.

[ 2743.850112] qcserial 1-1.3:1.0: device disconnected
[ 2805.475950] usb 1-1.3: new high-speed USB device number 33 using ehci-pci
[ 2805.568907] usb 1-1.3: New USB device found, idVendor=05c6, idProduct=9008
[ 2805.568913] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2805.568916] usb 1-1.3: Product: QHSUSB_DLOAD
[ 2805.568918] usb 1-1.3: Manufacturer: Qualcomm CDMA Technologies MSM
[ 2805.569281] qcserial 1-1.3:1.0: Qualcomm USB modem converter detected
[ 2805.569391] usb 1-1.3: Qualcomm USB modem converter now attached to ttyUSB0

disconnect then reconnect and with sudo perl qdload.pl -pfile MPRG8960.hex -lfile 8960_msimage.mbn -lreset

[ 2833.941640] qcserial 1-1.3:1.0: device disconnected
[ 2844.635265] usb 1-1.3: new high-speed USB device number 34 using ehci-pci
[ 2844.727875] usb 1-1.3: New USB device found, idVendor=05c6, idProduct=9008
[ 2844.727880] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2844.727883] usb 1-1.3: Product: QHSUSB_DLOAD
[ 2844.727886] usb 1-1.3: Manufacturer: Qualcomm CDMA Technologies MSM
[ 2844.728290] qcserial 1-1.3:1.0: Qualcomm USB modem converter detected
[ 2844.728406] usb 1-1.3: Qualcomm USB modem converter now attached to ttyUSB0
[ 2848.274194] usb 1-1.3: USB disconnect, device number 34
[ 2848.274373] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[ 2848.274389] qcserial 1-1.3:1.0: device disconnected
[ 2848.474394] usb 1-1.3: new high-speed USB device number 35 using ehci-pci
[ 2848.567501] usb 1-1.3: New USB device found, idVendor=05c6, idProduct=9008
[ 2848.567506] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2848.567509] usb 1-1.3: Product: QHSUSB_DLOAD
[ 2848.567512] usb 1-1.3: Manufacturer: Qualcomm CDMA Technologies MSM
[ 2848.567925] qcserial 1-1.3:1.0: Qualcomm USB modem converter detected
[ 2848.568048] usb 1-1.3: Qualcomm USB modem converter now attached to ttyUSB0
[AT&T Samsung Galaxy Note I717] darkspr1te:
From the looks of it the device is not accepting the hex file, it's a possibility your device needs a signed hex and mbn file.
[AT&T Samsung Galaxy Note I717] KalBha:
Help me..Still trying to make my mobile up..

Hi,

I followed the instructions as per the previous post but still waiting to see my mobile up. Kindly help.
[AT&T Samsung Galaxy Note I717] darkspr1te:
Remind me as to the current status of the device, sorry but I support dozens of threads sometimes hard to keep up.
[AT&T Samsung Galaxy Note I717] afaneh92:
thats what I think, any way how to get it signed and how to get the one from a working device?
[AT&T Samsung Galaxy Note I717] KalBha:
The Device Story

Hi Darksprite,

First, I flashed GT-N7000 XXLT4 onto SHV-E160L (unknowingly). The mobile got bricked.

Then after going through your thread, I was able to restore my device to working condition.

Later, after few days of working of the device, under the settings menu, I selected factory restore. The device then turned off, then the Android logo appeared with animation of installation. The device then booted and stuck up at the boot screen. The ROM in which i did the factory reset is KIES_HOME_E160LKLJMC1_1034927_REV02_user_low_ship. tar.md5 and twrp recovery is installed. Later on i can only enter the download mode and nothing else.

Later i followed your suggestions in the next post to modify the bin files. Also i downloaded the 900lang rom. But whatever i try to flash on to the device, it shows pass in ODIN but it shows device installation failed as in the attached file.

Kindly help. This would be of great relief for me.

Please read the attachment from my previous post on page 37. I am unable to upload it again here.
[AT&T Samsung Galaxy Note I717] Syed Muneeb:
SGH-i747m Hard Bricked :(
[AT&T Samsung Galaxy Note I717] darkspr1te:
Hi, Ok i am up to speed on where you are. Do you have a backup of your efs (some of that should have been backed up by running my tools as per the OP) ,

These are the possible solutions.

1. Use the resistor trick i documented PCB pictures & resistor location to force the device into qdloader then run brickfix to restore any backups you have.

Videos of dis-assembly-resistor trick

2. create a .tar to brick sbl1 by flashing it from odin and use method one.

3. try via linux pc to see what is accessible as windows sometimes does not have the right drivers (example MTP) , my cherry rom has adb enabled from the start, as does my recoveries, flashing them may allow adb, i often bricked to the same point and still had adb

but a i had a entire emmc backup it was no issue to format the bootloaders to brick it then using method 1 I would refresh the entire drive.

Beyond that I am out of suggestions that I am willing to mention.

can you also try using the pit file i posted when flashing via odin but dont click repartition unless you have a backup of the EFS

darkspr1te
[AT&T Samsung Galaxy Note I717] AA27:
I have a LG 840 (Lucid) that I bricked trying to use a different kernel (I had already root and flashed CM 10 and it was working great). I tried your method but this is the message I get:

-e Brick Fix v2-0

______________

-e By Darkspr1te, See README for thanks & References

-e

-e Checking For Qualcomm Device

-e Device Found !!!

-e \e[00;31mError:\e[00m device found in QDLOAD Mode, switching to QDLOAD

see qdload.pl By JC Sullins , http://github.com/jcsullins/qdloader

Expected VID/PID of 05c6:9025, Instead I get :-

-e \e[00;33mBus 001 Device 021: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)\e[00m

-e Do you wish to Upload HEX & msimage.mbn now? \e[00;31mWarning Dangerous\e[00m

brixfix.sh: 33: read: Illegal option -n

brixfix.sh: 34: [: n: unexpected operator

Operation cancelled at user request

jose@jose-GT5660E:~/Downloads/Brixfix-2-1$
[AT&T Samsung Galaxy Note I717] darkspr1te:
I think its your bash/sh program different from the one the script was designed for. If you google changing your bash/command line interpreter you should find plenty of results. It was built and tested on ubuntu 12.04

darkspr1te
[AT&T Samsung Galaxy Note I717] AA27:
Thanks for the quick reply, appreciate it! :D

I am on Ubuntu 14.04 LTS. I am going to try your recommendation and let's see if it works.

I had a 12.04 CD somewhere at home but I can't find it so I am downloading it again to run in Live version.
[AT&T Samsung Galaxy Note I717] AA27:
Tried with 12.04, I even downgraded and installed it.

Same results as last time.

:(
[AT&T Samsung Galaxy Note I717] AA27:
Qualcomm developers site

https://developer.qualcomm.com/download

I registered there and there is some good info. It might be helpful for those with this processor. :good:
[AT&T Samsung Galaxy Note I717] cesarMarq:
I have the same problem on my Optimus F3. (http://xdaforums.com/android/help/optimus-f3-bricked-qualcomm-hs-usb-t2873119)

that Qualcomm Tool Pack V2-1 can solve?
[AT&T Samsung Galaxy Note I717] maxrfon:
The thing why it does not work on other 8960 is that every manufacturer has own keys to sign firmware images for each model (bootloader in this case).

That's why the solution won't work on other phone models.
[AT&T Samsung Galaxy Note I717] alraggad:
lg g2 ls980 sprint

hello

my phone is lg g2 ls980 sprint

in ubuntu show my phone is

root@ubuntu:~# sudo lsusb

Bus 001 Device 003: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

How can I fix this using your tool ?
[AT&T Samsung Galaxy Note I717] maxrfon:
No how. Sorry.
[AT&T Samsung Galaxy Note I717] androidlabs:
E160L pit file

please someone share 32 GB pit file for E160L i need it very badely. i will be very greatfull.
[AT&T Samsung Galaxy Note I717] darkspr1te:
It's the same as S/K models, posted here already, I think awesomefireduck posted it.
[AT&T Samsung Galaxy Note I717] androidlabs:
HELLO DARKSPRITE! thanks for your kind reply i have read every single post here in this thread but i couldent find the 32gb pit for e160x devices it would be gereat if your share it with me. i am facing very strange problem i think there is something wrong with my partition table. when i boot my device it goes till gaaps activation screen and from there touch only works once after that device goes to blank screen and detects as qhsusb. it means i can access odin mode recovery mode etc, can you please help me with the solution.?

Br,

Babar Abbasi
[AT&T Samsung Galaxy Note I717] darkspr1te:
It's on the first page, the files for the K model have been posted there for a while, today I've added the L model files. When i have time i will check for broken links and update where I can. So many projects, so little time.

heres a shortcut,

http://xdaforums.com/showthread.php?t=2136738
[AT&T Samsung Galaxy Note I717] n-neo:
hi there

i have a nubia z5s mini , hard bricked with this message in device manager "Qualcomm HS-USB Diagnostics 9008"

the device runs snapdragon 600 , and it was bricked after presumably installing a rom that probably bricked it after pressing the restart in recovery the phone never woke up , no light whatsoever and no vibration but it is recognized in the device manager .

is there any possible way for me to bring it back to life ? PLEASE !!! HELP !

my laptop is on windows 8.1 , do i need another os for that ? what are the tools that i should use if any ?

thank you in advance
[AT&T Samsung Galaxy Note I717] ONYXis:
Hello.

I have an Amazon Kindle Fire HDX - MSM8974, Sahara protocol.

I have original files: NON-HLOS.bin, sbl1, tz, aboot, rpm and sdi. Also I have first 5120 bytes of mmcblk0 and parsed gpt table (partition name, size in KB and blocks, start sectors). Also I think I have proper MPRG8974.hex.

Maybe [MENTION=4864296]darkspr1te[/MENTION] and [MENTION=4372730]E:V:A[/MENTION] have experience in the recovery of similar devices or have docs how to generate a proper msimage.mbn for sahara protocol (QPST version above 399) if it makes any sense of course?
[AT&T Samsung Galaxy Note I717] darkspr1te:
It is hard for us to be able to provide a debrick solution without the device, too many variables for us to cover.

The msimage.mbn file(and sister files like sbl1.mbn) is created by the OS developer so not all devices have it or need it or have leaked it. Developers are only given these sources after signing a NDA and only for the specific device they sign up for so there is no universal msimage.mbn AFAIK but this could be proved with actual testing across a few devices.

Also later devices from my 8660 model have different boot structures now , example my device had sbl1/2/3 but yours has sbl1 and sbi , these changes need to be taken into account when working towards a solution.

The Bottom line is that without a device we cant offer up much help and with the sheer volume of bricked devices/users it's not easy to follow the threads , nor do we have all that time to really spare to educate the owner up to the required level to debrick on their own, hence we tried to create threads to collate this knowledge (msm bootloaders thread, patrtition thread, debrick thread etc).

Maybe take a look at my documentation in debricking a qualcomm thread, once i did my research and posted the information in a clear manner you will see that help from others was invaluable to my research and eventual solution, this also encouraged other dev's working towards similar goals to release information they had and in turn collaborate to provide final solution, as a example without J C sullins help we would not have a stable hex uploader with the additional features, that was not my code, I found that program and tweaked it enough to work with my device, JC ran with it and turned it into what you see now and what's in my current code base.

We do try and offer advise where we can and follow the new threads where can, but as you have seen with xda it's very hard to filter the noobs demanding and I mean some DEMAND we help them, so yeah it's much easier if we have a specific thread thats kept on topic,

regards

darkspr1te
[AT&T Samsung Galaxy Note I717] alraggad:
darkspr1te please how to i find this files MPRG8974.hex and 8974_msimage.mbn for lg g2
[AT&T Samsung Galaxy Note I717] kryptonite:
Possible to recover LG G2 From Qualcomm HS-USB Qdloader 9008

[MENTION=4864296]darkspr1te[/MENTION] , thanks for suggesting that I use this topic to start discussing on how to fix the LG G2 using this method.

[MENTION=3279781]bender_007[/MENTION] FYI as I may need some help here.

I am trying to fix my LG G2 - LS980 using this method. Currently my phone is completely bricked and when I connect to PC it enumerates as QDLoader 9008 mode.

I already have the Partition type as GPT.

PrimaryGPT.bin is the partition table , could anyone else confirm ? This is part of the Firmware package for the phone.

Since its already named PrimaryGPT.bin I am assuming its GPT partition and it contains the partition table info.

Out of the 4 requirements from the first post, we have 3 & 4 (includes all partitions backed up , not just bootloader , aboot etc), we need to get 1 and 2 done. 2 is going to be challenging

as we need correct HEX for 8974 CPU.

Also would a HEX file of one manufacturer work on another ? EG 8974.hex from XIAOMI work on LG devices?

From post #30 of the topic, if security (root cert checking) is enabled by the OEM (htc, samsung) it appears that we will need a signed hex.So does LG require this ? If so how do we sign this ?

1. Alteration of the scripts to use the files specific to your device

2. Correct HEX and SD-CARD loader also known as sdcard mbn

3. Correct partition information (knowing if it's MBR/GPT or hybrid)

4. Correct bootloaders for your device (SBL1/2/3/ABOOT)
[AT&T Samsung Galaxy Note I717] kryptonite:
As a note I realized that while using QPST , it will only detect your phone (if its in QDLoader 9008 mode) if you have QPST already running and then plug in the phone. Only then will it show the phone is detected in sahara download protocol mode.

See QPST.PNG attached.

If you already had the phone connected and then you start up QPST , it will not detect the phone .
[AT&T Samsung Galaxy Note I717] kryptonite:
I was able to create the required XML files and used the hex files from what was available on the net. But I am stuck as below.

** physical partition 0 **

program file modem.img, file offset 0, start sector 16384, sectors 131072

program file sbl1.img, file offset 0, start sector 147456, sectors 1024

program file dbi.img, file offset 0, start sector 148480, sectors 64

program file DDR.img, file offset 0, start sector 163840, sectors 64

program file aboot.img, file offset 0, start sector 180224, sectors 2048

program file rpm.img, file offset 0, start sector 182272, sectors 1000

Device mode = Sahara on port 10006

server event monitor enabled

path for selected COM port = "_HCD1!hub:0!dev:1"

Timeout waiting for device

device wait found 0 0
[AT&T Samsung Galaxy Note I717] ONYXis:
I'm pretty sure that msimage_xxx.mbn not suitable.
[AT&T Samsung Galaxy Note I717] kryptonite:
[MENTION=5594063]ONYXis[/MENTION] , do you think its due to the msimage_xxx.mbn or the MPRG8974.hex file ?
[AT&T Samsung Galaxy Note I717] ONYXis:
Yes. XML's need to flash firmwares after device turns on into diagmode (Qualcomm MMC Storage).

To turn device into storage-mode is enough 2 files - proper MPRG8974.mbn (hex) and msimage8974.mbn. And I think that MPRG8974.mbn sized ~59 kb is suitable for most devices, but msimage is original for each device.

But this is only my assumptions. About MPRG8974.hex (~313 kb)...I tried download through script this file (converted to bin) and device rejects it at start, two files MPRG8974.mbn (59kb an 38 kb) is acceptable.
[AT&T Samsung Galaxy Note I717] kryptonite:
[MENTION=5594063]ONYXis[/MENTION] thanks , could you point me to how you are determining the device accepts or rejects particular hex / mbn files.

I am trying to create msimage8974.mbn but getting some errors using emmcdownload too, any other suggestions ?

Below is the error.
[AT&T Samsung Galaxy Note I717] ONYXis:
You need use syntax partition-boot.xml like this:

<?xml version="1.0" ?>
<data>
<!--NOTE: HDX7_16GB partition_boot.xml-->
<program file_sector_offset="0" filename="NON-HLOS.bin" label="modem" num_partition_sectors="131072" physical_partition_number="0" size_in_KB="65536.0" start_sector="131072" />
<program file_sector_offset="0" filename="sbl1.mbn" label="sbl1" num_partition_sectors="1024" physical_partition_number="0" size_in_KB="512.0" start_sector="262144" />
<program file_sector_offset="0" filename="rpm.mbn" label="rpm" num_partition_sectors="1000" physical_partition_number="0" size_in_KB="500.0" start_sector="528388" />
<program file_sector_offset="0" filename="sdi.mbn" label="dbi" num_partition_sectors="64" physical_partition_number="0" size_in_KB="32.0" start_sector="263168" />
<program file_sector_offset="0" filename="emmc_appsboot.mbn" label="aboot" num_partition_sectors="4096" physical_partition_number="0" size_in_KB="2048.0" start_sector="524292" />
<program file_sector_offset="0" filename="tz.mbn" label="tz" num_partition_sectors="1000" physical_partition_number="0" size_in_KB="500.0" start_sector="786432" />
<program file_sector_offset="0" filename="gpt_main0.bin" label="PrimaryGPT" num_partition_sectors="34" physical_partition_number="0" size_in_KB="17.0" start_sector="0" />
</data>

But if I understand clear this method not for msm8974, in our case we need use

python singleimage.py -x singleimage_partition_8974.xml

from boot_images/core/storage/tools/ptool/

I do not find this tool.

it is custom python scrypt, was written guy exactly for my case.