Related
I've had my fascinate for about 3 weeks and I rooted it and overclocked. I flashed a 2.2 rom that was for a I9000 because my buddy said it worked on his captivate. When it come back on after reboot the screen said galaxy s I9000 and that's it it just kept running that and nothing else. I could get into factory recovery but I can't do anything from there except reboot. and it won't flash update zip either. I will go into download mode and I tryed odin restore now it just has samsung across the screen. Am I bricked cuz I can't get anything to work?
Oh now I've manage to get into CWM recovery but it won't let me apply any zip files or restore any back ups, is that vodoo messing things up?
So you flashed a ROM that isn't compatible with your phone? And you are suprised that it broke?
As for downgrading you might try to find the stock image via: hxxp://forum.xda-developers.com/showthread.php?t=782204&highlight=odin
If that doesn't work you better figure out a good excuse for the Verizon store...
Good luck!
frostysax said:
Oh now I've manage to get into CWM recovery but it won't let me apply any zip files or restore any back ups, is that vodoo messing things up?
Click to expand...
Click to collapse
Were you running a kernel with Voodoo installed and active when you flashed the ROM?
If you're filesystem is still ext4 and you don't have a Voodoo kernel running, I'm thinking you've got a date with Odin at best.
Sent from my SCH-I500 using XDA App
Odin. I would like to think you should be able to remove it via the uninstaller listed on that page as well, ?if it is voodoo, but if you can't install anything with CWM then I know it won't work. :/ Also, did you disable voodoo first?
He was valid in trying something different... I don't believe using a ROM from another phone entirely was a good idea, but eh, now we know for sure not to do it.
Yes gentlemen I think its bricked. I have tried the odin restore, I have put the stock image on the SD card using my htc eris and put it in CWM/backup and then put the card back in the phone and tried a backup/restore it still comes up can't mount data every time it says E:Can't mount /dev/block mmcblk0p2(File exist) Can't mount data . I really don't think there's anything left for me to try fellas. I just got my service put back on the eris. If I can't get into it you can't prove its been rooted can you I still got a week left before my 30 days is up. I some wan't to experament with any solutions I am wide open before I put this in the mailbox and send it back. Thanks for your help guys but I will get me another, I guess you know what not to do now"LOL"
frostysax said:
Yes gentlemen I think its bricked. I have tried the odin restore, I have put the stock image on the SD card using my htc eris and put it in CWM/backup and then put the card back in the phone and tried a backup/restore it still comes up can't mount data every time it says E:Can't mount /dev/block mmcblk0p2(File exist) Can't mount data . I really don't think there's anything left for me to try fellas. I just got my service put back on the eris. If I can't get into it you can't prove its been rooted can you I still got a week left before my 30 days is up. I some wan't to experament with any solutions I am wide open before I put this in the mailbox and send it back. Thanks for your help guys but I will get me another, I guess you know what not to do now"LOL"
Click to expand...
Click to collapse
Oh wells... Sorry dude. Did you flash System, kernal and pit with Odin?
yes I did but nothing happened when I went to the pit file. Itook it out of m downloads put it in odin with the pit button and hit start,am I doing that right thats the only thing that I did'nt see anthing happen when I hit start. How do you fun the pit file in odin?
I ran into the same exact issue on day 1 with my Fascinate, minus flashing a ROM meant for another phone. I could boot, but my phone wiped to factory at every boot, and I couldn't even run the ota. I exchanged it that same day, and no troubles since. Good luck.
Sent from my Fascinate using the XDA app
you flashed your radio...it's bye bye... Go to verizon and try to blame it on the ota after you flash back to stock...
If you don't know what your doing.... dont do it... That is the number one rule in flashing roms....
Ya well I guess its an expensive paperweight now.I will take your advise and blame it on the OTA. I odered this one over the phone so they have to mail me another one no matter what. You live and learn and that was a great lesson on what never to do. Thanks for all your help I still have my eris to play with for now,I'm running nonsensikal froyo. Perhaps I will zip a new rom on that"LOL"
frostysax said:
Ya well I guess its an expensive paperweight now.I will take your advise and blame it on the OTA. I odered this one over the phone so they have to mail me another one no matter what. You live and learn and that was a great lesson on what never to do. Thanks for all your help I still have my eris to play with for now,I'm running nonsensikal froyo. Perhaps I will zip a new rom on that"LOL"
Click to expand...
Click to collapse
1: If you're going to mod your phone, you should have insurance, and be prepared to use it.
2: "Blaming it on the ota" just makes everyone suffer. You think that $600 phone will just pay for itself? Not likely. Consumers end up footing the bill, every time. And, in turn, companies like Motorola place E-fuses in their phones to prevent this very thing from happening to cover their bottom line, which in turn affects the modding community too by reducing access to devices.
3: Those phones do get tested when returned. They can/will see that it doesn't have proper software in it when they go to refurb it. And they have no problem charging your account for an out-of-warranty exchange after the fact.
Normally I would agree.... but...
1.they charge 600 dollars for a phone that is not worth 600.
2. There wouldn't be a problem if they didn't hold back the release of a new ota. (With a new update these phones are easily fixable.)
3. They over charge cellphone service. And add 300 dollar cancellation fees.... come-on they don't mind screwing us... screw them.
Sent from my SCH-I500 using XDA App
There is no excuse for fraud. This is 100% user error. Own up and pay for your choice to ignore the big warning at the top of every flashing thread.
Sent from my Voodoo-powered Fascinate with XDA
Are you serious. I just paid AT&T $300 dollars to cancel an expensive contract just to go to verizon and end up paying more. If you think the phone company is suffering you are sadly mistaken my friend. I have two phones on my contract and pay right at $250 a month, they ain't hurtin for money. I tell you what, if you bricked your phone and it was within your 30 days, now be honest would you call them and say hay I just voided my warrenty and I need to pay for this phone and give you more money for another one or would you try and come up with something else to say. It could happen to you
I do not believe you are bricked. Follow all instructions for odin and also fix the mbr using original.mbr or the program provided by adrynalyne.
Ethics aside, flashing a rom should not brick your phone. Unless you used Odin, and pushed the "radio" button, it can be fixed. Adrynalyne's voodoo removal fix should fix almost any phone problem. http://forum.xda-developers.com/showthread.php?t=804784
Try it and see if it works.
what is "mbr "I have not tried that yet and where would I find info on it? What roll does the pit file play in odin restore? is there a certain way to do the pit file? Everything flashed but when I got to the pit file put in odin and hit start nothing happens is that normal? Anymore feedback I will anything at this point, Thanx guys,
Pit is for partition mapping. Mbr is master boot record. From what I saw in one of your earlier posts it looks like your mbr is messed up. Use adrynalynes guide in the post linked to you above by Sgtmack.
I went to the above web site and downloaded the stock kernal but when Iwent to download the mbr file it sent me to a web page with almost nothing on it. again I ask when I do the pit file in odin can someone give me step by step cuz I feel like I 'm doing something wrong here.
[EDIT 3] Worked fine, finally, thanks for all the help.
[EDIT 2] Yeah, I don't know how it happened or what happened, but I got a lot further. I started to get Odin failing at recovery and then remembered this thread which I found earlier: http://forum.xda-developers.com/showthread.php?t=907261&page=2
Basically did it exactly like how the OP fixed it, and the phone is currently being flashed.
But now I have a different problem, seems I can't get a break.
http://img651.imageshack.us/i/stuck.jpg/
It's stuck there, should I just wait? Is it supposed to take a while? Or is there a problem? Been there for about an hour now.
[EDIT] So the phone works now, but Odin won't flash for me. What could the problem be if it's stuck on Initializing (or rather, Initialzing as the program puts it)? I've tried 1.61, 1.7, used the DI18 file and removed the md5 bit so that the file ends in .tar, etc
Hey, so I've been desperately trying to return my Epic to stock DI18, and I tried clockwork mod which didn't work, and then I tried doing it through Odin, and it kept hanging on Initializing.
Anyway, I keep trying with Odin, and ended up taking out my battery and putting it back in, but now the phone won't turn on. It doesn't turn on normally, not through download mode, not recovery, nothing.
Any help? What can I do? I tried searching but every result ends up being about turning on bluetooth or wifi, etc., and the few that are related to bricking talk about going into download mode to flash with Odin.
I hope you didn't take the battery out while flashing odin...
you can't turn it on in any way right?
can you charge it via usb? maybe you just ran out of power while flashing?
Uh, yeah, that's exactly what I did. Every time Odin would hang at Initializing, I'd have to remove the battery and restart the phone to try again.
God, I am so stupid, it is ridiculous.
The battery did have a decent amount of charge last time I checked though.
Hold down 1 and power and insert battery while holding them. That should get you into d/l mode. Taking out the battery while odin is stuck on initializing does not harm the phone.
Sent from my Bonzai'd Epic 4g.
I just did something like what you said leather, and I got it into download mode.
Now I'm afraid to do anything. Any reason why my flashing through Odin wouldn't work?
Odin is picky about the computer its running on. I used a laptop when i first started flashing..no issues ever.
Fixed my desktop and instantly ran into odin problems. Try changing USB ports and make sure youve got no firewalls running.
Sent from my SPH-D700 using XDA App
Yeah, what I don't know how it happened or what happened, but I got a lot further. I started to get Odin failing at recovery and then remembered this thread which I found earlier: http://forum.xda-developers.com/showthread.php?t=907261&page=2
Basically did it exactly like how the OP fixed it, and the phone is currently being flashed.
But now I have a different problem, seems I can't get a break.
http://img651.imageshack.us/i/stuck.jpg/
It's stuck there, should I just wait? Is it supposed to take a while? Or is there a problem? Been there for maybe 5-6 minutes now.
The factory always takes the longest; so give it time. And do NOT pull the battery at that point. Youll have to say good bye epic :<
Sent from my SPH-D700 using XDA App
How did this end up? Did it move past FACTORY FS?
Nope, still stuck in that same exact place. Is it supposed to take this long or has something gone wrong?
Could I unplug it and try again at this point, or would that brick it? It's just stuck there, what do I do? I'd love to try different usb ports and such, but I can't if I don't stop this process, just don't know how to do it without bricking it.
And thanks for the help so far.
Did you remove the. Md5 at the end of the tar file?
Sent from my SPH-D700 using XDA App
No, I put the md5 back to start from the beginning with everything as it comes from downloads and such.
What do I do about it right now though? Can I safely unplug it and restart it or...?
Seems like you have no choice but to unplug it. Removing the md5 shouldn't make a difference. Try a different USB port.
Sent from my SPH-D700 using XDA App
Yeah, thankfully it didn't brick. I feel like I'm walking through a minefield with this thing.
Anyway, switched ports, had the file renamed to end in .tar, made sure Odin was opened as administrator in Windows 7, and thankfully it flashed fine.
Now I'm back at vanilla 2.1, can start fresh in terms of upgrading, was having some problems earlier. Is that GPS locking problem present in 2.3? Assuming I put ClockworkMod 3 on it and have the file system reset to EXT4, can I just flash to 2.3 ROMs right away?
Such problems
Hi everyone,
Skip this first paragraph if you just want to read my steps from problems to solution:
I hope this post helps people who were in the same situation I was in.
A few days ago I just happened to read the news about the new gingerbread for the AT&T i997 Samsung Infuse. I read that it wasn't over the air. Because of what has been seeming as a bluetooth leak after trying everything to stop the leak up to hard resetting it, I figured I'd pray that gingerbread fixes it. So on went my quest in the last few days trying to get this gingerbread update as fast as I could.
1) I downloaded keys mini for the Samsung device which was needed for the upgrade. I installed it on my main pc which is windows 7 64 bit. After installation, it's first run, it automatically updated the application.
2) I plugged in my phone via usb and it said device not registered so I got in contact with a Samsung rep in chat who told me to register it and it would take 24 hours.
3) I registered on Samsung and waited about 48 hours and still no change.
4) Got impatient and read about GTG Ultimate unbrick which is supposed to return my stock phone back to it's out of box condition which eliminated what I thought as an error with my phone of it not being registered.
5) Now after plugging it in after the unbrick. I got a message stating "device already up to date". I kept getting this for the last couple days. Sigh
6) Read that I could download the new gingerbread stock ROM without being rooted. Just had to use the ODIN3 I got with the GTG Ultimate unbrick zip file and supply the ROM I997UCKL2-Homebinary.tar.md5 as the input file.
7) Follow basically same instructions as unbricking but not reformatting and just supplying the md5 file as the input for hte PDA button then clicking start.
8) Odin 3 message status window was stuck at setupconnection and I knew this wasnt right. It was stuck for over 15 minutes and it should only do that for a minute or less.
9) Unplugged usb and big error in red on Odin 3 (but didn't have a choice)
10) Tried removing battery and retrying the flash but now a bigger issue the screen was all colored specs or in other words multi colored spots. Rut roh!
11) After scratching my head and googling like crazy some others had the same issue and they mentioned removing the battery and trying again but didn't mention that the spots would remain on the screen while the items could be flashed fine.
12) Tried again this time it got past setupconnection but was stuck at initializing.
13) Thought to myself let me try it on my Windows Vista 32 laptop.
14) Voila. It worked. So don't give up if you see the colored spots on your screen. There still is a chance. I now have gingerbread. THANKS EVERYONE!
Next Morning Update:
I was too quick to be happy. It seems I am one of the small few who is having touch sensitivity issues and lag typing on the lower right side of the screen especially with the back key (backspace). I typed my first reply to an email and the third word in the backspace was completely disabled.
Glad you got it working.
Am i the only one when i saw "what now" immediately thought about that lead paint commercial ?
iSaint said:
Am i the only one when i saw "what now" immediately thought about that lead paint commercial ?
Click to expand...
Click to collapse
GTG Ultimate unbrick zip is missing can u re-up it plz?
Okay so - recently my I9000m went into a boot loop (during normal use - though I did have voodoo installed) and I can not access recovery mode. I could however access download mode.
I attempted to install stock firmware from samfirmware - no luck.
I attempted to install stock firmware from the forums - no luck.
I attempted to install EZBase - no luck.
I even attempted to use Virniks 'stock everything' tutorial - no luck.
After all these attempt and various other attempts involving 3 button fixes I was still having boot-loops.
So I got desperate - and I installed the Odin One Click for captivate - I know...bad idea but like I said.. I was desperate.
Now my i9000m (bell canada) starts up with the AT&T Logo and then boot loops!
The worst part is I can't even access download mode anymore! I understand that this is probably due to the fact that the buttons are remapped - keeping that in mind I tried as many key combos as I could but still get nothing but the AT&T Logo looping over and over.
So to the point.. does anyone have a surefire way to get to captivate download mode on a I9000M?
I've read about the JIG solution but I'll use that as a last resort as I would have to order the pieces (I'm not much of a solderer).
So are there any non-JIG solutions to get back to download mode/restore my phone?
All input is appreciated and I'd like to thank everyone that has tried to help me these last couple of days!
Sounds like your internal SD card is dead.
I was having similar issues where the phone would just bootloop. I re-flashed 4-5 different stock roms which all did the same thing. One of the stock roms allowed me into recovery mode, which yielded no success only a no sd card message.
I have gone ahead and sent my phone out to Bell for repair.
Viper717 said:
Sounds like your internal SD card is dead.
I was having similar issues where the phone would just bootloop. I re-flashed 4-5 different stock roms which all did the same thing. One of the stock roms allowed me into recovery mode, which yielded no success only a no sd card message.
I have gone ahead and sent my phone out to Bell for repair.
Click to expand...
Click to collapse
I'm thinking of doing the same (bringing it to bell) though I'm not sure they'll honor the warranty with it booting up with the AT&T logo, hah :<
Yeah i dont think they would service that, i was fortunate enough to get back a stock i9000m rom so it still boot up with that.
You can try contacting samsung directly to see if they will be able to repair for you, or try the jig and re-flash to stock bell rom
Viper717 said:
Yeah i dont think they would service that, i was fortunate enough to get back a stock i9000m rom so it still boot up with that.
You can try contacting samsung directly to see if they will be able to repair for you, or try the jig and re-flash to stock bell rom
Click to expand...
Click to collapse
Called samsung last night - they said I have to bring it to bell first.
Worst case scenario I'll pay sammy to fix it =/
Update: Just got off the phone with Bell, described my problem, said that I messed with the software real hard and they said that as long as I didn't remove any warranty stickers I'll still be able to get it fixed by samsung foh freeee.
Viper717 said:
Sounds like your internal SD card is dead.
I was having similar issues where the phone would just bootloop. I re-flashed 4-5 different stock roms which all did the same thing. One of the stock roms allowed me into recovery mode, which yielded no success only a no sd card message.
I have gone ahead and sent my phone out to Bell for repair.
Click to expand...
Click to collapse
I have urgued him to flash any SGS firmware with recovery image, but he didn't listen.
And yes, I think that his internal storage bus is dead.
If so, he should write down IMEI of his phone, and send email to the Samsung Korea with the info, that his internal SD card is dead. They will send him brand new phone.
But in the case he would rather use warranty service of his provider, he will need to:
a) try reboot with adb, and fastest as he can, try to issue "reboot download" command with it
OR
b) make JIG, and reboot to download mode, and reflash stock ROM
Asking Samsung Korea for new phone with IMEI sent to them do not require any of above...
EDIT: I have missed your last reply. Good to know, that Bell will fix it for you. But I do not think that they will be able to fix it. They will more likely give you new phone.
Virnik0 said:
I have urgued him to flash any SGS firmware with recovery image, but he didn't listen.
And yes, I think that his internal storage bus is dead.
If so, he should write down IMEI of his phone, and send email to the Samsung Korea with the info, that his internal SD card is dead. They will send him brand new phone.
Click to expand...
Click to collapse
I did listen - no matter how many times I tried to flash the sgs firmware w/ recovery image it would just keep booting and wouldn't enable the functionality.
As i detailed above I tried several recommended methods to re-enable the recovery mode and none of them worked.
Thanks for your help - hopefully Bell honors what they said on the phone.
Sozage said:
I did listen - no matter how many times I tried to flash the sgs firmware w/ recovery image it would just keep booting and wouldn't enable the functionality.
As i detailed above I tried several recommended methods to re-enable the recovery mode and none of them worked.
Thanks for your help - hopefully Bell honors what they said on the phone.
Click to expand...
Click to collapse
OK. Just do not panic :-D
You will get your phone back, more likely new one.
And on other hand, this result is not your fault. Some "first-line" SGS phone models has been faulty. You are not the first one with such problem.
Virnik0 said:
OK. Just do not panic :-D
You will get your phone back, more likely new one.
And on other hand, this result is not your fault. Some "first-line" SGS phone models has been faulty. You are not the first one with such problem.
Click to expand...
Click to collapse
They said they would send it to Samsung and give me a loaner until mine is back.
Not sure if they'll still honor it when I show up in person...but I'm hoping for the best.
So to give a final update:
After a couple commutes back and forth to the Bell store and a couple phone calls to Samsung it looks like I voided the warranty and I'm SOL on getting this phone repaired.
The (semi)bright side of the story is that I have an insurance policy with Bell and I'm getting a brand new SGS for $150.
Sozage said:
So to give a final update:
After a couple commutes back and forth to the Bell store and a couple phone calls to Samsung it looks like I voided the warranty and I'm SOL on getting this phone repaired.
The (semi)bright side of the story is that I have an insurance policy with Bell and I'm getting a brand new SGS for $150.
Click to expand...
Click to collapse
Little too much for a few hours of your time. If you'd reflashed stock ROM and ignored vibrant fw, as I've suggested, they would have no chance to find out what happened, and you've been given new phone for free. But you were in a hurry. Besides, your second, but in the circumstances of your haste not important misstake was, that you've told them what you have done.
Sent from my GT-I9000 using XDA Premium App
Virnik0 said:
Little too much for a few hours of your time. If you'd reflashed stock ROM and ignored vibrant fw, as I've suggested, they would have no chance to find out what happened, and you've been given new phone for free. But you were in a hurry. Besides, your second, but in the circumstances of your haste not important misstake was, that you've told them what you have done.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Exactly what I thought...you gave them extremely obvious reasons to put you at fault when you could have easily gotten a free replacement out of this. Don't answer questions that aren't asked
My father's I9000M had a failed SD and I got it replaced for free. Ironically his had a single ROM flashed on it and mine has had over 100 and been 100% fine.
chambo622 said:
Exactly what I thought...you gave them extremely obvious reasons to put you at fault when you could have easily gotten a free replacement out of this. Don't answer questions that aren't asked
My father's I9000M had a failed SD and I got it replaced for free. Ironically his had a single ROM flashed on it and mine has had over 100 and been 100% fine.
Click to expand...
Click to collapse
Btw, it does not matter how many times you'll reflash, this sd bus failure is pretty common in some first series of GT-9000 and GT-9000M
Sent from my GT-I9000 using XDA Premium App
chambo622 said:
Exactly what I thought...you gave them extremely obvious reasons to put you at fault when you could have easily gotten a free replacement out of this. Don't answer questions that aren't asked
My father's I9000M had a failed SD and I got it replaced for free. Ironically his had a single ROM flashed on it and mine has had over 100 and been 100% fine.
Click to expand...
Click to collapse
My BELL phone started up with an AT&T logo... even if I didn't volunteer the information they would have figured it out and sent me the bill.
As soon as they determine it is off warranty Samsung charges $35 dollars just to evaluate the problem and then charges you to fix it.
Yes I should have just brought it back when it first messed up but I figured my warranty was already voided due to the voodoo installation that I could not reverse (due to the boot loops).
Lesson learned.. probably won't tweak my phone too much in the future...especially if (like my last phone) I can't get into recovery mode - though I'm hoping this is fixed in the new phone I get.
Sozage said:
My BELL phone started up with an AT&T logo... even if I didn't volunteer the information they would have figured it out and sent me the bill.
As soon as they determine it is off warranty Samsung charges $35 dollars just to evaluate the problem and then charges you to fix it.
Yes I should have just brought it back when it first messed up but I figured my warranty was already voided due to the voodoo installation that I could not reverse (due to the boot loops).
Lesson learned.. probably won't tweak my phone too much in the future...especially if (like my last phone) I can't get into recovery mode - though I'm hoping this is fixed in the new phone I get.
Click to expand...
Click to collapse
$5 jig could have saved you $150
But at least you're having your phone repaired...
Kops said:
$5 jig could have saved you $150
But at least you're having your phone repaired...
Click to expand...
Click to collapse
Not repaired! New phone! Maybe even one without a faulty SD card!
Sozage said:
My BELL phone started up with an AT&T logo... even if I didn't volunteer the information they would have figured it out and sent me the bill.
As soon as they determine it is off warranty Samsung charges $35 dollars just to evaluate the problem and then charges you to fix it.
Yes I should have just brought it back when it first messed up but I figured my warranty was already voided due to the voodoo installation that I could not reverse (due to the boot loops).
Lesson learned.. probably won't tweak my phone too much in the future...especially if (like my last phone) I can't get into recovery mode - though I'm hoping this is fixed in the new phone I get.
Click to expand...
Click to collapse
The lesson you should've learn is to READ before you attempt anything.
I've flashed about anything to this phone and it's pretty hard to really brick the thing... Flashing the rom from a captivate is realy not in the line of "tweaking" rather than no-sens what so ever...
t1mman said:
The lesson you should've learn is to READ before you attempt anything.
I've flashed about anything to this phone and it's pretty hard to really brick the thing... Flashing the rom from a captivate is realy not in the line of "tweaking" rather than no-sens what so ever...
Click to expand...
Click to collapse
Right, it should be enought to use common sense, and think a little before any further action. I have tried almost anything, starting with dualboot to xubuntu linux, or editing apk's, modding and themming apps (not always successful), erasing all data partitions, created new ones, installed (or at least tried) to install gentoo linux with simple routing capability, and so on. And I'm still here.
Truth is, that some first lines of SGS were affected with faulty sd bus. But there is no need for paying warranty service, and no need to be few days without my phone. If common sense is used, then User would not:
1) install captivate firmware
2) flash anything before cwm is working
if both above fails, he'll reboot to the download mode, flashed canadian or any other fw containing Sbl.bin, alias recovery.
After that, he would flash standard stock firmware which is used by his operator. As a last thing, he would wipe sdcard from recovery.
Phone will look, behave and WILL BE same as he'd bought it.
So they will look on it, and will see standard, untouched phone, which is unknowingly rebooting itself.
Voila! They'll have no other chance then give you brand new phone right on the spot.
So for the next time, keep your mouth shut at least, when you deal with operator ;-)
Sent from my GT-I9000 using XDA Premium App
t1mman said:
The lesson you should've learn is to READ before you attempt anything.
I've flashed about anything to this phone and it's pretty hard to really brick the thing... Flashing the rom from a captivate is realy not in the line of "tweaking" rather than no-sens what so ever...
Click to expand...
Click to collapse
I wish people would read the entire thread before posting more bs like this.
Trying to put the captivate software on my phone via Odin One Click was the 10th or so thing I tried to do to restore my phone. Nothing would work - recovery mode did not work on my phone nor was I able to restore it.
Flashing the captivate software was an attempt to get recovery working (a desperate attempt) and had nothing to do with my comment about tweaking.
diaf.
I know there is nothing you can do but out is bs that you' voided' warranty. they make you pay $150 for THEIR hardware failure.
Hi guys this is just an experience sharing....
I am also one among those who bricked their phone by wiping
I was able to recover my note from brick state to working state with the help of forest1971 and hg42...special thanks to them. After recovering from brick my phone was showing some lag and it used to hang now and then..I got nearly 9.5 GB of my internal sd recovered. So I thought of giving it to samsung and getting it replaced.
I tried wiping wiping wiping with many custom roms but none bricked my phone again...Then I thought of deleting the sys partition with rm command and tried to reboot. But this time I was able to enter cwm recovery but any how it was hang at samsung logo....I was afraid that samsung may find that I have rooted my phone so I reinstalled stock GB rom and then tried to update to ics but it also failed. Then I downloaded ics stock rom and installed it with odin and used triangle away app to reset the counter. The I tried to wipe but of no use. Again I installed cwm and wiped may times but there was no problem at all. I was really surprised, I am in stock ics rom and wiping in cwm but not bricking my phone I wiped nearly 10 times but no sign of brick, my phone is working.....
At last I reinstalled my stock ics to get stock recovery and went to samsung. I told them my phone hangs now and then. There they tried to install the new ics rom and my phone bricked at that time... :fingers-crossed: Now I am waiting for replacement...they told my phone will be replaced with in 2 weeks...heheeee...
In 2 Weeks?
Hope "Samsung" will not see this thread in the meantime...
replacement in 2 weeks? that too in ernakulam? you're lucky bro. keep us updated
Thats interesting story, you dont want to brick it, it brick. Now you want to brick it, it won't. Thats funny. :laugh:
anjath said:
replacement in 2 weeks? that too in ernakulam? you're lucky bro. keep us updated
Click to expand...
Click to collapse
is that too late???? ....:crying:
JazonX said:
In 2 Weeks?
Hope "Samsung" will not see this thread in the meantime...
Click to expand...
Click to collapse
Actually a part of the reason for these type of replacement is samsung itself....it is the bug in their kernal that is making phones brick...
Any way with this experience I learned to play with my phones partitions...how to delete it, re-create it, change its size...etc.....
From my experience what I think is samsung will be able to reuse these motherboard....the technicians in these local service outlet may not be knowing how to recover from such cases, they may not even have the equipments to repair such problems. These are just a problem with the partition blocks not a major hardware issue.....I am sure that samsung can recover from such bad blocks in the partitions....
Hi guys....Today I got my note's mother board replaced after a great war....:good:
By today it is one week after I gave my note to the service center people. Today I went there to know the status. As usual it was very crowded there and there were lot of people complaining... I just showed my work sheet to one guy there and asked for status...He went inside and told me that they are loading software...I told them the complaint was not for software but for board...That guy was not knowing that I gave it for replacement, and thus accidentally I came to know the truth that they haven't even send my phone for replacement.:crying:
This made me mad and I shouted there and asked them what the hell were you guys doing for the last one week...and the war started...they tried to tell some lame excuse and I strongly argued ..... they tried to reflash my phone many times and it failed..... then I called samsung call centre and I told the whole story and I asked for the procedure to complaint againt that authorized service centre and gave them the details of that service centre. They asked me to talk with its manager which was already done and was of no use at all...Then the samsung guy told me that they will make a solution and will call in half an hour....But in 15 minute what happened was the manager of the authorized service centre was asking and searching for some board...and in some minute they told me that they are replacing the mother board. and in 45 - 60 min I got my phone with new mother board....:fingers-crossed:
Im sorry mate, can you explain exactly how did you brick your phone the first time i just want to play it safe cause in my case i have to go to my cel company and then they have to go to samsung and well im afraid they will take tooo long
thanks
Zbc said:
Im sorry mate, can you explain exactly how did you brick your phone the first time i just want to play it safe cause in my case i have to go to my cel company and then they have to go to samsung and well im afraid they will take tooo long
thanks
Click to expand...
Click to collapse
First time I was on stock ics rom. I installed cwm recovery and accidentally I wiped in cwm recovery and my phone bricked.
Wrong Post.
sandy4everyone said:
First time I was on stock ics rom. I installed cwm recovery and accidentally I wiped in cwm recovery and my phone bricked.
Click to expand...
Click to collapse
Thank you im just a little scared of flashing ill be careful
I have the att s4 with the mf3 build which I received via an ota update. I recently did the root for this build which worked perfectly, afterwards I read through 47 pages of forums and was trying to do the work around djrbliss put out, around page 40 someone says if your phone is rooted just download goomanager and installscriptrecovery. then reboot recovery. I downloaded goomanager then installed script, after this I hit the reboot recovery and the phone went into download mode. and it will stay there. If i restart it returns to download mode. Any Ideas?
Im not 100% but u may hve read wrong. This has happened to everyone who has tryed to flash a recovery on mf3. You can only have root there is no custom recovery for this build. Ok now this is wat you do take your phone to bestbuy tell them kies f'd ur phone up nd they can reflash mf3.at this moment mf3 isnt available to general public
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Yeah, read the forums. I mean seriously, almost every other post, including the one you read, tells you that drjbliss's exploit was patched in mf3, and can brick your device if you attempt to install a custom recovery. It is, quite literally, the biggest topic in the S4 forums. Also, there is no odin flashable image for mf3, so you cannot return to stock without taking it to bestbuy. Read more in the q&a section, as this same mistake has been made and asked about at least a hundred times. Literally.
In conclusion, you have a paperweight till you take it to get it flashed back to normal.
ok thanks for the help
cooljg said:
ok thanks for the help
Click to expand...
Click to collapse
Read this thread. Best buy can flash the stock mf3 firmware and get your recovery back. http://forum.xda-developers.com/showthread.php?p=45457012
Either that or J-Tag.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Hey guys thanks for chiming in. I want to give a thank you to those who have gave me a serious answer. I will go back to best buy and try again, but I sent my wife up there and she said the cell phone department told her they do not flash firmware there. She said she asked them if the service section did and the lady told her no again. I am fairly familiar with flashing the firmware on an s3 I just haven't messed with the s4 that much,and obviously I didn't read as well as I thought I did or it wouldn't be bricked. I do have one other question tho if Best Buy can flash it back to stock firmware, is it safe to assume at some point I should be able to flash it back via odin when the mf3 build is released by sammobile? Either way if best buy doesn't flash it back i'm screwed on this one and i'll just have to pick up another s4 tomorrow. I just want to know if this one can be fixed i'd really hate to waste a perfectly good phone.
If and when mf3 firmware is available you should be able to flash with odin. Best buy seems to be using a new software package other than Odin so who knows if an odin package will be available.
I believe at best buy they have to have a "Samsung Experience" booth or area to do the flashing. The normal best buy service counter can't do it.
~wolverine~ said:
I believe at best buy they have to have a "Samsung Experience" booth or area to do the flashing. The normal best buy service counter can't do it.
Click to expand...
Click to collapse
Correct
Question on brick fix
Hey guys thanks for the helpful info. I took it to the samsung experience part of best buy and the guy fixed it. He didn't have to flash the firmware tho, he took the back off and replaced the battery then I don't know what combination of buttons he hit or what but he held something and it was able to reset the phone and came up normally. Does anyone know what he could of hit? The phone was stuck in download mode no matter what you hit it would only reset to it. I had tried booting and holding volume up and home and releasing home for the recovery boot. As a recap of what happened I had rooted the phone and then downloaded goomanager and ran the installed script option under settings then I reset and was stuck in download mode. I just found it crazy that he never had to hook it to his computer to fix it.
cooljg said:
Hey guys thanks for the helpful info. I took it to the samsung experience part of best buy and the guy fixed it. He didn't have to flash the firmware tho, he took the back off and replaced the battery then I don't know what combination of buttons he hit or what but he held something and it was able to reset the phone and came up normally. Does anyone know what he could of hit? The phone was stuck in download mode no matter what you hit it would only reset to it. I had tried booting and holding volume up and home and releasing home for the recovery boot. As a recap of what happened I had rooted the phone and then downloaded goomanager and ran the installed script option under settings then I reset and was stuck in download mode. I just found it crazy that he never had to hook it to his computer to fix it.
Click to expand...
Click to collapse
Hmm, that is interesting. Did he replace the battery temporarily while 'resetting the phone with combination of buttons'?
Or did he place the battery inside and let you have it?
Sounds like a simple factory reset...
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
haremmon said:
Hmm, that is interesting. Did he replace the battery temporarily while 'resetting the phone with combination of buttons'?
Or did he place the battery inside and let you have it?
Click to expand...
Click to collapse
He originally plugged my phone up when I gave it to him but it wouldn't come on so he unplugged it and replaced the battery. The battery I had was completely dead. After he replaced the battery he turned it on and it went to the download screen with the little green alien. After that he held some buttons and kept looking at the back and then the front of the phone. I couldn't really see what he hit but shortly afterwards it came up with my lock screen picture. After that he said it doesn't need flashing but he would flash the firmware if I wanted so I said ok and he did. I have the phone now working great but it doesn't show rooted anymore.
Omg how do people not know this already. I have had my S4 for 2 days even i know better and I cant believe people dont read