Helping a friend, I have a T-Mobile s5 here that was working flawlessly on all stock software. Then installed the latest 2.8.3 TWRP using odin and proceeded to make a full backup including EFS to SD Card.
I installed the later CyanogenMod and gapps and then wanted to return to my stock backup to maintain full support for a Samsung gear watch. Rebooted to TWRP, attempted full-restore and restore said it was completed, but was not. It'd get part-way through recovering files and then jump to completed. Odd.
I then downgraded the recovery to 2.8.1 (my device is running that version and backup/restore seems to work great) and then attempted restore again. Says complete but fails and will not boot. Trying to do an advanced-wipe would give me errors and would not complete a simple wipe of System. I tried to restore again but with using md5 verification. With that enabled, the md5's fail- even on EFS.
I then just stock odin-installed stock firmware. The phone booted just fine, upon setting, network was working perfectly., ESN is good, etc. I then turned on WiFi and things were fine. Connected to a WiFi network and shortly after it would soft reboot itself. It'd do this every time I connected to a WiFi connection. I noticed sometimes when I went into the WiFi panel, there would be a message for a moment saying it was in Factory Mode.
So, it will NOT connect to a WiFi network now but everything else seems to be okay. Because we attempted restore of what seems to be a corrupt backup, I believe this could have caused EFS issues and I do not know what to do to fix this.
I have read so many different things and one being that backing up and then deleting the /EFS folder and rebooting may fix the WiFi issues but I didn't dare mess with that.
Any suggestions?
I installed the later CyanogenMod and gapps and then wanted to return to my stock backup to maintain full support for a Samsung gear watch. Rebooted to TWRP, attempted full-restore and restore said it was completed, but was not. It'd get part-way through recovering files and then jump to completed. Odd.
I then downgraded the recovery to 2.8.1 (my device is running that version and backup/restore seems to work great) and then attempted restore again. Says complete but fails and will not boot. Trying to do an advanced-wipe would give me errors and would not complete a simple wipe of System. I tried to restore again but with using md5 verification. With that enabled, the md5's fail- even on EFS.
I then just stock odin-installed stock firmware. The phone booted just fine, upon setting, network was working perfectly., ESN is good, etc. I then turned on WiFi and things were fine. Connected to a WiFi network and shortly after it would soft reboot itself. It'd do this every time I connected to a WiFi connection. I noticed sometimes when I went into the WiFi panel, there would be a message for a moment saying it was in Factory Mode.
So, it will NOT connect to a WiFi network now but everything else seems to be okay. Because we attempted restore of what seems to be a corrupt backup, I believe this could have caused EFS issues and I do not know what to do to fix this.
I have read so many different things and one being that backing up and then deleting the /EFS folder and rebooting may fix the WiFi issues but I didn't dare mess with that.
Any suggestions?