Database Develop

Galaxy Tab bricked.. like really bricked

Ok guys, I feel this is just the end of the games... I was flashing back the Roto JME fw with the swype keyboard issue fixed that I have just made, when I accidentally unplugged the tab while starting flashing and in downloading mode.
Now all I get is a logo with a phone an alert symbol and a computer .
Windows as well as Odin see it, but I can't do anything, as Odin hangs on waiting for connection, or something like that.
Is there anything I can do?? Or do I really have to take it to the warranty? And if I will have to take it to the warranty will they see I have previously flashed a beta rooted image on it??
Here's what I am talking about
Please I need some help..
Thanks

Is there no recovery mode by buttons like the captivate? I hate seeing all the bricks
Sent from my SPH-P100 using XDA App

Its not bricked
heimdall close-pc-screen
should restart it
then power it off
then put it into download mode again using power + volume down
-d

Technomancer said:
Its not bricked
heimdall close-pc-screen
should restart it
then power it off
then put it into download mode again using power + volume down
-d
Click to expand...
Click to collapse
damn it says Failed to access device. Error: -12 .. I am on windows with latest version of heimdall ...

Segnale007 said:
damn it says Failed to access device. Error: -12 .. I am on windows with latest version of heimdall ...
Click to expand...
Click to collapse
Ops, it was the driver... damn windows ...
Solved btw.. I just realized I have lots of things to learn ... I have almost died of heart attack when I saw my tab stucked on that logo.. and now its back again..
Thank u falks

You need to make sure samsung kies are not running for sure unistall it and try it again

use odin. that is still download mode. might take you a couple of tries but works. i was in your shoes the other day

Everything is fixed thanks to Tecnomancer. Thank u guys
Sent from my GT-P1000 using XDA App

Could you please list the steps you went through in order to fix this - for everyone else's sake? Thx!
Segnale007 said:
Everything is fixed thanks to Tecnomancer. Thank u guys
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse

I've heard plenty of goofy stories about bricking devices over the years. You must conclude the following:
1.Flash your device in a locked room to avoid your wife/ child pulling cables or pressing buttons.
2.Don't touch anything while you're flashing. This is why many people that could help you will ignore you after reading about 'accidentally disconnected' wires - they just assume you're a moron not worth helping.
3.Read instructions carefully and write the procedure out in your own words if its your first time.
I've been flashing for years and haven't had a brick yet. Not crossing my fingers either because it has little to do with luck and much to do with care. In this way its a lot like making babies...

ftgg99 said:
2.Don't touch anything while you're flashing. This is why many people that could help you will ignore you after reading about 'accidentally disconnected' wires - they just assume you're a moron not worth helping.
Click to expand...
Click to collapse
Good advice.
My only semi-bricks (that involved an hour or two of trial and error to unbrick) resulted from some manner of overzealous cable unplugging.

zyborg said:
Could you please list the steps you went through in order to fix this - for everyone else's sake? Thx!
Click to expand...
Click to collapse
This is what I have done
Technomancer said:
Its not bricked
heimdall close-pc-screen
should restart it
then power it off
then put it into download mode again using power + volume down
-d
Click to expand...
Click to collapse

ftgg99 said:
2.Don't touch anything while you're flashing. This is why many people that could help you will ignore you after reading about 'accidentally disconnected' wires - they just assume you're a moron not worth helping.
Click to expand...
Click to collapse
Well, first of all thanks for ur nice words. Let me just say that I was about to disconnect another device from the hub where the GTAB was attached and flashing at that time, and yea, I accidentally unplugged the GTAB instead of the other device. I may be a moron, thanks, and thankfully not everyone believes themselves as god, which is a good reason to not help other people who are in troubles, even if for stupid things sometimes... If everyone were thinking like u we were probably still at the age of 1400 ...

Mate it wasn't a barb directed at you personally, but you weren't exactly careful were you?
I'm no god... but I've never bricked a device either, and I've been flashing for over five years now. To top it off I've almost never owned a device which could be taken back to the shop (90% of them come from other countries, not my local retailers). Perhaps this has taught me to be careful.
In any case, what I said holds true, and if you ask around I'm certain you find most will agree.

Dude, you have the best avatar! I can't keep my eyes away! Good luck, and don't worry about mistakes - that is one reason this forum exists.

Cannot start my Gtab after trying update JMC
...Hello everybody,
I am really worry about the fact my Gtab doesn't want to switch on after trying to flash it. I tried all process to put it on download mode or recovery but nothing work.
Do you have any idea about it ? Is there a specific procedure to switch on (eg : press power for 1 minutes + blablabla).
My provider doesn't want to take my Gtab in warenty before my contract is activated (the 4th of february).
Thank you for your answer

HELP, I have same problem, please explain how Hemidall can fix it?
Thanks
[email protected]

zyborg said:
Could you please list the steps you went through in order to fix this - for everyone else's sake? Thx!
Click to expand...
Click to collapse
I also had a semi-bricked VZW Tab, with the phone-triangle-computer warning graphic at start up. (I flashed a new boot loader, and failed to read the instructions closely enough. Either the file was incorrect for my device, or the drivers were not loaded correctly, but my tablet was borked.)
Using heimdall 1.3.2 (with the correct drivers, on a 32-bit windows system), I clicked the "close pc screen" option to clear the warning.
I then held the power button until it turned off, then held vol+ and power to re-enter download mode. Once in download mode, I used heimdall 1.1.1 to flash the zImage from SCH-I800-Stock-Rooted-2.3.5. My tablet (still unrooted, and still stock?) booted, but sat at the SAMSUNG logo for ten minutes or more. (It announced its progress, telling me periodically "five minutes remaining", etc.)
Once it finished, my tablet was revived. I will now follow the above advice and read all instructions very carefully, re-writing them in my own words to ensure I understand what I'm doing, before I try this again.

One year old thread......do you guys ever watch posting dates???
Sent from my GT-P1000 using Tapatalk 2

...like REALLY bricked
bumping this old thread in hopes that someone can point me in the right direction...
Got my p7510 (10.1" wifi retail) stuck pretty badly when trying to restore stock ROM coming from Overcome (it came rooted from ebay). From what I gather from the forums, seems like my bootloader is still locked.
whenever I attempt to flash a BOOTLOADER, PIT, or PDA using ODIN it connects, initializes, and gets stuck on "Flashing boot.img"
I think the recovery partition is damaged. When I boot using Power + Volume Down, I can get to the screen where you select recovery mode or download mode but recovery mode will not load. The screen flickers when I select recovery, but goes nowhere. Download mode works.
I tried using nvflash to force the right software onto it but I get error 0x4 (usb write failed).
There has to be a way to restore the stock bootloader and get this thing running again. Tablet will not boot android at this point. I have been searching the forums for about a week now, anyone have any ideas?

Unique problem, only see Rainbow Recovery and nothing else

I have spent the last 4 hours searching this forum and countless others. I installed a custom gb rom over my froyo base, which resulted in rainbows. In a panic I went into rom manager and tried to recover my nand backup and now I am stuck in a boot loop with a rainbow'ed clockworkmod.
The version I have is ClockWorkMod Voodoo lagfix Recovery 2.5.1xx in red text.
I have tried every combination listed and I can not get odin to see my vibrant. All I can make out is that every now and then I can get into the recovery menu. From there I can get to the download mode, however I can't read the menus.
All I got is I have to go down 7 to get to the mount & storage option, but from there I don't know where "boot to download" is...
I have looked all over for screen shots to help me narrow it down. Can anyone please tell me how to get to the "boot to download" option in CwM?
I'm at a loss. Also I have not found anyone stupid enough to be in my position so I couldn't find anything useful to help me.
Please help!

modfrenzy said:
I have spent the last 4 hours searching this forum and countless others. I installed a custom gb rom over my froyo base, which resulted in rainbows. In a panic I went into rom manager and tried to recover my nand backup and now I am stuck in a boot loop with a rainbow'ed clockworkmod.
The version I have is ClockWorkMod Voodoo lagfix Recovery 2.5.1xx in red text.
I have tried every combination listed and I can not get odin to see my vibrant. All I can make out is that every now and then I can get into the recovery menu. From there I can get to the download mode, however I can't read the menus.
All I got is I have to go down 7 to get to the mount & storage option, but from there I don't know where "boot to download" is...
I have looked all over for screen shots to help me narrow it down. Can anyone please tell me how to get to the "boot to download" option in CwM?
I'm at a loss. Also I have not found anyone stupid enough to be in my position so I couldn't find anything useful to help me.
Please help!
Click to expand...
Click to collapse
Sounds like you had the wrong bootloaders installed for the ROM you were trying to use.
I'm using Recovery v2.5.1.3. From the intial boot into recovery it's 7 down to the "advanced" menu then 8 down to reboot to Download mode (or up 2).
Hope this helps.

U need gb bootloader
Sent from my HTC Glacier using xda premium

elry567 said:
U need gb bootloader
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Yes, but he can't install it without getting into download mode.

I have had this issue. I wound up looking up CwM on google and seeing what the buttons were and using the pistures as a guide to were things were. I suggest doing this (IF you cant manualy boot into download mode.) And flashing to stock. Give yourself a fresh start. Rooting and installing CwM takes all of like 5 minutes, and if you have your contacts and such saved to your sim or google account you wont lose those (so you have nothing to fear).
I have personaly messed up my vibrant many times in wierd ways (such as this) and have found that it can be fixed allways, even without the unbrickable mod this phone is nearly unbreakable.

LMAO!! Unbelievable that in the past 48 hours 3 people posted either bricked or semi-bricked posts in the wrong section. You would think people would take their time in doing a little research in the proper sections.
In any case, here's your answer: http://forum.xda-developers.com/showthread.php?t=848737
And before you start criticizing my bashing response to your post. The link I just gave you is about 6-7 posts under yours. So again, if you actually took the time to do a little reading and research, you would've found this.

djquick said:
LMAO!! Unbelievable that in the past 48 hours 3 people posted either bricked or semi-bricked posts in the wrong section. You would think people would take their time in doing a little research in the proper sections.
In any case, here's your answer: http://forum.xda-developers.com/showthread.php?t=848737
And before you start criticizing my bashing response to your post. The link I just gave you is about 6-7 posts under yours. So again, if you actually took the time to do a little reading and research, you would've found this.
Click to expand...
Click to collapse
And not to mention that once again people don't take the time to notice that they are in the dev section not the q&a thread please lets get or stuff together peeps and stop being lazy!!!

djquick said:
LMAO!! Unbelievable that in the past 48 hours 3 people posted either bricked or semi-bricked posts in the wrong section. You would think people would take their time in doing a little research in the proper sections.
In any case, here's your answer: http://forum.xda-developers.com/showthread.php?t=848737
And before you start criticizing my bashing response to your post. The link I just gave you is about 6-7 posts under yours. So again, if you actually took the time to do a little reading and research, you would've found this.
Click to expand...
Click to collapse
Wow, talk about hate. I tried everything, including that link that you just sent me, I can't tell if it is in Download mode or not jerk. I've done this before and I rarely post problems unless I'm really really stuck.
All I see is rainbows on my screen for the clockwork recovery. It's not like everybody else's problem. Maybe you should take a minute and read my full post before making me feel lower than I already am about making a stupid mistake.
@jackdog
thanks for the numbers but I tried them and I got nothing except a reboot back into recovery. I tried 7 down, enter. then 8 down to what is suppose to be reset in download mode but it just resets.... I'm positive that I have that clockworkmod version, damn it!

modfrenzy said:
Wow, talk about hate. I tried everything, including that link that you just sent me, I can't tell if it is in Download mode or not jerk. I've done this before and I rarely post problems unless I'm really really stuck.
All I see is rainbows on my screen for the clockwork recovery. It's not like everybody else's problem. Maybe you should take a minute and read my full post before making me feel lower than I already am about making a stupid mistake.
@jackdog
thanks for the numbers but I tried them and I got nothing except a reboot back into recovery. I tried 7 down, enter. then 8 down to what is suppose to be reset in download mode but it just resets.... I'm positive that I have that clockworkmod version, damn it!
Click to expand...
Click to collapse
use android screencast to see behind the rainbows, and get yourself into download mode from there
http://code.google.com/p/androidscreencast/

thachosenone said:
use android screencast to see behind the rainbows, and get yourself into download mode from there
http://code.google.com/p/androidscreencast/
Click to expand...
Click to collapse
I've been trying for the last hour to get my computer to read my phone but the only time it sees something is when the vibrant is looping from the boot screen to another screen? ( it's rainbowed out) and then it repeats. I'm trying to download and install the drivers for the damn thing but I'm not having any luck.
Can any post post pictures of the clockworkmod recovery menus?

modfrenzy said:
I've been trying for the last hour to get my computer to read my phone but the only time it sees something is when the vibrant is looping from the boot screen to another screen? ( it's rainbowed out) and then it repeats. I'm trying to download and install the drivers for the damn thing but I'm not having any luck.
Can any post post pictures of the clockworkmod recovery menus?
Click to expand...
Click to collapse
ODIN!!! Get into download mode and either flash the bootloaders mentioned above or flash a froyo rom. The easiest way into DL mode is to pull battery, hold volume up AND down, plug phone to PC, re-insert battery.
If you flash bootloaders you won't have this problem again and will be able to flash both GB and Froyo roms (eclair too if you want). Check out the custom bootloader thread fpr info.

explodingboy70 said:
ODIN!!! Get into download mode and either flash the bootloaders mentioned above or flash a froyo rom. The easiest way into DL mode is to pull battery, hold volume up AND down, plug phone to PC, re-insert battery.
If you flash bootloaders you won't have this problem again and will be able to flash both GB and Froyo roms (eclair too if you want). Check out the custom bootloader thread fpr info.
Click to expand...
Click to collapse
I can't get into download mode because every screen I see is nothing but that rainbow garbage. I've tried every single button combo and odin isn't picking it up! Trust me I've tried all of that stuff. I need a frame of reference. I'm about to post a video so you guys understand what I see...

Unless you're HW locked (which I doubt if you're rooted) then manual-booting into DL mode should work. Do the following:
-Unplug phone. Remove battery, sd, sim.
-Set up ODIN on the PC, put the bootloader file in or the JFD, whichever you pick. If that's bootloader, please uncheck "Auto-reboot"
-Plug in phone with battery out
-Now while holding vol up and down firmly in and power, place the battery in the phone. Keep holding the three keys until ODIN recognizes your phone as a yellow COM port.
-ODIN. Let it finish. Reboot when it says success.
Goodluck, this should work- and I think DL mode is visible regardless of bootloaders. I may/may not be right on that.
---
You could also try adb. Just plug it in and type the command... 'reboot download' I think. Should get you in download mode.

Also to even humor you on the Download mode screen being rainbows, the odin would still recognise the phone. if taking out the battery dont work then . hold volume upkey (only) and plug in usb cord. if that doesnt work buy or make a jig

Seriously we did the whole rainbow screen thing for about 2 full months this past spring. DL mode will never be rainbow, only recovery. It is a safe mode seperate from most everything "we" do to the phone and other than hard bricking your phone you should be able to get into it. I have never heard of DL mode being "rainbowed".
First try to hold both volume keys and power. If that doesn't work try what Troy said and hold volume up and power. If all else fails call a buddy to come and read these directions that everyone is posting. Not trying to be smart but we really did go about 2 months with "rainbows" and I don't remember any bricks or anyone not being able to get into DL.

I've done all of those steps. I have read countless threads about it. I know exactly how played out it is. I have already ordered the damn resistor to make a jig. Nothing is working and that is why I am panicking. I can't imagine how many people pester you guys about the same damn thing. I'm sorry. I just want Odin to read my damn phone so I can upgrade the bootloader and be done with it. adb doesn't read the phone either, no matter what I do. Thank you for your help, if the jig doesn't work then it doesn't work.

*sigh*
If you haven't yet realized, several of the "old pros" on this forum have placated your lack of reading by posting the steps to solve your problem. If none of their solutions have worked, your phone is dead. Given your inability to find such basic information on a problem that has been thoroughly solved 200x over (Hell, I tried to make a thread with "rainbow" in the title and XDA gave me 900 similar threads on the problem) I suggest you try a simpler phone.
Maybe an etch-a-sketch.

kaintfm said:
*sigh*
If you haven't yet realized, several of the "old pros" on this forum have placated your lack of reading by posting the steps to solve your problem. If none of their solutions have worked, your phone is dead. Given your inability to find such basic information on a problem that has been thoroughly solved 200x over (Hell, I tried to make a thread with "rainbow" in the title and XDA gave me 900 similar threads on the problem) I suggest you try a simpler phone.
Maybe an etch-a-sketch.
Click to expand...
Click to collapse
You know what I don't seem to get is since when is this forum full of [email protected]? Seriously. I've put in all of my time to search and I did follow all the steps from what I have found and tried it over and over again. You seem to just want to bash people simply because you think they are a moron. You know what I get that, but I how posted repeatedly that I have looked over those forums and still have the same issue, and all I get is a stupid noob video on youtube. Real mature. The mod can close or delete this thread for all I care, I needed help and thanks to you and a few others on here for making things worse then they should have been. For those of you that posted helpful information and tried to help me thank you. I will leave all of you a thanks. I'm done.

You don't understand how exasperating it is for forum regulars to write long, painstakingly researched guides on how to solve common problems only to have a thousand yahoos ignore it, make their own thread, and then ***** when people get snippy that they completely ignored any and all forum guidelines in posting that thread titled "OMG How do I flash a ROM and how do I root and I can't get recovery to install!"
Your problem is not unique. If you're seeing a rainbow, you have not yet reached download mode. Take out the battery. Wait 5 minutes. Plug the ORIGINAL USB cable into your computer. Hold down BOTH volume keys and ONLY both volume keys while inserting the cable. KEEP HOLDING THE KEYS and insert the battery. Release the keys. You should be in download mode. If that doesn't work, you either did it wrong, or your phone is dead. Try it several times over until you're satisfied that it's one or the other.

WoW.. just read through the thread and no one has been out of line... There have been several very good and trusted peeps.. Devs even. . Who gave you an answer. Your problem is jot unique. Download mode does can be a ***** to get into sometimes. Keep trying.

[Q] Need help - My Galaxy Tab SPH-P100 Bricked

​
I have tried installing EA24 stock (http://forum.xda-developers.com/showthread.php?t=1133053) but still Freeze when booting. The error message shown on the picture. I am clueless and need your help.

gtabspring said:
​
I have tried installing EA24 stock (http://forum.xda-developers.com/showthread.php?t=1133053) but still Freeze when booting. The error message shown on the picture. I am clueless and need your help.
Click to expand...
Click to collapse
I had a more complicated version of this. couldn't format, couldn't mount, nothing. My tab showed this, I tried flashing several different kernels/roms/cwm, everything, nothing. Actually made it worse. It got to a point where when I powered on, I only got the backlit softkeys. A few times I got a weird image I've never seen before. Something about bad or unknown upload mode (with a little droid in teh corner....should have taken a picture). And finally I would get nothing; HOWEVER, if I plugged my tab into my laptop and gave it a few seconds, ODIN would see it. I could try flashing a kernel, but it would never process, just hang at the first step so....
with the tab plugged into the laptop and ODIN showing a connection, I would hold VOL DOWN + POWER until I see it disconnect (this is evident of a power down since I have no lights to indicate that). Once it disconnects (yellow box disappears) you can let go of POWER but do NOT release VOL DOWN. It will reconnect shortly thereafter. You are now in Download mode (whether or not you actually see anything on the tablet. You can test this theory by flashing something. What fixed it for me? I downloaded firmware from samfirmware.com. Specifically I downloaded JJ7 v2.2 (full file name I used was P1000XWJJ7.rar) I think what made the difference was using all 3 files. I did not use a PIT file, I put P1000XWJJ7-REV03-ALL-CL669843.tar.md5 in the PDA box, MODEM_P1000XXJK5_REV_00_CL690077.tar.md5 for Phone, and GT-P1000-CSC-MULTI-OXXJK2.tar.md5 in CSC. I did NOT check repartition. Now, this was after I had tried several things like flashing PIT by itself, different stock kernels, full ROMs, etc.... This was the final step I took. Now I'm back to normal.
I'd be interested to see if this solves anyone else's problem. I am so thrilled that I just fixed my "bricked" tab (no power, no response, no apparent charging even) that I'm hoping my time and effort can help someone else.
Let us know what happens. I am actually scouring the forums now because I know at least 2 others were having similar problems as I and maybe this will help them as well.
BTW, I did lose EVERYTHING on the internal SD, including all my backups. Thankfully I always made backups to External
P.S. I should mention it is an AT&T (GSM) Tab.

swedishcancerboi said:
I had a more complicated version of this. couldn't format, couldn't mount, nothing. My tab showed this, I tried flashing several different kernels/roms/cwm, everything, nothing. Actually made it worse. It got to a point where when I powered on, I only got the backlit softkeys. A few times I got a weird image I've never seen before. Something about bad or unknown upload mode (with a little droid in teh corner....should have taken a picture). And finally I would get nothing; HOWEVER, if I plugged my tab into my laptop and gave it a few seconds, ODIN would see it. I could try flashing a kernel, but it would never process, just hang at the first step so....
with the tab plugged into the laptop and ODIN showing a connection, I would hold VOL DOWN + POWER until I see it disconnect (this is evident of a power down since I have no lights to indicate that). Once it disconnects (yellow box disappears) you can let go of POWER but do NOT release VOL DOWN. It will reconnect shortly thereafter. You are now in Download mode (whether or not you actually see anything on the tablet. You can test this theory by flashing something. What fixed it for me? I downloaded firmware from samfirmware.com. Specifically I downloaded JJ7 v2.2 (full file name I used was P1000XWJJ7.rar) I think what made the difference was using all 3 files. I did not use a PIT file, I put P1000XWJJ7-REV03-ALL-CL669843.tar.md5 in the PDA box, MODEM_P1000XXJK5_REV_00_CL690077.tar.md5 for Phone, and GT-P1000-CSC-MULTI-OXXJK2.tar.md5 in CSC. I did NOT check repartition. Now, this was after I had tried several things like flashing PIT by itself, different stock kernels, full ROMs, etc.... This was the final step I took. Now I'm back to normal.
I'd be interested to see if this solves anyone else's problem. I am so thrilled that I just fixed my "bricked" tab (no power, no response, no apparent charging even) that I'm hoping my time and effort can help someone else.
Let us know what happens. I am actually scouring the forums now because I know at least 2 others were having similar problems as I and maybe this will help them as well.
BTW, I did lose EVERYTHING on the internal SD, including all my backups. Thankfully I always made backups to External
P.S. I should mention it is an AT&T (GSM) Tab.
Click to expand...
Click to collapse
Thanks for the suggestion. I think your version of galaxy tab is different with mine and I am not sure that it will work. I am really desparate for solution. This disaster started when the tab's battery is low and suddenly off and when it's charged and turned on it bricked

Point being, tabs are tabs. You will need to use the same procedure, but a different ROM that is designed for your tablet. Go there and find a ROM. There is a thread about unbricking your tablet, I think in the Android Development section that should have a link to samfirmware.com and may provide you with a ROM version that should work. something that may help: plug your tab into the charger at least overnight. I used the stock charger and cable and charged it for 12 hours or so. I did not get any indication that it was charging since the screen and softkeys would not respond, but it did charge.
Of course, I look back and I think you have an indicator, but still a good idea. Try it anyway. Can't make it worse, eh? Mine seemed hardbricked, but it wasn't. I was real close to taking it apart before I found something that works. I believe, IMO, what really fixed it is flashing ROM (PDA), Modem, and CSC files all at once. It could have been something else, but that was the last thing I did before it finally booted.
Go to samfirmware.com, create a free account, and sign in. Then go here (I think your tab is a P1010, correct?) http://www.samfirmware.com/WEBPROTECT-p1010.htm
and Download this:
1010XWKC1 ## MULTI - CSC - OXXKC1 P1WIFI 2.2.1 2011 March DOWNLOAD
(click on DOWNLOAD)
Unzip that file you just downloaded
Start ODIN
Hold VOL DOWN and plug in tab to computer
I believe 3 files should be in the .rar (you can use 7-zip to open, Google it)
the MODEM file goes in Phone.
the CSC file goes in, you guessed it, CSC
last one is PDA.
I think I just rewrote instructions that can be found in the Galaxy Tab Bible. lol. This is what I would do. It worked for me.

Password for P1000XWJJ7.rar
Gentlemen,
I've downloaded both P1000XWJJ7.rar and P1010XWKC1_OXXKC1 to fix my bricked tab, but both require a password to extract the archives. Does anyone know the password? Has anyone had the same issue? I doubt it, otherwise i think it would have been addressed. Any help is appreciated.

I'm having the same problem were you able to fix it?

jairo_pena said:
Gentlemen,
I've downloaded both P1000XWJJ7.rar and P1010XWKC1_OXXKC1 to fix my bricked tab, but both require a password to extract the archives. Does anyone know the password? Has anyone had the same issue? I doubt it, otherwise i think it would have been addressed. Any help is appreciated.
Click to expand...
Click to collapse
try sampro.pl
see if that works.

I too require the passwords to be able to extract these files if someone would be so kind.

Copied straight from SamFirmware.com. It is right at the top of the download page.
try both of these... seems it could be either one of them
## Password is samfirmware.com
# Password is samsung-firmwares.com
Click to expand...
Click to collapse

where can i get these files for the sprint version of the tab i believe the model is p100 I don't see it listed on the recommended website

oxbeast1210 said:
where can i get these files for the sprint version of the tab i believe the model is p100 I don't see it listed on the recommended website
Click to expand...
Click to collapse
do a quick search of the dev thread for EA24 and you should be able to find the original SPH-P100 files. then you can find the EB28 and EF17 updates as well to get all the way to the official GB release.

tried the suggested file still get the error that the OP got in the first screen

oxbeast1210 said:
tried the suggested file still get the error that the OP got in the first screen
Click to expand...
Click to collapse
ok, no one likes a bricked device so let's see what we can do to help you. tell us where you are with your problem. by that i mean what model do you have, what rom were you running, what did you do or try to do that bricked your phone. i'll keep an eye on this thread looking for your response and we'll go from there.

I have the sprint p100 model room was stock rooted gingerbread.
I mailed the Tab to my brother when he got it tab battery was
completely dead and after he charged it and turned it on
he had that error
---------- Post added at 01:30 AM ---------- Previous post was at 01:29 AM ----------
thank you very much for helping me!!

can anyone help?

I have the T-Mobile version of this, but here's a guide and download files to recover your stock ROM. You can follow the entire guide if you want the Overcome ROM as well:
Guide:
http://www.teamovercome.net/p1000/?page_id=17
Downloads:
http://www.teamovercome.net/p1000/?page_id=21
Good luck!
NOTE:
Sprint modem is not listed, but you can fix that later. If you can get it to work with this guide & using the last modem file, we can go from there.

gtabspring said:
​
I have tried installing EA24 stock (http://forum.xda-developers.com/showthread.php?t=1133053) but still Freeze when booting. The error message shown on the picture. I am clueless and need your help.
Click to expand...
Click to collapse
try the one on teamovercome . net I have soft bricked mine but it worked after i followed their instructions there..

Has anyone EVER confirmed that overcome work for non GSM tab, for unbricking and CwM functions?
Sent from my GT-P1000 using XDA

Not booting past the "Galaxy S" screen...

Hey guys,
In a bit of a pickle at the moment. I grabbed an S1 off a friend to try and teach myself about rooting and flashing custom ROMs and such using Odin. With the final intent getting it to run ICS. Not a very hard challenge, but evidently it is for me.
I'll explain what I did, and if you can help without investing too much of your time I would be very grateful.
When I got it, it was running 2.3.3, all the tutorials I read told me to update it to 2.3.6 before doing anything more. I managed to root the phone easy enough, no issues there. But when I tried to put 2.3.6 on via Mobile Odin, (which I used to flash my S2 to ICS, long story) it had seemed to freeze on 'flashing flash kernel' for a good 15 or so minutes.
Being the daft monkey that I am, I exited the program...by removing the battery (don't judge me please). When I went to turn it on, it wouldn't load past the "Samsung Galaxy S" screen.
It goes into Download mode fine, and I've tried to flash an abundance of different Gingerbread ROMs onto the phone and Odin has just been getting stuck on the "setup connection" every time I've tried to flash.
I have tried using different USB ports which is readily suggested by most people and seems to work, using my laptop instead, different cords as well. No luck. Nothing happens when I press volume UP + home + lock like it used to, so I can't even factory reset or anything =\
I did find somewhere that suggested adding a PIT file to Odin and selecting repartition but every one yells at each other when 'repartition' gets mentioned, lol.
I hope this is in the right place, please bare with me if I used any wrong terminologies, I am relatively new to this.
Has anyone got some suggestions that may help me with my problem? =\
Thank you!
Taylor

sigh...here's my recovery kit, unzip, read .txt file, proceed
http://db.tt/MOGZx01S
Credits to nitr8 and chainfire

Thanks, sorry for being such a hassle...

Twinning92 said:
Thanks, sorry for being such a hassle...
Click to expand...
Click to collapse
No problems, was teasing ya! You will end up with root and custom recovery, if you then go to slim website and read and follow installation instructions you will then have lush ics

[Q] Forgot USB-debugging downgrading

Hi!
This is my first post an I hope I did put it on the right place and I havent found any other post that really matches my problem.
Anyway, I was so happy for being able to bring back stock rom on a rooted SGS2 I9100 who didnt worked proper with its root. In this case, no USB-debugging were necessary.
After this mission I felt ready to try to downgrade the SGS Advance I9070 from stock Jelly Bean to Stock Ginger Bread by mainly following one of all those tutorials about how to do it. And I know its said - enable USB-debugging.
But as I were interupted by my wife just before I were going to proceed, I totally forgot it when I finally went back to my work of downgrading. As I were a bit stressed, I just connected the phone to Odin and slammed the PDA-button like I did with the SGS2. It went smooth all the way through Odin and the green PASS showed up. But when the phone were about to boot up it stuck at the Samsung-logo. Its in a bootloop. After a short time of wondering about what went wrong, it struck my head I forgot to enable USB-debugging. Amen!
So, I forgot debugging while running JB-stock to downgrade to GB-stock. The only thing I can reach now is download-mode except the bootloop Samsung start interface. Its probably occured because I forgot enable debugging, right? And does it mean this device is bricked for real or is there anyway to bring back life?
Best regards // emsoh

emsoh said:
Hi!
This is my first post an I hope I did put it on the right place and I havent found any other post that really matches my problem.
Anyway, I was so happy for being able to bring back stock rom on a rooted SGS2 I9100 who didnt worked proper with its root. In this case, no USB-debugging were necessary.
After this mission I felt ready to try to downgrade the SGS Advance I9070 from stock Jelly Bean to Stock Ginger Bread by mainly following one of all those tutorials about how to do it. And I know its said - enable USB-debugging.
But as I were interupted by my wife just before I were going to proceed, I totally forgot it when I finally went back to my work of downgrading. As I were a bit stressed, I just connected the phone to Odin and slammed the PDA-button like I did with the SGS2. It went smooth all the way through Odin and the green PASS showed up. But when the phone were about to boot up it stuck at the Samsung-logo. Its in a bootloop. After a short time of wondering about what went wrong, it struck my head I forgot to enable USB-debugging. Amen!
So, I forgot debugging while running JB-stock to downgrade to GB-stock. The only thing I can reach now is download-mode except the bootloop Samsung start interface. Its probably occured because I forgot enable debugging, right? And does it mean this device is bricked for real or is there anyway to bring back life?
Best regards // emsoh
Click to expand...
Click to collapse
LOL...:laugh: Wives will remain Wives!
The device is Soft Bricked and can be resurrected..did you follow this procedure: http://forum.xda-developers.com/showthread.php?t=2195673 ?

arneldna said:
LOL...:laugh: Wives will remain Wives!
The device is Soft Bricked and can be resurrected..did you follow this procedure: http://forum.xda-developers.com/showthread.php?t=2195673 ?
Click to expand...
Click to collapse
Haha.. Well, I had to drive her to the shop and that was enough to make me lose my patience of remembering important rules just because I had to go with other important rules. Like the gentleman I am. :fingers-crossed:
Thanx for reply. It makes me glad you do believe its possible to fix this issue. The link you showed is on of those I been looking at before I got started. But after a lot of comparing between several links from i-net, I decided to go with the procedure that the majority declared. For example, in this link its said "re-partition" must be ticked in. The other guides said not. Only "reboot" and "time-reset" to be ticked in.
The stock firmwire I downloaded were from some address connected to Samsung. It means there were only one file with all included just to insert in the PDA. Now, afterwards..I do understand it isent that hard to fill in 3 lines myself instead of one. But it seemed simplier with only one at that time. As I am a newbie about changing software in phones, I were ready to make mistakes but not this mistake and I really dont know what guides who are the best to go with.
Do you think it will make any difference if I go with your link and try again?
Remember, the phone were not rooted. Im really not sure, but I think I read somewhere that if debugging are not enabled on official kernel, theres no way back because cant reach debugging in any way. But I hope its not true.
Now, as far as I understand in my case...what I did was to erase the operation system I had (stock 4.1.2) and filled it up with (stock 2.3.6) but it only reached the gates and not the internal of the phone. It means there are no operating system at all?
Then why Odin shows PASS? And if no communication files can reach the phone, how is it possible that the counter now shows the phone has been rooted? Yes, I tried to root it today and Odin showed PASS again. And as the counter counts, it must mean the phone is not 100% blocked from communication even without debugging enabled?
But still the phone act as described earlier. Only Samsung-logo, bootloop and I can only go forward to download-mode.
:crying:

emsoh said:
Haha.. Well, I had to drive her to the shop and that was enough to make me lose my patience of remembering important rules just because I had to go with other important rules. Like the gentleman I am. :fingers-crossed:
Thanx for reply. It makes me glad you do believe its possible to fix this issue. The link you showed is on of those I been looking at before I got started. But after a lot of comparing between several links from i-net, I decided to go with the procedure that the majority declared. For example, in this link its said "re-partition" must be ticked in. The other guides said not. Only "reboot" and "time-reset" to be ticked in.
The stock firmwire I downloaded were from some address connected to Samsung. It means there were only one file with all included just to insert in the PDA. Now, afterwards..I do understand it isent that hard to fill in 3 lines myself instead of one. But it seemed simplier with only one at that time. As I am a newbie about changing software in phones, I were ready to make mistakes but not this mistake and I really dont know what guides who are the best to go with.
Do you think it will make any difference if I go with your link and try again?
Remember, the phone were not rooted. Im really not sure, but I think I read somewhere that if debugging are not enabled on official kernel, theres no way back because cant reach debugging in any way. But I hope its not true.
Now, as far as I understand in my case...what I did was to erase the operation system I had (stock 4.1.2) and filled it up with (stock 2.3.6) but it only reached the gates and not the internal of the phone. It means there are no operating system at all?
Then why Odin shows PASS? And if no communication files can reach the phone, how is it possible that the counter now shows the phone has been rooted? Yes, I tried to root it today and Odin showed PASS again. And as the counter counts, it must mean the phone is not 100% blocked from communication even without debugging enabled?
But still the phone act as described earlier. Only Samsung-logo, bootloop and I can only go forward to download-mode.
:crying:
Click to expand...
Click to collapse
Don't worry - as long as you have access to download mode you are fine :good:
I am not sure as I never downgraded to GB myself, but from my understanding of posts in here it is partitioning issue.
JB got different sizes or mount points (forgot exactly) of key partitions and that is what is wrong here - it cannot find some components to finish booting.
re-partition is the main thing here.
Get file from this guide.
Key point is:
9)Hit on PIT button and select the PIT file extracted from the downloaded package in first step above (GT-I9070_EUR_XX_8G.pit).
You should be able to use your 1-file-ROM and get it working, as long as you use .pit and tick re-partition.
Worst case scenario - flash JB again (no re-partition needed) and it will be working as before ;]

th3cr0w said:
Don't worry - as long as you have access to download mode you are fine :good:
I am not sure as I never downgraded to GB myself, but from my understanding of posts in here it is partitioning issue.
JB got different sizes or mount points (forgot exactly) of key partitions and that is what is wrong here - it cannot find some components to finish booting.
re-partition is the main thing here.
Get file from this guide.
Key point is:
9)Hit on PIT button and select the PIT file extracted from the downloaded package in first step above (GT-I9070_EUR_XX_8G.pit).
You should be able to use your 1-file-ROM and get it working, as long as you use .pit and tick re-partition.
Worst case scenario - flash JB again (no re-partition needed) and it will be working as before ;]
Click to expand...
Click to collapse
Ok, it makes me a bit more calm and Im starting to believe a bit, theres a way back for the phone to rise again. So you mean it might not be the failure of missed debugging, instead the critical main thing can be re-partiton?! It sounds very possible based on what you said.
The thing now is, ofcourse I would be satisfied if my first plan come true. But right now I really dont care what version it´ll be running, rooted or not. I only want it to act like a smartphone again n matter what´s installed. So I will go with your advise and test it one by one.
Thanx so far! To be continued..

SOLVED Forgot USB-debugging downgrading
I must admit I didnt really believed it wud work even I hoped it wud do. Before I started the new operation I gave it the chances 75% negative and 25% positive. But I was so wrong.
It really passed!!
Im so thankful for the support. To arneldna who made me reconsider this current version and tutorial for firmware downgrade. And to th3cr0w who explained and really pointed out the missing spot in my failure of action during the installing process.
The solution - Just to be sure, I followed the tutorial exactly. When it rebooted it showed up not to be my country region so I did it again with my nordic region all-in-one tar-file. This time just to be safe, I enabled usb-debugging and also unknown sources. Idk if it had any use but just in case of. And Voila..back to my region and everything seems to be as it was the first time I started up the phone when it was new last summer. After that I did a factory reset which I learned is useful to do.
As this was only one of my childrens phones, I actually got 3 more of the same to downgrade to work smooth again. But now I learned another lesson. I hope!
THANX A LOT to both of you! :good:

emsoh said:
I must admit I didnt really believed it wud work even I hoped it wud do. Before I started the new operation I gave it the chances 75% negative and 25% positive. But I was so wrong.
It really passed!!
Im so thankful for the support. To arneldna who made me reconsider this current version and tutorial for firmware downgrade. And to th3cr0w who explained and really pointed out the missing spot in my failure of action during the installing process.
The solution - Just to be sure, I followed the tutorial exactly. When it rebooted it showed up not to be my country region so I did it again with my nordic region all-in-one tar-file. This time just to be safe, I enabled usb-debugging and also unknown sources. Idk if it had any use but just in case of. And Voila..back to my region and everything seems to be as it was the first time I started up the phone when it was new last summer. After that I did a factory reset which I learned is useful to do.
As this was only one of my childrens phones, I actually got 3 more of the same to downgrade to work smooth again. But now I learned another lesson. I hope!
THANX A LOT to both of you! :good:
Click to expand...
Click to collapse
Glad to know you fixed it.. Appreciate your patience and efforts... :thumbup:
You don't care where I sent it from....!