[AT&T Samsung Galaxy Note I717] darkspr1te:
brixfix & basefix

These files are for Samsung SHV-E160L only, how ever the theory should work on any device in QDLoader mode, the partition locations and loader files will be device specific

Any one willing to try on other devices please be familiar with your hardware and partitions and alter the script/files to suit your devices,

I only have the SHV-E160L device so it's not been tested on anything else but hopefully this will be expanded on to include other devices

I have no issues with anyone willing to tidy up, port or include in a one click solution the information i've put here, just cred me :) and post your work here

Hi Folks,

Here with V1 public of my brixfix and basefix scripts. They are deisgned to be used via ubuntu linux.

I will give a recap on what's what.

If your device is just totally dead, no screen, no enumeration in linux or windows then the boot chain is corrupt and the device is hanging in one of the stages before or including aboot, if this is your postition the only way to fix is JTAG or shorting the resistor i found to disable booting from EMMC.

If your device is in QDLoad mode then the chain of trust for booting has been broken and the device is failing over to ROM based PBL.

(QDLoad PBL)

This is the prefered state as we now have the ability to fix with software only.

To unbrick the device we first write MPRG8660.HEX into PBL memory and the device re-enumerates as MSM Qualcomm device but using the same PID/VID.

We then write a basic bootloader to the device that turns the EMMC memory into a SD-CARD and reboot the device.

We then write new partition table & primary bootloader chain back to the device, reboot and you're done.

Files

QPST: http://www.filecrop.com/79059791/index.html

brixfixv1.zip http://www.mediafire.com/?2dd6urq6kg8jkok

Instructions:-

For devices in QDLoad mode only (Samsung SHV-E160L / MSM8660-MDM9600 chipset)

You need the brixfix zip file, extract contents onto a wid0ws machine, install QPST and plug device in, make sure battery is in and charged if possible

i've included the qualcomm drives and adb drivers here but the other drivers are installed with kies

run qpstconfig and add a serial port that your device is on (see atached images)

load emmcswdownload and, make sure it's setup the same as attached image(Program Bootloaders tick, Backup NV tick, trusted mode tick, search path = location of extracted brixfix zip file, NO tick on program EMMC).

Then click download, the QPST will transfer the HEX file to ram, then enumerate again,QPST then write 8660_msimage.mmbn and the device will enumerate as a SD-CARD & comport ( Qualcomm 9025)

Here you need to transfer to Linux

extract the bixfix zip file on your linux computer, plug in phone after the above 8660_msimage.mbn has been loaded to emmc. Linux will see it as a drive (ive hard coded my script for SDB, please change if you drive has a different ID under /dev/, eg SDC, SDD )

run brixfix.sh

you should now remove battery and cable, replace battery and the device should boot into ODIN mode or fully boot and should not require baseband fix ( i've fixed the files)

For Baseband fix

Enable ADB mode on the device and plug into linux computer, run basefix.sh program to restore chain of trust (bootloaders signed to this device)

For Tyller

, please download and extract brixfix onto your linux pc, run basefix.sh.

[B]darkspr1te@darkspr1te-dev-pc:~/brixfix/$[/B]./sh basefix.sh
Backing up Bootloaders

if any of the following fail with errors do no reboot your device, correct the error and re-execute

1000+0 records in
1000+0 records out
512000 bytes transferred in 0.050 secs (10240000 bytes/sec)
2853 KB/s (512000 bytes in 0.175s)
3000+0 records in
3000+0 records out
1536000 bytes transferred in 0.113 secs (13592920 bytes/sec)
3486 KB/s (1536000 bytes in 0.430s)
1000+0 records in
1000+0 records out
512000 bytes transferred in 0.036 secs (14222222 bytes/sec)
2918 KB/s (512000 bytes in 0.171s)
4096+0 records in
4096+0 records out
2097152 bytes transferred in 2.690 secs (779610 bytes/sec)
4102 KB/s (2097152 bytes in 0.499s)
5000+0 records in
5000+0 records out
2560000 bytes transferred in 0.078 secs (32820512 bytes/sec)
5537 KB/s (2560000 bytes in 0.451s)
1000+0 records in
1000+0 records out
512000 bytes transferred in 0.020 secs (25600000 bytes/sec)
3139 KB/s (512000 bytes in 0.159s)

Copying bootloaders to device - /sdcard/

5349 KB/s (512000 bytes in 0.093s)
5647 KB/s (1536000 bytes in 0.265s)
3280 KB/s (512000 bytes in 0.152s)
4171 KB/s (2097152 bytes in 0.490s)
4260 KB/s (512000 bytes in 0.117s)

Copying Bootloaders to MMC
Restoring Chain of trust
1000+0 records in
1000+0 records out
512000 bytes transferred in 0.222 secs (2306306 bytes/sec)
3000+0 records in
3000+0 records out
1536000 bytes transferred in 0.625 secs (2457600 bytes/sec)
1000+0 records in
1000+0 records out
512000 bytes transferred in 0.129 secs (3968992 bytes/sec)
4096+0 records in
4096+0 records out
2097152 bytes transferred in 0.510 secs (4112062 bytes/sec)
1000+0 records in
1000+0 records out
512000 bytes transferred in 0.102 secs (5019607 bytes/sec)

Restore complete,
if any error occurs please resolve the error and re-execute this script, dont reboot the phone or you could
end with a bootloop or worse a hang before aboot.mbn (little kernel/download mode loader) is executed and odin mode is activated
the hang will require JTAG or a hardware mod to reactivate QDload mode, you will then need to run brixfix.sh

both files are coded to exit on running, you have to remove the command exit from the script, this is to ensure you have read the instructions first and dont blindly run the program.

just edit the file and remove the first exit command you see, save and run.

I have tested these files many times on my device but there is always a possibility for mistakes so please dont hold me responsible.

Post any feedback here on the forums

for users with GPS issues please see included dial codes text file or next post

Regards

darkspr1te