Develop Bugs

[Q] Phone won't boot. Vibrates three times. Need advice.

My G2 won't boot normaly and is acting very straingly. I did a search of other similar problems people have had, but nothing matches what is happening to mine. It started when I noticed my power button and volume up button stoped working. I assumed it was a glitch and thought a reboot might help. Since the power button wasn't functioning, I pulled the battery to reboot it. That's when it stoped working. When I turn it on normaly with the power button, the screen stays off, it vibrates three times, and the led blinks orange untill I put the battery. If I attempt to boot into recovery with the button combination, it does the same. If I attempt to boot into HBoot, it vibrates five times and the led lights up solid green. Here's where things get realy strange. When I plug the phone into the charger while the phone is off, after about five seconds the phone comes on into the recovery bootloader even though when I boot while holding the buttons it dosn't work. I have the ClockworkMod touch recovery installed. From within the recovery I have full access to everything including ADB with root access. When I select the reboot option from recovery, it does the same thing with the vibrating and the blinking led. I tried the key test in the recovery and I discovered that my volume up button only works intermitently and my power button seems to be working fine. I haven't attempted to flash a new rom yet because I'm assuming it must be something else since I can't even access HBoot, and I'm scared if I touch anything I'll loose access to recovery and ADB as well.
Any advice? Could a damaged volume up button contact cause all this to happen? Should I try flashing it from recovery even though I can't access HBoot?

Thread moved to Q & A section, post in the relevant section next time.

in adb try
adb reboot-bootloader

demkantor said:
in adb try
adb reboot-bootloader
Click to expand...
Click to collapse
Just tried it. Screen goes black, vibrates three times, and led blinks orange untill I pull the battey. It was a good Idea though, I didn't think to try that myself.

you know what, are these very quick vibrates? you mentioned there is a problem with your volume rocker (sticky keys?) your phone may be trying to get into the jtag/download mode.
not sure how to use this mode on the vision but tell me if this is the same response you get.
take out battery, hold both volume buttons, plug phone into computer.
it should vibrate three times rapidly and computer should look for driver :
Qualcomm CDMA Technolgies MSM driver
not sure where to get the proper driver for the vision but ive used this mode to root other android phones and i know there is a "unbricking project" for various phones that use this mode.
nothing for the vision that i know of though.
but being you have adb access maybe test a few things first like see if anything is accessible from your emmc
type:
Code:
adb shell
dmesg | grep mmc0
and see what happens
edit:
i can replicate you situation by holding volume up while powering on
you have a stuck volume up key, almost 100% just open up phone and clean it out and you should be just fine!

Help with bootlooped mi5s :(

Hi.
I have a Xiaomi mi5s 64/3 GB in an endless bootloop. Here are the details:
The phone is:
rooted
bootloader unlocked
developer mode enabled
internal storage *not* encrypted
no MIUI account activated
USB debugging on
running the last EU MIUI 9.x development version (don't remember the exact version) with Android 7.0
has TWRP 3.2.1.0 and supersu 2.82
no password is set for unlocking the screen etc.
For some unknown reason the phone suddenly rebooted yesterday and got into an infinite bootloop cycle. I haven't changed any roms recently or done any such flashing. My google play automatic updates were disabled, but a few days ago I manually updated all the apps.
The only odd thing that happened prior to this bootloop, was that when shooting some photos with the google camera mod (same one I've been using for the past few weeks), 2 images were saved as corrupt unreadable files. But that happened a few hours before the bootloop suddenly started.
The current status is:
1. I cannot turn the power off (tried holding the power button, or power button + vol up and down for a very long time --> nothing).
2. I cannot enter recovery mode using vol up + power.
3. I cannot enter EDL using all 3 buttons.
4. If I hold volume down, it enters fastboot but automatically exits from it within 4 seconds (ADB and miflash cannot detect the device in this short period of time). holding the volume down button for a long time has a repating enter-exit-after-4-seconds from the fastboot graphics.
I waited until the battery was completely dead, than started charging it and the status described above was unchanged.
QUESTION 1 - restoring the internal data is my number one priority - does it seem possible here?
To be exact: I want the DCIM folder with the photos+ videos. What should I try now?
QUESTION 2 - I ordered an EDL cable, but am unsure if it supported for my MIUI version. if the EDL cable works, can I force the phone to enter recovery mode from within EDL?
If so - I guess I can copy the internal data to an external USB OTG flash drive I have (that works well with the phone).
If my data is restored, I will then move onto trying to reflash the phone, but at this point this is the least of my worries...
Thanks all.

Anyone?

Maybe it's a problem with the button? I would disassembly the phone and check the hardware.

bedson87 said:
Maybe it's a problem with the button? I would disassembly the phone and check the hardware.
Click to expand...
Click to collapse
I don't know - the buttons don't seem like they are stuck in any way. When I push them, they click back out as usual.
Update - I created an EDL flash cable by stripping the cable gently, exposing the green and black wires, and looping them together - connecting this cable to the phone didn't help either.
Maybe I need to wait for the battery to die so the phone will turn off, connect this cable to the phone, keep the power button pressed while I connect it to the usb port in my PC... what do you think?

I have the same problem with mi 5s which started after update. Don't know what to do.

Took the phone to a local lab - it was all due to a faulty power button module.

Cannot boot into download mode

Hi everybody, yesterday I was playing with my old Galaxy A50 trying to install a custom rom unsuccessfully.
I repeated the procedure three times installing TWRP and then Havoc OS but every time I tried to reboot from TWRP to OS I was stuck at the warning screen saying that the phone bootloader was unlocked and booting into download mode to reflash TWRP was blocked as it showed "only official binaries can be installed" (yes I installed Samsung disabler but still).
Still I was able to get the phone into download mode and reinstall the stock firmware as it seemed to be the only way to install and boot TWRP.
But at 4th time repeating the process I got frustrated, shut down the computer and left the phone on the warning screen still connected to computer usb cable.
Then I got back and noticed the phone was off as the battery died.
Indeed the battery died, so I put the phone in charging and after it reached 100% I tried to boot into download mode again to reflash stock firmware.
But here's the strange thing, I cannot boot into download mode anymore as pressing vol up+vol down while connecting usb cable, shows the lightning charge logo for 5 secs and then reboots infinitely with the same pattern.
If I force reboot by pressing vol down+power it shows the Samsung logo with the warning below it, then skips to another screen with another warning suggesting to press power button to continue (which does nothing) and after a while reboots to samsung logo.
So it doesn't seem it is bricked, it looks more like a battery controller fault, so I tried to detach the battery flex from the board, hoping it would reset the controller but it's still the same.
Also I tried with the flex detached and still no download mode is possible.
Was the download mode somehow erased? (if it's even possible considering it's the motherboard firmware)
If you need photos, videos or even a call on zoom, Skype, webex I would be glad to show you

same i got the same problem i can't find nothing for this when i press volume up and down and put the otg cable its simply charges but it gets stuck on the logo image there's no way to fix this but the only way is to open the phone,change the emmc and put one from samsung,close the phone flash a custom rom and you are done.

If you can enter recovery, do it. As soon as your phone gets into it, select the power off variant and then try to enter the download mode.
It seems like you did not unlock the bootloader, did you?

The bootloader Is unlocked i can't enter in the recovery because the phone locks on charging logo and its fully charged but when i try without charger It doesn't start.

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.

Question My Poco F3 froze then i proceeded to a hard reset. Phone goes into bootloop without any display. Any FIxes?

So I am normally using my phone scrolling through social media but it suddenly froze so I tried to hard reset it, but it goes in to a bootloop without any display on the screen. I could tell it is on a bootloop because of the repeating vibration everytime the phone boots up.
My device is Poco F3 (alioth) Running stock MIUI 12.5 bootloader unlocked and rooted with Magisk.
Things I have tried:
Long pressing power button, long pressing both power button and volume down button, long pressing power and volume up button, then long pressing all of them.
Plugging it on my PC but it doesn't even detect it. Tried inputting
Code:
adb devices
and
Code:
fastboot devices
Still doesn't work. I even made sure that my drivers are working so I tried it on my brothers Poco F3 and the PC can detect his phone through ADB commands.
Waiting for a day if it magically turns on again. Nope.
Charging it up because maybe the battery is low. Nope.
At this point my only two choices is opening up the back panel then replugging the battery so it completely turns off and hopefully boots up. But its a risky task since I don't have special tools to open up my phone, and my another choice is just bring it on a service center.

rururi said:
So I am normally using my phone scrolling through social media but it suddenly froze so I tried to hard reset it, but it goes in to a bootloop without any display on the screen. I could tell it is on a bootloop because of the repeating vibration everytime the phone boots up.
My device is Poco F3 (alioth) Running stock MIUI 12.5 bootloader unlocked and rooted with Magisk.
Things I have tried:
Long pressing power button, long pressing both power button and volume down button, long pressing power and volume up button, then long pressing all of them.
Plugging it on my PC but it doesn't even detect it. Tried inputting
Code:
adb devices
and
Code:
fastboot devices
Still doesn't work. I even made sure that my drivers are working so I tried it on my brothers Poco F3 and the PC can detect his phone through ADB commands.
Waiting for a day if it magically turns on again. Nope.
Charging it up because maybe the battery is low. Nope.
At this point my only two choices is opening up the back panel then replugging the battery so it completely turns off and hopefully boots up. But its a risky task since I don't have special tools to open up my phone, and my another choice is just bring it on a service center.
Click to expand...
Click to collapse
If the phone is bootloader locked don't do anything, take it to service center it's out of your hands.
If service center intends to charge you something well you could find some people online with edl accounts to do flashing for you but this sounds like hardware issue if you don't see poco logo ...
Edit: Sry didn't read the post fully - did u try fastboot devices when in fastboot mode - volume down and power ? If it is recognized and bootloader unlocked you can try flashing - go with xiaomi firmware, last thing you want is to be stuck on custom firmware when you take it in for repair - again only if bootloader is unlocked

since your brother pc can recognize, tried fastboot miui.eu on his pc
but I had this problem before and the only solution is to change mainboard on the xiaomi service center.

rururi said:
So I am normally using my phone scrolling through social media but it suddenly froze so I tried to hard reset it, but it goes in to a bootloop without any display on the screen. I could tell it is on a bootloop because of the repeating vibration everytime the phone boots up.
My device is Poco F3 (alioth) Running stock MIUI 12.5 bootloader unlocked and rooted with Magisk.
Things I have tried:
Long pressing power button, long pressing both power button and volume down button, long pressing power and volume up button, then long pressing all of them.
Plugging it on my PC but it doesn't even detect it. Tried inputting
Code:
adb devices
and
Code:
fastboot devices
Still doesn't work. I even made sure that my drivers are working so I tried it on my brothers Poco F3 and the PC can detect his phone through ADB commands.
Waiting for a day if it magically turns on again. Nope.
Charging it up because maybe the battery is low. Nope.
At this point my only two choices is opening up the back panel then replugging the battery so it completely turns off and hopefully boots up. But its a risky task since I don't have special tools to open up my phone, and my another choice is just bring it on a service center.
Click to expand...
Click to collapse
Do you have any clue as to why this happened? Any mods done besides applying Magisk?
If the software got damaged, you could try the EDL Mode but that's difficult. Should be your last resort.
If hardware, then I don't know unfortunately...but then how?

rururi said:
So I am normally using my phone scrolling through social media but it suddenly froze so I tried to hard reset it, but it goes in to a bootloop without any display on the screen. I could tell it is on a bootloop because of the repeating vibration everytime the phone boots up.
My device is Poco F3 (alioth) Running stock MIUI 12.5 bootloader unlocked and rooted with Magisk.
Things I have tried:
Long pressing power button, long pressing both power button and volume down button, long pressing power and volume up button, then long pressing all of them.
Plugging it on my PC but it doesn't even detect it. Tried inputting
Code:
adb devices
and
Code:
fastboot devices
Still doesn't work. I even made sure that my drivers are working so I tried it on my brothers Poco F3 and the PC can detect his phone through ADB commands.
Waiting for a day if it magically turns on again. Nope.
Charging it up because maybe the battery is low. Nope.
At this point my only two choices is opening up the back panel then replugging the battery so it completely turns off and hopefully boots up. But its a risky task since I don't have special tools to open up my phone, and my another choice is just bring it on a service center.
Click to expand...
Click to collapse
If it's recognised by your brothers pc, try that pc for flashing stock fastboot rom using miflash, and don't forget to choose 'flash and wipe' instead of 'flash and lock' in bottom right corner of miflash. Let us know how you get on

Happened today. Random bootloop while under normal use. Also occasionally attempted to trigger the emergency SOS call when power BTN clicks 5 times.
Saved by a solution in poco x3 thread.
The failure mode I experienced was possibly a "sticky" power button.unsure if it's an electrical short or something mechanical in nature tho since it's intermittent triggering of the power button.
Temp fix was some quick clicks of the power button a bunch of times(20-30 clicks?).
Also shut off the emergency sos function.

jowaii89 said:
Happened today. Random bootloop while under normal use. Also occasionally attempted to trigger the emergency SOS call when power BTN clicks 5 times.
Saved by a solution in poco x3 thread.
The failure mode I experienced was possibly a "sticky" power button.unsure if it's an electrical short or something mechanical in nature tho since it's intermittent triggering of the power button.
Temp fix was some quick clicks of the power button a bunch of times(20-30 clicks?).
Also shut off the emergency sos function.
Click to expand...
Click to collapse
Same... it started calling emergency number and wouldn't shut off by holding power button.
Worst device ever
{Mod edit: Inappropriate language edited. Oswald Boelcke}