Related
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.
As for me it is not. I'm currently using Oli/Nex 1.93 unsigned.
Referring to the repair service i have send my diamond in, because of a broken USB port, it is a "illegal" piece of software and warranty repair has been rejected. They'd like to charge € 300.- for mainboard replacement.
Well, i have never heard before of a broken USB Port because of Hard-SPL and i even don't believe that Hard-SPL is capable of doing this.
My USB Port stopped working after plugging my diamond to my PC (long time after i had installed Hard-SPL). Charging still works but no way to get it recognized by ActiveSync or as harddisk.
My Assumption is the repair service is talking crap - they probably didn't even check the hardware and pointed their fingers at Hard-SPL after discovering it.
I'd like some comment, from the devs maybe, that Hard-SPL is harmless and not even capable of bricking the USB Port.
thanks,
nervdoc
it is done what is done, but for other people please restore the original spl before sending it to the service as a matter of fact restore the orig. rom also.
as for your question, what rom exactly did you have, cause some people expirience the async problem but normaly it gets solved by the rom shef.
No...that hardware malfunction has not been caused by Hard-SPL.
But they are talking about charging you for repair because they just had a look at the bootloader screen, noticed that you have "void-ed" the warranty by modifying the SPL...and this has been mentioned as a caveat so many times in the relevant threads, and if you could have cared to read properly before installing it, you would have known how to revert back to, or load the stock SPL(and stock Radio and ROM, if you flashed a different one) back before sending your device for warranty. This way the device would have been in stock conditions and they would have repaired it for free.
Hard Luck buddy, but that's the way it is...sad but true.
nervdoc said:
As for me it is not. I'm currently using Oli/Nex 1.93 unsigned.
Referring to the repair service i have send my diamond in, because of a broken USB port, it is a "illegal" piece of software and warranty repair has been rejected. They'd like to charge € 300.- for mainboard replacement.
Well, i have never heard before of a broken USB Port because of Hard-SPL and i even don't believe that Hard-SPL is capable of doing this.
My USB Port stopped working after plugging my diamond to my PC (long time after i had installed Hard-SPL). Charging still works but no way to get it recognized by ActiveSync or as harddisk.
My Assumption is the repair service is talking crap - they probably didn't even check the hardware and pointed their fingers at Hard-SPL after discovering it.
I'd like some comment, from the devs maybe, that Hard-SPL is harmless and not even capable of bricking the USB Port.
thanks,
nervdoc
Click to expand...
Click to collapse
a known problem on HTC devices for the USB board to blow (leading to lack of being able to sync, but still charge) is charging in the car.
if the Diamond is plugged into a charger while the car is started, a hight current can be passed to the diamond resulting in the USB or Mainboard blowing.
I was running my providers original software but unfortunately i was not able to return to original SPL without a working usb port.
Is it possible to revert back to original SPL without working USB port? Didn't find anything besides flashing from internal storage - whitch didn't work for hard-SPL.
If i had really voided the terms of guarantee is questionable as there is no point which says "don't upload unofficial software"
warranty is excluded if (translated from german):
Damage, in particular dark blotch, lines or cracks on the display.
Damage due to fall, violent pressure etc.
Damage due to water.
Damage due to inappropriate handling.
Damage due to not authorized accessories.
Point 4 could apply though O2 (my provider) offers also firmware/software upgrades.
And as stated before (Hard-)SPL is not able to cause this damage.
Nevertheless i'll try to object to their refusal.
regards,
nervdoc
nervdoc said:
I was running my providers original software but unfortunately i was not able to return to original SPL without a working usb port.
Is it possible to revert back to original SPL without working USB port? Didn't find anything besides flashing from internal storage - whitch didn't work for hard-SPL.
If i had really voided the terms of guarantee is questionable as there is no point which says "don't upload unofficial software"
warranty is excluded if (translated from german):
Damage, in particular dark blotch, lines or cracks on the display.
Damage due to fall, violent pressure etc.
Damage due to water.
Damage due to inappropriate handling.
Damage due to not authorized accessories.
Point 4 could apply though O2 (my provider) offers also firmware/software upgrades.
And as stated before (Hard-)SPL is not able to cause this damage.
Nevertheless i'll try to object to their refusal.
regards,
nervdoc
Click to expand...
Click to collapse
Hi nervdoc,
let them answer, where exactly it is stated (in the german warranty agreement), that the warranty is void after flashing certain software products.
If they cannot point this out, take legal action.
bye,
Thilo
nervdoc said:
I was running my providers original software but unfortunately i was not able to return to original SPL without a working usb port.
Is it possible to revert back to original SPL without working USB port? Didn't find anything besides flashing from internal storage - whitch didn't work for hard-SPL.
If i had really voided the terms of guarantee is questionable as there is no point which says "don't upload unofficial software"
warranty is excluded if (translated from german):
Damage, in particular dark blotch, lines or cracks on the display.
Damage due to fall, violent pressure etc.
Damage due to water.
Damage due to inappropriate handling.
Damage due to not authorized accessories.
Point 4 could apply though O2 (my provider) offers also firmware/software upgrades.
And as stated before (Hard-)SPL is not able to cause this damage.
Nevertheless i'll try to object to their refusal.
regards,
nervdoc
Click to expand...
Click to collapse
Maybe ActiveSync via bluetooth? Then you don't need your usb.
pietrucci said:
Maybe ActiveSync via bluetooth? Then you don't need your usb.
Click to expand...
Click to collapse
Bluetooth doesnt work while in Bootloader mode...
not possible, sorry.
I have send them a fax pointing out that regarding the terms of warranty there was no breach at this point.
Bluetooth is an option i already have considered and also used for activsync (...god is that slow)
nervdoc said:
I have send them a fax pointing out that regarding the terms of warranty there was no breach at this point.
Bluetooth is an option i already have considered and also used for activsync (...god is that slow)
Click to expand...
Click to collapse
u managed to get Acticesync to work over bluetooth!!
that has got to be a first.
i have tried soooooo many times with different phones lol
mugglesquop said:
u managed to get Acticesync to work over bluetooth!!
that has got to be a first.
i have tried soooooo many times with different phones lol
Click to expand...
Click to collapse
Was kind of a fight but a least I have succeeded. You can even start customruu.exe to flash.
Works flawlessly until entering the bootloader.
nervdoc said:
Was kind of a fight but a least I have succeeded. You can even start customruu.exe to flash.
Works flawlessly until entering the bootloader.
Click to expand...
Click to collapse
lol, i bet.
yeh, that is the problem, needs to have a USB connection, as a bluetooth connection is not supported by the BIOS (or whatever the bootloader thingy is).
Of course bluetooth is supported by SPL.
You can even route the bluetooth connection once you're in the bootloader.
But for that you need to change the port settings (available via console only).
Anyway, yes, Hard-SPL could have bricked the usb port.
Why ?
The usb init itself might have changed between the mfg version (old version) and newer spl versions. So, newer hardware leads to newer voltage settings / calibration.
But honestly ... I doubt that the usb port was bricked by just hard-spl.
In fact, most usb ports are bricked by sticking the usb cable first into the pc and then into the phone ... either due to electrostatic issues or due to overvoltage (unstable usb connection).
So imho a bricked usb port is 99% an hardware issue and no software issue if the software was intended for the phone.
Cya,
Viper BJK
viperbjk said:
Of course bluetooth is supported by SPL.
You can even route the bluetooth connection once you're in the bootloader.
But for that you need to change the port settings (available via console only).
Click to expand...
Click to collapse
ah right, cheers for that
*hides in corner*
viperbjk said:
But honestly ... I doubt that the usb port was bricked by just hard-spl.
In fact, most usb ports are bricked by sticking the usb cable first into the pc and then into the phone ... either due to electrostatic issues or due to overvoltage (unstable usb connection).
So imho a bricked usb port is 99% an hardware issue and no software issue if the software was intended for the phone.
Cya,
Viper BJK
Click to expand...
Click to collapse
Exactly this happened. Phone was on and after connecting it to pc the screen went dark.
Had to remove battery and put it back in to turn my diamond on again.
Another thing is to make this clear to O2's repair service
Hi
try change the spl without USB like the rom or radio file transfer though bluetooth file to internal storage change name for DIAMIMG and reset phone keep pressing volup button and back button then when phone recognized file press power button to start updating
nervdoc said:
As for me it is not. I'm currently using Oli/Nex 1.93 unsigned.
Referring to the repair service i have send my diamond in, because of a broken USB port, it is a "illegal" piece of software and warranty repair has been rejected. They'd like to charge € 300.- for mainboard replacement.
Well, i have never heard before of a broken USB Port because of Hard-SPL and i even don't believe that Hard-SPL is capable of doing this.
My USB Port stopped working after plugging my diamond to my PC (long time after i had installed Hard-SPL). Charging still works but no way to get it recognized by ActiveSync or as harddisk.
My Assumption is the repair service is talking crap - they probably didn't even check the hardware and pointed their fingers at Hard-SPL after discovering it.
I'd like some comment, from the devs maybe, that Hard-SPL is harmless and not even capable of bricking the USB Port.
thanks,
nervdoc
Click to expand...
Click to collapse
they've been told to do this, HTC have sent a document round to RMAs about it.
I would contact them back and tell them that they're talking bull**** and they can either prove that the SPL is causing the hardware defect (in line with EU law requiring the manufacturer to prove your modification breaks the device) or shut up and repair it.
lesiohormon said:
Hi
try change the spl without USB like the rom or radio file transfer though bluetooth file to internal storage change name for DIAMIMG and reset phone keep pressing volup button and back button then when phone recognized file press power button to start updating
Click to expand...
Click to collapse
Already tried this. As far as i know HardSPL is write protected.
At least it didn't work. The update process went well but checking bootloader afterwards it still showed olinex 1.93.
@olipro
Is it possible to restore stock SPL from Internal Storage though HardSPL is installed?
If yes, are there any special tricks to perform. As stated above i already tried without success.
Unfortunately I don't have a good idea for you. But, I had a motherboard on my PC which simply caramelized anything I conected to the front USB console: A Sony camera, A bluetooth adapter, a memory stick, and ALMOST an ipod of a friend which costs 300 euros...Fortunately we conected all the other things before and we realized the problem with the motherboard.
So, it might be something simular in your case, maybe...Check with something cheap, with an old memory stick? Then you will know: don't connect anything...
Just an idea to prevent further accidents....
For 300€... maybe better to wait, save another 300 and buy a blackstone?
Or...save and buy a new diamond? For 300 you can buy on e-bay easily... a bit risky...
I have the unassembling manual of the HTC, I downloaded it from somewhere on this forum, have a look. if you want I can send it to you by email. Changing the motherboard looks easy! The only thing you can do is to see which bad things are the best...
Wish you find the best solution!
Plese keep us informed.
As for the repair service - they refused. Now they're talking about "mechanical damage to the motherboard" which is not covered by warranty.
They also offered me an error report - for some extra charge. Really consumer-friendly.
Now I'll try my luck with the dealer where i bought it.
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.
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?
Hi, all...
Quick question: did somebody in this forum ever had problems with USB? Mine seems to work only for charging. 'Till the last week, it worked as MSC, with no major problems, then it became faulty, disconnecting and connecting.
Now, to have data connection, is necessary to put pressure at the male connector and hold it this way. I think that it'll require a new PCB, as it doesn't look like software failure. I've googled up and there were other people having trouble with Xperia, but not M, specifically.
So, must I bring it to the assistence?
There's only one way to find out where the source of the problem is: to reflash the ROM.
The USB connector might have got damaged somehow. You can try it with any other device or maybe another xperia m to check for software fault or damage of the USB connector. Try to keep your device at a level below the port for USB in your computer.
elmkzgirxp said:
There's only one way to find out where the source of the problem is: to reflash the ROM.
Click to expand...
Click to collapse
Tried with CM 4.4 (FXP one, that's, by the way, terrifc). But it presented the same failure, then I reverted to the stock 4.3's CWM backup, because I didn't want to reinstall every app. Well, at least I,'m now sure that's a hardware failure.
cooldudeachyut said:
The USB connector might have got damaged somehow. You can try it with any other device or maybe another xperia m to check for software fault or damage of the USB connector. Try to keep your device at a level below the port for USB in your computer.
Click to expand...
Click to collapse
Tried everything (or near everything). It charges, however. There are a little failure, but it should work if the phone is left quiet or not shaken while using it connected to the outlet.
So, for now, I'm going to transfer things using Samba or detached SD (the last being the fastest). Later I'll send it for repair... Shame it perhaps won't work with OTG (a feature I've been searching for, when I bought XM), but, when having money, I'm going to get it fixed.
Thanks for the replies, anyway.
prppedro said:
Tried with CM 4.4 (FXP one, that's, by the way, terrifc). But it presented the same failure, then I reverted to the stock 4.3's CWM backup, because I didn't want to reinstall every app. Well, at least I,'m now sure that's a hardware failure.
Tried everything (or near everything). It charges, however. There are a little failure, but it should work if the phone is left quiet or not shaken while using it connected to the outlet.
So, for now, I'm going to transfer things using Samba or detached SD (the last being the fastest). Later I'll send it for repair... Shame it perhaps won't work with OTG (a feature I've been searching for, when I bought XM), but, when having money, I'm going to get it fixed.
Thanks for the replies, anyway.
Click to expand...
Click to collapse
Most problems don't get fixed just by restoring /system. You have to flash the whole
ROM, if it failed with system. If you're worried so much about your data, then just backup /data then restore it afterwards...
I also have this problem.i just elevates the charger cable and its charging but its not working if its not elevated.tried different charger but the problem still persist.so i conclude that its the port in the phone that s malfunctioning.
Sent from my C1905 using XDA Premium 4 mobile app
even my usb cable didn't work. I tried connecting other mobiles too but dint work. And i realized its not problem with the os, but the cable itself was fault!