I have a Samsung S7 Edge that kept rebooting itself randomly. I thought it might be due to a corrupt update. As time went by it started to bootloop several times before booting properly.
I managed to remove my Google account to disable FRP but I didn't manage to activate the secure startup pin before flashing.
Used Odin 3.14.4 and downloaded the BTU version of the firmware, but I later realised that the version used was XEU. Does that matter at all? Once the flash completes it auto reboots and begins bootlooping again. I have tried to clear cache partition and also factory reset via recovery menu. It again starts bootlooping many times, until it reaches the following screen that says;
Encryption failed. Unable to start up your device. The encryption process was interrupted. You need to reset your device to factory default settings. This will erase all your data. [Reset].
Click to expand...
Click to collapse
What else can I do here? I have not tried changing any settings in Odin, I left it at its defaults.
I am also unable to flash TWRP, as I understand I would need to unlock the bootloader beforehand and I'm not able to get it to boot.
Any luck? Its too late though
Related
i have verizon s7 edge. nougat. attempted to use odin to load engineering bootloader. succeeded and proceeded to reboot phone. then stuck in a boot loop. (tries to boot, vibrates, then tries again). tried to wipe cache partition and do factory reset w/o resolution. cant force power off but somehow stumbled into mode to boot into safe mode which also did not work. phone not rooted, was loading above to unlock (obviously). of note, did just update to nougat the day prior to doing this but phone working fine (although slow) after the update. any help appreciated.
ok...flashed factory rom and now working fine. still not sure what i did wrong to crash it initially. any ideas welcome.
Make sure your using the correct eng boot for nougat.
After fresh rom flash set up phone go to settings developer options and make sure oem unlock is checked.
Flash eng boot in ap slot.
Let phone reboot and start back up then you can run root.bat
So I enabled secure start-up then flashed a Sammobile stock Rom using Odin. Stupid mistake. The phone now gives me a warning saying that the phone has secure start-up on it and I need to factory reset. There is then the option to reset at the bottom. This just then reboots to the same screen repeatedly. I then flashed TWRP to reset the phone that way but that immediately runs a script to send me back to the secure start-up constant reboot. So I need to somehow remove this Rom I think. Unfortunately TWRP is out becuase of the script that runs
I'm not changing any options in Odin. Maybe I should?
Can one of you awesome guys help me please. Is there a flashable Odin Rom that will skip this secure start-up message....?
Long story short - when using wifi my s7 edge started to restart several times until it got to boot loop. I tried various things, enter and exit download mode, factory reset, partition cache clear, nothing helped. I tried to flash stock firmware several times (different versions) but it didn't help. I can go to recovery and download mode, odin recognizes the device and passes the flashing, however it does not boot. Always stuck on "galaxy s7 edge" screen.
Do you guys have any idea what could I do? I was thinking about installing twrp, however will I be able to install it if the setting in developers setting "OEM unlock" was not enabled?
heofizzy said:
Long story short - when using wifi my s7 edge started to restart several times until it got to boot loop. I tried various things, enter and exit download mode, factory reset, partition cache clear, nothing helped. I tried to flash stock firmware several times (different versions) but it didn't help. I can go to recovery and download mode, odin recognizes the device and passes the flashing, however it does not boot. Always stuck on "galaxy s7 edge" screen.
Do you guys have any idea what could I do? I was thinking about installing twrp, however will I be able to install it if the setting in developers setting "OEM unlock" was not enabled?
Click to expand...
Click to collapse
Hello,
You don't have to worry, your phone isn't broken, i flash roms every day so i'm very familiar with does kind of "Errors". I'm here to assist you.
So without the OEM Unlock option enabled your phone won't be able to boot to recovery neither system if you flash a custom rom, flashing the stock firmware via Odin is the only way so try does steps:
1. Download stock firmware for your model from sammobile.
2. Extract the files and place them in the correct tab.
3. Disable auto-reboot in option panel.
4. Soon after it finish flashing, long press volume down and power button until screen turns off, then quickly press volume up, home button and power button.
5. Phone should now boot to recovery from which you have to do a factory reset and wipe cache/data.
6. Restart system.
Phone should boot just fine now, it might take 5 minutes for the first boot, if you're stuck for more than 5 minutes i would kindly ask you to take a picture of your log in recovery.
If you manage to boot the phone go to developer settings and enable OEM unlock then you can flash TWRP and from TWRP a custom rom.
If you have questions and still need help, feel free to pm me for anything, i'm here to help you!
Grettings,
SwitchDeath
So I took it to the service, it was a faulty motherboard.
I have same issue with my s7 edge, but with AT&T version (G935A). I couldn't find the firmware from sammobile as previous instruction from SwitchDeath. Do I have any other option to download the firmware from other source? Nothing seem to work for me from all other forum instructions and downloads, it just stuck in "galaxy s7 edge" screen on and off and not reboot at all. Please help!
Hello everybody. After days of struggling with LGUP I finally managed to flash stock kdz file and boot my LG G6. However after booting I am welcomed with "Encryption unsuccessful" screen telling me that I need to wipe phone to use it. When I click wipe button it restarts itself and shows "erasing" but when that finishes it again shows me that same screen telling me to wipe it again. My bootloader is locked unfortunately, so I can't obviously flash TWRP or anything(I have unlock.bin but I can flash it because OEM unlock is not allowed in settings). I tried flashing with LGUP several more times with different kdz files, but when they succeed again same happens.
Also LGUP does not allow me to use "refurbish" flash mode(I can use only upgrade-so I can't erase the device), so if anyone has an idea how to wipe it off or something. I have feeling like recovery can't wipe it and because of that I always get that "encryption" error. I will post pictures for you to see. Many many thanks for any solution!
The very first step before you even thought about twrp since you already had the .bin file should have been to unlock bootloader.
Sent from my LG-H870 using Tapatalk
I had the same problem. What I did is use uppercat connecting the phone when it was in this screen to restart the process from the beginning.
imsonica said:
I had the same problem. What I did is use uppercat connecting the phone when it was in this screen to restart the process from the beginning.
Click to expand...
Click to collapse
Wait, uppercut would recognize phone when that screen is on, I thought phone must be in download mode for uppercut to work? And also just wondering why can't I wipe the phone, LGUP refurbish doesn't work, as far as I know storage must be formated to break that "encryption secure start up". Thanks for reply
In fact the screen is on in that specific encryption error.
In my case Uppercut was able to perform the operation, basically I stop the boot during encryption at first reboot and I had this error.
Thinking the TWRP recovery was able to fix it I installed it but the problem was still there. But with the TWRP on, the phone reset is not working, only way was to restart all the process, formatting the phone to be able to use it.
imsonica said:
In fact the screen is on in that specific encryption error.
In my case Uppercut was able to perform the operation, basically I stop the boot during encryption at first reboot and I had this error.
Thinking the TWRP recovery was able to fix it I installed it but the problem was still there. But with the TWRP on, the phone reset is not working, only way was to restart all the process, formatting the phone to be able to use it.
Click to expand...
Click to collapse
I was thinking that TWRP can rescue me since there is wipe option available, but I can't tick" allow OEM unlock " to unlock bootloader... So all I am left with is LGUP(uppercut) and stock recovery, and problem is I think none of them can wipe(reset) the phone. LGUP gives me error that "kdz file does not support refurbish flash"(no matter what kdz file I chose) and wipe in stock recovery simply does nothing. And BTW isn't Uppercut same as LGUP just with necessary .dll files so LGUP can work? Thanks
imsonica said:
I had the same problem. What I did is use uppercat connecting the phone when it was in this screen to restart the process from the beginning.
Click to expand...
Click to collapse
Just wondering so you flash everything while on the encryption screen or you went to download mode
I performed a factory reset from within the OS and when it restarted it was stuck on the Samsung splash page. After this I performed a reset from the recovery menu. Now the phone was stuck in a boot loop. At this point I re-flashed the factory ROM from ODIN and it is again in a boot loop. Sometimes it makes it to setting up the apps but just resets again.
For some reason the phone attempts to install an update whenever I enter the recovery and once there it states that it cannot locate files. The location of these files is "E:". I have no idea why it cannot locate anything it looks for and why " E: " is not there if it needs that location as the phone is completely stock.
Did you flash the HOME-CSC or the normal CSC file? I too got into a bootloop after a factory reset from the recovery, so flashing with the CSC file could be useful I guess. Recovery checking for an update always happens for me and it goes to recovery normally after checking.