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
Related
I flashed the following KA6, and I didn't realize it would wipe my apps and contacts. I took a nanroid backup using CWM beforehand, and I'm trying to boot into CWM to restore my backup. However whenever I tell CWM to reboot into recovery or to restore the backup, the phone reboots into the standard Samsung Andriod e3 recovery, which does not allow me to restore my backup.
How can I get CWM to boot up so I can do a restore?
http://forum.xda-developers.com/showthread.php?t=919760
I figured it out.
I'm having the same problem. How did you fix it?
I have flashed, deleted the clockwork recovery files, re-flashed, rebooted, etc, etc.
I can only get the standard blue recovery mode. I run reinstall packages and all it does is quickly shows it's attempting to install the clockwork update.zip file but just boots back into the blue standard recovery mode. Yes I have confirmed the update.zip file is there. I have removed it, reflashed, rebooted, etc. Running reinstall packages takes me into a constant loop.
This really sux.
Anyone got ideas on what my problem might be?
Thanks
Getting the same, and when I go check on my rom backups of my default OS there are no roms to be found after it says it created them successfully.
I erased any existing update.zip, then I told clockworkmod to reinstall, boot into recovery, in the blue menu I selected reinstall package, it rebooted into blue recovery again, and I selected reinstall package for the second time and then it finally rebooted into clockworkmod.
If this doesn't work you can try to follow this guide to get clockworkmod working again.
http://forum.xda-developers.com/showthread.php?t=925400
In the mist of my experimenting trying to get this to work, I did use the app Quickboot which is on the phone already to boot the phone into download mode. Then I did a hard reset (hold power button for 10 seconds), and tried the whole process I described in the previous post. I would guess this is not necessary, but it's just what I did.
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.
Before I ask, I have very limited knowledge of ADB and have been using "interface" like programs like WugFresh for all my Android root/flashing/pushing.
This is on my Nexus 6
I wanted a custom ROM. I settled on Cyanogenmod. Somewhere during the process I messed up and had to start over. I must have unchecked/checked a box I should/shouldn't have because I kept getting the E: Unable to mount Storage and cannot see my phone in Windows Explorer as an MTP device. So I did a complete factory reset, flashed the stock ROM and it seemed to resolve the error. I then flashed CM 12.1 again and started the daunting process of reconfiguring my phone. I chose not to restore my backup because I wasn't sure if the error would come back too (n00bie, I know). Then I also made the mistake of allowing the OTA CM update. Well I lost root as a result. So I attempted to root again but it got stuck at the boot logo. In a panic I booted into TWRP and dirty flashed CM 12.1 using ADB sideload. All was good, I re-rooted again successfully, but now I am getting the same E: Unable to mount Storage error again.
So I guess my question is, how do I do a backup so I do not have to reconfigure everything again and still be able to flash the stock ROM. Or do I even need to flash the stock ROM again, can I do a factory reset and flash CM 12.1 or will my error not be resolved?
Thanks in advance.
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.
hey guys just looking for some help. ive been modding and flashing phones from 2014, but its always gone really smoothly, so my diagnostic ability is lacking.
it started with flashing twrp. my bootloader is unlocked, usb debugging on, device is showing in adb and fastboot, and i can flash twrp without any issues. hoowever when i go to boot twrp, only the stock recovery boots. i tried to flash twrp using the XiaoMiTool v2, but the same thing happened. i eventually got around this by just booting twrp instead of trying to flash it. so i got in, took a full back-up and started installing a custom rom.
the first one i tried was ParanoidAndroid Quartz. i wiped cache, dalvik and storage then transferred it to my phone, tried to flash and got "zip verification failed". so i turn off zip verification and tried again. it flashed perfectly with zero errors. however, when i reboot the phone it would only boot to stock recovery and not twrp (expected) or the new rom. i tried that a few times, then tried LineageOS, and MSM Xtended 10. all of them had the same issue, the flashed without a hitch, then wouldnt boot.
i also tried flashing a new fw-vendor and it just straight up failed. Then i decided to cut my losses and restore my twrp backup, and that came back with the error, "extractTarFork() process ended with error: 255"
Software before i began these attempts was completely stock, so i dont know what is going wrong, but as of now, my phone is bricked, i cant install a new rom or restore my back-up.
any help is appreciated guys. thanks
You can figure out this problem with
1 Copy backup folder to computer
2- Format Data - Yes , Wipe Everything
3- Install ROM that you have installed before and boot
4- Go to TWRP, format data yes reboot recovery
5- Paste backup folder to internal storage and restore