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.
Related
I booted my device with wrong image now it is turning on in loop.
Error Showing
Invalid Boot.img or Recovery.imgo fact
This may be due to downloading the non-secure image from 3rd sites.
Please POWER-OFF and flash lenovo's official image.
Flashtool should be a good option for image downloading
What can i do.
I was not able to Factory reset my device, so i downloaded recovery file from forum and tried to recover but now it s stuck
I tried to root my phone.. without installing any custom recovery i just installed magisk manager then the zip file and started recovery booting (by pressing home+power+vol up). First it showed installing system updates then its displayed that failed to open recovery cause no such file. Now i cant reboot my device. There is a boot loop. I have tried wiping cache partition, data factory reset but still it dosn't opens. its stuck in samsanug logo page and keeps on booting again and again.
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
Hello,
I tried to flash my S8 with TWRP with Odin. OEM and Debugging is active. After I had some failed flashes, when I now boot into revocery (VolUp+Bixby+Power) there is a blue background with a yellow warning sign and a dead android guy and "no command" but after some seconds I get into recovery mode. Even though I made factory reset and wipe I still get the error everytime I boot into recovery. When I now go to bootloader, flash TWRP with Odin I get a succesfull-message from Odin. But when I boot into recovery afterwards there is still the Android Recovery and not TWRP.
I tried different Odin and TWRP Versions and deactivatet F.reset and autostart.
Can someone help me? According to google search the blue background with the dead android guy should be gone after factory reset and wipe but its still there.
crackhead131 said:
Hello,
I tried to flash my S8 with TWRP with Odin. OEM and Debugging is active. After I had some failed flashes, when I now boot into revocery (VolUp+Bixby+Power) there is a blue background with a yellow warning sign and a dead android guy and "no command" but after some seconds I get into recovery mode. Even though I made factory reset and wipe I still get the error everytime I boot into recovery. When I now go to bootloader, flash TWRP with Odin I get a succesfull-message from Odin. But when I boot into recovery afterwards there is still the Android Recovery and not TWRP.
I tried different Odin and TWRP Versions and deactivatet F.reset and autostart.
Can someone help me? According to google search the blue background with the dead android guy should be gone after factory reset and wipe but its still there.
Click to expand...
Click to collapse
Sounds like incorrect installation of TWRP.
Did you boot up into TWRP straight after installation? not system.
Note: - USB Debugging is not required.
- Just start up odin leave default settings - In options section you can untick Auto Reboot then flash TWRP then boot into TWRP manually before starting system.
Hello everyone,
I flashed teamwin today and afterwards lineagos. All worked like a charm. However, I tried getting root access using this tutorial (
), but there was an error message when I installed the "no-verity" zip. I rebooted it, all went normal and after another restart it now is stuck at the teamwin page.
I can go into download modus, but flashing teamwin again, does not result in any changes. Teamwin version is 3.6.2_9-0.
What can I do?
Thanks
Since I can't turn it of (I have to either go into download mode or get stuck at the twrp screen), I would really appreciate fast help
E: Fastboot and adb unfortunatelly don't seem to work, because the phone is not listed when I type "adb devices".
E2: I downloaded the "latest" Firmware from Sammobile, Flashed (only) the AP file (2,6 GB), choose "Auto-reboot" in Odin and after the reboot I managed to get into the normal bootloader -> Wipe cache and factory reset.
After restart Android 8 started to get set up.
If you encounter this: Be careful and make sure your battery is charged! Because when stuck in bootload it gets hot and apperently drains the battery quite fast.