Related
I think I've bricked my Galaxy S II.. I got it yesterday and tried to flash 2.3.5. When I was flashing with Odin, the program went unresponsive and crashed. There was nothing else to do but take out the battery.. I shouldn't have done it, but I did. And now it won't turn on at all. I've tried the 3 button method, for download mode, and a jig from my old i9000. Nothing has worked. The screen wont even turn on. I don't know what to do... Help Please??
you need a jtag.If it wont go into download or recovery its gone.
What do you, Jtag? I've got a usb jig, does that work? Or are they the same thing?
*What do you mean
aren't jigs phone-specific?
Any new info on this? Did jtag worked or whatever. I keep eye on this thread but looks like OP disappeared. Genuinely curious what happened with the phone.
Hmm .. very wierd that phone wont turn on ... i have broken Odin flashes purposedly many times myself but always I can get back into it ...
You could try power drain ... remove battery ... press power on button for 10 seconds (WITHOUT BATTERY IN) ... now put battery back in and try to go into Download mode.
Sorry but i got busy with other stuff but wanted to explain to him about the JTag.Its a special box called a RiffBox JTag and what it does is basically wipes the motherboard/bootloader and in most phones repears the bootloader aswell of a fully bricked phone so it can be put into download mode again letting you re-flash via Odin and thus saving your phone.A little miracle that means no more bricked phones.There doesnt seem to be that many around and to buy they aint cheap at all but if you can find a dealer or a phone shop who has one they can do it for you.For example.I bicked my phone and was going to buy the box on ebay.es imported (in spain there isnt any for sale) for 160euros complete or 140 without cables.Searched this site:
http://www.jtagbox.com/riff-jtag-bo...s-unbrick-bricked-phone-riff-box-owners-list/
and found a shop in Barcelona who did it for me for 35euros plus postage "BARGIN!!!!".If you search youtube and google for RiffboxJtag in your country you should find someone with a unit willing to help out or check the link ive given as it has a list of users worldwide.
EDIT:A jig is not a JTag.A jig will boot your SEMI-BRICKED(phone showing some kind of life ex.classic icon of phone/arrow/computor,menu and back arrow lights work e.t.c.) phone into download mode.A FULLY-BRICKED(dead,no signs of life.wont start.no download,recovery,lights nothing.DEAD!!!) phone needs a JTag
@cooza , Thanks for that explanation and site I even found one near me, that some day might come handy.
I must ask now to further clear my doubts, this riffjtag box, like you said is able to "revive" or "unbrick" _any_ bricked SGS2? No matter how bad is it? Im kinda new around these things and trying to suck up as much info/knowledge possible, before I decide to flash/root/?brick? xD haha ( hope not for last one) my phone.
Devourz said:
@cooza , Thanks for that explanation and site I even found one near me, that some day might come handy.
I must ask now to further clear my doubts, this riffjtag box, like you said is able to "revive" or "unbrick" _any_ bricked SGS2? No matter how bad is it? Im kinda new around these things and trying to suck up as much info/knowledge possible, before I decide to flash/root/?brick? xD haha ( hope not for last one) my phone.
Click to expand...
Click to collapse
Hi.As i said before there are semi and hard bricked phones.A semi bricked phone can normally be booted into download mode with the 3 button combo or a jig and your away again.It has the usuall symbol of a phone and a PC with a warning sign in the middle of them.Hard bricked is when the bootloader is damaged and there is basically no return.You got yourself a very expensive paper-weight for the office desk.Its like trying to turn on your phone with no battery in it.Dead,gone and not coming back.Before the Riffbox the only solution was the rubbish bin or maybe change the motherboard(but a few years ago that was an extremely pricey task if possible).Now we have the box.You can screw you phone to the point of no return and still the box will bring it back to life as it wipes the motherboard and in the case of the SGS2 also repears the damaged bootloader which is what boots your phone to start with.One thing to know,and i dont know if it happens to everyone but mine came back with 2.3.3 installed but there was no recovery mode.If this happens all you have to do is re-flash via Odin a more reciente firmware WITHOUT PIT FILE and yourll get recovery mode back at reboot.Obviously youll need to plug in your phone before hand to re-install the drivers.Same with Odin.boot to download,plug in,installs,unplug,then open Odin and flash.
EDIT:yourve got my name there so if something ever happens and you need a hand to re-flash after a jtag just send me a private message.Here to help.
SamBroomby said:
I think I've bricked my Galaxy S II.. I got it yesterday and tried to flash 2.3.5. When I was flashing with Odin, the program went unresponsive and crashed. There was nothing else to do but take out the battery.. I shouldn't have done it, but I did. And now it won't turn on at all. I've tried the 3 button method, for download mode, and a jig from my old i9000. Nothing has worked. The screen wont even turn on. I don't know what to do... Help Please??
Click to expand...
Click to collapse
im not juding you...but next time is better to flash with CWM.
Odin only for root kernel...
cooza said:
Hi.As i said before there are semi and hard bricked phones.A semi bricked phone can normally be booted into download mode with the 3 button combo or a jig and your away again.It has the usuall symbol of a phone and a PC with a warning sign in the middle of them.Hard bricked is when the bootloader is damaged and there is basically no return.You got yourself a very expensive paper-weight for the office desk.Its like trying to turn on your phone with no battery in it.Dead,gone and not coming back.Before the Riffbox the only solution was the rubbish bin or maybe change the motherboard(but a few years ago that was an extremely pricey task if possible).Now we have the box.You can screw you phone to the point of no return and still the box will bring it back to life as it wipes the motherboard and in the case of the SGS2 also repears the damaged bootloader which is what boots your phone to start with.One thing to know,and i dont know if it happens to everyone but mine came back with 2.3.3 installed but there was no recovery mode.If this happens all you have to do is re-flash via Odin a more reciente firmware WITHOUT PIT FILE and yourll get recovery mode back at reboot.Obviously youll need to plug in your phone before hand to re-install the drivers.Same with Odin.boot to download,plug in,installs,unplug,then open Odin and flash.
EDIT:yourve got my name there so if something ever happens and you need a hand to re-flash after a jtag just send me a private message.Here to help.
Click to expand...
Click to collapse
Thank you mate! I am getting my SGS2 this week so ive been doing alot of reading and research about everything. Thanks for your contribution and kind offer to help if ever comes to that. Very appreciated.
No worries mate.truth is its very hard to fully hard-brick an i9100.The main thing to watch out for,and its a mistake that first-time users/flashers have done,is to flash there i9100 phones with i9000 firmware by mistake.An SGS is not an SGS2 and if they are mixed you WILL hard-brick your device.Here on XDA everything is clearly marked and on their right pages so you cant go wrong if you take your time dont rush-in.But just in case you havnt seen it heres the thread:
Firmwares:
http://forum.xda-developers.com/showthread.php?t=1075278
CF-Root Kernels: (if you feel the need)
http://forum.xda-developers.com/showthread.php?t=1103399
Hi, dont bother faffing with it mate, if you have only had it a day take it back and tell them it wouldnt boot after an automatic Kies update. If they cant turn it on they wont know you bricked it until it gets back to the factory and to be honest after selling 10 million of these babies they wont even bother checking it out, they'll just put it into spares or straight recondition it.
I did the same thing to my xoom, PC world couldnt turn it on so they just gave me another.
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.
Well in my evil experimenting ways, I managed to hard brick my SGP 4.0 (YP-G1CWY/XAA)... well at least I think it is hard bricked.
Symptoms...
* The unit will not power on at all. (even with a fully charged battery)
* Completely black screen
* Holding the Power button for a whole minute does nothing.
* Holding Power Button + Volume Up or Down for a whole minute do nothing.
* Plugging it into a USB port (or a Wall-Adapter) does nothing. Doesn't even show a battery icon. I don't even think the unit is even getting warm.
I suspect this is a full brick. I am unsure what my options are at this point. I heard that something called a USB JIG might fix this problem, but I don't know if it will. I am unsure if this USB JIG device is compatible with my particular device. (YP-G1CWY/XAA)
Any help would be appreciated. Thank you.
Kwipper said:
Well in my evil experimenting ways, I managed to hard brick my SGP 4.0 (YP-G1CWY/XAA)... well at least I think it is hard bricked.
Symptoms...
* The unit will not power on at all. (even with a fully charged battery)
* Completely black screen
* Holding the Power button for a whole minute does nothing.
* Holding Power Button + Volume Up or Down for a whole minute do nothing.
* Plugging it into a USB port (or a Wall-Adapter) does nothing. Doesn't even show a battery icon. I don't even think the unit is even getting warm.
I suspect this is a full brick. I am unsure what my options are at this point. I heard that something called a USB JIG might fix this problem, but I don't know if it will. I am unsure if this USB JIG device is compatible with my particular device. (YP-G1CWY/XAA)
Any help would be appreciated. Thank you.
Click to expand...
Click to collapse
so i have your device. i ordered one and am going to receive it hopefully tomorrow. my friend has it he just needs to give it to me. so i can tell you if it works. ill send you a link to which one i bought and if it works ill let you know so you can invest in it.
That would be great! Please let me know. =)
Well I now know why my device hard bricked. I was trying to use Odin 1.8.5 to flash a rom (the one under G1UEKI8) that I downloaded from this page....
http://forum.xda-developers.com/showthread.php?t=1531850
... and apparently I didn't know that it had a boot loader inside of it. (sbl.bin) When I flashed the rom, it also flashed the bootloader as well, causing it to brick. Honestly, I'm kinda suprised that it did brick. The ROM should have been for my device. I checked the model numbers n' everything, yet it still bricked.
Is there anyway we can put a warning out about this particular ROM?
I actually flashed that same ROM and my device booted up but the touch screen don't work that's why I had to get the jig
Sent from my MB855 using XDA
Same exact thing happened to me. I dont think there is a fix since i spent countless hours installing ubuntu and trying to use the ressurectore. Since the pc doesnt even detect it i gave up. I took it to best buy no questions asked they returned all the money and insurance money to. I decided to get a ipod touch instead and wait for the galaxy player 4.2 . Well you would better be off returning it for a new one.
Hyperrunner said:
Same exact thing happened to me. I dont think there is a fix since i spent countless hours installing ubuntu and trying to use the ressurectore. Since the pc doesnt even detect it i gave up. I took it to best buy no questions asked they returned all the money and insurance money to. I decided to get a ipod touch instead and wait for the galaxy player 4.2 . Well you would better be off returning it for a new one.
Click to expand...
Click to collapse
shoulda waited until i had news on the jig. if i can get it into download mode then im sure i can fix it. patience is a virtue.
Ok as you have saw sbl.bin isn't the only bootloader file. As boot.bin, sbl.bin and param.lfs are the bootloader files, they are NECESSARY to a full device restore. I have tried it with my device and it does work. But as I said if you are here for just a upgrade or a back to stock DO NOT FLASH IT. mime can test it when his jig will come in. (if he wants.)
Btw the bootloader files are from Klin1344 and he does have a US player.
zaclimon said:
Ok as you have saw sbl.bin isn't the only bootloader file. As boot.bin, sbl.bin and param.lfs are the bootloader files, they are NECESSARY to a full device restore. I have tried it with my device and it does work. But as I said if you are here for just a upgrade or a back to stock DO NOT FLASH IT. mime can test it when his jig will come in. (if he wants.)
Btw the bootloader files are from Klin1344 and he does have a US player.
Click to expand...
Click to collapse
ill test it still waiting for it.
Hey guys! Sorry I'm taking so log with te jig. Should be in tonight. Not making promises. Lol.
Sent from my MB855 using XDA
Confirmed! the jig works. now on to test the full recovery
---------- Post added at 04:21 AM ---------- Previous post was at 04:10 AM ----------
oficially messed up my device. wont turn on and jig doesnt even work. no button combos work.
Okay. So let me get this clear. You had a completely dead Samsung Galaxy Player 4.0 (YP-G1CWY/XAA). Dead meaning...
... there was a completely black screen
... Nothing you did made the screen turn on
... plugging the USB charger did nothing, (not even a battery icon)
... but plugging in this JIG actually got you to a download screen? If so... THIS IS AWESOME!
It was not completely dead. It dead now. Lol. The touch screen didnt work so I could t get o download mode. Used the jig it worked. Flashed full recovery and its dead now jig won't wok
Sent from my MB855 using XDA
I'm a noob (and I watched the video just a while ago) and I'm pretty sad to make my first XDA developers' forum post with an embarrassing failure post. The symptoms I'm having with my 2 days new YP-G1CWY/XAA are exactly the same as the OP's. I'm just trying to leave my record of what and how it happened.
- Encouraged by my success of installing CM7 on a Galaxy Player 5.0 US by following http://forum.xda-developers.com/showthread.php?t=1540255 , I decided to install CM7 on a Galaxy Player 4.0 US by following http://forum.xda-developers.com/showthread.php?t=1527576 .
- Steve's kernel installed well (followed http://forum.xda-developers.com/showthread.php?t=1377771 ). Then proceeded to install the ROM using the recovery mode. This installation completed well (at least it said so).
- However, it showed the boot-loop phenomenon. I tried to reinstall the ROM again using the same instruction, but didn't help. So I thought I should try a full recovery by following http://forum.xda-developers.com/showthread.php?t=1531850 . I believe I used the corect .pit file and the correct .tar.md5 file (G1UEKI8).
- Now I have a fully bricked Galaxy Player 4.0 US, leaving only a battery that effectively cost $180.
- I tried to use the unbrickable resurrector by AdamOutler (following http://forum.xda-developers.com/showthread.php?t=1369799 and http://forum.xda-developers.com/showthread.php?t=1386669 <-- this one is titled for Gal Player 5.0), but neither worked at all. I used a separate machine (an old PC that runs Ubuntu just well), and I'm not sure if it's just a coincidence, but just plugging in the bricked GP 4.0 to this Ubuntu box and trying the unbrickable resurrector crashed the Ubuntu box several times and now the Ubuntu box doesn't boot up!
I think the post "[STOCK ROM] Full Recovery For Samsung Galaxy Player/S Wifi 4.0" ( http://forum.xda-developers.com/showthread.php?t=1531850 ) should be removed or marked with a very strong warning. In that post, I don't see any reply reporting a success, but only reports of bricked players.
Hopefully someone comes up with a magical solution, or if I can learn how to tackle this with some other experienced developers' help, I'd be more than happy to try it... Thanks anyway to all community members for showing how to do all these.
danadara said:
I'm a noob (and I watched the video just a while ago) and I'm pretty sad to make my first XDA developers' forum post with an embarrassing failure post. The symptoms I'm having with my 2 days new YP-G1CWY/XAA are exactly the same as the OP's. I'm just trying to leave my record of what and how it happened.
- Encouraged by my success of installing CM7 on a Galaxy Player 5.0 US by following http://forum.xda-developers.com/showthread.php?t=1540255 , I decided to install CM7 on a Galaxy Player 4.0 US by following http://forum.xda-developers.com/showthread.php?t=1527576 .
- Steve's kernel installed well (followed http://forum.xda-developers.com/showthread.php?t=1377771 ). Then proceeded to install the ROM using the recovery mode. This installation completed well (at least it said so).
- However, it showed the boot-loop phenomenon. I tried to reinstall the ROM again using the same instruction, but didn't help. So I thought I should try a full recovery by following http://forum.xda-developers.com/showthread.php?t=1531850 . I believe I used the corect .pit file and the correct .tar.md5 file (G1UEKI8).
- Now I have a fully bricked Galaxy Player 4.0 US, leaving only a battery that effectively cost $180.
- I tried to use the unbrickable resurrector by AdamOutler (following http://forum.xda-developers.com/showthread.php?t=1369799 and http://forum.xda-developers.com/showthread.php?t=1386669 <-- this one is titled for Gal Player 5.0), but neither worked at all. I used a separate machine (an old PC that runs Ubuntu just well), and I'm not sure if it's just a coincidence, but just plugging in the bricked GP 4.0 to this Ubuntu box and trying the unbrickable resurrector crashed the Ubuntu box several times and now the Ubuntu box doesn't boot up!
I think the post "[STOCK ROM] Full Recovery For Samsung Galaxy Player/S Wifi 4.0" ( http://forum.xda-developers.com/showthread.php?t=1531850 ) should be removed or marked with a very strong warning. In that post, I don't see any reply reporting a success, but only reports of bricked players.
Hopefully someone comes up with a magical solution, or if I can learn how to tackle this with some other experienced developers' help, I'd be more than happy to try it... Thanks anyway to all community members for showing how to do all these.
Click to expand...
Click to collapse
wow... why does the US player have that much of a problem?
Anyway I closed the US link so no one can download it (Sorry for the devices bricks)
zaclimon said:
wow... why does the US player have that much of a problem?
Anyway I closed the US link so no one can download it (Sorry for the devices bricks)
Click to expand...
Click to collapse
I think that it would work without the bootloaders because all the partitions are pulled directly from the device and can be flashed. Besides, if you don't flash bootloaders, the worst that could happen is just a soft-brick, which can be recovered.
klin1344 said:
I think that it would work without the bootloaders because all the partitions are pulled directly from the device and can be flashed. Besides, if you don't flash bootloaders, the worst that could happen is just a soft-brick, which can be recovered.
Click to expand...
Click to collapse
Maybe but if someone is coming from CM7, it can be different. I think I'll put a last link, if it's dont work by then I'll leave US support.
EDIT: Nvm what I said about CM7
Someone possibly posted a binary counter reset zip for the att note obviously renamed it as att reset counter zip,which was probably for the wrong model phone... can anyone help cause i believe that is what happened my m****fin phone wont reboot and i followed the instructions and the provided download link for the att reset-counter zip
after i flashed it in cwm the note wont turn on i get and can hear usb recognition when plugged into pc but screen is black , battery pull wont work download mode wont come on
Feeling like a victim here with no solution??
HELP ANYONE?
lojak29 said:
whoever the pos is that posted a binary counter reset zip for the att note obviousally renamaed it as att reset counter zip,wich was probably for the wrong model phone... can anyone help cause i believe that is what happened my m****fin phone wont reboot and i followed the instructions and the provided download link for the att reset-counter zip
after i flashed it in cwm the note wont turn on i get and can hear usb recognition when plugged into pc but screen is black , battery pull wont work download mode wont come on
Feeling like a victim here with no solution??
HELP ANYONE?
Click to expand...
Click to collapse
Well just because the screen is BLACK does not mean that your phone is not in download mode.......i would put the phone into download mode and plug it up to odin anyway....see if goes yellow for the com port #
and if your accusing someone of blatently bricking your phone with a false file......you will be hard pressed to prove that here. i dont see ANY i7000 dev thread over here.
so just be a little more careful next time.
no i followed the links in xda that is supposed to be reputable
I used the att counter reset .zip NOT THE ROGERS NOT THE TELUS!!
And it said flash successfull.
when i reboot from cwm nothing nothing !!
and every other follow up said nothing but yay and awesome and worked perfect!
What gets me is wtf happened.
i can see it recognized when i plug into my pc and when i hold power button i can hear stuff on the pc but the screen has no response I tried to see if i could get a port to recognize by vol down and power but no com ports appear
Calm down, there is no reason to call anyone out.
You knew the risks of flashing beforehand. If your phone is recognized by the computer then it means it's not bricked. Don't just assume it's bricked. There are things called jigs, if you have done your search before freaking out.
Just saying.
Well ive also read that qhbusb dload is a bad sign meaning hardbrick
since it accepts the device as unrecognized
the screen of death so called is being described as what im dealing with on forums
hyukki said:
Calm down, there is no reason to call anyone out.
You knew the risks of flashing beforehand. If your phone is recognized by the computer then it means it's not bricked. Don't just assume it's bricked. There are things called jigs, if you have done your search before freaking out.
Just saying.
Click to expand...
Click to collapse
just an fyi on all samsung 2.3.6 the jig was disabled by samsung. you now have to have the device jtaged by an asr
drksilenc said:
just an fyi on all samsung 2.3.6 the jig was disabled by samsung. you now have to have the device jtaged by an asr
Click to expand...
Click to collapse
Yep mine was in that state and a jig dint work, got it replaced by ATT cause they cant really figure with the phone in that state.
So just to confirm, you have blindly tried to get into download mode, you do have the samsung SGH-I717 USB Drivers installed on your machine, and ODIN does not recognize the phone? If you havent done all of that, start with the USB Drivers, then try to blindly get into DL mode via vol down+power from a hard off state. Wait for the vibrate then let go, with the drivers installed and the phone in "DL" mode Odin should recognize it. If it does you can flash back to stock with the appropriate files.
Hope that gives you a place to start.
Lojak et al: Flashing .....
YOUR PHONE IS YOUR RESPONSIBILITY........
Know who made the rom/kernel etc and read carefully BEFORE flashing things..... 99.8% of the ppl in XDA are good responsible members, just have to watch out for the exception.
But, bear in mind what you do to your phone is YOUR issue not anyone's here and....... caveat emptor is the advice Everyone can only offer. Many here might be able to help you resolve, just calm down and think it through, then post logically the issues and the members will offer some ideas up.... they always do....
Why would you want to reset the counter? My understanding is that Samsung will still know whether you flashed your phone or not...
Sent from my SAMSUNG-SGH-I717 using XDA
stulzerl said:
Why would you want to reset the counter? My understanding is that Samsung will still know whether you flashed your phone or not...
Sent from my SAMSUNG-SGH-I717 using XDA
Click to expand...
Click to collapse
I was under the impression that as long as the counter is 0 they won't know you've flashed it. Is this wrong?
its interesting to see how worried people are when it comes to a flash counter issue if you turn your phone in to be repaired/replaced under warranty.
when you think about the thousands of phones that go in weekly for warranty claims, do you know how many techs they would have to employ to start checking all the phones binary counters?
I'm sure that if any testing at all goes on, with a warranty claimed phone, is no more than just trying to turn it on, and if it doesn't come on, then its just moved on down the return line...
Obvious signs of abuse, would probably give them a reason to take a closer look, but how many people do any of you know that have warranty claims turned down because they flashed a custom rom?
I've been on phone forums for many years, and read thousands of posts, and I can't even think of a handful of times that I read about someone getting turned down for warranty repair/replacement because of their flash counter.
Hell, Sprint even has an official "policy" on how to handle warranty issues with rooted phones.
The yellow triangle annoys me, so I will try and get rid of that when it shows up, but I don't care what my flash counter says..
Hey guys !
Well...
Yesterday, I decided to flash a new ROM on my aunt's SII...
It wasn't the first time I did this : my own phones have all been flashed, I know how it works !
But... I got a problem ! While I was wiping the data/cache, the phone got stuck on this step. Then, shut down. And now, it doesn't boot anymore. Screen stays black. I did everything I found on the web : tried to boot on recovery and on download mode, tried to press the buttons to get into these modes and inserting the battery while pressing, tried to connect it on USB (not even detected)...
After some researches, I found out that it was a eMMC problem...
Anyway, in a nutshell, my phone is hard bricked. What can I do ?
Thanks.
rohecla said:
Hey guys !
Well...
Yesterday, I decided to flash a new ROM on my aunt's SII...
It wasn't the first time I did this : my own phones have all been flashed, I know how it works !
But... I got a problem ! While I was wiping the data/cache, the phone got stuck on this step. Then, shut down. And now, it doesn't boot anymore. Screen stays black. I did everything I found on the web : tried to boot on recovery and on download mode, tried to press the buttons to get into these modes and inserting the battery while pressing, tried to connect it on USB (not even detected)...
After some researches, I found out that it was a eMMC problem...
Anyway, in a nutshell, my phone is hard bricked. What can I do ?
Thanks.
Click to expand...
Click to collapse
what stock firmware version was the Phone when u did the wipe from recovery (if it was on ICS 4.0.4 then ur phone will be bricked because of the kernel of ICS4.0.4 being plagued with the 'EMMMC' brick bug and only a JTAG or a MB replacement is the solution for it) .
JTAG won't work; motherboard replacement or bin.
I think it was 4.0.4...
Motherboard replacement is the only thing I can do ?
Mate.... Samsung KNOWS this is a problem.......I'd try for warranty repair/replacement.....if the phone is less than two years old, you have a good chance......
Just remember to 'act dumb' at the service center..... Tell them you were trying to use kies to update from ICS and the phone died...... If it is the emmc brickbug, there's NO WAY they can check what os was on ur phone or whether you'd rooted or modified it in any way.....right now it's an unrecoverable (expensive) paperweight........
This might be my S2, or it might be my W...but it's definitely CM
Yeah, I saw this is a quite common problem... But often, it's just a soft brick. In my case, it's a hard brick...
And warranty expired two months ago...
Well, it's unlikely to succeed, but you could try emailing Samsung explaining your situation regarding expired warranty and going on to explain that updating with kies is a 'normal' procedure and that it's that 'normal' Samsung provided procedure plus the 'unstable' OS version (having read on the internet about 4.0.4 brickbug) that have killed a phone that would otherwise be working today. Stress the point that the ICS firmware AND kies were both supplied by Samsung for official (end user) use on Samsung devices......see what they say.....can't hurt right?
This might be my S2, or it might be my W...but it's definitely CM
Yeah, they're going to honour an expired warranty. That happens all the time
Mb....I *did* say right at the start that it probably wouldn't work..... But what has he got to lose?
Lol.....they *might* be suffering from an excess of Xmas and new year goodwill.......
This might be my S2, or it might be my W...but it's definitely CM
I have twice super bricked my two SGS-2s.... EMMC bug is one hell of a pain in ass. You have to let go some SD card space, but u can revive you phone using the URL in my signature. I revived both my phones losing about a GB space in one and a couple GBs in other. Good Luck
alvinasnow said:
but u can revive you phone using the URL in my signature
Click to expand...
Click to collapse
People have said he needs a new motherboard.Do you know something they dont?.
S4 victim
The problem is that I can't flash anything ! The phone simply doesn't turn on ! No recovery mode, no download mode, nothing ! It doesn't even charge !
Yes try this link from alvinasnow
http://forum.xda-developers.com/showthread.php?t=1667886
So far as I know if you only connect your phone normally if it os charging then it already has some kind of connection with the pc I believe its adb.
But since you dont have warranty you can give it a shot to save money so just give it a try and read carefully. I was surprised when I got this phone, that samsung would make a big mistake like that its a just shame.
Edit: i dont know or you need jtag or riff and I will not test it cause I dont have a superbrick phone with mmc cap erase.
But just open device manager on the pc and connect the phone and see if there is a new device connected.
In my opinion my previous phone has one of the best options to make it unbrickable
It was nvflash but it sucked.nvidia wouldnt release sources.
Gooodluck with your phone
Sent from my GT-I9100 using Tapatalk
Which part of this phone needs a motherboard replacement are you lot having trouble comprehending ?
OK...For all the slow kids who keep posting to this thread (including the OP); this phone needs a new motherboard. No threads promising magical fixes are going to work, there is no other way to fix this.
Is this clear now or do I have to make another post in bolded caps to make it really clear ?
There is a SLIGHT chance that if a JTAG recovery house can boot a kernel via JTAG (I do not know if RIFFBox can do this or not), they can use the solution that the Kindle Fire community used. (This was a recent discovery 2-3 months ago)
The problem is, I have attempted to provide information on this solution to these JTAG houses with no response. I don't know if they can boot a modified kernel via JTAG or not.
Currently:
All Exynos4 devices that are Superbricked are unrecoverable, as Samsung refuses to provide any way to boot these from USB, and anyone who could develop a solution hasn't responded (since most dead devices are long gone at this point...)
All Qualcomm-based Samsungs that are Superbricked are hosed too
Kindle Fires that are Superbricked are recoverable as of 2-3 months ago thanks to some discoveries by Oranav that were used by Hashcode to develop a recovery solution. This solution can't be used on Samsung Exynos4 devices as it depends on the ability to boot the device from USB.
And folks...... @Entropy512 needs to be listened to.......he is the dev who has done the most research into this issue and (somebody cmiiw) was the one who discovered the "emmc cap erase" command was the culprit. I think he also wrote the original (much copied) 'got brickbug' app which tells you if your phone is affected or not. If what he says doesn't work, then as @MistahBungle says, the ONLY OTHER OPTION is a new motherboard........
This might be my S2, or it might be my W...but it's definitely CM
Well...
I think I'm just going to call the insurance, and see what they can do ! Even if my warranty is now void, they may replace the phone !
Thank you all !