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?
Related
i've read almost every single post related on this subject, tried almost everything but no go.
recently, i installed SS-6 to my girlfriend's Vibrant but she didn't like it, so i attempted to revert to my nandroid from the original stock rom.. nandroid gave an MD5 error and did not installed.
at that point, i had already wiped data/cache, prior to nandroid.
i rebooted the phone, and now im stuck on the Vibrant splash.
i have tried to go to recovery mode via hard buttons but no go. i actually tested with another Vibrant and on that one, im able to get into recovery so it is not that i'm missing pressing a button or what not. been trying anxiously to see if im able to go either to download mode or get into cwm and flash cyanogenmod!
tried to use ODIN/ADB in order to boot into cwm to flash another rom, but it doesn't see the phone. ive already installed samsung drivers.
if i connect the charger, the battery indicator doesnt come up. it stays on that lined-circle screen forever, even after taking the USB cable out.
please help!
EDIT: added [Q] and added some more grammar errors.
any help is highly appreciated.
I had this same problem... The only thing that would fix it was this thing I had to buy called a Jig. It was less than $8 (with free shipping) on eBay.
http://www.ebay.com/itm/Fix-Download-Mode-USB-Jig-Samsung-Captivate-Galaxy-S-/140520601309
It delivered in 2 days and my phone is working perfectly now
just ordered one!
thanks!
one more thing, are you able to just install a different ROM through ODIN or ADB without having to do the full wipe? im wanting to save the contents of the internal SD.
thanks again
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.
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 everyone! Kinda my first post here so be gentle
I have a S3 which i rooted almost instantly when i purchased it a year ago. Haven't had any kind of problems with it until now. Over the year i've tried most of the roms out there but now i decided to try the rom called "illusion" (don't know if this problem is related tho!)
It was working fine for a couple of days but suddenly today my phone started bootloopin. I can't even go into CWM or download mode. Sometimes it can stay in CWM och even boot up but after like 2 minutes it restarts again. I've managed to wipe everything once but no change. Was able to install a new rom BARELY, then it restarted again. I've tried remove SD and/or SIM but no change. Ain't working with a usbcable either.
What can I do? Seeing that I can't stay in download mode to use ODIN.
I'd appreciate any help.
a USB recovery jig may be your best shot otherwise its a service center repair
Hello,
I wish I could explain my problem quickly and clearly, but I lost count on the amount of times I wiped, flashed and reset my Tablet so... I just hope someone comes up with a genius idea, because I'm desperate. I've tried everything.
Today I decided I wanted to try and find a better ROM I could install on my Ainol Tablet, and after doing some research I found out there was a 10.1 version of Cyanogenmod that was apparently quite popular.
I followed a tutorial I found on slatedroid.com (Flashed CM 10.1, Gapps and compatibility file) and only after I found out I just flashed a ROM built for the previous model of my tablet. When I reset it it came up as if it had done a Factory reset (same firmware but everything came up in chinese).
Then I went on and managed to find a tutorial for mine; repeated the process.
Right after doing that I re-read the tutorial (I would love to attach the link but I am a new user and am not allowed to...) and realised I was supposed to update my stock firmware to the latest version before flashing CM on it (apparently so they had the same kernel). Luckily, I had made a backup with TWRP so I went back to it and went looking on my PC for said firmware.
When I managed to find it, I realised the wifi on my tablet was gone. Whenever I switch it on, it goes back off after a few seconds. So no internet.
Then I thought I could just get that update file from my PC and copy it through USB. But that wasn't working either, my laptop will not recognise it whenever I plug it. The tablet won't even recognise a USB flashdrive.
Lastly, I realised there was a miniSD card port so I tried getting the file in through that as well. In this case, the tablet displayed a "preparing SD card" message but nothing happened afterwards...
I'm completely stuck. I have tried several times going back to Factory settings through TWRP, or reloading that backup I made, erasing Dalvik/Cache every single time, but the problems are still there. Everything else seems to be working though...
I did some research and it does look like I flashed a ROM with the wrong kernel so all the drivers are gone... (When the tablet is off and charging it displays a battery that used to stand vertically. Now it comes up horizontally...).
If that was the case, would anyone have any clue on anything I could do to fix it? Any files I could get rid of? Or maybe some secret menu on TWRP I haven't taken into account...?
Any ideas would be extremely appreciated. Please help! :'(
Thanks in advance.