[Q] Odin successful. Still in boot loop. - Vibrant Q&A, Help & Troubleshooting

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...

Related

[Q] Help! I have both AT&T and Vibrant Start Screens :(

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

So is my Vibrant bricked?

I partitioned my SD card using ROM Manager, turned the phone off and got a black screen with lit keys. So, I read around and was told to use ODIN to reflash the stock TMO build, so I did. Now, Im getting the TMO logo and Galaxy S screen, but I get a black screen still.
I cannot get into download mode. I vol - and power and I get the Vibrant logo, then it goes back off. Even when plugged it, I get the batt charging animation, then back to the Vibrant screen.
I tried to push the update.zip to the SD card through ADB, but I get a permission denied message, meaning the root was killed.
So, is this phone pretty much screwed? I cant think of any other way to get it going outside of moving the update.zip to the sd card by a 3rd party measure i.e card reader/another phone
dude that's not even close to a brick as the phone is still responsive somehow..
do this:
1. pull out battery wait 5-10secs
2. connect USB to computer and phone
3. hold down the vol +/- buttons
4. plug in battery
5. you should be in download mode now
6. do what you gotta do with ODIN
good luck
Dont use that method to get to DL mode . Do it this way . First turn off your phone , then plug the usb cable into your computer ONLY . Next hold both volume buttons and plug the micro usb into your phone . Also use odin v1.3 and flash the rom of your preference .
Edit : xtone beat me to the punch
trill12 said:
I partitioned my SD card using ROM Manager, turned the phone off and got a black screen with lit keys. So, I read around and was told to use ODIN to reflash the stock TMO build, so I did. Now, Im getting the TMO logo and Galaxy S screen, but I get a black screen still.
I cannot get into download mode. I vol - and power and I get the Vibrant logo, then it goes back off. Even when plugged it, I get the batt charging animation, then back to the Vibrant screen.
I tried to push the update.zip to the SD card through ADB, but I get a permission denied message, meaning the root was killed.
So, is this phone pretty much screwed? I cant think of any other way to get it going outside of moving the update.zip to the sd card by a 3rd party measure i.e card reader/another phone
Click to expand...
Click to collapse
Yes using ROM Manager to repartition your phone will create the "soft-brick" you are experiencing. But as one person has already noted, this can pretty much be recovered using ODIN.
Definitely follow the advice given in Posts 2 and 3 of this thread to get into Download mode. If you're not getting the desired results using ODIN, what settings are you using? For example, what are the names of the .pit and .tar files you are using? Did you check or leave unchecked the "re-partition" option?
Sorry for the noobery. Im usually good at this.
Well, I was able to get into download mode and get ODIN to run, but im getting a MBD checksum error when I boot into recovery.
And I cannot install CWM through the market because my Application Storage is at 0.00B for some reason.
trill12 said:
Sorry for the noobery. Im usually good at this.
Well, I was able to get into download mode and get ODIN to run, but im getting a MBD checksum error when I boot into recovery.
And I cannot install CWM through the market because my Application Storage is at 0.00B for some reason.
Click to expand...
Click to collapse
What ROM did you flash. You might want to perform a factory reset and then flash the stock JFD ROM and see if that fixes your problem.
Good luck.
Oh this is a nightmare.... exactly what happened to me.
I'll be honest, I tried and tried and tried all sorts of stuff and somehow I got it back reading again.
I would ODIN to Eugenes Froyo that doesn't brick and see where that gets you. Thread is in developers section and I am pretty sure that's what got me back working but follow ALL the instructions. With no application room I couldn't push, unistall, install ect...
blizzard1017 said:
Oh this is a nightmare.... exactly what happened to me.
I'll be honest, I tried and tried and tried all sorts of stuff and somehow I got it back reading again.
I would ODIN to Eugenes Froyo that doesn't brick and see where that gets you. Thread is in developers section and I am pretty sure that's what got me back working but follow ALL the instructions. With no application room I couldn't push, unistall, install ect...
Click to expand...
Click to collapse
That's only needed if he flashed a rom with the wrong kernel or if he flashed a rom without disabling voodoo .
Sent from my SGH-T959 using XDA App
Just get to DL mode as xtone and I stated in post 2 & 3 . Then flashed to JFD with odin v1.3 and click the repartition box in odin and you'll be fine .
Sent from my SGH-T959 using XDA App
I had this problem for the last two days, but I found a way to fix it thanks to a user (whom I don't know the name of)
I did this to go back to stock firmware (JFD), make sure you have that downloaded.
Look for Eugene's Galaxy S Froyo PDA, for the i9000, not the Vibrant. Flash it through Odin with the 512 pit file. It's not going to boot up but take you to recovery mode instead, and it's going to remap your Volume buttons, but you can still get into DL mode (up is now down, and vice versa but whatever)
Now Odin back to stock, using the same 512 pit and there you go! Should boot up with no problem. Now you can redo everything, but remember to never partition through ROM Manager ever again!
Sent from my SGH-T959 using XDA App
Is there a link you could provide him?
AgentFour20 said:
That's only needed if he flashed a rom with the wrong kernel or if he flashed a rom without disabling voodoo .
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
His exact symptoms happened to me when the noob in me decided to repartition in Rom Manager awhile back. I am just suggesting he uses this tool as an option. It's definitely a good tool to use regardless of how he got where he got.
something like this happened to a buddy of mine, i'm trying to fix it, but the guy was completely stock so it makes no sense... I've tried everything, and i cant seem to find eugenes files...
Mr.Duck said:
something like this happened to a buddy of mine, i'm trying to fix it, but the guy was completely stock so it makes no sense... I've tried everything, and i cant seem to find eugenes files...
Click to expand...
Click to collapse
Eugenes rom are on his new site www.eb-production.proboards.com
Sent from my SGH-T959 using XDA App
OK, I got it fixed. Heres how.
I was finally able to get into ODIN and flash Eugenes Froyo.
So, from there, I was getting an MD5 checksum error when Id try to get into recovery, and I couldnt install the ROM Manager from the Market
Well, upon inspection of a the Nero V3 build I had downloaded, there was a ROMManager.apk there. So I pushed it onto my phone, reflashed to CWR (had to do it about 3 times) and reinstalled Nero V3.
After installing the build, I was able to re-enable voodoo and its theres no more MD5 craziness when I access the Recovery
trill12 said:
OK, I got it fixed. Heres how.
I was finally able to get into ODIN and flash Eugenes Froyo.
So, from there, I was getting an MD5 checksum error when Id try to get into recovery, and I couldnt install the ROM Manager from the Market
Well, upon inspection of a the Nero V3 build I had downloaded, there was a ROMManager.apk there. So I pushed it onto my phone, reflashed to CWR (had to do it about 3 times) and reinstalled Nero V3.
After installing the build, I was able to re-enable voodoo and its theres no more MD5 craziness when I access the Recovery
Click to expand...
Click to collapse
So voodoo was the culprit . lmao
I dont remember you ever mentioning that . Any way glad you figured it out and have your phone back .
AgentFour20 said:
So voodoo was the culprit . lmao
I dont remember you ever mentioning that . Any way glad you figured it out and have your phone back .
Click to expand...
Click to collapse
Apparently. Completely forgot I attempted to enable it. I was freaked all the way out trying to repair the damn thing.

[Q] Stuck at vibrant screen after odin

Ok, I was restoring my phone to stock with odin following these stpes
Disable Voodoo
Odin to eugenes froyo that wont brick
sticks at vibrant screen
tried odining to JFD
odin completes but still hangs at the vibrant screen
I have tried with and with out repartition checked and I am able to enter and exit download mode freely, I have tried 3 differnt versions of odin and 2 different downloads of the pda and pits. Any help would be great.
EDIT, Odin is finishing at the pass stage when the phone attempts to boot Currently flashing the JI6 seeing if it works.
Still not getting anywhere, I have now tried to odin to eugenes froyo, JFD, JI6, all which end the same with out a boot screen, I can get download but no recovery.
From my understanding when you flash eugenes froyo that wont brick the boot animation should change to the international one, mine has not done that so I am starting to wonder if there is an issue with the flashes themself.
How long did you wait after flashing the stock firmware? The first boot usually takes a while after an Odin. Did Odin finish flashing everything to the point that it said restart in blue?
You can find instructions to revert to stock http://forum.xda-developers.com/showthread.php?t=734475
I've gotten myself out of some pretty bad "bricks" with JFD and ODIN... make sure you also use the stock .pit file and you can check repartition, use JFD and should fix you right up.
I have waited for 10-15 minutes after it says restart and then sometimes after it says pass, and I have done to jfd and stock pit.
left phone at boot fell asleep woke up hr or so later still at vibrant screen, still cannot access recovery but can access download mode.
To OP. What custom rom did you run before flashing back to stock? Have you recovered?
iynfynity said:
To OP. What custom rom did you run before flashing back to stock? Have you recovered?
Click to expand...
Click to collapse
I was on axura the newest one and did not like it that much tbh had tons of processes starting nonstop and was constantly down to 35m of memory while idle. No I have not recoverd, I have flashed every combo I can think of with ODIN but alas have had no luck.
Currently it is being warrantied out for a free replacement.
ionic7 said:
I was on axura the newest one and did not like it that much tbh had tons of processes starting nonstop and was constantly down to 35m of memory while idle. No I have not recoverd, I have flashed every combo I can think of with ODIN but alas have had no luck.
Currently it is being warrantied out for a free replacement.
Click to expand...
Click to collapse
orage
So tired.... I am in the same boat. But I get to flash Eugenes froyo but i have 0 room in app storage. Then When I try to Odin to stock JFD and stock .pit it all goes well untill I get to recovery and it tells me in red text "data wipe failed"
The phone reboots and goes black after the galaxy s animation.
You think samsung will fix it for me? I go the phone in July 2010.
To OP.
have you tried flashing eugenes froyo that doesn't brick? I can't understand why a lot of these bricks are happening right now. Especially when you do flash your phone back to stock.
iynfynity said:
To OP.
have you tried flashing eugenes froyo that doesn't brick? I can't understand why a lot of these bricks are happening right now. Especially when you do flash your phone back to stock.
Click to expand...
Click to collapse
Yes read the first post it says what i have flashed.
Charlie Brown said:
orage
So tired.... I am in the same boat. But I get to flash Eugenes froyo but i have 0 room in app storage. Then When I try to Odin to stock JFD and stock .pit it all goes well untill I get to recovery and it tells me in red text "data wipe failed"
The phone reboots and goes black after the galaxy s animation.
You think samsung will fix it for me? I go the phone in July 2010.
Click to expand...
Click to collapse
How would I know if samsung will fix it.. I called tmobile said it got bricked while doing JI6 boom problem solved. Their support is not that great though he was having me try to access root by calling it a secert master menu, then asked if i tethered my comp to it but his definition of tether was syncing files I was just playing dumb and letting him ask me his questions
ionic7 said:
How would I know if samsung will fix it.. I called tmobile said it got bricked while doing JI6 boom problem solved. Their support is not that great though he was having me try to access root by calling it a secert master menu, then asked if i tethered my comp to it but his definition of tether was syncing files I was just playing dumb and letting him ask me his questions
Click to expand...
Click to collapse
Rooting your device and flashing custom roms onto it voids your warranty from t-mobile. You are wasting your time trying to see if they will help, This is NOT in their job description. They might laugh at you.
@OP Try flashing to a TRUE stock firmware, I personally would not flash from a custom rom to another custom rom, does that make sense? You should go back to t-mobiles legit 2.1. There is a link in the Bible here under the Dev forum. But, The link is broken. So Ive uploaded it here http://www.mediafire.com/?8kw71bx06an0vwg
Don't give up on odin yet, try things like changing your usb ports on the computer, this has worked for me. I also have a video tutorial using odin, it might be of some help to you. http://forum.xda-developers.com/showpost.php?p=10207377&postcount=1
Good luck!
ionic7 said:
Yes read the first post it says what i have flashed.
Click to expand...
Click to collapse
try that again.
Sent from my SGH-T959 using XDA App
Im having the same issue with, "Data Wipe Failed" and have 0.00 space in Application storage but my phone reboots into eugenes 2.2 perfectly fine and works, but the application storage seems to be empty still...very frustrating.
cvibe88 said:
Rooting your device and flashing custom roms onto it voids your warranty from t-mobile. You are wasting your time trying to see if they will help, This is NOT in their job description. They might laugh at you.
@OP Try flashing to a TRUE stock firmware, I personally would not flash from a custom rom to another custom rom, does that make sense? You should go back to t-mobiles legit 2.1. There is a link in the Bible here under the Dev forum. But, The link is broken. So Ive uploaded it here http://www.mediafire.com/?8kw71bx06an0vwg
Don't give up on odin yet, try things like changing your usb ports on the computer, this has worked for me. I also have a video tutorial using odin, it might be of some help to you. http://forum.xda-developers.com/showpost.php?p=10207377&postcount=1
Good luck!
Click to expand...
Click to collapse
have changed usb cord, port, computer, have flashed jfd ji6 froyo that wont brick, 512 pit,513 pit,and they have not laughed at me in anyway they are sending my new phone now and a g2 to try out soo either way I have something soon. I also was going from axura to stock to a custom rom not from one to the other and I do know how to use odin, I know what I am doing just need help figuring this one out has to be something im missing or its just not gonna work. 50 odins and nothing kinda says it all.
I am in the same boat.. tried ODIN + stock ROM from various sources, nothing seems to work.. am I out of luck ??

Solution for random boot loop? (not from flashing)

I'm not noob to flashing or soft brick recovering but this has me confused...
I was running unNamed lastest for a lil while now. Everything was working fine until here recently, while stopped at a rest area checking a webpage my phone cut of and got stuck on a boot loop, only showing the kernal splash screen. Was like wtf? Tried pulling battery ,wiping cache and dalvik. No help. Was like that's fine, have a cwm back up from week ago. Nope didnt work. Was like ok let me try flashing something on my phone that's saved on sd. Flashed Miui, didn't work. Finally got back and tried using this Odin One click "Odin3 One-Click Downloader Stock I-777 UCKH7 with Root no BL" by entropy from the flashing without triggering flash counter guide. Still boot loops only showing the black Samsung Galaxy S II screen. This is after 3 what the odin says as 3 successful flash attempts.
I'm at my wits end, of all the soft bricking i've recovered from, where I assumed as long as a bad bootloader flash didn't happen and i could still get to download mode I'm fine, it could be fixed. But this has me stumped.
*After going into 3e recovery and trying to wipe data, it won't even now go back into 3e recovery. Attempts to but says something like deleting cryption meta data or something of that nature.
-confused-
Nerz said:
I'm not noob to flashing or soft brick recovering but this has me confused...
I was running unNamed lastest for a lil while now. Everything was working fine until here recently, while stopped at a rest area checking a webpage my phone cut of and got stuck on a boot loop, only showing the kernal splash screen. Was like wtf? Tried pulling battery ,wiping cache and dalvik. No help. Was like that's fine, have a cwm back up from week ago. Nope didnt work. Was like ok let me try flashing something on my phone that's saved on sd. Flashed Miui, didn't work. Finally got back and tried using this Odin One click "Odin3 One-Click Downloader Stock I-777 UCKH7 with Root no BL" by entropy from the flashing without triggering flash counter guide. Still boot loops only showing the black Samsung Galaxy S II screen. This is after 3 what the odin says as 3 successful flash attempts.
I'm at my wits end, of all the soft bricking i've recovered from, where I assumed as long as a bad bootloader flash didn't happen and i could still get to download mode I'm fine, it could be fixed. But this has me stumped.
*After going into 3e recovery and trying to wipe data, it won't even now go back into 3e recovery. Attempts to but says something like deleting cryption meta data or something of that nature.
-confused-
Click to expand...
Click to collapse
The one-click downloader is NOT from me, it's a repack of my tar file - and it's starting to sound like the one-click is doing something weird and not flashing the kernel properly.
Use regular old Odin (or Heimdall) to flash the raw tar package.
I'll try it. Though I don't understand how I am in the position I am in from browsing the web on my phone to directly going into a hootloop that neither that odin one click will fix, or any cwm roms won't fix.
Sent from my GT-I9000 using XDA App
I won't have access to computer till later today but I'm trying to figure out what could be wrong. I was thinking that maybe my partitions were bad, but doesn't that odin used, repartition, using a pit file (think that is what pit is for)? Although, this was not from a flash, but rebooted from a couple weeks old successful flash of unNamed while browsing the web so I don't see how that can be the problem. However, even if the partitions were bad, wouldn't odin fail a flash because it has no where to send the firmware files? Also if it was a type of hardware failure, such as processor, wouldn't it not even show the kernel Galaxy S II splash screen? Or is this something that only the gpu handles? It was able to get into cwm before I used the odin though so I can't believe it's cpu because I'm sure that recovery should use it. Just can't figure it out, never had a problem with a boot loop a flash couldn't fix.
If I can't get it to work, will flashing a stock kernel with cwm increment the flash counter? If not I guess I could access my internal sd, try and pull my pictures and the roms off there and then send it to warranty. However I really don't want to. Thanks to anyone in advance.
Sent from my GT-I9000 using XDA App
Nerz said:
I won't have access to computer till later today but I'm trying to figure out what could be wrong. I was thinking that maybe my partitions were bad, but doesn't that odin used, repartition, using a pit file (think that is what pit is for)? Although, this was not from a flash, but rebooted from a couple weeks old successful flash of unNamed while browsing the web so I don't see how that can be the problem. However, even if the partitions were bad, wouldn't odin fail a flash because it has no where to send the firmware files? Also if it was a type of hardware failure, such as processor, wouldn't it not even show the kernel Galaxy S II splash screen? Or is this something that only the gpu handles? It was able to get into cwm before I used the odin though so I can't believe it's cpu because I'm sure that recovery should use it. Just can't figure it out, never had a problem with a boot loop a flash couldn't fix.
If I can't get it to work, will flashing a stock kernel with cwm increment the flash counter? If not I guess I could access my internal sd, try and pull my pictures and the roms off there and then send it to warranty. However I really don't want to. Thanks to anyone in advance.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Ok so after flashing the odin file from http://forum.xda-developers.com/showthread.php?t=1286432 it is still bootlooping at splash screen.
I'm not sure what my options are right now. I'm pretty sure bootloaders can't be the problem. I can't re-partition from odin because it says it can't open the specified file "(Line: 1828)". Is this because it doesn't have pit file? I don't understand how this problem manifested.
If I need to pull contents from sd card from cwm, will flashing a cwm kernal increment flash counter?
Don't repartition using a PIT, it's a great way to screw up your phone. (Hopefully you haven't flashed a PIT at all yet... If you have, I don't quite know what's going on.)
Sent from my GT-P7510 using Tapatalk
Entropy512 said:
Don't repartition using a PIT, it's a great way to screw up your phone. (Hopefully you haven't flashed a PIT at all yet... If you have, I don't quite know what's going on.)
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
Have yet to flash a pit file.
Sent from my GT-I9000 using XDA App
I'm in the same situation, except with a Sprint GSII. Have you found a fix, yet?
Juq said:
I'm in the same situation, except with a Sprint GSII. Have you found a fix, yet?
Click to expand...
Click to collapse
Hello there from colombia, i have the same thing over here, i`m stuck with a SGS SGH I777 the flash counter says 7 and either flashing CWM 5 or re-uploading stock room wont work, i have no way to buy a jig and it is pretty odd that im in a different country and i can`t send my phone for warranty repair, i`ve read all over and seems like there is no answer for this. Can anyone get rid of the Deleting Crytion Meta data?? this is all i get. ( and eternal boot loop ).
Thanks in advance.
hardgrid said:
Hello there from colombia, i have the same thing over here, i`m stuck with a SGS SGH I777 the flash counter says 7 and either flashing CWM 5 or re-uploading stock room wont work, i have no way to buy a jig and it is pretty odd that im in a different country and i can`t send my phone for warranty repair, i`ve read all over and seems like there is no answer for this. Can anyone get rid of the Deleting Crytion Meta data?? this is all i get. ( and eternal boot loop ).
Thanks in advance.
Click to expand...
Click to collapse
Will try to help, but will need more specific information.
The OP of this thread started bootlooping while checking a web page in his browser. So, how did it happen for you? Please give as much exact information as possible. Was it after a flash? Or did it start while you were using the phone? Or how?
Mine was connected to an aftermarket car charger while it happened. I read a post somewhere and a couple ppl it happened to believed the same thing, since it was in my 30 day trail period I sent it back to Sams club and got my replacement today. Since I didn't have a jig at the time, I didn't want to flash a cwm kernel and increase my flash counter so I lost some pics of my kids.
Not sure if it was charger related but I couldn't find a fix and wouldn't really call myself a noob at flashing. Might have some things to learn nut far from a noob.
Sent from my I897 using XDA App

[Q] Vibrant Black Screen on First Boot After Odin

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.

Categories

Resources