Database Users

Restoring CWM backup leads to splash loop

I'm using: NexusHD2-ICS-4.0.4-CM9-HWA V2.4
Something went wrong on my phone so I decided to restore a backup. I had one from 2 weeks ago. After the restore completed, I rebooted my phone. It was stuck on the ROM splash screen and never got past that. I left it running for 20 minutes. I tried clearing /cache and dalvik-cache, with no luck. If I format /data then it works, but then of course all my data is gone.
Luckily I had a previous backup which did work.
I'm nervous about nandroid backup/restore. Can I trust it? It only happened for this particular backup, but why would it happen at all? There were no MD5 sum errors at all.
Any advice would be useful.

frostinide said:
I'm using: NexusHD2-ICS-4.0.4-CM9-HWA V2.4
Something went wrong on my phone so I decided to restore a backup. I had one from 2 weeks ago. After the restore completed, I rebooted my phone. It was stuck on the ROM splash screen and never got past that. I left it running for 20 minutes. I tried clearing /cache and dalvik-cache, with no luck. If I format /data then it works, but then of course all my data is gone.
Luckily I had a previous backup which did work.
I'm nervous about nandroid backup/restore. Can I trust it? It only happened for this particular backup, but why would it happen at all? There were no MD5 sum errors at all.
Any advice would be useful.
Click to expand...
Click to collapse
I've had an issue only once with CWM backup where my data from the ROM was lost but the ROM itself flashed fine. I suspect though that I actually had to reboot a few times more before giving up so quickly, because somehow the wallpaper was still kept and I've found on occasion that my data from a ROM restore/update slowly comes back after a few reboots. Anyway, as for your issue, did you change partition sizes between the time you made a backup and when you tried to restore it? I'm using NexusHD2 and I know that the required partition sizes have changed quite a lot between the ROMs.

Nigeldg said:
I've had an issue only once with CWM backup where my data from the ROM was lost but the ROM itself flashed fine. I suspect though that I actually had to reboot a few times more before giving up so quickly, because somehow the wallpaper was still kept and I've found on occasion that my data from a ROM restore/update slowly comes back after a few reboots. Anyway, as for your issue, did you change partition sizes between the time you made a backup and when you tried to restore it? I'm using NexusHD2 and I know that the required partition sizes have changed quite a lot between the ROMs.
Click to expand...
Click to collapse
I did not change the partition size at all. The backup before this one worked fine, so it can't be that. I also just did a new backup of today, and restored it. It worked at the first boot and didn't take extra time. I then tried restoring the broken backup again but ONLY data, and again I got a splash screen loop. I doubt multiple reboots will help, but I did try that.
I have an urge to mount the data backup and slowly take out folders until I find out the cause. If not for anything else, just out of my own curiosity.

Nigeldg said:
I've had an issue only once with CWM backup where my data from the ROM was lost but the ROM itself flashed fine. I suspect though that I actually had to reboot a few times more before giving up so quickly, because somehow the wallpaper was still kept and I've found on occasion that my data from a ROM restore/update slowly comes back after a few reboots. Anyway, as for your issue, did you change partition sizes between the time you made a backup and when you tried to restore it? I'm using NexusHD2 and I know that the required partition sizes have changed quite a lot between the ROMs.
Click to expand...
Click to collapse
I am facing exactly the same problems...
In same cases i got bootloops when restoring a Backup, in other cases i can boot after restoring but then my data is gone and i am asked to configurate my phone again with the wizard...
I never tried to boot several times if the data comes after some tries...
Btw I also didn't change the partitions...is it possible that it has something 2 do with link2sd?

In that case (@OP) I'm guessing its just a broken backup. This is why I always use Titanium as well. It takes up less space and you can restore it on almost any ROM.
Sent from my NexusHD2

Are you using an A2SD script? or do you have an ext partition?
You may have resized it, you can also try formatting it.

Nigeldg said:
I've had an issue only once with CWM backup where my data from the ROM was lost but the ROM itself flashed fine. I suspect though that I actually had to reboot a few times more before giving up so quickly, because somehow the wallpaper was still kept and I've found on occasion that my data from a ROM restore/update slowly comes back after a few reboots. Anyway, as for your issue, did you change partition sizes between the time you made a backup and when you tried to restore it? I'm using NexusHD2 and I know that the required partition sizes have changed quite a lot between the ROMs.
Click to expand...
Click to collapse
Marvlesz said:
Are you using an A2SD script? or do you have an ext partition?
You may have resized it, you can also try formatting it.
Click to expand...
Click to collapse
I use Link2SD, i have ext4....i didn't change anything in the SD Card Layout since first install of the Rom and updated several times without any problem...

what is the secret of stability

What is the secret of stability folks? i was a veteran at making mistakes when flashing roms...(i failed day 1 of owning my DSstreak5...sat seemingly dead for a week before i got things going)
Anyway my post is looking for some post detailing what works. And that means those veterans that appear to be able to go further than 48hrs without a hitch. Is it about how much gets wiped i constantly wipe dv and perform both resets. and still boot to problems.
I have mastered Baseband changes and such one of my crucial first issues (currently 366bb via dsc flashme3).
but as of late I am having problems getting reliable operation out of the box on a few roms..dsc and longhorn.
Dsc has been fairly usable...My bread and butter or must have apps are lastfm and somafm.. i must have these functional but ity appears these may be causing issues...they freeze and fc off and on.
Longhorn seems to want to throw process errors right from the start...with 2.9.1 it constantly froze at boot...(is it truely 366 compatible)
anyway thats my rant for now please post your views and tips...while i attempt to try lxdroid...wish me luck!!!
ps does loading/transferring files in ubuntu linux vs windows make any difference in the stability of files or the sd?

ellisna said:
What is the secret of stability folks? i was a veteran at making mistakes when flashing roms...(i failed day 1 of owning my DSstreak5...sat seemingly dead for a week before i got things going)
Anyway my post is looking for some post detailing what works. And that means those veterans that appear to be able to go further than 48hrs without a hitch. Is it about how much gets wiped i constantly wipe dv and perform both resets. and still boot to problems.
I have mastered Baseband changes and such one of my crucial first issues (currently 366bb via dsc flashme3).
but as of late I am having problems getting reliable operation out of the box on a few roms..dsc and longhorn.
Dsc has been fairly usable...My bread and butter or must have apps are lastfm and somafm.. i must have these functional but ity appears these may be causing issues...they freeze and fc off and on.
Longhorn seems to want to throw process errors right from the start...with 2.9.1 it constantly froze at boot...(is it truely 366 compatible)
anyway thats my rant for now please post your views and tips...while i attempt to try lxdroid...wish me luck!!!
ps does loading/transferring files in ubuntu linux vs windows make any difference in the stability of files or the sd?
Click to expand...
Click to collapse
You may wanna try an app called SD maid... it looks for unused directories and files and THOROUGHLY will clean up your system
Are you doing factory resets from both StreakMod and Dell recoveries?
When you flash ROM you should flash ROM and do a factory reset... then boot back into recovery, wipe cache and dalvik, flash ROM again, then fix permissions from recovery before booting
Also... every once in a while I like to completely wipe my SD card with diskpart using the clean all command and then let the Streak format it. Once booted and SD formatted, I mount in recovery and copy files back to the SD using the robocopy commands from Windows
I can honestly say that apart from the occasional wifi freeze or hangup I have zero problems with apps on my Streak
Mind you I don't install apps just for the sake of having it or because it was cheap on sale... I run what I need to get done what I need.... I don't use task killers but I do use Autorun Manager to prevent apps from starting and Autokiller Memory Optimizer to help out with memory
Nor do I ever have apps installed to my SD cars
Hope some of that helps
Sent from my CM9 TouchPad using TapaTalk 2

cdzo72 said:
You may wanna try an app called SD maid... it looks for unused directories and files and THOROUGHLY will clean up your system
Are you doing factory resets from both StreakMod and Dell recoveries?
When you flash ROM you should flash ROM and do a factory reset... then boot back into recovery, wipe cache and dalvik, flash ROM again, then fix permissions from recovery before booting
Also... every once in a while I like to completely wipe my SD card with diskpart using the clean all command and then let the Streak format it. Once booted and SD formatted, I mount in recovery and copy files back to the SD using the robocopy commands from Windows
I can honestly say that apart from the occasional wifi freeze or hangup I have zero problems with apps on my Streak
Mind you I don't install apps just for the sake of having it or because it was cheap on sale... I run what I need to get done what I need.... I don't use task killers but I do use Autorun Manager to prevent apps from starting and Autokiller Memory Optimizer to help out with memory
Nor do I ever have apps installed to my SD cars
Hope some of that helps
Sent from my CM9 TouchPad using TapaTalk 2
Click to expand...
Click to collapse
I am going to start easing up on the moving to sd ...things do become a little iffy when i move programs over
Wiping the sd card deserves a fresh look...I do recall once long ago wiping or swaping the sd and getting better results initially.
Maybe some mild corruption is occuring during some file transfers?
I wonder if anyone has noticed more or less issues transfering via the usp vs pulling the sd completely and using a sd adapter/slot?

cdzo72 said:
You may wanna try an app called SD maid... it looks for unused directories and files and THOROUGHLY will clean up your system
Are you doing factory resets from both StreakMod and Dell recoveries?
When you flash ROM you should flash ROM and do a factory reset... then boot back into recovery, wipe cache and dalvik, flash ROM again, then fix permissions from recovery before booting
Click to expand...
Click to collapse
The streakmod data/factory reset followed by the dell reset is a true staple in my flashing diet...
i have on occassion tried the double flash as well...but just to clarify you are recommending :
1...access Recovery .....streakmod(my recovery of habit) or clockworkmod(not sure of use on the streak5 havent used since gingerstreak)
2...flash ROM "X"
3...do a factory reset........ "dell" or "streakmod" or "both" (i have done a reboot rather than any resets between the second flash)
4...access Recovery
5...wipe cache
6...wipe dalvik cache
7...flash ROM "X" again
8...fix permissions
9...reboot
I will try to add the double flash more as a matter of design than troubleshoot option in future

[Q] CROMi 4.2.1 Install Issues

Got a question here on installing CROMi 4.2.1, love the ROM when I get it working, my problem is, whenever a new version is out and I try to install I run into all kinds of issues. I'll try to outline the exact problems I'm having here. It goes something like this, I will download new ROM, throw it onto SD card, then boot into recovery and attempt to install. Now if I try to install without clearing any caches/data etc. it will say it installs, but then it won't boot into the ROM at all, just sticks at ASUS screen. So I go through and clear everything, internal, system, dalvik cache etc. Then I try to install again, usually it will fail at least 5-6 times, sometimes it just won't do it at all, so I'll reboot, go into recovery again and try it, still no go. Then I'll use a different SD card, still won't work right, then I'll clear everything again and go for another try and after 3 or 4 or more failed times it will finally install and boot. So I'm curious if there's just something obvious and dumb that I'm missing here, or if it's just a normal issue with this and something that will always be there? It just doesn't make sense to me that it would fail so many times and just work for no apparent reason? Any pointers would be much appreciated!

I assume your using twrp 2.4.4.0-4.2 as your installing CROMi for 4.2.1 and on the 4.2.1 bootloader (10.6.1.8)?
If so not sure this is the issue but I have had & read of other's having issues with some micro sd cards using twrp 2.4.4.0-4.2
You could try in twrp doing a full wipe (cache, dalvik cache, factory reset, system, internal storage) then in twrp file manager copy the CROMi rom zip from your micro sd to your internal storage and install the rom from there and see if that works without issue.

pjc21 said:
I assume your using twrp 2.4.4.0-4.2 as your installing CROMi for 4.2.1 and on the 4.2.1 bootloader (10.6.1.8)?
If so not sure this is the issue but I have had & read of other's having issues with some micro sd cards using twrp 2.4.4.0-4.2
You could try in twrp doing a full wipe (cache, dalvik cache, factory reset, system, internal storage) then in twrp file manager copy the CROMi rom zip from your micro sd to your internal storage and install the rom from there and see if that works without issue.
Click to expand...
Click to collapse
Yep those are the versions I'm working with! Didn't realize there were sd card issues, thanks for the info. One last question, where should I copy the ROM to on the internal storage? Don't want to accidentally copy to a place that's gonna get wiped during install.

Sounds like you have something corrupted.
I'd do a full wipe of internal storage (making sure you have all your backups on external storage), flash the rom and see if that helps.
Also if your ext card is causing issues try booting without it in after the first flash.....

sbdags said:
Sounds like you have something corrupted.
I'd do a full wipe of internal storage (making sure you have all your backups on external storage), flash the rom and see if that helps.
Also if your ext card is causing issues try booting without it in after the first flash.....
Click to expand...
Click to collapse
The famous sbdags himself responds! Just wanted to take the opportunity to tell you that your ROM is incredible, puts the Transformer on par with, or better than the iPad. Installed RC2 this morning and it is running great! Thanks for all the great work. When I was having those install issues I would do a full wipe of internal, system, and all caches, but installs would still fail extremely often. The strange thing is, that after a few wipes, and numerous times trying to install, it would finally work and boot and everything would work fine. I'm thinking it has something to do with how the SD card interacts with the recovery system but maybe I don't know what I'm talking about. All that I know is that I downloaded on my tab this morning, and ran the install from the internal storage, and bam, flawless install the first time around. So I'm going to give some kudos to pjc21 because I think it was just an issue with the SD card interfacing with recovery.

asinglenoob said:
The famous sbdags himself responds! Just wanted to take the opportunity to tell you that your ROM is incredible, puts the Transformer on par with, or better than the iPad. Installed RC2 this morning and it is running great! Thanks for all the great work. When I was having those install issues I would do a full wipe of internal, system, and all caches, but installs would still fail extremely often. The strange thing is, that after a few wipes, and numerous times trying to install, it would finally work and boot and everything would work fine. I'm thinking it has something to do with how the SD card interacts with the recovery system but maybe I don't know what I'm talking about. All that I know is that I downloaded on my tab this morning, and ran the install from the internal storage, and bam, flawless install the first time around. So I'm going to give some kudos to pjc21 because I think it was just an issue with the SD card interfacing with recovery.
Click to expand...
Click to collapse
Glad to hear it worked as it should. :good::good::good:

[Help Needed] Apps won't restore or install after flashing rom [SOLVED!]

Well, my first venture into rom flashing hasn't been the most successful one as it's caused a really strange issue that a couple people on another thread have tried to help me solve, but I figure I had hijacked that thread long enough so this issue deserved it's own thread.
I rooted, unlocked bootloader, and installed TWRP v2.4.0.0 on Stock Android 4.1.1. Everything worked great. Until I flashed a rom. Now, I have been through wiping Cache, Dalvik Cache, Factory Reset, Flashing the rom (I've tried 4 with the same exact issue), flashing Gapps... All seems to go well and it says "success" when I flash, and I reboot into system. Run the setup of Google. Everything seems great and working fine. Here's where the problem is. When Google Play Store starts downloading for restore, and I'm on a solid wifi connection, nothing downloads. I have also tried stopping the downloads and installing apps individually. When I do that, I receive the same error message over and over for any app:
Unknown error code during application install: "-24"
I've rebooted, wiped cache, dalvik cache. Nothing installs. Same error. I did somehow, some way, get Titanium backup to install after numerous tries... when I try to restore any of that backup it just hangs on the first app. It does not restore anything. No batch apps. No single apps. No app data.
The odd thing is, the first time I flashed a rom, it seemed to load up fine. Stupidly, when I was running Titanium Backup for a restore I was not paying attention to what I was restoring. I was restoring all apps and app data... It caused an issue and a bunch of force closes, as you can probably imagine. So I rebooted into recovery and wiped and reinstalled rom and gapps. And virtually nothing has installed since. I have wiped and reinstalled AOKP, PACman, Carbon, and CM to no avail. Nothing seems to solve my issue. I'd love to at the very least be able to regularly install apps from the Play Store. At this point I'm not even concerned with restoring app data if that's too much to ask. I just want to be able to use my phone normally again as this is my "daily driver". If I have to go back to 4.1.1, that would be fine with me. I just want to get back to normal. And I'll do whatever it takes to get there. Any help at all would be appreciated.
Here is the original thread that some people have been giving me great advice on as to what to do, but none of it has fixed the issue yet unfortunately:
http://forum.xda-developers.com/showthread.php?t=2341470

Jersey846 said:
Well, my first venture into rom flashing hasn't been the most successful one as it's caused a really strange issue that a couple people on another thread have tried to help me solve, but I figure I had hijacked that thread long enough so this issue deserved it's own thread.
I rooted, unlocked bootloader, and installed TWRP v2.4.0.0 on Stock Android 4.1.1. Everything worked great. Until I flashed a rom. Now, I have been through wiping Cache, Dalvik Cache, Factory Reset, Flashing the rom (I've tried 4 with the same exact issue), flashing Gapps... All seems to go well and it says "success" when I flash, and I reboot into system. Run the setup of Google. Everything seems great and working fine. Here's where the problem is. When Google Play Store starts downloading for restore, and I'm on a solid wifi connection, nothing downloads. I have also tried stopping the downloads and installing apps individually. When I do that, I receive the same error message over and over for any app:
Unknown error code during application install: "-24"
I've rebooted, wiped cache, dalvik cache. Nothing installs. Same error. I did somehow, some way, get Titanium backup to install after numerous tries... when I try to restore any of that backup it just hangs on the first app. It does not restore anything. No batch apps. No single apps. No app data.
The odd thing is, the first time I flashed a rom, it seemed to load up fine. Stupidly, when I was running Titanium Backup for a restore I was not paying attention to what I was restoring. I was restoring all apps and app data... It caused an issue and a bunch of force closes, as you can probably imagine. So I rebooted into recovery and wiped and reinstalled rom and gapps. And virtually nothing has installed since. I have wiped and reinstalled AOKP, PACman, Carbon, and CM to no avail. Nothing seems to solve my issue. I'd love to at the very least be able to regularly install apps from the Play Store. At this point I'm not even concerned with restoring app data if that's too much to ask. I just want to be able to use my phone normally again as this is my "daily driver". If I have to go back to 4.1.1, that would be fine with me. I just want to get back to normal. And I'll do whatever it takes to get there. Any help at all would be appreciated.
Here is the original thread that some people have been giving me great advice on as to what to do, but none of it has fixed the issue yet unfortunately:
http://forum.xda-developers.com/showthread.php?t=2341470
Click to expand...
Click to collapse
2 suggestions:
1) i think others have reported having issues with TWRP 2.4, so try 2.5 or 2.3.2.3
2) I think the error could be a lack of internal storage, so certainly try the "wipe internal storage" in TWRP (after making sure that your ROM/GApp files, backups (including Tibu) are saved to your external folder

jco23 said:
2 suggestions:
1) i think others have reported having issues with TWRP 2.4, so try 2.5 or 2.3.2.3
2) I think the error could be a lack of internal storage, so certainly try the "wipe internal storage" in TWRP (after making sure that your ROM/GApp files, backups (including Tibu) are saved to your external folder
Click to expand...
Click to collapse
Ok giving this a shot. I did notice that you had mentioned a different version of TWRP than I had. I will try the wiping internal storage before I install a different TWRP then if that doesn't work, TWRP. Gotta find the external folder. Unless you just mean anything that is on the actual SD card.

Jersey846 said:
Ok giving this a shot. I did notice that you had mentioned a different version of TWRP than I had. I will try the wiping internal storage before I install a different TWRP then if that doesn't work, TWRP. Gotta find the external folder. Unless you just mean anything that is on the actual SD card.
Click to expand...
Click to collapse
i would actually recommend installing TWRP 2.5 first.
never wipe external SD card.
if you have an app called Root Explorer, that works best.

jco23 said:
i would actually recommend installing TWRP 2.5 first.
never wipe external SD card.
if you have an app called Root Explorer, that works best.
Click to expand...
Click to collapse
Ok I'll try 2.5 then. And I wasn't gonna wipe the card, just was wondering if when you said external folder you were talking about the SD card. Root explorer works great.. if i could install it.
EDIT: Since I am away from my computer, I tried the multiple wipe method. Didn't change anything. So I will be changing TWRP versions later and will post an update.

Jersey846 said:
Ok I'll try 2.5 then. And I wasn't gonna wipe the card, just was wondering if when you said external folder you were talking about the SD card. Root explorer works great.. if i could install it.
EDIT: Since I am away from my computer, I tried the multiple wipe method. Didn't change anything. So I will be changing TWRP versions later and will post an update.
Click to expand...
Click to collapse
You never mentioned using TWRP 2.4. DEFINITELY replace that. Also, just a thought. If you haven't already done so, try using the option to fix permissions. I'm fairly sure its an option in TWRP.
Sent from my XT907 using xda premium

Back in business! Wow thank you all so much! What a pain it's been but without the help I'd have never guessed how to get this running as perfectly as it is now. Here's what worked for me:
Installed TWRP 2.5 (Instead of what I had, 2.4)
Then followed jco23's precise directions:
jco23 said:
- I use TWRP 2.3.2.3 (SS has been uninstalled via it's own app, not Tibu or the system awhile ago) - but TWRP 2.5 works just fine for others
- after downloading the ROM and GApps (or any file that I intended to flash for that matter), I always place the file on the mnt/external1 directory. I
m not sure if this will make a difference, but I recall it being an issue back on my Droid Charge days
- after flashing the files, does TWRP say successful?
- perhaps you do need to a double wipe of everything prior to flashing:
1) mount everything
2) wipe cache
3) wipe dalvik cache
4) wipe system
5) factory reset/wipe data
6) wipe internal storage (if you do this, make sure to change your TiBu backup folder to your external1 directory, or this will be gone too!!!!! also make sure that the system backup you made is on the external1 directory as well
7) reboot recovery
8) install ROM
9) install GApps
Click to expand...
Click to collapse
And it's working flawlessly. Able to download or restore anything from Gapps. Was able to restore some specific app data from Titanium Backup (did not want to ruin the phone again and do that full restore so I selected specific apps that I really wanted the data on).
Thanks to everyone who took the time to assist me and a special thanks to jco23 and netizenmt who were with me through this whole debacle, leading me through every possible fix they could think of. As for those of you that may be wondering which ROM I settled on... AOKP.

Good for you bro! That stinking TWRP 2.4.0 is such a menace! Wish there was a way to have it yanked from circulation. Glad you're up and running!
Sent from my Droid Razr M using xda premium

Jersey846 said:
Back in business! Wow thank you all so much! What a pain it's been but without the help I'd have never guessed how to get this running as perfectly as it is now. Here's what worked for me:
Installed TWRP 2.5 (Instead of what I had, 2.4)
Then followed jco23's precise directions:
And it's working flawlessly. Able to download or restore anything from Gapps. Was able to restore some specific app data from Titanium Backup (did not want to ruin the phone again and do that full restore so I selected specific apps that I really wanted the data on).
Thanks to everyone who took the time to assist me and a special thanks to jco23 and netizenmt who were with me through this whole debacle, leading me through every possible fix they could think of. As for those of you that may be wondering which ROM I settled on... AOKP.
Click to expand...
Click to collapse
glad you finally got it working - this is just the first step in becoming a crack-flasher....

jco23 said:
glad you finally got it working - this is just the first step in becoming a crack-flasher....
Click to expand...
Click to collapse
Yeah, I've got it bad. I have had CM 10.1, Slimbean, Carbon AND AOKP on my phone all in the last 2 days. Carbon is on it right now. No telling what will be on it by tonight.
Sent from my XT907 using xda premium

netizenmt said:
Yeah, I've got it bad. I have had CM 10.1, Slimbean, Carbon AND AOKP on my phone all in the last 2 days. Carbon is on it right now. No telling what will be on it by tonight.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
funny, and the goal is to find a ROM that you're happy with and don't need to flash.
but I've been on Carbon since 7/5, and very happy.

[Q] Freezing, rebooting, and can't flash stock rom (reverts to previous state)

Okay, so I feel like I've looked everywhere and tried everything for this problem with my Nexus 7. The closest thing I found was this:
(Google: Nexus 7 2012 rebooting reverts back to previous state)(I can't post outside links as I am a new member)
and there was no followup reply, and the thread was closed.
Here's my problem (I want to be very detailed in case I missed something):
I've had Cyanogenmod 11 on my Nexus 7 for a long time (I think I started with M1 release). I recently installed the M7 release after previous nightly and it was working so smooth that I had finally decided there was no need to install nighties anymore. Everything was going fine until the night after when I noticed it kept rebooting, so I reverted it back to the nightly I had before (June 11th?) because I assumed it was probably something bad with the update. Except it did the same thing, rebooting after a couple minutes, which is weird because it never did that with this nightly. There was never enough time to download the nightlies before it reboots so I tried downloading them on my laptop and then just transferring them to my nexus via usb. I put it in the cmupdate folder so that I could quickly go to settings and press install (as it can see the update from there). It rebooted to install, but it went into cwm with what appears that nothing happened, and I usually never see cwm when updating this way. So I figured, while I'm here, I could just "install zip" and find that zip I just transferred and install, right? Nope. The zip mysteriously vanished, yet the other two updates were still there (M7 and the previous nightly). So I just rebooted just to try the process again, maybe the file transfer didn't work. Same thing happened. So I went to cwm and tried wiping cache, nothing. Wiped dalvik cache, nothing. So I went and did it, wiped data/factory reset, that did NOTHING, as in I rebooted and everything was still there.
So I got to the point where I just wanted to see if I could just revert back to stock so I have a place to start from, maybe contemplate on just staying there for a while where there shouldn't be problems. So I got that all set up with fastboot, got the latest 4.4.3 image, unarchived until I could get to the flashall.bat I ran that and it was successful. Okay now I can just boot into that, right? Suddenly I see the cyanogenmod boot graphic. What happened? Even all of my apps are still there. Still freezing and rebooting.
I tried reverting to stock manually by erasing then formating everything that I can, flashed bootloader (grouper 4.23), flashed zip, locked bootloader, unlocked bootloader (trying to erase as much as I can). This did nothing, still cyanogenmod. I tried a third time while rebooting to bootloader with each step. Nothing. I tried doing a factory reset within cyanogenmod, but when I press the "erase everything" button it doesn't lead anywhere, so I could never get that to start the process. I also tried doing the erasing and formatting from cwm (which isn't being overwritten, as it seems, by all the attempts at flashing stock?), nothing.
I was curious. I uninstalled Netflix because it was right there in my dock. Then I rebooted myself. When it came back up, Netflix was still there. I tried various things, also going back to locking the bootloader and rebooting the bootloader, it still said it was unlocked. So I came to the conclusion that literally nothing was being written or committed to the sdcard no matter what I do.
I did some more research and found that article up top. So I tried uninstalling some apps because it said it may have something to do with a third-party app misbehaving (seems a bit extreme, I'll do it anyways), but there's never enough time to erase everything before it reboots. It also said to try to get it into safemode. I think I might have gotten there once but it still rebooted (which makes me think that it didn't get to safemode), the rest of the times it wouldn't even get to the lockscreen.
What I'm currently attempting is to see if I can get it into safemode, or I'm trying to uninstall or stop/clear data for every single app with an intentional reboot each time.
Anyone got any idea what's going on? Is it maybe a bad sector, or worse, bad sdcard?

Gonna bump this. Still no luck on my part.
Anyone have any idea?
Perhaps somehow something got triggered to prevent anything being written to the sdcard? (Kinda like the lock switch on actual sdcards?) Is everything I've been doing going straight to memory since everything reverts back after a reboot? That's the only explanation I can think of.
Perhaps there's more I could try. I'm only moderately knowledgeable with things like fastboot and roms, so maybe someone with more experience might have more insight. Please, chime in.
Thanks in advance,
JM

Same problem here....

Flash factory image

USBhost said:
Flash factory image
Click to expand...
Click to collapse
Although you flash the factory image, the previously ROM boots again, that is precisely the problem.

Amd64bits said:
Although you flash the factory image, the previously ROM boots again, that is precisely the problem.
Click to expand...
Click to collapse
O ok

Amd64bits said:
Same problem here....
Click to expand...
Click to collapse
Curious, how did you get to the point where it boots the previous rom? Same as me or something else? Are you using cyanogenmod? I want to try and rule out some possibilities.
I'm at the same point since last time. Trying to nuke the hell out of cyanogenmod but it won't go away!
This just outright baffles me!

Try this out format /system /cache /data with twrp to f2fs
If it doesn't boot then cheers you got out if the loop
Then adb sideload an f2fs ROM and kernel them flash

USBhost said:
Try this out format /system /cache /data with twrp to f2fs
If it doesn't boot then cheers you got out if the loop
Then adb sideload an f2fs ROM and kernel them flash
Click to expand...
Click to collapse
I have clockworkmod recovery v6.0.4.3 probably from installing cyanogenmod, however formating any of those partitions does literally nothing. I'm not sure what file system it formats it to, but the process seemed too quick for a full format.
I cannot flash a different recovery because... well... it doesn't remember me flashing a recovery (even when nothing "fails" when flashing). So I'm stuck with whatever is already on my internal storage. Nothing is writing to the sdcard, and nothing is being deleted.

violoncellemuse said:
I have clockworkmod recovery v6.0.4.3 probably from installing cyanogenmod, however formating any of those partitions does literally nothing. I'm not sure what file system it formats it to, but the process seemed too quick for a full format.
I cannot flash a different recovery because... well... it doesn't remember me flashing a recovery (even when nothing "fails" when flashing). So I'm stuck with whatever is already on my internal storage. Nothing is writing to the sdcard, and nothing is being deleted.
Click to expand...
Click to collapse
Boot twrp temporary from the bootloader

USBhost said:
Boot twrp temporary from the bootloader
Click to expand...
Click to collapse
I'm unfamiliar with this, how do I boot temporarily?

violoncellemuse said:
I'm unfamiliar with this, how do I boot temporarily?
Click to expand...
Click to collapse
1 set getting on computer

Okay, so I was able to boot twrp and change the partitions to f2fs. No dice. Still cyanogenmod.

violoncellemuse said:
Okay, so I was able to boot twrp and change the partitions to f2fs. No dice. Still cyanogenmod.
Click to expand...
Click to collapse
then you did boot twrp temporary

USBhost said:
then you did boot twrp temporary
Click to expand...
Click to collapse
I did. I didn't know that was possible until now.
But still, changing the file system or formating anything doesn't do anything after I reboot. I even checked after I changed the file system to f2fs in twrp to see the "current file system" when changing the partitions again, but it says it's ext4 still.
I tried repairing system, which processed quickly. However, trying to repair cache and data led to an error. Perhaps this might mean something? or is this normal?

violoncellemuse said:
I did. I didn't know that was possible until now.
But still, changing the file system or formating anything doesn't do anything after I reboot. I even checked after I changed the file system to f2fs in twrp to see the "current file system" when changing the partitions again, but it says it's ext4 still.
I tried repairing system, which processed quickly. However, trying to repair cache and data led to an error. Perhaps this might mean something? or is this normal?
Click to expand...
Click to collapse
thats not normal
ok i know why its a new cyanogenmod feature
no matter what you do cyanogenmod is now unkillable lol
this is such a strage problem

USBhost said:
thats not normal
ok i know why its a new cyanogenmod feature
no matter what you do cyanogenmod is now unkillable lol
this is such a strage problem
Click to expand...
Click to collapse
Do you have any more info? Perhaps my sdcard is "softlocked" or something.

violoncellemuse said:
Do you have any more info? Perhaps my sdcard is "softlocked" or something.
Click to expand...
Click to collapse
i have been noticing CWMR is the root of all the problems
i dont sorry but your not the only one i think there are 3+ people that have this same problem
formating should have fixed it

USBhost said:
i have been noticing CWMR is the root of all the problems
i dont sorry but your not the only one i think there are 3+ people that have this same problem
formating should have fixed it
Click to expand...
Click to collapse
I do thank you for trying to help me out.
I found a thread with someone with the same problem I'd like to direct people towards: http://forum.xda-developers.com/showthread.php?t=2800064

violoncellemuse said:
Curious, how did you get to the point where it boots the previous rom? Same as me or something else? Are you using cyanogenmod? I want to try and rule out some possibilities.
I'm at the same point since last time. Trying to nuke the hell out of cyanogenmod but it won't go away!
This just outright baffles me!
Click to expand...
Click to collapse
Well, I have Paranaoid Android 4.4.4, not Cyanogen, and everything seemed ok until I installed Cloudmagic (and maybe Busybox?) that poped up a Play Store error (I don't remember which one), and suddenly all the problems began. It started to reboots, rebooted so many times that I decided to flash another ROM... but this wasn't possible.
My recovery is TWRP, so we can discard Cyanogen, ParanoidAndroid, CMW and TWRP as guilty, I think.
USBhost said:
Try this out format /system /cache /data with twrp to f2fs
If it doesn't boot then cheers you got out if the loop
Then adb sideload an f2fs ROM and kernel them flash
Click to expand...
Click to collapse
Tried that, nothing happened, still with Paranoid Android.
violoncellemuse said:
I did. I didn't know that was possible until now.
But still, changing the file system or formating anything doesn't do anything after I reboot. I even checked after I changed the file system to f2fs in twrp to see the "current file system" when changing the partitions again, but it says it's ext4 still.
I tried repairing system, which processed quickly. However, trying to repair cache and data led to an error. Perhaps this might mean something? or is this normal?
Click to expand...
Click to collapse
Same here.