Develop Bugs

AT&T Tab Black Screen/White Line During Bootup Fixed

I took my stock AT&T tab and wiped it then flashed Roto JME-4. When I rebooted, I had a black screen for about 60 seconds, with a skinny white line, and I could hear the samsung music. After about 1.5 minutes, I pressed the power key, and screen went totally black - no line. Then I pushed power again, and everything was normal after that, unless I rebooted.
Anyway, here is it fix:
1) go to http://forum.xda-developers.com/showthread.php?t=899196 and download the jj4bootloader.zip file
2) use odin to flash the unzipped jj4 file. It goes in PDA and nothing else in any options.
3) upon reboot, you will have a 100% normal startup with logo and music.
I used the Bootloader Patch app to check this, and it reports it is safe, and that I can flash anything.
Thanks to Roto, Chain Fire, and alexnoalex

Ok, so, just to be sure I'm not going to break my Tab, doing this ONLY changes/fixes the boot animation etc. (get's rid of the AT&T stuff, and puts in the Samsung stuff).
To be clear, I just flashed Roto's latest Euro firmware (Baseband P1000XXJMA, Build FROYO.XXJME), so performing this fix won't affect/change ony of this stuff right?
If I have to re-flash everyting from scratch, then it's really more trouble than it's worth (Blank screen at bootup? Big deal... It's just at boot right? Everything else works perfectly!)

I wish rotohammer and other rom devs would include this information clearly in their initial posts. Took me awhile to find this fix but it works well. This is also important because you can't see the recovery screen without it.
Sent from my GT-P1000 using Tapatalk

Jade Eyed Wolf said:
If I have to re-flash everyting from scratch, then it's really more trouble than it's worth (Blank screen at bootup? Big deal... It's just at boot right?
Click to expand...
Click to collapse
This is just a quick 30 second flash thru odin, it only repairs the black screen, and doesn't touch anything else!
The developers took out the sound and logo to make the rom file size correct.

That's just the answer I was looking for! Thank you good sir!

Glad I could help.

Hello, I have the same problem but I cannot flash the zip file because my computer doesn't detect the tab when I'm in download mode. I tried updating the drivers and software and it still doesn't want to detect it. I cannot get into recovery mode because of the black screen/white line. Do you know what I can do to get my computer to detect my TAB? I tried searching the forum but could not find any info that helped. Any help is much appreciated. Thanks!
AT&T SGH-i987
Firmware 2.2
Baseband P1000XXJHA
Kernel 2.6.32.9 [email protected] #19
Build Froyo.XXJMA

Are you using windows xp, or 7? Put the tab in download mode before you connect to the computer. Is your tab set to usb debugging mode?

I used Win XP, Windows 7 x64 and x86, non of them worked. They can detect my Galaxy S I9000 phone but not my TAB. Yes, I tried it with both debugging on and off, it still doesn't work. Could it be the kernal's fault? Maybe the cable? It will charge the TAB but for some reason my computer won't detect it.

Try different usb cables and ports on the computer.

I tried a different wire and usb ports and it's still not working. I just realized the TAB is not charging anymore. It doesn't make the charging sound when I plug it in. Figured out it's not the cable because it worked on another TAB. Could it be the firmware or kernal?

Not charging when plugged in the computer, or in the wall outlet? Plug it in the wall for at least for hours to get a full charge.

It charges if I plug it into the wall but its very slow like when you charge it via usb. Im using the original charger and cable. There is an x next to the charging/lightening icon on the top when I plug it into the wall and computer.

Just let it charge all night. Be sure its off when charging.

What's the point of having it fully charged? How will that help? My computer still won't detect it even if it's fully charged. I need help to get my computer to detect it so I can restore the original firmware.

I have seen five problems like yours, and after a complete charge, then reboot the phone into download mode, the problem cleared up. They used a different usb port also.
Go to windows update and update your pc.
Look a few threads further down named «help help help»

Ok its currently 50% now. Ill let you know once its fully charged. Thanks for your help so far.

Its 100% and my computer still doesn't detect it. Now what?

Did you have a chance to see the thread “help help help"?
This will sound crazy, but double check your cable - recently someone had the same trouble, because they had dust in the cable connector.

I cannot see the thread you're referring to.
Yes, I did tried a different cable and it's still the same.

[Q] hey odin flash guys, I need help

Impatient EB13, tried to ODIN DI18... pulled the plug after 5 minutes of no progress. Got a "smart phone ! CPU" image and decided to ODIN the pre rooted EC5... I've been waiting for 30 minutes now. What should I do?

if you have used odin before then just start over and do it till it works and i suggest you stick to EB13 for now

Pull the battery, try a different USB port, and/or cable.

Stock cable sucks for data transfer. Really only good for charging. Same with USB ports on the front of your computer. Its really better to use a different cable plugged in to a port in the back of your computer.

elrey75 said:
Impatient EB13, tried to ODIN DI18... pulled the plug after 5 minutes of no progress. Got a "smart phone ! CPU" image and decided to ODIN the pre rooted EC5... I've been waiting for 30 minutes now. What should I do?
Click to expand...
Click to collapse
Of course we assume you are in download mode and a com port shows up in Odin.

watermoore said:
Stock cable sucks for data transfer. Really only good for charging. Same with USB ports on the front of your computer. Its really better to use a different cable plugged in to a port in the back of your computer.
Click to expand...
Click to collapse
When I first got my Epic I saw so many posts like this that I went down and got a BB cable. Since then I use the stock cable to ODIN all the time. I think using a back mounted port is much more important than blowing $ on a cable.

Yeah, I followed all directions and downloaded the necessary files. Tried all recommendations but once I saw the "phone ! Cpu" I couldn't get it past image.xxx in odin. Took it in to a sprint service center and they had no remedy so they gave me a new one, not refurbished. And wouldn't you know it... EB13... How? Why? I have no idea. Thanks for the help, I'm staying put.
Sent from my original EPICS' step brother...

[Q] Unable to Odin/CWM restore

I have had my Epic for few months now, and have yet to encounter this error. Today both my parents decided to buy the Epic's (woot 3 epics in the house), and so I go and try to Root it for them. I go to the first one, and put CWM 3.1.0.1 on it. Everything goes fine, I reboot into CWM, everything dandy, shutdown and go into download mode (Hold 1 then press power button), done this many times. But here came the problem. Odin has failed during the flash and now the phone shows (Phone ---- ! ---- Computer) display when I try to boot it up or try to go into CWM. So I have tried Odin again with download mode, I did get the yellow download screen, but Odin keeps failing. I have tried different USB ports/cables. Different pit files and modems, including EB13, EC05 and EH06. And I am sure the files work, as I have just tried the second phone, and everything went fine. ... So yeah... uh... Attached are two screenies.
This is my Odin Print out
And this is the screen I get
NVM, got it to work using this :
kennyglass123 said:
There is still hope. Take out the battery and hold the power button for 30 seconds. Leave the battery out and plug the USB into the computer and then hold the "1" key on the keyboard and then press and hold the power button. It should get you back into download mode.
Click to expand...
Click to collapse

Glad you got it fixed!
(And that you searched, albeit after posting XD)
Posted by Mr. Z's Epic 4G.

Thank you for that post. Kids loaded some stuff on my notebook and it froze during Odin. Just happened to happen on this thread and Viola. Download mode accessed, Odin fixing.
I was about to go to Sprint today.
I love XDA.
Sent from my SPH-D700 using XDA Premium App

Hey that was my quote...YAY!
Glad you got it fixed dude!

Well, the true fix for me is the Battery is bad somehow... I can Odin like nothing if I take the battery out, but the second the battery is in and I try to Odin, it Fails... is this the case for you guys?

shiroimin said:
Well, the true fix for me is the Battery is bad somehow... I can Odin like nothing if I take the battery out, but the second the battery is in and I try to Odin, it Fails... is this the case for you guys?
Click to expand...
Click to collapse
I think that is caused by whether your computer has a powered or non-powered USB port.

no, because I have Odined 2 other Epics on the exactly same cable and same USB port, so it has nothing to do with that. It was truly just the battery.

shiroimin said:
no, because I have Odined 2 other Epics on the exactly same cable and same USB port, so it has nothing to do with that. It was truly just the battery.
Click to expand...
Click to collapse
Did you try swapping the battery from the other Epic and see if it truly is interfering somehow?

Bricked My Nexus / Bad USB Connection

I just wanted to share what happened before it was bricked so others could possibly avoid it (and because I didn't think I could brick a Nexus...).
Yesterday my USB connection began failing intermittently. It would charge, but the computer would not always recognize the device. On Windows 7, I got an error message saying that the device had malfunctioned and that I should try reconnecting it. On OSX, Android File Transfer could not find my device. Unplugging and plugging back in got the computer to recognize it about 20% of the time.
I went back to stock using fastboot, but I had to battle with it for several hours because of how unreliable my USB connection was. On stock I still had the problem, but I wondered if I had just gotten unlucky during flashing since I had so many failed attempts. Then I decided I would try again with Odin since it just takes one flash to go back to stock. Unfortunately, my USB connection failed again during the Odin flash. I pulled the battery (this could be the true problem but I couldn't get the flash process to start over otherwise) and at this point my phone was bricked. The screen showed an image with a phone and a computer with an exclamation point between them. I couldn't get to my bootloader and couldn't try any other fixes because my computer would no longer recognize my phone at all.
Long story short, if your phone's USB connection begins to malfunction then don't use Odin.

Sorry to hear that. This is something I learned (second hand, thank god) when I had my Galaxy S1. Odin can simultaneously be the best and worst tool you use.
Sent from my Galaxy Nexus

ericaraj said:
I just wanted to share what happened before it was bricked so others could possibly avoid it (and because I didn't think I could brick a Nexus...).
Yesterday my USB connection began failing intermittently. It would charge, but the computer would not always recognize the device. On Windows 7, I got an error message saying that the device had malfunctioned and that I should try reconnecting it. On OSX, Android File Transfer could not find my device. Unplugging and plugging back in got the computer to recognize it about 20% of the time.
I went back to stock using fastboot, but I had to battle with it for several hours because of how unreliable my USB connection was. On stock I still had the problem, but I wondered if I had just gotten unlucky during flashing since I had so many failed attempts. Then I decided I would try again with Odin since it just takes one flash to go back to stock. Unfortunately, my USB connection failed again during the Odin flash. I pulled the battery (this could be the true problem but I couldn't get the flash process to start over otherwise) and at this point my phone was bricked. The screen showed an image with a phone and a computer with an exclamation point between them. I couldn't get to my bootloader and couldn't try any other fixes because my computer would no longer recognize my phone at all.
Long story short, if your phone's USB connection begins to malfunction then don't use Odin.
Click to expand...
Click to collapse
There is a chance it's not totally bricked, that happened to me on an other samsung device while i was flashing with odin. U pulled the battery too early.i also had that black screen with the yellow pc and exclamation mark, try another usb port in ur pc and try to flash again with odin, if not, take the battery out and keep it out for a while (i don't know, 30min for example) then try odin again... u should be able to enter download mode somehow despite the screen u got now.
Sent from my Galaxy Nexus using xda premium

ericaraj said:
I just wanted to share what happened before it was bricked so others could possibly avoid it (and because I didn't think I could brick a Nexus...).
Yesterday my USB connection began failing intermittently. It would charge, but the computer would not always recognize the device. On Windows 7, I got an error message saying that the device had malfunctioned and that I should try reconnecting it. On OSX, Android File Transfer could not find my device. Unplugging and plugging back in got the computer to recognize it about 20% of the time.
I went back to stock using fastboot, but I had to battle with it for several hours because of how unreliable my USB connection was. On stock I still had the problem, but I wondered if I had just gotten unlucky during flashing since I had so many failed attempts. Then I decided I would try again with Odin since it just takes one flash to go back to stock. Unfortunately, my USB connection failed again during the Odin flash. I pulled the battery (this could be the true problem but I couldn't get the flash process to start over otherwise) and at this point my phone was bricked. The screen showed an image with a phone and a computer with an exclamation point between them. I couldn't get to my bootloader and couldn't try any other fixes because my computer would no longer recognize my phone at all.
Long story short, if your phone's USB connection begins to malfunction then don't use Odin.
Click to expand...
Click to collapse
Your phone is not bricked. This happened to me on my Vibrant countless times. Not it's basically trial and error to get it to show up on Odin, but use a reliable USB connection, like another port on your PC or something. Trust me, you're fine. I was ****ting myself when this happened for the first time, but it's just like download mode, you can still restore to stock.
rayiskon said:
There is a chance it's not totally bricked, that happened to me on an other samsung device while i was flashing with odin. U pulled the battery too early.i also had that black screen with the yellow pc and exclamation mark, try another usb port in ur pc and try to flash again with odin, if not, take the battery out and keep it out for a while (i don't know, 30min for example) then try odin again... u should be able to enter download mode somehow despite the screen u got now.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Even if he can't enter download mode, if Odin recognizes the phone while the screen with the exclamation mark is up, he'll be fine.

iCaptivate said:
Your phone is not bricked. This happened to me on my Vibrant countless times. Not it's basically trial and error to get it to show up on Odin, but use a reliable USB connection, like another port on your PC or something. Trust me, you're fine. I was ****ting myself when this happened for the first time, but it's just like download mode, you can still restore to stock.
Even if he can't enter download mode, if Odin recognizes the phone while the screen with the exclamation mark is up, he'll be fine.
Click to expand...
Click to collapse
I had a feeling that it wasn't truly bricked, but since my phone's USB driver (or whatever aspect of USB data transfer) was malfunctioning I couldn't do anything about it. I think of it this way: if in that state my phone had a 5% chance of being recognized by Odin, and if my phone already had less than a 20% chance of being recognized before the soft-brick, then I had a 1% chance or less that it would even show up in Odin and even lower odds at a successful flash. Regardless, Verizon agreed to send me a warranty replacement.

iCaptivate said:
Your phone is not bricked. This happened to me on my Vibrant countless times. Not it's basically trial and error to get it to show up on Odin, but use a reliable USB connection, like another port on your PC or something. Trust me, you're fine. I was ****ting myself when this happened for the first time, but it's just like download mode, you can still restore to stock.
Even if he can't enter download mode, if Odin recognizes the phone while the screen with the exclamation mark is up, he'll be fine.
Click to expand...
Click to collapse
Same here with the vibrant. IIRC there was a special way to get your phone to recognize Odin when it happened. Something like plugging in the phone to the computer and then pulling the battery. Odin even worked when I borked a flash and the screen wouldn't even turn on. I would think the nexus could be brought back similarly.
But if the USB port is on the fritz I'm not sure I would want to bring it back.

As far as I'm concerned Odin is the worst thing you can hook up to your devce. No single program has bricked more devices than Odin.
______________
Just Flash It !!!

on my old SGS1 there was chance get back bricked device by method called "JIG"..(its hardware way get back download mode) but i dont study it more...

I don't think its bricked, I once restore my phone from a black screen that Odin still recognized as download mode. The drivers can get iffy, do you have a third comp that you can install fresh drivers on. Also is your USB jack on the Nexus loose? Sometimes it really is due to your PC's USB connection. I also had issues with cheap blackberry cables and had to use higher quality ones.
Did you try going into download mode by connecting it to the PC while with battery removed and hold (whatever buttons to boot it into download mode), then insert the batteries. Or try entering using a jig.
Also a bit lazy of me (on phone), but can someone point me to where to get Odin images for the Nexus?

try to use another cable to connect ur phone to pc
just flash stock via odin, it's not bricked.
My s2 sometimes has that problem when i flash stock

eksasol said:
I don't think its bricked, I once restore my phone from a black screen that Odin still recognized as download mode. The drivers can get iffy, do you have a third comp that you can install fresh drivers on. Also is your USB jack on the Nexus loose? Sometimes it really is due to your PC's USB connection. I also had issues with cheap blackberry cables and had to use higher quality ones.
Did you try going into download mode by connecting it to the PC while with battery removed and hold (whatever buttons to boot it into download mode), then insert the batteries. Or try entering using a jig.
Also a bit lazy of me (on phone), but can someone point me to where to get Odin images for the Nexus?
Click to expand...
Click to collapse
I appreciate the advice but I no longer have that phone. My replacement should come today.
With regards to the drivers, I was referring to the drivers on the phone not on the computer. I honestly don't know if there are USB drivers on the phone (I would think there are) or even if those drivers were causing the malfunction.
The first thing I'm doing this afternoon is plugging my replacement phone into my computer. If the new one doesn't work right then I'll have to make a trip to the Apple store because the problem will almost certainly be my laptop. I'll also owe a big apology to Verizon.

Epic 4g softbricked?

I had a SPH-D700 that was deactivated (Sprint) and I decided to root it. I did a bit of research and found that you needed Odin to root it. I downloaded Odin and the CWM tar for the Epic 4g and then put the phone in download mode. i took a bit of work to get Odin to recognize it, but it eventually did. I followed qbking77's video from there. it hung on SetupConnection for a really long time though. I panicked and unplugged it. Now it won't boot except when in download mode. When I try to boot into recovery or boot regularly, there's no splash screen, just a "phone--!--computer" symbol. I have tried almost everything. I would really appreciate some help.

Get a heavy duty cable like a Blackberry one and odin cwm and like the video said flash the FC09 prerooted ROM. What happened was your cable is a little flaky.

I've used two cables so far, but it still could be... I start looking for a different one I guess

s-cubed said:
I've used two cables so far, but it still could be... I start looking for a different one I guess
Click to expand...
Click to collapse
pull the battery off.. leave it off for about 5 - 10 mins. place battery back in. boot into download mode, PLUG INTO BLACKBERRY DATA CABLE and start using odin. let us know if you still having problems.

Now when I plug it in, nothing comes up in Odin.

Dude your drivers are screwed or your USB is messed up use a new computer and try again. Also I prefer Nokia cables more. IMHO they are more durable that's what I use
Sent from my SPH-D700 using xda app-developers app

if you cant get it to appear in odin, try downloading heimdill, I find 1.11 the easisest to use,. Extract the fc09 rom. Now go to the drivers folder in the zip, open up zagdig, Turn on all l devices under the options menu. Look for samsung composite, or somethign similar. nnstall driver and then go to the frontend. Next put all the parts in and flash with the blackberry cable
you will find the download here http://www.glassechidna.com.au/products/heimdall/
note that the updates past 1.11 has a large change to the gui and maybe confusing, 1.11 is much simpler and as effective as the later update. Use that one for simplicity.