Hi everyone,
I am looking for a solution to recover my Samsung Galaxy S7 (SM-G930FD) from a bootloop, without TWRP. I have read through many posts to find a solution, but not have worked for me. Please read the full details before offering a solution.
- I rooted my phone, successfully, using CF Auto Root (via Odin). It was working fine for several days
- I installed Hide My Root from the Google Play Store, which did not work
- I installed XposedInstaller_3.0-alpha4.apk
- I installed TWRP Manager from the Google Play Store
- I installed BusyBox from the Google Play Store
- I downloaded xposed*.zip (xposed-v86-sdk23-arm64.zip) and xposed-uninstaller*.zip (xposed-uninstaller-20150831-arm64.zip)
- I installed TWRP. I did a lot at once, so some steps are a little fuzzy right now.
- I booted into recovery mode (TWRP) and completed a backup for the data, to the SD card.
- In recovery mode, I then selected BOTH zip files for install. Once that completed, the phone restarted and stuck at the Samsung logo.
- I booted into download mode and tried CF Auto Root again, with no success.
- I booted into recovery mode, but TWRP does not seem to appear. It goes to the default Android Recovery with the following options:
> Reboot system now (did not help)
> Reboot to bootloader (did not help)
> Apply update from ADB ("Update from external storage is disabled")
> Apply update from SD card ("Update from external storage is disabled")
> Wipe data/factory reset (did not help)
> Wipe cache partition (did not help)
> Mount /system (did not appear to do anything)
> View recovery logs (lists various logs)
> Power off (turns off phone)
Specifications:
- Samsung Galaxy S7 (SM-G930FD)
- Dual Sim
- International
- Exynos 8890 Octa-Core
- Android 6.0 (Marshmallow)
If you need any additional information that will help you determine a solution, I will attempt to provide to you what I can. I am only looking for possible solutions from the point in which I am at now, not what I did wrong or the correct way to go about doing it. It's a little too late for that now, isn't it? :eek:
Thank-you in advanced,
Brandon
I am looking for a solution to recover my Samsung Galaxy S7 (SM-G930FD) from a bootloop, without TWRP. I have read through many posts to find a solution, but not have worked for me. Please read the full details before offering a solution.
- I rooted my phone, successfully, using CF Auto Root (via Odin). It was working fine for several days
- I installed Hide My Root from the Google Play Store, which did not work
- I installed XposedInstaller_3.0-alpha4.apk
- I installed TWRP Manager from the Google Play Store
- I installed BusyBox from the Google Play Store
- I downloaded xposed*.zip (xposed-v86-sdk23-arm64.zip) and xposed-uninstaller*.zip (xposed-uninstaller-20150831-arm64.zip)
- I installed TWRP. I did a lot at once, so some steps are a little fuzzy right now.
- I booted into recovery mode (TWRP) and completed a backup for the data, to the SD card.
- In recovery mode, I then selected BOTH zip files for install. Once that completed, the phone restarted and stuck at the Samsung logo.
- I booted into download mode and tried CF Auto Root again, with no success.
- I booted into recovery mode, but TWRP does not seem to appear. It goes to the default Android Recovery with the following options:
> Reboot system now (did not help)
> Reboot to bootloader (did not help)
> Apply update from ADB ("Update from external storage is disabled")
> Apply update from SD card ("Update from external storage is disabled")
> Wipe data/factory reset (did not help)
> Wipe cache partition (did not help)
> Mount /system (did not appear to do anything)
> View recovery logs (lists various logs)
> Power off (turns off phone)
Specifications:
- Samsung Galaxy S7 (SM-G930FD)
- Dual Sim
- International
- Exynos 8890 Octa-Core
- Android 6.0 (Marshmallow)
If you need any additional information that will help you determine a solution, I will attempt to provide to you what I can. I am only looking for possible solutions from the point in which I am at now, not what I did wrong or the correct way to go about doing it. It's a little too late for that now, isn't it? :eek:
Thank-you in advanced,
Brandon
No comments:
Post a Comment