My wife has the ls980 and recently installed optimus de on it. Everything was great for over a week until this morning. The phone get very hot and froze. Upon loading back up it will not find any networks and it seems that the efs partition is corrupt as all of the device id numbers read 0. Then after a minute or two it will always lock and restart. I've tried to wipe and reinstall to make it run without restarting to get the pictures off of it, and it didn't help.
My main questions would be is would the efs being corrupt cause restarts, how would I fix the efs, and does flashing a back to stock file wipe the internal storage?
Phone randomly rebooted itself (hotbooted) and once it came back online, I noticed that my IMEI was gone. Any solutions?
EDIT: EFS Backup was deleted last time I flashed stock. Forgot to make another.
Hi all,
Some time ago i asked, and received, some support on these forums on how to properly carry out a nandroid backup... following the sound advice i got, i carried out my backup (using TWRP for the record, with all the options checked), and stored it away for a rainy day... said day came yesterday, when i messed up my system and rendered it instable (i tried to manually delete the dalvik cache directory in order to free up the 2,5GB of space it was taking)... since i knew there was i high chance of this ending in disaster, the last thing i did before the delete was carry out another nandroid, so i could easily return to where i had left off... how wrong i turned out to be
as soon as i the system became instable following my experiment of deleting the d. cache directory, i recovered the latest nandroid (i.e. the one i had made just hours before) and everything seemd to go smoothely until the first reboot... when the following happened:
- first reboot after recovery took ages, much like the first reboot following the flashing of a new rom... not the end of the world, but that was the first sign that all was not well
- the status bar disappeared, and there was no way of making it come back (i.e. nothing to do with the launcher, i typically use apex but i i tried switching to both nova and touchwiz which i also kept up to date but the stats bar was nowhere to be seen)
- even if not having a status bar with all the info on it is acceptable (which of course it isn't, but lets just say), the sytem became completely instable after 5minutes of operation... with each app taking turns to shutting down until i kept getting the message "system UI has closed" over and over, to the point that doing a reboot was challenging since i barely had the time to press on the screen between instances of this bloody error message appearing...
...i did of course try and return to my older nandroid backup, but... lo and behold... exactly same behaviour...
so now i have resorted to formatting the internal memory card and flashing a new rom and basically starting over... just what i hope the nandroid would spare me basically :/
question is: does this sort of error sound familiar to anyone? can someone give me a tip maybe on what i may have done wrong?
any opinion, tips& advice much appreciated
I have the exact same problem. It happens on TW Lollipop ROMs. Haven't found a fix. I'm using Philz Touch Recovery and the old no knox bootloader.
Anyone? I have researched this but cannot find any similar problems reported... it can't just be me and pavelcheto...
Maybe it a recovery fault. Faulty backup or faulty restore.
No problems with my older backups. I restored my KitKat TW backup, working fine. Restoring CM12 backups also works fine. I've looked for a new recovery, Philz is discontinued, CWM hasn't been updated for a year and I really don't like TWRP.
I use TWRP 2.8.3.0 and never have (and hopefully never will) encountered any issues with restoring backups.
Considering i recovered 2 separate backups for a total of 3 times (i tried recovering the first backup twice) i doubt the issue was with the recovery itself... however since pavelcheto had no issues with the kk recovery maybe it could be lollipop related?
Anyone successfully recovered a lollipop nandroid backup?
platypus78 said:
Considering i recovered 2 separate backups for a total of 3 times (i tried recovering the first backup twice) i doubt the issue was with the recovery itself... however since pavelcheto had no issues with the kk recovery maybe it could be lollipop related?
Anyone successfully recovered a lollipop nandroid backup?
Click to expand...
Click to collapse
I recovered my lollipop gpe backup a couple of times without a problem.
Data encryption may cause restoring problems.
I have restored CM12 backups (based on 5.0.2) serveral times, no problem there. I've had issues only with TouchWiz Lollipop ROMs, I have tried different custom roms, all get bugged at restore.
pavelcheto said:
I have tried different custom roms, all get bugged at restore.
Click to expand...
Click to collapse
Just to make sure I understand correctly : you mean all TW custom roms you've restored have had problems?
Wonder if anyone else has managed a bug-free restore of a 5.x TW?
Yes, but only on Lollipop. KitKat TW roms restore just fine. I am using Philz Touch Recovery. I have tried 3 different TW Lollipop roms and they all fail to restore properly. No wallpaper, black wallpaper and no status bar. And after a minute or two System UI starts crashing. If then I do factory reset from recovery and the rom starts normally (welcome guide and stuff) and works fine.
bumping this thread because i cant seem to find a solution for this anywhere.
TheAwesomeBit said:
bumping this thread because i cant seem to find a solution for this anywhere.
Click to expand...
Click to collapse
There's no solution for this as per comments above. TW LP is not restorable. You can flash a new lollipop ROM tho'
Sent from my GT-I9505
Hey guys,
First of all sorry for my not perfect english
Well pre story: my mom and me using both Note 4 but my one has WiFi issues since day 1 and she told me today to change the phones bcuz she dont care if 1mb/s or 5.
So I did something i never done before -.- rooted her Phone, installed twrp and made a full backup via twrp(ticked everything active) so.. moved the backup file into my SD and restored on my Phone.
Everything went good but i recognized a lot of lag after first Boot AND WiFi dont remember the saved Networks. Turning WiFi off happens instantly but turning back on Takes around half to a whole Minute.
What i tried so far:
- factory reset via twrp
- factory reset via Standard cwm
- flashed Modem and bootloader with odin (cok1)
- reverted back to kitkat
- flashed clean 5.1.1 cok1 with odin
Tried something with .pit file while installing but didnt recognize any difference..
So.. May the restore file destroyed some specific partitions? I havent got any clue What to do next :/
Any help or advise ?
Maybe i shouldnt restore efs to my moms N910F?
Nvm solved after i restored my luckily made efs backup
I can't figure out if I do so any help appreciated.
Everything on my Note 4 works fine except lags and crashes, only thing that has managed to fix that is the Wake Lock App but obviously it's training the battery.
The other issue I had was Private Mode not enabling which still isn't, and also WIFI was not remembering passwords so I used BuildProp Editor to change that Securestorage.support to falst from true and that fixed that.
Was getting the DM-Verity Failure issue whilst on stock unrooted so rooted it and added TWRP to fix that issue.
IMEI & Baseband etc... all showing up perfectly fine too.
Can't figure this one out.
I'm now rooted (thinking this would solve the issue) and on stock.
Any ideas appreciated.
Thanks.
Sorry for the extremely delayed reply, if you haven't already figured it out you probably do have a corrupt EFS. I've been messing with a refurbed unit I got for my wife off and on for months and finally just manually formatted /efs via twrp and rebooted. The stock rom rebuilt things no problem and the lag is gone. I know there was a problem with EFS as logcat showed a *TON* of errors from the SecureStorage package. After formatting the errors are gone. I made several backups via twrp and manually via tar just in case.