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.
Related
Hi guys.
I got a problem.
Got tired of lags, so i decided to wipe (data + dalvik) and reinstall Omega 27.1.
Now i can't boot up the phone - it just starts up CWM (6.0.1.2) when i reboot. Have tried to pull battery and when i insert it recovery just comes up.
What have i missed?
I have tried to install again, with and without wipes but still the same.
Can't restore nandroid either. Getting error on restoring /data, and just comes back to CWM again.
I'm kinda stuck.. ideas?
EDIT:
Just did a nandroid restore, error on restoring /data as always, but i rebooted and got into Android. I had to type in my google account information again, and all apps crashes all the time.
So I rebooted to recovery, and installed 27.1 (did a full wipe again), and now i can't get past recovery again.
Wtf?
mrBira said:
Hi guys.
I got a problem.
Got tired of lags, so i decided to wipe (data + dalvik) and reinstall Omega 27.1.
Now i can't boot up the phone - it just starts up CWM (6.0.1.2) when i reboot. Have tried to pull battery and when i insert it recovery just comes up.
What have i missed?
I have tried to install again, with and without wipes but still the same.p
Can't restore nandroid either. Getting error on restoring /data, and just comes back to CWM again.
I'm kinda stuck.. ideas?
EDIT:
Just did a nandroid restore, error on restoring /data as always, but i rebooted and got into Android. I had to type in my google account information again, and all apps crashes all the time.
So I rebooted to recovery, and installed 27.1 (did a full wipe again), and now i can't get past recovery again.
Wtf?
Click to expand...
Click to collapse
If you can get into download mode, flash a stock rom samsung www.sammobile.com with ODIN, then get root permissions and cwm with ]cf-root 6.4
devid801 said:
If you can get into download mode, flash a stock rom samsung www.sammobile.com with ODIN, then get root permissions and cwm with ]cf-root 6.4
Click to expand...
Click to collapse
Yes, it seems to be the only thing to do..
But does anyone know what is causing this?
Can't be the boot.img, because restoring the boot (wipes+restores) doesn't work. And installing a new rom also adds a new boot.img.
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
Alright, I know enough to be dangerous. I rooted my Samsung tab a 10.1 by installing twrp and then super su, all went fine. I then began to try and make a nandroid back up. It kept saying unable to mouth data, so I read a little and I changed data format. This caused a boot loop. Went in and changed back data format and used twrp to reset. All was fine again. I then attempted to use titanium backup. I recited a message backup was successful and reboot. I rebooted and now a boot loop. I then tried to reset with twrp and my file is gone. So, I downloaded what I thought was the right firmware to flash with Odin but just made that worse. Does anyone have a download for a rom I can flash with Odin to get this thing going. I have downloaded a couple and the either don't work or are the wrong one. SM-T580.
tlstaggs said:
Alright, I know enough to be dangerous. I rooted my Samsung tab a 10.1 by installing twrp and then super su, all went fine. I then began to try and make a nandroid back up. It kept saying unable to mouth data, so I read a little and I changed data format. This caused a boot loop. Went in and changed back data format and used twrp to reset. All was fine again. I then attempted to use titanium backup. I recited a message backup was successful and reboot. I rebooted and now a boot loop. I then tried to reset with twrp and my file is gone. So, I downloaded what I thought was the right firmware to flash with Odin but just made that worse. Does anyone have a download for a rom I can flash with Odin to get this thing going. I have downloaded a couple and the either don't work or are the wrong one. SM-T580.
Click to expand...
Click to collapse
Alright, I was using an olsee version of odin, got the new one and I was able to flash a rom. It says tab a 6 on boot up bit it is functional. Now my question? Can anyone recommend a custom rom that is nebiew friendly. I'm food at following directions and problem solving but I about had a panic attack, I just got this $300 thing. Sigh off relief for at least getting it functional again.
Hmm
Ok so I have flashed a stock rom, 6.0.1, flashed TWRP, and installed SuperSU. all is working well again. However I am still getting "unable to mount data" message in TWRP when i try to make a backup. If i uncheck data on the list it backs up fine. This is what got me in that boot loop pickle before when i tried to change the data format. What data format? Idk, im scared to jack with it anymore, and im done with titanium backup, it has burned me in the past, though i think what went wrong there was when i backed everything up i then went and change data format and after all that restored and the backup was in a different data format. Idk newbie guess. I am just trying to getting a reliable nandroid backup. Anymore ideas? Perhaps i should just leave it alone and be happy with just having root.
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.
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?