Related
My VZW rooted 4.4.4 GS5 decided to shut off, and reboot into recovery. Had TWRP with SS installed about 3 weeks ago, and all was working EXCELLENT, without any problems. I've been using this thing rooted and debloated for about 2 or more years. I have never tried to install any other custom ROMs. All I did was debloat the VZW crap off of it. I tried SS in the past, but it did not seem to do anything, so I uninstalled it, so I thought.
It appears as though through recovery, that it has been wiped.
The ROM installed was the 4.4.4, which all I wanted to do was debloat a couple years ago, which I did. Now the phone seems to have taken a crap, and I can't seem to get it to do anything. There is probably about 70% battery to play with. I can get it booted to recovery, but nothing else. I attempted to sideload the 4.4.4 firmware, but was unsuccessful. Maybe I don't know what I am doing. When I originally rooted, I used Odin to downgrade to 4.4.4, per instructions I found. But now, I don't know what to do.
Can someone please hold my hand here, and PM or email me so I can get this phone up and running again? This is both my personal and business phone. Please PM me, or email to [email protected]
Thank you.
Can you get into Download mode? If so, from there you should be able to Odin flash firmware located at sammobile's site.
Beeko said:
Can you get into Download mode? If so, from there you should be able to Odin flash firmware located at sammobile's site.
Click to expand...
Click to collapse
It will boot to Recovery mode, and give me the options to install via ADB, from external, etc. Not sure if I know exactly what you are meaning by d/l mode.
It obviously does not boot normally.
When it boots to recovery, my options are reboot system, apply update from 1. ADB, 2. External, 3. Cache, or the two wipe options.
That is as far as it will go now.
Just put batt back in, connected USB cord from PC and tried to boot. Up top, in red Secure Fail: Recovery. Then a msg on the screen. System software not authorized by VZW has been found on your phone. Please turn off and go to a VZW store for help.
When it does turn on, it goes to the Samsung screen and says Custom, with the unlocked padlock. It has displayed that since the day I rooted, back about two years ago, but has always booted through.
Now it is going back to Recovery, and gives me those 5 previous options for installing / recovery. But that's where I am stuck, and need a little (a lot) of expertise and guidance.
Pull battery, put battery back in , then hold power, volume down and home at same time. If it boots to download mode then use Odin
johnnycooper said:
Pull battery, put battery back in , then hold power, volume down and home at same time. If it boots to download mode then use Odin
Click to expand...
Click to collapse
I don't think it boots to d/l mode. It boots to Recovery, then gives me the options that I previously listed; ABD, External, or cache. I don't believe that ADB is d/l mode, is it?
johnnycooper said:
Pull battery, put battery back in , then hold power, volume down and home at same time. If it boots to download mode then use Odin
Click to expand...
Click to collapse
It only boots to recovery.
You tried to boot to download mode with battery pulled - volume down, power, home button?
johnnycooper said:
Pull battery, put battery back in , then hold power, volume down and home at same time. If it boots to download mode then use Odin
Click to expand...
Click to collapse
johnnycooper said:
You tried to boot to download mode with battery pulled - volume down, power, home button?
Click to expand...
Click to collapse
Okay, now it seems like I 'might' be getting somewhere. Yes, now the battery is OUT, and it did boot to ODIN, and I think it might be doing something. See?, need the hand holding. Will update, in a bit to see if this works. Thank you!
The phone says it's d/l, but there doesn't seem to be much happening on the ODIN screen.
You have to have usb hooked to pc , open Odin on pc. Then press up on phone then load factory tar to Odin
---------- Post added at 10:36 PM ---------- Previous post was at 10:33 PM ----------
Go here and read the part that days prepare your phone after #9
http://forum.xda-developers.com/showthread.php?t=3290370
Working Root Method For 5.0 Lollipop Roms [OE1] [OG5] [OK3] [PB1] [3-3-16]
Okay, it went through what appeared to be an install, then it showed that it was upgrading, through 145, did a reboot, but now all it is doing is turning on and off, showing the GS5 screen with the Custom padlock logo.
Pull battery , boot to recovery, wipe cache. If that dont work, start over
boblpn said:
Okay, it went through what appeared to be an install, then it showed that it was upgrading, through 145, did a reboot, but now all it is doing is turning on and off, showing the GS5 screen with the Custom padlock logo.
Click to expand...
Click to collapse
It prepared the phone, rebooted, showed the red VZW screen, and now seems to be stuck in a boot loop. I have done a battery pull, and rebooted, but still stuck in a loop.
Should I try installing a different ROM? If yes, which one? Can you provide a link?
boblpn said:
Should I try installing a different ROM? If yes, which one? Can you provide a link?
Click to expand...
Click to collapse
Already did, it's in the link
question..What if he ONLY wants to go back to his KK 4.4...all he has to do is ODIN the NCG, towelroot, install SuperSU and then flash the 4.4 and he'll be back...what is being offered may not be what he wants and then may not go back to KK if he so desires...you got to give and explain to users what will happen if done...
If you can get to DL mode, Run Odin as admin on your PC and then load up whatever stock firmware you want from HERE.
He can use this thread here which could be helpful as well. http://forum.xda-developers.com/showthread.php?p=53447942#post53447942
boblpn said:
The phone says it's d/l, but there doesn't seem to be much happening on the ODIN screen.
Click to expand...
Click to collapse
It won't download anything unless you push it using Odin. Boot into recovery and give me the build number at the top. Then we can find the factory firmware to push with Odin in download mode.
Pixel not powering on, I flashed TWRP 3.2.1.2 and tried to flash superuser 2.82 SR5. Superuser never installed but the phone seemed to be working fine, I went back into twrp a few times and everything seemed fine. So i was trying to bootback into twrp one more time to try and install supersu from otg usb drive and just after selecting recovery mode it shut down and now it will not power back on?? any help from anyone, I tired plugging it into the wall and it does not seem to power on at all or even charge. Thanks in a advance for any help!
I had an issue like this. Hold down the power button and down volume button at the same time. Keep holding it down. It took 20-30 seconds for me.
By the way, what version of Android are you on? SuperSU won't work on Android 8.1. You have to use Magisk. You can use the latest Magisk but if you want to use @Chainfire's FlashFire app, you have to use Magisk v14.2.
I think flashing SuperSU is what broke your ****. Try flashing SuperSU uninstaller and then reboot into recovery and flash magisk
KittyRgnarok said:
I think flashing SuperSU is what broke your ****. Try flashing SuperSU uninstaller and then reboot into recovery and flash magisk
Click to expand...
Click to collapse
His phone won't turn on lol
shagbag913 said:
His phone won't turn on lol
Click to expand...
Click to collapse
He didn't give any details as to what he means by won't turn on. To me that means system isn't working and bootloader and recovery are intact. Your phone doesn't need to boot properly to flash a zip
KittyRgnarok said:
He didn't give any details as to what he means by won't turn on. To me that means system isn't working and bootloader and recovery are intact. Your phone doesn't need to boot properly to flash a zip
Click to expand...
Click to collapse
He said his phone will not power on. He also said he plugged it in and It still wouldn't power on. It sounds to me that his phone won't power on lol.
shagbag913 said:
He said his phone will not power on. He also said he plugged it in and It still wouldn't power on. It sounds to me that his phone won't power on lol.
Click to expand...
Click to collapse
Look at you being helpful and contributing to the thread. Would you rather me suggest literally nothing like you or assume that he is under recoverable circumstances and provide a potentially simple fix? He has not indicated whether he has tried to boot fastboot or recovery.
KittyRgnarok said:
Look at you being helpful and contributing to the thread. Would you rather me suggest literally nothing like you or assume that he is under recoverable circumstances and provide a potentially simple fix? He has not indicated whether he has tried to boot fastboot or recovery.
Click to expand...
Click to collapse
"So i was trying to bootback into twrp one more time to try and install supersu from otg usb drive and just after selecting recovery mode it shut down and now it will not power back on??"
---------- Post added at 11:51 PM ---------- Previous post was at 11:47 PM ----------
Aphex^ said:
Pixel not powering on, I flashed TWRP 3.2.1.2 and tried to flash superuser 2.82 SR5. Superuser never installed but the phone seemed to be working fine, I went back into twrp a few times and everything seemed fine. So i was trying to bootback into twrp one more time to try and install supersu from otg usb drive and just after selecting recovery mode it shut down and now it will not power back on?? any help from anyone, I tired plugging it into the wall and it does not seem to power on at all or even charge. Thanks in a advance for any help!
Click to expand...
Click to collapse
I would try holding the power button for a good 5 mins, some say that can turn it back on. If that doesn't work plug it into a PC and look to see what its name is on your PC. If it says "Qualcomm HS-USB QDLoader 9008", unfortunately its hard bricked.
Actually
KittyRgnarok said:
Look at you being helpful and contributing to the thread. Would you rather me suggest literally nothing like you or assume that he is under recoverable circumstances and provide a potentially simple fix? He has not indicated whether he has tried to boot fastboot or recovery.
Click to expand...
Click to collapse
Your actually are talking about the problem I just did a couple of hours ago...I was so mad...Like WTH did I do wrong. THANK YOU FOR YOUR HELP
Hello everyone,
If you are trying to flash TWRP to an android oreo 8.1 google pixel, it will not work, so DON'T ATTEMPT IT! I have tried this before and your best bet as of now is to flash the bootloader back to stock. If you need to use it for whatever reason just fastboot into it.
Also, SuperSU doesn't work with Android 8.1 Oreo, as it isn't compatible. The new method is using Magisk Manager.
If you can't turn on your phone, then this means your bootloader is completely damaged and you will need to replace your phone.
mcbeat257 said:
Hello everyone,
If you are trying to flash TWRP to an android oreo 8.1 google pixel, it will not work, so DON'T ATTEMPT IT! I have tried this before and your best bet as of now is to flash the bootloader back to stock. If you need to use it for whatever reason just fastboot into it.
Also, SuperSU doesn't work with Android 8.1 Oreo, as it isn't compatible. The new method is using Magisk Manager.
If you can't turn on your phone, then this means your bootloader is completely damaged and you will need to replace your phone.
Click to expand...
Click to collapse
You definitely can flash twrp on an 8.1 pixel. I have it right now. Also, most of the time that does mean it is hard bricked, but sometimes these phones can trick you. If you think your phone is bricked because the screen is off and there is no response, hold the power button down for 1 to 2 minutes, SOMETIMES it can come back on.
I had a similar issue where the phone would not turn on after I was loading TWRP via Fastboot. I went to sleep that night thinking I had bricked it. Held every button down for at least 90 seconds and every combination of buttons. Woke up in the morning to try it one more time before I gave up and it easily booted up but only had 1% battery. I had charged it fully before trying to load TWRP. I plugged it in and charged it and was good to go including Fastboot booting into TWRP and then flashing SuperSu and the Xposed framework. Both work fine. Rooted and using Xposed modules.
I came here to see if I could flash TWRP to the phone. Apparently I can, but would love to know what the steps are so as not to screw anything up or mess up which partition, etc.
What the freak did I just read. Seems to me the issue is not twrp but whatever people are trying to flash using twrp. @mcbeat257 TWRP works just fine. Been running the latest for several months now. Works on 8.1 both stock and custom roms, even on Android P DP2. So If you can't make it work while several others users have then I would say you're not eligible to give advice as to say "do not attempt it!". You must be doing something wrong. Please stop spreading false information. I'd be happy to help you out if you describe the procedure you've been going about to flash it to make it work.
As to the OP, try as shagbag913 told you to do. Press the power button for some minutes. Or try power-button+volume down (See if you manage to get into the bootloader menu). If it doesn't work then connect your device to your computer and see if it's recognized. If it's flat dead and won't turn on then motherboard might be toast. If it's recognized as shagbag913 said as a Qualcomm HS-USB QDLoader 9008 then it's hardbricked.
---------- Post added at 01:59 PM ---------- Previous post was at 01:39 PM ----------
724A said:
I had a similar issue where the phone would not turn on after I was loading TWRP via Fastboot. I went to sleep that night thinking I had bricked it. Held every button down for at least 90 seconds and every combination of buttons. Woke up in the morning to try it one more time before I gave up and it easily booted up but only had 1% battery. I had charged it fully before trying to load TWRP. I plugged it in and charged it and was good to go including Fastboot booting into TWRP and then flashing SuperSu and the Xposed framework. Both work fine. Rooted and using Xposed modules.
I came here to see if I could flash TWRP to the phone. Apparently I can, but would love to know what the steps are so as not to screw anything up or mess up which partition, etc.
Click to expand...
Click to collapse
There is an entire thread for twrp and how to flash: https://forum.xda-developers.com/pixel/development/twrp-alpha1-pixel-devices-t3500314
My Galaxy S7 (SM-G930R4) has decided to not want to boot. I can't boot normally or into recovery. I can only boot into Odin mode.
I've tried to flash stock rom, but it doesn't seem to work. I've heard that I should use the ROM from samsmobile, so I'll try that next.
This all started to happen after I accidentally turned on the phone right before I took the battery out. I put that battery back in and it booted fine, but after a few minutes it rebooted and started to reboot over and over again. It won't even show the charging screen when it is turned off and plugged in.
OK, I tried to flash the stock rom with Odin, but it still is in a boot loop. I've flashed it 3 times. I've firmware files from different sites. It seems that this S7 is dead. Please help!
Try to flash another rom and keep in mind that it sometimes takes up to 10-15 minutes at the first boot.
You could also just flash TWRP...
ATP-Flo said:
Try to flash another rom and keep in mind that it sometimes takes up to 10-15 minutes at the first boot.
You could also just flash TWRP...
Click to expand...
Click to collapse
TWRP for the Samsung Galaxy S7 (SM-G930R4)???
Also, now I've been greeted with the screen that says "An error has occurred while updating the device software." It says to use the Samsung Smart Switch PC software to fix it. Hopefully that works.
Where are you?
What firmware are you using? Branded or unbranded?
Have you looked on Sammobile for the correct firmware?
Are you able to boot into system recovery? Home+VOLUME UP+Power (Not Download)?
Oh you have got the G930R4. I thought G930F.
Then I don't know if there is a TWRP you could flash.
But if there is one you could just flash it and enter recovery mode and install a new ROM from within the TWRP environment.
Check this out.
https://dl.twrp.me/herolte/
Sounds like your device is currently bricked anyways, so just give it a try.
Maybe you can get a working TWRP recovery mode again.
Also check these links:
http://www.techzai.com/root-galaxy-s7-s7-edge-android-8-0/
and
https://twrp.me/samsung/samsunggalaxys7.html
cooltt said:
Where are you?
What firmware are you using? Branded or unbranded?
Have you looked on Sammobile for the correct firmware?
Are you able to boot into system recovery? Home+VOLUME UP+Power (Not Download)?
Click to expand...
Click to collapse
I am in the US.
I'm on Android 8.0 (Oreo)
I have a US Cellular Branded phone.
As soon as the phone is turned on, it tries to boot into recovery, but it can't so it keeps on trying over and over again. I've tried the firmware from SamMobile, but nothing seems to work.
When I flash to Stock ROM, and I turn the phone on, it stays in a bootloop of the "Recovery Booting..." screen.
When I flash the rooted Engineering rom, and I turn the phone on, it stays in a bootloop of the Samsung S7 logo. I can't boot into safe mode.
I tried to use Samsung Kies... didn't work... I tried to use Samsung Smart Switch... didn't work... I've tried 3 or 4 different ROMs from different websites.... didn't work.
i have the same problem. was able to enter download mode several times, but at some point it died completely (not charging anymore). how do you manage to take the battery out? does the SM-G930R4 the possibility to easily remove it?
Cloud2F said:
i have the same problem. was able to enter download mode several times, but at some point it died completely (not charging anymore). how do you manage to take the battery out? does the SM-G930R4 the possibility to easily remove it?
Click to expand...
Click to collapse
The glass panel on the back is glued onto the phone. If you remove the glass, there are screws and from there, it's easy. I broke the glass in the process... so yay me.
Mine won't charge either. It is completely dead, but it will still turn on when I plug it into my computer.
Really strange. Mine is not turning on, even tried several locations, charger, etc. Once I had download mode while having a black screen. Keep an eye on odin and instantly flash firmware if it got recognized. I press all three buttons while plugging in; that's how it worked the first time for me....
Looking for some help please! My phone battery died the other day, I plugged it in to charge and turned it on at 3% battery life only to get stuck in a boot loop.
Did a factory reset and then successfully flashed with odin and current firmware G930TUVS9CSC1. After flashing it went to installing a system update screen only getting to about 32%, then it said erasing for a while and went back to the samsung startup screen stuck in apparently the same boot loop I started with.
Is my phone screwed or did I miss something? looking for any help, thanks.
vexcesban said:
Looking for some help please! My phone battery died the other day, I plugged it in to charge and turned it on at 3% battery life only to get stuck in a boot loop.
Did a factory reset and then successfully flashed with odin and current firmware G930TUVS9CSC1. After flashing it went to installing a system update screen only getting to about 32%, then it said erasing for a while and went back to the samsung startup screen stuck in apparently the same boot loop I started with.
Is my phone screwed or did I miss something? looking for any help, thanks.
Click to expand...
Click to collapse
It sometimes does this, make sure the firmware your using is correct for your device and flash again.
UNCHECK "auto reboot" in Odin
Disconnect when flash complete Do Not Turn The Phone On
Reboot into recovery volume up+home+power
Wipe cache/factory rest
Reboot
cooltt said:
It sometimes does this, make sure the firmware your using is correct for your device and flash again.
UNCHECK "auto reboot" in Odin
Disconnect when flash complete Do Not Turn The Phone On
Reboot into recovery volume up+home+power
Wipe cache/factory rest
Reboot
Click to expand...
Click to collapse
Thanks. Appreciate the input, but it didn't work for me after trying it twice. I am positive I have the right firmware.
It boots up with no led indicating light and continues to just flash the opening samsung screen for eternity.
Got the phone to boot up normally but now it wont read my sim card. sim works in my other phone. Any ideas?
vexcesban said:
Got the phone to boot up normally but now it wont read my sim card. sim works in my other phone. Any ideas?
Click to expand...
Click to collapse
SIM reader on phone, blow into hole to dislodge any dust and make sure sim is flat in adapter. Very rarely a software problem with sim not read.
cooltt said:
SIM reader on phone, blow into hole to dislodge any dust and make sure sim is flat in adapter. Very rarely a software problem with sim not read.
Click to expand...
Click to collapse
interesting, it worked fine before this started 2 days ago. I guess maybe the sim card reader broke? theres definitely no dirt in there and it seems to make a good connection (tried a new sim card had lying around and it etched lines into the sim card nicely).
Also I should mention that I had no clue what I was doing and flashed a dozen or so different versions of firmwares probably like 20 times, so maybe I caused it.
vexcesban said:
interesting, it worked fine before this started 2 days ago. I guess maybe the sim card reader broke? theres definitely no dirt in there and it seems to make a good connection (tried a new sim card had lying around and it etched lines into the sim card nicely).
Also I should mention that I had no clue what I was doing and flashed a dozen or so different versions of firmwares probably like 20 times, so maybe I caused it.
Click to expand...
Click to collapse
Er.... Yes!
You have to flash the correct region firmware for your device or you end up with problems like you have.
Search for the SamFirm tool on here it's great for getting the correct firmware direct from Samsung servers.
cooltt said:
Er.... Yes!
You have to flash the correct region firmware for your device or you end up with problems like you have.
Search for the SamFirm tool on here it's great for getting the correct firmware direct from Samsung servers.
Click to expand...
Click to collapse
Okay well that tool's forum post says it's deprecated so I followed the alternative link to updato and got stock 8.0 from there. Flashed phone, everything works 100% but still no sim detected.
I'm wondering If I broke my phone because I even tried some custom rom with a pit file and probably did that wrong as well.
vexcesban said:
Okay well that tool's forum post says it's deprecated so I followed the alternative link to updato and got stock 8.0 from there. Flashed phone, everything works 100% but still no sim detected.
I'm wondering If I broke my phone because I even tried some custom rom with a pit file and probably did that wrong as well.
Click to expand...
Click to collapse
PIT won't do anything to SIM.
Try all of these
Hey i am having the same problem odin flash with succes but the phone still only shows the first samsung glaxy s7 screen and then reboots.
Also i cant acces recovery.
i have the same problem
Huzalio said:
Hey i am having the same problem odin flash with succes but the phone still only shows the first samsung glaxy s7 screen and then reboots.
Also i cant acces recovery.
Click to expand...
Click to collapse
hi, did you find a way to fix it?
@cooltt I made an account here in order to thank you! I was stuck in a boot loop after flashing a stock ROM and your advice saved my phone. I thought I bricked it!!
q-l-p said:
@cooltt I made an account here in order to thank you! I was stuck in a boot loop after flashing a stock ROM and your advice saved my phone. I thought I bricked it!!
Click to expand...
Click to collapse
Glad I could help
cooltt said:
It sometimes does this, make sure the firmware your using is correct for your device and flash again.
UNCHECK "auto reboot" in Odin
Disconnect when flash complete Do Not Turn The Phone On
Reboot into recovery volume up+home+power
Wipe cache/factory rest
Reboot
Click to expand...
Click to collapse
I'm having this same issue but it won't boot into recovery at all, I don't know what to do.
iroveashe said:
I'm having this same issue but it won't boot into recovery at all, I don't know what to do.
Click to expand...
Click to collapse
First MAKE SURE you are flashing correct firmware for your device.
What device do you have and what country?
If you are sure it's correct. Flash again with Odin but uncheck "auto reboot" in options.
When pass appears just disconnect phone, it doesn't matter what it shows on the screen.
In this sequence press and hold the following... Volume down+home+power.
As soon as the screen goes black move your finger to Volume up while still pressing home+power. It may take several attempts.
When recovery menu appears wipe cache partition then reboot.
Leave phone go through boot sequence, ignore what appears on the screen during this time it is normal. This boot should take around 5 minutes.
EDIT: FIXED, I did what you did, but for that to work I had to flash it without the hidden.img. Then it rebooted and got stuck on the logo again, but i was able to boot into recovery. Thank you so much.
cooltt said:
First MAKE SURE you are flashing correct firmware for your device.
What device do you have and what country?
Click to expand...
Click to collapse
Hey, thank you for responding.
I'm not 100% sure it's the right one
Device: Samsung A510M
Country: Argentina
Carrier: Personal
I downloaded a firmware from sammobile matching those specifications, but it fails at the last step with hidden.img.
This morning I downloaded another firmware through samfirm, but that one fails at modem.img instead.
I will try your instructions with either of them.
---------- Post added at 07:01 PM ---------- Previous post was at 06:06 PM ----------
cooltt said:
As soon as the screen goes black move your finger to Volume up while still pressing home+power. It may take several attempts.
Click to expand...
Click to collapse
To be clear, I only need to repeat this part of the process, not reinstall the firmware every time, correct? I've been trying to do this for a while, but it just shows:
"An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
So i updated my phone automatically yesterday from the latest update, after it was done, i haven't been able to access my phone in anyway, it keeps on looping samsung logo and a window that says "This phone's bootloader is unlocked´and its software integrity can't be verified" and so on, ive tried to enter either Download mode and recovery mode, but none of the methods seems to have an affect on the phone at all, please help, thanks
Hmm if u have PC download Smart Switch and do Emergency Firmware recovery. That should fix it totally.
FakerS3 said:
Hmm if u have PC download Smart Switch and do Emergency Firmware recovery. That should fix it totally.
Click to expand...
Click to collapse
- The phone does not show up on the pc either
Was your phone rooted? That could explain it.
riggerman0421 said:
Was your phone rooted? That could explain it.
Click to expand...
Click to collapse
Yes
thorius95 said:
Yes
Click to expand...
Click to collapse
Same issue here. s10e stuck in boot loop (between samsung logo and warning about the bootloader being unlocked) after yesterday's update.
So far I had no success putting the phone into recovery or download mode.
The phone was rooted, then flashed with custom ROM, then flashed again with stock firmware. I kept the bootloader unlocked because I read it was risky to re-lock the bootloader.
So, is it now hopelessly bricked?
chibuche said:
Same issue here. s10e stuck in boot loop (between samsung logo and warning about the bootloader being unlocked) after yesterday's update.
So far I had no success putting the phone into recovery or download mode.
The phone was rooted, then flashed with custom ROM, then flashed again with stock firmware. I kept the bootloader unlocked because I read it was risky to re-lock the bootloader.
So, is it now hopelessly bricked?
Click to expand...
Click to collapse
Thats a good question, far as i know, my phone is unable to get any form of connection to the pc, not able to start up in recovery or download mode either. What i know for sure, there is a way out, we just have to find the way
Never attempt to update if you have rooted and made any changes to the system, deleted or added system apps, modified kernel, changed boot logo,etc.
thorius95 said:
Thats a good question, far as i know, my phone is unable to get any form of connection to the pc, not able to start up in recovery or download mode either. What i know for sure, there is a way out, we just have to find the way
Click to expand...
Click to collapse
So, here's how I put the phone in download mode.
I left the battery to drain completely, then without pressing the power button, I pressed the volume down and Bixby button; and only then I plugged the cable. Without pressing the power button, the phone started straight into Download mode.
Now Odin sees the phone, I'm about to flash it with the stock firmware and see what happens.
thorius95 said:
Thats a good question, far as i know, my phone is unable to get any form of connection to the pc, not able to start up in recovery or download mode either. What i know for sure, there is a way out, we just have to find the way
Click to expand...
Click to collapse
Maybe this thread helps: https://forum.xda-developers.com/galaxy-s10/help/galaxy-s10-bootloop-updte-to-android-10-t4023201
It's probably Samsung's vaultkeeper that caused the bootloop.
thorius95 said:
Thats a good question, far as i know, my phone is unable to get any form of connection to the pc, not able to start up in recovery or download mode either. What i know for sure, there is a way out, we just have to find the way
Click to expand...
Click to collapse
I just wanted to give an update of how I rescued my phone and kept all the information on the phone memory intact (this was one of the challenges, as I had some photos on it).
I put it in download mode by draining the battery, then tried to flash the updated firmware. It didn't work, leading once again to boot loop and all I could do was boot to the stock Android recovery - not helpful.
So I got it to download mode again and flashed the stock firmware it originally came with (prior to the update). In Odin, I put HOME_CSC in the CSC field, to keep the phone memory from being erased. This solved it.
Hope this info can help someone having the same issue.