Hi all,
Yesterday I installed an app from the play store and my phone suddenly turned unresponsive (the app was seemingly innocent) and crashed. When I attempted to turn it back on, it would reach the Samsung logo and go no further. I have attempted to fix it using smart switch, kies, odin etc yet it is still in a boot loop. Smart Switch, Kies and Odin all manage to successfully complete flashing the stock ROM but nothing changes. I have also wiped the cache and factory reset the device via the recovery mode, yet the boot loop still occurs.
Also, the boot loop isn't consistent. Sometimes it will only reach the "Samsung galaxy S7 - powered by android" splash screen, the "Samsung" splash screen, the green "installing apps..." splash screen and sometimes when it reaches the "Samsung" splash screen it crashes halfway.
As a side note, I am able to reach recovery and download mode.
Can anyone give me any further suggestions?
Thanks in advance
zelkov said:
Hi all,
Yesterday I installed an app from the play store and my phone suddenly turned unresponsive (the app was seemingly innocent) and crashed. When I attempted to turn it back on, it would reach the Samsung logo and go no further. I have attempted to fix it using smart switch, kies, odin etc yet it is still in a boot loop. Smart Switch, Kies and Odin all manage to successfully complete flashing the stock ROM but nothing changes. I have also wiped the cache and factory reset the device via the recovery mode, yet the boot loop still occurs.
Also, the boot loop isn't consistent. Sometimes it will only reach the "Samsung galaxy S7 - powered by android" splash screen, the "Samsung" splash screen, the green "installing apps..." splash screen and sometimes when it reaches the "Samsung" splash screen it crashes halfway.
As a side note, I am able to reach recovery and download mode.
Can anyone give me any further suggestions?
Thanks in advance
Click to expand...
Click to collapse
Hmm... This is puzzling, have you tried to boot into safe mode and then delete the app.
Here's how to turn on Safe mode:
1. Power the phone off.
2. Once the phone is off and all lights are emitting,
press and hold the “Power” button to turn the S7
back on.
3. When the Galaxy logo appears on the screen,
press and hold the “Volume Down” button.
4. Continue to hold the “Volume Down” button until
the phone completely boots. You will see the
words “Safe Mode” appear in the lower left
corner of the screen if you performed the steps
properly.
Here's how to get out of Safe Mode (if you are lucky and the device boots):
Just powering off and then restarting should get you out of Safe Mode, although some models may require you to hold down the Volume Down key.
Side Note: This probably would not work, although as the phone does not boot even after you flashed stock ROM.
Extra Side Note: Please check that you have not mistakenly flashed the wrong stock ROM as that may also produce the same symptoms.
EXTRA Extra Side Note: Try installing ADB on your laptop using this link:
http://forum.xda-developers.com/showthread.php?t=2317790&page=63
And then running adb devices to see if your device gets recognised, if it does try adb logcat and report back any errors you see to the forums, maybe we can understand something out of it.
By the way, please update this thread on any progress. :good:
Hope you get your device fixed!
Edit: I am curious, what is the name of the app?
Random04 said:
Hmm... This is puzzling, have you tried to boot into safe mode and then delete the app.
Here's how to turn on Safe mode:
1. Power the phone off.
2. Once the phone is off and all lights are emitting,
press and hold the “Power†button to turn the S7
back on.
3. When the Galaxy logo appears on the screen,
press and hold the “Volume Down†button.
4. Continue to hold the “Volume Down†button until
the phone completely boots. You will see the
words “Safe Mode†appear in the lower left
corner of the screen if you performed the steps
properly.
Here's how to get out of Safe Mode (if you are lucky and the device boots):
Just powering off and then restarting should get you out of Safe Mode, although some models may require you to hold down the Volume Down key.
Side Note: This probably would not work, although as the phone does not boot even after you flashed stock ROM.
Extra Side Note: Please check that you have not mistakenly flashed the wrong stock ROM as that may also produce the same symptoms.
EXTRA Extra Side Note: Try installing ADB on your laptop using this link:
http://forum.xda-developers.com/showthread.php?t=2317790&page=63
And then running adb devices to see if your device gets recognised, if it does try adb logcat and report back any errors you see to the forums, maybe we can understand something out of it.
By the way, please update this thread on any progress. :good:
Hope you get your device fixed!
Edit: I am curious, what is the name of the app?
Click to expand...
Click to collapse
Thank you for your suggestions. I managed to get it to boot up by deleting the cache.img file before flashing the ROM. However, I have encountered another issue - firstly, it prompted me for the password used to encrypt the device storage and when I did it did not recognise the password; thankfully default_password worked for this. Now, Google is asking me to enter an email address previously synced to the device, though I can't remember such addresses!
The app is called "Roll the Ball - slide puzzle" created by BitMango.
zelkov said:
Thank you for your suggestions. I managed to get it to boot up by deleting the cache.img file before flashing the ROM. However, I have encountered another issue - firstly, it prompted me for the password used to encrypt the device storage and when I did it did not recognise the password; thankfully default_password worked for this. Now, Google is asking me to enter an email address previously synced to the device, though I can't remember such addresses!
The app is called "Roll the Ball - slide puzzle" created by BitMango.
Click to expand...
Click to collapse
Google is asking for you to enter the Gmail id you signed in to when you set up play store (i.e your gmail account), this is called FRP and is installed on all latest Android devices to prevent someone who is not the owner to factory reset the phone (theft) through the recovery.
Although if you are unable to login due to it being corrupted or some other reason then follow this guide. http://forum.xda-developers.com/galaxy-s7/how-to/bypass-frp-samsung-s7-edge-global-usa-t3405954/
Best of Luck!:good:
Edit: Please read through the thread before you try to follow the guide as the guide does not work on latest Samsung firmwares so you may need to install an older version of the ROM for your phone.
(By the way, if you don't already use it, try Updato instead of Sammobile as it does not have a download speed limit. Link to the Thread: http://forum.xda-developers.com/gal...rgest-online-firmware-archive-t3413785/page18 , also, if this does not work try to use Samfirm, (precedessor to Updato/deprecated) it still (allegedly) works! Link: http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647/page99
Random04 said:
Google is asking for you to enter the Gmail id you signed in to when you set up play store (i.e your gmail account), this is called FRP and is installed on all latest Android devices to prevent someone who is not the owner to factory reset the phone (theft) through the recovery.
Although if you are unable to login due to it being corrupted or some other reason then follow this guide. http://forum.xda-developers.com/galaxy-s7/how-to/bypass-frp-samsung-s7-edge-global-usa-t3405954/
Best of Luck!:good:
Edit: Please read through the thread before you try to follow the guide as the guide does not work on latest Samsung firmwares so you may need to install an older version of the ROM for your phone.
(By the way, if you don't already use it, try Updato instead of Sammobile as it does not have a download speed limit. Link to the Thread: http://forum.xda-developers.com/gal...rgest-online-firmware-archive-t3413785/page18 , also, if this does not work try to use Samfirm, (precedessor to Updato/deprecated) it still (allegedly) works! Link: http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647/page99
Click to expand...
Click to collapse
I managed to bypass the FRP but after factory resetting it I'm back to the beginning. This time, it boots to the lock screen that asks for the password to decrypt the file storage (default_password works for this) and then goes to the green splash screen with rotating gears that says "Android is upgrading... starting app xx of xx" and then crashes and loops.
Thank you for those links! I have been using Sammobile and it is so slow.
zelkov said:
I managed to bypass the FRP but after factory resetting it I'm back to the beginning. This time, it boots to the lock screen that asks for the password to decrypt the file storage (default_password works for this) and then goes to the green splash screen with rotating gears that says "Android is upgrading... starting app xx of xx" and then crashes and loops.
Thank you for those links! I have been using Sammobile and it is so slow.
Click to expand...
Click to collapse
If you can go to the Android is starting splash screen my first post in this thread (the safe mode one) may work. (On second thought, probably not, but still worth a shot)
Also, don't forget to take an adb logcat of your device as detailed in the first post as it may point out what exactly is causing the crash. (look out for recurring errors).
I wish that I could add more to this, but I am honestly running out of ideas.
Edit: Have you tried wiping the cache partition. :fingers-crossed:
Sent from my Samsung SM-G935F using XDA Labs
Random04 said:
If you can go to the Android is starting splash screen my first post in this thread (the safe mode one) may work. (On second thought, probably not, but still worth a shot)
Also, don't forget to take an adb logcat of your device as detailed in the first post as it may point out what exactly is causing the crash. (look out for recurring errors).
I wish that I could add more to this, but I am honestly running out of ideas.
Edit: Have you tried wiping the cache partition. :fingers-crossed:
Sent from my Samsung SM-G935F using XDA Labs
Click to expand...
Click to collapse
Cheers for reminding me about safe mode; that made it boot up. I'm confused as to why safe mode made it work however, since I haven't installed any third party apps?
zelkov said:
Cheers for reminding me about safe mode; that made it boot up. I'm confused as to why safe mode made it work however, since I haven't installed any third party apps?
Click to expand...
Click to collapse
Safe Mode disables mostly all background running services, widgets and other non-system/user-installed apps. I think it may have to do with widgets or the pre-installed bloatware/crapware.
Have you tried the adb logcat with your phone when booting up without safe mode? I am asking you to do this as it may point out what exactly is causing this error.
By the way, Safe Mode does not seem to exactly disable user installed apps as I was able to open XDA Forums App on my S7 Edge. (Screenshot attached). :laugh:
Sent from my Samsung SM-G935F using XDA Labs
Random04 said:
Safe Mode disables mostly all background running services, widgets and other non-system/user-installed apps. I think it may have to do with widgets or the pre-installed bloatware/crapware.
Have you tried the adb logcat with your phone when booting up without safe mode? I am asking you to do this as it may point out what exactly is causing this error.
By the way, Safe Mode does not seem to exactly disable user installed apps as I was able to open XDA Forums App on my S7 Edge. (Screenshot attached). :laugh:
Sent from my Samsung SM-G935F using XDA Labs
Click to expand...
Click to collapse
After booting in safe mode, it then let me boot normally for some reason. I bypassed the FRP lock again and factory restored the device, it seems to be working perfectly now, still a very strange experience. Thanks for your help!
zelkov said:
After booting in safe mode, it then let me boot normally for some reason. I bypassed the FRP lock again and factory restored the device, it seems to be working perfectly now, still a very strange experience. Thanks for your help!
Click to expand...
Click to collapse
It is probably a mystery that nobody should bother with now! Glad that I could help! :victory::victory::good:
Sent from my Samsung SM-G935F using XDA Labs
Related
Yesterday my phone started acting up. All running process crashed and not many was able to start. I had to constantly click "force close". I think this started after I installed the Google+ app, but not sure.
I have tried uninstalling all unnecessary apps, without luck. I then tried wiping to factory settings by using the Android menu, but without any changing. I then tried by holding vol+ and power, going in to recovery and wiping both to factory and app cache. This doesn't change anything either. By googling I can see some suggests to hold vol- and power, to get to a another wiping-functionality but this just boots my Nexus S to normal state - no menu appears.
Has anybody an idea of what I can do?
Edit: more info; if I click "Report" and investigate the message sent to Google, I see that error has something to do with SQLite-relatet classes. Which makes some sense, alot of my changes are reset each time the phone is rebooted. For instance did I miss a call a couple of hours before the phone went crazy - this is shown at each boot in the notification area eventhough I clear the area and/or goes to missed call section
Factory reset via menu does delete all your "custom" apps, so I'd say it's not one of the existing apps causing problems.
The way you describe function after your factory reset sounds like factory reset didn't work properly.
If you feel safe I'd recommend rather flashing 2.3.4 again using either Odin or the OTA zip from Google (requires open bootloader).
I think you're right that factory reset doesn't do what is expected. Once I click it, the phone reboots and shows the Android guy next to an unwrapping package. This lasts only 2 seconds, then it reboots itself again and goes into normal phone mode (where all the app-crashing starts again).
I have not flashed or rooted my phone before, but I will consider this now since my NS is pretty much a brick. Thank you for your swiftly response.
Edit: Shouldn't I get a menu, when I push and hold vol- button, while turning on the device? Right now it just boot as normal.
Before you use odin....try going into rom manager a reflashing clockwork! Ive had that android dude on my screeen but reflashibg via rom manager always fixed it. Try that
Sent from my Nexus S using XDA Premium App
Wow my Nexus has totally shut me out.
I cannot use ClockworkMod unfortunately since I am not able to root my phone. It is not detectable via USA (when I use vol+/pwr and connect USB). I am unable to check the USB Debugging option on the phone. Each time I check it, go to home-screen and back to the menu, it has de-selected it again. Also I noticed when I read the info that is sent to Google for all those app-crashes I get, I see SQLiteException and error in an SQLite.java file. So it seems like some database layer is broken.
I read one could copy the ClockWork.img to my phone and use the standard recovery option to flash the img (I think). But when I go into the recovery menu, the file is gone. When I boot the phone again, it has deleted the .img file - eventhough if I copy it to several different folders, they are all gone :-(.
I feel pretty screwed at the moment. How can I else wipe all data?
I'd recommend to check if your device is correctly identified in windows. Missing USB drivers might cause problems. Get the latest drivers and a guide from here.
If you succeed booting into fastboot properly (vol up and power) you can follow this guide. Get the latest cwm recovery.img here.
Last option would be to boot into download mode (vol up + vol down + power + plugging in usb cable) and use Odin from samfirmware.com
--
All options require correctly working USB drivers.
I managed to unlock the bootloader, by quickly turning on USB-debugging (before any processes started to crash) and install the drivers from this post:
http://forum.xda-developers.com/showpost.php?p=6819751&postcount=4
A reboot later, I got this message:
"System UIDs Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
Right below was a button saying "Im feeling lucky" (??)
I installed ClockworkMod using fastboot and tried "Fixing permissions" with no luck. I will try some ROM later on, and hope it will bring my phone back
Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.
rentaric said:
Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.
Click to expand...
Click to collapse
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything
DennisRP said:
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything
Click to expand...
Click to collapse
See I'm no expert on this whole thing. At this point I'd just flash a whole new system via Odin. Prolly not the smartest or safest option, but that's what I'd do because I don't know better. If that wouldn't fix it either, I'd return the phone on warranty
I was looking at Odin from the start, since nothing else seemed to be working.
So right now I got started on Odin. Followed the .pdf steps and flashed the bootloader at first succesfully. I was asked to remove the battery and re-connect my NS. Began downloading "pda" and "phone", but at around 10% a big fat red "fail" message appeared and now I just see the Google-logo on startup. I still cant flash any roms via fastboot.
Im too tired too right now, been working with this for 14 hours straight. I will look at it tomorrow evening. Thanks for your help rentaric
Weird, you're not the first one who had trouble running Odin using their guide.
Overall it's pretty simple.
Enter download mode. Vol up vol down and power at the same time while plugging in the USB cable. Start Odin, should show a yellow colored box with a port number. Uncheck everything but reset timer and auto reboot. Unzip the correct zip file from samfirmware.com (check if you got i9020 or i9023 and get the universal Odin exe), apply file from the folder accordingly. Bootloader and bootloader. Phone and modem. Pda and pda. Csc can remain empty (will change carrier info in fastboot).
Double check md5 hash to avoid broken files.
Sent from my Nexus S using XDA App
rentaric said:
Weird, you're not the first one who had trouble running Odin using their guide.
Click to expand...
Click to collapse
Of course I did not go to bed, how should I be able to sleep with a broken phone .
The firmware suggested on samfirmware.com for my phone, was 2.3.3 and some other version (my phone was 2.3.4.2/GRJ22 or something similar, I suspect that might be the cause. Also I unchecked everything, that might also have been of importance). The flash will always fail when everything was downloaded - it then said something about "remote" and "Loke" and then fail. But as I mentioned, I had succesfully flashed boot.img (2.3.3) thus no boot occured now. I googled the correct bootloader, used fastboot and was booting succesfully again.
I began looking more into the sdcard, as error-messages was leading me this way. To compress 4 hours of investigations into a few lines, it seems as my PBA is malfunctioning as other xda-members have experinced. Only solution is sending the phone to Samsung for a PBA replacement. I purchased the phone in Bestbuy USA and the danish Samsung partners are not too joyfull about this - I will contact Samsung and hope they can help me.
I experinced the exact same thing as this poor guy - http://forum.xda-developers.com/showthread.php?t=993403
Every thing you try to do to /sdcard is worthless.
Formatting (USB/using CWM/using adb shell linux commands) says "Succes" but nothing happens.
Copying files says "Succes" but nothing happens. If I boot phone into CWM, mount usb and upload new rom/apk/whatever and try to do a "install update.zip" it fails with some mounting errors.
Im ready to go cry in a corner - I really want this to be fixable via software, but I probably have to realize that this is a hardware issue.
Apparently Samsung doesn't offer worldwide warranty for cellularphones :´(. God it sucks to pay repair-expenses on a 1 month old mobile.
Chrizuki said:
My Relay wont boot into recovery mode. Whenever I hold the Volume-Up + Home + Power, it turns on then it says on the top left corner a small blue colored message saying "RECOVERY BOOTING..." and then it goes to the "Galaxy S Relay from T-Mobile" screen and then black screen. Nothing happens, it doesnt boot into recovery but it can turn on and function well with the OTA Jelly Bean 4.1.2 update as well as boot into Download mode. I have rooted it before when It was still ICS 4.0.4 and I guess I didnt unroot it correctly.
A couple of days ago, I heard about the Jelly Bean update, which I wanted, so I used Kies to update. I connected my phone while in Download mode and Kies did its thing and my phone was unrooted when it booted up and had Jelly Bean. It worked perfectly, but it couldnt boot into recovery mode. I dont think it's a huge problem to not boot into recovery, but to me, I feel safer having it.
Is there a way to fix this using just Samsung Kies? Is there a way to flash that recovery or something using Odin? If so, where can I find it and how do I do it?
Thanks in advance!
Sent from Chrizuki's SGH-T699 in Development using xda app-developers app
Click to expand...
Click to collapse
My Relay wont boot into recovery mode. Whenever I hold the Volume-Up + Home + Power, it turns on then it says on the top left corner a small blue colored message saying "RECOVERY BOOTING..." and then it goes to the "Galaxy S Relay from T-Mobile" screen and then black screen. Then it goes back to the "Galaxy S Relay from T-Mobile" screen followed by black and back again.
My phone is currently NOT rooted. I attempted to root it when I first got it and almost bricked it so when I got it back to working I just left it. I've had my phone over a year and have recently over the past few months had issues with the charging port and batteries even holding a charge. Bought extended life slim batteries and a charger due to that issue. Then just yesterday I was using facebook on my phone and it randomly rebooted and wouldn't stop boot looping. Only way I've stopped it thus far is to take out the battery.
Any help would be greatly appreciated.
Sounds as though your recovery image might be corrupted. I'd utilize ODIN or heimdall to reflash recovery using download mode and see if that fixes your issue. If you were rooted, and feeling adventurous, you could even do so from within the OS. One more question though: Are you releasing the buttons when you see the samsung boot logo with 'RECOVERY BOOTING....' in the corner? If you do not, then the phone will simply reboot again into the OS. Always let the buttons go once the recovery boot process begins.
Magamo said:
Sounds as though your recovery image might be corrupted. I'd utilize ODIN or heimdall to reflash recovery using download mode and see if that fixes your issue. If you were rooted, and feeling adventurous, you could even do so from within the OS. One more question though: Are you releasing the buttons when you see the samsung boot logo with 'RECOVERY BOOTING....' in the corner? If you do not, then the phone will simply reboot again into the OS. Always let the buttons go once the recovery boot process begins.
Click to expand...
Click to collapse
Haven't had much of a chance to try due to distractions plus work along with internet issues at home and a friend's house. I will try ODIN. What is heimdall? I've never heard of that.
Yes, each time I try to reboot into recovery I am releasing the buttons as soon as I see the samsung boot logo with 'RECOVERY BOOTING....'
As always Magamo, Thanks for your help
RockinRita said:
Haven't had much of a chance to try due to distractions plus work along with internet issues at home and a friend's house. I will try ODIN. What is heimdall? I've never heard of that.
Yes, each time I try to reboot into recovery I am releasing the buttons as soon as I see the samsung boot logo with 'RECOVERY BOOTING....'
As always Magamo, Thanks for your help
Click to expand...
Click to collapse
Heimdal is an open source program that implements the ODIN functions. I usually use it as a command line tool, but it does have GUI front ends.
http://glassechidna.com.au/heimdall/
getting frustrated
Magamo said:
Heimdal is an open source program that implements the ODIN functions. I usually use it as a command line tool, but it does have GUI front ends.
http://glassechidna.com.au/heimdall/
Click to expand...
Click to collapse
Magamo, I've downloaded Odin 3. 10..6. Not exactly sure what to do now cos I just tried to put my phone into download mode and it boot loops again! So if I can't go into recovery mode or download mode, what can I do? My phone is not rooted and I don't want to root it. Ideally I want to be able to at least copy some of my text messages before rooting it but how can i do anything if I can't get it to go into recovery mode, download mode, or even turn on without boot looping?!
I dont even know what made it randomly one day decide to shut itself off and boot loop.
Any ideas you (or anyone else has) would be very much appreciated!
-Rita-
Sorry i guess i cant help u on this one. But good luck m8!
So I have a recent issue that I have not seemed to resolve. Today, under normal use, my pixel's screen went black and I have not been able to power it back on. I was using the pixel dust rom when the issue happened. I have booted into twrp and tried to factory reset but the screen even went black during the wipe. After that, I booted into the bootloader and attempted to flash google's factory image. The phone actually stays on during the bootloader session. It seemed that I was able to flash the factory rom but once I tried to reboot, the same thing happens. The boot animation will play but that's as far as it gets until the screen goes black once again.
If anyone has had this issue or if anyone has an idea on how to resolve this issue, please respond quickly.
Much Appreciated!
After the screen goes black, are you still able to communicate with the device over adb/fastboot? Have you tried reflashing the factory image (make sure the checksum is correct!)? If you put the phone in the refrigerator for a bit, will it last longer before going black (i.e., bad solder)?
post-mortem said:
After the screen goes black, are you still able to communicate with the device over adb/fastboot? Have you tried reflashing the factory image (make sure the checksum is correct!)? If you put the phone in the refrigerator for a bit, will it last longer before going black (i.e., bad solder)?
Click to expand...
Click to collapse
So during fastboot, the screen actually doesn't go black. I am still able to remain communication and That is when I tried flashing the factory image. How do you make sure that the checksum is correct? I didn't receive any errors during the flash indicating that it didn't flash properly.
If you're using Windows, Hashtab is a good, free checksum program with a GUI.
Download
Info/Review
On Google's image download page, copy the SHA-256 listed, and compare it to what you have locally (which you used to flash onto your phone).
how to boot into twrp? almost the same issue to you, adb cant find my phone.
jcd173339 said:
So I have a recent issue that I have not seemed to resolve. Today, under normal use, my pixel's screen went black and I have not been able to power it back on. I was using the pixel dust rom when the issue happened. I have booted into twrp and tried to factory reset but the screen even went black during the wipe. After that, I booted into the bootloader and attempted to flash google's factory image. The phone actually stays on during the bootloader session. It seemed that I was able to flash the factory rom but once I tried to reboot, the same thing happens. The boot animation will play but that's as far as it gets until the screen goes black once again.
If anyone has had this issue or if anyone has an idea on how to resolve this issue, please respond quickly.
Much Appreciated!
Click to expand...
Click to collapse
bush911 said:
how to boot into twrp? almost the same issue to you, adb cant find my phone.
Click to expand...
Click to collapse
If adb cant detect your phone, it looks like the only way that you're going to boot into twrp is through the bootloader mode (if you had it previously installed). Holding down volume down and power will get you into bootloader and then using the volume buttons, you can cycle through the options until you find "recovery". Pressing the power button will select that option.
post-mortem said:
After the screen goes black, are you still able to communicate with the device over adb/fastboot? Have you tried reflashing the factory image (make sure the checksum is correct!)? If you put the phone in the refrigerator for a bit, will it last longer before going black (i.e., bad solder)?
Click to expand...
Click to collapse
It looks like your freezer method works. Putting it in the freezer actually gets the phone to boot completely into google's factory image. its usuable for about a minute until the problem of freezing and turning off reoccurs. It feels like the phone warms up while running so maybe i have a hardware problem rather than software.
I seem to have the exact same problem with my pixel 32gb, my device was not rooted, nor did I had any custom recovery but the bootloader was unlocked. The issue happened one day while I was browsing the device went black right infront of me. It was not like I did a dirty flash/mod or something. I'm able to detect my pixel via fastboot, able to flash the factory image no problem, but does not boot up after successful completion of the flashing, it just goes black after "google" logo. Anyone found a solution yet??
thank you sir, I have twrp installed previously. but the screen doesnt turn on so I can't choose the recovery model. and try to hold the power button for a while the phone will become warm. no other response:crying:
jcd173339 said:
If adb cant detect your phone, it looks like the only way that you're going to boot into twrp is through the bootloader mode (if you had it previously installed). Holding down volume down and power will get you into bootloader and then using the volume buttons, you can cycle through the options until you find "recovery". Pressing the power button will select that option.
Click to expand...
Click to collapse
Thufail19 said:
I seem to have the exact same problem with my pixel 32gb, my device was not rooted, nor did I had any custom recovery but the bootloader was unlocked. The issue happened one day while I was browsing the device went black right infront of me. It was not like I did a dirty flash/mod or something. I'm able to detect my pixel via fastboot, able to flash the factory image no problem, but does not boot up after successful completion of the flashing, it just goes black after "google" logo. Anyone found a solution yet??
Click to expand...
Click to collapse
Maybe try locking the bootloader? I might try to do that since you and i both are experiencing the same problem with an unlocked bootloader. But i can't see why that would impact anything.
Hi,
Apologies if this has been asked before, but I've done a relatively thorough search and I can't find a solution to this problem.
I have an S6 (SM-G920F), It was playing up for a few weeks before this, not charging well, and what not, thought it was a cable/hardware issue. Then it stopped working entirely. Initially when it was plugged into the wall it would say it was 91% charged, but if you tried to turn it on it would turn off, and reboot into the charging screen.
I've done quite alot of reading and I've ended up flashing it with Odin (I have a single .md5 file, which i've loaded onto the phone via AP) using the most recent FIrmware UK EE for the SM-G20F. This was successful, however now it only loads the Black screen with white text Samsung S6 powered by android screen and then goes blank and back to the white text screen.
I downloaded an alternative firmware (the one previous version), but this has had the same effect. I've tried to repartition with odin, but this fails.
1.) Is there anyway I can fix this?
2.) If not Is there anyway to remove files whilst in downlod mode?
3.) If I cannot fix it or recover my data, is there anyway to wipe the data securely from my phone so I can sell it for parts?
At present, I can't access recovery mode, only download mode. But whilst Odin communicates with the phone in download mode, I can't seem to access my files from explorer?
1. I would say you'd have to clear cache, immediately after flashing the firmware with Odin, but to do that, you'd have to get to Recovery Mode first...
Why can't you get to it? Does it just start trying to boot nornally? Because if so, it's just a matter of timing it. What I do is... hold power+home+voldown to get to the screen that asks me if I want to get into Download Mode, I press cancel, and immediately start holding power+home+volup until I see the bootsplash screen, and release the power button but keep holding home+volup, and it gets me to Recovery every time, even when I have difficulties such as this.
2. Not that I'm aware of. BUT you could flash TWRP with Odin, and if you then can manage to get to Recovery, you just need to plug your phone into a computer, and your phone will show up in the computer as a device/disk and you can freely remove stuff from it.
If... IF this were to work, I would suggest downloading a stock-based ROM and flashing it. It's far more likely to work properly and bootup without issue than the firmwares you can get, and it's far less much of a headache to do.
3. Nope. There are apps that can wipe data securely (such as Shreddit which does it according to military standards), but it can't be done from Download Mode. There may be some script that could do it in Recovery Mode, but I doubt it.
I mean... technically... you could flash TWRP, go to Recovery, move to your PC all the stuff you want to keep, select the wipe option in TWRP and then transfer randomly generated data from your PC to your phone until it's full - there are many apps that can generate such data. It's not something you could pass off as very very secure, but it should suffice.
I seem to always keep going to trying TWRP - so, you know, give it a shot.
King-V said:
1. I would say you'd have to clear cache, immediately after flashing the firmware with Odin, but to do that, you'd have to get to Recovery Mode first...
Why can't you get to it? Does it just start trying to boot nornally? Because if so, it's just a matter of timing it. What I do is... hold power+home+voldown to get to the screen that asks me if I want to get into Download Mode, I press cancel, and immediately start holding power+home+volup until I see the bootsplash screen, and release the power button but keep holding home+volup, and it gets me to Recovery every time, even when I have difficulties such as this.
2. Not that I'm aware of. BUT you could flash TWRP with Odin, and if you then can manage to get to Recovery, you just need to plug your phone into a computer, and your phone will show up in the computer as a device/disk and you can freely remove stuff from it.
If... IF this were to work, I would suggest downloading a stock-based ROM and flashing it. It's far more likely to work properly and bootup without issue than the firmwares you can get, and it's far less much of a headache to do.
3. Nope. There are apps that can wipe data securely (such as Shreddit which does it according to military standards), but it can't be done from Download Mode. There may be some script that could do it in Recovery Mode, but I doubt it.
I mean... technically... you could flash TWRP, go to Recovery, move to your PC all the stuff you want to keep, select the wipe option in TWRP and then transfer randomly generated data from your PC to your phone until it's full - there are many apps that can generate such data. It's not something you could pass off as very very secure, but it should suffice.
I seem to always keep going to trying TWRP - so, you know, give it a shot.
Click to expand...
Click to collapse
Thanks for your reply! So after flashing it goes straight back into the boot loop. Weirdly if its plugged into my laptop it spend about a second or two on the "Samsung Galaxy S6: Powered by Android" screen before plunging into darkness and shortly after repeating the same message. However if I plug it into the wall it spend over twice as long on that screen before repeating the cycle. It never goes any further.
I've tried your suggestion about perhaps its timing for recovery mode, but even if I go straight from cancelling download mode to trying the power, up and home key it doesn't go to recovery. I've tried a variety of timings both plugged into my laptop and plugged into the wall to no avail. If the phone isn't plugged in, it literally won't do anything whatsoever, won't even hint at turning on.
So Next I tried flashing it with TWRP via Odin and nothings changed, exactly the same bootloop and I still can't get into recovery mode.
I'm starting to think that sadly this phone my be beyond repair! Thanks for your help though, much appreciated.
Hi! I usually run out of my bootloops like this:
try this:
1: go to download mode, and press Power + home + volume —
2: As soon as the screen turns black, continue pressing Power and home, quickly release "volume —" and press "volume +". This will get you into recovery mode.
It always worked for me, so I wish the same for you. Good luck! (And sorry for my bad english)
vinicius_guerra said:
Hi! I usually run out of my bootloops like this:
try this:
1: go to download mode, and press Power + home + volume —
2: As soon as the screen turns black, continue pressing Power and home, quickly release "volume —" and press "volume +". This will get you into recovery mode.
It always worked for me, so I wish the same for you. Good luck! (And sorry for my bad english)
Click to expand...
Click to collapse
Hi Vinicius,
Thanks for the suggestion. Unfortunately it didn't work, I even tried flashing it back to a standard ROM from TWRP, but it still didn't do anything, just back to the Samsung logo and the loop continues ever more!
Hi, I have this problem as well.
Originally I had TWRP and root flashed into my phone but for reasons I needed to remove root.
So I followed the Odin route stated here "Mobikin how to remove root from android" (I can't post links but this should be the top result when googling)
However I didn't know if the recovery/boot should have went into AP or BL on the Odin menu and googling didn't give me any answers so I may have tried both....
Right now I tried flashing TWRP and I can't seem to boot into TWRP as well.
I was able to get into recovery mode but clearing data/cache didn't fix it for me.
EDIT: I managed to flash in another stock rom and it boots into the SAMSUNG logo but gets stuck there. I already went into recovery mode to delete data and cache partition but it still doesn't boot.
Melioetta Zyguard said:
Hi, I have this problem as well.
Originally I had TWRP and root flashed into my phone but for reasons I needed to remove root.
So I followed the Odin route stated here "Mobikin how to remove root from android" (I can't post links but this should be the top result when googling)
However I didn't know if the recovery/boot should have went into AP or BL on the Odin menu and googling didn't give me any answers so I may have tried both....
Right now I tried flashing TWRP and I can't seem to boot into TWRP as well.
I was able to get into recovery mode but clearing data/cache didn't fix it for me.
EDIT: I managed to flash in another stock rom and it boots into the SAMSUNG logo but gets stuck there. I already went into recovery mode to delete data and cache partition but it still doesn't boot.
Click to expand...
Click to collapse
Same experience. For all those 6 years that I used this device, the wifi was okay until now. It (wifi) is very buggy (turning on and off, and sometimes won't turn on at all) so I restarted the device, then bootloop happens. I flashed the stock rom via odin and clear data and cache. But it is still bootlooping. I think this is the sign that I need to replace my phone IF I couldn't find a fix to this.
Hi all,
Im in a desperate and urgent need of help.
My Mrs pixel 7 pro is stuck in a boot loop that restarts 5 seconds after the google writing appears when starting. I wasn't home when it happened but she doesnt really make sure her phone has some battery before turning it on, as soon as she sees 2% she starts it, so im guessing maybe she bricked it while the phone was trying to apply an update when turning it on as she said that the external battery didnt have any juice left inside.
Anyway,
I know i can wipe the phone from recovery mode and make it into a factory reset phone. The issue here is we have over 6000 photos and videos of our son in that phone that she hasnt copied to the external hard drive i gave her for months due to her not liking that her little laptop is slow.
I tried recovery mode Reboot, i tried going into safe mode (no luck as it will go straight into fastboot mode). She doesnt care about a lot of things and obviously she never unlocked the developer setting or bootloader so device state is also locked.
I am begging you, anything any info or advice on how i can get those pictures out of the phone. Is there any way i can flash the stock firmware just to make the phone start and copy them after?
Any possibility or chance or retrieval?
I am willing to pay anyone that can guide me in the right direction as there are over 6 months worth of photos and memories.
Thanks in advance and may the luck be on my side.
andyysk said:
Hi all,
Im in a desperate and urgent need of help.
My Mrs pixel 7 pro is stuck in a boot loop that restarts 5 seconds after the google writing appears when starting. I wasn't home when it happened but she doesnt really make sure her phone has some battery before turning it on, as soon as she sees 2% she starts it, so im guessing maybe she bricked it while the phone was trying to apply an update when turning it on as she said that the external battery didnt have any juice left inside.
Anyway,
I know i can wipe the phone from recovery mode and make it into a factory reset phone. The issue here is we have over 6000 photos and videos of our son in that phone that she hasnt copied to the external hard drive i gave her for months due to her not liking that her little laptop is slow.
I tried recovery mode Reboot, i tried going into safe mode (no luck as it will go straight into fastboot mode). She doesnt care about a lot of things and obviously she never unlocked the developer setting or bootloader so device state is also locked.
I am begging you, anything any info or advice on how i can get those pictures out of the phone. Is there any way i can flash the stock firmware just to make the phone start and copy them after?
Any possibility or chance or retrieval?
I am willing to pay anyone that can guide me in the right direction as there are over 6 months worth of photos and memories.
Thanks in advance and may the luck be on my side.
Click to expand...
Click to collapse
If you can enter recovery mode try to sideload the same exact ota package of the rom she's running, maybe that can help. Good luck!
andyysk said:
Hi all,
Im in a desperate and urgent need of help.
My Mrs pixel 7 pro is stuck in a boot loop that restarts 5 seconds after the google writing appears when starting. I wasn't home when it happened but she doesnt really make sure her phone has some battery before turning it on, as soon as she sees 2% she starts it, so im guessing maybe she bricked it while the phone was trying to apply an update when turning it on as she said that the external battery didnt have any juice left inside.
Anyway,
I know i can wipe the phone from recovery mode and make it into a factory reset phone. The issue here is we have over 6000 photos and videos of our son in that phone that she hasnt copied to the external hard drive i gave her for months due to her not liking that her little laptop is slow.
I tried recovery mode Reboot, i tried going into safe mode (no luck as it will go straight into fastboot mode). She doesnt care about a lot of things and obviously she never unlocked the developer setting or bootloader so device state is also locked.
I am begging you, anything any info or advice on how i can get those pictures out of the phone. Is there any way i can flash the stock firmware just to make the phone start and copy them after?
Any possibility or chance or retrieval?
I am willing to pay anyone that can guide me in the right direction as there are over 6 months worth of photos and memories.
Thanks in advance and may the luck be on my side.
Click to expand...
Click to collapse
As @acuicultor said;
Here's Googles official OTA updates and instructions etc.
From what i've read briefly and as far as i can gather (still running a stock pixel 7 pro - for the first phone in god knows how long, so i'm not well read on this device but...) if you can sideload the latest OTA update via sideload then you should in theory be able to save the data and boot again. But if you flash full firmware then your device will be wiped in the process (if that's even possible with a locked bootloader).
Very best of luck
EDIT: hmm thinking about it, you won't have enabled USB debugging in dev options, hang on, i'll reboot direct to recovery to see if i can get the device recognised without USB debugging enabled. Sorry to be vague (hopefully someone more experienced with this device will chime in with more advice), like i say, i'm not rooted, flashed with custom rom - nothing, just plain old stock so i've not read up much on proceedures for this device. Bare with me!!
Had another thought, do you or have you been using Google photos to view your images on the device. If so, did you enable backup photos online when you first set the app up? If so, they could be backed up automatically...
Edit: my bad..
Try this link
If that fails just Google 'Google photos sign in'
Just tried from recovery to run some adb cmd's, no joy without enabling debugging 1st
There may be hope... If your photos aren't backed online already from above link...
EDIT:
1. From power off state (make sure the device is charged before apply any ota update) Press vol down and power together. As soon as it boots to google logo, let go of vol down, then power. That will put you in fastboot mode where you use the vol up/down to navigate to Recovery mode and power button to select.
2. Then when you have the screen that says 'no command', press power button and CLICK vol up (releasing vol up straight away but keeping power pressed). That'll take you a blue menu at top of screen.
3. Use vol buttons to navigate to 'apply update from adb'. I have checked using 'adb devices' and 'adb reboot sideload' cmd's on PC and the device is now recognised...
Will write further instructions shortly. (no guarantees this will work tho without losing data...or even if it'll work at all - i suspect the OTA update with just fail to transfer)
OR there is another option, using the same instructions above (1) in fastboot mode use the volume buttons to navigate the menu, power button to select Rescue mode. Then contact your service center for support who will advise/offer support - hopefully, which may end up having to send the device in and still offers no guarantee of preserved data
reg66 said:
@acuicultor said;
Here's Googles official OTA updates and instructions etc.
Click to expand...
Click to collapse
Following the link it's all explained there:
- no USB-Debugging needed
- booting recovery by key combo
- no loss of any data when using the OTA files
Also turning on USB-Debugging in developer options is not necessary for the recovery. It's enabled by default and moreover the recovery doesn't consider any system settings like disabled/enabled USB-Debugging.
WoKoschekk said:
Following the link it's all explained there:
- no USB-Debugging needed
- booting recovery by key combo
- no loss of any data when using the OTA files
Also turning on USB-Debugging in developer options is not necessary for the recovery. It's enabled by default and moreover the recovery doesn't consider any system settings like disabled/enabled USB-Debugging.
Click to expand...
Click to collapse
Ahh cool. I obviously didn't read much of it! Dunno what's happened to the chap, maybe his wife has killed him lol
reg66 said:
Ahh cool. I obviously didn't read much of it! Dunno what's happened to the chap, maybe his wife has killed him lol
Click to expand...
Click to collapse
yes, maybe...
FYI: Stock recovery only uses a minimal adbd with a very limited set of commands. That's why some known ADB commands won't work.
minadbd