Database Info

[Q] What Have I Done?!!?

Hi. This is my first time posting. I apologize in advance, im going to come across as a noob.
I got tired of waiting for google to get 2.3 to the N1 users. I decided it was time to unlock and root my phone, after all thats what it was designed for. Up until this point the phone was stock with all updates. I thought one touch root no longer worked. I dont know why i thought this. I used a guide to work through it. I cannot post links otherwise i would. ilikemygooglephone . com is where it came from
Everything worked according to this guide until I completed it and powered my phone on for the first time. I thought I was going to see a stock wiped nexus one...Instead I got shafted.
The phone reboots randomly. It happens quickly and unpredictably.
Notification bar will never slide down. If i try to the phone lags but never shows notifications.
No 3g
No wifi
The phone says I have no service (selected network tmobile unavailable) although I can still make and receive calls.
The sd card will not mount. I cannot access it on the phone. When pluggen into my laptop the phone will charge but wont give me the option to access the sd card.
At times the graphics are buggy and dont operate properly
There are probably other problems that i am forgetting but I think this says enough. Since i cannot access the SDcard I really dont know what to do.
Im sorry if this thread is in the wrong place or happens to be a previously answered question. I just really like my phone and I hope its not wasted. Can someone tell me what I did wrong or how i can get this right.

YEAH i noobed it.
I freaked out on the above issue for about 5 hours. Now I believe i have everything back to normal. My problem was i didnt load the proper superboot. Once i found the FRG83 one and redid the process using that instead it worked fine. Either i was using the wrong superboot or i had a corrupted download somehow.
Feels good to figure it out on my own though....i feel...less noob.....NAH

Any advice for an Android beginner?

I just got the Captivate about a month ago. Had a regular phone for about a year, touch screen went out, bought a replacement digitizer but knew it was a temporary fix anyway and wanted a new phone. Convinced the maternal unit to use her contract extension to get me a new phone, and snagged the Captivate for $30 from RadioShack. My first Android phone, and I have to say I'm horribly disappointed, but I guess I'm doing something wrong here.
First two or three weeks, my mom had the phone and got to play around with it for a while. Wasn't until the 29th that I got the phone, and I just played around with it for a week and got all the apps I deemed useful and worthwhile. Eventually realized I couldn't use Flash in the browser, nor Skype, etc., without upgrading to 2.2.
So, I went through the tutorial Samsung provided, watched videos on Youtube just to be sure, but followed everything Samsung's tutorial said word for word. ... only for my phone to end up completely screwed up. Gallery, Browser, Music Player, Video Player, and many other default applications were missing. Now I'm smart enough with technology to think, okay, something's wrong. I knew about the factory reset, so I went to go to settings to do that, and realized. ... oh wait, the Settings menu is also missing. Wonderful. There was no "Settings" button in the Applications list, and if I tried getting to it from the menu button, it simply did nothing at all.
Found Odin, flashed back to 2.1, and then factory reset and got rid of every application I had and etc., so that absolutely nothing was on it, basically a stock phone. Tried upgrading again fresh, still following the instructions very closely. Same problem occurred, and I was pissed. Gave up on 2.2, tried flashing back to 2.1 /again/ with Odin, only for my phone to decide it didn't want to enter download mode anymore. Forced it using 'adb reboot download', but alas, it locked up in the middle of flashing back to 2.1 and wouldn't do anything. I waited about 30 minutes to see if it'd resume the flashing process at all, but nothing, so I regrettably had to disconnect the USB cable and hard brick the phone (wouldn't turn on or anything).
Still under warranty, so I replaced it from RadioShack, and now have a new Captivate. Went ahead and installed all the applications I needed, used the Sideload Wonder Machine to install a few third-party applications, had no problem doing that for a while. Didn't bother attempting to upgrade. However, my computer got a trojan and deleted the MBR. Repaired using the XP boot disc, but it meant I was back on SP2. After installing every last one of the damn updates all over again, I decided to check up on some new applications to install via sideloading.
Hooked up my phone, it detected all the new hardware again since the drivers seemingly were also lost amongst everything else during the repair, only for it to encounter an error on the "Samsung Android Composite ADB Interface". So, I uninstalled the drivers, tried installing them manually. Hooked up the phone, but it still wanted to try to install that one driver and failed. I've restarted my computer, uninstalled the drivers, attempted manually installing them through device manager, you name it. Still can't get it to work -- it keeps having a fatal error every time. However, it's only when my phone has USB Debugging on. Installs every single driver perfectly fine when it's off, in MTP/Mass Storage/Kies mode. Just has a "fatal error" in USB Debugging on that one driver.
tl;dr, the drivers are broken on my computer and I can't fix them despite actually /not/ being computer illiterate. And, I kind of still want 2.2, but apparently the stock 2.2 update is a pain in the rear end and I no longer have a warranty through RadioShack now, so I can't risk bricking my phone due to a faulty update process. Any suggestions?

err, the only thing you should have needed to do was install the latest version of Kies, plugged the phone in, it would have prompted you to do the update. It's quite painless..

Edit: Sorry irrelevant

sw411 said:
err, the only thing you should have needed to do was install the latest version of Kies, plugged the phone in, it would have prompted you to do the update. It's quite painless..
Click to expand...
Click to collapse
At the time I tried, Kies itself didn't support the Captivate. Only Kies mini. And in order to do that upgrade, I had to install the drivers, then put the phone into download mode to install more drivers for some odd reason, restart the phone (taking out the battery and putting it back in), then hook it up. Kies mini wouldn't detect the phone for several tries at first, finally got it about the 10th time in. Then go to the "Upgrade phone" link, and yeah. I followed the instructions from Samsung's official SGH-i897 Froyo upgrade guide.
I did EXACTLY as the instructions say, down to the wire. Still ended up both times with all those applications missing and the settings panel missing, unable to do a factory reset without flashing back to 2.1 first.

Install z4root and root phone
Install rom manager
Flash clockwordmod recovery from rom manager
Choose a 2.2 rom from the forums
Download and copy to SD card
Install via rom manager
????????
Profit
Hope this helps. Btw I reccomend firefly or serendipity for the rom
Sent from my Captivate running CyanogenMod7 using XDA Premium App

brendanmurphy said:
Install z4root and root phone
Install rom manager
Flash clockwordmod recovery from rom manager
Choose a 2.2 rom from the forums
Download and copy to SD card
Install via rom manager
????????
Profit
Hope this helps. Btw I reccomend firefly or serendipity for the rom
Sent from my Captivate running CyanogenMod7 using XDA Premium App
Click to expand...
Click to collapse
Only downside to rooting the phone is the voided warranty. I don't entirely know what I'm doing there when it comes to flashing, and if I manage to do something wrong and brick the phone again, I'm completely wiped. I don't have the money to replace the phone at all. I have no job. ._. Only reason I got the phone was because I managed to get some spare money fixing up a friend's computer, and the maternal unit's contract extension was available. I'm not paying for the phone, still my parents. Damn economy in this state is so broken, and I'm screwed over worse since I have no diploma.
However, I was looking into info on the roms, and while I was tempted to try out CM7 for the fact it was 2.3, I actually considered getting Paragon RC6 from what I had read. Just decided not to because I can't replace the phone if I screwed up. In the slim chance I do opt to risk not having a phone at all if I do something wrong, would you say Paragon's worthwhile or would it be better to go with Serendipity? I do like TouchWiz, and Wifi access is a must (200 MB plan isn't going to cover it with how I use data; I'm frequently using Wifi in as many places as is possible), but I'm pretty sure both of those are fine there. Just not really sure which would be better overall, performance-wise.
I can't do either of them right now anyway until I figure out why the drivers aren't installing. So that's my first issue.

Don't worry about bricking I almost guarantee you will brick your phone once. But that is what Odin is for and it's almost impossible to hard brick a phone these days. Just install paragon with the instructions I gave its really fool proof these days to install rom. You will learn by trying if you mess up so be it that's what xda is here for to help.
Drop me a pm anytime if you need help
Sent from my Captivate running CyanogenMod7 using XDA Premium App

brendanmurphy said:
Don't worry about bricking I almost guarantee you will brick your phone once. But that is what Odin is for and it's almost impossible to hard brick a phone these days. Just install paragon with the instructions I gave its really fool proof these days to install rom. You will learn by trying if you mess up so be it that's what xda is here for to help.
Drop me a pm anytime if you need help
Sent from my Captivate running CyanogenMod7 using XDA Premium App
Click to expand...
Click to collapse
Well. Despite it being almost impossible, I've managed it once already within the first month of having one. Kind of why I'm a bit skittish about actually going through with it. I'm definitely all about modding and customizing things to your liking, but not having the funds to fall back on if I /do/ screw up bigtime again, yeeeeah.
After looking at Firefly and Serendipity thoroughly, though, I'm impressed. It's a tough choice between the three (Paragon, Serendipity, and Firefly). I'm leaning towards Serendipity now though after watching a video just to see the interface. Kinda not a huge fan of the GB launcher -- I liked the side-scrolling app launcher more, honestly -- but that's not a big deal.
So, let's see if I've got the details down right before I try anything. Search z4root in Market, install. Subsequently get Rom Manager, install it. Flash ClockworkMod (via Rom Manager). Pick a 2.2 rom (which will be a tough choice), and download it to my microSD card to put in the phone. Install said rom (via Rom Manager). And then, voila, it's done.
Did I miss anything, or am I actually following instructions right here?
Edit: Nope, can't find z4root in the Market anyways. Means I'd have to Sideload it, and until I get this driver issue solved, that's not gonna work either. That's gonna be the first thing necessary to fix since it also means I can't use Odin if I do anything wrong... Downloading Serendipity now though, so if I can get that fixed, I may go ahead and try this out after I get some sleep. But since I'm nocturnal, time for some rest. Hoping for some tips or pointers when I get back on. Definitely looking forward to good experiences with XDA and my Android phone.

Yea those are the exact steps its really simple. http://forum.xda-developers.com/showthread.php?t=944418 try this it will install drivers for you ans sideload apps. This is a useful tool
Sent from my Captivate running CyanogenMod7 using XDA Premium App

The.Se7enth said:
Only downside to rooting the phone is the voided warranty.
Click to expand...
Click to collapse
Quick question. Did you purchase the insurance through AT&T for the phone? If so, you will most likely always be able to get it replaced even if it's been rooted. It's just as simple as calling the help line, and saying that you have no idea what happened, and it won't work now. Of course that is worst case scenario
From my experience, the Captivate is a pretty difficult phone to hard brick compared to some others. For a beginner, all of this can be somewhat overwhelming, we've all been there. But once you get the hang of the whole process, you'll be good to go!

Yeah I've done that once already. Just called in and told them that it seems like a software problem and they replaced it no charge.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

Beginner help....
AT&T warranty is for 1 year on new phones, 90 days on phones you purchase as refurbished. (30 day "I just don't like THIS phone" replacement/return in both cases.) If Radio Shack will not replace the phone, AT&T should swap. If neither is willing to help, Samsung will honor their 1 year warranty, but it requires shipping back to Samsung.
Your situation sounds like your Windows PC is the problem. A complete reinstall of Windows & apps (not just a quick MBR repair / install over top of existing stuff) may be your best bet if you can't use a different machine.
Kies Mini should upgrade your phone to 2.2 painlessly - without you having to do anything but plug it in and click the on screen button.

Also if you root and need to return it just flash back to stock which will take away root and at$t is none the wiser, most likely

peypey008 said:
Quick question. Did you purchase the insurance through AT&T for the phone? If so, you will most likely always be able to get it replaced even if it's been rooted. It's just as simple as calling the help line, and saying that you have no idea what happened, and it won't work now. Of course that is worst case scenario
From my experience, the Captivate is a pretty difficult phone to hard brick compared to some others. For a beginner, all of this can be somewhat overwhelming, we've all been there. But once you get the hang of the whole process, you'll be good to go!
Click to expand...
Click to collapse
Nope. Don't feel their insurance policies are worth it. You spend more money on the insurance policy in total, even if it's month-to-month, than you would on a brand new contractless phone. Besides, I had only made $120 from fixing up three ancient computers (so ancient they actually had ISA slots and DIMM SD-RAM memory -- one was even a Pentium II), and only had $50 by the time I bought the phone which was a couple months later. My $50 went towards the phone and a pack of screen protectors, while my mom covered the upgrade fee. Couldn't afford the insurance policy even if we wanted to.
But I do greatly appreciate the encouragement. I'll give it a go in a bit, and try out flashing Serendipity. I'll follow the official instructions from their own website though, because I read this on their FAQ:
"Never use ROM Manager. EVER, EVER, EVER, EVER, EVER!"
pouelle said:
AT&T warranty is for 1 year on new phones, 90 days on phones you purchase as refurbished. (30 day "I just don't like THIS phone" replacement/return in both cases.) If Radio Shack will not replace the phone, AT&T should swap. If neither is willing to help, Samsung will honor their 1 year warranty, but it requires shipping back to Samsung.
Your situation sounds like your Windows PC is the problem. A complete reinstall of Windows & apps (not just a quick MBR repair / install over top of existing stuff) may be your best bet if you can't use a different machine.
Kies Mini should upgrade your phone to 2.2 painlessly - without you having to do anything but plug it in and click the on screen button.
Click to expand...
Click to collapse
RadioShack replaced the phone the first time, but the manager there said after replacing it once, the warranty was thus void. I'm not sure if profanity is allowed here, but you can figure out which word I wanted to reply to him. It's eight letters long, starts with bull.
I've read posts on AT&T forums saying if the phone's bricked or can't be repaired by user methods though, especially if it's rooted, that they won't honor the warranty at all and will consider it user error and that you're out of luck. Even people who tried to upgrade to 2.2 stock had issues with that. But I dunno.
Anyways, my machine works perfectly for everything else. Before the repair, when I tried to upgrade? It was a fresh install. I had just reformatted it because it was performing sluggish before and I decided I wanted a single-boot installation instead of having my old dual-boot of Windows 7 and XP. It's now just XP for the time being, seeing as how the hardware's limited and I want to get the best out of it for gaming (I can run 7 with ease, but it uses more resources than XP, thus games don't run as well).
I realize earlier I may have come off as implying the upgrade to 2.2 process was difficult. I don't mean it was "difficult" by any means necessary. It was simply a plug the phone in, let all the drivers install, unhook and put in download mode, hook up again for more drivers. Restart phone, start up kies, hook up phone, and click "Upgrade phone" button. Accept the terms of service or whatever, and wait. Upgrade starts, phone flips into download mode on it's own, restarts a couple times, and voila, you're on 2.2. I thought it was a piece of cake. My issue is that regardless of how easy it was, it still ended up rather broken because all those applications were missing, on top of the fact the Settings panel was also gone, leaving me unable to perform a factory reset.
I have one last question. If I do somehow manage to get these drivers to work again (without reformatting, which I don't have the time to do), should I have the SIM card out while flashing the ROM? I'm wondering, subconsciously, if somehow that may have had something to do with the upgrade to 2.2 screwing up so bad. I had the SIM card in, with all my applications installed at first. Second time, no apps or anything were installed, but the SIM card was still in.
Edit: Well aware of most forums having a "do not double post" rule, as much as I want to bump this thread with an update on the issue. But, I've restarted my computer, tried a different USB cable, uninstalled and reinstalled the drivers from numerous different sources, and still the same "fatal error" issue on "Samsung Android ADB Composite Interface". I simply cannot get that to install whatsoever, and without it, the phone isn't detected as being hooked up even by SWM, much less anything else. Seriously, what do I do? I'm not reformatting my computer, because I simply see no reason for it, but I have no other computer I can use. How do I get these drivers to install properly like they did before?

The.Se7enth said:
At the time I tried, Kies itself didn't support the Captivate. Only Kies mini. And in order to do that upgrade, I had to install the drivers, then put the phone into download mode to install more drivers for some odd reason, restart the phone (taking out the battery and putting it back in), then hook it up. Kies mini wouldn't detect the phone for several tries at first, finally got it about the 10th time in. Then go to the "Upgrade phone" link, and yeah. I followed the instructions from Samsung's official SGH-i897 Froyo upgrade guide.
I did EXACTLY as the instructions say, down to the wire. Still ended up both times with all those applications missing and the settings panel missing, unable to do a factory reset without flashing back to 2.1 first.
Click to expand...
Click to collapse
Fail, Kies Mini works from Kies mode on the phone. It puts the phone into download mode when you start the upgrade from Kies Mini.
Just saying...

The.Se7enth said:
Nope. Don't feel their insurance policies are worth it. You spend more money on the insurance policy in total, even if it's month-to-month, than you would on a brand new contractless phone. Besides, I had only made $120 from fixing up three ancient computers (so ancient they actually had ISA slots and DIMM SD-RAM memory -- one was even a Pentium II), and only had $50 by the time I bought the phone which was a couple months later. My $50 went towards the phone and a pack of screen protectors, while my mom covered the upgrade fee. Couldn't afford the insurance policy even if we wanted to.
But I do greatly appreciate the encouragement. I'll give it a go in a bit, and try out flashing Serendipity. I'll follow the official instructions from their own website though, because I read this on their FAQ:
"Never use ROM Manager. EVER, EVER, EVER, EVER, EVER!"
RadioShack replaced the phone the first time, but the manager there said after replacing it once, the warranty was thus void. I'm not sure if profanity is allowed here, but you can figure out which word I wanted to reply to him. It's eight letters long, starts with bull.
I've read posts on AT&T forums saying if the phone's bricked or can't be repaired by user methods though, especially if it's rooted, that they won't honor the warranty at all and will consider it user error and that you're out of luck. Even people who tried to upgrade to 2.2 stock had issues with that. But I dunno.
Anyways, my machine works perfectly for everything else. Before the repair, when I tried to upgrade? It was a fresh install. I had just reformatted it because it was performing sluggish before and I decided I wanted a single-boot installation instead of having my old dual-boot of Windows 7 and XP. It's now just XP for the time being, seeing as how the hardware's limited and I want to get the best out of it for gaming (I can run 7 with ease, but it uses more resources than XP, thus games don't run as well).
I realize earlier I may have come off as implying the upgrade to 2.2 process was difficult. I don't mean it was "difficult" by any means necessary. It was simply a plug the phone in, let all the drivers install, unhook and put in download mode, hook up again for more drivers. Restart phone, start up kies, hook up phone, and click "Upgrade phone" button. Accept the terms of service or whatever, and wait. Upgrade starts, phone flips into download mode on it's own, restarts a couple times, and voila, you're on 2.2. I thought it was a piece of cake. My issue is that regardless of how easy it was, it still ended up rather broken because all those applications were missing, on top of the fact the Settings panel was also gone, leaving me unable to perform a factory reset.
I have one last question. If I do somehow manage to get these drivers to work again (without reformatting, which I don't have the time to do), should I have the SIM card out while flashing the ROM? I'm wondering, subconsciously, if somehow that may have had something to do with the upgrade to 2.2 screwing up so bad. I had the SIM card in, with all my applications installed at first. Second time, no apps or anything were installed, but the SIM card was still in.
Edit: Well aware of most forums having a "do not double post" rule, as much as I want to bump this thread with an update on the issue. But, I've restarted my computer, tried a different USB cable, uninstalled and reinstalled the drivers from numerous different sources, and still the same "fatal error" issue on "Samsung Android ADB Composite Interface". I simply cannot get that to install whatsoever, and without it, the phone isn't detected as being hooked up even by SWM, much less anything else. Seriously, what do I do? I'm not reformatting my computer, because I simply see no reason for it, but I have no other computer I can use. How do I get these drivers to install properly like they did before?
Click to expand...
Click to collapse
Yea once you have serendipity installed don't use rom manager but for initial install your fine
Sent from my Captivate running CyanogenMod7 using XDA Premium App

cappysw10 said:
Fail, Kies Mini works from Kies mode on the phone. It puts the phone into download mode when you start the upgrade from Kies Mini.
Just saying...
Click to expand...
Click to collapse
You can "say" all you want, my good sir, but google the instructions. They tell you clearly to put the phone into download mode TO FINISH INSTALLING DRIVERS. You don't start up Kies mini until after all the drivers are installed, at which point you hook up the phone with USB Debugging, not Kies mode. I appreciate your willingness to help, but be sure to read everything I say before you correct me. I'm not that slow. I read instructions thoroughly and I've read quite a lot of posts on these forums. I work with computers regularly -- just not Android. The issue had nothing to do with that anyway, so that doesn't even matter.
brendanmurphy said:
Yea once you have serendipity installed don't use rom manager but for initial install your fine
Sent from my Captivate running CyanogenMod7 using XDA Premium App
Click to expand...
Click to collapse
I'm sure it's possible, and I don't mean to come off disrespectful, but I'm just gonna go with the instructions on their website. Just seems a safer route to install a ROM by the creator's instructions, you know? Only thing I'm not sure about is what they mean by "Flash it in 2e recovery (twice)." on ClockworkMod.
The.Se7enth said:
I have one last question. If I do somehow manage to get these drivers to work again (without reformatting, which I don't have the time to do), should I have the SIM card out while flashing the ROM? I'm wondering, subconsciously, if somehow that may have had something to do with the upgrade to 2.2 screwing up so bad. I had the SIM card in, with all my applications installed at first. Second time, no apps or anything were installed, but the SIM card was still in.
Edit: Well aware of most forums having a "do not double post" rule, as much as I want to bump this thread with an update on the issue. But, I've restarted my computer, tried a different USB cable, uninstalled and reinstalled the drivers from numerous different sources, and still the same "fatal error" issue on "Samsung Android ADB Composite Interface". I simply cannot get that to install whatsoever, and without it, the phone isn't detected as being hooked up even by SWM, much less anything else. Seriously, what do I do? I'm not reformatting my computer, because I simply see no reason for it, but I have no other computer I can use. How do I get these drivers to install properly like they did before?
Click to expand...
Click to collapse
These two are still my top questions now. Is it a good idea to have the SIM card out during the upgrade process, and not put it back in until after the update is 100% complete?
Also, I'm really frustrated about this whole driver thing. I know the drivers aren't broken because I used them on this very computer before, and the repair shouldn't have damaged anything because absolutely everything else is working flawlessly. But every time I've uninstalled the drivers completely, and hook up the phone, it keeps getting a fatal error on that. Apparently "S3C6410 Android ADB" is the name of the device that can't install drivers.

[Q] Issue with I9003 - Pseudo Factory Reset

Hi forum!!
I've been a happy Samsung Galaxy I9003 owner for a while now, and I've always come to this forum for reference on any issues encountered. But right now I have an issue i'm having a hard time understanding, and it's quite a mistery.
Everything started when I downloaded the new Gingerbread update. The phone was wonderful, worked perfectly, but it had one little issue. I left it one night, and the morning after when i picked it up i saw that it was prompting for the initial data (language, use 3G-Wifi, etc). I completed the form once more, and it was back to factory...but in a weird way. Contacts were gone, SMS were gone, APNs were gone, WiFis were gone...but my apps were still there! They were even ordered alphabetically in the menu! Weird, really weird...Background was back to the factory one, icons on the main desktop were back to factory ones, ringtones were back to factory ones. But all my app configurations were still there, emails, gmail, market, corporate email...it was all there.
I discarded this as an issue with the Gingerbread ROM i installed (from Kkrraazzyy's post, the last one), so I downgraded to Froyo once more. Now, why would I ever want to do that?
Idiot me did not look into what version I was running. So I tried the version i remembered I had installed. Worked nice, installed nice...but....next morning...SAME ISSUE! Once more the initial configuration and the same thing...no APNs, no SMS, no Contacts, no nothing, but apps and configs, purrfect!
Now, what I did was move to other Froyo images thinking that I might have gotten the wrong one. I discarded 4 or 5 of them, with different things not working on my phone exactly.
So, after a bit of debating with myself, I decided to upgrade to another GB, but not the final version, a previous one. When i connected it to Samsung Kies, to restore my backup, Kies greeted me with a "I've got a new firmware for your phone...do you wish to upgrade?". I thought "Why not? Maybe if the Samsung software is performing the upgrade, then it might work, considering that i wouldn't be intervening and possibly not interfering with it. So it upgraded, took a considerable amount of time in comparison to ODIN, but it went through.
How did it go? Smooth as silk...everything was wonderful! Apps worked, hardware worked, phone run well...backup went in perfectly...i was so happy! Last night I was watching a movie with it, it was great! So i went to sleep with a happy smile on my muzzle, only to wake up this morning and find the phone with....THE FRIGGIN' START FORM ONCE MORE!! FFFFFFFFFFFUUUUUUUUUUUUUUU!!!!!!
Once more, no APNs, no SMS, no Contacts, no WiFi, no nothing!!! Back to factory partially!
So now i'm thinking...firmware is out of the question...is there any chance there might be something physically wrong with my phone by now?? Something like...I don't know...I haven't got the slightest idea. So i'm open to ideas about what this might be about..
Oh, a colorful note...don't know if it has something to do, but i consider it sporty to let you know about it. A weird thing about a Froyo version i installed, was that when you woke up the phone, it would show a red sign on the top saying "Internal SD memory removed". I was truly shocked since I thought that the internal memory could not be removed without the phone crashing. But well, i just discarded that data at the time as an issue with the image.
Ideas, anyone? If not, i'm guessing i'll just place it under my car, ran it over, and get another with the insurance...

I think I heared such problem once a time. Try in this way
1. flash kpe with all 4 files
2. flash kpm single file as pda file.
3. do factory reset
if it solve ur problem then its better for u. But if u still face internal sd card error problem then straight way flash stock firmware which is available in ur country & go to samsung center & tell them that suddenly this problem is occured. Dont tell them that u have ever flashed anything on it.

CollieDawg said:
Hi forum!!
I've been a happy Samsung Galaxy I9003 owner for a while now, and I've always come to this forum for reference on any issues encountered. But right now I have an issue i'm having a hard time understanding, and it's quite a mistery.
Everything started when I downloaded the new Gingerbread update. The phone was wonderful, worked perfectly, but it had one little issue. I left it one night, and the morning after when i picked it up i saw that it was prompting for the initial data (language, use 3G-Wifi, etc). I completed the form once more, and it was back to factory...but in a weird way. Contacts were gone, SMS were gone, APNs were gone, WiFis were gone...but my apps were still there! They were even ordered alphabetically in the menu! Weird, really weird...Background was back to the factory one, icons on the main desktop were back to factory ones, ringtones were back to factory ones. But all my app configurations were still there, emails, gmail, market, corporate email...it was all there.
I discarded this as an issue with the Gingerbread ROM i installed (from Kkrraazzyy's post, the last one), so I downgraded to Froyo once more. Now, why would I ever want to do that?
Idiot me did not look into what version I was running. So I tried the version i remembered I had installed. Worked nice, installed nice...but....next morning...SAME ISSUE! Once more the initial configuration and the same thing...no APNs, no SMS, no Contacts, no nothing, but apps and configs, purrfect!
Now, what I did was move to other Froyo images thinking that I might have gotten the wrong one. I discarded 4 or 5 of them, with different things not working on my phone exactly.
So, after a bit of debating with myself, I decided to upgrade to another GB, but not the final version, a previous one. When i connected it to Samsung Kies, to restore my backup, Kies greeted me with a "I've got a new firmware for your phone...do you wish to upgrade?". I thought "Why not? Maybe if the Samsung software is performing the upgrade, then it might work, considering that i wouldn't be intervening and possibly not interfering with it. So it upgraded, took a considerable amount of time in comparison to ODIN, but it went through.
How did it go? Smooth as silk...everything was wonderful! Apps worked, hardware worked, phone run well...backup went in perfectly...i was so happy! Last night I was watching a movie with it, it was great! So i went to sleep with a happy smile on my muzzle, only to wake up this morning and find the phone with....THE FRIGGIN' START FORM ONCE MORE!! FFFFFFFFFFFUUUUUUUUUUUUUUU!!!!!!
Once more, no APNs, no SMS, no Contacts, no WiFi, no nothing!!! Back to factory partially!
So now i'm thinking...firmware is out of the question...is there any chance there might be something physically wrong with my phone by now?? Something like...I don't know...I haven't got the slightest idea. So i'm open to ideas about what this might be about..
Oh, a colorful note...don't know if it has something to do, but i consider it sporty to let you know about it. A weird thing about a Froyo version i installed, was that when you woke up the phone, it would show a red sign on the top saying "Internal SD memory removed". I was truly shocked since I thought that the internal memory could not be removed without the phone crashing. But well, i just discarded that data at the time as an issue with the image.
Ideas, anyone? If not, i'm guessing i'll just place it under my car, ran it over, and get another with the insurance...
Click to expand...
Click to collapse
Did you solved the problem??? I am having the same problem and I tried with some firmwares too.

vishal24387 said:
I think I heared such problem once a time. Try in this way
1. flash kpe with all 4 files
2. flash kpm single file as pda file.
3. do factory reset
if it solve ur problem then its better for u. But if u still face internal sd card error problem then straight way flash stock firmware which is available in ur country & go to samsung center & tell them that suddenly this problem is occured. Dont tell them that u have ever flashed anything on it.
Click to expand...
Click to collapse
I'll try that today and get back to you with the results! Thanks for the answer!

CollieDawg said:
I'll try that today and get back to you with the results! Thanks for the answer!
Click to expand...
Click to collapse
LMAO, I lol'd hard at your post regarding it went overnight FUU.
Firstly, the post was a little long, but interesting. Me gusta.
The problem could be the following
- What class is your SD card? Some tend to buy cheap ones, or some tend to offer when you get a SALE they pitch in a ****ty SD card that literally messes your phone. Made in Taiwan > Made in China. For some. There have been cases when the SD card has not been "ejected" properly the phone tends to receive this as a crash and default sets everything back to stock *Apple does this aswell*. But ofcourse I implore you to try using ANOTHER SD card. If your using one that used to be from a Nokia phone then you need to format that ****. Some files in Nokia cause issues with the Android, this happened when I first got my phone aswell. I would suggest getting one from branded companies, Kingston/SanDisk, IMO, Sandisk is the best. Cheap yet to the mark.
- What put me on edge was your contacts and messages being gone. Maybe it's SD related. Iunno.
PS: Don't use Kies. Kies is horrible. If 2 ugly trolls mated, Kies was probably the result.
To test: Use XXKPH/XXKPM Choice is yours, Don't know how to flash it? Link is under my sig, Remove your SD card. Use it for a day, Fill up the internal memory with atleast 500MB of stuff. Lastly? Pray that overnight the trollfairy doesn't swap your phone with a factory reset one .

Hey Misledz! Thanks for your reply!
About the SD Card, I'm using a Kingston Class 4, 8GB one. But the issue is presenting with "Internal SD Card". While i'm doing this with the phone, just out of precaution, i take it out and i haven't placed it inside my phone yet.
And the whole "Trollfairy" thing, it's starting to look like a viable explanation to it, LOL!!
Misledz said:
LMAO, I lol'd hard at your post regarding it went overnight FUU.
Firstly, the post was a little long, but interesting. Me gusta.
The problem could be the following
- What class is your SD card? Some tend to buy cheap ones, or some tend to offer when you get a SALE they pitch in a ****ty SD card that literally messes your phone. Made in Taiwan > Made in China. For some. There have been cases when the SD card has not been "ejected" properly the phone tends to receive this as a crash and default sets everything back to stock *Apple does this aswell*. But ofcourse I implore you to try using ANOTHER SD card. If your using one that used to be from a Nokia phone then you need to format that ****. Some files in Nokia cause issues with the Android, this happened when I first got my phone aswell. I would suggest getting one from branded companies, Kingston/SanDisk, IMO, Sandisk is the best. Cheap yet to the mark.
- What put me on edge was your contacts and messages being gone. Maybe it's SD related. Iunno.
PS: Don't use Kies. Kies is horrible. If 2 ugly trolls mated, Kies was probably the result.
To test: Use XXKPH/XXKPM Choice is yours, Don't know how to flash it? Link is under my sig, Remove your SD card. Use it for a day, Fill up the internal memory with atleast 500MB of stuff. Lastly? Pray that overnight the trollfairy doesn't swap your phone with a factory reset one .
Click to expand...
Click to collapse

Man this guy should seriously thing of taking writing as a profession.

ganeshbiyer said:
Man this guy should seriously thing of taking writing as a profession.
Click to expand...
Click to collapse
I know right?! Maybe writing is a profession of his. Despite the long nature I was strangely indulged to read it
@Collie, Well the problem happens at times when you don't factory reset. *2767*3855# that should get you in to a manual factory reset. The phone's internal memory sometime's has issues with that, You may however need to flash the latona file to repartition the drive. After the repartition, the flashing of the firmware and lastly, le factory reset. That should serve as a stable ground base
Kingston Nice.
Updates?

KIES really is a POS. Every time i flash a new fw and my phone does the initial boot while its connected to the pc I see the horrid screen on my phone reminding me that KIES is installed on my pc. FUUUUUUUUU

ganeshbiyer said:
Man this guy should seriously thing of taking writing as a profession.
Click to expand...
Click to collapse
Thanks!! I'm actually just a Wintel / Citrix / VMWare administrator. I've written a few fanfics here and there back when i was a filly, but not anymore!

Misledz said:
I know right?! Maybe writing is a profession of his. Despite the long nature I was strangely indulged to read it
@Collie, Well the problem happens at times when you don't factory reset. *2767*3855# that should get you in to a manual factory reset. The phone's internal memory sometime's has issues with that, You may however need to flash the latona file to repartition the drive. After the repartition, the flashing of the firmware and lastly, le factory reset. That should serve as a stable ground base
Kingston Nice.
Updates?
Click to expand...
Click to collapse
About that, maybe I'm doing the reset in an incorrect way. I've been using Vol +, OK, Power to enter the second recovery mode and factory reset the phone. I don't know if this is the same as using the code.
Update on what I did:
I installed the last version of Gingerbread once more, flashed with Odin. This time i did not install any app or register in google, i just left it as it was. This was done saturday afternoon. At night, i took it with me, and i left it in my bag while I was at the club. When i got back to it, around 6 AM, it hadn't rebooted. So i went home, went to sleep, woke up at midday for lunch and....FFFFFFUUUUUUUUUU!!!!!

LOL the irony of the best order. Well did you try without the sdcard? That's your last option from your side, the next possible is getting the unit changed if you are under warranty, just don't mention odin, rather always blame kies LOL. If the end of the world happened, kies. World War 3,kies. There was a user who had the same issue reported like 5months ago, he had internal ROM problem where the phone failed to save the information it was given causing it to say the internal was corrupt? He ended up getting a new unit and found out later the unit he had previously was a faulty handset
Sent from my GT - I9003 in the bathroom

Misledz said:
LOL the irony of the best order. Well did you try without the sdcard? That's your last option from your side, the next possible is getting the unit changed if you are under warranty, just don't mention odin, rather always blame kies LOL. If the end of the world happened, kies. World War 3,kies. There was a user who had the same issue reported like 5months ago, he had internal ROM problem where the phone failed to save the information it was given causing it to say the internal was corrupt? He ended up getting a new unit and found out later the unit he had previously was a faulty handset
Sent from my GT - I9003 in the bathroom
Click to expand...
Click to collapse
SD has been out since day 1, since I started having this issue, first thing i thought is "this idiot is saving its own files to the SD instead of its own memory, and when it reboots for some reason it can't find the files and goes nuts".
So yes, i'm thinking about just taking it to the store and getting a new one...

THAT'S IT! I'm taking it to the store tomorrow...
Now it's just rebooting itself...Samsung logo going on and on....
Thanks everyone for the help!!!

CollieDawg said:
THAT'S IT! I'm taking it to the store tomorrow...
Now it's just rebooting itself...Samsung logo going on and on....
Thanks everyone for the help!!!
Click to expand...
Click to collapse
Get it replaced asap so you can join the "famiry" !

Misledz said:
Get it replaced asap so you can join the "famiry" !
Click to expand...
Click to collapse
If I don't get it changed tomorrow, my next post will be a link to youtube, where you'll find a video of me lighting it up on fire, then dancing around it as it burns, and finally running it over with my car...total destruction, should be covered by my insurance...

CollieDawg said:
If I don't get it changed tomorrow, my next post will be a link to youtube, where you'll find a video of me lighting it up on fire, then dancing around it as it burns, and finally running it over with my car...total destruction, should be covered by my insurance...
Click to expand...
Click to collapse
ROFL, That was literally the funniest thing I heard all month
wish you good luck

CollieDawg said:
If I don't get it changed tomorrow, my next post will be a link to youtube, where you'll find a video of me lighting it up on fire, then dancing around it as it burns, and finally running it over with my car...total destruction, should be covered by my insurance...
Click to expand...
Click to collapse
LOL i would have done the same, only a little different, burn it, dance and wait for the ashes to settle, drink up the ashes or feed it to my dog, then walk upto the nearest samsung retailer and take a dump on the entrance entitled 'Now your phone is ****', I'm pretty sure the insurance covers the carpet too.
Sent from my GT - I9003 in the bathroom

CollieDawg said:
If I don't get it changed tomorrow, my next post will be a link to youtube, where you'll find a video of me lighting it up on fire, then dancing around it as it burns, and finally running it over with my car...total destruction, should be covered by my insurance...
Click to expand...
Click to collapse
Excellent! I loved your whole style of writing although your issue might yet get resolved at the samsung service center but this description is a total Lullzzz.. Lol!
Also I humbly request you to leave a PM with a few links of your fan fic stories! thanks...
Tapashocked via my gt-I9003 with a random keyboard of my choice !

Misledz said:
LOL i would have done the same, only a little different, burn it, dance and wait for the ashes to settle, drink up the ashes or feed it to my dog, then walk upto the nearest samsung retailer and take a dump on the entrance entitled 'Now your phone is ****', I'm pretty sure the insurance covers the carpet too.
Sent from my GT - I9003 in the bathroom
Click to expand...
Click to collapse
Super Duper epic Lol!
Boss you've redefined the whole meaning of taking a ****! :O
Tapashocked via my gt-I9003 with a random keyboard of my choice !

[Q] dial pad problem!

Hello all. i am noob. i just got the infuse last night. used the 010 hex editor to get the unlock code for the phone. i also used that 1click root program. the problem i am facing is that after i did all of this my dial pad is all messed up. the bottom buttons (send key, voicemail key etc) are cut off about half way. its almost as if its a screen resolution problem. was hoping someone has an answer to this better than what att told me which is i need to get a new phone, i really hope thats not the case. please help!

GTG's Ultimate Unbrick will put your phone back to stock.
Then use SuperOneClick to root and I used InfuseRootUnlock_v4, to get my Unlock code.

Any guaruntees it will work? i will try this. and the unlocker you speak of i tried using but kept getting an error message and it wouldnt provide me the unlock code. i guess i could punch in the same one i have written down? I appreciate the help, thankyou.

I don't trust att. My dsl was down, I told them that I knew of three others that were also down.
She had me unplug my dsl modem, then informed me that ghe modem was bad because she couldn't access it.
She then proceeded to try and sell me a new modem. I refused of course, knowing that it was them and not me.
So, no guarantees, but that's what I'd do.
Cranky...

ok. So, i turned the phone off. took out the battery, gave it a second, popped the battery back in, held down both volume buttons while doing so plugged in the usb cable, nothing shows up in the COM line on Oden3.
Sigh what to do now?
Is there any other way I can get the phone back to stock everything?
By the way, if it helps, when i rooted the phone I did NOT install any custom roms, i left it the way it was.
Thankyou for all the help you have been giving me so far.

and Odin recognizes it when i have the phone on and plug it into my computer.
When i boot into down load mode, My computer says that it does not recognize the device? which is weird.
I have also installed Kies

Okay, sorry to be posting endless amounts of posts but i just found something out. This phone must have already been rooted and someone must have already installed a custom rom. i looked at the phone settings and it says its running on "Infused". Now, going into clockworkmod and then into download roms, then to the gtg465x, in BIG BOLD letters it says "WARNING: DO NOT TRY TO INSTALL YOURSELF! FOLLOW INSTRUCTIONS POSTED ON XDA" - Infused v2.2.3
Which is exactly what rom i am running on.
My guess is, is that some "genius" decided not to pay attention to that and follow the directions and screwed it all up. WHICH was not me. Hence, i have not installed a custom rom on this phone.
So back to step one I guess. I sincerely apologize for this, I really do appreciate your help.
Could I install another custom rom such as CM7? Maybe that will fix the dialer issue?

FIXED
okay so i fixed it. All i did was re,download the rom. did both wipes, (didnt do backup, already had one) let it install the rom again, back to normal. Finally.
Thankyou for your cooperation though!

Glad to hear
Cranky...

same problem
chuckles_prs said:
Hello all. i am noob. i just got the infuse last night. used the 010 hex editor to get the unlock code for the phone. i also used that 1click root program. the problem i am facing is that after i did all of this my dial pad is all messed up. the bottom buttons (send key, voicemail key etc) are cut off about half way. its almost as if its a screen resolution problem. was hoping someone has an answer to this better than what att told me which is i need to get a new phone, i really hope thats not the case. please help!
Click to expand...
Click to collapse
im having same problem on tmobile note 3 running dompop v5.1 i cant find a solution have you yet.

Nexus S has no service or USB connection

I have a Sprint Nexus S 4G that I've recently rendered without service or USB connection as a result of a fastboot accident. I'm currently running ICS 4.0.3 (Dooderbutt-aosp-v-5 build), but have tried restoring multiple backups on CM7 to no avail. Wiping all user data in CWM doesn't fix it either. I have also tried flashing the LC1 radio zip with no results.
The way I see it, my two best courses of action would either be to try and return to a stock ROM so that I can send the device in under warranty or to continue to try to fix it myself, which has been less than successful so far. Every process I have found online to return to stock seems to end in fastboot oem lock, which won't do anything for me as my phone doesn't show up in fastboot devices, file explorer, or seem to be recognized by my computer in either Ubuntu or Win 7. I've tried connecting on my friends' computers with the same results. I've also tried using another USB cable. No dice.
Sorry if I missed something obvious before posting. I tried to do a lot of research online and have reached the end of what I know what to do. Any suggestions?

Bump.
After some more researching, it appears that there is no way to lock the bootloader except through USB connection with a computer. Does this mean I'm out of luck? Any suggestions as to how to solve this issue? Since my first post, I've flashed ICS 4.0.4 with no improvement on the above symptoms. Also, auto-rotation doesn't seem to work. My Baseband version in About is listed as Unknown. Does anyone have any clue? Replies would be greatly appreciated.

have you updated the android drivers on your computer? you wont be able to connect to fastboot without the drivers. you can get it here http://www.junefabrics.com/android/ do the free download(on your computer) then follow the on screen instructions.

simms22 said:
have you updated the android drivers on your computer? you wont be able to connect to fastboot without the drivers. you can get it here ... do the free download(on your computer) then follow the on screen instructions.
Click to expand...
Click to collapse
I'm running Ubuntu, so from what I understand, I don't need any drivers. Prior to this fiasco, my computer recognized it as a storage device in the file system as well as a device in fastboot. It doesn't come up as either now.

I had a similar problem after I updated to ICS 4.0.3, what version of Ubuntu do you have, and does the device show up when you run lsusb?
Also, have you checked inside the usb connector to see if one of the pins is bent or damaged?

I'm running Ubuntu 11.10 and no, my Nexus doesn't show up in lsusb or anything else I seem to try. I have checked the pins in the connector of the phone and even bent them around a little bit, but I doubt that's the problem. Since it disappeared immediately after a bad flash, I'm fairly confident this is a software-induced error.

Ok, the only other thing I can think of is a bad kernel or baseband, but since you've tried several different roms, I don't think that's the problem (unless you put on one that's not for your model).
Sorry I can't be more helpful, hope you figure it out!

Thanks for your help anyway. To be clear, each rom has its own kernel and baseband, correct? Are those things I can flash independently of roms like the radio?

Found something, not sure if you've seen it already : http://forum.xda-developers.com/showthread.php?t=1077168
This bit is especially interesting :
"*If your having problems after the radio flash......go to dialer:
Type in *#*#72786#*#*, put your msl in, and let it re-provision"

For the usb not connecting, I had the same problem. After trying every computer in the house, I grabbed a can of compressed air for electronics and blew out my micro usb port on the phone itself. There was a small piece of lint in there that was causing the connection to not be made. It's worth a try.

statisticalanomaly said:
Found something, not sure if you've seen it already : http://forum.xda-developers.com/showthread.php?t=1077168
This bit is especially interesting :
"*If your having problems after the radio flash......go to dialer:
Type in *#*#72786#*#*, put your msl in, and let it re-provision"
Click to expand...
Click to collapse
I'm attempting to try this work around, but I can't seem to find my msl. I've tried putting in an incorrect code and checking alogcat for it as well as the terminal output of getprop. Neither of these give me the number. Sprint mentions using this code for resetting your phone in this tutorial, but I can't for the life of me find the part of their site that shows the msl.
This is exhausting. I really appreciate all your guys' help though. Thanks so much.

Unfortunately, I never figured out how to solve the problem. I took my phone into Sprint the other day and lucked out on the repair technician. He was messing around trying stuff and had a moment of realization when he booted into Clockworkmod. Even though I had voided my warranty, he still let me replace the phone for the $35 fee. I walked out with a brand new Photon 4G. I'm so happy, it's like Christmas in May!
To others who have this problem: sorry, but I don't know what to tell you! Mine was probably bricked. The MSL number didn't connect the phone and neither did anything else I tried. Best of luck to you.