Related
Okay, today I was about to flash a new rom so I attempted to wipe, but I got an error that the phone could not mount the cache (and later couldn't mount data). It says "E:Can't mount CACHE:recovery/command" on the next line "E:Can't mount CACHE:recovery/log" and the next "E:Can't open CACHE:recovery/log". So I have tried reflashing recovery to fix it and it did not work. I cannot flash any rom without an error or restore my nandroid backups. I am in the process of trying to restore the nandroid backups throught fastboot. Can anyone give me any help on this?
SOLUTION: blancoisgod recommends formatting the cache partition to fix this problem
Did you pull the battery and retry?
Yep. Actually, the phone wont even turn on anymore. I will just have to return it to tmobile tomorrow
toby4059 said:
Yep. Actually, the phone wont even turn on anymore. I will just have to return it to tmobile tomorrow
Click to expand...
Click to collapse
This is exactly why manufacturers don't want people rooting and messing with their phones.
So because of your stupidity and lack of foresight you're now going to return your phone?! That's laughable.
Now T-Mobile and HTC have to pick up the bill for someone else's ignorance.
Note to self....remember your name and never help you!
No man dont turn it into tmobile. Now everyone is gonna ride you because you broke it and your going to return it because of what you have done,not the manufacturer.
Go ahead and turn it in, but please read around a bit before you do this again.
CBConsultation said:
This is exactly why manufacturers don't want people rooting and messing with their phones.
So because of your stupidity and lack of foresight you're now going to return your phone?! That's laughable.
Now T-Mobile and HTC have to pick up the bill for someone else's ignorance.
Note to self....remember your name and never help you!
Click to expand...
Click to collapse
Your right it is my fault; although, I am not sure what I did wrong. I am not a complete idiot and have been doing this stuff for a while. I did everything by the instructions and this happened. I actually saw this happen to someone in the G2 forum but no one found a solution. I see how returning the phone would be wrong but what are my options? I am only 15, no income, so what could I do. If I had income of course I would just pay for a new phone. I hope I am not coming off as a dumb juvenile crook, I apologize.
toby4059 said:
Your right it is my fault; although, I am not sure what I did wrong. I am not a complete idiot and have been doing this stuff for a while. I did everything by the instructions and this happened. I actually saw this happen to someone in the G2 forum but no one found a solution. I see how returning the phone would be wrong but what are my options? I am only 15, no income, so what could I do. If I had income of course I would just pay for a new phone. I hope I am not coming off as a dumb juvenile crook, I apologize.
Click to expand...
Click to collapse
Did you make a backup image? If so you could just flash your recovery image and be golden. If not, then your options are very limited.
I was not trying to hurt or insult your feelings but we constantly see people who 'think' they know what they're doing with these same issues all day every day.
My advice is limited as well at this point because I'm not sure exactly what you've done or precautions you had in place for this.
Can you even boot into the OS at all? Do a factory reset?
CBConsultation said:
Did you make a backup image? If so you could just flash your recovery image and be golden. If not, then your options are very limited.
I was not trying to hurt or insult your feelings but we constantly see people who 'think' they know what they're doing with these same issues all day every day.
My advice is limited as well at this point because I'm not sure exactly what you've done or precautions you had in place for this.
Can you even boot into the OS at all? Do a factory reset?
Click to expand...
Click to collapse
I cannot turn the phone on what so ever. I was flashing my backup through fastboot then tried to reboot and now it will no longer turn on. I fastboot erased recovery, system, userdata, and boot and restored them from the nandroid backup I had taken prior to the error. The day prior I had rooted successfully and flashed the desire z port. I decided I wanted to try the HD port so I wiped and flashed the rom. When I rebooted it got to the lockscreen and it showed some graphical corruption then began to boot loop. I turned it off and went to recovery and thats when the CACHE errors started. Was I supposed to wipe the dav cache because I am pretty sure I did. I just want to find out what I did wrong so it won't happen to me or anyone else.
toby4059 said:
I cannot turn the phone on what so ever. I was flashing my backup through fastboot then tried to reboot and now it will no longer turn on. I fastboot erased recovery, system, userdata, and boot and restored them from the nandroid backup I had taken prior to the error. The day prior I had rooted successfully and flashed the desire z port. I decided I wanted to try the HD port so I wiped and flashed the rom. When I rebooted it got to the lockscreen and it showed some graphical corruption then began to boot loop. I turned it off and went to recovery and thats when the CACHE errors started. Was I supposed to wipe the dav cache because I am pretty sure I did. I just want to find out what I did wrong so it won't happen to me or anyone else.
Click to expand...
Click to collapse
Between ROM's, you said you wiped. What did you wipe? Cache? Dalvik? Partition?
You said you're not too sure so I am going to assume you either didn't wipe something you should have or you did wipe something you shouldn't have.
Try this. Remove the battery for 10 minutes. When the battery is removed, hold the power button for about 2 minutes. This will drain any residual current left on the board. After the 10 minutes are up, try reinserting the battery, hold the volume- button and try to power on. We'll see if you can manage to boot into recovery at this point.
CBConsultation said:
Between ROM's, you said you wiped. What did you wipe? Cache? Dalvik? Partition?
You said you're not too sure so I am going to assume you either didn't wipe something you should have or you did wipe something you shouldn't have.
Try this. Remove the battery for 10 minutes. When the battery is removed, hold the power button for about 2 minutes. This will drain any residual current left on the board. After the 10 minutes are up, try reinserting the battery, hold the volume- button and try to power on. We'll see if you can manage to boot into recovery at this point.
Click to expand...
Click to collapse
Okay I will give that a try thanks.
I had the same error just right now man
What you want to do is format the cache partition when you get the thing booted.
blancoisgod said:
I had the same error just right now man
What you want to do is format the cache partition when you get the thing booted.
Click to expand...
Click to collapse
Did you do that and did it fix? I did that through adb and thats when it stopped booting, although I think the boot issue is unrelated to my current problem.
i did it via clockwork
Alright, I will try this if I can ever get my phone started again.
Hey Guys,
About two weeks ago, I left to go out of the country. I left my phone powered on and sitting on my desk.
I come home, and my wife said she plugged it in to use the alarm on it, however it just looped over and over at the Sprint 4G animation.
I have tried replacing the battery, cooling it down, and other random things, but nothing seems to unstick it.
The phone is stock un-modded phone.
When i try to go to recovery mode, first time it just hung at the HTC logo, last time I tried, it gave a small picture of a phone, with a red triangle and an exclamation mark.
I can run a crc check using the 'image crc' option from the bootloader, and after a minute, it comes back with:
hboot: 0xFBDE7777
boot: 0xE4841560
recovery: 0x3F342ECF
system: 0x98F9E14F
I have tried with and without the SD card, and with/without being plugged in.
SPEEDY XE SHIP S-ON
HBOOT-0.93.0001
RADIO-1.07.00.1129
eMMC-boot
Nov 15 2010, 13:19:54
The only other thing I can think of, is that I saw a low memory error a few hours before I left.
I have some really important data on the phones built-in memory. Any ideas or suggestions are most appreciated!
Thanks!
Actually, I just found in recovery mode, to hold the power button and vol+ button to get details.
E:Can't open /cache/recovery/command
E:Error in DATA:data/recovery/log
(No space left on device)
So I am guessing it is stuck looping due to being out of internal memory space.
I have the following options:
Reboot system now
Apply sdcard:update.zip
Wipe data/factory reset
Wipe cache partition
I am worrid that even wiping the cache partition might cause some sort of data loss?
Can anyone confirm that for me?
Any ideas or suggestions on how to get in to free some space up otherwise?
Thanks!
Do not wipe anything yet. If you have a way of Fully charging the Battery without the device, do so. Let the battery fully charge, then put it back in the phone. Power it up and see if it will boot normally.
Wiping cache will not cause data loss, and it may be your only option to try and get it booting, if you call Sprint their gonna go a whole factory data reset and that clears all
Sent from my myTouch_4G_Slide using Tapatalk
strapped365 said:
Wiping cache will not cause data loss, and it may be your only option to try and get it booting, if you call Sprint their gonna go a whole factory data reset and that clears all
Sent from my myTouch_4G_Slide using Tapatalk
Click to expand...
Click to collapse
I know you said no data loss for wiping the cache, is there any reason that I shouldn't just go ahead and try wiping the cache? Just wanna check things before I do something
Thanks a bunch!
Narkain said:
I know you said no data loss for wiping the cache, is there any reason that I shouldn't just go ahead and try wiping the cache? Just wanna check things before I do something
Thanks a bunch!
Click to expand...
Click to collapse
Sorry buddy took a nap LOL give it a shot, if all lease fails a full wipe is needed
Sent from my myTouch_4G_Slide using Tapatalk
Just wipe cache. What it will do will force your phone to re-creat all of your dalvik-cache. It will take a really long time to boot depending on how many apps you have installed for it to load up in the boot proccess. Give it time to boot, it's not a bootloop unless your bootanimation keeps restarting with a blank screen inbetween. If that doesn't work most likely your data got corrupted some how and you'll have to wipe data.
sparksco said:
Just wipe cache. What it will do will force your phone to re-creat all of your dalvik-cache. It will take a really long time to boot depending on how many apps you have installed for it to load up in the boot proccess. Give it time to boot, it's not a bootloop unless your bootanimation keeps restarting with a blank screen inbetween. If that doesn't work most likely your data got corrupted some how and you'll have to wipe data.
Click to expand...
Click to collapse
Completed the cache wipe no problem. Phone boots up, loads the sprint animation, and then just sits looping sprint animation like usual.
Is there a custom bootloader that would let me browse the internal file system?
Mebbe delete something?
Without going into much detail just in case it's of a private nature. What kind of Data are you trying to retrieve? Contacts, SMS, Emails,...? The reason I ask is because it sounds like you may have to wipe the all the Data in order to get it to Boot.
prboy1969 said:
Without going into much detail just in case it's of a private nature. What kind of Data are you trying to retrieve? Contacts, SMS, Emails,...? The reason I ask is because it sounds like you may have to wipe the all the Data in order to get it to Boot.
Click to expand...
Click to collapse
SMS, random note & app data and some other stuff for legal reasons. I checked the sd card, none of what I need is on it.
Is there really no way to access the internal memory from any custom bootloader?
Or a way to insert some sort of script to erase some crap log file on the internal memory?
The phone stills has the default AmazonMP3 app and some other crap that I could script a deletion for to easily free up memory safely.
Also, I noticed under recovery options it also says "E:Can't open /cache/recovery/command" in yellow at the bottom.
I really don't want to wipe the phone
Thanks
Narkain said:
SMS, random note & app data and some other stuff for legal reasons. I checked the sd card, none of what I need is on it.
Is there really no way to access the internal memory from any custom bootloader?
Or a way to insert some sort of script to erase some crap log file on the internal memory?
The phone stills has the default AmazonMP3 app and some other crap that I could script a deletion for to easily free up memory safely.
Also, I noticed under recovery options it also says "E:Can't open /cache/recovery/command" in yellow at the bottom.
I really don't want to wipe the phone
Thanks
Click to expand...
Click to collapse
I mean you could try to adb pull items from recovery, but you need the sdk for that, and you also have to know exactly where the info is.
I don't think it will pull like the actual sms messages or anything but you should be able to pull some things from system or data
Sent from my myTouch_4G_Slide using Tapatalk
So... I've had a Kindle Fire with CM7 for quite a long time. I stopped using the tablet and just recently found it. Deciding I wanted to sell it, I thought doing a factory reset as well as wiping everything from every option would bring it back to stock. Apparently that wasn't so. Now it won't even turn on. I mean, I can boot to Recovery using TWRP, but there's nothing to flash at all. I mean, that should be expected, considered I, well, wiped my SD card.
I would have known how to fix this a year ago, but it seems I did not retain the know-how I once possessed. So, as a last-ditch effort, I'm coming here and asking what I should do before I do something even worse to it.
Mighty Maniel said:
So... I've had a Kindle Fire with CM7 for quite a long time. I stopped using the tablet and just recently found it. Deciding I wanted to sell it, I thought doing a factory reset as well as wiping everything from every option would bring it back to stock. Apparently that wasn't so. Now it won't even turn on. I mean, I can boot to Recovery using TWRP, but there's nothing to flash at all. I mean, that should be expected, considered I, well, wiped my SD card.
I would have known how to fix this a year ago, but it seems I did not retain the know-how I once possessed. So, as a last-ditch effort, I'm coming here and asking what I should do before I do something even worse to it.
Click to expand...
Click to collapse
I'm assuming your intention is to revert to stock?
http://forum.xda-developers.com/showthread.php?t=1638452
soupmagnet said:
I'm assuming your intention is to revert to stock?
http://forum.xda-developers.com/showthread.php?t=1638452
Click to expand...
Click to collapse
Thanks for the reply, but the instructions just aren't working. I must have gotten rid of something important. I wiped the cache, dalvik cache, battery stats, rotation, system, and SD card. I try flashing the stock ROM and it always fails.
I got my phone rooted, and wanted to try the Per app PDI using Xposed framework. Unfortunately upon installing the framework, my phone will not boot any more (stuck at ATT logo). I saw on the Xposed framework that I can try copying /system/bin/app_process.orig back to /system/bin/app_process, but can't seem to get into ADB. Can someone help please?
tvu815 said:
I got my phone rooted, and wanted to try the Per app PDI using Xposed framework. Unfortunately upon installing the framework, my phone will not boot any more (stuck at ATT logo). I saw on the Xposed framework that I can try copying /system/bin/app_process.orig back to /system/bin/app_process, but can't seem to get into ADB. Can someone help please?
Click to expand...
Click to collapse
You dun goofed. Try rebooting into recovery mode by holding down Vol up+Home before the Samsung logo comes up, and hit "wipe data/factory reset", but if it was a framework mod, then it's likely a problem with the /system/ partition. In that case, you're out of luck until we have an Odin-flashable factory image prepared.
breakingspell said:
You dun goofed. Try rebooting into recovery mode by holding down Vol up+Home before the Samsung logo comes up, and hit "wipe data/factory reset", but if it was a framework mod, then it's likely a problem with the /system/ partition. In that case, you're out of luck until we have an Odin-flashable factory image prepared.
Click to expand...
Click to collapse
Factory Reset worked in recovery.
Thanks!!!
tvu815 said:
Factory Reset worked in recovery.
Thanks!!!
Click to expand...
Click to collapse
Woot woot, but be a tad more careful next time
After trying Xposed, I couldn't enable the framework, I got the same issue of the phone hanging at the AT&T logo, and tried a factory reset. Now I get "Unfortunately, Settings has failed to load." after completing the setup wizard. USB debugging is no longer enabled due to the reset. Any way around the setup wizard or suggestions?
wtd966 said:
After trying Xposed, I couldn't enable the framework, I got the same issue of the phone hanging at the AT&T logo, and tried a factory reset. Now I get "Unfortunately, Settings has failed to load." after completing the setup wizard. USB debugging is no longer enabled due to the reset. Any way around the setup wizard or suggestions?
Click to expand...
Click to collapse
People need to quit trying to install Xposed?
Looks like for you, it's a system issue. Try performing another factory reset (you never know), and clear the cache.
Are you able to access anything after you complete the setup wizard?
breakingspell said:
You dun goofed. Try rebooting into recovery mode by holding down Vol up+Home before the Samsung logo comes up, and hit "wipe data/factory reset", but if it was a framework mod, then it's likely a problem with the /system/ partition. In that case, you're out of luck until we have an Odin-flashable factory image prepared.
Click to expand...
Click to collapse
hey i had the same issue but when i went into factory reset i just get an error :crying::crying::crying: is there any way to get a zip file out of the system? i have access to a fully stock SGS4 that has not been touched
ericos123 said:
hey i had the same issue but when i went into factory reset i just get an error :crying::crying::crying: is there any way to get a zip file out of the system? i have access to a fully stock GS4 that has not been touched
Click to expand...
Click to collapse
What error do you get when the factory reset fails? As for a zip file, we don't have any flashable system images yet, our devs are working on it, but when it's ready, you'll be able to use Odin to repair your device.
On a side note, I live 5 miles away from the national Samsung warranty repair facility in Richardson, TX, and they sell accessories at their front desk, so I went today to get a super cheap MicroSD card (32gb for $18.99). I chatted it up with a technician that works there, he's serviced my old Nexus S and Galaxy Note, and he mentioned that while they have a system image for the S4s, it's only for the international model, they're not expecting any fubar S4s until next week
breakingspell said:
What error do you get when the factory reset fails? As for a zip file, we don't have any flashable system images yet, our devs are working on it, but when it's ready, you'll be able to use Odin to repair your device.
On a side note, I live 5 miles away from the national Samsung warranty repair facility in Richardson, TX, and they sell accessories at their front desk, so I went today to get a super cheap MicroSD card (32gb for $18.99). I chatted it up with a technician that works there, he's serviced my old Nexus S and Galaxy Note, and he mentioned that while they have a system image for the S4s, it's only for the international model, they're not expecting any fubar S4s until next week
Click to expand...
Click to collapse
it only wipes the data, when going to wipe the cache it pops up with no command and the android laying on his back with a red triangle it does not actually give an error code tried to wipe the cache by itself but can not do that
could i root the other phone i have access to make a rom backup and them flash it using the stock recovery? can just rename it update.zip?
ericos123 said:
it only wipes the data, when going to wipe the cache it pops up with no command and the android laying on his back with a red triangle it does not actually give an error code tried to wipe the cache by itself but can not do that
could i root the other phone i have access to make a rom backup and them flash it using the stock recovery? can just rename it update.zip?
Click to expand...
Click to collapse
Unfortunately that won't work, the flash will fail. The stock recovery can't accept any packages that aren't signed by Samsung. If we had an unlocked bootloader, we could have a custom recovery, and ergo, the ability to install custom packages, but at the moment, there's no purpose for recovery aside from performing a factory reset .
On that note, if your cache is failing to wipe just by hitting factory reset, try wiping it using the separate option, but it looks like your device is currently out for the count regardless. Thems the breaks, sorry
breakingspell said:
Unfortunately that won't work, the flash will fail. The stock recovery can't accept any packages that aren't signed by Samsung. If we had an unlocked bootloader, we could have a custom recovery, and ergo, the ability to install custom packages, but at the moment, there's no purpose for recovery aside from performing a factory reset .
On that note, if your cache is failing to wipe just by hitting factory reset, try wiping it using the separate option, but it looks like your device is currently out for the count regardless. Thems the breaks, sorry
Click to expand...
Click to collapse
tried wiping just the cache and it starts to wipe says error and the phone reboots but stays on a blank screen
ericos123 said:
tried wiping just the cache and it starts to wipe says error and the phone reboots but stays on a blank screen
Click to expand...
Click to collapse
So it's surely a problem with your /system directory. Just keep posted until we have a solution, I'm sure you're not the only one with a shiny $200 paperweight
breakingspell said:
So it's surely a problem with your /system directory. Just keep posted until we have a solution, I'm sure you're not the only one with a shiny $200 paperweight
Click to expand...
Click to collapse
so frustrating now no cell phone ..... ohhh well it will take a bit of time but at least its only soft bricked
ericos123 said:
so frustrating now no cell phone ..... ohhh well it will take a bit of time but at least its only soft bricked
Click to expand...
Click to collapse
Surely you've got a backup phone? I never get rid of my old phones, in case my daily driver gets lost or stolen, I have a Galaxy Note and a Nexus S (my last two phones) to substitute
breakingspell said:
Surely you've got a backup phone? I never get rid of my old phones, in case my daily driver gets lost or stolen, I have a Galaxy Note and a Nexus S (my last two phones) to substitute
Click to expand...
Click to collapse
i can use the gf's old phone but when i got this i gave my old cell to my mom hers was ancient, how long did it take them to get roms working on the international version of the S4?...... also i was reading the I337 and I337m are identical is this true? because if it is samsung released the kernel source
ericos123 said:
i can use the gf's old phone but when i got this i gave my old cell to my mom hers was ancient, how long did it take them to get roms working on the international version of the S4....... also i was reading the I337 and I337m are identical is this true? because if it is samsung released the kernel source
Click to expand...
Click to collapse
Roms were available almost right away due to the unlocked bootloader of the GT-i9500/5, but At&t and Verizon decided that they want to rile some people up.
As for the i337m, it's the Virgin mobile version. While it contains the same processor and chipset, the bootloaders are different, and thus, flashing anything for the i337m would screw the device up even more
breakingspell said:
Roms were available almost right away due to the unlocked bootloader of the GT-i9500/5, but At&t and Verizon decided that they want to rile some people up.
As for the i337m, it's the Virgin mobile version. While it contains the same processor and chipset, the bootloaders are different, and thus, flashing anything for the i337m would screw the device up even more
Click to expand...
Click to collapse
i thin i know what the issue is with the phone it was the build.prop when i was playing with it on reboot things got wonky..... i did save a backup on the device, is there anyway i can adb into the phone pull that backup and replace the modded file with the original?
Does factory reset unroot the phone? I'm thinking of returning it. Just so much lag for me.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
silkshocker said:
Does factory reset unroot the phone? I'm thinking of returning it. Just so much lag for me.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
No it does not
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
silkshocker said:
Does factory reset unroot the phone? I'm thinking of returning it. Just so much lag for me.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
This haha...gotta love when new devices come out
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
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.