My screen broke tonight enough to make it unusable, and I was offered in store exchange when I called B&N support. I am running CM7, and would like to know if it is possible to either restore to stock or wipe the hard drive to remove evidence of rooting before I send it back.
I managed to get into adb and read in another thread to try rm -r *, which is supposed to wipe everything, but I got a bunch of read only errors. It appears that the nook will now not boot into CM7 (which is good), but I fear that I haven't wiped it far enough to be safe from a chargeback. Any ADB wizards out there with some advice?
I think I have done it. I opened up a shell in adb, mounted /system as r/w, then did rm -r *. after a reboot it won't even boot into adb anymore. it comes on for about 4 seconds then shuts off immediately. I can't tell what is happening on the screen because of the damage, but i'm hoping it is enough that the folks who check returns at BN can't prove it was rooted.
What are you wanting it to boot into if you just deleted everything in the system partition?
Sent from my HERO200 using XDA App
I think he wanted it to not boot at all in preference to booting into CM7.
I'm pretty sure that if they looked beyond the broken screen they'd be able to determine that you've rooted it: Having no files but still a filesystem on /system is kinda suspicious, and I imagine that having CWM instead of the stock recovery would be something of a giveaway as well.
Sorry if I should post this in the Dev thread. I've been through the forums, I've googled around, and none of the guides have helped solve this. I'll succinctly describe what I did and where I'm at.
I had CM9 (oat's LnT ROM) and WebOS dual booting just fine. Since LnT was discontinued, I decided I'd see if maybe another ROM would work better since I was having issues. I put AOKP on via CWM. Now, however, both Cyanogen and AOKP showed up in my boot menu with Cyanogen as the default. One time I forgot to change what the boot was, and it tried (and failed) booting cyanogen.
Since then, I can't boot anything. CWM can't mount anything, so I can't get to my nandroid backup, webOS won't boot. I'd honestly be happy with a pure factory reset and starting from scratch, but I can't get anywhere with webos doctor either. It fails at 8%:
Oct 11, 2012 12:20:23 PM com.palm.nova.installer.recoverytool.CardController runnerFinished
WARNING: flashing failed, move to failed card
A found a guide at wwwDOTsouldevteamDOTnet/blog/2012/07/24/fix-bricked-hp-touchpad-recovering-software-bricked-touchpad/ that looked promising, but I can't find any volumes:
[email protected]:/# lvm.static vgscan --ignorelockingfailure
Reading all physical volumes. This may take a while...
[email protected]:/#
Any advice or help would be most welcome.
stace said:
Sorry if I should post this in the Dev thread. I've been through the forums, I've googled around, and none of the guides have helped solve this. I'll succinctly describe what I did and where I'm at.
I had CM9 (oat's LnT ROM) and WebOS dual booting just fine. Since LnT was discontinued, I decided I'd see if maybe another ROM would work better since I was having issues. I put AOKP on via CWM. Now, however, both Cyanogen and AOKP showed up in my boot menu with Cyanogen as the default. One time I forgot to change what the boot was, and it tried (and failed) booting cyanogen.
Since then, I can't boot anything. CWM can't mount anything, so I can't get to my nandroid backup, webOS won't boot. I'd honestly be happy with a pure factory reset and starting from scratch, but I can't get anywhere with webos doctor either. It fails at 8%:
Oct 11, 2012 12:20:23 PM com.palm.nova.installer.recoverytool.CardController runnerFinished
WARNING: flashing failed, move to failed card
A found a guide at wwwDOTsouldevteamDOTnet/blog/2012/07/24/fix-bricked-hp-touchpad-recovering-software-bricked-touchpad/ that looked promising, but I can't find any volumes:
[email protected]:/# lvm.static vgscan --ignorelockingfailure
Reading all physical volumes. This may take a while...
[email protected]:/#
Any advice or help would be most welcome.
Click to expand...
Click to collapse
This could be of help, though it's not complete, it's a start in the right direction.
http://forum.xda-developers.com/showthread.php?t=1729179
Good luck.
Edit : Here's another link that could help : http://forum.xda-developers.com/showthread.php?t=1426244
chicle_11 said:
This could be of help, though it's not complete, it's a start in the right direction.
http://forum.xda-developers.com/showthread.php?t=1729179
Good luck.
Edit : Here's another link that could help : http://forum.xda-developers.com/showthread.php?t=1426244
Click to expand...
Click to collapse
Thanks for those links. Alas, the process in the second link presumes that the first command "vgscan" will find and identify a "store" volume. But mine doesn't find any volumes. I'll see if that author has any helpful advice on how I can create the volume group.
this should be a real simple fix. obviously you still have moboot working correct? and you are still able to boot into clockworkmodrecovery CWM correct?
now im guessing by the "failed at 8% issue that youre likely on windows 7 64bit orr maybe even vista 64bit correct?
do you have the android-sdk installed on your computer and are you familiar with how to enable ./adb connections?
if yes then this should only take a few minutes to fix.
I have moboot, and can boot into CWM, but CWM complains about not being able to mount any dirs.
I get the 8% issue whether I use Windows 7 64 bit or Mac OS 10.7.
I'm sure I can muddle through adb connections. Do you have any tips for me to try? I can't successfully get the tablet to boot anything -- the closest is CWM which, as I say, can't mount anything.
Hey Guys
So I thought I found a great deal on craigs list... touch pad for a good price... but it turns out I bought more then I barganed for. To cut to the chase the old owner seems to have a semi installed CM9 installed, but the something messed up and now im the new owner... :crying:
I tried to delete this guys photos in WebOS but he keeps coming back to huant me! IT seems that all the files are locked in read only mode and factory restores wont work
I tried this post
[Guide] Factory condition restoration / Downgrade to webOS 3.0.0
http://forum.xda-developers.com/showthread.php?t=1426244
and
[HOWTO][CM7 ALPHA2.1] FIX - sdcard storage mounts as readonly
http://forum.xda-developers.com/showthread.php?t=1322127
so far with no luck..
When i Tried Doctor os it fails at %12
Any suggestions guys?
PLEASE HELP
I once royally screwed mine by using windows to format it. You could try that...
WebOS doctor and the novaterm will get it going after that...
Just an idea...
Sent from my SAMSUNG-SGH-T989 using xda premium
I tried both WebOS = Failed at 12%
Novaterm =factory reseting and some other stuff
Please help :crying:
-SGA- said:
I once royally screwed mine by using windows to format it. You could try that...
WebOS doctor and the novaterm will get it going after that...
Just an idea...
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Did you try mounting the SD in windows through webos and then right clicking on the drive and click format?
Sent from my aokp_tenderloin using xda premium
I'm able to mount and format but when I reboot that guys photo is back Along with the system files and folders
QUOTE=-SGA-;33722106]Did you try mounting the SD in windows through webos and then right clicking on the drive and click format?
Sent from my aokp_tenderloin using xda premium[/QUOTE]
Update
So I was able to boot into clock work with this thread :
http://forum.xda-developers.com/showthread.php?t=1302433
Comman used : novacom boot mem:// < uImage.ClockworkMod
Once in there I tried all the various options
format sd card / fix permissions / wipe X options
I also tried : CM7: Fixes for SDCARD issues
from : http://rootzwiki.com/topic/13277-cm7-fixes-for-sdcard-issues/page__st__90
but when i load files into the sdcard via mounting through clockwork Im unable to install from zip from SD card... due to the read only nature of this current drive...
My new Lead on this problem is from this thread : http://newbrightidea.com/2011/08/26/hacking-the-touchpad-part-1/
what caught my eye was his statement about mounted read only by default... (see below)
in theory if i follow his steps i may be able to unlock this read only bug and fully install CM9... Stay tuned.
STARTING OPENSSH SERVER
Harder than it sounds! The root filesystem is mounted read-only by default, but you can hack your way around that with:
mount -w -o remount /
Then, add the sshd user and group to /etc/passwd and /etc/group
Setup an ssh key using ssh-keygen and set the “HostKey” property in sshd_config to point to the private key.
If you didn’t remount the root FS as read-write, you need to set UsePrivilegeSeparation to true.
Start sshd like so:
krunktor said:
I'm able to mount and format but when I reboot that guys photo is back Along with the system files and folders
QUOTE=-SGA-;33722106]Did you try mounting the SD in windows through webos and then right clicking on the drive and click format?
Sent from my aokp_tenderloin using xda premium
Click to expand...
Click to collapse
[/QUOTE]
Removed.
emuX said:
Removed.
Click to expand...
Click to collapse
EmuX
are you refering to this post:
http://forum.xda-developers.com/showpost.php?p=24047078&postcount=3
Yes, I was. That's why I removed the post since you'd already found it. Although I didn't do all the steps suggested - just the first few and then ran webos doctor with it all uninitialised.
I just did:
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
mkdosfs -f 1 -s 64 /dev/store/media
Click to expand...
Click to collapse
(Oh, and I've got a 32gb device in case that makes any difference.)
Also, how long did you wait for webos doctor to complete? After using that approach I left mine running for a long time at 8% or 12% (I forget which) and it eventually carried on.
Recently my phone had a low battery status. It booted up but apparently lost power somewhere when restoring the Apex Launcher screens.
Since then it just shows the Samsung logo and gets rather hot. I left it in this state for over an hour with no progress.
Boot and recovery mode work fine. Unfortunately adb is not in root by default, as such pulling is useless as nothing is mounted.
issuing
Code:
adb root
will result in:
Code:
adbd cannot run as root in production builds
I can issue for instance:
Code:
adb shell
su
e2fsck -pv /dev/block/mmcblk0p10
mount -t ext4 /dev/block/mmcblk0p10 /data
Unfortunately I cannot tar gzip and copy to the externalSD nor pull the data folder.
Starting dalvikvm fails:
Code:
127|[email protected]:/ # dalvikvm
dalvikvm
Dalvik VM init failed (check log file)
What options do I have to backup my data? Please provide me with concrete ideas and steps.
Many people are having similar problems, and I sincerely thank you if you can help me figure out a way to backup my data at this stage.
After reading the first two sentences and the title:
Buy a new battery.
Install something else, you are still on an early leak and not an official release.
I found a quick solution. All kudos and thanks go out to Philz as well as
TAHER128
Instructions and files are here:
http://www.youtube.com/watch?v=1TinSwsehZ8
After the new recovery mode and kernel is installed, reboot into recovery mode and go to the mount menu in order to select "mount USB storage". Backup everything to your PC.
From hereon out you are safe.
Install busybox if you want. Reflash a stock or custom rom if you want and/or dig your way through logs and fixes within a now powerful bash shell.
blairmiller said:
This problem is difficult to solve by your phone itself. Maybe you need to install some software to help you.
Click to expand...
Click to collapse
This thread is 2 months old
root
The reasons for getting a bootloop on your Android device might be anything. If you wish to know the reason why your Android phone is stuck on the bootloop, you need not type your problem on the Google search box. Just calm yourself for a while and think what you did just before. It could be anything! Here are some major reasons why your Android device is caught in a bootloop.
So last night, I was beta testing a ROM. After playing with it for a while, decided to go back to my previous setup and work on something. I rebooted into TWRP, wiped my Dalvik Cache, data, cache, and system partitions, and tried to flash the nandroid of Kinology I had been running before testing the beta ROM. I rebooted... only to discover that my Kindle wouldn't boot past the 2nd bootloader.
I thought, "okay, no biggie, I can fix this. I tried wiping and then flashing a couple of other ROMs I had on my SD card. Didn't work. I rebooted the bootloader and flashed a trio of images I had on my hard drive via fastboot. Nope. I tried sideloading CM10.2. Still nope. I tried mounting USB and pushing a ROM to my SD card and flashing from there. Again, no (anyone noticing a pattern?).
No matter what I do, I can't flash anything or get anything to transfer over to my device.
Help!!
Why do I get the feeling this has something to do with the boot image... Does it ever boot to the point you can logcat? Also I thought I read about some issues restoring nandroid's after the system was using selinux, though I haven't experienced this with mine. You tried cm 11? I know it had full selinux support. If you can't get the logcat to work I think there's a module that gets dumped that you can access in twrp over adb. And of all things to ask, if you flash the ROM in testing back does it still boot? If so that would make me think something weird is going on with the boot image. Also what version of twrp are you using?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Why do I get the feeling this has something to do with the boot image... Does it ever boot to the point you can logcat? Also I thought I read about some issues restoring nandroid's after the system was using selinux, though I haven't experienced this with mine. You tried cm 11? I know it had full selinux support. If you can't get the logcat to work I think there's a module that gets dumped that you can access in twrp over adb. And of all things to ask, if you flash the ROM in testing back does it still boot? If so that would make me think something weird is going on with the boot image. Also what version of twrp are you using?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks for answering. "adb logcat" doesn't work. It only shows "-waiting for device-". I tried flashing CM11 this morning, but the install failed. I also tried re-flashing your ROM again this morning, but same result. I've got TWRP 2.6.0.0. I've been meaning to flash the latest one from @Hashcode, but it slips my mind every time I think of it.
Something weird: whenever I push anything to the device over ADB, I push it to the SD card. But when I run "ls /sdcard/" in ADB shell, there's nothing there (even though it says it has been successfully pushed).
EDIT: Okay, I flashed the latest version of TWRP (2.6.3.1). I flashed CM11, and it reported that the flash was sucessful. But when I rebooted... nope.
This is weird... So weird. I'm almost at a loss, have you tried flashing a boot.IMG via fastboot corresponding with whatever ROM you flashed? I know I keep saying I think it's this without any real proof but this is kinda bizarre and if no ROM's are working and all you see is the kindkle logo I would assume that the init.RC scripts never got passed the pvrsrvinit or somewhere around that, possibly even before that since adb isn't working when the device is on the logo. You using adb from windows or Linux?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Ph0enix_216 said:
No matter what I do, I can't flash anything or get anything to transfer over to my device. Help!!
Click to expand...
Click to collapse
After I read this, I decided to try and restore and everything restored just fine *whew*. What I do know is that when ever this situation has come up (and a few people have stated they had this problem) only a complete factory restore fixed the problem. You're gonna have to break out the fastboot cord.
stunts513 said:
This is weird... So weird. I'm almost at a loss, have you tried flashing a boot.IMG via fastboot corresponding with whatever ROM you flashed? I know I keep saying I think it's this without any real proof but this is kinda bizarre and if no ROM's are working and all you see is the kindkle logo I would assume that the init.RC scripts never got passed the pvrsrvinit or somewhere around that, possibly even before that since adb isn't working when the device is on the logo. You using adb from windows or Linux?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
The init.RC scripts are still there, no matter how much I wipe in TWRP. I can see them using TWRPs file explorer. I haven't tried flashing the boot.img, I will try that. As for ADB, I'm using it on Windows 8, of all things.
LinearEquation said:
After I read this, I decided to try and restore and everything restored just fine *whew*. What I do know is that when ever this situation has come up (and a few people have stated they had this problem) only a complete factory restore fixed the problem. You're gonna have to break out the fastboot cord.
Click to expand...
Click to collapse
As I said before, I tried flashing two different sets of images via fastboot. Thanks for the response though. What all did you do in your restore process?
UPDATE
Okay, I tried re-installing CM10.2, and then flashing the boot.img from it via fastboot. Still no dice.
Is there any hope of recovering from this? It's been longer than a year, so I don't think Amazon will simply switch it out under warranty.
Agh, I was going to ask hashcode about it on the irc earlier and I forgot about it because my friend asked me to fix his pc...
Also remind me to slap this phone's spell check. It took me way longer to write the previous statement than it should have.
Edit: he's still in there but I think he's afk right now.
Sent from my LG-P769 using xda app-developers app
Ph0enix_216 said:
As I said before, I tried flashing two different sets of images via fastboot. Thanks for the response though. What all did you do in your restore process?
Click to expand...
Click to collapse
I just wiped and then restore 4.3 PA nandroid. That was another thin I forgot to mention.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
---------- Post added at 04:18 AM ---------- Previous post was at 04:14 AM ----------
LinearEquation said:
I just wiped and then restore 4.3 PA nandroid. That was another thin I forgot to mention.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was gonna suggest to flash CM10.2 first and then move up to CM11 because that was the route those with this problem had to go (4.3 then 4.4.) Restoring CM11 right off the bat did not seem to work for some reason. That's why I keep a 4.3 nandroid in TWRP, for just such a case. But I see you tried that.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
LinearEquation said:
I just wiped and then restore 4.3 PA nandroid. That was another thin I forgot to mention.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's weird, because I wiped then tried to restore my Kinology nandroid. Am I looking at an irreparable brick, or do I want to look into investing in a new tablet?
Wait until Monday, think you might get more info on a weekday... I have a theory of something that might fix your kindle but it could potentially hard brick it as well so I don't want to explain it yet until it's a last resort.
Edit: just talked to hashcode, he says to "adb pull /sdcard/ ." your sdcard and wipe internal storage, he also said because of kinology kernel not having selinux that if you want to use it you will have to downgrade twrp first and wipe everything again, you might find it easier to do it after flashing cm11 first. So basically back up the sdcard and wipe everything, check off everything including internal storage then push a Rom and flash it.
Sent from my LG-P769 using xda app-developers app
stunts513 said:
Wait until Monday, think you might get more info on a weekday... I have a theory of something that might fix your kindle but it could potentially hard brick it as well so I don't want to explain it yet until it's a last resort.
Edit: just talked to hashcode, he says to "adb pull /sdcard/ ." your sdcard and wipe internal storage, he also said because of kinology kernel not having selinux that if you want to use it you will have to downgrade twrp first and wipe everything again, you might find it easier to do it after flashing cm11 first. So basically back up the sdcard and wipe everything, check off everything including internal storage then push a Rom and flash it.
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
Checked everything. Wiped it all. Pushed a ROM via ADB. Not working.
I did some exploring with TWRP's built in file explorer. Despite wiping internal storage, I can still see some things I had on there previously. At the root of my device, however, I can also see this:
Code:
boot
cache
data
dev
efs
etc
license
proc
recovery
res
root
sbin
sdcard
supersu
sys
system
tmp
vendor
default.prop
file_contevts
fstab.bowser
fstab.goldfish
init
init.rc
property_contexts
seapp contexts
sepolicy
ueventd.bowser.rc
ueventd.goldfish.rc
ueventd.rc
I may be mistaken, but isn't that some of Firefox OS's stuff? The init.rc files you were talking about? It all may just mean nothing. Also, all my SD contents seem to be preserved in "/data/media/". I tried flashing CM11 from there as well. The flash was successful, but at boot... nada.
Still, thank you all for trying
Umm sorry I'm a little late to the party... Or funeral(if we cant fix your kindle) I was testing stunt's FireFox OS too and after testing I flashed back to my CM11 back up just fine, why not use the system image restore tool in the development section (minimize error, the tool is 99.9% fool proof) bailed me out multiple times when I thought my kindle was a goner(i know you manually flashed images. But why not try a tool?), and I have a theory... Stunt PMd me instructions on how to get the kindle to pick up/read the SD card I didn't try implementing the code because I'm not that techy but did you try it? What if the solution messed with your internal SD card since Firefox OS and Android Have their differences? Or something went wrong will modifying the commands stunts gave you?
And no...I'm not trying to insult Stunt's work or defame it, nothing is perfect and anything is possible so sorry if my response seems a bit disrespectful to the devs work.
Sent from my SAMSUNG-SGH-T769 using XDA Premium 4 mobile app
I still think this has something to do with selinux... I would know more if you had a serial hookup to the kindles motherboard but I don't even have that, if I had some kernel output it would be useful... Those files you saw that I mentioned aren't Firefox OS specific, they are Linux specific, they are going to always appear there because they are loaded from the initial ram disk in the boot.IMG, since android uses a Linux kernel you have init.rc files and such. Some of those directories are from recovery, the folders that should know appear empty I think are /data, /cache, /system and I can't remember the rest offhand. I will have to ask hashcode about this more tomorrow. I can think of something you might do from fastboot that might fix this but I don't know the specifics and it might wipe the boot loader, which wouldn't necessarily be bad as long as you reflash it before rebooting, but I'd like to avoid my idea because it seems rather risky, anyways I will ask about this tomorrow, so don't look into my concept idea....
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
when you said your sdcard contents are preserved, did you mean even after wiping internal storage that the sdcard's contents were still there?
stunts513 said:
when you said your sdcard contents are preserved, did you mean even after wiping internal storage that the sdcard's contents were still there?
Click to expand...
Click to collapse
Correct. Not only are they still there, but I can't seem to add anything to it. Pushing via ADB is successful on the PC end, but if I check the SD card, no change. Also, everything I had before the brick on my SD card is still in "/data/app", if that tells you anything.
Thanks for taking time to they and help me
>>>Sent from my ZTE Valet Z665C<<<
Ph0enix_216 said:
Correct. Not only are they still there, but I can't seem to add anything to it. Pushing via ADB is successful on the PC end, but if I check the SD card, no change. Also, everything I had before the brick on my SD card is still in "/data/app", if that tells you anything.
Thanks for taking time to they and help me
>>>Sent from my ZTE Valet Z665C<<<
Click to expand...
Click to collapse
ok um at this point hashcoed is helping me out and i tink i can fix it but it will be easier if i can msg you on skype or in the irc, whatever works best for ya, because this will involve some trial an error over an adb shell... i would try it on my own but it will involve me backing up quite a bit of data and you already have done that so i thought this might be easier than me formatting my own in the process...
Edit: Ok actaully try this first and see what happens, boot into recovery and run this in an adb shell
Code:
umount /data
mke2fs -T ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata
that should actually format the userdata partition and hopefully fix this. though make sure that the unmount worked first, you don't want to try to format a partition while its mounted.
2nd edit:actually i'm a moron, you don't even need to umount /data, just uncheck it in the mount section, you can tell i'm way to used to normal linux... always a good idea to run mount and double check its not on the list but it shouldn't be.
SUCESS!!!
stunts513 said:
ok um at this point hashcoed is helping me out and i tink i can fix it but it will be easier if i can msg you on skype or in the irc, whatever works best for ya, because this will involve some trial an error over an adb shell... i would try it on my own but it will involve me backing up quite a bit of data and you already have done that so i thought this might be easier than me formatting my own in the process...
Edit: Ok actaully try this first and see what happens, boot into recovery and run this in an adb shell
Code:
umount /data
mke2fs -T ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata
that should actually format the userdata partition and hopefully fix this. though make sure that the unmount worked first, you don't want to try to format a partition while its mounted.
2nd edit:actually i'm a moron, you don't even need to umount /data, just uncheck it in the mount section, you can tell i'm way to used to normal linux... always a good idea to run mount and double check its not on the list but it shouldn't be.
Click to expand...
Click to collapse
SUCESS!!! I did what you said and formated the data partition, and I was able to successfully push CM11 to my Kindle. I flashed it, it reported the flash as successful, and I rebooted.. I was greeted by new CM11 boot animation (right now, it's one of the most beautiful things I've ever seen.
Thank you to everyone who responded to this thread. It's nice to know that there are people nice enough out there to take the time and help someone in need.
Some questions though:
1.) With this SELinux or whatever, can I still switch ROMs as easily as I did before? Or am I now limited to CM11 and such?
2.) What exactly happened? I've never had this happen before, where my /data partition derped out and TWRP wouldn't flash anything.
I'm not to familiar with how selinux works but from we hat I remember I think it was something like this. You had a recovery that I think may have supported selinux but I'm not positive about that. The kinology ROM you had on there had no selinux support in the kernel. My ROM has some selinux support in it since I based it on 4.3, and I have no idea what happened that messed it up after that, all I can tell based on what you had to do to fix it is that the xattributes for selinux were not getting cleared off the partition and for some reason the ROM's that could handle selinux didn't seem to like it either. If you want to run kinology again you may need to downgrade twrp so you can reformat the partition again so it reformats without selinux but I'm a bit confused on this myself, this isn't my best field in computers.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app