Develop Bugs

Wave S8500/S8530 Development Platform Mod AKA UnBrickable Mod

This modification will go like this:
http://forum.xda-developers.com/showthread.php?t=1206216
note: this modification seems to look slighty different on S8500 than S8530 (slighty different board layout) - please check this post - http://forum.xda-developers.com/showthread.php?p=17724584#post17724584 (still needs testing)
This can be applied to a bricked phone and unbrick it without JTAG.
After that, unbricking your Wave will be almost as easy like this is (need kinda different soft, as following movie been made with SGS series phone):
See here for more info about unbricking Captivate:
http://forum.xda-developers.com/showthread.php?t=1242466
(Unbricking Wave tools are on its way)
I haven't tested it by myself but it will work. I did teardown of mine S8530 damaged mainboard.
Introduction
I'm not kidding when I say UnBrickable. Modifying the OM pins means you
can boot from USB, UART or MMC. This makes the phone quite UNBRICKABLE.
There is nothing you can do software wise to prevent the device from
booting into this mode. We are communicating with the unrewritable,
efused IROM on the processor. It's the thing that makes the system on a
chip into a "system on a chip".I am here now to tell you how to turn
your Samsung Wave into a KIT-S5PC110 development board. The
KIT-S5PC110 development board is the platform used to develop our
phones. There are some differences between this mod and the official
development platform. The S5PC110 has a removable internal SDCard and
no touchscreen.
Why would you want to do this? When you plug in the battery and
connect it to the computer in "off" mode, it will become an S5PC110
board awaiting download of a program to run. This occurs long before
anything like software or firmware enters the processor. This is the
IROM of the device awaiting commands or a power on signal.
Because it is accepting a memory flash, anything may be put onto the
device to perform a boot sequence..... Apple iOS (iPhone4 has the same
processor) WP7 (mango supports this processor).
This will be a replacement for JTAG once we are able to make some
firmware. How could it possibly be better then JTAG? Let's count the
ways....
1. The only part required is a wire.
2. No shipping time.
3. No cost for a box to interface the computer.
4. Permanent.
5. Can be done as a preventive measure.
6. Gives the ability to test new Bootloaders temporarily.
7. Allows development of the entire system.
8. Removes worry about flashing and acts as a backup.
After performing this mod:
Remove the battery, replace the battery, your phone will connect to the
computer via USB and await commands. Otherwise it will pretty much act
like a Droid Charge. See the Special Instructions section.
Modification
You will need:
1. Get someone who knows what they're doing with a soldering
iron. If they don't know what flux is, then they don't know what
they're doing. You can speak to AdamOutler or
Connexion2005(aka MobileTechVideos.com). I don't know who from Europe region is able to perform this mod, I still need some more soldering practice, probably in month or two I will be also able to perform this.
2. soldering iron - make sure it's sharp, if it's not sharp, then
sharpen it, flux it and retin it.
3. flux
4. solder
5. tweezers
6. A relay (possibly- for the wire within to use as a bridge)
Performing the modification:
1. tear apart your phone... Make sure to take out your SIM and external
SDCard before you do this.
1A. Remove the mainboard (you can see on the movie how to do it)
S8500 disassembly movie (S8530 looks basically the same):
Mainboard picture:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Closer picture:
xOM resistors mapping:
2. Perform the mod by removing the xOM5 resistor and connecting its active (CPU) side to the active side of xOM0 or xOM3 resistor (so it become pull-up instead of pull-down).
3. Reassemble the phone.
Special Instructions
This may change battery charging sequency, or even disable it when the phone is turned off (it may be needed to turn on the phone first) <-- needs some tests
To turn on the device, and operate in normal mode, you must hold the
power button for 5 seconds.
3 button Download mode works as usual, however you must not have the
S5PC110 drivers installed on the computer. 301Kohm Factory Mode JIGs work as well, but you must press power to bypass the S5PC110 iROM dload mode.
Conclusion
Congratulations. You now have a device which works like a KIT-S5PC110
with an OM Value of 29. Now get to developing some serious custom
software. See here for setting up the UART output
http://forum.xda-developers.com/showthread.php?t=1235219
Reading material
Creating your own Samsung Bootloaders:
http://forum.xda-developers.com/showthread.php?t=1233273
KIT-S5PC110 manual: http://www.mediafire.com/?94krzvvxksvmuxh
how to use DNW: http://tinyurl.com/dnw-how-to
Flash using openOCD and DNW:
http://www.arm9board.net/wiki/index.php?title=Flash_using_OpenOCD_and_DNW
another DNW example:
http://www.boardset.com/products/mv6410.php
ODroid dev center:
http://dev.odroid.com/projects/uboot/wiki/#s-7.2
Drivers and utilities
This will be an ever expanding list
Windows Drivers
http://forum.xda-developers.com/attachment.php?attachmentid=678937&d=1312590673
Windows Download Tool DNW:
http://forum.xda-developers.com/attachment.php?attachmentid=678938&d=1312590673
Windows Command Line Download Tool:
http://forum.xda-developers.com/showpost.php?p=17202523&postcount=27
Linux DNW Utility:
http://dev.odroid.com/projects/uboot/wiki/#s-7.2
Firmware
One-Click Resurrector (made for SGS series):
http://forum.xda-developers.com/attachment.php?attachmentid=705515&d=1314762609
Bootloader Hello World by Rebellos
http://forum.xda-developers.com/attachment.php?attachmentid=698077&d=1314105521
Please note that we are not yet able to rebuild Wave's NV_Data, so if you damage your IMEI (by trying to flash SGS stuff before dumping your oneNAND through Badadroid) you have to deal with it on your own.
Thanks to Adam Outler.
Please message me or simply make post here if you perform this mod and need any additional info.
Already done MODs:
Captivate (the first one): http://forum.xda-developers.com/showthread.php?t=1206216
Droid Charge: http://forum.xda-developers.com/showthread.php?t=1245391

It is important to note that this modification has never been performed on a S8500 before. Rebellos is very competent and will work out the details of the firmware portion. His HIBL allows insecure code to be loaded to the device and it is extremely likely that this modification will lead to easy development of alternate firmwares for your device. This mod enables a special download mode which will allow you to experiment freely as long as you have a backup of your EFS and critical data.
Once Rebellos is able to get the firmware operational, and he will likely work with you directly and remotely if you're willing, recovery of the S8500 will be this easy:
We are fully confident in this modification and if you have a bricked S85**, please send a PM to Rebellos. He will develop a firmware rather quickly to resurrect the device and then everyone will have an UnBrickable Wave!

Bonus - have you been ever wondering how does PoP BGAs or S8530 mainboard without CPU does look?
http://i53.tinypic.com/xlf8rt.jpg
From the left to right:
- oneNAND+oneDRAM+DRAM package
- Hummingbird CPU
- S8530 Mainboard
If you want I can take better macro photos of these. Also if someone want to try reballing of memory package (CPU has got burned core) I can donate it to him. However it has got like 0.1mmx0.1mm size balls. Maybe if I ever get rich and smart and I get bionic hand, I'll make a board under this package.

So Adam Did you try this with the Wave S8500/S8530 ??? or you still need a Wave for donation ???
I am very interested in this but i won't do it because i heard about some stability problems after removing the resistor
Also i have a question...Can i put the resistor back after unbricking my device or it will be totally fried??
Best Regards

You can put the resistor back if you manage to. SMD elements are usually high-temp resistable.
There is no stability problems if you connect it to some other pullup or pulldown resistor.
CPU will become unstable only if you remove resistor and leave xOM5 line unconnected to anything as it'll take electrostatic charges and induce voltage from other elements and electromagnetic field causing noise inside of CPU when not grounded or HIGHed.

you mean it will act like a really tiny capacitor (i am electrical engineering student)
Do you think that mod will reach the mobile repairing shops?
i mean if you could write a good bootloader that will dual boot android and bada (yes i think you are genius enough) then this can go to mobile shops to get it done by experts hands that will be awsome(i've never opened up my Wave and don't have much experience to do this)
You will get donations for this for sure
Best Regards

mylove90 said:
So Adam Did you try this with the Wave S8500/S8530 ??? or you still need a Wave for donation ???
I am very interested in this but i won't do it because i heard about some stability problems after removing the resistor
Also i have a question...Can i put the resistor back after unbricking my device or it will be totally fried??
Best Regards
Click to expand...
Click to collapse
Rebellos performed the destructive inspection on his own device. The work is complete, you may modify your device according to the specs above. This will allow you to boot from USB.
You may be able to put it back, but it's not likely, and you will never need to.
MobileTechVideos.com is already offering this service for Captivates as the mod is finished and we have it working fully on Linux platform. All thats left for Wave is for Rebellos to work with someone who has a working Wave (maybe 1 hour via google talk). Modify your device and PM Rebellos.
If your device is broke this will resurrect it. If your device is not broken, this will allow you to flash Android ROMs without fear of permanent damage.
I think Rebellos already has worked out the changes needed to the bootloaders to run Android on Bada with the BadaDroid project.

mylove90 said:
you mean it will act like a really tiny capacitor (i am electrical engineering student)
Click to expand...
Click to collapse
No. Rather like tiny not-grounded antenna or induction coil, which transforms all magnetic field jitters into small, noisy voltage current, which are very annyoing for CPU.
(thats why in electronic chips all pins should be connected to something which can provide stable LOW or HIGH state, if they doesn't support internal PUD mechanism)
mylove90 said:
Do you think that mod will reach the mobile repairing shops?
Click to expand...
Click to collapse
That would be awesome. Writing dual-boot bootloader isn't a huge deal, but needs some work and designing, for example problem is that oneNAND (the fastest flash memory we can use) size is only 512MB, so it can hold only like 150% of 1 OS files. That could be solved by moviNAND repartitioning and modifying bada kernel properly to not wipe Android partitions.
AdamOutler said:
I think Rebellos already has worked out the changes needed to the bootloaders to run Android on Bada with the BadaDroid project.
Click to expand...
Click to collapse
Yup, got these files ready. But I don't want to release something completely untested.
//edit:
Here you have links to modified S8530 and S8500 BL3 images.
Original, decrypted and extracted and ones can be used aswell, but needs dload-mode key combination to be hold. The modified ones does enter DLoad mode immediately.
Entrypoint for both is 0x42480000
http://hummingbird-hibl.googlecode.com/svn/trunk/HummingBirdInterceptorBootloader/S8500_BL3.bin
http://hummingbird-hibl.googlecode.com/svn/trunk/HummingBirdInterceptorBootloader/S8530_BL3.bin

I'm not seeing any action here. If you bricked your device, this will resurrect it.
Rebellos, you want me to start working on the Ultimate One-click resurrector? I don't feel motivated since Boone has put your work of proper pin identification to work... maybe the Bada guys don't DIY, or they just rather pay for JTAG?
Using this mod you can get Android on your device. You can load other device's firmware. Its very powerful and allows you to revert all changes.

AdamOutler said:
I'm not seeing any action here. If you bricked your device, this will resurrect it.
Rebellos, you want me to start working on the Ultimate One-click resurrector? I don't feel motivated since Boone has put your work of proper pin identification to work... maybe the Bada guys don't DIY, or they just rather pay for JTAG?
Using this mod you can get Android on your device. You can load other device's firmware. Its very powerful and allows you to revert all changes.
Click to expand...
Click to collapse
Maybe it's just because Wave users groups is much smaller than Cappy, also it isn't Android device, so people aren't flashing it so often as Cappy. Or they are just scared the crap out of DIY. ;d

it is not like that
Wave is not easily bricked (thank Samsung for that)
Until now i saw people with out knowledge who bricked it
Rebellos , you know bootloader is flashed in nearly 2 seconds and the phone will be bricked only if you did something wrong in these 2 seconds
i promise if my Wave bricked i'll try that method but where is the software stuff ?!
Please complete what you started Adam , Rebellos
Best Regards

mylove90 said:
it is not like that
Wave is not easily bricked (thank Samsung for that)
Until now i saw people with out knowledge who bricked it
Rebellos , you know bootloader is flashed in nearly 2 seconds and the phone will be bricked only if you did something wrong in these 2 seconds
i promise if my Wave bricked i'll try that method but where is the software stuff ?!
Please complete what you started Adam , Rebellos
Best Regards
Click to expand...
Click to collapse
Under Linux-- The HIBL gets loaded with this command:
Code:
sudo smdk-usbdl -f ./HIBL.bin -a D0020000
the SBL gets loaded very similarly
Code:
sudo smdk-usbdl -f ./S8500_BL3.bin -a 42480000
You should boot at this point. The HIBL is standard, the BL3 is provided in post 8 http://forum.xda-developers.com/showpost.php?p=17311448&postcount=8

Hi, first of all, sorry for my bad english, i'm spanish.
I bricked my wave more than one month ago. I have disassembled the phone but the xOMS mapping isn't the same. I have tried to modify the xoms but no results. Here are one photo of the xoms mapping, if you know who is the mod than i must to do, i'll try to do.
Here are the photo: h**p://i51.tinypic.com/wk1x52.jpg
This is my first post, i cant post links, change ** for tt.

jomadeto said:
Hi, first of all, sorry for my bad english, i'm spanish.
I bricked my wave more than one month ago. I have disassembled the phone but the xOMS mapping isn't the same. I have tried to modify the xoms but no results. Here are one photo of the xoms mapping, if you know who is the mod than i must to do, i'll try to do.
Here are the photo: h**p://i51.tinypic.com/wk1x52.jpg
This is my first post, i cant post links, change ** for tt.
Click to expand...
Click to collapse
Sorry. I assumed that S8500 board is the same, because schema in service manual is the same. However, it seems that there are differences.
Also see your mistake.
You connected some pulled up line straight to GND, you just made some resistor (I haven't traced it, it doesn't seem to be xOM, if order is the same) pull-down.
I'm sure the upper-left row of 3 are pull-ups, the bottom-right row of 3 are pull-downs. So resistors order should be the same.
All X resistors are pull-ups, with VCC on the upper side.
VCC line is marked purple
part of GND is marked by red spray - you can see it is big baseline, going through whole board.
second and third X resistors counting from the left should be xOM0 and xOM3.
1, 5, 2, 4 correspond to the xOM lines, they have CPU and GND sides arranged the same as on my picture from S8530 - 1,5,2 has GND on the downside, 4 has got GND on the upside.
The easiest way is connecting some VCC side of any X resistor with CPU side of xOM5 resistor, IF xOM5 resistor is 100kOhm or higher (should be around 100kOhm). If it is not - you should unsolder xOM5 resistor.
You can also connect CPU side of any X resistor with CPU side of any xOM5 resistor (theoretically the safest way, however mentioned above - short circuiting VCC with GND through 100kOhm resistor - is used on Samsung's dev board) IF you can find X resistor with resistance few times smaller than xOM5.
I'm sure this will work if done properly.
Remember to remove the soldering you've done already. Also remember to not leave xOM5 line not-connected to GND nor VCC - this will cause CPU to hang often.
Your board:
My board:
Can you see similiarities? I hope so.
After that just try ModeDetect by AdamOutler http://forum.xda-developers.com/showthread.php?t=1257434
And you should see UnBrickable Debug.

Thanks for the info Rebellos, later i'll try and post the results.

I can't unbrick my phone, after disassemble the phone and mod another time, obtain the same result, no answer on the phone and can't find the device in linux. Probably the reason is that the mod that i have done are incorrect (i haven't the tools necesary). For more info, i used Ubuntu 11.04 under virtualbox and under livecd. Thanks for all, and sorry but my experience can't help you in the development of this tool.

jomadeto said:
I can't unbrick my phone, after disassemble the phone and mod another time, obtain the same result, no answer on the phone and can't find the device in linux. Probably the reason is that the mod that i have done are incorrect (i haven't the tools necesary). For more info, i used Ubuntu 11.04 under virtualbox and under livecd. Thanks for all, and sorry but my experience can't help you in the development of this tool.
Click to expand...
Click to collapse
If you simply remove the resistor, about 1/2 of the time it should enumerate properly with the battery removed from the device. Once you have unbricked, jumper the xOM5 to something (high or low) so that it's not free floating.

hmmm Port Android easier, i see, but i am always asking myself why putting so much energy in a device that is after 2 years surely gone from market? (Only a question)
The energy could be put in other directions but everyone has his special hobby...
Seeying this android port will be maybe finished when everyone gets new device, for personal it has no sense to put the free time in such projects.
I know what i am talking about, i developed slyfer 3 months, hacked their server got for 9 months all firmwares, but what i have now from this? Nothing, i am very sad that i put so much time in such a project with no future, maybe you guys understand what i mean. So much skills can be on other site usefuller.
@Rebellos, why you dont try a "jailbrake" like for bada? You have the skills for that, but it seems that all of your energy will go in the bootloader for android, so around more than 50% (cause a lot arent on forums) will not have benefits from it. But anyway its your work and decision. And as we all know a not possible for bada doesnt exists.
Everything is possible.
But think about it the life is short, maybe things that helps all would make you also happy as me, but if you already know that your work will be in nearly a year for nothing it would be better to search another thing to kill time. Slyfer now is a dead program with no sense, it only shows me that i made it some day but uselesser it cannot be like this:
http://www.youtube.com/watch?v=UkgoSOSGrx4
Only my thinking.

You have the skills for that, but it seems that all of your energy will go in the bootloader for ...
Click to expand...
Click to collapse
Why not improve Reversing skills...
Bootloader knowledge is mandatory for deeper research/develop of Hardware or Software solutions...
Not everyone need it or understand it.
Anyway.
Its free decision.
@ larioteo
You are interested in Software ...
Others are interested in Hardware... like me...
Rebellos for instance like to learn more about Hardware + Software.
@Rebellos, why you dont try a "jailbrake" like for bada?
Click to expand...
Click to collapse
You know the answer...
Compression Algo of apps_compressed.bin (same for RC1 and CSC Languages... aka QMD compressed stuff) is not complete hacked...
Bootloader contains Algo for QMD...
Best Regards

Jomadeto, sorry for that it didn't worked
Larioteo, that movie is awesome. Thank you.
Excuse me little offtopic, but... maybe someone can PM me this
What exactly is jailbreak?
According to first phrase of this definition:
http://en.wikipedia.org/wiki/IOS_jailbreaking
We do already have jailbreak. Through modified FOTA we can force BL to load any ARM binary, any modified bada apps and so on. Just gimme practic target and I can try to achieve it someway. (I hope I'll have dev board soon )
But, beggining studies in 3 days, so ain't sure how much time I'll have for various hobby R&D.

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?

Roll back from the 60% latest firmware

Has anybody successfully been able to flash older firmware than today's 60%Green roll out?
I'm unaffected and have the green battery but would really like to know if it's still possible with ODIN, or if Samsung have made it more difficult somehow.

Just tried to flash the original firmware in Odin and it failed ...
I am also interested by a solution !

alltaken123 said:
Has anybody successfully been able to flash older firmware than today's 60%Green roll out?
I'm unaffected and have the green battery but would really like to know if it's still possible with ODIN, or if Samsung have made it more difficult somehow.
Click to expand...
Click to collapse
Out of sheer curiosity, why would anyone not want to return the phone? If you received the update, presumably your phone was on the potentially compromised list. How do you make the determination that it's unaffected?

@tiroger
Every device will eventually be updated, mine is a 2nd batch device (replacement) so it was unaffected (Black square on box), hence the green battery. I agree people should be returning these devices, however, like yourself i'm curious and wondered if a firmware downgrade was still possible after this update.
I am concerned for grey market devices that have been purchased from abroad, Samsung are not replacing these unless back in the native device region, a little unfair IMO.

I denied the update by quickly restarting my phone when the countdown appeared and now im having mysterious battery drain issues =/ but ill exchange my phone this weak anyway

alltaken123 said:
@tiroger
Every device will eventually be updated, mine is a 2nd batch device (replacement) so it was unaffected (Black square on box), hence the green battery. I agree people should be returning these devices, however, like yourself i'm curious and wondered if a firmware downgrade was still possible after this update.
I am concerned for grey market devices that have been purchased from abroad, Samsung are not replacing these unless back in the native device region, a little unfair IMO.
Click to expand...
Click to collapse
Looks like I have some reading comprehension problem. hehe. I misunderstood your comment. I agree that the green icon is a bit of an eye sore. Hopefully it's temporary and will switch back to white if and when Nougat is released.

tossero said:
Just tried to flash the original firmware in Odin and it failed ...
I am also interested by a solution !
Click to expand...
Click to collapse
Thanks, any particular error? Which firmware did you try to flash from/to? (Obvious I know but we can build a clear view of attempts on this thread)

alltaken123 said:
Thanks, any particular error? Which firmware did you try to flash from/to? (Obvious I know but we can build a clear view of attempts on this thread)
Click to expand...
Click to collapse
I've tried the one before the 60% update for France XEF (6.0.1 N930FXXU1BPH6 N930FOXM1BPH5 ) .
The error appears from the beginning , a red "failed" message. The file is ok since I've flashed it 2 times before.
Cheers~
PS: For the time being I am charging it to 80%(settings-device maintenance-battery-3 dots-advanced settings-uncheck "limit maximum charge to 60% ) thanks to @s_h_a_g_g_y , solution here: http://forum.xda-developers.com/note-7/help/battery-charging-limited-to-60-t3465566/page5

tiroger said:
Looks like I have some reading comprehension problem. hehe. I misunderstood your comment. I agree that the green icon is a bit of an eye sore. Hopefully it's temporary and will switch back to white if and when Nougat is released.
Click to expand...
Click to collapse
Yeah, it's an eyesore that could and probably will go away once they get at least 97+ percent of the affected devices back. Maybe with the 7.x update. In any event there were a lot of updates to Grace UX in this and the Sept. security patches. Why on God's green Earth would folks take a white battery icon over the UI updates and security patches? it seems insane to me.

Wait what was this update? I was reading and heard a vibration then phone reset, I thought it was the phone resetting on its own randomly (hadn't happened once yet) then saw it updating. Is there a changelog we can see somewhere? I just see a green battery icon being different. (I'm on a new replacement Note 7).

alltaken123 said:
@tiroger
Every device will eventually be updated, mine is a 2nd batch device (replacement) so it was unaffected (Black square on box), hence the green battery. I agree people should be returning these devices, however, like yourself i'm curious and wondered if a firmware downgrade was still possible after this update.
I am concerned for grey market devices that have been purchased from abroad, Samsung are not replacing these unless back in the native device region, a little unfair IMO.
Click to expand...
Click to collapse
I imported the note 7 from Singapore into the UK and am receiving assistance
Taken from samsung's Singapore site http://www.samsung.com/sg/note7exchange/
What if I bought it in Singapore but now residing in another country? How can I ship it back and how can you send the units outside of Singapore?
Please contact the Samsung Customer Service Center in your residing country for information on the exchange process in your residing country. We assure you that we will be assisting all Galaxy Note 7 customers in the exchange, regardless of your residing country and the country where you purchased the device.

itsjustbilly said:
I imported the note 7 from Singapore into the UK and am receiving assistance
Taken from samsung's Singapore site http://www.samsung.com/sg/note7exchange/
What if I bought it in Singapore but now residing in another country? How can I ship it back and how can you send the units outside of Singapore?
Please contact the Samsung Customer Service Center in your residing country for information on the exchange process in your residing country. We assure you that we will be assisting all Galaxy Note 7 customers in the exchange, regardless of your residing country and the country where you purchased the device.
Click to expand...
Click to collapse
That's amazing news. I bet it's a relief right?
I noticed initially that Samsung service centre's were playing hard ball on that issue.

stevierayvaughan said:
Wait what was this update? I was reading and heard a vibration then phone reset, I thought it was the phone resetting on its own randomly (hadn't happened once yet) then saw it updating. Is there a changelog we can see somewhere? I just see a green battery icon being different. (I'm on a new replacement Note 7).
Click to expand...
Click to collapse
I believe the update brings a green battery icon (Showing you're unaffected by the recall) as you noticed and a few behind the scenes changes to the Gracenote UX. Anyone using a recalled device is limited to 60% charge by the same firmware update.

alltaken123 said:
That's amazing news. I bet it's a relief right?
I noticed initially that Samsung service centre's were playing hard ball on that issue.
Click to expand...
Click to collapse
They tried to get me to take it back to the retailer, i said im not going back to singapore anytime soon, i was put on hold a few times sometimes for 5 or 10 minutes and supervisors got involved, but they did agree to exchange it - saying i would get a UK version phone, i said i only want the international variant. the saga continues but yes i will hopefully get the replacement (and the right one)

alltaken123 said:
I believe the update brings a green battery icon (Showing you're unaffected by the recall) as you noticed and a few behind the scenes changes to the Gracenote UX. Anyone using a recalled device is limited to 60% charge by the same firmware update.
Click to expand...
Click to collapse
Not in all markets. Canada does not limit the battery, but has a pop up warning that shows up every 3 hours.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
P.S
I still have my old device and new and have not noticed any behind the scene changes. What have you noticed?
Edit: excerpt from an interview with Samsung Canada:
An software update that will change the color of the battery icon on new Note 7 phones from white to green is heading out, automatically installing itself on every phone. Data charges for the update are zeroed out by carriers.
“In the event that you have a device that hasn’t been replaced, the software will detect what battery is in there and prompt you to register for the exchange program,” Brannen said.
While Samsung can flip a “kill switch” to remotely deactivate every old unit or limit the charge of the battery, — a strategy the company has chosen to apply in the US and Korea — the Canadian division has opted instead for a somewhat gentler prod: a notification every three hours urging users to switch up to a new Note 7.
“We have worked very closely with HQ and we determined that’s the wrong message to send,” Brennan said. “The message that we want to send to consumers is: ‘I want you to exchange your devices.’ Allowing you to only charge a device to 60 percent is not going to drive a great consumer experience.”
Sent from my SM-N930W8 using Tapatalk

alltaken123 said:
I believe the update brings a green battery icon (Showing you're unaffected by the recall) as you noticed and a few behind the scenes changes to the Gracenote UX. Anyone using a recalled device is limited to 60% charge by the same firmware update.
Click to expand...
Click to collapse
Thank you!

tiroger said:
Out of sheer curiosity, why would anyone not want to return the phone? If you received the update, presumably your phone was on the potentially compromised list. How do you make the determination that it's unaffected?
Click to expand...
Click to collapse
Cause, they don't exchange it yet. So they want us to go around with a half battery. no way!

@jmitr Thanks for the info. I was reading on one of the recall threads today that a user was aware of some Gracenote UX improvements including security a little thin in detail but information none the less. I'll try and tag the user in once I find the thread.
Could you please post your firmware revision? It would be interesting to see if you're using the same as the US devices, only differentiated by region detection perhaps.

alltaken123 said:
@jmitr Thanks for the info. I was reading on one of the recall threads today that a user was aware of some Gracenote UX improvements including security a little thin in detail but information none the less. I'll try and tag the user in once I find the thread.
Could you please post your firmware revision? It would be interesting to see if you're using the same as the US devices, only differentiated by region detection perhaps.
Click to expand...
Click to collapse
Old:
New:
Here you go.
Sent from my SM-N930W8 using Tapatalk

Omg that battery is ugly in blue background... rly hate Samsung now

Samsung Galaxy Watch SM800X RETAIL MODE removal

Hello. I am totally new to this forum. Please help me. I am a complete novice.
I have purchased a galaxy watch at auction. It is in retail mode. I have looked everywhere for straightforward advice on what I can do to remove retail mode and make this watch work normally. I cannot even connect my phone.
Does anyone know where I can find this information in one place? Or where I can find a step by step tutorial to remove Retail mode, and make this watch functional normally. Is this possible or have I purchased a brick?
Thank you in advance

Sadly, I suspect you may have bought a dud. The retail devices very rarely contain the full technology to make the device work. This is certainly the case for phones, so I suspect its the same for smart watches. Someone may have a little more knowledge and hopefully prove me wrong. Good luck

S20 Ultra Bricked (G9880)

Hi guys, i come here searching for help, it was a normal day, i was out with the phone fully working, it was on my pocket, when i get home i see that it's off, tried to turn on and nothing... tried vol- and power to enter download mode and nothing, the screen is always black.
Connected it to my laptop to see if it shows up as a USB device, it sounds like it connected and in "Device Manager" it show as "QUSB_BULK_CID:0412_SN:BA92F870" but ODIN doesn't detect it, so i can't try to install a clean ROM.
I can't take it to samsung as this model is a HONG KONG one and i'm in Chile, they won't apply warranty and legally i had only 3 month in a external shop but i'm on my 5th month, so it's not use to try that way.
A few points about the phone:
Latest firmware: (INSTALLED NATURALLY, I GOT IT FROM SAMSUNG OFFICIALY)
Country/Carrier: Hong Kong
Date: 2020-10-26
Version: 10
PDA: G9880ZHU2BTJ6
CSC :G9880OZS2BTJ6
NEVER EVER tried to install a rom or something on the phone, i was happy with how it works and the battery i got from it.
Now i bought a S20 FE as a momentary replacement because i can't be without a phone for my work... i've read lots and lots of threads on XDA and other places but all of them are about the Note 4, so it's really out of date to try fix it that way, at least 6-8 years old posts.
Anyone here had a similar issue? is it fixable?
Hope someone can help, it really hurts loosing a phone that costs +USD1000
Thanks guys.

Gerstark said:
Hi guys, i come here searching for help, it was a normal day, i was out with the phone fully working, it was on my pocket, when i get home i see that it's off, tried to turn on and nothing... tried vol- and power to enter download mode and nothing, the screen is always black.
Connected it to my laptop to see if it shows up as a USB device, it sounds like it connected and in "Device Manager" it show as "QUSB_BULK_CID:0412_SN:BA92F870" but ODIN doesn't detect it, so i can't try to install a clean ROM.
I can't take it to samsung as this model is a HONG KONG one and i'm in Chile, they won't apply warranty and legally i had only 3 month in a external shop but i'm on my 5th month, so it's not use to try that way.
A few points about the phone:
Latest firmware: (INSTALLED NATURALLY, I GOT IT FROM SAMSUNG OFFICIALY)
Country/Carrier: Hong Kong
Version: 10
CSC :G9880OZS2BTJ6
NEVER EVER tried to install a rom or something on the phone, i was happy with how it works and the battery i got from it.
Now i bought a S20 FE as a momentary replacement because i can't be without a phone for my work... i've read lots and lots of threads on XDA and other places but all of them are about the Note 4, so it's really out of date to try fix it that way, at least 6-8 years old posts.
Anyone here had a similar issue? is it fixable?
Hope someone can help, it really hurts loosing a phone that costs +USD1000
Thanks guys.
Click to expand...
Click to collapse
Aorry to hear that.. did tou try vol up and power to go to recovery?

Gerstark said:
Hi guys, i come here searching for help, it was a normal day, i was out with the phone fully working, it was on my pocket, when i get home i see that it's off, tried to turn on and nothing... tried vol- and power to enter download mode and nothing, the screen is always black.
Connected it to my laptop to see if it shows up as a USB device, it sounds like it connected and in "Device Manager" it show as "QUSB_BULK_CID:0412_SN:BA92F870" but ODIN doesn't detect it, so i can't try to install a clean ROM.
I can't take it to samsung as this model is a HONG KONG one and i'm in Chile, they won't apply warranty and legally i had only 3 month in a external shop but i'm on my 5th month, so it's not use to try that way.
A few points about the phone:
Latest firmware: (INSTALLED NATURALLY, I GOT IT FROM SAMSUNG OFFICIALY)
Country/Carrier: Hong Kong
Date: 2020-10-26
Version: 10
PDA: G9880ZHU2BTJ6
CSC :G9880OZS2BTJ6
NEVER EVER tried to install a rom or something on the phone, i was happy with how it works and the battery i got from it.
Now i bought a S20 FE as a momentary replacement because i can't be without a phone for my work... i've read lots and lots of threads on XDA and other places but all of them are about the Note 4, so it's really out of date to try fix it that way, at least 6-8 years old posts.
Anyone here had a similar issue? is it fixable?
Hope someone can help, it really hurts loosing a phone that costs +USD1000
Thanks guys.
Click to expand...
Click to collapse
The device is powering on and off randomly on it's own, correct? This sounds like a hardware issue, you may have a defect somewhere in the power supply chain. If you have a reputable repair agency nearby, not necessarily Samsung, this would be my first step. Not sure why Odin isn't detecting the device. Here's an article which offers common solutions for this problem.
https://rootmygalaxy.net/fix-odin-not-detecting-samsung-android-phone/
Good luck!

myaslioglu said:
Aorry to hear that.. did tou try vol up and power to go to recovery?
Click to expand...
Click to collapse
Yes, but it doesn't work, screen alway stays on black, i know it's not fully dead because it sounds as a USB driver when connected to my laptop
varcor said:
The device is powering on and off randomly on it's own, correct? This sounds like a hardware issue, you may have a defect somewhere in the power supply chain. If you have a reputable repair agency nearby, not necessarily Samsung, this would be my first step. Not sure why Odin isn't detecting the device. Here's an article which offers common solutions for this problem.
https://rootmygalaxy.net/fix-odin-not-detecting-samsung-android-phone/
Good luck!
Click to expand...
Click to collapse
tomorrow i'll try to take it somewhere, thanks for the link, but i already tried all those tips

I take it you have a Qualcomm cpu? If so you need to install the Qualcomm usb driver, link https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/ or a newer version if available. This should solve the problem in regard of pc connection, usb recognition and most of all reading the internal memory. Please use Google search for mor info and the correct procedure as i never used this myself. Good luck.

gee2012 said:
I take it you have a Qualcomm cpu? If so you need to install the Qualcomm usb driver, link https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/ or a newer version if available. This should solve the problem in regard of pc connection, usb recognition and most of all reading the internal memory. Please use Google search for mor info and the correct procedure as i never used this myself. Good luck.
Click to expand...
Click to collapse
Anything you can find on google i already tried, installing the drivers didn't help either... thanks tho!

Oh hey, its you! We spoke on reddit a few days ago about this problem, sorry to see you haven't been able to fix it.
Have you tried all your USB ports? Or maybe another computer? Worst case scenario there's a solid chance Samsung will repair it either for free if you're lucky or for a price. Even if you bought it from another country there's a possibility the manufacturer's warrant is intact especially because it sounds like you didn't do anything to the phone at all that would've warranted the sudden failure.
Does ADB see it when it's plugged in? If you don't have ADB installed follow this: https://www.xda-developers.com/install-adb-windows-macos-linux, then once installed run "adb devices" from command prompt.