Related
I have a problem with Galaxy s2. Basically it started to drain my battery like hell.
It gets empty in about 10 hours.
Now when I want to flash the phone once again in order to get everything back as it was when I bought it I cannot. This is due to MTP connection activating itself as soon as I turn on the phone. And I cannot enable usb debugging due to that as it says that I have to remove the USB cable.
In addition my phone charges itself really fast about 2 hours. And when I try to power it on without charger plugged in it gives me charging image and yellow triangle with ! in it and thermometer aside flickering. Does anyone have any ideas how to fix my phone?
Have you tried using CWM to wipe all data + clear all cache, then do a fresh re-install?
Yes I tried it now. It still says my USB is connected when its not. And now it doesnt unlock my sim card.
Factory reset that dont work return phone to a service centre ..
jje
Well thats the case I have voided warranty already. Wondering if there are any chances I could put old rom back before returning it?
Make a DIY USB JIG then flash it back to stock rom and have it checked.
EarlZ said:
Make a DIY USB JIG then flash it back to stock rom and have it checked.
Click to expand...
Click to collapse
Not sure what do you mean by DIY USB JIG but I cannot flash it because I cannot switch USB debugging on... Thats the case it shows me that USB is always connected when it isnt and when USB is connected it doesnt let to switch on USB debugging.
Route is source stock rom and Odin load stock rom into Odin enter download mode on phone and then connect cable and flash rom .
No download mode
http://forum.xda-developers.com/showthread.php?t=819551
jje
JJEgan said:
Route is source stock rom and Odin load stock rom into Odin enter download mode on phone and then connect cable and flash rom .
No download mode
http://forum.xda-developers.com/showthread.php?t=819551
jje
Click to expand...
Click to collapse
Thank you all who have replied. I have now managed to get over the USB issue somehow but still something is wrong either with battery sensor or battery. When I power off my phone it switches on automatically and shows the thermometer and battery charge icon. Anyone else have had this problem? It also charges up to 95% and it bursts to 100% very quickly.
EDIT: Now I tried my friends battery and I did not get the flickering temp error and my friend didnt get it with my battery as well. So something now I'm totally out of ideas.
Service centre .
jje
I am having the same issues here, wonder if the topic creator resolved this in any way? I am thinking of getting a new battery?
Just FYI wear a condom or something on your galaxy S II. As it turns out from service my phone supposedly has liquid damage which does not the warranty apply. I have to pay 240 euros in order to get it fixed :S
Hey Guys.
I had an S1 7 months prior to buying the S2, and have upgraded/fresh installed ROMS many many times over the past year. Once the S1 bricked during an upgrade and I was able to get it into Download Mode without using a micro-USB jig from instructions on this website. If my memory serves me correctly, it was a procedure something fairly simple like hold the Home, Volume Up and Power buttons continuously until the phone goes into forced Download Mode.
However, this procedure doesn't work with the S2 or I'm remembering it incorrectly, and I'm unable to find that instruction webpage again. Now my S2 is almost bricked showing a message I've not seen before, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
So far, I cannot get past this message and Kies 2.0.2.11071_128 doesn't recognize the device nor that emergency recovery is needed.
Unfortunately Samsung programmers haven't been quite smart enough or forward thinking enough to make Kies work from behind a proxy which requires authentication (I live and work on a university campus and the only way to the internet is via proxy and authentication) and it has never shown in the past 9 months of usage that it needs to update itself nor finds any official ROM releases. Therefore I've been forced to use Odin and ROMs from here or samfirmware.com for my updates. Until now, there has never been any major problems that I couldn't get around.
Do any of you have instructions on how I can get my S2 into download mode so as to get Odin to recognize the device? It is not possible for me to make my own JIG here in Thailand as there is nowhere for me to go purchase electronic equipment and parts such as soldering irons and resistors. I am a computer engineer and could easily build such if it were possible to get needed parts.
Thanks hugely in advance for any help offered.
Just order a high from ebay
Sent from my GT-I9100 using XDA Premium App
cmcole101 said:
Hey Guys.
I had an S1 7 months prior to buying the S2, and have upgraded/fresh installed ROMS many many times over the past year. Once the S1 bricked during an upgrade and I was able to get it into Download Mode without using a micro-USB jig from instructions on this website. If my memory serves me correctly, it was a procedure something fairly simple like hold the Home, Volume Up and Power buttons continuously until the phone goes into forced Download Mode.
However, this procedure doesn't work with the S2 or I'm remembering it incorrectly, and I'm unable to find that instruction webpage again. Now my S2 is almost bricked showing a message I've not seen before, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
So far, I cannot get past this message and Kies 2.0.2.11071_128 doesn't recognize the device nor that emergency recovery is needed.
Unfortunately Samsung programmers haven't been quite smart enough or forward thinking enough to make Kies work from behind a proxy which requires authentication (I live and work on a university campus and the only way to the internet is via proxy and authentication) and it has never shown in the past 9 months of usage that it needs to update itself nor finds any official ROM releases. Therefore I've been forced to use Odin and ROMs from here or samfirmware.com for my updates. Until now, there has never been any major problems that I couldn't get around.
Do any of you have instructions on how I can get my S2 into download mode so as to get Odin to recognize the device? It is not possible for me to make my own JIG here in Thailand as there is nowhere for me to go purchase electronic equipment and parts such as soldering irons and resistors. I am a computer engineer and could easily build such if it were possible to get needed parts.
Thanks hugely in advance for any help offered.
Click to expand...
Click to collapse
Well kiss my rosy red butt-cheeks! Speaking from personal experience as tech support, I know empirically to replicate something 52 times prior to asking for assistance. This instance shouldn't have been an exception!
Directly after posting this request for assistance, I decided to try Odin once again and DANGED if this time it found my device even with the "Firmware encountered" error showing. Odin stopped around 90% and forced me to reset my S2, but this time it went right into Download mode with nary a fuss. Now Odin just successfully installed KG6.
So if there is anything to be learned from this experience, either by other users with similar issues or myself, it is "if at 1st you don't succeed, try again and again and again and again."
UPDATE 2 : 29th Nov
ok lemme rephraze what i need
i am having a drain bug in my setup, be it stock or custom rom .
using latest safestrap and running stock ICS , black widow and eclipse Roms
all showing similar levels of battery drain.
cant use fastboot or anything that requires a PC to flash stuff as my phone wont connect to any PC.
just tell me how to fix this battery drain issue without using a PC
------------------------------------------------------------------------------------------
UPDATE as on Nov 29th
after reading a lot , i came to know that the guy from whom i bought this phone flashed a kexec XT910 CM10 build on it , the build couldnt work as the phone process was force closing ,
but i suppose despite my reactivating the stock the kexec build kernel is still functional on the phone thereby leading to battery loss in sleep as well as occasional freeze,
So i guess in this light someone can shed some light on the issue of how can i replace this evil cm10 kexec kernel with the stock ics Xt912 kernel WITHOUT THE USE OF A PC as i suspect flashing of that cm10 build isnt letting me connect to any PC in any mode with any cable.
CHK the attached pics for the condition the phone was in when i bought.
=====================================================
ORIGINAL QUERY
got a XT912 Of ebay.
phone has safestrap , stock partition , and 4 others .
when i got it , it was on cm9 i guess or 10 with phone process force closing
iall i did was boot to stock Xt912 thru safestrap ( stock ics 4.0.4 was already there )
But the issue has been i have not been able to connect this phone to any PC with any cabae at all, wanted to clean it and flash the 4.0.4 XML via rsd lite , the phone charges alright via usb cable, but as soon as you plug it in the prompt says unrecognised device, changes all the options in storage settings as well.
but i could live without that,
the other and most annoying major issue is that the Kernel in stock has gone totally evil, its sucking up all the juice Gsam battery info shows 85% of battery was drained by it sitting idle in last 6 hrs
one more interesting thing is that the phone itself becomes frozen , the soft touch lights keep glowing and the phone screen goes black and unresponsive to everyrthing, i have hardset reset by power and vol down to reboot. wehat is this happeneing
its happening on stock ROM as well as eclipse rom that i just installed on another partition thru safestrap.
can anyone tell me
1.. how to get over usb connection unrecognized thingy ( tried every possible thing i could fine )
2.. how can i flash the stock ICS with stock kernel without connecting to usb, are there zip files available for that , dont wanna mess up whatever i already am having.
any help would be appreciated
lord dredd said:
got a XT912 Of ebay.
phone has safestrap , stock partition , and 4 others .
when i got it , it was on cm9 i guess or 10 with phone process force closing
iall i did was boot to stock Xt912 thru safestrap ( stock ics 4.0.4 was already there )
But the issue has been i have not been able to connect this phone to any PC with any cabae at all, wanted to clean it and flash the 4.0.4 XML via rsd lite , the phone charges alright via usb cable, but as soon as you plug it in the prompt says unrecognised device, changes all the options in storage settings as well.
but i could live without that,
the other and most annoying major issue is that the Kernel in stock has gone totally evil, its sucking up all the juice Gsam battery info shows 85% of battery was drained by it sitting idle in last 6 hrs
can anyone tell me
1.. how to get over usb connection unrecognized thingy ( tried every possible thing i could fine )
2.. how can i flash the stock ICS with stock kernel without connecting to usb, are there zip files available for that , dont wanna mess up whatever i already am having.
any help would be appreciated
Click to expand...
Click to collapse
are your drivers installed?
yes installed and reinstalled latest drivers many times.
currently installed MotorolaDeviceManager_2.3.4, i guess they r latest.
updated the safestrap
installed another ROM in eclipse 1.5 on the partition 2
but still battery drain is similar and got 2 phone freezes as well.
and still not able to connect the phone to PC in any possible way .
looks like some glitch in the kernel as Gsam battery monitor shopws kernel is using up a lot of battery.
nones having any idea ?
i am kinna stuck guyz
chip in with whatever you think is doable
regards
lord dredd said:
nones having any idea ?
i am kinna stuck guyz
chip in with whatever you think is doable
regards
Click to expand...
Click to collapse
try different cable or computer. then, if eclipse or stock "sees" your device, flash stock firmware using RSD lite
or, flash another kernel
also, there is another method flashing stock firmware, but I see now that the site is not working anymore...
http://www.eternityproject.eu/topic/53-eternityproject-fla****-rsd-alternative-for-flashing/
try yourself later
good luck
is it not possible to flash another kernel , i meran the stock kernel using cwm or safestrap ?
i guess till this phone accepts any cord or PC , thats the best bet
lord dredd said:
is it not possible to flash another kernel , i meran the stock kernel using cwm or safestrap ?
i guess till this phone accepts any cord or PC , thats the best bet
Click to expand...
Click to collapse
Unfortunately there is NO way to flash stock firmware, nor kernel without using an usb cable...
You can only flash radio with custom recovery (I've tried bootmenu manager)
For a better info about flashing kernel, see posts 525 and 526 form here:
http://forum.xda-developers.com/showthread.php?t=1964792&page=53
Have you tried another computer and cable?
Also I suppose your pc doesn't see the phone when is in fastboot mode...
Yes nothing in USB or fast boot mode.
Although phone does connect in sbf made but that again needs it to be in fast bout to flash the ROM.
Gonna give those links a try.
Is there any jig or something somewhere.
edit : well again this also requires connecting to PC , which isnt possible
is there no way to flash stock or just kernel only via recovery
Sent from the DAD of all S2s - The Epic Touch.
UPDATE as on Nov 29th
after reading a lot , i came to know that the guy from whom i bought this phone flashed a kexec XT910 CM10 build on it , the build couldnt work as the phone process was force closing ,
but i suppose despite my reactivating the stock the kexec build kernel is still functional on the phone thereby leading to battery loss in sleep as well as occasional freeze,
Can anyone now shed some light on the issue of how can i replace this evil cm10 kexec kernel ( if my assumption is correct ) with the stock ics Xt912 kernel WITHOUT THE USE OF A PC as i suspect flashing of that cm10 build isnt letting me connect to any PC in any mode with any cable.
Or may be just link me to any custom stock based ROM which has the stock kernel in it.
i can transfer the rom zip to my sd card thru other means and flash thru the safestrap recovery
lord dredd said:
UPDATE as on Nov 29th
after reading a lot , i came to know that the guy from whom i bought this phone flashed a kexec XT910 CM10 build on it , the build couldnt work as the phone process was force closing ,
but i suppose despite my reactivating the stock the kexec build kernel is still functional on the phone thereby leading to battery loss in sleep as well as occasional freeze,
Can anyone now shed some light on the issue of how can i replace this evil cm10 kexec kernel ( if my assumption is correct ) with the stock ics Xt912 kernel WITHOUT THE USE OF A PC as i suspect flashing of that cm10 build isnt letting me connect to any PC in any mode with any cable.
Or may be just link me to any custom stock based ROM which has the stock kernel in it.
i can transfer the rom zip to my sd card thru other means and flash thru the safestrap recovery
Click to expand...
Click to collapse
The kexec Kernel doesnot delete your stock kernel , it just bypasses it . Your best bet is to ask the CM10 dev on how to remove/uninstall the ROM & kernel. I guess HSD-Pilot/Hashcode will be able to help you out.
lord dredd said:
UPDATE as on Nov 29th
after reading a lot , i came to know that the guy from whom i bought this phone flashed a kexec XT910 CM10 build on it , the build couldnt work as the phone process was force closing ,
but i suppose despite my reactivating the stock the kexec build kernel is still functional on the phone thereby leading to battery loss in sleep as well as occasional freeze,
Can anyone now shed some light on the issue of how can i replace this evil cm10 kexec kernel ( if my assumption is correct ) with the stock ics Xt912 kernel WITHOUT THE USE OF A PC as i suspect flashing of that cm10 build isnt letting me connect to any PC in any mode with any cable.
Or may be just link me to any custom stock based ROM which has the stock kernel in it.
i can transfer the rom zip to my sd card thru other means and flash thru the safestrap recovery
Click to expand...
Click to collapse
The link below has a complete stock ROM zip that I had to use to restore a while back when I screwed things up trying to add Google Now to ICS. LOL
I used the 6.7.2
http://sbf.droid-developers.org/cdma_spyder/list.php
thanks mate , but these ROMs can be flashed only thru RSDlite in fastboot mode and for that you need your phone to be connected to a PC ,
and my issue is my phone doesnt get recognised by any PC at all
i need a kernel or a rom with a kernel that can be flashed via recovery
ok lemme rephraze what i need
i am having a drain bug in my setup, be it stock or custom rom .
using latest safestrap and running stock ICS , black widow and eclipse Roms
all showing similar levels of battery drain.
cant use fastboot or anything that requires a PC to flash stuff as my phone wont connect to any PC.
just tell me how to fix this battery drain issue without using a PC
help me plz !!!
Don't know on the fixing battery draing and I am out of suggestions.
Just a few things. And I read a lot of your problem.
When you say windows won't recognize it, are you talking about USB pop ups when you plug it in saying device not recognized?
Because the phone is fragged. That would seem normal.
I just double-checked mine.
In AP fastboot mode windows does not load the normal USB drivers. The only place it shows in windows is under ADB Device in Device Manager. No pop ups.
When in AP Fastboot, the phone recognizes when a USB cable is plugged in. AND when I fire up RSDLite, and I click show devices and it shows nothing. But it should still load.
I just wanted to make sure that you weren't relying on the normal pop-up you get when you normally plug your phone in. You are not going to get that when phone is in fastboot mode. Windows won't show any pop-ups. But it does show in Device Manager under ADB Devices. And the phone switches over to connected on the display.
I just wasn't clear if you had tried that from reading your posts.
Hope you get it resolved.
Hi,
lord dredd I have exactly the same problem, but i haven't applied custom ROM or other kernel. My Device is running on stock OS.
This problem began on sunday, 25th of November, and from that day i'm struggling to repair it.
What i have discovered through App "BetterBatteryStats" is that there are constantly active two kernel wakelocks: "usb" and "suspend_backoff". Through App "OS Monitor" i found that process "system" is constantly using 15-30% of CPU. Sometimes this process is calming down, but plugging USB cord to the phone results in waking it up again.
I think that this two are connected with each other.
The last thing i can now think about is that the USB port or motherboard in the device is corrupted.
I hope that this information will be helpfull in diagnosing what is causing this problem.
Sory, if my english is bad, but i'm not, a native english speaker.
85gallon said:
Don't know on the fixing battery draing and I am out of suggestions.
Just a few things. And I read a lot of your problem.
When you say windows won't recognize it, are you talking about USB pop ups when you plug it in saying device not recognized?
Because the phone is fragged. That would seem normal.
I just double-checked mine.
In AP fastboot mode windows does not load the normal USB drivers. The only place it shows in windows is under ADB Device in Device Manager. No pop ups.
When in AP Fastboot, the phone recognizes when a USB cable is plugged in. AND when I fire up RSDLite, and I click show devices and it shows nothing. But it should still load.
I just wanted to make sure that you weren't relying on the normal pop-up you get when you normally plug your phone in. You are not going to get that when phone is in fastboot mode. Windows won't show any pop-ups. But it does show in Device Manager under ADB Devices. And the phone switches over to connected on the display.
I just wasn't clear if you had tried that from reading your posts.
Hope you get it resolved.
Click to expand...
Click to collapse
Yes I have tried the fast bolt modes and tried flashing with rsd lite as well as tried adb commands too
But nothing actually happens.
The phone sits like that and in adb it says waiting for the device.
I have now lost all hope and will not use this phone.
Sent from the DAD of all S2s - The Epic Touch.
Send a PM to some devs with detailed info about your problem, one of them will help you
Try hashcode, whirleyes, frasertag.
Also you can check this forum:
http://www.droidrzr.com/index.php/index
And most important: DON"T LOSE HOPE
heblu said:
Send a PM to some devs with detailed info about your problem, one of them will help you
Try hashcode, whirleyes, frasertag.
Also you can check this forum:
http://www.droidrzr.com/index.php/index
And most important: DON"T LOSE HOPE
Click to expand...
Click to collapse
thanks a lot mate
lets hope this becomes phone again and doesnt remain like a damn paperweight
regards
guyz tell me
howabout if i downgrade my safestrap to 2
and flsah this
http://forum.xda-developers.com/showthread.php?t=1716392
i guess this one might help fix if this flashed a kernel as well ?
regards
PS : got a working link from droidrazr forumjs.
Greetings,
My son has a Galaxy s2 running stock 2.3 which he bought in Singapore over a year ago, I think. He states that it has not been rooted. Over the last several weeks he has been getting the 'kernal panic upload mode' screen when the battery was getting low. Last week it became permenant regardless of the battery level. Yesterday I was able to talk him through entering recovery mode. He wiped the partition cache and rebooted with no apparent effect. A picture of the recovery mode screen idicates that the system was unable to mount /data (unknown error: 0). But it did show media files were copied succesfully. ... I've attached a picture of the screen. The phone is no longer recognized in Win7.
My basic question. How might we rescue the pictures and some text from the phone before redoing the os?
TIA,
Kim
Kim, flash siyah v5 and try cwm.
Also drill your son on what is that he did exactly, cause he must have done something.
Sent from the little guy
I had thought that if all else failed I would have him use Odin to re-apply his existing os. My thinking was that the file and partition structure would be close enough to what's there to allow normal usb connection and to d/l his pics and what not. Then I'd get him to install something with a little more support for recovery and snooping about. Decent enhancements!!
I don't know what he did other than I think he might have overloaded the little beast with too many apps constantly calling home on an older os. But, that's just a guess. Thanks for the upgrade suggestions. I'm only starting to research that aspect. I suspect that going direct to the better burns will be the way we'll end up going.
Be well,
Kim
Siyah is a custom kernel, no danger regarding existing data.
By flashing it you'll be able to access a temp recovery called clockwork mode.
Sent from the little guy
Greetings gastonw,
My son's getting the usb drivers from the Samsung site for the i9100. I found the tar Siyah-s2-v5.0.1.tar for Odin.
Odin3 version is 3.04. Don't know what else I need.
I'm going to be doing this long distance and I've not handled a smart phone personally so ...
1. Start the phone in download mode.
2. Connect phone to computer
3. Start Odin (making sure that Kies is not running), Odin should recognize the phone.
4. Load the tar in the pda section
5. check automatic reboot, and start.
6. I presume that I will know when it's done because odin will report success or finished, and the phone will boot.
To grab the data off this phone do we use the recovery mode or will it now be called clockwork mode?
At which point I presume we shut the phone down and do a normal start/boot.
Any thoughts would be appreciated. Thanks for your help. Reading the specs on the Siya work I'm almost tempted
to go get a phone for myself.
Be well,
Kim
Lol, that's awesome, your playing by the book
Custom recovery will become CWM instead of stock recovery.
And go ahead and get yourself a new phone, you're in for a hell of a ride.
Sent from the little guy
Thank!! My son called and said the usb still doesn't work. Hum .... I hope not, but I may be back to see if there's a way to transfer something from an sd card in order to save the data. On the flip side ...
Kim
Odin doesn't see his device or the pc calls it "unknown device"?
Can he get it to boot, he can use airdroid app or dropbox to transfer over wifi.
The custom kernel is just to get rid of that pabic message.
Sent from the little guy
Mornin' gastonw,
Well, as of a couple of minutes ago, win7 did not recognize the phone. Hopefully with a reinstallation of the Samsung specific usb drivers win7 and/or Odin will recognize the phone.
Interesting. When he booted into download mode the top of the screen said something like, 'Odin download mode'. Does this indicate that it might be rooted? To the best of my knowledge he was unaware of the three button boot loader mode and hence would not have changed the phone from the basic generic non-branded phone that he bought. Just wondering. If it is rooted is there a way to manually do, via the recovery mode, what Odin will be doing? It seems to me that if recovery allows to d/l from the sd card there must be a destination to be designated. I have no idea what the drive and directory layout is, and I'm a tad rusty on linix shell commands, don't even know what shell android uses. But, if I knew where the package had to go ... .
I'll write again when I know more.
Thanks again,
Kim
Well the last I heard is that no USB *and* it's probably a win7 problem!!!! Good golly miss molly!
Anyway, snooping about I found a thread [howto] which indicated that putting a clock work mod zip on an sd and d/ling it thru the recovery mode would install the clock work mod recovery boot.
http://forum.xda-developers.com/showthread.php?t=1814801
Now I can not find a further reference to a zip with the name format used in this post. However at the modclockwork site I do find two
http://clockworkmod.com/rommanager. One is for 'touch'. I don't know the difference between the two. But, am I understanding correctly that I can put the appropriate zip on an sd from which I can d/l thru the standard recovery mode which on restart I presume will give me access to cmw recovery mode? Seems to easy. LOL!!!
Any help would be appreciated.
Kim
This is how you root & flash cwm via recovery: http://m.youtube.com/#/watch?v=7psIQU69h3M&desktop_uri=/watch?v=7psIQU69h3M&gl=MX
Tell him to try another PC to see if it sees the device.
Genuine s2 usb I assume?
Sent from the little guy
Was trying to go from GB 2.3.3 to OmniROM 4.4.4 on a friend’s S2 (GT I-9100).
I rooted using Framaroot (the first version, the latest wouldnt work), got root, checked with RootChecker. Then I tried to install CWM.
Spent hours trying, I wanted to do everything "on device" rather than use Heidal or ADB (use inux on my desktop), tried MobileOdin, but there was no "recovery" option, so tried ROM Manager using a guide ( http://luvis.se/tipstricks/root-and-install-kitkat-on-samsung-galaxy-s2-i9100-without-a-computer/ ), but kept failing cos of E signature verification, even though ROM Manager said it was installed.
I d spent hours and hours on the internet looking for how to install, seems its difficult because the device was GB.
So I tried MobileOdin again and just installed the "CWM-KitKatCompatible-i9100.zip" I downloaded from the above guide using the "install update.zip" option, I cancelled it when the warning came up about firmware can brick your device, but then hit "ok" (partly in frustration and partly cos I ve never bricked a device before as I m (USUALLY) always careful).
Now it just boots the the Samsung Galaxy S2 screen, then the screen goes blank after 10 seconds or so. Stupid, stupid me.
So can anyone help me recover it using ADB, Android Studio or maybe Heimdal or direct me to a guide on how to ? Everything I read uses Odin and assumes you can get into recovery. All that time trying to avoid connecting it to a pc and now I ve deffo got to.
typos1 said:
Was trying to go from GB 2.3.3 to OmniROM 4.4.4 on a friend’s S2 (GT I-9100).
I rooted using Framaroot (the first version, the latest wouldnt work), got root, checked with RootChecker. Then I tried to install CWM.
Spent hours trying, I wanted to do everything "on device" rather than use Heidal or ADB (use inux on my desktop), tried MobileOdin, but there was no "recovery" option, so tried ROM Manager using a guide ( http://luvis.se/tipstricks/root-and-install-kitkat-on-samsung-galaxy-s2-i9100-without-a-computer/ ), but kept failing cos of E signature verification, even though ROM Manager said it was installed.
I d spent hours and hours on the internet looking for how to install, seems its difficult because the device was GB.
So I tried MobileOdin again and just installed the "CWM-KitKatCompatible-i9100.zip" I downloaded from the above guide using the "install update.zip" option, I cancelled it when the warning came up about firmware can brick your device, but then hit "ok" (partly in frustration and partly cos I ve never bricked a device before as I m (USUALLY) always careful).
Now it just boots the the Samsung Galaxy S2 screen, then the screen goes blank after 10 seconds or so. Stupid, stupid me.
So can anyone help me recover it using ADB, Android Studio or maybe Heimdal or direct me to a guide on how to ? Everything I read uses Odin and assumes you can get into recovery. All that time trying to avoid connecting it to a pc and now I ve deffo got to.
Click to expand...
Click to collapse
Can you get into download or recovery mode?
noppy22 said:
Can you get into download or recovery mode?
Click to expand...
Click to collapse
Cant get into recovery but can get into download mode. Tried One-click Unbrick and it cant connect to device, which reminded me that when I connected it to my (Ubuntu) pc (before I bricked it) I got an error message saying it couldn’t mount Android device (I got rid of my S2 a couple of years ago but it always connected to my pc with no problems). Which seems to me like a real problem - how can I un-brick it if I cant connect via USB ?
typos1 said:
Cant get into recovery but can get into download mode. Tried One-click Unbrick and it cant connect to device, which reminded me that when I connected it to my (Ubuntu) pc (before I bricked it) I got an error message saying it couldn’t mount Android device (I got rid of my S2 a couple of years ago but it always connected to my pc with no problems). Which seems to me like a real problem - how can I un-brick it if I cant connect via USB ?
Click to expand...
Click to collapse
First, I don't have any experience with ubuntu, so I would suggest connecting to a windows pc via usb, making sure you install the drivers for the s2, then download odin. Once you have odin setup, I would flash a stock rom .tar from sammobile.com. From there you can flash a kernel such as philz to gain root access, and then omni or other rom.
noppy22 said:
First, I don't have any experience with ubuntu, so I would suggest connecting to a windows pc via usb, making sure you install the drivers for the s2, then download odin. Once you have odin setup, I would flash a stock rom .tar from sammobile.com. From there you can flash a kernel such as philz to gain root access, and then omni or other rom.
Click to expand...
Click to collapse
Heimdal on Ubuntu (or a Mac) will do the same job as Odin on Windows (and is more reliable), but I have this USB problem I mentioned above, so I m not sure anything is going to work if theres a problem with USB on the device (USB debugging was enabled). One-Click Unbrick cannot connect to it and nor can my pc.
typos1 said:
Heimdal on Ubuntu (or a Mac) will do the same job as Odin on Windows (and is more reliable), but I have this USB problem I mentioned above, so I m not sure anything is going to work if theres a problem with USB on the device (USB debugging was enabled). One-Click Unbrick cannot connect to it and nor can my pc.
Click to expand...
Click to collapse
Probably obvious, and you've maybe tried already, but will a different usb data cord work? And I would try a different pc just to rule it out.
Here is something to read as well about recovering from soft bricks. Hope it helps -
http://forum.xda-developers.com/galaxy-s2/general/guide-fix-unflashable-soft-bricked-gsii-t1449771
noppy22 said:
Probably obvious, and you've maybe tried already, but will a different usb data cord work? And I would try a different pc just to rule it out.
Here is something to read as well about recovering from soft bricks. Hope it helps -
http://forum.xda-developers.com/galaxy-s2/general/guide-fix-unflashable-soft-bricked-gsii-t1449771
Click to expand...
Click to collapse
Thanks, already read that, its not the cable as I use it on other devices without problems.
typos1 said:
Thanks, already read that, its not the cable as I use it on other devices without problems.
Click to expand...
Click to collapse
Mate, the only thing I can suggest is make sure you have drivers for the phone(although the message saying can't mount device indicates a problem like corrupted partitions or nand, rather than missing drivers), and try a different pc. The fact you can get into download mode at least suggests you can flash a kernel or something, but you need a connection to the pc to do that(as you already know). I hope someone else has some other ideas
noppy22 said:
Mate, the only thing I can suggest is make sure you have drivers for the phone(although the message saying can't mount device indicates a problem like corrupted partitions or nand, rather than missing drivers), and try a different pc. The fact you can get into download mode at least suggests you can flash a kernel or something, but you need a connection to the pc to do that(as you already know). I hope someone else has some other ideas
Click to expand...
Click to collapse
I wont need drivers as Linux has drivers built into it - it works out of the box, no messing around installing them like with Windows.
I just gotta spend some time getting the firmware and finding instructions on doing it with Heimdall, theres so many versions of the S2 it makes finding the right software complex.
And I ve just got to hope there isnt a problem with the usb port on the device or I m really buggered
typos1 said:
I wont need drivers as Linux has drivers built into it - it works out of the box, no messing around installing them like with Windows.
I just gotta spend some time getting the firmware and finding instructions on doing it with Heimdall, theres so many versions of the S2 it makes finding the right software complex.
And I ve just got to hope there isnt a problem with the usb port on the device or I m really buggered
Click to expand...
Click to collapse
Lol, I forgot that on Samsung devices you have to press home as well as power and vol up for recovery, found this out while trying to fins out how to unbrick it !
It wouldnnt boot but it WOULD boot to recovery, CWM recovery !
So flashed a CM kernel then Omni and all is fine, OmniROM installed !
typos1 said:
Lol, I forgot that on Samsung devices you have to press home as well as power and vol up for recovery, found this out while trying to fins out how to unbrick it !
It wouldnnt boot but it WOULD boot to recovery, CWM recovery !
So flashed a CM kernel then Omni and all is fine, OmniROM installed !
Click to expand...
Click to collapse
Haha! The simple things in life....
noppy22 said:
Haha! The simple things in life....
Click to expand...
Click to collapse
Yeah !
Ta for your input !
Try flashing official frimware with odin or flash siyah kernel with heimdal
Should fix your problem
Greetings all,
I am a real noob and have recently taken to playing with my android devices.
Unfortunately I am in a predicament with my old S3 I9300.
I really screwed up and failed to make a Nandroid back up when using TWRP to flash Cynagenmod 13, after following the correct procedure on my other I9300 and successfully flashing it I became cocky and made the fatal error of not having a back up. A bit of back story but perhaps unrelated it was also suffering the old "Failed to Mount EFS" message which I have recently learnt to fix on my Old Old I9100 S2 using ADB.
After flasing It was in a Cynagenmod boot loop and was not able to be recognized by my pc via download mode or recovery, so was unable to use Odin, Kies or even ADB.
After experiencing USB issues with Cynagenmod 13 on my other I9300 when the flash was successful, I decided that perhaps it would be better to flash Android Revolution as the USB connections just seem to work better. After the flash seemed to be successful and the Samsung Logo just hung around and never booted.
I played with it all day, trying to get Kies, ADB and Odin to recognize it to no avail, (I tried every little trick on Google, reinstall drivers, restart pc , restart device, plug unplug, play with the buttons and the battery etc.....) the thing is, is that Odin would recognize it in bootloop.
After growing tired of this not working, for some stupid reason I decided to flash CWM over TWRP via MicroSD, i just thought maybe I could get ADB to work or something. Anyway the flash worked and I continued to try ADB, KIES and ODIN but nothing.
To make matters worse currently when I try to go to Recovery CWM is now looping (I'm hoping its a passing phase), so with recovery gone my phone is restricted to Download mode. I really think my last chance is to get download mode communicating with Kies to get the Firmware.
Feeling frustrated and about throw my phone on the recycling heap after googling and reading so many XDA threads I decided to reach out and ask for any help or suggestions in finding a way to get my phone recognized in Download Mode.
I thank you for your time in reading this post and look forward to hearing any advice.
Cheers.
muddled said:
Greetings all,
I am a real noob and have recently taken to playing with my android devices.
Unfortunately I am in a predicament with my old S3 I9300.
I really screwed up and failed to make a Nandroid back up when using TWRP to flash Cynagenmod 13, after following the correct procedure on my other I9300 and successfully flashing it I became cocky and made the fatal error of not having a back up. A bit of back story but perhaps unrelated it was also suffering the old "Failed to Mount EFS" message which I have recently learnt to fix on my Old Old I9100 S2 using ADB.
After flasing It was in a Cynagenmod boot loop and was not able to be recognized by my pc via download mode or recovery, so was unable to use Odin, Kies or even ADB.
After experiencing USB issues with Cynagenmod 13 on my other I9300 when the flash was successful, I decided that perhaps it would be better to flash Android Revolution as the USB connections just seem to work better. After the flash seemed to be successful and the Samsung Logo just hung around and never booted.
I played with it all day, trying to get Kies, ADB and Odin to recognize it to no avail, (I tried every little trick on Google, reinstall drivers, restart pc , restart device, plug unplug, play with the buttons and the battery etc.....) the thing is, is that Odin would recognize it in bootloop.
After growing tired of this not working, for some stupid reason I decided to flash CWM over TWRP via MicroSD, i just thought maybe I could get ADB to work or something. Anyway the flash worked and I continued to try ADB, KIES and ODIN but nothing.
To make matters worse currently when I try to go to Recovery CWM is now looping (I'm hoping its a passing phase), so with recovery gone my phone is restricted to Download mode. I really think my last chance is to get download mode communicating with Kies to get the Firmware.
Feeling frustrated and about throw my phone on the recycling heap after googling and reading so many XDA threads I decided to reach out and ask for any help or suggestions in finding a way to get my phone recognized in Download Mode.
I thank you for your time in reading this post and look forward to hearing any advice.
Cheers.
Click to expand...
Click to collapse
Hey Mate,
Firstly we all are noobs here helping each other, secondly from my experience of S3, it is such a device that under any condition, if your hardware is intact, you can recover your phone from almost anything, so yeah you might have a solution to your problem.
Coming to the problem at hand, i had the same thing happen to my S3, (only twrp logo showed, couldn't access recovery, no ROM, only download mode available) the way i fixed it was using odin, now i know you say that odin is not recognizing your device, the thing is firstly Kies is useless in this situation acc. to me, it only works stock ROM and that too with difficulty, what i would say is go here - http://developer.samsung.com/technical-doc/view.do?v=T000000117
and then install the drivers to your PC, next up download the official firmware from sammobile or any other site (careful of the version you are using), now put the phone in download mod, start odin and then connect your phone. Now, hopefully odin will recognize your phone and you can flash the official firmware, also i would recommend to stay on the official firmware for like a week before returning to flashing again as i have noticed that constant flashing and wiping leads to not only errors like "unable to mount EFS" but also serious errors like "Unable to mount /system" or "Unable to mount /Data" ,which clearly sucks
Please try the method and tell me if it worked , if not we'l try something else but we sure as hell will get your device working again
If still not recognized then here is a suggestion :
Exit/uninstall from nokia/ovi suit.
Exit/uninstall bluestack. (if u r using it)
Update your drivers(phone specific)
Use correct odin version acc to ur phone
Sent from my Micromax E352 using XDA-Developers mobile app
I'm just gonna throw my 2 cents in too. I didn't read your whole thread as I'm in a slight rush right now.
But basically -
Can your PC recognise your phone when it's plugged into USB in Download Mode? If so, use ODIN to flash any stock firmware and you're back to square one (working, but stock) phone. Then go from there. Obviously try to flash the right firmware or you'll end up no further forward.
If it can't recognise it, try reinstalling the drivers, uninstalling the programs mentioned above and using another USB cable. My experience with my own S3 has shown potential wear with the USB port on the bottom of the phone presumably due to it's age and as a result it doesn't recognise many USB cables.
Regards