Related
It's my beloved I9100P. Last night it strangely failed. I realised in the morning when the alarm didn't go off. The phone was switched off.
When I tried to switch on, it got stuck in boot loop. The carrier animation and samsung logo will keep repeating. So I thought I will go into recover mode and do a factory reset. Phone went into factory mode the first time. I thought let me do a restart from there, just to see what happens. At this point, I noticed a lot of red errors on recovery mode screen, most of which saying something like "unable to mount /cache". I restarted it, but unfortunately the phone again went into boot loop.
Now when I tried, it refused to go even to recovery mode. I tried several times, but every time it got stuck on Samsung Galaxy logo.
It went into download mode fine, so I thought I will flash Orange UK carrier ROM. I downloaded the ROM and tried flashing with ODIN. ODIN recognised the device, but the flashing failed with error "Complete (Write) operation failed".
I don't know what to do now, have exhausted all option that I knew.
Any help in reviving my phone please?
@kaushal101 Keep yourphone phone connected to your pc and keep it in download mode. Dont disconnect it it could turn into a hardbrick which you can't fix without jtag repair service.
What you could do is see or you have installled all drivers, kies is disabled, right odin version. Google the problem and you would probably find an answer fast. I hope this message isnt too late..
wulsic said:
@kaushal101 Keep yourphone phone connected to your pc and keep it in download mode. Dont disconnect it it could turn into a hardbrick which you can't fix without jtag repair service.
What you could do is see or you have installled all drivers, kies is disabled, right odin version. Google the problem and you would probably find an answer fast. I hope this message isnt too late..
Click to expand...
Click to collapse
Interesting. After trying several things, I did unplugged it from the machine. It shows the upgrade failed warning message whenever I try to switch it on now, which was expected.
I can still go to download mode and restart the ODIN flashing original Orange firmware process, but it fails with the same error. The only difference is, the first time it failed on CACHE step. Now it is failing one step earlier, at NAND writing stage.
Is there any hope? I had kies disabled etc., but will give it another shot. My phone was accessible with kies and I could also upload my development APKs from Android studio. So I think drivers shouldn't be a problem.
@kaushal101 I dont really have much knowledge about the s2 anymore, so the only good thing I can suggest is to google the problem and get more people to your thread here to help you and or find other threads about the same thing.
It is good that your phone can still go into downloadmode, I think there is still hope to fix your phone
wulsic said:
@kaushal101 I dont really have much knowledge about the s2 anymore, so the only good thing I can suggest is to google the problem and get more people to your thread here to help you and or find other threads about the same thing.
It is good that your phone can still go into downloadmode, I think there is still hope to fix your phone
Click to expand...
Click to collapse
Thanks for keeping the hope alive!
Have followed XDA's S2-ODIN troubleshoot guide, with no luck so far. Tried different versions of ODIN, reinstalled USB drivers, made sure KIES is removed from processes etc. None has helped so far. I'll keep looking!
kaushal101 said:
Thanks for keeping the hope alive!
Have followed XDA's S2-ODIN troubleshoot guide, with no luck so far. Tried different versions of ODIN, reinstalled USB drivers, made sure KIES is removed from processes etc. None has helped so far. I'll keep looking!
Click to expand...
Click to collapse
Did you tryed another stock rom version?
Try other usb cable.
Sounds weird but try to leave the battery out of your phone for like a couple minutes
Try other usb port.
Try other computer:silly:
These are the things I can think of atm.
Have tried other USB port. Have tried a different firmware.
Am going to try a different PC today, will also give different cable a shot. But the cable I'm using is Samsung official one which came with the phone. And I've been uploading APKs using this cable fine, so am quite sure the cable is fine. But still, will give it a shot. Thanks for replying
Hi all.
I have installed the Cyanogenmod 12.1 UNOFFICIAL on my Galaxy S II for several months, but yesterday, suddenly, the phone shutted down and kept doing this everytime I tried to turn it on, until I couldn't even go further than the "Samsung Galaxy S II" sign.
At first I could boot in recovery mode, so I tried to do a full wipe and then re-install the Cyanogenmod, but something went wrong during the installation and a dead android with a red triangle appeared in the background. I rebooted the phone, and from that moment on I couldn't even boot in recovery mode anymore.
So I followed this guide found in the forum to fix the issue (http://forum.xda-developers.com/galaxy-s2/general/guide-fix-unflashable-soft-bricked-gsii-t1449771) and it worked well, because the phone installed everything successfully.
Now, the bad news is that the phone keeps shutting down soon after the operative system starts (I can't even finish the initial configuration). The good news is that at least I can boot in recovery mode (in this way the phone is turned on as long as there is enough battery energy, so it is not an hardware problem, I guess).
I really don't know what else could I do.
Can you help me in any way please? Is it a known issue? How can I fix this?
If you need further informations I'll be happy to let you know them.
Very thanks in advance.
You are using an unofficial build of CM, install an official build of CM12
Fhronk said:
Hi all.
I have installed the Cyanogenmod 12.1 UNOFFICIAL on my Galaxy S II for several months, but yesterday, suddenly, the phone shutted down and kept doing this everytime I tried to turn it on, until I couldn't even go further than the "Samsung Galaxy S II" sign.
At first I could boot in recovery mode, so I tried to do a full wipe and then re-install the Cyanogenmod, but something went wrong during the installation and a dead android with a red triangle appeared in the background. I rebooted the phone, and from that moment on I couldn't even boot in recovery mode anymore.
So I followed this guide found in the forum to fix the issue (http://forum.xda-developers.com/galaxy-s2/general/guide-fix-unflashable-soft-bricked-gsii-t1449771) and it worked well, because the phone installed everything successfully.
Now, the bad news is that the phone keeps shutting down soon after the operative system starts (I can't even finish the initial configuration). The good news is that at least I can boot in recovery mode (in this way the phone is turned on as long as there is enough battery energy, so it is not an hardware problem, I guess).
I really don't know what else could I do.
Can you help me in any way please? Is it a known issue? How can I fix this?
If you need further informations I'll be happy to let you know them.
Very thanks in advance.
Click to expand...
Click to collapse
Is your device boots and works well on stock?
nhmanas said:
Is your device boots and works well on stock?
Click to expand...
Click to collapse
My device couldn't even boot in the end. However I solved the problem by changing battery, so it wasn't a software problem. Thank you anyway!
Greetings Everyone,
Yesterday i installed the last CM13 nightly via the CM updater in this phone.
But after the phone restarted, a green android and a "installing system update" appeared for a few seconds then after it went black, the screen blinks each 5 seconds or so, but nothing ever happens. I left the phone on overnight to see if something came up, but to no avail.
Furthermore, now i cannot enter recovery mode, only download mode and my computer does not recognize the phone. I tried pretty much everything, the basic guide on rooting i9100, KIES, Odin, Heimdall flashing, offering corpses to the Old Ones and nothing works.
Does anyone have any insight on what might be happening? I installed CM13 on my two phones (a z3c and a Note 4) and everything went smoothly. Now with this i9100 i was using 6.0.1 but everything went to hell after i tried this update.
Thanks in advance
I'm in a same boat
Hey Mate ....!
I'm in a same boat i have tried almost everything Odin seems worked for 30 seconds and than it shows failed. I love this perticuilar handset allot it was gifted to me by very special it was awarded to me by my last company i want to save it please help me if anyone has the solution . What exactly happen to you , Same happen to me exactly same. please update if you get solution. Thanks in Advance.
Regards
Fazal
argethalm said:
Greetings Everyone,
Yesterday i installed the last CM13 nightly via the CM updater in this phone.
But after the phone restarted, a green android and a "installing system update" appeared for a few seconds then after it went black, the screen blinks each 5 seconds or so, but nothing ever happens. I left the phone on overnight to see if something came up, but to no avail.
Furthermore, now i cannot enter recovery mode, only download mode and my computer does not recognize the phone. I tried pretty much everything, the basic guide on rooting i9100, KIES, Odin, Heimdall flashing, offering corpses to the Old Ones and nothing works.
Does anyone have any insight on what might be happening? I installed CM13 on my two phones (a z3c and a Note 4) and everything went smoothly. Now with this i9100 i was using 6.0.1 but everything went to hell after i tried this update.
Thanks in advance
Click to expand...
Click to collapse
You might find your answer here I'm not clever enough to post the link so you get it "Longhand".
Go To Forum Galaxy SII General.
Scroll to [Guide} Fix an unflashable or soft bricked GSII (i9100G/P/T/ versions included)
Have a good read through it and if you dare go for it . It's a "back to the future" sort of thing, takes you back to "jellybean" and android 4.1.2. (The route I took anyway)! Good Luck!
same problem here! please help me get my phone back :crying:
argethalm, fazallfrd, ThiagovGuerra
I had same problem - but ....... it was software bricked. Like yours.
If I repair then all of you can repair like me.
http://forum.xda-developers.com/galaxy-s2/development-derivatives/rom-cyanogenmod-13-t3223808
Everything i take from this link.
You can rebuild with patient.
This problem has been driving me absolutely mental. About 2 months ago, I tried to root my Galaxy Tab 4 8.0 by T-Mobile (it was an old device anyways), I used the Odin method, and while it was installing, it said that the process was successful, and I saw it all come through. However, when my device restarted, it was stuck at "Starting apps..." for about an hour, so I tried restarting. Then it was stuck on the T-Mobile logo for 1.5 hours. I did a hard wipe/reset, and it was fine... for about a week.
The funny thing about it is, after I did the hard reset, certain bugs would happen, a different bug each time. (For example, Google Play apps would be stuck at "installing", screenshots wouldn't save, apps would crash repeatedly, etc) So if I tried to restart, it wouldn't fix it, but instead it would bootloop. I have to hard reset/wipe my whole system each time it happens, and it drives me up the friggin wall.
I saw online that you can try flashing your system by installing the default drivers onto your computer, and install it on your system through Odin. (or something like that, I'm not that professional at mobile technology) Awesome. Just one problem.. I have looked everywhere and I can't find the driver specifically for my system. I have looked for the driver ever since the problem got worse and I found out about this information, but I found nothing.
If anyone has any idea on how you can help, please respond as soon as you can. Thank you very much.
iamnekro said:
This problem has been driving me absolutely mental. About 2 months ago, I tried to root my Galaxy Tab 4 8.0 by T-Mobile (it was an old device anyways), I used the Odin method, and while it was installing, it said that the process was successful, and I saw it all come through. However, when my device restarted, it was stuck at "Starting apps..." for about an hour, so I tried restarting. Then it was stuck on the T-Mobile logo for 1.5 hours. I did a hard wipe/reset, and it was fine... for about a week.
The funny thing about it is, after I did the hard reset, certain bugs would happen, a different bug each time. (For example, Google Play apps would be stuck at "installing", screenshots wouldn't save, apps would crash repeatedly, etc) So if I tried to restart, it wouldn't fix it, but instead it would bootloop. I have to hard reset/wipe my whole system each time it happens, and it drives me up the friggin wall.
I saw online that you can try flashing your system by installing the default drivers onto your computer, and install it on your system through Odin. (or something like that, I'm not that professional at mobile technology) Awesome. Just one problem.. I have looked everywhere and I can't find the driver specifically for my system. I have looked for the driver ever since the problem got worse and I found out about this information, but I found nothing.
If anyone has any idea on how you can help, please respond as soon as you can. Thank you very much.
Click to expand...
Click to collapse
What you read in the internet means re-flashing your stock rom (system), that is the fix for your problem, the way to do it is to download and install Samsung USB drivers if you hadn't done that already, and Download stock rom from here or here search your model number in the search box and choose the stock rom based on your country, and flash with Odin, it's pretty much the same way you tried to root using CF-ROOT method:
1-you boot into download mode (volume down + home button + power button)
2-and then connect your phone to PC.
3-open Odin and uncheck everything except "auto reboot" and "F. Reset Time" (you should find it like that already), make sure your phone is recognized by Odin, you will see a blue box with a message saying "0:[COMX]" where X is a number.
4-press AP (or PDA in some versions) locate your stock rom which should be in .md5 format, and choose it, then 5-press start.
6-wait for the process to finish (takes a while) and then the phone should reboot itself and you will get a message in Odin saying "Reset!"
PS: you must register on the sites to download..bad thing i know but it's obligation.
Searched both of these websites for the drivers, found nothing.. I've been searching the internet for hours and not one driver was found. Extremely disappointed.
iamnekro said:
Searched both of these websites for the drivers, found nothing.. I've been searching the internet for hours and not one driver was found. Extremely disappointed.
Click to expand...
Click to collapse
Give me your model number.
Sorry found it in the thread title
@iamnekro
That is the link from the first site:
SM-T337T latest firmware android 5.1.1
That is the link from the second site:
SM-T337T latest firmware android 5.1.1
Obviously you didn't search at all...LOL
PS: It's called Stock Firmware or Stock ROM.... not Drivers
Register on any of the sites first to download.
And press the thanks button please
Regards Migo
I'll have to close the thread.. my computer isn't that advanced and is low on space anyways...
iamnekro said:
I'll have to close the thread.. my computer isn't that advanced and is low on space anyways...
Click to expand...
Click to collapse
It doesn't need any advanced computer and only the size of the stock rom and Odin, it's no big deal.
Hello all.
I´m pretty desperated at this point. No matter what, my phone (LG G2 mini D620k, I have 2 years with it) keeps bricking. Keep in mind I´m a noob in this world, so I´m looking for help here.
This started like 2 months ago, it bricked so I searched on Internet and did the hard reset. It worked well, for a while. I downloaded all my usual apps without rooting it, then suddenly: bricked.
Another hard reset, and again, it worked. So someday it started freezing, apps closing, so in like a week I used 10 times the LG Mobile support tool to fix errors. It fixed the phone but just for 1-2 days. So again, I did factory reset (this time from the phone, it wasn´t bricked), rooted it, debloated it, and worked fine for 48 hours. Last night it again, from nothing, bricked.
Did hard reset again. I'm asking here: what is wrong with the phone? What is causing this? Is an app? Too many apps? Hardware? Battery?
I love my phone but I´m tired of sitting 3 hours every 2 days fixing it. Cannot afford a new phone or looking for specialized help, so I´m asking here for help.
Keep in mind I´m a noob in this. Can someone help me?
Sorry if this matter is already answered, I did a search and found nothing like this.
Sorry for my bad english.
When you say "bricking" do you mean bootlooping (the LG boot animation keeps playing)?
If so, try to capture a logcat while it's bootlooping via adb. Let it capture for a minute, or so. Then send it to me.
Then, pull out the battery for a couple of seconds, put it back in and power up the phone. Does it still bootloop?
Teutonica said:
This started like 2 months ago, it bricked so I searched on Internet and did the hard reset. It worked well, for a while. I downloaded all my usual apps without rooting it, then suddenly: bricked.
Click to expand...
Click to collapse
I have the same issue!! I've tryed every CM Rom, custom roms, stock roms and now latest RR, and still the same problem. After flash I install only FB, Messenger and Insta (it's girlfriend's phone) and after 1-2 days phone gets bootloop (only RR logo). I have to do hard reset and flash again whole system to work properly again (for a few days).
I gave my G2Mini to service (not LG Service) but they said that its motherboard issue (probably some boot memory is broken and has memory "leaks") But I think that it cant be this. If this is possible I would try to flash whole system on SD card not internal memmory, maybe this will work
help!
Edit:
Vagelis1608 said:
When you say "bricking" do you mean bootlooping (the LG boot animation keeps playing)?
If so, try to capture a logcat while it's bootlooping via adb. Let it capture for a minute, or so. Then send it to me.
Then, pull out the battery for a couple of seconds, put it back in and power up the phone. Does it still bootloop?
Click to expand...
Click to collapse
I have sometimes stuck on LG logo, and sometimes on Resurrection logo, only full wipe, and flash help (I can still enter recovery mode and TWRP) How to capture logcat via adb? Pulling out battery doesn't help
Up.
Please help me Anybody know the solution? I really need this. (sorry for double post)
Khotu said:
Up.
Please help me Anybody know the solution? I really need this. (sorry for double post)
Click to expand...
Click to collapse
Grab a logcat via adb.
Install adb and Google's drivers (for custom ROMs, LG's for stock ROMs).
Let it record for a minute and give it to us.
I managed to install CM13, worked fine for a month I guess... started with random bugs "x app stopped working". So I restarted the phone and it's in eternal logo when I turn it on.
Since I'm a totally noob at this, I can't find a noob-friendly guide to make it work again.
:crying:
Teutonica said:
I managed to install CM13, worked fine for a month I guess... started with random bugs "x app stopped working". So I restarted the phone and it's in eternal logo when I turn it on.
Since I'm a totally noob at this, I can't find a noob-friendly guide to make it work again.
:crying:
Click to expand...
Click to collapse
Wipe /data in recovery.
If that doesn't work, reinstall the ROM and 'pico' OpenGApps
Vagelis1608 said:
Wipe /data in recovery.
If that doesn't work, reinstall the ROM and 'pico' OpenGApps
Click to expand...
Click to collapse
Managed to connect it to my laptop (I could't before), used LGMobile support tool, back to original rom. I guess it will be matter of time to get same errors as before. At least it works again... idk for how long :s
Hard life for a android n00b :x
update:
it freezes suddenly (started in the middle of a skype videocall).
I'm starting to suspect it's a ram problem. Any ideas?
I have the same problem. Did you find any solution?
Nope just threw away this phone and bought new one
Khotu said:
Nope just threw away this phone and bought new one
Click to expand...
Click to collapse
You should had sold it for parts