Related
My phone (model 1007) had been rooted and running Serendipity. All was well until I had trouble with phone calls. So I unrooted and reflashed to stock. I reformatted and it was like brand new, out the box. I didn't have the time to reroot so I kept it clean. I pressed on 'update' on the settings menu (was that stupid of me?) and it just shut down. So NOW,
I can't turn it on! My phone starts to turn on but just shows this little spinning circle and the screen goes black. I can get into download and recovery though, so that's good right?
The phone will only charge. The very FEW times I actually got it to turn on the phone said that the USB was connected when it wasn't!
Could someone please, please help me?
Also, this is a phone from the warranty dept. It's refurbished because my other Captivate wouldn't turn on (I'm just having some sucky luck, right?)
So am I still able to return it? It's been less than 90 days i got it and has never been in contact with water or dropped. In fact, I always cradle it in a nice case.
I'm just terrified of the horror stories I've heard about Samsung warranty dept and AT&T's warranty dept. I don't want to give it to them to have some crazy $500 charge, you know? I think I don't have anything to worry about but it just freaked me out.
I had a similar experience, but mine caught itself in a reboot loop. I wa able to get back into download mode and re-flash, fixing the issue.
Have you tried to see if it will at least go into download mode?
Sent from my SAMSUNG-SGH-I897 using XDA App
Restless101 said:
My phone (model 1007) had been rooted and running Serendipity. All was well until I had trouble with phone calls. So I unrooted and reflashed to stock. I reformatted and it was like brand new, out the box. I didn't have the time to reroot so I kept it clean. I pressed on 'update' on the settings menu (was that stupid of me?) and it just shut down. So NOW,
I can't turn it on! My phone starts to turn on but just shows this little spinning circle and the screen goes black. I can get into download and recovery though, so that's good right?
The phone will only charge. The very FEW times I actually got it to turn on the phone said that the USB was connected when it wasn't!
Could someone please, please help me?
Also, this is a phone from the warranty dept. It's refurbished because my other Captivate wouldn't turn on (I'm just having some sucky luck, right?)
So am I still able to return it? It's been less than 90 days i got it and has never been in contact with water or dropped. In fact, I always cradle it in a nice case.
I'm just terrified of the horror stories I've heard about Samsung warranty dept and AT&T's warranty dept. I don't want to give it to them to have some crazy $500 charge, you know? I think I don't have anything to worry about but it just freaked me out.
Click to expand...
Click to collapse
The OTA update ATT sent out has been known to cause these issues on some phones, Here are your 2 options. 1. Return it and get another referb. 2. Go down to your local Radio shack and get the parts for a jig, (directions in the forums. A search for Jig will get you there) and then not worry about much flashing roms from then as a Jig will work 99.9% of the time.
That is of course after you see if you can get into download mode without the jig.
lol I've tried jigs before. I suck at making them and it never worked for me. Clearly, I've been too sloppy in making them. I can get into download mode. But I've already reflashed with the same results. If I keep getting the same results I'm afraid someone will tell me I have a hardware issue.
Is the jig the only thing left to try?
Thanks soooo much for replying!
Restless101 said:
lol I've tried jigs before. I suck at making them and it never worked for me. Clearly, I've been too sloppy in making them. I can get into download mode. But I've already reflashed with the same results. If I keep getting the same results I'm afraid someone will tell me I have a hardware issue.
Is the jig the only thing left to try?
Thanks soooo much for replying!
Click to expand...
Click to collapse
Yes. Sure shot option. Worked like a charm for me
Restless101 said:
lol I've tried jigs before. I suck at making them and it never worked for me. Clearly, I've been too sloppy in making them. I can get into download mode. But I've already reflashed with the same results. If I keep getting the same results I'm afraid someone will tell me I have a hardware issue.
Is the jig the only thing left to try?
Thanks soooo much for replying!
Click to expand...
Click to collapse
Ok you can get into download mode so you should be ok. What have you been flashing?
#1 dont need a jig - just 3 resistors
http://forum.xda-developers.com/showpost.php?p=10112309&postcount=1
HINT dont touch the resistor leads with your bare fingers, it can change the resistance, especially if youre sweaty. USE TAPE on the ends
#2 if you dont think you can do that, you can buy a premade jig on ebay DELIVERED for under 10 bucks, i just ordered one for 8 just in case.
Trusselo said:
#1 dont need a jig - just 3 resistors
http://forum.xda-developers.com/showpost.php?p=10112309&postcount=1
HINT dont touch the resistor leads with your bare fingers, it can change the resistance, especially if youre sweaty. USE TAPE on the ends
#2 if you dont think you can do that, you can buy a premade jig on ebay DELIVERED for under 10 bucks, i just ordered one for 8 just in case.
Click to expand...
Click to collapse
use this one buddy and be patient with it. it works if you need help you can pm me cause ive been there before.
So I was flashing the steam kernel and it failed using Odin. I then got the infamous pic with the cell phone-exclamation-computer. I have had this happen in the past. No prob right? I have a jig which I've used before several times and it worked. Now when I use the jig i get the same pic, not download. I tried adb. device not found. tried pluging in with both vol up and down pressed, same thing. Any suggestions? I'm hoping this is recoverable. I've even tried taking out the battery, plug in usb to comp than phone, holding down vol down button and putting back the battery. Same prob. Tried reinstalling the drivers....same prob.
The fact that your getting that image is a great sign. The jig you are using may be not functioning properly. If its a home made jig, they can easily become ineffective if you touch the resistors. That changes the resistance of the whole jig and will fail to put the phone in download.
Sent from my SAMSUNG-SGH-I897 using XDA App
It's a jig I bought of ebay. It's worked several times in the past.
I soft bricked and got that picture. When I plugged into Odin one click it lit up, and I flashed back to stock. It didn't do it the first time. I opened Odin, plugged in, and held all three buttons, as it looped. After two or three loops, it recognized in Odin, and I was able to restore to stock.
I tried what I was flashing in the first place, and soft bricked again, this time no matter what I did Odin was no go, but I was able to fix with a jig.
Give Odin a try. Others have had that too: phone!computer working as download mode.
Sent from my Captivate running Continuum 5.5
quarlow said:
I soft bricked and got that picture. When I plugged into Odin one click it lit up, and I flashed back to stock. It didn't do it the first time. I opened Odin, plugged in, and held all three buttons, as it looped. After two or three loops, it recognized in Odin, and I was able to restore to stock.
I tried what I was flashing in the first place, and soft bricked again, this time no matter what I did Odin was no go, but I was able to fix with a jig.
Give Odin a try. Others have had that too: phone!computer working as download mode.
Sent from my Captivate running Continuum 5.5
Click to expand...
Click to collapse
Quarlow, you are AWESOME!!!!! Got it to stock again. Didn't use oneclick cuz this build is a 1010 build, so i've been apprehensive about using it, so instead I used Odin 3 v1.52 and used ucjh2 in the pda and 512 pit and repartitioned. Odin recognized the phone even though I had the phone!comp thing going on. First time it failed so I tried again and it worked perfectly. Thanks much my friend, I would've never thought to just try it without having download and the shoveling droid.
I hear about all this JIGS being used, why is it that I dont ever need to use one??? IM GLAD I DONT THOUGH
I hear about all this JIGS being used, why is it that I dont ever need to use one??? IM GLAD I DONT THOUGH
Click to expand...
Click to collapse
If you haven't soft bricked yet then your not flashing enough then I haven't needed mine in quite a while but it is worth it to have around for sure rather than when it happens and you struggle to build one or wait to buy one for a few days/week. Cheapest insurance to have around.
Plus I think most roms have progressed enough that is less common to have bugs in them that would soft brick the phone. But maybe 6-8 months ago with trying out all the different 2.1 and 2.2 roms it was bound to happen. If it wasn't for me getting soft bricked on occasions and learning how to recover from it I wouldn't of learned half what I think I know...
Sent from My KickAss Captivated CM7 OC'd 1.55Ghz/Undervolted
Since I updated to 2.3 with the GB bootloaders I have not needed my jig. I put one together from a spare cord and 2X150k resistors - worked great when I needed it.
I'm on vacation now and want to flash something but dont have my jig...you know how that goes when you need it most...
RockRatt said:
If you haven't soft bricked yet then your not flashing enough then I haven't needed mine in quite a while but it is worth it to have around for sure rather than when it happens and you struggle to build one or wait to buy one for a few days/week. Cheapest insurance to have around.
Plus I think most roms have progressed enough that is less common to have bugs in them that would soft brick the phone. But maybe 6-8 months ago with trying out all the different 2.1 and 2.2 roms it was bound to happen. If it wasn't for me getting soft bricked on occasions and learning how to recover from it I wouldn't of learned half what I think I know...
Sent from My KickAss Captivated CM7 OC'd 1.55Ghz/Undervolted
Click to expand...
Click to collapse
Dude, believe me, i flash like no one you have ever seen, I'm just smart enough not to brick it and if i do, i dont need a jig, my phone has always gone into download mode no prob!
Sent from my Captivate Rocking MIUI!
Through one of my flashing...bricking...odin one clicking I lost my bootloaders that gave me the ability to hold buttons and get into DL or recovery mode. This was all while playing around with 2.1 - 2.2. Since going to 2.3 the button method has always worked...although I still keep the jig handy...just in case...
b-eock said:
Dude, believe me, i flash like no one you have ever seen, I'm just smart enough not to brick it and if i do, i dont need a jig, my phone has always gone into download mode no prob!
Sent from my Captivate Rocking MIUI!
Click to expand...
Click to collapse
I'll keep an eye out if you ever hard brick... . Bricking is typically a part of flashing. Very highly recognized DEV's have PM'd me after hard bricking. There's no shame in it as it happens every now and then.
REMY4223 said:
I soft bricked my older Captivate, but was able to Odin back to stock then to Froyo via Kies. Since I was back to stock I tried the following after reading that ATT was replacing older Captivates.
Just letting everyone know who has a Galaxy S phone. I called ATT (6/21/11)and let them know that my phone has random shutdowns (once monthly), they checked the EMIE (I think that is what it is called) # on the phone, and they are replacing at no cost. I currently have a remanufactured (30 day warranty)1006 build I purchased Oct. 2010. My new SGS is shipped.
Click to expand...
Click to collapse
Remy, Please stop spamming the board. I see that you're excited to let everyone else know about what you were able to do, but you've replied with the exact same message in more than 10 different threads. This behavior will likely end up with some pretty serious repercussions if you continue.
connexion2005 said:
I'll keep an eye out if you ever hard brick... . Bricking is typically a part of flashing. Very highly recognized DEV's have PM'd me after hard bricking. There's no shame in it as it happens every now and then.
Click to expand...
Click to collapse
I still haven't bricked, but I got Adam to do the unbrickable mod for me! Haven't needed it yet.
Sent from my I897 using xda premium
[Tutorial][Bell Atrix]What need to be done before Warranty Service?
It applies all the Bell Atrix, doesn’t matter you have Orange FR 2.1.1 or UK 2.2.3 on the phone or whatever
Simple Version:
Make sure you have CWM Recovery on it(http://forum.xda-developers.com/showthread.php?t=1019143)
Download the stock system.img (http://www.multiupload.com/T6L5RS2WH1), if you have the backup by nandroid, you can skip this step
Enter CWM Recovery to restore system.img only, then do Wipe out Data&Cache, or Force Close will be with you!
Install GingerBreak to root your phone, you can download from here: http://forum.xda-developers.com/showthread.php?t=1044765
Install CMW Recovery again, but this time, choose CHARGE MODE in order to uninstall the custom recovery
Use GingerBreak to un-root the phone
Do a factory again, then you are ready to throw this phone to any Bell Retail Store for repair
Just remind that Bell will take 4~6weeks to get your phone fixed, if you need a loaner phone, it’s $25+tax, ask before borrow since some store doesn’t even have smartphone to lend…
Full Detail Version coming soon...
Thanks, good tut to have.
Stock Bell Atrix on Rogers with updated radio, Rooted, deodexed, Honeycomb theme, and frozen!
With glad root and webtop mod on stock firmware would it be ok to just return the stock web top files and unrooted for warranty?
Why wouldn't you just a sbfflash...?
Sent from my MB860 using Tapatalk
hoodlikegaza said:
Why wouldn't you just a sbfflash...?
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Because there is no Bell SBF available (to date)
scorneil said:
Because there is no Bell SBF available (to date)
Click to expand...
Click to collapse
Yes, but in your tutorial you're just removing root access and custom recovery. You're not changing the firmware from the phone back to 0.3.7 (Bell firmware) because there isn't a Bell SBF to flash (you're right about that). If one was already running 2.1.1 or 2.2.3 with root access, they could simply reflash their respective SBF's and it would produce the same results as your tutorial. Maybe I'm missing something from your guide, but as far as I understand, once you've flashed a different SBF, there is no way of getting back to official Bell. Your guide seems to be a roundabout way to get back to stock 2.1.1 or 2.2.3 for warranty purposes, while a simple reflash would produce the same results.
thegregulator said:
Yes, but in your tutorial you're just removing root access and custom recovery. You're not changing the firmware from the phone back to 0.3.7 (Bell firmware) because there isn't a Bell SBF to flash (you're right about that). If one was already running 2.1.1 or 2.2.3 with root access, they could simply reflash their respective SBF's and it would produce the same results as your tutorial. Maybe I'm missing something from your guide, but as far as I understand, once you've flashed a different SBF, there is no way of getting back to official Bell. Your guide seems to be a roundabout way to get back to stock 2.1.1 or 2.2.3 for warranty purposes, while a simple reflash would produce the same results.
Click to expand...
Click to collapse
absolutely true.
best chances for full repair is flash stock SBF 2.2.3 and then if you really wanna get technical, simply edit your prop file for cosmetic purposes.
NFHimself has this crazy way of flashing close to stock images but thats pretty much retarded as there's no point as it really doesnt mean any closer to stock than this crap and is fickle/easy to detect as it is if Motorola was looking for it.
thegregulator said:
Yes, but in your tutorial you're just removing root access and custom recovery. You're not changing the firmware from the phone back to 0.3.7 (Bell firmware) because there isn't a Bell SBF to flash (you're right about that). If one was already running 2.1.1 or 2.2.3 with root access, they could simply reflash their respective SBF's and it would produce the same results as your tutorial. Maybe I'm missing something from your guide, but as far as I understand, once you've flashed a different SBF, there is no way of getting back to official Bell. Your guide seems to be a roundabout way to get back to stock 2.1.1 or 2.2.3 for warranty purposes, while a simple reflash would produce the same results.
Click to expand...
Click to collapse
You are right, however stock system.img(from original bell firmware, not 2.1.1 or 2.2.3) already has the right prop file and bell bloatware, comparing 2.1.1 or 2.2.3, im too lazy to look for bloatware and changing by root. this seems the easiest way for me.
other than the radio version, i dont think motorola could find out this is flashed Atrix but anyway, I am still waiting for my atrix back
ks2hot4u said:
With glad root and webtop mod on stock firmware would it be ok to just return the stock web top files and unrooted for warranty?
Click to expand...
Click to collapse
better do a factory reset and unroot
I work for bell. and all I have to say about this thread is that it should be closed and deleted. I actually thought these kind of guides were frowned upon...
If the phone was working 100% before you starting screwing with it, we shouldn't have to honor your warranty. Thats why ROOTING VOIDS Warranty.
If you screw up your windows load, Best buy doesn't say, heres a new pc. They say, here's a bill for the techie. We work on commission in these stores, and i hate wasting my time with some moron who shouldnt have screwed with what he couldn't fix. /rant
Its annoying to deal with people who brick their phones, and then give bs excuses as to why its not working. I usually do my best to help people, but its better to tell us the truth and have us help, then lie through your teeth that its a problem with the device.
It costs me extra hours of work to deal with DOA phones, and it costs everyone including motorola tons of $$$ for stuff that is screwed up by the consumer.
Why can't the people who don't know what theyre doing, leave the dangerous stuff to the guys who know how to fix their own problems?
Edit: the exception to this is true hardware issues. But those don't seem to come up all too often with this phone, just battery life issues.
But thats the thing if you brick your device, this guide won't help as the phone is a brick.
As for hardware issues, this is the exact reason for this thread IMHO, something useful to me as my fingerprint reader is slightliy off physically which results in the device thinking that fast swipes are taking place when they are not. now I can use this when I am ready to take my device in without being harrassed about software.
With my N1 even with the bootloader unlocked they still took in the device if it was proven to be a hardware defect (again had a problem with my power button - just my luck i guess) Doubt bell would do the same.
binary110 said:
I work for bell. and all I have to say about this thread is that it should be closed and deleted. I actually thought these kind of guides were frowned upon...
If the phone was working 100% before you starting screwing with it, we shouldn't have to honor your warranty. Thats why ROOTING VOIDS Warranty.
If you screw up your windows load, Best buy doesn't say, heres a new pc. They say, here's a bill for the techie. We work on commission in these stores, and i hate wasting my time with some moron who shouldnt have screwed with what he couldn't fix. /rant
Its annoying to deal with people who brick their phones, and then give bs excuses as to why its not working. I usually do my best to help people, but its better to tell us the truth and have us help, then lie through your teeth that its a problem with the device.
It costs me extra hours of work to deal with DOA phones, and it costs everyone including motorola tons of $$$ for stuff that is screwed up by the consumer.
Why can't the people who don't know what theyre doing, leave the dangerous stuff to the guys who know how to fix their own problems?
Edit: the exception to this is true hardware issues. But those don't seem to come up all too often with this phone, just battery life issues.
Click to expand...
Click to collapse
who would use this for anything other than a hardware issue? anyone who can follow this guide can also follow a SBF flash instruction to solve their software issues
binary110 said:
I work for bell. and all I have to say about this thread is that it should be closed and deleted. I actually thought these kind of guides were frowned upon...
If the phone was working 100% before you starting screwing with it, we shouldn't have to honor your warranty. Thats why ROOTING VOIDS Warranty.
If you screw up your windows load, Best buy doesn't say, heres a new pc. They say, here's a bill for the techie. We work on commission in these stores, and i hate wasting my time with some moron who shouldnt have screwed with what he couldn't fix. /rant
Its annoying to deal with people who brick their phones, and then give bs excuses as to why its not working. I usually do my best to help people, but its better to tell us the truth and have us help, then lie through your teeth that its a problem with the device.
It costs me extra hours of work to deal with DOA phones, and it costs everyone including motorola tons of $$$ for stuff that is screwed up by the consumer.
Why can't the people who don't know what theyre doing, leave the dangerous stuff to the guys who know how to fix their own problems?
Edit: the exception to this is true hardware issues. But those don't seem to come up all too often with this phone, just battery life issues.
Click to expand...
Click to collapse
QFT, but......we are referring to hardware isssues here, not software.......and rooting has nothing to do with that.
Sent from my Blue Myst GladiAtrix on Bell using the XDA Premium App.
I agree, its totally cool for hardware issues, but i'm thinking about the guys who have the lower half of the touch screen not working because they screwed the software up. 9/10 issues with any smartphone is software related.
binary110 said:
I agree, its totally cool for hardware issues, but i'm thinking about the guys who have the lower half of the touch screen not working because they screwed the software up. 9/10 issues with any smartphone is software related.
Click to expand...
Click to collapse
since no one seems to be able to replicate this issue (to my knowledge) that would imply that it IS hardware related and not software
Rediculous
binary110 Your completly in the dark if you think this phone or any other smartphone wont have defects and hardware malfunctions.
My Atrix has wicked bad screen response when plugged into any power source with stock charger or other... im not returning mine as this is a minor issue. Although my roomates cant hold gps, drops calls constantly, misses calls and msgs for lack of signal and has constant reboots since stock with only root to obtain webtop mod.
So according to your logic he dosent deserve to have his 500+ $ phone replaced cuz it will cost motorola money and your lazy ass some commision ??
THIS IS THE WRONG FORUM FOR YOU !
binary110 Your completly in the dark if you think this phone or any other smartphone wont have defects and hardware malfunctions.
My Atrix has wicked bad screen response when plugged into any power source with stock charger or other... im not returning mine as this is a minor issue. Although my roomates cant hold gps, drops calls constantly, misses calls and msgs for lack of signal and has constant reboots since stock with only root to obtain webtop mod.
So according to your logic he dosent deserve to have his 500+ $ phone replaced cuz it will cost motorola money and your lazy ass some commision ??
THIS IS THE WRONG FORUM FOR YOU !
Click to expand...
Click to collapse
I never said the phone was not capable of being defective. I said that when someone brings it in for an issue that they caused themselves. The phones are more often screwed up by a customer, than they are actually defective.
90% of the charger issues are from using a charger different than the motorola one that came with the phone. Especially the ones with the screen response. I noted it on my atrix as well. I also have replaced a customers phone for this.
This IS a valid reason to replace the phone.
But this is also easily noticeable BEFORE you go through the process of rooting/modding the phone. and as such, you should take it up with the place your purchased it before modding it.
Its like buying a car, ripping the engine apart right away. only to find that it runs like crap after you've ripped it apart... You probably should have done a test drive before purchasing. Do you understand what i mean?
Furthermore, your friend has a legitimate issue, I'm talking about people who brick their phones and play stupid. As well, I can tell you're a part of the generation who feels they're entitled to everything under the sun from the carrier you deal with. Yet, no cable company fixes your damn television. And especially not if you screw it up yourself.
Its not apples to apples, in the sense that the cable company doesn't subsidize your tv. but even if you got a tv as a promotion through them, they'd send you to the manufacturer. Which is what i'd prefer to do with people who do stupid stuff and want it fixed.
Don't act like my time isnt worth money just because youre a needy consumer. What i'm saying is just man up, tell us you screwed it up, and we will do everything we can help.
For you to be trolling the way that you are, its obvious that this ISNT THE FORUM FOR YOU.
Thank you.
By the way, Watch your language on the forums.
seven2099 said:
absolutely true.
best chances for full repair is flash stock SBF 2.2.3 and then if you really wanna get technical, simply edit your prop file for cosmetic purposes.
NFHimself has this crazy way of flashing close to stock images but thats pretty much retarded as there's no point as it really doesnt mean any closer to stock than this crap and is fickle/easy to detect as it is if Motorola was looking for it.
Click to expand...
Click to collapse
Uhm, what? How did I get dragged into this PMS fest?
Ridiculous.
Be nice guys... We are all Canadian, we love peace, don't we?!
In my case, my touchscreen's digitalize is 100% broken, it's either hypersensitive or non-sensitive at all... It happened on Bell Stock rom but I was trying to flash sfb to see if it could be fixed...
Unfortunately, i got my repair back today and still the same issue, i asked the bell staff to try the touchscreen and she said the phone is not boot up properly...
Oh well, after 90s, I ask her to try again, she clicked "BACK" 10 times in order to get back, and 5 times to run Bell Self-serve
well, I really unsatisfied with the result and I had to left the phone there and waiting for another 2 weeks, AGAIN!!!
I have 3yr contract with Bell so it has to waste time and money to get my phone fixed cuz its carelessness and impatience are wasting my money and time... The $30 loaner phone sucks and cannot even been changed...
well, looks like a little away from the topic but I've just out of the store...
even according to the repair menu, the bell stock sbf has been applied on and change of the part which i know its not the digitalize, the phone is still unusable...
AT&T users are lucky since they have their own stock sbf to flash when they wanna a repair but poor Bell users they have to use those tutorials like mine to do repair, OR UNLOCK THE BOOTLOADER AND I WONT ASK FOR WARRANTY
btw, maybe that's the reason why Apple is cool, they can get your iPhone replaced in maximum 60min not 60days even there is just a dust in screen
NFHimself said:
Uhm, what? How did I get dragged into this PMS fest?
Ridiculous.
Click to expand...
Click to collapse
see what you caused?
jk
I understand where binary was coming from but again this thread isn't for that reason. At the same time I bet we can all say we wish carriers like bell and rogers were completely full of staff like you that come with the line we will do whatever we can to help. most times reps come off as just going through the motions or looking for whatever reason to close the case.
Hey all,
I was trying to flash from stock (I897UCKF1) to 2.3.3 (I897UCKF1), which were both flashed using Odin. Partway through the 2.3 flash, it froze (which has happened to me many times before), so I disconnected my phone and pulled the battery. Now I've got what seems to be a hard brick; I've tried every button combination I can find and nothing will force it into download.
Would a jig help me here? If not...would I be able to send it into samsung, considering it's still under warranty (I could even throw in an "I dunno what happened, I was just doing the official update!")? I'm really hesitant to drop the money for a jtag, but I will if I must.
Any help is appreciated.
Jarvill said:
Hey all,
I was trying to flash from stock (I897UCKF1) to 2.3.3 (I897UCKF1), which were both flashed using Odin. Partway through the 2.3 flash, it froze (which has happened to me many times before), so I disconnected my phone and pulled the battery. Now I've got what seems to be a hard brick; I've tried every button combination I can find and nothing will force it into download.
Would a jig help me here? If not...would I be able to send it into samsung, considering it's still under warranty (I could even throw in an "I dunno what happened, I was just doing the official update!")? I'm really hesitant to drop the money for a jtag, but I will if I must.
Any help is appreciated.
Click to expand...
Click to collapse
Before you do anything, does the phone show any signs of life at all? Lights come on, makes sounds, levitates several inches off the floor, etc? If you can get it to respond in any way, it's most likely not bricked, just "clay".
If you're in a clay state, you can most likely use a jig (make your own or buy one) to get into download mode and get rolling again.
If it's totally lifeless, JTAG or warranty service are pretty much your only options.
Nope, this one is actually 'bricked.' No lights, no noise, just that damned solid black screen.
Jarvill said:
Nope, this one is actually 'bricked.' No lights, no noise, just that damned solid black screen.
Click to expand...
Click to collapse
If you're under warranty, you could send it back to samsung and hope for the best. There's a monetary risk involved with that, but your other choice is mobiletechvideos (connexion2005) and the $50 Jtag service.
So it's either maybe pay a lot, or definitely pay less.
jmtheiss said:
If you're under warranty, you could send it back to samsung and hope for the best. There's a monetary risk involved with that, but your other choice is mobiletechvideos (connexion2005) and the $50 Jtag service.
So it's either maybe pay a lot, or definitely pay less.
Click to expand...
Click to collapse
att let me keep my old one at no cost. happened in the middle of may.
they sent me one with a blemished screen so im going to eventually pay to jtag my old one and use it as a primary and keep the new one as a backup.
jmtheiss said:
If you're under warranty, you could send it back to samsung and hope for the best. There's a monetary risk involved with that, but your other choice is mobiletechvideos (connexion2005) and the $50 Jtag service.
So it's either maybe pay a lot, or definitely pay less.
Click to expand...
Click to collapse
Thanks for the help. Do you have an idea of what I might've done wrong so I don't do it again?
Jarvill said:
Thanks for the help. Do you have an idea of what I might've done wrong so I don't do it again?
Click to expand...
Click to collapse
It sounds like the bootloader flashing was borked. One of a couple scenarios is currently in place:
1. Mismatched bootloaders (froyo or eclair and GB bootloaders)
2. Corrupted bootloader (one or both)
When Odin was pushing bootloaders to your phone and froze, something didn't completely write, and now the phone can't reach the necessary stages to continue the boot process.
You may want to read up here, as this poster does a really good job of explaining all of this.
My understanding is that JTAG physically connects to the motherboard of the phone and pushes correct bootloaders over whatever is there now.
To prevent this in the future, make sure you have a computer that has a solid power connection, a solid USB cable that has shown it works properly on smaller, non-dangerous flashes, and a good download of whatever rom you're flashing.
And if at all possible, don't pull the cable when you're doing any sort of bootloader flashing (basically jumping to or from gingerbread bootloaders).
For the cost of 3 small resistors, it's worth a shot to build your own jig.
Many people have had good luck that.
Sent from my GT-I9000 using XDA App
Sometimes it will help if you keep the battery out of it for 5 mins, or press the Download Mode button combo for 30 seconds.
Sent from my GT-I9000 using Tapatalk
Don't forget to try gb button combos and eclair button combos.
mrhaley30705 said:
Don't forget to try gb button combos and eclair button combos.
Click to expand...
Click to collapse
he was flashing KF1, the captivate gb. that has the same button combos, its only the I9000 bootloaders that have different (better) combos.
Had the same thing happen to me last night. Mine at least shows life. Froze up while trying to upgrade to 2.3.3. None of the button combos do anything but bring up the Phone <!> PC death screen. Bought the resistors for a jig today, it turned the phone on but right to the death screen again. Any ideas? Guessing jtag is my only option now...
thats not a death screen that is the "flash incomplete" screen, when odin freezes before it writes the image for the download mode screen that screen is all that is there when download protocol is initiated. use the jig and if odin sees it from that screen try flashing from where is is.
studacris said:
he was flashing KF1, the captivate gb. that has the same button combos, its only the I9000 bootloaders that have different (better) combos.
Click to expand...
Click to collapse
You are correct. Had a brain fart here.
So I was on atomic fusion and tried to flash another gb rom. Somewhere during the odin process it seemed to be stuck and I stopped it and tried again to get a red screen of death. I tried everything to get to d/l mode but nothing. So I called att and I have about a week left in my warranty so I went that route. Am I gonna be charged 400 dollars when they find out I was rooted with roms not theirs? I'm really nervous, I should have never flashed to gb, its to freeking complicated for me to understand all the bootloading and kernal stuff. Any thoughts or experiences to help ease the pain? Thanks
Prolly shouldn't have flashed if you weren't confident. In yourself.
Sent from my SGH-I897 using XDA Premium App
If your phone shows any signs of life they will most likely be able to tell that you are not stock.
Your fine, I did the same thing as you are doing. I just acted like a clueless idiot and they never suspected a thing, but it was with Rogers not AT&T.
Sent from my Galaxy S Firefly 3.0
For all the topics asking this question I'm yet to see anyone come back saying that they have been refused, or charged extra after a new one is already sent out. In all likely hood they don't even check because they don't really care. If it is a hardware issues they are gonna have to swap pieces or even the main/motherboard which will come with stock pre-loaded at factory. If it is software they will just use what ever method they designed into the phone to force rewrite over what was in there before.
Now if you were taking it to a service center, where they are going to take a look in hopes of getting that very phone back into a working condition then maybe... just maybe. But if the phone does not boot then they are just gonna add it to the rewrite pile and give you a referb (or new if you ask nicely enough). This is why they always say "you might lose all your data so make a backup before hand."
Thanks, that makes me feel better, now all I have to do is survive a couple days without it. I won't be making that mistake again. What did I do wrong? I had no problem going from phoenix ultimate to atomic fusion. I was gonna try to go to cog5, I thought I was doing it right. All I did was use the odin that it said to use and it seemed to be stuck. What do you do when it freezes up during the odin process? Are you screwed no matter what you do? Should I have used the odin that takes you to stock 2.1 first? I'm really trying to understand all this but there's just so many ways about everything.