yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab  Android Development] PriMarius:
Right now I do not need it, but recently do some more of flashing, so I had my thoughts.. :-)

This awesome mod removed a very weak point from our wonderful device,

and was made in the right Spirit. Highly informative thread to read how it was developed.
[Galaxy Tab  Android Development] ronpinoy253:
[RECOVERY] Confirmed Success!!!

I want to thank the amazing development that went into this recovery method. I have a Galaxy Tab 7" Verizon edition. I totally bricked it, stupidly soft bricked it (aka Yellow Exclamation with PC and Phone icon) and then proceeded to fully hard brick :rolleyes:

My hard brick symptoms:

Black screen (no matter what I did) when turning on the tablet. Tried recovery mode startup and download startup to no success. I could somehow flash roms to the tablet still as it was detected in ODIN 1.7 and Heimdall, but the only thing that would change no matter what ROM I tried would be that I would either get a black screen at turn on with a startup sound or a black screen at turn on with startup sound and capacitive buttons lit up.

Solution was the Unbrickable Mod. Following all steps I proceeded to remove the xOM5 resistor and then using a thin wire which I had electric taped and anchored to the top of the CPU? pad adjacent, I formed the wire carefully to make one end contact the top of the now removed xOM5 resistor pad (inward section closest to the CPU? pad) and formed the other end of the wire to contact the xOM0 resistor at the top end (section closest to the CPU? pad which is same side as other end of wire connected to xOM5 resistor pad). I used super glue (yes super glue!) to hold the wire in place at these two locations and then following the rest of the guide, I used the Resurrector software to get my tablet into download mode and then proceeded to use the DJ11 stock one-click recovery to flash a ROM onto the tablet.

All I can say is amazingly my tablet works now. Thanks so much for the hard work done to make this possible for us.

All flashing was done in Ubuntu operating system as Windows 7 does not like the Java based recovery software (Resurrector and one-click recovery).
[Galaxy Tab  Android Development] still_token:
i screwed up on doing this fix...the unbrickable mod went fine...resurection goes just fine...problem is i have a p1010 and being dumb and not paying attention i flashed the bootloaders with the p1000 one click recovery...how can i fix this? just want normal stock firmware
[Galaxy Tab  Android Development] AdamOutler:
use the resurrector again and flash P1010 bootloaders.
[Galaxy Tab  Android Development] still_token:
That's the problem..I don't know how to implement them..this is the first time I've used LINUX

I've rooted my phones, modded xbox 360's , ps3, WII, even my t.v. But for some reason I'm at a loss on this...I've been trying to figure out how to make my own one click with the p1010 stock firmware but I'm lost...I've messed it up to the point that it errors out because the pit doesn't match..can't even get the download screen any more after trying to manually flash with heimall..
[Galaxy Tab  Android Development] still_token:
So after tinkering with things I was able to get heimdall to flash the individual pieces of the firmware if I did them 1 by 1 but still a no go on boot..still can't repartition it errors out every time..is there a way to wipe everything and start fresh? Any chance any one can make me a one click with the p1010 firmware and bootloaders? Any help would be much appreciated..otherwise on a past ditch effort I will have to send it of for jag service..I thought unbrickable meant I could recover from anything lol
[Galaxy Tab  Android Development] AdamOutler:
Im mobile.. you can get the firmware from sammobile.com. you will need a new pit. Find the stock pit from a p1010
[Galaxy Tab  Android Development] alexgogan:
do you want me to make you one from my device going to replace the screen over the weekend, factory reset then root so can do it when am finished.. . ohhhhh and retrain the Fecken battery as well.

regards
[Galaxy Tab  Android Development] alexgogan:
if you still need it by the weekend pm your email and will upload the file for you.

regards
[Galaxy Tab  Android Development] still_token:
ok i have the stock firmware...unzipped all files loaded them in heimdall 1 by on and made sure all files corresponded ie: sbl = sbl.bin ....i have the stock pit file that was included from samfirmware with the firmware i downloaded i created a one click...problem is everytime it goes to upload the pit file it disconects and cannot repartition...im at a freaking loss here lol... i can make it thru a flash on odin as long as i dont repartition but the tablet wont boot..im guessing it's because i flashed the bootloader from a p1000 on the p1010...i know dumb rookie move lol.. any other ideas?

---------- Post added at 06:58 PM ---------- Previous post was at 06:55 PM ----------

Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna

http://www.glassechidna.com.au

This software is provided free of charge. Copying and redistribution is

encouraged.

If you appreciate this software and you would like to support future

development please consider donating:

http://www.glassechidna.com.au/donate/

Initialising connection...

Detecting device...

Claiming interface...

Attempt failed. Detaching driver...

Claiming interface again...

Setting up interface...

Checking if protocol is initialised...

Protocol is not initialised.

Initialising protocol...

Handshaking with Loke...

Beginning session...

Session begun with device of type: 0

Uploading PIT

ERROR: Failed to confirm end of PIT file transfer!

PIT upload failed!

Ending session...

ERROR: Failed to send end session packet!

Re-attaching kernel driver...

---------- Post added at 07:43 PM ---------- Previous post was at 06:58 PM ----------

now odin is screwing up...probably cause the cable disconnected during a flash...this sucks lol

<ID:0/007> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> P1010XXKPI_P1010XEUKPI_HOME.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/007> Odin v.3 engine (ID:7)..

<ID:0/007> File analysis..

<ID:0/007> SetupConnection..

<ID:0/007> Initialzation..

<ID:0/007> Get PIT for mapping..

<ID:0/007> Firmware update start..

<ID:0/007> cache.rfs

<ID:0/007> NAND Write Start!!

<ID:0/007>

<ID:0/007> Complete(Write) operation failed.

<ID:0/007> Removed!!

<OSM> All threads completed. (succeed 0 / failed 1)
[Galaxy Tab  Android Development] alexgogan:
can you get to download mode at all?
[Galaxy Tab  Android Development] still_token:
I can only get to download mode via unbrickable resurrecter.....
[Galaxy Tab  Android Development] AdamOutler:
use a new cable. Try again. You may have NAND failure.
[Galaxy Tab  Android Development] alexgogan:
Did not think of that actually
[Galaxy Tab  Android Development] still_token:
All this started after a hard brick...wouldn't power up so I did the unbrickable mod and used the wrong one click...nothing but a headache since
[Galaxy Tab  Android Development] still_token:
What would cause nand failure?
[Galaxy Tab  Android Development] alexgogan:
Like any writing to disk there can be loads of potential probs from cable disturbance, powers spike and few others as well

Could be galley faulty blokes swell
[Galaxy Tab  Android Development] still_token:
Is it recoverable via jtag?
[Galaxy Tab  Android Development] AdamOutler:
A NAND failure requires replacement of the NAND or the board. the board is generally more cost effective to replace given the complexity of soldering BGA form-factor chips.
[Galaxy Tab  Android Development] still_token:
just a quick update...playing around with the tab out of desperation i tried adams one click for the p1000... now i can power up device with an endless bootloop of the samsung icon...i can make the device go into download mode by pressing volume down and power...i can get to a recovery mode by pressing volume up and power...but im back at square one...wrong bootloaders yes i flashed them from the p1000 and obviously the wrong firmware as im on a p1010...any suggestions? cable must be good and the nand must not be fried...come on guys we can revive this thing lol
[Galaxy Tab  Android Development] still_token:
adam your one click for the p1000 works like a champ... can you make one for the p1010? please :-)
[Galaxy Tab  Android Development] AdamOutler:
I don't do that unless I have a device to work with. Can you make a heimdall tar.gz and verify it works?
[Galaxy Tab  Android Development] alexgogan:
If you download the gb firmware that might be able to help

http://xdaforums.com/showthread.php?p=17795474

Has the link also did you try emergency firm ware restore on keis?
[Galaxy Tab  Android Development] still_token:
Didn't know there was such a feature
[Galaxy Tab  Android Development] alexgogan:
Yep handy for cases like v this hehehe one of the few things it is good for.
[Galaxy Tab  Android Development] still_token:
Yeah that didn't work...never backed it up before so no code...I think I can near it of I can get it to flash normalboot.img it fails every time
[Galaxy Tab  Android Development] alexgogan:
Feck

Did you try flashing gb for the 1010 yet
[Galaxy Tab  Android Development] still_token:
Yes I did
[Galaxy Tab  Android Development] still_token:
Like I said it fails while flashing normalboot.img
[Galaxy Tab  Android Development] AdamOutler:
you need to repartition. Likely you have repartitioned in the past and now the boot.img won't fit there anymore. Otherwise, if you are using a matching pit and boot.img and repartitioning, you have hardware failure... nand/emmc failure.
[Galaxy Tab  Android Development] still_token:
But why would it write your one click with no problems but on it's native firmware it basically gives me the finger? That's the part that had me scratching my head...could it be the unbrickable mod for the

P1000 doesn't work the same as the p1010? Could that cause problems?
[Galaxy Tab  Android Development] AdamOutler:
no. you need to specify repartitioning and use a valid partition table for your device's stock firmware.
[Galaxy Tab  Android Development] still_token:
I have done that...many times in fact...just doesn't work
[Galaxy Tab  Android Development] alexgogan:
What happens and what error out put do you get
[Galaxy Tab  Android Development] aleg_81:
hi guys!!

hi guys!

I would help you! :)

the theory:

this is the final work!

This Debrickable mod (and mod Resurrection) works fine!

what you need:

1. a good friend (thanks Ivan DZ)

2. great hands... (or friend's ones!)

3. a tuning wire like this (enamelled copper coil)... thinner may be better but warm deforme it faster

4. remove the resistor xOM5

5. bridge xOM5 to xOM0

6. then mount your G Tab

7. run the Ultimate UnBrickable Resurrector using Ubuntu

8. connect G Tab to pc

9. in UUBR appears "S5PC111 detect"

10. click "Perform Resurection" in few seconds your Tab is in Download Mode (

in pc's software appear the usual pic "download mode" that appear also in Android Devices, the Android that works in yellow, BUT in Tab it may not appear, in mine only the flash turned on and the screen was off!

11. now your Tab is in Download Mode! Do not disconnect the Tab! The Download Mode is supported by software, if you disconnect the Tab it lost the Download Mode!

12. run Heimdall One-Click

13. click "Flash"

14. re do points 10-13 until Heimdall One Click allow to check "Flash Bootloader"!

15. check "Flash Bootloader"... wait...

16. Here you are your resurrected TAB !!!! (it's running stock GB Rom!)

special thanks to AdamOutler

and to Ivan DZ!
[Galaxy Tab  Android Development] AdamOutler:
^^ That is in the first post. Why write the guide again?
[Galaxy Tab  Android Development] aleg_81:
Hi Adam,

i write an other guide simply because I add pics... and explain in other way some steps that for you are very simple but not for all is the same! I read your guide but i didn't understood very well so i suppose that other people may have a little help...

if it is a problem i can remove it...
[Galaxy Tab  Android Development] caliginous:
Has anyone in London, UK managed to do this?

and would they like to have a go at fixing mine for some cash? I haven't a clue about soldering!
[Galaxy Tab  Android Development] terminal 7:
done

Okay so after pondering a while I finally went head and tried the mod.

Soldering is very small here and I have experience but still found it fairly tricky. A good magnifying glass helps.

Anyway after several flash attempts with heimdal and Odin and even using recovery (I got a decent recovery to flash using Odin) I still not quite back in action.

It boots but boots o over and over .. I did manage to flash a rotohammer firmware which booted but I have no touch screen.. this is one thing I was concerned about anyway since the developer board has no touch screen and that's now what my tab is discovered as in device manager.

Anyhow even with roto firmware it only stays booted a minute then rebooted again.

May be my tab was beyond repair .. ill try some more stuff in give hours time after another recharge.

Before I go just gotta say huge thank you for this mod hardware and software as its by far one of the most in depth fix jobs I ever tried from the xda pages.. brilliant work.

.

.
[Galaxy Tab  Android Development] alcuin:
If it boots over and over, try booting into recovery, then wipe data and cache. That fixed it for me.
[Galaxy Tab  Android Development] AdamOutler:
Yep. You should really use heimdall. It works better. Heimdall is a total flash. Rotohammer is a partial.
[Galaxy Tab  Android Development] prabhu1980:
Adam I would like to sumup what you said in a old computer language.

I am completely outdated from the 2000.

What you are trying to do is boot thru external device.

Like when the Hard Disk is new / corrupt we use an external device to recover it connecting it as the slave.

I used to change the jumper settings to pull into slave mode so he listens to whatever his master says.

You use a wire instead on the jumper.

You use programs to flash the bootloaders.

I remember biting my nail flashing CMOS..

Good work Adam. Request you to do the same for Galaxy Note.

I have linked the JEDEC EMMC standard for you which gives more clarity to you.

Coz i am a chemical engineer, i donot understand many technical words...http://xdaforums.com/attachment.php?attachmentid=1092056&d=1338275277
[Galaxy Tab  Android Development] mo-mo:
hi guys

need advice tried the mod a few day ago.. soldering was done correctly but the soldering pad on the motherboard came up.. is there any was to fix this?

---------- Post added at 02:38 AM ---------- Previous post was at 01:39 AM ----------

thx bud...
[Galaxy Tab  Android Development] alexgogan:
Hi ya,

What do you mean by came up?
[Galaxy Tab  Android Development] Haktar:
well I had one hell of a day yesterday, I was following your tut, everything was going well removed the xOM5 resistor fine then I had to go help a customer, in the time I was gone my college did a dc jack on a laptop, for that he put the temp up quite a bit on the soldering iron, i came back and didnt check and i lifted the non grounded bad of the xOM5 resistor, i don't supposes there's any work arrounds or alternative points?
[Galaxy Tab  Android Development] ohlala:
Gtab p1000

Hi all,

Please can you help me to save my GTAB P1000 GSM Version from SFR France.

Voila, the problem is my TAB displays a message saying that "the load (charge) is suspended from the battery because the temperature is very high or very low" tab works very well but does not Chagre. So I changed the battery myself, but no result. As it is no longer under warranty. I do not know what to do. After several hours of searching on the net I came across post.

I wonder if I can apply the procedure UnBrickable Mod And Software Resurection on my P1000 for a solution or you have another idea to save my TAB P1000….

Please HELP me and very sorry for my bad english…

What i do already...

1. Try with a new battery

2. Hard reset

3. reinstall a new version '(shipped version)

:crying::crying::crying::crying:
[Galaxy Tab  Android Development] priyana:
could be bad sensor?

If that is the case, the new battery won't help.

Unbrickable mod is not for this type of error though.
[Galaxy Tab  Android Development] ohlala:
Thank you very much for your answer, but you have any idea for sensor problem..

Thanks again...
[Galaxy Tab  Android Development] karmacoma7:
Thank you, mr. Adam for a new hope.

I did the mod.

The tab lights the buttons below the screen when connected to pc.

windows said unrecognized device - no prob booting ubuntu...

Resurrected under ubuntu

flashed under ubuntu, incl bootloader

still the device doesn`t start -

after flashing - i`m trying to power it on - it still behaves as a debug board meaning lights the buttons, and that`s it.

Can you kindly help ?
[Galaxy Tab  Android Development] ceemamhere:
Hi All!!

Thanx Adam for this MOD. I have a GTp1000 and got it hard bricked.. ive done the hardware mod but i have a problem with ressurector on step one. It detects S5PC110 and after clicking download i get this...

S3C64XX Detected!

=> found device: bus 003, dev 017

=> loaded 1310720 bytes from /tmp/ceeHeimdallOneClick96951B6C/UnBrickPack/Sbl.bin

=> Downloading 1310730 bytes to 0x40244000

=> Data checksum f37e

=> usb_bulk_write() returned 1310730

Modified SBL Injection Completed Download Mode Activated.

and on top i now have Device not detected Device not found. Can someone please help me as im at wits end and i cant live without my tab :((
[Galaxy Tab  Android Development] ceemamhere:
Same Boat

Hey,

Did you manage to solve your issue, if so what did you do as im in the same situation and getting help is not easy here... :crying:
[Galaxy Tab  Android Development] priyana:
I am a nosey busy body.

But I will try to help here.

You can find that fella's post. (click on his handler name and select "find all post by ..")

A day after he said he run into this, he posted this:

http://xdaforums.com/showthread.php?p=30024112#post30024112

that seems to be his workaround.

Your case may be different.

In your last post you seems to have download mode activated,

you should then flash a complete rom on it, for example the GB-stock-safe-v5 from overcome.

(Disclaimer: I have never performed unbrickable mod)
[Galaxy Tab  Android Development] lucasbasso2:
erro

I need help, after the procedure completed when I go back to old rom it hangs in the odin SetupConnection this so the more hours. how to proceed
[Galaxy Tab  Android Development] matrixcore:
Botched unbrickable mod

hi, i've managed to botch my mainboard while attempting unbrickable mod. i would like

by i combination of different factors, i've managed to rip off the whole solder pad (non grounded side) where xOM5 must be soldered, the grounded side (the one facing the exterior side of the tablet) is ok.

AFAIK no other component has been damaged. i did not attempted further soldering after realizing what i did. The tab obviously won't boot.

the questions i have are:

1) could the tab be brought to life via JTAG?

2) if answer to (1) is positive, would the tab still boot normally even with xOM5 resistor missing?

Thanks a lot.
[Galaxy Tab  Android Development] J-ROCK:
I've had success with unbrickable mod , it brought it back to life. Once alive I found the reason my tab wouldn't work, my internal SD is damaged
[Galaxy Tab  Android Development] AdamOutler:
It will work just fine if you get download mode. usually 32% is where it stops to buffer though.. are you sure you didn't disconnect it too early? It can halt for about 2-3 minutes. If it halts for more than 5 minutes you probly have a bad NAND. But honestly, 32% halt means is buffering.
[Galaxy Tab  Android Development] rakionowner:
When you see this image you are in S5PC110 SEC SoC mode. When you see this mode you must proceed to step 2.

But, nothing happens when i clicked the download mode button, it only shows me "BEGIN RESURRECTION SEQUENCE" it takes a long time to proceed the system? .... Or i made a mistake at the first step "Without doing HARDWARE MOD"? , i did choose "GALAXY S" and the system gives me "the list". But nothing done, which point i've lost?
[Galaxy Tab  Android Development] supersincero:
This tools will work on a Galaxy Tab SGH-P100 Sprint ????
[Galaxy Tab  Android Development] openmatrix:
Can you make a guide to make galaxy tab 2 unbrickable?????
[Galaxy Tab  Android Development] mythi:
galaxy tab 2 is semi not-brickable !!
[Galaxy Tab  Android Development] openmatrix:
why????:)
[Galaxy Tab  Android Development] mythi:
Because there is no way to hard brick it exccept damging your emmc and ticking repartition in odin !!!
[Galaxy Tab  Android Development] openmatrix:
Good news:good:.Thanks for the information:cyclops:
[Galaxy Tab  Android Development] AlbioB:
I have a P1000 that suddendly stopped to turn on. It's stuck on S5PC110 mode.

I followed this guide (software part), and I flashed bootloader too.

Heimdall completed the flash sequence with no errors, but the device still reboots in S5PC110 mode.

I flashed again and again almost 10 times, but I get no results. The device still reboots to S5PC110 mode.

Maybe internal memory is damaged? It sounds strange to me since I get no write errors.

Thanks for your advice.
[Galaxy Tab  Android Development] ildar_prophet:
+1 for damaged NAND. It's so pity heimdall cannot read NAND, just write!

Sent from my PIPO S3/CM 10.1 ROM by Oma
[Galaxy Tab  Android Development] Trekeyus:
Sounds like your NAND became WOM write only memory. Never a good thing.
[Galaxy Tab  Android Development] ildar_prophet:
First off thanks a lot to [MENTION=3409868]F50+[/MENTION] and [MENTION=3682533]AdamOutler[/MENTION]. You made it possible for one brick to get back to life!

Part 1. Hardware.

I ironed the jumper and smdk-usbdl64 restored the bootloader.

My jumper wasn't tiny so I got rid of it. But I didn't put resistor to its place. The tablet works without it for 4 month already.

Problems related:

Slow power up (need to hold Power for a couple of seconds, maybe two or three tries to start up)

Charging doesn't start automatically when plugged in

No problems found besides above.

(still thinking about putting the resistor back)

Thanks a lot again!
[Galaxy Tab  Android Development] ildar_prophet:
Part 2. Software

One issue with it is that Resurrector crashes with exception.

Another one is: it is unnecessarily toooooo biiig!

As I understand, the only thing we need is restored IBL+PBL and SBL. After that a user can flash a stock ROM or something of the kind if required.

Again, thanks a lot! :cowboy:
[Galaxy Tab  Android Development] Yayan.F:
whether this modification way for samsung P1000 only?
[Galaxy Tab  Android Development] ildar_prophet:
The mod requires soldering a fuse to a particular place of the circuit. Do you think that you can find similar circuits in other devices?

Though there's one such device: the pure Korean analog of P1000 by ... AnyCall (OEM ed) I think... Don't remember the exact model.. I didn't look inside but 80% that the circuit is similar.

Sent from my PIPO S3/CM 10.1 ROM by Oma
[Galaxy Tab  Android Development] Yayan.F:
Thank's sir for information....

My device is p3100,ok I'll try on my device.

hopefully not happen anything on my device.and also ready to accept the risk for a better development and gain valuable knowledge.

One once thank you very much.
[Galaxy Tab  Android Development] ildar_prophet:
That seems to be a very bad idea. Different SoC, different pins etc., etc. You have a very tiny chances to find the pin that does the Unbrickable job.
[Galaxy Tab  Android Development] Yayan.F:
That risk is curiosity. everything must be try and will know.

But I'll think twice to do it.

Thank's a lot guyz...