SHV-E160L Debricking Tool / Qualcomm Tool Pack V2-1

RussianBear · Feb 19, 2013

funkym0nk3y said:
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.

Lg has lgnpst (qpst equivalent). See if it detects your phone. If so, you might be able to flash it via that tool.

arie001 · Feb 20, 2013

SGH-I727 (msm8060 chipset) SII Skyrocket

I have tried running the v2 tool in SUSE 12.2 live and the script runs ok but when this is where it hits a brick wall. Have you come across this error before?
--feedback on linux compatibilities--
I get script errors when I try to run it in Ubuntu 12.10 or 12.04 live versions, the output is corrupted with % symbols and such as if it is using a different character set or something. It exits at the "Do you wish to Upload HEX & msimage.mbn now? Warning Dangerous" prompt.
--end feedback on linux compatibilities--

Code:

linux@linux:~/Brixfix-2-1> sudo sh brixfix.sh

Brick Fix v2-0
______________
By Darkspr1te, See README for thanks & References

Checking For Qualcomm Device
Device Found !!!
Error: device found in QDLOAD Mode, switching to QDLOAD 
see qdload.pl By JC Sullins, xxxxxxxxxxxx

Expected VID/PID of 05c6:9025, Instead I get :-
Bus 002 Device 006: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

Do you wish to Upload HEX & msimage.mbn now? Warning Dangerous
y
Executing qdload 
Requesting SoftwareVersion...
Version: PBL_DloadVER1.0
Requesting Params...
Params: 06 01 01 00 90 00 00
Uploading file 'MPRG8660.bin' to QDLOAD...
Writing 1024 bytes to 0x2a000000; 164996 bytes left.
Writing 1024 bytes to 0x2a000400; 163972 bytes left.
Writing 1024 bytes to 0x2a000800; 162948 bytes left.
Writing 1024 bytes to 0x2a000c00; 161924 bytes left.
........
Writing 1024 bytes to 0x2a027c00; 2180 bytes left.
Writing 1024 bytes to 0x2a028000; 1156 bytes left.
Writing 1024 bytes to 0x2a028400; 132 bytes left.
Writing 132 bytes to 0x2a028800; 0 bytes left.
Executing file...
Sending MAGIC...
MSG: Qfprom Fuse List: Blowing FAILED    
MSG: Failed Fuse addr:  
MSG: 0x00000000 
MSG:    Error Status:  
MSG: 0x00000000 
Sending secureMode...
Sending openMulti ...
Uploading file '8660_msimage.mbn'...
Writing 1024 bytes to 0x00000000; 1620548 bytes left.
Invalid Response: 0e 57 72 69 74 65 20 75 6e 73 75 63 63 65 73 73 66 75 6c 0a

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
linux@linux:~/Brixfix-2-1> 

linux@linux:~/Brixfix-2-1> sudo sh brixfix.sh

Brick Fix v2-0
______________
By Darkspr1te, See README for thanks & References

Checking For Qualcomm Device
Device Found !!!
Error: device found in QDLOAD Mode, switching to QDLOAD 
see qdload.pl By JC Sullins ,
Expected VID/PID of 05c6:9025, Instead I get :-
Bus 002 Device 007: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

Do you wish to Upload HEX & msimage.mbn now? Warning Dangerous
y
Executing qdload 
Requesting SoftwareVersion...
Invalid Response: 0e 49 6e 76 61 6c 69 64 20 43 6f 6d 6d 61 6e 64 0a
Failed to get software version

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
linux@linux:~/Brixfix-2-1>

Is this error being caused by the emmc requiring a code? If so what would I ask in the SGH-I727 forum to get the file needed?

darkspr1te · Feb 20, 2013

I will decode the error later but I think it's because you have a different CPU.
My shv-e160l has a msm8660, so brick fix is built for that,
For i727 its been listed with msm8260 & apq8060, can you confirm which CPU you have.
As mentioned, brixfix was originally build for the shv, I need copies of the partition table /boot loaders to expand it's support.
I am currently away from my stash of code (I only took ROMs to rebuild this trip )
But will be back in from of my code by Monday next week, then I can lookup what the error could be, unless SLS decodes it first.
But at a guess on the error, wrong CPU for the hex file uploaded.

sent from the Darkspr1te's lair

arie001 · Feb 20, 2013

I just read that the APQ8060 is only for devices that don't require cellular service but is otherwise the same as MSM8260. So mine must be the MSM8260. The MSM8660 offers more frequencies I believe and is said to be best suited to international phone use but is otherwise same as the MSM8260. Though I suppose at the low level they could all have subtle differences causing incompatibilities.

Sent from my Nexus 7 using xda app-developers app

-EDIT-
Pulled the phone apart and it is APQ8060.

cbwfnhxk · Feb 20, 2013

Thank you!

Thank you!：好：：好：

darkspr1te · Feb 20, 2013

cbwfnhxk said:
Thank you!：好：：好：

Che che, welcome

sent from the Darkspr1te's lair

visa0kr · Feb 20, 2013

Big thanks to our Hero *darkspr1te*

Thank u so much darkspr1te, ur hero ^^
Also read ur posts about debricking E160L, great job.
I tried running brickfix under ubuntu 12.2 live usb, there were some problems, it said cant open device, or there is no such directory while writing 8660_msimage.mbn and 8660_MPRG.hex
And the same problem while writing *.mbn files
Then i manual edited paths in brixfix.sh
(example : dd if=$MODEL'/home/ubuntu/Desktop/Brixfix-2-1/SHV-E160L-16GB/partition0.bin' of=/dev/sdb seek=0 count=1 bs=512 )
After writing all needed files to Sdb , remove/replace battery and Power up phone
I was so happy when seeing SAMSUNG logo xD
Thank u again ^^!)

darkspr1te · Feb 20, 2013

visa0kr said:
Thank u so much darkspr1te, ur hero ^^
Also read ur posts about debricking E160L, great job.
I tried running brickfix under ubuntu 12.2 live usb, there were some problems, it said cant open device, or there is no such directory while writing 8660_msimage.mbn and 8660_MPRG.hex
And the same problem while writing *.mbn files
Then i manual edited paths in brixfix.sh
(example : dd if=$MODEL'/home/ubuntu/Desktop/Brixfix-2-1/SHV-E160L-16GB/partition0.bin' of=/dev/sdb seek=0 count=1 bs=512 )
After writing all needed files to Sdb , remove/replace battery and Power up phone
I was so happy when seeing SAMSUNG logo xD
Thank u again ^^!)

Which device did you unbrick ? Also the code shown above if from a very old version of the programs, the new one auto detect the drive it's connected too.
Has the device now fully booted ? Is everything running right?

sent from the Darkspr1te's lair

RussianBear · Feb 20, 2013

Dark, have you considered rolling this out to other msm8660 devices?

darkspr1te · Feb 20, 2013

RussianBear said:
Dark, have you considered rolling this out to other msm8660 devices?

Yes I have, I've been changing all the fixed var's inside the code to allow a minor or major amount of tampering with the setup.
Current task is improve the backup system to auto detect the information, currently it does my device perfect, even if I tamper with the locations of the boot loaders , it still follows them around, next step is add code to pull the header from the .mbn file and know 'exactly' which loader it is, from there create a auto table of filename/partition/real partition contents based on header/partition type size etc. That table, inclusive of a backup is enough to create auto debricks, that is we only need to see it once and its supported.
That once still requires a user to upload a file though, something users don't seem always willing to do.

sent from the Darkspr1te's lair

RussianBear · Feb 20, 2013

darkspr1te said:
Yes I have, I've been changing all the fixed var's inside the code to allow a minor or major amount of tampering with the setup.
Current task is improve the backup system to auto detect the information, currently it does my device perfect, even if I tamper with the locations of the boot loaders , it still follows them around, next step is add code to pull the header from the .mbn file and know 'exactly' which loader it is, from there create a auto table of filename/partition/real partition contents based on header/partition type size etc. That table, inclusive of a backup is enough to create auto debricks, that is we only need to see it once and its supported.
That once still requires a user to upload a file though, something users don't seem always willing to do.

sent from the Darkspr1te's lair

I've noticed that.... that's to be expected though. Major props for your work!

SouL Shadow · Feb 20, 2013

darkspr1te said:
I will decode the error later but I think it's because you have a different CPU.
My shv-e160l has a msm8660, so brick fix is built for that,
For i727 its been listed with msm8260 & apq8060, can you confirm which CPU you have.
As mentioned, brixfix was originally build for the shv, I need copies of the partition table /boot loaders to expand it's support.
I am currently away from my stash of code (I only took ROMs to rebuild this trip )
But will be back in from of my code by Monday next week, then I can lookup what the error could be, unless SLS decodes it first.
But at a guess on the error, wrong CPU for the hex file uploaded.

sent from the Darkspr1te's lair

I'll take a look at it if I get some free time. I've been super busy lately and have barely touched my computer in a couple weeks now.

A quick glance suggests there's multiple small errors, but I would need to dig in to it further.

EDIT:
The command 0e is the Log command in streaming download.

The first log message says:
"Write unsuccessful"

The second log message says:
"Invalid command"

The first message could be due to using the wrong hex file for that chipset (?)

The second message is because the script tries to communicate with download mode, but the phone is still in streaming download.

The third error I see is the phone trying to blow a qfuse (at an invalid address). It's unclear from the output as to why that happened.

-SLS-

visa0kr · Feb 21, 2013

darkspr1te said:
Which device did you unbrick ? Also the code shown above if from a very old version of the programs, the new one auto detect the drive it's connected too.
Has the device now fully booted ? Is everything running right?

sent from the Darkspr1te's lair

Mine is Galaxy Note E160L 16GB
It's working prolly now xD
I also fixed Menu and Back button not working by flashing E160L_Teamleader_v1.0 rom (GB rom)
Connect Internet via 3G/Wifi, Dial *#2663# then chose Touch key FW update.

Im gonna flash "Dakrpsr1te's Cherry Rom" later today
Great job sir. Thanks again ^^

arie001 · Feb 21, 2013

SGH-I727 pit file

lart2150 kindly uploaded a pit file in this thread http://xdaforums.com/showthread.php?t=1485519&page=12 which should be from a SGH-I727 Skyrocket. Will this help?

The same thread also has a pointer to this one http://xdaforums.com/showthread.php?t=1629508 with a file named mmcblk0p11.bin also advertised as a pit file dump kindly uploaded by cshmitt.

arie001 · Feb 23, 2013

Other considerations if having USB problems

SouL Shadow said:
I'll take a deeper look at it later.

You should note that qualcomm chipsets do not have support for USB 3.0. While the linux USB 3.0 driver is backwards compatible with the older standards, it is still buggy so it's best to only use USB 2 and lower ports.

Also, you should be using a 32bit Linux distro with a kernel from 2012 or later.

-SLS-

Also avoid USB ports featuring power-share. My laptop has one of it's USB ports designated to charge devices even when the laptop is powered off, it has a small lightning bolt beside the USB logo. I've noticed this port causes problems with Windows device detection and flags it as an unknown device (even with the proper drivers loaded, other ports work fine).

Also for anyone not familiar with USB 3.0, the ports normally have a blue center to them.

jon1234444 · Feb 24, 2013

still lurking, trying to debrick my Evo 3D (8660) here, could never get past the cookie error in qpst. when running the latest script everything seems to go well until sending magic:

Code:

Sending MAGIC...
Response: 03 00 03
Invalid MAGIC response.

any idea what that response means?

arie001 · Feb 24, 2013

Evo 3D unbricking

jon1234444 said:
still lurking, trying to debrick my Evo 3D (8660) here, could never get past the cookie error in qpst. when running the latest script everything seems to go well until sending magic:

Code:

Sending MAGIC... Response: 03 00 03 Invalid MAGIC response.

any idea what that response means?

Have you been to this thread yet?
http://xdaforums.com/showthread.php?p=25501934

--EDIT--
I noticed this result when experimenting a little, when brixfix.sh sees the phone in :9008 mode it calls the "switchmode.sh" script which qdloads two files in order to get the phone into the SD card mode. I tried loading the 8660_msimage.mbn first on a freshly connected SGH-I727 before loading "sudo perl qdload.pl -pfile MPRG8660.bin" command and got this same exact response:

Code:

/Brixfix-2-1> sudo perl qdload.pl -lfile 8660_msimage.mbn
Sending MAGIC...
Response: 03 00 03
Invalid MAGIC response.

So it looks like maybe your MPRG8660.bin file is missing/renamed, or is not uploading correctly before the 8660_msimage.bin file is uploaded.

jon1234444 · Feb 24, 2013

arie001 said:
Have you been to this thread yet?
http://xdaforums.com/showthread.php?p=25501934

yes, tried everything else that's out there

RussianBear · Feb 24, 2013

jon1234444 said:
yes, tried everything else that's out there

Your phone is most likely in a different type of download mode.the one that's not supported by this unbrick method.

darkspr1te · Feb 28, 2013

BarakOsama said:
Please someone share a PIT file of 32GB E160x device..

I now have the files for a model K, thanks to 2ndcarpenter for making this possible.
This means I can now support L / K 32 GB or 16 GB , I need to do some initial testing and will upload a updated brixfix

Darkspr1te

Sent from my A210 using Tapatalk 2

SHV-E160L Debricking Tool / Qualcomm Tool Pack V2-1

Recognized Contributor

Senior Member

Senior Member

Senior Member

New member

Senior Member

New member

Senior Member

Recognized Contributor

Senior Member

Recognized Contributor

Senior Member

New member

Senior Member

Senior Member

Member

Senior Member

Member

Recognized Contributor

Senior Member

Similar threads

Top Liked Posts