Develop Bugs

[Q][Solved] Stuck on boot animation! How to get in bootloader?

I had just flashed the BlackICE ROM and started to like that, except from that it sometimes froze. So I read the BlackICE forum and saw that there were a few others with the same problem, and they got tipsed about undervolting with the built-in undervolting menu. So I did so too, and it worked about 1 hour. Then it froze again and won't come pass the bootanimation.
Normally i would press power and vol down button, but my vol down button has it own life, and won't function when I want to. So i can't get into the bootloader and reflash or wipe data.
Any helpful tip? Any other key kombination, or maybe i can access it from my computer when plugged inn with USB?
Thanks!

Sorry to hear about your problem.
Try this,
Download this simple adb package --> HERE & extract
Remove & reinsert your battery
Plug into your PC and wait for the orange charging LED to light up
Using cmd navigate to the folder you unzipped adb to
e.g
Code:
cd C:\adb
Now try this command
Code:
adb reboot bootloader
Hopefully that should restart your device into bootloader, from there you can select recovery.

Thank you very much for your answer, but I don't see any link? It seemed like you wanted to post a link?
EDIT: Is it this package maybe? 34MB?
Link: http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/

Ahh yes, I forgot the adb package.
I've added it to the original post. It's only 200~KB.

It worked! But are there any adb command to enter recovery from bootloader? Since my volume buttons don't wanna cooperate I am not able to get down to "Recovery" atm. I tried volume up, and it worked for one selection, so now it stands on the bottom.
Thanks again btw

I thought it would, you can try,
Code:
adb reboot recovery
You may need to pull your battery & start again.

I tried that and then I just got a long list of commands that I could try out. I then found
Code:
adb reboot [bootloader:recovery]
That did not work either, so I just tried rebooting into bootloader again, and now the volume up button would work long enough to select recovery! So now I have reflashed and things seem to be working again
So thank you again, for saving my phone

possibly bricked??
I have tried the steps above and am getting "Error: Device not found" I am assuming this means that the usb debugging has somehow been switched off?
Complete newbie please excuse me (I have got my phone stuck at the htc screen and volume down button seems to have died on me)!

[Q] Tried to install Beatmod ICS, stuck on "screensaver" usb and recovery won't work

[Q] Tried to install Beatmod ICS, stuck on "screensaver" usb and recovery won't work
Hi guys,
I've watched the n00b video and been googling for the last few hours as well as reading through various pages on the XDA forum. I've found a lot of problems that are kinda similar and tried various solutions but don't seem to be quite getting there.
Basically I had Virtuous Affinity as the OS and clockworkmod installed (should be the most up to date versions of both, they were put on no more than a week ago) as well. I also had a backup of current OS and so on on the SD card, as well as the original zip of the rom.
I decide I want to give ICS a go and so I downloaded the betamod ICS and then loaded it. It asked me if I wanted to do a dalvik cache wipe, a dalvik cache + data wipe and a third option I don't recall. I went with the dalvik cache wipe (at the time I was under the impression that was the correct course of action) then put it back in my pocket while ICS installed.
I get my phone out of my pocket later and it's kinda stuck on what looks like (but logically isn't, I'm guessing it was meant to be a splash screen type thing while ICS installed or some such) a screensaver which just loops endlessly. The only thing you can really do is take the battery out and turn her on again, in which case you once again end up in the endless screensaver loop.
I've tried booting to recovery using volume - and the power button and unfortunately it just boots straight into the looping screensaver again.
Getting a bit worried and feeling adventurous I tried seeing what I could do with ADB, however the computer seemed unable to recognise that any device was connected with ADB devices not listing anything.
I've read up a lot and I'm at a loss as to what to do - there's a rom on the SD card and there also should have been a backup but I just can't get it into recovery.
I do have the ability to view the SD card on another device and interact with it, so if there's a potential SD fix, that's certainly not out the window.
But yeah, I'm clueless how to proceed here and very green at the whole rom business. Can anyone advise what I might try to do from here? I don't care what state I end up going back to, or if I lose my data, I can get all that back, I just want the phone in some semblance of basic operation.
I'll be keeping an eye on the thread, if I've left out any pertinent data ask away and thanks in advance for anyone with a clue how I can fix this mess .
EDIT: Post may be better off in ICS thread above and I do apologise if so, I would move it but I seem unable to delete it.

Remove battery for 5 seconds and then try again to boot into recovery using volume -and power button.

ik222 said:
Remove battery for 5 seconds and then try again to boot into recovery using volume -and power button.
Click to expand...
Click to collapse
I have, it doesn't work. I've left the battery out for a fairly long period. Volume - + power still just brings it back to the "screensaver" loop.
Thanks for the suggestion though.

Turn the phone off completely; pull the battery out for a bit then replace it and don't touch anything. Don't try to turn it on. Plug the phone by usb to your pc (still turned off). At the command prompt in the folder containing adb.exe type "adb reboot recovery" - the phone should power on and go to recovery where you can wipe properly and reflash whatever you want.
You should be able to boot to recovery using the volume down + power button combo (hold the volume-down key, then press and hold the power button and keep both held until you get to the bootloader menu); the only thing that's wrong with your phone is that you've flashed one ROM over another without wiping it first, so the ROM can't load but this shouldn't affect your bootloader or recovery.
Worst case you can flash a RUU which will restore it to the official firmware; you'll then need to re-root and re-install a recovery image to be able to flash custom ROMs again.

Very helpful post, thanks! I'll try all that and see how I go, I'll post if I still have trouble.
Yeah I dunno why I can't boot to recovery it's weird. The volume button wasn't working, so I removed it and am pressing in the volume down portion of the volume button with a pen while holding down the power button. It's possible perhaps I'm not successfully depressing volume down, but I'm 99% sure I am and that that's not it. I am however doing it as you and other guides advise, depress volume down, hold it and then depress power and hold both for about three seconds, no joy!
Anyway, as said, I'll try what you're recommending and see how I go. Thanks!

hopscotchjunkie said:
At the command prompt in the folder containing adb.exe type "adb reboot recovery"
Click to expand...
Click to collapse
Curious what you mean by this? Cause there's no command prompt in the folder ADB is in. Do you mean in command prompt, be in the folder, i.e. c:\abd kinda thing? I tried just loading command prompt and typing abd reboot recovery, no device detected - no joy.

Ethicistabdiel said:
Curious what you mean by this? Cause there's no command prompt in the folder ADB is in. Do you mean in command prompt, be in the folder, i.e. c:\abd kinda thing? I tried just loading command prompt and typing abd reboot recovery, no device detected - no joy.
Click to expand...
Click to collapse
Yeah that was what I meant; I've got a feeling that that only works when the phone is powered off if you had USB debugging activated on the phone beforehand, so if that's not working that might be why.

c:\adb
results in error: device not found.
ADB app itself is in C:\adb\platform-tools but when I try that it goes The System cannot find the path specified. I've tried cd/adb and I can get that far but I can't get to adb/platform-tools.
EDIT:
Okay, I managed to get to c:\adb\platform-tools but adb reboot recovery is still advising error: device not found. Guessing perhaps I didn't have usb debugging enabled. Are you able to suggest another work around at all? I'm happy to flash it to whatever, I don't mind losing data, just want to get it in working order again. I don't see how I can though when I seemingly don't have access to recovery or USB...hrmm, must be some way around.

Accidental double post, sorry.

You need to try get into recovery mode, where you can do a full wipe and see if that fixes anything.
Firstly, remove your battery then re-install it, your phone should still be turned off at this stage. Press and hold the volume down button, then additionally press and hold the power butter, until something appears on the screen. If the bootloader appears, you can then boot into recovery from there.
If the above fails to work, report back with your results and hopefully something else will be suggested.

Ethicistabdiel said:
c:\adb
results in error: device not found.
ADB app itself is in C:\adb\platform-tools but when I try that it goes The System cannot find the path specified. I've tried cd/adb and I can get that far but I can't get to adb/platform-tools.
EDIT:
Okay, I managed to get to c:\adb\platform-tools but adb reboot recovery is still advising error: device not found. Guessing perhaps I didn't have usb debugging enabled. Are you able to suggest another work around at all? I'm happy to flash it to whatever, I don't mind losing data, just want to get it in working order again. I don't see how I can though when I seemingly don't have access to recovery or USB...hrmm, must be some way around.
Click to expand...
Click to collapse
Your only other option to get into recovery is the volume-down/power-on combination. Like I said, I can't think why that's not working unless it's related to your missing volume button (maybe it's not maintaining a constant pressure on the button when you're using whatever to press through the hole).
If you still can't get that to work, I would suggest finding a stock RUU and flashing that. It's an .exe file that runs from your PC and will return your ROM, bootloader and radio back to stock. Obviously that means you'll lose root and your custom recovery so you'll need to do all that again from scratch. There's a sticky in the dev section with a link to a thread with various RUUs (it's named something along the lines of "shipped & test ROMs" - I'll check that and link to it once I've dragged myself out of bed to the computer). You'll lose all your data, but if you took a backup beforehand you can restore that once you're back up and running.
//sent from my Desire HD using Tapatalk; all errors entirely intentional.

Yeah I'm starting to think perhaps the down button is just broken.
What state should the phone be for the RUU, turned off with usb plugged in or turned on? Bearing in mind, that when on, all it will do is the "screensaver". Will it work in either of those states?
Thanks, will deffo research more when I get home. Appreciate the help immensely.

http://forum.xda-developers.com/showthread.php?t=824357&page=5
Guessing you mean that as far as the ruu thread. Am downloading a stock rom atm, with shaped internet till tomorrow, meh! Will see how I go. Have a feeling phone was probably Vodafone branded at stock though, so that could make for extra fiddling but yeah, fingers crossed.

If you are able too install a stock-rom you can work from their than install 4EXT recovery
touch than you doen't need the volume buttons.

I downloaded the most recent stock rom on the link above. When I try to install it though, phone off or on, it advises a USB connection error. Is this likely to be because I originally had vodafone stock and need to make a gold card, or should it still at least be recognising it? It does advise not to run any programs on the phone or anything when while installing the update, but of course, as long as my phones turned on it's stuck on the damned screensaver loop.

http://forum.xda-developers.com/archive/index.php/t-841890.html
Gonna give that a go, fingers crossed!
D'oh, just found out my mobile was Three at stock and not Vodafone, the search continues .

Gah, I'm about tearing my hair out here, I want my damned phone back . Stuck using a $79 Huwawei Vodafone thing at the moment and it's so so so awful.
Anyway. I was under the impression that making a goldcard would mean I could RUU a non-Three stock rom on the phone. I made a goldcard following these instructions; http://www.addictivetips.com/mobile/how-to-make-gold-card-for-htc-desire-hd/
Then I turned the phone on as the RUU advises, (meaning it's scrolling through the feckin' "screensaver") and start the process and once again get a USB connection error.
What's the better process at this stage, try and take it back to Three stock? I don't see how I can at the moment, the only Three stock I can find seems to be rom, not RUU, meaning I'd need to load from the phone, which I can't due to no recovery. Or should I keep trying to get the goldcard thing to work, maybe try some different RUU's or something?
I'm open to any other suggestions as well. Had a bit more of a fiddle around with my volume down button, no matter what I do though, I can't get recovery mode. Always boots first to the white HTC screen and then starts the infernal "screensaver" loop.

Ethicistabdiel said:
Yeah I'm starting to think perhaps the down button is just broken.
What state should the phone be for the RUU, turned off with usb plugged in or turned on? Bearing in mind, that when on, all it will do is the "screensaver". Will it work in either of those states?
Thanks, will deffo research more when I get home. Appreciate the help immensely.
Click to expand...
Click to collapse
How come the volume down button be broken. When you were using Affinity Rom weren't you able to use your volume button for music. Remove SD card from phone then press "First - Volume down gently for 2 sec" & press-hold power button when it goes into bootload place your sd card back select option "REBOOT RECOVERY". I think your panicking too much just be patient nothing is wrong, i think your just hurrying it up...

The volume button didn't work before either. I had to manually adjust volume from settings. I thought it was just because of the dodgy plastic button on top, but using a pen to depress the button underneath doesn't work either.
Believe me, I've been trying to fix this for days now, every different way of depressing volume down in order to get to recovery has not worked. Short of taking the phone apart and seeing if I can see what's wrong with the button (doubtful with my level of expertise) then it ain't happening via that method.
Got a little bit hopeful with this;
http://www.htcdev.com/bootloader/ruu-downloads
But that too requires my phone to be in usb debugging mode, which of course, it isn't.
Is there anyway to force the phone into usb debugging mode using some form of hack or some such? The thing is, it is powered and everything, I can turn it on, the screen works and all that jazz and indeed the phone will charge from USB and the computer makes a noise when I plug or unplug it, the phone itself however won't do anything other than the "screensaver" ICS installation loop. I guess I'm thinking where there's life there's hope and perhaps there's some way in that state I can get it to switch debugging on, though I think I'm reaching at this point .

Ethicistabdiel said:
The volume button didn't work before either. I had to manually adjust volume from settings. I thought it was just because of the dodgy plastic button on top, but using a pen to depress the button underneath doesn't work either.
Believe me, I've been trying to fix this for days now, every different way of depressing volume down in order to get to recovery has not worked. Short of taking the phone apart and seeing if I can see what's wrong with the button (doubtful with my level of expertise) then it ain't happening via that method.
Got a little bit hopeful with this;
http://www.htcdev.com/bootloader/ruu-downloads
But that too requires my phone to be in usb debugging mode, which of course, it isn't.
Is there anyway to force the phone into usb debugging mode using some form of hack or some such? The thing is, it is powered and everything, I can turn it on, the screen works and all that jazz and indeed the phone will charge from USB and the computer makes a noise when I plug or unplug it, the phone itself however won't do anything other than the "screensaver" ICS installation loop. I guess I'm thinking where there's life there's hope and perhaps there's some way in that state I can get it to switch debugging on, though I think I'm reaching at this point .
Click to expand...
Click to collapse
The only option i can think of is "Fix your volume button from your nearest Service centre". Without that you cant do anything. I am Sorry....

[Q] Help! Accidentally deleted system and can't restore or install

Coming from a phone with microSD extension, I had never encountered such an issue:
I bought this phone with a stock 4.2 Rom installed and tried to install a custom Rom. I first installed the latest version of touch recovery (tried it and it seemed to work fine) and did a backup using the default settings. Then I erroneously chose to format system and data, thinking that I could then "install from zip". Strangely, these steps deleted everything in the /sdcard directory and I couldnt select "external SD" (because the phone isnt equipped with it anyways?). Then I made a second mistake and restarted the phone, despite the message warning that I no longer had an OS installed. I took the battery out, and then held the power down while pressing the power button. The phone couldn't get into recovery, but instead showed a screen with the android logo, a large "Start" sign above it, and "Downloading...", "Do not turn off target !!" below it. Pressing the power button now got the phone to show just "Google" and a lock logo under it. The PC (windows 7) can not detect the phone throughout the process.
I tried the latest tool kit and samsung's USB driver but couldnt get the phone recognized by the PC.
Does this mean that the phone is doomed???
Please help!!!
Trent

Relax, it's not easy to 'doom' your Nexus. Especially with all the hard-workers in XDA
Try accessing Recovery mode by holding down BOTH vol up + vol down, as well as power. Holding just vol down + power is 'Download Mode', and at the least you can get to this. Means your phones far from doomed

Thanks a lot for the reply!
As a matter of fact, I also figured out how to get back to recovery (if only I had read your post earlier, my pain would've been much less!). But the problem remains that I can not get a target ROM onto the phone, since: 1. whatever I did seemed to have gotten rid of the nand backup supposedly stored in /data/media/TWRP/BACKUPS/ (I'm using TWRP V. 2.3.2.1). 2. I can not get my PC(or Mac, for that matter) to recognize the phone or the internal storage.
Any pointer from here?
Thanks again!!!
Trent

You can download a factory image and install with fastboot. It's quite easy and instructions are readily available on this forum. You can then install a custom ROM afterwards if stock is not your thing.

Found the answer finally!
It's the adb push method. Basically, it's to install adb drivers and execute a few commands via the command window. Not too bad... Don't know much about fastboot yet though ... If anyone else needs more details, please PM me (to save public bandwidth).
Thanks a lot anyways, whpnhp and jocalderone!!!
Trent

m8 stuck in hboot and safe mode - fastboot not working but managed to get adb to reco

hi guys im having a problem here and would greatly appreciate some help. I have already installed android platform tools and the htc usb drivers. The phone will start in hboot only but will not go to fastboot (power button will not activate fastboot). The pc does not recognize the device either so cant use fastboot commands. Power button + vol up will boot to safe mode but then the os starts acting crazy with the touchscreen being activated all over the place (very annoying). while in safe mode, adb devices command shows that it recognizes the phone but also says unauthorized. What the heck can i do here to get this phone operational again?

What is the history of the device? Was it broken when you got it? Was there any problem with the power button before it started having these problems (only boots to bootloader or safe mode)?

Hey thanks for replying. I got the device new from att around 4 or 5 years ago and have had no problems out of it aside from a badly cracked screen which i replaced myself about 8 months ago. All of the buttons have always worked just fine.
I forgot to mention I unlocked the phone through htc website about 3 years ago and planned on rooting and modding the phone but never got around to it. I can't quite remember if I flashed a custom recovery though. I should also mention the phone got wet before all this started happening (not submerged kind of wet just rained on some )
So I'm assuming ADB sees the device as unauthorized because I'm unable to select OK when the debugging window pops up on the phone. This is due to the OK button being in a dead zone on the touch screen. This zone is the middle half of the screen top to bottom. I'm hoping it's just corrupted firmware and not a physical hardware issue as I mentioned earlier I have already replaced the screen once already.
As for fastboot not recognizing the device, I'm starting to think it's because of this older mini laptop I'm having to use as a backup because my good laptop is being loaned out to someone for a while longer. This mini laptop has 3 usb ports on it but all I believe are usb 1.1 (LOL!). Does fastboot require usb 2.0 or higher to work properly? The phone is visible in Device Manager (both internal and external storage), and I'm able to move files around no problem.
Also, does the sim card have to be in the phone in order to fix the firmware and os? I have the sim in a very basic flip phone right now just so I can make and recieve calls! I need my M8 back badly!
I'm assuming since the phone will actually get to hboot and will also boot into safe mode that this phone is recoverable ie. not bricked. I just need help with doing everything in the right order , so I dont end up doing something very wrong and rendering the device useless. Again thanks for replying and any help you might be able to give would be greatly appreciated!

My responses below in red font:
brokenm8 said:
I should also mention the phone got wet before all this started happening (not submerged kind of wet just rained on some )
Not clear on what you are telling us here. Are you saying that the current condition (stuck in hboot/safe mode) happen directly after it getting wet? Is so, then it would be pretty clear to me, that it is a hardware issue caused by water damage.
So I'm assuming ADB sees the device as unauthorized because I'm unable to select OK when the debugging window pops up on the phone.
You need debugging selected in phone Settings>Developer Options, as well as being able to "OK" the debugging connection request when you are connected to PC. Failing to do either of those, will prevent adb from being used. But I'm not clear on what adb command you want to use. Fastboot and adb should be thought of as 2 related, but different things. For recovering a phone in your condition, fastboot is the one you want.
As for fastboot not recognizing the device, I'm starting to think it's because of this older mini laptop I'm having to use as a backup because my good laptop is being loaned out to someone for a while longer. This mini laptop has 3 usb ports on it but all I believe are usb 1.1 (LOL!). Does fastboot require usb 2.0 or higher to work properly? The phone is visible in Device Manager (both internal and external storage), and I'm able to move files around no problem.
I don't remember USB 1.1 being an issue with adb/fastboot. In fact, it's probably more compatible then USB 3.0, which is known to cause issue with some of the HTC tools. I think I was using an old PC with Windows XP on it, when I first got my M8 (although not sure what type USB ports).
More important, is that fastboot will only work when fastboot mode selected while in bootloader (highlighted in red near the top of the screen). From what I remember, it goes to fastboot mode by default, if you boot into bootloader while the phone is connected to a PC. If not, and you can't select fastboot with the power button, than that is a problem
Also, does the sim card have to be in the phone in order to fix the firmware and os?
SIM card is not needed to fix the OS.
I'm assuming since the phone will actually get to hboot and will also boot into safe mode that this phone is recoverable ie. not bricked. I just need help with doing everything in the right order , so I dont end up doing something very wrong and rendering the device useless.
If the phone is s-on, there isn't much you can do, that is not reversible, or will make the condition worse. But as you said, it's best to follow specific instructions as we give them to you.
Click to expand...
Click to collapse

Not clear on what you are telling us here. Are you saying that the current condition (stuck in hboot/safe mode) happen directly after it getting wet? Is so, then it would be pretty clear to me, that it is a hardware issue caused by water damage.
Click to expand...
Click to collapse
Yes the current condition happened directly after getting wet.
More important, is that fastboot will only work when fastboot mode selected while in bootloader (highlighted in red near the top of the screen). From what I remember, it goes to fastboot mode by default, if you boot into bootloader while the phone is connected to a PC. If not, and you can't select fastboot with the power button, than that is a problem
Click to expand...
Click to collapse
Mine doesn't go into fastboot by default when booted into bootloader while connected to PC. While at the HBOOT main screen, Fastboot is at the top of the list of options available to select followed by Recovery, Factory Reset, etc... The power button does not activate any of the options in HBOOT but it works just fine to power the phone on or off and in combination with the Vol Up button to boot the OS which always goes into safemode. However, the Vol Down button doesn't work anywhere. This seems to indicate to me that HBOOT and/or the firmware might be corrupted? As I mentioned earlier, I am able to move files around with no problem. Pretty sure I can't put a RUU into the root directory and fix this because I'm unable to relock the bootloader due to fastboot not working right? If so, is there a way to load/flash a good copy of HBOOT and/or firmware to the phone via my sd card?

brokenm8 said:
However, the Vol Down button doesn't work anywhere. This seems to indicate to me that HBOOT and/or the firmware might be corrupted?
Click to expand...
Click to collapse
I'd say that is a big leap of logic, and probably not a correct one. Hboot is required for the very basic functioning of the phone. Hboot corruption usually equals hard brick (screen won't even come on).
I'd say it's more likely the water damage caused hardware failure of the vol down button.
brokenm8 said:
Pretty sure I can't put a RUU into the root directory and fix this because I'm unable to relock the bootloader due to fastboot not working right? If so, is there a way to load/flash a good copy of HBOOT and/or firmware to the phone via my sd card?
Click to expand...
Click to collapse
You can only flash RUU or firmware with an unlocked bootloader, if the device is s-off.
You also can't flash hboot separately unless you have s-off. You can flash firmware, which contains hboot. But again, unless you have s-off or can relock the bootloader, you can't flash firmware.

Hi there
I got the same exact problem with my m8. At the screen telling : s-on, locked..., the power button and the vol down button are not working, the vol up button is scrolling down instead of scrolling up. It appears that I am stuck in Hboot only I can't use fastboot or any other option. This is the second time I am facing that problem. The first time, I have replaced the motherboard, but since then I didn't flash any rom or done any mod on my htc and here I am now with the same mess.

Glasskeramika said:
I got the same exact problem with my m8.
Click to expand...
Click to collapse
Did you drop it in water, like the OP?
I would suggest anyone refrain from saying you have the "exact same problem" on this forum. I've seen that phrase (or similar) posted dozens (probably hundreds) of times. And not once, have I found (after digging for details) that statement to actually be true. Way too many variables in phone versions, software, what was done to it, etc.
Your time is much better spent giving specific details on the phone, and letter us go from there.

I did not drop in the water.
It went off after battery fully drained. When I tried to turn it on after I plugged it in my computer to charge it, the screen in the attachment showed off. It does show options like fastboot, recovery..etc, but I can't select any of them : the power button (on that screen) doesn't work but it does turn on my phone, the volume down button doesn't work at all (neither on safe mode nor on the attached screen). The vol up button works good when it's running on safe mode, but it plays the role of the vol down button once on that screen (it scrolls down instead of scrolling up).
I need to mention that I had that problem (the same exact haha) two years ago when I rooted my htc m8. Everything was just fine till one day, my phone suddenly started lagging a lot. When I tried to reboot it, that famous screen showed off. I took it to a guy who has replaced the motherboard :crying:. The phone was doing good, I didn't mod anything or rooted it, but it wasn't recognizing the second camera (once on the htc's camera app, it says that my finger is hiding the second camera). But everything was all good for about 1 year, till I got that problem again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 08:09 AM ---------- Previous post was at 07:54 AM ----------
Glasskeramika said:
I did not drop in the water.
It went off after battery fully drained. When I tried to turn it on after I plugged it in my computer to charge it, the screen in the attachment showed off. It does show options like fastboot, recovery..etc, but I can't select any of them : the power button (on that screen) doesn't work but it does turn on my phone, the volume down button doesn't work at all (neither on safe mode nor on the attached screen). The vol up button works good when it's running on safe mode, but it plays the role of the vol down button once on that screen (it scrolls down instead of scrolling up).
I need to mention that I had that problem (the same exact haha) two years ago when I rooted my htc m8. Everything was just fine till one day, my phone suddenly started lagging a lot. When I tried to reboot it, that famous screen showed off. I took it to a guy who has replaced the motherboard :crying:. The phone was doing good, I didn't mod anything or rooted it, but it wasn't recognizing the second camera (once on the htc's camera app, it says that my finger is hiding the second camera). But everything was all good for about 1 year, till I got that problem again.
Click to expand...
Click to collapse
Link (remove all space, please) to the mentioned screen : https: // imgur. com/a/yPY Z4rX
(The image doesn't appear in the previous post that I couldn't edit, oh yeah spam )

Question S21 FE - endless bootloop and download mode/recovery not working (properly)

Hello,
my wife got a S21 FE (SM-G990B/DS VD2). Yesterday it started to reboot over and over out of a sudden, showing the samsung logo first, followed by the knox logo, then shutting off and on again. Tried several guides to enter Recovery or Download Mode. The only thing that worked was entering download mode by pressing Vol up, down and power while a USB-Cable is plugged in, but as soon as i press the vol up button to pass the "warning screen", it shows some phone specs for a couple of seconds, shuts off and starts bootlooping again. After some hours, the phone once entered recovery mode when it lied next to me for about an hour. Tried to wipe cache, but just got an error I can't remember right now. Hoped it fixed itself when it made it to recovery and just rebooted to see if it works again, but then it just keept bootlooping again.
Since then I couldn't figure out why it once booted to recovery on it's own nor why I can't force it to enter recovery by pressing vol up + on.
Still hope it's just a faulty update or bug, but feels very much like it's a hardware related issue. Replacing the phone won't be an issue, but I'd really want to save data on the phone as my wife didn't make any backups and really wants to keep the photos.
As I just found guides that included recovery or DL-Mode, which are both no valid options for my case, I'd be thankful for any ideas to fix the phone or at least gain access to files before replacing it.
So.. did anyone come across similar issues and found a solution to revive the phone or are there any "unpopular" ways to recover samsung phones out of this state?
Edit:
Turned off completely overnight, booted once to system, looped again and now it's working like nothing ever happened. Got no clue what caused it or why it is working again. Saved everything for the case it happens again.
Wouldn't trust that device anymore, but my wife wants to keep it.
¯\_(ツ)_/¯

I would just like to reply here and add my own potential fix and also would like confirmation that it would work.
So I have a SM-G996B in a boot loop which returns a 'fs_mgr_mount_all' error. Possible to reboot into recovery mode, cleared cache and restarted bootloader etc with the same boot loop. Powered off and connected to PC for Download mode for ODIN recovery but upon pressing volume up, it then restarts again so Download mode recovery is impossible.
I know however that Developer options and USB debugging was enabled on the device as well as unlocked boot loader. I was able to download the correct original stock OS based on the PDA , CSC and Android version.
I have then installed the latest ADB software on my PC and Samsung USB drivers.
By then rebooting into recovery mode, I have the option of 'Apply update from ADB'. I have then confirmed the device connects using the ADB devices command.
I would like to clarify one thing however. I want to keep the user data at all costs. By using the stock firmware and renaming as update.zip, will it use the HOME_CSC and not the CSC file? If not would it work if I open the zip and remove the CSC before re-zipping to make sure?
Thanks

Reebee said:
Hello,
my wife got a S21 FE (SM-G990B/DS VD2). Yesterday it started to reboot over and over out of a sudden, showing the samsung logo first, followed by the knox logo, then shutting off and on again. Tried several guides to enter Recovery or Download Mode. The only thing that worked was entering download mode by pressing Vol up, down and power while a USB-Cable is plugged in, but as soon as i press the vol up button to pass the "warning screen", it shows some phone specs for a couple of seconds, shuts off and starts bootlooping again. After some hours, the phone once entered recovery mode when it lied next to me for about an hour. Tried to wipe cache, but just got an error I can't remember right now. Hoped it fixed itself when it made it to recovery and just rebooted to see if it works again, but then it just keept bootlooping again.
Since then I couldn't figure out why it once booted to recovery on it's own nor why I can't force it to enter recovery by pressing vol up + on.
Still hope it's just a faulty update or bug, but feels very much like it's a hardware related issue. Replacing the phone won't be an issue, but I'd really want to save data on the phone as my wife didn't make any backups and really wants to keep the photos.
As I just found guides that included recovery or DL-Mode, which are both no valid options for my case, I'd be thankful for any ideas to fix the phone or at least gain access to files before replacing it.
So.. did anyone come across similar issues and found a solution to revive the phone or are there any "unpopular" ways to recover samsung phones out of this state?
Edit:
Turned off completely overnight, booted once to system, looped again and now it's working like nothing ever happened. Got no clue what caused it or why it is working again. Saved everything for the case it happens again.
Wouldn't trust that device anymore, but my wife wants to keep it.
¯\_(ツ)_/¯
Click to expand...
Click to collapse
Similar issue with same phone. In a bootloop after trying to root. None of the button combinations have worked for me, for the past several days.
Tried powering the phone off for the whole night.
When connected to the PC shows phone is in recovery mode via adb (blank screen though).
Want to know how to get into DL-mode, guaranteed.

Got to DL mode by pressing vol up + down + power + usb cable connected in PC and phone. However, couldn't do anything there, but maybe you can
Also, phone is still working and I still have no clue what was the problem and what fixed it.