I have a Samsung Galaxy Tab2 10.1 GT-P5110. I have TWRP 3.1.1.0 running OK. Trying to restore a backup from the three I have, because the battery died having been left on and it now longer boots.
Lineage 13.0-20171104-nightly-espressowifi-signed.zip
Restore appears to go OK. Reboot to system, and it gets to STARTING APPS. Then reboots, over and over.
On one occasion it got to the opening screen before rebooting. Tried TWRP and install and that fails with "Updater Process ended with error 7. Error installing zip file." Tried putting a fresh zip file on the SDCARD but still not working.
I think it is possiblely something to do with the apps reinstall.
Is there anyway of stopping installing the apps, or has anyone other pointers?
Thanks
Related
I have a Galaxy Note 2 i317, and use a Macbook pro 2011. I successfully rooted my note 2, and suceeded in installing Paranoid android 3.10, not Gapps. When i went to run it, it said that the keyboard had stopped. I tried to flash Gapps to fix this, (B1-DHO-GAPPS.zip). After flashing it, the phone booted properly, but before i could reach the unlock screen, the error "Unfortunately, the process com.google.process.gapps as stopped." appeared, and when i clicked ok, it changed to "Unfortunately, Android Keyboard (AOSP) has stopped." and then to "Unfortunately, Setup Wizard has stopped." I have tried multiple times to format and erase all data, clear cache, and clear dalvik, reflash the rom and gapps, or just the rom, and then re-clear the cache, but the error continues to occur. I tried to replace GAPPs on my microsd, but my computer now refuses to read it, and Android File Transfer won't connect to my phone. Really, I am fine with not having a rooted Note 2 at this point, I would just like for it to work. Please help.
Answer?
Ok before doing anything else , just restore your note 2 to stock ROM, here's how to :good:
First download the stock ROM and drivers (if you don't already have the drivers) - Click here
Download odin if you don't have it
Here's a tutorial to flash roms to galaxy note 2 using odin - click here
Hit the thanks button if i helped
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.
Hey all, so I decided to go from stock rooted to a custom rom, and see the progress since I last tried it and I encountered the following problem:
I formatted data and factory reset, and then I installed the custom rom, followed by the GAPPS.
Twrp rebooted every time I tried installing Gapps, so I was confused.
The following error occurred when before Aroma started:
"E:Legacy environment property did not initialize successfully. Properties may not be detected"
The next thing I did was I rebooted recovery, no cigar. I tried reinstalling the recovery, no cigar.
I tried formatting data again, and got the error that /data can't be mounted now. This started to worry me lol.
So I tried repairing it and then rebooting, and I tried updating to a newer TWRP but even there, the twrp version won't update. Its still the same number.
I'm too afraid to reboot and see if the rom boots or not, but when trying to flash even a stock rom ZIP it tells me the following:
"This package is for "Joan,h932" devices; this is a ""."
so twrp doesn't know what phone I have?
I am trying right now to restore my TWRP backup but it doesn't want to restore the data, so I'm trying without.
If you can help I would appreciate it very much!!
Here are the screenshots https://imgur.com/a/SLCPdIQ
EDIT: I finally figured it out. Hitting the reboot menu did nothing, because it was for some reason stuck and just rebooted into the same recovery version with the glitch.
I had to do a hard reset, and the finger dance again, and now everything is fixed.