Soft Brick - I don't know what to try anymore - S6 - SM-G920I - Galaxy S6 Q&A, Help & Troubleshooting

Hello partners. I'm new to the forum, so please, if you are using a term I don't know let me know.
So, this all started back in December. I flashed my S6 (SM-G920I) with Nougat 7.0 and all went really good.
And a few days ago I decided that I wanted to try to install Oreo 8.0 from Nexus Team (https://forum.xda-developers.com/ga...nt/g92xx-android-o-samsung-galaxy-s6-t3663901)
I did it, although the post specifically said that they didn't know if my device was supported.
I'll guide you through the steps I made.
1 - I updated TWRP (As I hadn't done it since December)
2 - I flashed the Oreo ROM (All went well, but I didn't erase data)
3 - I think this is an error based in the fact that I hand't erased the data: My phone got stuck at the Oreo loading screen.
4 - I tried to get to recovery so I could erase all the things I'd forgotten and flash again.
5 - I can't enter recovery mode - Somehow it got troubled with the OS, and I can't acces to it anymore.
6 - I say "Well, maybe I can try downloading Android 7.0 and flashing through Odin"
7 - I did, but as I'm not able to erase data, it got conflicted again. Now stuck at Samsung logo.
So, I can enter download mode, but I can't enter any other mode (Bootloader, Recovery) to erase the data that has been left from other OSes (Now like three different ones).
I just don't know what to do. I can't get my phone to a technician till Monday, so that's the time I have to try and figure it out. Now I'm downloading the Android Studio, but I think it doesn't matter much because I can't enter to the bootloader mode.
I swear, I'm so frustrated not being able to do anything. I'm not that much of a mobile person, I'm more from PC, I'm pretty new in this "Flashing" community, so that's why I made a huge mistake by not erasing the data.
So TL;DR: Didn't erase data, soft bricked, can't enter recovery or bootloader, only download mode. Phone stuck at Samsung loading logo.
Hope you can help guys, as I don't know what to do anymore.
Thanks beforehand.

Flash G920FXXU5EQH6_G920FXEO5EQH2_XEO via Odin

masterofreal said:
Flash G920FXXU5EQH6_G920FXEO5EQH2_XEO via Odin
Click to expand...
Click to collapse
But isn't that rom for a G920F? Mine is a G920I

Just install again the recovery through download mode and then erase all your data

Glackstone said:
But isn't that rom for a G920F? Mine is a G920I
Click to expand...
Click to collapse
G920F/G920I are the same. Both international, I is just Australia/Oceania

dargon17 said:
Just install again the recovery through download mode and then erase all your data
Click to expand...
Click to collapse
I did it. I installed last TWRP version, but I can't access Recovery through Vol. Down + Home + Power. Not either can I force it through ADB 'cause USB Debugging is off.
Visera said:
G920F/G920I are the same. Both international, I is just Australia/Oceania
Click to expand...
Click to collapse
Ok, I'll try, I have till Monday to figure something out.

Related

Samsung Galaxy S7 Bootloop/Recovery Mode

Model: SM-G930T (T-Mobile USA)
So today, I had an app not responding. I tried restarting my phone only to get stuck in a bootloop. My Recovery Mode isn't able to boot, but I can still access Download Mode. I tried to install the stock rom for my device to get the error with
"SW rev check failed FUSED 3 > BINARY 2"
"EMMC WRITE FAILED"
I'm thinking of trying to install the stock recovery, but apparently, I have to reinstall the stock rom, which I already did.
Thank you for taking your time to read this.
I have a ton of issues with my s7. Samsung's smart switch has saved the day several times.
Download it and give it a shot:
http://www.samsung.com/us/smart-switch/
Smart Switch quick-tut.
Start as admin
More (At top)
Emergeny
Device init
enter model , s/n search
localh85 said:
I have a ton of issues with my s7. Samsung's smart switch has saved the day several times.
Smart Switch quick-tut.
Start as admin
More (At top)
Emergeny
Device init
enter model , s/n search
Click to expand...
Click to collapse
I'm running through it right now, but it tells me to boot into recovery? As noted, I am not able to reboot into recovery
megakiller99 said:
I'm running through it right now, but it tells me to boot into recovery? As noted, I am not able to reboot into recovery
Click to expand...
Click to collapse
You should just put your phone in download mode and then run the samsung program, it will do everything else
volume down + power + middle button to go to download mode.
localh85 said:
You should just put your phone in download mode and then run the samsung program, it will do everything else
volume down + power + middle button to go to download mode.
Click to expand...
Click to collapse
Whew, it's currently downloading applications for it. Thank you so much! I attempted to use a TWRP custom recovery for the T-Mobile USA version, but it looks like that was what blocked me out the recovery mode. Do you know of any custom recovery available for this?
megakiller99 said:
Whew, it's currently downloading applications for it. Thank you so much! I attempted to use a TWRP custom recovery for the T-Mobile USA version, but it looks like that was what blocked me out the recovery mode. Do you know of any custom recovery available for this?
Click to expand...
Click to collapse
Im not big on the phone extras (i have TWRP but not a big expert on it)..
basically this will factory reset your phone and make it working again, its up to you if you want to flash it again with ODIN and get TWRP on there.
I have a ton of issues after rooting my s7 exynos that I dont even do it anymore or remove bloatware. Something is clearly up with my device but im happy with the phone working, its ok if its a bit slower than it should be - for me.
localh85 said:
Im not big on the phone extras (i have TWRP but not a big expert on it)..
basically this will factory reset your phone and make it working again, its up to you if you want to flash it again with ODIN and get TWRP on there.
I have a ton of issues after rooting my s7 exynos that I dont even do it anymore or remove bloatware. Something is clearly up with my device but im happy with the phone working, its ok if its a bit slower than it should be - for me.
Click to expand...
Click to collapse
That version of TWRP isn't available for my model, sadly. More for the international versions excluding US
megakiller99 said:
That version of TWRP isn't available for my model, sadly. More for the international versions excluding US
Click to expand...
Click to collapse
You should read the s7 t mobile section before you damage your phone. If you go there you'll see you can't flash twrp on the g930t
It can be rooted but no custom recovery.
I went into a boot loop after xposed install can't get out of recovery mode on my sm g 930t flashed 3 different firmware packages
MASSTAHV91 said:
I went into a boot loop after xposed install can't get out of recovery mode on my sm g 930t flashed 3 different firmware packages
Click to expand...
Click to collapse
Hi mate
What exposed file did you use?
When 3 different firmwares ( odin) and still in a bootloop?
MAX 404 said:
Hi mate
What exposed file did you use?
When 3 different firmwares ( odin) and still in a bootloop?
Click to expand...
Click to collapse
Thank you for responding. Yeah I couldn't get it out of the loop tried every version of Odin I could find used galaxys7root.com's firmware Sam's and one I found on here the only thing that wouldn't fail flashing was the boot loader with the modified odin
localh85 said:
I have a ton of issues with my s7. Samsung's smart switch has saved the day several times.
Download it and give it a shot:
http://www.samsung.com/us/smart-switch/
Smart Switch quick-tut.
Start as admin
More (At top)
Emergeny
Device init
enter model , s/n search
Click to expand...
Click to collapse
i tried to use smart switch but i dont know what my serial# is because i cant boot into android, am i missing something?
Can confirm this flashed fine on my "Three" branded [unlocked] UK S7. Thankfully, the ghastly Three branding has gone

Bricked S7?

So I went to flash a Rom with Odin and now I can't get past the recovery screen. The phone will not show up when I plug into USB either. Is this phone officially toast?
Our crystal ball here at XDA is on the blink, unfortunately you're going to have to manually provide more information
Wlane1979 said:
So I went to flash a Rom with Odin and now I can't get past the recovery screen. The phone will not show up when I plug into USB either. Is this phone officially toast?
Click to expand...
Click to collapse
Hi mate
You said past recovery screen in recovery mode?
What firmware you flashed with odin , which files ?
If you can get into download mode there is hope still... can you? , go to recovery factory reset see if you can boot now , if not flash again firmware with odin , to avoid losing data use your home_csc file if that does not work flash again this time using CSC and checking re partition option in Odin
The phone orginally was stuck in a boot loop so I downloaded what I thought was a working Rom to fix it. Apparently something went wrong because now all I can do is get to hard reset recovery screen. I can wipe cache and format and all but it does not do anything.
I tried to plug the phone onto my computer and nothing happens now where as before it would recognize as a s7 and would recognize in Odin.
Wlane1979 said:
The phone orginally was stuck in a boot loop so I downloaded what I thought was a working Rom to fix it. Apparently something went wrong because now all I can do is get to hard reset recovery screen. I can wipe cache and format and all but it does not do anything.
I tried to plug the phone onto my computer and nothing happens now where as before it would recognize as a s7 and would recognize in Odin.
Click to expand...
Click to collapse
Model S7?
ROM you Flashed?
Download mode should still work no matter what you do with firmware tbh
It was a live demo stuck in boot loop. G930x
I'm not sure I remember the file name but it was the stock ldu rom
Wlane1979 said:
The phone orginally was stuck in a boot loop so I downloaded what I thought was a working Rom to fix it. Apparently something went wrong because now all I can do is get to hard reset recovery screen. I can wipe cache and format and all but it does not do anything.
I tried to plug the phone onto my computer and nothing happens now where as before it would recognize as a s7 and would recognize in Odin.
Click to expand...
Click to collapse
But what did you try to flash a custom rom or a stock firmware?
What did you format in recovery?
Sometimes during bootloops getting into download mode is tricky , keep trying
@*Detection* sorry mate i did not see your replies
MAX 404 said:
@*Detection* sorry mate i did not see your replies
Click to expand...
Click to collapse
Don't worry, two heads are better than one
---
Yea OP, as above, getting into DL mode sometimes takes a few attempts, keep Volume Down & Home & Power pressed until the phone reboots twice, after the second reboot keep them pressed and see if it boots into download mode
AFAIK with the demo units you need to flash the G930F firmware to them to unlock
But still no modem or fingerprint reader even after that iirc
But I can't used my pc to flash anymore. It does not show a device connected like if I plug in my s8.
The picture shows where I am stuck
Ok I got past that screen in dl Mode and found the right firmware or so I believe. Odin freezes when trying to add AP file. Without it my phone stays on the load screen. Help!
Wlane1979 said:
Ok I got past that screen in dl Mode and found the right firmware or so I believe. Odin freezes when trying to add AP file. Without it my phone stays on the load screen. Help!
Click to expand...
Click to collapse
Wait, ODIN takes a long time to load AP, and looks like it has frozen, just wait and it will add eventually
Can someone point me to the correct thing I need to download then? There are so many. What do I need since its a sm-g390x?
Wlane1979 said:
Can someone point me to the correct thing I need to download then? There are so many. What do I need since its a sm-g390x?
Click to expand...
Click to collapse
Maybe you can use the emergency recovery from samsung.. with serial number it will flash the correct firmware.
I'm not sure being a live demo unit
Wlane1979 said:
I'm not sure being a live demo unit
Click to expand...
Click to collapse
G930F firmware for demo units
*Detection* said:
G930F firmware for demo units
Click to expand...
Click to collapse
There are many of the 930f I have found but none of which for the United States.
Wlane1979 said:
There are many of the 930f I have found but none of which for the United States.
Click to expand...
Click to collapse
That's because it's an International firmware, use United Kingdom (BTU)
I did the firmware flash. Everything seemed to go smoothly but now I am stuck on a flashing Samsung screen
Wlane1979 said:
I did the firmware flash. Everything seemed to go smoothly but now I am stuck on a flashing Samsung screen
Click to expand...
Click to collapse
Did you use CSC rather than HOME_CSC?
Try booting into recovery and factory reset

Boot loop s6 g920f

Hi guys,
so here is the thing...my sister gave me s6 to fix it which i thought it would be pretty easy but...she got the phone from her friend who doesnt know much and i assume he went for rooting it but fail...at first, it was all stock and problem was on booting. It was an update screen followed by no command error(same screen after firmware installation - which that guy probably did)..Anyways, i wanted to enter recovery, do the reset and thats it, but i couldnt scroll up and down although volume up and down is working...so i installed twrp via odin and i can access it now... I have done the reset but nothing...it just randomly restarts after samsung logo and keeps going like that. Also very importamt thing you need to know is that all of thi cant be done without charger. Without charger phone is dead..So guys ,do you think it is hardware, or do i need to install proper firmware or something else.. Thank you and sorry for bad english
svetp said:
Hi guys,
so here is the thing...my sister gave me s6 to fix it which i thought it would be pretty easy but...she got the phone from her friend who doesnt know much and i assume he went for rooting it but fail...at first, it was all stock and problem was on booting. It was an update screen followed by no command error(same screen after firmware installation - which that guy probably did)..Anyways, i wanted to enter recovery, do the reset and thats it, but i couldnt scroll up and down although volume up and down is working...so i installed twrp via odin and i can access it now... I have done the reset but nothing...it just randomly restarts after samsung logo and keeps going like that. Also very importamt thing you need to know is that all of thi cant be done without charger. Without charger phone is dead..So guys ,do you think it is hardware, or do i need to install proper firmware or something else.. Thank you and sorry for bad english
Click to expand...
Click to collapse
Hi svetp,
I had the same problem. Whenever I tried to flash the Stock ROM things got worse, until in the end I had the same problem as you. Then I read that AOKP image cures almost always such problems - and it worked ! Don't do this if phon is still under warranty as it triggers the knox counter !
If you can still access download mode try the following:
download the latest TWRP file for your S6 model
download AOKP image for your S6 model
download GAPPS for your S6 model
enter download mode
flash TWRP with Odin, but un-tick "Auto-Reboot" in Odin
when completed go to recovery at once (don't let the phone try to boot normally, just "kill" phone and hold the buttons for download mode)
when in recovery (TWRP) start ADB software (if you don't know how google samsung galaxy S6 ADB for advice)
transfer the downloaded AOKP image and GAPPS to your phone (/sdcard is a nice place) via ADB
wipe cache in TWRP
install image and GAPPS
wipe cache and reboot your phone
everything should be normal by then
Good luck !
Peter

Bricked when returning to stock (No command)

Hey guys,
decided to flash the latest DBT Firmware via Odin to get back to stock completely. (G930FXXU3ESA3)
After flashing the firmware through Odin the phone reboots and then installs an update and erases data (blue background).
After a second reboot I end up with a blue screen and the simple error: "No command".
I can not get into recovery, as I end up with the same error message wether booting into recovery or the system.
I CAN however get into downloadmode and flash twrp, after that I can boot into system but I want to keep the whole system vanilla, without TWRP.
Installing TWRP keeps the device encrypted, no matter what. I can wipe, then install no-verity-encrypt and as soon as I reboot the device is encrypted again.
Ive tried: Different Firmware Version (December 2018), 3 different cables, different odin versions.
Edit: attached an Image of the message that Pops up after about 30sec on the no command screen.
Ok, so your device will take UK Unbranded BTU firmware. You can get it from a few sources and even direct from Samsung servers with Samtool.
Forget all that flashing TWRP and non verify nonsense, if you can get into download mode you can flash firmware, obviously make sure the firmware downloaded is not corrupt etc.
I've used Odin V10 -13 to flash BTU and every version flashed it correctly. Sometimes you do get that "installing update" and then "erasing" but that's fine just leave the phone for a few minutes it should eventually reboot normally.
FLASH No verity.zip
VIA TWRP
https://forum.xda-developers.com/attachment.php?attachmentid=4490455&d=1525176288
cooltt said:
Ok, so your device will take UK Unbranded BTU firmware. You can get it from a few sources and even direct from Samsung servers with Samtool.
Forget all that flashing TWRP and non verify nonsense, if you can get into download mode you can flash firmware, obviously make sure the firmware downloaded is not corrupt etc.
I've used Odin V10 -13 to flash BTU and every version flashed it correctly. Sometimes you do get that "installing update" and then "erasing" but that's fine just leave the phone for a few minutes it should eventually reboot normally.
Click to expand...
Click to collapse
Just tried the latest BTU with Odin 3.13.1, same problem. Its reboots into the blue screen, applying system update to about 32% and then switches to "Erasing". After about 1min it reboots, shows "Installing System update" for a second and I end up with "No command" again. And from there on it just constantly reboots into the "No command" screen.
This seems like the same problem. I can not enter stock recovery to wipe though...
Things ive tried so far:
- Different firmware Versions (all oreo since downgrading is impossible)
- Formating with pit files
- Different Odin Versions
- Unplugging and replugging the battery
- Installing TWRP, wiping data and then installing stock recovery through TWRP
Did u try in Odin nand erase and repatition option? If not try it ( make sure u have pit file extracted or downloaded from the net)
Scorpionea said:
Did u try in Odin nand erase and repatition option? If not try it ( make sure u have pit file extracted or downloaded from the net)
Click to expand...
Click to collapse
Did a efs backup through TWRP just in case, then flashed the latest DBT firmware with nand erase -> still the same problem.
I can only guess that this was caused by using a backup from another phone back when Oreo came out, this probably messed something up really badly. Very weird, im kinda lost.
Killuminati91 said:
Just tried the latest BTU with Odin 3.13.1, same problem. Its reboots into the blue screen, applying system update to about 32% and then switches to "Erasing". After about 1min it reboots, shows "Installing System update" for a second and I end up with "No command" again. And from there on it just constantly reboots into the "No command" screen.
This seems like the same problem. I can not enter stock recovery to wipe though...
Things ive tried so far:
- Different firmware Versions (all oreo since downgrading is impossible)
- Formating with pit files
- Different Odin Versions
- Unplugging and replugging the battery
- Installing TWRP, wiping data and then installing stock recovery through TWRP
Click to expand...
Click to collapse
Ok, from the no command screen do the following.
Hold power until phone switches off, then press power+home+volume up. The phone should now boot into original recovery screen. Select "wipe/factory reset" and then reboot device. Job done.
cooltt said:
Ok, from the no command screen do the following.
Hold power until phone switches off, then press power+home+volume up. The phone should now boot into original recovery screen. Select "wipe/factory reset" and then reboot device. Job done.
Click to expand...
Click to collapse
Tried that, recovery is simply not working. If I hold vol - + power + home to restart and switch immediatly to vol + I boot into the usual blue screen with No command. I even tried unplugging the battery to shut off the phone and boot into recovery from there but that is not working either. Sorry should have stated that more clearly.
If I flash TWRP however, I can easily boot into TWRP with the recovery button combo.
Killuminati91 said:
Tried that, recovery is simply not working. If I hold vol - + power + home to restart and switch immediatly to vol + I boot into the usual blue screen with No command. I even tried unplugging the battery to shut off the phone and boot into recovery from there but that is not working either. Sorry should have stated that more clearly.
If I flash TWRP however, I can easily boot into TWRP with the recovery button combo.
Click to expand...
Click to collapse
Ok it's a tricky one so one more thing I would suggest is download and install Samsung smart switch on your PC, place the phone in download mode plug it into lap top and choose emergency software recovery in smart switch
Edit. I just remembered before that try this button combo from the no command screen volume up+volume down+power.
cooltt said:
Ok it's a tricky one so one more thing I would suggest is download and install Samsung smart switch on your PC, place the phone in download mode plug it into lap top and choose emergency software recovery in smart switch
Edit. I just remembered before that try this button combo from the no command screen volume up+volume down+power.
Click to expand...
Click to collapse
Hmmh. Searched a lot for the version that still supported emergency recovery. (which seems to be 4.0). If I go into download mode, start smartswitch and try to use emergency recovery there is nothing for me to select.
Volume up + down and power gives me the terminal like look which I attached in the first post with all those error messages.
Killuminati91 said:
Hmmh. Searched a lot for the version that still supported emergency recovery. (which seems to be 4.0). If I go into download mode, start smartswitch and try to use emergency recovery there is nothing for me to select.
Volume up + down and power gives me the terminal like look which I attached in the first post with all those error messages.
Click to expand...
Click to collapse
The EFS partition is corrupt or blank, it's the only logical explanation but the TWRP back up should solve that, without looking at it my self and running some commands i cant help your further.
cooltt said:
The EFS partition is corrupt or blank, it's the only logical explanation but the TWRP back up should solve that, without looking at it my self and running some commands i cant help your further.
Click to expand...
Click to collapse
TWRP backup was created after I ran into problems though. Ive checked some more things and it seems like the serial number that is displayed (in combination rom and or Z3X) is not the same SN that is printed on the back of the phone. Could this be related? And how would I go about changing it back to the one on the sticker? The IMEI is correct.
Had someone who was more into the whole thing contact me here but when I wanted to "donate" only half of what he was asking he refused to help me.
Killuminati91 said:
TWRP backup was created after I ran into problems though. Ive checked some more things and it seems like the serial number that is displayed (in combination rom and or Z3X) is not the same SN that is printed on the back of the phone. Could this be related? And how would I go about changing it back to the one on the sticker? The IMEI is correct.
Had someone who was more into the whole thing contact me here but when I wanted to "donate" only half of what he was asking he refused to help me.
Click to expand...
Click to collapse
Thats because he's a scammer. Never donate to get your phone fixed! Donate to Rom developers and things you like but never to get the phone fixed, they're usually lying.
The serial number should be the same ON the phone as displayed IN phone. Tell me the story about the phone, how did you get it? what region? where are you? what firmware was installed? Can you still flash a ROM with TWRP? Can you check OEM unlock?
---------- Post added at 04:53 PM ---------- Previous post was at 04:51 PM ----------
nmnmnmnmnmnmnmnmnm
Pretty sure he was just trying to remote repair for a price, which is not allowed on XDA. Would obviously donated on my own if he actually fixed it.
Bought the phone unlocked directly from a provider (simply - germany - dbt - g930f) back in 2016. Tripped kn0x after a few months, installed a few custom roms until Oreo came out.
This is where I messed up I think: I used a TWRP backup from someone else that he had shared here on XDA, which probably included his /efs too.
Since then I had constant connection problems, weak internet connection, dropped calls and so on.
Broke my screen and then decided to repair it myself. Bought a new frame, screen, battery, usb-port, earpiece and vibrator - managed to assemble all of that.
I can install all latest official firmwares (bootloader 3) through Odin. If I leave it at that I have no recovery and end up with the initially shown screen and "No command".
If i install TWRP from there and simply root with magisk or apply dm-verity-fix I can boot into the stock firmware with everything working.
I can also install ROMs. Just going completely vanilla is not possible anymore. OEM Unlock is checked, USB debugging works.
Edit: What is also astounding: If I flash version DBT-G930FXXS3ERHD-20180918145033 (oldest possible Oreo Version) I can enter recovery and do a factory reset and wipe cache.
If I do that however I am stuck at the Galaxy S7 Logo, not even bootlooping.
Killuminati91 said:
This is where I messed up I think: I used a TWRP backup from someone else that he had shared here on XDA, which probably included his /efs too.
Click to expand...
Click to collapse
awww.....come on man you should have said this at the start! Of course you can't use someone else's EFS data, it's unique to your handset. Custom Rom's patch some but not all EFS data that's why they work and in your case that's why Stock firmware isn't going too.
Anyway if this is the problem (and i suspect it is) there is only one way to fix it with Octopus box which can write all the important info back onto the EFS. Your IMEI, Serial, Mac address etc. Odin reads the info from the EFS prior to nand write start, if the phone serials don't match it will always fail at some point.
You can install a custom via twrp but it will not work correctly due to EFS data miss match. Octopus box is your answer.
cooltt said:
awww.....come on man you should have said this at the start! Of course you can't use someone else's EFS data, it's unique to your handset. Custom Rom's patch some but not all EFS data that's why they work and in your case that's why Stock firmware isn't going too.
Anyway if this is the problem (and i suspect it is) there is only one way to fix it with Octopus box which can write all the important info back onto the EFS. Your IMEI, Serial, Mac address etc. Odin reads the info from the EFS prior to nand write start, if the phone serials don't match it will always fail at some point.
You can install a custom via twrp but it will not work correctly due to EFS data miss match. Octopus box is your answer.
Click to expand...
Click to collapse
Dang it. Thank you! Off to find someone who can do this via remote access or in Berlin.
Same situation right now with my S7. Damn.
Hi everyone. Did you guys find any way to resolve this issue? i have exactly the same issue here.. but in my case i cannot use twrp cuz i never installed it before... the issue happened right after i tried to enter the recovery mode by pressing the buttons...
my wife's galaxy s7 touch screen was acting weird and i tried to get into the recovey mode..which is pretty muh easy to do... but once i tried the no command msg came up and now i have exatly the same case as the guy that opened this thread....also done everything hes done....any clue about this anyone?
id appreciate some help..
thanks in advance
Diego Boffa
Anyone?
I have exactly the same error with "fail to open recovery_cause(No such file or directory)#
My Tablet is now stuck with a blue "android dead" screen saying "No command".
My history to disaster:
- i've recovered a "broken" Samsung Tablet (sm-T585) with corrupted file system via
* Download Mode works -> TWRP install -> Mount option -> use ADB to recreate EFS partition -> re-flash stock image (android 8) with odin
- device works fine
- then i've noticed it can only be used with a certain cell provider (o2)
- then i've tried to flash an older version of the stock rom (android 7) due some problems in Android 8 (often some slow downs while operating)
- this doesn't work, the flash don't start
- therefore nothing should be happend, or?
- then i've can't get anymore in the stock recovery to wipe all data
...therefore the mess began:
* i can't flash TWRP anymore
* i can't flash stock recovery anymore
* i only can get into download mode
* i can only flash a certain rom type successfully (green PASS within odin), but with the final stuck with boot loop, with the mentioned blue screen
* other rom version can't flashed
I hopefully ask you guys here, if anyone can help me?
Any help would be very appreciated ...

S10e Literally stuck in bootloops after 2020 Update

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.

Categories

Resources