When I wipe the dalvik and battery stats, it just goes RIGHT back to the previous screen. shouldn't there be SOME kind of confirmation that the wipe took place? If so and since im NOT getting that confirmation, what do I need to do to fix this?
Thank you in advance to all of you that answer me.
p.s. - WTH is up with this ghost VM notification from sprint. I am running the RC1 from Darch and this darn VM wont GO AWAY!!
maybe try re-flashing your recovery?
Pauper7 said:
When I wipe the dalvik and battery stats, it just goes RIGHT back to the previous screen. shouldn't there be SOME kind of confirmation that the wipe took place? If so and since im NOT getting that confirmation, what do I need to do to fix this?
Click to expand...
Click to collapse
I just noticed this... is this normal? Everything else works fine, wipe cache, reboot, flashing roms/kernels/etc.,
i was updating my touchpad CM9 to V2 from aplha .06 and i just downloaded it stright to the touchpad with wifi and went to update it. I wiped the cach and all that but right before i went to install the CM9 i accidently hit the fix permissions button, it was like 5 am had just woken up and was in a hurry. Now that i try to boot to CM it wont do it at all it just reboots. I was wondering if anyone had an insight on it and could help me let me know.
Thanks in advance
plada2315 said:
i was updating my touchpad CM9 to V2 from aplha .06 and i just downloaded it stright to the touchpad with wifi and went to update it. I wiped the cach and all that but right before i went to install the CM9 i accidently hit the fix permissions button, it was like 5 am had just woken up and was in a hurry. Now that i try to boot to CM it wont do it at all it just reboots. I was wondering if anyone had an insight on it and could help me let me know.
Thanks in advance
Click to expand...
Click to collapse
Try flashing over.
Wipe data, cache and Dalvik and start fresh. It sounds like you had a bad flash...
plada2315 said:
i was updating my touchpad CM9 to V2 from aplha .06 and i just downloaded it stright to the touchpad with wifi and went to update it. I wiped the cach and all that but right before i went to install the CM9 i accidently hit the fix permissions button, it was like 5 am had just woken up and was in a hurry. Now that i try to boot to CM it wont do it at all it just reboots. I was wondering if anyone had an insight on it and could help me let me know.
Thanks in advance
Click to expand...
Click to collapse
I did the exact same thing and thought I had screwed things up. Luckily I had backed up prior so I simply restored it and it appears to have been fixed. There might be another way to remedy this in case you don't have back up though.
Good luck with finding a solution.
Sent from my MIUI Evo 3D
Everytime I try and install any Aroma installer, i can get though all the menu's, making all selections, but then once I click to actually start the installation, the phone screen just goes black, and the phone reboots, without the installation having completed. Which is quite an annoyance seeing as most installers are Aroma for the HTC One!
I have tried multiple recoveries (TWRP, CWM, CWM touch) all have the same error. I temporarily solved it for 1 install, by reflasing the boot image of my ROM (trickdroid 7.0)
No idea what has caused this, does anyone have a clue how to fix it? That doesn't involve a complete wipe?
Also, using volume keys makes no difference on this, only prevents crashing during menus
Video of what I mean is here: http://www.youtube.com/watch?v=KEP9aJzUFGo
dh2311 said:
Everytime I try and install any Aroma installer, i can get though all the menu's, making all selections, but then once I click to actually start the installation, the phone screen just goes black, and the phone reboots, without the installation having completed. Which is quite an annoyance seeing as most installers are Aroma for the HTC One!
I have tried multiple recoveries (TWRP, CWM, CWM touch) all have the same error. I temporarily solved it for 1 install, by reflasing the boot image of my ROM (trickdroid 7.0)
No idea what has caused this, does anyone have a clue how to fix it? That doesn't involve a complete wipe?
Also, using volume keys makes no difference on this, only prevents crashing during menus
Video of what I mean is uploading as I type this, allow 20 minutes (my internet is that bad)
Click to expand...
Click to collapse
first i would say dont have your phone plugged in while flashing and second make sure your phone is cool not hot. seems to get worse for me when the phone gets hot. also there is a new sense rom that doesnt use aroma its called rayglobe 4.0
skinsfanbdh said:
first i would say dont have your phone plugged in while flashing and second make sure your phone is cool not hot. seems to get worse for me when the phone gets hot. also there is a new sense rom that doesnt use aroma its called rayglobe 4.0
Click to expand...
Click to collapse
Phone wasn't plugged in, and the issue i'm having it with now is the kernel, I have the ROM installed, problem didn't start until a day or so after the rom install. Can't tell what started it
dh2311 said:
Phone wasn't plugged in, and the issue i'm having it with now is the kernel, I have the ROM installed, problem didn't start until a day or so after the rom install. Can't tell what started it
Click to expand...
Click to collapse
are you wiping davlik and cache before flashing that will also help and you might want to try fastboot erase cache
skinsfanbdh said:
are you wiping davlik and cache before flashing that will also help and you might want to try fastboot erase cache
Click to expand...
Click to collapse
Just tried that, same error after fastboot cache wipe aswell as davlik cache. So frustrated, only just got a HTC one, usually a nexus guy, and never had experience with Aroma before this, not a good first impression of Aroma
dh2311 said:
Just tried that, same error after fastboot cache wipe aswell as davlik cache. So frustrated, only just got a HTC one, usually a nexus guy, and never had experience with Aroma before this, not a good first impression of Aroma
Click to expand...
Click to collapse
yea its an aroma issue not phone or rom issue. have you used all in one toolkit to fastboot erase cache and install recovery
skinsfanbdh said:
yea its an aroma issue not phone or rom issue. have you used all in one toolkit to fastboot erase cache and install recovery
Click to expand...
Click to collapse
I'm on mac, so it would require Parallels, so I just type them out to save the hassle. I'm manually installing the kernel now, flashing boot.img in fastboot and pushing all the extras via ADB but I'd still like to figure out whats up with my phone and Aroma. It's not like the zips are faulty, its every single aroma installer, so something on my phone must be up
dh2311 said:
I'm on mac, so it would require Parallels, so I just type them out to save the hassle. I'm manually installing the kernel now, flashing boot.img in fastboot and pushing all the extras via ADB but I'd still like to figure out whats up with my phone and Aroma. It's not like the zips are faulty, its every single aroma installer, so something on my phone must be up
Click to expand...
Click to collapse
yea maybe. every once and a while aroma gives me a lot of issues but most of the time it only takes 1-3 times to install. but if you get tired of it give rayglobe a try i think its pretty good
skinsfanbdh said:
yea maybe. every once and a while aroma gives me a lot of issues but most of the time it only takes 1-3 times to install. but if you get tired of it give rayglobe a try i think its pretty good
Click to expand...
Click to collapse
I'm not overexaggerating when I say I've tried this about 20 times. Going for a full wipe, back to RUU and see if that solves all this
dh2311 said:
I'm not overexaggerating when I say I've tried this about 20 times. Going for a full wipe, back to RUU and see if that solves all this
Click to expand...
Click to collapse
ive had that also i just restored my backup and quit for the day then tried the next day and it worked
dh2311 said:
I'm not overexaggerating when I say I've tried this about 20 times. Going for a full wipe, back to RUU and see if that solves all this
Click to expand...
Click to collapse
try with re-downloading the file and put it in root of your sd card
rambo12345 said:
try with re-downloading the file and put it in root of your sd card
Click to expand...
Click to collapse
tried that as well, tried all kinds of different directories, and redownloading the files, but files that did work and I have installed now wont, so i have no clue whats happened
dh2311 said:
tried that as well, tried all kinds of different directories, and redownloading the files, but files that did work and I have installed now wont, so i have no clue whats happened
Click to expand...
Click to collapse
Are you touching the screen at all? Like even the slightest touch? I know that in the ARHD thread it mentioned that's an issue and will cause problems. I know that I accidentally touched it and messed everything up for me. I am now super careful when I flash to make sure I touch nothing except the buttons.
Okay, in a weird turn of events, I thought i would rather than going to an RUU just wipe everything and reinstall everything, and the Aroma installers for the ROM and tweaks are working so far...
EVERYTHING WORKED! Dont know whether it was the wipe, just luck, installing using only volume keys and power button. But this seems to have gone away :fingers-crossed:
nolimit78 said:
Are you touching the screen at all? Like even the slightest touch? I know that in the ARHD thread it mentioned that's an issue and will cause problems. I know that I accidentally touched it and messed everything up for me. I am now super careful when I flash to make sure I touch nothing except the buttons.
Click to expand...
Click to collapse
I could well be... have some working now, but if one breaks, Ill try reinstalling using volume keys and power button and never touch the screen
awesome. glad you got through it bro:good:
Whenever i boot, whether its cold or warm, 1/3 times it will boot loop and the only way to fix it is clearing the cache through recovery. Sometimes its fine and boots normally, others it takes 5-10 times to boot properly or, i can just clear the cache but my apps have to optimize again and it takes awhile. Can anyone relate or provide a fix? thanks.
clayton128 said:
Whenever i boot, whether its cold or warm, 1/3 times it will boot loop and the only way to fix it is clearing the cache through recovery. Sometimes its fine and boots normally, others it takes 5-10 times to boot properly or, i can just clear the cache but my apps have to optimize again and it takes awhile. Can anyone relate or provide a fix? thanks.
Click to expand...
Click to collapse
Sounds like a Kernel issue to me. Try using CM 10.1 in the Vivid Development Thread.
TheROMGuy said:
Sounds like a Kernel issue to me. Try using CM 10.1 in the Vivid Development Thread.
Click to expand...
Click to collapse
took your advice and updated, its much better all around. thanks!
clayton128 said:
took your advice and updated, its much better all around. thanks!
Click to expand...
Click to collapse
No problem. Glad its working for you.
So, I followed this thread, used unsu, and things just as described in there:
https://forum.xda-developers.com/apps/magisk/switching-supersu-to-magisksu-t3625579
The thing is, I flashed LineageOS's boot.img which I had, though... now, my phone will get past the "SAMSUNG" logo, and the warranty bit kernel notification thing on the top left... and it'll automatically reboot, and then boot again to download mode, I can boot to recovery mode, everything except the actual system...
Just a guess (I've not checked the link): go to recovery and wipe cache and dalvik before reboot to system.
wilsonhlacerda said:
Just a guess (I've not checked the link): go to recovery and wipe cache and dalvik before reboot to system.
Click to expand...
Click to collapse
Unfortunately, nope..
Jasiniok said:
So, I followed this thread, used unsu, and things just as described in there:
https://forum.xda-developers.com/apps/magisk/switching-supersu-to-magisksu-t3625579
The thing is, I flashed LineageOS's boot.img which I had, though... now, my phone will get past the "SAMSUNG" logo, and the warranty bit kernel notification thing on the top left... and it'll automatically reboot, and then boot again to download mode, I can boot to recovery mode, everything except the actual system...
Click to expand...
Click to collapse
Did you back up the boot in twrp before u do that?
I had similar problems before but i immediately gave up to use and just restore my boot partition from working one
Kglim said:
Did you back up the boot in twrp before u do that?
I had similar problems before but i immediately gave up to use and just restore my boot partition from working one
Click to expand...
Click to collapse
Nope, I didn't xD. But yeah, luckily I didn't have a lot of pictures and things(Even tho i could back them up), but yeah, I installed a even newer rom(unofficial). Thanks a lot for helping/trying to help!
Jasiniok said:
Nope, I didn't xD. But yeah, luckily I didn't have a lot of pictures and things(Even tho i could back them up), but yeah, I installed a even newer rom(unofficial). Thanks a lot for helping/trying to help!
Click to expand...
Click to collapse
I think you could save ur data partitiin and sjust system wipe and dirty flash for carry yiur data.
Good luck to ya!!! :fingers-crossed: