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.
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.
Hi there!
This thread is my last hope, so please dont let me down folks...:cyclops:
The story short - one sunny morning i turned on my HTC Nexus One and it got stuck with te X on the screen for about 15 minutes, non of the buttons responded, so i did the first thing that came in my mind - i pulled out the battery. After inserting the battery the phone went full brick, i mean literally, no reaction on anything, even conected to the wall charger, there is no sign of life, no charging LED, nothing. Connected to the PC, it says USB device not recognised.
I dont think this is a hardware proble, the phone workwd fine until this interrupted power on. Phone runned on stock Androud, i have not played aroun with it - no bootloader unlock, no rooting.
I searched the internet for a solution, tried a lot of button combinations like in this thread:
http://forum.xda-developers.com/showthread.php?t=1069032
but still no luck, i cannot restore or flash it while my PC does not recognise the phone.
Found some info about those Usb Jig things, but they work only on Samsung phones, so, is there a way to force the phone to go in recovery mode, or give any sign of life so i can try to recover it or flash a diferent ROM?
The warranty has ended, so no hope there.
Hope there is a way out of this, and, sory for my bad english. :good:
Veesais said:
Hi there!
This thread is my last hope, so please dont let me down folks...:cyclops:
The story short - one sunny morning i turned on my HTC Nexus One and it got stuck with te X on the screen for about 15 minutes, non of the buttons responded, so i did the first thing that came in my mind - i pulled out the battery. After inserting the battery the phone went full brick, i mean literally, no reaction on anything, even conected to the wall charger, there is no sign of life, no charging LED, nothing. Connected to the PC, it says USB device not recognised.
I dont think this is a hardware proble, the phone workwd fine until this interrupted power on. Phone runned on stock Androud, i have not played aroun with it - no bootloader unlock, no rooting.
I searched the internet for a solution, tried a lot of button combinations like in this thread:
http://forum.xda-developers.com/showthread.php?t=1069032
but still no luck, i cannot restore or flash it while my PC does not recognise the phone.
Found some info about those Usb Jig things, but they work only on Samsung phones, so, is there a way to force the phone to go in recovery mode, or give any sign of life so i can try to recover it or flash a diferent ROM?
The warranty has ended, so no hope there.
Hope there is a way out of this, and, sory for my bad english. :good:
Click to expand...
Click to collapse
Well no, bricked is a term used when you are rooted and flash a bad rom,kernel,etc. You have no root, so you cannot be "bricked". Just a software failure, you cannot flash another rom because, again, you have no root or custom recovery. Your best bet is trying to send it back to your carrier and get it replaced
ParanoidKang said:
Well no, bricked is a term used when you are rooted and flash a bad rom,kernel,etc. You have no root, so you cannot be "bricked". Just a software failure, you cannot flash another rom because, again, you have no root or custom recovery. Your best bet is trying to send it back to your carrier and get it replaced
Click to expand...
Click to collapse
The warranty time is out, so there is no help from the carrier, unless for cash...
But there must be a way to bring it back to life.
Veesais said:
The warranty time is out, so there is no help from the carrier, unless for cash...
But there must be a way to bring it back to life.
Click to expand...
Click to collapse
Now the screen may not show, but try booting into fastboot mode by press and hold the Trackball+Power buttons together.
I'm not sure about the nexus one, but newer nexus devices have factory images, supplied by Google. If they exist for the nexus one, you should be able to save your device by flashing them through fastboot. That is if the images exist and you can get to fastboot.
Sent from my Nexus 4 using XDA Premium 4 mobile app
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
Hey everyone, i have an issue that i have searched for and can't seem to find anything exactly the same so thought id just jump and ask.
I have a GS3 that has suddenly decided to stop working. It is un-rooted and was stock. I had it on charge over night and woke up to find it like this.
When i try to power the phone on it simply goes to the samsung logo and stops there and if i try to charge it all i get is the initial battery image but it does not move to indicate that it is charging.
I have tried going into the recovery mode to reset data etc but when i do it is covered with red writing saying that it cant find system files and folders, so im thinking somehow the system has corrupted itself..
I have also tried to reload the defauly system os via odin but cant get the computer to even recognize the device..
Can anyone help?
MattMcGoogan said:
Hey everyone, i have an issue that i have searched for and can't seem to find anything exactly the same so thought id just jump and ask.
I have a GS3 that has suddenly decided to stop working. It is un-rooted and was stock. I had it on charge over night and woke up to find it like this.
When i try to power the phone on it simply goes to the samsung logo and stops there and if i try to charge it all i get is the initial battery image but it does not move to indicate that it is charging.
I have tried going into the recovery mode to reset data etc but when i do it is covered with red writing saying that it cant find system files and folders, so im thinking somehow the system has corrupted itself..
I have also tried to reload the defauly system os via odin but cant get the computer to even recognize the device..
Can anyone help?
Click to expand...
Click to collapse
Does it look like this >> View attachment 3274198 << if so your emmc could be damage/ corrupt. There are things you could try but all need odin if you can't get odin to recognize your phone then I recommend a service repair.
Thanks for the reply.
That's exactly what it looks like.
By service repair do you mean a service centre?
MattMcGoogan said:
Thanks for the reply.
That's exactly what it looks like.
By service repair do you mean a service centre?
Click to expand...
Click to collapse
Yep i'm afraid so :crying: You could try reinstalling drivers on your pc or try a different pc etc to try and get odin to see your phone but it's a bit of a long shot.
What can a service centre do to fix that though?
Thay can replace emmc chip, but usually they are replacing whole motherboard, reprogram efs and flash newest stock firmware.
I hope your phone is under warranty.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
Damn... Unfortunately it's not any more...
Might have to see how much a board is or just upgrade