I tried making a backup on safestrap recovery but it said something like error making backup forsystemomag.
Any idea what that's about, and how I can make one?
I heard this error occasionally occurs restoring too.
I tried wiping dalvik beforehand and still no luck.
I get: Error while writing /systemomag
Any suggestions?
Related
I had a issue on Xposed module I had installed that stopped the phone from working.
Prior to making any modifications to the rom done a backup in TWRP just in-case.
Upon failure in tried to restore but in-countered this.
I would get "could not access /data/data/com.android.vending" followed by "too many files open"
This kept me from restoring the backup...and doing any wiping as wiping would also have this issue.
I tried a format data that seemed to work.
I then used Odin to reload the EMJ9 and it passed
But in it's reboot the "Note 2" wound only flash and not boot into the system. Same with trying after a battery pull. Same thing when trying to get into recovery.
Tried to Odin again but it now fails from the start. (tried other D/L's with same result)
Not sure what other options......
khw1959 said:
I had a issue on Xposed module I had installed that stopped the phone from working.
Prior to making any modifications to the rom done a backup in TWRP just in-case.
Upon failure in tried to restore but in-countered this.
I would get "could not access /data/data/com.android.vending" followed by "too many files open"
This kept me from restoring the backup...and doing any wiping as wiping would also have this issue.
I tried a format data that seemed to work.
I then used Odin to reload the EMJ9 and it passed
But in it's reboot the "Note 2" wound only flash and not boot into the system. Same with trying after a battery pull. Same thing when trying to get into recovery.
Tried to Odin again but it now fails from the start. (tried other D/L's with same result)
Not sure what other options......
Click to expand...
Click to collapse
Update. Looks like got the phone back by reinstalling the PIT file. Now to re-root.
Hello,
I have a Kobo 10HD and rooted and installed CWM v6.0.5.1. I made a backup before and then installed Titanium Backup update.zip. Installation of that zip caused a bootloop (back to CWM). No problem, I thought, I can just restore the backup I made. No dice. I tried to restore the backup and still bootlooping. I even tried to installed the stock ROM ZIP and it fails with the message: (from recovery.log):
nv_copy_blob_file: couldn't get the device path
script aborted (no error message)
script aborted (no error message)I:Legacy property environment disabled.
E:Error in /data/media/0/macallan-ota-932.zip
(Status 7)
Installation aborted.
I have read that some people have had success installing this zip using stock recovery, but I have no idea how to get stock recovery.
Also, I noticed using adb shell that CWM does actually put all the files back into system and other areas during the restore. Upon reboot, and subsequent bootloop, the system files are gone. It must have something to do with an automatic script that is running after restore.
SOLVED!
zhzhou said:
Hello,
I have a Kobo 10HD and rooted and installed CWM v6.0.5.1. I made a backup before and then installed Titanium Backup update.zip. Installation of that zip caused a bootloop (back to CWM). No problem, I thought, I can just restore the backup I made. No dice. I tried to restore the backup and still bootlooping. I even tried to installed the stock ROM ZIP and it fails with the message: (from recovery.log):
nv_copy_blob_file: couldn't get the device path
script aborted (no error message)
script aborted (no error message)I:Legacy property environment disabled.
E:Error in /data/media/0/macallan-ota-932.zip
(Status 7)
Installation aborted.
I have read that some people have had success installing this zip using stock recovery, but I have no idea how to get stock recovery.
Also, I noticed using adb shell that CWM does actually put all the files back into system and other areas during the restore. Upon reboot, and subsequent bootloop, the system files are gone. It must have something to do with an automatic script that is running after restore.
Click to expand...
Click to collapse
After a few more hours of fiddling, I was able to get the device back up. I wiped absolutely everything manually with CWM (format /X) instead of Wipe/Factory Reset. The factory reset was not clearing the SD card, but format/data and /data/media cleared it. I then applied the stock zip that is available via adb sideload. Installation failed with the same error, but I rebooted with the adb reboot command. The device booted back into Kobo stock requiring several updates. It actually got stuck repeating one update several times until I booted back into stock recovery and cleared data and did a factory reset. The update applied correctly and then another upgrade came (a total of three upgrades). I rooted again and we are back in business.
For some reason, I think the key step was manually wiping /data/media. I'm not exactly sure why this would cause a bootloop for CWM restore. Anyway, I hope this helps someone else who may run into a similar issue.
Hi zhzhou!
Just a quick question:
do you happen to remember if stock recovery for Kobo was CWM? I'm in process of restoring stock ROM +recovery and little bet surprised to see CWM after flashing stock recovery
Thanks a lot!
zhzhou said:
After a few more hours of fiddling, I was able to get the device back up. I wiped absolutely everything manually with CWM (format /X) instead of Wipe/Factory Reset. The factory reset was not clearing the SD card, but format/data and /data/media cleared it. I then applied the stock zip that is available via adb sideload. Installation failed with the same error, but I rebooted with the adb reboot command. The device booted back into Kobo stock requiring several updates. It actually got stuck repeating one update several times until I booted back into stock recovery and cleared data and did a factory reset. The update applied correctly and then another upgrade came (a total of three upgrades). I rooted again and we are back in business.
For some reason, I think the key step was manually wiping /data/media. I'm not exactly sure why this would cause a bootloop for CWM restore. Anyway, I hope this helps someone else who may run into a similar issue.
Click to expand...
Click to collapse
Stock was definitely not CWM. It was a long time ago and I no longer have the device, but I think CWM was still present after restoring stock. I think you'll need fastboot if you want to flash the stock recovery image back on. But why do that? TWRP is now available for the device.
Thanks for quick reply! I had CM on it but had some artifact issues so wanted to revert to full stock, even recovery
zhzhou said:
Stock was definitely not CWM. It was a long time ago and I no longer have the device, but I think CWM was still present after restoring stock. I think you'll need fastboot if you want to flash the stock recovery image back on. But why do that? TWRP is now available for the device.
Click to expand...
Click to collapse
On my Galaxy S5 (SM-G900F, Android 4.4.2) I made a nandroid backup of "everything" (boot, cache, recovery, system, etc.) about six weeks ago (using PhilzTouch recovery). Yesterday I tried to restore it, and it seemed to work but when Android had booted up I started getting force closes all over the place.
I tried wiping cache and data, but it didn't make any difference. I had a look at the log for one app when it crashed, and it was due to java.io.IOException: open failed: EACCES (Permission denied). I have not changed anything on the SD card since I did the backup (sent the phone in to repair a dead pixel but they wouldn't do it on warranty, so I got the phone back the way it was).
One idea I had was that something was messed up with the file permissions, so I tried the app "Fix permissions" but that didn't help either.
I then thought I'd try to flash Lollipop using FlashFire. Everything went well, and I was really surprised to see that now all the apps were working flawlessly! So to get back to KitKat (which is what I want), I then tried flashing the KitKat ROM (BTW, these are all official samsung ROMs from SamMobile. Now it didn't even boot properly, it got stuck on "Android is upgrading - Starting apps...". Tried wiping data/cache again but nothing worked.
I have since tried repeating the but without flashing Lollipop (i.e. flashing the same ROM as the one in the nandroid backup when running the restored KitKat installation), but it always gets stuck on the "Android is upgrading" screen (have tried many combinations of boot/preload/system/etc).
So it seems that I CAN restore the KitKat nandroid backup, but it's unusable "as is" because of most the apps force closing. However, if I flash Lollipop "on top" of the backup, everything works.
Can someone explain this, and possibly provide a solution? I'd really like to have this phone exactly as it was when I did the nandroid backup.
Hello Everybody,
first of all thanks for reading my thread.
I have a problem...tried to flash a custom kernel 2 days ago, and it went wrong. So I had to flash official fw again to come back to Xiaomi.eu then.
Before I tried to flash the kernel, I made a backup with TWRP.
My problem now is, every time I try to restore this backup, TWRP gives me an ERROR 255 when it tries to restore data partition.
Error message says something with "error create fork" or similar.
Have tried different things, also for example to wipe data before, or to format data, but nothing helps.
Device is decrypted on start of TWRP. So that is not the problem, I guess.
Anyone eventually has a clue/a tipp what I can try or what may be the problem?
Or isn't LRTWRP generally not able to restore backups?
Would be grateful for any help... ?
So I created a full backup of my device using TWRP and now just tried to restore it and it's just completely messed up my device. I got an error saying extracttarfork() process ended with error=255. My device was a custom timurs rom which I dont remember how to go through the whole process again. From the videos I have seen apparently I need to reflash it. How do I do that? What files do I need? Can someone please help
So, although the message logs shows that it formatted and wiped the system, I just thought i would give it a restart and see if I get a bootloop. But it seems to have not done anything of such like deleting or wiping because the system is still the same. However, I did notice my bootanimation logo has gone back to the version before the backup. So I don't know what exactly has happened.
Is it possible on TWRP to do a clean fresh install and then flash the Timurs Kernel rom back on? My tablet is in fix mode and I don't really have access to the volume buttons to force TWRP easily. So I'm thinking I would like to do a clean android refresh and flash the kernel again.
It's definately messed something up because now when I try to transfer a file into the System partition using TWRP i get error saying Full SELinux support is present. This never happened before. Any ideas please on how I can just start fresh on this?