Would there be a reason I can't restore CM12.1 - d2vzw? I can restore my previous non-CM roms. I'm using CWM 6.0.4.5 and I've tried wiping data, cache and dalvik, then restoring my backup. I tried to restore the 1st nightly, but it rebooted into recovery.I reinstalled the zip from scratch and have updated till today.Today I booted up into official nightly from May 17th, 1st install went fine like before but when I tried to check if I could restore with the new nightly. Still no go. The Samsung logo comes on, stays on 30 sec. then reboots into CWM Recovery again. I can restore back to a former rom of a different maker. Any suggestions?
Thanks, Tom
tshuford said:
Would there be a reason I can't restore CM12.1 - d2vzw? I can restore my previous non-CM roms. I'm using CWM 6.0.4.5 and I've tried wiping data, cache and dalvik, then restoring my backup. I tried to restore the 1st nightly, but it rebooted into recovery.I reinstalled the zip from scratch and have updated till today.Today I booted up into official nightly from May 17th, 1st install went fine like before but when I tried to check if I could restore with the new nightly. Still no go. The Samsung logo comes on, stays on 30 sec. then reboots into CWM Recovery again. I can restore back to a former rom of a different maker. Any suggestions?
Thanks, Tom
Click to expand...
Click to collapse
I've had some issues before regarding actions within the CWM on my d2vzw. I got rid of CWM and installed TWRP 3.0.2-0. I was then able to do much more.
I had also read somewhere that CWM is an abandoned project and TWRP is kept current and is also recommended by Cyanogenmod for all their ROM's and other flashable files.
The link for the d2vzw TWRP is https://dl.twrp.me/d2vzw/
Good luck!
Related
Hi,
I've been using cyanogen mod 9 without any issues. recently i upgraded to cyanogen mod 9.1 and have been noticing minor glitches. nothing to be worried about. Recently i used Bluetooth to share files ( have used it before). when i powered off the Bluetooth it rebooted and is now stuck at boot animation. Also cannot connect to my PC. any suggestions or workaround to the problem? would be appreciated.
Restore backup, reflash kernel and/or rom (boot into recovery, or factory reset (in that order). Or if none of those things are a goer, back to stock via Odin try those steps (try to restore backup first if you have one, if not reflash CM & if you get bootloop or whatever after a clean install of CM, factory reset).
MistahBungle said:
Restore backup, reflash kernel and/or rom (boot into recovery, or factory reset (in that order). Or if none of those things are a goer, back to stock via Odin try those steps (try to restore backup first if you have one, if not reflash CM & if you get bootloop or whatever after a clean install of CM, factory reset).
Click to expand...
Click to collapse
I'm sure there is a bug in Bluetooth implementation in mod 9.1. I did a cache wipe, after that it was stuck in another kind of loop. rebooted normally, immediately Bluetooth turns on and it reboots again.
how do i reboot into recovery? previously i was using adb for that. i restored backup ( it was of mod 9) now it wont even boot.
ok. so i finally managed to get it working. i had accidentally restored mod 9 backup onto mod 9.1 so i used odin to flash ClockworkMod-Recovery_5.5.0.4 booted and now i'm back to a month older backup. Oh well since i have to restore my settings anyway why not try mod 10.1?
Installed latest CM10 nightly. Now just sits at boot animation. Attempted to restore. Backups gone. All other ROMS gone for SD card. Can get into recovery, but am lost at that point. Tried clearing cache several times through fastboot. Have no clue how to use adb to sideload. Rate myself as an almost noob. Any help appreciated.
johnpius said:
Installed latest CM10 nightly. Now just sits at boot animation. Attempted to restore. Backups gone. All other ROMS gone for SD card. Can get into recovery, but am lost at that point. Tried clearing cache several times through fastboot. Have no clue how to use adb to sideload. Rate myself as an almost noob. Any help appreciated.
Click to expand...
Click to collapse
I'm in the same boat, stuck at the CM boot animation. How did you get back to recovery? I hold the power button and the home and back buttons flash and that's it.
Edit: The whole "hold the phone up to a bright light while holding the power button" trick did the job. I was flashing from Android Revolution to CM10.1 and I did perform a factory reset and sideloaded CM through CWM. After another wipe everything worked out fine.
Are you coming from another rom? If so, did you factory reset after flashing ?
cschmitt said:
Are you coming from another rom? If so, did you factory reset after flashing ?
Click to expand...
Click to collapse
Im assuming based on his post he is not coming from another rom and has been flashing CM nightlies regularly and this latest flash was done per routine but is not working for some reason.
I updated the latest 6-23 nightly and its working fine so far, sorry to hear about your issues.
Sent from my Nexus 7 using Tapatalk 2
I dirty flashed the latest nightly as well, no issues.
So I'm tying to help my best friend flash CM11 on his e970, it's rooted and had TWRP 2.7.0.1 installed. I did a full backup and attempted to wipe data, system, cache, and dalvik. It would start then flash off and then back to TWRP again. Doing this one at a time showed that the error happened when attempting to wipe data. I tried the latest Phil's CWM and backed up wiped fine but when I attempted to install CM11 either M6 or the 052114 Nightly it gives a status 7 error. So I tried it with the latest CWM touch recovery and the same thing. Backups restore each time. I then attempted to flash Mokee thinking it must be an.issue with the downloads, and still status 7. Any ideas? Thanks, every time I google the error I read it's a recovery issue, now I'm not too sure it is in this case. 3 different recoveries and 3 different ROMs. I did keep the phone on ice to keep it cool when it was getting hit to be safe.
Thanks
I downloaded the 3/29/15 nightly build, copied it to my SD card and booted into recovery. Flashed, wiped data/factory reset and then boot to all sorts of errors from the Google apps. I can't use the tablet at all.
I've tried reflashing and wiping to no avail. I'm flashing in CWM 6.0.2.8 and there's no build newer than 3/29.
Should I just go back to 10.1.3?
For the record, I didn't think gapps was included with the ROM, but apparently it was.
General_Mayhem said:
I downloaded the 3/29/15 nightly build, copied it to my SD card and booted into recovery. Flashed, wiped data/factory reset and then boot to all sorts of errors from the Google apps. I can't use the tablet at all.
I've tried reflashing and wiping to no avail. I'm flashing in CWM 6.0.2.8 and there's no build newer than 3/29.
Should I just go back to 10.1.3?
For the record, I didn't think gapps was included with the ROM, but apparently it was.
Click to expand...
Click to collapse
I fixed it.
I reflashed CM10.1.3, downloaded CWM 6.0.4.6, upgraded CWM using Rashr, and reflashed CM12.
I seem to have shot myself in the foot recently. I've been on CM 13 for nearly a year now and I wanted to try out LineageOS for the hell of it since I am planning to get a new phone and I wanted to put LineageOS on that as well. So I downloaded an unofficial build of LineageOS for the G850W and followed some basic instructions: backup with TWRP, wipe with TWRP, and flash both the ROM and OpenGApps with TWRP. All three of these went well and I was able to install LineageOS. Now the problem: I tried restoring my backup (a CM 13 based backup) thinking I could restore some things from that backup and when I went to restart the CM boot screen popped up and I immediately knew I must have messed up. Checking my backup it contained boot, cache, system, EFS, modem, and a couple other folders/partitions that I can't remember off the top of my head. I then simply tried to redo everything again: backup, wipe, flash. While I am able to backup, wipe, and flash, and I am able to proceed past my device's boot screen, the Lineage OS boot screen seems to either be stuck or it is taking a long time. I've waited for 30 minutes with no change and I am sure that shouldn't be the case at all. Stock ROM was the same way, sitting on the Samsung logo with the sparkles forever. I managed to reinstall CM 13 but it's a very buggy install as sometimes it restarts randomly and goes through the "preparing applications" thing upon restart. Furthermore data doesn't seem to work and IMEI info is not found and sometimes in the stock recovery mode it shows that the EFS partition could not be found. Same thing happens when I poke around in ADB, I do not see any EFS partition when I type in the mount command. Clearly I've really messed things up. So would there be some way to fix things considering I do have a backup of things before I messed things up? How would I use my backup to fix everything? Would there be other tools I should be trying? Any help would be appreciated.
Flash original firmware
echo124 said:
Flash original firmware
Click to expand...
Click to collapse
I did: "Stock ROM was the same way, sitting on the Samsung logo with the sparkles forever".
Erase everything on your phone (aftet backup) and flash stock again.
echo124 said:
Erase everything on your phone (aftet backup) and flash stock again.
Click to expand...
Click to collapse
I've done that as well already, still the same issue.
:fingers-crossed:Flash stock, flash same version twrp used to backup, flash same version of cm 13 used on backup, try restore.