tried to boot in to recovery and got a screen with a white triangle and a yellow exclamation point inside above an android robot.
the suggestion is to battery pull. anyone else have this issue? if so, what's the procedure on reboot?
thanks.
I think that's the Stock Recovery Menu ( i kept getting it when i was trying to install the Patches from Fresh & used Clockwork Recovery because the two weren't compatible ).
Do you definitely have a Custom Recovery installed?
You pressed the power button instead of the optical trackpad when trying to reboot from custom recovery
Optical trackpad? What Evo has one of those? LMAO!
Flash Clockwork recovery or AmonRa recovery. You have stock (no recovery).
It is hard to answer your question without further specifics.
For example:
1.) Are you rooted?
a.) If yes, what are you trying to boot into recovery for? - flash radio/wimax or rom???
b.) If no, go to Android Development and read how to Root and install a custom recovery.
2.) If you have a custom recovery, what is it?
to put it simpler than this.
1. What ROM do you have?
2. What custom recovery do you have?
3. What step did you do to get into recovery? - from android or from boot up?
*If you pull a battery while trying to flash a radio, you might have the coolest looking paper weight in your part of the town
Hello shawnathan9!
I have similar problem with my Nexus one.
I have a rooted phone (used superoneclick to root)
Installed clockworkmod and flashed it with the recovery image.
Since I wanted to install latest cynogenmod I used clockworkmod to install the latest radio for it. Now when the phone rebooted it is hung diplaying a white triangle with and exclamation mark inside it. I haven't removed my battery yet and have plugged it to a power source. Can you help me ?
You're rooted, but you are trying to access recovery, but you don't have one loaded. Search google for Amon_RA or clockwork recovery to flash. If you have rom manager, you should be able to flash either or and it should work.
I did the unrevolked 3 and got it rooted. Then I booted it up into the recovery mode and ran clockworkmod. Now how do I get a rom (like mikfroyo 4.5) on it? I tried booting and selecting a zip from my sd card(which mikfroyo 4.5 is on it in zip form still) But it would not finish/aborted ? What am I doing wrong? I have the sptint HTC EVO 4 g phone with all the latest hboot ect on it.
charlieborg44 said:
I did the unrevolked 3 and got it rooted. Then I booted it up into the recovery mode and ran clockworkmod. Now how do I get a rom (like mikfroyo 4.5) on it? I tried booting and selecting a zip from my sd card(which mikfroyo 4.5 is on it in zip form still) But it would not finish/aborted ? What am I doing wrong? I have the sptint HTC EVO 4 g phone with all the latest hboot ect on it.
Click to expand...
Click to collapse
It did say no sd-ext found, skipping backup of sd-ext. in Clockworkmod. Still getting the white triangle with the yellow ! in it?
bhaismachine said:
Hello shawnathan9!
I have similar problem with my Nexus one.
I have a rooted phone (used superoneclick to root)
Installed clockworkmod and flashed it with the recovery image.
Since I wanted to install latest cynogenmod I used clockworkmod to install the latest radio for it. Now when the phone rebooted it is hung diplaying a white triangle with and exclamation mark inside it. I haven't removed my battery yet and have plugged it to a power source. Can you help me ?
Click to expand...
Click to collapse
That is part of updating the radio. Just let it finish and it will reboot into recovery. The phone has to go to that screen to update the radio. You may be able to save it by booting into that screen and just let it sit there for a while...eat dinner...take a dump...do whatever and come back and see if your phone is in recovery. I would turn it off and charge it first to make sure you have enough battery to finish the update.
I have the same experience, when I updates to Gingerbread (OTA).
housry23 said:
That is part of updating the radio. Just let it finish and it will reboot into recovery. The phone has to go to that screen to update the radio. You may be able to save it by booting into that screen and just let it sit there for a while...eat dinner...take a dump...do whatever and come back and see if your phone is in recovery. I would turn it off and charge it first to make sure you have enough battery to finish the update.
Click to expand...
Click to collapse
Hello thank you so much for your information. I will leave the phone in that mode (screen hung with triangle an exclamation mark inside + android green logo below) and plug in the charger, until tomorrow morning. Then I have a question if tomorrow the phone still hung in that screen mode, what I have to do?
If you can give me solution, I would be very thankful. Happening in August 23, 2011.
Android_maniac said:
Hello thank you so much for your information. I will leave the phone in that mode (screen hung with triangle an exclamation mark inside + android green logo below) and plug in the charger, until tomorrow morning. Then I have a question if tomorrow the phone still hung in that screen mode, what I have to do?
If you can give me solution, I would be very thankful. Happening in August 23, 2011.
Click to expand...
Click to collapse
After 2 days, trying to download updates firmware (OTA) GingerBread on HTC Evo 4G, I failed because the phone has been rooted, I found a "superuser permision" app. in the the All apps menu.This meant it is a rooted android phone, which will not permitted to update firmware OTA, is this true? If yes, this is the cause of screen hung at triangle with exclamation inside, and android green logo below.
August 26,2011.
Thats what my phone is doing the clockworksmod menu will not come up only see the
white triangle with the exc symbal with the android symbal. have to pull the battery out ot reset but phone still loads up and works.
hi all, my wife has been running cm6.1 and lately it has had a few issues, so i go to download through rom manager, it fails downloading several times, download on a computer and transfer it over, boot into recovery through rom manager(i feel retarded for this one... no back up, didnt wipe) and install, well, it goes to the cm boot animation, sits for a long time, then i remember i didnt wipe so i attempt to get back into recovery and wipe, well, some how, the phone managed to go back to the stock recovery... needless to say i became very very confused...
does anyone have any insight?
thanks in advance
If you havent s-off, then you probably will see stock recovery and need to flash the update.zip to get to clockworkmod. I think i remember that right.
Sent from my T-Mobile myTouch 3G Slide using XDA App
i finally did get cm 7 up and running, and in rom manager it says that i have the latest availible clockwork recovery, but i can only get to it if i rebot to recovery through rom manager, if i go through the boot loader, it takes me to the black screen with the ! in the triangle, then after several button pushes takes me to stock recovery
This happens because ROM Manager reads the altered 'update.zip' from your SD card and it is recommended you use that program (app) to do all your loading and ROM stuff. Though if your phone is powered off you can hold Volume Down and power then after getting to the Triangle "!" screen pressing volume up and power gets you to altered 'update' screen.
hey guys, i've just flashed CyanogenMod 7.0.3 to my device and the wifi turns on, can see wifi networks and accepts my WEP password, however hangs at "Obtaining IP address...", eventually disconnecting and trying all over again.
I was previously running the 7.0 release with no problems and in my newb naivety i failed make a backup of the ROM.
Any suggestions?
EDIT: Now i cant boot into recovery. I just get the bootloader screen (i think? the white one with the skateboarding Androids at the bottom?) and selecting Recovery just sends me back there. This has now gone from an expected easy fix to something thats starting to get me worried. Can anyone help?
Do a full wipe and re-install the rom again, chances are something corrupted the 1st install which does happen apparently.Don't worry too much mate, over the past 2 weeks ive installed and re-installed about a dozen times and on a few occasions been in exactly the same spot your in.
thanks, but no can do. I cant boot into recovery and thus cant wipe and re-install...
Dumb question, you are holding down the volume(down) and power button at the same time to get into recovery mode??
Wow that's weird, try going into ROM Manager and flashing a different version of Recovery.
thanks for the responses guys. Yeah im doing the vol down + power to get to recovery. I cant get further than the white skateboarding Android screen. ROM manager doesnt let me flash new recovery versions because there aren't any.
You can flash a older recovery, scroll to the bottom when in RomManager and select All ClockworkMod Recoveries and try to flash something like 3.0.0.6
Sent from my Desire HD using Tapatalk
yeah when i do that i get "No legacy recoveries found"
EDIT: i turned on my mobile data and now i can choose older recoveries from ROM manager but i still cant boot there regardless of which one i choose
PS can a mod change the title of the thread cos i realize now my problem is more to do with booting into recovery rather than the wifi issues. Thanks
reading around it seems like i need to use fastboot to reflash the recovery.img from my computer. will try it tonight
Hi All,
Got a problem with my HOX. Rooted, and was running Franco kernel and PKMN ROM. Had a few issues so flashed back to stock kernel, wiped and reinstalled ROM.
Now I've got a problem; boots up, get a sense lock screen, then when I unlock I just get a white screen with HTC logo on that doesn't go away.
Help!
I've reflashed stock boot.img in fastboot, I've done a fastboot erase cache and still have same issue.
EDIT:
Well, got it to boot. Going thru setup now and it's INCREDIBLY SLOW. It's like it's underclocked to 100mhz or something. It's completely unusable - hitting "Next" in the Android setup menu takes 30 secs to process etc... This is kind of what was starting to happen before I wiped and reflashed - could it be I have corrupt storage or something?
landwomble said:
Hi All,
Got a problem with my HOX. Rooted, and was running Franco kernel and PKMN ROM. Had a few issues so flashed back to stock kernel, wiped and reinstalled ROM.
Now I've got a problem; boots up, get a sense lock screen, then when I unlock I just get a white screen with HTC logo on that doesn't go away.
Help!
I've reflashed stock boot.img in fastboot, I've done a fastboot erase cache and still have same issue.
EDIT:
Well, got it to boot. Going thru setup now and it's INCREDIBLY SLOW. It's like it's underclocked to 100mhz or something. It's completely unusable - hitting "Next" in the Android setup menu takes 30 secs to process etc... This is kind of what was starting to happen before I wiped and reflashed - could it be I have corrupt storage or something?
Click to expand...
Click to collapse
Did you remember to install kernel modules AFTER you installed your ROM? Roms come with their own kernels and the kernel modules are already installed under /system/lib. So unless you flash the kernel modules after the ROM, ROMs kernel modules get installed instead.
Yes, I did. Got it working now though - not sure what it was but mounted USB storage and got windows to scan the storage - then re-downloaded the ROM and flashed again. Weird....!
Hi folks,
I had my G920P on PB6 base, with TWRP from here; http://forum.xda-developers.com/spr...nt/tool-utility-twrp-3-0-0-1-teamwin-t3335260, and installed TeamSPR 3.6 ROM (http://forum.xda-developers.com/sprint-galaxy-s6/development/teamspr-rom-v3-t3380648). All was running dandy.
Then one day, I flashed @tdhite 's SkyHigh kernel (v3.2, can be grabbed here; http://forum.xda-developers.com/sprint-galaxy-s6/development/kernel-skyhigh-mm-6-0-1-kernel-t3350673). All was smooth.
Then I wanted to revert back to the default kernel that shipped with TeamSPR ROM, so extracted the boot.img from the ROM zip, and used Flashify (got latest from the Play Store) to flash it. This is where things went downhill.
Upon rebooting, and entering recovery, nothing happened. I don't recall what happened at this point (whether I rebooted, or went to flash SkyHigh zip again, because I was panicking?), but upon attempting to reboot, I entered this bootloop from hell, in which the ROM would not get past the "samsung" screen (I am assuming the equivalent of the Sprint LTE screen, since the TeamSPR ROM replaces that with the international screen :good.
In desperation, I booted into recovery, made a nandroid backup, and took out everything I wanted out of the device.
Then, I went here; http://forum.xda-developers.com/spr...ide-links-files-update-root-restore-t3366862/
got the latest (PF4) TAR (yes, MD5 checked out), wiped the phone from TWRP (system/data/cache/internal storage), and ODIN-ed that.
According to ODIN, all went without a hitch.
When the phone rebooted, it went into stock recovery, and it displayed a "applying update" message, followed by "erasing...", and then "applying update". And then, abruptly rebooted itself.
Bootup now went to the Sprint logo, and then "optimizing apps" green/teal screen (it optimizes 32 apps, for whatever it's worth). Almost instantly after the 32nd app is "optimized", the phone reboots again, and this bootloop restarts.
If I broke the loop by going to recovery (still stock recovery at this point), I am greeted again with with "applying update" message, but then I get the dreadful android with an exclamation point sign on top, undoubtedly having failed to apply whatever updated it was trying to do.
Pressing the power button at this stage, gets me to the stock recovery.
Here, I wiped cache, and did a factory reset. Both yielded no different behavior upon reboot from what has been outlined post-ODIN flash.
(I have tried versions 3.10.6 and 3.11.1 of ODIN, by the way - same result).
I got the latest TWRP available (link posted here; http://forum.xda-developers.com/spr...ide-links-files-update-root-restore-t3366862/), wiped system/cache/data/internal storage, and installed TeamSPR ROM (but not their 3.6 OTA). Rebooted the device, but the device goes into bootloop again on the flashing "Samsung" screen, so back to square 1.
At this point, I am not sure what else to try. The phone is a paperweight at this point, and I am really hoping for it not to remain as such.
Ideas?
Thanks in advance!
nostrings said:
Hi folks,
I had my G920P on PB6 base, with TWRP from here; http://forum.xda-developers.com/spr...nt/tool-utility-twrp-3-0-0-1-teamwin-t3335260, and installed TeamSPR 3.6 ROM (http://forum.xda-developers.com/sprint-galaxy-s6/development/teamspr-rom-v3-t3380648). All was running dandy.
Then one day, I flashed @tdhite 's SkyHigh kernel (v3.2, can be grabbed here; http://forum.xda-developers.com/sprint-galaxy-s6/development/kernel-skyhigh-mm-6-0-1-kernel-t3350673). All was smooth.
Then I wanted to revert back to the default kernel that shipped with TeamSPR ROM, so extracted the boot.img from the ROM zip, and used Flashify (got latest from the Play Store) to flash it. This is where things went downhill.
Upon rebooting, and entering recovery, nothing happened. I don't recall what happened at this point (whether I rebooted, or went to flash SkyHigh zip again, because I was panicking?), but upon attempting to reboot, I entered this bootloop from hell, in which the ROM would not get past the "samsung" screen (I am assuming the equivalent of the Sprint LTE screen, since the TeamSPR ROM replaces that with the international screen :good.
In desperation, I booted into recovery, made a nandroid backup, and took out everything I wanted out of the device.
Then, I went here; http://forum.xda-developers.com/spr...ide-links-files-update-root-restore-t3366862/
got the latest (PF4) TAR (yes, MD5 checked out), wiped the phone from TWRP (system/data/cache/internal storage), and ODIN-ed that.
According to ODIN, all went without a hitch.
When the phone rebooted, it went into stock recovery, and it displayed a "applying update" message, followed by "erasing...", and then "applying update". And then, abruptly rebooted itself.
Bootup now went to the Sprint logo, and then "optimizing apps" green/teal screen (it optimizes 32 apps, for whatever it's worth). Almost instantly after the 32nd app is "optimized", the phone reboots again, and this bootloop restarts.
If I broke the loop by going to recovery (still stock recovery at this point), I am greeted again with with "applying update" message, but then I get the dreadful android with an exclamation point sign on top, undoubtedly having failed to apply whatever updated it was trying to do.
Pressing the power button at this stage, gets me to the stock recovery.
Here, I wiped cache, and did a factory reset. Both yielded no different behavior upon reboot from what has been outlined post-ODIN flash.
(I have tried versions 3.10.6 and 3.11.1 of ODIN, by the way - same result).
I got the latest TWRP available (link posted here; http://forum.xda-developers.com/spr...ide-links-files-update-root-restore-t3366862/), wiped system/cache/data/internal storage, and installed TeamSPR ROM (but not their 3.6 OTA). Rebooted the device, but the device goes into bootloop again on the flashing "Samsung" screen, so back to square 1.
At this point, I am not sure what else to try. The phone is a paperweight at this point, and I am really hoping for it not to remain as such.
Ideas?
Thanks in advance!
Click to expand...
Click to collapse
Everything you have said is normal. EXCEPT rebooting after optimizing apps.
What I suggest, is power down phone COMPLETELY via TWRP. Boot phone to download mode. Flash PF4 TAR.
Let it do its thing, including rebooting to recovery to apply the update. But pay close attention!! After it shuts down to reboot to Android, interrupt it and go straight to recovery. Then WIPE data/factory reset from stock recovery.
Then reboot to Android.
nostrings said:
Hi folks,
I had my G920P on PB6 base, with TWRP from here; http://forum.xda-developers.com/spr...nt/tool-utility-twrp-3-0-0-1-teamwin-t3335260, and installed TeamSPR 3.6 ROM (http://forum.xda-developers.com/sprint-galaxy-s6/development/teamspr-rom-v3-t3380648). All was running dandy.
Then one day, I flashed @tdhite 's SkyHigh kernel (v3.2, can be grabbed here; http://forum.xda-developers.com/sprint-galaxy-s6/development/kernel-skyhigh-mm-6-0-1-kernel-t3350673). All was smooth.
Then I wanted to revert back to the default kernel that shipped with TeamSPR ROM, so extracted the boot.img from the ROM zip, and used Flashify (got latest from the Play Store) to flash it. This is where things went downhill.
Upon rebooting, and entering recovery, nothing happened. I don't recall what happened at this point (whether I rebooted, or went to flash SkyHigh zip again, because I was panicking?), but upon attempting to reboot, I entered this bootloop from hell, in which the ROM would not get past the "samsung" screen (I am assuming the equivalent of the Sprint LTE screen, since the TeamSPR ROM replaces that with the international screen :good.
In desperation, I booted into recovery, made a nandroid backup, and took out everything I wanted out of the device.
Then, I went here; http://forum.xda-developers.com/spr...ide-links-files-update-root-restore-t3366862/
got the latest (PF4) TAR (yes, MD5 checked out), wiped the phone from TWRP (system/data/cache/internal storage), and ODIN-ed that.
According to ODIN, all went without a hitch.
When the phone rebooted, it went into stock recovery, and it displayed a "applying update" message, followed by "erasing...", and then "applying update". And then, abruptly rebooted itself.
Bootup now went to the Sprint logo, and then "optimizing apps" green/teal screen (it optimizes 32 apps, for whatever it's worth). Almost instantly after the 32nd app is "optimized", the phone reboots again, and this bootloop restarts.
If I broke the loop by going to recovery (still stock recovery at this point), I am greeted again with with "applying update" message, but then I get the dreadful android with an exclamation point sign on top, undoubtedly having failed to apply whatever updated it was trying to do.
Pressing the power button at this stage, gets me to the stock recovery.
Here, I wiped cache, and did a factory reset. Both yielded no different behavior upon reboot from what has been outlined post-ODIN flash.
(I have tried versions 3.10.6 and 3.11.1 of ODIN, by the way - same result).
I got the latest TWRP available (link posted here; http://forum.xda-developers.com/spr...ide-links-files-update-root-restore-t3366862/), wiped system/cache/data/internal storage, and installed TeamSPR ROM (but not their 3.6 OTA). Rebooted the device, but the device goes into bootloop again on the flashing "Samsung" screen, so back to square 1.
At this point, I am not sure what else to try. The phone is a paperweight at this point, and I am really hoping for it not to remain as such.
Ideas?
Thanks in advance!
Click to expand...
Click to collapse
You have to let it die completely, and when it does die boot into download mode continuously until it wonr anymore (completely dead), and charge until 15% (incase u have to try again). Should b fixed
nostrings said:
Hi folks,
. . .
so extracted the boot.img from the ROM zip, and used Flashify (got latest from the Play Store) to flash it. This is where things went downhill.
. . .
Click to expand...
Click to collapse
The post above (assuming this gets there in time) about killing the battery and restarting is correct (generally).
But what you did was not correct (in the quote). You cannot simply pull a boot image, restore that and presume that's enough. The reason is at boot, before selinux is turned down to permissive (init.d processing usually), your file contexts will likely not be correct. There are many commands in the flash updater-script handlers that fixup the permissions to match the ramdisk used. Additionally, there will probably exist inconsistent init.d handling, or otherwise none at all (i.e., with a stock boot.img).
My Skyhigh kernels generally fixes up the permissions in updater-script, even for ROMs that did not set up their initial files contexts correctly, so things will be smooth as you note. Going back to an improperly formed kernel flash, or just pulling the boot image and forcing it into place is not a good idea in general. Flash the full kernel flash next time so it can do its work. Or ask for help first -- we can get you settled.
Let ur s6 die meaning go to odin mode let it sit for hours until it auto shuts off ..while off plug in cable charge to about 10% plug off cable go into recovery first wipe data and cache n restart ...and wallah ur phone is fixed ...hit like it will help...100% this will work on ur phone
nostrings said:
Hi folks,
I had my G920P on PB6 base, with TWRP from here; http://forum.xda-developers.com/spr...nt/tool-utility-twrp-3-0-0-1-teamwin-t3335260, and installed TeamSPR 3.6 ROM (http://forum.xda-developers.com/sprint-galaxy-s6/development/teamspr-rom-v3-t3380648). All was running dandy.
Then one day, I flashed @tdhite 's SkyHigh kernel (v3.2, can be grabbed here; http://forum.xda-developers.com/sprint-galaxy-s6/development/kernel-skyhigh-mm-6-0-1-kernel-t3350673). All was smooth.
Then I wanted to revert back to the default kernel that shipped with TeamSPR ROM, so extracted the boot.img from the ROM zip, and used Flashify (got latest from the Play Store) to flash it. This is where things went downhill.
Upon rebooting, and entering recovery, nothing happened. I don't recall what happened at this point (whether I rebooted, or went to flash SkyHigh zip again, because I was panicking?), but upon attempting to reboot, I entered this bootloop from hell, in which the ROM would not get past the "samsung" screen (I am assuming the equivalent of the Sprint LTE screen, since the TeamSPR ROM replaces that with the international screen :good.
In desperation, I booted into recovery, made a nandroid backup, and took out everything I wanted out of the device.
Then, I went here; http://forum.xda-developers.com/spr...ide-links-files-update-root-restore-t3366862/
got the latest (PF4) TAR (yes, MD5 checked out), wiped the phone from TWRP (system/data/cache/internal storage), and ODIN-ed that.
According to ODIN, all went without a hitch.
When the phone rebooted, it went into stock recovery, and it displayed a "applying update" message, followed by "erasing...", and then "applying update". And then, abruptly rebooted itself.
Bootup now went to the Sprint logo, and then "optimizing apps" green/teal screen (it optimizes 32 apps, for whatever it's worth). Almost instantly after the 32nd app is "optimized", the phone reboots again, and this bootloop restarts.
If I broke the loop by going to recovery (still stock recovery at this point), I am greeted again with with "applying update" message, but then I get the dreadful android with an exclamation point sign on top, undoubtedly having failed to apply whatever updated it was trying to do.
Pressing the power button at this stage, gets me to the stock recovery.
Here, I wiped cache, and did a factory reset. Both yielded no different behavior upon reboot from what has been outlined post-ODIN flash.
(I have tried versions 3.10.6 and 3.11.1 of ODIN, by the way - same result).
I got the latest TWRP available (link posted here; http://forum.xda-developers.com/spr...ide-links-files-update-root-restore-t3366862/), wiped system/cache/data/internal storage, and installed TeamSPR ROM (but not their 3.6 OTA). Rebooted the device, but the device goes into bootloop again on the flashing "Samsung" screen, so back to square 1.
At this point, I am not sure what else to try. The phone is a paperweight at this point, and I am really hoping for it not to remain as such.
Ideas?
Thanks in advance!
Click to expand...
Click to collapse
Hey bud thats that constant rebooting issue yes it reboots about ten times before it can optimize those apps then if u do get to start up itll still reboot every min right. well let it die completly man die so much it wont turn on at all then plug it in aand turn it on bingo
I'm not sure if anyone mentioned this but there is a Soft Power-Off(basically the same effect as pulling out your battery) on a Samsung Galaxy S6. All you need to do is Hold volume down and the power button.
tdhite said:
The post above (assuming this gets there in time) about killing the battery and restarting is correct (generally).
But what you did was not correct (in the quote). You cannot simply pull a boot image, restore that and presume that's enough. The reason is at boot, before selinux is turned down to permissive (init.d processing usually), your file contexts will likely not be correct. There are many commands in the flash updater-script handlers that fixup the permissions to match the ramdisk used. Additionally, there will probably exist inconsistent init.d handling, or otherwise none at all (i.e., with a stock boot.img).
My Skyhigh kernels generally fixes up the permissions in updater-script, even for ROMs that did not set up their initial files contexts correctly, so things will be smooth as you note. Going back to an improperly formed kernel flash, or just pulling the boot image and forcing it into place is not a good idea in general. Flash the full kernel flash next time so it can do its work. Or ask for help first -- we can get you settled.
Click to expand...
Click to collapse
The letting it die has done it. I am still not sure why it worked, but I am really glad it did. Thank you!!!
RE: writing boot.img into BOOT partition manually. Yeah, not the best idea to go about it (to put it nicely ). My line of thinking was, any file contexts would have been set by the init.d scripts that run as a result of your kernel having been previously flashed. Clearly, I paid for this assumption with an entire day of panic. There's so much I still have to learn about kernel development, and especially for our devices.
Trpling said:
I'm not sure if anyone mentioned this but there is a Soft Power-Off(basically the same effect as pulling out your battery) on a Samsung Galaxy S6. All you need to do is Hold volume down and the power button.
Click to expand...
Click to collapse
I did do that multiple times, to no avail.