[Q][HELP] Bricked Galaxy S2 In Need Of Advice - Galaxy S II Q&A, Help & Troubleshooting

Ok, so Monday I had my Galaxy set up with Dorimanx kernel 7.22 dual booting 4.1.2 RR (1st ROM) and SalmanROM V4.2.(2nd ROM). I decided to remove the 2nd ROM and went to dual boot options in Recovery mode to remove it, however the phone got stuck while formatting data. I Restarted the phone in Recovery and was able to do a backup but when trying to access the internal SD card I got the error can't mount emmc/.
After reading a bit here: [GUIDE] Fix an unflashable or soft bricked GSII (I9100G/M/P/T VERSION INCLUDED!) I found that my phone was soft bricked and had NAND rw corruption. I followed the steps but was not able to flash the recovery files or the kernel alone, I was only able to succesfully flash the bootloader but once I did that I tried the kernel again and had no luck. I decided to do it again and flashed the bootloader, Odin displayed it was completed and the phone rebooted, only that this time it didn't turn on.
Now my phone is basically dead, it doesn't turn on, it is not recognized by PC/Odin. I ordered a USB Jig which is supposed to arrive next week to see if that can revive it but looking around the web I'm seeing a guy selling an S2 for basically $100 dlls., the phone turns on you can hear the music when booting, rings when you call, only that the screen stays black. Seeing that my S2 might have a damaged motherboard this could help me fix it for less than what Samsung might charge me (I got the phone used so it doesn't have warranty)
My question is, should I wait for the jig to try and revive the phone? What chances do I have ? or should I get the spare one and replace the motherboard?
Thanks for helping!

USB Jig did not work, I will need a JTAG. Can anyone recommend me a good one? I've seen this one http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-jtag-brick-repair/ seems reliable but I want a second opinion.

Related

[Q] Soft-Brick help!

Hello guys, I have (I think) soft bricked my Galaxy S2.
(Details: UK Phone, Carrier was Orange but now I am running 3 on it, official phone model Galaxy I9100T (NFC support iirc) )
Right I am curious bunny hacking away at the phone from the day I bought it, reading pages after pages on different roms and kernel and everything. Finally I settled on CyanogenMod 9 and then went straight to the CM10.1 release. Today Morning I installed the 23/02/2013 CM10.1 realease and then started browsing the XDA forums on whats new. I came across the Siyah 6.0b kernel release and saw it was compatible with cm10.1, eager and foolish I downloaded the apk without doing any further reading or any instruction, overconfident from all the flashing I have been doing for the past year, flashed the kernel via CWM recovery. Now the phone is stuck in what I assume is a boot loop (again I am pretty noobish).
So What have I tried to fix the soft brick?
I tried to go "restore" an img I had taken a week ago of the system with CWM but the phone would no longer boot into recovery.
So I went ahead and got all the recovery package (I9100TDULP9_I9100THUTLP7_HUT) to reflash my phone with Odin 3.07.
This is where I hit a brick wall and now I am truly lost at what to do, my computer doesn't recognise the phone (Download Mode). I keep getting "there is a problem with this device" error and the Device manager shows an unknown device connected. So I installed the Samsung drivers from the samsung website with no luck. Still getting unknown device error. So I googled for a solution and the only solution that came up was reformat my PC since it could be a problem within the OS, so I went forward and used two other PC and still getting the error. Please Help SOS.
tl;dr: Getting Device not recognised error when I connect phone to the computer via USB cable.
Thanks in advance to all the knights to my rescue
DNoob92 said:
I came across the Siyah 6.0b kernel release and saw it was compatible with cm10.1, eager and foolish I downloaded the apk without doing any further reading or any instruction, overconfident from all the flashing I have been doing for the past year, flashed the kernel via CWM recovery. Now the phone is stuck in what I assume is a boot loop (again I am pretty noobish).
So What have I tried to fix the soft brick?
Click to expand...
Click to collapse
Just go to recovery menu (VOLUP+MENU+POWER) and wipe cache and wipe dalvik. That should fix it.
surplus mplieac
crocodilechris said:
Just go to recovery menu (VOLUP+MENU+POWER) and wipe cache and wipe dalvik. That should fix it.
Click to expand...
Click to collapse
I cannot enter Recovery Mode, the screen just goes blank
EDIT: So the only thing that works atm is
1) The battery charge animation (huge green battery in the middle of the screen) when plugged in.
2) Download/Odin mode (which 3 computer refuse to recognise when connected via a USB cable)
EDIT2: The other thing I forgot to mention was, that I have lost the original SII micro USB cable which was black and now I am using the white micro USB cable I received with my Galaxy Note 2.
You could try uninstalling all Samsung-related drivers/software (Ie: Kies), download the Android Naked Driver or the Android ADB Driver (I wish I could recall where I got it from, but it also came with the driver for the Galaxy SII... Sounds like it might be more of a driver issue than it would be a cable issue..
Borrow and S2 cable.
There are a lot of guys having issues with note's cable.
Try a laptop, and install kies on any other pc you try.
Flash siyah v5 instead of flashing v6.
You can relax, if the only thing you did is flash a kernel then there is nothing wrong with your phone.
Try different cables, try Odin 1.85 (that one always worked for me), try different pc's, reinstall drivers, make sure no kies process is running in the background.
First of all thanks for the replies
I couldn't get the drivers working still (after re-installing, installing kies). But while eating lunch I remembered reading about removing battery and pressing the Power button and it doing something I couldn't quite remember. So I thought to myself it wouldn't hurt trying. Did that and the phone Finally booted in recovery mode, I took a breather of relief and than located my previous backup img and restored the phone.
But now a new problem arose, the phone went into SIM lock as soon as it booted and now I guess I have to fix that
Well thanks guys
Quick question guys is SIM network unlock pin basically same unlocking phone form a carrier?
It's asking for a SIM pin or network code?
Get galaxysim unlock by searching xda (free here, paid at play store).
Sent from the little guy

[Q] Black screen after Odin ROM flash

Hi,
I have a cracked screen, so I bought a bricked S2 off gumtree. I'm having a go at getting it to run again. So far all I know is that the previous owner was in the middle of flashing Odin, it said that the flash failed, and then he was unable to boot the phone any more. No powerup, no vol+home+power. No nothing.
The guy seems straight-up, I've no reason to suspect any more damage than reported. I've been in contact with him after the sale, and gave him a guilt-free opportunity to fess up in case he had done anything else.
I made a microUSB jig, and had a go with that, but no luck.
Is there anything else I can try?
--------
Secondary question (if I can't get the new phone up and running) - changing over the screens: would I dismantle both phones and move the screen from the new brick to my phone? or would I move the motherboard from the old/cracked to the new?
are you sure that you made e good JIG
if not, buy one
if it doesn't help and doesn't boot at all....it's dead

[Q] Recovering data from hard-bricked GT-I9100

Hi
I looked around for a while but didn't find a solution to my problem so starting a new thread.
The story:
My wife's phone (2.5 years old, unrooted, not sure what OS version - i think ICS) has stopped working - stuck at the logo. Everything on it was not backed up in a while - contacts, meetings, photos so it had to be attempted to restore.
After reading around i tried to flash a CWM - as suggested in http://forum.xda-developers.com/showthread.php?t=2168448.
I couldn't access the SD card in recovery mode, so i tried the adb sideloader.
Unfortunately it worked - i flashed the kernel from CWM-SuperSU-v0.97.zip (based on this post http://forum.xda-developers.com/galaxy-s2/general/how-to-root-stock-recovery-t1994544) and hard bricked the phone.
Now it doesn't react at all - stuck at a black screen. The only indication that it is still alive is that it warms up when plugged in.
I got my hands on USB JIG but it didn't do any affect - i tried the 2 methods i found (http://forum.xda-developers.com/galaxy-s2/general/ref-usb-jig-faq-frequently-questions-t1402286 and plugging the jig before returning the battery).
Any ideas what to do, except for sending it somewhere to use JTAG ?
Any help would be appreciated, i told her we can save her data
A strange problem!!!
Maybe you were affected by super brickbug?

Galaxy S II full dead after failed repartition(is the main bootloader bugged)

1. The galaxy hangs during normal work(it had custom ROM but was working fine for years), the display showed messed up image and was unresponsive, had to remove the battery(so it was caused by bug or flash storage error).
2. The galaxy could no longer be booted, it was stuck on Samsung Galaxy S II screen and in bootloop(if the flash storage partitions are bugged, I guess it can't boot the SPL and the device is stuck in the main bootloader, is it located in separate ROM chip or in the storage flash chip?).
3. It couldn't boot to recovery, only to download(odin) mode(again I guess it's part of the bootloader on the separate rom chip).
4. Tried to reflash, had to interrupt the operation because it didn't started at all(no progress on NAND write flash).
5. Tried to repartition with .pid file, again no progress with the operation.
6. After that, the device is completely dead, we tried removing the battery, using the charger and other common stuff but it can't be started anyway.
So can the failed repartition/flash operations bug the ROM bootloader so when you press the power button the CPU can no longer execute any instruction(I guess it's hardwired to some init instructions in the bootloader).
Any information about the internal storage chips or any ideas what to do?
Same problem here
Hi I've got the same problem with my phone since i've updated my cm13 on sgs II phone seemed to be working perfectly but around month later woke up and saw that my phone stuck on samsung logo (Same as your did) what i've done was restart to see is it works or recorvery boot up but nothing seemed to be happening. After some time decided to reinstall OS using odin but phone been comp[letely inresponsible to what i've tried to put on it (always been stuck on Nand write start (tried everything)). I tried to repartition it again but after that same as your phone died without any sensible reason. I "temporary" fixed it by pealing off the motherboard specific conductor. It even boot up but afterr that i runned out of charge died again. I can feel that phone is starting to be warm just like it's working but i still have black screen of death, so is there anybody who might actually help with this thread ?
HeadlessHorse said:
Hi I've got the same problem with my phone since i've updated my cm13 on sgs II phone seemed to be working perfectly but around month later woke up and saw that my phone stuck on samsung logo (Same as your did) what i've done was restart to see is it works or recorvery boot up but nothing seemed to be happening. After some time decided to reinstall OS using odin but phone been comp[letely inresponsible to what i've tried to put on it (always been stuck on Nand write start (tried everything)). I tried to repartition it again but after that same as your phone died without any sensible reason. I "temporary" fixed it by pealing off the motherboard specific conductor. It even boot up but afterr that i runned out of charge died again. I can feel that phone is starting to be warm just like it's working but i still have black screen of death, so is there anybody who might actually help with this thread ?
Click to expand...
Click to collapse
same thing happened to my galaxy grand 2
it was charging i was at 80% when i seen it last time i left it for sometime to complete the charge after 15-20min i piked it and i saw it was blank... after that till now it is dead..

Samsung Galaxy Note 1 N7000 need JTAG

Hi everyone,
Hopefully I have put this in the right place.
I have a N7000 sitting doing nothing.
I made it not work at all in trying to fix it.
I know alot more now but believe the device soft bricked and in trying to fix ended up using odin, a stock flash and ticked repartition.
So, the ROM install failed and the partitions got wiped.
The device does not show anything on the screen now at all. Believe it charges, as when I plug it in the device gets warm.
Anyways, is there someone near me (sydney, australia) that has a JTAG device which could be used to bring this device back from the dead?
Thanks

Categories

Resources