Related
I see the update is failing for a lot of people on the Samsung Captivate. Mine was reflashed using Odin3, and the update failed like so many others. I reflashed using Odin3 again, tried the update, and the same exact thing happened. The update fails at 50%.
The first time around, I was rooted and lagfixed, I tried it that way, then unrooted and tried again.
The second time around, I made absolutely no changes to the phone whatsoever, except signing in to my google account, and upping the screen timeout to 30 mins.
Doubt that this information is helpful to anybody, but was hoping maybe these symptoms would point to a trend as to why so many people's Captivates can't update.
Also, how many of you that failed used an Odin3 reflash any time before it failed?
I just flashed back to stock using the Odin One Click program and my updated failed at 50%. I tried 4 different time with the same result. I even reflashed a second time, did a Master Clear, and a Factory Reset. Stil no joy.
This morning as soon as I saw the news of the release I immediately hit the software update in the settings menu. Downloaded and just before I went to install I decided maybe it would be smart to do a rom backup with rom manager. Did that, and went ahead and then attempted to install it. It got to 100% and then said update failed, rebooted, said the same thing, update wasn't successful. However, if you checked about phone, it said it was jh7, but none of the jh7 stuff was there. The phone was rooted, sideload enabled, clockwork installed, and bloat removed, that's it. Never flashed a rom or lag fix or anything like that.
At this point I decided to try using the odin one click to stock jf6. Installed it, and tried to update again. Now, I'm getting what most people are getting, update fails very quickly at 50%, the phone reboots with no changes.
So I decided to use my clockwork backup, and restore my phone back to what it was before all this started this morning. Of course, since I remembered to do the backup AFTER downloading and postponing the update, it's sitting there waiting to go. Decided to try it and see if it acted the same as this morning, and now it's doing what it did right after the jf6 one click, gets to 50% and then fails with no effect.
How complete a wipe/restore of the phone is using rom manager? Because the update behavior on mine is different now after messing with odin than it was before, even after restoring it with rom manager.
Rooted with Sideloading on JH2. Not much else done to my phone. It has always worked well.
I didn't even get a percentage when trying to install. Just reboots and says "Update Failed".
Same issue here. Flashed back to JF6 using Odin one click. Update fails at 50%.
Only thing i can think of its that, that particular fw in odin is not the original fw flashed on the phone when bought and it does some sort of checksum or some kind of check.
50%, puke, and now when I click on update it tells me no firmware which I think is funny.
has anyone tried the firmware from
http://forum.xda-developers.com/showthread.php?t=777291
?
I don't have a PC at work (or even a x86 Mac) to play with.
Mine did the samething. I've used the the one click reinstaller a few times after trying out different roms. Maybe the one click installer changes something and it's blocking the update from totally completing. I hate to reinstall everything again but maybe theres a better way to do a total factory restore so we can get the update.
I'd guess that if it's doing a difference update (just applying the new stuff, not a full ROM) it needs a checksum match to be sure it doesn't bork the phone. Failing that (i.e. anything different from a pure stock phone) it will abort at some point.
There is a pure JF6 stock rom linked somewhere here on the forum--I'll see if I can find it, but it was never stickied or anything. Some guy just uploaded it because the one-click wasn't "pure" so to speak.
I guess this is their way of saying "you don't like our firmwares in the first place, you don't get this one either!"
Mine did all the same as you guys , failed at 50%. So I just got a new phone from att , told them it keep failing update. Did update right in store on new phone and boom installed no problem. On top of that gps is dead on, on new phone with update. Didn't get to try with out update. Already made sure I can get into download mode, no problems there. Note just scared to flash any roms since gps is perfect lol.
Sent from my SAMSUNG-SGH-I897 using XDA App
Omg and no xda force close lol . Also rf cal date is 7/10/2010 , old phone rf cal date was 8/07/10
Gps couldn't lock to nothing.
Sent from my SAMSUNG-SGH-I897 using XDA App
I tried using the Samsung Kies program and it says "this device's version cannot be updated". I'm wondering if that one click installer is not what it should be. Maybe if we flash to a different Captivate firmware the Kies program will update it.
I agree, I just like the way the one click installer worked. I know there's other roms/kernels posted, and I guess I'll have to do some legwork here. Here's hoping.
Just reflashed back to stock for the third time using Odin3 One Click and now when I check for updates it It says No Updates Available. Prior to this, it would dwnload the updated and reboot the phone and fail at 50% while installing. Frustrating!
I never use the 1click odin, I always put the .pit and the JF6 file into the 'normal' odin and use that -- haven't seen if anyone has tried that yet anywhere? Maybe that'll work.
BTW I still have no update available even after calendar trick :/
Hey guys, I did root my captivate. My question is do I need to un-root the device to apply the gps update or it does not matter.
Just downloaded JF6
how would I flash this back to my phone?
sorry if thats a stupid question but I cant find an answere seraching
I downloaded JF6 from Samfirmware.com. I'm going to back up my current ROM, then do an Odin w/Repartition and use the JF6 from Samfirware.com.
We'll see if that works. . . .
cellgeek said:
I downloaded JF6 from Samfirmware.com. I'm going to back up my current ROM, then do an Odin w/Repartition and use the JF6 from Samfirware.com.
We'll see if that works. . . .
Click to expand...
Click to collapse
Let me know how that goes. (Have family up in FloMo, very great place btw).
cellgeek said:
I downloaded JF6 from Samfirmware.com. I'm going to back up my current ROM, then do an Odin w/Repartition and use the JF6 from Samfirware.com.
We'll see if that works. . . .
Click to expand...
Click to collapse
Tried this a little while ago. I went to run the update and now it's saying that no updates are available.
I spent about an hour on the chat window with ATT support and they can't seem to find a way to reset it to push again. The guy on the other end was knowledgeable as far as I could tell.
hell - he even mentioned froyo. He said they have ALOT of information on it for the captivate but no release date yet.
Alright. I have a Captivate on AT&T. It's bricked. It was one click rooted and had Perception 9.5 installed. I did the clockwork mod automatically when I rooted. I didn't use Odin. I dragged the Perception zip onto the SD. Restore mode via 3 button, install. I ran it first time no prob. I kept it for about 7 days, and I decided I wanted to try 10.1, and then if that didn't work, ROMkitchen custom.
So, I needed to go back to stock, right? I saw the Odin3 version, but on Designgear's thread, the Odin3 link was broken. So, I dl'ed the JH7_OTA.zip file, dragged to my SD, 3 button restore mode, install. WRONG! I now have a perma-AT&T screen. I don't wanna mess anything up, as I know just enough to get in trouble.
Please excuse me, as I'm sure it's been answered somewhere. I'm new from iPhone, and I know forum manners. I'm on my way out to my job, where I'll remain for the next 5 days. I only have access to an XP machine.
Please help if you can, and thanks in advance.
Find a link for a reupload of the Odin One Click, its in the thread. And then put your phone into download mode then flash.
ShredNasty said:
So, I needed to go back to stock, right? I saw the Odin3 version, but on Designgear's thread, the Odin3 link was broken. So, I dl'ed the JH7_OTA.zip file, dragged to my SD, 3 button restore mode, install. WRONG! I now have a perma-AT&T screen. I don't wanna mess anything up, as I know just enough to get in trouble.
Click to expand...
Click to collapse
No you really didn't need to go back to stock, but that's water under the bridge now. I don't know which firmware you need for your particular phone. For a batch 1009 and earlier this should be fine. For others you may need this. Personally, I'd stay away from the one-click which disables button combos on all newer builds.
K, well I feel dumb. I dl'ed Odin3, discovered "restore mode" and "download mode" aren't the same thing, put my phone in dl mode, clicked start on Odin, and was finished. Super simple back to stock.
Thaks for the help though guys. I appreciate it....
opcow said:
No you really didn't need to go back to stock, but that's water under the bridge now. I don't know which firmware you need for your particular phone. For a batch 1009 and earlier this should be fine. For others you may need this. Personally, I'd stay away from the one-click which disables button combos on all newer builds.
Click to expand...
Click to collapse
So, going back to stock isn't needed when changing ROMs? Under what circumstance do I need to flash stock?
ShredNasty said:
So, going back to stock isn't needed when changing ROMs? Under what circumstance do I need to flash stock?
Click to expand...
Click to collapse
If you manage to mess things up to the point you can't flash a custom ROM through recovery/CWM. Or if you need to exchange/return the phone for some reason.
ShredNasty said:
So, going back to stock isn't needed when changing ROMs? Under what circumstance do I need to flash stock?
Click to expand...
Click to collapse
In my opinion, only if nothing else works. I went a couple of months flashing mine dozens of times without using odin. I only flashed to stock prior to sending my phone back to Samsung to see if I could get the GPS fixed/improved.
Right on man. I appreciate it. I'm learning fast. Next time I flash, I'll just flash right over P10.1....
From what I've read since joining this community is that people tend to have mixed results/opinions about flashing to stock before changing ROMS. Personally, I always do... Each Captivate out there seems to have different quirks that do odd things from time to time, and are sometimes completely random. If you have no problem simply flashing a new ROM over what your using currently... by all means. If you have problems or Force Close issues.. try going back to stock first... All depends on what you are comfortable with..
Hey all. Just joined the forums a few minutes ago and I have a burning question on why it is necessary to flash back to stock with odin before you try different roms. Why can you not just boot into clockwork, factory wipe, wipe cache, wipe d cache and then simply load the new rom from sd? The reason I ask is because I have been bouncing between cognition and paragon for about 2 weeks now NOT using the method of flashing back to stock 2.1 without a single problem. I'm sure there is a good reason flashing back to 2.1 before trying new roms, I would just like to know why. I was able to preform a stock wipe using odin3 one time last week (just did it to make sure the phone would do it) it just seems like a really long process, but I'll start doing it that way to avoid a brick.
Thanks
to be safe, and some roms mod files that others dont, some roms depend on apps and files in the stock rom that might be different or not there at all in other roms.
long process? extra 5 minutes when you get used to it. if you are ATT use ODIN ONE CLICK to restore stock 2.1 (hint: it takes one click)
For the most part, you don't really need to flash back to stock. It used to be a bigger deal to flash back to stock because some of the Roms would intervene with each other and mess things up. It is still recommened for a clean flash, but I rarely do it and my flashes work great.
EDIT: @Trusselo: damn it! Second time someone beat me to the answer tonight!
HAHA
and forget ODIN ONE CLICK !!
i keep forgetting about this
http://forum.xda-developers.com/showthread.php?t=944418
ALL IN ONE CAPTIVATE TOOLBOX
I have been trying roms weekly since November and have only needed to flash to stock twice, after failed flashes caused by my lack of patience. YMMV of course
jayjr1105 said:
Hey all. Just joined the forums a few minutes ago and I have a burning question on why it is necessary to flash back to stock with odin before you try different roms. Why can you not just boot into clockwork, factory wipe, wipe cache, wipe d cache and then simply load the new rom from sd?
Click to expand...
Click to collapse
It's not necessary and not even a good idea. Also, why wipe cache and d-cache when the install script does that?
Trusselo said:
to be safe, and some roms mod files that others dont, some roms depend on apps and files in the stock rom that might be different or not there at all in other roms.
Click to expand...
Click to collapse
ROMs don't mod or use any files which are on the phone prior to installing them. All the files on your phone after the install were in the CWM flashable zip file. Any ROM cook would be stupid to do otherwise. The exception would be no-wipe ROMs, but you would never flash to stock before using one of those.
Ive also wondered this as well and talking to guys like opcow, and a couple other Devs such as MikeyMike and a lot of guys at the Andromeda IRC they all agree that you should be perfectly fine now as long as you wipe everything before you flash.
I may try with Andromeda when I get home because I have my PC and Jig there just in case but still may try now. But also tlaking to a lot of users that they dont even do it anymore now because of the install scripts and as Opcow said if you think logically its technically safer.
Trusselo said:
long process? extra 5 minutes when you get used to it. if you are ATT use ODIN ONE CLICK to restore stock 2.1 (hint: it takes one click)
Click to expand...
Click to collapse
Actually thats not true at all.
If your a build 1009 and under you can use the one click. Although the build 1008 sometimes have problems.
But for the Build 1010's and up (like me) you have to use Odin3 and take a good 30-40 minutes just to get to JH7 because half of the time I lose my 3 buttons then have to push the 3 button fix over via ADB. I have gotten use it and its a pain in the ass.
And the time I listened to someone that says ALL ATT people can use the one click it completely ****ed my phone and if I didnt have a jig my phone would have been completely screwed up.
Im not trying to be rude im just saying I saw a post very similar to that a couple weeks ago and it came very close to completely bricking my phone and reading posts here now saying they have the same problem and if they dont have a jig they just got a 200 dollar paper weight.
Sorry for getting off topic back to topic today Im going to flash Andromeda over Darkyy 9.3 and wipe data cache and d cache in CWM and see how it goes although everyone and even the devs and a lot of users now a days say it should work perfectly.
Dlev7 said:
Actually thats not true at all.
If your a build 1009 and under you can use the one click. Although the build 1008 sometimes have problems.
But for the Build 1010's and up (like me) you have to use Odin3 and take a good 30-40 minutes just to get to JH7 because half of the time I lose my 3 buttons then have to push the 3 button fix over via ADB. I have gotten use it and its a pain in the ass.
And the time I listened to someone that says ALL ATT people can use the one click it completely ****ed my phone and if I didnt have a jig my phone would have been completely screwed up.
Im not trying to be rude im just saying I saw a post very similar to that a couple weeks ago and it came very close to completely bricking my phone and reading posts here now saying they have the same problem and if they dont have a jig they just got a 200 dollar paper weight.
Sorry for getting off topic back to topic today Im going to flash Andromeda over Darkyy 9.3 and wipe data cache and d cache in CWM and see how it goes although everyone and even the devs and a lot of users now a days say it should work perfectly.
Click to expand...
Click to collapse
+1 Guys if you don't know exactly what to do/suggest please don't say it. I'm not trying to start a war, but a wrong suggestion can easily soft or hard brick someones phone. This is a forum, so no one can stop you from saying things, but think about if it happened to you? You would be pissed!
Anyways back on topic, what model phone do you have, because having a 1009 model phone makes flashing and going back to stock (usually) so much easier. But then again, I rarely use odin because all the roms are compatible for the most part.
Sent from my SGH-I897 using XDA App
I've never used ODIN because I haven't wanted to try to run it from GNU/Linux in a virtual box.
I just wipe and flash from clockwork like the op. Been flashing roms for a couple months now, never had a single problem. (except when I noobed it up by trying to flash back to a nandroid backup via Rom Manager. Even then, didn't need Odin to sort it out).
If I ever run into a problem, then I'll try Odin, but I'm waiting to cross that bridge till I come to it.
To prevent exceptions or troubles from the version you already have... so everybody comes from the same rom, understand?
I flash to jf6 because that's what I have been conditioned to do for a while. However, the few times I was impatient and didn't....no problems either.
From all the reading I've done here, the only reason to do it is for the placebo effect.
There was once a time when all the new roms were built on the unofficial froyo and it only had 3e recovery. The quickest way to get around that was to flash stock. Also the lag fixes were tricky and easily fixed by flashing stock. Now recovery is in the kernel. As long as you insure the kernal lag fix in rom A understands the kernal lag fix in rom B flash away. Nandroid backups are kind of useless they don't backup the kernal or the modem. Save odin for when things go really wrong(;~ )
Sent from my i897 using XDA App
I have done it both ways, and there its no difference going back to stock and or flashing over other roms. I flash often, have not got stick in boot loop in months
I like to go back to stock since I KNOW that everything has been defaulted back to normal. Just a security blanket step for me.
I flashed andromeda over darkyy 9.3 just wiping data cache and d cache. Nothing wrong. Everything worked perfect so I got to believe that if you just wipe everything it should work perfectly.
Just for safety I got a jig and odin but for now I'm saving a good 45 minutes to not flash back to stock
Sent from my SGH-I897 using XDA App
HI!
Just recently signed up so I can't seem to post this question in the FASTY III forum....I kind of understand why xda has this policy about new members not being able to post int he developmental forums...but still...
I recently moved from FASTY II to III...ran into a bunch of issues but I managed to resolve most of them by going through the forums. What I am having trouble with is my inability to get to the Recovery menu. I have tried to go there thru the shutdown menu, by doing the button holding trick, and even from ROM Manager... none of those seem to work for me. Very frustrating... All those mentioned attempts only bring up an ATT screen which wont go away until I reboot the phone into a normal start....
So why am I unable to enter Recovery mode?
Any help would be much appreciated. Thank you!
nycmon said:
HI!
Just recently signed up so I can't seem to post this question in the FASTY III forum....I kind of understand why xda has this policy about new members not being able to post int he developmental forums...but still...
I recently moved from FASTY II to III...ran into a bunch of issues but I managed to resolve most of them by going through the forums. What I am having trouble with is my inability to get to the Recovery menu. I have tried to go there thru the shutdown menu, by doing the button holding trick, and even from ROM Manager... none of those seem to work for me. Very frustrating... All those mentioned attempts only bring up an ATT screen which wont go away until I reboot the phone into a normal start....
So why am I unable to enter Recovery mode?
Any help would be much appreciated. Thank you!
Click to expand...
Click to collapse
in terminal emulator type su and then reboot recovery maybe it work
or may be you just flashed unsupported recovery
nycmon said:
HI!
Just recently signed up so I can't seem to post this question in the FASTY III forum....I kind of understand why xda has this policy about new members not being able to post int he developmental forums...but still...
I recently moved from FASTY II to III...ran into a bunch of issues but I managed to resolve most of them by going through the forums. What I am having trouble with is my inability to get to the Recovery menu. I have tried to go there thru the shutdown menu, by doing the button holding trick, and even from ROM Manager... none of those seem to work for me. Very frustrating... All those mentioned attempts only bring up an ATT screen which wont go away until I reboot the phone into a normal start....
So why am I unable to enter Recovery mode?
Any help would be much appreciated. Thank you!
Click to expand...
Click to collapse
I have been having the same problem recently, but not just with this rom. I have flashed many roms to my device, but it appears that almost everytime i try to flash something now, the same exact thing happens as the OP. any information on what is wrong or how to fix this would be greatly appreciated.
When you boot up...do you guys get a scrambled screen that looks like white noise?
that's caused by froyo bootloaders on a gingerbread ROM.
Not all That familiar with fasty though...dunno of the jump from 2 to 3 was froyo to ginger, just a guess.
studacris said:
When you boot up...do you guys get a scrambled screen that looks like white noise?
that's caused by froyo bootloaders on a gingerbread ROM.
Not all That familiar with fasty though...dunno of the jump from 2 to 3 was froyo to ginger, just a guess.
Click to expand...
Click to collapse
Sometimes this happens, but i am usually still able to use the rom after i wait for awhile. Recently it just gets stuck at the ATT logo screen and does nothing else.
HERE is a package containing JUST the ginger boots.
MAKE SURE YOU HAVE A GOOD PHONE/PC CONNECTION, FLASHING BOOTLOADERS IS THE ONLY WAY TO TRULY HARD BRICK
studacris said:
HERE is a package containing JUST the ginger boots.
MAKE SURE YOU HAVE A GOOD PHONE/PC CONNECTION, FLASHING BOOTLOADERS IS THE ONLY WAY TO TRULY HARD BRICK
Click to expand...
Click to collapse
i just tried it with a solid connection and it almost instantly said failed in the red box. now i cant turn it on or get to download mode so im pretty sure it is hard bricked. is there any way you can help me with this?
EDIT: False alarm, i can still get to download mode so i can ODIN back to stock, but i do not know if i should risk it again
Whew that was close.
You can flash to stock using a bootloader less package, that way if it fails it can't hard brick.
Then if that works, find an entire stock gingerbread package with bootloaders included, and flash that instead of just the bootloader one click. this again, will involve risk, but full Odin package seem to work better on some phones than one clicks do.
I tried to flash the bootloader again and it succeeded. i then proceeded to try and flash Fasty KK4 v1.1 and once again i was stuck at the ATT logo. For some reason with every rom i flash, when the logo pops up, it starts dim and then get bright. After it gets bright, it stays that way and it is a real pain not being able to use custom roms anymore.
If you have the GB bls just make sure you follow LL's instructions in the OP for Fasty. I had the same issue, but it was me mistake for not following the istructions properly
studacris said:
When you boot up...do you guys get a scrambled screen that looks like white noise?
that's caused by froyo bootloaders on a gingerbread ROM.
Not all That familiar with fasty though...dunno of the jump from 2 to 3 was froyo to ginger, just a guess.
Click to expand...
Click to collapse
i DO get a very colorful white noise screen whenever it boots up ...the screen goes away once it fully reboots....I wondered about it but just assumed it was a quirk of the FASTY III package...
Is Rom Manager a froyo based app?
No, ROM manager is poop. Not implemented on galaxy devices properly, and won't work past eclair, and even them it was severely limited to just downloading an update.zip to your sdcard...which you could put there manually with out having to root...
FORGET ROM MANAGER EXISTS
studacris said:
No, ROM manager is poop. Not implemented on galaxy devices properly, and won't work past eclair, and even them it was severely limited to just downloading an update.zip to your sdcard...which you could put there manually with out having to root...
FORGET ROM MANAGER EXISTS
Click to expand...
Click to collapse
Really? Rom Manager helped me a lot until this Fasty III installation....even in my previous rom Fasty II it worked fine and did great for backing up and restoring backups....saved my asss a few times with those restores lol....But if this program doesn't work for fasty III what comparable program can I use?
Also I still can't intorecovery mode...nothing works...I even tried using ADB and Droid Explorer....nothing seems to get it into recovery mode...
Am I going to have to flash back to stock ROM and try reinstalling fasty iii again? This seems all so tedious lol...
OR is there a way for me to flash back to Fasty II without having to go back to stock rom? or without having to access the recovery screen?
Thank you^
All that backing up and restoring you did with ROM manager can be done in cwm recovery and that's what you should use from now on. No app needed at all.
Follow the instructions I've already provided in this thread. You'll either need Odin to flash the gingerbread bootloaders,
or to go back to a froyo firmware, first flash a froyo kernel with Odin and THEN the froyo ROM. stock isn't needed.
Recovery in a gingerbread kernel is completely inaccessible with froyo bootloaders.
studacris said:
All that backing up and restoring you did with ROM manager can be done in cwm recovery and that's what you should use from now on. No app needed at all.
Follow the instructions I've already provided in this thread. You'll either need Odin to flash the gingerbread bootloaders,
or to go back to a froyo firmware, first flash a froyo kernel with Odin and THEN the froyo ROM. stock isn't needed.
Recovery in a gingerbread kernel is completely inaccessible with froyo bootloaders.
Click to expand...
Click to collapse
Thank you for the info!
Looks like fasty III is a GB based mod after all...I guess I should read up more on the rom before installing lol....I did not expect the dev to go from froyo to gb -_-
I was thinking of using your previous post for the one click gb bootloaders only....but it seems a little iffy and I can't afford to hardware brick the phone lol...
Makes me wonder tho...is it really THAT risky to flash bootloaders? It would make things simpler if i could just flash the gb bootloaders and go from there....
the whole flash should take less than a minute, where the actual writing takes only a few seconds...but if you were to lose communication in that awful window then it would be bad day.
But that is a small window, and if you have never had connection issues you should be ok if Odin tends to be iffy, you van try heimdall I've heard that works better for some.
Still haven't tried flashing the bootloaders because i'm scared of the possibility of hard bricking my phone... If worst case scenario was to happen and it gets hard bricked....are there any options to restore that phone? or is it just paper weight after?
Also until I flash those bootloaders there is no way to back up my phone or anything?
Thanks for all ur help btw!
another issue i am having is that the phone seems pretty laggy after installing this rom...even with tegra overclock premium and tweaking it up to 1252mhz 1275mv 1100mv setting...it still seems laggy when opening sms etc....is this just the results of a bad rom install? also battery life seems crappy....even after doing the battery recalibration...of course i couldn't wipe the battery stats since i cant get into recovery...
Hard bricks are recoverable by a hardware modification known as unbrickable mod, search for user Adam outler, or go to mobiletechvideos.com they both offer this service if you're not a soldering expert.
Battery recalibration does NOTHING the stats are reset everytime you charge to 100, and besides that they don't calculate your current battery level, just what's been using it, its what's used in settings> about phone> battery use. It has nothing to do with extending battery life.
oh lol...i have been reading all these threads where people are talking about how much their battery life improved after they did the recalibration and stat wipe ....well anyways I am going to attempt the bootloader flashing...I hope everything goes well! after that I want to try reflashing the fasty III ROM...
Do you have any recommendations as far as a good ROM for teh captivate? One that doesn't lag and has good gps & battery life? I would appreciate any help you can give.
Thanks!
I attempted to root my SGS (which had stock Gingerbread Value 2.3.6) using a guide on the Snappyguides blogspot page (the system won't let me, as a newbie, post the URL).
Odin did its thing and then the Samsung Galaxy screen came up (just the white lettering, not the multicoloured animated S) and then... nothing. It just stayed like that for about five seconds, then the white Samsung Galaxy S came up again, then the blank screen ad infinitum.
I can access the download screen and I can access the recovery screen (which does seem to indicate that ClockworkMod v2.5.1.0 has been installed). The trouble is that none of the options seem to do anything.
I have tried searching the forum for similar problems and have read the sticky. The only answers I seem to have been able to find so far suggest flashing a new Rom.
Before I go this far, is flashing a new Rom really necessary in this instance? I have never done this procedure before, so I'm wary of messing things up even further. But obviously if the phone is past the point of no return as far as the stock Rom is concerned, then that'll be what I have to do.
I'd appreciate some advice before doing anything else to my phone though.
I now seem to be able to get the recovery menu options to respond, so maybe all is not lost. Have set it to root and it's currently converting to EXT4 and is about halfway through that.
I'm hoping once that's done, it'll be bootable.
If not, what do I need to do to make the SGS boot again? Is there any way of getting back to stock or can I only flash a stock rom back on?
Nope, still not booting. It just keeps going to the Samsung I9000 white lettering, stays there for five seconds, goes blank for five seconds, then the white lettering goes back and on, off like that forever.
So... anyone willing to help?
...
have a look in this thread http://forum.xda-developers.com/showthread.php?t=1225879
Lexrsk said:
have a look in this thread http://forum.xda-developers.com/showthread.php?t=1225879
Click to expand...
Click to collapse
Thanks for responding.
Sorry for being a n00b but I can't find anything in there that helps me. All I see is a lot of jargon about various roms, kernels and something called Voodoo.
I had a working phone with Gingerbread 2.3.6 Value. I added Clockworkmod via Odin. Now I can't get the phone to boot beyond the splash screen. It doesn't even get as far as the animated S, all I get is the splash screen going on and off every few seconds.
All I want is to get my phone working again, I really couldn't care less about custom roms etc.
If anyone can help this poor n00b, I'd be very grateful!
Incidentally, I've downloaded what I understand to be the factory rom for JW4 from sammobile.com - this is a 171MB zip file with just two files inside - a tar file called JW4_JW5_JW4 and a dll file called SS_DL.dll. I'm not really sure what to do with these to restore my phone via Odin. This is the kind of thing I need help with - the threads I've read so far don't make much sense to a poor confused n00b I'm afraid.
evilcartman2 said:
Thanks for responding.
Sorry for being a n00b but I can't find anything in there that helps me. All I see is a lot of jargon about various roms, kernels and something called Voodoo.
I had a working phone with Gingerbread 2.3.6 Value. I added Clockworkmod via Odin. Now I can't get the phone to boot beyond the splash screen. It doesn't even get as far as the animated S, all I get is the splash screen going on and off every few seconds.
All I want is to get my phone working again, I really couldn't care less about custom roms etc.
If anyone can help this poor n00b, I'd be very grateful!
Incidentally, I've downloaded what I understand to be the factory rom for JW4 from sammobile.com - this is a 171MB zip file with just two files inside - a tar file called JW4_JW5_JW4 and a dll file called SS_DL.dll. I'm not really sure what to do with these to restore my phone via Odin. This is the kind of thing I need help with - the threads I've read so far don't make much sense to a poor confused n00b I'm afraid.
Click to expand...
Click to collapse
I'll help u, I went through this when I was a noob and because I didn't know about xda I had to just figure a way out, I am sorry to say but u have soft bricked your phone, luckily its not hard to unbrick, here's a link to a post i made the other day with proper guides that I use often and they are noob friendly, the files u need to download are there but it 2.3.3 and it JW4 but it will be a start to get ur phone back to life,
If you like my posts hit thanks
Here the link http://forum.xda-developers.com/showthread.php?p=25572245
If you like my posts hit thanks
OK, thanks for that. I'm supposed to be asleep right now, so I'll come back to this later but thanks for helping.
But just to clarify for now - this will restore the phone to a working version of 2.3.3 and from there I can get back to the latest stock rom (2.3.6) via Kies, yes? I need to get into Kies anyway to restore my contacts from backups (as I haven't yet seen a way of restoring the backups except via Kies).
Thanks once again.
evilcartman2 said:
OK, thanks for that. I'm supposed to be asleep right now, so I'll come back to this later but thanks for helping.
But just to clarify for now - this will restore the phone to a working version of 2.3.3 and from there I can get back to the latest stock rom (2.3.6) via Kies, yes? I need to get into Kies anyway to restore my contacts from backups (as I haven't yet seen a way of restoring the backups except via Kies).
Thanks once again.
Click to expand...
Click to collapse
Yip I guess that is right. I have never tried it but yes it should work
If you like my posts hit thanks
Well, I did get it working again in the end by using a factory rom. Thanks for your help anyway, W1nst0n.
I do intend to attempt to root it again but this time I intend to do it properly.
Any suggestions on what may have caused the boot problem I had? Perhaps using a version of ClockworkMod that was incompatible with 2.3.6 Value?
evilcartman2 said:
Well, I did get it working again in the end by using a factory rom. Thanks for your help anyway, W1nst0n.
I do intend to attempt to root it again but this time I intend to do it properly.
Any suggestions on what may have caused the boot problem I had? Perhaps using a version of ClockworkMod that was incompatible with 2.3.6 Value?
Click to expand...
Click to collapse
Yeah that or the wrong root file for ur baseband
If you like my posts hit thanks
evilcartman2 said:
Well, I did get it working again in the end by using a factory rom. Thanks for your help anyway, W1nst0n.
I do intend to attempt to root it again but this time I intend to do it properly.
Any suggestions on what may have caused the boot problem I had? Perhaps using a version of ClockworkMod that was incompatible with 2.3.6 Value?
Click to expand...
Click to collapse
Check in about phone for the kernel version. for example mine is 2.6.35.7-I9000TDVJV6-CL530973
The important part is the bold text.
search the link that i posted earlier for a odin version and flash as PDA
Good luck
Evilcartman, when u wanna get me help find me on the I9000 q&a-ask me anything I got the answer thread, it where I spend most of my time.
If you like my posts hit thanks