Database Users

[Q] Semi-Brick?

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.

[Q] Stuck on the X logo, pls help...

Guys, its my first time to try to do some modding on Android and unfortunately Im stuck with a problem.
I did a good install with drivers, unlocked it successfully then installed TWRP 2.5 mako. after installing TWRP, I locked my phone again. Then I went to TWRP recovery then made a backup. After backup was complete, I was to reboot but was prompted something like "my device seemed not to be rooted. Do you like to install SU?" But I choose "dot not install" instead. Then it rebooted. Then the Google logo showed up longer than usual, then the X logo and was stuck on it from there. I waited till morning thinkin the phone might be configuring itself for the first time after all the things I have done but to my surprise, when I got up this morning, still on the X logo! I then tried to reset by pressing the power button for some seconds. It rebooted but same thing happens, google logo showed up for a longer time than usual then stuck again on the X logo. Then I tried fastboot, it did went to fastboot. Tried to reset bootloader, tried using TWRP reset system and reboot but still no success.
What do you think happenede and what did I do wrong? What should I do now to fix this.
Im really nervous now thinking I might have bricked my phone. Im a newbie so I really have no idea..
Hope you guys could help. Thanks!

Try clearing cache in twrp if that doesn't work flash the stock recovery and clear cache from there.
Sent from my Xoom using Tapatalk 4 Beta

El Daddy said:
Try clearing cache in twrp if that doesn't work flash the stock recovery and clear cache from there.
Sent from my Xoom using Tapatalk 4 Beta
Click to expand...
Click to collapse
thanks for the reply. You mean using "Wipe" in twrp right? After choosing wipe, i was prompted with 2 button options and a swipe option. 1 button was "advance wipe", the other was "format data" and the swipe option was "swipe to factory reset" what should I use? It says "factory reset wipes data, cache and dalvik (not including internal storage). Most of the time this is the only wipe that you need." You mentioned to try to clear cache, do you mean to say the data and dalvic as well? If so then should I choose the swip option which is "factory reset"?
Thanks again..

Nope just the cache. This phone sometimes has issues when wiping data/cache from the bootloader. (Which is what happens when you unlock the bootloader) The way to fix the bootloop problem is to wipe cache using the stock recovery.
Sent from my Nexus 4 using Tapatalk 4 Beta

vinz_bangiz said:
thanks for the reply. You mean using "Wipe" in twrp right? After choosing wipe, i was prompted with 2 button options and a swipe option. 1 button was "advance wipe", the other was "format data" and the swipe option was "swipe to factory reset" what should I use? It says "factory reset wipes data, cache and dalvik (not including internal storage). Most of the time this is the only wipe that you need." You mentioned to try to clear cache, do you mean to say the data and dalvic as well? If so then should I choose the swip option which is "factory reset"?
Thanks again..
Click to expand...
Click to collapse
Try factory reset first if that doesn't work you may have to sideload a ROM onto it. The same thing happened to me a couple of times. Sometimes a factory reset worked but most of the time I ended up sideloading.

El Daddy said:
Nope just the cache. This phone sometimes has issues when wiping data/cache from the bootloader. (Which is what happens when you unlock the bootloader) The way to fix the bootloop problem is to wipe cache using the stock recovery.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
so just to clear, i would not try anymore to clear cache via twrp or should i try it first before flashing stock recovery and clearing it from there? To be honest, im quite careful now in every move ill make coz Im afraid i might make matters worst.
Pls advice. thanks for your patience.
by the way, in case I would really need to flash stock rom, how to do it and where to get right stock recovery?
Thanks again!

All the info to flash recovery and resources are here: http://forum.xda-developers.com/showthread.php?t=2010312
Basically, download the stock image. Extract the folder down til you see the recovery.img.
Then using fastboot type the command:
fastboot flash recovery recovery.img
Then boot into recovery and clear cache.
Sent from my Nexus 4 using Tapatalk 4 Beta

El Daddy said:
All the info to flash recovery and resources are here: http://forum.xda-developers.com/showthread.php?t=2010312
Basically, download the stock image. Extract the folder down til you see the recovery.img.
Then using fastboot type the command:
fastboot flash recovery recovery.img
Then boot into recovery and clear cache.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
oh ok. I understand now. Sorry, its my first time so im not that familiar yet on how things go. I did a lot of reading and browsing as well but xda sure is very overwhelming in information..
P41ll37 is suggesting sideload which I also am not yet familiar with. i tried to search it but most of it led to using a toolkit. I mentioned in another post that I made that I wanted to learn instead of jsut being able to fix my problems. Could you advice me as well or lead me to the right link to know how to do this.
Thanks!

Guys! before trying anything else, I tried to clear cache using TWRP and choosing advance then marked the delvic cache and cache then restarted system, was asked if I wanted to installed SU, this time I choose yes, it rebooted by itself, but still nothing happened. same stuck on X logo problem.
But then, I tried wipe again in TWRP this time choosing factory reset, then restarted system again, google logo did stay a longer but not as long as before, then X logo appeared and stayed there like forever but after a minute or so.. FINALLY! it went to the Welcome screen asking for what language I should use.
So i guess this means it is fixed already?
Also, since I choose to install SU a while ago, does this mean my phone is already rooted as well? How would I know? Well, maybe installing a root app like titanium backup should tell right?
If so, then looks like I have advanced already on my step by step learning to mod my phone. I was only in the unlocking and custom recovery part last night. Tonight was supposed to be rooting and putting custom rom but I was still trying to learn thru our forum guides.
I wana thank you guys for your time, kind help and suggestions. This was my first experience in modding and right away I was faced with a problem to be solved. This is good anyway as a learning experience.
One last thing, could you guys tell what really happend, how I went into this kind of problem or what caused it? As I mentioned, I was noping not only to mod or fix my phone but rather really learn on how to do or fix things. Like a difference between a toolkit and manually doing it. Right?
Thanks again guys!

vinz_bangiz said:
Guys! before trying anything else, I tried to clear cache using TWRP and choosing advance then marked the delvic cache and cache then restarted system, was asked if I wanted to installed SU, this time I choose yes, it rebooted by itself, but still nothing happened. same stuck on X logo problem.
But then, I tried wipe again in TWRP this time choosing factory reset, then restarted system again, google logo did stay a longer but not as long as before, then X logo appeared and stayed there like forever but after a minute or so.. FINALLY! it went to the Welcome screen asking for what language I should use.
So i guess this means it is fixed already?
Also, since I choose to install SU a while ago, does this mean my phone is already rooted as well? How would I know? Well, maybe installing a root app like titanium backup should tell right?
If so, then looks like I have advanced already on my step by step learning to mod my phone. I was only in the unlocking and custom recovery part last night. Tonight was supposed to be rooting and putting custom rom but I was still trying to learn thru our forum guides.
I wana thank you guys for your time, kind help and suggestions. This was my first experience in modding and right away I was faced with a problem to be solved. This is good anyway as a learning experience.
One last thing, could you guys tell what really happend, how I went into this kind of problem or what caused it? As I mentioned, I was noping not only to mod or fix my phone but rather really learn on how to do or fix things. Like a difference between a toolkit and manually doing it. Right?
Thanks again guys!
Click to expand...
Click to collapse
basically whenever you flash a factory image (and perhaps even some custom ROMS) you have to do a factory reset for really two reasons. The first reason is to get it out of bootloop. For some reason whenever the phone is flashed it will go on endless loop until you boot into recovery and factory reset. Also, you will need to check your storage after you flash. The phone has a tendency to lose half its memory after a flash. Check storage and if at half memory do another factory wipe and you should be good to go.
The easiest way I do it is to simply reboot the phone after flashing the files, I then allow the phone to reboot and get stuck on the bootloop. I then hard shut the phone off by holding down power. Once shut down boot into fastboot and then fastboot boot TWRP recovery where I then wipe the phone. After it reboots it will stick on the X logo for a few minutes and get to the welcome screen. From there log in and get it set up again.
Also, this is where you should check storage. I notice that more often than not mine still is only half storage (despite my TWRP wipe), so I use the phone to factory reset and then when it reboots the phone has full storage again.
Im sure there is probably someone out there with a better system but that is how I do it.

thos25 said:
basically whenever you flash a factory image (and perhaps even some custom ROMS) you have to do a factory reset for really two reasons. The first reason is to get it out of bootloop. For some reason whenever the phone is flashed it will go on endless loop until you boot into recovery and factory reset. Also, you will need to check your storage after you flash. The phone has a tendency to lose half its memory after a flash. Check storage and if at half memory do another factory wipe and you should be good to go.
The easiest way I do it is to simply reboot the phone after flashing the files, I then allow the phone to reboot and get stuck on the bootloop. I then hard shut the phone off by holding down power. Once shut down boot into fastboot and then fastboot boot TWRP recovery where I then wipe the phone. After it reboots it will stick on the X logo for a few minutes and get to the welcome screen. From there log in and get it set up again.
Also, this is where you should check storage. I notice that more often than not mine still is only half storage (despite my TWRP wipe), so I use the phone to factory reset and then when it reboots the phone has full storage again.
Im sure there is probably someone out there with a better system but that is how I do it.
Click to expand...
Click to collapse
Thanks for the reply. really very informative!
The easiest way I do it is to simply reboot the phone after flashing the files, I then allow the phone to reboot and get stuck on the bootloop. I then hard shut the phone off by holding down power. Once shut down boot into fastboot and then fastboot boot TWRP recovery where I then wipe the phone. After it reboots it will stick on the X logo for a few minutes and get to the welcome screen. From there log in and get it set up again.
Click to expand...
Click to collapse
Actually, this is exactly what I did and the one that solved my problem.
Also, this is where you should check storage. I notice that more often than not mine still is only half storage (despite my TWRP wipe), so I use the phone to factory reset and then when it reboots the phone has full storage again.
Click to expand...
Click to collapse
About this, are you referring to the remaining free storage or that actual usable storage of the phone. To my knowledge, a new 16gb nex4 would actually give you about 12+gb of free usuable space. Do you mean I should observe if this has dropped to about 6gb? or are you reffering to for example I have 5gb remaining free space before flashing and rebooting then after this I should observe if the "remaining free" space is now only around 2.5gb after rebooting it?
Looking forward to your clarification.. thanks again!

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

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

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

Same problem here....

Flash factory image

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Need FULL WIPE

Hi. I have the Galaxy S5. I updated it to the latest firmware which screwed my device. It is overheating for nothing. Many time I flashed back to stock roms but nothing's changed. I suspect there is still left in the device from the latest firmware "virus". I want to do full wipe. I heard wipe cache and wipe partition only delete user's data. Isn't there a way to start from FULL scratch? Thanks.

karasahin said:
Hi. I have the Galaxy S5. I updated it to the latest firmware which screwed my device. It is overheating for nothing. Many time I flashed back to stock roms but nothing's changed. I suspect there is still left in the device from the latest firmware "virus". I want to do full wipe. I heard wipe cache and wipe partition only delete user's data. Isn't there a way to start from FULL scratch? Thanks.
Click to expand...
Click to collapse
If you reflash your device and you do a full wipe from recovery, then your phones software should be like brand new. It might be a hardware issue.

Newyork! said:
If you reflash your device and you do a full wipe from recovery, then your phones software should be like brand new. It might be a hardware issue.
Click to expand...
Click to collapse
No it doesn't delete everything. Because when I downgrade to KitKat from Lollipop, the power off battery animation is still from Lollipop, just for an example. That's why there is TWRP recovery (just discovered it) which allow you to delete the Data, Cache, System and Preload partitions of your internal memory. Since I am not rooted "yet", I am looking for an alternative for it. Anyone?

karasahin said:
No it doesn't delete everything. Because when I downgrade to KitKat from Lollipop, the power off battery animation is still from Lollipop, just for an example. That's why there is TWRP recovery (just discovered it) which allow you to delete the Data, Cache, System and Preload partitions of your internal memory. Since I am not rooted "yet", I am looking for an alternative for it. Anyone?
Click to expand...
Click to collapse
Very funny.
I guess try to do a emergency upgrade with kies.

Newyork! said:
Very funny.
I guess try to do a emergency upgrade with kies.
Click to expand...
Click to collapse
What is funny exactly?
It doesn't work. There is no device listed.

karasahin said:
What is funny exactly?
It doesn't work. There is no device listed.
Click to expand...
Click to collapse
When you flash a full firmware from sammobile it should reflash everything, including custom recovery or the boot animation.

Newyork! said:
When you flash a full firmware from sammobile it should reflash everything, including custom recovery or the boot animation.
Click to expand...
Click to collapse
MAYBE it should but it doesn't in my case. I'm telling you the device has Lollipop power off battery animation while KitKat firmware is installed. There are still something left in the device. Look for the thread below:
http://forum.xda-developers.com/showthread.php?t=1983489
Why should TWRP or CMW recovery separately add System and Preload partitions options if not for a reason?

I think I have to root and lose my warranty. Damn you Samsung...

Because no OEM in their right mind is going to give people a device with a recovery capable of wiping the system partition, that's completely inane.
Sent from my LG-H631 using Tapatalk

Blu8 said:
Because no OEM in their right mind is going to give people a device with a recovery capable of wiping the system partition, that's completely inane.
Sent from my LG-H631 using Tapatalk
Click to expand...
Click to collapse
Yeah? What makes you think it is completely insane or insecure to do this? Are you saying TWRP developers (and others who put that choice to their recoveries) are stupid? Do you think they put that option just for hobby?

Jesus Christ, I'm saying giving that option to the average customer is stupid because they would delete their system partition, brick their phones and then blame the makers of the phone. Why do you think you break your warranty when you root or install custom software like TWRP?
Sent from my LG-H631 using Tapatalk

Hello,
Thread cleaned...
Some good points were made however the way comments were expressed should take a more respectful tone.
A general note to all: When you ask a question, please don't expect to agree with or like every response. Please don't look for opportunities to argue. Focus on the question asked and seek out the answer(s) that satisfies your needs.
Regards

Thank you.
Still waiting for help.

BUMP

BUMP!

BUMP

BUMP

Here is what I do so far:
Revert back to factory settings
Delete old app infos via Google
Wipe cache and full wipe via stock recovery
Flash full ROM via Odin
Root and custom recovery to wipe system, cache, dalvik, boot, simply anything can be erased
Yet nothing helped. Using KitKat 4.4.2 now and still have Lollipop animations that indicates there are datas AFTER all of those wipes. I'm absolutely furious!!!

Will my device be okay if I flash another country's stock ROM?

I can't understand this situation really: Why even after all those wipes I still end up with the Lollipop battery animation while I'm using KitKat (even very early builds)? Let me be clear: I am no against the Lollipop battery animation but it confirms some data are erase proof. And because of it, I think there is no way to get back the phone to its very roots. Is there a logical explanation for this or shall I stop trying by calling it Android's stupidity?

TWRP - Wiped Delvik Cashe and Cashe - Now stuck at Axon logo?

It's been running perfectly fine the past 24 hours, but I hadn't wiped these since adding all the new apps to my phone, so I wiped those (in advanced wipe) like I've done 100's of times before on other ROOTed phones. Now, my A7 has been sitting at the Axon logo for about 15 minutes.
It's warm/hot like it's doing something but I can't tell? I rebooted it and it did the little swoosh and animation, then back at the Axon logo again.
Has anyone else experienced a LONG wait at the Axon 7 logo after wiping those?
[EDIT]
I gave up and did a complete wipe and restored my backup from last night. I didn't wipe anything after the restore and it booted up in less than 2 minutes and seems to be working fine.

tele_jas said:
It's been running perfectly fine the past 24 hours, but I hadn't wiped these since adding all the new apps to my phone, so I wiped those (in advanced wipe) like I've done 100's of times before on other ROOTed phones. Now, my A7 has been sitting at the Axon logo for about 15 minutes.
It's warm/hot like it's doing something but I can't tell? I rebooted it and it did the little swoosh and animation, then back at the Axon logo again.
Has anyone else experienced a LONG wait at the Axon 7 logo after wiping those?
[EDIT]
I gave up and did a complete wipe and restored my backup from last night. I didn't wipe anything after the restore and it booted up in less than 2 minutes and seems to be working fine.
Click to expand...
Click to collapse
i now you just edited your OP, but here a few Note:
1- when you do a Dalvik Cache wipe , Your device will take minutes to boot (is like your done a Full Factory Reset and yes may take longer tahn 10 or 15 mins sometimes)
2- now that you know you have a perfect backup, do a extra copy and move it to your PC or SDCard or just both.

DrakenFX said:
i now you just edited your OP, but here a few Note:
1- when you do a Dalvik Cache wipe , Your device will take minutes to boot (is like your done a Full Factory Reset and yes may take longer tahn 10 or 15 mins sometimes)
2- now that you know you have a perfect backup, do a extra copy and move it to your PC or SDCard or just both.
Click to expand...
Click to collapse
I have a backup on my SD card now.....
I've been running custom ROMs for 4 years and have done this probably 2000+ times. Usually it doesn't hang at the logo that long, but instead goes to the optimizing apps screen. When it has hung, like on my Nexus 6P, it meant something screwed up and I had go back and restore a backup. But I've also come to realize that every phone is different and the Axon may have needed a few more minutes.
But, I did wipe them when I installed Xposed yesterday afternoon and it didn't hang?
There's no telling? I know this is all new right now for the A7, it'll get easier and more reliable as time goes by.

Did you use systemless root?
Sent from my 6045I using XDA Premium HD app

Recon Freak said:
Did you use systemless root?
Sent from my 6045I using XDA Premium HD app
Click to expand...
Click to collapse
I'm not sure?
I unlocked my bootloader
Flashed TWRP
Flashed SuperSU 2.65
adb command to disable system write protection
Flashed Xposed (which I know breaks systemless ROOT).

tele_jas said:
I'm not sure?
I unlocked my bootloader
Flashed TWRP
Flashed SuperSU 2.65
adb command to disable system write protection
Flashed Xposed (which I know breaks systemless ROOT).
Click to expand...
Click to collapse
Try using the latest supersu (2.74 maybe). But before you flash it go to terminal inside twrp. Once in terminal type (no quotes) "echo SYSTEMLESS=true >> /data/.supersu. Then flash the latest supersu. Upon reboot it will take longer than normal. Once rebooted open supersu app. It should tell you the binary needs updated. Update ti using the normal option. Then reboot. Supersu should be good to go. Then if you like falsh the Xposed. See if all is gtg.

Delete