yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note I717] canika:
SHV0E160S

Good day Sirs,

hi to all. sir. please help, i have a korean note 1 phone and i think i brick it? but i dont know the condition of my unit. my story, my unit is working fine when i find out that i can make up grade (custom rom), i use the odin software without knowing it will brick my unit very stupid of me. i click the PIT button and the the phone go blank (dead). i read almost 2 days here in this threads but maybe only a few things i understand. arround 10%.

please help me to fix my unit

best regard

Canika
[AT&T Samsung Galaxy Note I717] canika:
Samsung galaxy note SHV-E160s 16gb

Good day,

sir my unit is not rooted yet when i brick, still posible to fix this?

do you have a fix file for this model?

can you some how give me a noob instruction? i am so noob about this sorry:(

thanks and regards

canika:)
[AT&T Samsung Galaxy Note I717] darkspr1te:
Hi,

As a noob i recommend you read the forum and posting guides.

Please try and state exactly what you were doing, what the device is doing now, it's model , the firmware you were on, any relevant information that you may have.

for example is it showing up under device manager ? do you have any access ?

darkspr1te
[AT&T Samsung Galaxy Note I717] canika:
hi sir darkspr1te

this is my 3rd day reading you solution but still i have only 20-30% of understanding (still noob sir)

im trying to install custom rom to my unit when i stupidly try the PIT button on Odin3-v1.85. after that the screen go blank, cannot power on!

i think i dammage the partion.

the unit is samsung galaxy note SHV-E160S - 16gb ,JB 4.1.2 from korea (thats all info i got)

right now sir im downloading UBUNTU OS but im not quit sure if this the right one, Ubuntu 12.04 LTS 32bit

i tried some of your solution but i think i did not follow it correctly, im on the brixfix you made. but no luck

if i plug the unit in USB it will go to QDLOAD in widows. i never try in ubuntu! by the way this is the first time i will use linus os.

thats the stupid story of mine

by the way sir do i need to dismantel the unit and make some modifacation on hardware?

thanks and regards

Canika
[AT&T Samsung Galaxy Note I717] darkspr1te:
My brickfix package will work for you ( the linux one should, winX unfinished) but you need to change the bootloaders for S model ones, I sadly dont have copies of the S model bootloaders.

Ubuntu any version will work .

No you wont need to dismantle the device unless you make a mistake, if your do and lock the device between bootloaders (as my device was when i recevied it) then you need the Boot bypass hack which was based off adam outlers works and turned into a real world hack by myself.

the brickfix package contains scripts to backup the bootloaders from a working device (backup.bat -win and getpart.sh -linux)

the bootloader files you require are :-

sbl1.mbn
sbl2.mbn
sbl3.mbn
tz.mbn
aboot.mbn
rpm.mbn

regards

darkspr1te
[AT&T Samsung Galaxy Note I717] canika:
sir merry christmas

maybe after this busy days i will install ubuntu but as i said this will be my first time to use the OS so i dont have any idea.

thanks and regards

canika
[AT&T Samsung Galaxy Note I717] Sergius89:
Hi guys!

I have question to you.

Could you help me unbrick my "Motorola Electrify M XT901", it's "qualcomm HS-USB Dloader 9008" now.

This phone have same CPU as samsung SHV-E160L (as far as i know).

I have stock rom with next files:

sbl1_signed sbl2_signed sbl3_signed

tz_signed

rpm_signed

partition_signed

fsg_signed

aboot_signed

boot_signed

devtree_signed

logo_signed

modem_signed

recovery_signed

system_signed

cdrom_signed

And xml file for motorola flasher. (I need fast boot to flash phone)

Its posible create some img file, bootloader or some else from stock rom and flash it with QPST, BrixFix or some other tools?

I would be very appreciate it for any help!!!
[AT&T Samsung Galaxy Note I717] darkspr1te:
I Had posted a reply to this but it seems it got eaten by the internet,

Can you confirm if the device accepts the hex file and then in turn accepts the .mbn sdcard file (use qpst to confirm this )

darkspr1te
[AT&T Samsung Galaxy Note I717] Sergius89:
I trying download PRG8660.hex and 8660_msimage from BrixFix-2-2 folder via eMMC Software Downloader,

but i have error:

"Image Download Failed. Cookie(if present) not receiced."

Use QPST 2.7.378. Perhaps i use wrong files or tools?
[AT&T Samsung Galaxy Note I717] darkspr1te:
Hi,

as a experiment please rename PRG8660.hex to ePRG8660.hex and try again,

also it's assumed that the cookie error is a result of either a requirement for a signed hex file or the emmc chip is damaged.

if thats the case then there is nothing we can do at the moment.

darkspr1te
[AT&T Samsung Galaxy Note I717] Jay_P11:
Will any of this work for an HP Touchpad 32GB? Unfortunately, JCSullins method of debricking the TP returns the dreaded "Open multi failed" error, I've also heard it be called the cookie error. I've tried everything, is there any known way to fix this? I'd hate to lose a good tablet. I have all the .mbn files (aboot.mbn, rpm.mbn, sbl1.mbn, sbl2.mbn, sbl3.mbn, tz.mbn) not sure how to go about using those but nothing anywhere else works. Will trying this tool on it brick it completely? I need help :(

EDIT: To my understanding this is an APQ8060 or MSM8660/MSM8260, also I've got a few files laying around that had to do with this, would the .hex/.bin ever be named emmcbld.bin? I would also need a pitfile for the Touchpad, and a partition0.bin file. I think I know what I'm doing but there seems to be too much going on here that I don't understand.
[AT&T Samsung Galaxy Note I717] Jay_P11:
So I ran the Brixfix anyway, everything was going smooth until qdload turned up with the very same "Open Multi failed" error. I know it has to be the hex file, but I've been looking on the internet for a good day now trying to find the Touchpad's hex file. And whenever I do actually find it, I'm not sure how I would implement it into Brixfix.

EDIT: Now trying to run it through QPST, and I need a partition table file. I want to re-write it through there and then try running the Brixfix or even JCSullins' tpdebrick. These files are to be found nowhere on the internet, and I don't know how or where to get them elsewhere. All QPST tells me is that it failed to open the partition file.
[AT&T Samsung Galaxy Note I717] Sergius89:
I tried different names of hex file, but no result. The same error.

I think maybe it's not MSM8660, and i can't find full specification of my phone with current model of CPU.

darkspr1te thanks for you help.
[AT&T Samsung Galaxy Note I717] Magusbob:
Would this work for an ATT LG OG e970. My device will not power on at all, but when plugged into USB it shows Qualcomm HS-USB QDLoader 9008 (COM4). Any help would be greatly appreciated.
[AT&T Samsung Galaxy Note I717] darkspr1te:
Hi,

JCSullins, myself and a few others around the XDA worked on this together, each inputting the requirements to bring each device to a flashable point, sadly none of us has overcome the cookie error.

the APQ8060 is a msm8660 without radio included on the SOC. they share the same codebase and sources.

The feeling was towards a EMMC error when this come up, mainly because we know the hex file works on the cpu and its sole job is to flash the MBN file to the emmc, it does provide some other features but we only did minor work in that area due to personal constraints/time.

Yes you are right, there is a lot of info in this thread, its here to provide a spring board for dev's to port to other devices so a working knowledge of files systems/linux/bootloaders/SOC systems, E:V:A post's a great deal on that, also via my original SHV-E160 debrick thread you will see that I document the SHV device and it's setup, how i reversed it all, combine that with adam outlers bootloader work with XOM/boot resistors led to this thread.

The key to this solution is the hex file, if someone could come up with a better version of it that would be great, i didnt know enough at the time to even consider further dev work on the hex, the sources had been found but it was beyond me.
[AT&T Samsung Galaxy Note I717] DennyTek:
Invalid Response: 03 00 02 upload File failed Galaxy Exhibit 4g

Hmmm, I tried brixfix 2-2 on my bricked samsung galaxy exhibit 4g and I get this. "Invalid Response: 03 00 02

uploadFile failed."
[AT&T Samsung Galaxy Note I717] haminhthang:
help me

i have a pantech sky im-810s(brick) and it in QSHUSB_DLOAd. I don't have hex file and mbn of chip Qualcomm Snapdragon S3 APQ8060. I do in mbn and hex file of 8660 it do not work. you can help me?. My english very bad, you can understand
[AT&T Samsung Galaxy Note I717] darkspr1te:
all the hex files ive seen

https://mega.co.nz/#!rNtj1SAI!I6CjkiaSDna6rV8GAToLYiB6t5E-dzQ4keYxSG8W7qc

good luck
[AT&T Samsung Galaxy Note I717] haminhthang:
help me

I'm sorry. My english very bad.I hope everybody will understand me
[AT&T Samsung Galaxy Note I717] E:V:A:
For those of you who make posts similar to this:

WTF!!

You need to learn how to provide more info,

or you will be hated here at XDA very quickly.

AND we will have your posts removed!

People like darkspr1te are of a rare kind who does all his work for free,

and people like you is wasting his time and wasting everyone else's time

as well, having to see and deal with your stupid posts.

You need to find out your exact model, you can find it in various places and under settings. (Or if bricked, under the battery inside.)

If you don't know how find this most basic info, de-bricking using these developer tools, is NOT for you!

I tried to find this model and processor info, but they're sold with different processors I think. Exynos and Snapdragon. You'll have to give us more specific info regarding model numbers and where you bought it.

1) How did you get it there?

2) Probably you updated bootloaders since these tools where created. All files are now signed...

No, the HEX files are extremely processor dependent. They have to match exactly.

It's unclear what it means that the cookie is not received, whereas if it was not valid, it would be more understandable.

The magic cookie is 12 bytes, but usually just specified by 8 hexdigits, appended to the SBL1 image. But there are several other things added there as well, depending... Do provide a hexdump of the last 128 bytes of a working sbl1 image file.

Perhaps, the device is not in a HEX receivable mode, after all. Perhaps, they've changed protocol with more recent bootloader updates?
[AT&T Samsung Galaxy Note I717] DennyTek:
It's the 2011 model with a snapdragon (from T-Mobile)

It's the 2011 T-Mobile galaxy exhibit rocking a 1ghz snapdragon MSM8255. here's the xda wiki page for it as well: http://xdaforums.com/exhibit-4g?nocache=1&z=5757149037472006
[AT&T Samsung Galaxy Note I717] haminhthang:
thank you

thank you, althought it don't helpful with me. because my phone have use recovery built wrong partition, so I use it to wide data and results it brick.

I have unbrick it by QPT software of qualcom but it no use and it have error "Image Download Failed. Cookie(if present) not receiced.". if everyone know fix it, I will thank very much.
[AT&T Samsung Galaxy Note I717] Sergius89:
It is a Motorola Electrify M XT901 mobile phone.

It is have a dual core CPU with 1.5 GHz core clock and adreno 225 GPU. It seems thet cpu is from Qualcomm Snapdragon 4 family. Phone have not gsm modul.

Under the battery its not useful find information about CPU becous ther is a RAM chip soldered on top of the CPU.

I think thet it is a MSM8960 chip but not sure.

Tried flash MSM8960.hex abd have cookie error.

listen to any suggestions. Thanks.
[AT&T Samsung Galaxy Note I717] darkspr1te:
I give up. Please close this thread
[AT&T Samsung Galaxy Note I717] lovepashah:
Need Help on SHV-E160s 32 GB

Hi I need help on my SHV-E160S Galaxy note wrongly flashed international ROM with pit file on my SHV-E160Variant and it is bricked.

I tried your brixfix method and now it is booting into download as well as recovery but Bootlader changed from SHV-E160S to SHV-160L

And now i flash any rom it boot loops only flashing rom successfuly was E160L_Teamleader_v1.0 i.e. SHV-E160L-PDA_V1.0.tar ROm it bott and comes up but touch screen dont work.

kindly help all other rom gives boot loop of all variants.

Need help seriously.
[AT&T Samsung Galaxy Note I717] darkspr1te:
It has been discussed many times that you require the bootloaders from the S model, you replace the one in the brickfix package (aboot.mbn is most important as that defines the device model/type)

I have many times requested that users backup and post these files, as i dont have the device i cant help.

darkspr1te
[AT&T Samsung Galaxy Note I717] rruleford:
Could this work for the tmobile s2. If so how could I make it work? Running backtrack on my laptop right now so it would be perfect time to try
[AT&T Samsung Galaxy Note I717] darkspr1te:
please see Posting guides
[AT&T Samsung Galaxy Note I717] lovepashah:
Thanks Darkspr1te & Babaknuri

HI Darkspr1te

Thanks for the wonderful program that you made and thanks to babaknuri for the bootloaders files of SHV-E160S 32 GB

By Mistakenly i had Flash my SHV-E160S with N7000 International Version Pit File and Firmware which Bricked by Device to QHSUSH_Dloader Mode. Only Black Screen. No Download Mode, No Recovery Mode.

And I Came Across your thread and tried your method i was able to get my Device on download Mode but my bootloader changed from SHV-E160S to SHV-E160L

And Thanks to BABAKNURI who had give me the bootloader files after lot of tries of SHV-E160S and i was able to GET my phone up and running.

Sharing SHV-E160S 32 BG Bootloader including pit file taken backup from your application darkspr1te. AS you didnt had bottloader and will be helpful other SHV-E160S Users

Thanks again Darkspr1te a lot for the wonderful application.
[AT&T Samsung Galaxy Note I717] tech128:
Hello darkspr1te,

I have an HTC Evo 4G that I bricked when I forgot about the different erase sizes on 003 and 004 evos.

I flashed the eng hboot onto it, and now it only boots to hboot. It still sees the old partition table, but if I try to read anything from them, it just says "bad block!" (I'm very certain the whole emmc isn't bad)

I was able to get code to directly execute in hboot by patching the jump command in memory and can execute any arm code directly on the device. This was kinda cool for a little while, printing stuff to the screen, etc. But since I'm not really getting anywhere with that method I decided to try this route.

I have NPRG8650 hex and bin files. They load and execute, but it doesn't seem to do anything but slightly change the vid and pid. It still is reported to any version of linux as /dev/ttyUSB0

I tried to force the usb mass storage driver onto the new vid/pid, but it doesn't want to do anything once it's loaded.

Since the evo uses the mbr and ebr format for the partitions, it is quite difficult to create a partition.xml

It also uses mtd format for the flash, which seems to be more difficult to deal with in general.

Especially since I can't read any of the partitions off of the device.

I read in one of your previous threads that you were able to read and write the emmc directly somehow, after loading the hex files.

Did you use revskills to do that, or some other way?

By the way, here's a copy of the partition table:

... INFO[radio]:(OTHER) block start=0, size=497 (0 KB)
INFO[hboot]:(RAW) block start=497, size=6 (768 KB)
INFO[misc3]:(RAW) block start=503, size=7 (896 KB)
INFO[mfg]:(RAW) block start=510, size=6 (768 KB)
INFO[sp1]:(RAW) block start=516, size=9 (1152 KB)
INFO[wifi]:(RAW) block start=525, size=5 (640 KB)
INFO[recovery]:(RAW) block start=530, size=40 (5120 KB)
INFO[boot]:(RAW) block start=570, size=20 (2560 KB)
INFO[system]:(YAFFS) block start=590, size=2800 (369600 KB)
INFO[cache]:(YAFFS) block start=3390, size=1280 (168960 KB)
INFO[userdata]:(YAFFS) block start=4670, size=3421 (451572 KB)
INFO[wimax]:(RAW) block start=8091, size=96 (12288 KB)
INFO[misc]:(RAW) block start=8187, size=5 (640 KB)
INFO[rcdata]:(OTHER) block start=0, size=0 (0 KB)
INFO[cpld]:(OTHER) block start=0, size=0 (0 KB)
INFO[microp]:(OTHER) block start=0, size=0 (0 KB)
INFO[a1026]:(OTHER) block start=0, size=0 (0 KB)
INFO[tp]:(OTHER) block start=0, size=0 (0 KB)
INFO[nv]:(OTHER) block start=0, size=0 (0 KB)

Each block is 128k

It looks like radio through misc are standard partitions, while the rest are extended, but I'm not totally sure.

Another problem is that I don't have the correct partition ids for all those partitions.

I have them for hboot, boot, system, userdata, recovery, and misc. But not for any of the others.
[AT&T Samsung Galaxy Note I717] darkspr1te:
Hi,

when you say you have "NPRG8650 hex and bin files" do you mean the hex and mbn sdcard loader?

can you post your dmesg when you trigger the upload? does it change pid/vid when you only upload the hex (this is executable code) or when you send the mbn/bin file? the mbn file is only written, it point of execution happens after restarting the device. If your change of pid/vid happens after the mbn file when the device is reset does it stay at that pid/vid for all power on's after that or does it go back to the original pid/vid ?

you can have up to 2 pid/vid changes, breifly here is what happens

upload of hex, hex executed, pid/vid change to represent the device in QDLOADER mode (it's now running minimal code to write to emmc)

after upload of mbn device , no pid/vid change should occur unles device is reset after upload of mbn file as all your doing is writing to emmc, the QDLOADER code thats running will allow you to carry out other functions , eg write to memory, read memory etc. , the python script for uploading the hex/file file triggers a reboot at the end, this can be commented out for debug purpose to see if the device is still in qdloader mode or not, if it is still in qdloader mode and you can carry out further qdloader functions then the issue lies with the .mbn which is a mini os to only provide access to sdcard

darkspr1te
[AT&T Samsung Galaxy Note I717] tech128:
Hello darkspr1te,

I mean the hex file flash programmer. I have the hex and converted binary form of the hex. I do not have the bin / mbn. That is the problem.

It changes pid / vid when the hex is uploaded. So it must be getting to QDLOADER mode, but I can't go any further at the moment.
[AT&T Samsung Galaxy Note I717] darkspr1te:
Have you tried any other mbn/sdcard loader ? Along with your working hex file?

Darkspr1te
[AT&T Samsung Galaxy Note I717] tech128:
No I haven't. I thought I had to use a msimage file that was generated by emmcswdownload, based on partition data from the device.

I'll try to find some sdcard loaders that might be compatible.
[AT&T Samsung Galaxy Note I717] darkspr1te:
The hex file is a small 'get you going code' that loads into the cpu to allow debug/diagnostics/writing to emmc in slow mode, it only there for us to write the mbn file which is again a small get you going code but boots the cpu in custom code that exposes the emmc as a sdcard.

I've been able to use other mbn files not for the exact model but same series, so in my case any 8x60 mbn worked, although no promises, am no expert.

It's a start, if you can execute the hex and it's able to accept further qdloader commands then your half way there.

It's worth reading my thread on debricking the 8660/shv-e160l, it shown there what commands/triggers can be sent after the hex.

are you running linux or windows ?

darkspr1te
[AT&T Samsung Galaxy Note I717] tech128:
I can run whatever os is required. My server is running linux. So I've mostly been working from there.

I just tried to use the 8660_msimage.mbn. It didn't like it.

-snip-

Writing 1024 bytes to 0x00430400; 708 bytes left.

Writing 708 bytes to 0x00430800; 0 bytes left.

Executing file...

Sending MAGIC...

Sending secureMode...

Sending openMulti ...

MSG: No partition table received before open multi

ERROR: No partition table received before open multi

Invalid openMulti response.

I skimmed that thread on debricking the 8660/shv-e160l, I'll have a closer look.
[AT&T Samsung Galaxy Note I717] darkspr1te:
ok, well good to know, it's been a while since i dug into the qualcomm docs, they are archived due to space but i will try and have a look to see what the cpu layout of the 8650 is, there are differences in the partition system between the 7xxx/8xxx , the 7 series does not use same 3 stage sbl onto aboot.mbn setup for example.

if your willing to guineapig your device i will try and help you through further understanding of the different setup's between the cpu's/parititions.

no promises but if we can get into sdcard mode we are 99% there.

I recently helped a user debrick a cherry burst without ever seeing the device, that user is now dev'ing a version of cm11 for the device and has built enough data up for a automated debrick of the device, although i've not implemented the device into my automated system due to time.

I am currently working with some local communities here in Zambia where i live to do a music festival, try and get the local music out there along with some well known act's from around the area.

Check out the facebook page for it,if you like it, the Hit the Like

http://www.facebook.com/Siavongamusicfestival

darkspr1te

EDIT: found a phone that has the same cpu, this link 8650 CPU WP7

it uses the following partition layout

this is a different partition layout so the 8x60 mbn will not work. thats my mistake.

i will try and look at my notes again,
[AT&T Samsung Galaxy Note I717] tech128:
Darkspr1te,

Sure no problem. If it bricks past being able to get into qdloader mode, I can always try to jtag it. Although I would prefer not to since I'd have to do a lot of probing to find which pad is which.

I'm having a pretty hard time finding any 8650 based mbn loaders. This might take awhile. Still reading your debrick thread btw.
[AT&T Samsung Galaxy Note I717] darkspr1te:
I Might be wrong, but the 8x50 series is before they introduced the single image file, it a multi image file(s) we are now looking for using those file names i quoted in my prior post, the OEM's themselves will give them different names or collectively call it one thing. in your case we need to load several files into the device for trigger the sdcard mode and i am not even 100% sure it's has a s card mode and it's not just a case of replacing the .mbn files with the ones you get from another device/fw upgrade. This is where we also need to dig into the f/w upgrade files for the device, see whats in there and what they call the files, there are several methods i used to match my 8660 device files to the samsung naming convention, but thats another story.

darkspr1te
[AT&T Samsung Galaxy Note I717] tech128:
You might be right on the no-sdcard-mode. I haven't seen any mention of it through most of my readings on debricking 8650 based phones.

But looking at this one particular recovery set I have, it looks like all I might need is a good partition.mbn file.

user@internet ~/downgrade_WM6_boot $ ls -la

total 1368

drwx------ 2 user user 4096 Jan 28 23:49 .

drwxr-xr-x 15 user user 4096 Jan 28 13:16 ..

-rw-r--r-- 1 user user 199364 Jan 7 03:44 NPRG8650.bin

-rw-r--r-- 1 user user 560823 Jul 20 2011 NPRG8650.hex

-rw-r--r-- 1 user user 33424 Oct 29 2011 dbl.mbn

-rw-r--r-- 1 user user 275372 Oct 29 2011 fsbl.mbn

-rw-r--r-- 1 user user 291424 Oct 29 2011 osbl.mbn

-rw-r--r-- 1 user user 464 Apr 28 2010 partition.mbn

I'll take a crack at that after I'm done reading your thread. The more attack vectors, the merrier.

Darkspr1te, I really appreciate all the help you have given me thus far. I can't thank you enough.
[AT&T Samsung Galaxy Note I717] darkspr1te:
Your Welcome,

Can you post those files, I would like to have a look inside them.

they are sort of triggering a memory but i would have to look at some of the docs i have to really help, but i think there is a sdcard mode, i would have to see inside the files first to be sure , something about anyclub.org which is not loading on my end right now,

darkspr1te