Database Develop

[Q] Bricked m7u

Hi guys, I have the non-lte One running on 2.24.707.3. Today, I restored my stock nandroid (4.2.2) and then tried the rumrunner s-off (rumrunner_m7_2.24.401.1). It worked, and I was successfully s-off, superCID on hboot 1.54. I then flashed a modified hboot(descenpet_HBOOT_1.54_2.24_MOD) to remove the red warning. All went well. Later, while I was recieving a call, the phone got hung up, so I did a reset (holding the power + vol down buttons). The phone got switched off, but never booted back up.. I tried holding the power + vol down buttons but even the buttons aren't flashing.. Connecting it to my pc makes no connection sounds, and again holding the combo makes no difference. The charging light also doesn't light up. Please tell me what I should do, and whether it is a hard brick or soft brick. Thanks in advance.

Just press and hold the power button on it's own and see if anything happens

EddyOS said:
Just press and hold the power button on it's own and see if anything happens
Click to expand...
Click to collapse
Tried it, no avail. I think it's a hard brick, it's detected in my pc as in the screenshot. Any idea what to do?
Its not clear in the screenshot, it says Qualcomm HS-USB QDLoader 9008

n1234d said:
Tried it, no avail. I think it's a hard brick, it's detected in my pc as in the screenshot. Any idea what to do?
Its not clear in the screenshot, it says Qualcomm HS-USB QDLoader 9008
Click to expand...
Click to collapse
why did you use modified hboot now you are in serious trouble. As you are supercid download any ruu and try flashing and if your pc can connect via fastboot you can fix your phone. To check you must type in adb fastboot devices. if results are positive tell me i can help you then

hapticc said:
why did you use modified hboot now you are in serious trouble. As you are supercid download any ruu and try flashing and if your pc can connect via fastboot you can fix your phone. To check you must type in adb fastboot devices. if results are positive tell me i can help you then
Click to expand...
Click to collapse
I used a modded hboot to remove the red warning, have a look at this page (http://forum.xda-developers.com/showthread.php?t=2316726)
To do an RUU, I need to reboot in fastboot, but I can't even get the phone to charge.. Of course adb doesn't detect it..
Another point to note is that I rebooted several times after flashing the modded hboot, and it worked all those times, so this is just random... :'(

Why do people care about the red writing? Unless you're sending it to HTC for repair it makes no difference! It just leads to complications such as this

EddyOS said:
Why do people care about the red writing? Unless you're sending it to HTC for repair it makes no difference! It just leads to complications such as this
Click to expand...
Click to collapse
Well, 2 things
1: The process worked, ok? It's a perfect process to remove the red text, and the modded hboot also worked, I rebooted several times after flashing it.
2: The matter of the fact is that I am actually sending it in for camera replacement.. I guess I'll just tel them to replace the mobo along with it..
So, lets stop fighting like losers and find a way to get out of this situation! It'll help many people in the future
Sent from my iPod touch using Tapatalk

C'mon anybody? I can give more info if required, I'd prefer to know how to solve this myself, rather than relying on htc...
Sent from my iPod touch using Tapatalk

If it's not booting up , and you're stuck in that QDLOAD thing, it's usually the mainboard that's fried and HTC replaced the mainboard in my Sensation under the warranty when it happened to me. I was S-OFF at the time as well, and it came back 100% stock and working

n1234d said:
Well, 2 things
1: The process worked, ok? It's a perfect process to remove the red text, and the modded hboot also worked, I rebooted several times after flashing it.
2: The matter of the fact is that I am actually sending it in for camera replacement.. I guess I'll just tel them to replace the mobo along with it..
So, lets stop fighting like losers and find a way to get out of this situation! It'll help many people in the future
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
good luck buddy btw to remove tampered i just ran indian ruu

n1234d said:
C'mon anybody? I can give more info if required, I'd prefer to know how to solve this myself, rather than relying on htc...
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
I think most of the time, that's not something fixable unless by a service center. You may wanna check this thread: http://forum.xda-developers.com/showthread.php?t=2331454
For one guy the phone "magically" just started again, but I wouldn't hold my breath.
Sorry mate.

Ok, thanks for the info.. Maybe I'll make a strong case. My phone was originally replaced with a new one within a week because of battery problems, and scratch marks that I didn't make.. Then the second one had its mobo replaced for that same battery problem, and now I was going to send this in for replacement because my lower speaker is louder than the upper, and my camera has the dreaded pink tint and my phone has a big gap on its side where the service center guys hadn't closed the phone properly..and now this.. Oh boy, am I gonna make a strong case!!
Sent from my iPod touch using Tapatalk

nkk71 said:
I think most of the time, that's not something fixable unless by a service center. You may wanna check this thread: http://forum.xda-developers.com/showthread.php?t=2331454
For one guy the phone "magically" just started again, but I wouldn't hold my breath.
Sorry mate.
Click to expand...
Click to collapse
Yeah, I haven't got any alarms to save me now ;'/
But mine did get bricked randomly..
Sent from my iPod touch using Tapatalk

How about I try this?
http://unlimited.io/qhsusbdload.htm

As it doesn't mention the One I'd say no

EddyOS said:
As it doesn't mention the One I'd say no
Click to expand...
Click to collapse
Oh well, I went ahead and tried it anyways, but nothing happened.. So back to my good ol Nokia for now.. Btw, does rumrunner work with hboot 1.55??
Sent from my iPod touch using Tapatalk

Not yet, no

I bet we'll be seeing a lot more of these threads now...

Okay, although I've read a lot and I've learnt quite some bit, I want to know that if it wasn't the phone that unexpectedly died, was it my mistake somewhere? So I'll start with what I did, step by step, please have a look and tell me if I did anything wrong
1. Originally on ViperOne, tampered and unlocked on hboot 1.54
2. Restored stock nandroid 4.2.2 (2.24.707.3)(India) unrooted
3. Downloaded rumrunner (the version that I previously mentioned)
4. Started the exe
5. Phone reboots 2-3 times, process completes at pouring(3)
6. Reboot to verify s-off
7. Restore ViperOne nandroid
8. Run Revone to reset tampered flag
9. Flash modified hboot to remove warning.. Succeeds, reboot to verify warning gone
10. Reboot like 5-6 times to admire at the bootloader
11. I got a call and my phone hung
12. Reset the phone by holding power+vol down
Aaand the phone never booted again..
Sent from my iPod touch using Tapatalk

crixley said:
I bet we'll be seeing a lot more of these threads now...
Click to expand...
Click to collapse
Lol yeah.. I wouldn't think of myself as a total douche though, maybe I missed something..
Sent from my iPod touch using Tapatalk

Samsung Galaxy S3 mini is completely dead

Yesterday evening my phone was on the charger then it suddenly stopped and it is completely dead. It isn't showing any signs of life ever since, even if I charge it. It doesn't even show offline charging and I can't send it to Samsung as it's rooted so my warranty it VOID. It seems to me that it has Sudden Death Syndrome because it has been recently been switching off and now it's completely dead. What should I do? I'm pretty much screwed!

KoolKid98189 said:
Yesterday evening my phone was on the charger then it suddenly stopped and it is completely dead. It isn't showing any signs of life ever since, even if I charge it. It doesn't even show offline charging and I can't send it to Samsung as it's rooted so my warranty it VOID. It seems to me that it has Sudden Death Syndrome because it has been recently been switching off and now it's completely dead. What should I do? I'm pretty much screwed!
Click to expand...
Click to collapse
Can you enter download mode?

robintjeuuu said:
Can you enter download mode?
Click to expand...
Click to collapse
Well... I managed to just get it into offline charging. When I boot it up in normal mode it shows Samsung Galaxy S3 mini then after a few seconds the bottom lights flash for half a second and shut down. When I try to boot to recovery, model name then shut down. Yes it can just about make it into download mode.

KoolKid98189 said:
Well... I managed to just get it into offline charging. When I boot it up in normal mode it shows Samsung Galaxy S3 mini then after a few seconds the bottom lights flash for half a second and shut down. When I try to boot to recovery, model name then shut down. Yes it can just about make it into download mode.
Click to expand...
Click to collapse
If you get into download mode, go to sammobile en download the firmware for your phone and flash it with odin. if that worked, open stock recovery and do a fatory reset to make sure everything is back to stock... Then you can just hope it won't happen again.

robintjeuuu said:
If you get into download mode, go to sammobile en download the firmware for your phone and flash it with odin. if that worked, open stock recovery and do a fatory reset to make sure everything is back to stock... Then you can just hope it won't happen again.
Click to expand...
Click to collapse
I tried flashing stock recovery and ROM through Odin, it said pass but nothing actually seemed to fix and it still has the same problem that it shuts down after showing logo and when I boot to recovery it just shows TeamWin for a few seconds and shuts down so looks like I'm screwed and I have to use my BlackBerry :'(

KoolKid98189 said:
I tried flashing stock recovery and ROM through Odin, it said pass but nothing actually seemed to fix and it still has the same problem that it shuts down after showing logo and when I boot to recovery it just shows TeamWin for a few seconds and shuts down so looks like I'm screwed and I have to use my BlackBerry :'(
Click to expand...
Click to collapse
Ok, can't help you, maybe search this forum for unbrick device. I know there are fixes that can be used with some bricks.

robintjeuuu said:
Ok, can't help you, maybe search this forum for unbrick device. I know there are fixes that can be used with some bricks.
Click to expand...
Click to collapse
And I don't think Samsung will repair it as my warranty is void and I doubt if my parents would get me a new phone as this phone is only 3 months as well! And I have seen an unbrick thread and I tried it and it didn't work :'(

Well, I know how you feel. My charging port died once after I changed rom. Samsung asked me 200 for repair. Maybe you can give it a try and send him in... You never know Samsung loves you more than me..
Sent from my GT-I8190 using Tapatalk

robintjeuuu said:
Well, I know how you feel. My charging port died once after I changed rom. Samsung asked me 200 for repair. Maybe you can give it a try and send him in... You never know Samsung loves you more than me..
Sent from my GT-I8190 using Tapatalk
Click to expand...
Click to collapse
My dad took it to the service centre and they said they can't fix it as it's rooted so I'm screwed :'(

sunny296 said:
thanks,this index help me out very much.
Click to expand...
Click to collapse
What do you mean?

Zamoro1 said:
it is not samsung galaxy problem. it was your problem. you must close your downloading and other working while it is on charging.
Click to expand...
Click to collapse
It wasn't downloading anything?

Don't worry everyone I sent it to a repair shop (not Samsung) so I hope they manage to fix it.

Mine also dead
KoolKid98189 said:
Don't worry everyone I sent it to a repair shop (not Samsung) so I hope they manage to fix it.
Click to expand...
Click to collapse
Have you any news about the problem in your phone?
Mine (i8190 with one of the mclaws roms from previous week) also appeared in the morning shut down and there's no way of starting it. It does not even vibrate when power button pressed, as if the battery was completely empty.
Tried with another battery and checked that the original one had charge, but no luck. It does not start (normal, download or recovery, makes no difference).
Any ideas?

PelosBi said:
Have you any news about the problem in your phone?
Mine (i8190 with one of the mclaws roms from previous week) also appeared in the morning shut down and there's no way of starting it. It does not even vibrate when power button pressed, as if the battery was completely empty.
Tried with another battery and checked that the original one had charge, but no luck. It does not start (normal, download or recovery, makes no difference).
Any ideas?
Click to expand...
Click to collapse
Well mine was dead for a day then I plugged it into the charger (this was after a day and I left it on charge all night and it wouldn't start) and I held the power button for 10 seconds while it was on the charger it showed offline charging so I let it charge for a bit and then I powered it on and it seemed to be bricked so I sent it to a phone repair shop (not Samsung as my warranty is void). If it doesn't show any signs of life then it's bricked. If it comes to life then it is also probably bricked. I tried flashing many recoveries, ROMs, kernels and params and nothing happened.

In the S III Mini General forum there are topics about getting your phone back to stock so that it is covered by warranty.

james.faction said:
In the S III Mini General forum there are topics about getting your phone back to stock so that it is covered by warranty.
Click to expand...
Click to collapse
I tried to flash stock ROM and recovery but nothing actually worked!

1. Did you follow the instructions in detail?
2. What does "nothing actually worked!!" mean??
Maybe you need to work out what is the problem and why it is failing. Then you will be able to figure out if it is actually fixable, and if so how to fix it. "Trying everything" doesn't really work unless you make an effort to analyse the results you get every time you try something.
You could try posting in one of the threads about taking the phone back to stock. The people who posted them might be able to help you, they are more experienced at this sort of thing.

james.faction said:
1. Did you follow the instructions in detail?
2. What does "nothing actually worked!!" mean??
Maybe you need to work out what is the problem and why it is failing. Then you will be able to figure out if it is actually fixable, and if so how to fix it. "Trying everything" doesn't really work unless you make an effort to analyse the results you get every time you try something.
You could try posting in one of the threads about taking the phone back to stock. The people who posted them might be able to help you, they are more experienced at this sort of thing.
Click to expand...
Click to collapse
I tried those solutions and they didn't work.

Kid, can you read?
What did you try? What was the result?
"didn't work" isn't a result, it's you giving up. Without even trying to find out why it didn't work.

james.faction said:
Kid, can you read?
What did you try? What was the result?
"didn't work" isn't a result, it's you giving up. Without even trying to find out why it didn't work.
Click to expand...
Click to collapse
I read all instructions, and when I flashed it via Odin, nothing actually changed even with the params!

Gues Ibricked my stock phone.

Hello everyone!
Today I received my HTC One. I gues it is a demo phone. When I tried to get into bootloader it was all chinese. As I do not understood that language I tried to guess wich one was 'exit' pushed the last one in menu and it powered down. But now, when I turn it on, it vibrates, display blinks and nothing happens. When I hold volume up + power button it let's me choose between 4 boot options. Fastboot, normal boot, recovery mode, vart boot. Tried every option, but it still vibrates, blinks and nothing happens. Any ideas?

Cibulis said:
Hello everyone!
Today I received my HTC One. I gues it is a demo phone. When I tried to get into bootloader it was all chinese. As I do not understood that language I tried to guess wich one was 'exit' pushed the last one in menu and it powered down. But now, when I turn it on, it vibrates, display blinks and nothing happens. When I hold volume up + power button it let's me choose between 4 boot options. Fastboot, normal boot, recovery mode, vart boot. Tried every option, but it still vibrates, blinks and nothing happens. Any ideas?
Click to expand...
Click to collapse
do you have a photo?
I think you bought a fake unit

Sent from my HTC One using xda app-developers app

Cibulis said:
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
ok you bought a fake... I am very sorry for you. That has to be f*cking annoying. I think nobody can help you... but if you wanna take the risk of a hardbrick you might run through a RUU... but this will most likely hard brick your device...
Try this command here while in fastboot (use it on pc with cmd)
Code:
fastboot getvar all
If you don't know how to install fastboot... just google it
edit:
always quote or mention me so i get notified... otherwise i won't be able to answer you

dfjldfsljfs
LibertyMarine said:
ok you bought a fake... I am very sorry for you. That has to be f*cking annoying. I think nobody can help you... but if you wanna take the risk of a hardbrick you might run through a RUU... but this will most likely hard brick your device...
Try this command here while in fastboot (use it on pc with cmd)
Code:
fastboot getvar all
If you don't know how to install fastboot... just google it
edit:
always quote or mention me so i get notified... otherwise i won't be able to answer you
Click to expand...
Click to collapse
This is from fastboot

Cibulis said:
This is from fastboot
Click to expand...
Click to collapse
OMFG, that's horrible... I'm sorry for you.. that's really a fake unit and if you can't give it back and recieve the money back too... I'm sorry for you.. they cheated you.
I hope for you that you find some way to boot the device and that it works... but since it's not a HTC One I can't help you... The only thing I could do is to try try try again... but this is something everyone can do... so sorry mate..!
Good luck ! :good:
Edit:
Trying in this case means holding down several button combinations and selecting different options in the bootloader... Good luck !

Cibulis said:
This is from fastboot
Click to expand...
Click to collapse
I just googled HTT89_WE_JB2 and you do indeed have a clone IHTC One .. their was a rom that come up in the search though

After I hardbricked it, nothing was happening. Took the phone appart for fun. Removed battery, did some tricks with google help and after 24 my chinese phone now works. It is iHTC One as I understand now.
Sent from my HTC One using xda app-developers app

Red Triangle Stock Sense 6 update

Just received the stock update to Sense 6. I am in Canada, on Telus, fully stock.
When the phone boots into the recovery to flash the update, I am getting a red triangle and the error is unexpected contents in settings.apk
Any suggestions on how to get this update working other than hard resetting before the update?
Thanks.

Can you reboot normally? Just select the Reboot system option? Also, if it insists on going to update, hold power button to forcefully restart and keep pressing the volume down button to get into bootloader mode.
Try restart from there.
As you are FULLY stock (no root, should say LOCKED on that bootloader screen) you can either consider going through the warranty OR trying it yourself to fix by unlocking bootloader OR take it to someone locally.
Unfortunately all options will lead to data loss.

SaHiLzZ said:
Can you reboot normally? Just select the Reboot system option? Also, if it insists on going to update, hold power button to forcefully restart and keep pressing the volume down button to get into bootloader mode.
Try restart from there.
As you are FULLY stock (no root, should say LOCKED on that bootloader screen) you can either consider going through the warranty OR trying it yourself to fix by unlocking bootloader OR take it to someone locally.
Unfortunately all options will lead to data loss.
Click to expand...
Click to collapse
Yes it reboots and yes I have a locked bootloader. I would hard reset before sending it out for servicing.
Any other people having this issue?

mfpreach said:
Yes it reboots and yes I have a locked bootloader. I would hard reset before sending it out for servicing.
Any other people having this issue?
Click to expand...
Click to collapse
Not heard of a problem while updating. You are special.

What are your guys thoughts on flashing a stock ruu and then trying to ota to sense 6?

mfpreach said:
What are your guys thoughts on flashing a stock ruu and then trying to ota to sense 6?
Click to expand...
Click to collapse
Great idea!

mfpreach said:
What are your guys thoughts on flashing a stock ruu and then trying to ota to sense 6?
Click to expand...
Click to collapse
Did your problem solved?

Haha I haven't been able to try, on my 8.1 box I get an error 170 when trying to connect the phone in ruu. On my win7 box the ruu just auto closes....

mfpreach said:
Haha I haven't been able to try, on my 8.1 box I get an error 170 when trying to connect the phone in ruu. On my win7 box the ruu just auto closes....
Click to expand...
Click to collapse
well error 170 is either because your drivers aren't installed correctly or because you have a bad usb cable/port

alray said:
well error 170 is either because your drivers aren't installed correctly or because you have a bad usb cable/port
Click to expand...
Click to collapse
Thanks,I will look into it tomorrow.
Are there even good drivers for 8.1 yet bearing in mind I don't have a USB 3 port?

mfpreach said:
Thanks,I will look into it tomorrow.
Are there even good drivers for 8.1 yet bearing in mind I don't have a USB 3 port?
Click to expand...
Click to collapse
hi, we have similar issues although mine is the soundhound_freemium.apk instead of settings.apk, I hope that you will get your issue settled and also update me and the rest of us who are having the issues here. good luck and thanks! (do check out my thread which I've just posted like 5 minutes back!)

Do not install sense 6 upgrade
I would recommend NOT installing the stock Sense 6 upgrade. I installed it a couple days ago and currently my phone is bricked because of it.
I posted about my issue in another thread. In case people want to read what's been going on i'll repost it here.
Kg810 said:
So I performed the Sense 6 upgrade a couple days ago, update went through fine, yesterday morning my phone started acting all weird (sluggish, random reboots, bunch of apps reporting errors, etc) and battery was draining fast.
I probably rebooted my phone 10 times, 5 times normally by just the power button and the remaining times through the light trick, power button and volume button. Once my phone finally got back to normal, I was typing on whatsapp and then suddenly it froze.
It froze for a couple minutes and then it turned off. I believe the battery was at 39%. I plugged the phone into my work computer and it would make the USB connection sound, then after a few seconds it would display drivers failed to install followed by 3 subtle sounds similar to the connection sound. So right away I checked Device Manager and it displayed QHSUSB_DLOAD.
Currently my phone has been charging all night, currently it is being charged at work and there has been no sign of life.
I've tried putting it in the freezer, the light trick, the laptop connecting/disconnecting trick, and the go ole punching the phone trick. None of them have worked.
The phone is definitely not charging at this point as it is stone cold when I hold it or touch the wall charger.
Any ideas what I can do? I don't want to contact Rogers and have to send it in. I've got so many songs, videos and pictures I have yet to backup.
Any help and/or suggestions welcome.
Click to expand...
Click to collapse

Kg810 said:
I would recommend NOT installing the stock Sense 6 upgrade. I installed it a couple days ago and currently my phone is bricked because of it.
Click to expand...
Click to collapse
Well your issue have nothing to do with the sense 6 update. You even said that you have updated the phone a couple of days before your phone died. QHSUSB_DLOAD mode mean your phone motherboard is dead, either because of an hardware failure or because you have flashed something really wrong (probably not your case). So how an hardware failure could be caused by a sofware update and only occur days later....? unfortunately, you must send your phone for repair.
---------- Post added at 05:23 PM ---------- Previous post was at 05:22 PM ----------
mfpreach said:
Thanks,I will look into it tomorrow.
Are there even good drivers for 8.1 yet bearing in mind I don't have a USB 3 port?
Click to expand...
Click to collapse
if you have a win7 computer, then use that one.

alray said:
Well your issue have nothing to do with the sense 6 update. You even said that you have updated the phone a couple of days before your phone died. QHSUSB_DLOAD mode mean your phone motherboard is dead, either because of an hardware failure or because you have flashed something really wrong (probably not your case). So how an hardware failure could be caused by a sofware update and only occur days later....? unfortunately, you must send your phone for repair.
Click to expand...
Click to collapse
Maybe I wasn't clear.
Tuesday night before I went to bed I performed the upgrade.
Wednesday morning, is when the issues started occuring.
Today is May 29th, Tuesday was May 27th, which is 2 days ago, hence why I said I performed the upgrade a couple days ago.
From the time I performed the install Tuesday night to Wednesday morning when I got into work, there was nothing done to the phone. The only thing that was done was the Sense 6 upgrade.
So you're trying to tell me that the upgrade has nothing to do with it?

Kg810 said:
So you're trying to tell me that the upgrade has nothing to do with it?
Click to expand...
Click to collapse
If your phone was 100% stock, I highly doubt the ota could hard brick it.
like I said QHSUSB_DLOAD = defect motherboard
in most cases because:
1- hardware failure
or
2- Flashing something that screwed your phone (i.e flashing something not meant for your phone with S-OFF)
I'm not saying its impossible, but I think it's more a coincidence

alray said:
If your phone was 100% stock, I highly doubt the ota could hard brick it.
like I said QHSUSB_DLOAD = defect motherboard
in most cases because:
1- hardware failure
or
2- Flashing something that screwed your phone (i.e flashing something not meant for your phone with S-OFF)
I'm not saying its impossible, but I think it's more a coincidence
Click to expand...
Click to collapse
I've had the phone for a little over a year and it has been 100% stock. Never tinkered with it in any way shape or form.
I just can't see how it is a mere coincidence that right after the update, my phone starts acting up, and then becomes bricked.

Kg810 said:
I've had the phone for a little over a year and it has been 100% stock. Never tinkered with it in any way shape or form.
I just can't see how it is a mere coincidence that right after the update, my phone starts acting up, and then becomes bricked.
Click to expand...
Click to collapse
Anyway, your only way out of this qhsusb brick is to send your phone for repair.
Sorry

mfpreach said:
Yes it reboots and yes I have a locked bootloader. I would hard reset before sending it out for servicing.
Any other people having this issue?
Click to expand...
Click to collapse
facing same problem with you. my problem haven't fix. from malaysia

akasi91 said:
facing same problem with you. my problem haven't fix. from malaysia
Click to expand...
Click to collapse
From Malaysia as well, hey mind telling me how big is your sense 6 update download size?

kuzumitaiga said:
From Malaysia as well, hey mind telling me how big is your sense 6 update download size?
Click to expand...
Click to collapse
6xxmb.

unable to boot in recovery

Hi, can anyone please point me to the correct method for booting in recovery? All the volume up/down+power key combinations do not work for me.
Thanks.

gbmolina said:
Hi, can anyone please point me to the correct method for booting in recovery? All the volume up/down+power key combinations do not work for me.
Thanks.
Click to expand...
Click to collapse
Hi how are things.
do you have root?
Magisk?
if you have magisk, from there you can start.

No root, obviously, otherwise there is a ton of apps for booting in recovery.

gbmolina said:
No root, obviously, otherwise there is a ton of apps for booting in recovery.
Click to expand...
Click to collapse
I understand that the equipment must be turned off.
1.connect usb cable to pc.
2.connect cable to s20 fe.
(wait for the battery percentage to appear.
3. press volume + and power at the same time (it will turn off after 2 seconds, keep pressing, until the s20 logo appears
4. done.

Thank you, worked like a charm. This is new, I mean, the connection to the PC. Thanks again.

gbmolina said:
Thank you, worked like a charm. This is new, I mean, the connection to the PC. Thanks again.
Click to expand...
Click to collapse
If you want to be root at some point.
Magiks application has the option to reboot in recovery mode.
excellent day .

Hi guys, I have the exact same problem (no root, Android 13 update from 1st of March) and your solution doesn't work. It doesn't want to go into recovery or download mode whatever combinations I try. Do you have any advices?

yabol708 said:
Hi guys, I have the exact same problem (no root, Android 13 update from 1st of March) and your solution doesn't work. It doesn't want to go into recovery or download mode whatever combinations I try. Do you have any advices?
Click to expand...
Click to collapse
if your team is business, it will not work.
There are variants that are blocked by companies.
If that's your case, you can't this way.
Several teams have already passed with that detail.

mezacorleehone said:
if your team is business, it will not work.
There are variants that are blocked by companies.
If that's your case, you can't this way.
Several teams have already passed with that detail.
Click to expand...
Click to collapse
No, it is and it was a personnal one. Unless you mean blocked by mobile operator.

yabol708 said:
No, it is and it was a personnal one. Unless you mean blocked by mobile operator.
Click to expand...
Click to collapse
There are teams that your work gives you. (companies, corporations, etc.)
They send to ask for the equipment with Samsung, they block the access to recovery and download.
In my repair shop, Samsung equipment arrives with that block.
In your case, you say that it is not business, I don't know what causes your problem.

yabol708 said:
No, it is and it was a personnal one. Unless you mean blocked by mobile operator.
Click to expand...
Click to collapse
keep trying
I put the cable into the PC, halfway plug the cable into the phone while it's turned off. then I start holding volume up plus power for recovery and then push the cable all the way into the phone immediately after.

Ok. Thank you both for the help. I'll try this method as well.

Found out why the recovery mode didn't want to turn on. The cable was just for charging :/ Plugged in another one and it worked like a charm. Thanks for all the help guys.

I just joined. I can not see where I start a new thread to ask a question.
Can someone direct me?
BTW - My problem is I installed Fire Toolbox, It ran once and now only open a gray box on the sceen and freezes. Rebooted , uninstalled - reinstalled, tried diff versions...?