In the last few days, my N7100 (which I gave to wife) has gone twice in bootloop by itself while idling.
Every time TWRP showed that the phone was unable to mount /efs.
By restoring the efs partition from a nandroid backup I could restart it again both times.
The double failure of /efs at less than a week distance makes me think there's something very wrong in the phone.
After first efs restore I did a factory reset and installed only 2-3 fundamental apps, so I don't think it's the fault of a rogue program.
Do you think my device is at the end of its life cycle? Is there anything I could do to fix it?
Thanks.
'SHAME'sung...?
Only God Can Forgives!?
Related
so i created a nandroid backup this morning through rommanager and it took WAY longer than usual. roughly 25 minutes to complete. and at then end it said there was some error backing up /data. didnt seem like a big deal to me. so i go back, delete some of the older nandroids to make space so i could redo the backup in CWM.
tried backing up again, it said i dont have enough data. then i rebooted my phone, and i only have 193mb left of space.
does anyone have any ideas how i can recover the lost space? or just how to fix this in general?
Are you looking in system/storage?
I hope this is the right subforum, there are _so_ many q-q
Hello,
Yesterday I was up to surfing on my GNex running CM10 nightly 2012-08-2?, but it just hung, vibrated, showed me the Google logo and booted up again. This is not unusual since it is a very early build, but when it was up again and demanded my PIN, I could hardly enter 3 digits when it hung and rebooted again. After 6 times it really annoyed me and I pulled out the battery.
I tried booting in Safe Mode, but that didn't work either. So I wiped system and both caches, flashed the same build again, same problem
I can imagine that wiping data would help, but my last backup is quite a few weeks old and I don't want to lose my data so this would be the very last solution.
I hope someone will be able to help me
qsuscs
Oh, maybe this could be important: I use ClockworkMod Touch 6.0.1.0
You could try to flash the newest nightly and see if that works, but in the end I think you are going to have wipe your data. You could make a backup from cwm and try wiping than restoring the backup. I don't know if that would help any but it could be worth a shot.
And dont restore app/system data.
Sent from my i9250
If you can still get into the recovery, you can run a backup and then restore apps/data from a nandroid via titanium backup once you get it up and running.
Nandroid does not really work.
Code:
ClockworkMod Recovery v6.0.1.0
SD Card space free: 7426MB
Backing up boot image...
Backing up recovery image...
Backing up system...
Freeing space...
Done freeing space.
Backing up data...
Error while making a backup image of /data!
Does anyone know why it doesn't, or maybe another backup solution?
Could I do a backup with another recovery? Or could flashing anotherr recovery even cause data loss?
Triple post hope you can forgive me
So I flashed TWRP. Nandroid didn't work there, too, but I think I know the reason: /data needs to be mountet read-only for the backup, but this is impossible when it is written to the internal storage (/data/media). And since neither TWRP nor ClockworkMod have a TCP stack, I'll need an USB-OTG-adaptor and an USB flash drive. Luckily, I know someone who has one, gonna ask him tomorrow...
I started having this problem ever since I upgraded my phone to 4.1.2 T989UVMC6. Sometimes when the power button gets accidentally pressed for 10 seconds in my pocket, the phone vibrates 3 or 4 times, then gets to the Galaxy SII screen and gets stuck there. A couple of times it got to the glowing Samsung logo, but then it got stuck there. I tried everything to get it to boot (rebooting, wiping cache, dalvik, fixing permissions) but nothing worked. I searched everywhere for a solution but got nothing. Some people said it's caused by the Preload partition, but that got me nowhere. The only thing I could do at that point was to restore my latest backup. I would lose all my changes since the backup but at least it would boot and even reboot normally.
After many experiments, I realized the problem is with the Data partition... So my current solution when it gets stuck at boot:
1. Reboot into recovery.
2. Create a backup of just the Data partition (you can do a full backup if you want but this way is just faster).
3. Restore the backup you just created.
4. Run the Infamous Cache Wipe (probably not necessary, but doesn't hurt).
5. Reboot and enjoy!
The only problem I noticed so far, when doing the backup to external SD, I would lose all my messages (SMS and MMS). Doing the backup to internal SD, everything gets restored normally.
If anyone has more insight into this issue, or has a better and more permanent solution, please share.
If this helps you as much as it helps me, please hit Thanks
I never heard that before!!! Thanks! :s
Sent from my cell phone telephone
Edit fiftyfuknmillion;
soooooooooooooooo, the error was a lack of space on the internal memory. Deleted some crap and the restores occured fine!
Particular data recovered and backed up externally.
sooooooooo, back to my original question; how the **** do I delete EVERYTHIGN on the phone before handing it back??
Edit3; ok, title edit. My major concern is not been able to get this restore to work. Anyone able to help.
extractTarFork() process ended with ERROR: 255
Short history;
1) HTC M8 on TWRP 3.0.20, rooted, running fine, backed up no issues. Screen breaks, getting warrenty replacement. Create new backup, System Data and Boot. Completes fine to microSD.
2) return phone to stock recovery before taking into store as to not void warrenty, stock recovery loads fine, warrenty approved.
3) go to return phone to previous state (TWRP & restore that backup) and the backup fails with above Error 255.
4) complete format to 6.24.841.1 including recovery - loads fine, phone looks brand new with exception of some data remaining on internal storage.
5) tried multiple things, restoring just the boot, restoring only data, wiping this and that. So far, nothing will let the Restore succeed.
Any help would be much appreciated!!!
Hi all;
My beloved M8 had vertical line on the touch screen die so I couldn't touch in that zone - 10 days before the warranty was due to end - lucky! Telstra honnored the warranty without issue, and they are replacing the unit with a new M8.
Questions;
1) Can I take my Backup from TWRP 3.0.20 (on an external microSD) and load it onto the new M8? best method or just install TWRP and restore this backup?
2) in past experiences I had issues with restores and rooting, and I've always noticed certain data is still on the phone after reloading a "clean install". What is the absolute best way to delete all data? (I have a tinfoil hat sometimes). I want to delete absolutely everything possible so the phone is effective factory new.
Thanks for your support.
Edit: I just tried to restore to a Backup created 2 nights ago and received Error 255? Any ideas why?? (still using same original M8 - replacement not here yet).
Edit2; extractTarFork() process ended with ERROR: 255
it appears I can't even load my last backup from 2 nights ago. What have I done wrong??? It was made with TWRP 3.020 and using the same 3.0.20 to reload it.
Not familiar with Error 255. Maybe try using the TWRP "Format data" button in the Wipe section; in case there is some data corruption preventing the restore?
Hello guys,
I have a question, yesterday I made a copy of all the partitions of the phone, one by one ... in qfil, using the partition manager.
The thing is, I wanted to test things and save my setup before formatting.
When I finished testing things, I started flashing the partitions one by one again. When I finished, I turned on the phone and I got a screen that said:
"Could not decrypt (or something like that), memory will be erased." Then it started to format data alone. And the Rom appeared at boot with nothing of mine configured, nothing of the backup, just like a factory reset.
Can someone help me to know what has happened? Do I need to flash the dm-verity-forceencrytp when restoring with qfil?
All I want is to restore my backup of .bin files
Before restoring, I flashed the base kdz of my backup. I do not understand that it could have gone wrong, or it could have gone wrong, and the backup is done by another method, other than backing up each of the partitions.
have you found any solution for this ?. I have the same problem.