Hi all,
I have looked for a similar post, I found out that many people experienced something like that trying unlocking their phones, but I haven't found out any solution.
Here is my situation:
I have tried to unlock my s5830 (orange spain carrier), I have used a method which it seems to be dangerous for the phone, but of course I have found out it was dangerous after I have already tried it
Anyway after I discovered the unlock number contained in the perso.txt file in the efs folder, my phone restarted without service once and after that it went in a bootloop mode, it goes on a download mode, but there is no way to get back recovery mode or a normal boot.
I flashed the s5830 several times with many firmware, but no one worked, and the phone is still stuck in an infinite loop, in which I am not even able to see the samsung logo coming out at the very beginning.
I know many phones got bricked in this way, I wanted to know if anybody has been able to recover the phone or if anybody know any possible solution.
And if not, do you know if the warranty is covering this problem? I just got the phone a couple months ago; i have unlocked other devices before, but this is the first time I have experienced a problem so I am quite new about warranty as well. Please HELP ME
Merry Christmas guys!!!
Thanks in advance
sfrat said:
Hi all,
I have looked for a similar post, I found out that many people experienced something like that trying unlocking their phones, but I haven't found out any solution.
Here is my situation:
I have tried to unlock my s5830 (orange spain carrier), I have used a method which it seems to be dangerous for the phone, but of course I have found out it was dangerous after I have already tried it
Anyway after I discovered the unlock number contained in the perso.txt file in the efs folder, my phone restarted without service once and after that it went in a bootloop mode, it goes on a download mode, but there is no way to get back recovery mode or a normal boot.
I flashed the s5830 several times with many firmware, but no one worked, and the phone is still stuck in an infinite loop, in which I am not even able to see the samsung logo coming out at the very beginning.
I know many phones got bricked in this way, I wanted to know if anybody has been able to recover the phone or if anybody know any possible solution.
And if not, do you know if the warranty is covering this problem? I just got the phone a couple months ago; i have unlocked other devices before, but this is the first time I have experienced a problem so I am quite new about warranty as well. Please HELP ME
Merry Christmas guys!!!
Thanks in advance
Click to expand...
Click to collapse
if you can get into download mode im guessing there is some hope for you.
go here: http://droidangel.blogspot.com/2011/05/samsung-galaxy-ace-s5830-original-stock.html
look for: S5830XXKP9
and make sure you have odin 4.38 and flash with that.
try to install cwm and install a customrom
Sent from my GT-S5830 using xda premium
sfrat said:
Hi all,
I have looked for a similar post, I found out that many people experienced something like that trying unlocking their phones, but I haven't found out any solution.
Here is my situation:
I have tried to unlock my s5830 (orange spain carrier), I have used a method which it seems to be dangerous for the phone, but of course I have found out it was dangerous after I have already tried it
Anyway after I discovered the unlock number contained in the perso.txt file in the efs folder, my phone restarted without service once and after that it went in a bootloop mode, it goes on a download mode, but there is no way to get back recovery mode or a normal boot.
I flashed the s5830 several times with many firmware, but no one worked, and the phone is still stuck in an infinite loop, in which I am not even able to see the samsung logo coming out at the very beginning.
I know many phones got bricked in this way, I wanted to know if anybody has been able to recover the phone or if anybody know any possible solution.
And if not, do you know if the warranty is covering this problem? I just got the phone a couple months ago; i have unlocked other devices before, but this is the first time I have experienced a problem so I am quite new about warranty as well. Please HELP ME
Merry Christmas guys!!!
Thanks in advance
Click to expand...
Click to collapse
with the cellphone off, put out ur baterry for a minute, then maintain ur finger into the volume down button and the power button tell a friend or if u can alone insert the batery while quickly pressing volume down and power button to get into download mode, and flash.
Hehehe,bootloop is horrible,you just have to get in download mode & flash with 2.3.4 firmware with Odin,just that steps and you save your SGA.
I got bootloop many times and Odin saved me.
Sent from my SGA
robinandroid said:
try to install cwm and install a customrom
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
he cant go back in recovery mod............
If you can go to recovery mode than you can just wipe the data and cache. This saved me many times. Otherwise on what ever OS you may be , just create new user name after removing samsung android drivers. Login from new user name and than re install drivers again and now flash your phone from firmware which was installed on your phone before you bricked it. This helped me a few times.
dr_vishal said:
If you can go to recovery mode than you can just wipe the data and cache. This saved me many times. Otherwise on what ever OS you may be , just create new user name after removing samsung android drivers. Login from new user name and than re install drivers again and now flash your phone from firmware which was installed on your phone before you bricked it. This helped me a few times.
Click to expand...
Click to collapse
hey guys thanks for the answers, but unfortunately i am not able to reach the recovery mode, my phone just reach the download mode.....i will try with the xxkp9, even if i have already tried it...I guess i have tried at least 15 firmwares without any success
Helping to make your Christmas Merry
It seems that you've already received a lot of help for unbricking your device. So I'll try to help out in unlocking your phone after you finished unbricking it.
This is the method I personally used on my locked Ace:
http://forum.xda-developers.com/showthread.php?t=1335548
It's perfectly safe. 100%.
King Kaze said:
if you can get into download mode im guessing there is some hope for you.
look for: S5830XXKP9
and make sure you have odin 4.38 and flash with that.
Click to expand...
Click to collapse
I have tried the XXKP9 again, it is not working, as usual Odin ends to load the firmware and then it goes back in the endless loop mode....there is no chance to get it back?
franzks said:
It seems that you've already received a lot of help for unbricking your device. So I'll try to help out in unlocking your phone after you finished unbricking it.
This is the method I personally used on my locked Ace:
http://forum.xda-developers.com/showthread.php?t=1335548
It's perfectly safe. 100%.
Click to expand...
Click to collapse
thank you very much I will follow your advice...IF I will be able to get my phone back which seems impossible =(
@dr_vishal
Thank you first of all, I have tried to uninstall and reinstall the android device driver, but it doesn't seems to be the problem, Odin ends with a "PASS" at the end, I guess there still is comunication in the between the two devices...
Hopefully it will be a Merry Christmas =)
It's not impossible. I'm relatively new here but I have noticed quite a few "bricked" threads already. Most of them (if not all) have been able to fix their device. I haven't seen a single person permanently brick their device, so I would guess that your chances of fixing it are really high. Just be patient and keep describing your situation and more experienced help will certainly arrive. I'd really like to help out but I have no idea how to fix it as I have not experienced bricking my phone yet.
Anyway, if the method for unlocking I suggested works for you kindly press the Thanks Button. Merry Christmas!
franzks said:
It's not impossible. I'm relatively new here but I have noticed quite a few "bricked" threads already. Most of them (if not all) have been able to fix their device. I haven't seen a single person permanently brick their device, so I would guess that your chances of fixing it are really high. Just be patient and keep describing your situation and more experienced help will certainly arrive. I'd really like to help out but I have no idea how to fix it as I have not experienced bricking my phone yet.
Anyway, if the method for unlocking I suggested works for you kindly press the Thanks Button. Merry Christmas!
Click to expand...
Click to collapse
Thank you franzks!
I promise I will try your method and I am positive it will works, but I need to get my phone back...so I will add few new information I have found out talking to a friend of mine which has my same device and the same carrier as well.
The version built-in is:
GINGERBREAD.BVKQ9
S5830BVKQB
[email protected]#1
Any suggestion about the firmware I am suppose to flash in?
I am actually passing through all the version contained in the address droidangel you gave me...at the moment no one is working...I will keep trying...
sfrat said:
Thank you franzks!
I promise I will try your method and I am positive it will works, but I need to get my phone back...so I will add few new information I have found out talking to a friend of mine which has my same device and the same carrier as well.
The version built-in is:
GINGERBREAD.BVKQ9
S5830BVKQB
[email protected]#1
Any suggestion about the firmware I am suppose to flash in?
I am actually passing through all the version contained in the address droidangel you gave me...at the moment no one is working...I will keep trying...
Click to expand...
Click to collapse
Guys,
I am out of ideas, I have tried each single firmware I have seen around internet, no one is working, any tip or advice or suggestion?
I messed up with the efs, and I guess that's all, the phone is gone....now it needs a JTAG or whatever is its name....
maybe to get the warranty still valid I should broke totally the phone over charging it....??
sfrat said:
Guys,
I am out of ideas, I have tried each single firmware I have seen around internet, no one is working, any tip or advice or suggestion?
I messed up with the efs, and I guess that's all, the phone is gone....now it needs a JTAG or whatever is its name....
maybe to get the warranty still valid I should broke totally the phone over charging it....??
Click to expand...
Click to collapse
Did you try that?
http://forum.xda-developers.com/showthread.php?t=1153310
just a thought
a lot of people have talked about reflashing it and all but have you managed to get into the recovery mode at all once you have reinstalled the rom with odin? if you can get to that you just need to hit factory reset, wipe cache and wipe dalvik and normaly after that it will work fine... so far ive been stuck in soft brink 3 times and each time doing the wipes from the recovery mode has worked...
Pinting said:
Did you try that?
http://forum.xda-developers.com/showthread.php?t=1153310
Click to expand...
Click to collapse
I've tried to use the oneclick, but it seems it doesn't recognize the phone, since, i guess, it's made for a galaxy s.
The others are not my case, since I am able to get download mode, and all these are made to can get it back.
Anyway I found out a post in which the people were talking about the s5500, which apparentely is similiar to my device, and the owners of that model experienced a similar problem doing the same process....anyway in that post the people needed to use a Jtag, which is the only way to get it back....so I though it could be the same solution for my problem...but I don't know anybody with Jtag, so the only way is contacting the service center.
thanks anyway, when I will be back at home after Christmas I will try to find the ticket and I will probably try to get it back in warranty, since is preatty new...
@torchwolfery
I am not able to reach recovery mode, there is no way to get it back, even flashing the phone with different firmwares, all I got is download mode, and apparently that is completely pointless...since the only change in the phone behavior is that if i install a certain firmwares it doesn't even have the back-light working when it is stuck in bootloop.
Warranty is your only hope (as it was mine once and it worked).
I didn't think it was possible to brick these phones. There I have tried so much to try and brick it but I have not been able to as it still always goes into 'download' mode. The only advice I can give you is double check that you are using the correct version of Odin which is v4.38 and that you use cooper v1.0 as your OPS. If dont mind me asking, but exactly what did you do or do you remember the steps you took to brick it? What buttons are you using for 'recovery' mode.
Also please clarify if Odin is going in a loop or does the phone come on and then keeps rebooting? If it is the phone that keeps rebooting, then wiping cache and data partition should do the trick. This can be done by going into recovery mode (which I am aware you cannot get into) or if you can manage to get into the dialler quick enough before the reboot, by dialling *7267*3855# and that should format the relevant partitions (data and cahce) and bring it back to factory settings. Without further info, I cannot really tell exactly what the situation is.
The fact that you are getting 'download' mode, I dont think that it is bricked because it will still allow you to write the relevant directory/files to the relevant blocks. Either way, would be interested to know.
Related
heya all!
i just got my GT-I9100 today; it was bought from A1 (part of vodafone) austria, but it does not have a simlock, they usually "lag behind" with those and business customers seem to be able to get some of the first models that do not have any lock yet.
but thats not the issue; i fiddled around with a few things, namely: root it with that superoneclick thingie, install rom manager, (unsuccessfully) try to flash clockworkmod recovery with it, ..
and then i realized that it does not actually replace the "android system recovery 3e" at all, for some reason. actually i seemed to have both the 2e and the 3e version available SOMEwhere, when i did an "adb reboot recovery" i got into the 3e version, with some key combo i managed to get into 2e (i think it was vol-down + power)
in any case, after searching forums for a while i found info that people have been installing "darky's 9.2 resurrection" in this case because it kind of completely wipes everything and gives a clean base to start with.
so i tried that, and i think it was a bad idea to actually re-partition with odin with the included PIT file. in any case, the flashing process completely halted right after it started; after many minutes i unplugged the phone, odin immediately gave me a red FAIL label, and since the phone didn't react anymore i power cycled it via its battery. i guess that was the second mistake
now i'm stuck in a state of complete darkness. the appearently common issue of "black screen after logo" is something different, i don't get ANY reaction from the phone WHATSOEVER. regardless of what keys i press in what combinations etc, it acts as if the battery was completely empty (which it definitely is not). USB does not do anything either.
i also noticed that the phone got unusually warm in the area of the camera, not like HOT, but warmer than i was able to get it by just toying around with it the hour before. i mean, if i try to turn it on and stuff, so it looks to me as if it is doing something, but it cannot even initialize the display or usb.
i ordered some components and will try this method http://forum.xda-developers.com/showthread.php?t=819551 even tho it explicitly states that it won't help against all-blackness, just in case.
anyone got any ideas of what i could still do? or is trying to get a replacement from the carrier my only option?
just for additional info, i also have 2 HTC desires, and never managed to brick them to death, i have some clues about adb and the sdk in general, i'm not completely clueless when it comes to android, but since i don't even get any kind of touchable interface (usb wise) i'm out of ideas...
thanks & regards
hi mate darkys rom is for the samsung galaxy s not the gaxy s 2 and clockwork mod wont work either
andypull15 said:
hi mate darkys rom is for the samsung galaxy s not the gaxy s 2 and clockwork mod wont work either
Click to expand...
Click to collapse
hmn i kind of wasn't sure about darkys rom after my attempts anymore
in the beginning i thought the galaxy s2 was actually called i9000, until i opened it once again and say that it states 9100
but in any case - is there anything i can do, software wise?
anyone got any ideas of what i could still do? or is trying to get a replacement from the carrier my only option?
Fake /wrong rom they may reject it under warranty .
http://forum.xda-developers.com/showthread.php?t=1075278
Try flash a stock rom .
jje
JJEgan said:
anyone got any ideas of what i could still do? or is trying to get a replacement from the carrier my only option?
Fake /wrong rom they may reject it under warranty .
http://forum.xda-developers.com/showthread.php?t=1075278
Try flash a stock rom .
jje
Click to expand...
Click to collapse
well thats the problem, i can't flash anything. i have no way of going into download mode, or any other mode, its just "dead".
Try to use the "magical cable", i think this cable work also on SG2 and not only the SG1 ... There is a lot sellers on ebay.
Sorry did i not mention the download mode recovery jig .
If it boots via the recovery jig to download mode you may be able to fix or at least fix enough to claim warranty .
jje
yep i guess i will get the components on monday (and i need to borrow a soldering iron
i already got info from the carrier that they will replace it, i just hope they won't look at it too much
can tyou tell us if tyou succeded ? I'm in the exact same situation.
makrook said:
can tyou tell us if tyou succeded ? I'm in the exact same situation.
Click to expand...
Click to collapse
heys, i got a replacement from the carrier for free, and i'm not gonna brick it just to retest *g*
i ordered components for the usb rig and they already arrived, but i have not yet found time to test it, partly because i don't really need it - this time i did not make the mistake of flashing a wrong partition table......
regards
additional info: i'm on cognition S2 now. before i went there, i flashed 3-part stock 2.3.4 firmware, and this time, it was the right PIT file *g* so everything worked like a charm.
Received a brand new Ace yesterday, and immediately rooted it with super one click with no problems.
However I then tried to run the 'Galaxy Ace Unlock apk' which I'd found elsewhere.
It generated an unlock pin, but after rebooting it stuck on the Galaxy Ace flash screen. After 5 minutes I pulled the battery out, waited, then rebooted. Now it doesn't even get to the Galaxy Ace screen when switched on.
The screen backlight comes on (with a black screen) for a couple of seconds, then off, then on - but it never gets any further.
So far I've tried
- Flashing Stock Froyo via Odin
- Flashing VillainRom via Odin
In both cases the phone enters download mode, Odin completes all steps without error, but on reboot I am left with the black screen of death again!
Anything else I could try?
I have the same problem.
Have you found a solution?
zongamin said:
Received a brand new Ace yesterday, and immediately rooted it with super one click with no problems.
However I then tried to run the 'Galaxy Ace Unlock apk' which I'd found elsewhere.
It generated an unlock pin, but after rebooting it stuck on the Galaxy Ace flash screen. After 5 minutes I pulled the battery out, waited, then rebooted. Now it doesn't even get to the Galaxy Ace screen when switched on.
The screen backlight comes on (with a black screen) for a couple of seconds, then off, then on - but it never gets any further.
So far I've tried
- Flashing Stock Froyo via Odin
- Flashing VillainRom via Odin
In both cases the phone enters download mode, Odin completes all steps without error, but on reboot I am left with the black screen of death again!
Anything else I could try?
Click to expand...
Click to collapse
Hey!
Dose you RESET FACTORY SETTINGS and FORMAT CACHE in recovery, before flashing with ODIN?
CHEERS!
Did the light lit when you entered the download mode? That's the indicator.
I got the same proble, tried several firmwares with odin but, when the phone reboots it starts flashing again
Hey!
You all, try THIS one.
CHEERS!
casiocas said:
Hey!
You all, try THIS one.
CHEERS!
Click to expand...
Click to collapse
I tried it, several times with different firmwares but it doesn´t do anything. The phone, when rebooting with odin, keeps flashing the black screen
moe_szislack said:
I tried it, several times with different firmwares but it doesn´t do anything. The phone, when rebooting with odin, keeps flashing the black screen
Click to expand...
Click to collapse
Hey!
Just wanted to ask, FROM WHERE you downloaded you UNLOCK soft. Can you give me the link? PLEASE!
CHEERS!
casiocas said:
Hey!
Just wanted to ask, FROM WHERE you downloaded you UNLOCK soft. Can you give me the link? PLEASE!
CHEERS!
Click to expand...
Click to collapse
Sorry if it sound rude, it wasn´t my intention.
I download the soft form samfirmwares.com.
Cheers
moe_szislack said:
Sorry if it sound rude, it wasn´t my intention.
I download the soft form samfirmwares.com.
Cheers
Click to expand...
Click to collapse
Ok, I get. But SORRY, then I cant help. You must contact then, from where you downloaded it.
Just I hope you get fixed your phone(If you most take it to SERVICE, try to explain them that you tryed RESET FACTORY SETTINGS. It work for several ppl-s here, who must take his phone to SERVICE). Just be 10 times SURE, that you cant flash or recovery you phone, or they can do the same and see that your phone WAS ROOTED or FLASHED the CUSTOM ROM(JUST BE SURE, THEY CANT ACCESS YOU PHONE or you lose you WARRANTY).
I hope all ENDS good! Fingers crossed for you phone!!!
CHEERS!
casiocas said:
Ok, I get. But SORRY, then I cant help. You must contact then, from where you downloaded it.
Just I hope you get fixed your phone(If you most take it to SERVICE, try to explain them that you tryed RESET FACTORY SETTINGS. It work for several ppl-s here, who must take his phone to SERVICE). Just be 10 times SURE, that you cant flash or recovery you phone, or they can do the same and see that your phone WAS ROOTED or FLASHED the CUSTOM ROM(JUST BE SURE, THEY CANT ACCESS YOU PHONE or you lose you WARRANTY).
I hope all ENDS good! Fingers crossed for you phone!!!
CHEERS!
Click to expand...
Click to collapse
I forgot to say that I put a sim card (from other country) inside the ACE to check if it was unlocked.
Can it be the problem?
moe_szislack said:
I forgot to say that I put a sim card (from other country) inside the ACE to check if it was unlocked.
Can it be the problem?
Click to expand...
Click to collapse
Hey!
I want to help you, REALLY, but a bout that queation, I CANT ANSWER, RIGHT NOW. DONT KNOW EXACTLY. SORRY!
I try to find answers tomorrow(we have here 23:27). Tomorrow to work.
CHEERS!
casiocas said:
Hey!
I want to help you, REALLY, but a bout that queation, I CANT ANSWER, RIGHT NOW. DONT KNOW EXACTLY. SORRY!
I try to find answers tomorrow(we have here 23:27). Tomorrow to work.
CHEERS!
Click to expand...
Click to collapse
Ok, Thank you
Need help screen just flashes and blinks..
Tried multiple rom flashes...odin says pass but the ph doesn't boot up
Sent from my SAMSUNG-SGH-I897 using XDA App
misterio_mr111 said:
Need help screen just flashes and blinks..
Tried multiple rom flashes...odin says pass but the ph doesn't boot up
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
The same thing happens to me, Anybody has any idea?
Just send it to the service center.
No other recovery method is know.
I have been in every forum arond for this kinda brick and there is no solution for YOU to do. Also there is absolutely no way for Samsung to see either say that after the first boot the battery went dead and it never started again. It will be covered by your warranty and brand new ace! Now dont go making stupid mistakes again hope i helped
Sent from my GT-S5830 using XDA App
Apk/sim bricked my phone.
Unlock Apk also bricked my phone in the same manner.
The app generating the code is not the problem on it's own, it's when you put the "other" Sim card in and reboot that does the damage.
I got a buzz when i could still get Download Mode and Odin gave me a PASS when i reflashed, but alas the phone never rebooted and it still flashed black at me.
I'm trying everything to bring it back to life before it goes to the Service Centre and i have to give them some blag as to why it's bricked.
Other than Download Mode i can get "Emergency Dload Mode"(ARM9) & RAMDUMP.
BLZBud said:
Unlock Apk also bricked my phone in the same manner.
The app generating the code is not the problem on it's own, it's when you put the "other" Sim card in and reboot that does the damage.
I got a buzz when i could still get Download Mode and Odin gave me a PASS when i reflashed, but alas the phone never rebooted and it still flashed black at me.
I'm trying everything to bring it back to life before it goes to the Service Centre and i have to give them some blag as to why it's bricked.
Other than Download Mode i can get "Emergency Dload Mode"(ARM9) & RAMDUMP.
Click to expand...
Click to collapse
I got the same problem and still nobody has found how to unbrick the phone.
I´ll keep searching
moe_szislack said:
I got the same problem and still nobody has found how to unbrick the phone.
I´ll keep searching
Click to expand...
Click to collapse
Even Samsung don't have an easy way to repair it, hence they replace the mainboard to fix the issue.
So I had previously rooted my SGSII, and decided to try installing CM7 on it. I used CWM Recovery and ran it off the SD card, and everything appeared to work fine. I think I had a bad/not fully functioning CWM or something, as it didn't list an option to backup anything (I'm guessing because I flashed the stock kernel after rooting?) Anyway, it will no longer boot. I can access download mode, but Odin fails everytime I try to flash anything back on there. When I try to boot my phone, I just get a "Firmware upgrade encountered an issue" error.
EDIT: I just tried again as I was writing this, after rebooting, reinstalling my drivers and rebooting my computer. I was able to get the Firmware to flash properly in Odin. Now I have my phone booting and getting stuck on the "Samsung Galaxy SII GT-I9100 splash screen... Doesn't seem to go any further than that though, unfortunately.
Any ideas what I can do? Is it possible that I need re-flash a bootloader or something ??
Any help would be supremely appreciated!
So I was just trying to re-install the Kernel, using the CF unsecured kernel, and it failed, but when I try to go into recovery mode, it looks as though it managed to install CWM Recovery. I have no idea what to do from here, and am sort of afraid to do anything for fear or bricking the phone completely...
I'm hoping someone out there knows how to fix this, I feel like such a tool
As long as you can get into download-mode, your phone isn't bricked.
If you switch from or to a TouchWiz-based ROM, you have to do a full-wipe in the recovery.
Sent from my GT-I9100 using XDA App
Go back to stock first via download mode via odin
Nah you're good. Similar thing happened to me at my first flashing attempt. Get your stock firmware from Intratech's thread, put the phone into download mode & flash the firmware via Odin.
Then maybe have another go at rooting the phone with the matching CFRoot kernel.
Porkchops said:
So I was just trying to re-install the Kernel, using the CF unsecured kernel, and it failed, but when I try to go into recovery mode, it looks as though it managed to install CWM Recovery. I have no idea what to do from here, and am sort of afraid to do anything for fear or bricking the phone completely...
I'm hoping someone out there knows how to fix this, I feel like such a tool
Click to expand...
Click to collapse
yes, if you can still go in download mode it's no so difficult..this "small brick" it's on of "Android things to do" once in your SGS2 life
Hi guys. I'm in a worst situation. As my phone after a failed ODIN downgrade from Android 2.3.6 to one stock kernel is completelly dead - it doesn't boot anymore - not even managed to put it back into download mode or revert to fact defaults (no keys, no lights not even battery charging displayed when pluged in) - tryed the USB jig also. Nothing worked.
The question is: Will Samsung manage to repair and how much will it cost - an average ammount offcourse. Because I guess it's out of the question to be considered a warranty issue. I guess it will be visible somebody have done smth to the ROM by a software approach....
This is the short story because I would bore you to discuss all the things I have been through - it was only my faoult out of stupidity
HELP!
I don't see why Samsung wouldn't fix it ? As to how much they'll charge you, I think you'll find that will vary from country to country (labour costs being variable, etc). No, I don't think you'll be able to have it repaired under warranty.
You might want to look at having it JTAG repaired by someone other than Samsung. This will possibly be cheaper than having Samsung repair it. Do a search on here/Google.
alexdonc said:
The question is: Will Samsung manage to repair and how much will it cost - an average ammount offcourse. Because I guess it's out of the question to be considered a warranty issue. I guess it will be visible somebody have done smth to the ROM by a software approach....
HELP!
Click to expand...
Click to collapse
Thank you very much. I have searched alot to actually understand - unfortunatelly for me it will cost... I saw on youtube a JTAG in action right now (cannot post the link yet). I understand now it is the only way. I'll keep you posted guys. Tomorrow I'll go to service.
I'm sorry it's going to cost Alex. A difficult thing to happen, I know
Here's a link for a JTAG repairer in the US who is also a member here, tho I see you've already found one. I'm sure doing it this way will be cheaper/probably faster than having Samsung do the repair as well.
alexdonc said:
Thank you very much. I have searched alot to actually understand - unfortunatelly for me it will cost... I saw on youtube a JTAG in action right now (cannot post the link yet). I understand now it is the only way. I'll keep you posted guys. Tomorrow I'll go to service.
Click to expand...
Click to collapse
Thax. Funny thing is that this is exactly the thing I found - the same mobiletechvideos in US Now I allready have an ideea of how much should cost that. Hopefully I'll find a local GSM repair shop with the posibilitty to unbrick it cheep - or at least not much than 50USD - in local currency ofcource.
I'm still thinking if it is possible to use an ATMEL copy process - like in the old times for EEPROMS - I have done that in the past. In theory it might work but I will never do it - alredy scared about what happened to my beloved droid.
Thx again Mistah and have a gr8 day and a wonderfull new 2012!
Yeah I've seen a report or two on here from people who have used his service & have been happy. Must admit I found his page when thought I'd bricked my phone after my first flash attempt messed up. Yeah you might be able to get it done cheaper somewhere local, and that will mean less time without the phone for you without the phone in mail from you to the US & back again.
Let us know how you get on, your experience will be a good guide for people in future who have the same problems as you.
No probs man, happy to give you the little help I did. You too Alex Hope you have a great year & you get your phone back & working soon
alexdonc said:
Thax. Funny thing is that this is exactly the thing I found - the same mobiletechvideos in US Now I allready have an ideea of how much should cost that. Hopefully I'll find a local GSM repair shop with the posibilitty to unbrick it cheep - or at least not much than 50USD - in local currency ofcource.
I'm still thinking if it is possible to use an ATMEL copy process - like in the old times for EEPROMS - I have done that in the past. In theory it might work but I will never do it - alredy scared about what happened to my beloved droid.
Thx again Mistah and have a gr8 day and a wonderfull new 2012!
Click to expand...
Click to collapse
Hello again. Solved right now. The service didn't charged me at all - I was kind of lucky after all. Unfortunately there are still some issues I have from the start. I'll keep on digging - software related.
I recently hard bricked my phone after flashing CyanogenMod 10. I know that CyanogenMod doesn't even touch the bootloader but somehow I ended up with a very expensive paperweight. But luckily Samsung Care replaced the motherboard in my phone and now my phone is good as new. But that doesn't mean that I'm gonna refrain from flashing or rooting. I've been rooting since 2 years now & this is the first time I've ever hard bricked the phone. But this experience really did scare me. So, to avoid it, in future, I wanna know all about hard brick. So please answer my following questions:
1) What exactly is hard brick?
2) Possible ways in which one could end up with a hard bricked phone? (Mainly SGS3)
3) Possible ways of recovery from hard brick?
Thanks a lot in advance. I want this thread to be a complete source of information to anyone who is new to flashing & needs DO's & DONT's of flashing properly.
saurabh_goyal93 said:
I recently hard bricked my phone after flashing CyanogenMod 10. I know that CyanogenMod doesn't even touch the bootloader but somehow I ended up with a very expensive paperweight. But luckily Samsung Care replaced the motherboard in my phone and now my phone is good as new. But that doesn't mean that I'm gonna refrain from flashing or rooting. I've been rooting since 2 years now & this is the first time I've ever hard bricked the phone. But this experience really did scare me. So, to avoid it, in future, I wanna know all about hard brick. So please answer my following questions:
1) What exactly is hard brick?
2) Possible ways in which one could end up with a hard bricked phone? (Mainly SGS3)
3) Possible ways of recovery from hard brick?
Thanks a lot in advance. I want this thread to be a complete source of information to anyone who is new to flashing & needs DO's & DONT's of flashing properly.
Click to expand...
Click to collapse
1: You hardbricked your phone if you can't power it on at all. That means no Recovery and no Download mode. No lifesign at all.
A softbrick on the other hand is the situation that your phone powers up but stucks at a certain point and you can`t boot it up to the OS. However Recovery and/or Download Mode is still accessible, so you can flash a ROM, which usually solves the problem.
2: If you screw up the Bootloader. How can you screw up the bootloader? If you flash the bootloader through Odin there is always the chance that during the flash process your OS crashes or you by accident disconnect the USB cable. Although I heard cases where people hardbricked their phones during flashing a ROM through CWM (like in your case). This however doesn't make sense because like you already said most ROMs don't touch the Bootloader, so even if something happens during the flashing process, you should still be able to get at least to Download Mode. So with cases like that I assume that it is a hardware failure of some sort.
3: If you screwed up the bootloader then you can bring your phone back to life by using JTag. There are people who do this for a little money, so if you don't have warranty anymore, this is the way to go because it's a lot cheaper than replacing the mainboard.
Thanks a lot
Thanks for such an informative reply. Really appreciate it.
Scarface1991 said:
1: You hardbricked your phone if you can't power it on at all. That means no Recovery and no Download mode. No lifesign at all.
A softbrick on the other hand is the situation that your phone powers up but stucks at a certain point and you can`t boot it up to the OS. However Recovery and/or Download Mode is still accessible, so you can flash a ROM, which usually solves the problem.
Click to expand...
Click to collapse
I know the symptoms. But what exactly is a hard brick? Hardware is burned out? Software isn't able to communicate with hardware? Like, what happens exactly inside the phone?
Scarface1991 said:
2: If you screw up the Bootloader. How can you screw up the bootloader? If you flash the bootloader through Odin there is always the chance that during the flash process your OS crashes or you by accident disconnect the USB cable. Although I heard cases where people hardbricked their phones during flashing a ROM through CWM (like in your case). This however doesn't make sense because like you already said most ROMs don't touch the Bootloader, so even if something happens during the flashing process, you should still be able to get at least to Download Mode. So with cases like that I assume that it is a hardware failure of some sort.
Click to expand...
Click to collapse
How can one screw up during bootloader update/flash? The process takes like 5 seconds!!
Plus Samsung Galaxy S3 GT-I9300 doesn't allow flashing of any other device's bootloader.(Yeah yeah, I was about to flash GT-I9305's bootloader on mine by mistake!) Odin stops automatically during flashing. I don't know whether it is a security feature by phone or odin but whatever it is, it ROCKS!
saurabh_goyal93 said:
Thanks for such an informative reply. Really appreciate it.
I know the symptoms. But what exactly is a hard brick? Hardware is burned out? Software isn't able to communicate with hardware? Like, what happens exactly inside the phone?
Click to expand...
Click to collapse
The Bootloader is the first thing that is loaded when you power up your phone. If you screw up the bootloader your phone won`t boot up at all. This is caused by the user of the phone, that`s why people say: "Your hardbricked your device".
If your hardware fails to function properly because of whatever reason then it`s not a hardbrick but simply a hardware failure. It is in most cases not caused by the user (except if someone would be dumb enough to overclock CPU/GPU to a ridiculous high level)
How can one screw up during bootloader update/flash? The process takes like 5 seconds!!
Plus Samsung Galaxy S3 GT-I9300 doesn't allow flashing of any other device's bootloader.(Yeah yeah, I was about to flash GT-I9305's bootloader on mine by mistake!) Odin stops automatically during flashing. I don't know whether it is a security feature by phone or odin but whatever it is, it ROCKS!
Click to expand...
Click to collapse
Look at the XDA Q&A Threads. There are several cases a day where people have problems flashing something on their phones because Odin fails for some reason. That`s why I would use Odin only when it`s really necessary. When I had my first Smartphone (Samsung Wave) I flashed a lot of stuff on it and one time the flash tool just reported an error and that`s it (bootloader was screwed). I don't know why it failed until this day. So flash a bootloader only if it`s absolutely necessary because this is the most dangerous thing that you can do to your device.
I hard bricked my phone by rushing to install a new ROM before i had to leave for work. Later when I retraced my steps I realized that I made a stupid and critical mistake. I installed a ROM for a Galaxy S2 onto my Galaxy S3.
The installation appeared to be going smoothly. When it was complete I pressed the "reboot now" button. My phone turned off and never turned back on.
Now the phone has no signs of life. No Power, No Recovery, No download mode, No drivers when I plug it into a computer USB port. The computer does recognize that some kind of USB device is connected to it though. Which is what makes me believe that the phone is not dead and must be repairable.
I've done research and it appears that there are 3 options. (Please let me know if there are more)
Option #1: Pay someone to perform a JTAG repair service.
Option #2: Attempt to boot into recovery using a JIG.
Option #3: Play dumb and return my phone under warranty.
Questions
Option #1: is there a kit you can buy to perform this JTAG repair yourself? I will be more careful in the future but I don't want to be helpless if this ever happens again.
Option #2: I find conflicting advice here. Will this help my phone? eBay sellers warn that a JIG will not help a phone boot into download mode if it doesn't even power on at all. Has anyone attempted this with a phone in the same condition as mine? if so, what was the outcome?
Option #3: The easy way out . But also the defeated unhonest route I would rather avoid. It seems that most people reporting a phone in this condition never explain how they fixed their phone. What do they do?
My phone is still under warranty. Will they be able to detect that I caused the malfunction if I tell a lie that this just happened one day after charging the phone over night?
What do people do when their warranty has expired?
Please let me know how you handled this?
I hope this at least helps someone prevent what I did. Take your time!
I look forward to any advice
Sent from my SGH-I747M using xda app-developers app
fullycompletely said:
I
This is I9300 forum if you do not have I9300 this is the wrong forum and any advice may not apply to your phone .
You say >>>>>
SGH-I747M
Option #1: Pay someone to perform a JTAG repair service.
That may work but it depends upon the actual problem .
Option #2: Attempt to boot into recovery using a JIG.
Dirt Cheapo always worth a try .
Option #3: Play dumb and return my phone under warranty.
It will be either rejected for warranty or repaired .
Questions
Option #1: is there a kit you can buy to perform this JTAG repair yourself?
YES use GOOGLE search .
I will be more careful in the future but I don't want to be helpless if this ever happens again.
But JTAG is no magic solution .
helpless is a simple fact of reading the faqs and guides after its broken .
Option #2: I find conflicting advice here. Will this help my phone? eBay sellers warn that a JIG will not help a phone boot into download mode if it doesn't even power on at all. Has anyone attempted this with a phone in the same condition as mine? if so, what was the outcome?
READ the JTag thread .
My phone is still under warranty. Will they be able to detect that I caused the malfunction if I tell a lie that this just happened one day after charging the phone over night?
What do people do when their warranty has expired?
Phone is not old enough for no warranty but warranty refused then you pay .
Click to expand...
Click to collapse
fullycompletely said:
I hard bricked my phone by rushing to install a new ROM before i had to leave for work. Later when I retraced my steps I realized that I made a stupid and critical mistake. I installed a ROM for a Galaxy S2 onto my Galaxy S3.
The installation appeared to be going smoothly. When it was complete I pressed the "reboot now" button. My phone turned off and never turned back on.
Now the phone has no signs of life. No Power, No Recovery, No download mode, No drivers when I plug it into a computer USB port. The computer does recognize that some kind of USB device is connected to it though. Which is what makes me believe that the phone is not dead and must be repairable.
I've done research and it appears that there are 3 options. (Please let me know if there are more)
Option #1: Pay someone to perform a JTAG repair service.
Option #2: Attempt to boot into recovery using a JIG.
Option #3: Play dumb and return my phone under warranty.
Questions
Option #1: is there a kit you can buy to perform this JTAG repair yourself? I will be more careful in the future but I don't want to be helpless if this ever happens again.
Option #2: I find conflicting advice here. Will this help my phone? eBay sellers warn that a JIG will not help a phone boot into download mode if it doesn't even power on at all. Has anyone attempted this with a phone in the same condition as mine? if so, what was the outcome?
Option #3: The easy way out . But also the defeated unhonest route I would rather avoid. It seems that most people reporting a phone in this condition never explain how they fixed their phone. What do they do?
My phone is still under warranty. Will they be able to detect that I caused the malfunction if I tell a lie that this just happened one day after charging the phone over night?
What do people do when their warranty has expired?
Please let me know how you handled this?
I hope this at least helps someone prevent what I did. Take your time!
I look forward to any advice
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
try a USB Jig. only a few £ off ebay etc.
Hey guys,
I have a galaxy s3 (I9300) and I've had it rooted for some time now. I started using CyanogenMod 10.2 nightlies a few months ago and they've mostly been fine. The odd issue comes up but I've been able to work it out. So, a few hours ago my phone just turned off of its own accord and started to bootloop, but on the "Samsung Galaxy S3 GT-19300" screen, not the CyanogenMod screen (to clarify, this screen comes up first then the cyanogenmod one usually). I've tried booting into recovery (CWM 6) but it just shows the CWM boot logo thing (that cog with the hat) and then loops back to the galaxy s3 page. I've also tried putting it in download mode, and it seems to stay on the warning page longer than it does anywhere else, but it wont let me actually put in it download mode from there.
I had a look around google and saw people have had the same problem, but everything I could find was when people had flashed a new rom/kernel etc. and something had gone wrong in the process. The weird thing about mine is that I haven't changed anything, even downloaded any new apps, for maybe a week, so it's not like something suddenly changed. I also wasn't using it when it started, it was just sitting on the table next to me.
Usually I can work these things out, but I'm stumped here. Any help would be really appreciated.
Thanks in advance!
danielbollom said:
Hey guys,
I have a galaxy s3 (I9300) and I've had it rooted for some time now. I started using CyanogenMod 10.2 nightlies a few months ago and they've mostly been fine. The odd issue comes up but I've been able to work it out. So, a few hours ago my phone just turned off of its own accord and started to bootloop, but on the "Samsung Galaxy S3 GT-19300" screen, not the CyanogenMod screen (to clarify, this screen comes up first then the cyanogenmod one usually). I've tried booting into recovery (CWM 6) but it just shows the CWM boot logo thing (that cog with the hat) and then loops back to the galaxy s3 page. I've also tried putting it in download mode, and it seems to stay on the warning page longer than it does anywhere else, but it wont let me actually put in it download mode from there.
I had a look around google and saw people have had the same problem, but everything I could find was when people had flashed a new rom/kernel etc. and something had gone wrong in the process. The weird thing about mine is that I haven't changed anything, even downloaded any new apps, for maybe a week, so it's not like something suddenly changed. I also wasn't using it when it started, it was just sitting on the table next to me.
Usually I can work these things out, but I'm stumped here. Any help would be really appreciated.
Thanks in advance!
Click to expand...
Click to collapse
can you at least enter download mode after a long time you said? if not, try pulling out the battery for 5 minutes or more and re-insert and enter download mode. i hope it's not sds! good luck
sriram231092 said:
can you at least enter download mode after a long time you said? if not, try pulling out the battery for 5 minutes or more and re-insert and enter download mode. i hope it's not sds! good luck
Click to expand...
Click to collapse
Nope, if I press the volume up button to go into it, it just goes back to the bootloop. I'll try the battery thing though, thanks!
Nope, it didnt work, I left it out for maybe half an hour and nothings changed :/ anyone else got any ideas?
SDS thread and BootLoop identical questions posted .
What does Product Code say in download mode .
But if you cannot get to download mode then you need a service centre repair .
looks like u are facing SDA but a bit diffrend than a normal SDS.. mine still can go into download mode with blank product name..
If product name is blank in download mode then you got sudden death, consider a phone as a brick. Nothing will help, including repartitioning.
You need to contact service centre.
I'll check it in a minute, but if it is bricked, will any service center actually help me seeing as it's rooted and all?
danielbollom said:
I'll check it in a minute, but if it is bricked, will any service center actually help me seeing as it's rooted and all?
Click to expand...
Click to collapse
AFAIK if it's sudden death then it's not possible to detect root and other modified things, or in other words - nobody has money to prove that you have been using unofficial firmware .
JustArchi said:
AFAIK if it's sudden death then it's not possible to detect root and other modified things, or in other words - nobody has money to prove that you have been using unofficial firmware .
Click to expand...
Click to collapse
Ahhhh, well that is handy then
In terms of a service centre, will samsung have a list of them somewhere so I can find one near me?
So I contacted samsung and they gave me the link to book into a service centre etc, but I just realised that when I try to go into recovery mode, the CWM recovery logo comes up before going back to bootloop. Is there any way to get rid of that so that my root is completely untraceable?
danielbollom said:
So I contacted samsung and they gave me the link to book into a service centre etc, but I just realised that when I try to go into recovery mode, the CWM recovery logo comes up before going back to bootloop. Is there any way to get rid of that so that my root is completely untraceable?
Click to expand...
Click to collapse
If you can't flash anything with Odin (stock software) then you're screwed. Eventually you can try to enter recovery and flash "eraser" of recovery, but this requires working recovery... So if you actually can enter recovery then you can also flash anything, which will literally delete everything.
In other case, no, no way. But if you're lucky enough you may break it just by leaving your phone on for some hours in bootloop, haha.
JustArchi said:
If you can't flash anything with Odin (stock software) then you're screwed. Eventually you can try to enter recovery and flash "eraser" of recovery, but this requires working recovery... So if you actually can enter recovery then you can also flash anything, which will literally delete everything.
In other case, no, no way. But if you're lucky enough you may break it just by leaving your phone on for some hours in bootloop, haha.
Click to expand...
Click to collapse
Is there any way to wipe it with magnets or anything? hahah I'm clutching at straws now, but otherwise I'm just left with an expensive paperweight so I'm trying to find anything I can
danielbollom said:
Is there any way to wipe it with magnets or anything? hahah I'm clutching at straws now, but otherwise I'm just left with an expensive paperweight so I'm trying to find anything I can
Click to expand...
Click to collapse
To be honest think twice before physically crashing your internal memory, as it may void your warranty at all.
I'd try flashing stock firmware through odin, if it doesn't work I'd try flashing anything through recovery. If both of these methods fail just leave your phone in bootloop and hope that it'll automatically destroy everything... :laugh:
Seriously though, you can either physically destroy internal memory or leave it in bootloop and hope for the best, eventually send them device in current status. Up to you, because you won't have a possibility to do anything else.
JustArchi said:
To be honest think twice before physically crashing your internal memory, as it may void your warranty at all.
I'd try flashing stock firmware through odin, if it doesn't work I'd try flashing anything through recovery. If both of these methods fail just leave your phone in bootloop and hope that it'll automatically destroy everything... :laugh:
Seriously though, you can either physically destroy internal memory or leave it in bootloop and hope for the best, eventually send them device in current status. Up to you, because you won't have a possibility to do anything else.
Click to expand...
Click to collapse
If I send it back to them as it is now it'll take them about 20 seconds I reckon before they see the CWM logo, realise its rooted and send it straight back, so I dont know what I'm gonna do hahah