I have a Verizon Galaxy Tab that was running stock 2.2 and rooted. I was in the process of flashing EZbase as a step in installing a custom rom when it died on me. I have no idea what happend because I plugged it in and clicked start before I left from work and when I got home it was dead. The screen stays black but when I plug it in to my laptop the computer and even odin recognize it. The LED flash on the back next to the camera stays on constantly unless I hold the power button down for a few seconds then it restarts and comes on again. I think everything is running fine but the screen is just not working. I've tried flashing it back to stock and many other things I found on the internet but nothing. So does anyone know what I can do to fix this? Any help would be greatly appreciated as I really don't want this to have ruined it. Thanks.
If still under warranty flash back to stock, unroot and return under warranty...
I have tried flashing to stock but I have no way of knowing if it actually worked...
Bump?
Sent from my SAMSUNG CAPTIVATE running Serindipity 6.4 using XDA App
Why do people think its logical to title the subject of your topic as "Help Needed" or "Help Please" etc??
Subject titles are supposed to be descriptive of the subject, not the fact you need help. If everybody titled their help subjects like this just think what it would be like trying to browse this a section.
Related
Hello,
I have been keeping up on these forums for awhile now and have learned it should be hard to brick the Captivate, well that's what i fear may have happened.
I hope you guys have ideas on how i can fix this, What happened is.
I followed the info from this tread here, http://forum.xda-developers.com/showthread.php?t=734871
I was flashing the I9000 rom to my Captivate, i have done a few roms before with out problems.
This time i flashed the rom from the US section and flowed the instructions on the I9000 rom and Odin3 did a reset to reboot the phone and that's the last time i seen anything on the screen.
So i thought it would be best to let it keep going and didn't touch anything, then Odin3 gave me the Green light and said passed but the screen was still black.
So i unhooked Odin3 and pulled the battery thinking maybe i just needed to reboot it, but nothing came back.
I have tried to put it back into download mode but have not been able to, its acting kind of like its not turning on now.
I have tried holding down volume up and down and inserting the usb cable after i put the battery back in but that does not work any more.
I have read that the volume buttons on the I9000 roms are backwards so i thought maybe that might be the problem but am out of ideas.
I hope you guys have some ideas, ill own any one a beer for help on this.
SpinDry2010 said:
I have been keeping up on these forums for awhile now
Click to expand...
Click to collapse
Not long enough to know this belongs in Q&A, apparently.
Yea sorry about that i was reading in that section didn't notice until after i posted.
So is it possible that the bootloader got jacked since i see nothing on the screen?
I have to question why you used a thread that was posted in July...
If you can't get into Download mode using any of the button combos, you'll need to make a Jig.
If that doesn't work, you're **** out of luck.
Jig? 10 char
Well the date of the thread does not seem to matter, but a Jig would only seem to work if i had a boot screen and just had flashed a crippled loader.
But looking into this further i found that the fing bootloader was packaged into the I9000 rom, now since that seems to be what i flashed i can see why that killed it.
I wish i would have known this before hand but i guess lesson learned unless some one thinks that should not matter.
I will have to send it back but i should be ok on that with ATT, but i will stay away from letting the Slb.bin stay in the flash next time.
My captivate will no longer vibrate. Haptic intensity is up, vibrate is turned on. I even went to the test using sgs tools. Nothing. I am running Serendipity 6.4. It's been a while since it has vibrated, but I'm just now getting around to asking the fine folks here. Thanks for any info.
Probably a hardware problem, flash to stock and see if it vibrates then.
ok so, noob question. Do I just find a stock ROM and flash it? or is there a different procedure? If it's just a matter of finding a stock OS ROM, where might i find one?
http://forum.xda-developers.com/showthread.php?t=731989
you really should've know that BEFORE you flashed away from stock.
thanks, backing up apps and flashing right meow. will i have to reinstall clockwork and reroot? Any suggestions if I dont get my vibration back? Also, any ROM suggestions? Ive been running serendipity 6.4 for a while now and have enjoyed it, but i want a change.
that will take you back to stock 2.1 like you just turned it on for the first time.
if the vibration doesnt work from there call and ***** to at&t or samsung and get a warranty replacement as that would be a hardware issue.
if you still have the update.zip with clockwork on it rooting isnt needed just have that on the root directory of the /sdcard and 'reinstall packages' twice to install a rom.
as for rom suggestions noone can really tell you as its all based on personal preference.
no vibration. oh well. I'd rather not sit on hold with at&t or samsung
Thanks to the people that helped me. I think it's probably a hardware issue and now I will take it up with AT&T . I really do hate being on hold.
I have the same issue. Did you replace the speaker/vibrator assembly? Thinking about buying one from Mobiletechvideo guy.
OK so I haven't been on here or done anything to my phone in a couple months. I had andromeda 3 the whole time i haven't been flashing. I come back and immediately go back to stock and flash symply gs2 then I flash Mosaic and then I flash apex. I was just using all the roms for a short while and seeing which one was better. I disabled lagfix each time I flashed one over the other. I wasn't liking any of them too much so I wanted to back to a custom 2.2 rom. So I flash back to stock using one click. Everything looks like its going fine until odin stops. It just freezes and I believe it stopped around where it says something about "factory.rfs". Now from there I know I'm screwed. I leave it there for about 25 minutes to hope that it continues but when it doesn't I remove it. Then my phone has a red list of sentences with numbers and letters appearing. About 4 or 5 lines of them. After I try removing the battery and trying to turn the phone back on it has the same red lines of letters. Then I do it again and my phone won't even turn on. So what am I looking at here? I don't have a jig so I haven't tried that method yet. I was going to try that one click unbrick but I don't think it will work. I came back to xda and was really just rushing with everything and didn't really care for what I was doing. So was I doing everything right? or was I supposed to use something else to go back to stock from 2.3.4?
Much help appreciated!
Edit: Idk if I mentioned this but I think I may have forgotten to disable lagfix while going back to stock.
A JIG may pull you out of this but if it does not you will need JTAG. PM if it comes to that as I can fix it for you via JTAG very quickly...
Lol I actually just fixed it. Thank you for offering the help though. If a mod wants to close this or something feel free to do so.
So here is what I have. One of my friend's girl friend attempted to flash here T849 T-Mobile tablet. I do not have any info on if she attempted with Heimdal or Odin but the result was that it would not turn off. They brought it to me and I ran down the battery and recharched it, I was able to get it into download mode and have attempted several firmwares via Odin. All have passed and installed fine. When I turn on the tablet after the flashes it still has the black/blank screen. I hear the boot sound and the soft buttons at the bottom light up as normal. Its like the screen is dead. I do not believe it is though. Any suggestions?
I have attempted the power+touching screen trick to reset. It resets fine but still no response from the screen.
Like the other ten people posting about a black screen, you have a protected bootloader.
I have been part of this community for about 5 years, I read alot on here dont post alot. I have read all the threads pertaining to that problem but have not found a solution that worked to fix it, or else I would have not posted. So rather than post a smart ass response trying to expose me as a lazy xda newb asking a dumb question how about suggesting something that I have not tried.
As stated in the first post I have done complete stock rom reinstalls and can not see an image on the screen so I can not turn the apk to unlock the bootload. So still no love. Do you have a suggestion?
Also, I have nothing on the screen at all. most of the protected boot loader stuff I have read at least has the phone exclamation triangle computer graphic up. I have nothing.
I gave him the answer and he complains about it.
rangercaptain said:
Like the other ten people posting about a black screen, you have a protected bootloader.
Click to expand...
Click to collapse
Ok, you stated that other people have had a similar problem. The ways to avoid it are in several places in the galaxy tab forums. The ways to fix it I have yet to find. If you are as helpful as you are suggesting would you be as so kind as to give a tip on how it could be recovered? This is not even my tab. I would not have had this problem in the first place.
Please i need help with my samsung captivate, i've gone through various post and thread in all forum pertaining 2 soft brick or hard brick. But i don't what i can call my own because all i get when i try booting the device in various mode is white display at times with several colour doting display or fading display with several color, whenever i try boot in download mode it displays the white with several colour and at my computer i get gadget driver installation succesful then d phone power off and on which i hear disconnection n connection sound from my pc. so it keep repeat d same thing. pls help how can i fix this. i need genuine solution.... thks
What were you doing before it bricked? ie. Were you flashing something, using it to hammer nails, or mixed it up for soap in the shower?
Sent from my cm_tenderloin using xda premium
-SGA- said:
What were you doing before it bricked? ie. Were you flashing something, using it to hammer nails, or mixed it up for soap in the shower?
Sent from my cm_tenderloin using xda premium
Click to expand...
Click to collapse
I wanted to install cm-9-20120804-NIGHTLY-captivatemtd on the device. Actual the installation was successful then when i was trying to restore my backup. it now stoped in d process of installing boot sector. after which remove the battery to start again. that was when it started showing that. actuall when i press power to on it doesn't respond but it only show the display when i plug my charger or usb to computer.
I had exactly the same problem. Use a program called one-click unbrick, that will get your phone back into download mode. After that you can use odin to restore stock. Watch out though, I was very happy when this all worked and I booted into stock only to find out that restarting the phone would brick my phone even worse than it was before. Now the computer wont even pick it up at all and it is stuck in a white at&t bootloop screen when I turn it on. When it is plugged in, all I get is a grey battery that isnt charging and it will not go into download mode. I don't know what I did wrong so I cant tell you how to prevent this problem so just be careful.
A jig would likely be your best option to force your phone in download mode.
If you haven't tried it already, try flashing a stock rom using Heimdall. I've had much better luck using that program than Odin with my own phone.
droyd666 said:
I had exactly the same problem. Use a program called one-click unbrick, that will get your phone back into download mode. After that you can use odin to restore stock. Watch out though, I was very happy when this all worked and I booted into stock only to find out that restarting the phone would brick my phone even worse than it was before. Now the computer wont even pick it up at all and it is stuck in a white at&t bootloop screen when I turn it on. When it is plugged in, all I get is a grey battery that isnt charging and it will not go into download mode. I don't know what I did wrong so I cant tell you how to prevent this problem so just be careful.
Click to expand...
Click to collapse
droy... The problem you're describing is exactly what happened to the first cappy I had, fortunately for me, I did it within a week of getting the phone.... I took it to an AT&T service center *aaack*, they were nice enough to tell me that there was nothing they could do and that I should be able to get it sent back in. Fortunately for me, it was right around the time when the 2.3.5 stock update came out and there were a few other people that were having somewhat similar problems. To try and fix it, I tried the jig, which I constructed myself only, ran the meter tests and found out that it didn't work after trying 3 different ones. I sent it back and got another, fortunately, I haven't ran into the issue again, so I think it may just be some kind of fault on the board given that I've never read of anyone else until now running into the problem
Thanks youall, gr8 help