Related
Update: I figured out the issue
So, I had my device rooted and attempted to install the Voodoo lagfix. I had the SRE 1.3, but I didn't apply the one click lag fix. From what I found, there shouldn't be any problem applying the voodoo lagfix over the SRE kernel. Anyways, to be sure, I reflashed my kernel back to the stock JH7, and used the update.zip method. I got the robot voice telling me it was done, but it stayed on the ATT startup screen for, well, EVER. It never booted up past that point. Worried I had done something wrong, I reflashed, and ran the remove lagfix thing as there was a voodoo folder created. I tried it again and I got the same thing.
Again, I removed the lagfix, reflashed, and tried again, but this time, I fell asleep (for 8 hours or so...) and it was still at the ATT boot screen.
Am I doing something wrong?
Note: I do have my device overclocked (as included with the SRE build I used). Would that matter?
Thanks!
Looks like the overclocking wasn't compatible. This thread can be closed/deleted. Thanks
like i have said in a few post asking questions, i am very new to the android world....so far though i love it. best phone OS i have seen....i am torn between a few roms on here that i like, features of some and others...i have a friend that has been helping me to do everything, he is a veteran at this stuff....i am having some issues with roms, 3 that i have tried and liked is phoenix 2.0, gingerclone, and perception 10.1, the problems i am having is that the phone seems to shut it self off, it does it with any of the roms i am pretty sure...i have been trying to use SetiroN i9000 SuperOptimized v1.5.6 kernel for the great UV/OC features....almost seems like you can never get these phones to 1.6 though so is there a better kernel that you guys would suggest for use with these roms instead.....maybe the glitterballs...also when i use the Odin3 One Click to try and restore my phone it leaves all the files from CWM and Voodoo on the phone is there a better way to restore the phone? any help that you guy can give me would be great...btw i am not a noob when it comes to computers, so i can pretty much comprehend most of what you can throw at me just looking for some experienced users....ty in advance
Jason
Use odin and master clear your phone. It wipes EVERYTHING off your phone and returns it to stock.
Also, do you use oc feature when you experience these random shutdowns?
Sent from outerspace
even without OC i am still getting the shutdowns....also i can use one click and hit the start and it does what its supposed to but if i get into downloading mode and hit master clear it just sits at starting master clear for like 10 minutes and does nothing
superj3211 said:
even without OC i am still getting the shutdowns....also i can use one click and hit the start and it does what its supposed to but if i get into downloading mode and hit master clear it just sits at starting master clear for like 10 minutes and does nothing
Click to expand...
Click to collapse
Master clear doesn't work through download mode. It works with the phone turned on and fully booted. After you use odin to flash back to stock, enable usb debugging under settings-applications-development. With usb debugging enabled, launch odin, plug in your usb cable (odin should now recognize your phone), and THEN hit "Master Clear". It will run, your phone will reboot, and the internal sd will be wiped clean. If you have any data on there that you want to keep, back it up on your computer before doing the master clear otherwise it will be gone for good.
Also, a friend of mine just got a captivate a few weeks ago and he wanted me to root/flash it for him. Every time I tried, no matter what I did, he kept getting random shut-downs while running custom roms. Even with cognition, which is crazy stable and built off captivate firmware. I have flashed my phone more times than I can count, so I'm convinced the issue was with his specific phone, but who knows??
On a final note, don't bother with trying to oc your phone to 1.6. Its not stable. Most people can barely get it oc'ed to 1.35. You can still use seti's 1.5.6, just don't enable the higher frequencies. You could also switch to one of his 1.4.7 variants. If you want pure stability, use fire bird kernel or gkitterball's kernel if you still want the oc.
cool thank you...i am liking the firebird, but everyone is talking great about glitterballs kernal, but the zip that gb is packed with wont install....trying to figure out the version that is packed with phoenix rising 2.0....anyone know this answer....also i tried phoenix when it first hit and then tried gingerclone now going back to phoenix the background is different, how do i get back to the original theme
Hello. As you can see from the title, I am stuck at the sgh I897 bootscreen. No matter what rom I flash I still get stuck unless i flash ultimate 7 tims tweak which I don't want because TiBu keeps erroring. I've tried Odining a thousand times. Oh and did I mention i'm leaving for vacation in 3 hours? Yea so time is kinda a factor. I'm not freaking out if you get that tone from this thread, but i'm kinda aggrivated, as this is the last thing i need to worry about. Any help is appriciated, and if you have the time, throw in the name of the best battery life on what rom just in case I get stranded in the desert and my phone has been on for 24 hours lol.
You are going back to stock but other roms won't install
Yes. I odined and then I flashed some Roms from my SD like I always do and then it got stuck.
EDIT: I flashed continuum, darky's and serendipity and they got stuck. But I flashed Andromeda, and it worked.
How long are you getting stuck for because some roms take a little longer on the first boot due to file conversions and initial install.
Longer than normal. About half an hour before I lose patience.
Hello astute folks on XDA!! My name is Brian and i'm a flash-a-holic. I'd like to share with you my experience that ultimately lead to me fubaring my beloved captivate.
I've flashed everything under the sun on this phone from roms to different kernels to modems. You name it, i flashed it with great success (after researching, never flashed on a whim.) UNTIL... Yesterday.. lol.. I was running a leaked 2.3.4 gingerbread rom and i noticed the problem first starting while trying to connect my phone to my computer via usb. The two didn't communicate when for the last 6 months, every single time i plugged in, my computer and phone recognized each other every single time. So that was my first clue that something aint right. Next thing i did was power the phone off. Went to turn it back on and NOOOOPPPEEEEE!!! Nothing!!!!! Held all three buttons and the little grey circular icon came on (the one that is initially in the battery icon when the phone is powered off but it's plugged in) but immediately shut off. Nothing turned my phone back on, but i was able to get into download mode. So thats what i did. I used odin3 oneclick to go back to stock eclair thinking that that will start everything all over, erase the bad/corrupt files and so forth. Flash was successful. Got back to stock eclair and got stuck in MTP initialization (you know, the screen in which you get if your debugging mode wasn't checked.) But it hung on that screen. No buttons would allow my to exit so, I pulled the battery. Then, the same damn thing.. I could NOT get the phone to power back on. Lesson learned for me. (today i learned that going back to stock is NOT a fresh install.) Used odin again, but this time unplugged my cord BEFORE i got to the eclair boot screen. As i'm peering at this home screen, i noticed that my USB connecting notification was flashing on, off, on, off yet my cord was unplugged. At this point i called tech AT&T tech support because i knew i was screwed. (i told them i tried to update to the 2.2 they provided on website and the phone cut out, lol).. I spent an hour on the phone and got no where other than determining that my phone is farked and they are gonna send me out a replacement (which will take 4 to 6 days) because luckily it was under warranty still. Tech support couldn't get my phone to turn on, but i could, lmao.. So... here i am stuck with a phone where usb debugging mode is buggin out!!!!!!! To wrap this story up, what i did was got back into download mode and flashed gingerbread bootloaders and a kernel and voila!! So long as i don't turn my phone off, i have a fully operational phone until my new cappy arrives in the mail in 4-6 days. (Dicks.. If i had been ordering a new phone, i'd have the option for next day shipping but thats another story.)
TLDR: Flashing too much will get you in a bad situation. Stick with a rom/modem/kernel setup that suits your needs because your next flash could be your last depending on the components in your phone.
EDIT: MAKE IT KNOWN THAT I HOLD NO ONE RESPONSIBLE OTHER THAN MYSELF FOR THE FUBARING OF MY CAPPY!!!!!!!!!!
Ok!?! This is not a question, this should be in the general thread if anywhere.
Could a moderator please move this.
Things break...and ppl make mistakes... I'm still trying to figure out which one happened in your situation.
Sent from my SGH-I897 using XDA Premium App
That's a common hardware issue with the captivate. Happened to me twice. Its just the USB port spassing out thinking tthe cable is constantly getting plugged in and unplugged and freezing tthe phone with its craziness. Both times it was replaced under warranty. I'm paranoid it'll happen again now that I'm out of warranty.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
speedy_11 said:
Ok!?! This is not a question, this should be in the general thread if anywhere.
Could a moderator please move this.
Click to expand...
Click to collapse
Oops, my bad!! It needs to be somewhere as a precaution to those that think flashing is completely harmless
EDIT: upon further contemplation, it really is a question of what went wrong
Sent from my GT-I9000 using XDA Premium App
I am a flash addict as well
i have flashed all froyo based roms on my cappy !
Can anyone confirm that excessive flashing may risk my phone?
Doubtful that excessive flashing had anything to do with this. Just be sure to do all necessary wipes and take all the required steps before you flash a rom and you SHOULD be okay. You are always taking a risk when you flash your phone regardless of how many times it has a positive outcome.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
Thanks for the quick response....!
now i dont need to worry
xijar said:
Doubtful that excessive flashing had anything to do with this. Just be sure to do all necessary wipes and take all the required steps before you flash a rom and you SHOULD be okay. You are always taking a risk when you flash your phone regardless of how many times it has a positive outcome.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
Click to expand...
Click to collapse
I'm 99% sure my board failed because of cheap, unreliable components. However, that 1% is still in the back of my mind that it could have been from something I flashed. I suppose I'll never know.
Sent from my fubared, soon to be replaced cappy running GT-I9000 gb rom using XDA Premium App
It is hard to tell from what you say that it was purely hardware. Definitely sounds like the issue locked up the phone more then it did mine the two times I experienced it but it definitely wasn't performance friendly to me either. It seemed to settle down for,me intermittently then act up again. I never lived with it for too long since there's a warranty center i can do a walk in exchange at less than a mile from my house.
PS. I would flash stock jf6 then update via kies if possible before you send iit in to avoid being charged $500 for voiding the warranty. If kies wont work flash jf6 and find the jh7_ota.zip file floating around the forums to flash stock jh7 In cwm then remove cwm. There is a zip file that restores stock recover. I can provide these files if you can't find them not sure if they still have active dl links.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
Accidental post. Please delete.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
xijar said:
It is hard to tell from what you say that it was purely hardware. Definitely sounds like the issue locked up the phone more then it did mine the two times I experienced it but it definitely wasn't performance friendly to me either. It seemed to settle down for,me intermittently then act up again. I never lived with it for too long since there's a warranty center i can do a walk in exchange at less than a mile from my house.
PS. I would flash stock jf6 then update via kies if possible before you send iit in to avoid being charged $500 for voiding the warranty. If kies wont work flash jf6 and find the jh7_ota.zip file floating around the forums to flash stock jh7 In cwm then remove cwm. There is a zip file that restores stock recover. I can provide these files if you can't find them not sure if they still have active dl links.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
Click to expand...
Click to collapse
As I started before, the phone is fully functional with gingerbread other than the occasional usb flickering..Only problem I have with it really is if I turn the phone off, it won't turn back on unless I hold power and volume up, enter cwm and then select reboot now.
Before I send it back, I'll odin back to jf6 first with oneclick. Without cwm on the phone, lol, it absolutely won't turn on by just using the power button. I made sure of this before I even called the warranty department and explained my dilemma
The nice thing is that I can use the phone while I wait fire the new one to arrive AND I can flash and experiment with everything now without worries!!!
Sent from my fubared chappy running GT-I9000 GB rom using XDA Premium App
I am also a flash-o-holic and I think that if you flash with odin lots with repartition checked or are enabling/disabling voodoo lots, it can mess up your phone. Has happened to me twice, just sent my phone today for the second time. Both times this happened to me it happened when successfully flashing back to stock with 512.pit and repartition checked. On boot up it stalls at the "S" screen and never goes past it and in recovery I get some errors like:
error: can't mount /dev/block/mmcblk0p1
error: can't mount sdcard
I flashed many different firmwares with different pit files and different android versions but all conclude the same, stuck at the "S" boot screen.
I have determined that the partition tables were messed up and I tried to fix it by putting parted on my phone and trying to repartition it from the shell. Both times I get the "unable to write to /dev/block/mmcblk0 - I/O error!" Also, from CWM Recovery I try repartition sdcard but it also comes up with an error. The last time I sent it into Samsung repair they had to replace the main board to get it working properly again. Think it is definitely a good idea to find a rom / kernel / modem you are happy with and stick with it for a while.
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!