Develop Bugs

Harrier Forum?

Is it completely absurd me thinking that there should be a forum added for the Harrier as it is CDMA? I'm just thinking it would be a lot more convenient for people to find solutions for their particular hardware.

It would be nice since what works on the BA obviously doesn't work on the Harrier, but I think there must be an unusually small number of people that use the Harrier. It seems there is little interest in the Harrier judging by the fact you posted this question over 2 weeks ago and I'm the 1st to respond!

iam also intrested

Very Interrested.

I would be too. But everything has been said and done already about the Harrier (6600s). And until someone figures out how to get the rom updated to WM5 or 6 there is nothing else. Every other forum is dead or removed that I know of. I brought up trying to use the WM5 rom for a samsung i730 as our stepping stone. But as of now there hasn't been any reply.
I'll say it again. If anyone could tell (show) me how to strip down the rom from the i730 to just the OS and the drivers, I think we could get somewhere. But I know next to nothing about it. And sure as hell don't know enough to go it on my own.

The main problem is the bootloader, not OS. To run WM5/6, you need a WM5/6 compatible bootloader. The OS itself is actually not device specific. It can actually be ported from one device to another with relative ease. The drivers may be a problem, but I've heard in some cases WM2003 drivers can work, and I think most drivers from the Blue Angel may work in the Harrier with the exception of the radio drivers. So basically, I think even tearing the i730 ROM apart won't help. That's not even considering the XIP! Most files in the XIP are device-specific. Even if we had a WM5/6 capable bootloader, I'm not sure we could come up with a compatible XIP.
Samsung bootloaders are usually very, very different from HTC. It's remotely possible it could work, but if it doesn't, it will PERMANENTLY brick the phone. It could definitely at least get us further ahead if it were possible to try different bootloaders, but experimenting with bootloaders is 100% guaranteed to brick the phone. That would be no big deal if someone knew the JTAG pads in order to repair a bricked phone with corrupt bootloader, but without knowing the JTAG pads, it's rather silly to even attempt it.
Most of the time when a device doesn't support WM5/6, but someone made it work, it's using the bootloader and XIP out of a leaked ROM. Perhaps through a secret connection through someone that works at HTC.
I tore apart my 6700's ROM and noticed there's a file, RadioServicePresent.dll that seems specific to CDMA whose description is "Harrier Radio Present Service". Could that possibly mean somewhere, there is a prototype WM5 for Harrier?

'No GSM' repair trying. Direct programming K5D5657ACM

First of all, sorry if my english is not very good. I'm from spain and I have a Universal that suffered a power failure during gsm flashing and the gsm bootloader was corrupt. It shows the message 'No GSM' during startup and i couldn't find the way to repair... Not possible to reprogram gsm firm, didn't work trying to Unlock, no SuperCID and it seems that neither Jtag (i read that jtag on Universal isn't connected to the gsm chipset).
So... i thought about programming the ROM chip of the GSM module directly accesing it's pins in the PCB. The main problem: this SMD chip has its pins under its body, like a typical PC main processor and not along its borders, so, the only way to see what points on the PCB could give us access to the concerned pins in the ROM, would be unsoldering it... ufff... not an option, but... when I was having a look at the PCB's pictures for the JTAG from the wiki...... Bingo! A completely naked PCB picture! But... oops, the zoom square of the JTAG zone, is just over the conducting paths i want to see!!!
Please! It would be fantastic that the person who made that picture, make another one, where i can see the whole gsm module to track the paths... even better if i could see the opossite side. But doesn't matter if don't!
This ROM employs an electrical protocol very similar to other ROMs and I think It should't be dificult to program using a PIC or similar to drive signals, data and timigs, just to read or write it "as a whole", secuentially. Of course if i find the way I will pos it here with details for everyone.
Thanks in advance! I'm fascinated with your work!

JTAG for radio chipset? I tried to find it but no luck, old problem with hermes/universal. I tried reworking the qualcomm 6250 but nothing. Chip you are talking about is BGA not SMD, and it is very hard to remove it.

sometime NO GSM and sometime will detect a radio rom.

why my dopod 838pro sometime it cannot detect a radio rom and show a NO GSM, but if detect it a radio rom and it will hang about and half hours and reset will turn back to NO GSM, is hardware or software prob, anyone can give me a solution?

Provide more information - OS version and Radio version. Its probably a hardware problem but you may try to reflash to a manufacturer's shipped version and retest.
I had the same problem basically. Phone would freeze up, get repeated NO GSM messages, drop the radio even when it finds it after several minutes of use. I did buy the phone off eBay used and it did freezeup in WM5 ALOT.
I took the phone apart and cleaned all the contacts - same problems. Reflashed manufacturer's rom again and it took. Before it sometimes would hang up - looking for GSM radio. Took it apart again FULLY and put everything back together. It is now working for the past week. No freezeups or drops. Seems to always find GSM on bootup.

last time using a official rom wm6 also freeze up, then flash it to manila2d rom, it also got a same prob, try reflash a radio rom, but always get stuck at 6%, but try and try then 100% done, but also same prob.
so ur solution is try Reflashed manufacturer's rom again?

Thats what I did but the flash alone didn't fix the problem. I don't think a rom flash will bring your phone back but you may get lucky. I had to open it up and clean and reposition things. For some reason it worked. I still get screen fade to white and the directional pad on the front sometimes doesn't work - you move the scroll wheel and it will work again. Might have to replace the dPad circuit board or flex cable. The HERMES seems to have MAJOR problems with quality control and the radios. I personally think the battery presses against a backing plate which rests directly against the chipsets. The silver plate behind the battery does flex and it shouldn't. It probably should be a little thicker to prevent flexing. The heat from charging and the pressure from the battery I think causes the radios to fail. Bad soldering also may be a problem but any pressure on a motherboard and chipsets isn't a good thing. Also screws that are too tight also may contribute to the problem.
My phone has been working for about a week. Prior to that it was getting constant NO GSM errors on bootup and dropped calls. Today the phone was out of the house for the first time in weeks and it worked without any problems - no freezes (did a lot before) and no dropped radio. It has been sitting on my desk for two weeks without any problem. Will try it a few more days and see.

herm200 no GSM
Hi! I have read all thread about no GSM from here.
I have already do many many tests, tried to flash any radio rom extracted, hard reset, mtty with set 1e 1... I have already dissasemble and reassemble it
but no one fix the problem No GSM.
I have the same probleme, sometime no gsm and sometime ok.
So please, if anyone find everything which can fix this problem please post it!
Sorry for my english!
Thanks a lot for all jobs and helps.

Hello all, my hermes had this problem too!
Sometime it works, " 1.56.70.11" and sometime no! "NO GSM"
i have done about twenty flash thinking it will resolve this problem...
After reading a topic on this problem, i have understand it was an hardware problem. Something unsolde.
I have buy "double face scotch", i have disasemble the phone completely.
And on every chip and on the "battery"( little round and flat) i have put a little piece of scotch. it will do a pression on every chip to keep chip connected on the motherboard.
From this moment, the phone has never freeze, no more "no gsm" message!
ALL IS GOOD
Sorry for my poor english.

Many things can affect the radio
Try this...
Un plug your batt... insert a big piece of aluminium under the batt over the gsm chip... it wil not work properly... Magnetic issues... the batt do this things too i prove it on a Nokia... the batt without the stick = radio problem no signal...
Abd here i got the same trouble no gsm sometimes i realized that has been a lot flashes but noup, was a dialer that makes this issues 3G phone canvas,.... back to touch dialer 3G or 2G and its good now... think the CPROG and some other is not so compatible.

Desperately please help me, my Dopod 838 Pro has No GSM!

hey dude try another rom... the roms with HTC phonecanvas 2g or 3g do this issues on my hermes dunno why... thats th reason i dont cook anymore phoncanvas on my roms.

Update Radio ROM to 1.47
I had same problem just recently, and the recommendation that I got was update your Radio ROM ONLY...I upgrade to Radio 1.47 as all the time I was loosing service connection as well as No GSM...after this, my Hermes took live again.
I had 1.16 Radio...!!! and that issue came up after upgrading to one of the so many cooked ROM...I don't remember which one...
Check this link for more info, it saved my life!!!
http://forum.xda-developers.com/showthread.php?t=295751
Cheers,

Why can't a bricked phone be revived?

This is a question for those in the know when it comes to programming.Why isn't there a way to revive a bricked phone? Can't there be some method for a host computer to manually write the radio to the device? How does HTC fix a bricked phone for it to be a refurb?
I'm just very curious about this because I see a few people attempt to update the radio only to lose power and brick their EVO. I have no programming experience so don't know what goes on at the internal component level. Thanks in advance for your input.

It goes back to the old bootstrapping problem when computers were being developed. A computer (in this case, your cell phone) is pretty dumb at the hardware level. All it can do is run programs. That's ALL it can do. It can't even load a program, only run them. Thus the problem. It gets solved by injecting a "bootstrap" program at startup (from the phrase "pull yourself up by your bootstraps") which is a program that runs and gives access to all the I/O, and the computer can then load more programs.
When you update this bootstrapping program, it gets dicey, because if it isn't written right, or if there's a glitch during the update, this most basic of all functions gets corrupted. If the program that tells the phone how to load programs goes away, all the phone can do is... sit there. Like a brick.
Hope this helped!

That helped me, thanks.

Soylent Grin said:
It goes back to the old bootstrapping problem when computers were being developed. A computer (in this case, your cell phone) is pretty dumb at the hardware level. All it can do is run programs. That's ALL it can do. It can't even load a program, only run them. Thus the problem. It gets solved by injecting a "bootstrap" program at startup (from the phrase "pull yourself up by your bootstraps") which is a program that runs and gives access to all the I/O, and the computer can then load more programs.
When you update this bootstrapping program, it gets dicey, because if it isn't written right, or if there's a glitch during the update, this most basic of all functions gets corrupted. If the program that tells the phone how to load programs goes away, all the phone can do is... sit there. Like a brick.
Hope this helped!
Click to expand...
Click to collapse
Thanks for the info. That is interesting. So how does HTC initially put the bootstrap in and/or how do they handle a bricked phone?

Soylent Grin said:
It goes back to the old bootstrapping problem when computers were being developed. A computer (in this case, your cell phone) is pretty dumb at the hardware level. All it can do is run programs. That's ALL it can do. It can't even load a program, only run them. Thus the problem. It gets solved by injecting a "bootstrap" program at startup (from the phrase "pull yourself up by your bootstraps") which is a program that runs and gives access to all the I/O, and the computer can then load more programs.
When you update this bootstrapping program, it gets dicey, because if it isn't written right, or if there's a glitch during the update, this most basic of all functions gets corrupted. If the program that tells the phone how to load programs goes away, all the phone can do is... sit there. Like a brick.
Hope this helped!
Click to expand...
Click to collapse
Thanks good explanation appreciate that.

rafroehlich2 said:
Thanks for the info. That is interesting. So how does HTC initially put the bootstrap in and/or how do they handle a bricked phone?
Click to expand...
Click to collapse
There is probably a JTAG interface somewhere in there. In fact,that's how the original hack of the IPhone was done. (Better ways were since found) Most devices have a quasi standard interface for programming the flash and accessing and the hardware for diagnostics. For instance,linksys routers actually have a spot on the board to solder a header and you can make a cable that connects to the parralel port. Do a google search for "Hairy Dairy Maid Debrick" and you will find it. A similar thing is probobally possible with the Evo (Ive even seen them on Hard Drives and CD Rom drives) The problem is,its not entirely standardized,and it might not even be a connector or pads on the board. It might instead be a matter of knowing where you can connect the leads on the board to something that under the right circumstances BECOMES the JTAG connector. (For instance,a pin that controls something else might be a JTAG interface for the first few hundred milliseconds of start-up,or if a certain other pin of the chip is grounded when the power is applied. It might also be completely internal to the chip,and there be NO connectors on the board (it almost CERTAINLY has the capability,they need it during prototyping) and the chips might be programmed BEFORE they are soldered in. It might take replacing the rom chip to get it to go. There are lots of ifs
Chances are though,the factory has a special cable and a special software program that can reprogram the device. To replicate that might be relatively easy or could be next to impossible but requires a certain degree of knowledge about the hardware. What I suspect is,until someone who has the skills to make such a cable bricks their phone,they wont bother figuring out how to debrick one. In fact,when that person bricks their phone,they will probably take it back to sprint and say "I dont know what happens" In fact,even if its stuck looping in an obviously hacked boot loader he for some odd reason cant undo,hes probably going to send it back to sprint. I know someone who did exactly that to their brand new HP laptop. He found that 15kv from the flyback of an old B&W television applied to the memory slots took care of the looping and Best Buy gave him another one. As he put it "I dont know what happened,but it smells bad and wont boot up"

pflatlyne said:
There is probably a JTAG interface somewhere in there. In fact,that's how the original hack of the IPhone was done. (Better ways were since found) Most devices have a quasi standard interface for programming the flash and accessing and the hardware for diagnostics. For instance,linksys routers actually have a spot on the board to solder a header and you can make a cable that connects to the parralel port. Do a google search for "Hairy Dairy Maid Debrick" and you will find it. A similar thing is probobally possible with the Evo (Ive even seen them on Hard Drives and CD Rom drives) The problem is,its not entirely standardized,and it might not even be a connector or pads on the board. It might instead be a matter of knowing where you can connect the leads on the board to something that under the right circumstances BECOMES the JTAG connector. (For instance,a pin that controls something else might be a JTAG interface for the first few hundred milliseconds of start-up,or if a certain other pin of the chip is grounded when the power is applied. It might also be completely internal to the chip,and there be NO connectors on the board (it almost CERTAINLY has the capability,they need it during prototyping) and the chips might be programmed BEFORE they are soldered in. It might take replacing the rom chip to get it to go. There are lots of ifs
Chances are though,the factory has a special cable and a special software program that can reprogram the device. To replicate that might be relatively easy or could be next to impossible but requires a certain degree of knowledge about the hardware. What I suspect is,until someone who has the skills to make such a cable bricks their phone,they wont bother figuring out how to debrick one. In fact,when that person bricks their phone,they will probably take it back to sprint and say "I dont know what happens" In fact,even if its stuck looping in an obviously hacked boot loader he for some odd reason cant undo,hes probably going to send it back to sprint. I know someone who did exactly that to their brand new HP laptop. He found that 15kv from the flyback of an old B&W television applied to the memory slots took care of the looping and Best Buy gave him another one. As he put it "I dont know what happened,but it smells bad and wont boot up"
Click to expand...
Click to collapse
Wow. Thanks for the detailed answer. Too bad this isn't a standardized item. I hope eventually things progress enough where this isn't even a thought. Thanks again for the good response.
Sent from my PC36100

rafroehlich2 said:
Wow. Thanks for the detailed answer. Too bad this isn't a standardized item. I hope eventually things progress enough where this isn't even a thought. Thanks again for the good response.
Sent from my PC36100
Click to expand...
Click to collapse
Yea,it would be nice if it were. Its kinda sorta quasi standard,so it HAS been done in some cases where its necessary,but often there are easier ways around it. Personally, I have allways thought that its a pretty stupid thing to make a piece of equipment that can fail due to a bad flash. The people who designed many of the flash memory chips seemed to agree,and they added something called a "boot block" to many,but the way its implemented,when its implemented doesn't fully protect you from a bad flash. Its even worse now that everything is in ball grid array chips soldered down to the board.

Phone life after death. Breaking the Jtag taboo.

I had some research yesterday, yet I still can't find a proper answer to most of my questions about the following subject. Hoping some of the experts here can contribute some of their knowledge and hopefully I will edit this thread to a guide, or at least spare others the need for wondering around the web as I did.
Well, Few days ago I turned off my phone, and it wont turn on or response to any physical key combination, usb connection (Except for charging the battery) or even that famous Samsung jig (301KΩ Between pin 4 and 5 on the usb connection). It is not recognizable by any device while connected through usb interface. It is permabricked. The worst thing that can happen to a phone while the hardware is intact.
Although the name indicates otherwise, some things can be done in order to get the device working again.
It is a process in which the phone's main bored is exposed, than a special device (e.g riff box) is connected to certain areas on the pcb that were made that way for the initial configuration of the phone back in the factory. The pinout of the connection varies in each model, but the interface is the same and called "Jtag". Than, that device connects to a pc through usb interface.
So the first step would be to get that device and to connect it to both pc and phone's motherboard through a certain pinout that is mostly hard to get. You'll need a driver for that jtag flashing device and a compiled file which you would like to flash in to your phone. I don't know if that file is specific to each model or to the certain chip the phone is using (Can different models with the same chip be flashed the same way? Reply if you know and I'll edit it here).
By what I know, after flashing that file the phone will be accessible through usb interface for further flashing of the rom.
Alternatively, There are some companies that offer that kind of service. I couldn't find any who work with T989, and prices for that kind of service.
I would like to have as much information as possible and maybe eventually I'll be able to get my phone fixed. In that case I'll add some photos and document the process.

Michael.fri said:
I had some research yesterday, yet I still can't find a proper answer to most of my questions about the following subject. Hoping some of the experts here can contribute some of their knowledge and hopefully I will edit this thread to a guide, or at least spare others the need for wondering around the web as I did.
Well, Few days ago I turned off my phone, and it wont turn on or response to any physical key combination, usb connection (Except for charging the battery) or even that famous Samsung jig (301KΩ Between pin 4 and 5 on the usb connection). It is not recognizable by any device while connected through usb interface. It is permabricked. The worst thing that can happen to a phone while the hardware is intact.
Although the name indicates otherwise, some things can be done in order to get the device working again.
It is a process in which the phone's main bored is exposed, than a special device (e.g riff box) is connected to certain areas on the pcb that were made that way for the initial configuration of the phone back in the factory. The pinout of the connection varies in each model, but the interface is the same and called "Jtag". Than, that device connects to a pc through usb interface.
So the first step would be to get that device and to connect it to both pc and phone's motherboard through a certain pinout that is mostly hard to get. You'll need a driver for that jtag flashing device and a compiled file which you would like to flash in to your phone. I don't know if that file is specific to each model or to the certain chip the phone is using (Can different models with the same chip be flashed the same way? Reply if you know and I'll edit it here).
By what I know, after flashing that file the phone will be accessible through usb interface for further flashing of the rom.
Alternatively, There are some companies that offer that kind of service. I couldn't find any who work with T989, and prices for that kind of service.
I would like to have as much information as possible and maybe eventually I'll be able to get my phone fixed. In that case I'll add some photos and document the process.
Click to expand...
Click to collapse
1st off, it's "taboo" not tabu. Secondly there is already a pretty good amount of threads that have covered this in detail, I'm certain because I have posted in them. Lastly, please SEARCH the existing threads before creating a new one; the answers to all your questions are already there.

1. Thanks, Changed to "Taboo".
2. I searched, I really did. I went all over google with many key words and covered up this forum as well. All I got is some articles about the jtag protocol, which is good for knowledge but too general for the application I need, and some threads in which people writing that their phone is bricked and asks what to do about it. Not a single post is about how to fix that independently, and what does it require. If you could give me link to these threads you say that covers up the subject, I'll delete this thread at once.

Michael.fri said:
1. Thanks, Changed to "Taboo".
2. I searched, I really did. I went all over google with many key words and covered up this forum as well. All I got is some articles about the jtag protocol, which is good for knowledge but too general for the application I need, and some threads in which people writing that their phone is bricked and asks what to do about it. Not a single post is about how to fix that independently, and what does it require. If you could give me link to these threads you say that covers up the subject, I'll delete this thread at once.
Click to expand...
Click to collapse
don't pay attention to that guy he like to troll every where he goes. Try to google search for mobile tech or Adam Outler, and check if he get the Jtag service for our phone. If I'm not wrong the charge for the Vibrant was $50.00 plus shipping and handling. I hope you can fix your phone.
Sent from my SGH-T989 using xda premium

Do you know what caused the brick?
Sent from my SGH-T989 using xda premium

Searched, and yet no result. Sending the phone to the U.S is quite risky. I have no idea how they're intended to pack it before sending it back. I would rather doing this in Israel.
I saw on ebay several devices associated with Jtag. the price starts from 10$ for a simple usb dongle, through 30$ devices, which is the price of most of the jtag devices I found, to the 150$ riff box that is associated with phone unbricking.
By what I know Jtag is a simple serial protocol. I just need sort of "bridge" to translate the logic 1's and 0's with the right voltage level and certain clock speed to a usb interface or even RS232. How expensive can that be?
I also contacted several ebay sellers which offer a jtag repair service. they all answered this model is not supported.
I would go to Samsung labs in Israel and see what they can do to get it working.
I just thought to invest 20$, get that sort of device and to get it done by my own.
Another issue is the pinout. The pinoput of the Jtag connection is not shown in any website, so I have no way of knowing how to connect on this specific PCB.
Last thing I need is that new bootloader I can flash, and a software to flash it through. Where can I download it?
About the reason for bricking the phone, I have no Idea. As I said, last time I've installed new rom was more than a week prior to the incident. I've used some overclocking app mostly to underclock my phone, cause it drained the battery like hell before, even while it was running on stock and after changing the rom several times.
I also used some usb otg device which worked normally, but was not plugged to the device even few hours before it was bricked.

Hopefully we can figure out the cause of these permabricks so we can prevent it from happening to more people.
Sent from my SGH-T989 using xda premium

I gotta say, this is quite alarming. That the phone can just hard brick itself like this spontaneously.
I've had some scary experiences with the phone myself. Like a couple of random reboots that required the long power press for the phone to power back on. At least it always came back on.
I'm also from Israel myself so a similar scenario can bring me to the same situation as you.
Good luck with getting any kind of solution.
Sent from my SGH-T989 using xda premium

parusia said:
don't pay attention to that guy he like to troll every where he goes. Try to google search for mobile tech or Adam Outler, and check if he get the Jtag service for our phone. If I'm not wrong the charge for the Vibrant was $50.00 plus shipping and handling. I hope you can fix your phone.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Troll for advising to follow the posted rules of membership ? WOW

I just contacted Adam and still no jtag for this device .
Sent from my Galaxy Nexus using XDA App

did you look for a service manual?
- the manual may cover schematics for jtag device.

Been flashing phones since the Razr and never bricked a phone I couldn't repair myself. That is until I tried to flash my GSII back to stock through odin. Sent it to Samsung and they had to replace motherboard. Now I'm a little nervous about using odin.

reocej said:
Been flashing phones since the Razr and never bricked a phone I couldn't repair myself. That is until I tried to flash my GSII back to stock through odin. Sent it to Samsung and they had to replace motherboard. Now I'm a little nervous about using odin.
Click to expand...
Click to collapse
I recommend splurging on the $2-3 for a jig, I have had moments where I thought I was SOL & the jig saved my arse.

Michael.fri said:
Last thing I need is that new bootloader I can flash, and a software to flash it through. Where can I download it?
Click to expand...
Click to collapse
Did you solve your problem?

I was looking at using QPST
QPST is a program often frowned upon here at xda. It is commonly used to flash phones, and has little to do with android coding. The software is made for Qualcomm (or by them) and this device has a chip from them in it. This has tools for building and installing bootloaders and partition tables. Our device after a hard brick (and still serviceable by JTAGing) has a com port open still and if you load the driver in windows you will see a port number as others here on XDA have said. The driver allows ODIN to see the device but not connect. QPST does connect, but I have not attempted to flash anything to it since I have not built any files to load. I'm kind of stuck creating the needed xml that makes the partition table and headers and file that are to be loaded to partitions. This is really a softbrick, in my opion, but nobody has the knowledge for this level of building and coding, with this tool, here at XDA. If somebody does, it may make those selling JTAG services mad, but that would mean we could fix our phones on our own. On my own, I'm a few weeks away from this solution, with some help from people here that know how to write xml for partition tables and can help me locate files for a build, I can generate the files, test them, make a write up and post the solution in just a few days.
By the way, this is a multi-device solution in the long run. We get one fixed and we can start on the others with this same issue, where the only life left in the device is the Qualcomm download mode driver showing in windows device manager.

Michael.fri said:
I had some research yesterday, yet I still can't find a proper answer to most of my questions about the following subject. Hoping some of the experts here can contribute some of their knowledge and hopefully I will edit this thread to a guide, or at least spare others the need for wondering around the web as I did.
Well, Few days ago I turned off my phone, and it wont turn on or response to any physical key combination, usb connection (Except for charging the battery) or even that famous Samsung jig (301KΩ Between pin 4 and 5 on the usb connection). It is not recognizable by any device while connected through usb interface. It is permabricked. The worst thing that can happen to a phone while the hardware is intact.
Although the name indicates otherwise, some things can be done in order to get the device working again.
It is a process in which the phone's main bored is exposed, than a special device (e.g riff box) is connected to certain areas on the pcb that were made that way for the initial configuration of the phone back in the factory. The pinout of the connection varies in each model, but the interface is the same and called "Jtag". Than, that device connects to a pc through usb interface.
So the first step would be to get that device and to connect it to both pc and phone's motherboard through a certain pinout that is mostly hard to get. You'll need a driver for that jtag flashing device and a compiled file which you would like to flash in to your phone. I don't know if that file is specific to each model or to the certain chip the phone is using (Can different models with the same chip be flashed the same way? Reply if you know and I'll edit it here).
By what I know, after flashing that file the phone will be accessible through usb interface for further flashing of the rom.
Alternatively, There are some companies that offer that kind of service. I couldn't find any who work with T989, and prices for that kind of service.
I would like to have as much information as possible and maybe eventually I'll be able to get my phone fixed. In that case I'll add some photos and document the process.
Click to expand...
Click to collapse
Mobile Tech offers the JTag service. There is even a discount for XDA members. They offer the service for all variants of the S2
Here you go!
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-jtag-brick-repair/

daxxone said:
QPST is a program often frowned upon here at xda. It is commonly used to flash phones, and has little to do with android coding. The software is made for Qualcomm (or by them) and this device has a chip from them in it.*snip* On my own, I'm a few weeks away from this solution, with some help from people here that know how to write xml for partition tables and can help me locate files for a build, I can generate the files, test them, make a write up and post the solution in just a few days..
Click to expand...
Click to collapse
Any word on a fix using QPST?