Related
I've been searching, and reading, and my eyes hurt. I normally don't like to post threads, but I'm left with no choice. If this topic has been covered, then I guess my searchin' skillz are stating to lack. Here is my delimna:
Rooted, Lagfix, enabled Side-loading, recently installed ClockworkMod, stock firmware. I ran a backup using ROM Manager/ClockworkMod. I was attempting to install the Mobile AP fix for WiFi Hotspotting from designgears. I downloaded the new kernel per instructions (Mobile AP ony). I first tried installing it using ROM Manager's boot option into Clockwork without renaming MobileAP.zip. Still received black screen when I open the Mobile AP settings that the new kernel was trying to fix. So I thought that the flash didn't work, so this time I renamed the kernel file to update.zip and did the standard method of flash using stock recovery mode.
Now the phone boots to the Galaxy S screen, then just a black screen. The bottom row buttons seem to be active, but nothing happens. Holding power....nothing. I have to pull the battery; however, I can boot into stock recovery.
Now here's the delimna. I can boot into recovery, but the update.zip file is NOT the one for ClockworkMod, its the modified kernel. Is there a way that I can browse the files on the phone so I can change the update.zip file? I want to put Clockwork's in place so I can restore using my backup made yesterday....It's not a huge order if I have to flashback to stock and lose everything as I usually do that everynow and again anyways (usually I'm prepared). I won't lose anything important that isn't already backed up except maybe some pictures....
BUT, I can't help but try. It's just me I like to break stuff and fix 'em. I want to try to run that backup I made. I have Odin, and I tried flashing the kernel back to stock (i had one hell of a time finding information on how to use it). As a matter of fact, I found instructions on HOW to use it, but I gave up trying to find useful information on how the program runs (like a user guide, what else can it do, that sort of thing....). I spent hours reading thread after thread........information overload I guess.
I figured someone might point me in the right direction. How can I browse/edit the contents of the phone while in Recovery or Download mode?
You could try letting the phone boot up, yes I know it's only a black screen, then plug in the usb to your PC and see if ADB works.
If so then just adb shell into it and work with command line.
I'm not sure if ADB would work in stock recovery mode but that's worth a shot too.
Excellent idea, but no luck. I can get the computer to recognize the phone in recovery mode, but ADB shows the device offline, and Windows Explorer shows 2 drives with the whole "insert disk into drive ..." message. Can't boot phone to enable "development mode", that might have something to do with it......unless I'm missing something?
swedishcancerboi said:
Excellent idea, but no luck. I can get the computer to recognize the phone in recovery mode, but ADB shows the device offline, and Windows Explorer shows 2 drives with the whole "insert disk into drive ..." message. Can't boot phone to enable "development mode", that might have something to do with it......unless I'm missing something?
Click to expand...
Click to collapse
Wasn't sure if that would work or not.
So, if you turn it on and just let it sit as long as a normal boot, then try adb does anything work?
I actually let it sit for ~15 minutes. computer doesn't even register the usb being plugged in. I'm going to give it another go or two, but in about an hour I'm going to have to call it quits and just flash it with Odin. Don't want to give up yet, but I am driving out of town later this afternoon and must have my phone for the trip. Maybe I'll break it again tomorrow and play with it over the weekend!
Let me know if you have any other ideas. I'll let you know when I give up.
While on that subject (watch someone tell me to move my post after this.....), maybe I'll experiment with a new ROM. Any recommendations? (without OC, device is fast enough). I haven't read much on the different flavors available at the moment (I think I read something about a 2.2 from I9000 or something?).
swedishcancerboi said:
While on that subject (watch someone tell me to move my post after this.....), maybe I'll experiment with a new ROM. Any recommendations? (without OC, device is fast enough). I haven't read much on the different flavors available at the moment (I think I read something about a 2.2 from I9000 or something?).
Click to expand...
Click to collapse
Hybrid from eugene is pretty fast especially if you add the voodoo kernel to it. Thats what I heard tho. Because when i tried it out it was pretty quick with out a lagfix and without autokiller. Only used it for 20 min tho as i couldn't get Titanium backup to work. I think the titanium problem is a hit or a miss.
well, I guess I'm going to have to load stock and wipe everything...oh well. Let's see how this goes. Then I'll start playing with ROMs this weekend. Thanks anyway!
swedishcancerboi said:
well, I guess I'm going to have to load stock and wipe everything...oh well. Let's see how this goes. Then I'll start playing with ROMs this weekend. Thanks anyway!
Click to expand...
Click to collapse
Well, if your going to do that take an extra 2 minutes and load Eugenes Hybrid R3 while your at it. It's extremely easy to do and in my opinion the fastest thing we can put on these phones right now.
Vibrant ROM? is that safe? I mean, I know they are all Galaxy S, but is the hardware really that identical?
I don't think eugenes captivate hybrid is actually a vibrant rom. I think he just borrowed some of the better parts.
Sent from my SAMSUNG-SGH-I897 using XDA App
Got it! I used the one click stock down loader to get the phone to boot. I then noticed that many of my files were still there, music, zips.....so I thought....maybe my backup is still there.
Instead of using my original root, I decided to try Unleash the Beast.applied it so I could load Rom Manager.i opened Rom manager and it showed my backup!
I tried restoring then without success (no update.zip) and had to flash clockwork (even though it showed it already loaded, guess it needed to be refreshed, makes sense since it is a fresh firmware), selected my restore and it ran like a charm.
I am just surprised. I thought the act of flashing the Rom would wipe everything. Apparently not if you never do the "master clear."
Thankfully I had just installed Rom Manager the day before and had a fresh backup. Looks liked I'm gonna have to start shelling out more beer money to the devs!
Now I can prepare to break it again and again. Let the fun begin!
Sent from my SAMSUNG-SGH-I897 using XDA App
Nice. Yeah, stuff you have stored on your "internal SD" is safe between flashes. Of course apps, contacts, etc get wiped, but that's an easy fix.
"the more you know," eh? Ha!
Sent from my SAMSUNG-SGH-I897 using XDA App
After waiting for the official AT&T froyo release with the captivate, I decided to just go ahead and flash a froyo ROM. I've decided to flash the axura ROM first since i heard good things about it.
So while I'm finishing charging my phone before the flashing, is there anything I need to keep note of before flashing so that I can prevent bricking my phone? I've read up on the forums and watched the video from connexion2005 from the post: http://forum.xda-developers.com/showthread.php?t=867153.
Its pretty scary since I'm not much of a tech savy guy and this is my first android phone. Any help and suggestions will be appreciated.
agegsg said:
After waiting for the official AT&T froyo release with the captivate, I decided to just go ahead and flash a froyo ROM. I've decided to flash the axura ROM first since i heard good things about it.
So while I'm finishing charging my phone before the flashing, is there anything I need to keep note of before flashing so that I can prevent bricking my phone? I've read up on the forums and watched the video from connexion2005 from the post: http://forum.xda-developers.com/showthread.php?t=867153.
Its pretty scary since I'm not much of a tech savy guy and this is my first android phone. Any help and suggestions will be appreciated.
Click to expand...
Click to collapse
Backup all your apps and data with Titanium Backup. Make sure your battery is fully charged, and removing your sim and SD cards are good practice.
Have fun! You won't go back.
- Backup all your files and make a nandroid backup!
- Get Odin3 One-Click and drivers to get your phone back to stock in case you brick it: http://forum.xda-developers.com/showthread.php?t=731989
- There may be additional precautions you can take, so read through related threads on xda.
agegsg said:
After waiting for the official AT&T froyo release with the captivate, I decided to just go ahead and flash a froyo ROM. I've decided to flash the axura ROM first since i heard good things about it.
So while I'm finishing charging my phone before the flashing, is there anything I need to keep note of before flashing so that I can prevent bricking my phone? I've read up on the forums and watched the video from connexion2005 from the post: http://forum.xda-developers.com/showthread.php?t=867153.
Its pretty scary since I'm not much of a tech savy guy and this is my first android phone. Any help and suggestions will be appreciated.
Click to expand...
Click to collapse
If you've read as much as you claim to have read, then you're probably in good shape. It's really not an unsafe process as long as you have some idea of what you're doing. I was very nervous about it myself the first time, but since then I've probably flashed 20 roms without a problem.
A couple of things that I would tell you, if you aren't already aware:
1. MAKE SURE that BEFORE you flash, you can get into download mode from the phone being off using one of the methods. I'm sure you've seen the one-click flash back to JF6 (stock) that was posted - download that if you haven't. For me, removing the battery, sim, and ext sd, replacing the battery, and holding down both volume buttons while plugging in the USB works really well - just make sure Odin is running before you do that. If you do manage to brick it, you will want to be able to get to download mode and flash back to stock.
2. After moving to a custom rom, it is best to always flash back to stock before flashing a different rom; you can avoid a lot of potential problems this way.
3. After rooting your phone, backup the update.zip in /sdcard/ on your computer. Any time you flash back to stock, you can reinstall CWM really easily by just putting that update.zip back in /sdcard/ and choosing "reinstall packages" from the recovery menu again. Sometimes you may have to do it twice before it enters CWM.
4. OCLF in the market is, to me, the easiest and quickest way to root your phone, but the one click root method isn't much worse. Just a matter of preference, I guess.
Good luck! Come back if you have any problems.
EDIT: apparently two people replied while I was typing my response lol! But what they said is very good as well.
Thank you for all your help. One quick question though, do I need the android ID changer?
the biggest mistake people make is not making sure they have the button combinations to enter recovery or download. (download = hold both volume buttons own and plugging usb cable in; recovery = hold volume buttons down, then holding power until AT&T screen pops up, letting go of power but still holding both volume buttons) if either of these don't work, you must, before doing ANYTHING else, flash the stock odin one click with the button fixes; it is posted somewhere in the development forum. and no you shouldn't need the android id changer unless you want to keep the android id that your phone came with. then open the changer and click save id and flash your rom of choice. most custom roms have a script to automatically load a saved id or randomly generate one if there wasn't a saved one. good luck in all your flashing endeavors!
edit: also as bodaciousdrake mentioned previously about cwm recovery, you should always keep the update.zip that contains cwm recovery on your sd card and you'll never need to change that to something else because using cwm recovery you can flash any .zip file that you want and it does not need to be named update.zip.
Take out the external SD card before you accidently delete 10 GB of music you had just perfected the selection of. (not that I accidently did that... lol)
mindbullet said:
Take out the external SD card before you accidently delete 10 GB of music you had just perfected the selection of. (not that I accidently did that... lol)
Click to expand...
Click to collapse
lol oops! Did that happen with a master clear, or when you flashed the rom? I have forgotten to take out the sim/ext sd once or twice but I have never had a problem...yet.
agegsg said:
Thank you for all your help. One quick question though, do I need the android ID changer?
Click to expand...
Click to collapse
Yes, you need it. Download it from the market, while on 2.1, and save your id onto your sd card. After you are on 2.2, choose Load id and it will automatically reboot.
majinzen said:
Yes, you need it. Download it from the market, while on 2.1, and save your id onto your sd card. After you are on 2.2, choose Load id and it will automatically reboot.
Click to expand...
Click to collapse
What exactly is the point in saving the phone id? Sorry I'm kinda a noobie at this and looking up things about phone id, it seems like it just is an identifier for the phone but doesn't really provide anything.
Also, how do I get out of download mode? I've put it in download mode to make sure it works and it seem I can't get out of it... I've done the 2 volume bottons with the usb cord.
there's another thread in this forum that answers that question perfectly. also to exit download mode you need to pull the battery out.
slifer315 said:
there's another thread in this forum that answers that question perfectly. also to exit download mode you need to pull the battery out.
Click to expand...
Click to collapse
Really? just take the battery out?
agegsg said:
What exactly is the point in saving the phone id? Sorry I'm kinda a noobie at this and looking up things about phone id, it seems like it just is an identifier for the phone but doesn't really provide anything.
Click to expand...
Click to collapse
Basically, a lot of 2.2 Roms come with the same android id, 977blah... If you don't want market issues later I would suggest that you put in your original 2.1 android id. You can always search more if that answer isn't sufficient. And yes, do a battery pull to get out of download mode.
I've master cleared but can't seem to root. Every time I try with the one click root, and I go to recovery, it said it can't find the update.zip from the /sdcard/
yep, just pull the battery. also you don't need to root to flash roms. just grab the update.zip containing clockwordmod recovery from the thread in the development forum, put it on your sd card, boot to recovery and select reinstall pacakges. after that, reboot the phone (you might have to reinstall packages again) then you'll be ib clockwordmod recovery and you'll be able to flash any rom you want without having to change the filename.
agegsg said:
I've master cleared but can't seem to root. Every time I try with the one click root, and I go to recovery, it said it can't find the update.zip from the /sdcard/
Click to expand...
Click to collapse
For some reason I got this too the first few times I tried to root. I then noticed that in the cmd prompt, for a split second it said failed to push update.zip or something due to privileges.
How I fixed it was ran the one-click root on windows in admin mode. It worked after that.
Thanks guys for all your help. I got it to flash the ROM and it seems I haven't bricked my phone
Thanks again
Hi guys,
I have been searching the forums for 2 weeks now trying to fix this myself, but I have put my pride in my pocket and am asking for help.
Backstory: Rooted phone, flashed CWM, used tons of custom froyo ROM's (doc roms mainly) and most recently Darky's 9.3 (awesome).
But then i decided I wanted Gingerbread (this is where the trouble began). Gingerbread worked just fine, but as there is no custom roms, I flashed back to 2.2 (obviosly screwed something up), because since then I have been plagued with process com.whatever.android.somethingelse has stopped unexpectedly. please try again.
please don't ask which force close message I am getting, lets just say, I am pretty sure I am getting them all!
I have flashed stock 2.1, custom 2.1, stock 2.2, custom 2.2's, I even went back to gingerbread a few times trying to fix this ***** of a problem. I tried re partitioning just the .pit file and then the other 3 files seporatly. NOTHING WORKS.
So, I am calling out to all you guys and girls who are heaps smarter than me to please help. the phone functions, turns on, make or receive calls and texts (not mms), emails work sometimes, but if I turn the phone off and on all the settings are wiped and I need to reload all the user details.
Oh, I should also add another major issue, I cannot use the internal memory for anything, I cannot take pictures unless I select the external SD card, I cannot install apps from market or .apk. I cannot even move data to it when its mounted on the pc.
I am completely lost. please help me.
And thanks in advance.
I
C'mon guys, I know there is a lot to read, but please, can no-body help me?
Sounds like it might be a dead internal sd card. You said you tried a re-partition with 3 file firmware? That should fix pretty much anything. I think your only option is to return to samsung at this point.
DrFredPhD said:
Sounds like it might be a dead internal sd card. You said you tried a re-partition with 3 file firmware? That should fix pretty much anything. I think your only option is to return to samsung at this point.
Click to expand...
Click to collapse
Thanks for the response.
is it possible to fix myself?
As Samsung will not cover it, even if I flash the stock Telstra ROM, it will still show that it has been rooted?
In doing your research, I'm sure you've heard of the internal SD problems that plague the i9000, are you by chance with Bell Mobility? This line concerns me..
"Oh, I should also add another major issue, I cannot use the internal memory for anything"
When I experienced multiple FCs (force closes) and incompatible system UID's, I tried flashing every kind of ROM there was with every kind of PIT file as well to no avail. However, one in particular worked for me and others. It is usually referred to as a full ROM. It contains the .csc and .sbl in it as well as the usual ROM contents.
The ROM I used is called FULL-i9000UGJH2.tar. Note, flashing this ROM with a pit file (be it 512, 513, or 803) wouldn't help me at all. What fixed the problem was flashing ONLY the ROM file in ODIN. Unfortunately, I can't find the thread where I found this ROM. I suggest searching around for it, if you can't find it PM me, and I will up it somewhere for you.
I'm not sure if this will help with your specific case, but its worth a shot. Also, wherever applicable, do a factory reset, clear your cache, and a full wipe install.
Good luck.
[edit]
Do a complete wipe and install with a stock 2.2 or 2.1 ROM in ODIN, there will be no evidence of a root.
Kops said:
In doing your research, I'm sure you've heard of the internal SD problems that plague the i9000, are you by chance with Bell Mobility? This line concerns me..
"Oh, I should also add another major issue, I cannot use the internal memory for anything"
When I experienced multiple FCs (force closes) and incompatible system UID's, I tried flashing every kind of ROM there was with every kind of PIT file as well to no avail. However, one in particular worked for me and others. It is usually referred to as a full ROM. It contains the .csc and .sbl in it as well as the usual ROM contents.
The ROM I used is called FULL-i9000UGJH2.tar. Note, flashing this ROM with a pit file (be it 512, 513, or 803) wouldn't help me at all. What fixed the problem was flashing ONLY the ROM file in ODIN. Unfortunately, I can't find the thread where I found this ROM. I suggest searching around for it, if you can't find it PM me, and I will up it somewhere for you.
I'm not sure if this will help with your specific case, but its worth a shot. Also, wherever applicable, do a factory reset, clear your cache, and a full wipe install.
Good luck.
[edit]
Do a complete wipe and install with a stock 2.2 or 2.1 ROM in ODIN, there will be no evidence of a root.
Click to expand...
Click to collapse
Thanks for this dude, I will start my search for that rom.
I do a factory reset, wipe cache and data every time, however after doing all of that and flashing a new rom, it still has my google account details in the phone?? this is wierd, as I factory reset from recovery mode AND wipe all data from within the phone? Any suggestions?
Edit: and no, its is an Australian Telstra i9000
glennr said:
Thanks for this dude, I will start my search for that rom.
I do a factory reset, wipe cache and data every time, however after doing all of that and flashing a new rom, it still has my google account details in the phone?? this is wierd, as I factory reset from recovery mode AND wipe all data from within the phone? Any suggestions?
Edit: and no, its is an Australian Telstra i9000
Click to expand...
Click to collapse
Hmm, that is odd. How are you flashing your ROMs, using CWM? Have you used ODIN before?
Kops said:
Hmm, that is odd. How are you flashing your ROMs, using CWM? Have you used ODIN before?
Click to expand...
Click to collapse
I am using odin, this is the wierd part. I have tried repartitioning, not repartitioning, I have tried 512.pt 803.pit, full wipe and reset from both in the phones settings and recovery mode. reboot it, go through settup wizzard (which eventually force closes requiring me to reboot), go into accounts and there is my google account still set up???
Edit: also, I cannot find a file called FULL-i9000UGJH2.tar, I am downloading i9000UGJH2.tar as we speak, but i doubt it is the one you were reffering to, if you are able to point in in the right direction, that would be ace.
Cheers
glennr said:
I am using odin, this is the wierd part. I have tried repartitioning, not repartitioning, I have tried 512.pt 803.pit, full wipe and reset from both in the phones settings and recovery mode. reboot it, go through settup wizzard (which eventually force closes requiring me to reboot), go into accounts and there is my google account still set up???
Click to expand...
Click to collapse
If you're entering your gmail address in during the setup wizard, our google account will be linked. If you're not setting anything up and it is remembering your info, then something is definitely fishy.
I would flash back to a stock rom, and see what Samsung or your provider can do for you. In all honesty, the only thing I would be able to suggest is flashing and wiping
[edit]
When you download that ROM, open it up (using a program like WinRAR). The point of a full rom is that it contains
-cache.rfs
-dbdata.rfc
-factoryfs.rfs
-modem.bin
-param.lfs
-sbl.bin
-zimage
I'm unsure of any incompatibilities between the Canadian and Australian versions, but I will upload my copy for you to try.
Kops said:
If you're entering your gmail address in during the setup wizard, our google account will be linked. If you're not setting anything up and it is remembering your info, then something is definitely fishy.
I would flash back to a stock rom, and see what Samsung or your provider can do for you. In all honesty, the only thing I would be able to suggest is flashing and wiping
Click to expand...
Click to collapse
I'm not entering any info during the setup wizard?
could it be something to do with the file system gingerbread uses? these issues only started when I went back from gingerbread to froyo? (and before you ask, I have tried going back to gingerbread with no solution)
I may have to bite the bullet and shoot it back to Samsung... or just buy another one! would love to try FULL-i9000UGJH2.tar if you could remember where you got it?
Thanks again for your help.
Cheers,
glennr said:
I'm not entering any info during the setup wizard?
could it be something to do with the file system gingerbread uses? these issues only started when I went back from gingerbread to froyo? (and before you ask, I have tried going back to gingerbread with no solution)
I may have to bite the bullet and shoot it back to Samsung... or just buy another one! would love to try FULL-i9000UGJH2.tar if you could remember where you got it?
Thanks again for your help.
Cheers,
Click to expand...
Click to collapse
I seem to have remembered it being in this thread, which is why i had it on bookmark, but I'm not sure if the link has been removed or if i had been mistaken since I can no longer find it. I'm uploading for you to Rapidshare, where you can download as a free user...~30 mins . Again, I'm not sure if there are modem incompatibilities or not since this I am in Canada, and you are in Australia.
Another place to check may be here...
http://forum.xda-developers.com/showthread.php?t=846913
Kops said:
If you're entering your gmail address in during the setup wizard, our google account will be linked. If you're not setting anything up and it is remembering your info, then something is definitely fishy.
I would flash back to a stock rom, and see what Samsung or your provider can do for you. In all honesty, the only thing I would be able to suggest is flashing and wiping
[edit]
When you download that ROM, open it up (using a program like WinRAR). The point of a full rom is that it contains
-cache.rfs
-dbdata.rfc
-factoryfs.rfs
-modem.bin
-param.lfs
-sbl.bin
-zimage
I'm unsure of any incompatibilities between the Canadian and Australian versions, but I will upload my copy for you to try.
Click to expand...
Click to collapse
Mate that would be great, I am not too fussed about compatibility at this stage, just want to get access to the internal sd again, then I can flash one of the many working froyo roms I have.
Cheers bud.
glennr said:
Mate that would be great, I am not too fussed about compatibility at this stage, just want to get access to the internal sd again, then I can flash one of the many working froyo roms I have.
Cheers bud.
Click to expand...
Click to collapse
The way you're referring to accessing this internal SD....are you flashing your ROMs to an external microsd card?
Here is the full UGJH2 that I flashed (with no other options) that saved me.
http://rapidshare.com/files/456841681/FULL-I9000UGJH2.tar
Give it a shot.
Kops said:
The way you're referring to accessing this internal SD....are you flashing your ROMs to an external microsd card?
Here is the full UGJH2 that I flashed (with no other options) that saved me.
http://rapidshare.com/files/456841681/FULL-I9000UGJH2.tar
Give it a shot.
Click to expand...
Click to collapse
No, by accessing my SD, i mean being able to download ansd install apps (and things like that). also, just tried to remove my google (gmail) account from my phone, and it wouldn't let me, it keeps force closing.
Thanks for the upload mate, I really appreciate it, currently downloading it, will let you know.
Cheers again.
Kops said:
The way you're referring to accessing this internal SD....are you flashing your ROMs to an external microsd card?
Here is the full UGJH2 that I flashed (with no other options) that saved me.
http://rapidshare.com/files/456841681/FULL-I9000UGJH2.tar
Give it a shot.
Click to expand...
Click to collapse
Hey mate, no go, i got some functionality back on the phone, but still force closes and I cannot save anything to SD (or install apps).
another email account (an exchange server account) that was previously deleted has appeared back set up and working (I have not been able to set this up for a week), it appeared on its own which leads me to think there is a hidden partition on my internal sd, hence I cannot access it. must be something to do with Gingerbread.
Thanks for all your help though.
glennr said:
Hey mate, no go, i got some functionality back on the phone, but still force closes and I cannot save anything to SD (or install apps).
another email account (an exchange server account) that was previously deleted has appeared back set up and working (I have not been able to set this up for a week), it appeared on its own which leads me to think there is a hidden partition on my internal sd, hence I cannot access it. must be something to do with Gingerbread.
Thanks for all your help though.
Click to expand...
Click to collapse
Edit: It just completely crashed again, force closes just about everything that is open, phone functionality is gone (phone icon vanished) as did contacts. freezes for a couple of minutes and then reboots. i may have to throw it at a wall!
I cannot find anything about the gingerbread partition that would cause problems with froyo. damn this thing!!!
Have you tried reformatting your internal SD
Settings>SD card and phone storage>internal SD>Format
http://forum.xda-developers.com/showthread.php?t=845708
You might find it useful.
SCIENTYREAL said:
Have you tried reformatting your internal SD
Settings>SD card and phone storage>internal SD>Format
Click to expand...
Click to collapse
Hi mate,
I have tried that several times, i think there is a hidden partition thanks to Gingerbread.
I would be sure that your internal sd card is screwed but since everything worked fine before gingerbread something else has probably happened. Also your data wont delete and that seems to be the source of the problem. Try to install the lagfix from k13d and see if it had any results. This should reformat all partitions on the internal sd.
Sorry for the long read, this is half rant and half question.
Alright, I got a captivate a long time ago (about a year and 3 months ago), loved it, rooted it and installed cyanogenmod as soon as I got home, changed roms and kernals constantly, did whatever I wanted to do.
About 3 months ago my screen stopped working.. So I take it in and they give me a refurb captivate, looked brand new so I didn't mind. However, when I tried to get into recovery it didn't work, the 3-button-method just wouldn't work at all, period, so I try to get it to work, gets stuck in bootloop.. pretty much every time I try to flash a rom something goes wrong and I get stuck in a bootloop but I can usually get into recovery or download mode because I had CWM.
So I'm on maxq's rom and it's working great for the past 2 months, decide not to mess with kernals or anything, however today I decided to try ICS, load it up, everything's fine, then I realize my soft keys aren't working, search for awhile, can't find anything, finally just manually start looking through the rom pages, and someone said that if you have the problem to just odin back to stock and try again.
I odin back to stock, but now 3 button combo doesn't work.. So more searching, find that I can run the 3e fix by TRusselo, doesn't work because I need root, more searching on how to root without recovery, find "SuperOneClick", root with superoneclick, then run 3e fix, everything is working fine, I check my email and load the ICS files onto SD card, go to restart and go into recovery mode.. Bricked, stuck in a bootloop, won't go to recovery, won't go to download, nothing.
Why the **** was I able to do anything I wanted with my old captivate, but if I even root this one it bricks? And what did I do to even brick it? I only ran the 2 programs and both of them worked flawlessly.
I guess my only option is to usb jig it, but honestly now I'm convinced that the phone is just faulty, I want to run the thing over.
-Pirate said:
So I'm on maxq's rom and it's working great for the past 2 months, decide not to mess with kernals or anything, however today I decided to try ICS, load it up, everything's fine, then I realize my soft keys aren't working, search for awhile, can't find anything, finally just manually start looking through the rom pages, and someone said that if you have the problem to just odin back to stock and try again.
Click to expand...
Click to collapse
If you would have actually searched you would have known it was a bug in the glitch. There are atleast 40 pages about that.
-Pirate said:
I odin back to stock, but now 3 button combo doesn't work.. So more searching, find that I can run the 3e fix by TRusselo, doesn't work because I need root, more searching on how to root without recovery, find "SuperOneClick", root with superoneclick, then run 3e fix, everything is working fine, I check my email and load the ICS files onto SD card, go to restart and go into recovery mode.. Bricked, stuck in a bootloop, won't go to recovery, won't go to download, nothing.
Click to expand...
Click to collapse
If you flashed ICS you should know it takes 2 flashes for it to work first time. Having a jig around is always a good idea as well.
-Pirate said:
Why the **** was I able to do anything I wanted with my old captivate, but if I even root this one it bricks? And what did I do to even brick it? I only ran the 2 programs and both of them worked flawlessly.
Click to expand...
Click to collapse
Stuff doesn't work as intended. Keep in mind everything is still in dev and not all devices are the same. But you should have searched a little more and it would have ran =/
U def don't need a jig. If it's booting it's not bricked. Try removing battery, start Odin, hold down power and down, plug in and put battery in. This should bring u to download mode.
prbassplayer said:
If you would have actually searched you would have known it was a bug in the glitch. There are atleast 40 pages about that.
Click to expand...
Click to collapse
I did start to see a few people with the problem, however many people do not follow up with what fixes their problem, and I did what a few people had said to do.
prbassplayer said:
If you flashed ICS you should know it takes 2 flashes for it to work first time. Having a jig around is always a good idea as well.
Click to expand...
Click to collapse
I should of mentioned that I did flash a few times, 3 total I think, it was getting stuck at boot.
prbassplayer said:
Stuff doesn't work as intended. Keep in mind everything is still in dev and not all devices are the same. But you should have searched a little more and it would have ran =/
Click to expand...
Click to collapse
I understand that **** happens but honestly my old captivate could always get into recover mode and download mode no matter what, it's extremely frustrating that something changed with the newer models. One of my questions was what caused the brick? I did nothing wrong from what I see and it was running perfectly until I tried to restart/boot into recovery.
Oh and mbc663, thanks but download mode doesn't work at all, nor does recovery obviously.
I can't say exactly what you are doing. Best advice I can do Re download your .zips Flash back to stock GB and try again.
-Pirate said:
About 3 months ago my screen stopped working.. So I take it in and they give me a refurb captivate, looked brand new so I didn't mind. However, when I tried to get into recovery it didn't work, the 3-button-method just wouldn't work at all, period, so I try to get it to work, gets stuck in bootloop.. pretty much every time I try to flash a rom something goes wrong and I get stuck in a bootloop but I can usually get into recovery or download mode because I had CWM.
So I'm on maxq's rom and it's working great for the past 2 months, decide not to mess with kernals or anything, however today I decided to try ICS, load it up, everything's fine, then I realize my soft keys aren't working, search for awhile, can't find anything, finally just manually start looking through the rom pages, and someone said that if you have the problem to just odin back to stock and try again.
I odin back to stock, but now 3 button combo doesn't work.. So more searching, find that I can run the 3e fix by TRusselo, doesn't work because I need root, more searching on how to root without recovery, find "SuperOneClick", root with superoneclick, then run 3e fix, everything is working fine, I check my email and load the ICS files onto SD card, go to restart and go into recovery mode.. Bricked, stuck in a bootloop, won't go to recovery, won't go to download, nothing.
Why the **** was I able to do anything I wanted with my old captivate, but if I even root this one it bricks? And what did I do to even brick it? I only ran the 2 programs and both of them worked flawlessly.
I guess my only option is to usb jig it, but honestly now I'm convinced that the phone is just faulty, I want to run the thing over.
Click to expand...
Click to collapse
Last year, I had issues with my original Cap, and got a "new" one. I learned that the bulk of the Caps going out as replacements are referbs. The one I got was a 1008 build, and does not have 3 button recovery. There are minor differences with each and every Cap that's out there. That's why some have issues with ROM's and some don't, some can over clock like crazy, and some can't at all. My guess is you have a 1008 as well, but that really doesn't matter. You just have a different device and as you seem to already have learned.
It sounds like there is more research you need to do. Even though the devices are a bit different, if you are having issues with ROM's loading, then I would say it's more of a procedure issue, than one with your device.
My procedure, is,
Remove SD/Micro SD
Odin1 Click to Stock JF6, and Master Clear(This will erase EVERYTHING)
Root with One-Click Root
Use Sideload Wonder Machine to install ROM Manager, copy update.zip and 3buttonFix to my SD, then reboot into recovery
Once in recovery I install the 3buttonFix, and install my new ROM
For me this has proven to be a very good method versus going from one ROM to another. The Master Clear cleans EVERYTHING off of your SD, so there is no chance for anything to corrupt your new install. Anytime I read a post of a install gone FUBAR, USUALLY a Flash To Stock/Master Clear (FTS/MC) fixes it
Before using Odin 1 Click, check your devices build number!! If it is higher than 1012, I would NOT recommend using 1 click, there is a higher chance of hard brick on the newer devices
Kangi...if you flash a firmware package without bootloaders, you won't have to do the 3 button fix every time. And if you keep a copy of the update.zip on your pc you don't have to even root, let alone bother with side loading ROM manager.
Cezar has a no boots jf6 and after you run that, you can still use master clear in one click.
Sounds like you got one of the refurbs that is missing the SBL. Have you looked at this thread? http://forum.xda-developers.com/showthread.php?t=1129821
I've not had this problem myself but it sounds like that might help. If I remember reading correctly, once this is flashed it should stick as long as you don't flash any other bootloaders on top of it.
Its not missing the sbl. The sbl it has doesn't respond to key combos. Derpa sherpa moment for samsung I guess?
Rofl yeah...if it was missing the sbl it would be fuggin bricked!
studacris said:
Kangi...if you flash a firmware package without bootloaders, you won't have to do the 3 button fix every time. And if you keep a copy of the update.zip on your pc you don't have to even root, let alone bother with side loading ROM manager.
Cezar has a no boots jf6 and after you run that, you can still use master clear in one click.
Click to expand...
Click to collapse
I know, thanks. I'm such a creature of habit, I started doing it like this a bit over a year ago, and has worked flawlessly for me(just jinxed myself!) so I never saw a reason to "fix what aint broke".
I'll take a look at Cezar's thanks!
Yeah, missing SBL was a poor choice of words. My bad.
kangi26 said:
Last year, I had issues with my original Cap, and got a "new" one. I learned that the bulk of the Caps going out as replacements are referbs. The one I got was a 1008 build, and does not have 3 button recovery. There are minor differences with each and every Cap that's out there. That's why some have issues with ROM's and some don't, some can over clock like crazy, and some can't at all. My guess is you have a 1008 as well, but that really doesn't matter. You just have a different device and as you seem to already have learned.
It sounds like there is more research you need to do. Even though the devices are a bit different, if you are having issues with ROM's loading, then I would say it's more of a procedure issue, than one with your device.
My procedure, is,
Remove SD/Micro SD
Odin1 Click to Stock JF6, and Master Clear(This will erase EVERYTHING)
Root with One-Click Root
Use Sideload Wonder Machine to install ROM Manager, copy update.zip and 3buttonFix to my SD, then reboot into recovery
Once in recovery I install the 3buttonFix, and install my new ROM
For me this has proven to be a very good method versus going from one ROM to another. The Master Clear cleans EVERYTHING off of your SD, so there is no chance for anything to corrupt your new install. Anytime I read a post of a install gone FUBAR, USUALLY a Flash To Stock/Master Clear (FTS/MC) fixes it
Before using Odin 1 Click, check your devices build number!! If it is higher than 1012, I would NOT recommend using 1 click, there is a higher chance of hard brick on the newer devices
Click to expand...
Click to collapse
I didn't think anyone else was going to reply to this thread, whoops.
Thank you for helping me, but I'm still having trouble.
Rom manager doesn't show up in Market, Sideload wonder machine tells me [INSTALL FAILED OLDER SDK] with any apk of Rom manager I find.
kangi26 said:
3buttonFix to my SD, then reboot into recovery
Click to expand...
Click to collapse
How do you reboot into recovery when 3buttonfix hasn't been applied yet?
This sucks and is extremely frustrating, I feel like my captivate is just trolling me.
-Pirate said:
I didn't think anyone else was going to reply to this thread, whoops.
Thank you for helping me, but I'm still having trouble.
Rom manager doesn't show up in Market, Sideload wonder machine tells me [INSTALL FAILED OLDER SDK] with any apk of Rom manager I find.
How do you reboot into recovery when 3buttonfix hasn't been applied yet?
This sucks and is extremely frustrating, I feel like my captivate is just trolling me.
Click to expand...
Click to collapse
When I get home later tonight I'll link you everything you'll need. Again, VERY important, what is your build number? If it's 1012 or higher, don't use Odin 1 click
Sent from a autonomous device
kangi26 said:
When I get home later tonight I'll link you everything you'll need. Again, VERY important, what is your build number? If it's 1012 or higher, don't use Odin 1 click
Sent from a autonomous device
Click to expand...
Click to collapse
Ok, finally got it working, I did exactly what you said, I found the rom manager 3.00.002 or whatever and that worked with sideloader, it took some messing around with but I'm running ICS now, thank you so much man, you've helped me so much, and now I can change roms and keep up to date without worrying about constantly soft-bricking.
As for my build number, I'm not sure, the only thing I see under build number in settings is: "IML74k"
-Pirate said:
Ok, finally got it working, I did exactly what you said, I found the rom manager 3.00.002 or whatever and that worked with sideloader, it took some messing around with but I'm running ICS now, thank you so much man, you've helped me so much, and now I can change roms and keep up to date without worrying about constantly soft-bricking.
As for my build number, I'm not sure, the only thing I see under build number in settings is: "IML74k"
Click to expand...
Click to collapse
The build number is actually under your battery, and looks like 10.06, 10.07, 10.08 and so on. It is the production date
Edit** And as a side note, do NOT try to use the 3buttonFix with a GB ROM, it WILL brick your phone in a really bad way. ONLY use it with 2.1 or 2.2
kangi26 said:
The build number is actually under your battery, and looks like 10.06, 10.07, 10.08 and so on. It is the production date
Edit** And as a side note, do NOT try to use the 3buttonFix with a GB ROM, it WILL brick your phone in a really bad way. ONLY use it with 2.1 or 2.2
Click to expand...
Click to collapse
Is it weird that I don't have a build number? It seems I can't post pictures without a few more posts, maybe this will work: deleted
And thanks for the warning on the 3buttonfix, I'm going to have to read more about bootloaders though, I don't understand what you and studacris were talking about earlier in the thread, haha.
-Pirate said:
Is it weird that I don't have a build number? It seems I can't post pictures without a few more posts, maybe this will work: imgurDOTcom/26sXGl.jpg
And thanks for the warning on the 3buttonfix, I'm going to have to read more about bootloaders though, I don't understand what you and studacris were talking about earlier in the thread, haha.
Click to expand...
Click to collapse
I havent seen that before, there doesnt seem to be a build#
Might want to pull that photo, it's not too good having your IMEI number publicly displayed
kangi26 said:
I havent seen that before, there doesnt seem to be a build#
Might want to pull that photo, it's not too good having your IMEI number publicly displayed
Click to expand...
Click to collapse
Maybe because it's a refurb? and whoops didn't think about that.
-Pirate said:
Maybe because it's a refurb? and whoops didn't think about that.
Click to expand...
Click to collapse
I'm not sure why, mine is a referb, and I have a sticker with mine on it. Ooh well, it is what it is
Sent from a autonomous device
I know this is a common thing, as I searched before coming to the conclusion that I had to create my own thread about this topic. However, everyone says to re-flash to stock, which is what caused this problem for me. I had a huge error with the phone, and after 2 weeks of flashing, I am able to get it to this stage where it will boot up, but after booting up, the screen turns black, but the bottom buttons light up, and can be pressed, but no action.
I can access recovery and download mode. Odin recognizes my phone. I can charge with phone off (the battery image shows it charging.)
Here is the thread where I discussed my issues if you care to learn more about my issues (it was a dbdata error).
androidforums.com/samsung-galaxy-s/567335-factory-reset-wont-fix-galaxy-s-infinite-boot-mode.html
Anyways, now there is no errors (no red lines during recovery mode). But I have no idea what to do.
No one has a clue? This really sucks, I've spent so much time trying to fix it when all along it can't really be fixed it seems.
Try flashin to Stock i897ucKK4.... http://forum.xda-developers.com/showthread.php?p=18370912
Sent from my SAMSUNG-SGH-I777 using xda premium
4-2ndtwin said:
Try flashin to Stock i897ucKK4.... http://forum.xda-developers.com/showthread.php?p=18370912
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
I've tried that. With that rom it boot loops and gives me a dbdata error.
Edit. Just tried again and after the att screen during boot up it gives me different variations of this screened like a grainy type of image. I snapped a pic below. I tried going into recovery and it gave me the same image on the screen.
Imgur.com/qyo5P.jpg
U need to flash the KK4 WITH the GB Bootloaders.
Sent from my SAMSUNG-SGH-I777 using xda premium
4-2ndtwin said:
U need to flash the KK4 WITH the GB Bootloaders.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
(I've tried that as well, and I tried it again)
After flashing it booted in recovery, and tried to do the wipes.
Failed to mount /sdcard (I/O error) -- (There's no SD card inside, so that's probably why)
E:copy_dbdata_media: can't mount /sdcard your storage not prepared yet, please use UI menu format and reboot actions.
--Wiping data
Formatting /data...
Formatting/dbdata...
Formatting /cache...
Data wipe failed.
Then I tried a wipe data/factory reset. And this time it said Data wipe completed.
Then when I rebooted it said
Failed to mount /data (invalid argument)
And then it said another error but it was in yellow, so I didn't really catch it.
And it boot loops.
[Thank you for attempting to help me by the way!]
Do a search in the Q & A forum for the dbdata error that you are getting. This has happened before to several persons and i do remember that there were a few threads on this already.
U probably are going to have to flash a stock firmware (that is contained in a .tar file) through regular Odin3 v1.83 (or similar). This Odin is Not a "one click". Make sure the .tar file for the stock contains the dbdata.rfs file and also don't use the pit file. See if that works. --- The i897ucKF1 in the Dev forum would be a firmware that comes to mind that has all u need. Quick search should lead u to that one.
If successful, u should be able to flash up to KK4 afterwards or go to Dev Roms if u want.
4-2ndtwin said:
Do a search in the Q & A forum for the dbdata error that you are getting. This has happened before to several persons and i do remember that there were a few threads on this already.
U probably are going to have to flash a stock firmware (that is contained in a .tar file) through regular Odin3 v1.83 (or similar). This Odin is Not a "one click". Make sure the .tar file for the stock contains the dbdata.rfs file and also don't use the pit file. See if that works. --- The i897ucKF1 in the Dev forum would be a firmware that comes to mind that has all u need. Quick search should lead u to that one.
If successful, u should be able to flash up to KK4 afterwards or go to Dev Roms if u want.
Click to expand...
Click to collapse
I've tried 3 different roms with Odin3 v1.85. (that contain dbdata.rfs in the tar)
Maybe with that rom I'll have better luck. I searched for that rom at samfirmware and downloaded it. I searched in the dev forum, and all I got was an odin one click for that rom, and you said to do the regular version.
I flashed it, and it gave me the same error as before. With the data wipe failed and other errors. Then when it boots, it boot loops only the att logo.
Att logo, darkness for a second. Then repeat.
Also. I've done numerous searches for the words I'm getting, and every one says to flash back to the kk4 stock rom, but that's what causes the problems for me.
Is there anyone that can help at this point?
Is it possible that I have messed up partitions on the internal SD card? I found a way to fix that, but its for the HTC incredible. Any ideas on a captivate version of this thread?
forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/#entry56396
albokid2468 said:
Is there anyone that can help at this point?
Is it possible that I have messed up partitions on the internal SD card? I found a way to fix that, but its for the HTC incredible. Any ideas on a captivate version of this thread?
forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/#entry56396
Click to expand...
Click to collapse
Have you tried this one yet? http://forum.xda-developers.com/showthread.php?t=731989
This is probably the best restore rom I know of, it will flash eclair bootloaders so you will have to reflash gingerbread bootloaders before you flash any current roms.
If this doesn't do it then it sounds like you may have a bad spot in the memory module itself, possibly a bad transistor in the circuit. You may need some advanced help from a technician, I don't know if any of these jtag guys have advanced diagnostics but it wouldn't hurt to check it out.
As a last resort, you may have to send it in to Samsung.
crt60 said:
Have you tried this one yet? http://forum.xda-developers.com/showthread.php?t=731989
This is probably the best restore rom I know of, it will flash eclair bootloaders so you will have to reflash gingerbread bootloaders before you flash any current roms.
If this doesn't do it then it sounds like you may have a bad spot in the memory module itself, possibly a bad transistor in the circuit. You may need some advanced help from a technician, I don't know if any of these jtag guys have advanced diagnostics but it wouldn't hurt to check it out.
As a last resort, you may have to send it in to Samsung.
Click to expand...
Click to collapse
I've tried that one. That is one of the few where it will give no errors, however it boots up to a black screen. I believe that was the state I was in when I started this thread, with that rom.
Is the memory module or the transistor in the circuit located on the main board of the device. I was thinking of buying a logic board (mother board) and replacing it with a new one.
Although at this point, I got the Galaxy S3 so this phone isn't really a necessity at this point.
albokid2468 said:
I've tried that one. That is one of the few where it will give no errors, however it boots up to a black screen. I believe that was the state I was in when I started this thread, with that rom.
Is the memory module or the transistor in the circuit located on the main board of the device. I was thinking of buying a logic board (mother board) and replacing it with a new one.
Although at this point, I got the Galaxy S3 so this phone isn't really a necessity at this point.
Click to expand...
Click to collapse
Hi bro, have you solved your problem? Eager to hear from you cause I am having the excat same trouble.....
qaler2010 said:
Hi bro, have you solved your problem? Eager to hear from you cause I am having the excat same trouble.....
Click to expand...
Click to collapse
Look here: http://forum.xda-developers.com/showthread.php?p=39614278#post39614278
BWolf56 said:
Look here: http://forum.xda-developers.com/showthread.php?p=39614278#post39614278
Click to expand...
Click to collapse
Thks for your reply
I am not new to captivate, I have already had it for nearly 2 years, and everything including odin ways that used to work now doesn't....
So strange, yesterday it was ok as usual ,but when I got up this morning and it couldn't light up the screen no matter what physical button I hit. So I did flashing but it results in nothing.
Use I897UCJF6-final-OCD-REV0 and my phone can boot up but screen comes black during boot animation
Use 3FileKF1NOBOOT or JF6_secure, my phone just gets stuck on the first boot screen
Use custom recovery, then (E:failed to mount /data (file exists) E:delete_data_files: can't mount /data your storage not prepared yet, please use ui menu for format and reboot actions)
So sad now...I haven't backed up my data and for now it looks like I could never get it back...
qaler2010 said:
Thks for your reply
I am not new to captivate, I have already had it for nearly 2 years, and everything including odin ways that used to work now doesn't....
So strange, yesterday it was ok as usual ,but when I got up this morning and it couldn't light up the screen no matter what physical button I hit. So I did flashing but it results in nothing.
Use I897UCJF6-final-OCD-REV0 and my phone can boot up but screen comes black during boot animation
Use 3FileKF1NOBOOT or JF6_secure, my phone just gets stuck on the first boot screen
Use custom recovery, then (E:failed to mount /data (file exists) E:delete_data_files: can't mount /data your storage not prepared yet, please use ui menu for format and reboot actions)
So sad now...I haven't backed up my data and for now it looks like I could never get it back...
Click to expand...
Click to collapse
Try using Odin KK4 with bootloaders. JF6 is really outdated.
BWolf56 said:
Try using Odin KK4 with bootloaders. JF6 is really outdated.
Click to expand...
Click to collapse
Thanks again for your quick reply.
//Now I have only found one kk4 with bootloader download link in hotfile.com, which is currently not banned in my country...
So would you please be that kind to post another download link like in mediafire, dropbox or googled docs?
But I don't really think it is the problem of being outdated or not, JF6 and that I said above worked fine before...
FYI, I was using Slim 4.2.2 build 2.5 when I got the trouble, maybe there is something special I don't know when downgrading to GB?
Regards!
--------
Found the link:http://www.mediafire.com/?zqpip6uac4n7ov7
qaler2010 said:
Thanks again for your quick reply.
Now I have only found one kk4 with bootloader download link in hotfile.com, which is currently not banned in my country...
So would you please be that kind to post another download link like in mediafire, dropbox or googled docs?
But I don't really think it is the problem of being outdated or not, JF6 and that I said above worked fine before...
FYI, I wasing using Slim 4.2.2 build 2.5 when I got the trouble, maybe there is something special I don't know when downgrading to GB?
Regards!
Click to expand...
Click to collapse
JF6 is Froyo, not GB. Therefor, you're flashing the wrong bootloaders. You need the GB bootloaders, hence why I'm telling you to use KK4.
As for links, the only one I have is: http://hotfile.com/dl/137865417/4bc...S_Bootloaders_Re-partition_Full_Wipe.zip.html - Which is hotfile.com and I can't upload it to my db at work.
BWolf56 said:
JF6 is Froyo, not GB. Therefor, you're flashing the wrong bootloaders. You need the GB bootloaders, hence why I'm telling you to use KK4.
As for links, the only one I have is: http://hotfile.com/dl/137865417/4bc...S_Bootloaders_Re-partition_Full_Wipe.zip.html - Which is hotfile.com and I can't upload it to my db at work.
Click to expand...
Click to collapse
Pretty sure not the issue of bad flash after odining KK4...
I start to believe corrupted, or even worse, dead internal storage causes all the hell....
qaler2010 said:
Pretty sure not the issue of bad flash after odining KK4...
I start to believe corrupted, or even worse, dead internal storage causes all the hell....
Click to expand...
Click to collapse
Sorry but this isn't very clear.. Did you manage to flash Odin KK4 with bootloaders? Did it say complete and reboot the phone? If so, what exactly happened and what exactly did you do?