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
Hi,
the long story:
bought a used Samsung GT-I8160 (Galaxy Ace II) on Tuesday. It is without simlock and not branded. Originally it had Gingergread installed. I tried my SIM and after some fundling it in the slot it finally worked, I got connection, could recieve and send messages and use the Internet via the browser.
After that I tried to get it rooted via Odin v3.07, I8160XXLL2_CWM_5.0.2.6_ANT.tar.zip and UPDATE-SuperSU-1.65.zip wich worked. So I went on and tried CM 10.1 and 10.2 and Vanilla RootBox Build 4m which all worked extremely well. Just a single glitch: I could not get it to recognize my SIM any more. Even with holding it in place for better connection to the contacts to the chip. Remembering, that it once worked I thougt to flash the stock rom (via sammobile.com) back on and tried I8160XXLL2_I8160ATOMA1_ATO.zip which succeeded in Odin but brought me to my final problem.
The Problem:
Right now while booting or booting to recovery it gets stuck on the first screen, which is a Samsung Startsplash or a black screen or a frozen loading circle. Therefore I can not enter any codes or wipe any data through recovery.
I can start the phone in Odin Mode and flash custom roms, stock roms, kernels and whatever, what gets a succeed and a PASS! in Odin, but changes nothing for re-booting while flashing or booting manually into the other modes.
Searching the Internet I have not found a solution and even the problem seems to be rare. As last resort I tried to flash the GT-I8160_EUR_XX_4G.pit as mentioned in one post while Re-Partition through Odin, what did not change a thing. I guess I did something awefully wrong on the way but would like to get it undone. If there is no solution to do it myself I will have to go to a store next week.
Thanks for reading.
PS: Same Posting goes to the Forum on sammobile.com
I had the same problem and I found a solution here: (3w)taringa.net/comunidades/galaxyace/6526325/Aporte-Desbrickear-Samsung-Galaxy-Ace-S5830-M.html
Hi everyone,
First of all, thanks for all the help/development done here, it is really awesome. I am new to rooting/rom so, I've spent a lot of time reading forum threads and looking at people's issues and it's been really helpful.
Yesterday, I spent all day trying to update my Bell Mobility Samsung Galaxy S Vibrant GT-I9000M from Froyo 2.2 to 4.2+
I sucessfully rooted the device, installed SpeedMod kernel(with Odin 3.04) and got CWM Recovery working when I restart the cellphone.
Afterward, I tried to update with different ROM(CyanFox, CM11, Mackay OmniROM...) but always got Status 7 error at CWM. So I figured I'd try to upate to a recent Kernel and installed GearKernel_JBPlus_Vibrant_1.0.3v.tar trought Odin. The phone got in an installation loop. Here is a poor webcam photo of the error(sry couldn't get better) : http://i.imgur.com/L3b0RmF.png. It says something like Estimating(?) volume for path [grep], Can't mount grep, Installation Aborted. Restart, splash screen, installation aborted, loop.
I had this loop at other occasions trying to update Kernel. The solution had been to put the cellphone in Download mode and reinstall Speedmod Kernel with Odin. This is what I did again.
It allowed me to get in Recovery mode but I couldn't go passed it. Attempt at restoring backup didn't worked. So I decided I'd go back to everything stock and followed this thread http://forum.xda-developers.com/showthread.php?t=1047087 and used Odin with the PIT and TAR files.
This got me in my worst position so far. If the cellphone is plugged, it loops between dark screen and the little "loading thingy" before the battery, but nothing more, no battery charge. If I try to open it without the plug, it display the GALAXY S GT-I9000 splash screen(which is weird cause I'm using I9000m) for a couple second then goes dark.. Then splash screen.. then dark... pretty quickly.
I can go in Download mode but I haven't succeeded to get in Recovery mode. I have adb on my computer but I haven't been able to call anything from it at the point I am.
I have found different threads showing different solution for various problems but I feel like I tried enough and I'd like to avoid bricking my cellphone so I decided I'd make my own post detailing the steps I took.
What should be my next step to get out of this loop? It seems like I only have Odin/Download mode to help me.
Thanks again.
If you have the gt-i9000m that is not the vibrant. The vibrant is the sgh-t959. Thats probably your problem
Sent from my Nexus 4 using xda app-developers app
Hi guys,
Short and fast:
Have: SAMSUNG Galaxy i9300 splash screen (black and white)
Don't have: Booting past this
Phone can: Enter recovery and download mode (ODIN)
I can't: Figure out what to do next
First poster here but I've been helped so many times just reading the threads on here.
I'm currently having a bit of trouble. Last night my phone ran out of battery while filming - no big but as the battery died the screen started to get these distortions and lines across it which have disappeared since so no worries there. When I try and turn it back on though it will get to the first splash screen where it says "SAMSUNG Galaxy SIII I9300" and it will just sit there for hours. I have tried reverting to a rom through cwm I previously found stable but still the same problem. I can enter download mode as well but not sure what to do from here.
I've been trying for a few hours to find what exactly the problem is but to no avail. Anyone have a suggestion?
I am on Virgin (Optus) in Australia
Currently downloading OPS-I9300XXUGNB4......... .zip which I believe is stock firmware, is this in the right direction?
I have downloaded/installed ADB and FastBoot as well
Follow the guide in general forum sticky thread to flash a stock firmware with Odin, then factory reset in recovery.
It sounds like you've corrupted one or more emmc partitions, if it's the efs then you'll need to restore a backup to fix.
Sent from my GT-I9300 using Tapatalk
It's looking like my GS2 is giving up the fight
I've been running Neatrom 6.4 for ages and everything has been fine until the other day.
My phone randomly turned off and then kept bootlooping (stuck on samsung screen). I couldn't access recovery, only download mode.
I've tried flashing several kernels and roms on odin without any success. Now the phone tells me there is a firmware problem and when I plug it in it says 'charging.jpg' draw failed....not really sure how to fix this.
I saw the advice in this thread but it doesn't seem that relevant since I have an underlying issue beyond the jpg being missing.
Any ideas on what to do?