Related
There has been some confusion over whether ClockworkMod Recovery actually wipes the dalvik-cache correctly. I decided to test it myself. I booted into CW recovery, fired up ADB, and mounted /data. Looking inside /data/dalvik-cache I saw a list of .dex files (the cache, of course). So I unmounted, then used the CW menu to wipe the dalvik-cache. Note, this is NOT just the "wipe cache" option on the main menu. This is a separate option under "advanced." Then I re-mounted /data and looked again . . . and the dalvik-cache directory was completely gone. Rebooting into Android and looking again, it was back (rebuilt) after a long-ish boot time (rebuilding phase), so I'm sure that at least my install of CW v2.5.0.1 is wiping the dalvik-cache just fine.
If you're still not sure, you could use ADB to wipe the cache yourself:
Code:
adb shell
mount /data
rm -rf /data/dalvik-cache/*
Then you can use the Clockwork menu to wipe everything else and flash your ROM. These three commands actually just delete everything inside the dalvik-cache directory, whereas Clockwork appears to remove the directory entirely. Doesn't really matter either way, the system will replace the directory if it gets deleted.
Feel free to replicate my results. That's how science works.
UPDATE: Just did a similar test with the "wipe data/factory reset" menu option. This actually wipes the entire /data directory, which includes the dalvik-cache, so doing a dalvik wipe would be redundant if you're doing a full data wipe anyway. Correct me if I'm wrong.
Thanks I've never had any problems with clockwork, but it seems like there has been a pox on its name since my arrival to the android/evo community.
In particular, I always wondering if I was just being overly redundant going into the advanced menu and wiping dalvik cache ON TOP of a data/cache wipe when flashing a new rom. I'm gonna trust your experiment and stop doing it!
vladthedog said:
Thanks I've never had any problems with clockwork, but it seems like there has been a pox on its name since my arrival to the android/evo community.
In particular, I always wondering if I was just being overly redundant going into the advanced menu and wiping dalvik cache ON TOP of a data/cache wipe when flashing a new rom. I'm gonna trust your experiment and stop doing it!
Click to expand...
Click to collapse
Can't argue with empty directories. The only possible catch would be if there is a dalvik-cache log or something elsewhere outside of /data, but I'm 99.7% sure just doing a "data wipe / factory reset" will wipe dalvik no problem. Still do the other "wipe cache" option as well, though.
Oh I will..I'm just lazy and if I don't have to go ALL the way into the advanced menu too wipe my dalvik I will feel a whole lot better about the world
Sent from my PC36100 using XDA App
redundancy never hurt anybody
when you clear the dalvik are you supposed to get some sort of confirmation. whenever i clear it ask me i want to and when i reply yes, it just goes back to the menu. idk if anything actually is happening. (is this what you guys are referring to?)
Yes, that's what we're talking about. Mine is the same way, but it appears to be fine. For one thing, if you do a data wipe first, the dalvik cache goes with it so there would be no real delay even if you then tried to clear it separately. It's already gone. But there should be some sort of confirmation added to the next update, IMO.
crakerjaks said:
redundancy never hurt anybody
Click to expand...
Click to collapse
I always wipe at least twice, it's cleaner. No one likes leaving any bits behind after wiping only once.
firemedic1343 said:
I always wipe at least twice, it's cleaner. No one likes leaving any bits behind after wiping only once.
Click to expand...
Click to collapse
Ah, aha, yes. Very good.
crakerjaks said:
redundancy never hurt anybody
Click to expand...
Click to collapse
redundancy never hurt anybody
TheBundo said:
redundancy never hurt anybody
Click to expand...
Click to collapse
I thought it killed the cat?
Sent from my PC36100 using XDA App
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
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!
Hey everyone.
So, as every Android I've ever had.. Sometime the device needs a reboot... The battery goes out faster then it should, stuff runs a bit slower and i reboot gives me a clean start.
Here, a reboot does not do that, everything is still open on recent apps as if i didn't reboot at all .. What is the solution for this?
One thing you can do, if you have a custom recovery installed is first, close all open apps, reboot into recovery and delete Cache and Dalvik Cache... then reboot, let it do it's thing... you're as refreshed as you can get without wiping entirely and starting over.
CJ-Wylde said:
One thing you can do, if you have a custom recovery installed is first, close all open apps, reboot into recovery and delete Cache and Dalvik Cache... then reboot, let it do it's thing... you're as refreshed as you can get without wiping entirely and starting over.
Click to expand...
Click to collapse
First of all, Thank you!
is no one else bothered by this? sigh
Caniv said:
First of all, Thank you!
is no one else bothered by this? sigh
Click to expand...
Click to collapse
I've done this method a few times... I usually once I do a full fresh new rom setup will go through and setup everything, tweak it all up nice, remove things I don't want, etc... and when I'm 100% operational... I'll go to recovery, wipe the cache and dalvik, make a nandroid backup and boot back up. I run into less problems it feels like this way.
I just swipe them all away then reboot, its a pain but since I want to use android pay its something i have to live with.
please anyone help
every time i flashing a rom it going to be too laggy even after a full wipe !
even after changing the recovery the proplem not resolved !!
No solutions. All of us have this lag problem. Maybe it has something to do with our device from production.
Try wiping the whole device 3-4 times without -rf option enabled. It works. If it isn't working the use dreamstar's recovery and wipe the device
me too have the lag issue now
---------- Post added at 08:23 PM ---------- Previous post was at 07:35 PM ----------
SupulEdirisinghe said:
Try wiping the whole device 3-4 times without -rf option enabled. It works. If it isn't working the use dreamstar's recovery and wipe the device
Click to expand...
Click to collapse
Tried wiping 3 times also used dreamstar's cwm recovery but found no use
still the device is too much laggy
until now no solution is found
ashish1989 said:
me too have the lag issue now
Tried wiping 3 times also used dreamstar's cwm recovery but found no use
still the device is too much laggy
until now no solution is found
Click to expand...
Click to collapse
Did you wiped the whole device? I meant system + data + internal + dalvik + cache.. whenever I exclude internal the lags continue..
BTW i meant dreamstar's TWRP recovery
SupulEdirisinghe said:
Did you wiped the whole device? I meant system + data + internal + dalvik + cache.. whenever I exclude internal the lags continue..
BTW i meant dreamstar's TWRP recovery
Click to expand...
Click to collapse
I m sorry I mean TWRP recovery and yes after going to advanced wipe I wiped everything excluding external sd card and flashed stock rom
Tried this many times but getting huge lags
Any suggestions????
You have to format data buddy. Instead of going to advanced wipe choose "wipe data"
Then flash Stock and then you can flash any rom afterwards. No lags guaranteed
SupulEdirisinghe said:
You have to format data buddy. Instead of going to advanced wipe choose "wipe data"
Then flash Stock and then you can flash any rom afterwards. No lags guaranteed
Click to expand...
Click to collapse
There are only three options in twrp i.e. advanced wipe, format data and swipe to factory reset
Which one to choose
My mistake I meant format data there. Choose format data. It'll take a while but does the job
SupulEdirisinghe said:
My mistake I meant format data there. Choose format data. It'll take a while but does the job
Click to expand...
Click to collapse
Ok let me try
Will reply shortly
SupulEdirisinghe said:
My mistake I meant format data there. Choose format data. It'll take a while but does the job
Click to expand...
Click to collapse
I have done format data but still getting lags
Any other solution
Now I'm facing something like that..
SupulEdirisinghe said:
Now I'm facing something like that..
Click to expand...
Click to collapse
I have done format data and after that going to advanced wipe I have done wipe system and cache
Done these steps many times but still facing lags
Guys anybody have solution for these lags
Using TWRP 3.0.0 and 3.1.1 from Dreamstar bro
ashish1989 said:
I have done format data and after that going to advanced wipe I have done wipe system and cache
Done these steps many times but still facing lags
Guys anybody have solution for these lags
Using TWRP 3.0.0 and 3.1.1 from Dreamstar bro
Click to expand...
Click to collapse
Use 3.0.1 from dreamstar..
And format data for 2-3 times and format system for 20+ times???.. keep a stopwatch and measure the time it takes to finish one wipe of system. once all the **** is removed it should be like 10mins some said that it goes like 14mins.. easiest way is wipe for more than 20 times and reflash ROM download A1 SD bench app. Do a benchmark of internal storage. If Write speed is 20MB/s or more then your problem is fixed if not go back to wiping ???
SupulEdirisinghe said:
Use 3.0.1 from dreamstar..
And format data for 2-3 times and format system for 20+ times???.. keep a stopwatch and measure the time it takes to finish one wipe of system. once all the **** is removed it should be like 10mins some said that it goes like 14mins.. easiest way is wipe for more than 20 times and reflash ROM download A1 SD bench app. Do a benchmark of internal storage. If Write speed is 20MB/s or more then your problem is fixed if not go back to wiping ???
Click to expand...
Click to collapse
Bro can You provide download link for 3.0.1 from dreamstar
ashish1989 said:
Bro can You provide download link for 3.0.1 from dreamstar
Click to expand...
Click to collapse
Too lazy to find the link so I uploaded by my self
https://drive.google.com/file/d/0BxUVy1MbGMPKUVhDQkxsT3JmYW8/view?usp=sharing
SupulEdirisinghe said:
Too lazy to find the link so I uploaded by my self
https://drive.google.com/file/d/0BxUVy1MbGMPKUVhDQkxsT3JmYW8/view?usp=sharing
Click to expand...
Click to collapse
[emoji23][emoji23][emoji23][emoji23][emoji23][emoji23][emoji23]
Sent from my SM-G532F using Tapatalk
One of the easiest solution
Hello Everyone,
As all of us (G360H users) know, no matter what we do, lagness comes back after few days of smoothness. I am going to share what I do as a fix.
After flashing any ROM cleanly, lagness bothers after few days. So what to do?
>After you feel your phone is lagging, restart your phone to Recovery (TWRP 3.0.0 and above)
>Backup your system only (to internal storage or SD card doesn't matter, it's normally 600 to 700 MB)
>After Backup is completed, go to wipe section and then advanced wipe then wipe only system (at least 4 times without -rf option enabled, wiping takes some time)
>After wiping system few times, restore the system Backup from 2nd step, once completed restart your phone to system.
>Smoothness can be felt again but it's gonna come back again after few days (normally in around 15 days) REPEAT above steps again.
There's nothing new but this saves time in backing up and wiping up everything or the hassle of setting up a newly installed ROM. All your installed apps and data will stay safe and as they were.
Regards,
S
SupulEdirisinghe said:
Use 3.0.1 from dreamstar..
And format data for 2-3 times and format system for 20+ times.. keep a stopwatch and measure the time it takes to finish one wipe of system. once all the **** is removed it should be like 10mins some said that it goes like 14mins.. easiest way is wipe for more than 20 times and reflash ROM download A1 SD bench app. Do a benchmark of internal storage. If Write speed is 20MB/s or more then your problem is fixed if not go back to wiping
Click to expand...
Click to collapse
Bro done all the steps and used dreamstar's 3.0.1 twrp recovery
Formatted data for 3 times, formatted system for 20+ times
But still getting lags, but they are least now as compared before
any more solutions???
ashish1989 said:
Bro done all the steps and used dreamstar's 3.0.1 twrp recovery
Formatted data for 3 times, formatted system for 20+ times
But still getting lags, but they are least now as compared before
any more solutions???
Click to expand...
Click to collapse
Well you just have to do that for a little longer . When we use a storage we write and delete data continuously.. So our eMMC acts like a SSD when we write data they store in blocks and when we delete them usually the indexes are deleted ad data remains. so when we write something again those data in blocks are replaced by new data. So when lot of I/O precesses are going on it eventually remains filled blocks and they acts like fragments in HHDs, o remove them we need the process called trimming. Due to our eMMC's bug that wouldn't finish completely. So we have to wipe the storage manually until all blocks are completely wiped out and clean. Unless R/W speed will get low like 8mbps and that causes lags. Be patient and wipe until it's all gone