yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy S II SGH-T989] Suraido:
Just to let you guys know i'm not dead, and still working on this, just had some much crap to handle lately with my company and one of my friend's company too. Plus my original friend with the t989d took forever to give me the other phone and to boot he threw it into the wall and seems dead also :mad: ... So will be trying to bring it back to life using both phones and then hopefully i will be able to actually do something with this... And to answer a few new followers, if your phone is hard bricked and only gets detected on USB as a qualcomm modem device of some sort, yes once we are done with all this, it should bring your hard bricked t989d back to life, if it has no material defects and is really just hardbricked.
[T-Mobile Samsung Galaxy S II SGH-T989] xDonny:
I have a hard bricked t989d in mode 9008.

I am eagerly awaiting any progress on this
[T-Mobile Samsung Galaxy S II SGH-T989] Trozzul:
hopefully soon, i still dont know what i can do to help, probably nothing at this point.
[T-Mobile Samsung Galaxy S II SGH-T989] Lord Zog:
I'll be getting back into this as soon as I'm out of the hospital. I didn't forget you guys, and no, its not me who's admitted. :) I'm here with a friend.
[T-Mobile Samsung Galaxy S II SGH-T989] Suraido:
We all are :P and yes 9008 mode is the same as all of us, since our t989ds all have the qualcomm 9008 modem :) And so we already have some good progress going so far, and i've been able to push some files into the t989d without too many hickups, but i'm still missing some images and a viable partition table to complete the unbricking on my side. And we have a few good souls and a few experts on this, so we should be able to get it done. Only problem is that most of our experts have very little time to fiddle around with this for now, so progress is slow. Myself, i'm still in the thick of work with my company and a friend's company too and i have too much work and too little time for now to touch the t989d... Plus i have to try to revive one that a friend threw into the wall to be able to try and get the files i need out of it... So that slows my progress down big time!! Plus as i said, with the workload i have right now, it'll be about 2 weeks or so before i can have time to check into this again and try to do miracles. So don't get discouraged, progress is slow, but no one abandonned this yet, so we will get there sooner or later :)
[T-Mobile Samsung Galaxy S II SGH-T989] xDonny:
Can this phone be unbricked with a jig?
[T-Mobile Samsung Galaxy S II SGH-T989] Suraido:
Nope, tried it before and doesnt work. This phone has the newer MMC chipset with emergency download mode so the USB jig method wasnt necessary and wasn't implented.
[T-Mobile Samsung Galaxy S II SGH-T989] xDonny:
I'm slightly crestfallen at that. Is there anything I can do to help?
[T-Mobile Samsung Galaxy S II SGH-T989] nate38654:
magldr or something?

So what are we waiting on, a good s2 img that will write the bootloader. Am I understanding right? Is there any thing I can do to help also? Can we not boot from sd in the mean time like we dis on thw hd2 where we had a option to boot wp7 or android with magldr? Theres got to be something. Where there is a will, there surely is a way.:p
[T-Mobile Samsung Galaxy S II SGH-T989] nate38654:
magldr ?

oh btw, Mine bricked while flashing in twrp somehow!

---------- Post added at 10:38 PM ---------- Previous post was at 10:17 PM ----------

OK!I, downloaded the img file and used disk img to burn to micro sd and now I have successfully made my way back into twrp. Now I will try to wipe and flash. I will update in a bit. Seems as if you have had twrp loaded before hard brick, this might just work! I phone was stuck in qhsusb_dload 9008 and didn't even do anything, now I ameven recognized in odin!

---------- Post added at 11:23 PM ---------- Previous post was at 10:38 PM ----------

Any way to add a rom to flash in twrp on that img file , My problem is I cant switch micro sd cards and install new rom.
[T-Mobile Samsung Galaxy S II SGH-T989] Trozzul:
Your not able to get into Download mode? if you can try flashing a rom there. your device was hard bricked right? not able to access anything no sign of life. i dont use twrp so i cant help you there. also the point we were trying to do is yes making the device boot off of a SD card.
[T-Mobile Samsung Galaxy S II SGH-T989] nate38654:
yes no sighn of life what so ever !and now its working!!!! I booted to twrp recovery with your img file, mounted sd , added a zipped rom to sd. un mounted sd and installed the rom. Perfect!

Seems to only run off sd card though , what gives.
[T-Mobile Samsung Galaxy S II SGH-T989] nate38654:
Update

I am now able to boot into system and also download mode removed sd and fixing to install rom in odin once jelly bean official tmobile t989 rom finishes downloading.

still needing img on sd to boot roms! I don't understand.

It seems that my emmc bootloader fails so it boots with sd, is this correct? how do i fix this?
[T-Mobile Samsung Galaxy S II SGH-T989] nate38654:
help please!

or can I at least make the image a second partition on the sd card so the phone doesn't say blank sd card?
[T-Mobile Samsung Galaxy S II SGH-T989] Trozzul:
im not sure, is there any files you want me to dump to you? one of my working T989s is on ICS i could update it to jelly bean if you need me to, here walk me through what you did to boot it from your SD card, my hard bricked T989 had CWM before and you said you have Twrp so this might not work, just walk me through it i guess, link the the image burner, the image you got.
[T-Mobile Samsung Galaxy S II SGH-T989] xDonny:
Could you post a guide on what you did to get it to twrp? I think I had that installed before my brick.

EDIT: Read your post, I"ll try the steps you''ve already detailed

EDIT2: I suppose I'll wait, I can't get the img to go to the sd card with any software I have.
[T-Mobile Samsung Galaxy S II SGH-T989] xDonny:
Can you send the image you put onto the sd card? I've tried the ones downloaded in this thread and they all say they are corrupted and cannot be used
[T-Mobile Samsung Galaxy S II SGH-T989] nate38654:
Give me a couple days as I am in the hospital and just had a baby, or the wife did. I will follow up with you guys soon.
[T-Mobile Samsung Galaxy S II SGH-T989] xDonny:
Congrats on the kid!
[T-Mobile Samsung Galaxy S II SGH-T989] Trozzul:
Yeah Congrats man, hopefully everything went Well. please take your time!
[T-Mobile Samsung Galaxy S II SGH-T989] gohaun:
Congrats on having a kid.

I though we were waiting for the T989D boot info.

I sent the info from my T989, but was under the impression that you needed another boot info from the T989D

With this thread, will we be able to get the picture data off with this method.

Brian L
[T-Mobile Samsung Galaxy S II SGH-T989] paranoxxx:
Hi ,

there is a chance that this work with ours T989 ?

Ultimate cure to the 'QHSUSB_DLOAD' of Mi2/S

http://xiaomi.eu/community/threads/ultimate-cure-to-the-qhsusb_dload-of-mi2-s.20567/
[T-Mobile Samsung Galaxy S II SGH-T989] xDonny:
This particular program doesn't work but I'm sure it's similar to the brixfix software we have seen earlier in the thread,

Does anybody have any updates? I want this phone to stop being a paperweight
[T-Mobile Samsung Galaxy S II SGH-T989] paranoxxx:
Hi ,

as you can see , the phone is being recognized on the MiFlash...
[T-Mobile Samsung Galaxy S II SGH-T989] xDonny:
Yes, mine did as well, however it will not read any image files I use.
[T-Mobile Samsung Galaxy S II SGH-T989] gohaun:
As far as I can tell the chipsets are similar but are NOT the same for the mi/mi2 and the SGH-T989.

So you should be able to see it like you have mentioned, but the program cant go around the boot files as those are different.

Im also waiting for an update, as I have one sitting here that is in perfect condition.

I got a zip file sent to the guys that need it, but I dont have anything else that I can do that I know of.

If there is, let me know.

Brian L
[T-Mobile Samsung Galaxy S II SGH-T989] xDonny:
Could you supply me with the zip file you have?
[T-Mobile Samsung Galaxy S II SGH-T989] paranoxxx:
Please could you upload the zip :)
[T-Mobile Samsung Galaxy S II SGH-T989] gohaun:
It what the backup file that they wanted from an unbricked device.

Its on post #52 if you want to download it.

Brian L
[T-Mobile Samsung Galaxy S II SGH-T989] Krebs830:
It appears that the "boot from sd" option wasn't implemented until the Galaxy S3. However, using Brixfix v2, a stock JB ROM, a lot of research and a little trial and error I was able to unbrick my Galaxy S2 (SGH-T989, 16GB) from the Qualcomm 9008 mode. I used the latest Ubuntu, but for some reason the "read" commands in Brixfix.sh didn't work, so I bypassed those parts. I also took a chance and used the partition0.bin from the folder supplied with Brixfix (since they're similar chipsets and both are 16GB) and it worked! Afterwards, I was able to boot it into Odin mode and reload the stock .pit and ROM, and now the phone works like it should. :D
[T-Mobile Samsung Galaxy S II SGH-T989] xDonny:
Did this - got to Odin mode, I'm confident this is fixed though.

Thank you to all the contributors of this.
[T-Mobile Samsung Galaxy S II SGH-T989] gohaun:
Do you have the steps on what you did that worked?

I have one sitting here that has been waiting for months to get fixed.

Was the Brickfix V2 what I used or did you find that somewhere else?

Thanks

Brian L
[T-Mobile Samsung Galaxy S II SGH-T989] Krebs830:
Yes, I used Brixfix V2 from this thread:

http://xdaforums.com/showthread.php?t=2136738

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

I basically followed the instructions given there, except as follows:

1. In the brixfix folder I created a folder named SGH-T989-16GB, then unzipped the T989 JB ROM into it. I then copied partition0.bin into it from the SHV-E160L-16GB folder.

2. I opened brixfix.sh in gedit and:

A. Changed the model no. from "SHV-E160L-16GB" to "SGH-T989-16GB"

B. Changed all instances of "read -n 1 choice" to "read choice"

C. Saved and exited.

3. In the terminal window I typed "sudo sh brixfix.sh" (it didn't accept "sudo ./brixfix" for some reason).

I had to run it three times, and answer "y" each time. After that, the phone tried to boot, and failed. I took the battery out, put it back in, held the + and - keys and plugged in the USB cable (connected to the computer, of course). It booted into download mode, and from there I was able to Odin the stock .pit file and ROM.
[T-Mobile Samsung Galaxy S II SGH-T989] gohaun:
You used ubuntu 14.04 correct?

I will see if i can get it to work on windows 7 (64 bit).

Thanks for the heads up as i havent been looking around but to just watch this thread.

Brian L
[T-Mobile Samsung Galaxy S II SGH-T989] Krebs830:
Yes, Ubuntu 14.04. I used Windows 7 x64 for Odin. I'm a newbie on Linux, but it's been fun learning about it.

---------- Post added at 03:11 AM ---------- Previous post was at 02:56 AM ----------

My apologies, I forgot to state that I downloaded the Qualcomm .bin and .mbn files for the T989 and copied them into the brixfix folder. I think the ones he supplied are different. I'm at work now, but I'll verify this when I get home.
[T-Mobile Samsung Galaxy S II SGH-T989] Krebs830:
I zipped-up the files that I used to successfully unbrick my phone and uploaded the file to sendspace (/file/4ybh7c)

Unfortunately, it's a free account, so for now it's only available for 30 days. Unzip it, and copy the contents of the folder into the Brixfix-2-1 folder, and allow them to replace existing files.

Disclaimer: These are for a T-Mobile Galaxy S2, SGH-T989 (a.k.a. "Hercules"). They worked for me, and they could work for similar models, but all downloaders will use them at their own risk. I am not responsible if you damage your phone.

All credit goes to [MENTION=4864296]darkspr1te[/MENTION] and his contributors.
[T-Mobile Samsung Galaxy S II SGH-T989] Joe Blough:
Could you be so kind to point me in the direction of the stock .pit file and ROM :o)

I can probably get the rom but the pit would be grand...or both as you know they work:good:
[T-Mobile Samsung Galaxy S II SGH-T989] gohaun:
There are only 4 files, just copy those into the Brixfix 2-1 folder?

Should I remove the SHV-E160L folder from the Brixfix 2-1 folder that i have?

So then this will allow us to just start at step 3 in your post #92. Is that correct?

Thanks

Brian L
[T-Mobile Samsung Galaxy S II SGH-T989] Krebs830:
Should be 3 files and a folder. You don't need to remove the other, the program won't use it.

---------- Post added at 01:38 AM ---------- Previous post was at 01:08 AM ----------

Yes, it should be 3 files and a folder, and you can start at step 3. You don't need to remove the other, the program won't use it. I'll add the .pit file to the zip. I'm having trouble receiving PM's at work, so I apologize if I don't reply.
[T-Mobile Samsung Galaxy S II SGH-T989] paranoxxx:
Hi ,

i think it did not worked for me .

The first time i run the brixfix.sh it seemed that it was working , there was informations of writing files...

but there was a mistake , the Qualcomm .bin and .mbn files for the T989 were not in the brixfix folder

now when i try to run brixfix.sh , i have this :

Tested with backtrack r5 :

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

Checking For Qualcomm Device
No QDLOAD device found, checking for SD-CARD Mode
Device found !!!!
Mode is SD-CARD/msimage mode at device node /dev
With USB PID/VID ID of 05c6:9025
Detailed Output is Bus 001 Device 015: ID 05c6:9025 Qualcomm, Inc.

Do you wish to write parititon Warning Dangerous
y

Writing parititon to /dev
dd: opening `/dev': Is a directory
dd: opening `/dev': Is a directory

Do you wish to write bootloaders Warning Dangerous
y

Writing bootloaders sbl1,sbl2,sbl3,rpm,aboot to /dev
dd: opening `/dev': Is a directory
dd: opening `/dev': Is a directory
dd: opening `/dev': Is a directory
dd: opening `/dev': Is a directory
dd: opening `/dev': Is a directory

Do you wish to write TrustZone Warning Dangerous
y

Writing TrustZone to /dev/
dd: opening `/dev': Is a directory

If no errors occured then disconnect and remove/replace battery, if ANY error occured do not disconnect device, fix error and rerun or seek advice !!

Same on Ubuntu

Brick Fix v2-0
______________
-e By Darkspr1te, See README for thanks & References
-e
-e Checking For Qualcomm Device
No QDLOAD device found, checking for SD-CARD Mode
-e -n \e[00m
-e Device found !!!!
-e Mode is SD-CARD/msimage mode at device node /dev
-e With USB PID/VID ID of \e[00;44m05c6:9025\e[00;31m
-e -n Detailed Output is
-e \e[00;33mBus 001 Device 009: ID 05c6:9025 Qualcomm, Inc. \e[00m

-e Do you wish to write parititon \e[00;31mWarning Dangerous\e[00m
y

[: 134: y: unexpected operator
-e Do you wish to write bootloaders \e[00;31mWarning Dangerous\e[00m
y

[: 134: y: unexpected operator
-e Do you wish to write TrustZone \e[00;31mWarning Dangerous\e[00m
y

[: 134: y: unexpected operator

If no errors occured then disconnect and remove/replace battery, if ANY error occured do not disconnect device, fix error and rerun or seek advice !!
paranox@ubuntu:~/Desktop/Brixfix/Brixfix-2-1$

the phone is no longer detected as QDLOAD device.

what i can do now :( ??
[T-Mobile Samsung Galaxy S II SGH-T989] Krebs830:
There must still be a bug in the "read" commands. By the first printout it looks like the first part was successful, and your phone is no longer in the QDLOAD mode, it's now in SD-CARD mode, which is part two. If we can debug the "read" commands it should work. I'll look at it when I get home from work.
[T-Mobile Samsung Galaxy S II SGH-T989] Trozzul:
alright so what i am getting at by reading so far is you used this brickfix program and was able to get into download mode somehow? mind explaining a little more and where would you get these files? upload them to mediafire or something please!
[T-Mobile Samsung Galaxy S II SGH-T989] Krebs830:
Hi! I jumped into this thread at post #89, and after that I began describing what I've done to unbrick my SGH-T989 using darkspr1te's BrixFix V2. I've posted a link to his thread, uploaded a .zip file to sendspace, and posted the info to access that (I'm not allowed to post external links, yet). I now find that I've made a mistake while editing the shell, and am working to correct it. Note that the repair mode for BrixFix only functions in Linux, according to darkspr1te. Please consult his thread, as well. Thanks!
[T-Mobile Samsung Galaxy S II SGH-T989] Krebs830:
Update

Okay, I've corrected the shell, added the .pit file (for use with Odin) into the SGH-T989-16GB folder, compressed all into a new SGH-T989.zip and uploaded it to www.sendspace.com/file/gy3s0l (the last character is a lowercase L, not a 1). I didn't include the Jelly Bean ROM, as I'm limited to only 300MB on sendspace. The ROM and Odin flashing instructions are readily available on xda and elsewhere, you just need to search for whichever version your phone was on when it bricked.

This was all performed using Ubuntu 14.04, on the desktop. It seems to work in rudimentary testing, but I no longer have a bricked phone to experiment with. The disclaimer I posted above still applies.

Note: Disregard the steps I described previously, and do this:

1. Go to darkspr1te's BrixFix V2 thread (linked above), read his instructions, then download and extract the complete BrixFix package (the first download link).

2. Download SGH-T989.zip from www.sendspace.com/file/gy3s0l and extract it. You will get a folder named SGH-T989. Open it and copy all of the items as-is into your Brixfix-2-1 folder. Allow it to overwrite the existing files.

3. Plug your phone into your computer, if it isn't plugged-in already.

4. Open a terminal session and navigate to the Brixfix-2-1 folder.

5. Type the following commands:

sudo chmod a=rwx brixfix.sh

sudo ./brixfix.sh

When it prompts, type "y". At this point, if you get an error, DO NOT answer "y" to anything else! Things have to happen in a particular order. A bunch of writing should occur, then it should end with some instructions. Follow them.

6. Repeat step 5 up to 3 more times.

7. Afterwards, the phone may attempt to reboot on its own (and fail), but that's ok.

8. Disconnect the phone from the USB cable. Take the battery out for several seconds and put it back in.

9. Hold the + and - buttons down, and connect the USB cable. If all went well it will boot into download mode, and then you can use Odin to flash the .pit file and ROM.

Let me know how it works. If it doesn't, I will continue debugging. If it does, I'll submit all this to darkspr1te so that he can incorporate it, if he wants.

Thanks,

Jim
[T-Mobile Samsung Galaxy S II SGH-T989] paranoxxx:
still stuck here for me :/

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

Checking For Qualcomm Device
No QDLOAD device found, checking for SD-CARD Mode
Device found !!!!
Mode is SD-CARD/msimage mode at device node /dev
With USB PID/VID ID of 05c6:9025
Detailed Output is Bus 001 Device 012: ID 05c6:9025 Qualcomm, Inc.

Do you wish to write parititon Warning Dangerous
y
Writing parititon to /dev
dd: opening `/dev': Is a directory
dd: opening `/dev': Is a directory

Do you wish to write bootloaders Warning Dangerous
y
Writing bootloaders sbl1,sbl2,sbl3,rpm,aboot to /dev
dd: opening `/dev': Is a directory
dd: opening `/dev': Is a directory
dd: opening `/dev': Is a directory
dd: opening `/dev': Is a directory
dd: opening `/dev': Is a directory

Do you wish to write TrustZone Warning Dangerous
y
Writing TrustZone to /dev/
dd: opening `/dev': Is a directory

If no errors occured then disconnect and remove/replace battery, if ANY error occured do not disconnect device, fix error and rerun or seek advice !!
paranox@ubuntu:~/Desktop/Brixfix-2-1/Brixfix-2-1$
[T-Mobile Samsung Galaxy S II SGH-T989] Krebs830:
Alright, the read command is working now, but this is a different issue. Try this: unplug the phone from the computer, remove the battery for 10 seconds or so, put it back in, and reconnect (don't push any buttons). Try running it again, and post the results.
[T-Mobile Samsung Galaxy S II SGH-T989] paranoxxx:
think no changes...

paranox@ubuntu:~/Desktop/Brixfix-2-1/Brixfix-2-1$ sudo ./brixfix.sh

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

Checking For Qualcomm Device
No QDLOAD device found, checking for SD-CARD Mode
Device found !!!!
Mode is SD-CARD/msimage mode at device node /dev
With USB PID/VID ID of 05c6:9025
Detailed Output is Bus 001 Device 013: ID 05c6:9025 Qualcomm, Inc.

Do you wish to write parititon Warning Dangerous
y
Writing parititon to /dev
dd: opening `/dev': Is a directory
dd: opening `/dev': Is a directory

Do you wish to write bootloaders Warning Dangerous
y
Writing bootloaders sbl1,sbl2,sbl3,rpm,aboot to /dev
dd: opening `/dev': Is a directory
dd: opening `/dev': Is a directory
dd: opening `/dev': Is a directory
dd: opening `/dev': Is a directory
dd: opening `/dev': Is a directory

Do you wish to write TrustZone Warning Dangerous
y
Writing TrustZone to /dev/
dd: opening `/dev': Is a directory

If no errors occured then disconnect and remove/replace battery, if ANY error occured do not disconnect device, fix error and rerun or seek advice !!
paranox@ubuntu:~/Desktop/Brixfix-2-1/Brixfix-2-1$
[T-Mobile Samsung Galaxy S II SGH-T989] Trozzul:
when i type in sudo ./brixfix.sh i get a command not found. should i be inside the brixfix-2-1 folder?
[T-Mobile Samsung Galaxy S II SGH-T989] gohaun:
Ok I got to step 5 here.

First issue is that it has the read -n 1 choice

Changed that to the read choice like you mentioned in the other steps.

When I get that going, I hit y the first time and i get:

brixfix.sh: 34: [ y: unexpected operator

Operation cancelled at user request

Unable to continue from here.

I start the brixfix.sh and it shows QDLOAD device found, so its still in that first stage.

Thanks for all the help so far.

Brian L

---------- Post added at 03:02 PM ---------- Previous post was at 02:45 PM ----------

It should be sudo sh brixfix.sh not sudo ./brixfix.sh

Im sure he will get that update. That is show on Post #92 if im not mistaken.

Brian L
[T-Mobile Samsung Galaxy S II SGH-T989] Krebs830:
Yes, I ran it from inside the Brixfix-2-1 folder, and "sudo ./brixfix.sh" seemed to work ok. I also found that I had to change the read lines back to "read -n 1 choice". Last night I tried using chmod to make the shell executable, maybe that's the difference. In terminal, in the Brixfix folder, type: sudo "chmod a=rwx brixfix.sh" (with the quotes) and hit enter. If you don't get an error, try sudo ./brixfix.sh again.

---------- Post added at 10:41 PM ---------- Previous post was at 10:26 PM ----------

Yep, same results. The shell isn't setting the "DEVICE" variable for some reason. I don't remember, are you using Linux or Windows? I think it only works in Linux. It doesn't have to be Ubuntu, as long as it has a terminal program. It also requires the "ls" (lowercase L) command set, which you can apt-get. To see if you have it, type ls or lsusb in the terminal window.
[T-Mobile Samsung Galaxy S II SGH-T989] gohaun:
I have a 14.04 ubuntu system running at this time.

I do have ls command set.

I ran the lsusb and linux sees the ID as the 05c69008 Qualcomm wireless modem (QDL mode)

When I try the sudo ./brixfix.sh I get command not found.

When I try to set it to a shell sudo "chmod a=rwx brixfix.sh" it gives me the command help for chmod.

Brian L
[T-Mobile Samsung Galaxy S II SGH-T989] Joe Blough:
Shoot, I didn't see the .pit file in the new .zip. Please upload for us :)

Thanks!
[T-Mobile Samsung Galaxy S II SGH-T989] Krebs830:
It looks like the phone is okay, and that it's being detected correctly. If I understand the dd message, it's unable to find the path to the phone, which is weird. Could Ubuntu have it mounted as a USB storage device? If so, try unmounting it and try again.

---------- Post added at 01:35 AM ---------- Previous post was at 01:25 AM ----------

It should be in the SGH-T989-16GB folder as pitfile.pit.