Related
I encrypted my 10.1 yesterday without thinking all the way though. I found out that I could no longer flash kernels while the tablet is encrypted, since the SD card is not accessible in CWR.
I've tried doing a factory reset on my tab and each time, it boots up like nothing happened. I've also tried removing the pin that I put on it and the option to remove it is grayed out.
Do any of you know of a way to do a full wipe on the 10.1? Or could I reflash it using ODIN?
Thanks in advance.
id like to know this as well
still nothing? im starting to think this is an easy fix that nobody has posted about yet
there has to be something that im missing
try post # 6 in the linked thread, restore with unmodified vanilla version image from second link provided in the post, after booting from fastboot into recovery with clockworkmod recovery img; pushing it into the device sd with adb commandline, check the post for modifications and the link for details.
http://forum.xda-developers.com/showthread.php?t=1161325
whenever i try to reset to factory defaults, it just reboots like nothing happened
re-flash a stock firmware via odin as tar or fastboot/nandroid as img (backup restore)
Ones the tab is encrypted, there's no way to un do it. Unless you do what mughalgxt suggested. Good luck
Thanks guys, I went through some of these steps and found some other good tutorials to get me back up and running. All i wanted was to try the new kernel/bonsai rom out and I'm now able to do that
**** encryption, put a lockscreen password and be done with it.
I'm still struggling with this, as well: off to read some of the linked threads, because even with flashing a stock image with ODIN I'm still not able to recover the device. At least I managed to proceed past the boot loop I WAS in (when attempting to flash from CWM) - but now, I can get to the point where the device prompts me for the decryption key (meaning, it's clearly not yet restored to factory defaults) - but can't get it boot to completion. I also note that I've still got CWM Recovery, not stock.
It seems, at some point, encryption-key be damned, right? Meaning, if I don't care about recovering the contents of the encrypted partition - surely these low-level tools have the ability to simply format the partitions? Perhaps not - at least, not CWM - as attempts to format /data continue to fail.
Off to review the linked threads to try to gain some additional insight.
I ran into this same issue a long while back. As I recall (and it's been a while), you won't be able to wipe from CWM, but you can wipe from Settings / Privacy / Factory Data Reset. I could be wrong, but I know that I didn't have to do any adb pushing or anything with special images.
Hi SacTilt-
Thanks for the reply - and agreed: Had I actively started the effort from a functioning device, I think I could have selected that option.
As it turns out - I ran CWM, rebooted into recovery, and... next thing I knew, I was in boot loop hell.
I've tried flashing a variety of files via ODIN: Some at least allow the device to boot to the point where I get the initial password prompt - which I can provide, and proceed past... but then the device just 'goes blank'.
What I'm looking for is a 'start-from-scratch', no concern for data loss, delete the dang encrypted /data folder already, will ya?... approach.
As I've mentioned, a variety of ODIN files from a myriad of sources haven't seemed to quite do the trick. I feel like I'm missing something obvious - but can't find the right angle to spot it.
Perhaps fastboot might be what I'm looking for?
FWIW: the device was rooted when I started, so I've got full Titanium backups, with which I can restore, once I recover the actual device / OS.
Thanks for any insight.
Hey guys...if anybody finds a solution to this, please let me know...I am stuck with this same damn experimental ROM I've had from day one...it's getting really old. All I want is to get rid of this stupid encryption. Thanks for any help. Tried ODIN flashing, wiping data from security screen, wiping from CMR, etc.
Have you tried formatting the sd? Whenever i had my ns4g i accidentially did the same thing and i wiped the SD and it removed the encryption.
Sent from my GT-P7510 using XDA Premium HD app
Using nightly 150 and everything was going well. Now the nook can't quite get through an entire boot process. The screen goes blank and I have to reboot/plug into charger/unplug/replug. When trying to restore back to an old backup it gets about halfway through restoring system before the screen goes black and may or may not reboot. I have been trying to fix this for 3 days now. I cant get through a whole restore process without this happening. I need help. Thank you in advance for any ideas/suggestions.
EDIT: I put on a new anti-glare screen protector just minutes before this started. Could that have anything to do with this? Four corners being pushed down or something like that. Just thought I'd throw that in there.
In CWM, format System, Data, and Cache. Then install the latest Nightly, and from there re-flash CWM. Then restore the backup of data.
ikingblack said:
In CWM, format System, Data, and Cache. Then install the latest Nightly, and from there re-flash CWM. Then restore the backup of data.
Click to expand...
Click to collapse
I have tried this from recovery and it does not get through the install before shutting off on me. Should I try using a CWM SD card? Do you think that would make a difference?
Definitely try a CWM sd card. Make the sd card and copy the "clockworkmod" folder from your current sd card to the CWM sd card. From there restore the backup.
Edit: Try taking off the Screen Protector first.
Solved! I think it might have had something to do with my charger. The base of the cable is frayed and it may have not been getting charged. So the battery would die before it was getting through the install. Never gave me the battery low indication though til today. Thank you iKing for your fast response. Calling 1800thebook to see if they still send out new ones!
Alright, Congrats on getting it to work. And yes, they should give you a free cable. They did mine when my cable was screwed. Good Luck!
Gotta be the worst cable ever made!
@ mods i realised my mistake in posting this in the wrong section and posted in the right one but people are replying to this one......so please dont delete this just yet
I in my infinite wisdom tried to mod a file on my phone. I did a titanium backup 1st but forgot to move it to my external SD Doh!
So that went wrong and now I'm stuck in a boot loop with only the stock recovery screen. Need to install stock rom and adb not recognized. (Im sure ill figure that) but my main question is, is there some way to recover data from the internal "sd" memory?
I really appreciate any advice anyone can give
I am not sure if I understood your question.. if you have CWM then just access recovery mode and you will have an option to mount the SD and you will be able to access all your files via USB from your PC
?
I don't have cwm . Like I said I only have the stock recovery screens I.e factory reset and download mode.
Do a factory reset, it won't erase your data.
Not sure that would work. It says wipe user data and factory reset so surely it would wipe my data. Plus I don't think that'll work anyway as I changed a file which caused the boot loop so I don't think a factory reset will fix that file.
Androboyben said:
Not sure that would work. It says wipe user data and factory reset so surely it would wipe my data. Plus I don't think that'll work anyway as I changed a file which caused the boot loop so I don't think a factory reset will fix that file.
Click to expand...
Click to collapse
what info are you trying to get off the device? the sms etc are stored on your data and will be wiped by a reinstall/factory reset
anything on the usb side for storage will not get touched
Factory reset wont clear anything on the internal_sd
thank you.....but
thanks for the replies peeps ill trust your knowledge (and have pressed the thanks button )
got a day off tomorrow so gonna try and get it up and running again,
Question though, being as i buggered up the stock rom wont flashing the new rom (when i figure out how) delete internal data either.
the reason im being carefull is i did some awesome illustrations (imo) for a childrens book im writing so hoping to save those.
Androboyben said:
thanks for the replies peeps ill trust your knowledge (and have pressed the thanks button )
got a day off tomorrow so gonna try and get it up and running again,
Question though, being as i buggered up the stock rom wont flashing the new rom (when i figure out how) delete internal data either.
the reason im being carefull is i did some awesome illustrations (imo) for a childrens book im writing so hoping to save those.
Click to expand...
Click to collapse
it depends on if you use a wipe or non wipe rom, a non wipe wil lkeep qall the data stored on the android system intact but you might get bootloops if it doesnt replace the file you say you deleted
took the plunge......alls good
Richy99 said:
it depends on if you use a wipe or non wipe rom, a non wipe wil lkeep qall the data stored on the android system intact but you might get bootloops if it doesnt replace the file you say you deleted
Click to expand...
Click to collapse
Thanks Richy99, i took the plunge and followed nasgilani's guide to installing stock rom, i was supprised when it completed that even my home screens etc were as they were before (appart from widgets being blank) and glad to see "as you all said" my data intact.
i shall be more cautious before i start messing with mods next time
basically internal usb storage of 11gb will never be touched when you factory reset nor wil lanything on an external sd card
the only thing that gets wiped is the 1gb internal space for the rom and data on that partition such as sms/email etc
I know this is an old topic but I noticed it wasn't exactly answered.. I'm trying to send mine back to the factory for warranty because the power button no longer functions. I have the stock rom and recovery and I'm stuck in boot loop because I can't execute factory wipe with the power button. I'd like to pull my data off of the internal SD but am unable to fix the bootloop without forcing the wipe.
I know metter is over now, it was just ur worrying, otherwise wiping cache,wiping data from recovery , flashing stock rom (wipe/non wipe) nothing.will erase data on internal memory.
Just for knowledge
aroma file manager is available, which works from recovery, it can work even you device stucked, unable to boot..
Edit ; sometime you feel ashamed, just come to know this is 6month old topic
Sent from my GT-N7000 using xda premium
Hi everyone, sorry to post but I'm at wits end.
I've searched and googled all over for the past week and have found problems similar to mine but none of the fixes have worked.
If this has already been asked I apologise and will remove but here goes:
I rooted my phone and using the latest cwm flashed the rc1 of cm10, this didnt flash properly so I tried again, no joy.
I read around and decided to try with a different recovery, twrp.
So I tried flashing with that, again no joy. so i used twrp to do factory reset and cache wipes. As I was unfamiliar with the layout of twrp I'm under the impression I've deleted or wiped the cache/system and data partitions.
I've since flashed a PIT file to restore the original partitions, gone back to stock tried reflashing new roms. Its been a nightmare.
The issue itself is no recovery can mount the ext-sd which is actually the internal memory and cannot access the cache/log etc.
The phone itself shuts down randomly and then will not boot up.
Adb can't write or push anything to the device either, the strange thing is when the phones working for brief periods of time I can read and write to device memory?so at this point I'm flat out of ideas.
Any help/ideas or advice would be gratefully received, once again thanks guys
kingbob134 said:
Hi everyone, sorry to post but I'm at wits end.
I've searched and googled all over for the past week and have found problems similar to mine but none of the fixes have worked.
If this has already been asked I apologise and will remove but here goes:
I rooted my phone and using the latest cwm flashed the rc1 of cm10, this didnt flash properly so I tried again, no joy.
I read around and decided to try with a different recovery, twrp.
So I tried flashing with that, again no joy. so i used twrp to do factory reset and cache wipes. As I was unfamiliar with the layout of twrp I'm under the impression I've deleted or wiped the cache/system and data partitions.
I've since flashed a PIT file to restore the original partitions, gone back to stock tried reflashing new roms. Its been a nightmare.
The issue itself is no recovery can mount the ext-sd which is actually the internal memory and cannot access the cache/log etc.
The phone itself shuts down randomly and then will not boot up.
Adb can't write or push anything to the device either, the strange thing is when the phones working for brief periods of time I can read and write to device memory?so at this point I'm flat out of ideas.
Any help/ideas or advice would be gratefully received, once again thanks guys
Click to expand...
Click to collapse
Try and root your phone again with this http://forum.xda-developers.com/showthread.php?t=2219803
Thanks for the suggestion, this is the root file I've been flashing already
kingbob134 said:
The issue itself is no recovery can mount the ext-sd which is actually the internal memory and cannot access the cache/log etc.
Click to expand...
Click to collapse
Ext sd is your sdcard.Internal memory is the system and data.
The pit file was not needed after you formatted the system.Its only for repartition.
My suggestion is to format system flash stock rom do a factory reset then reboot.
Sent from my GT-I9500 using Tapatalk 4
Sorry thats my mistake, I can't mount ext-sd in recovery to format it and nothing can be acessed in cache or cache/logs, hence I thought it was an issue with the partitions. I've tried your suggestion but will try again.
Thankyou
kingbob134 said:
Sorry thats my mistake, I can't mount ext-sd in recovery to format it and nothing can be acessed in cache or cache/logs, hence I thought it was an issue with the partitions. I've tried your suggestion but will try again.
Thankyou
Click to expand...
Click to collapse
Is your phone booting fine ? I didn't understand your actual problem.I just checked the recovery.Sd-ext is the second partion for the sdcard./external sd is the sdcard.
If cache can't be mounted just format it.
Sent from my GT-I9500 using Tapatalk 4
Hi again. Cache can be mounted and formatted but recovery can't access cache/logs. My biggest issue is that the phone will randomly close when under stress and hit a bootloop that can only be cured by attaching the charger. The phone does boot I'm currently running pacman ROM. Tbh I'm fairly certain I wiped something important but flashing stock and even a pit file hasn't corrected it
kingbob134 said:
Hi again. Cache can be mounted and formatted but recovery can't access cache/logs. My biggest issue is that the phone will randomly close when under stress and hit a bootloop that can only be cured by attaching the charger. The phone does boot I'm currently running pacman ROM. Tbh I'm fairly certain I wiped something important but flashing stock and even a pit file hasn't corrected it
Click to expand...
Click to collapse
Weired.Did you try other recoveries ? Unfortunately I don't have any idea of what else you can do.
I've tried cwm, twrp and am currently running philztouch recovery as this seems to be the most stable on my phone, I can mount every directory but sd-ext and it also cant format that directory.
I installed AParted app to it this afternoon during a shortlived moment of clarity, phone not me, and tried fixing partitions/blocks. the only viewable were /dev/block/mmcblk0 and /dev/block/mmcblk1
the former, blk1 had 4 pieces of varying sizes but no registered file system whilst the latter was fat32. Could it be that the unacessable sd-ext is in the wrong file format? I've read for cwm and philz it needs to be ext4 but I may be mistaken.
also the crashing seems to occur when an app or process attempts to write to our unaccesable area and leaves me in a bootloop stating the battery is dead. So weird...
beginning to lose hope of solving this and fixing my buggy phone
Anyone with any ideas/experience please help, I'm willing to try almost anything at this point
thanks again guys
ext-sd?
Have no idea about this, but who cares
Many TWRP and CWM first releases break /data and /cache when you format them in recovery
Only known fix for is to flash a full STOCK rom (sammobile tar.md5) using odin + PIT (the right one, memory wise)
All my last recovery releases fully support all format options on S4
By the way, internal storage = sdcard = /data
Thanks for your quick reply Phil. I've flashed back to stock multiple times using a pit file and the sammobile firmware for my device. No joy unfortunately. And your recovery brings back an error when trying to mount or format sd-ext. I don't know what the issue could be but its crashing my phone near constantly
kingbob134 said:
Thanks for your quick reply Phil. I've flashed back to stock multiple times using a pit file and the sammobile firmware for my device. No joy unfortunately. And your recovery brings back an error when trying to mount or format sd-ext. I don't know what the issue could be but its crashing my phone near constantly
Click to expand...
Click to collapse
Hi,
try to fix it tru kies recovery.
Have you tried formating your Ext SD card in a PC? maybe its corrupt?
Also the boot loop you mentioned, only being fixed by attaching a charger sounds like a faulty battery. Is it swollen in the middle?
I would try new SD card and/or battery and see if that helps.
I've tried lies and no joy. The sd-ext is a partition in the internal memory not the external SD card, confusing I know. Battery appears fine. During my reading someone mentioned it may be inaccessible due to it being in the wrong format also that it could've corrupted blocks of memory and the crash occurs when the phone tries to access said block. Any thoughts?
kingbob134 said:
I've tried lies and no joy. The sd-ext is a partition in the internal memory not the external SD card, confusing I know. Battery appears fine. During my reading someone mentioned it may be inaccessible due to it being in the wrong format also that it could've corrupted blocks of memory and the crash occurs when the phone tries to access said block. Any thoughts?
Click to expand...
Click to collapse
Hhhhmmm have you tried running a e2fsck on the sd-ext block?
Sd-ext is the second partition of the SD card while /external-sd is the primary.If you don't have a second partition that's normal if it can't get mounted.
Sent from my GT-I9500 using Tapatalk 4
sd-ext is in external_sd
If that's only error you get, it is not an error, it is normal
Google for sd-ext
ijnegea jessie
Well that clears that issue but still leaves me with the crashes and bootloop.
When I try to flash a ROM via recovery it isn't 100percent successful and it then says it can't access cache and cache/recovery/log even though when the phone is running they are visible so I know they're there. This is driving me to despair now. Thanks for the input guys
kingbob134 said:
Well that clears that issue but still leaves me with the crashes and bootloop.
When I try to flash a ROM via recovery it isn't 100percent successful and it then says it can't access cache and cache/recovery/log even though when the phone is running they are visible so I know they're there. This is driving me to despair now. Thanks for the input guys
Click to expand...
Click to collapse
Did you try a factory reset with philz recovery ? Technically that should format cache and data with a compatible filesystem
Sent from my GT-I9500 using Tapatalk 4
Styrke said:
Did you try a factory reset with philz recovery ? Technically that should format cache and data with a compatible filesystem
Sent from my GT-I9500 using Tapatalk 4
Click to expand...
Click to collapse
Yeah I tried that. Still nothing
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.