Looking for help... - Verizon Samsung Galaxy S6

I have a Verizon Galaxy S6 that keeps rebooting. It will allow me to get to the home screen for about 30-45 seconds before it reboots again. During that very short interval, I was able to turn on developer options in settings. With another reboot, I was able to quickly accept ADB permissions from my laptop. I am getting ready to RMA the device, but first I need to get my pictures off. I tried installing TWRP so that I can do a backup, but the device is NOT rooted, and the DM security will not let me install a new recover image. The phone will stay on forever when in bootloader mode, but fastboot cannot "see" any attached devices. Is there any other way to get to my device's hard drive when this thing won't stay on long enough?
Any advice/suggestions are greatly appreciated.

baddison said:
I have a Verizon Galaxy S6 that keeps rebooting. It will allow me to get to the home screen for about 30-45 seconds before it reboots again. During that very short interval, I was able to turn on developer options in settings. With another reboot, I was able to quickly accept ADB permissions from my laptop. I am getting ready to RMA the device, but first I need to get my pictures off. I tried installing TWRP so that I can do a backup, but the device is NOT rooted, and the DM security will not let me install a new recover image. The phone will stay on forever when in bootloader mode, but fastboot cannot "see" any attached devices. Is there any other way to get to my device's hard drive when this thing won't stay on long enough?
Any advice/suggestions are greatly appreciated.
Click to expand...
Click to collapse
Download the exact same stock firmware you are currently on from Sammobile.com that way you almost eliminate your chances of a bootloop
for your device and flash it in odin in ap /pda slot as long as you don't wipe in recovery or do a nand erase your data should still be there
Sent from my SM-G900V using Tapatalk

[email protected] said:
Download the exact same stock firmware you are currently on from Sammobile.com that way you almost eliminate your chances of a bootloop
for your device and flash it in odin in ap /pda slot as long as you don't wipe in recovery or do a nand erase your data should still be there
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
thanks...will go ahead and give this a try.

baddison said:
thanks...will go ahead and give this a try.
Click to expand...
Click to collapse
did not work...turns out the harddrive is bad. device doesn't even stay on long enough to boot up after the firmware install. even opened it up and swapped out the battery. ended up resetting to factory default, which also did not complete successfully, cause the device keeps rebooting and doesn't stay on long enough for the reset to complete....
thanks anyway.

Related

G955FD Softbricked. OEM Unlock is Disabled.

Help Help Help :
Can I get some help? I bricked my phone because I was trying to install twrp. It flashed but I got TWRP cant install.Because. OEM locked.
It flashed. Great. But now IT STILL DOESNT BOOT. I'm stuck at NO COMMAND, it keeps restarting after 20-30 seconds of showing no command. and it's looping all over.*
i flashed stock firmware.It is flashed.Then reboot.Then install system update.Then Erasing.Then rebooting.Then NO COMMAND.Then reboot itselve recovery mode.Then i wiped factoory and cache.Then press rwboot to system.Then Samsung Galaxy S8 Plus.Then install system update.Erasing.No Command. etc. Keeps rebooting. its on NO command screen. It just restarts. Doesnt boot. I want to enable OEM Unlock. I installed combination binary. But not appear in Developer Mode.
i flash atock with Kies emergency.I flash different stock firmware from updato.com. But nothing happend.
I'm a little confused.
What state is your phone currently in, i.e. can you get into download mode, turn off... what?
JeffDC said:
I'm a little confused.
What state is your phone currently in, i.e. can you get into download mode, turn off... what?
Click to expand...
Click to collapse
KIES says that. (THR) Stock. i downloaded it and flashed with Odin. Then reboot. Then system install update. Then Erasing. Then reboot and No Command! 30 seconds keeps rebooting itself 30 seconds interval Random.
I did factory format, cache clear. then the same problem. i want to install twrp recovery with oden. It says Oem Lock. Not allowed. But i flashed Combinary file. I can get into system and i to developer mode but dosnt seem OEM UNLOCK that ll do enable it.
Ok mate, but if you press Vol- + Bixby + power for couple of seconds, can you access to download mode? If you can, I think you'll have to install the firmware all over again.
Try flashing using latest firmware from sammobile. Use Odin to flash all the files contained in firmware download. Make sure you get latest firmware for your carrier. Google how to flash using Odin. Hope this gets you in the right direction. Good luck finding what u need, do copious amounts of research before attempting any rooting of devices and if all steps aren't clear as day to you then do not attempt it unless you don't mind buying multiple expensive phones to tinker with.
Did OP find a fix to this problem?
I am experiencing a similar issue. Picked my phone up to find had randomly gone into a boot loop. Tried soft reset, cache wipe, factory reset - all successful but the phone would still reboot and be stuck on device model screen. Next I decided to flash the device with stock firmware. The flash passed in Odin, the phone then rebooted, loaded to device model screen, then a screen appeared saying "installing updates" which would make it to 25% then crash. After this the phone keeps booting, shows a screen with a dead android icon and says "no command" or "error". I have tried to flash the device using Oreo and Nougat firmware but have failed every time (although the flash did pass in Odin)
Any help would be greatly appreciated as I would rather not buy a new phone due to a random hardware fault which is out of my control.
southsideswaggar said:
Try flashing using latest firmware from sammobile. Use Odin to flash all the files contained in firmware download. Make sure you get latest firmware for your carrier. Google how to flash using Odin. Hope this gets you in the right direction. Good luck finding what u need, do copious amounts of research before attempting any rooting of devices and if all steps aren't clear as day to you then do not attempt it unless you don't mind buying multiple expensive phones to tinker with.
Click to expand...
Click to collapse
This is perfect if you have soft bricked your phone!
follow this video maybe it help you
https://forum.xda-developers.com/ga...g-aqg5-fix-t3636857/post73032395#post73032395
https://www.youtube.com/watch?v=VTi3uBkpJic&t=155s

Stock Pixel 2 Locking Up on Boot: What are my options?

Hi All,
First, thanks for clicking into my question! This is my first post, but I've been lurking here since I used to flash new roms on my original Nexus on a frequent basis, and a Gen1 Kindle Fire before that.
My fiancee is in a bind with her Pixel 2, so I'm hoping you all can help me out.
Her Pixel 2 threw a bunch of app errors over the course of two days, so she opted to reboot -- unfortunately it now locks up at the loading screen, with the Google 'G' and a loader bar (she's running the latest 8.1, pre-Pie) and hangs there, overheating until the battery runs out and we shut it down. We can get into the Recovery menu, but none of the reboot options there seem to help, and there is only the Factory Reset option remaining that we haven't tried.
This happened in the middle of a huge camping excursion as her Bachelorette, so there was limited WiFi and data access to back anything up -- so locked behind that endless boot sequence is a lot of irreplaceable images and video.
What are my options to pull the user data out of there before a factory reset? Is it possible on a (stock, non-root, Google sourced) phone to flash the Pie update? Would that restore functionality?
Can I get to the data somehow through ADB without the phone booting up and unlocked?
Maybe something crazy, like a take a full image of the phone that I then shove on the replacement Pixel 2 that Google is sending us?
Any guidance would be much appreciated!
You could try booting to TWRP with "fastboot boot <filename here>". Then copy the files from there. I'm not sure if this will work if she had the screen locked beforehand though. You could also try flashing the latest factory image but make sure your remove the "-w" from the flash-all.bat file before running the script so it will not wipe user data. Both of these options might not be possible though if you do not have the boot-loader unlocked.
cynnican said:
Hi All,
First, thanks for clicking into my question! This is my first post, but I've been lurking here since I used to flash new roms on my original Nexus on a frequent basis, and a Gen1 Kindle Fire before that.
My fiancee is in a bind with her Pixel 2, so I'm hoping you all can help me out.
Her Pixel 2 threw a bunch of app errors over the course of two days, so she opted to reboot -- unfortunately it now locks up at the loading screen, with the Google 'G' and a loader bar (she's running the latest 8.1, pre-Pie) and hangs there, overheating until the battery runs out and we shut it down. We can get into the Recovery menu, but none of the reboot options there seem to help, and there is only the Factory Reset option remaining that we haven't tried.
This happened in the middle of a huge camping excursion as her Bachelorette, so there was limited WiFi and data access to back anything up -- so locked behind that endless boot sequence is a lot of irreplaceable images and video.
What are my options to pull the user data out of there before a factory reset? Is it possible on a (stock, non-root, Google sourced) phone to flash the Pie update? Would that restore functionality?
Can I get to the data somehow through ADB without the phone booting up and unlocked?
Maybe something crazy, like a take a full image of the phone that I then shove on the replacement Pixel 2 that Google is sending us?
Any guidance would be much appreciated!
Click to expand...
Click to collapse
ADB sideload the latest OTA zip in stock recovery, that should get you up and running again without needing a wipe
crixley said:
ADB sideload the latest OTA zip in stock recovery, that should get you up and running again without needing a wipe
Click to expand...
Click to collapse
Thank you! I'll be giving this a try as soon as she's home on Monday.
Does recovery mode automatically enable the USB Debugging that ADB uses?
cynnican said:
Thank you! I'll be giving this a try as soon as she's home on Monday.
Does recovery mode automatically enable the USB Debugging that ADB uses?
Click to expand...
Click to collapse
Yep you can sideload without needing it toggled in developer mode
crixley said:
Yep you can sideload without needing it toggled in developer mode
Click to expand...
Click to collapse
This worked perfectly, thank you!
cynnican said:
This worked perfectly, thank you!
Click to expand...
Click to collapse
I'm glad to hear! Nothing worse than having to wipe and losing important things you can't get back. I've had that happen a few times. Happy to help.
I'm not very technical - please keep this in mind with my query below.
I have a Pixel 2 which overnight stopped working - my guess is that it rebooted due to an automated software update.
I now only get the page with the robot on it's back.
Options in green on this page are Barcodes, Power Off, and Start.
After reading a lot online I've tried all the usual key press combinations to no avail.
I've also downloaded ADB and FASTBOOT to my Mac.
ADB doesn't see the phone when plugged in via USB (ie. ADB DEVICES doesn't return anything)
FASTBOOT DEVICES does, however, show the serial number as listed on the page with the robot on it's back (and the -l option adds "usb:" plus an 8 digit number and the letter "X"
FASTBOOT REBOOT restarts the phone and brings me back to the robot on it's back page.
Other information on the Robot on it's back page include -
Product Revision: walleye MP1
Boot-slot: b
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: locked
Advice online suggests I need to unlock the phone, so I've tried FASTBOOT FLASHING UNLOCK, and FASTBOOT OEM UNLOCK but neither work.
When I try these I get "FAILED (remote: Flashing Unlock is not allowed)"
An article on Android Police suggests this may have been a bug on the Pixel 2 originally and that it's now resolved.
Unfortunately, my cat 22 situation seems to be that I need to do a factory reset, but the steps I've found as to how to do a factory reset all lead back to the Robot on it's back page, so I can't see how to move forward to with recovering my phone?
Can anyone help please?
Really frustrated that my new phone can put itself into this state without me having done anything and that it's seemingly impossible to recover from this state now that it's in it.
At very least I'd like to wipe all data from the phone so I can send it off for repair.
Thanks in advance.

S10e Literally stuck in bootloops after 2020 Update

So i updated my phone automatically yesterday from the latest update, after it was done, i haven't been able to access my phone in anyway, it keeps on looping samsung logo and a window that says "This phone's bootloader is unlocked´and its software integrity can't be verified" and so on, ive tried to enter either Download mode and recovery mode, but none of the methods seems to have an affect on the phone at all, please help, thanks
Hmm if u have PC download Smart Switch and do Emergency Firmware recovery. That should fix it totally.
FakerS3 said:
Hmm if u have PC download Smart Switch and do Emergency Firmware recovery. That should fix it totally.
Click to expand...
Click to collapse
- The phone does not show up on the pc either
Was your phone rooted? That could explain it.
riggerman0421 said:
Was your phone rooted? That could explain it.
Click to expand...
Click to collapse
Yes
thorius95 said:
Yes
Click to expand...
Click to collapse
Same issue here. s10e stuck in boot loop (between samsung logo and warning about the bootloader being unlocked) after yesterday's update.
So far I had no success putting the phone into recovery or download mode.
The phone was rooted, then flashed with custom ROM, then flashed again with stock firmware. I kept the bootloader unlocked because I read it was risky to re-lock the bootloader.
So, is it now hopelessly bricked?
chibuche said:
Same issue here. s10e stuck in boot loop (between samsung logo and warning about the bootloader being unlocked) after yesterday's update.
So far I had no success putting the phone into recovery or download mode.
The phone was rooted, then flashed with custom ROM, then flashed again with stock firmware. I kept the bootloader unlocked because I read it was risky to re-lock the bootloader.
So, is it now hopelessly bricked?
Click to expand...
Click to collapse
Thats a good question, far as i know, my phone is unable to get any form of connection to the pc, not able to start up in recovery or download mode either. What i know for sure, there is a way out, we just have to find the way
Never attempt to update if you have rooted and made any changes to the system, deleted or added system apps, modified kernel, changed boot logo,etc.
thorius95 said:
Thats a good question, far as i know, my phone is unable to get any form of connection to the pc, not able to start up in recovery or download mode either. What i know for sure, there is a way out, we just have to find the way
Click to expand...
Click to collapse
So, here's how I put the phone in download mode.
I left the battery to drain completely, then without pressing the power button, I pressed the volume down and Bixby button; and only then I plugged the cable. Without pressing the power button, the phone started straight into Download mode.
Now Odin sees the phone, I'm about to flash it with the stock firmware and see what happens.
thorius95 said:
Thats a good question, far as i know, my phone is unable to get any form of connection to the pc, not able to start up in recovery or download mode either. What i know for sure, there is a way out, we just have to find the way
Click to expand...
Click to collapse
Maybe this thread helps: https://forum.xda-developers.com/galaxy-s10/help/galaxy-s10-bootloop-updte-to-android-10-t4023201
It's probably Samsung's vaultkeeper that caused the bootloop.
thorius95 said:
Thats a good question, far as i know, my phone is unable to get any form of connection to the pc, not able to start up in recovery or download mode either. What i know for sure, there is a way out, we just have to find the way
Click to expand...
Click to collapse
I just wanted to give an update of how I rescued my phone and kept all the information on the phone memory intact (this was one of the challenges, as I had some photos on it).
I put it in download mode by draining the battery, then tried to flash the updated firmware. It didn't work, leading once again to boot loop and all I could do was boot to the stock Android recovery - not helpful.
So I got it to download mode again and flashed the stock firmware it originally came with (prior to the update). In Odin, I put HOME_CSC in the CSC field, to keep the phone memory from being erased. This solved it.
Hope this info can help someone having the same issue.

Issue with Samsung Note 8 SM-950F

Hi all! I have exhausted every avenue I can think of, with now hitting a roadblock attempting to repartition the device.
I took this phone to get its physical structure repaired as well as the screen. It took them 6 hours. When I got the phone back they said the "software crashed" and that they attempted firmware flashes to no avail.
The phone is in a constant Boot Loop. It will sit on the Samsung splash screen for a minute, go to a blue screen which tells me it is installing a system update, then an Android figure comes up saying Error. It does this over and over again. I hit the power and volume up key to quickly look at the commands it was throwing out and saw it was unable to access certain directories which I assume is the reason for the failure.
So I reflashed this phone with my relevant firmware using Odin. No firmware or combination of files and methods has brought this phone back.
I was hoping for some help with this project. I want to resurrect this phone, it's a great phone. I would love the satisfaction of doing it myself than at a store.
lexlex121 said:
Hi all! I have exhausted every avenue I can think of, with now hitting a roadblock attempting to repartition the device.
I took this phone to get its physical structure repaired as well as the screen. It took them 6 hours. When I got the phone back they said the "software crashed" and that they attempted firmware flashes to no avail.
The phone is in a constant Boot Loop. It will sit on the Samsung splash screen for a minute, go to a blue screen which tells me it is installing a system update, then an Android figure comes up saying Error. It does this over and over again. I hit the power and volume up key to quickly look at the commands it was throwing out and saw it was unable to access certain directories which I assume is the reason for the failure.
So I reflashed this phone with my relevant firmware using Odin. No firmware or combination of files and methods has brought this phone back.
I was hoping for some help with this project. I want to resurrect this phone, it's a great phone. I would love the satisfaction of doing it myself than at a store.
Click to expand...
Click to collapse
Sometimes after flashing via Odin, it is necessary to boot into stock recovery and factory reset then wipe cache partition then reboot. This doesn't always solve bootloop after flashing via Odin but it is a common solution.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Sometimes after flashing via Odin, it is necessary to boot into stock recovery and factory reset then wipe cache partition then reboot. This doesn't always solve bootloop after flashing via Odin but it is a common solution.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I don't understand how to get into recovery mode. The phone, when the charger plugs in, attempts to boot all the time.
I know the Recovery mode key combo but I have no idea to power off this phone. I've let the battery run.

Question HELP PHONE STUCK ON BOOTLOOP AT GOOGLE WRITING AND CANT GET DATA OUT

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

Categories

Resources