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.
Hey guys i have a bit of a problem. I tried rooting my phone with the one touch root and when i went to turn off my phone and restart it, it would get stuck on the Samsung screen. This worried me for a bit until i read more and found out how to get into download mode.
so now my phone goes to download mode, however Odin does not recognize my phone. when i plug my cable into my phone i hear the "ding-dung" sound, but nothing shows up. Ive read about trying other cable, but none of the other cables i tried worked.
And the current driver i have on my computer is the one from the Samsung website, and i also have.
what could my problem be?
bcusitsjeff said:
Hey guys i have a bit of a problem. I tried rooting my phone with the one touch root and when i went to turn off my phone and restart it, it would get stuck on the Samsung screen. This worried me for a bit until i read more and found out how to get into download mode.
so now my phone goes to download mode, however Odin does not recognize my phone. when i plug my cable into my phone i hear the "ding-dung" sound, but nothing shows up. Ive read about trying other cable, but none of the other cables i tried worked.
And the current driver i have on my computer is the one from the Samsung website, and i also have.
what could my problem be?
Click to expand...
Click to collapse
The first time you use Odin it has to get more drivers from the net. Check in to see if it is still looking for those. That can take like 30 minutes sometimes. Then if it is anything like my laptop Odin only works in that usb port.
Check this and also try another cable and other ports until you see Windows searching for drivers.
Had that exact same problem Saturday night.
It was recommended to me to go watch the qbking videos, which I did.
He has a walk through on using Odin and it took me through the process step by step and once I figured out how to use it was very pleased with how easy it was.
Other things I noticed were:
a) don't use stock Samsung Cable (I believe this is emphasized in the video)
b) get Odin ready to use with the .pit file and the .md5 file and THEN plug the phone in. I don't know why this affected me, but it did.
c) try every USB port available. Some of mine didn't work.
http://forum.xda-developers.com/showthread.php?t=1009997
This is the link to the qbking thread. Good Luck! That's incredibly unnerving until you see that boot screen again!
Had that exact same problem Saturday night.
It was recommended to me to go watch the qbking videos, which I did.
He has a walk through on using Odin and it took me through the process step by step and once I figured out how to use it was very pleased with how easy it was.
Other things I noticed were:
a) don't use stock Samsung Cable (I believe this is emphasized in the video)
b) get Odin ready to use with the .pit file and the .md5 file and THEN plug the phone in. I don't know why this affected me, but it did.
c) try every USB port available. Some of mine didn't work.
http://forum.xda-developers.com/showthread.php?t=1009997
This is the link to the qbking thread. Good Luck! That's incredibly unnerving until you see that boot screen again!
You can also try downloading the Samsung USB drivers from their support site. Install those drivers, then plug the phone in and see if you have better results.
This is probably covered in those videos, but thought it was worth mentioning...
Sometimes rebooting the pc helps
Just realized I posted twice. I wasn't really trying to pad post stats...
As far as downloading the drivers, I believe the videos DO cover this. Just make sure you get the right drivers. I actually downloaded both because the 64 bit drivers didn't work with my 64 bit Windows 7, don't know why. The 32 bit on the other hand worked without problems.
Thanks for all the help guys. I finally got it working, and i flashed Syndicate on it, and have the Emotionless beast theme on it.
so far im loving my rooted phone, and now i know pretty much everything i need to know about rooting my phone. lol
Hey Everyone,
I'm hoping someone can help me find a way to un-brick my Galaxy Nexus GSM 16GB (GT-I9250M). Before you call me an idiot, I'll have you know I wasn't flashing it or anything. I was simply listening to music when the screen went all glitchy and the sound started looping. Then the phone attempt to restart, but mid way through booting, it would glitch out again. It would repeat this until I finally pulled the battery. When I got home, I tried to get it into Fastboot mode or Download/Odin mode. Neither of which worked. I was running the stock version of android. If I recall correctly, it was running 4.0.2.
So in a nutshell, here's the status of the phone:
Regardless of what I do, Fastboot mode and Download/Odin are not accessible.
No matter what combination of buttons I press, the screen always shows: Phone ... Yellow Alert Triangle ... Computer
Using Galaxy Nexus Toolkit or Wug's Toolkit, the phone is not listed under Fastboot or ADB devices.
While the phone is plugged in via USB without a battery, I see device manager adding and releasing an OMAP4440 device every second or so.
When I plug in the phone (with the battery) in via USB while its off, it will turn itself on showing the alert screen mentioned above.
ODIN is about the only app/toolkit I've used that "sees" the device.
Using ODIN, I have tried various stock images mentioned in the forums. All of them have either failed or get stuck on "NAND Write Start!!"
I've read dozens of posts on various forums but I could not find a concrete solution, so I'm appealing to you guys for help. Any help would be great appreciated.
Thank you!
Based on what you have described, even if I could get it working again, I would try to get a warranty replacement, provided that is an option. Sounds like a hardware failure. Like I said, even if it somehow started working again, I wouldn't trust it.
1. first off you need to download "Odin 3 v1.85" here
2. also download CF-Root-GGN_YAKJU_ICL53F-v5.1 here
3. open Odin in your computer
4. where it says PDA put CF-Root-GGN_YAKJU_ICL53F-v5.1
5. Power on the device and when you have the "phone triangle pc screen" connect it to your PC.
6. ???
7. PROFIT!!!
kmdub said:
Based on what you have described, even if I could get it working again, I would try to get a warranty replacement, provided that is an option. Sounds like a hardware failure. Like I said, even if it somehow started working again, I wouldn't trust it.
Click to expand...
Click to collapse
You're probably right. I still have my Nexus S which I can fall back to resort to this. I will try what nonione has suggested, and if that doesnt work, I will likely look to replace the phone.
I've never seen a samsung phone that couldn't be recovered (other than physical or water damage).
You can easily get the phone back with odin (no you do not have to be in odin mode on the phone).
Study up on it....tons of threads, use search.
Never seen a bricked Samsung....ever...and I've had at least 6 or 8 different models.
(edit)
There;s quite a bit more to it than nonione tried to walk you thru.
You will need the correct drivers on your computer first...buncha other steps too.
Study hard before you try odin.
Google, "Galaxy Nexus OMAP Unbricker". Download it and when the OMAP devices comes up in the Device Manager quickly right click on it and install the driver includes with the OMAP download. Once the driver has installed run the .bat file in the download. Should go to Fastboot now.
Then:
http://forum.xda-developers.com/showthread.php?p=27160425
Download the .pit file here:
http://forum.xda-developers.com/showthread.php?p=27152659
Sent from my SGH-T769 using Tapatalk 2
That's easy to repair, dude
That's not a brick, that's just telling you, that the firmware files are corrupt, all you need, is a jig, a Windows PC, Odin and chainfires ODin files
I can walk you through, on Teamviewer, if you want. I've had this problem quite a lot (Not on the GNex, though) I jope I get it, so I get a GS 3 ^^
I do have the same phone with the same problem..but currently out of the country, so cant get it replaced.. I get no yellow triangle my phone is completely dead..I tried the omap flash no luck..please let me know if the omap flash tool worked for you..
Hey guys,
So a bit of an update. I tried using Odin to flash. None of the files suggested worked for me. I also tried the OMAP flasher. While it "did something" without erroring out, it did not switch to fastboot mode for me. My phone is simply stuck in that yellow alert state. So now, i'm going to try using a Jig as familyguy59 has suggested. I saw a video of one guy use one to fix the exact same issue as I'm having, albeit with his Samsung Galaxy 2, but it looks promising. I purchased one a couple days ago and it should come soon. I'll let you guys know how it goes.
Hey Guys,
So I tried the jig i bought. No dice. I'm pretty disappointed. : / I guess off to Samsung it goes... I just don't have any luck with Samsung products.
I've owned my SGII since release, went through a few roms, never had any issues. I have been running liquidsmooth for a month or two, without much issue. Although, lately stablity has dropped off a little. Nothing bad, just a freeze every few days and other minor hiccups.
Then something bad happened.... Last night I was using the phone and it turned off. Then it wouldn't boot. Battery pull, and rebooted but no joy. Then I booted to recovery (TWRP, but I'm not sure which version) and found that it said something along the lines of "E: could not mount /system", along with lots of other similar failure to mount messages. Oh well, I guess I'll just wipe it and flash something new. Any attempt to wipe would hang and then the phone would turn off after a few minutes.
Then I went to flash the stock setup from odin (using the howto from the dev section) , but it too would fail every time. I even tried different builds from samsung's official roms, but they all would fail to install on the phone. I read every thread I could find, and the next thing to try seemed to be an emergency recovery through Kies. That also failed, except it left my phone hard bricked. I can't get into download or anything, nothing shows in the device manager, just completely dead... I made a USB jig, but no luck there either.
I'm completely frustrated... I don't know what to do now... Buy a MB from ebay? The phone was flawless before all this. Any suggestions? I'm using a blackberry pearl for now, I can't let that happen.
Have you tried the Jig on another Samsung phone so you know the one you made physically works?
Some people have managed to get into DL Mode by pulling the battery, SIM, SD, etc. For 5 - 10 minutes then connecting it to the pc with Odin running b4 inserting the battery to enter DL Mode.
Otherwise mobiletechvideos has a really good reputation and turn around time for JTag service.
There is a chance its a hardware problem, and hopefully another member on here can shed some light on the possibility of it being a HW issue or not..
Cheers,
Chris
Thanks for the suggestions. I don't have another samsung phone to try the jig with, but I'll see if I can get a friend to let me hook up this crazy looking thing. I got the resistors set up to 299K, hoped that would be close enough, but perhaps not.
I tried that plug-first-battery-second trick to get into DL mode, but that's not working either.
I looked at the jtag service too, but my fear is that I have corrupted memory. In that case, I wouldn't get a refund if I still couldn't get to a fully healthy boot. It seems odd though... not like it's a common trend for this particular model (that I've seen).
Just seems so strange that it happened for no apparent reason... before it was hard bricked I was able to USB mount the internal storage and access and transfer almost all the contents, except for one folder. I wonder if that one part of the memory caused all the problems?
Again, thanks for the suggestions. I'll keep plugging away at anything that might help, and in the mean time I guess I'll keep my eyes out for broken phones or some way to salvage a board.
If im not mistaken, a hard brick should show up in you device manager as the board itself when connected.
Does anything show in you device manager when its connected? And have you tried using a different PC which has never had Kies installed on it, where you just install the drivers for the T989?
Odin tends to fail at the modem or due to the presence of a .PIT
I got myself out of a brick which started over the a very similar issue, but due to a bad flash.
After 5 hrs of getting nowhere (I was using a Jig) I would get Odin to recognize the phone (My Screen was NOT displaying the DL Mode screen, It was going into DL Mode but other than Odin recognizing it, there were no signs of life!) after enought tries but flashing to stock would fail. I ended up taking a shot at flashing the stock kernel using 512.Pit from a T959, Reflashing the same Kernel, then flashing recovery. I don't advise anyone do this as that PIT file is NOT for a T989, and it may have been BS luck not the use of that PIT file that did the trick.
But I did get it back running %100
Good tips, thanks! Were you using the jig to get the phone into the black screen download mode?
I hadn't tried another PC, although I did make sure any Kies processes were disabled. I just tried another computer, but still nothing gets recognized. Oddly enough, not even the basic "hard brick" USB driver shows up in the device manager.
Thanks for the additional ideas.
This happen to me before, I just cleared cache and Davik then rebooted recovery then flashed another Rom.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Unfortunately for me, since data, cache, and system couldn't be mounted, I couldn't successfully clear them.
KLR Rico said:
Good tips, thanks! Were you using the jig to get the phone into the black screen download mode?
I hadn't tried another PC, although I did make sure any Kies processes were disabled. I just tried another computer, but still nothing gets recognized. Oddly enough, not even the basic "hard brick" USB driver shows up in the device manager.
Thanks for the additional ideas.
Click to expand...
Click to collapse
I would put the jig in with the battery and everything still removed, and alot of trial and error trying things like battery first then connecting the cable with Odin always being already running. Then doing the reverse, etc.
When I did get Odin to recognize the phone, one thing I learnt is when it would detect, it only ever happened after having killed and reopened Odin. I have no explanation on why using "End Task" after each attempt to connect and opening Odin again made a difference but it did.
Have you had a look at the QPST thread? I would ask one of the members contributing to it about why you would or would not see the board. And you could always try installing the boards drivers manually, or enable "Show hidden devices" in your device manager.....
Did you contact the guys at mobiletechvideos and explain the details?
You were able to boot to recovery, so it sounds partition related. But I would try just to flash the stock UVLH1 kernel and recovery with Odin vs full stock rom if you do get it to detect. And if it does detect with Odin eventually do not let it reboot or loose power. Just Kill Odin, unplug the cable if you need to, Start Odin again and reconnect the cable. Once in DL Mode it will stay in DL Mode as long as you have the reboot option in Odin unchecked, etc.
Also if you can get the battery charged fully somehow, your best shot is with a fully charged battery.
Chris
So i tried to root my tablet yesterday and i didnt notice at first that i pick an mx5 for an older android phone i have. So i stopped odin on my pc and the tablet was stuck in download mode frozen, so i took the battery out and now it wont turn on, but when i plug it in to my computer it still shows up in odin but xant connect to it what can i do?
Why did you take out the battery? Letting it die could of helped. Did you press start of anything in odin? Or did you stop odin while it flahed the md5. This could determine if your partition isnt messed up. The only tip I got right now is to take it to samsung and get it repaired.
I took the battery out to see of i could reboot it but it didnt work and yes ot was mod process in odin before i realized what i had done, i dont really want to send it into samsung because i dont want it to be gone for awhile, could a computer repair store do it for me?
Try this. Read post #1. http://forum.xda-developers.com/showthread.php?t=2838473
Thank you so much got it working again, time to log some crazy jerrys game hours
So that link that i gave you worked?
well i tried it, but it didnt work when it was in the computer but connecting it again must have done something cause i was able to get download mode so i just flashed the proper files and got it working