My friend has an S21 Ultra 5G with the Exynos SoC. There's an app that constantly crashes, Samsung Audio Remote, that he NEEDS to control the volume on his sound bar because he's handicapped and can not use a physical remote. After a total of 3 HOURS on the phone with Samsung support, the next step and alleged solution is to wipe the cache partition. But I can not get I to recovery. The procedure support told me to use, that I tried 3 times while they were on the phone, did not work. Now, I'm no tech god, but I have successfully flashed dozens of roms on several devices over the years, including 4 Samsung Galaxy devices, so I know a thing or two about pressing buttons in the right sequence. But, this S21 is kicking my tail. It's sooooo much is a trainwreck that I have decided that Samsung does NOT want my money, so I'll be happy to never give them a penny more. But. My friend has this $1000 turd so he's got to get it figured out. So. Please. How do I get into recovery so I can wipe the cache partition on this pile of junk?
Build number is G998BXXU2AUBB.
As a side, this problem exists on his S21, my Moto G Stylus, and his Galaxy Tab tablet, but it does NOT exist on his LG Stylo 3, so I'm pretty confident that even wiping the recovery partition will not solve the problem, but if you've ever dealt with tech support, you know that until you do the next useless troubleshooting step, they won't move on to try to actually solve the issue. So, I gotta do it.
Turn off the device.
Then boot with both the power button and the volume up button pressed (and hold them) until the phone boots to recovery.
Skander1998 said:
Turn off the device.
Then boot with both the power button and the volume up button pressed (and hold them) until the phone boots to recovery.
Click to expand...
Click to collapse
In my experience this only works if the phone is turned off and connected by a USB-cable to a computer. If it doesn't sense the cable connected it will just boot to normal Android OS.
fdomi said:
In my experience this only works if the phone is turned off and connected by a USB-cable to a computer. If it doesn't sense the cable connected it will just boot to normal Android OS.
Click to expand...
Click to collapse
Ya... You need to connect a cable for it to work!
Sukrith said:
Ya... You need to connect a cable for it to work!
Click to expand...
Click to collapse
It's funny that several websites forget to mention this, they just write about the key combination and rebooting, but without the cable being connected to the PC it won't boot to recovery.
on most devices you dont actually need the cable connected first and some devices do weird stuff like turn on when you plug them in. They probably dont have the actual device.
sesnut said:
on most devices you dont actually need the cable connected first and some devices do weird stuff like turn on when you plug them in. They probably dont have the actual device.
Click to expand...
Click to collapse
Yes, yet they inform and post the key combination as if they have tried it themselves.
You needs to connect to PC to reboot to recovery along with combo key started from Android R on Samsung devices. On older os it doesn't requires
dr.ketan said:
You needs to connect to PC to reboot to recovery along with combo key started from Android R on Samsung devices. On older os it doesn't requires
Click to expand...
Click to collapse
Actually you don't need to connect the cable to a PC...the cable has to be connected to a power source. I booted to recovery with the cable connected to my power bank..
amirage said:
Actually you don't need to connect the cable to a PC...the cable has to be connected to a power source. I booted to recovery with the cable connected to my power bank..
Click to expand...
Click to collapse
Power isn't important, storage is
Wall mount power won't work, power bank, usb storage will do.
amirage said:
Actually you don't need to connect the cable to a PC...the cable has to be connected to a power source. I booted to recovery with the cable connected to my power bank..
Click to expand...
Click to collapse
I tried that and it didn't work for me, I actually needed to boot into a PC, or maybe it doesn't work with simple slow charge USB? I will play with this to see if it works with another power source.
fdomi said:
I tried that and it didn't work for me, I actually needed to boot into a PC, or maybe it doesn't work with simple slow charge USB? I will play with this to see if it works with another power source.
Click to expand...
Click to collapse
Try any usb storage if you have, it will work. It doesn't need power.
Even usb c headphones will work
Related
UPDATE - Turns out the motherboard was dead. Apparently it's a problem that's been going around S10s lately
Left my S10 on the table over the night. Woke up this morning and nothing's responding. After 5 years of developer experience, I believe this device is hard bricked.
Tried force restarting
Recovery mode (bixby+power+volume up) doesn't work at all
Power button, and any other combination of power button, volume buttons, and bixby buttons does not work at all. No sign of life
Plugged it into computer and I see no devices in device manager, even with correct drivers
ADB and fastboot search does not find anything
Tried charging it with all sorts of chargers, with no sign of life
Because of this, I believe my device to be completely bricked (in which case, the only option is warranty and replace). I think it's a motherboard issue - not a battery issue, as it doesn't work even when plugged in. Am I missing something here?
What scares me is that I literally did nothing to it, and all of a sudden it bricks. I can't even flash stock firmware as my computer won't recognize it.
Try holding volume down and bixby button and then plug in the usb to a computer.
Oh no, you brick, you buy!!!!
Player04 said:
Try holding volume down and bixby button and then plug in the usb to a computer.
Click to expand...
Click to collapse
matthewclso said:
Power button, and any other combination of power button, volume buttons, and bixby buttons does not work at all. No sign of life
Plugged it into computer and I see no devices in device manager, even with correct drivers
Click to expand...
Click to collapse
Tried that already.
Player04 said:
Oh no, you brick, you buy!!!!
Click to expand...
Click to collapse
As for the warranty, Samsung does replace all devices as long as the fault was not on the user. Per Samsung's warranty policy, all devices are covered for one year for issues such as this.
matthewclso said:
Tried that already.
As for the warranty, Samsung does replace all devices as long as the fault was not on the user. Per Samsung's warranty policy, all devices are covered for one year for issues such as this.
Click to expand...
Click to collapse
If i may ask, which version of the S10 is this.
Player04 said:
Try holding volume down and bixby button and then plug in the usb to a computer.
Oh no, you brick, you buy!!!!
Click to expand...
Click to collapse
So, I let a friend of mine use my old M7 in order to repartition/format an sd card (using an OTG adapter). Came back with phone completely dead. I do suspect he ended up partitioning or formatting one of the system partitions in there (possibly the bootloader?) phone was rooted so...
Anyway, situation is as follows: Phone looks dead. Long pressing the power button does nothing, no vibration, no keys light up, no screen comes on.
BUT, when connecting it to the computer I get the usb connection sound on my Windows 10. If I long press the power button for ~10 seconds, i do get the usb disconnection sound, followed again by the usb connection sound. So "something" is alive in there. Also, power+vol down button does reboot the phone.
However there's no way to access recovery, bootloader, adb/fastboot, or even flash a RUU.
It isn't even charging when I plug it in, no red led.
Anything else I could try before giving up?
Thank you.
akpe said:
So, I let a friend of mine use my old M7 in order to repartition/format an sd card (using an OTG adapter). Came back with phone completely dead. I do suspect he ended up partitioning or formatting one of the system partitions in there (possibly the bootloader?) phone was rooted so...
Anyway, situation is as follows: Phone looks dead. Long pressing the power button does nothing, no vibration, no keys light up, no screen comes on.
BUT, when connecting it to the computer I get the usb connection sound on my Windows 10. If I long press the power button for ~10 seconds, i do get the usb disconnection sound, followed again by the usb connection sound. So "something" is alive in there. Also, power+vol down button does reboot the phone.
However there's no way to access recovery, bootloader, adb/fastboot, or even flash a RUU.
It isn't even charging when I plug it in, no red led.
Anything else I could try before giving up?
Thank you.
Click to expand...
Click to collapse
When you here that USB sound when connecting to your pc, go to the windows device manager and look for devices in the usb section. Is the phone showing as "QHSUSB_DLOAD" or simply "HTC Phone" ?
alray said:
When you here that USB sound when connecting to your pc, go to the windows device manager and look for devices in the usb section. Is the phone showing as "QHSUSB_DLOAD" or simply "HTC Phone" ?
Click to expand...
Click to collapse
Hey, thanks for the reply, sorry for the delay. Yeah, it shows something similar to QHSUSB_DLOAD. Looked it up a bit, guess it's completely borked.
akpe said:
Hey, thanks for the reply, sorry for the delay. Yeah, it shows something similar to QHSUSB_DLOAD. Looked it up a bit, guess it's completely borked.
Click to expand...
Click to collapse
Yep sounds like your phone is in Qualcomm download mode. Usually this can happens for 2 reasons.
1- Hardware failure
2- Bad firmware flash
this thread can help: https://forum.xda-developers.com/showthread.php?t=2770684
Hard to tell since we don't know what your friend exactly did or what was used from that usb-otg drive.
A phone shop that can connect to your phone using jtag/riff could maybe fix it but doesn't worth the $$ asked for a 2013 phone, imo.
alray said:
Yep sounds like your phone is in Qualcomm download mode. Usually this can happens for 2 reasons.
1- Hardware failure
2- Bad firmware flash
this thread can help: https://forum.xda-developers.com/showthread.php?t=2770684
Hard to tell since we don't know what your friend exactly did or what was used from that usb-otg drive.
A phone shop that can connect to your phone using jtag/riff could maybe fix it but doesn't worth the $$ asked for a 2013 phone, imo.
Click to expand...
Click to collapse
As far as he told me, he just used an app to try to format the otg drive, multiple times, and after a reboot phone died. He couldn't remember which app he used, but since phone was rooted, I can only guess he actually tried to format some system partition.
I will give the unbricking project a go, need to find a linux machine first. I really know jack about linux, but I guess it's no harm trying it Thank you!
So im trying to unbrick my 3t, its my 2nd device.. and i tried with MSM tool. i keep getting errors such as firehouse communiocation handshake failed, sahara communication etc. For some reason when i just hold vol up by itself it doesnt show up as qualcomm in device manager. i have to hold power as well. but i keep getting different errors
The correct way to enter Qualcomm restore is by making sure the phone is 100% turned off and wait some more. Then keep pressing volume up while connecting cable until device shows up as the Qualcomm restore device. If it doesn't work, choose an USB 2.0 port instead of 3.0 or the other way aroune if possible or try another USB-C cable. And if it still doesn't work, maybe the PCB or USB connector of phone is broken in hardware.
pitrus- said:
The correct way to enter Qualcomm restore is by making sure the phone is 100% turned off and wait some more. Then keep pressing volume up while connecting cable until device shows up as the Qualcomm restore device. If it doesn't work, choose an USB 2.0 port instead of 3.0 or the other way aroune if possible or try another USB-C cable. And if it still doesn't work, maybe the PCB or USB connector of phone is broken in hardware.
Click to expand...
Click to collapse
I did. i keep getting firehousecheckrsp failed
xHvlios said:
I did. i keep getting firehousecheckrsp failed
Click to expand...
Click to collapse
You can try pressing and holding down the power button for 40 seconds when phone is on, this should force shutdown your phone without entering quickboot powersave as I think you will get this firehousecheckrsp error if phone was shutdown normal from OxygenOS ROM.
After this, startup the Qualcomm tool on PC, hold volume up and connect USB-cable. Check Windows Device Manager that the Qualcomm device is there and that the driver is working without any exclamation mark on it.
Bricked OP3T
pitrus- said:
The correct way to enter Qualcomm restore is by making sure the phone is 100% turned off and wait some more. Then keep pressing volume up while connecting cable until device shows up as the Qualcomm restore device. If it doesn't work, choose an USB 2.0 port instead of 3.0 or the other way around if possible or try another USB-C cable. And if it still doesn't work, maybe the PCB or USB connector of the phone is broken in hardware.
Click to expand...
Click to collapse
Hello, happy greetings to you and I hope you are safe. I also keep getting firehousecheckrsp failed sahara communication etc even if my device is surely 100% off (as it has no indicator whatsoever even if connected to the power brick, no vibration, just plain black screen). Also did hold the power button for more than 40 secs just to be sure. Though a bit of good news I guess is that my device can be detected as Qualcomm 9008 in Ports & Com in Device Manager when I hold the volume up button for several seconds.
Btw, these are the tools I used but none of them worked.
https://forum.xda-developers.com/on...ck-tool-3t-unbrick-data-babloo-t3737791/page3
https://forum.xda-developers.com/on...k-unbrick-tutorial-oneplus-3t-t3515306/page71
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Do hope to hear from you soon. Thank you.
Have you followed the complete guide?
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
But for sure it has Something to do with your usb version. Try diverent cable's for sure usb 2.0 is far more stable!
Followed guide
reef2009 said:
Have you followed the complete guide?
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
But for sure it has Something to do with your usb version. Try diverent cable's for sure usb 2.0 is far more stable!
Click to expand...
Click to collapse
Hello, thanks for noticing my question. I did follow the guide, changed USB ports, used another cable, and I still have the FirehoseCheck RSP Failed errorno:258 also Last Communication Status: Downloading cache.img Failed.
Also tried ones from Android 8 from this thread:
[OP3T][LATEST 9.0.6] Collection of unbrick tools
https://forum.xda-developers.com/oneplus-3t/how-to/op3t-collection-unbrick-tools-t3896765/page2
Is there another way for this?
Do hope to hear from you again. Thank you.
Anybody know how to go into the recovery mode , since i was unable to do it by the usual way ? S21 ultra exy
Lots of articles online and YouTube videos..LSS..you need to connect your phone to a USB storage (preferably a computer)..power off completely...restart pressing power and volume down...you should be recovery
amirage said:
Lots of articles online and YouTube videos..LSS..you need to connect your phone to a USB storage (preferably a computer)..power off completely...restart pressing power and volume down...you should be recovery
Click to expand...
Click to collapse
Sorry to correct you, but it's power and volume UP ! not down! Of course what's important is to have the phone connected via USB cable to a PC, or pen drive, power bank etc, otherwise it will just boot to normal Android OS.
fdomi said:
Sorry to correct you, but it's power and volume UP ! not down! Of course what's important is to have the phone connected via USB cable to a PC, or pen drive, power bank etc, otherwise it will just boot to normal Android OS.
Click to expand...
Click to collapse
Thanks...I meant to write volume up but I was screaming at some to put their music volume "down"...down and up got mixed up...heehhe...the perils of multitasking!
fdomi said:
Sorry to correct you, but it's power and volume UP ! not down! Of course what's important is to have the phone connected via USB cable to a PC, or pen drive, power bank etc, otherwise it will just boot to normal Android OS.
Click to expand...
Click to collapse
Why on samsung an additional step ( to connect to usb) required ?
All others can open recovery with buttons itself
aj7400 said:
Why on samsung an additional step ( to connect to usb) required ?
All others can open recovery with buttons itself
Click to expand...
Click to collapse
Bureaucracy, red tape name it what you like... Samsung just wanted to make our lives more miserable..
amirage said:
Bureaucracy, red tape name it what you like... Samsung just wanted to make our lives more miserable..
Click to expand...
Click to collapse
Still we buy it ,
why ?
aj7400 said:
Still we buy it ,
why ?
Click to expand...
Click to collapse
Ahh...the philosophical question...the answer to this can be found in the famous quote by Confucius, "Never raise hands to angry child, it leave groin exposed." Who is who in this quote is best left to interpretation!
amirage said:
Ahh...the philosophical question...the answer to this can be found in the famous quote by Confucius, "Never raise hands to angry child, it leave groin exposed." Who is who in this quote is best left to interpretation!
Click to expand...
Click to collapse
Came back from cricket , still have the groin guard ,
Come on baby
aj7400 said:
Came back from cricket , still have the groin guard ,
Come on baby
Click to expand...
Click to collapse
Please do hit like if I put a smile on your face!
Thankyou guys
fdomi said:
Sorry to correct you, but it's power and volume UP ! not down! Of course what's important is to have the phone connected via USB cable to a PC, or pen drive, power bank etc, otherwise it will just boot to normal Android OS.
Click to expand...
Click to collapse
Still cant boot into recovery , do i need to use the original cable ?
iamcgs said:
Still cant boot into recovery , do i need to use the original cable ?
Click to expand...
Click to collapse
Not necessarily, any USB-C to USB-A cable should work. Make sure the phone is completely switched off. You need to press vol up+power for some time until the Samsung splash screen changes to the recovery mode.
amirage said:
Not necessarily, any USB-C to USB-A cable should work. Make sure the phone is completely switched off. You need to press vol up+power for some time until the Samsung splash screen changes to the recovery mode.
Click to expand...
Click to collapse
It only boot to system . Try it a couple times already
iamcgs said:
It only boot to system . Try it a couple times already
Click to expand...
Click to collapse
Is this of any help:
Have you enabled developer mode and you have it set up for USB debugging already? If so you can use the ADB command line to restart your phone by issuing the following from a command prompt in the directory you installed ADB/Fastboot or anywhere if you put them in your path variable -- "ADB reboot recovery"
If you're not having any luck with that, you may need to reset (NOT factory reset, that will wipe everything) press and hold the volume down key and the bixby/power key and hold them for a 15 second count, even when the device powers off. This combination will power it off no matter what. After the slow count of 15, release the keys, plug in your USB cable, and press and hold power/volume up key as the previous posters instructed you - until the phone starts and you see the logo - this should boot you into recovery mode as well.
Is your phone booting into the system? If so, a 3rd option you may avail yourself of is an restarting app for non-rooted devices such as Shutdown, there are several, read the descriptions and pick your poison from the Google play store (If you're running a stock device make sure the app you choose doesn't require root) it will however, require you to grant accessibility permissions - full control of device and SHUTDOWN in order to function - and that will give you the option to reboot to recovery mode.
Good Luck, L4XS
I cannot boot in to recovery mode. Volume up & power key won't work (cable is not helping). Any idea?
Timing is everything. Relax... I hit reboot and once the screen flashes off hold the volume up button until the menu comes up.
Won't work. I did try this so many times.
Try this:
Power down the smartphone.
Then wait a few seconds for it to completely shut down. ...
Now press and hold the Power and Volume Up buttons at the same time.
And continue holding these two buttons down even after the Galaxy S21 starts to boot back up.
Not working... I don't know what is wrong.
prfraczek said:
Not working... I don't know what is wrong.
Click to expand...
Click to collapse
Unplug the cable if you haven't.
Did you toggle on Developer options?
Try turn it off.
Turned developer options off still no luck. Weird.
If your timing is off with the button push it will do that. Sometimes it takes one time, sometimes 2 or 3. Don't power off; hit restart. Before it starts to boot have the volume up button depressed.
LADB is so much easier for stuff like this if unrooted. once setup properly, just issue out
Code:
reboot recovery
I gave up. I am going to shi...y Samsung Store tomorrow to do this. It is unbelievable. All my browsers lags and I cannot simply clear a cache. Every day I am regretting swap from 1+8 pro. I thought Samsung changed since I had s8 but no - it is even more laggy, bloated. They do and sell the best hardware but simply have no clue about software optimisation. Thanks all for help
I can assure that clearing cache partition will have zero impact to your issues.
Why are you so certain the cache partition is the answer?
skymera said:
I can assure that clearing cache partition will have zero impact to your issues.
Why are you so certain the cache partition is the answer?
Click to expand...
Click to collapse
Saying it won't work is impossible to predict. If it does work, and many times it does, the issue is gone... a cheap but good trick.
Clearing the system cache is part of the light maintenance I do or when odd behavior occurs.
skymera said:
I can assure that clearing cache partition will have zero impact to your issues.
Why are you so certain the cache partition is the answer?
Click to expand...
Click to collapse
I'd like to do this before wiping whole phone and re-setup 20x2FA authenticators. It can be dns, webview and much more. So I believe it is good idea start from clearing cache partition
I couldn't get it to work either, until I had the usb cable connected to my laptop - then it was able to boot in to recovery mode and let me clear the cache.
I tried it just with the cable in the phone, the cable in the charger and the phone, no cable and the only way it worked was with the cable connected to laptop and phone with the laptop powered on.
Odd!
heartyparty said:
I couldn't get it to work either, until I had the usb cable connected to my laptop - then it was able to boot in to recovery mode and let me clear the cache.
I tried it just with the cable in the phone, the cable in the charger and the phone, no cable and the only way it worked was with the cable connected to laptop and phone with the laptop powered on.
Odd!
Click to expand...
Click to collapse
That's very strange behavior.
Maybe a firmware, C port PCB or mobo issue.
Keep an eye on it... no likey.
Try this:
Power down the smartphone.
Connect the phone with PC or laptop via USB cable OR while your phone is closed connect a type c USB memory stick.
Now press first Volume Up button and then the Power button (don't leave the Volume Up button)
And continue holding these two buttons down even after the Galaxy S21 starts to boot up.
You will see the recovery options to your screen.
miltos74 said:
Try this:
Power down the smartphone.
Connect the phone with PC or laptop via USB cable OR while your phone is closed connect a type c USB memory stick.
Now press first Volume Up button and then the Power button (don't leave the Volume Up button)
And continue holding these two buttons down even after the Galaxy S21 starts to boot up.
You will see the recovery options to your screen.
Click to expand...
Click to collapse
This did the trick. Thank you so much for it. Even more, chrome lag gone!
prfraczek said:
This did the trick. Thank you so much for it. Even more, chrome lag gone!
Click to expand...
Click to collapse
I'm happy for helping my friend. Have a nice day.
blackhawk said:
Try this:
Power down the smartphone.
Then wait a few seconds for it to completely shut down. ...
Now press and hold the Power and Volume Up buttons at the same time.
And continue holding these two buttons down even after the Galaxy S21 starts to boot back up.
Click to expand...
Click to collapse
is the button working when the phone is on?
flairepathos.info said:
is the button working when the phone is on?
Click to expand...
Click to collapse
What do you mean?
Only the power button is active at all times.
The volume up/down inputs are only active when as/after the phone is/has been powered on.