Basic info: phone is not rooted, the only messing I have done with it was to flash an updated official firmware via Odin (2 years ago) and after that even Kies recognised the firmware as the one I should have.
Yesterday I had a freeze at ~44% battery, did a reset and the phone booted with 0% battery. It switched off, so I took the battery out, put it back in and swtiched it on again. It showed 10% battery, but before completely booting up it froze again. From this point on every time I switch it on it gets to the pulsing 'SAMSUNG' screen at startup and stays there forever.
I am buying a new battery tomorrow. I have researched some ways I can recover the phone, but I am not sure if they will wipe the data. In particular, I would very much like to save my contacts. Is there a way to do this? For example, I read that to flash CWM recovery with Odin I need to unlock bootloader, which will wipe my data. Would one of the various data recovery softwares work in this case (Yodot, Dr.Fone)? Can I get an update to the firmware to my SD card and apply it from the stock recovery, possibly not wiping the phone and recovering the OS?
Also, FYI, I can get to recovery mode, to download mode, but not to safe mode.
Related
Alright, I was having problems with my CyanogenMod, and I went to restart my phone because it kept force closing all my apps (including system processes) and it got stuck on the Vibrant screen and never started up.
I went to Nandroid to restore my backup I made before CM7, and it must be corrupted, because it refused to restore, so I said to hell with it and decided to start from scratch.
Long story short, I ended up flashing the wrong ROM by accident because I got confused between the Samsung Vibrant and the Samsung Galaxy S 4G, and somehow I got my phone stuck at an AT&T World Phone logo, and it won't do anything else. I've tried entering recovery AND download mode, and neither will work. Also, when I plug my phone into the USB port, the charging indicator gets stuck at the very beginning, showing a pinwheel and a greyed out battery.
I ordered a USB jig, hoping this would help send my phone into DL mode, but I'm still open to any ideas anyone has until then. I haven't had a phone for a couple days and its killing me!
itsjuztin said:
Alright, I was having problems with my CyanogenMod, and I went to restart my phone because it kept force closing all my apps (including system processes) and it got stuck on the Vibrant screen and never started up.
I went to Nandroid to restore my backup I made before CM7, and it must be corrupted, because it refused to restore, so I said to hell with it and decided to start from scratch.
Long story short, I ended up flashing the wrong ROM by accident because I got confused between the Samsung Vibrant and the Samsung Galaxy S 4G, and somehow I got my phone stuck at an AT&T World Phone logo, and it won't do anything else. I've tried entering recovery AND download mode, and neither will work. Also, when I plug my phone into the USB port, the charging indicator gets stuck at the very beginning, showing a pinwheel and a greyed out battery.
I ordered a USB jig, hoping this would help send my phone into DL mode, but I'm still open to any ideas anyone has until then. I haven't had a phone for a couple days and its killing me!
Click to expand...
Click to collapse
Here's some tips:
1. NEVER restore non-cm7 nandroid backups on a cm7 based rom.
2. Flash stock JFD with repartitioning checked to go back to stock.
3. Reflash vibrant bootloaders. You may have some captivate bootloaders or a mismatched param.lfs that's causing the AT&T bootsplash. It could be one or the other and mismatching captivate and vibrant bootloaders or params could lead to a brick so just flash the vibrant bootloaders since it contains both bootloaders and param.lfs.
4. DL mode depends on the bootloaders you run.
Froyo bootloaders-------------
1. Volume up and down with USB inserted and with battery disconnected
2. Insert battery without letting go of buttons
Gingerbread bootloaders-------
1. hold power and volume up with the battery inserted and with the phone powered off
2. connect USB to pc when booted into DL mode.
P.S. Can you take a picture of the front and the back of the phone so I can identify the kind of phone you are using at this moment?
The name you are using for the device you have is kinda confusing me.
Hello.
I have a i9100 smartphone with stock XWLSW firmware. After last change of firmware I did not even root it. So it was all stock without root.
My battery was already in bad condition - from 9 AM till 2-4 PM it gets to 15%.
But anyway.
Yesterday it discharged to 1%, when I plugged charger into the phone. I left it working, and after a while I tried to turn the screen on, but the phone was not responding to power key. It was not turning on the screen, and long hold did not turn the phone on.
I unplugged the charger, took out battery and saw a small wet spot on sticker and on battery (maybe it leaked a bit).
Well, it was not the first priority at the moment, so I just wiped it, and put the battery back, then I turned the phone back ON.
It started, but now I have a boot loop at Samsung Logo. When the battery was still discharged I could hear the discharge signal after logo, and then the logo starts again, and discharge signal again, etc.
I left it in that state for a night with charger plugged in. In the morning - it was in the same condition.
Things I tried:
Removing battery for over 10 minutes, clearing Cache from recovery.
Both recovery and download modes are working.
So the question is - can I restore the phone without Factory reset?
If not - can I somehow backup my data (savegames, etc) before doing factory reset?
I just tried to update the firmware again using ODIN with no luck. It updated successfully, but than again hangs on Samsung Logo.
Rule 1: Don't complain until you haven't tried factory reset.So be a man,and do a full wipe.
^^^^
What he said. Also, flash a 3 part firmware, which will also wipe your phone & has a funny habit of fixing situations like this.
I was going to do a Factory Reset or flash 3 part firmware, but only after I backup data. That was my main point of creating this thread - how to backup data in this situation.
Anyway, I did install Philz kernel, wiped dalvik cache, cache partition - it helped, but not for long. I saw my desktop, but after few seconds it went into boot loop again. I then did a Custom backup of data only, and did a Factory Reset through recovery.
Now I try to restore data to see what it will give me.
So i have been having pretty much the same problem with some little differences.
First my battery seems OK, no leaking no nothing, but it might just got old as I've got the phone for over 2 years now... Second, my bootloop occurs after full discharge, when i try to turn on the phone afterwards it just gets stuck on Galaxy SII logo, not even the boot, and stays that way no matter how long i wait. Third, at about the last 5-8% my screen starts flickering as if it wasn't getting enough electricity which shouldnt happen too and never happend before 4 months or so.
So lastly I've been getting this bootloop every now and then. Ive got a temporary fix by backing up my phone through recovery then wiping it clean and then restoring. But i just cant figure out why it does that.... I mean wipe helps, but i do restore everything afterwards....
Without restoring the problem still occurs so its not like i restore something deffective in the sw that makes this happen...
Hi, I've had a quick search and couldn't find anything that matches my question.
My S3 is stuck on the flashing 'Samsung' screen, I've tried connecting it to my pc to restore it with Kies but it won't load up. I've never tried to root it so could I put the phone into download mode and root it then save my data?
I've done a far bit of reading trying to fix it and I've started the phone in boot mode and wiped the cache but I need to get my data off the phone.
I'd be grateful for any help. Thanks:good:
Edit: I rooted it because I got bored of waiting and it still isn't getting past the flashing Samsung screen any ideas?
Try flashing the exact same firmware with Odin, disable kies first.
This might allow your phone to boot but you'll probably have to factory reset anyway. If done in recovery this shouldn't wipe the internal sd card, but you will lose all apps and settings etc.
For the phone to spontaneously stick during boot usually means a corruption issue, most often of the internal storage.
This is the problem I am having with my Samsung Galaxy Note 3 (SM-N900P). This problem just popped up out of the blue on a stock ROM a few days ago and nothing I have tried has gotten close to fixing the issue
Description:
a) The boot sequence repeats in a loop with no more sound. The phone would reboot at the Sprint splash screen
What I've done so far:
a) Pulled the battery and depleted the capacitors
b) Installed TWRP and did a complete wipe
c) Tried installing a custom ROM to see if the issue persisted. ROMs failed to install as /system was being sketchy (at times it was reporting 0MB for partition and then an actual value after repair). When I managed to get a ROM to install still stuck in the boot loop
d) Used Odin to do a full restore to a stock NC5 ROM. The phone got up to initial configuration page and then rebooted, now only gets to the Samsung splash screen before rebooting
Items that I can get into:
Recovery mode
Download mode
I have a 30 second video of it rebooting but cannot post it currently due to the forum rules
Question:
Is this issue fixable or is it a sign of internal memory failure?
Try an older version of TWRP, i.e. 2.8.5.0
Or, try a different recovery.
I'm not sure that it will work, but it's worth a try.
Good luck!
Are you doing it this way?
http://forum.xda-developers.com/showthread.php?t=3069667
rbeavers said:
Are you doing it this way?
http://forum.xda-developers.com/showthread.php?t=3069667
Click to expand...
Click to collapse
I didn't notice that but I just installed TWRP 2.8.0.0 through Odin (like a few minutes ago). Phone actually managed to get to the stock recovery image config screen and was working as long as the cable was still attached to the computer.
As soon as I removed the cable it went straight back to the boot loop
SubRyan said:
I didn't notice that but I just installed TWRP 2.8.0.0 through Odin (like a few minutes ago). Phone actually managed to get to the stock recovery image config screen and was working as long as the cable was still attached to the computer.
As soon as I removed the cable it went straight back to the boot loop
Click to expand...
Click to collapse
Here is what you need to do. First pull battery, reinstall. If you can boot into twrp recovery, fine wipe everything i.e. caches, system, data, etc. If you are on a stock recovery do a factory reset. Pull battery, reinstall and boot into download mode.
NOW let's go to work. First use odin to flash stock NC5 tar. Chances are it will bootloop, STOP !!!! don't panic. Just reflash with odin again. The second time it should take. Remember that your device is setting up for first time use. This will take 3-5 minutes, sitting at the Samsung logo. Since didn't list the most important thing which is what OS you where on where the device Borked, or what you where doing with the device when it Borked. I'm going to assume it was on 4.4.4 and you tried to downgrade to 4.4.2 NC5. In which case a bootloop on the first bootup after a downgrade is normal, you have to flash twice to reset the bootloader. For more info click on rom flashing basics in my signature. Enjoy !!!
Problem solved. I started getting suspicious when the phone would boot up with the charging cable attached to the computer today
The issue was an aftermarket Mugen Power battery that developed a fault. Put the stock battery back in and problem resolved
Thanks for the help guys
Hello guys, hope you doing well... I've an serious problem with my main phone. First, thank you for taking the time to read my story.
I have an Sprint LG G3 32GB since 2 monts ago and it was performing very well. Then I've flashed Resurrection Remix and a custom kernel on it and everything worked perfectly until some days back. I came back from school and left my data opened since the morning and the phone was discharged. I putted it in charge and was sending some messages on whatsapp. I tried to play some music but the phone was not making any sound and it locked on lockscreen and wasn't able to unlock it. Thought it was an OS bug and tried to reboot. While trying I felt asleep and left the phone in charge. Some hours later, the phone won't just boot and in TWRP, it shows Internal storage OMB.
I've waited some time and tried again then it came and I've restored the KitKat stock ROM. After that, the phone started bootlooping and freezing in logo. I was always facing Internal storage OMB and corrupted partition (cache, userdata, system, etc...).
2 days after, I've managed to flash an stock and fresh install TOT via LG FLashTool. The first time, the process didn't worked and I re-tried and then it flashed successfully the phone rebooted to Factory Reset Status 2. I've rebooted and it started with the QHS 9008 Loader COM. I've used boarddiag and restoring stock partitions and tried to flash again via LGFlashtool but the phone will just reboot during flashing in Download Mode and come back in QHS Loader.
This morning, I've sucessfully restored everything and the phone even booted up. It was discharged so I turned it off and left it in charge. Since 3 hours ago, when I try to start the phone, it may freeze on LG Logo or just stay in QHS with everything black. Managed to try AP CHECK and EMMC TEST but AP Pass and EMMC gives me "Error while trying to read partition from EMMC". Basically, that means that my EMMC has fried out or have been damaged. BUT, SURPRISE, sometimes the phone will boot up normally and work for 2 to 5 minutes and power off again and going back to QHS.
NOTE:
-I can't access download mode
-I've flashed the ZV6 cause that's the only ROM who restored via boarddiag and flashed successfully via Download mode
- Also, I've remarked that in the storage page in settings, the phone will show 9GB available and put 21GB in MISC unusable. That's anormal...
THANKS YOU for reading until here.
This is my main phone, any help would be appreciated thanks a lot for responding.
SOLVED
Unmonted the phone and heated a little bit the EMMC chip and putted an small paper in other to make some pressure and remounted.
Everything worked nicely.
Am know facing unlocking issue