Database Users

Need help (Qtek2020)

Hi all
yesterday, while trying to put my device into my jeans pocket, i left it and it fall down to the ground... No damage at the moment after a first check... everything ok... BUT... after coming back home, i've put it into the connection base and anything happened... i've tried softreset but anything happened too.... so i've noticed, looking at the bottom of the qtek, that the port for the cable/base connection wasn't ok.
Here is the problem.... i get no activesync connection or power charging because the port is damaged... i've found that this port moves in every direction and so it isn't well attached to the mainboard. So i decided to disassemble the device to understand what is the problem whit my qtek.
After disassembling it, i noticed that the port has lost the weld that locks it to the mainboard...
And now??? What to do??? The port is completely detached and i think that there is no way to weld it again to the MB.
I'm out of warranty time too and i think that the warranty doesn't cover this kind of problem even because the technician will understand the reason of the unwelding.... and even because i'm not using my original rom from qtek....
So i thought one thing... is there any way to find a cable to connect the device from the port that i found just under the battery??? Where can i find the right cable??? And will it be usefull to get back again all the functionalities???
Please help.... i don't want to break up from my qtek so soon.... and i would like to wait few months before to buy a new device... (universal).
Hope someone will give me some advices... or suggestions.
Bye.... MINDGAP.

Anyone's got an advice for me??? Anyone can help???
I'm in troubloe here and i would like to understand if i could make my own cable to use from the back door port that i found under the battery cover of my device.
I tried to look in the himalaya wiki page but i found anything about this port.... only connection for the main port... that i can't use anymore because it's completely distroyed....
Please help me i can't believe that i'have to throw away my pocket pc only because of this problem....
What i would like to understand is if i can weld the port back again to the MB or even to give power from the port that is placed under the battery to use it only like Navigator in my car.
Please let me know if i can find a cable or a different solution in order to get my device back with all functionalities... i could even send the device to someone who could repair it and send it back again.
I would pay to have it back repaired.
Hope someone will help.
Thanks and have a nice day!

some images from the disaster!!!!
ok... here u are some images taken this afternoon.... featuring my POOR DEVICE..... terribly wounded.... almost dead!!!!
Hope these images will help you in trying to find a solution....
THIS IS THE SITUATION HERE.......
{
"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"
}
THE CONNECTOR IS FULLY DETACHED FROM THE MB.... AND I DON'T KNOW WHERE TO BUY ONE BRAND NEW... OR IF I CAN USE THIS ONE AGAIN.......
HERE U ARE TWO IMAGES OF THE MB WITHOUT THE CONNECTOR... AS U CAN SEE.... THE MB IS NOT DAMAGED AT ALL..... AND I THINK THAT THERE COULD BE A WAY TO RESOLD THE CONNECTOR......
ONE DOUBT ABOUT THIS LAST PICTURE.... IS THE SECONDARY PORT USABLE???? WHERE CAN I FIND A CABLE OR CONNECTOR THAT MATCH WITH IT????
LAST PICTURES SHOW THE STATUS OF THE CONNECTOR AND THE CAGE THAT PROTECTS IT.... IS THERE ANYWAY TO USE THEM AGAIN???
I HOPE THAT SOMEONE HAS SOME SOGGESTIONS FOR ME BECAUSE AFTER A SEARCH ON THE FORUM I FOUND ONLY INFORMATION ABOUT THE CONNECTORS BUT NOT IF IT IS POSSIBLE TO SOLDER AND TO BUY A NEW ONE.......
Thanks in advance just for reading this post.... and thanks much more for answering.....

Mindgap,
go to www.ipaqrepair.co.uk, order the Switch Board Socket 22 Pin (3800 Series)
Product code: 204
link is:
http://www.ipaqrepair.co.uk/view_product.php?product=204
I think your device will be good as new.
good luck
ATC

Thanks for everything u did for me ATC.....
I hope my device will be back soon...
Best regards.
Mindgap

if this is still a problem for you and all else has failed then I would be preperd to try and resoulder the connection for you I do have all the right equipment and I have experance as I have chiped sevreal Xboxs and thay have a fue fiddley bits plus I was traned to militry spec in solderin at EEV but there is no garantee but from what I have seen I may well be able to do the job. You can pm me in here and I will be watching this thred.

...
Well I've had also this problem once. I have broken this connector off the board with the charging adapter from charger. Anyway it isn't too difficult to repair that if you are a bit handy. Just use a micro-solder and carefuly sold the connector back.
Important:
1. Don't plug the battery while you repair that!
2. Use the rosin to prevent decant the pewter on the pins
3. Use the pewter-suction band to remove the pewter from the connector if is it too much
4. When finished,use a mechanical tools to remove the rest of the rosin. Don't use alcohol based solvents(I have damaged the JoyStick with Isopropyl-Alcohol)!
5. Ensure that all pins are solded separately and no pins are bridged by soldering!
Probably this will result as a Hard-reset,because the repair will take probably more than 30mins without battery or you can short-circuit the backup battery. Therefore backup all your data(WM5-Only RAMdisk).

In the meantime, you could still communicate with your wounded beast say using Activesync over Bluetooth (that will sort out your sync issues and allow you to have an up to date copy of your data). Similalry if you have or can get an SD card you can dunp copies of data onto that too.
Also if you can get your hands on a second battery quickly enough, use the cradle to keep one bat on charge while using the other in the device. Regularly swap over will mean that you can at least use your Himam until you are in a position to solder new/old parts.
Regards - Mallow1

Can some one post a topic or a detailed manual on how to disassemble the hima?
Regds Aldo

...
You need to remove the black antenna cover. After that is it easy. Just few screws. Remove all parts in cover neighbourhood(card,stylus,antenna connector cap). Then release both hooks located at the top of the battery with your nail or small screwdriver pushed into the stylus hole and at the volume-slider location. After that release fixings in surround of the card slot. Do it easily and carefully! Otherwise you can break the plastic. You can find also the service manual at wiki.xda-dev,but DON'T do it that way! That procedure is wrong.

Disassaemble
Can anyone send some pictures on how to disassemble the qtek. Which screws do we need to pull out and how do you do that?

hi i did assemble the connector my self , but i m in Egypt , Cairo ...if you like call me on my handy
+20123382923
Jimmy Rag

Project Electric Himalaya

Hello to all. I'm a "new" member to the XDA-Dev community, and I am today presenting a document on my project that I've been dreaming about for 2 years or so. Finally, I had enough time to take time off my schedule to do something significant today - start this project officially.
I have an O2 XDA II with a broken connector. I will be attempting to hardwire an electrical source to the device by as many means possible. I have created this thread for people to come together and discuss any information they might have, any thoughts/ideas they want to share, or any observation(s) on their own experiments with this device.
http://s21.photobucket.com/albums/b296/tubecena/?action=view&current=himalaya.jpg
ps. : Here is something i forgot to add to the drawing :- At the end of the two wires in the end, I aim to put a USB male/female (haven't decided). Maybe i'll even redesign the area of the connector, but that would result in heavy work. We'll see how it goes. (and see how this thread gets feedback)
Here's something that might kickstart your contribution to this thread :
- Will it be possible to run the device without a battery with a charger of 5V?
- Will it be possible to join the two plates, positive (1+2) and negative (5+6), together, and get more power? Will there be any changes? Will there be a performance hike?
- What will happen to the device if a charger of 5.2V is used?
- If the two end wires are left not connected to a source, will an energy leak of any kind happen?
- Will the length of the wires significantly increase resistance and therefore reduce battery life?
I'm new here, go easy on me! >.<
Thanks for your time, and effort.

your questions are mainly in the general electric cat rather then himalya really
"- Will it be possible to run the device without a battery with a charger of 5V?"
yes unless the device detect the batt present and refuse to work without it
"- What will happen to the device if a charger of 5.2V is used?"
thumb rule is 20% each way without any problem
"- If the two end wires are left not connected to a source, will an energy leak of any kind happen?"
electrons travel from + to minus can't travel over air unless it's very hf
"- Will the length of the wires significantly increase resistance and therefore reduce battery life?"
there are many sites which let you calc the resistence of wires over lenght
but if you don't make them longer then 50cm you should not worry

Ah, thank you for your reply. Yes maybe you are right about the "electrical category" part, but since I was working on Himalaya, I might have just gotten a little over-excited and thought I might start a "project". Right you are, indeed this is purely electrical stuffs, but if you/anyone else might have any other information or ideas to refurbish your Himalaya, maybe this might be the place?
I was thinking of making use of the cradle from XDA II, resulting in a rewiring of the cradle and the device. Then that would mean that I need alot of USB cables, a drill, and maybe some wood? Well, if anyone has any points to bring up, speak up yeah?
In any case, IF I do decide to make something to help those dead Himalayas (like I said earlier, remodelling the cradle and device), then we'll have this thread as a tut.
Thanks and have a nice day people.

DEAD Hima.
okay, so i took two wires, connected the battery and the device (one plate and one pin each) and tried to fire up the device. It wouldn't start. I reinserted the battery to the Hima and it wouldn't fire up. I'm guessing that it's DEAD. Anyone might want to help me on this one?
- my connector is dead.
- my 2 batts are fully charged, still no avail. (not dead batt i guess)
- i charged my backup batt but still no avail.
- either there is an overall power undersurge(i'm just shooting random thoughts), or the RED SWITCH is causing the problems. coz the red switch is indeed loose"r", or, more loose, than before. Maybe I hit it abit too hard in the process and thought the battery did it, i'm not sure. Any help would be appreciated.
Oh and I'm buying a SECOND HAND PDA/XDA/WMTS DEV. I'm situated in Singapore. And I just need a very cheap one. I wouldn't mind if it has 1/10 cosmetics, coz i just need it to let my mum play solitaire. She's an avid player and would be very very cranky if she doesn't play in every few hours. Would preferably consider a very rundown XDA II, or XDA IIs, provided the cost is below SGD 70. Thanks and have a nice day people.
ps. even if it's not rundown, just pm me, we'll see how it goes. I need this asap!

Connector broken
Hi,
I have the same problem, my PDA connector (22 pins) is broken and I would like to connect directly the power on the battery pins (6 pins connector) but I dont know where are the + and - on these 6 pins!!!
Thanks for your help,
TD.

thats why we made a wiki for you
http://wiki.xda-developers.com/index.php?pagename=Connectors

completely broken
No because the 22 pins connector is completely broken (motherboard too)!!
But when I plug a charged battery, it's OK...

curious
tdfamily said:
Hi,
I have the same problem, my PDA connector (22 pins) is broken and I would like to connect directly the power on the battery pins (6 pins connector) but I dont know where are the + and - on these 6 pins!!!
Thanks for your help,
TD.
Click to expand...
Click to collapse
yeah even i got curious where does the right pin on my himalaya
because i'm on my project to recover my hima to out of his grave

lontong balap said:
yeah even i got curious where does the right pin on my himalaya
because i'm on my project to recover my hima to out of his grave
Click to expand...
Click to collapse
http://pinouts.ru/PDA/pda_wallaby_pinout.shtml
Have fun

how about fitting a mini usb to the himalaya?
You see, i would do it but my himalaya is very precious to me, so if i screwed up i am done for.

flyboyovyick said:
how about fitting a mini usb to the himalaya?
You see, i would do it but my himalaya is very precious to me, so if i screwed up i am done for.
Click to expand...
Click to collapse
Hardwiring means HARDWIRING YEAH
{
"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"
}
I wonder that hima could survive it.

aeroflyluby said:
Hardwiring means HARDWIRING YEAH
I wonder that hima could survive it.
Click to expand...
Click to collapse
whats that you are holding in your hand?

flyboyovyick said:
whats that you are holding in your hand?
Click to expand...
Click to collapse
A soldering

You're right: It looks a bit like a Gamma Scout! lol

When my connector goes thats what iam going to do. mini usb it.

flyboyovyick said:
When my connector goes thats what iam going to do. mini usb it.
Click to expand...
Click to collapse
Flashing via bluetooth would be genius (and possible, radio stack should support it)

Developing methods to recover bricks without JTAG

I have not seen anything in the Captivate forums about UART, I2C, or really anything other then Download Mode/Recovery Mode. We could use some developers to help with this project. It's an interesting combination of hardware, software, and inter-chip communications protocols...
I think everyone knows about the 301Kohm resistor between pins 4 and 5. Did you know about the 150Kohm or the 619Kohm resistors? How about the middle battery pin?
Watch this video.
Resources
Users
One-Click Unbrick was relesed This will unbrick softbricked phones http://forum.xda-developers.com/showthread.php?t=1153310
Kernel developers
UART Kernel debug log AND shell terminal (like adb shell without adb active) On the captivate you can get into the SBL prompt, then type
Code:
printenv
setenv SWITCH_SEL 6543
printenv
saveenv
This changes the SWITCH_SEL value from 65 to 6543 and enables extra output. This will give you a kernel debug output and drop you into a shell prompt.
Developers
bootloader source code For a simlilar samsung device: http://forum.xda-developers.com/showthread.php?t=1018862&page=68
here is the iROM,: I've rehosted it here: http://teamkomin.googlecode.com/svn-history/r75/branches/IROMcode/bootdumps.rar
here: http://www.mediafire.com/file/c9bg6gyk1cuapsz/bootdumps.rar
and here: ftp://adamoutler.dyndns.org/bootdumps.rar
we need help deciphering it. We think the annotations may be wrong. This is the unchangable code in the first few blocks of memory. There must be a way to communicate with this.
Hardware guys
S5PC110 processor datasheethttp://www.mediafire.com/file/3znisgfm3amxgpj/S5PC110_EVT1_UM10.pdf This is the processor in our phones. This documents everything which is capable natively with the processor. It is 2425 pages long.. I read through it and added some notes here.. This is the meat of the manual: http://forum.xda-developers.com/showthread.php?t=1018862&page=51
FSA9280A datasheet http://www.mediafire.com/?d4e21efhuktctcb This is the first time we've had access to this manual. Our phones use the FSA9480A chip, this chip is functionally the same. The datasheet here describes all functions available to the USB switching device. From the FSA9280 datasheet we've located all resistor values. http://forum.xda-developers.com/showpost.php?p=14408452&postcount=62
All
The All-In-One GalaxyS HackPack hardware, software and documentation on our phones http://forum.xda-developers.com/showthread.php?t=1111866
It has been revealed from a source which is not to be mentioned that the OM pins/registers are fixed and cannot be changed on the processor without removing the processor from the device or making some hardware modifications.
Here's some must read threads.
Fun with resistors:http://forum.xda-developers.com/showthread.php?t=820275 This thread shows all known resistor values
Lets save some bricks:http://forum.xda-developers.com/showthread.php?t=1018862 This thread deals with ways to revive phones from the dead. We are hacking the heck out of them in here.
Development platform booting from MMC http://hi.baidu.com/j2h3344/blog/item/85740dfc0be35951d7887dd5.html This is the platform used to develop our phones. We need to find these OM bits, or access them somehow.
the middle battery pin http://forum.xda-developers.com/showpost.php?p=13448859&postcount=253 This may be the answer. We could use some help in this area.
Download the GalaxyS Hack Pack here: http://forum.xda-developers.com/show....php?t=1111866
Known Causes of hard Bricking
1. PBL(Primitive bootloader) and SBL(secondary bootloader) were not designed for the phone
2. Mismatched PBL/SBL combination
3. SBL does not fit in the Partition information table, or location does not match Partition Information Table
4. Bad USB cables
5. power loss
6. Damaged PBL/SBL
--Theoretical--
7. Something known as Secondary Bootloader Rotation may be to blame for improper bootloaders sometimes. Apparently when flashing, the SBL and SBL2 blocks may switch places. In this case you may have the proper PBL, but the SBL is not proper for the device.
Hardware Used
If you're looking to help, you'll need some development hardware. I use an Arduino Mega. http://www.bizoner.com/arduino-atme...e-p-180.html?zenid=9mg23h688slfjgh88910o5jfd2 This is a programmable interface. You can use this code to talk to the phone. http://forum.xda-developers.com/showpost.php?p=13351363&postcount=223
Here's some plans for a communications adapter http://forum.xda-developers.com/showthread.php?t=925034
The plan
If we can get into a bricked phone via UART or the i2C bus, or the USB bus, or any other method available to U301, we can corrupt the PBL(boot.bin) in the OneNand which will cause the processor to search for a PBL and SBL on USB, UART and MMC.
If we can locate an additional communications port somewhere on the phone we can change or corrupt the code running in memory and then cause the processor to reboot into USB or UART mode.
So far we know of UART only and have eliminated that as a solution on it's own.
{
"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"
}
Using SBL, it is very likely possiblity that Windows7 phone or iOS, or ubuntu could be ported over.... Basically, full control.
Why you should help
We've been working on ways to recover these phones for months now. We're comming to an end. We need massive amounts of testing to figure out this last bit.
This is a call to duty. Every developer who has ever released a boot.bin, SBL.bin, param.ifs or a PIT with their release needs to be a part of this. Every member who has ever bricked a phone while using one of the many tools which are designed to upgrade your phone can help. Anyone who wants to feel secure while flashing their phone should put some effort into this because it's expensive and requires superhuman soldering to JTAG these phones. If you've even thought about using Odin3, we need your help.
Update: UnBrickable Captivate http://forum.xda-developers.com/showthread.php?t=1206216

Seems interesting / promising, unfortunately I can't help BC I moved back to Morocco (Africa) and only brought 1 captivate with me. Good luck that is all I can say.
Sent from my SGH-I897 using XDA Premium App

Really interesting and very cool.
But I have a fully bricked captivate which I still have cause it was a friends who just went onto the Inspire. Always have wondered if I could recover the hard brick.
Wish I could help but I'm pretty useless with Soldering and taking apart my phone. But if development moves along with this I'd love to support. The idea of porting those OS and helping everyone saving hard bricked phones would be great.
Good Luck!
Sent from my SGH-I897 using XDA App

im bookmarking this. i can only help in fabrication. im not a super genius dev. but threads/projects like this do interest me.

Middle battery pin? Reminds me of the battery jig trick on the original PSP.
All-in-all, this looks promising, I'll be following it.

Posted up the iROM in the first post. this is the code which we hope to establish communications...
Keep in mind, this could be over the USB port, the Middle battery terminal, or even the headphone port.

But I have a fully bricked captivate which I still have cause it was a friends who just went onto the Inspire. Always have wondered if I could recover the hard brick.
Click to expand...
Click to collapse
I'M GETTING ONE OF THOSE IN THE AM!!!!!
i have a fully bricked cappy that i bricked lastnight. i was able to recover from the phone..!..pc icon but then failed @95% via odin3 v1.00.
i will mail you the cappy if you can fix it and use it as a test mule for future brick\unbrick attempts...... the outer glass is broken thanks to a fall from my lap to the concrete

I think I actually discussed this with you before. I ran twice into some instance where no action would make difference on the phone, no response to key combos, no response to charger or USB. But, download mode was still accessible via USB Jig.
What could've happened there?

cumanzor said:
I think I actually discussed this with you before. I ran twice into some instance where no action would make difference on the phone, no response to key combos, no response to charger or USB. But, download mode was still accessible via USB Jig.
What could've happened there?
Click to expand...
Click to collapse
Not really positive at this point, id suspect corrupted pbl.bin or param.lfs partitions. I've seen some weird stuff with the pbl. One phone would only output uart when volume + was held for 5 seconds.
Basically from my understanding... The IROM loads into the processor. This is the first 40000 bytes and it's protected memory. The iROM brings up basic functionality for the processor, including the initial factory UART/MMC load of PBL & SBL. The IROM then instructs the phone to load the IBL/PBL(Initial Boot Loader/Primitive Boot Loader). The IBL initializes memory for the SBL(Secondary Boot Loader) , then the PBL loads Params(a partition on the OneNAND) and checks the pins on the processor for commands. The PBL then makes more memory available for applications, then locates and and loads the SBL. The SBL initializes other functions and then locates and loads the kernel.
The SBL is responsible for Download Mode and the SBL prompt. it is basically the system's "BIOS" for lack of a better word. I'm not sure of the steps which can be skipped for sucessful download mode.

The iRom download it broken.
Ill look at it once your reupload

Some kid reported the iROM code as being in violation of the terms of agreement of the hosting website... It must have been a kid because Samsung would not do that. Just as we have a right to use tools to disassemble our phones, take pictures, annotate those pictures and post them on the internet, we have the same right to the IROM. It's not hurting Samsung's sales, nor is it intellectual property of Samsung. We bought the phones and it came with this. The only intellectual property in this document belongs to the person who disassembled and annotated this code.
I've rehosted it here: http://teamkomin.googlecode.com/svn-history/r75/branches/IROMcode/bootdumps.rar
here: http://www.mediafire.com/file/c9bg6gyk1cuapsz/bootdumps.rar
and here: ftp://[email protected]/bootdumps.rar username xda password developers
Lets not be childish and hinder progress anymore by clicking buttons. I've removed that ability.

I think this is a wonderfull bunch of work that is being done here and if i can offer any assistance please let me know. If you would like a private IRC channel to discuss your work in with other developers I would be more than happy to provide to a quiet private place to do so. Just shoot me a pm if i can be of any assistance.

We can really use some SGS folks to help. Check out the lets save some bricks thread mentioned in the first post.

Two quick questions:
1. How would you manage to get these files? First, aren't they burned into the nand? Secondly, wouldn't they be assembled already? How do you disassemble them?
2. Do you have any good links/books on how to learn arm assembly? I know some x86, but I've never found a good link to arm based stuff (or any sort of dev platform, for that matter).
Sorry about being semi-offtopic.

Subscribed, and very interested in following progress on this.
Also: Sending PM.

Nothing revolutionary to add just yet.
However, I just finished adding a JTAG breakout to my collection. This is what my current test setup looks like:
We could use some more DIYer's on this project. The biggest thing to have is an Arduino and a microUSB breakout board. We need to figure out how to get this phone to boot from MMC, USB, or UART... and we know Samsung does this to bricks.

this looks interesting.. gonna keep my eye on it

AdamOutler said:
Nothing revolutionary to add just yet.
We could use some more DIYer's on this project. The biggest thing to have is an Arduino and a microUSB breakout board. We need to figure out how to get this phone to boot from MMC, USB, or UART... and we know Samsung does this to bricks.
Click to expand...
Click to collapse
i can build anything, the purchase of and arduino and making the breakout board are easy but i would have no idea what to do with it afterwards.
it is funny the time you posted this because my friend found out about a club that works with arduino boards making all sorts of things and asked me if i wanted to go to there meetings. this thread popped up the next day.
well i may buy an arduino board or 2 but im not sure if even then i can be helpful

Well, a pretty much unexplored area of the phone is the middle battery terminal. The middle battery terminal is a ADC(analog to digital converter) pin. We know for a fact that it triggers something called EXT-I2C (External Inter-Integrated Circuit). EXT-I2C can be used to communicate with any chip on the I2C bus. The I2C bus connects with everything on the phone... Call Processor, OneNand, Memory and Application Processor. Using the EXT-I2C, we would have full control over the phone.
I know the middle battery terminal has something to do with it because I managed to get my phone to boot-loop with the pin disconnected and I saw messages about EXT-I2C NACK( EXT-I2C not acknowledged) when playing with resistance values and watching the UART output on my Arduino MEGA.
The unanswered questions are,
How to reproduce that EXT-I2C message?
What are the Addresses on the I2C bus?
Which pins control the I2C bus?
Here's some of the possible I2C bus connections:
USB VCC
USB Ground
USB D+
USB D-
Batt+ (when powered on USB)
Batt- (when powered on USB)
BSI (Battery Signal Indicator - middle battery pin)
Headphone Left Audio
Headphone Right Audio
Headphone Video
Headphone Ground
all External-SDCard (MMC) connections
all SIM connections
This is something you can bring to the table at that Arduino club. You can also read up on this hackaday article http://hackaday.com/2011/05/11/i2c-101/

If anyone has a good idea of which pins may be OM pins here, let me know..
Side facing LCD screen
Side facing back of unit

The Captivate Development Platform mod AKA UnBrickable Mod

Background
First off, big thanks to TheBeano and Midas5 for teaching me about UART, decompiling bootloaders and figuring out how the OM values work. Their initial work and dedication in "Lets Save Some Bricks" inspired me greatly. Since the work started we've analyzed UART outputs, hacked the heck out of the SBL prompt, obtained both decompiled and source for bootloaders, and generally learned a **** ton about our devices... Mind you, that's a Metric **** ton, not the Imperial **** ton, which is equivalent to nearly 2000 assloads. The reason I'm branching this operation at the current point is because this modification is specific to our device. The proper modifications for other Samsung devices have not been identified yet. We're first! Yay! We need to focus on Captivate firmware development now. The firmware may encompass all GalaxyS models as well, but this modification will only work on the Captivate.
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 Captivate 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 captivate. 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 send me a PM(my username @gmail.com) or Connexion2005(aka MobileTechVideos.com). Note: I do not work for/with mobiletechvideos.com.
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 (for the wire contained within)
getting started:
You will need a very small peice of wire. Tear apart the relay unravel the coil within and grab about 12cm~ of wire. The fact that it comes from a relay is important because relays generally have very small wire which are individually treated with a non-conductive coating.
Take the 12cm~ wire from the relay and tin the very edge of it. No more then 1/32". If you tin more then 1mm, cut off the excess. It is desirable to have a slight bit of excess solder on the tip of this wire.
performing the modification:
1. tear apart your phone... remove 6 #0 phillips screws from the back. Two of them are under the battery slide flap. The slide flap must be up on one end and down on the other in order to get to these screws... Don't LIFT the slide flap, just rotate it at an angle. Once the 6 screws are out, then you can separate the back from the front. Make sure to take out your SIM and external SDCard before you do this.
{
"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"
}
2. remove the mainboard... there's a single screw and 5 connectors which require removal. Remove them. Pull the board out and place it on your workspace
3. remove the EM shield from the processor side.
4. remove the OM5 resistor in the picture below. It's coated in glue. I've found the best thing is to just coat the area in flux and let it do the work while prodding with the iron to move the resistor out of place.
5. Connect the active side of xOM0 resistor to the active pad on OM5's resistor pads.
http://i51.tinypic.com/160zmty.jpg
6. reassemble the phone.
Special Instructions
This replaces the battery charging sequence. The normal battery charging sequence can be activated by holding power for 4 seconds.
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. You can use your custom rom menu option, adb reboot download, or use a terminal to "reboot download". 301Kohm Factory Mode JIGs work as well, but you must press power to bypass the S5PC110 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 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
Linux Detector tool: http://forum.xda-developers.com/showthread.php?t=1257434
Linux Automated UnBricker:http://forum.xda-developers.com/showthread.php?t=1242466
firmware
Bootloader Hello World by Rebellos http://forum.xda-developers.com/attachment.php?attachmentid=698077&d=1314105521
UnBrick tool http://forum.xda-developers.com/showthread.php?t=1242466

Great work adam. cant wait to see this used to reflash bootloaders or something.

now we need firmware... i figured adam would have flashed something already , and thought about getting back from that flash later

https://github.com/teamhacksung/uBoot
possibility of uBoot on our devices... so much nicer than our current bootloaders. initial work has been done by codeworkx for compatibility with our boards, but (obviously) hasn't been tested

COOOL
looks good

Very exciting work y'all! Any plans on using it to dual boot Andbuntu/iOS?

Wow dude, you do some great work. Keep us posted!
Now if it only was a light sabor too....

i did a little bit of reading and definitly agree it would be cool to get uboot on our phones,
along with unbicking devices.
I would love to help sadly I have no knowledge of this low level stuff, or soldering skills.
I will watch this thread closely. Good luck guys.
http://www.linuxfordevices.com/c/a/...s-UBoot-the-universal-open-source-bootloader/

I was attempting to see what i could "upload" from my daily phone. I messed up my daily phone while performing this modification. I was trying to remove the xOM5 resistor and got impatient. I broke it off, it took the pad with it and I and was left with only a .001mm wire on the board. I attempted to solder it for about 6 hours straight and after a while I swiped off 5 resistors in a line. I'm sure I could repair it, but I just went and bought another phone.
Lesson: Take your time, and don't try to force anything. That glue is tough and it acts as a heat sink. Remove the glue from one side of the resistor, heat the entire resistor up and let it slide off. Don't try to speed it up.
Once you perform this modification everything works just fine. No problems. It's a risky procedure though.
I still have not tested any firmware sucessfully. I tried a few precompiled uboots, but I did not yet try the uboot mentioned above.

This looks awesome, although I'm hesitant to do it, because there's always that chance that I will need to RMA. Sorry about your phone Adam, I think everyone in the forum is probably in love with you now though!
Sent from my SAMSUNG SGH-I897 using XDA Premium App

I would add that when doing this work, you should use ESD protections. Wrist strap (you can rig a homemade version), ESD mat, etc. Not as big of a risk in a humid environment, but as relative humidity drops, the risk increases. You can never be to safe if your phone is valuable to you. Typically, consumer electronics are hardened to ESD through connectors and the housing, but when you are directly handing the PCBA, you are potentially bypassing the hardware filters.

I need something to flash with this bad boy now.
Sent from my GT-I9000 using XDA Premium App

Adam, thanks for all your work, and everyone else for that matter. Connexion never responded to my PM about jtag work, but this little modification is so damned easy I went ahead and did it. I'll be patiently waiting for a firmware we can use to reflash bricked phones in the future.
Again, thanks a ton!

I don't need to rework the board do I? As in is picture 4 simply for reference?

Proxyep said:
I don't need to rework the board do I? As in is picture 4 simply for reference?
Click to expand...
Click to collapse
Picture 6.

Adam, did you try tracing the i2c?
It might give us an un-brick mode without even soldering om5.

So what would this exaclty do?, dont wanna do it till i know exactly what it does.
Sent from my Cappy with Glitch V11 LL at 1.6GHz stable, Juwe's RAM script, V6 script, V8 kickass kernel tweaks, and 3G booster script using XDA Premium App

midas5 said:
Adam, did you try tracing the i2c?
It might give us an un-brick mode without even soldering om5.
Click to expand...
Click to collapse
No, I have not been messing with hardware since I found the OM5 mod. I wish to develop this further. If you can get me a pin number to trace I will do that. Please look up the pin in the S5PC110 manual and I will trace it... I've been very busy locating software for this mod.
b-eock said:
So what would this exaclty do?, dont wanna do it till i know exactly what it does.
Sent from my Cappy with Glitch V11 LL at 1.6GHz stable, Juwe's RAM script, V6 script, V8 kickass kernel tweaks, and 3G booster script using XDA Premium App
Click to expand...
Click to collapse
Currently we are running into this:
Code:
��������������������������������������������������������������������������������
Uart negotiation Error
Secure Fail Error
Secure Fail Error is likely because the uBoot I am loading violates the S5PC110 chain of trust. I am working to locate software which will not violate the chain of trust.
See this post for more:
popfan said:
I found this while waiting for the reply from Samsung.
http://www.aesop.or.kr/?document_srl=266600&mid=Board_Download_S5PC100
This is Linux Native - Complier Package
Please note this is in Korean.
One more found:
http://www.aesop.or.kr/?mid=Board_Download_S5PC100&page=2&document_srl=75581
USB OTG-Mon Binary ??
Last one - S5PC100 Code Visor Debug resource
http://www.aesop.or.kr/?document_srl=267106&mid=Board_Download_S5PC100
Click to expand...
Click to collapse
I have a 3 day waiting period for my id on that site to become active, at which point, I believe we will have a solution.

I believe the binary on this page will be the solution http://www.aesop.or.kr/?mid=Board_Download_S5PC100&page=2&document_srl=75581

b-eock said:
So what would this exaclty do?, dont wanna do it till i know exactly what it does.
Sent from my Cappy with Glitch V11 LL at 1.6GHz stable, Juwe's RAM script, V6 script, V8 kickass kernel tweaks, and 3G booster script using XDA Premium App
Click to expand...
Click to collapse
Allows you to boot from things other than the internal sdcard, and overwrite memory on the phone. Basically, if you break a bootloader, this is the only thing that could fix it beyond re-jtaging it.
At this point, there's no real point unless a) your device is bricked or b) Adam gets the software half up and running, in which you could do it as a pre-emptive measure.

I9000 Technician Service Manual (latest)

Contents :-
1. Specification
2. Product Function
3. Exploded View and Parts list
4. MAIN Electrical Parts List
5. Level 1 Repair ( Software un-bricking)
6. Level 2 Repair
7. Level 3 Repair
8. Flow Chart of Troubleshooting
Power On Failure
Initial Failure
Abnormal charging part
NO SIM Failure
Microphone Part
Speaker Part
Receiver Part
Blue Tooth & WiFi is not working
FM Radio does not work
LCD is still off after Power ON
Touch Screen does not work
Camera function does not work
GSM Failure
WCDMA Band 1
WCDMA Band 2
9. Schematic Diagrams
10. Concept and Main features
11. Block Diagram
12. Component and Location
13. Dis assembly and Assembly
14. Trouble shooting
15. Calibration
download and enjoy 22.2 MB
http://www.4shared.com/office/6tdZOd1J/I9000_Technician_Manual.html
http://www.mediafire.com/?or3hgpu1bvjf103
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
{
"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"
}
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.​

Any mirrors that do not reqiure signon?

skibbi_pl said:
Any mirrors that do not reqiure signon?
Click to expand...
Click to collapse
Nope, signing on is not a big deal actually, as a member it allows you to download anything else you need by searching that site and also upload what you want.
anyway..i will try to upload it elsewhere, as soon as i can sign up to them

thanks... Especially for the mediafire link
Sent from my GT-I9000 using XDA

madushan92 said:
thanks... Especially for the mediafire link
Sent from my GT-I9000 using XDA
Click to expand...
Click to collapse
you are welcome to it

Thank you
Thank you very much. I gave it a read and page 96,97 & 98 relate to component level information and is relevant to my question.
Although, I couldn't find a part number for the motherboard as a whole. May be I should provide more information about the problem I'm facing to help narrow things down.
After a pretty(very) bumpy ride, I noticed that the phone had switched off and wasn't coming back on. I assumed that I had damaged the phone. I put it on charge and a few hours later, to my surprise, it came back on. Ever since, I've been facing these problems.
a. Phone consumes battery whilst in switched off mode. I'm talking ~40% drop overnight.
b. 2g works only via 64K SIM cards. Phone disconnects from the network when I set it to 2g when on a 32K SIM.
c. Wi-Fi doesn't work - I get the obtaining IP address error. From the battery usage stats, I can tell that the Wi-Fi unit is drawing power.
Folks at the Samsung service centre suggested that I replace the entire motherboard. It costs ~ £120, which is a little too steep and much to invest on a 2 yr old phone. Spares and peripherals usually carry a nasty mark up, which is why I'm trying to get one from the makers or others who are willing to sell it for lesser.
Edit: Stock ROM fixed the Wi-Fi issue.

vinu_h said:
Thank you very much. I gave it a read and page 96,97 & 98 relate to component level information and is relevant to my question.
Although, I couldn't find a part number for the motherboard as a whole. May be I should provide more information about the problem I'm facing to help narrow things down.
Click to expand...
Click to collapse
Pages 8 to 16 gives the part and code numbers, although, these are not detailed, without them, you will have a hard time trying to buy online...best thing to do is let a technician at your end, check it and let him tell you what parts you need and than you try and purchase them online with part numbers
from what you are saying it could be a simple cracked board ...that may need some reconnection as it is obviously shorting causing power drain even when in OFF mode .
off course technicians can be tricky, so may need to find someone you can trust

xsenman said:
Pages 8 to 16 gives the part and code numbers, although, these are not detailed, without them, you will have a hard time trying to buy online...best thing to do is let a technician at your end, check it and let him tell you what parts you need and than you try and purchase them online with part numbers
from what you are saying it could be a simple cracked board ...that may need some reconnection as it is obviously shorting causing power drain even when in OFF mode .
off course technicians can be tricky, so may need to find someone you can trust
Click to expand...
Click to collapse
You're right. Finding a trustworthy technician can be tricky. Even when I do, they won't offer any kind of assurance. £120 with a guarantee is starting to appear more attractive than £50 with none.
I was lazy. It's listed on page 9. This must be the part number of the motherboard - QMP01 A/S ASSY-PBA MAIN_GT-I9000B,BRAZ (SVC) GH82-04996A
Online search of that part# doesn't help in anyway whatsoever.

Where is the internal memory located on hardware
can anyone tell me if internal memory of the phone ( where the recovery, rom , bootscreen and so on ) is located in MoviNand piece of hardware on the motherboard ?

laurentiudll said:
can anyone tell me if internal memory of the phone ( where the recovery, rom , bootscreen and so on ) is located in MoviNand piece of hardware on the motherboard ?
Click to expand...
Click to collapse
[Tutorial][A.I.O Rescue & Recovery] My Secure Digital (SD card) Storage
look for the Embedded SD or iNAND as shown in the image
Check this out! Links to useful Guides and " Banned " Documentaries ​

thanks for the file, great to have around for reference