I'm experiencing some gradual slowdown with my M7 running Viper One 7, to the point where I'm clearing the caches once a week. Seems stoopit.
Since I've flashed prolly 20 ROMs over the last year, I'm thinking that it might be worthwhile to do a factory reset, wipe the SD and all.
If I make a Nandroid with TWRP and use that to start with, wouldn't that actually include any bad gris gris and therefore kind of null the point of doing the factory reset?
Would I be better off, after the factory reset, flashing the ROM and Kernel (EL-X) from scratch and dropping all else from a back-up?
Or am I over thinking this?
Something slowing my M7.
I have 140 apps. No games.
About a dozen of which are running normally, using 785mb of 1.7gb RAM.
And 27.5G of total storage used.
Wtf 140 apps? I got maybe 30.
metropical said:
If I make a Nandroid with TWRP and use that to start with, wouldn't that actually include any bad gris gris and therefore kind of null the point of doing the factory reset?
Click to expand...
Click to collapse
Probably but it might worth a try
Would I be better off, after the factory reset, flashing the ROM and Kernel (EL-X) from scratch and dropping all else from a back-up?
Click to expand...
Click to collapse
imo, yes it would be better to start over from scratch.
I have 140 apps. No games.
About a dozen of which are running normally, using 785mb of 1.7gb RAM.
Click to expand...
Click to collapse
shouldn't be an issue
And 27.5G of total storage used.
Click to expand...
Click to collapse
thats a lot, but I'm not sure its related to your issue.
Fairtex said:
Wtf 140 apps? I got maybe 30.
Click to expand...
Click to collapse
that's what I had when I bought my Sensation.
But stuff comes along ...........
alray said:
Probably but it might worth a try
imo, yes it would be better to start over from scratch.
shouldn't be an issue
thats a lot, but I'm not sure its related to your issue.
Click to expand...
Click to collapse
then away we go ......... from scratch
metropical said:
then away we go ......... from scratch
Click to expand...
Click to collapse
good luck, let me know if it worked
alray said:
good luck, let me know if it worked
Click to expand...
Click to collapse
no matter what I do, ViperOne remains as does the ElementalX kernel.
Weird
metropical said:
no matter what I do, ViperOne remains as does the ElementalX kernel.
Weird
Click to expand...
Click to collapse
what did you try ? Format Data in TWRP will completely erase the phone
then adb push a rom back to the phone and your off to a clean start
clsA said:
what did you try ? Format Data in TWRP will completely erase the phone
then adb push a rom back to the phone and your off to a clean start
Click to expand...
Click to collapse
thanks
http://forum.xda-developers.com/showpost.php?p=56964579&postcount=42028
metropical said:
thanks
http://forum.xda-developers.com/showpost.php?p=56964579&postcount=42028
Click to expand...
Click to collapse
so you have already done the Format Data ?
clsA said:
so you have already done the Format Data ?
Click to expand...
Click to collapse
I have . and in updating TWRP, I wiped the phone again.
so sideloading again.
ah well
so far, the couple apps that were misbehaving have been better.
but the 1 xPosed module I have, MacroExpansion isn't working correctly.
metropical said:
I have . and in updating TWRP, I wiped the phone again.
so sideloading again.
ah well
so far, the couple apps that were misbehaving have been better.
but the 1 xPosed module I have, MacroExpansion isn't working correctly.
Click to expand...
Click to collapse
The second you installed xPosed you screwed up in my opinion .. I have no use for it. But i understand many like it for the Sense 6 toolbox fuctions
alray said:
good luck, let me know if it worked
Click to expand...
Click to collapse
so far so good. found 1 offending app that slowed others, so it's gone.
seems to be back to what I remember.
Related
1.st off thanks for the extremely helpful guides and taking the time to root this device because the copious amount of OE bloatware is horrible.
2.nd I rooted my 510 and now i have no "home" screen. I can view apps and settings and if i recieve a text i can view it by clicking the notification but if i hit home it goes straight to the google search menu?
I tried a factory reset and nothing.
Thanks in advance.
bdawg the third said:
1.st off thanks for the extremely helpful guides and taking the time to root this device because the copious amount of OE bloatware is horrible.
2.nd I rooted my 510 and now i have no "home" screen. I can view apps and settings and if i recieve a text i can view it by clicking the notification but if i hit home it goes straight to the google search menu?
I tried a factory reset and nothing.
Thanks in advance.
Click to expand...
Click to collapse
Are you running a stock rom or something else? It sounds like Sense isn't installed.
well i was on the stock ROM. but now i think i made the problem worse by trying to fix it. now it wont boot passed the HTC screen. SO i guess i need to try to load a factory boot image?
bdawg the third said:
well i was on the stock ROM. but now i think i made the problem worse by trying to fix it. now it wont boot passed the HTC screen. SO i guess i need to try to load a factory boot image?
Click to expand...
Click to collapse
Yeah, if you've got TWRP installed I would flash a stock rom. CM11 is also usable minus the cameras.
dipspit said:
Yeah, if you've got TWRP installed I would flash a stock rom. CM11 is also usable minus the cameras.
Click to expand...
Click to collapse
Do you have a stock Rom? I cant find one that works. I'm also a huge noob.
bdawg the third said:
Do you have a stock Rom? I cant find one that works. I'm also a huge noob.
Click to expand...
Click to collapse
Who's your service provider?
dipspit said:
Who's your service provider?
Click to expand...
Click to collapse
boost. sorry i thought i posted that
bdawg the third said:
boost. sorry i thought i posted that
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=57042931&postcount=1 V2 Flash that in TWRP.
i get an "unable to open zip" error
bdawg the third said:
i get an "unable to open zip" error
Click to expand...
Click to collapse
What all have you actually flashed or done to the phone? And this error is in TWRP and not fastboot right?
dipspit said:
What all have you actually flashed or done to the phone? And this error is in TWRP and not fastboot right?
Click to expand...
Click to collapse
thats the problem im not %100 sure. im pretty sure i have no OS currently flashed. and yeah the error is in twrp
bdawg the third said:
thats the problem im not %100 sure. im pretty sure i have no OS currently flashed. and yeah the error is in twrp
Click to expand...
Click to collapse
How are you getting the zip over to the phone? Use adb push or an external sd card. You might need to wipe (factory reset) in TWRP before you try and install.
Ok it opened the zip and says flashed successful. now its just sitting on the htc boot screen hmm
bdawg the third said:
Ok it opened the zip and says flashed successful. now its just sitting on the htc boot screen hmm
Click to expand...
Click to collapse
Sounds like a problem with boot. Do a factory reset in TWRP, flash http://forum.xda-developers.com/showpost.php?p=57174863&postcount=1 and then afterwards flash that ROM.
Download the zip in this post and adb push that file to your TWRP/BACKUPS/ folder and restore like that. I forgot the other ROM I had you flash required a previous backup to have been made.
nope still stuck on the htc boot
bdawg the third said:
nope still stuck on the htc boot
Click to expand...
Click to collapse
I edited my post after posting. Did you try that?
dipspit said:
I edited my post after posting. Did you try that?
Click to expand...
Click to collapse
Im getting an unable to find partition for path error?
bdawg the third said:
Im getting an unable to find partition for path error?
Click to expand...
Click to collapse
Regarding http://forum.xda-developers.com/desire-510/development/virgin-sprint-htc-desire-510-stock-t2961521 , are you going about it this way?
There's not really a rom that you can flash without already having a backup. If all else fails you can fastboot oem lock and then run the Sprint 510 RUU from http://www.htcdev.com/devcenter/downloads
dipspit that last link did it! Thank you so much for your help. Ive learned my lesson about not making backups haha.
I can no longer write any custom roms to my N6. Started with PURE 3.5 but now effects any rom i try to flash. I have brought my N6 back to factory state multiple times even relocking it. Only thing I can do is Fastboot flash N6 image from google manually piece by piece. I do have working 5.01 and phone works. Roms either hang or have errors. or just write the boot.img file. TWRP works other wise i can backup and restore, I am using 2.8.3.1. I have searched all over for a fix....
There used to be some weird mounting stuff that would make roms not boot. Thought that was worked out in pure shamu 3.1 ish.
Where do the roms hang? Did you ever fix permissions using twrp? Any kind of log you can pull?
dipstik said:
There used to be some weird mounting stuff that would make roms not boot. Thought that was worked out in pure shamu 3.1 ish.
Where do the roms hang? Did you ever fix permissions using twrp? Any kind of log you can pull?
Click to expand...
Click to collapse
I had no problem updating Pure for over a month from like 2.0 to 3.4.
they all hang when writing to system as far as i can tell. happens regardless of Pure....from a fresh clean image of 5.0 or 5.01 i can not flash any roms. driving me nutzo....i can no longer flash pure 3.4 either but i can restore the phone from a nandroid backup i had on my pc and run Pure 3.4 just fine.
Did you wipe everything except internal storage first? I had this issue earlier until I realized that I forgot to do that when coming from the stock ROM.
Pilz said:
Did you wipe everything except internal storage first? I had this issue earlier until I realized that I forgot to do that when coming from the stock ROM.
Click to expand...
Click to collapse
yes and both cache.....
also made sure system not mounted.
very frustrating.
Bignoze73 said:
yes and both cache.....
also made sure system not mounted.
very frustrating.
Click to expand...
Click to collapse
That is very odd, did you try reflashing TWRP or using a different version.
Pilz said:
That is very odd, did you try reflashing TWRP or using a different version.
Click to expand...
Click to collapse
mutiple times......tried all versions of TWRP too.
I can write a custom kernal like elementalx no problem.....just not roms.
Bignoze73 said:
mutiple times......tried all versions of TWRP too.
Click to expand...
Click to collapse
It doesn't make sense considering you also flashed back to stock. Have you also tried to flash a ROM from your PC rather than from your phone? There has to be some reasonable explanation for why it's not working.
Pilz said:
It doesn't make sense considering you also flashed back to stock. Have you also tried to flash a ROM from your PC rather than from your phone? There has to be some reasonable explanation for why it's not working.
Click to expand...
Click to collapse
how do you do that? the custom roms dont have system.img file like N6 image. The Pure 3.92 is in .dat format, another rom is folders. I also get checksum errors when extracting.
I also noticed in the last 24 hours there are 2 other threads with people have almost the same issues flashing roms. I think it has something to do with TWRP but no matter becuase no version works for me.
Bignoze73 said:
how do you do that? the custom roms dont have system.img file like N6 image. The Pure 3.92 is in .dat format, another rom is folders. I also get checksum errors when extracting.
I also noticed in the last 24 hours there are 2 other threads with people have almost the same issues flashing roms. I think it has something to do with TWRP but no matter becuase no version works for me.
Click to expand...
Click to collapse
If you restore your stock recovery on your phone you could try this.
Make sure TWRP is not installed on your phone and that the stock recovery is installed and working:
Have TWRP in your platform tools folder named however you want
Then use "fastboot boot recovery 'whatever you named TWRP' "
This will boot TWRP without installed it. Then try to flash the ROM using TWRP. You can also use the"adb push" to sideload the ROM onto your phone so you can find it via TWRP.
nope did not work.....roms just hang or flash new boot.img only.
i even tried erasing recovery partion and reflashing stock than twrp 2.8.3.1......that did not work either....something is stopping TWRP from writing to system.
thanks for your help
Bignoze73 said:
nope did not work.....roms just hang or flash new boot.img only.
i even tried erasing recovery partion and reflashing stock than twrp 2.8.3.1......that did not work either....something is stopping TWRP from writing to system.
thanks for your help
Click to expand...
Click to collapse
You're welcome, have you tried to contact some of the devs here to see if maybe they could help? I think the worst case scenario would be to RMA the phone.
Pilz said:
You're welcome, have you tried to contact some of the devs here to see if maybe they could help? I think the worst case scenario would be to RMA the phone.
Click to expand...
Click to collapse
RMA the phone??? ?What are you gonna tell them?? ? That you can't flash any custom Roms through TWRP?? ?
laureanop said:
RMA the phone??? ?What are you gonna tell them?? ? That you can't flash any custom Roms through TWRP?? ?
Click to expand...
Click to collapse
No obviously not look, but if you have other issues (in assuming you might if you can't flash a ROM) then that's the worst case scenario option.
Pilz said:
No obviously not look, but if you have other issues (in assuming you might if you can't flash a ROM) then that's the worst case scenario option.
Click to expand...
Click to collapse
This is a tough one cause if his factory image works without issues they're gonna have no reason to send him a replacement
laureanop said:
This is a tough one cause if his factory image works without issues they're gonna have no reason to send him a replacement
Click to expand...
Click to collapse
That's true, but there must be something wrong if he can't flash anything else so I'm sure he could find some issues.
Pilz said:
That's true, but there must be something wrong if he can't flash anything else so I'm sure he could find some issues.
Click to expand...
Click to collapse
Is there a tool or command to do a full memcheck of both ram and storage
rgraville said:
Is there a tool or command to do a full memcheck of both ram and storage
Click to expand...
Click to collapse
I'm not sure I've never had the need to do one from adb or fastboot
Pilz said:
I'm not sure I've never had the need to do one from adb or fastboot
Click to expand...
Click to collapse
yeah its pretty nuts....how can I return a phone that works fine other than the fact it wont flash a custom rom?
Must be another way to write a rom but TWRP......
thanks!
Bignoze73 said:
yeah its pretty nuts....how can I return a phone that works fine other than the fact it wont flash a custom rom?
Must be another way to write a rom but TWRP......
thanks!
Click to expand...
Click to collapse
I assume you are also out of the return window. Well if you are unlucky or lucky (depending on how you view it) you could have an issue eventually. They will RMA for burn in, camera issues etc... The camera issue was common in the earlier production models that I had. There should be another method, I would look into it if you have time.
Please if someone can take the time to help me save a lot of time.
So I had to restore my Nexus 6 back to stock from CM12 to unlock the phone so I could start using Project Fi. So I went back set it up and was ready to restore back to cm12. Well every time I try to go back to one of my updates it runs for maybe a min and then the phone restarts and then just stays on start up screen without starting up.
this has nothing to do with the unlocking of the phone because 2 months ago when I needed to restore from cm12 it did the same thing!
So why cant I restore using twarp on my device and what do I have to do to get back my restore.
also when I try to just reload cm12 it fails .
PLEASE HELP ME SOMEONE! LOL
CM is your first problem. LOL All that aside. Usually when it stops on startup screen the kernel is borked. Try fastbooting/flashing a compatible kernel.
Try wipe cache and dalvik from recovery. If it still doesn't boot, wipe data, then restore apps using titanium
Can you guys please look at clip I made of the issue. Thanks so much!
https://youtu.be/3C8LtPu9LsA
<iframe width="420" height="315" src="https://www.youtube.com/embed/3C8LtPu9LsA" frameborder="0" allowfullscreen></iframe>
No need. Follow our advice
enzosly said:
Can you guys please look at clip I made of the issue. Thanks so much!
https://youtu.be/3C8LtPu9LsA
<iframe width="420" height="315" src="https://www.youtube.com/embed/3C8LtPu9LsA" frameborder="0" allowfullscreen></iframe>
Click to expand...
Click to collapse
To start I would actually wipe. Dalvik and cache is not a wipe. This only affects apps saved in ram.. Wipe system. Your flashing over old system and data. It is different flashing images than it is flashing restores. Can have files that are not overwritten. Basically a full dirty flash. Can't go stock and then dirty flash rom over the top. Especially CM. Too much doesn't match. Your flashing different bases over the top of each other. This is why people need permission fixes. The UID's don't match between the different bases. Have never used fix permissions unless testing and then shows us need to fully wipe.
prdog1 said:
To start I would actually wipe. Dalvik and cache is not a wipe. This only affects apps saved in ram.. Wipe system. Your flashing over old system and data. It is different flashing images than it is flashing restores. Can have files that are not overwritten. Basically a full dirty flash. Can't go stock and then dirty flash rom over the top. Especially CM. Too much doesn't match. Your flashing different bases over the top of each other. This is why people need permission fixes. The UID's don't match between the different bases. Have never used fix permissions unless testing and then shows us need to fully wipe.
Click to expand...
Click to collapse
ok so do a full wipe is what your saying then? Ill give it a try
enzosly said:
ok so do a full wipe is what your saying then? Ill give it a try
Click to expand...
Click to collapse
Yes. Also make sure boot is checked when make a backup. If restore doesn't contain kernel CM won't boot with stock kernel.
prdog1 said:
Yes. Also make sure boot is checked when make a backup. If restore doesn't contain kernel CM won't boot with stock kernel.
Click to expand...
Click to collapse
Ok so I did a full wipe and still same thing. I also went into fixing permissions and nothing.
what should I do next I guess? again thank you for taking the time
enzosly said:
Ok so I did a full wipe and still same thing. I also went into fixing permissions and nothing.
what should I do next I guess? again thank you for taking the time
Click to expand...
Click to collapse
Backup may be bad. Wipe everything and flash a full image/rom. Stopping on the splash usually means corrupted kernel. Rom not booting. If get to boot animation it is rom related. Need to start fresh. Google saves your apps so it no big deal. Rather have clean working rom than worry about apps and resetup.
enzosly said:
Ok so I did a full wipe and still same thing. I also went into fixing permissions and nothing.
what should I do next I guess? again thank you for taking the time
Click to expand...
Click to collapse
NEVER fix permissions.
Download the rom and flash it. Then use titanium to restore apps.extracted from.your nandroid.backup, if it can.
danarama said:
NEVER fix permissions.
Download the rom and flash it. Then use titanium to restore apps.extracted from.your nandroid.backup, if it can.
Click to expand...
Click to collapse
I agree if have to fix permissions rom is borked. Still looks like corrupted backup. Wipe all and fastboot stock or flash clean rom.
danarama said:
NEVER fix permissions.
Download the rom and flash it. Then use titanium to restore apps.extracted from.your nandroid.backup, if it can.
Click to expand...
Click to collapse
fix_permissions works, but not via recovery. i use stericsons fix_permissions app. it goes through and fixes permissions, per each app, when you are fully booted.
simms22 said:
fix_permissions works, but not via recovery. i use stericsons fix_permissions app. it goes through and fixes permissions, per each app, when you are fully booted.
Click to expand...
Click to collapse
It fixes mismatched UIDs which means you have a corrupt install. LOL
simms22 said:
fix_permissions works, but not via recovery. i use stericsons fix_permissions app. it goes through and fixes permissions, per each app, when you are fully booted.
Click to expand...
Click to collapse
Thing is they can't know what permissions everything is supposed to have, so its guess work and can lead to more problems l. Besides, permissions should never need fixing anyway
prdog1 said:
It fixes mismatched UIDs which means you have a corrupt install. LOL
Click to expand...
Click to collapse
whatever.. last time i installed anything was when m came out. honestly, ill use that app maybe twice a year, but it does work.
---------- Post added at 03:10 PM ---------- Previous post was at 03:08 PM ----------
danarama said:
Thing is they can't know what permissions everything is supposed to have, so its guess work and can lead to more problems l. Besides, permissions should never need fixing anyway
Click to expand...
Click to collapse
na, it doesnt ever need fixin', its just something ill do every once in a while. kind of a habit leftover from the older android days.
simms22 said:
whatever.. last time i installed anything was when m came out. honestly, ill use that app maybe twice a year, but it does work.
Click to expand...
Click to collapse
Just saying after years as a tester and thousands of builds. Was a big thing when they were porting roms to a different device. UIDs were broke all over the place. See the same thing if dirty flash different bases like Lolli over KitKat or a complete base change as an example ( L to M). Don't see mismatched UID's on updates made on same base.
prdog1 said:
Just saying after years as a tester and thousands of builds. Was a big thing when they were porting roms to a different device. UIDs were broke all over the place. See the same thing if dirty flash different bases like Lolli over KitKat or a complete base change as an example ( L to M). Don't see mismatched UID's on updates made on same base.
Click to expand...
Click to collapse
im very known as a dirty flasher btw :angel:
(and i did dirty flash m over terminus)
simms22 said:
im very known as a dirty flasher btw :angel:
(and i did dirty flash m over terminus)
Click to expand...
Click to collapse
Some have the luck. Apparently this poster don't.
prdog1 said:
Some have the luck. Apparently this poster don't.
Click to expand...
Click to collapse
its not luck, its all about doing it properly
I keep getting this notification. Tried wiping catch, and still no luck. On screwed ROM with elemental x kernel
alphamale said:
I keep getting this notification. Tried wiping catch, and still no luck. On screwed ROM with elemental x kernel
Click to expand...
Click to collapse
What notification? It looks like you've got plenty of space to me.
JimSmith94 said:
What notification? It looks like you've got plenty of space to me.
Click to expand...
Click to collapse
See attached file
alphamale said:
See attached file
Click to expand...
Click to collapse
Thats for your system storage, not your personal data. When you installed that firmware, did you use a full Gapps package versus a minimal one?
christianpeso said:
Thats for your system storage, not your personal data. When you installed that firmware, did you use a full Gapps package versus a minimal one?
Click to expand...
Click to collapse
I honestly don't know its the due clear gapps. I changed my kernel to permissive, and since I did that the notification is gone. Is there another solution to fix that you know of
If it's your /system partition that's full, delete /system/app/(foreign keyboards that you don't need such as GoogleHindiIME, GoogleJapaneseIME, GooglePinyinIME)
...also korean
electricpete1 said:
...also korean
Click to expand...
Click to collapse
Haha, yeah thanks! I just noticed that I missed that one when an update for it showed up in the Play Store today.
hey my nexus 6 battery stats are screwed the usage shows as system ui and a factory reset didnt help either runnung stock rom no root any ideas? thanks
maybe a bit more of an expaination? its normal for system ui to show up in the battery stats, and factory resets dont do a thing, try flashing a factory image.
simms22 said:
maybe a bit more of an expaination? its normal for system ui to show up in the battery stats, and factory resets dont do a thing, try flashing a factory image.
Click to expand...
Click to collapse
sorry if i didnt write up well i mean the only thing in the battery usage is system ui
lukem99626 said:
sorry if i didnt write up well i mean the only thing in the battery usage is system ui
Click to expand...
Click to collapse
what android version are you on? latest is 6.0.1..
simms22 said:
what android version are you on? latest is 6.0.1..
Click to expand...
Click to collapse
yeah latest but im behind on a security update thanks
lukem99626 said:
yeah latest but im behind on a security update thanks
Click to expand...
Click to collapse
try flashing the latest factory image, but it should fix itsrlf anyways. how long has it been happening?
simms22 said:
try flashing the latest factory image, but it should fix itsrlf anyways. how long has it been happening?
Click to expand...
Click to collapse
couple days now after i flashed the factory rom from chroma
lukem99626 said:
couple days now after i flashed the factory rom from chroma
Click to expand...
Click to collapse
ahh.. chroma. the issue is chroma, I'm 1000% sure of it. try pure nexus ROM