My S7 has suddenly rebooted and now it won't go pass Samsung logo. At the first few reboots I was able to see PIN unlock screen where it would eventually freeze and automatically reboot, but now as I removed SIM and microSD it will only boot to Samsung logo in best case.
I have tried to enter recovery mode, but it freezes after 7 seconds at initial screen stating "updating system files". I can only successfully enter download mode.
What should I do? The warranty is not valid anymore, could I flash it with odin? Is there any way to recover data from internal memory? Please help.
krneki10 said:
My S7 has suddenly rebooted and now it won't go pass Samsung logo. At the first few reboots I was able to see PIN unlock screen where it would eventually freeze and automatically reboot, but now as I removed SIM and microSD it will only boot to Samsung logo in best case.
I have tried to enter recovery mode, but it freezes after 7 seconds at initial screen stating "updating system files". I can only successfully enter download mode.
What should I do? The warranty is not valid anymore, could I flash it with odin? Is there any way to recover data from internal memory? Please help.
Click to expand...
Click to collapse
Hey, same problem here !
I have, in addition of all that, the famous "Black screen & blue led" issue when i try to boot up my S7.
But my phone keep freezing when he try to boot. Keep freezing and rebooting 30 seconds after i unlock the screen with the pin (when he can boot), and for the recovery, it works for me, but only once in ten ...
Every times he freeze at the boot, i must wait when the battery hae 0% and shut down automatically
i already tried to wipe cache, but the situation doesn't change anymore.
i don't know too how to recover the internal storage data ...
If someone can help us .. :fingers-crossed:
(For me, my phone is entirely stock, and never flashed)
Related
The unit has been used for about 2 months and remains quite new. It was quite stable before. Yesterday night, about half an hour after plugged in for charging and with WiFi Hotspot turned on for sharing 3G data to another netbook, the unit suddenly rebooted itself. It then stopped at the start-up screen and remained there for several minutes. I kept holding the power button for a few seconds to turn it off but it then automatically reboot itself afterwards, and stopped at the start-up screen again. It means that even complete turning off is not possible.
Trying to enter into recovery mode showed the following few lines:
# MANUAL MODE #
-- Updating application...
Copying Common Apks.
Click to expand...
Click to collapse
and then it automatically rebooted again. It means that it can't enter into recovery mode normally.
It was possible to enter into download mode. And it was the first time this machine went into download mode. I run Odin Downloader and flashed the official stock ROM. After showing "Pass", the device rebooted itself. Unfortunately, it still stopped at the start-up screen, just showing "Samsung Galaxy Tab 7.0 plus". It is really troubesome. I have experience playing several Android devices before and it is the first time I face such troublesome problem.
The device is an official product. The biggest problem is that the original purchase invoice was lost and most likely that I couldn't get official support, repair service or replacement.
May I ask if anyone would kindly provide me some help or advice. Thanks!
Instead of going into download mode go into recovery mode and see if there are any errors. Your scenario is sounding very similar to the one I had in the past.
I just ran into a nasty snag at boot logo as well. nandroid, stock kernel and factory reset were no help. Try Odin back to Stock, it still may not get past boot logo, hold vol up and power to get into recovery and factory reset. Hope it works for you.
Unfortunately I was unable to get into recovery mode even after odin flashing stock ROM.
It rebooted itself a few seconds after displaying some lines of text. I can't see the normal recovery menu.
Hey there XDA! I thought I'd root my P920 a few days back, which went smooth, no issues and I was enjoying my newly rooted Optimus
I wanted to get a new kernel for it, so first thing I did was install CWM, Then clicking on 'Flash ClockworkMod recovery' in the app, which then flashed a CWM recovery if I'm not wrong. The final thing left to do was rebooting into the recovery, which I did by clicking 'Reboot into recovery'
Now waiting for the phone to reboot into recovery, the LG logo came up on screen, and stayed there for some time, which is normal behaviour as it takes a bit of a while to boot up for me, but then something odd happened, the logo disappeared and the screen blacked out, leaving the phone off. Immediately noticing this, I tried to boot the phone up as I normally would, but again the same thing occurred, logo appears, then phone blacks out and returns to an off state.I repeated this a few times, but to no avail.
These are some things I tried:
Normal booting multiple times
Normal booting after battery pull
Normal booting while charging
Normal booting after removing SD card (this resulted in a blue screen appearing after the LG logo on bootup, though I was impatient and didn't wait to see what would happen so I pulled the battery out )
Normal booting after removing SD card and then battery pull
Normal booting after removing SD and SIM card
Normal booting after removing SD and SIM and then battery pull
Booting into recovery multiple times
Booting into recovery while charging
Booting into recovery while charging
Booting into recovery after removing SD card and battery pull
Booting into recovery after removing SD card
Booting into recovery after removing SD and SIM card
Booting into recovery after removing SD and SIM card and battery pull
So as can be seen I've tried tons of situations
A few times, the screen turned into repeated patterns of static colour, it's difficult to describe but its only happened a couple times, and appeared on top of the LG logo. From what I've gathered, something is preventing the phone from booting up properly, either normally or into recovery, unless the problem is something else entirely. Also I don't have any NANdroid or Titanium backups.
So my questions are, could it be that I need a full charge for it to boot properly? Otherwise what's the problem and how do I get the phone to boot normally? I would prefer that all data on the phone is not erased but if it's a must then so be it.
I really appreciate any and all help I can get here, thanks!
P.S. I'm new to rooting and customising at that level, so please ask for any additional details or anything I was unclear about. Apologies to all for the lengthy first post, thanks again!
AW: [Q] Boot issues after installing CWM recovery
Hi welcome
Girst thing you have to do before flashing or doining something with your phone is a nandroid backup. I do always a titaniumbackup and saved pictures and music manually only for insurence. Next thing, whcich app do you use for flashing cwm?
For your data im not sure if you can rescue that i dont think so.
If i understand it right your are stuck on bootlogo right?
To rescue your phone you can always go back to gb by flashing kdz file with flashtool. Watch here
http://forum.xda-developers.com/showthread.php?t=1540163
But in that case you will loose all your data on phone.
P.S. and next time if you want to flash cwm use os_hackings all in one tool. And flash twrp recovery its better and didnt have so much bugs
Sent from my LG-SU760 using xda app-developers app
I used ROM Manager for flashing cwm, yes I am stuck on bootlogo
Thanks for the help! I'll try out what you suggested and report back here if it works
Hi there,
I changed my broken screen on nexus 5 but after that unable to boot.
I can boot in recovery mode, actually I did a factory reset and also a fresh ROM installation via ADB.
The problem is still the same: the device seems to start normally, I see google logo etc but when I have to put pin to unlock SIM I see the screen for half second and then the screen go black.
Please help me!
Thanks,
Sandra
Hello XDA!
This morning, I attempted to flash Cyanogenmod 12 (CM12) onto my Google Nexus 6 using this youtube tutorial that I cannot link in this post, because I am a new member. The title of the video is "How to install CyanogenMod 12 Official Lollipop on the Nexus 6" It can be found on youtube.
Whenever I boot up the phone, it shows the "Google" screen. then the Cyanogenmod boot animation appears. A white popup shows up saying "Android is Starting Up. Finishing Boot" The entire screen then comes to life with cyanogen's default background. Finally, an error message consumes the screen saying "ENCRYPTION UNSUCCESSFUL. Encryption was interrupted and can't complete. As a result, the data on your phone is no longer accessible. To resume using your phone, we need to preform a factory reset. When you restore your phone after the reset, you'll have an opportunity to restore any data that was backed up to your google account." The only button shown on the screen says "RESET PHONE". If clicked, the phone reboots, but before it can boot it gets stuck loading the TWRP Recovery application. What happens is, it'll show the TWRP logo, then the screen will turn off, then it'll show the TWRP logo again, then this loop will repeat endlessly. The only thing that I could do was reboot the phone into the boot loader by holding down the power button, and the volume down button. From here, I attempted to boot into recovery mode. The same thing happens, the TWRP screen loads, then disappears, and that just repeats itself endlessly. I also tried to preform a factory reset, but that didn't work.
As you can see, I really need some help.
The encryption failing may be caused because I came off of a custom ROM where I had the phone's encryption disabled.
THANK YOU VERY MUCH, and if I can provide any information, please ask.
Hey guys!
Obviously, the force of the "lack-of-knowledge" gods has struck again...
I was just trying to create a backup of my Galaxy S7 (930F) using TWRP recovery. The first attempt failed, saying "couldn't mount /data"...i browsed through the web and searched for solutions...found a video on youtube saying that it would be recommendable to change the file system if the EXT4 didn't work...so i did to exFAT and then, hell broke in on me...
The phone got stuck in changing the file system...after 20 min i killed it by pressing all 4 buttons...then it kept booting and booting to the galaxy logo...i tried to shut down again and reboot into recovery....it worked and I could see my providers logo again....but after that "Samsung" appeared, changing in brightness and nothing more since then...i shut it down and here I am..
Is it bricked..or what can I do now? Please help!!!!!
Thanks in advance!
Greetings Alex
Flash a stock ROM from here
Code:
http://updato.com/firmware-archive-select-model?q=G930F
With ODIN from here
Code:
https://mega.nz/#!acoGhA7a!17OPP5A1g9d7-GxAqCbjXFpmYfO7CgAHNcaZxqEkOao
And the phone in download mode (Volume down & home & power)
If you can't get it into download mode, hold those three buttons in until the phone reboots a second time, hopefully into download mode
dr.zikzak said:
Hey guys!
Obviously, the force of the "lack-of-knowledge" gods has struck again...
I was just trying to create a backup of my Galaxy S7 (930F) using TWRP recovery. The first attempt failed, saying "couldn't mount /data"...i browsed through the web and searched for solutions...found a video on youtube saying that it would be recommendable to change the file system if the EXT4 didn't work...so i did to exFAT and then, hell broke in on me...
The phone got stuck in changing the file system...after 20 min i killed it by pressing all 4 buttons...then it kept booting and booting to the galaxy logo...i tried to shut down again and reboot into recovery....it worked and I could see my providers logo again....but after that "Samsung" appeared, changing in brightness and nothing more since then...i shut it down and here I am..
Is it bricked..or what can I do now? Please help!!!!!
Thanks in advance!
Greetings Alex
Click to expand...
Click to collapse
Hi!
Does it got fixed for you? I have the same issue.