Related
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.
Hi all, having a problem with my new Epic 4g Touch.
I rooted it, then after having some other problems, tried to flash back to stock via Odin. Not sure if I did something wrong, but in the middle of the flash, Odin had an error. Now the phone won't boot.. it goes straight to the [phone]....[!]....[computer] screen with the text "Firmware upgrade encountered." It goes to the same screen when I try to boot into recovery. It also goes to this screen when the phone is off and I plug it in (ie, there is no battery charging screen).
I can get into download mode, but I can't get my computer to recognize that the phone is plugged in. I have tried multiple computers, different USB ports, different cables, re-installing drivers on the computer, but no matter what I try, the computer never makes any indication that the phone is plugged in. Kies won't see it, Odin won't see it, nothing in device manager, no alert sound when plugging/unplugging, nothing.
I am afraid I have a soft brick on my hands and I might have to take it back to the Sprint store or send it to Samsung (used a USB jig to reset bin count to 0). Anyone have any idea how to get the computer to see it again so I can just try flashing it again?
SAME PROBLEM, PLEASE HELP, PLEASE. If you fixed yours tell me how.
Anyone come up with successful suggestions to this issue? I think I'm now in the same boat after going back to stock. I can't get any computer/cable combination so see the device, which keeps me from using Odin to fix it. Thanks!
I've gotten in that mode before. It does it whenever the phone has been opened in the special mode for updating (which is done by ODIN during the flash process and is a step beyond ODIN D/L mode), but that mode is not closed down properly. It'll do that even if you flash an unused partition like recovery.bin, so it has no bearing on whether your ROM is actually bricked or not. It is just the default behavior when the special flash mode wasn't close down properly.
USB jig restored functionality.
That is assuming you weren't flashing a GSM ROM by mistake.
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.
Hey guys, so my phone was on 10 percent battery, however i never plugged it in. It eventually went flat so i plugged my phone in and nothing is happening. I've tried different powerpoints and cables but nothing works.My phone is rooted and has a custom rom so I doubt warranty is an option. Any help is greatly appreciated!
what does it do when you plug it into the computer? And what about have you put it in download or recovery mode?
killswitch451 said:
what does it do when you plug it into the computer? And what about have you put it in download or recovery mode?
Click to expand...
Click to collapse
Neither recovery or download work. I also left it plugged it in all night and it still doesnt work so im guessing the battery is stuffed
Guys I need your help
I don't know what happened to my Note II phone.
Only thing I've done was to root it. I'm still using the same O.S. I haven't tried flashing something on it before
Here's what happened.
I was just chillin, chatting on Messenger when all of a sudden, the phone LED indicator flashes but it doesn't unlock. then the phone died and when i was trying to charge it, there was only a charge icon on the screen but it wasn't moving.
The next day i bought a new battery and now what happened was that it wasn't going through the Galaxy Note II screen (bootloop perhaps?) i tried going through recovery mode -- dead android icon then it shuts down. and i was still able to access download mode
before i was able to follow the soft brick recovery mode, all of a sudden it doesn't even go to recovery/download mode anymore
LED indicator does not turn on for charging even if i plug it into the charger.
What do i need to do? i don't have JTAG as an option
I read somewhere that I you can boot hardbricked phones using an SD card by doing something about partition stuff there will that work? :laugh::laugh::laugh: hope to get some replies from you guys :good::good:
Have you tried using a 2.0 amp charger and letting the phone charge for a few hours?
audit13 said:
Have you tried using a 2.0 amp charger and letting the phone charge for a few hours?
Click to expand...
Click to collapse
no i haven't tho the battery has a charge (i tested it on a different note 2 i booted)
phone doesn't go into recovery mode anymore. anything i can do to revive it? btw sorry for the late reply
Not much you can do if the phone can't get into recovery mode.
When connected to a computer, do any devices appear in the device manager?
I am also facing the same problem,,,,..not entering to recovery mode .......when trying to install stock firmware through odin (using windows 10)it says nand write and next step fail....i didn't even root my phone.....please friends help me....Thanks in advance....and yes it enters to download mode
Are you using the original Samsung USB cable? Tried other USB cables and all USB ports on the computer? What is the specific Odin error?
audit13 said:
Are you using the original Samsung USB cable? Tried other USB cables and all USB ports on the computer? What is the specific Odin error?
Click to expand...
Click to collapse
i don't have the samsung cable,,,,I was using the sony data cable with cylinder shapes at the ends
yes,i tried all the ports
odin says FAIL! after the Nand write start
What is the error message in Odin? You could also post the log from the log window.