Related
I have a Fascinate. And it shows no signal. A circle with a line through it at the top. When I go into Baseband Version it says unknown. And hardware version does also. How can i fix this? I was thinking the modem.bin file would fix it. But all i can find is the epic modem.
Have you tried activating it? Dial *228 option 1. If that doesn't work try *228 option 2.
that doesn't do anything. its as if i don't have a radio. no signal at all. service is great in the area.
nuthin2los said:
that doesn't do anything. its as if i don't have a radio. no signal at all. service is great in the area.
Click to expand...
Click to collapse
have you tried updating radio to newest version in DI01?
how would i do that is i dont have service?
I doubt there is anything you will be able to do about it. Just get it warranty replaced; it's a hardware failure. Same thing happened on my Droid1.
Unfortunately, you have nice little PDA device, but it will no longer be usable as a phone.
We've seen a number of these, and not one has been saved yet. We simply do not have the modem.bin file to replace it with.
This happens when you flash anything using the "PHONE" box in Odin, not the "PDA" box. It will also happen if you flash another carriers modem.bin file over yours, regardless of which box you choose. Always, always, use the "PDA" box in Odin.
There's only two things to do at this point.. Wait until we get a modem.bin, or exchange the unit.
DI01 modem.bin is available. I'm not sure if the stock one is as well.
forum.xda-developers.com/showpost.php?p=8279071&postcount=1
CrimsonSentinel13 said:
DI01 modem.bin is available. I'm not sure if the stock one is as well.
forum.xda-developers.com/showpost.php?p=8279071&postcount=1
Click to expand...
Click to collapse
That's an update to the modem.bin, not the actual modem.bin file. It won't work if you have the same problem as the OP.
Feel free to try it. I guarantee it won't work, but you can't make anything worse at this point. We can recover from just about everything, except the modem.bin issue.
still no modem.bin???
I'm having a similar issue. How do I get this fixed?Do I go to verizon, or samsung? the samsung webpage told me to call a representattive, so I'm assuming there is no repair spot in my area.
Besides, I bought this over ebay (it was mint condition). Do I still have warranty?
Thanks everyone for any help
no warranty 4 u..my problem is the same as your and the wont send a replaacement because i ddnt nuy from a vzw store smh
There is a fix for this over at droid forums a post by me in the Samsung Fascinate Development section this forum wont let me post a link
PM me
Sent from my SCH-I500 using XDA App
trapstarr56 said:
still no modem.bin???
Click to expand...
Click to collapse
It bugs the hell out of me to post this as it is untested, but if the phone is already bricked (flashed via PHONE in Odin or flashed a ROM made for something *other* than the Fascinate), this thread seems to have a modem.bin.
http://forum.xda-developers.com/showthread.php?t=842625
Again....and I cannot stress this enough: DO NOT USE THIS FILE. FOR ANYTHING.
PERIOD.
(unless you used the "PHONE" option in Odin or flashed a non-fascinate ROM)
OOPS! I messed up in odin when flashing my first rom, with my new $200 phone my dad bought me two days ago. As you can imagine I am extremely sad, and I need some help. Anyways, I think I did something in Odin that messed up my modem.bin, which explains why i have a circle with a line throught it on my notification bar where the signal status would usually be. So, I thought, the DJ05 update has modem.tar, and I flashed that with Odin, but I still have that same circle with a line through it. Plz Help
Flash in PDA. Not phone.
Good luck.
Sent from my SCH-I500 using XDA App
yes, if you are lucky PDA will work... Try it and if it doesn't work, there are other things you can do.
But if you're not going to read and respond to this thread. I'm just wasting my time typing this out for you.
Been doing
Thats what I've been doing, I flashed it in PDA before flashing the rest of DJ05. I have read, and Im not just posting this without looking.
-Dan
Edit:
Do I need a PIT file to flash the modem, because I haven't been using one.
No, you don't need a PIT file with the modem. What did you flash initially that started this problem? There may not be anything you can do.
Sign up for the extra insurance. Step on your phone, pay the $80 deductible and get a new phone. Cancel insurance.
Well, I rooted it, installed clockwork mod, and then the SuperClean Rom. Then I decided to go back to my Nandroid backup, but that was unsuccesful so I went to do something in Odin (I think I was trying to restore to DJ05 again). Please tell me all of my options. Im already extremely upset, and the phone was bought off Ebay N.I.B so there is no option of that insurance.
Do you know exactly what it was that you flashed via Odin and how you did it? Was it something in this forum, another forum? Was it something for the Telus Fascinate? Did you use the phone button or pda button when flashing?
To be honest, I really cant remember what I was flashing, I as probabley trying to re-install DI01. It wasn't anything from Telus or the Vibrant, it was specifically for Verizon. And I always did it in PDA. Except today I flashed the DJ05 modem.tar using phone. Hope thats not bad.
dandog96 said:
Except today I flashed the DJ05 modem.tar using phone. Hope thats not bad.
Click to expand...
Click to collapse
That would be the problem, and there isn't a fix as far as I'm aware.
Ok, well even without that, my point is I did this about an hour ago. And even before every flashing in phone I had this problem. I am so upset.
Please post in the relevant forum next time.
Thank you.
nir36 said:
Please post in the relevant forum next time.
Thank you.
Click to expand...
Click to collapse
My apologies. Any Updates?
If you flashed via the Phone button at any point, your phone is no longer usable or fixable unless someone has found a fix that I haven't seen yet. Whether the problem started before you used the phone button or not, using the phone button pretty much guaranteed there is no way to fix it.
Im a NOOB so I might not be right, but here is my argument. There have been people with the same prob. that pressed the phone button before. Theyre solution has been to flash a new modem.bin. I just want to know WHY after having the same problem as other people, and taking the same solution my phone still doesnt work. I don't know, maybe im just not willing to take a broken phone as an answer.... but...
dandog96 said:
Im a NOOB so I might not be right, but here is my argument. There have been people with the same prob. that pressed the phone button before. Theyre solution has been to flash a new modem.bin. I just want to know WHY after having the same problem as other people, and taking the same solution my phone still doesnt work. I don't know, maybe im just not willing to take a broken phone as an answer.... but...
Click to expand...
Click to collapse
As far as I know, no one has recovered their phone after flashing the modem via the Phone button. Any links to support that?
imnuts said:
As far as I know, no one has recovered their phone after flashing the modem via the Phone button. Any links to support that?
Click to expand...
Click to collapse
http://www.droidforums.net/forum/samsung-fascinate-development/97808-modem-bin-no-signal-fix.html
Right now Im going to Odin restore DI01 stock to my Fascinate and then try and OTA update via Wi-Fi if that is possible.
You can't update OTA via wifi... That contradicts itself. And if you are flashing to stock DI01, what are you hoping to update to? DL09 isn't available yet.
Have you tried flashing the all in one di01 by adrynalyne? That may be you only option.
Also, samsung gives a warranty, you might be able to take it to vzw in worst case scenario.
Kevin Gossett said:
You can't update OTA via wifi... That contradicts itself. And if you are flashing to stock DI01, what are you hoping to update to? DL09 isn't available yet.
Click to expand...
Click to collapse
Welk as I read on x.d.a today dl09 was officially released for download by ota. Im 90% sure
So, I just thought I would come here to let everyone know what the SBL actually does to your phone. Me, being a dev, am always flashing test stuff.
The SBL is actually a fix for the Phone-!-PC soft brick screen.
It allows you to flash with ODIN while on that screen. I've tested this SBL through and through and haven't seen any issues with it.
krylon360 said:
So, I just thought I would come here to let everyone know what the SBL actually does to your phone. Me, being a dev, am always flashing test stuff.
The SBL is actually a fix for the Phone-!-PC soft brick screen.
It allows you to flash with ODIN while on that screen. I've tested this SBL through and through and haven't seen any issues with it.
Click to expand...
Click to collapse
Hmmm never even heard of that screen before lol... but I was hearing stories of people able to get ODIN to recognize their phone while it was completely off. Can you confirm if that is true or not?
Wow that puts that scare to rest. thanks krylon of teamwhiskey!
I knew it....been sayin that all along.. thx for confirming that for us..
Settai said:
Hmmm never even heard of that screen before lol... but I was hearing stories of people able to get ODIN to recognize their phone while it was completely off. Can you confirm if that is true or not?
Click to expand...
Click to collapse
False. ODIN will not see the phone while it is off...
*looks at his dead vibrant sitting on the desk hooked to the PC with ODIN open.
The Phone-!-PC screen is the softbrick screen you get when you have a bad ODIN flash.
Thanks Krylon........ BTw your name is a brand of paint
thanks for the confirmation there krylon.
do you have any idea on why or how so many ppl ended up bricking trying to go to Bionix-v? originally, i thought it was the sbl doing it and that's why i never flashed it.
krylon360 said:
So, I just thought I would come here to let everyone know what the SBL actually does to your phone. Me, being a dev, am always flashing test stuff.
The SBL is actually a fix for the Phone-!-PC soft brick screen.
It allows you to flash with ODIN while on that screen. I've tested this SBL through and through and haven't seen any issues with it.
Click to expand...
Click to collapse
so that's what happened to me the other day...I had a bad flash in Odin and that screen came on....but Odin did reconnise the phone and I was able to flash it....I guess Sammy has been looking out for us the "flashers"
Oniyuri said:
thanks for the confirmation there krylon.
do you have any idea on why or how so many ppl ended up bricking trying to go to Bionix-v? originally, i thought it was the sbl doing it and that's why i never flashed it.
Click to expand...
Click to collapse
Bricking as in Soft Bricking? or Bricking as in the brick I have laying on my desk.
krylon360 said:
False. ODIN will not see the phone while it is off...
*looks at his dead vibrant sitting on the desk hooked to the PC with ODIN open.
The Phone-!-PC screen is the softbrick screen you get when you have a bad ODIN flash.
Click to expand...
Click to collapse
Ahhh got ya man thanks for the info, hope you get your new vibrant soon man
krylon360 said:
Bricking as in Soft Bricking? or Bricking as in the brick I have laying on my desk.
Click to expand...
Click to collapse
Brick as in your brick
Settai said:
Brick as in your brick
Click to expand...
Click to collapse
^yes that. some ppl in the Bionix-v thread here and the one on the TW forums have reported hard bricks after flashing (i think one was even coming from Nerov5 which stopped me in my tracks). Since I'm not in the US atm, I definitely don't want to take any chances.
Settai said:
Brick as in your brick
Click to expand...
Click to collapse
SBL wont do that.
You PBL (Primary Bootloader) crashed.
If some how the SBL became corrupt during the DL, it might have corrupted the PBL.
Mine bricked due to flashing the PBL and SBL for the 4G, then ODINing to JFD and flashing the JI6 SBL. my PBL was already hosed.
krylon360 said:
SBL wont do that.
You PBL (Primary Bootloader) crashed.
Click to expand...
Click to collapse
ah... but what could cause a pbl to crash while flashing? i really do wanna investigate the issue as ppl have also been bricking doing the otc froyo update too (but then again, i automatically figured it was kiesmini in the first place).
krylon360 said:
SBL wont do that.
You PBL (Primary Bootloader) crashed.
If some how the SBL became corrupt during the DL, it might have corrupted the PBL.
Mine bricked due to flashing the PBL and SBL for the 4G, then ODINing to JFD and flashing the JI6 SBL. my PBL was already hosed.
Click to expand...
Click to collapse
Looks like there was at least one more hard brick today, he was going to Bionix V BUT went to it following a bad Odin. Maybe others are doing the same thing, f-ing up an odin or flash and then trying to recover by flashing whatever is on their sdcard?
http://forum.xda-developers.com/showthread.php?t=936389
I suppose that is the downside to Bionix being so popular, it just happens to be the Rom they are flashing at that moment.
jellette said:
Looks like there was at least one more hard brick today, he was going to Bionix V BUT went to it following a bad Odin. Maybe others are doing the same thing, f-ing up an odin or flash and then trying to recover by flashing whatever is on their sdcard?
http://forum.xda-developers.com/showthread.php?t=936389
Click to expand...
Click to collapse
I can tell you that wasn't the scenario in my case. I had been running the same rom for a couple of days, saw that Bionix V was released, and decided to flash it. I backed up some updated apps with titanium, backed up call logs, sms, etc with MyBackup Pro, rebooted into clockworkmod recovery, did a nandroid, then flashed bionix V. The install finished and returned to the CMRecovery menu, I selected "reboot system now", and that was it. Phone was dead on arrival
jellette said:
Looks like there was at least one more hard brick today, he was going to Bionix V BUT went to it following a bad Odin. Maybe others are doing the same thing, f-ing up an odin or flash and then trying to recover by flashing whatever is on their sdcard?
http://forum.xda-developers.com/showthread.php?t=936389
Click to expand...
Click to collapse
I responded. I have a feeling it's when ODIN crashes thats causing the corruption within the PBL.
I've got a new flashing tool...(Not ODIN, nor Heimdall) Lets just say, it's for the Sidekick 4G as well as the Orion...oh, and I have a new ODIN version, and a new Pit file for the Sidekick 4G and Orion and Vib 4G...
Once I get my new phone, I'll test out the new flashing app.
Alkaloid said:
I can tell you that wasn't the scenario in my case. I had been running the same rom for a couple of days, saw that Bionix V was released, and decided to flash it. I backed up some updated apps with titanium, backed up call logs, sms, etc, rebooted into clockworkmod recovery, did a nandroid, then flashed bionix V. The install finished and returned to the CMRecovery menu, I selected "reboot phone now", and that was it. Phone was dead on arrival
Click to expand...
Click to collapse
When mine bricked, I had flashed an I9000 sbl, and then flashed a vibrant sbl while still on the I9000 rom - as soon as the flash ended it just went black and after just one $130 insurance claim I was up and running with a new phone..
Jellette, remember that 2.2.1 rom you were working on a while back that was posted in your repo over at TW forums? I was one of the ones who flashed that. I never could get it to work properly, but Ever since that flash my phone always booted with the "GT-I9000" start up screen then "Vibrant" screen. Also after that I always had to hold volume up and power to get into DL mode instead of vlume down or volume up & down + power which is the way I used to have to get into DL mode. I always wondered if it had some affect on the boot loader. Could this combined with the flash of the new SBL in the new boionix rom have caused the brick? It's the only thing I can think of as far as why or how my SBL shat itself.
jellette said:
When mine bricked, I had flashed an I9000 sbl, and then flashed a vibrant sbl while still on the I9000 rom - as soon as the flash ended it just went black and after just one $130 insurance claim I was up and running with a new phone..
Click to expand...
Click to collapse
hehe no insurance claim for me. Luckily I was able to get back to JFD before mine died, so just had to pay the $20 for expedited shipping.
Okay,
There is a growing number of us XDA members on the Vibrant platform who have just bricked out phones. Save for other DEV tools, which I have not used, do not have access, and do not know how to use, for all intensive purposes, this phone is Br'iKTed ! ! !
Here are the series of events
1. flashed the latest Bionix
2. Worked great, some bugs, but for the most part without incident.
3. Flashed new DOW Kernel,
4. worked great for 2 days.
5. then on night 2, the phone was stuck on the DOW Green robot screen
6. could not get into Recovery mode (none of the recovery modes)
7. Phone would not boot
8. ODIN back to stock
9. After Vibrant screen, the phone turns off. No soft keys, Nada!
10. Flashed JI5, Ji6, Eugene's Non Bricking Froyo (ODIN Files)
11. Same result, Turned off after Vibrant
and
12. still cant' get into recovery
I am having problems with the phone starting up and loading what I flashed.
I flashed JI5 Ji6, and Eugene's non bricking Froyo Rom
These 3 are the only ones I was able to find that is ODIN flashable
Why you ask?
I cannot get into Recovery, but I can get into Download mode. I can't get into any recovery at all. NOTHING. This is why ODIN seems to be my only option.
But regardless of any ROM i flash, my phone shuts off right after the Vibrant screen. No splash screen, no loading, no booting. .Nothing. It just shuts off.
I can't charge it either.
i get a Charging bootloop. HOurglass - battery shows up for a bit, then restarts over and over.
So in other words. it's ****ed.
Hope that explains it sufficiently. if you have any more questions or suggestions, Im open man, Im open.
Help me
So I'm not sure how DEVs would like to proceed on this.
TW (I've always loved your roms. Been following you since the first BIONIX 1.8)
Morific (If it's the Kernel, i'd like to know about it)
Thanks for reading guys. I wanted to give everybody a heads up.
I don't know what the problem is, but I do know that the phone does not work.
I'd appreciate some suggestions or anything.
And to inform the community that this problem is out there. I hope there aren't any more bricked phones.
Cheers,
have you tried using odin with the repartition checked
Yes I have.
Tried it with/ Without. Using Just the Tar file, using just the base file. I've tried it all.
Thanks
a4 moda said:
Yes I have.
Tried it with/ Without. Using Just the Tar file, using just the base file. I've tried it all.
Thanks
Click to expand...
Click to collapse
have you tried to odin to ka6 or ka7? something with a bootloader
not to be that guy, but how does this pertain to development? This sounds to me like an individual case of something going wrong and not an overarching issue with current available software. Just in case I am wrong I am flashing Bionix, and the DOW kernel myself to see if I end up with the same issue. My suggestion is flash back to stock, and exchange your device for a new one from T-Mobile.
I totally understand what your going through. I'm having the exact same problem, the DOW kernel flashed ok but then it didn't want to come off and it totally has my phone stuck on that damn green robot screen.
I soft-bricked my phone once by pulling USB cable immediately after ODIN forced my phone to reboot after flashing. It was the first time I ever ODIN'ed my phone, and thought the reboot (ODIN calls it reset) was the final step of flashing, and unplugged the USB cable. Anyway the phone did not initiate final step of the installation of JFD image, and went into boot loop. You can't imagine how freaked I was. It wouldn't go into recovery mode even if I pressed volume up, down and power combo, because it didn't stop rebooting right after the Vibrant logo. I am not sure if bootloader was not installed correctly, though. But I kept the phone rebooting for a while to see what happens. No luck. Eventually, I followed someone's instruction, and pulled my battery out, plugged USB to my laptop and to my phone, started ODIN, and popped in the battery. The phone immediately restarted into download mode, and I was able to flash the phone again.
My experience may not help you as it appears that you are able to flash ODIN-flashables, at least. But I hope this helps someone who's experiencing similar issues. And I would try downloading a JFD image and verifying MD5 before flashing. It could be bad downloads of the image files.
Try to go to eugenes forum and he has a file to download...it is his unofficial jk2 froyo rom. Don't use the old "froyo that does not brick" Try to flash that in ODIN. I just used it tonight when I got stuck in stock recovery with a MBR Check sum failure. That should get u back to where u can fix ur phone. Also I don't click the repartition button in ODIN just causes problems for me. If u need anything feel free to P.M. me.
Sent from my SGH-T959 using Tapatalk
STiGLOGiC said:
not to be that guy, but how does this pertain to development? This sounds to me like an individual case of something going wrong and not an overarching issue with current available software. Just in case I am wrong I am flashing Bionix, and the DOW kernel myself to see if I end up with the same issue. My suggestion is flash back to stock, and exchange your device for a new one from T-Mobile.
Click to expand...
Click to collapse
Completely reasonable. This pertains to development because if there is an endemic problem with one of our ROMS or KERNELS (not pointing fingers, just pointing out the possibilities that I know of, there could be more), people in our community need to know. Hence, I titled it "PUBLIC SERVICE ANNOUNCEMENT"
Thanks. I hear you about Tmobile. I'd rather not have to dump my problem on Tmobile if I can fix it, because I flashed the rom. Despite the fact that Tmobile JFS leaves something to be desired, they did deliver me a working phone. So i'd like to exhaust all possibilities before calling it quits.
hackman17 said:
I totally understand what your going through. I'm having the exact same problem, the DOW kernel flashed ok but then it didn't want to come off and it totally has my phone stuck on that damn green robot screen.
Click to expand...
Click to collapse
Exactly.
jaetm83 said:
I soft-bricked my phone once by pulling USB cable immediately after ODIN forced my phone to reboot after flashing. It was the first time I ever ODIN'ed my phone, and thought the reboot (ODIN calls it reset) was the final step of flashing, and unplugged the USB cable. Anyway the phone did not initiate final step of the installation of JFD image, and went into boot loop. You can't imagine how freaked I was. It wouldn't go into recovery mode even if I pressed volume up, down and power combo, because it didn't stop rebooting right after the Vibrant logo. I am not sure if bootloader was not installed correctly, though. But I kept the phone rebooting for a while to see what happens. No luck. Eventually, I followed someone's instruction, and pulled my battery out, plugged USB to my laptop and to my phone, started ODIN, and popped in the battery. The phone immediately restarted into download mode, and I was able to flash the phone again.
My experience may not help you as it appears that you are able to flash ODIN-flashables, at least. But I hope this helps someone who's experiencing similar issues. And I would try downloading a JFD image and verifying MD5 before flashing. It could be bad downloads of the image files.
Click to expand...
Click to collapse
Thanks for the heads up. I've gone through this myself many times. And i'm sure your post will help others out there. My problem (as well as many others on here with the same ROM and KERNEL I used) seems to be different and unique. Something that ODIN won't cure.
vibrant2010 said:
Try to go to eugenes forum and he has a file to download...it is his unofficial jk2 froyo rom. Don't use the old "froyo that does not brick" Try to flash that in ODIN. I just used it tonight when I got stuck in stock recovery with a MBR Check sum failure. That should get u back to where u can fix ur phone. Also I don't click the repartition button in ODIN just causes problems for me. If u need anything feel free to P.M. me.
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
Yes, tried that too. Same result. Vibrant.. then shut off.
Thanks anyway.
I had actually just had Bionix-v 1.2.1 and the new DoW combo to try out Voodoo Sound. I really loved the sound quality, but battery drain was not adequate as being my daily driver, even though I set it to run at 1ghz and used a sleep profile. After just over 2 days of use, I backed out by ODIN'ing to JFD and I installed Bionix-v 1.2.1 again. Only thing I have noticed so far is GPS not initiating immediately after it's turned on. I would go into GPS Test app, and turn on GPS after the app is started, but I get no satellites for at least 1 min. I used to get a lock within seconds, not minutes. I will try ODIN again tomorrow and see if it fixes. I guess I was lucky enough not to get a bootloop again though.
But I can't see why you and I would have any issues after the Bionix+Dow combo. Wouldn't ODIN just clear everything up? I even repartitioned when flashing, so my guess is that my system, data, datadata, etc., are all reformatted completely? Am I missing something?
I had the same problem. I flashed DoW and then the next day my phone didn't want to turn on. I pulled the battery and restarted it. It didn't want to start up all the way. It got to the vibrant screen and shut off. luckily for me, my replacement phone that I ordered a week ago came in the same day. I sent off my old phone letting samsung/tmo take care of it.
This exact same thing happened to me.
I too had the phoen bricked after flashing the DOW after Bionix 1.2.1
I have been flashing since the G1. This is the first time I've ever bricked a phone.
Hoping to get it fixed this weekend
Yo OP
Coming from a very scary brick my self, (phone wouldnt even turn on, bad dead horse test).
When your using Odin, are you using v1.7, are you using the correct stock JFD tar, when you repartion, are you using the correct pit file. Sounds to me that your partions are screwed, so try the pit approach first. If you phone wont boot at all after this, with odin open go into download mode by holding the vol rockers only, and plug USB in.
Then flash JFD.
black spirit said:
Yo OP
Coming from a very scary brick my self, (phone wouldnt even turn on, bad dead horse test).
When your using Odin, are you using v1.7, are you using the correct stock JFD tar, when you repartion, are you using the correct pit file. Sounds to me that your partions are screwed, so try the pit approach first. If you phone wont boot at all after this, with odin open go into download mode by holding the vol rockers only, and plug USB in.
Then flash JFD.
Click to expand...
Click to collapse
I spent over 12 hours working on this when it happened to me yesterday. Tried every tar and pit file and all versions of Odin I could find. There is no way to fix it with Odin. It is BRICKED!
If you have not already done this, I recommend doing this: http://forum.xda-developers.com/showthread.php?t=954509
Bay Wolf made a nice software for the computer that pretty much shows you a step-by-step instruction on how to flash to stock, reroot, and flash the new ROM of your choice. This program will push you into download mode, clockwork recovery, etc. There is a video on that link that will also show you a step-by-step instruction. Try that out if you haven't, and let us know how it goes.
That program comes with a PIT and TAR file for you to use as well.
Even if you say it is, this is not a Development thread and belongs in one of the other forums. I understand your frustration, however TW did not flash your phone, you did. Coming on here with a "PSA" that their ROM or Kernel loaded itself on your phone and broke it is not the way it should be done. Did you, before posting this, go to the TW irc for help or pm Sombionix or any other TW Dev?
Since you can Odin, Odin to stock 2.1 then connect to KIES mini while in download mode, if you can, and take the OTA.
drewdude007 said:
I spent over 12 hours working on this when it happened to me yesterday. Tried every tar and pit file and all versions of Odin I could find. There is no way to fix it with Odin. It is BRICKED!
Click to expand...
Click to collapse
I thought the same when it happen to me.
Nothing would work, but went that approach and happy days.
s1_odin_20100512.pit
and
T959UVJFD.tar
are the only ones you need, and if your good with your flashing, just do a pit first, no pda.
And if your still getting to download mode, ect, and dont have the computer /!\ phone icon on the screen, sounds like a soft brick.
jellette said:
Even if you say it is, this is not a Development thread and belongs in one of the other forums. I understand your frustration, however TW did not flash your phone, you did. Coming on here with a "PSA" that their ROM or Kernel loaded itself on your phone and broke it is not the way it should be done. Did you, before posting this, go to the TW irc for help or pm Sombionix or any other TW Dev?
Since you can Odin, Odin to stock 2.1 then connect to KIES mini while in download mode, if you can, and take the OTA.
Click to expand...
Click to collapse
I see where you're going, but he did not blame TW or anyone else. He may just be warning some people/asking for help. I do however agree that he posted in the wrong section.
Also, why would he need to pm sombionix or a TW dev before posting this?
SamVib said:
I see where you're going, but he did not blame TW or anyone else. He may just be warning some people/asking for help. I do however agree that he posted in the wrong section.
Also, why would he need to pm sombionix or a TW dev before posting this?
Click to expand...
Click to collapse
Because he started off with his problem stated as:
1. flashed the latest Bionix
2. Worked great, some bugs, but for the most part without incident.
3. Flashed new DOW Kernel,
Your phone probably IS charging.
Your /efs nodes may be messed up. Do you have a backup of your /efs?
Try reading here: http://forum.xda-developers.com/showthread.php?t=859914
I traded my Droid 2 for a fascinate last night. It was already rooted and running DL30. I have no sms/mms and want to get it working, obviously. I cant boot into cwm, I cant odin anything, and Im stuck. I dont wanna smash this phone against the wall but its heading there fast Someone please help. And before you guys start tellin me how google is my friend and all that, Im no noob, I exhausted my searchbar before posting...
How about more info then I can't do anything and im pissed. You can ALWAYS Odin
Sent from my SCH-I500 using XDA App
thatdudebutch said:
How about more info then I can't do anything and im pissed. You can ALWAYS Odin
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
If you can ALWAYS odin, would you mind telling me how? I asked for help...I know android man, this is different, I think something may be wrong with the phone.
Go to menu/settings/about. And what do the Build and Baseband say.
good day.
chopper the dog said:
Go to menu/settings/about. And what do the Build and Baseband say.
good day.
Click to expand...
Click to collapse
build is SCH-I500.DL30
baseband isS:i500.04 V.DIO1
To use Odin, you need to get into download mode. Turn the phone off, pull the battery, hold the volume down button, plug in the USB cable while continuing to hold the volume down button. Phone should now be in download mode and Odin should pick up the device (assuming you had the drivers installed as well already). When flashing anything via Odin, be sure to use the PDA button.
The issue sounds like you just need a new modem flashed to the phone, or downgrade your ROM to whatever version the baseband is. Personally, if you want to stick with Froyo, you should upgrade to EB01. It doesn't really fix much, but at least it has a modem available.
EDIT: Your issue is the DI01 baseband and DL30 build. I'd say update to EB01. If you want to stick with stock, go with DL09 and update to the EA28 OTA.
imnuts said:
To use Odin, you need to get into download mode. Turn the phone off, pull the battery, hold the volume down button, plug in the USB cable while continuing to hold the volume down button. Phone should now be in download mode and Odin should pick up the device (assuming you had the drivers installed as well already). When flashing anything via Odin, be sure to use the PDA button.
The issue sounds like you just need a new modem flashed to the phone, or downgrade your ROM to whatever version the baseband is. Personally, if you want to stick with Froyo, you should upgrade to EB01. It doesn't really fix much, but at least it has a modem available.
EDIT: Your issue is the DI01 baseband and DL30 build. I'd say update to EB01. If you want to stick with stock, go with DL09 and update to the EA28 OTA.
Click to expand...
Click to collapse
OK, I want EB01. I cant get odin to work. It says "<OSM> All threads completed. (succeed 0 / failed 0)" when I hit start. I have the EB01SC254.tar Im trying to use
mikeyinid said:
OK, I want EB01. I cant get odin to work. It says "<OSM> All threads completed. (succeed 0 / failed 0)" when I hit start. I have the EB01SC254.tar Im trying to use
Click to expand...
Click to collapse
did you ever install the samsung drivers on your computer
Seriously? you couldnt have looked that hard if you were on DL30. that isn't even a current leak. and there's a sticky thread with a how-to for everything HERE...
With such quotes as "DL30 is now outtdated as it was replaced by a newer release of froyo aka EB01."
and... "The Froyo EB01 update has it's own radio that needs to be flashed via Odin."
and HERE is a seriously HARDCORE step-by-every-tiny-step walkthrough for rooting/froyo/eb01. I didn't even search. It was in plain sight.
My god...
kmalinich said:
Seriously? you couldnt have looked that hard if you were on DL30. that isn't even a current leak. and there's a sticky thread with a how-to for everything HERE...
With such quotes as "DL30 is now outtdated as it was replaced by a newer release of froyo aka EB01."
and... "The Froyo EB01 update has it's own radio that needs to be flashed via Odin."
and HERE is a seriously HARDCORE step-by-every-tiny-step walkthrough for rooting/froyo/eb01. I didn't even search. It was in plain sight.
My god...
Click to expand...
Click to collapse
WOW. Jerks like you are why I stopped posting here. I am trying to tell you guys, I have followed all those tuts and they DO NOT WORK. If you dont want to help me dont post here, I am trying to get my phone working right and dont need your crap. You have less than 30 posts and you want to talk to me like that? I have enough knowledge about what Im doing to fix my problems on my own but this is differentl....
nitsuj17 said:
did you ever install the samsung drivers on your computer
Click to expand...
Click to collapse
Yea, I just rooted a Vibrant the other night. That was no problem compared to this...
I dont think you guys are following me. I got this phone last night already rooted and running DL30. I DID NOT FLASH IT MYSELF. I cant get into cwm to do anything and odin gives me the message i posted a few posts ago. I have the drivers installed.
When your phone is plugged in and Odin is open, does the ID:COM field show anything? It should turn yellow and display the COM port your phone is connected to. Also, you are clicking the PDA button and selecting the file you want to flash, correct? Your process should follow this: http://goo.gl/TEv2T and if you want to flash a full image (ROM/Kernel/Modem) it would take the place of the modem tar file, but it would still go under the PDA button.
re what imnuts posted (I was drafting a similar post when his popped up)...
I have experienced issues with the usb port not working correctly. If the Odin ID:COM field is blank, you might have a usb problem.
Does the phone allow you to mount the sdcard using the Samsung drivers? If not, odin won't work either.
imnuts said:
When your phone is plugged in and Odin is open, does the ID:COM field show anything? It should turn yellow and display the COM port your phone is connected to. Also, you are clicking the PDA button and selecting the file you want to flash, correct? Your process should follow this: http://goo.gl/TEv2T and if you want to flash a full image (ROM/Kernel/Modem) it would take the place of the modem tar file, but it would still go under the PDA button.
Click to expand...
Click to collapse
I think it is my drivers. They worked fine the other night. I just uninstalled and tried some posted in a thread here and it still doesnt work. It says problem with gadget serial.
I believe that all the SGS phones require different drivers to work properly. Download the most recent drivers from Samsung from the I500 download page
EDIT: Download
imnuts said:
I believe that all the SGS phones require different drivers to work properly. Download the most recent drivers from Samsung from the I500 download page
EDIT: Download
Click to expand...
Click to collapse
Those ones worked. But, I still get errors in odin. I tried to flash the EB01 modem first...
mikeyinid said:
Those ones worked. But, I still get errors in odin. I tried to flash the EB01 modem first...
Click to expand...
Click to collapse
Are you following this when trying flash? http://goo.gl/TEv2T What error is it giving you, and at what step in the process? Also, the screens should look similar as far as how the boxes look while flashing.
imnuts said:
Are you following this when trying flash? http://goo.gl/TEv2T What error is it giving you, and at what step in the process? Also, the screens should look similar as far as how the boxes look while flashing.
Click to expand...
Click to collapse
Its working now. I rebooted my computer and all is well. I really appreciate your help with this. We need more guys like you here at XDA. I have almost 800 posts at droid forums and dont come over here much because your expected to just know everything here. Thanks again.
mikeyinid said:
Its working now. I rebooted my computer and all is well. I really appreciate your help with this. We need more guys like you here at XDA. I have almost 800 posts at droid forums and dont come over here much because your expected to just know everything here. Thanks again.
Click to expand...
Click to collapse
I'll second that. I was skimming through this thread to see if anybody actually helped you with your issue rather than just saying "google it, n00b" and other such bs like that.
People are right, there *is* a lot of information to be found in these forums, but some people have lives and don't follow every single post in every single thread. I miss my days in iAudiophile.net where when a member had a legitimate question, the least we could do was to post a link to another thread for them to follow.
...So which EB01 rom did you upgrade to?