yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] AdamOutler:
it's unlikely unless we can get the manual for the OneNAND. I have not been able to find it. We need to know the entire communications protocol and the NAND's I2C address.

This method would require more hardware then our current method, which requires tools and a wire.. However, once perfected, it would be possible to have a sort of "jig" and I use the term loosely.. it would be a circuit board hooked to the main-board with a reprogrammable i2c compatible microchip on it, awaiting some sort of interrupt and upon receipt, it could send a pre-programmed data-gram to the OneNAND which would corrupt one of the first few bytes in the IBL+PBL partition.... Or it might even work for the DRAM as well if timing can be done properly.

This is not even a thought right now. Without a manual, it's not even realistic, so we should not discuss that until we get a manual.

We could... However, the problem is not in repartitioning, it's in the commands that Heimdall is sending. It's heimdall's ability to access the Odin3/Loki protocol.

We don't need to worry about safety during flashing anymore once this mod is applied. I mean, sure, it would be great and all.... But, like... why? I gots mine lol...

There's no reason to rewrite the Odin protocol. It's a good protocol. It's susceptible to bad data and operator error.

Repartitioning without writing bootloaders is a cause of bricking.. writing a PBL without an SBL is a cause of bricking. Writing a mismatched PBL/SBL combo is a cause of bricking. If you'd like to rewrite the SBL for these reasons, then that would be the way to do it.

It looks pretty much like the PBL calls a memory location of the SBL in DRAM and if that memory location is the start of the file, then it begins the SBL... If that memory location is not the start of the SBL, it ends up hard-bricked. Theoretically, we could reduce bricking by replacing the start of the SBL with a ton of jump-to instructions to the start of the SBL code.... Just thinking.

Operator error is the number one cause of bricking... hardware problems are number 2.

There COULD be more checks... I'd like to see a new primitive bootloader with support for certain key combinations to call IROM code to enter the IROM download mode... if Samsung would update all phones with this, there'd be no bricking problem.

I know right? But, try using the JTAG points with all the pads ripped off. that's like 7 wires to connect to pads the same size.. with about 3 wire spacing between each... that was the most rediculous soldering I ever did.
[Captivate Android Development] ronkoni:
can "wire glue" be used instead of using a soldering iron?

http://www.wireglue.us/
[Captivate Android Development] Rebellos:
I get the idea. But still no even single proof for access to oneNAND through I2C. Most likely it's not possible. Access to oneNAND from I2C would probably mean access to oneDRAM and DRAM aswell (they are all in one fusion memory chip, noticed it yesterday, lol)

You're right, if they only implement few additional instructions in PBL and IBL there wouldn't be the need of developing such mod.

I think it can be used. But would be good to have some solvent for it, in case you spill too much and do short circuit.
[Captivate Android Development] popfan:
I am not sure if this is kinda what you are looking for, but it may help out.

http://www.datasheetarchive.com/oneNand%20flash-datasheet.html

This has a bunch of basic info to really technical stuff on it about OneNAND with pre-programming info and other stuff like that.
[Captivate Android Development] AdamOutler:
Ok... after reviewing that, I realize that there is no easy way to perform an i2c one-nand corruption.

It would involve putting the Application CPU into I2C slave mode, then utilizing it to corrupt the OneNand... I don't know enough to do it as it would involve basically programming in assembly over i2c. The dream can still stay alive though.
[Captivate Android Development] midas5:
There are no master and slave devices on an I2C bus. For an individual transaction, one end is the master and one is the slave, but when a device is not actually sending, any other device can send.

I have not read the onenand manual, i just heard it was possible, but not sure if i should trust the source ;-)
[Captivate Android Development] midas5:
It should work on the tab.

Remove the battery.

Insert it again.

If you plug the tab via usb cable, which usb ids do you see, if any?
[Captivate Android Development] AdamOutler:
To clarify, plug into a LINUX computer... then type lsusb. This should say Samsung something...

If it does, you're ready to rock.
[Captivate Android Development] DemonWav:
I accidentally threaded one screw, they are so small it was one twitch of my wrist and it was threaded. Now it is impossible for me to get the screw out. I don't have a screw driver head small and flat enough to get it, they are all pointed and don't grab onto anything because its threaded. I guess I'll look for some different bits that might work better.
[Captivate Android Development] bulletproof1013:
So you stripped the head of the screw out?
[Captivate Android Development] DemonWav:
It's just barely stripped out enough that the bit I currently have won't catch it anymore. I need to get a smaller bit.
[Captivate Android Development] AdamOutler:
If you're having problems this early on, you might want to enlist some help.
[Captivate Android Development] bulletproof1013:
Did u use a jewelers screwdriver set?
[Captivate Android Development] nubecoder:
I've been using this screwdriver set for a couple years now, maybe not the smallest around, but suitable for most electronics related stuff I've come across.

I like the grip, since most precision sets don't have much to hold onto, this one works well for me.

=]
[Captivate Android Development] jgaviota:
Thanks for your responses, I don't have the Tab with me right now, I'll see what I can do during the weekend and post back.

Again Thanks to everyone working on this, I'm an electronics engineer and I know how difficult all of this really is :D

Superb work all of you

(And I really need a way to get some free time!!!)
[Captivate Android Development] DemonWav:
I don't plan on doing any modifications myself, I was just going to open it up to show my friend what it was in the real world. He said he wanted to see the real thing to compare to the pictures, but I accidentally screwed it up. No big deal really.
[Captivate Android Development] jgaviota:
Ok, I went to pick up the Tab

In the repair center they didn't even open it much less try to JTAG revive it.

One question, do I attempt the mod before trying lsusb?

I'll re read all the pertinent threads before destroying this thing :D

I'll set up a Linux box here asap.

Another question: Is there a cheap JTAG box capable of fixing the Tab? I live in Guatemala Central America.

Thanks again!
[Captivate Android Development] AdamOutler:
Its a tab? We don't have a mod for a tab yet. What you should do is hope you bricked it in a s5pc110 operational state. This will allow you to simulate unbrickable mod and run the app.

I think I can JTAG it if you would like. Send a pm.
[Captivate Android Development] sixstringsg:
Hey Adam, how much would you charge do do the mod on my phone? I have no soldering skills...
[Captivate Android Development] kuraijay:
yeah also want to know how much you would charge cuz pictures arent that great so i dont wanna mess it up
[Captivate Android Development] AdamOutler:
I'm charging $30 + a return UPS shipping label. I don't trust USPS in my area, UPS is great, but there is no UPS store.

Let me get some better pictures up.... It will be a little bit.
[Captivate Android Development] AdamOutler:
I think that's actually about as good as the picture can get. I did another one just for you.
[Captivate Android Development] matejcz:
re:

Hi, this tutorial is the best one. I've just bricked my Captivate - it can't boot...

I want to apply this mode, but I'm little confused with tutorial pictures...

On this picture:

First I must remove xOM5 resistor - the green one.

Then connect wire to active side of removed xOM5 pad - the green, and then connect wire to active side of xOM3 - green one.

Am I right?

Thank you for help!
[Captivate Android Development] AdamOutler:
Yes. Its that easy.
[Captivate Android Development] fritzgerald:
Holy Cow! I'm OK with soldering and I have a spare phone that I figured I'd give a go on...

I opened the phone... took out the board... saw the size of the area to work in... put the phone back together and started counting pennies to send it to Adam.

:x
[Captivate Android Development] bulletproof1013:
Its not that hard. (thats what she said)

Sent from my unbrickable cappy *bam*
[Captivate Android Development] kuraijay:
so if we send it, do we send the whole phone or the board
[Captivate Android Development] AdamOutler:
Its a lot more difficult to upload firmware and verify without the whole device. It's really not that hard because the glue on the board holds everything in place though.
[Captivate Android Development] abuthemagician:
Would the job be any easier with a hot air pencil and really nice pair of insulated tweezers?
[Captivate Android Development] AdamOutler:
Possibly, but the glue does require prodding of an unexpectedly rough manner for such a small device. The soldering iron works well.
[Captivate Android Development] abuthemagician:
Forgot about the glue part...
[Captivate Android Development] sconsylman:
AdamOutler

Hey man, quick question. Have a SGS4G with an authentic hard brick. Familiar with every soft and semi-soft brick trick online (hey, that rhymes), tried em' all.

So, a hard brick.

Phone is broken down with clean access to the motherboard right now. I'm examining it against your pictures here and in the Galaxy Hack Pack (thank you very much!) and the layout is slightly different although it appears to be pretty much the same board. Here's some fancy online shots of mine (not taken by me).

Can't post links yet (google): ifixit.com/Teardown/Samsung-Galaxy-S-4G-Teardown

I was wondering if you knew which was the OM5 and OM1 resistor on this board?

Can't seem to find any schematics on the sgs4g. And just to verify, does this one wire trick allow the phone to be put into download mode directly? Maybe I just wasn't totally clear on it doing this or just allowing specific low level software access (below Odin or Heimdall), as I have sifted through so much information.

I'm certainly no electrical noob, but I'm also not Nikola Tesla either. Damn Samsung's lack of info.

I will take close-ups later today if it might be useful. Very much appreciate all the work you have done, great stuff! And the other developers too.

Thanks!

Steve
[Captivate Android Development] AdamOutler:
I could take a look and guess, but I won't be able to tell for sure without removing the processor. It will be a 1 in 4 guess with judgement to bring the odds down. I can't gaurantee anything without removing the processor and visually inspecting the device. I want you to know that.

I have not yet received a GalaxyS4G board, but if you'd like to send it to me, I can send it back with the processor/OneNAND removed and then you can "do whatever" with it.
[Captivate Android Development] sconsylman:
Understood. 1 in 4 are not good odds, eh? Well, just looking to fix the hard brick and have it recoverable for any more that I could incur.
[Captivate Android Development] thecheatiscool:
After reading through the thread, I'm confused. Do I connect the wire to the OM1 resistor or the OM3? The instructions say OM1 but someone asked if they were to connect the wire to the OM3 and they were told that they were correct. Sorry if I misunderstood something.
[Captivate Android Development] Smasher816:
"5. Connect the active side of OM1 resistor to the active pad on OM5's resistor pads."

Edit: I Didn't see the part about someone saying that OM3, was good. Better get Adam to answer this one.
[Captivate Android Development] AdamOutler:
You need to connect to xOM5 to xOM0(high) or xOM3(high). If you jumper 1 and 5 you will not be able to boot from OneNand, only MMC/SDcard. This is not proper operation

Don't fool with xOM1. Just follow the instructions in the first post.
[Captivate Android Development] Smasher816:
That quote about OM1 to OM5 was from the instructions in the first post...
[Captivate Android Development] thecheatiscool:
Yeah..I'm still confused :confused:
[Captivate Android Development] AdamOutler:
I don't know how that got there. Use the pictures. I modified the first post. You do not want to touch xOM1. xOM0---xOM5
[Captivate Android Development] thecheatiscool:
Thanks for clearing that up, I'll probably attempt this on my hard bricked captivate sometime this week.
[Captivate Android Development] rsx19:
Did I just see ios. Get outa here
[Captivate Android Development] thecheatiscool:
Nothing wrong with choices, haha.
[Captivate Android Development] ugothakd:
Hey...couldn't this possible used with arduino bootloaders? And be like a really-super-complicated arduino? Since, technically, your turning it into a development board?
[Captivate Android Development] AdamOutler:
You seem to have the concept of a development board... but the idea is that you can use it as a development board the way it is. Not with Arduino IDE.... We don't need Arduino bootloaders. We have download mode. You can write in C and compile for ARMv7 then upload via HIBL.
[Captivate Android Development] gh123man:
I did the mod. YAY. if anyone wants semi high-res pics let me know. one question though. i slipped and removed the OM2. the phone functions normally so far. (i bridged the reaming pads on the board) should i be worried about anything?

thanks for your hard work
[Captivate Android Development] AdamOutler:
Dunno... kept us posted on random reboots or shutdowns, poor battery life or anything like that.
[Captivate Android Development] 41LY45:
Me! Me!

Interested in doing the mod as well.
[Captivate Android Development] GGXtreme:
I'm interested in this mod, but I'm worried that my USB port might be physically damaged and need replacing. Currently, the phone doesn't boot normally (stuck at kernel screen) and can't boot into recovery. It can go into download mode normally, but is undetectable by Odin or adb on any computer. It also doesn't charge the battery: if I plug it into the wall charger or a USB connection, the battery charge loading screen appears, then the screen flickers, the capacitive buttons light up and the battery screen gets this weird gray halo effect. Aside from the USB not working, the phone used to work fine until a bad CWM kernel flash—even the charging issue didn't occur until after this flash, so something must have gone seriously wrong. I took the phone apart and noticed that one of the microUSB port's connecting pins is much darker than the others: possibly burnt out? Is it safe to assume the microUSB port is damaged and needs to be replaced first?
[Captivate Android Development] AdamOutler:
If the phone boots, it's not bricked. You will want to get a new USB cable first. Use Linux and try ModeDetect and Heimdall One-Click.
[Captivate Android Development] GGXtreme:
Thanks for the response. It doesn't boot, it only gets to the kernel screen then freezes. Tried new USB cable, different USB ports, different computer—no recovery mode, no USB detection at any stage including download mode and no battery charging. It's positively either damage to the microUSB port or damage to the mainboard preventing the microUSB port from working. I was hoping to narrow it down because a physically damaged mainboard probably means this mod won't help, and I'm not sure if I'd actually be able to replace the microUSB port myself. I do know that the wifi radio was dead before any of this happened, so I suspected mainboard damage, but I'd like to be sure. I'll still give Linux a try when I get the chance.
[Captivate Android Development] gh123man:
okay so an update... i had to redo my soldering job. its fixed now. when i do lsusb it use to say Google inc. now it says Samsung :) which i am going to assume that is exactly what it should! so its safe to say the mod is most likely working. now for the bad news.

when the screen shuts off sometimes i cant wake it back up.

now i know it isn't shutting off because i was on a phone call for an hr. and the screen wouldn't turn on when i was done.

any ideas?

this is not my primary phone. if you would like me to try something. i would be glad to!
[Captivate Android Development] Jorge330823:
sorry if this question has come up but is this possible for nexus s 4g yet? and if so about how difficult is it? (i am pretty good with a soldering iron. i resurrect dead amplifiers and speakers but amps have pretty big boards)
[Captivate Android Development] funkym0nk3y:
can any1 clarify this, are the values of xOM5 and xOM1 are same ?

m asking this because while reapplying the mod, i mistakenly wiped the xOM1 resistor and put it somewhr and forgot, however i have the xOM5 resistor is with me, asking if its good to replace xOM5 with xOM1.

Also without the mod applied (no jumper from xOM5 active pad to xOM0 active pad) with xOM5 and xOM1 wiped off, my phone still gets detected in Unbrickable debug mode, can any1 explain this a little bit ?
[Captivate Android Development] AdamOutler:
A different resistor is better than no resistor. A straight solder bridge is better than no resistor. Anything is better than no resistor

Without power or ground applied to the pins on the processor they wildly flap about and act erratically. They will cause erratic behavior and the system will randomly hang.

Do anything you can to get the pads connected. If you have an extra resistor, use it. They should all be the same value on our phones anyway.
[Captivate Android Development] wesbound:
Message deleted. Sent PM instead
[Captivate Android Development] lildoggs:
Hey AdamOutler Thanks for doing a great job on my phone. It's been working great. If i wouldn't have done this mod my phone I would have bricked it 3x's already. Great job.
[Captivate Android Development] thecheatiscool:
I agree, he sent it back to me really fast and I don't have to worry about bricking it anymore.
[Captivate Android Development] flipbwoi:
Hey Adam, I've been reading up on this topic ever since I bricked my i896 a week ago. I was going to get it Riff Box fixed, but I figured if I'm going to spend close to $100 that this is worth a try. I know mines a complete brick (black screen) jig doesn't work etc.

Only thing is the pictures are a bit blurry and I don't want to solder to the wrong points. So here is my photo before I do it. Thanks again for all the hard work you and the team have done. And when you say remove xOM5, i need to actually remove it, not just solder the wire with the resistor still in place?

You can use this photo too btw in place of the one in the first post if you want, the resistors are more clear.
[Captivate Android Development] connexion2005:
You need to actually remove xOM5 and bridge the pad to the resistor as you have documented. Do not remove the processor...LOL.
[Captivate Android Development] flipbwoi:
Lol, okay I know it was probably a dumb question but I had to ask it since some of the photos he had didn't have the processor so I got curious.

Okay so remove xOM5 resistor, then solder the left side of that to the top side of xOM0, but do not remove xOM0? That sound right?

Sorry for any questions that seem simple, I just want to do the check and check and then check then proceed logic.
[Captivate Android Development] connexion2005:
That is correct. No dumb questions, you are correct in the fact you DON'T WANNA SCREW THIS UP. A wrong move could make the board never work again with JTAG or any other recovery.
[Captivate Android Development] flipbwoi:
Okay then just need to find my fine point solder tip and will give this a shot.

Oh and I just realized it was your video I watched on YouTube to take apart my captivate, thanks for the help in both cases now lol. I will post my results once I get it done.
[Captivate Android Development] AdamOutler:
I included pictures with the processor removed because I overdocumented this particular mod. It was the first one ever. I refer back here whenever I do a new device. I don't want to remove these pictures. Maybe ill reorganize.
[Captivate Android Development] flipbwoi:
Ah, yeah thats why I was at first sketchy about doing this when I saw the processor taken off lol. But now I understand, once I get my fine point solder tip I'll get to work on mine and hope that I don't screw it up haha. I'm on my iphone and miss the android....
[Captivate Android Development] goob1284:
Alright. I did read a lot on this topic. And I wanted t know if there was a video on this? Some of the pictures I can't see too well cause they seem blurry.
[Captivate Android Development] isa.ahmed:
sorry, but this realy hard to understand

as what is XOM5 and what i need to do it hard to get

sorry for this. i read it more than 100 time but did not get it
[Captivate Android Development] AdamOutler:
You might not want to attempt this then.

You remove the xOM5 resistor then jumper the active pad to the active pad of xOM3 or xOM1
[Captivate Android Development] AdamOutler:
they're blurry because they're small. A video will be far less clear. I tried and all you could see is me doing things to something. It didn't work.
[Captivate Android Development] isa.ahmed:
there is no step by step instaltion for new user?
[Captivate Android Development] btyre:
Is there anyone in UK that can perform this mod for me?

USB cable fell out whilst flashing with ODIN, now I can't even get to boot.

NVM, probably going to send it to MobileTechVideos
[Captivate Android Development] isa.ahmed:
i was trying to msg MobileTechVideos

but he never reply me..so how if i will send it?

am not sure if i will or not.
[Captivate Android Development] jmtheiss:
I wouldn't be too discouraged if Connexion2005 (mobiletechvideos) takes a little while to reply - my guess is that he's a busy person and that it will just take a little time.

This modification is a great modification, however, it is also something that I personally wouldn't recommended for anyone who doesn't have a good level of experience with soldering and small electronics. If you are really interested in having this done, keep trying to contact Connexion2005 or AdamOutler, or see if you can find a person who you are certain is highly skilled with soldering small electronics and have them do it.

I'm only giving you this warning because the small scale on which this modification takes place leaves very little room for error, and a hardware modification like this is not exactly new-user friendly.
[Captivate Android Development] isa.ahmed:
and this method, dose it need any kind of other hardwer?
[Captivate Android Development] goob1284:
Alright I'll try this soon. Thank you!
[Captivate Android Development] isa.ahmed:
can i trust this MobileTechVideos??

as this is the only one i found do fix it
[Captivate Android Development] Taderich:
I sent my Captivate to MobileTechVideos and the order was completed very quickly and worked quite well. Very happy with the service. I now have a fully functional an unbrickable Captivate!
[Captivate Android Development] isa.ahmed:
when you say unbrickable ....do you mean it canot be break any more?

in other word, can it ne break as the 1st time u did or not after the fix?
[Captivate Android Development] nimper:
What Unbrickable means is that you can always restore it to download mode if something bad happens.
[Captivate Android Development] isa.ahmed:
mmmm..

sorry...still did not get it.

i brik my phone by using ODIN and flash the bootloader

if i did this after the fix,,,will it be break...or it will be break proof :)
[Captivate Android Development] AdamOutler:
UnBrickable mod can correct any firmware based problem you can possibly cause on a device. If there is hardware damage that it won't work. This mod is very effective.