I unlocked the bootloader of my moto x pure and flashed twrp on it. I also installed cyanogenmod 13 onto my phone and everything was working fine, up until I tried using the encrypt feature in the cyanogenmod settings. I started the process, but after over 36 hours of it not finishing and staying in the booting screen I realized there was a problem. I cut the failed process short and from then on my phone would only ever stay in that same screen when powered it on. I tried restoring a backup as well as reinstalling the system, but when I try restoring it says there is an
"Error opening: '/data' (I/O error)".
When I try reinstalling cyanogenmod, twrp says it is successful but it stays in a bootloop, permanently showing the picture of the cyanogenmod guy.
Thanks in advance!
Related
So I was flashing a new rom on my phone (Liquid Smooth) and did a normal clean-flash. Booted in fine, set everything up, restored apps w/ Titanium and got the phone running. Set my DPI and restarted the phone. It got stuck at the splash screen for Liquid Smooth. Restarted, same thing. Went in recovery (TWRP 2.5.x) and cleared cache/dalvik but same thing. Did a clean flash and the phone booted up again.
Weird.
This time I just restarted it after I set up the phone and it did the same thing again. Now I had no idea what was going on. So I backed up all my data, went in recovery and did a complete format. Tried flashing Liquid and Omni, but TWRP kept giving me a "can't mount /data/user". Tried to mount it manually in the recovery, and it kept saying "Can't mount /data". Now I couldn't flash anything, and my phone wouldn't boot past the S4 logo. I have the MDL odin files saved alrady, so I flashed stock ATT FW back on, rooted again using CASUAL and I'm good to go.
Flashed Liquid again, and everything seems good, I've restarted the phone a couple times and it's been okay. However: is this any indication of faulty flash memory? Or was it just some sort of partition messup which happens from time to time?
Hi again! My Nexus 10 was having problems with permissions in the DCIM folder, meaning the camera couldn't take photos or videos. I booted into recovery and deleted the folder and its contents, and then the tablet bootlooped. I booted back into TWRP and formatted system, cache, and data, and reflashed the Lollipop 5.0 rooted ROM, and it bootlooped again. I went back into recovery and formatted everything, and then flashed CM12 Nightly KANG Lollipop, and it still bootlooped. So I went into Wug's Nexus Root Toolkit, selected "soft-bricked/bootlooped" and clicked the button to return to stock. I followed the instructions, and when it got to "pushing system" it errored, saying "Data Transfer Error (Unknown Error)" then (waiting for device). It does this no matter what android version I tell the program to install when flashing to stock. On the Nexus, the "Fastboot status" says "FAILEDinvalid partition" and then it changes to and stays "DATA2817caa8". I've scoured Google for 4 hours, and have tried everything I could find. Any help is appreciated, as I got the device used off Amazon, and it doesn't have a warranty, and I can't afford a new one. Thanks!
Hello!
First of all, the diagnostic in the title was given by a guy on reddit so ignore it if you want.
My Nexus 7 started freezing and crashing a few weeks ago. Last week I decided to change the rom from a CM 11 m8 to cm 11 m12.
While writing, after sending the system.img, it stopped at writing the system. Decided to try again but first I loaded TWRP and wanted to wipe everything just to be sure.
Apparently, in the console log, there were a ton of errors "cant mount /data", "cant mount /cache".
Looked up some solutions and managed to reformat using a make_ext4fs command. The /data errors were gone but the /cache is still there.
Tried reinstalling a rom again and it still failed. Also I tried to install a rom via the adb sideload. I manged to get a CM 11 running but the freezing was still there.
Whenever I try to install a stock rom, it stops at writing system and it says FileWriteError or something like that.
The tablet has been put to sleep for a week now and today when I opened it in TWRP, the /cache error was still there.
If anyone is interested in the reason it froze, I managed to boot into safe mode and there were a lot of NPEs thrown by Keyguard Manager or similar to that.
Please help me!
I downloaded the m-kernel zip a75 (lollipop 5.1.1) and flashed it through cwm. It reported a successful flash. I rebooted and it went to the google screen, then the boot screen, and then.......... the horrid optimizing apps screen! So, I waited for the apps to be optimized, and then it reported starting apps. The window closed and I expected it to boot but up but instead met by a brief NFC thing failure message and the device went back to the bootscreen and started doing everything over and over again. Please help! I really don't want to reset my device! Why isn't it working and what should I do?
youre beat. i did the same thing. the kernel does not work with 5.1.1 so unless you TOOK A BACKUP BEFORE FLASHING there is nothing you can do but reset.
you can try reflashing the rom without wiping the data partition, or restoring only the BOOT partition from backup. it will work, thats what i did until they get the kernel situation figured out. youre not the first to encounter this.
Yesterday I wanted to update my Nexus 4 to the latest nightly cm-13.0-20160221-NIGHTLY-mako.zip using the built-in update tool. The old build was cm-13.0-20160209-NIGHTLY-mako.zip.
But after hitting reboot, the screen went off and on repeatedly (just plain black). I let it like this for the night. In the morning it was still turning the screen on and off. I was able to reboot to the bootloader. Apparently, the update deleted TWRP and installed Cyanogenmod Recovery. I re-flashed twrp.img, and now I'm stuck there: booting ALWAYS goes to TWRP (or the bootloader), I can't boot the system anymore. I tried re-flashing the old nightly, retried the new one, tried sideloading an even newer one (cm-13.0-20160222-NIGHTLY-mako.zip), wiped cache, wiped data - nothing helped.
What can I do to unbrick my phone?
Do u have a back up to your stock Rom or any other Rom aside from CM?
Flash back to stock and start over with twrp, cm, and gapps.
I just flashed back to stock, the problem persists: bootloop, the lying android with a red warning sign is showing up very briefly, then it reboots.
My first attempt to go go back to stock was manually. Now I tried again using the Nexus Root Toolkit. (Note: both time I flashed build LMY48T
After it finished flashing, the error message (lying android with red warning sign) appeared again, but this time it stayed - no bootloop anymore.
Then I rebooted into revovery mode, and there was some output:
Code:
Finding update package...
Opening update package...
E:unknown volume for path [/storage/emulated/0/cmupdater/cm-13.0-20160221-NIGHTLY-mako.zip]
E:failed to map file
Installation aborted.
OTA failed! Please power off the device to keep it in this state and file a bug report!
So, despite all flashing, apparently it is STILL looking for the - now missing - cm13 update. Where is this coming from? There must be some flag somewhere, some config file or whatever.
So, after the next reboot, the ominous boot parameters seem to be gone - I'm on a fresh 5.1.1, build LMY48T.
I'm still curious what happened here. I guess the whole flashing wasn't necessary, I just needed to get rid of the malicious boot parameter. Maybe a file or a file system was readonly?
Any idea how this happened?