Database Info

Brick galaxy s2 without options did you throw it away?

Hi, I'm new and do not know if I put the post in the right place. Forgive. I have a I9100 with 4.1.2 official rom, no root and no usb debugging enabled. One day is automatically restarted and stayed in bootloop. I had no access to recovery, but yes in download mode. I tried multiple ways I found on Google, but without success. I can not retrieve it with kies. probe reinstall the recovery again and nothing, try adb and not worked. With odin can not flash with pit. When turned on I get the message that there has been a problem with the firmware and recover with kies, but can not. It is impossible to save him?
Sorry with my English.
Thank you.

k7neptune said:
Hi, I'm new and do not know if I put the post in the right place. Forgive. I have a I9100 with 4.1.2 official rom, no root and no usb debugging enabled. One day is automatically restarted and stayed in bootloop. I had no access to recovery, but yes in download mode. I tried multiple ways I found on Google, but without success. I can not retrieve it with kies. probe reinstall the recovery again and nothing, try adb and not worked. With odin can not flash with pit. When turned on I get the message that there has been a problem with the firmware and recover with kies, but can not. It is impossible to save him?
Sorry with my English.
Thank you.
Click to expand...
Click to collapse
You can flash custom recovery from bootloader mode

I do not have access to bootloader mode. Display show "Firmware Upgrade Encountered an issue ..." when I try to enter recovery mode / bootloader mode

k7neptune said:
I do not have access to bootloader mode. Display show "Firmware Upgrade Encountered an issue ..." when I try to enter recovery mode / bootloader mode
Click to expand...
Click to collapse
In this case, perhaps a JTAG service might be able to help you. Try if there is one in your region.

If that doesn't work you can sell it by pieces.

Thanks for your ideas. I'll see what I do ...

Is it fixable? Bricked S6 won't boot or accept ROM flashes.

Previously, I've talked about how I bricked my G920T by using an apk to try to root my phone.
Then I tried to do a factory reset with the stock recovery but it wouldn't even go into the stock recovery. So I flashed TWRP and wiped the whole phone including the system partition.
Then I tried to flash a stock 6.0.1 firmware to the phone but doing so did not improve the situation as my phone still won't boot. Even worse, when I power my phone, all I see is the blue LED indicator, no Samsung logo, nothing.
Then I tried to flash a custom ROM like XtreStoLite but that didn't fix anything either.
When I use TWRP or the stock recovery, the error "failed to mount /efs (invalid argument)" comes up on the log. I tried using the ADB method to fix it but my phone would not get recognized by ADB probably because USB debugging isn't on by default.
I cannot shut down the phone without having it charged to a power source then holding down PWR+DOWN VOLUME+HOME until the screen shuts off.
When I enter download mode, I don't see the warning screen, I enter the download mode directly.

It will warm you when you enter download. Or use TWRP and reboot into Download.Once in download flash the ROM using Odin. Get the latest one from SamFirm.
P.S. Next time root using CF Auto Root

yasteellutch said:
It will warm you when you enter download. Or use TWRP and reboot into Download.Once in download flash the ROM using Odin. Get the latest one from SamFirm.
P.S. Next time root using CF Auto Root
Click to expand...
Click to collapse
It doesn't warn me when I enter download mode, that's one of the problems.
I tried flashing the official ROM using ODIN, it still won't boot because of the efs error.

1) Download the latest SmartSwitch
2) Click on more -> Emergency software recovery and initialization
3) Go into Device initialization, enter your model name, search for it and proceed as advised by the assistant
That should fix everything, otherwise:
1) Download the latest official firmware for your model, the 4-File (or 3-File) Version
2) Use latest ODIN, check repartition in options
3) Select all the files and flash it

If EFS or DRK is corrupted, flashing roms, custom or not won`t help, it can be fixed via repair box maybe (Octoplus/Z3X)
Try to flash CF auto root for your model, if it still won`t boot, then find someone with a box to try to help you remotely or not.
But Smart Switch emergency initialization with phone sn would be the first thing I would try.

Orginator said:
1) Download the latest SmartSwitch
2) Click on more -> Emergency software recovery and initialization
3) Go into Device initialization, enter your model name, search for it and proceed as advised by the assistant
That should fix everything, otherwise:
1) Download the latest official firmware for your model, the 4-File (or 3-File) Version
2) Use latest ODIN, check repartition in options
3) Select all the files and flash it
Click to expand...
Click to collapse
Which mode should I be in when using SmartSwitch? No devices are shown when I have it plugged in during the bootup, and is so too in download mode but shows a not supported message.
brenner650 said:
If EFS or DRK is corrupted, flashing roms, custom or not won`t help, it can be fixed via repair box maybe (Octoplus/Z3X)
Try to flash CF auto root for your model, if it still won`t boot, then find someone with a box to try to help you remotely or not.
But Smart Switch emergency initialization with phone sn would be the first thing I would try.
Click to expand...
Click to collapse
How can someone with a box help me remotely?

zheyizhu said:
Which mode should I be in when using SmartSwitch? No devices are shown when I have it plugged in during the bootup, and is so too in download mode but shows a not supported message.
Click to expand...
Click to collapse
Download mode offcourse. Nevermind the not supported message.
Follow instructions from link below, I made it for such occasions:
http://forum.xda-developers.com/galaxy-s6/help/how-to-smart-switch-emergency-t3383448
zheyizhu said:
How can someone with a box help me remotely?
Click to expand...
Click to collapse
Well if you know someone who have a box, it doesn`t have to be remotely.
If not, it is possible to fix it remotely, with help of usb hub (FlexiHub or similar), tunneling (TeamViewer or similar) and box software (you connect phone to your computer, the other guy connects box to his computer, both of you are connected through a gateway to a wonderfull thing called internet, and everybody is happy ) .
Same as on site, just with few more things in between the phone, and the box.

brenner650 said:
Download mode offcourse. Nevermind the not supported message.
Follow instructions from link below, I made it for such occasions:
http://forum.xda-developers.com/galaxy-s6/help/how-to-smart-switch-emergency-t3383448
Well if you know someone who have a box, it doesn`t have to be remotely.
If not, it is possible to fix it remotely, with help of usb hub (FlexiHub or similar), tunneling (TeamViewer or similar) and box software (you connect phone to your computer, the other guy connects box to his computer, both of you are connected through a gateway to a wonderfull thing called internet, and everybody is happy ) .
Same as on site, just with few more things in between the phone, and the box.
Click to expand...
Click to collapse
The S/N sticker on the back of the phone is long gone, is there any other way I can find it besides from going into settings because I can't do that?
EDIT: I am able to borrow a friend's serial and got the firmware installed.
The Samsung boot logo is back now, however, the device still won't boot. The efs error is still there but the download mode warning sign came back.
EDIT #2: Okay, I flashed TWRP now and ADB is working once again. Can I utilize this to fix the efs error?

bypass password to enable usb debugging, Galaxy S20 FE

Greetings, Galaxy S20 FE inherited but password locked even after factory reset, can not enter into usb debugging any solutions?

Hard resetting doesn't remove password? Are you sure about that? You did it from the recovery and completely wiped everything?
That is impossible so I'm guessing you mean FRP.
Do you see this message " This device was reset. To continue, sign in with a Google Account that was previously synced on this device. " on your phone?
If so then follow this guide to help you with bypassing it. I recommend resetting the phone again but from the menu after you're done.
You can also follow this guide, it uses different method should the first fail. You can get your phone stock ROM from here.
Goodluck.

XDHx86 said:
Hard resetting doesn't remove password? Are you sure about that? You did it from the recovery and completely wiped everything?
That is impossible so I'm guessing you mean FRP.
Do you see this message " This device was reset. To continue, sign in with a Google Account that was previously synced on this device. " on your phone?
If so then follow this guide to help you with bypassing it. I recommend resetting the phone again but from the menu after you're done.
You can also follow this guide, it uses different method should the first fail. You can get your phone stock ROM from here.
Goodluck.
Click to expand...
Click to collapse
Thank you. I downloaded my rom from Sam firmware and extracted the but when I changed the ap file to a zip I needed a password to extract it to create combination file

Issue was resolved thank you kindly for responding
Fixed by @hainguyenthao

Fastboot, Samsung Galaxy A51

Hello, i wanted to ask how to fix the fastboot mode.
Everytime when i try to access it, it just says "Entering Fastboot..."and thats all.
I dont want to close it, thats not my problem, i just wanna flash a recovery.img, and the fastboot seems not working. Any ideas?

M3DUS4 said:
Hello, i wanted to ask how to fix the fastboot mode.
Everytime when i try to access it, it just says "Entering Fastboot..."and thats all.
I dont want to close it, thats not my problem, i just wanna flash a recovery.img, and the fastboot seems not working. Any ideas?
Click to expand...
Click to collapse
this could be because the galaxy A51 wasnt built with fastboot, and the code to launch this option was just reused from a different device, or because something isnt connecting properly.

Hello, I have the same ... Android 11 (and currently 12) (from Frija). So it is not the fault of incorrect configuration or with connecting. Only something is wrong with this phone ...

I have this device and this solved it for me:
Enable OEM unlocking in developer settings
Shut down the phone
Hold volume up and volume down
Plug in a USB cable connected to a computer (the computer being turned on)
Keep holding
You're in download mode!
Side note: This might not work in USA or Canada, I am from europe and it works here. I have no idea if it works in another region. Also, you can't just flash a recovery.img on Samsung since there is no real "fastboot", you have to use download mode and Odin.

But I know how to enter download mode... Problem is Fastboot mode...

There is no fastboot mode on a modern Samsung device. If there is, it's fake and you cannot flash anything with it. As you can see even from Wikipedia, Odin is the Samsung replacement of fastboot.
So no fastboot, only download mode.
If a guide is saying to use fastboot, it is not compatible with Samsung.
If you would tell me why you specifically need fastboot, I'll be happy to tell you how you can do it with Odin, if possible.

Because I have Samsung Galaxy A51 5G (A516B) with new Android 12 and I can't do a root! Because I can't upload TWRP (custom recovery) because I haven't OEM unlock option in Deveoper Option. I tried trick with set back date by 7days but not succes. Everything I;ve metioned here - I did at my phone with Android 11.
And... I have read that I can turn this fu**ing OEM option by comend at ADB: fastboot oem unlock.
Phew ...
So this fastboot method is the last method to do a root with my phone.

Upload TWRP by Odin in download mode -ends red warning - of corse...
Have you any ideas?
I would be grateful for help...

I have read this fastboot method at:
How to Unlock Bootloader On Samsung Galaxy Phones [EASY GUIDE]
Are you looking for a Complete tutorial on How To Unlock Bootloader on Samsung Galaxy Phones? If yes, then you have come to the right place.
www.guidetoroot.com

Yeah, that guide is not relevant on any modern Samsung device. Besides, even if it was, which it isn't, you would first need to enable OEM unlocking from the Developer Settings.
But the fact that you don't have an option for OEM unlock is weird, since I have the exact same device model and it is there for me.
May I ask what is your region and is your phone locked to a telephone carrier?

My region is PLS - Poland. And not - phone is not locked. Have you the newest system Android 12?

Yes, I do. It's weird that there isn't even an option for you.
I'll try to come up with some new ideas if I have time...

I'll be glad for it...

Hej, do you have any idea?

stanwin said:
Hej, do you have any idea?
Click to expand...
Click to collapse
Have you tried everything listed here?

BloodyFruitDestroyer said:
Have you tried everything listed here?
Click to expand...
Click to collapse
Yes, I did. Evething exept the last one...

You could try it. It might be risky, but it's the only option I personally can come up with right now.

I've tried this option but Odin stuck on "files verification". Any help?

have any of you encountered this problem?
And how did you solve it?

You can also try searching for combination firmware for your device online

Oneplus 8T stuck in Qualcomm CrashDump mode

After trying to restore stock OOS and rebooting fastboot my phone is now stuck in Qualcomm Crashdump mode. I have MSMDownloadTool installed but it won't open, it just opens a windows saying "Program has been started" after executing it.
I also can't reboot to the bootloader, the phone just turns on or off.
What to do?

From my rather long post in https://forum.xda-developers.com/t/...your-device-to-oxygenos.4180837/post-86563159 :
"connect the phone to the PC whilst it's still in CrashDump mode and then press Pwr + Vol Up until the phone buzzes and then hold Vol Up + Vol Dn and MSM will then connect."

Thank you, that worked. I have another question if you don't mind:
I tried to restore OxygenOS with https://forum.xda-developers.com/t/...xygenos-fastboot-roms-for-oneplus-8t.4348023/ but it cant find the create-logical device and delete-logical-device commands, also when I try to flash some of the image files fastboot complains about not being able to flash system critical files. I tried running fastboot flashing unlock_critical but that didn't change anything. Is there any other way to restore Oxygen OS with fastboot or is there any fix to my issues? I've been looking on the web for a few hours now, to no result.

petrolblue said:
Thank you, that worked. I have another question if you don't mind:
I tried to restore OxygenOS with https://forum.xda-developers.com/t/...xygenos-fastboot-roms-for-oneplus-8t.4348023/ but it cant find the create-logical device and delete-logical-device commands, also when I try to flash some of the image files fastboot complains about not being able to flash system critical files. I tried running fastboot flashing unlock_critical but that didn't change anything. Is there any other way to restore Oxygen OS with fastboot or is there any fix to my issues? I've been looking on the web for a few hours now, to no result.
Click to expand...
Click to collapse
The delete/create logical commands are in the thread OP, but you have to tap on "click to show" button.
Note that fastbootd is not the same as fastboot. And you need to be in that mode to avoid the "critical" warning and to be able to do the logical partitions stuff.

So, after massively failing to update my 8T I am stuck in a bootloop with a bit of Crash dump [dm-verity device corrupted force dump].
I am still able to access fastboot but that is it. I can't get adb working, when I attempt to enter recovery mode all I get is a black screen, MSM is not able to find my phone/I can't get my phone to enter EDL (been trying for about 5 hours now).
I feel so defeated by this can anyone help me?

Did you read my post (#2)?
Does your PC make a sound when you connect your phone to it in EDL mode? If so, try reinstalling the Qualcomm driver (though I've never needed to do that).
If you can get into bootloader, then you can try using the method in https://forum.xda-developers.com/t/guide-unbrick-or-restore-to-oos-using-only-fastboot.4289013/

BillGoss said:
Did you read my post (#2)?
Does your PC make a sound when you connect your phone to it in EDL mode? If so, try reinstalling the Qualcomm driver (though I've never needed to do that).
If you can get into bootloader, then you can try using the method in https://forum.xda-developers.com/t/guide-unbrick-or-restore-to-oos-using-only-fastboot.4289013/
Click to expand...
Click to collapse
Whenever I connect my phone to the pc it just auto-boots. In my devices the driver does show up. But I don't think I have been able to access EDL.
I did reinstall the driver as well, no change. I tried installing the drivers and MSM stuff on a 2nd pc, still unable to get it going.
I did come across this method and my phone/fastboot keeps erroring whenever I try to use cmd for anything beyond Reboot fast boot. It's weird.

Angilias37 said:
Whenever I connect my phone to the pc it just auto-boots. In my devices the driver does show up. But I don't think I have been able to access EDL.
I did reinstall the driver as well, no change. I tried installing the drivers and MSM stuff on a 2nd pc, still unable to get it going.
I did come across this method and my phone/fastboot keeps erroring whenever I try to use cmd for anything beyond Reboot fast boot. It's weird.
Click to expand...
Click to collapse
I see that your PC sees the phone (Qualcomm...) but has an ! against it. If you open that you should see the option to update the driver.
PS: you may need to flash boot, DTBO, and recovery in fastboot first before you can use fastbootd to flash the other partitions for the fastboot method.

BillGoss said:
I see that your PC sees the phone (Qualcomm...) but has an ! against it. If you open that you should see l the option to update the driver.
Click to expand...
Click to collapse
Right but where's the update? From everything that I can find it is the most updated version

Angilias37 said:
Right but where's the update? From everything that I can find it is the most updated version
Click to expand...
Click to collapse
I use the driver (Qualcomm HS-USB QDLoader 9008) from https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008

OK
BillGoss said:
Did you read my post (#2)?
Does your PC make a sound when you connect your phone to it in EDL mode? If so, try reinstalling the Qualcomm driver (though I've never needed to do that).
If you can get into bootloader, then you can try using the method in https://forum.xda-developers.com/t/guide-unbrick-or-restore-to-oos-using-only-fastboot.4289013/
Click to expand...
Click to collapse
Ok I take back what I said! That link with the CMDs worked!
I really don't know what I did differently, probably skipped a step or something, but I was able to reset my phone!
Still unsure what is going on with the drivers but the crisis has been averted!
Thank you BillGoss! You are incredibly helpful!