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.
Related
i told tmobile that i cant use the hardware keys to get in master reset menu. they sending me a 3rd one. but i had to pay for the shipping. i think its gona be the same model and i wont be able to get in master reset menu again..
what shall i do? if that's the case
All newer revisions are hardware lock.
No offense but how many people just read here that hardware locked vibrant's are bad and ask to get new one? Seriously? I just helped a buddy of mine with a hardware locked vibrant yesterday and it took just one extra step to mod his just like mine (which is normal). Just rooted via windows, flashed clockwork and you can boot into recovery from there, flash any roms you want. Now, granted, you have to be slightly more careful but if you make a mistake just get into download mode and flash with odin. Seriously, the hardware buttons just mean you can get into recovery if you get stuck at the vibrant screen, but if you really brick your phone, regardless of hardware lock, both types of phone are at the same level.
Seriously, 3 returns just to get this? By now you could have had your FIRST one modded to hell and back...
You may get lucky and get a Vibrant with the hardware keys working. I just got my vibrant replaced last week and the keys on the new one are operational. Even came with another external sd card.
madgravity34 said:
No offense but how many people just read here that hardware locked vibrant's are bad and ask to get new one? Seriously? I just helped a buddy of mine with a hardware locked vibrant yesterday and it took just one extra step to mod his just like mine (which is normal). Just rooted via windows, flashed clockwork and you can boot into recovery from there, flash any roms you want. Now, granted, you have to be slightly more careful but if you make a mistake just get into download mode and flash with odin. Seriously, the hardware buttons just mean you can get into recovery if you get stuck at the vibrant screen, but if you really brick your phone, regardless of hardware lock, both types of phone are at the same level.
Seriously, 3 returns just to get this? By now you could have had your FIRST one modded to hell and back...
Click to expand...
Click to collapse
There is no way to get in
Dl mode on the locked vibrants so if u messup ur bricked forever,and older model of vibrant you cant brick because you can always get in to download mode and use odin to re flash
Sent from my SGH-T959 using XDA App
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.
So I just wanted to share with you guys that I successfully bricked my Vibrant. Getting a new one on Thursday or Friday. You know what they say. That you learn the best way when you failed in something. So I have learned today what not to do to keep the phone up and running.
UPDATE:
Followed instructions kizer at http://forum.xda-developers.com/showthread.php?t=741027&highlight=bricked+download+mode&page=5 and it took me to download mode.
How did you brick it?
Segnaro said:
How did you brick it?
Click to expand...
Click to collapse
I was putting Eugene's leaked froyo on my vibrant. Been having problems with the SD card so I decided I was going to reflash it again. So I clicked on the re-partition in Odin as I tried doing it without repartitioning. For some reason it stopped in the middle of the process, I got impatient (waited only like 5 minutes) and decided to restart it. Was having problems with the computer at the time as well. To many things running.
I think that the controller for the keys got wiped as nothing responded afterward this happened. It would not even recognized being connected to the computer.
how did you explain it to t-mobile?
iynfynity said:
how did you explain it to t-mobile?
Click to expand...
Click to collapse
Just told them that their JI6 update crashed it with an incomplete installation. I know they guy that put in the warranty exchange for me. And as he hadn't got the update to his phone yet he figured that it makes sense. Heard about the update doing weird stuff.
I just figured they would take the phone and reflash it when they get it.
swehes said:
I was putting Eugene's leaked froyo on my vibrant. Been having problems with the SD card so I decided I was going to reflash it again. So I clicked on the re-partition in Odin as I tried doing it without repartitioning. For some reason it stopped in the middle of the process, I got impatient (waited only like 5 minutes) and decided to restart it. Was having problems with the computer at the time as well. To many things running.
I think that the controller for the keys got wiped as nothing responded afterward this happened. It would not even recognized being connected to the computer.
Click to expand...
Click to collapse
so another person messes up their phone and fraud's the warranty, great post.
Next are you SURE it's bricked? I've had many failed ODIN's and I've never ever bricked one.
rsfaze said:
so another person messes up their phone and fraud's the warranty, great post.
Next are you SURE it's bricked? I've had many failed ODIN's and I've never ever bricked one.
Click to expand...
Click to collapse
Hmmmm. Found one last post of how to get into download mode, and it took it in. Greatly surprised and happy as I am quite fond of this phone. Odin new Froyo to it. Quite remarkable.
MOD. Can you please remove this thread as I managed to undo my mistake?
swehes said:
Hmmmm. Found one last post of how to get into download mode, and it took it in. Greatly surprised and happy as I am quite fond of this phone. Odin new Froyo to it. Quite remarkable.
MOD. Can you please remove this thread as I managed to undo my mistake?
Click to expand...
Click to collapse
You didn't manage to undo your mistake.. You managed to fraud t-mobile on YOUR mistake.
Glad you "Fixed" your phone.
Lol so who doesn't have insurance?
Sent from my SGH-T959 using XDA App
The insurance doesn't cover bricking your phone by way of flashing unofficial firmwares anyways does it? So what's the point?
Sent from my SGH-T959
catchy subject header, and what a turn around like mine. I now know for sure the Vibrant is 100% bullet proof figuratively lol.
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
Hi everybody, I enjoyed my stock N4 for almost a year and today several apps started to crash suddenly, after that the device rebooted itself and never got out of the bootloop. I immediatly booted into recovery and tried to wipe the cache memory and perform a factory reset but I cannot do either of the two, the error I get is something like "can't mount cache partition".
What should I do? How did this happen?!? I really need my phone back asap.
Thanks everybody!
Flash the stock images.
Chromium_ said:
Flash the stock images.
Click to expand...
Click to collapse
Ok I will but...How can this happen? A fully stock phone who never had a problem suddenly corrupts it's partitions?! (This is my understanding of the situation, correct me if I am wrong)
Thanks again for the link
Update: unlocking the bootloader works but when I reboot it appears to be locked again.
flashing the bootloader img file fails.
chikosneff said:
Update: unlocking the bootloader works but when I reboot it appears to be locked again.
flashing the bootloader img file fails.
Click to expand...
Click to collapse
sounds like your storage itself fails. thats the same issue that happens when the storage goes bad.
simms22 said:
sounds like your storage itself fails. thats the same issue that happens when the storage goes bad.
Click to expand...
Click to collapse
Thanks for helping, yes it looks like..so I can throw away my phone or there's something more I can try?
It feels so weird because it's one of the few phones I always kept stock, never fell, never had a single problem. Damn.
chikosneff said:
Thanks for helping, yes it looks like..so I can throw away my phone or there's something more I can try?
It feels so weird because it's one of the few phones I always kept stock, never fell, never had a single problem. Damn.
Click to expand...
Click to collapse
You could give this a try, but I really doubt it'll do much. I guess its worth a shot though.
chikosneff said:
Ok I will but...How can this happen? A fully stock phone who never had a problem suddenly corrupts it's partitions?! (This is my understanding of the situation, correct me if I am wrong)
Thanks again for the link
Click to expand...
Click to collapse
chikosneff said:
Update: unlocking the bootloader works but when I reboot it appears to be locked again.
flashing the bootloader img file fails.
Click to expand...
Click to collapse
Tried to Toolkit yet ? http://forum.xda-developers.com/showthread.php?t=1766475
Why did it happen? A phone is basically a mini computer, same as when you have to reload a computer OS sometimes,(failing hardware, bad app???)
Timboe73 said:
Tried to Toolkit yet ? http://forum.xda-developers.com/showthread.php?t=1766475
Why did it happen? A phone is basically a mini computer, same as when you have to reload a computer OS sometimes,(failing hardware, bad app???)
Click to expand...
Click to collapse
I'll give it a shot thanks, but I am afraid that the fastboot flash error is pretty clear :crying:
I get the phone being a computer, and I am totally ready to reload an OS...but I am not so ready to see the storage fails so suddenly leaving me with no phone, especially because this phone has received more care than any other phone I ever had..
Timboe73 said:
Tried to Toolkit yet ? http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
If its failing when he does it manually via fastboot commands, its very unlikely that using a toolkit will change anything. A toolkit simply runs the same fastboot commands behind a GUI.
Switched to windows to give the toolkit a try, then I will follow the unbrick procedure...I still cannot believe that this phone is lost without even having experienced the fun to mess it up with my own hands
chikosneff said:
Switched to windows to give the toolkit a try, then I will follow the unbrick procedure...I still cannot believe that this phone is lost without even having experienced the fun to mess it up with my own hands
Click to expand...
Click to collapse
As expected: toolkit not working. Since the bootloader " relocks" itself after rebooting the toolkit is unable to flash it afterwards.
Will try to contact google support but I am currently living in Europe I don't think it will be easy to get help.
Any other help is greatly appreciated. Thanks everybody.
1. if its within the warrenty period, this is something that would be covered.
2. its fixable. it can be professionally repaired, or you can try to do it yourself with the right parts.
but you will lose whatever you had in your storage, if you havent already.
another case reported :/
i think some batches of nexus 4 contains emmc brick bugs
just see this thread, more then 5 or 6 have been reported here.
http://forum.xda-developers.com/showthread.php?t=2259334
so after reading that thread i **** my self, because if this occured to my nexus i will have no warranty no google claims no nothing because i live in Pakistan.
So i ran emmc check app on my phone to check what it shows.
my emmc check shows i have "NO, Sane chip"
this means i am safe? if it give me "Yes, Insane chip" then i,m not safe according the my theory.
EMMC check app also shows the chip type, my chip type is "016g92"
googling this chip type i came across no specific results, one from S3 sudden death thread discussion. one person reports he have the 016g92 type and it is a safe chip according to other folks.
and one person having a galaxy s3 bricked his emmcs chip and claim the warranty. after the phone returns his chip type change to 016g92
http://smartphone.usofttech.com/t85915.html
so they change the emmc chip to 016g92.
can i surely assume that my nexus is safe from this serious hardware defect?
also any one here run the emmc chip and do give there chips type here, as i want to confirm if i,m safe or not. if not i,m going to sale my phone here. because the lose will be unbearable for me if the brick did occured
---------- Post added at 11:48 AM ---------- Previous post was at 11:37 AM ----------
simms22 said:
1. if its within the warrenty period, this is something that would be covered.
2. its fixable. it can be professionally repaired, or you can try to do it yourself with the right parts.
but you will lose whatever you had in your storage, if you havent already.
Click to expand...
Click to collapse
Dear Sir do advice me
simms22 said:
1. if its within the warrenty period, this is something that would be covered.
2. its fixable. it can be professionally repaired, or you can try to do it yourself with the right parts.
but you will lose whatever you had in your storage, if you havent already.
Click to expand...
Click to collapse
I still have 2 weeks of warranty left but I'll be in Europe till next year..I will try to ask the warranty service if I can send it in at my own expense.
Damn a worldwide warranty service doesn't look so useless now as it looked when I bought it :laugh:
PHONE BACK FROM THE DEAD!!!
So I got in touch with google's customer care to arrange the RMA and just to show them that my phone was impossible to recover I jumped ahead and told 'em: ok let's do a factory reset together so that I can show you what's the problem....
Fastboot>recovery>>data wipe....COMPLETED!
I cannot understand why did it work, I tried to wipe it at least ten times yesterday.
So now I have my N4 back working. What's your opinion on what happened? Do you feel like the problem is going to show up again soon? Is there anything I should do now that it's working? I just did a factory reset, not the cache wipe.
Just FYI: RMA from oversea is a pain in the ass, you have to ship the phone back to somebody in the U.S. and THEN ask for the RMA.
I wish I had your luck, mine did the same thing about 2 weeks ago. Couldn't get it to factory reset either. Mounting issue. My RMA came in yesterday. I'm enjoying the new phone though. It's even got the little nubs on the back. Mine original was a creaky 1st or 2nd batch one, I think. I will miss all the memories, pics, and data on my old one though.
SefEXE said:
I wish I had your luck, mine did the same thing about 2 weeks ago. Couldn't get it to factory reset either. Mounting issue. My RMA came in yesterday. I'm enjoying the new phone though. It's even got the little nubs on the back. Mine original was a creaky 1st or 2nd batch one, I think. I will miss all the memories, pics, and data on my old one though.
Click to expand...
Click to collapse
Since I feel this problem is hardware related I do not feel completely safe and I believe you were the lucky one getting the RMA
I had no choice, I should have sent the phone back to the US and then ask for the RMA...big pain in the ass
:fingers-crossed: let's hope this thing holds