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.
Related
I'm running TWRP v2.3.0.1 and I've been having a lot of trouble the past few days trying to flash roms. I was on a stock rooted evo lte with s-on two days ago.
I decided to try out the cm 10 and used flash image gui to flash the boot and then was on cm 10. Decided that I wanted a more stable rom (gps wasn't working) So i went back and restored my original backup of my stock rooted evo. However, the wifi is not working (all it says is wifi - error, won't turn on). So i did a little research and thought maybe something with switching back and forth between kernels went wrong. I'll try to flash a sense based rom the same way i did cm 10. At this point i try to make another backup just incase and its going through everything in twrp and in the end it says backup failed. So i figure well the orignal backup I have is fine and continue
So i open meanrom up in flash image gui it does its thing (clear dalvik, cache). Reboot into recovery go to install meanrom and get the following:
"-mean rom logo-
Formatting and mounting partition...
e:error in /sdcard/meanrom-ics-v48-jewel-ltevo.zip
(status 1)
error flashing zip '/sdcard/meanrom-ics-v48-jewel-ltevo.zip'
updating partition details"
and twrp says FAILED, at this point i'm thinking maybe a bad download i'll try another rom/download
So at this point i restore my system and once again wifi is not working and try the same using freshrom. flash image gui, clear cache, etc. Reboot into recovery and gives me the same error and says failed.
So now i'm stuck on a stock rom backup that worked fine when i orginally backed it up but now wifi has an error? doesn't make any sense to me and i'm not sure why i'm unable to flash and roms or create new backups
Try flashing TWRP 2.2.2.0 in fastboot
i was able to fix wifi using vel7wil advice in this thread http://forum.xda-developers.com/showthread.php?t=1900759&highlight=wifi+error so for now everything is working on my backup. I'll see if i'm still having issues flashing roms now.
Hello Everyone,
I have a Transformer Prime (TF201) and recently decided it was time to update from the stock rooted ROM. I have TWRP so I downloaded the latest Cyanogen Mod for Transformer Prime (nightly build 10.1), made a full backup, cleared my caches, and tried to install the rom. Unfortunately what I wound up with was the startup animation for Cyanogen Mod and nothing more. And when I went back to restore my previous version, my tablet wasn't able to find it.
Since then I've done a number of different things in an attempt to restore it, mainly clearing caches, formatting data, and trying to flash either the 9.1 Stable Cyanogen Mod ROM, the 10.1 nightly build I originally tried, or the stock, rooted, deodexed ROM available here: http://forum.xda-developers.com/showthread.php?t=1911024. When I try to install either of the CM ROMs it goes through what appears to be an install process and I see the error "Unable to mount /staging." Once I see that error once, it continues to appear when I try to wipe cache/dalvik or do anything else from recovery. Despite receiving this error it says the install was successful but upon rebooting, it never is. When I try to install the stock, rooted ROM, it fails outright.
After poking around some I found the Prime Full Wipe here: http://forum.xda-developers.com/showthread.php?t=1670824. I gave this a shot thinking maybe if I get a fresh start I'll have more success but I'm afraid I'm still having no luck. After a full wipe and reboot I'm still receiving the same "unable to mount /staging" error with CM and the same failures with the stock ROM.
I don't know if this matters or not but I have been flashing all of these files from an external SD card. I tried to setup ADB or ASUS sync but I'd done it after I had already hosed the OS so I couldn't get my computer to recognize the tablet.
If you guys have any suggestions or clarifying questions, I'd love to hear them. Thank you!
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
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