Database Info

bricked my captivate?

i tried doing this: http://forum.xda-developers.com/showthread.php?t=1127249
and i failed, i got the first part down and i saw the red fish which is the devs logo. then the second part with the kernelKF1.tar file i guess i screwed up, because on reboot it would loop, it would go to at&t screen then it would show my screen really screwed up, with a whole bunch of colors and what not like as if it was tripping on acid haha. anyways now when i turn on my phone it shows a logo of a phone, a yellow triangle with an exclamation mark next to a computer. I do not want to lose all my apps and what not, i mean i doooo have 27 hours on my final fantasy 7 lol. so please guys what do i do to bring my phone back to life so i can try to root and flash a ROM correctly this time.

Does it say something about firmware upgrade failure, use recovery mode?

Yep. It's a soft brick so you can recovery it!
First: You must flash AT&T Gingerbread Bootloader from here: http://forum.xda-developers.com/showthread.php?t=1129821. (You must go to download mode by Vol Up + Vol Down + USB Plug or use a jig (google: Jig Captivate)
Then: Flash your kernelKF1.tar again (Download Mode) or Another kernel you like for KF1! (I prefer you flash this kernel: http://forum.xda-developers.com/showthread.php?t=1127322)
That's all!

-how do i access recovery mode? says nothing about an update failure.
-that's great news! does it matter that i was on 2.1 eclair first? back in the day i rooted my phone on the stock eclair and i beliiiiiieve did a lagfix as well, but no custom ROMS or anything like that.
-I use odin to flash both the bootloader/kernel correct? on odin i just have to wait for it to says "connected" in that little chatbox right? one of the box's all the way to the top isn't supposed to say anything until its passes right?
sorry for all the real dumb and seemingly obvious questions. But i want to make sure i know what i am doing so i can always do it correctly. thanks for all your help and quick replys guys i really appreciate it!

nismoasfuh said:
-how do i access recovery mode? says nothing about an update failure.
-that's great news! does it matter that i was on 2.1 eclair first? back in the day i rooted my phone on the stock eclair and i beliiiiiieve did a lagfix as well, but no custom ROMS or anything like that.
-I use odin to flash both the bootloader/kernel correct? on odin i just have to wait for it to says "connected" in that little chatbox right? one of the box's all the way to the top isn't supposed to say anything until its passes right?
sorry for all the real dumb and seemingly obvious questions. But i want to make sure i know what i am doing so i can always do it correctly. thanks for all your help and quick replys guys i really appreciate it!
Click to expand...
Click to collapse
1. Use combo keys: Vol Up + Vol Down + Power to access Recovery. If you are on AT&T Gingerbread Bootloader, you are good to go!.
2. You must disable lagfix before flash any rom. You can go stock and reflash it but i think you must get KF1 work to backup your game process!
3. If you flash KF1 with bootloader, you needn't to reflash it again. Just reflash kernel and you are unbrick. (If you are on AT&T Gingerbread Bootloader, on screen PC -- /!\ -- Phone, you can run ODIN and reflash kernel KF1. No need to go to Download Mode to flash kernel. If you can't flash from ODIN (try some time, change USB port, change PC, and reinstall Windows), you must reflash AT&T bootloader.
Good luck!

at&T gingerbread bootloader is a program like odin? or does it literally mean the booting of a gingerbread device? im so confuuuuused.
So i have to flash a stock 2.1 eclair? then do the kf1 file to get to 2.3.3 gb?

nismoasfuh said:
at&T gingerbread bootloader is a program like odin? or does it literally mean the booting of a gingerbread device? im so confuuuuused.
So i have to flash a stock 2.1 eclair? then do the kf1 file to get to 2.3.3 gb?
Click to expand...
Click to collapse
its questions like these that make people say 'read, read, read, read, then read some more'
the answer is literally everywhere in these forums......

i just made it so much worse, i used the gb bootloaders as well as used that ROM by using the kernel and a previous file in odin. i can still go to download/recovery, and if i just power on the phone it will loop at the at&t screen

when i get to recovery, the vol bottoms dont let me select anything. so my only option is to keep rebooting. i cant apply update from sd; even though im sure its because im doing it wrong!! someone please help i need this phone for the upcoming work week didnt think it would take 4 days to figure out.
Can Someone Please Please tell me step by step what i should do, i understand how to work the programs i just dont know the order in which to do them in. what am i to do? remember i was initially on 2.1 eclair with a voodoo lagfix, yet, i dont know what i am on know, i tried flashing ROMS as well as gb bootloaders.

so your volume buttons are broken?
just boot into download mode, flash back to stock with ODIN or Heimdall, whichever is easier for you to use, then leave your phone the fk alone, because you are compounding the problems by panicking.
its obvious that you havent truly understood what you have been flashing on your phone, and you are about to wind up with a pretty brick that will need to get sent to jtag/unbrickable mod.....
until you understand and comprehend what you are doing, leave it the hell alone, this isnt childs play here

Pirateghost said:
so your volume buttons are broken?
just boot into download mode, flash back to stock with ODIN or Heimdall, whichever is easier for you to use, then leave your phone the fk alone, because you are compounding the problems by panicking.
its obvious that you havent truly understood what you have been flashing on your phone, and you are about to wind up with a pretty brick that will need to get sent to jtag/unbrickable mod.....
until you understand and comprehend what you are doing, leave it the hell alone, this isnt childs play here
Click to expand...
Click to collapse
well said..

so have I lost all my apps? even flashing back to stock?.....and no, volume buttons are not broken.

i have the "firmware upgrade fail" and cant get into recovery...

OK! So i finally got the phone up and running late late last night. its on firmware 2.3.3 on build: cognition v2
kernel version: 2.6.35.7-I897UCKF1-CL273832
its definitely GB; thats something obvious. yet, i cant shake the feeling that it still feels slow. i ran quandrant and its a shy 1040. I know, I know, quadrant scores dont mean anything, but still.... i would think it would be in atleast the 1300+ especially with the lagfix from cognition5.

nismoasfuh said:
OK! So i finally got the phone up and running late late last night. its on firmware 2.3.3 on build: cognition v2
kernel version: 2.6.35.7-I897UCKF1-CL273832
its definitely GB; thats something obvious. yet, i cant shake the feeling that it still feels slow. i ran quandrant and its a shy 1040. I know, I know, quadrant scores dont mean anything, but still.... i would think it would be in atleast the 1300+ especially with the lagfix from cognition5.
Click to expand...
Click to collapse
If you know quadrants mean nothing then why are you looking to get a higher score?
But in all seriousness, I think were all a little surprised to see that you have a working phone and even more so one with a custom rom. You need to read up on here before you start messing with things again or your going wind up with a brick.
let me quote Mr. Haley here
its obvious that you havent truly understood what you have been flashing on your phone, and you are about to wind up with a pretty brick that will need to get sent to jtag/unbrickable mod.....
until you understand and comprehend what you are doing, leave it the hell alone, this isnt childs play here
well said..
Click to expand...
Click to collapse
Basically, nobody on here is going to offer you help until you attempt to help yourself. This isnt a support forum. None of it is. We are just kind enough to help you out. But its super annoying to see you put yourself in situations that we warned about then come back on here with OMG I THINK I BRICKED! So spend time reading and please realize we have 0 obligation to help if you brick.

capocaccia said:
If you know quadrants mean nothing then why are you looking to get a higher score?
But in all seriousness, I think were all a little surprised to see that you have a working phone and even more so one with a custom rom. You need to read up on here before you start messing with things again or your going wind up with a brick.
let me quote Mr. Haley here
Basically, nobody on here is going to offer you help until you attempt to help yourself. This isnt a support forum. None of it is. We are just kind enough to help you out. But its super annoying to see you put yourself in situations that we warned about then come back on here with OMG I THINK I BRICKED! So spend time reading and please realize we have 0 obligation to help if you brick.
Click to expand...
Click to collapse
Actually, it was me that said it.
Sent from my SAMSUNG-SGH-I777

And I just agreed with him.

thaaaanks for the life lesson; but I wouldnt be able to sit here and tell you im Running a custom ROM unless i did do my research. The time differences between my posts was me literally finding and reading countless articles. I'm asking questions not figuring out fallacys..

Don't be so defensive, they weren't talking down to you and belittling, just making sure you don't end up in a worse situation. Looking out for your best interest.

I know that....If my posts were that bad at least show me the simple corrections.I know the value of my phone, ill deal with it if it comes to that and even then nothing has happened since. Regardless, I got out of the soft brick and now I'm on DG's 2.3.3.

[Q] Motorola Photon 4g

okay so i have spent many hours with my new motorola photon 4g that i recently got from sprint. bout 4 days now. im more use to using samsung android devices and htc devices and this is my first motorola. i had been wanting to root it because its my favorite thing with an android when i get one. so i did research and unlocked my bootloader and did the unlock sbf file and installed clockwork mod revocovery as well. after all that my photon was working fine but was on stock rom. i had downloaded a rom and put it into the phone and of course installed it. im not used to motorola and it was my first time learning about their bootstrap and blah blah blah. after installing i had tried turning the phone on but it just stayed at the Motorola dual core screen. i tried booting three more times to no luck. so then i had tried another rom and again i had no luck. i should have done the smart thing which is after the unlocking and putting on recovery to make a back up immediately but for some reason didnt. so i go online to find another sbf file so that i could start all over and see my mistakes, but then my battery was way to low. my advice to you is to make sure your battery is filled up cuz trust me this was a ***** to figure all out. so this is what i did in case if any body has this kind of problem, cuz i know im not gonna be the first, well maybe, but definitely not the last. what i found out is the phone wont let you flash any files when battery is low. and as i can say, its for saftey reason cuz if it dies while flashing, well you might be **** out of luck. depending on what you are flashing. but what i found out is that if you connect the hone to the wall outlet, the phone will turn on into clockwork. dont try plugging into the computer cuz it will be useless. i tried several times till i finally got the message. the recovery is the only thing that can be booted up. you dont even need the battery in the photon. it will still turn on as long as it was in the outlet. i then transfered files to the sdcard from another phone, over and over till finding the right one, then flashed and flaseh. finally, finally found a rom that woul work with ,y phone. i kept the rom till i was able to charge the phone. rom kept bootlooping but it kept bootlooping long enough to charge the battery then flashed the sbf sprint file to my phone. i wanted to write this cuz i was hoping somebody would be able to explain to me what i may have done wrong with the flashing or if their was a step that i had skipped cuz it seems like no rom works as of now with my photon. hopefully someone can help me out here cuz i really do want a custom rom. or maybe someone can tell me what i should do in order to install a custom rom and have it work for me.

start here:
http://forum.xda-developers.com/showthread.php?t=1413349
jokersax11 has done an amazing job bringing ICS to the photon... I believe he will soon have his beta officially picked up by cyanogenmod... also, I am pretty sure he's close to fixing the 4G that you loose when you unlock the bootloader.

[GUIDE] T-Mobile US One S - How to ROOT and flash ROMs

So I know there's been some controversy and scares going around about the US version, since it JUST came out. I'm here to calm you guys down. I have now rooted mine, flashed an interim CWM touch version (not permanent) and have flashed a ROM......ALL successfully.
Here's what I did:
UNLOCKING:
Unlock your bootloader by registering at HTCdev.com and following the unlock instructions. Under device, choose "All other devices", as the One S is not yet listed. It'll walk you through getting your unlock token and flashing it.
ROOTING
Follow Paul O Brien's instructions on rooting your phone. I flashed the r3 superboot file he had. The first time it didnt take and just booted the phone back up. Second time it took, and seems to have stuck, at least for apps. Please note that my phone says *TAMPERED* along with the *UNLOCKED* notification. I have no idea what that means exactly, but everything works great for me.
This means if you dont want to leave Sense but want to get the tons of useless and annoying T-Mobile and other bloatware apps out, you can. T-Mo are dicks and make almost 100% of the apps on it by default SYSTEM apps, therefore unremovable. So you'll need root and Titanium Backup to freeze or delete them. I'd recommend freezing the non-TMo one's just in case.
FLASHING ROMS
1. Flash Paul O Brien's intermin CWM touch version. You MUST use this interim CWM version for the moment, as the others do not work properly. Some things like USB mount dont work in this interim version, but the important functions like wipe and flash, backup and restore, and restart do work. The CWM recovery seems permanent, based on my initial trials, so no worries about reflashing it each restart.
2. Flash your ROM of choice from Clockworkmod Recovery. I'm using Black Dragon right now, but there are others out there as well. I'm personally looking forward to CM9, but its a little ways away, usability-wise.
So there you have it, all you US guys. Don't be afraid to mod your phone. Remember all the warranty void disclaimers as always. I'm not responsible for you bricking your phone. This is just my experience in just under 24hrs of use. Things are looking good for the One S.

bump... i see US users still asking.
Mods, can we perhaps sticky this post of mine? I don't want to take credit for the actual methods of rooting, since Paul O Brien and others deserve that credit, but I think it'd be helpful for US users, since many don't know whether or not the international method works.
That, or perhaps editing the Intl guides to make it clear that the US version accepts the same methods and ROMs.

Worked great for me
Sent from my HTC VLE_U using xda premium

So if we root and flash a custom ROM is there any way to get the phone back to factory state, and get rid of the *TAMPERED* and *UNLOCKED* notification??

Did anyone else get a bit of a sad chuckle out of the first step in the instructions being "remove and reinsert battery"?

cyberchuck9000 said:
Did anyone else get a bit of a sad chuckle out of the first step in the instructions being "remove and reinsert battery"?
Click to expand...
Click to collapse
Great, now my blisters on my fingers will heal.
But still.... I cannot imagine not needing a batt pull.

nickmv said:
Mods, can we perhaps sticky this post of mine? I don't want to take credit for the actual methods of rooting, since Paul O Brien and others deserve that credit, but I think it'd be helpful for US users, since many don't know whether or not the international method works.
That, or perhaps editing the Intl guides to make it clear that the US version accepts the same methods and ROMs.
Click to expand...
Click to collapse
+1

androidcues said:
Great, now my blisters on my fingers will heal.
But still.... I cannot imagine not needing a batt pull.
Click to expand...
Click to collapse
If you need to perform a hard reset on the One S, you hold down the power button for about 7-10 secs.

First of all, thanks for this thread...I used the HTC One S All in one tool kit to unlock my phone, unfortunately I miss understood one of the directions(#5) and stopped using the tool kit and followed another thread, much to my surprise, my bootloader is unlocked, hooray My question is, how do I get back to the original state if that is possible? The reason I ask, is I would like to go back and do it correctly...I used better terminal emulator to see if I had root, but all I got was the $ sign instead of the # sign So I would like to start over...
Thanks in advance for the help

I'm honestly not sure what the procedure is for relocking an HTC bootloader. Perhaps do some Google research on some of the latest models, and I bet you'll find something.
That being said, once you unlock the bootloader a single time, the best you can do is go to **RELOCKED** state. You'll never get back **LOCKED**. Once it's gone it's gone. I'm curious about the **TAMPERED** message though. That's an ugly word.

not sure what exactly went wrong.
somehow flashed CWM and now thats the only thing my phone will boot to, even after re-flashing the stock recovery.
can't get the phone to turn on, only CWM every single time.

suhailtheboss said:
not sure what exactly went wrong.
somehow flashed CWM and now thats the only thing my phone will boot to, even after re-flashing the stock recovery.
can't get the phone to turn on, only CWM every single time.
Click to expand...
Click to collapse
Uh oh that doesn't sound good
Sent from my HTC VLE_U using xda premium

yeah, tried reflashing both CWM & stock recovery. phone still boots to CWM everytime.
Luckily i can still access the phone via ADB, (while in recovery) so i'm sure i'll be able to sort it out. just need to take a fresh crack at it tomorrow. gonna switch back to my galaxy nexus tonight. (oh wait, i dont have any other phones that use microsim)
haha.

Hmm, interesting. Did you flash the interim recovery that Paul O Brien posted, and not another version? Just wanna make sure. I've heard of this happening in my past experience with the Nexus S, but I can't recall what the deal was. Regardless, I don't think you're in trouble. As with your GNex, it's very hard to completely brick the device unless you flash perhaps a bad hboot file, however I'm not really familiar with HTC devices.
This is my first HTC so I'm still trying to learn how the hboot and other processes work together. Sry to hear you had bad luck.
UPDATE: You should try the root install script. It tells the phone to boot after install. That might get you booted atleast.
Some thoughts:
1. Flash the stock recovery back and reflash CWM
2. Clear cache and dalvik within CWM, and make sure to use the 'Reboot System' option if you aren't already.
From what I can tell, your "boot-to-recovery" flag is set on the phone, and isn't getting cleared.

nickmv said:
So I know there's been some controversy and scares going around about the US version, since it JUST came out. I'm here to calm you guys down. I have now rooted mine, flashed an interim CWM touch version (not permanent) and have flashed a ROM......ALL successfully.
Here's what I did:
UNLOCKING:
Unlock your bootloader by registering at HTCdev.com and following the unlock instructions. Under device, choose "All other devices", as the One S is not yet listed. It'll walk you through getting your unlock token and flashing it.
ROOTING
Follow Paul O Brien's instructions on rooting your phone. I flashed the r3 superboot file he had. The first time it didnt take and just booted the phone back up. Second time it took, and seems to have stuck, at least for apps. Please note that my phone says *TAMPERED* along with the *UNLOCKED* notification. I have no idea what that means exactly, but everything works great for me.
This means if you dont want to leave Sense but want to get the tons of useless and annoying T-Mobile and other bloatware apps out, you can. T-Mo are dicks and make almost 100% of the apps on it by default SYSTEM apps, therefore unremovable. So you'll need root and Titanium Backup to freeze or delete them. I'd recommend freezing the non-TMo one's just in case.
FLASHING ROMS
1. Flash Paul O Brien's intermin CWM touch version. Some things like USB mount dont work, but the important functions like wipe and flash and restart do. The CWM recovery seems permanent, based on my initial trials, so no worries about reflashing it each restart. I cant speak for the non-interim solutions, but from what I can gather, they are problematic, so avoid them for now.
2. Flash your ROM of choice from Clockworkmod Recovery. I'm using Black Dragon right now, but there are others out there as well. I'm personally looking forward to CM9, but its a little ways away, usability-wise.
So there you have it, all you US guys. Don't be afraid to mod your phone. Remember all the warranty void disclaimers as always. I'm not responsible for you bricking your phone. This is just my experience in just under 24hrs of use. Things are looking good for the One S.
Click to expand...
Click to collapse
Is this part a must? Would you mind PM'ing me with how to do this part if it's a must? I have Unlocked and rooted my phone, just waiting for a good ROM to come by.

Thongvilay said:
Is this part a must? Would you mind PM'ing me with how to do this part if it's a must? I have Unlocked and rooted my phone, just waiting for a good ROM to come by.
Click to expand...
Click to collapse
That step is only if you want to flash ROMs, or need to wipe cache, dalvik, etc. CWM is used for flashing and recovery/backup purposes. If you're not using ROMs yet, then you have no need for it.

nickmv said:
Hmm, interesting. Did you flash the interim recovery that Paul O Brien posted, and not another version? Just wanna make sure. I've heard of this happening in my past experience with the Nexus S, but I can't recall what the deal was. Regardless, I don't think you're in trouble. As with your GNex, it's very hard to completely brick the device unless you flash perhaps a bad hboot file, however I'm not really familiar with HTC devices.
This is my first HTC so I'm still trying to learn how the hboot and other processes work together. Sry to hear you had bad luck.
UPDATE: You should try the root install script. It tells the phone to boot after install. That might get you booted atleast.
Some thoughts:
1. Flash the stock recovery back and reflash CWM
2. Clear cache and dalvik within CWM, and make sure to use the 'Reboot System' option if you aren't already.
From what I can tell, your "boot-to-recovery" flag is set on the phone, and isn't getting cleared.
Click to expand...
Click to collapse
thanks for the tips, i had tried clearing cache/dalvik within CWM and it still would not work. and yes i did flas the interim CWM from paulobrien
luckily the phone would work via ADB while in CWM. So i pushed three different ROMS to the phone, at first each oen would lock up and reboot within 20 seconds of doing anything. I then went back into recovery & wiped data/cache/dalvik maybe 10 times out of sheer frustration. Then re-flashed a fresh copy of black_dragon_v4.0, didnt do anything after boot. just let it sit there till this morning.
now the phone seems to be working perfectly...
so hopefully if anyone encounters this problem my last couple posts will help them out!

suhailtheboss said:
thanks for the tips, i had tried clearing cache/dalvik within CWM and it still would not work. and yes i did flas the interim CWM from paulobrien
luckily the phone would work via ADB while in CWM. So i pushed three different ROMS to the phone, at first each oen would lock up and reboot within 20 seconds of doing anything. I then went back into recovery & wiped data/cache/dalvik maybe 10 times out of sheer frustration. Then re-flashed a fresh copy of black_dragon_v4.0, didnt do anything after boot. just let it sit there till this morning.
now the phone seems to be working perfectly...
so hopefully if anyone encounters this problem my last couple posts will help them out!
Click to expand...
Click to collapse
Wow, I have no idea dude. That sounds kinda crazy. Hopefully all will be well in the future and you won't come across it again.

the only variable i can think of is that i did have the phone about a week before launch. HTC mailed it to me directly.
I thought maybe that had somethign to do with it, but as far as i can tell the phone was the final shipping version.

I sent you a PM, trying to find a solution.

[Q] Kernal flashing gone wrong...need help :(

Hey everyone, I'm new to android and tried something just to install a custom ROM. I flashed the kernel and tried to install a new one and I thought it was going well when I heard the woman talking through the phone, but apparently not... Now when the logo shows as it starts but it never makes it pass there.
It shows something like TV static and then reboots again and again.
It hasnt stopped since... I really feel bad cause i feel like a failure and thats the only good phone i have ever gotten...
Ive also tried the recovery mode, that doesnt work. The logo at startup gets brighter then reboots agaain ans again... Please help me.. Please asap so i can use it finally... Thanks alot
Oh sorry i forgot to state the phone specs , im new here...
Samsung Galaxy S 4G
2.2
Couldnt get it updated to 2.3
Thanks again guys.

StrugglaREP said:
It shows something like TV static and then reboots again and again.
Click to expand...
Click to collapse
As the cobwebs clear, that sounds like problems with bootloaders going from Froyo to Gingerbread. I vaguely remember something about "rainbow" screens if you didn't follow the right steps in the transition.
I think your best bet is getting the Heimdall "one-click" approach to work for you. If you don't have a custom recovery running, there aren't a lot of choices.
@lumin30 wrote up a great set of instructions that I would follow carefully.
It's pretty hard to hard-brick an SGS4G, so breath easier...

I'll give it a try, thanks!
jeffsf said:
As the cobwebs clear, that sounds like problems with bootloaders going from Froyo to Gingerbread. I vaguely remember something about "rainbow" screens if you didn't follow the right steps in the transition.
I think your best bet is getting the Heimdall "one-click" approach to work for you. If you don't have a custom recovery running, there aren't a lot of choices.
@lumin30 wrote up a great set of instructions that I would follow carefully.
It's pretty hard to hard-brick an SGS4G, so breath easier...
Click to expand...
Click to collapse
Thanks for answering so quickly, I'll be sure to go and try it out right now and see what happens. I really hope th phone connects to the computer atleast cause it keeps restarting itself... as I said I'm really new to Android I was just trying to update the kernel toget the ROM able to update so I can put on a custom one and get the apps that I really need that wouldn't work on 2.2
But Thank you very much , I'll get right on it and see what happens and say whether it worked or not

[Q] Help I think I bricked my device!!!

I have a samsung galaxy s 4g from t-mobile I was trying to upgrade from ginger bread to ice cream sandwich and now the phone keeps restarting. When it turns on it shows the samsung galaxy s 4g startup then it shows the ice cream sandwich i tried to download and it shows a progress bar when it gets to the very end it restarts and does the same process over and over again. I tried to plug into computer and the computer says my device is not recognized. I need help!! What do I do? If video is needed I will provide one

jeffreylin_ said:
There is no OTA update to ICS for this device. If you messed it up, you should use the one click back to stock, which will revert everything back to the way it was when you first got it.
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
I know but I saw a video on youtube about it so i tried it and it just keeps restarting. Would you mind explaining how to do that because it I can't connect my phone to the computer it turns off every 15 secs and I can't go into recovery mode either.

The good news is that it is nearly impossible to "hard brick" an SGS4G. That you are seeing it repeatedly trying to start up tells me that it's more that you just have improper firmware on your device.
Take a look a the heimdall "one-click" collection http://forum.xda-developers.com/showthread.php?t=1358498
 @lumin30 has a great walk-through as well -- http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2
The most difficult thing about using them is getting the right drivers installed on your computer for your phone (and ROM).

jeffsf said:
The good news is that it is nearly impossible to "hard brick" an SGS4G. That you are seeing it repeatedly trying to start up tells me that it's more that you just have improper firmware on your device.
Take a look a the heimdall "one-click" collection http://forum.xda-developers.com/showthread.php?t=1358498
@lumin30 has a great walk-through as well -- http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2
The most difficult thing about using them is getting the right drivers installed on your computer for your phone (and ROM).
Click to expand...
Click to collapse
I can't do this because when i plug my phone in to the computer it says device not recognized and the phone restarts about every 15 seconds. If you need to see a video I can provide one. I need to fix it because i'm stuck with this phone for a few more months.

Google samsung usb download jig. You can buy one or make your own for just a few bucks. There is a thread or two on xda on making one. Couple of threads on how to get into download mode too.
Sent from my SAMSUNG-SGH-I547 using xda app-developers app

MuShRo0m said:
I can't do this because when i plug my phone in to the computer it says device not recognized and the phone restarts about every 15 seconds. If you need to see a video I can provide one. I need to fix it because i'm stuck with this phone for a few more months.
Click to expand...
Click to collapse
"Device not recognized" is Windows' polite way of saying that it can't make sense of drivers. I have a few polite things to say about Window's handling of drivers, but let's just say that it is tweaky, at best, and you apparently can only have one set of "similar" drivers installed at a time. You will have to work with the drivers once you get Download Mode under control.
That is is still rebooting seems to suggest that you don't have the power off / hold volup/vol dn / plug in USB sequence quite right.

jeffsf said:
"Device not recognized" is Windows' polite way of saying that it can't make sense of drivers. I have a few polite things to say about Window's handling of drivers, but let's just say that it is tweaky, at best, and you apparently can only have one set of "similar" drivers installed at a time. You will have to work with the drivers once you get Download Mode under control.
That is is still rebooting seems to suggest that you don't have the power off / hold volup/vol dn / plug in USB sequence quite right.
Click to expand...
Click to collapse
Thank you I just fixed it. I thought I was screwed thanks so much!! Do you know anything good to put on the device that is for the sgs4g because the last time I put the wrong ones and it ended up how it did. I tried valhalla final do you know any better ones.

I'm glad you got it going again! With luck, you won't have to try that again, but it is a great device to play around with as it is rather hard to get it to "hard brick" to the point where you can't get it into download mode and start again. Just keep lots of backups
There are lots of great ROMs out there for this device, in a few different flavors. You generally need to be careful how you upgrade between the flavors, especially as the big upgrade steps are often taken for granted by current ROMs
Froyo (I'll go out on a limb and say you don't want this)
Gingerbread, BML
Gingerbread, MTD
Ice Cream Sandwich (MTD only, I believe)
JellyBean (MTD only)
BML is the "stock" low-level disk routines used by Samsung ROMs, as well as some custom Gingerbread ROMs. MTD is an open-source alternative to BML that is popular with later Gingerbread ROMs, as well as probably all ICS and JB ROMs. If you are going to use an MTD ROM, you should find a solid MTD Gingerbread ROM to do the switch-over from BML to MTD to make sure it goes smoothly.
I can't really say which is "best" between all the ROMs. There are many good ones out there. A lot of people will have which ROM they use or like in their signature.
With any ROM, read the main thread to see what things might not work for you if you try the ROM.
Some of the general things that are pretty much universal are:
ICS
WiFi Calling doesn't work
Indicated WiFi signal level appears lower
JB
Built-in GPS doesn't work
WiFi Calling doesn't work
Indicated WiFi signal level appears lower

jeffsf said:
I'm glad you got it going again! With luck, you won't have to try that again, but it is a great device to play around with as it is rather hard to get it to "hard brick" to the point where you can't get it into download mode and start again. Just keep lots of backups
There are lots of great ROMs out there for this device, in a few different flavors. You generally need to be careful how you upgrade between the flavors, especially as the big upgrade steps are often taken for granted by current ROMs
Froyo (I'll go out on a limb and say you don't want this)
Gingerbread, BML
Gingerbread, MTD
Ice Cream Sandwich (MTD only, I believe)
JellyBean (MTD only)
BML is the "stock" low-level disk routines used by Samsung ROMs, as well as some custom Gingerbread ROMs. MTD is an open-source alternative to BML that is popular with later Gingerbread ROMs, as well as probably all ICS and JB ROMs. If you are going to use an MTD ROM, you should find a solid MTD Gingerbread ROM to do the switch-over from BML to MTD to make sure it goes smoothly.
I can't really say which is "best" between all the ROMs. There are many good ones out there. A lot of people will have which ROM they use or like in their signature.
With any ROM, read the main thread to see what things might not work for you if you try the ROM.
Some of the general things that are pretty much universal are:
ICS
WiFi Calling doesn't work
Indicated WiFi signal level appears lower
JB
Built-in GPS doesn't work
WiFi Calling doesn't work
Indicated WiFi signal level appears lower
Click to expand...
Click to collapse
Ok thanks for the suggestions but I have been looking at the tutorials on this and it says you need cwm but that isn't supported by this device sgs4g. What do i do? Here is what I am trying to install http://forum.xda-developers.com/showthread.php?t=2587589

MuShRo0m said:
...you need cwm but that isn't supported by this device sgs4g.
Click to expand...
Click to collapse
It is true that you can't install Clockwork recovery by itself on the SGS4G. However, the custom kernels have either CWR or TWRP "built in" to them. (On the SGS4G, kernel and recovery bound together and flashed as a single unit.)
Here is what I am trying to install http://forum.xda-developers.com/showthread.php?t=2587589
Click to expand...
Click to collapse
Well, that is quite a first ROM to try to flash! Let's see, it says "beta" in the header, it's been out for under 24 hours, people are reporting difficulties flashing it, it has a different partition structure than any other SGS4G ROM, oh, and it's the first KitKat ROM for the phone, so the Android part of the phone is very different and potentially still has major bugs. I think you're in for a world of hurt if you try something that hasn't stabilized to the point that people are generally successful with it, especially if you aren't comfortable with the whole flashing process yet.
I'd suggest one of the well-proven ICS ROMs as a start. The are relatively robust in their ability to install and generally perform very well on the phone. Take a couple weeks with it to know how it performs on the phone for you and then look again at what you might want to try out.
While you can generally upgrade your data from one Android release to the next using a tool like Titanium Backup, going back is dicey, at best. I didn't decide to upgrade my day-today phone from GB to ICS for quite some time after the ROMs were available for just that reason. I'd hate to find out that there was a show-stopper bug and I couldn't go back to GB without losing my data.

jeffsf said:
It is true that you can't install Clockwork recovery by itself on the SGS4G. However, the custom kernels have either CWR or TWRP "built in" to them. (On the SGS4G, kernel and recovery bound together and flashed as a single unit.)
Click to expand...
Click to collapse
I'm a noob when it comes to this stuff I have been looking around and I can't find any custom kernels that have it pre installed could you please help me on this.

jeffsf said:
Well, that is quite a first ROM to try to flash! Let's see, it says "beta" in the header, it's been out for under 24 hours, people are reporting difficulties flashing it, it has a different partition structure than any other SGS4G ROM, oh, and it's the first KitKat ROM for the phone, so the Android part of the phone is very different and potentially still has major bugs. I think you're in for a world of hurt if you try something that hasn't stabilized to the point that people are generally successful with it, especially if you aren't comfortable with the whole flashing process yet.
I'd suggest one of the well-proven ICS ROMs as a start. The are relatively robust in their ability to install and generally perform very well on the phone. Take a couple weeks with it to know how it performs on the phone for you and then look again at what you might want to try out.
While you can generally upgrade your data from one Android release to the next using a tool like Titanium Backup, going back is dicey, at best. I didn't decide to upgrade my day-today phone from GB to ICS for quite some time after the ROMs were available for just that reason. I'd hate to find out that there was a show-stopper bug and I couldn't go back to GB without losing my data.
Click to expand...
Click to collapse
That makes sense I'll wait for slim kat until the bugs have been fixed and until I get the hang of this.SO just to be certain I should start from ics then move up to jelly bean?

It's my personal opinion that the GB and ICS ROMs are the most stable and reliable for "daily driver" phones. Others like the JB experience. KitKat has a lot of potential, but I'd wait a bit until it settles down. The first few releases on any new Android version are generally a bit rough, even when from the best of devs.
The AntonX Basic kernel from the heimdall one-click thread should get you what you need to get started.
I'm a little puzzled though, how you flashed the first ROM if you didn't have CWR or some other recovery already installed. If it was ROM Manager that you used, it definitely would have caused problems (and will if you use it again).

jeffsf said:
It's my personal opinion that the GB and ICS ROMs are the most stable and reliable for "daily driver" phones. Others like the JB experience. KitKat has a lot of potential, but I'd wait a bit until it settles down. The first few releases on any new Android version are generally a bit rough, even when from the best of devs.
The AntonX Basic kernel from the heimdall one-click thread should get you what you need to get started.
I'm a little puzzled though, how you flashed the first ROM if you didn't have CWR or some other recovery already installed. If it was ROM Manager that you used, it definitely would have caused problems (and will if you use it again).
Click to expand...
Click to collapse
Ok I will try this right now see if I can even follow the tutorial and I got valhalla by using sgs kernel flasher which is an app on the marketplace.

jeffsf said:
It's my personal opinion that the GB and ICS ROMs are the most stable and reliable for "daily driver" phones. Others like the JB experience. KitKat has a lot of potential, but I'd wait a bit until it settles down. The first few releases on any new Android version are generally a bit rough, even when from the best of devs.
The AntonX Basic kernel from the heimdall one-click thread should get you what you need to get started.
I'm a little puzzled though, how you flashed the first ROM if you didn't have CWR or some other recovery already installed. If it was ROM Manager that you used, it definitely would have caused problems (and will if you use it again).
Click to expand...
Click to collapse
ok so I decided to go for slimkat 4.4.2 and I actually installed it correctly but I don't have the google play store and all that I tried to install gapps but not sure if I had the right version. When I was flashing them it said installation successful but when the phone rebooted it says the applications stopped working.

MuShRo0m said:
ok so I decided to go for slimkat 4.4.2 and I actually installed it correctly but I don't have the google play store and all that I tried to install gapps but not sure if I had the right version. When I was flashing them it said installation successful but when the phone rebooted it says the applications stopped working.
Click to expand...
Click to collapse
Hullo man (or mam) I'm the tooth cavity bringer as u can see (w kitkat or sth like that). For your issue, I think you first should get used to installing custom ROM on this phone first, with Recovery: backup & restore procedure, flashing zip,... and heimdall oneclick procedure as jeffsf has been avised you tho before installing kitkat. And yeah, a user got Playstore work out by heimdall oneclick back to stock, and follow my instruction in the slimkat thread again carefully (super clean install) so you can try if you know what you are doing then.
If you are feeling confused and frustrated w the instruction and bugs that might happen to your phone, you can/should flash sth considered stable first like ICS ROMs (that Jeffsf recommended) w Jeffsf's kernels as they are easier to flash and almost bug-free .
Sent from my GT-N7000 using Tapatalk 2

daothanhduy1996 said:
Hullo man (or mam) I'm the tooth cavity bringer as u can see (w kitkat or sth like that). For your issue, I think you first should get used to installing custom ROM on this phone first, with Recovery: backup & restore procedure, flashing zip,... and heimdall oneclick procedure as jeffsf has been avised you tho before installing kitkat. And yeah, a user got Playstore work out by heimdall oneclick back to stock, and follow my instruction in the slimkat thread again carefully (super clean install) so you can try if you know what you are doing then.
If you are feeling confused and frustrated w the instruction and bugs that might happen to your phone, you can/should flash sth considered stable first like ICS ROMs (that Jeffsf recommended) w Jeffsf's kernels as they are easier to flash and almost bug-free .
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
thanks for the suggestions I installed slimkat but I didn't have the play store because I forgot to flash the gapps now I finally got everything working it runs pretty smooth. I wanted to challenge myself so I chose the harder one and I did okay.