Database Info

What Did I Do Wrong?

Ok so I have Vahalla Final flashed through Odin as my first ROM on this phone. Everything has been great for a few days and I flashed the lighting tweak today with no issues. Just a little while ago I made a backup and flashed the Linda voices and the Ki3 modem bc I saw where the KJ6 didn't allow long text messages. When I flashed the modem some blue words popped up really zoomed in on another screen then it was done. The phone was laggy so i tried to delete everything and restore like I had done numerous times on old phone.
I did a factory reset then cache then tried to format system. These are all steps i used to successfully take on other phone. It won't let me format the system though. Says: "format_volume failed to mount "/system" error formatting system!"
Where did I go wrong? Am I supposed to do some more wacky things on this phone for a restore? Everything else on it seems to take 20 more steps

aburn95 said:
Ok so I have Vahalla Final flashed through Odin as my first ROM on this phone. Everything has been great for a few days and I flashed the lighting tweak today with no issues. Just a little while ago I made a backup and flashed the Linda voices and the Ki3 modem bc I saw where the KJ6 didn't allow long text messages. When I flashed the modem some blue words popped up really zoomed in on another screen then it was done. The phone was laggy so i tried to delete everything and restore like I had done numerous times on old phone.
I did a factory reset then cache then tried to format system. These are all steps i used to successfully take on other phone. It won't let me format the system though. Says: "format_volume failed to mount "/system" error formatting system!"
Where did I go wrong? Am I supposed to do some more wacky things on this phone for a restore? Everything else on it seems to take 20 more steps
Click to expand...
Click to collapse
CWM versions prior to those in bhndven's Slightly Modified Stock kernels have a problem with mounting/unmouting the /system partition in GB. I believe you can backup and restore user data, but nothing on the /system partition.
Flashing the KI3 modem shouldn't have had an effect like you're describing, though. I can't say I've had an issue like that at all or heard of people having that issue after flashing the modem.

stephen_w said:
CWM versions prior to those in bhndven's Slightly Modified Stock kernels have a problem with mounting/unmouting the /system partition in GB. I believe you can backup and restore user data, but nothing on the /system partition.
Flashing the KI3 modem shouldn't have had an effect like you're describing, though. I can't say I've had an issue like that at all or heard of people having that issue after flashing the modem.
Click to expand...
Click to collapse
So everything should run fine after trying the actual restore of my backup even though i couldn't format the system? I have a backup but don't want to restore over data that wasn't deleted or whatever. If that's possible.

How the hell do i know which modem to use anyways? There's like 10 to choose from

Uh yeah I forget it tries to format system anyways when restoring... and it couldn't. So what do i do? Re-flash the GB starter pack way through Odin?

aburn95 said:
Uh yeah I forget it tries to format system anyways when restoring... and it couldn't. So what do i do? Re-flash the GB starter pack way through Odin?
Click to expand...
Click to collapse
As for the modem, I'm using KI3 on mine. You already did a factory reset so you should be able to just re-flash Valhalla.

Trying now. Does Vahalla automatically change all the mounts that the other roms require changing before flashing?

aburn95 said:
Trying now. Does Vahalla automatically change all the mounts that the other roms require changing before flashing?
Click to expand...
Click to collapse
I'm not sure about that one. Definitely go check the original Valhalla post to make sure you don't have to set the mounts.

Guess you don't have too. I'm using it now. thanks for the help

aburn95 said:
Guess you don't have too. I'm using it now. thanks for the help
Click to expand...
Click to collapse
No worries. Good luck

Hey I still have an issue. I reflashed Vahalla through CWM and it was fine at first all the way through setting everything up like it was before. Ran smooth. I went to the market this morning and checked for updates and Google Search, Maps and Superuser updated. Phone started acting really laggy again. Scrolls really slow, pulls up GO Launcher menu slowly, etc.
It seems to me that the re flash installed over the existing data that was left on the phone since i couldn't format my system.
My new question is, what's the best way to re do everything including formatting the system if I can't format through CWM? If I flash through Odin does that format everything? Or am I better of just going through the whole GB Starter Pack process again?? Or will that even work now since i've already done it?

aburn95 said:
Hey I still have an issue. I reflashed Vahalla through CWM and it was fine at first all the way through setting everything up like it was before. Ran smooth. I went to the market this morning and checked for updates and Google Search, Maps and Superuser updated. Phone started acting really laggy again. Scrolls really slow, pulls up GO Launcher menu slowly, etc.
It seems to me that the re flash installed over the existing data that was left on the phone since i couldn't format my system.
My new question is, what's the best way to re do everything including formatting the system if I can't format through CWM? If I flash through Odin does that format everything? Or am I better of just going through the whole GB Starter Pack process again?? Or will that even work now since i've already done it?
Click to expand...
Click to collapse
Did you restore your previous apps are do fresh installs?

Restored w titanium..... ugh.. Flashing a new zip doesn't wipe anything right? Just installs over whats already there right?

aburn95 said:
Restored w titanium..... ugh.. Flashing a new zip doesn't wipe anything right? Just installs over whats already there right?
Click to expand...
Click to collapse
If you flashed and "it was fine at first all the way through setting everything up"...
try reflashing as you did before. Do fresh installs on as much as you can ONE AT A TIME. And then restore ONE AT A TIME what you can't do fresh installs on. It sounds like one of your backups is not agreeing with the system. Install/Restore ONE AT A TIME and play with phone between each to see if you can determine which backup your system is not agreeing with.
Did that make sense??
EDIT: And make sure to wipe dalvik cache and cache partition before you reflash as is always recommended.

stephen_w said:
No worries. Good luck
Click to expand...
Click to collapse
lumin30 said:
If you flashed and "it was fine at first all the way through setting everything up"...
try reflashing as you did before. Do fresh installs on as much as you can ONE AT A TIME. And then restore ONE AT A TIME what you can't do fresh installs on. It sounds like one of your backups is not agreeing with the system. Install/Restore ONE AT A TIME and play with phone between each to see if you can determine which on your system is not agreeing with.
Did that make sense??
EDIT: And make sure to wipe dalvik cache and cache partition before you reflash as is always recommended.
Click to expand...
Click to collapse
Yeah it makes sense thanks. I will do this despite how impatient I am (see where that got me). I'm just got spoiled on another phone that was way way easier to work with. Weren't as many options to screw up either.
Any suggestions on how I can get my system to format for future reference?

I feel like it's Go Launcher for some reason. In cased you missed it though, I didn't start having lag issues until I flashed the Ki3 modem and linda voices one after another. I have a good backup but I can't format system to restore it.

aburn95 said:
Yeah it makes sense thanks. I will do this despite how impatient I am (see where that got me). I'm just got spoiled on another phone that was way way easier to work with. Weren't as many options to screw up either.
Any suggestions on how I can get my system to format for future reference?
Click to expand...
Click to collapse
I have never formatted my system nor read anybody wanting/needing to format their system. A factory reset is what people use to clean the gremlins along with wiping dalvik cache and cache partition. Bhundven has recommended flashing the same rom twice in a row I believe to help make sure all installs correctly (I think he was talking about bootloaders when he recommended that).
But a factory reset is what I think you are trying to accomplish with formatting your system.
---------- Post added at 01:07 PM ---------- Previous post was at 01:04 PM ----------
aburn95 said:
I feel like it's Go Launcher for some reason. In cased you missed it though, I didn't start having lag issues until I flashed the Ki3 modem and linda voices one after another. I have a good backup but I can't format system to restore it.
Click to expand...
Click to collapse
I use GoLauncher on Vahalla Black with no problems. I think it has to do with your backup... not the app itself.

I wiped caches, did factory reset, tired to format system again with no luck and accidentally restarted before re-flashing Vahalla. Which, I guess I didn't really need to do anyways if it's an App causing the issue. I guess the factory reset would be enough. Smooth again so i will try some fresh reinstalls now. Thanks for the noob patience

lumin30 said:
I have never formatted my system nor read anybody wanting/needing to format their system. A factory reset is what people use to clean the gremlins along with wiping dalvik cache and cache partition. Bhundven has recommended flashing the same rom twice in a row I believe to help make sure all installs correctly (I think he was talking about bootloaders when he recommended that).
But a factory reset is what I think you are trying to accomplish with formatting your system.
---------- Post added at 01:07 PM ---------- Previous post was at 01:04 PM ----------
I use GoLauncher on Vahalla Black with no problems. I think it has to do with your backup... not the app itself.
Click to expand...
Click to collapse
Ok cool. In another phones forum a system wipe is actually suggested a lot. I think... I did it every time on the G2x before installing any new roms or backups. I wasn't doing it at first but started after someone suggested it. But yeah I think the factoy reset is enough. Seems to be enough so far.

aburn95 said:
I wiped caches, did factory reset, tired to format system again with no luck and accidentally restarted before re-flashing Vahalla. Which, I guess I didn't really need to do anyways if it's an App causing the issue. I guess the factory reset would be enough. Smooth again so i will try some fresh reinstalls now. Thanks for the noob patience
Click to expand...
Click to collapse
I am a noob too. No worries. Vahalla Black is solid. Backups are tricky. Fresh installs are the way to go.

[Q] Resetting device encryption

Hello, I am in a bit of a jam and am trying to find the best way out.
My device is encrypted using the native Android feature. I have Lean Kernel and CleanROM on the device. So it is rooted/unlocked. I was trying to clean the device further by uninstalling some useless apps with Titanium Backup. Turns out I messed up on something..
When the phone boots to the encrypted device screen, the keyboard doesn't show up! I am not able to get into the phone to do anything!
I have the latest CWM recovery installed. I tried a factory reset and such, but it says it fails to mount the internal SD card. /:
Anyone know how I can fix this and flash a new CleanROM? Data wiping is not a problem for me, but CWM refuses to mount the SD card to do it..
Any advice? I am relatively new to the Android scene, so try not to make things too complicated.

Odin?
EatonZ said:
Hello, I am in a bit of a jam and am trying to find the best way out.
My device is encrypted using the native Android feature. I have Lean Kernel and CleanROM on the device. So it is rooted/unlocked. I was trying to clean the device further by uninstalling some useless apps with Titanium Backup. Turns out I messed up on something..
When the phone boots to the encrypted device screen, the keyboard doesn't show up! I am not able to get into the phone to do anything!
I have the latest CWM recovery installed. I tried a factory reset and such, but it says it fails to mount the internal SD card. /:
Anyone know how I can fix this and flash a new CleanROM? Data wiping is not a problem for me, but CWM refuses to mount the SD card to do it..
Any advice? I am relatively new to the Android scene, so try not to make things too complicated.
Click to expand...
Click to collapse
This probably wouldn't work, but have you tried reflashing with Odin?

budzylikessoup said:
This probably wouldn't work, but have you tried reflashing with Odin?
Click to expand...
Click to collapse
I am looking at this thread:
http://forum.xda-developers.com/showthread.php?t=1984436
I am downloading the very first package. Since that seems to wipe everything, which is what I want at this point.
Will flashing that work?

I'm not sure if it will work, as I don't encrypt my device. What it will do is wipe your system, data, etc. partitions, but it won't touch your internal SD. This will probably be fine; it will install a keyboard and you should be able to enter your password, that is, if it can flash the ROM properly.

flanks vidsguir
budzylikessoup said:
I'm not sure if it will work, as I don't encrypt my device. What it will do is wipe your system, data, etc. partitions, but it won't touch your internal SD. This will probably be fine; it will install a keyboard and you should be able to enter your password, that is, if it can flash the ROM properly.
Click to expand...
Click to collapse
I'm still trying to understand how Android storage works, so I may sound like a noob here haha..
All I have is an internal SD card. I don't have an external one or anything. Are system, data located on another internal flash chip or something? If they are on the internal SD, I would imagine everything would be formatted and reset once this is flashed.

Sorry, I read the linked post wrong...So this will wipe everything, system, data, and internal SD.
As for the difference, the system and data are different partitions than the internal SD.. so normally when you factory reset in CWM, it just wipes the data, not your internal SD or system. What this means is that it won't touch some files, like ones you download from the internet, but it will get rid of all of your apps and appdata, as you know, and these are stored in the data partition.

I got it sorted. Thanks for the help.

Glad I could help!

EatonZ said:
I am looking at this thread:
http://forum.xda-developers.com/showthread.php?t=1984436
I am downloading the very first package. Since that seems to wipe everything, which is what I want at this point.
Will flashing that work?
Click to expand...
Click to collapse
Just wanna say this thread was a lifesaver, and I'll just leave my experience here for fellow noobs, like myself, stumbling into this issue.
I CMod'd my S3 with Clockwork (following very detailed instructions) and tried out encryption (knowing ahead of time that a factory reset would be in order if I didn't like it). As you all know Clockwork has trouble mounting the encrypted /sdcard/ directory, and won't do the factory reset. I was afraid that since Clockwork couldn't deal with the encrypted data, so too might Odin, leading to the risk of bricking. This thread gave me enough courage to give it a go. Following the above linked instructions solved the problem. Odin had no problem wiping and writing over the encrypted data. after I was back to stock I ran through installing Clockwork and CMod again. And just like that, the problem's fixed.
Thanks a bunch everyone!
EDIT:
I just got a response on twitter from a friend who ran into the same issue with clockwork. According to him, apparently TWRP doesn't have this flaw. My phone's working now and I don't want to monkey around with it anymore, but maybe a more experienced user out there could comment on/confirm this, and maybe add the info to the tutorials (if it's correct).
Thanks again!

SpoonlessCorey said:
Just wanna say this post was a lifesaver, and I'll just leave my experience here for fellow noobs, like myself, stumbling into this issue.
I CMod'd my S3 with Clockwork (following very detailed instructions) and tried out encryption (knowing ahead of time that a factory reset would be in order if I didn't like it). As you all know Clockwork has trouble mounting the encrypted /sdcard/ directory, and won't do the factory reset. I was afraid that since Clockwork couldn't deal with the encrypted data, so too might Odin, leading to the risk of bricking. This thread gave me enough courage to give it a go. Following the above linked instructions solved the problem. Odin had no problem wiping and writing over the encrypted data. after I was back to stock I ran through installing Clockwork and CMod again. And just like that, the problem's fixed.
Thanks a bunch everyone!
Click to expand...
Click to collapse
Yeah, I was worried I might have created a $200 paper-weight!
I'm glad that my question ended up helping you as well!:good:

[Q] Getting bsod after reboot on Liquid Smooth

Hi. I recently installed Liquid Smooth (Unofficial) 4.3 onto my Skyrocket. Since install, if I reboot the phone it will get the ever dreaded Black Screen Of Death. The only way I've found to fix this is to clear the data partition in my recovery (TWRP updated to most recent version) and then reflash the ROM and the gapps. Any ideas on how to keep the BSOD from happening again? I've tried everything I can think of. I tried just wiping the dalvek, cache and system and then flashing the ROM again. As I said, the only way I can find to "fix" it is to wipe the data partition and then flash the ROM and gapps again. I would have asked in that specific thread, but since I am a new member I can't until I reach the 10 post requirement.

CoolWolf22 said:
Hi. I recently installed Liquid Smooth (Unofficial) 4.3 onto my Skyrocket. Since install, if I reboot the phone it will get the ever dreaded Black Screen Of Death. The only way I've found to fix this is to clear the data partition in my recovery (TWRP updated to most recent version) and then reflash the ROM and the gapps. Any ideas on how to keep the BSOD from happening again? I've tried everything I can think of. I tried just wiping the dalvek, cache and system and then flashing the ROM again. As I said, the only way I can find to "fix" it is to wipe the data partition and then flash the ROM and gapps again. I would have asked in that specific thread, but since I am a new member I can't until I reach the 10 post requirement.
Click to expand...
Click to collapse
Try using the latest CWM recovery. Some people are reporting having better luck using this for the BSOD issue.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

jondroid2 said:
Try using the latest CWM recovery. Some people are reporting having better luck using this for the BSOD issue.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
I will try this and will get back to you. I'd still like to know what's causing the issue in the first place. I've been flashing on Samsung devices since the original Epic 4G launched. Never have had any issues like this before.

CoolWolf22 said:
I will try this and will get back to you. I'd still like to know what's causing the issue in the first place. I've been flashing on Samsung devices since the original Epic 4G launched. Never have had any issues like this before.
Click to expand...
Click to collapse
I've had the same issue and switching to cwm solved it. It's a real pita though as a prefer twrp and my nandroids are twrp. I switch back and forth between them.

jd1639 said:
I've had the same issue and switching to cwm solved it. It's a real pita though as a prefer twrp and my nandroids are twrp. I switch back and forth between them.
Click to expand...
Click to collapse
CWM fixed my BSOD. I've had 2 successful reboots so far. I too preferred TWRP over CWM. But oh well. I am in contact with the devs for TWRP to see if they are aware of the issue and can issue a fix for it.

CoolWolf22 said:
CWM fixed my BSOD. I've had 2 successful reboots so far. I too preferred TWRP over CWM. But oh well. I am in contact with the devs for TWRP to see if they are aware of the issue and can issue a fix for it.
Click to expand...
Click to collapse
There's an build of TWRP 2.7 that I've been using and haven't had any issues with. The only thing "wrong" with it is it only reads internal storage. Here's the Link

theesotericone said:
There's an build of TWRP 2.7 that I've been using and haven't had any issues with. The only thing "wrong" with it is it only reads internal storage. Here's the Link
Click to expand...
Click to collapse
Thanks. I'll download that and keep it in reserve for future reference.

[Q] Any way to recover lost EFS?

Ok, so I probably know the answer to this already :crying:
Brief story - stock rooted ROM with custom kernel. Made backup with TWRP. Flashed stock boot,img and system.img in fastboot, flashed downloaded update from 4.4 -> 4.4.2 in recovery. Wiped cache and dalvik - started but recovery locked up. Had to hold power to reboot phone. Booted fine but no network, no IMEI, no baseband.
And no I don't have and EFS backup
I take it the phone is now buggered.
Is there anything I can do to fix this??
Appreciate anything that might help this.

Cheesy Wotsit said:
Ok, so I probably know the answer to this already :crying:
Brief story - stock rooted ROM with custom kernel. Made backup with TWRP. Flashed stock boot,img and system.img in fastboot, flashed downloaded update from 4.4 -> 4.4.2 in recovery. Wiped cache and dalvik - started but recovery locked up. Had to hold power to reboot phone. Booted fine but no network, no IMEI, no baseband.
And no I don't have and EFS backup
I take it the phone is now buggered.
Is there anything I can do to fix this??
Appreciate anything that might help this.
Click to expand...
Click to collapse
The same thing happened to me. Flash the latest version of TWRP, wipe your cache again, and your phone will be back to normal.

not true for all you may end up having to RMA I had my efs backup it still didn't fix it sorry to be the bearer of bad news but they make it sound like bringing it back is 100% but in some cases that's not true
Sent from my Nexus 4 using xda app-developers app

ddloco said:
not true for all you may end up having to RMA I had my efs backup it still didn't fix it sorry to be the bearer of bad news but they make it sound like bringing it back is 100% but in some cases that's not true
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
In his case, if he just does what I said to do he'll be fine. He didn't lose his EFS, he rebooted in the middle of a cache wipe and his partitions got messed up. Updating TWRP and wiping the cache again will set everything straight. This is a fairly common issue with older versions of TWRP.

_MetalHead_ said:
In his case, if he just does what I said to do he'll be fine. He didn't lose his EFS, he rebooted in the middle of a cache wipe and his partitions got messed up. Updating TWRP and wiping the cache again will set everything straight. This is a fairly common issue with older versions of TWRP.
Click to expand...
Click to collapse
I'm just saying the same thing happens to me and nothing that's suggested fixed it that's why I say its not 100% me and another guy both had the same problem and the only way was to RMA I also had my efs but even after doing everything from going back to stock updateubg twrp and reflashing my esf backup my phone would not correct its self so I'm not saying that this method doesn't work for some people but for me and another used it was a no go

So why are you guys still using twrp if it is causing issues?
Just use cwm instead!
Sent from my Nexus 5 using Tapatalk

Elisha said:
So why are you guys still using twrp if it is causing issues?
Just use cwm instead!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
because the majority dont have any problems.
and people, take precautionary measures and back up your efs partition, its the first thing i did as soon as i had a custom recovery. it takes 2 seconds. and store it somewhere OTHER then your phones internal storage, like on a comp or dropbox

TheAtheistOtaku said:
because the majority dont have any problems.
and people, take precautionary measures and back up your efs partition, its the first thing i did as soon as i had a custom recovery. it takes 2 seconds. and store it somewhere OTHER then your phones internal storage, like on a comp or dropbox
Click to expand...
Click to collapse
This is not an EFS issues. Simple matter of twrp messing up partitions.
Sent from my Nexus 5 using Tapatalk

Elisha said:
This is not an EFS issues. Simple matter of twrp messing up partitions.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i know, still doesnt hurt to be caution though

ddloco said:
I'm just saying the same thing happens to me and nothing that's suggested fixed it that's why I say its not 100% me and another guy both had the same problem and the only way was to RMA I also had my efs but even after doing everything from going back to stock updateubg twrp and reflashing my esf backup my phone would not correct its self so I'm not saying that this method doesn't work for some people but for me and another used it was a no go
Click to expand...
Click to collapse
Yeah but did it happen to you the way it happened to OP? So far every single person that I have come across who was in this boat due to a bad cache wipe in TWRP was able to fix it by updating TWRP and re-wiping the cache. It's a well known issue.

_MetalHead_ said:
Yeah but did it happen to you the way it happened to OP? So far every single person that I have come across who was in this boat due to a bad cache wipe in TWRP was able to fix it by updating TWRP and re-wiping the cache. It's a well known issue.
Click to expand...
Click to collapse
Thanks for the help guys. Got it up and running again more by accident than anything. Seems like MetalHead was correct, the partition was fine but just not readable. Unfortunately in order to get up and running again I flashed all the stock images in flasboot and did a full factory reset in the stock recovery which fixed the problem. Sounds like I could have done without the full wipe after all but at least it's all fixed now.
As for backing up the EFS, lesson learned. I had the 1st official TWRP on the phone which had no option for EFS backup like the current one. Guess what I'll be doing right now??
Anyway, happy man again and thanks to all that replied :good:

I must apologize for saying its not 100% but the truth is I had the exact same thing happen and no stock or fast boot cache fixed it I'm living proof that it works for the masses but under rare circumstances this just doesn't solve it oh man how I wish this would've fixed mine I been using a inspire 4g its killing me I feel like I jumped out of a beemer and landed in a pinto lol
Sent from my Nexus 4 using xda app-developers app

Glad that the OP got the issue resolved !
on a side note , can anyone tell me what is the safest version of TWRP there ? i.e without this cache wipse issue ( taking too long to wipe ? )

ddloco said:
I must apologize for saying its not 100% but the truth is I had the exact same thing happen and no stock or fast boot cache fixed it I'm living proof that it works for the masses but under rare circumstances this just doesn't solve it oh man how I wish this would've fixed mine I been using a inspire 4g its killing me I feel like I jumped out of a beemer and landed in a pinto lol
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thats a bummer man. What kind of phone are you using now?
Lowresolution said:
Glad that the OP got the issue resolved !
on a side note , can anyone tell me what is the safest version of TWRP there ? i.e without this cache wipse issue ( taking too long to wipe ? )
Click to expand...
Click to collapse
I believe 2.6.3.4 is the latest version. That's the one I'm on, works just fine.
Sent from my Nexus 5 using XDA Premium 4 mobile app

_MetalHead_ said:
Thats a bummer man. What kind of phone are you using now?
I believe 2.6.3.4 is the latest version. That's the one I'm on, works just fine.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Got it , thanks mate Just upgraded my version of TWRP .

the nexus 4 is my phone I gave to my wife now that its hers I'm lucky to pick it up just to hop on xda but when its her Facebook time she hurrie up and kick me off lol the phone I'm using is an HTC inspire 4g it sucks
Sent from my Nexus 4 using xda app-developers app

[SOLVED] Storage Space Running Out - 8GB Free

I just rooted my phone, restarted made sure it was working (not the first time I've rooted), then I installed a few zips, restarted my phone a couple times and it was all working fine. I then made a nandroid backup with TWRP, and restarted my phone and it's suddenly running really slow, and I have the constant message saying "Storage Space running out" even though I have over 8GB free. I even just restored my phone to this backup, but as I expected, same error. Any ideas?:crying:

Jimmeeehhhh said:
I just rooted my phone, restarted made sure it was working (not the first time I've rooted), then I installed a few zips, restarted my phone a couple times and it was all working fine. I then made a nandroid backup with TWRP, and restarted my phone and it's suddenly running really slow, and I have the constant message saying "Storage Space running out" even though I have over 8GB free. I even just restored my phone to this backup, but as I expected, same error. Any ideas?:crying:
Click to expand...
Click to collapse
Did you wipe /cache in TWRP?

beekay201 said:
Did you wipe /cache in TWRP?
Click to expand...
Click to collapse
Yup, had no effect at all.. I resorted to flashing the factory image and re-rooting and installing zips. Still interested in a fix for this though, on the small chance it happens again[emoji16]

Jimmeeehhhh said:
Yup, had no effect at all.. I resorted to flashing the factory image and re-rooting and installing zips. Still interested in a fix for this though, on the small chance it happens again[emoji16]
Click to expand...
Click to collapse
The next step I was going to suggest was to flash /system again. Some people posted wiping /cache was enough for them, but others had to reflash /system.

beekay201 said:
The next step I was going to suggest was to flash /system again. Some people posted wiping /cache was enough for them, but others had to reflash /system.
Click to expand...
Click to collapse
Ah that makes sense now that I think about it.. I flashed the entire image (boot, recovery etc.) but should have just done system, would have been quicker. Easy solution right there

Jimmeeehhhh said:
Ah that makes sense now that I think about it.. I flashed the entire image (boot, recovery etc.) but should have just done system, would have been quicker. Easy solution right there
Click to expand...
Click to collapse
Yep, glad it worked.
Could you please just add "[SOLVED]" to the thread title? Thanks