Good morning guys
I've been having issues with my Galaxy S2 for about a month now so I'll try my best to explain what's happened.
I was playing on my PS4 and I had left my Galaxy S2 (non root) on charge. When I returned to check the charge levels, it had booted and was stuck on the black galaxy S2 logo screen. I was able to put it in download mode but not recovery and the phone would also charge. I removed the battery, tried to reboot but it just wouldn't boot past that screen. Upon reading on these forums about the potential issue, it sounded like the phone was softbricked so I tried to re-flash the stock rom that I downloaded from samware but Odin wasn't having any of it.
I tried multiple different PCs, Odin versions, USB cables and so on but it just kept failing. I eventually got fed up with trying to recover it and I just left it in storage. Today however, the wife has said she wants all the pictures off it so she can transfer them to her laptop so I got the Galaxy S2 out again and now it's dead. Won't turn on, won't charge, won't do anything. I've got a new battery but that won't charge either but I'm headed around a friend's later to charge it and see if that solves anything.
Any help or suggestions would be greatly appreciated :good:
MrChi 205 said:
Good morning guys
I've been having issues with my Galaxy S2 for about a month now so I'll try my best to explain what's happened.
I was playing on my PS4 and I had left my Galaxy S2 (non root) on charge. When I returned to check the charge levels, it had booted and was stuck on the black galaxy S2 logo screen. I was able to put it in download mode but not recovery and the phone would also charge. I removed the battery, tried to reboot but it just wouldn't boot past that screen. Upon reading on these forums about the potential issue, it sounded like the phone was softbricked so I tried to re-flash the stock rom that I downloaded from samware but Odin wasn't having any of it.
I tried multiple different PCs, Odin versions, USB cables and so on but it just kept failing. I eventually got fed up with trying to recover it and I just left it in storage. Today however, the wife has said she wants all the pictures off it so she can transfer them to her laptop so I got the Galaxy S2 out again and now it's dead. Won't turn on, won't charge, won't do anything. I've got a new battery but that won't charge either but I'm headed around a friend's later to charge it and see if that solves anything.
Any help or suggestions would be greatly appreciated :good:
Click to expand...
Click to collapse
Hi
Looks like your usb/charging Connector is broken.
Can be replaced if you are ready to spend money On an old device.
If your friend has a s2 try to connect it with your cable to your PC. If it works then it should be your usb Connector (having already a new battery)
But If you are able to enter (with loaded new battery) the recovery you can install philz cwm6 stock recovery with root and then flash a custom rom.
All files are zip files which you can copy on a micro SD card and can be installed from there without a PC.
So you have a working rom even with a broken Connector
Sent from my ME173X using XDA-Developers mobile app
---------- Post added at 04:47 PM ---------- Previous post was at 04:31 PM ----------
Just want to add:
In case you manage to install philz Kernel try first to reboot stock-rom. If it does'nt work, i would install custom rom.
Sent from my ME173X using XDA-Developers mobile app
Hi, it happened to me 2-3 yrs ago. Try this:
_phone off (check)
_take the battery out
_plug the phone in
_ wait a few seconds then put the battery back in
_ immediately, press and hold the power button.
Sometimes the USB charge chip get stuck and this somewhat "resets" it.
Also worth checking, remove the battery first, then with a small brush or a nail check for dust layer inside the USB plug.. it won't solve your problem, but might cause a bad connection (even if the connector click in).
Related
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
I have a Samsung Galaxy S2 SCH-R760.
What happened: Tried to update phone from standard IceCreamSandwich to Jelly Bean via Samsung provided SimpleUpgradeTool. Very new to flashing phones, forgot to check model number, first attempt failed. Eventually got the right one (difficult to do with my model apparently), and the mobile network wouldn't work. Was told to reset APN, could not find it anywhere in the system.
Got fed up and decided to revert back to original OS, which failed. Waited overnight (it was late) with the phone off. Found the right file (just going to go back to Jelly Bean), however whenever I attempted to get into recovery mode it told me there was not enough power and to charge the phone. Phone was plugged in, this happened a couple of times. Now after the phone has been plugged in for well over 3 hours I cannot get the phone to power on or anything, it absolutely will not respond. Attempted to use Kies, will not recognize my phone model and is waiting for the phone to be connected anyway. When plugged in (trying/using various different cords) I have a little faint blue light flashing in the top left corner of the phone (not the phone screen).
The phone has been in excellent condition up until this point, and I have little reason to believe that my battery just suddenly went 100% bad after showing no signs of decay in recent weeks. Any suggestions?
How did you try to revert? But kind of sounds like it might be hard bricked. If you can't get get into Download mode by Vol Down and Power and it isn't charging not even sure if this would work: http://forum.xda-developers.com/galaxy-s2/general/ref-usb-jig-faq-frequently-questions-t1402286
But unless you try another battery or something like that jig, and it does not power up to any screen, then your only hope would be a JTAG service. I recommend these guys:
http://mobiletechvideos.mybigcommerce.com/
es0tericcha0s said:
How did you try to revert?
Click to expand...
Click to collapse
Just tried to use the samsung quicktool program and just install the old OS back onto the phone.
Aquaserge said:
Just tried to use the samsung quicktool program and just install the old OS back onto the phone.
Click to expand...
Click to collapse
I'm not familiar with the QuickTool. Why not use Odin? It's the preferred method for most popular Samsung phones.
So I rooted my s4 using towelroot and stupidly tried to install a custom recovery. First CWM then TWRP (not sure if this has anything to do with it, likely not?). Now it has no power, and wont charge...
Events leading up to the dead s4:
I "rebooted to recovery" and it brought me to the DOWNLOADING! screen instead of a recovery manager, I held down power and then it shut off and it turned back on again and brought me to another screen asking me to continue or boot normally.
I booted normally.
Then I deleted a few of the annoying apps that were preinstalled, nothing that was listed as essential to the Kernel/OS using Root App Delete. Finally I went to work with the battery dying, and it died on the way.
I tried to charge it the following morning and it would not charge. No LED light, no vibrate that usually happens. I left it alone with the battery out for 2 days, switching back to my s3. Tried again, still nothing.
Wont charge, computer wont recognize. Tried 3 different cables, a samsung charger and my asus tablet charger. Apparently it is a brick.
Thought it might be the USB port, and from a previous screen swap I performed, I still had the old USB assembly, so I swapped them, and it still will not respond. I even tried the older screen, nothing.
Anyone have the slightest clue what happened? I bought another battery to try, but doubt it will resolve the problem.
daveyp225 said:
So I rooted my s4 using towelroot and stupidly tried to install a custom recovery. First CWM then TWRP (not sure if this has anything to do with it, likely not?). Now it has no power, and wont charge...
Events leading up to the dead s4:
I "rebooted to recovery" and it brought me to the DOWNLOADING! screen instead of a recovery manager, I held down power and then it shut off and it turned back on again and brought me to another screen asking me to continue or boot normally.
I booted normally.
Then I deleted a few of the annoying apps that were preinstalled, nothing that was listed as essential to the Kernel/OS using Root App Delete. Finally I went to work with the battery dying, and it died on the way.
I tried to charge it the following morning and it would not charge. No LED light, no vibrate that usually happens. I left it alone with the battery out for 2 days, switching back to my s3. Tried again, still nothing.
Wont charge, computer wont recognize. Tried 3 different cables, a samsung charger and my asus tablet charger. Apparently it is a brick.
Thought it might be the USB port, and from a previous screen swap I performed, I still had the old USB assembly, so I swapped them, and it still will not respond. I even tried the older screen, nothing.
Anyone have the slightest clue what happened? I bought another battery to try, but doubt it will resolve the problem.
Click to expand...
Click to collapse
simple research you could have avoided all this....unless you have a MDK bootloader you CAN NOT install any custom recovery like TWRP of CWM without messing your phone up. Safestrap is your ONLY option. The link below is where you should have started your research. Most likely now you will have to try odin a clean image tar of your phone's firmware base
http://forum.xda-developers.com/showthread.php?t=2606501
decaturbob said:
simple research you could have avoided all this....unless you have a MDK bootloader you CAN NOT install any custom recovery like TWRP of CWM without messing your phone up. Safestrap is your ONLY option. The link below is where you should have started your research. Most likely now you will have to try odin a clean image tar of your phone's firmware base
http://forum.xda-developers.com/showthread.php?t=2606501
Click to expand...
Click to collapse
thank you. I know i messed up, have rooted/installed cfw on like 10 android phones but they always packaged root and unlocked the bootloader at once, which I never noticed.
Also, how can I connect the phone to odin if it wont connect to a PC? or charge for that matter
daveyp225 said:
thank you. I know i messed up, have rooted/installed cfw on like 10 android phones but they always packaged root and unlocked the bootloader at once, which I never noticed.
Also, how can I connect the phone to odin if it wont connect to a PC? or charge for that matter
Click to expand...
Click to collapse
I can't help you that
daveyp225 said:
thank you. I know i messed up, have rooted/installed cfw on like 10 android phones but they always packaged root and unlocked the bootloader at once, which I never noticed.
Also, how can I connect the phone to odin if it wont connect to a PC? or charge for that matter
Click to expand...
Click to collapse
Re install your drivers then try again
Sent from my SCH-I545 using XDA Free mobile app
Sounds like a total brick to me. There are jtag services. I bought the equipment myself to jtag for a hard brick but my warranty company decided the replace my phone after all so I didn't have to use the equipment. Mine did the same exact thing. Wouldn't even get warm when plugged into the charger.
Hi Everybody, excuse me for my english
I am new in this forum, I go to talking about my experience in my case ,I have changed the touch screen it was broken, it this was 2 months ago and it worked very well, however one week ago this frozen screen , touch screen don't response , turn off and remove battery. then turn on and just begin and stop in animacion Galaxy Trend s7560m ,i tried some times and again the same , then i did the next pass
1. - i tried to do hard reset/ factory mode -- I can not get into that mode
2 - Downloading mode -- yes then I installed proper drivers for samsung, installed Odin3 and Firmware for galaxy trend s7560m.
I made the flashing with successful, when end my cell was working well.
This just worked for 5 hours about then the same frozen screen and stuck in boot, I went back to the same old process, and nothing Odin finished with PASS! however cell stuck in boot.
When connect the cell to AC current with the charger this don't charge just turn on and stuck in boot loop one and other , remove the battery and carge a multicharger until fully charged then try remove the battery and multicharger carge a charge until then try again fully loaded firmware and run , after a few days the same again .
I found a way to make it work only when this happens is to put the phone in downloading mode and connect the USB to the computer until a sound is heard connected dipositive wait a minute disconnect the power cell and ready works again without loading firmware , this only works with a limited battery that is only works if you have approximately 70% battery.
I not find way to do to work properly
Does anyone have a similar case? or any ideas will be taken into account
Thank you for taking the time to read this.
Hey Guys,
My Samsung Galaxy S3 is killing me, the problem is the following:
It was working fine one day and the next day, it started giving the error message "Unfortunately, the process com.android.phone has stopped." along with network and wifi going off and on every 5 to 10 seconds, overheating from the sim card and sd card side, and rapid draining of the battery, i have tried all the solutions i found but nothing worked for my case, so i had to go to the ultimate fix which is to recover factory settings, so i have restarted the phone, done the factory settings, and that solved the problem, the phone started fine, i started installing my apps again, and everything seemed ok, after the battery went dead, i replaced it with a charged one (i have a major problem with my charging port, its damaged beyond repair, so i have 2 batteries, using an external charger) then i started the phone, and the new problem happened, the phone is stuck on samsung logo, naturally i went for the factory reset again, but this time (to my great luck) that did not solve it, and i can see the error " E: failed to mount /efs (Invalid argument)" two times.
i have tried copying the md5 file to the sd card and done "apply update from external storage" but it did'nt help.
could anyone help me solve this problem by using the sd card? because i can not us usb cable to use Odin, or all that stuff
by the way, my phone is stock not rooted, jelly beans 4.3
In a twist of events, i actually managed to repair the charging port at a repair shop, the phone is charging normally and detected by windows, now, i have noticed that both samsung kies and smart switch give the message that my device is unsupported, no idea how, so i started using Odin, i have managed to flash twrp recovery to the phone successfully, tried to root the phone while in this state but no luck, got a stock rom from sammobile and i was successful at flashing it to the phone using Odin, but that did not solve the problem, i still think that the problem is the efs partition, its corrupted somehow, i don't know why, my phone was not rooted and never flashed it with a custom rom to expect such corruption, anyways, now my S3 is not stuck on samsung logo, its now caught in a bootloop, ulternating between samsung logo and the android green gut opened logo, i flashed recovery again with CWM, and now the bootloop is not happening, instead when i power the phone it goes to CWM recovery after samsung logo and stays in recovery, i believe the problem got weirder and weirder, any suggestions? how to fix the efs mounting issue without changing or deleting my IMEI, since my phone is not rooted, i did not have any backup of efs.
HI, I have had a variety of problems with my i9000 and so has pretty much everyone
Instead of going down the Odin root and getting mixed up in PIT files, there's a solution which with enough effort can fix almost everything. Use Samsung Kies. The program will restore your phone, no matter what state its in to its factory settings. Mine was so bad it didn't actually have an OS at one point. Once all the drivers are installed and u have connected ur phone, go to tools>emergency firmware recovery and type in the model and serial number. So GT-i9000 and ur serial number. Then put the phone into download mode and then click next and it will fix in about ten minutes. Be patient getting into D/L mode, because it is quite troublesome.
Hope I helped.
---------- Post added at 02:46 PM ---------- Previous post was at 02:41 PM ----------
Sorry,after reading, u said u cant use a usb cable. But then how did you copy the file to your sd card. If u cant use a cable at all, like not even at a friends house or something then im sorry. But if you can try what i posted above.
Mihir571 said:
HI, I have had a variety of problems with my i9000 and so has pretty much everyone
Instead of going down the Odin root and getting mixed up in PIT files, there's a solution which with enough effort can fix almost everything. Use Samsung Kies. The program will restore your phone, no matter what state its in to its factory settings. Mine was so bad it didn't actually have an OS at one point. Once all the drivers are installed and u have connected ur phone, go to tools>emergency firmware recovery and type in the model and serial number. So GT-i9000 and ur serial number. Then put the phone into download mode and then click next and it will fix in about ten minutes. Be patient getting into D/L mode, because it is quite troublesome.
Hope I helped.
---------- Post added at 02:46 PM ---------- Previous post was at 02:41 PM ----------
Sorry,after reading, u said u cant use a usb cable. But then how did you copy the file to your sd card. If u cant use a cable at all, like not even at a friends house or something then im sorry. But if you can try what i posted above.
Click to expand...
Click to collapse
Removing the sd card and using a card reader connected to your pc to put the files over the card is not an issue, but the phone's charging port which doubles as data connection is damaged and can't by changed because its motherboard point of connection is damaged by a stupid technician, so any solution to my problem (other than changing the whole board) would have to include the sd card to get thedata to the phone
herculese911 said:
Removing the sd card and using a card reader connected to your pc to put the files over the card is not an issue, but the phone's charging port which doubles as data connection is damaged and can't by changed because its motherboard point of connection is damaged by a stupid technician, so any solution to my problem (other than changing the whole board) would have to include the sd card to get thedata to the phone
Click to expand...
Click to collapse
If the phone is in such condition I would try and get it professionally repaired or get a new one. Butttt, because that's not how we do thing at XDA , i would suggest seeing if you could find a flashable file that consists of either stock firmware or a ROM u know is stable. For the S3 GT-i9300 i would suggest any of the ones in development on XDA, most worked for me, or a touchwiz based one thats stable. I think that might help. Also, try rooting it, if possible, and check the efs folder (i think it requires root to access) Check if files look corrupted or are missing compared to what they should be (google this)
Also, just checked, this might be what ur looking for:
http://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056
Mihir571 said:
If the phone is in such condition I would try and get it professionally repaired or get a new one. Butttt, because that's not how we do thing at XDA , i would suggest seeing if you could find a flashable file that consists of either stock firmware or a ROM u know is stable. For the S3 GT-i9300 i would suggest any of the ones in development on XDA, most worked for me, or a touchwiz based one thats stable. I think that might help. Also, try rooting it, if possible, and check the efs folder (i think it requires root to access) Check if files look corrupted or are missing compared to what they should be (google this)
Also, just checked, this might be what ur looking for:
http://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056
Click to expand...
Click to collapse
Thank you for your reply, but you keep forgetting the dark and gloomy fact that the phone won't start cannot be connected to pc, so rooting the phone is not possible, and correct me if I'm wrong, flashing the rom needs pc as well, I'm guessing if i can restore the efs folder with a stock one that should solve it, but is it possible to navigate to that folder in recovery mode?