Hi!
Im having trouble getting into CWM. I have been running MIUI on my Galaxy S i9000 for over a month now without any problems with CWM. Im running MIUI RC8vC right now and decided to update it to the latest release MGv2, but here comes the problem. I can't get into the Clockwork Mod Recovery mode.
What i have been trying is the standard 3-button-combination, where i end up on the splash screen for the Galaxy S i9000 and than nothing more happens (left it on for 10 minutes just to be sure). So i then tried rebooting into CWM using the ROM Manager from Market, ending up with the same result.
My question is, what is the most simple way of fixing this annoying problem?
Thanks!
how long are you holding the 3 button combo for ? you only need to do it until the GT-I9000 screen comes on, then let go.
anyway if you cant get it working its probably kernel related, did you flash they CM7 initial kernel before you came to MIUI,
do this again in ODIN and start the process again
Yepp that's what im doing, I have been using CWM quite a lot so im 100% sure im doing the combo correct, it seems like the CWM just wont boot up.
Yes i did, and after that i have been upgrading MIUI like 10 times for every new version without any problems at all, up until now with this release.
So the solution is to Flash the initial kernel again, then use the 3 button combo and install the latest release and all will be fine again hopefully?
RobertRoos_ said:
Yepp that's what im doing, I have been using CWM quite a lot so im 100% sure im doing the combo correct, it seems like the CWM just wont boot up.
Yes i did, and after that i have been upgrading MIUI like 10 times for every new version without any problems at all, up until now with this release.
So the solution is to Flash the initial kernel again, then use the 3 button combo and install the latest release and all will be fine again hopefully?
Click to expand...
Click to collapse
yes, that should work
weird problem and i have never heard of it before lol..
Thanks for the quick answer!
I did what you said and it worked fine, im now running the latest release of MIUI for Galaxy S.
But now i can't get into CWM again! This is really strange, and annoying, if i have to go back to the initial kernel all the time for upgrading MIUI, i do wonder what could be causing this problem. If it was the kernel that comes with the later releases av MIUI i suppose others would have similar problems, but i can't find anyone else having these kinds of problems.
Seems like im beeing followed by bad luck today.
so download mode IS working ??? Hmmm.... not a 3 button combo issue then..
How long have you been on MIUI, did you come from a gingerbread ROM ?
can i just ask how are you doing the 3 button combo..... (i feel stupid asking this, but this problem is so strange)
Yes, works like a charm- so as I said im on the MGv2 right now but with the same problem as before lol.
I've been on MIUI for about a month now, perhaps a little longer. No i came from Darkys v9.5, than did the standard update procedure going to a stock froyo rom and so on as described in the main MIUI thread.
Well im doing it the same way both when on the kernel for CM7 where i can get in, and when on the kernel for MGv2. Menu+Volume Up+POWER, Releasing Power directly when the "Galaxy S i9000 Samsung" splash screen turns up. So im 100% im doing the combination right. I can't get into CWM using the ROM Manager either that donät require the 3-button combination, so there must be something else.
Thanks for trying to help me with this!
no need for thanks we havent got it sorted yet lol
make a post in the MIUI thread in development, there is a lot of cleverer people in there and im hoping that they can shed some light on this bizzare situation
I wanted to do that in the first place, however i must reach 10 posts or so before i can post in there. You could not post my question in there for me you think? So i don't hace to just spam this forum with another 5 posts.
thats very respectful of you not wanting to spam the thread, but yes i will post your question now for you,
you can keep your eye on the post and watch the results, i will also post the results here when someone kindly answers it
EDIT: have you done a factory reset ? when in recovery did you format /system /cache / dalvik cache and then install MIUI
hey mate had a reply, dont know if you have been checking but here is what was said
I had a similar problem when first installing CM7, I believe it is a problem with having come from the original JVK. The solution was to flash an older Froyo version (JS3 in my case) and repartitioning with 512-pit, then installing MIUI again from scratch. Hope that helps.
Click to expand...
Click to collapse
hope this helps
Ill reply when more solutions come up
azzledazzle said:
thats very respectful of you not wanting to spam the thread, but yes i will post your question now for you,
you can keep your eye on the post and watch the results, i will also post the results here when someone kindly answers it
EDIT: have you done a factory reset ? when in recovery did you format /system /cache / dalvik cache and then install MIUI
Click to expand...
Click to collapse
azzledazzle said:
hey mate had a reply, dont know if you have been checking but here is what was said
hope this helps
Ill reply when more solutions come up
Click to expand...
Click to collapse
Thanks again azzledazzle!
Yes a did a complete wipe since I as well thought that might could solve the problem, however it did not.
Okay I will have a go at it tomorrow- I guess i need to find a ROM with a bootloader and all though when downgrading from 2.3.4?
yes, im not sure which firmware contains the bootloader or if you have to check 'update bootloader' in odin, i have never had to do this, so you will have to search.
but let me know how you get on and we can go from there.
Im off to bed now its late, if you get it fixed PM me, if not il be back to check on the thread tomo
Problem is now solved!
I was thinking that MIUI gets updates all the time, and switches between kernels quite often as well, so I decided to wait for the next update with a kernel-switch.
MGv4 was released today and had the kernel-switch I had been waiting for, so I just flashed over the initial kernel for CM7 again using ODIN. Than went into CWM and updated MIUI to MGv4.
Than with my fingers crossed i tried entering CWM again and it worked like a charm.
So I did not have to go back to FroYo and all that again, just had to wait for the next update.
Thanks for your help!
Related
1st A big Hiiii from India.
I am a noob in this android scene. The most closest experience I have had to this is moding PSP's(done so many can't count) bricked and unbricked as well.
I got my SGS this week and the first day itself i started to see how i can make it better.(had seen a lot of vid in youtube). Some problems i faced initially was:
1. the 3 key hold to go into recovery mode just wont work for me so i used the easy reboot recovery script.
2. Intially i tried a couple of roots which would give me errors like it failed to run. The phone came with DDJG4 and i was able to get Superuser 2.3.1 was able to update SU database to V5 from android market.
3. Installed Ryan ZA lagfix 1.6.0 from market and now I am able to get a quadrant score of 2172. Earlier it was around 900.
What I want to do now is to have 2.2 froyo on it. I want feedback as well as help. Feedback as in is it worth it? How do I goto 2.2 custom and which one? where do i get rom and which custom one to go for. I have been seeing so much of stuff on the internet that i am a little too much confused. All help appreciated and thanks for your post.
DO NOT INSTALL FROYO! you will brick or have problems. Read all the people who installed Jpc and prev betas. Seriously. Im sick of people asking for help after installing froyo who have not done their research as to how much problems it has. Also your phone had download disabled. If you screw up there's nothing anyone can do other then tell you to get hair dryer and heat the thing up. Also don't ask me about that as im not stupid enough to install unofficial froyo
Sent from my GT-I9000 using Tapatalk
DDJG4 is gr8 .. dont try to install any Froyo build as of now.. i have tried all and have experienced a lot of issue and reverted back final to DDJG4 ... wait for the official release or mess things up as u like.....
dewimagica said:
DDJG4 is gr8 .. dont try to install any Froyo build as of now.. i have tried all and have experienced a lot of issue and reverted back final to DDJG4 ... wait for the official release or mess things up as u like.....
Click to expand...
Click to collapse
how to revert back to DDJG4... cant find ne thing...
Alright folks i am so sorry had been away! I am really sorry i did not check the posts however was really restless to see flash 10 so I ended up using odin to get into I9000ZSJP2 I used paul's rom with clockwork mod from modaco.
It was real laggy and the ryan fix also dint help much. So I downloaded the OG DDJG4 as well as I9000XXJPC. Wanted to give one last try as had seen a lot of youtube vids of it being the most stable one out there.
Frankly it worked like a charm. I used it for couple of days it had all the features working. I even rooted it the way told in xda here. by using odin and couple of files. I restarted it many times and had no issues.
Suddenly this is the problem when i switched it off to switch my sim. The phone starts goes to Galaxy S logo and stays there for like 2 mins and then it goes black.
None of the recovery mode combo and download mode combo work for me hence I had to use script.
The script also dont work now over USB. I tried removing sim and sd card. How do i get back to JG4. all help appreciated. I am sure i am not going to froyo until final build if i get this fixed.
ickyboo said:
DO NOT INSTALL FROYO! you will brick or have problems. Read all the people who installed Jpc and prev betas. Seriously. Im sick of people asking for help after installing froyo who have not done their research as to how much problems it has. Also your phone had download disabled. If you screw up there's nothing anyone can do other then tell you to get hair dryer and heat the thing up. Also don't ask me about that as im not stupid enough to install unofficial froyo
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
ok i had froyo jpc and then easily went back to eclailr build because of bugs and then went to the hk jp2 which i love. yes he can have issues but bricking the phone is hard with odin if you follow the instructions
I dont think mine is brick eh! i can still turn it on. Its more like a no boot. Brick is a no post
I tried both JP2 and JP3 and they were OK at best since they were in early beta and inspite of speed, they were unstable and very unstable. I would say they are good to play around a bit but definitely not for daily use.
If you still want to get your hands wet, you can try Doc's RomMod Froyo V2 + Superlite (I9000XXJPC) 9/9/10
But as every one is saying already, stick to the current ROM and wait for an official release from Samsung.
Just don't forget to install a lag fix.
And don't worry about bricking, it's very hard to brick your phone, so go ahead and give a try and play around to know your device better.
Enjoy the SGS!
Thx mate.. needed some emotional support on this one.. well i have to report officially I could not get my phone working and recognized by Odin. The guys at samsung service center also gave up after looking at it for 30 mins. I have to say.. they knew less than I did about the phone. I have said its less then 7 days so either they fix software of I replace the phone. Thats how it works in india and guess what I went on the 7th day I read a lot of peps here sayin if the phone does not go into recovery or download by key combo it is getting replaced. I am going to post soon what happens. Until then keeping my fingers crossed and prayers.
PS: another guy in my office has SGS and he is able to go to recovery and download so its not like an all india thing.
I got my phone back last week they replaced it with another one with JG4
Which City do you live in? I have a Bricked phone and I am thinking of getting it replaced.
dhiru1602 said:
Which City do you live in? I have a Bricked phone and I am thinking of getting it replaced.
Click to expand...
Click to collapse
I am from HYD.. Btw I found a way to fix the non three button fix from the forum itself.. i just fixed one of my friend who had the recovery mode hold not working.. ova the weekend..
HELP! I am so scared...somebody help me!
I tried to installed the Overcome kernel but didn't like it, as each time I boot up, that voice comes up.
And plus, a few of my original apps was lost (including Market). So I thought i'd install with Odin again the:
CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar
And now, when i switch on the tablet, it'll boot with the animation and sound, but then a blank screen.
I can manage to boot into ClockworkMod recovery. Can i be saved? Please somebody help me!
Thanks
geoyakult said:
HELP! I am so scared...somebody help me!
I tried to installed the Overcome kernel but didn't like it, as each time I boot up, that voice comes up.
And plus, a few of my original apps was lost (including Market). So I thought i'd install with Odin again the:
CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar
And now, when i switch on the tablet, it'll boot with the animation and sound, but then a blank screen.
I can manage to boot into ClockworkMod recovery. Can i be saved? Please somebody help me!
Thanks
Click to expand...
Click to collapse
If you can boot into CWM, then you should easily be able to get into Download mode as well. You can go back to the stock image for your Tab, or try and reflash a different rom via CWM... sounds like just a bad flash for a soft brick..
pvtjoker42 said:
If you can boot into CWM, then you should easily be able to get into Download mode as well. You can go back to the stock image for your Tab, or try and reflash a different rom via CWM... sounds like just a bad flash for a soft brick..
Click to expand...
Click to collapse
Hi there, thanks for reply back to me.
I've managed to actually get it going again, by reflashing to the Overcome kernel.
However, some apps has disappeared and also the market.
Anyways, i wish to revert the whole thing back to stock, kernel and firmware. Is there a way I can do this via Kies?
Let me know what information regarding my tab you need. I believe it is the CPW (GSM) UK version.
cheers
geoyakult said:
HELP! I am so scared...somebody help me!
I tried to installed the Overcome kernel but didn't like it, as each time I boot up, that voice comes up.
And plus, a few of my original apps was lost (including Market). So I thought i'd install with Odin again the:
CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar
And now, when i switch on the tablet, it'll boot with the animation and sound, but then a blank screen.
I can manage to boot into ClockworkMod recovery. Can i be saved? Please somebody help me!
Thanks
Click to expand...
Click to collapse
LOL. FYI, your Tab is not haunted. That voice that you refer to, is basically an indicator that the file-system on the Tab is being converted from RFS to EXT4 (what some would affectionately refer to as the lag-fix). You should have left it to continue. That's the reason we ask people to let it finish booting before doing anything else. As always, when it comes to flashing a new firmware/kernel, it's always better to read up and know what to expect.
Anyway, by the looks of it, you might have a corrupted file-system, since you keep shutting it down mid-conversion. That's the reason "the voice" keeps coming back. If you'd allowed it to complete, it should not have returned.
Secondly, flashing the Overcome Kernel alone will NOT remove the Market application. If you were already on the CF-Root kernel, it might remove the CF-Root specific applications like the CwM "app" (and not the recovery functionality, mind you...) and the Tweaks app as these apps were created by ChainFire specifically for his kernel.
Best advice would be to re-flash a stock firmware first, to get your Tab into a clean system. From there, you can continue to to install the kernel of your choice (like ChainFire or Kouxudaxi's fine kernels as well.... these kernels, if I'm not mistaken, do not do automatic EXT4 conversions)
If you're unsure of how to do this, refer to the guide in teamovercome.net and it'll guide you in basic re-stocking (but using our Stock safe package which will provide you with the Gingerbread-based JQ1 firmware).
LOL, +100000000000000000000000 thepitbull...
thepittbull said:
LOL. FYI, your Tab is not haunted. That voice that you refer to, is basically an indicator that the file-system on the Tab is being converted from RFS to EXT4 (what some would affectionately refer to as the lag-fix). You should have left it to continue. That's the reason we ask people to let it finish booting before doing anything else. As always, when it comes to flashing a new firmware/kernel, it's always better to read up and know what to expect.
Anyway, by the looks of it, you might have a corrupted file-system, since you keep shutting it down mid-conversion. That's the reason "the voice" keeps coming back. If you'd allowed it to complete, it should not have returned.
Secondly, flashing the Overcome Kernel alone will NOT remove the Market application. If you were already on the CF-Root kernel, it might remove the CF-Root specific applications like the CwM "app" (and not the recovery functionality, mind you...) and the Tweaks app as these apps were created by ChainFire specifically for his kernel.
Best advice would be to re-flash a stock firmware first, to get your Tab into a clean system. From there, you can continue to to install the kernel of your choice (like ChainFire or Kouxudaxi's fine kernels as well.... these kernels, if I'm not mistaken, do not do automatic EXT4 conversions)
If you're unsure of how to do this, refer to the guide in teamovercome.net and it'll guide you in basic re-stocking (but using our Stock safe package which will provide you with the Gingerbread-based JQ1 firmware).
Click to expand...
Click to collapse
Hi there,
Thank you so much for your time in replying - I've managed to install what i believe is stock Gingerbread from Samsfirmware. So everything looks back to normal... tho i have posted another Question, with all my firmware details so I can be reassured I am back to stock.
So sorry, I panicked so badly last night..ha!
You have also special thread with many scenarios how to fix your tablet if anything goes wrong.
It helped me yesterday to revive my Galaxy Tab. Just suddenly it started freezing and restarting, after 3 weeks working perfectly on Overcome. Nothing changed, or updated, nothing installed for days, and all what was ever installed are programs I already have on my two other Android phones, it simply froze in the middle of work. Wipe didn't work, changing file system didn't work, etc...
Read the thread: http://forum.xda-developers.com/showthread.php?t=1133590
Very good material.
nidza said:
You have also special thread with many scenarios how to fix your tablet if anything goes wrong.
It helped me yesterday to revive my Galaxy Tab. Just suddenly it started freezing and restarting, after 3 weeks working perfectly on Overcome. Nothing changed, or updated, nothing installed for days, and all what was ever installed are programs I already have on my two other Android phones, it simply froze in the middle of work. Wipe didn't work, changing file system didn't work, etc...
Read the thread: http://forum.xda-developers.com/showthread.php?t=1133590
Very good material.
Click to expand...
Click to collapse
Im very glad that the guide helps many ppl
@the Op : do me a fav and flash safe
Sent from my GT-P1000 using Tapatalk
k0sh said:
Im very glad that the guide helps many ppl
@the Op : do me a fav and flash safe
Sent from my GT-P1000 using Tapatalk
Click to expand...
Click to collapse
Yup, in future i will be more careful when flashing, so glad that my tablet is back to normal (albeit with the Italian release of GB ) but everything works fine.
Will do more reading on the forums before undertaking any more flashing, make sure i know what i am doing and which Rom is best for me to use.
Cheers
Sent from my GT-P1000 using XDA App
geoyakult said:
Yup, in future i will be more careful when flashing, so glad that my tablet is back to normal (albeit with the Italian release of GB ) but everything works fine.
Will do more reading on the forums before undertaking any more flashing, make sure i know what i am doing and which Rom is best for me to use.
Cheers
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
best reaction i never read
Hi all,
I've been unable to find a post about this for quite some time so I decided to make a threat about it.
I have a recurring problem with my captivate. Usually after about 2 weeks of using a ROM my phone will have 2 issues pop up simultaneously. They seem to always happen together. It seems to happen after my phone shuts off and will not turn back on until I battery pull. Once I do that I am presented with these two issues:
1.) When I try and toggle Wifi it attempts to then simply says "error" underneath it. I have found a few threads about this but no answers
2.) Upon installation OR restoration of any app with Titanium Backup my phone does a soft reboot (goes to spinning CM logo or for ICS goes to the multicolored squares flying around).
Edit: On the newest MIUI it now says "insufficient storage available" instead of rebooting when I try to install an app after the issues crop up, wifi "error" is still the same
I've had these same 2 issues occur with CM7 Stable, RC, and many nightlies, MIUI, and TeamHacksung's ICS build. I believe it may have happened with cognition too but am not positive.
I do not restore any data with TB. Before each flash I wipe system, cache, dalvik, and do factory reset and still this issue occurs without fail after about 2 weeks on any ROM and the only fix I have is to flash a new one.
Nandroid backups DO fix the problem. If anyone is willing to look through logs or something and see what was different I would be eternally grateful and certainly send you something through PayPal
Any help is greatly appreciated and I am willing to try anything at this point. Thanks!
Sorry for the double post,
Is there a better forum to post this in?
spectralite said:
Sorry for the double post,
Is there a better forum to post this in?
Click to expand...
Click to collapse
Nah this is the right place. That's a very strange problem you're having though, and I don't know what the exact solution is, if there even is one for this. The only thing I can suggest is going back to stock, and then reinstalling CM7 or whatever you want
Sent from my lightning fast Glitched 1.3Ghz CM7 i897 Captivate
Thanks,
Well happened again on newest MIUI. Gonna go back to stock and start over. I'll update the thread if it does or does not happen again.
Unfortunately after using Odin to go back to stock and rerooting/flashing it happened again on the most current build of MIUI. I'm currently at a loss for what to do. Has anyone heard of or seen anything like this?
Thanks in advance
spectralite said:
Unfortunately after using Odin to go back to stock and rerooting/flashing it happened again on the most current build of MIUI. I'm currently at a loss for what to do. Has anyone heard of or seen anything like this?
Thanks in advance
Click to expand...
Click to collapse
Just curious, have you tried leaving it stock and seeing if it happens on a pure stock ROM? If so it could be a defect with the phone?
If you flash back to pure stock and the issue doesn't come back, maybe try a custom ROM that's closer to stock, not a CM or MIUI or ICS build. I haven't seen this issue, just trying to suggest some solutions.
I had this same problem with my fascinate. I flashed 1.10.21 MIUI follwed by glitch 13.1. This combination used to work, or so I thought. I flashed back to stock, 1.12.1 then a different package of glitch 13.1 and my wifi started working again. I know the captivates and fascinates are somewhat different, but try this out and see if it works.
bobbylx said:
Just curious, have you tried leaving it stock and seeing if it happens on a pure stock ROM? If so it could be a defect with the phone?
If you flash back to pure stock and the issue doesn't come back, maybe try a custom ROM that's closer to stock, not a CM or MIUI or ICS build. I haven't seen this issue, just trying to suggest some solutions.
Click to expand...
Click to collapse
I guess I could try that, I just like CM7/MIUI so much. Another thing that happens is many different applications start FCing after the problems all begin.
I tried to restore to a nandroid backup I had made before it happened this time and I received an MD5 mismatch which I believe happened last time I tried to restore...
New info:
I have not realized this before but it seems that I start getting a message that says, "Google Talk Authentication Failed", around the same time. Also FCs happen much more frequently. Is there anything I could be doing to cause this?
New Info
Just going to keep this updated with things I have tried in case anyone ever searches for this that has this issue:
Full format of SD card and odin back to stock did not prevent the issue from cropping up on the DarkKnight3 ROM with Icy Glitch. At this point I can only assume it is somehow hardware relatedl
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!
Hi everyone
Thanks for everyone's support before. It gave some confidance.
It doesn't work though. It's starts updating and then reboot with the message "Update failed, try using Kies, or go to Samsung service centre".
I removed root it didn't help. I got CWD flashed. Could that be a problem.
Could I get rid if it just to be able to uodate?
Need some help here. Kies seems dodgy judging by the posts.
Thanks in advance.
You need stock recovery if you want to update the official way.
What do I do
Could you explain to me what to do please. And should I mess with Kies. Or it wouldn't work either?
Or may be I could just flash it with Odin? Do you know where I could get
the latest Honeycomb flashable file? Since I already have CWM. And everything from xda seems to work. I just thought mabe just ODIN that update if I could get it.
Stock recovery means that I would need to get rid of CWM. How could I do it please?
Surprisingly enough I managed to get back to stock recovery. The Guide in this forum is amazing. I was scared stiff since i never done it before. It went well but still the update doesn't work. No root. No CWM. Still stops and reboots.
Anyone any ideas please?
Exactly what are you trying to do? You want the latest stock rom? Yes, you can flash it with Odin, there's a guide for that also.
I think it worked. I flashed a stock recovery with Odin. And then updated with Kies. It went down rather well. I sleepless night and all that stress just to see that I liked HC 3.1 better. Especially the dock bar that I could swipe before. And now I have to hit a stupid mini triangle.
Anyway, learnt quite a lot. Used Odin for for the first time and CWM. Cool.
It crashed already twice. Could it be because of installing too mush stuff too quickly? I'm just too impatient to get it back on the road. Like over a 20 apps at the rate of 2 or 3 at a time. Or is it supposed to be able to take it and sth is wrong with the ROM?
Cheers
Nobody cares probably but I'd just like to thank everybody who replied to
my posts. Everything seems to work now. I think it's better. Ebook in the update rom reads French now. Which is handy. That's life, as far as the fact that I bought Moonreader goes. Google play did a wierd thing that I didn't ask for but It saved me about 5 hours. It just backed up, finaly that feature worked, 95% of my apps and then automaticly reinstalled them after a crash and a factory reset. So now I have to sort out the sleep debt.
Love this forum even more now.
Oh and the Guide is ****ing brilliant.