I can't post the link but it is on youtube.
If you youtube "bigshotz" and click on my user name, its the last video I uploaded
Long story short, I used the Odin program for the captivate on accdident, but I found the Odin program for the Vibrant and got it back to stock. But I still have the AT&T Start Screen, anyone know how to get rid of it? Thanks!
Look in the Captivate forums for how to remove the AT&T boot screen. It should just be a file you can delete.
Sent from my SGH-T959 using XDA App
Wipe then reflash?
tried everything
anyone?
same thing happened on my phone when i installed a captivate firmware.. did you find any solutions?
same here. found this in the captivate forum, but no solution so far.
forum.xda-developers.com/showthread.php?p=7678939
Hi, I too have been looking for a solution for this. If you search at&t in the forums you will find multiple posts involving this that have all gone unanswered. I have tried installing multiple different roms, internal phone resets, various odin configurations, and probably a few other things I am overlooking to no avail.
Can't seem to find a solution...
Sent from my SGH-T959 using XDA App
You guys probably need to odin 'eugenes froyo that doesnt brick' then odin back to stock. It will completely wipe everything.
Sent from my SGH-T959 using XDA App
sensasian03 said:
same here. found this in the captivate forum, but no solution so far.
forum.xda-developers.com/showthread.php?p=7678939
Click to expand...
Click to collapse
Nice find! For those curious the file may be located in your /mnt/.Ifs directory. Its called logo_ATNT.jpg Also, the standard vibrant boot image is there named logo_T959.jpg
As that thread mentions, it seems any changes made to the file don't stick though. I have tried a few changes including permissions, rename, move, delete with no luck. ** EDIT ** From a little research, it seems that the /mnt folder represents android's current mouted systems. Kind of a 'virtual folder'. I am not a linux guru by any means so if I am mistaken here please let me know.
Fyi, the froyo that doesn't brick method has not worked for me in the past. Thanks for the suggestion though.
Sent from my SGH-T959 using XDA App
my phones network is showing at&t even i'm not using an at&t sim card. i screwed my efs folder. any idea how to fix?
Try flashing a stock Vibrant kernel? Worked for me when I built a kernel using the CONFIG_KEPLER* options by accident.
Kidshyy said:
I can't post the link but it is on youtube.
If you youtube "bigshotz" and click on my user name, its the last video I uploaded
Long story short, I used the Odin program for the captivate on accdident, but I found the Odin program for the Vibrant and got it back to stock. But I still have the AT&T Start Screen, anyone know how to get rid of it? Thanks!
Click to expand...
Click to collapse
I had exactly the same issue.
The problem is that you flashed the att captivate's sbl.bin which shows the first boot screen like "ATT world phone". So please find a vibrant sbl.bin and flash that through Odin.
I don't have that since I'm fine with the dual screens...
Thanks for the explanation on what file it comes from. I look into that. Never really been an issue for me either, more of an annoyance I guess.
Quick question/comment: why does the stock odin build for the vibrant not flash over this file? I guess it is not included in most builds?
Sent from my SGH-T959 using XDA App
SOLVED!!!!
Thanks for the guidance neasoon. Here is what I did to fix this issue.
1) Nandroid / Titanium backup (just in case)
2) Downloaded the 'update.zip' from this thread: http://forum.xda-developers.com/showthread.php?t=804305
3) Apply update.zip using Clockwork Recovery
4) Reboot, and fixed!!!
A few comments on this method:
Apparently the sbl.bin / boot.bin are relatively rare files to come across and are not located in most firmware leaks/updates. Hence the reason restoring using ODIN back to stock is not solving this issue. These files were grabbed from the JI4 leak and have been put into a flashable update.zip provided by untermensch. These files also fix phones with hardware locks and I believe have been included in some of the recent OTA updates. (Cannot verify as I have not received one) So some that have installed the OTA may have magically seen their 'AT&T' screens disappear afterwards.
I applied the update successfully, and all is well. (NO MORE BRIGHT WHITE AT&T SPLASH SCREEN!). Please make sure you read the OP in the link above before you proceed with the update. Keep in mind it is written towards those with hardware locked phones, so it mentions instructions to get into recovery via adb. Assuming you don't have a hardware locked phone you can reboot to recovery using normal methods to apply this update.
Cheers!
yes finally figured it out too.. what i did was i loaded firmware with boot.bin for a vibrant. and now i dont have the att white world phone bootscreen anymore. yay!
i tried the odin method and it works! no more stupid att boot screen. thanks a ton!
Will the froyo 2.2 fix this? After flashing the captivate onto my galaxy s then loading the ji6 pit, I'm not ready for the emotional roller coaster that may ensue if I do this.
As long as the boot.bin is included it should fix it. Not sure which rom this is included in though.
Sent from my SGH-T959 using XDA App
chupacabra613 said:
Will the froyo 2.2 fix this? After flashing the captivate onto my galaxy s then loading the ji6 pit, I'm not ready for the emotional roller coaster that may ensue if I do this.
Click to expand...
Click to collapse
Ok, I decided to grow a pair and used clockwork to install the zip file. worked like a charm!! Many thanks--Al
Related
I have seen numerous of threads with this same question, but no answer. The issue I have is that my Vibrant has BOTH the I9000 boot image and stock Vibrant image. I9000 comes on for about 2 seconds then the stock Vibrant image comes on. I've tried Odin back to stock JFD and the rom flashed successful, but the boot image won't change. I've read that it doesn't matter what rom you use itsilk not touch the bootloader image. Do any one know the necessary steps to erase the I9000 image and just keep the stock image?
The only reason I need the stock image is because I'm sending my Vibrant in for a new one and I don't want to be charged for tampering with this one. Please help me out. Thanks.
Sent from my SGH-T959 using XDA App
sounds like you flashed a I9K rom that had the I9K sbl.bin in the updates folder.
You need to look through the vibrant bible and flash the Vibrant sbl.bin.
This will fix your issue.
Thank you very much, I will try this soon as I get home. Where/how do I go about doing this? Use Odin? If which to use PDA, PHONE, CSC, or PIT? Also do I tick PHONE BOOTLOADER UPDATE? Thank you very much.
Btw I did not flash an I9000 rom. I used this so called 3 button fix and I guess it only works for the I9000.
Sent from my SGH-T959 using XDA App
there is a CWM flashable fix in the bible.
The 3button fix is what caused your issue. you flashed the one for the i9k, not the vibrant.
All it is, is a sbl.bin from a working phone.
OuncE718 said:
I have seen numerous of threads with this same question, but no answer. The issue I have is that my Vibrant has BOTH the I9000 boot image and stock Vibrant image. I9000 comes on for about 2 seconds then the stock Vibrant image comes on. I've tried Odin back to stock JFD and the rom flashed successful, but the boot image won't change. I've read that it doesn't matter what rom you use itsilk not touch the bootloader image. Do any one know the necessary steps to erase the I9000 image and just keep the stock image?
The only reason I need the stock image is because I'm sending my Vibrant in for a new one and I don't want to be charged for tampering with this one. Please help me out. Thanks.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Have you found a fix for this yet? I'm having the same issue
Has anybody found a solution to this problem? I'm having the same issue.
Other threads say that the i9000 bootloaders overwrote the vibrant ones and that they are not included in the files when you odin back to stock jfd. (The files are boot.bin and sbl.bin). AND I also heard that those files aren't going to be found anywhere because they were hardware encrypted?
What vibrant rom can I flash to that overwrites boot.bin and sbl.bin, which will not brick my phone?
Eugene's JK2 froyo...not the one that doesn't brick...
Well I thought I would try CM7. Apparently the ROM that I was running made a straight upgrade to CM7 impossible.
I flashed back to stock using
s1_odin_20100512.pit
T959UVJFD.tar
Passed with no issues. Also formated the internal SD. Now when I try the usual update.zip method of rooting, the little script seems to stop almost immediately but with no error messages. The progress bar only goes about a 1/10 of the way, then it says successful and reboots. However I don't have SU access nor busybox.
Totally stumped. Any thoughts? This phone was originally rooted in using the same method. If I were to guess, I would say that maybe this "original" ROM is not the original one I had on the phone when I bought it at T-Mo.
When I look at the phones ID it says:
model :SGH-T959
FW: 2.1 update 1
BB: T959UVJFD
Kern: 2.6.29
Build Number :Eclair (I don't remember it originally saying Eclair but I could be mistaken)
Any help would be appreciated.
Apparently the usual update.zip has been naughty lately. Use the attached update.zip posted by s15274n instead.
star_jones said:
Well I thought I would try CM7. Apparently the ROM that I was running made a straight upgrade to CM7 impossible.
I flashed back to stock using
s1_odin_20100512.pit
T959UVJFD.tar
Passed with no issues. Also formated the internal SD. Now when I try the usual update.zip method of rooting, the little script seems to stop almost immediately but with no error messages. The progress bar only goes about a 1/10 of the way, then it says successful and reboots. However I don't have SU access nor busybox.
Totally stumped. Any thoughts? This phone was originally rooted in using the same method. If I were to guess, I would say that maybe this "original" ROM is not the original one I had on the phone when I bought it at T-Mo.
When I look at the phones ID it says:
model :SGH-T959
FW: 2.1 update 1
BB: T959UVJFD
Kern: 2.6.29
Build Number :Eclair (I don't remember it originally saying Eclair but I could be mistaken)
Any help would be appreciated.
Click to expand...
Click to collapse
just use superonelick to root...here is a link..http://forum.xda-developers.com/showthread.php?t=803682
Alex9090 said:
Apparently the usual update.zip has been naughty lately. Use the attached update.zip posted by s15274n instead.
Click to expand...
Click to collapse
Lol. Love that post. You can always use the vibrant tools too to root it. Found under development, stickies
Sent from my T959 using Tapatalk
Dont mean to thread jack but can you link me where i can get odin, pit and tar file? seems like i am mental midget and cant find them.
Thank you
Sent from my SGH-T959 using XDA Premium App
vibrantcm7 said:
Dont mean to thread jack but can you link me where i can get odin, pit and tar file? seems like i am mental midget and cant find them.
Thank you
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
Download this......
http://forum.xda-developers.com/showthread.php?t=954509
star_jones said:
Well I thought I would try CM7. Apparently the ROM that I was running made a straight upgrade to CM7 impossible.
I flashed back to stock using
s1_odin_20100512.pit
T959UVJFD.tar
Passed with no issues. Also formated the internal SD. Now when I try the usual update.zip method of rooting, the little script seems to stop almost immediately but with no error messages. The progress bar only goes about a 1/10 of the way, then it says successful and reboots. However I don't have SU access nor busybox.
Totally stumped. Any thoughts? This phone was originally rooted in using the same method. If I were to guess, I would say that maybe this "original" ROM is not the original one I had on the phone when I bought it at T-Mo.
When I look at the phones ID it says:
model :SGH-T959
FW: 2.1 update 1
BB: T959UVJFD
Kern: 2.6.29
Build Number :Eclair (I don't remember it originally saying Eclair but I could be mistaken)
Any help would be appreciated.
Click to expand...
Click to collapse
I think there are two different stock flashes you can use. if you can't root its probably because you used the wrong one. I know that 2.2 froyo also has rooting issues.
vibrantcm7 said:
Dont mean to thread jack but can you link me where i can get odin, pit and tar file? seems like i am mental midget and cant find them.
Thank you
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=849028
star, I would suggest my noob guide in my signature. It has ODIN and two update.zips... one for just rooting, and the other to just flash CWR (the one I use). The latter allows you to ODIN > go straight into CWR and flash a rom.
Done.
i have alll the files needed. i have every file organized into a simple rar. goto my "lifesaver" post and download the rar. it should help!
I have tried v1.0 and v1.85 of Odin to fix my boot loop. Both said they were successful but in fact it just changed the boot loop's process. Now all that loops is black screen then the Vibrant screen (which I had never seen before). I also tried one click un-brick but the program will not stay open.
I can not enter recovery mode but can still enter DL mode.
This is all a result of trying to install the cyanogenmod using their wiki site (can't post links yet). I had completed installing Clockworkmod recovery as directed by the wiki site. It started when rebooting after installing Cmenard's Overstock Kernel.
Anyone who experienced this and was successful in fixing please do help.
Which file did you used when you used odin?
I used 2. The T959UVJFD.TAR and the 512.rar. I used winzip to extract them for Odin.
I did pretty much exactly what the link says. I tried checking repartition on the 4th try or so as well, sorry I can't post links yet....
http ://androidspin.com/2010/08/09/ how-to-restore-or-recover-your-samsung-vibrant/
Ummm usually reverting back to stock jfd through odin always works..
Many of us have been in bootloops before this one is different simply because CM7 is typically an easy flash. You may want to get different files they may not have downloaded to your computer correctly and then try to flash them using Odin. That's the only thing I can assume is the issue at this point.
Sent from my SGH-T959 using XDA App
yup, try a different file. You might want to try odin 1.3 too. Never failed for me.
Sent from my SGH-T959 using XDA App
iynfynity said:
yup, try a different file. You might want to try odin 1.3 too. Never failed for me.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Not really sure what other files to use. Every search I do for restoring to factory settings finds the ones I used. I will try them with odin 1.3 until I find new files.
Wondering if my samsung driver isn't installed properly. Will Odin even read it if it's not?
OK so, I screwed up. I have a sgs4g, DOH. Gona make a thread in the sgs4g section but help is still appreciated if anyone has some.
Exact same issue.
I had the same issue. Actually got it to boot and everything but everything past the Modem step was scrubbed everytime in Odin because the wrong partition was applied. You get this issue if you use the PIT from a Galaxy Vibrant on a Galaxy S 4G.
I was under the impression that the phone I was modding was a Vibrant. Took me a few hours but I eventually got to the bottom of it after reading every Vibrant thread from beginning to end. Here is a link to the post that saved my night.
http://forum.xda-developers.com/showpost.php?p=12806682&postcount=15
The proper PIT file for the Galaxy S 4G. So everyone with this issue just continue as normal and install a current ROM with this PIT.
On a side note.... all these damn Galaxy phones are confusing. No wonder I never wanted one. I am just fine with Motorola devices... The Optimus series is at least a bit better with the letter branding for each carrier. Galaxy series are all just galaxy...
I have used Odin to load Tar File: JFD and Pit file. Or just used Vibrant AIO and Odin through their. Everything loads fine, but when it boots I just get a black screen. I touch the soft keys and they light up. Some say it is a kernel issue, but I just do not know. Any help on this is welcome.
I have tried different versions of Odin, but nothing seems to work.
I wanted to try this, but the link is not working for me. At least I cannot get to MultiUpload for some reason.
http://forum.xda-developers.com/showpost.php?p=13071981&postcount=2
Thanks all!
Have you tried using bay_wolf's Vibrant Toolbox?
http://forum.xda-developers.com/showthread.php?t=954509
I've used it myself to flash back to stock, and it worked perfectly for me.
Already tried that thanks.
Edit---
Does anyone have the Odin zip EUGENE373_SamsungS_Froyo_PDA.zip?
StarWolfX0 said:
Already tried that thanks.
Edit---
Does anyone have the Odin zip EUGENE373_SamsungS_Froyo_PDA.zip?
Click to expand...
Click to collapse
You will find it for sure if you google it...that's the way that i found it but i'm on phone now and don't have the link...
Sent from my SGH-T959 using XDA
I have been looking for it, but all I find are 4shared links that are the same and invalid. So I am screwed at the moment. I am not sure what else that I could try.
StarWolfX0 said:
Does anyone have the Odin zip EUGENE373_SamsungS_Froyo_PDA.zip?
Click to expand...
Click to collapse
I can't link it bc I am mobile but if you go to the Vibrant section on Rootzwiki, Br1ckd's ICZen thread bottom of OP or post #2, you can find Eugene's rom
Thanks. Their is another post on XDA, but it only on MultiUpload. Is Multiupload down? All I get is a white screen.
If anyone could mirror when they have a chance that would be great!
Multi went down shortly after Mega went down.
Go here and download it. Or here if you don't want to stray away from XDA.
Thanks my friend! I was able to get into a ROM! However I discovered that I did not need it. I will use the ROM for emergencies in case I do. I found out that I pushed the wrong Update.zip file. I installed the root_update.zip and not cwm_update.zip. I do not think the root Update works well with Eugene's ROM anyway. Once I did that I was able to get ICS back up.
However I still have the Froyo Bootloader, and would like to update to Gingerbread. I tried flashing the GB bootloader, but it errored out looking for the PIT file and had to re-flash to stock. I will try again later, but just happy to get the phone working.
With a JIG this phone I would say, like most of you agree with, is very difficult to truly brick!
Thanks again all.
So here's what happened. I installed the kj6 cf root kernel then tried to install slimrom 4.2.2 build 8. I got stuck on semaphore logo, converted back to stock jfd with odin and now i'm stuck on the vibrant logo bootloop. My internal (i assume internal, may be external sd) storage is formatted horribly wrong as well because cwr keeps giving me errors about it and any rom I try to install fails or softbricks me. I've scoured the intered trying to figure out how to fix it but I can't. Please tell me this is fixable
agilma said:
So here's what happened. I installed the kj6 cf root kernel then tried to install slimrom 4.2.2 build 8. I got stuck on semaphore logo, converted back to stock jfd with odin and now i'm stuck on the vibrant logo bootloop. My internal (i assume internal, may be external sd) storage is formatted horribly wrong as well because cwr keeps giving me errors about it and any rom I try to install fails or softbricks me. I've scoured the intered trying to figure out how to fix it but I can't. Please tell me this is fixable
Click to expand...
Click to collapse
There is hope. I can link all the files to you later because I'm busy now, but I can tell you the way. I'm assuming you already have Odin and all the stock .pda and .tar files. So first flash the .pit and .tar and then flash the .pit and a file called dbdata which should be everywhere if you look for it. The dbdata file should mount your system and fix that problem. Also make sure you have re-format checked. If I remember right just playing around with those helped me with the same problem. I think the dbdata didn't work the first few tries then I tried something else and it worked. Let me know how it goes and I'll try to help you from there
Thank you.I did the pit and tar but didn't know about dbdata. Not sure if this helps or hinders but I have a 959v and it seems like its a 4gs istead of a vibrant. I thought they were the same but I see a separate forum for it. Ill check out posts there but if what you suggests works I'll be very appreciatve
Sent from my K00F using xda app-developers app
agilma said:
Thank you.I did the pit and tar but didn't know about dbdata. Not sure if this helps or hinders but I have a 959v and it seems like its a 4gs istead of a vibrant. I thought they were the same but I see a separate forum for it. Ill check out posts there but if what you suggests works I'll be very appreciatve
Sent from my K00F using xda app-developers app
Click to expand...
Click to collapse
Haha well if you don't have a vibrant you might want to make sure you have the correct .pit and .tar first. That's why is soft-bricked
That probably would explain my problem. I did just find that out yesterday, after I bricked it. I assumed the tar was for a variety of models since the file name included a couple letters that I thought might be different models . I'm guessing the pit is only for the vibrant. I'll head over to the s4g forum and see what I can find
Sent from my K00F using xda app-developers app