Database Info

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.

Question SM-A127F/DS "not running orginal software..."

Hello all togehter,
i tried to root my new Samsung A12 SM-A127F/DS with Magisk, but something went wrong.
Now i´m stuck at a but Logo with the info "This Phone is not running Samsungs´s offical Software..."
I tried to enter download mode again, but no idea how, the usual way doesn´´t work :-(
Do you have any ideas?
Thank you and best regards,
Wolfgang

BadPig-Ger said:
Hello all togehter,
i tried to root my new Samsung A12 SM-A127F/DS with Magisk, but something went wrong.
Now i´m stuck at a but Logo with the info "This Phone is not running Samsungs´s offical Software..."
I tried to enter download mode again, but no idea how, the usual way doesn´´t work :-(
Do you have any ideas?
Thank you and best regards,
Wolfgang
Click to expand...
Click to collapse
Welcome to the club of the unlucky users of the SM-A127F variant currently unknown to the XDA developers You can re-flash back your stock firmware, get it from https://samfw.com/firmware/SM-A127F. To enter the download mode you have to be quick: loosely insert the USB cable into the socket, hold the vol+ and vol- keys with one hand and once the phone reboots (screen goes blank) promptly insert the cable, still holding the keys. If the phone does not reboot by itself, then you have to be extra quick: prepare the USB cable in the socket, press vol- and power, then once the screen goes blank quickly switch the fingers to vol+ and vol- while inserting the cable with the other hand. But be reasonably careful with the socket, of course, don't break it.

By the way: did you use the patched Magisk, or the original v23? You have to use the patched version or wait until the version 24 comes out. Magisk v23 does not work on SM-A127F.

I have the same model.
Did anyone succeed in rooting it ?

hamidv2 said:
I have the same model.
Did anyone succeed in rooting it ?
Click to expand...
Click to collapse
I had successfully rooted my SM-A127F/DSN before. It shouldn't be much different from SM-A127F/DS. I've succeeded with both the patched Magisk and the self-compiled original git master. The latter method is preferred, although it is not easy to compile it. Magisk is a very powerful program, no different from the OS itself by the extent of its access, it gets very deep into the system, starts before the system and has the full access to everything, so using any patched binaries is a security risk.

Yes, getting in download mode is tricky. If you still stuck at the Samsung screen, maybe you have to clean flash your phone (i had to...)

Question Bricked oneplus 9 please help me reset it

i installed the DSU package and now the phone is stuck on your device is corrupted and cannot be trusted. I can only get into fast boot mode
can someone guide me through resetting it, I dont care about anything on the phone i just want it to go back

[FASTBOOT] [ROM] [PC REQUIRED] [OP9] Stock OOS 11.2.2.2AA
Greetings, I've appreciated @Slikkster2k's terrific thread that explains and walks you through fastboot recovery of a OnePlus 9. To make it more convenient, I've taken his process and adapted @mauronofrio's OnePlus 8 fastboot ROM to post a...
forum.xda-developers.com
This is flashed through fastboot

mattie_49 said:
[FASTBOOT] [ROM] [PC REQUIRED] [OP9] Stock OOS 11.2.2.2AA
Greetings, I've appreciated @Slikkster2k's terrific thread that explains and walks you through fastboot recovery of a OnePlus 9. To make it more convenient, I've taken his process and adapted @mauronofrio's OnePlus 8 fastboot ROM to post a...
forum.xda-developers.com
This is flashed through fastboot
Click to expand...
Click to collapse
If you can reach fastboot this method should work

_MartyMan_ said:
If you can reach fastboot this method should work
Click to expand...
Click to collapse
dont i need unlocked bootloader?

mattie_49 said:
[FASTBOOT] [ROM] [PC REQUIRED] [OP9] Stock OOS 11.2.2.2AA
Greetings, I've appreciated @Slikkster2k's terrific thread that explains and walks you through fastboot recovery of a OnePlus 9. To make it more convenient, I've taken his process and adapted @mauronofrio's OnePlus 8 fastboot ROM to post a...
forum.xda-developers.com
This is flashed through fastboot
Click to expand...
Click to collapse
dont i need unlocked bootloader?

You don't have bootloader unlocked? You might need to find your correct msm tool for your device, depending on if you got your phone from OnePlus or T-Mobile, or send it in for repair? A few people on here, including me, also was able to send it to OnePlus via 1 day airmail and have it shipped back the same way and repaired all for free. That might not be an option for you though, I don't know how much you need your phone but if it's bricked either way it might be the best option. Try the msm tool first though instead of using fastboot to flash stock.

casualBricker said:
dont i need unlocked bootloader?
Click to expand...
Click to collapse
To flash critical partitions, yes

D3G0N said:
You don't have bootloader unlocked? You might need to find your correct msm tool for your device, depending on if you got your phone from OnePlus or T-Mobile, or send it in for repair? A few people on here, including me, also was able to send it to OnePlus via 1 day airmail and have it shipped back the same way and repaired all for free. That might not be an option for you though, I don't know how much you need your phone but if it's bricked either way it might be the best option. Try the msm tool first though instead of using fastboot to flash stock.
Click to expand...
Click to collapse
+1 get a remote session from OnePlus tech's. He had said earlier he tried msm already and couldn't connect and changed op

D3G0N said:
You don't have bootloader unlocked? You might need to find your correct msm tool for your device, depending on if you got your phone from OnePlus or T-Mobile, or send it in for repair? A few people on here, including me, also was able to send it to OnePlus via 1 day airmail and have it shipped back the same way and repaired all for free. That might not be an option for you though, I don't know how much you need your phone but if it's bricked either way it might be the best option. Try the msm tool first though instead of using fastboot to flash stock.
Click to expand...
Click to collapse
A phone wouldnt have an unlocked bootloader from the start right? I've never been this deep in **** with my android so this is all really out of my depth. Ill send a message to the oneplus support while the file from the other post downloads, maybe it'll work after all

mattie_49 said:
+1 get a remote session from OnePlus tech's. He had said earlier he tried msm already and couldn't connect and changed op
Click to expand...
Click to collapse
My bad, didn't see that he changed op. I mean if he could not connect through msm, there are a few options to try, including installing a driver manually for the qcom device. I had to fiddle with drivers and whatnot for about an hour or so before flashing was able to successfully commence. msm should help but scheduling a remote repair might take a day or so from oneplus so might as well try you know?

casualBricker said:
A phone wouldnt have an unlocked bootloader from the start right? I've never been this deep in **** with my android so this is all really out of my depth. Ill send a message to the oneplus support while the file from the other post downloads, maybe it'll work after all
Click to expand...
Click to collapse
No it would not, however msm tool does not use unlocked bootloader. I was informed that you tried it and it did not work and removed it from your op, but what would not work? was the device not seen on com port?

D3G0N said:
No it would not, however msm tool does not use unlocked bootloader. I was informed that you tried it and it did not work and removed it from your op, but what would not work? was the device not seen on com port?
Click to expand...
Click to collapse
i havent used an msm? i couldnt get the com port to show up, or It was like showing up for short periods while i was doing certain inputs, but not long enough to get anything done

casualBricker said:
i havent used an msm? i couldnt get the com port to show up, or It was like showing up for short periods while i was doing certain inputs, but not long enough to get anything done
Click to expand...
Click to collapse
So you tried it though it sounds like. It requires specific steps to work. You need drivers to be installed, go into EDL mode by having the device off and holding volume up while plugging the device into your computer, and then you have to start it when the device is enumerated. Are you willing to try msm again? The only other options really are to have a remote session with oneplus, which might take a day or so to get done, or send it for free for repair?

D3G0N said:
So you tried it though it sounds like. It requires specific steps to work. You need drivers to be installed, go into EDL mode by having the device off and holding volume up while plugging the device into your computer, and then you have to start it when the device is enumerated. Are you willing to try msm again? The only other options really are to have a remote session with oneplus, which might take a day or so to get done, or send it for free for repair?
Click to expand...
Click to collapse
its the holding buttons part thats a little weird but im definitely ready to try it again. The problem occurs with how my phone is powercycling by itself whatever I do while its not in fast boot mode. This makes the MSM stop detecting the phone and I have to start over.

casualBricker said:
its the holding buttons part thats a little weird but im definitely ready to try it again. The problem occurs with how my phone is powercycling by itself whatever I do while its not in fast boot mode. This makes the MSM stop detecting the phone and I have to start over.
Click to expand...
Click to collapse
Yeah, I have bricked my op9 so many times I know what you are talking about. With the power cycling thing I have no idea why that happens, but sometimes if I start the msm tool while it is detected, it will stay in EDL mode and stop cycling. Other times I realized that it was not really in EDL mode to begin with. Make sure that the device is completely off. Open up msmtool and get it ready. Hold volume down and up, without holding the power button, and then connect it to your pc. Once it shows up just click start. You might need to try different usb ports, and/or make sure that your drivers are installed for qcom device in edl mode.

D3G0N said:
Yeah, I have bricked my op9 so many times I know what you are talking about. With the power cycling thing I have no idea why that happens, but sometimes if I start the msm tool while it is detected, it will stay in EDL mode and stop cycling. Other times I realized that it was not really in EDL mode to begin with. Make sure that the device is completely off. Open up msmtool and get it ready. Hold volume down and up, without holding the power button, and then connect it to your pc. Once it shows up just click start. You might need to try different usb ports, and/or make sure that your drivers are installed for qcom device in edl mode.
Click to expand...
Click to collapse
Thank you! i think im ready to start this hell, the "qualcom something 8001ish" driver showing up(while the phone shows up in msmtool) would mean the drivers are correctly installed right?

casualBricker said:
Thank you! i think im ready to start this hell, the "qualcom something 8001ish" driver showing up(while the phone shows up in msmtool) would mean the drivers are correctly installed right?
Click to expand...
Click to collapse
I believe so? in device manager you should see the device and then COM... like COM4 or COM3 or something, as long as it is COM and then a number, and if it shows up in msmtool then the drivers are probably installed. The process won't work if you dont have drivers set right, so try it and if it fails make sure that it is the right msmtool and that you have drivers installed. Do not touch it while it is doing its thing, lay it down on a surface or something just to be safe. Also you might not have to do this but I have found success with msmtool by going offline like disconnecting ethernet and turning off wifi, and setting my date back to december of 2018 in windows before starting the tool, I do not know why but if it fails try that first above all else.

D3G0N said:
I believe so? in device manager you should see the device and then COM... like COM4 or COM3 or something, as long as it is COM and then a number, and if it shows up in msmtool then the drivers are probably installed. The process won't work if you dont have drivers set right, so try it and if it fails make sure that it is the right msmtool and that you have drivers installed. Do not touch it while it is doing its thing, lay it down on a surface or something just to be safe. Also you might not have to do this but I have found success with msmtool by going offline like disconnecting ethernet and turning off wifi, and setting my date back to december of 2018 in windows before starting the tool, I do not know why but if it fails try that first above all else.
Click to expand...
Click to collapse
how do i make sure the phone is turned off, just when it goes black? and when I hold the volume buttons it goes into fast boot, does this mean I was too slow?

casualBricker said:
how do i make sure the phone is turned off, just when it goes black? and when I hold the volume buttons it goes into fast boot, does this mean I was too slow?
Click to expand...
Click to collapse
Yeah it should just be black screen. It goes into fastboot? You sure you aren't hitting the power button as well? In fastboot select power off. When it's off, hold only the volume buttons, and then plug it in.

D3G0N said:
Yeah it should just be black screen. It goes into fastboot? You sure you aren't hitting the power button as well? In fastboot select power off. When it's off, hold only the volume buttons, and then plug it in.
Click to expand...
Click to collapse
im not touching the powerbutton, it confuses me as well. do I wait for it to vibrate before I plug in the phone?

Question Recover after bad flash?

I was attempting to downgrade my moto g stylus 2021 from android 11 to 10. Something when wrong during my flash attempt and now I am stuck with a rapid bootloop where a motorolo logo will briefly flash on the screen and then go to back.
I can't seem to get back to fastboot although if I hold the down volume and power button the logo stops flashing and I just get a black screen.
Is there any possible path out of this I can try or did I hard brick my phone?

im having same thing downgrade issue i plug cord in just blink light no fastboot or recovery either.
So if you find a way let me know and ill do the same.

travy said:
im having same thing downgrade issue i plug cord in just blink light no fastboot or recovery either.
So if you find a way let me know and ill do the same.
Click to expand...
Click to collapse
Same boat as you two. Used "fastboot set_active b" after flashing stock firmware and ignored the bootloader warning. Now im stuck hardbricked with no success blankflashing. Including info for EDL Mode and log from one of my blankflash attempts as well as the correct firehose programmer for this device.

ezril said:
I was attempting to downgrade my moto g stylus 2021 from android 11 to 10. Something when wrong during my flash attempt and now I am stuck with a rapid bootloop where a motorolo logo will briefly flash on the screen and then go to back.
I can't seem to get back to fastboot although if I hold the down volume and power button the logo stops flashing and I just get a black screen.
Is there any possible path out of this I can try or did I hard brick my phone?
Click to expand...
Click to collapse
Seems to be a few of us in the same situation. I downloaded Motorola's program for, supposedly, diagnosing and fixing their phones. I'm hesitant to use it because the only place I have Windows is a VM and I've found that the connection between the phone and the computer can get a little sketchy on reboots because the USB forwarding.

Linux_SF said:
Seems to be a few of us in the same situation. I downloaded Motorola's program for, supposedly, diagnosing and fixing their phones. I'm hesitant to use it because the only place I have Windows is a VM and I've found that the connection between the phone and the computer can get a little sketchy on reboots because the USB forwarding.
Click to expand...
Click to collapse
I have had no luck whatsoever. Originally I thought I was successful using a blankflash although it was not. I've pretty much given up on that device for now although if you have anything that may help, I have no problem being the guinea pig, lol.
Keith

Question I can't access the download mode

So here is the deal.
This device (Galaxy A32 5G - SM A326B - Android 12) does not let me boot into the download mode in order to unlock bootloader and for eventually rooting it.
OEM unlock has been selected in the dev options.
No button pressing configuration is working.
Trying to access the fastboot mode in the recovery mode only shows a black screen with a red writing on top that fastboot mode is being loaded, but nothing is happening and Odin doesn't recognize the device.
I just want that turquoise, blueish download mode screen, but for the love of it, it just doesn't work getting there.
This is my backup device and I just want to root it. Coming from OnePlus I am spoiled but the fact that I can't access this mode with all kinds of button tryouts is just nagging on me.
Anyone experienced something similar?
Some help would be greatly appreciated.
Cheers

mrjuniork said:
OEM unlock has been selected in the dev options.
Click to expand...
Click to collapse
I have the SM A326U but unfortunately I tried to see if I had the OEM Unlock options in the Developer Options Activity, and it's not there.
Do you know what the hidden activity might be when you click on the OEM Unlock? Maybe we can bring it up with an Activity Launcher?

mrjuniork said:
So here is the deal.
This device (Galaxy A32 5G - SM A326B - Android 12) does not let me boot into the download mode in order to unlock bootloader and for eventually rooting it.
OEM unlock has been selected in the dev options.
No button pressing configuration is working.
Trying to access the fastboot mode in the recovery mode only shows a black screen with a red writing on top that fastboot mode is being loaded, but nothing is happening and Odin doesn't recognize the device.
I just want that turquoise, blueish download mode screen, but for the love of it, it just doesn't work getting there.
This is my backup device and I just want to root it. Coming from OnePlus I am spoiled but the fact that I can't access this mode with all kinds of button tryouts is just nagging on me.
Anyone experienced something similar?
Some help would be greatly appreciated.
Cheers
Click to expand...
Click to collapse
Did you try plugging into usb while holding down the buttons?

TimmyP said:
Did you try plugging into usb while holding down the buttons?
Click to expand...
Click to collapse
Yes, among other things. It just never enters that mode. It either restarts, goes into charging mode or reboots to recovery.
It's weird

maybe try "Samsung 300k Tool?" It looks like its designed specifically to reboot Samsungs into Download mode

TimmyP said:
maybe try "Samsung 300k Tool?" It looks like its designed specifically to reboot Samsungs into Download mode
Click to expand...
Click to collapse
Thx for this useful information. I could enter the download mode with this program but interestingly there is no way to use volume up button for proceeding to unlock the bootloader. Odin recognized the device properly but no way to unlock the bootloader. Isn't that strange? Also I did not see the warning screen, it went straight to the download mode screen.
I did not expect this to be such a pain...

Glad it worked! Samsungs always seem to have some sort of strange issue. I was recently stuck in a bootloop for a half hour until I finally got the key combo for recovery to work. Since it never turns off it becomes a pain!

TimmyP said:
Glad it worked! Samsungs always seem to have some sort of strange issue. I was recently stuck in a bootloop for a half hour until I finally got the key combo for recovery to work. Since it never turns off it becomes a pain!
Click to expand...
Click to collapse
I actually figured it out without the need of any 3rd part software.
There was obviously one option that I haven't tried yet. Pressing both volume buttons and then plugging in the USB cable till the warning screen shows up. That's it
Anyway, thx for taking your time to reply.
Cheers

mrjuniork said:
I actually figured it out without the need of any 3rd part software.
There was obviously one option that I haven't tried yet. Pressing both volume buttons and then plugging in the USB cable till the warning screen shows up. That's it
Anyway, thx for taking your time to reply.
Cheers
Click to expand...
Click to collapse
Hello Pal, were you able to root the device? I have bought an A33 5G, not sure if I will be able to root it. Extracting the boot.img file from original rom, patching it with Magisk and flashing back to the phone works? Can you use fastboot for it or do you need ODIN?

GauchoTche said:
Hello Pal, were you able to root the device? I have bought an A33 5G, not sure if I will be able to root it. Extracting the boot.img file from original rom, patching it with Magisk and flashing back to the phone works? Can you use fastboot for it or do you need ODIN?
Click to expand...
Click to collapse
Hello again.
Yes, I managed to root the device.
I used Odin for flashing the patched boot image. AFAIK, using fastboot isn't possible, hence Odin.
But make sure you have a backup in place, coz in my case, initially applying a patched image, led to another factory reset (the second one after unlocking the bootloader).

mrjuniork said:
Hello again.
Yes, I managed to root the device.
I used Odin for flashing the patched boot image. AFAIK, using fastboot isn't possible, hence Odin.
But make sure you have a backup in place, coz in my case, initially applying a patched image, led to another factory reset (the second one after unlocking the bootloader).
Click to expand...
Click to collapse
Hello, I need help with unlocking the bootloader as well. I can't find the Oem option and there is no unlock the bootloader option in download mode.