Hey guys been searching for hours and hours and I really need someone to tell me whether I should keep trying to just throw my phone in the can
Somehow my GT-i9100 locked up while running and app and when I took the battery out and restarted it was stuck on the Samsung Logo.
I accessed the recovery menu and wiped cache...didn't work and the phone wouldn't be recognized by the computer nor would it charge when plugged to the wall outlet.
I decided to flash a new stock rom *Previously had the latest version of official ICS on my S2" and I proceeded to select the format/wipe to factory option.
It stayed there then it turned of and now it's a complete total brick! wtf.
I've read quite a bit and it has all the symptoms of an eMMC failure.
Is there any way I can save my phone? Will a jig work to force it into download mode?
I'm supposing the pit file fix requires the phone to boot in recovery.
If you can help me out I'll really appreciate it.
Thanks.
If you have no download mode or recovery/the phone won't boot at all, a jig is highly unlikely to do anything - but try one anyway given they only cost a few bucks. You might get lucky.
Likewise a JTAG more than likely won't be possible, if you can have someone who does JTAG's take a look at it on the basis of no payment unless a JTAG can be done, again you may as well try it.
Most likely fix is motherboard replacement - new one by Samsung service centre (most expensive option) or 2nd hand one by you/a local mobile repair shop (less expensive option).
If your phone was rooted at the time you did a wipe & the stock rom you were running was 4.0.4, then yes, it's probably the brickbug. But if your phone wasn't rooted and not running 4.0.4, then it could have been a whole host of things that caused it to brick (I can't help but feeling there's a bunch of info missing here).
MistahBungle said:
If you have no download mode or recovery/the phone won't boot at all, a jig is highly unlikely to do anything - but try one anyway given they only cost a few bucks. You might get lucky.
Likewise a JTAG more than likely won't be possible, if you can have someone who does JTAG's take a look at it on the basis of no payment unless a JTAG can be done, again you may as well try it.
Most likely fix is motherboard replacement - new one by Samsung service centre (most expensive option) or 2nd hand one by you/a local mobile repair shop (less expensive option).
If your phone was rooted at the time you did a wipe & the stock rom you were running was 4.0.4, then yes, it's probably the brickbug. But if your phone wasn't rooted and not running 4.0.4, then it could have been a whole host of things that caused it to brick (I can't help but feeling there's a bunch of info missing here).
Click to expand...
Click to collapse
Phone was not rooted, I forget if the last official ICS upgrade for the phone was 4.0.4 it may well be, but I did the wipe from the stock recovery menu. I honestly didn't expect it to brick this way I wasn't even modding it. But I'll try to get someone who jtags I love this damn phone.
Only one confirmed case of brickbug happening to someone wiping from stock recovery, you are not another case.
Cross your fingers it's JTAG'able, will be relatively cheap (tho manage your expectations, far more unlikely that JTAG is possible than likely) compared to the alternatives.
Related
Hello,
I reciently rooted my samsung galaxy s2. I tried a few roms so i could get used to the system or restoring etc. However i encountered a problem whilst having a peek at an alpha jellybean rom, where i noticed that my CWM app on the phone had vanished? I attempted the restore using the 3 button combo and found that i kept recieveing E: can't mount/ E: can't cache messages whilst on the restore screen. i could find my latest restore on my sd card however it wouldnt restore. I believe the CWM was removed from my phone which caused it to not work. I was then stuck in a bootloop. no matter what i done, boot to a stock rom via odin, try the different CF roms i and try to put CWM back on to the phone? I read a post on here from someone who had the same problem, who was told it looked as though there is a problem with the partitions. i followed a tutorial and used odin to put Latona 20110114.pit on the phone. it said i would get a blank screen once this has done and i needed to remove then place the battery back in the phone then put it into download again. This didnt happen!! I done as instructed and now my phone wont go into recovery mode, download mode or even boot loop. I fear i have completely bricked my phone so i am trying to use oneclick heimdall to sort it however my PC keeps saying i need admin rights to install it which i have.
Can someone please help me out. I am new to this so please go easy on me.
many thanks
If you have no signs of life from the phone, it's probably cactus.
You might as well try a jig (but unlikely to work; still try one tho). Only option is service centre & hope they can't tell/don't care you've been messing with it & fix it under warranty or JTAG repair by a 3rd party repairer, at your cost obviously; will be cheaper than having Samsung/an authorised repairer fix it if they refuse warranty service which they're quite within their rights to do.
edinsam said:
i followed a tutorial and used odin to put Latona 20110114.pit on the phone.
Click to expand...
Click to collapse
First result of searching suggests that's meant for the I9003. Good job.
HA
Hello,
Awe well then. never mind eh, whats done is done! Its totally bricked so i thought i would chance my luck by sending it back to O2 for repair. I was reading the only other way to get the phone running again was to take it to bits and hook it up for some stock flashing. so heres hopping they sort it!
lesson learnt!!!
Hey guys
1) Restarted my phone today using CM10.1 from a very recent nightly (within the past week).
2) On restart, phone froze and got kernel panic.
3) Restarted into CWM and tried to do a restore to an earlier backup I had made.
4) Half-way through the restore, I got ANOTHER kernel panic (never had that before)...
5) Only things I could do with the phone after that was enter download mode...nothing else...couldn't enter recovery mode anymore.
6) Went into download mode and flashed this CWM-Recovery (http://forum.xda-developers.com/showthread.php?t=1118693) and followed the instructions to the letter.
7) Odin 3.07 hung on NAND Write Start
8) Tried using Odin 1.3, and it seemed to flash correctly. It says completed no errors.
Phone will now not even start and is completely unresponsive...pressing any combination of buttons will not start the phone, and the phone is not recognized in Odin anymore...did I just hard brick it? Any other ideas?
Thanks,
Elliott
Service centre. Although if you can have someone who does JTAG's have a look at it to determine whether it can be JTAG'd without you giving them any money up front (I.E you only pay them if it can be JTAG'd), try that first.
Thanks that's what I thought.
Also, try a jig if you can get one. In all likelihood won't work, but stranger things have happened & you have nothing to lose.
Yeah thanks that's what I plan on doing. Any idea what I did wrong, though? I don't want it to happen again if I get it working with a jig.
Impossible to say. Not sure why you flashed that nondescript kernel/recovery in that situation tho given it probably wouldn't have worked even if the flash had been successful (You would probably have ended up with bootloop given recovery was obviously 'broken'). I would have flashed stock with Odin (And that's certainly what I tell people in your situation on here to do because it normally works).
But flashing recovery rather than a stock rom probably didn't break your phone, put it that way, so you didn't do anything 'wrong' per se. Just remember if you get into a similar situation again, go back to stock via Odin & start again (re-root your phone/restore a backup, flash your custom rom/kernel again, etc).
If the jig works (and don't get your hopes up or anything, we're talking a 1 in 10,000 chance, and that's probably being generous), flash stock with Odin (you wont have much choice).
Well...brought it to a JTAG specialist today and he couldn't fix it either...says it's very rare and he's had 5 out of 80 S2's like this happen without being able to fix them...
Bummer. Motherboard replacement in that case. If the phone's under warranty, take it to a service centre & say as little as possible. You might blag it for a warranty fix. No warranty ? You can still have a new motherboard put in by a service centre (more expensive option usually), or you can source a 2nd hand MB from a 'donor' phone (one with a broken screen that's otherwise OK, etc) & either swap it in yourself or pay a local mobile repair shop to do it (usually cheaper option).
@ OP By following what you flashed I noticed the date, we're talking about a 2 years old thread, a lot have changed since.
Not sure that was what bricked your device but I get that panic mode.
The other thing that it comes to mind is nand corruption, which has been quite common these days with people running custom.
I'm with bungle there, the best recovery package is going back to stock and start fresh.
I, on the other hand, wouldn't accept the situation you are on, I would spend a whole week trying to get that phone to boot again, whether a second opinion on a jtag, a new jig, another battery or any other thread on here at xda.
If the device gets hot near the rear camera and it won't even charge nor get warm around that area dismiss what I just said and proceed with the mobo replacement bungle suggested.
And of course, if you did something else to your device and didn't share it please, come clean so others don't freak out by reading this.
Sent from...this is not even my S2
Hey
Nothing else was done to the device...just what I stated exactly.
I caved today and bought a BNIB S3 because I couldn't go without a phone anymore...
Thanks for the help, guys
Elliott
Hello,
I have a Samsung Galaxy S2.
After reading this post http://forum.xda-developers.com/showthread.php?t=2382579 I decided to root my phone.
So I went ahead and started with this step http://forum.xda-developers.com/showthread.php?t=1118693 because I was unsure if I had a kernel with the MMC-SUPERBRICK-BUG.
After I flashed CWM-SuperSU-v0.97.zip using Odin version 1.85 and after the phone rebooted it was stuck at the "triangle screen" for a few seconds then the display went black and I couldn't do anything further.
Up to this point the phone was still accessible in download mode (volume up, power and center button). I believe this is called "download mode". Sorry but I am a complete noob with rooting phones, etc...
So I panicked and took the phone to a repair shop (big mistake). The guy ran it in download mode then tried to flash something onto the phone (I think he used all 4 fields: Bootloader, PDA, Phone and CSC.
Then, in the middle of the operation, Odin froze when writing "setting up connection". Then the phone died ! pressing the 3 famous buttons does nothing and the phone just stays dead.
I had to leave the phone there as the guy said they will try to bypass stuff and try to connect to the CPU directly (sorry again if this sounds noobish). I did update my modem firmware and my computer BIOS in the past... but I guess this one was more complicated.
At the shop, they asked me to check again in 3 days. I am lost here. I don't know what to do anymore.
Is the phone hard bricked ? Should they bear all expenses for what they did ? I would bring back my phone and try something like this http://forum.xda-developers.com/showthread.php?t=1878255 or even a stock flash but I am afraid I cannot do that as the phone isn't even powering up anymore after they tried to repair it at the shop.
Any advice is appreciated.
Nope. You borked it. You tried to flash custom firmware to the phone & obviously failed spectacularly at it. Instead of trying to flash it yourself via download mode (which you could easily have done unless the NAND was borked), you paid them to do it. Sometimes flashes go bad. Sounds like that's what happened in this case.
Reading between the lines they sound like they're going to try & JTAG it (or have someone else do it). And if that fails I presume they'll change motherboards. You could always get the phone back & take it to someone who does JTAGs if that shop doesn't themselves.
MistahBungle said:
Nope. You borked it. You tried to flash custom firmware to the phone & obviously failed spectacularly at it. Instead of trying to flash it yourself via download mode (which you could easily have done unless the NAND was borked), you paid them to do it. Sometimes flashes go bad. Sounds like that's what happened in this case.
Reading between the lines they sound like they're going to try & JTAG it (or have someone else do it). And if that fails I presume they'll change motherboards. You could always get the phone back & take it to someone who does JTAGs if that shop doesn't themselves.
Click to expand...
Click to collapse
Yes I know I failed at it
Or maybe the shop technician is the one who broke it. At least when I had the phone with me I was still able to boot in Odin mode.
Do you think I could have recovered my phone if I had kept it with me and it was booting in download mode ?
I feel so pissed that I took it to that shop. I just wish I hadn't panicked and I had tried, instead, to fix it at home by asking for more help.
Anyway I still haven't paid them anything so far.
We agreed that they will pay for the motherboard because I brought in a working phone (that would power up at least). The owner of the shop was nice enough to agree that he would only charge me fees for installing new software on the phone (even if they have to change the motherboard) because he knows the phone was booting in Odin mode when I came in to the shop and his technician flashed the wrong firmware.
I also wrote down the board serial number so I can be sure they changed it (if they say they did that). So you are telling me the phone can still be fixed ? What does JTAG mean ?
Even if it is fixed I think I will be too scared to try and root it again. Unless I can understand in advance, step by step, what I need to do and what file version(s) I need to use.
Ok, I got my phone today in good working condition.
According to the shop, they had to replace an IC (I don't know what damaged the IC, I am assuming this happened when they tried to electrically jolt the phone) then JTAG it to get it to work again. They charged me a small fee (and they did end up bearing more than 50% of the expenses) because I brought in a phone that was booting in download mode and they take responsibility for what happened after that (flashing wrong files which caused the phone to completely stop booting).
Anyway, long story short, this was my first attempt to root a mobile phone and I learned my lesson.
I am running the following:
Model Number: GT-I9100
Android Version: 4.0.3 (which I will need to upgrade to 4.1.2 of course)
Baseband Version: I9100XXLPW
I know you will say read the sticky posts or the guides but the truth is, that's exactly what I did (you can see the links to the guide I tried to follow in my original post) and I still ended up failing at rooting/installing cyanogen on my phone right after installing Clockwork Mod.
The truth is I am scared to try again and mess up the phone. So this time I would rather be safe than sorry.
What can I do, this time, to safely root it and install a mod like Cyanogen.
Detailed steps are appreciated:
- Do I need to upgrade to 4.1.2 before rooting as 4.0.3 might have the superbrick bug ?
- How to backup the phone.
- Odin version to use, ClockWork Mod version to use, Cyanogen version to use
- How to connect the phone, how to reboot in download mode and all the necessary actions to avoid bricking my phone.
No spoon feeding aloud on XDA.better to read and learn how to do this and that but before you flash anything after learning how to do that learn how to fix it if it doesn't work. :thumbup:
andrewwright said:
No spoon feeding aloud on XDA.better to read and learn how to do this and that but before you flash anything after learning how to do that learn how to fix it if it doesn't work. :thumbup:
Click to expand...
Click to collapse
Fair enough, I figured I'd get that reply from someone and it's normal to be honest.
I decided not to try anything on my phone before I re-read the guides and be sure I know what I am doing.
I will also keep the phone running on stock firmware (after upgrading to JB 4.1.2) to check the battery consumption behavior which, I hope, will be fine since someone tampered with my phone's electronic components at the shop.
Hello,
Before anybody gives me the "Use search" or "Here's this link, it solves everything" : I tried all of that !
I read countless number of posts, I tried many things !
So here is what I have :
- Samsung Galaxy S II (GT-i9100) not booting (Stuck at Logo + recovery mod not working (Download mode is))
- Can flash (Tried many different ROMS
- Stock ROM "Ice Cream Sandwich XWLP7 (4.0.3)"
- Stock recovery mod not working but ClockWorkMod's one works when I put it
What I tried :
- Tried to delete data/reset user factory
- Tried to put different versions of CyanogenMod's ROM
- Tried to put different versions of Stock ROM
- Used a stock pit file to repartition using Heimdall
I'm out of clue, if somebody has an idea what I can try ...
Thank you very much !
Edit : Forgot to say, I have access to adb interface
Given you say you've tried 'everything', what exactly do you expect anyone here to suggest ? Motherboard replacement; new one by Samsung service centre (expensive option), 2nd hand one you source online & either swap yourself or pay a local mobile repair shop to swap (cheaper option).
MistahBungle said:
Given you say you've tried 'everything', what exactly do you expect anyone here to suggest ? Motherboard replacement; new one by Samsung service centre (expensive option), 2nd hand one you source online & either swap yourself or pay a local mobile repair shop to swap (cheaper option).
Click to expand...
Click to collapse
Thanks for the answer, I hope I didn't get too patronizing in my post
So basically my phone is bricked? Can't do anything about it?
Yeah, you did. And that's why I gave you that response.
Right...Now that we have that out of the way, search for Hopper8's 'Odin troubleshooting' thread. I don't think the link to 3 part firmware in the thread is live anymore, but the first thing I'd be doing is trying to hunt down any I9100 3 part stock firmware (not 4.0.4 though) & flashing that. Rationale being as it will wipe your phone, maybe it will remove remnants of what was previously on the phone & which may be causing problems. It's a longshot, but worth trying given the alternatives.
I'd also keep flashing stock firmwares (as many different ones as you can download), and go through all the troubleshooting steps in Hopper's thread. There's always a chance something simple/obvious is being overlooked which is tripping you up, which is easy to do if you've been at it for ages & have had no joy getting it fixed.
If after having done those things the situation hasn't changed, take it to someone who does JTAG's, and if they're prepared to have a look at it on the basis of 'you only pay them if a JTAG is possible' (I know a couple of repairers near me who do this, YMMV though), try that. It's unlikely to work/be possible, but worth trying.
If it isn't JTAG'able, then you either look at motherboard replacement as per my PP, or a new phone, as it's obviously a case of NAND corruption.
The 3 part firmware in hoppers guide is good........I'm hosting it now.....
Try the mediafire link before the dropbox one......
This might be my S2, or it might be my W...but it's definitely CM
Good news Might grab a copy myself in case it ever goes AWOL.
No probs MB.....that's what it's there for....
This might be my S2, or it might be my W...but it's definitely CM
Thank you very much for the 3 part stock firmware but it didn't solve my problem :x
I still have the phone not booting and the recovery mode bootlooping
I'll try option 2, I downloaded a bunch of stock firmwares from Sammobile and will flash my phone over and over
But I'm starting to get the impression that it's not gonna work...
I'll start asking around me if anybody has a not-working SG2 to get his motherboard
Definitely keep trying, but yeah unfortunately, you might want to start looking for that 2nd hand board.
Sorry for a very strange problem.... My wife still uses her old S III (I9300), although it is so outdated and partly broken. Some time ago we flashed CM 12, so that some apps who need a more up-to-date android can be used. But the phone is too slow, there is a crack in the display and sometimes it starts to reboot without any reason. There is not enough memory to install additional apps and without LTE it is no fun.
=> I want to buy a new smartphone for her, but she doesn't want to. She wants to save money and use it, until it is not usable any more.
Of course I could give it a good strike with a hammer or give it a treatment in the microwave oven, but I would prefer only a temporary lack of functions, so that perhaps later I can use it as backup phone for the kids. Therefore I am looking for some trick, app or system setting to SIMULATE, that the phone is broken. When she is happy with her new phone, I intend to "repair" it "by chance"....
Any ideas? How can I simulate, that the phone is broken? Thanks!
You need to hardbrick it.I dont know how to but you can Google it.
ArdaCsknn said:
You need to hardbrick it.I dont know how to but you can Google it.
Click to expand...
Click to collapse
Thanks for the reply! I googled, but i think i want to SOFTbrick it, not to hardbrick it. As I wrote above, I want to "revive" it after some time....
I think the simplest way may be to take the phone, create a backup of all data, put the phone into download mode, start flashing a stock ROM, remove the USB cable when it starts to flash the final file, and reboot the phone. Hopefully, the phone will display the "firmware upgrade encountered an error" message which can be resolved by re-flashing the stock ROM with Odin.
Based on my experience with flashing a stock ROM over a stock ROM, this procedure always leaves the data and apps intact.
cm_new said:
Thanks for the reply! I googled, but i think i want to SOFTbrick it, not to hardbrick it. As I wrote above, I want to "revive" it after some time....
Click to expand...
Click to collapse
Ah,sorry I read it but while replying I forgot somehow.Yeah, then you need to soft brick it .It can be achieved by deleting some system files.So phone can got into bootloop.If your wife doesnt now how to get in to recovery then you should be ok.
Stock rooted phone needed for this, activate factory app. It will give a black window with device information over everything onscreen. Disable factory app to remove it later on.
By flashing the stock firmware in an attempt to make it all better gives the perfect opportunity to pretend the process buggered it.
Put some clear tape on the battery contacts ?