Is there a more stable recovery for me to use with my CM9 TP? I have CWM 5.026 and the thing is like a cat. It works when it feels like, mostly doesn't. Sometimes it reboots by itself, sometimes it won't do much of anything, sometimes it stops after backing up boot but before system starts. I honestly feel like this CWM is going TROLOLOLOLOL.
Is there a more stable recovery for the TP or is my CWM isolated to just me?
NapalmDawn said:
Is there a more stable recovery for me to use with my CM9 TP? I have CWM 5.026 and the thing is like a cat. It works when it feels like, mostly doesn't. Sometimes it reboots by itself, sometimes it won't do much of anything, sometimes it stops after backing up boot but before system starts. I honestly feel like this CWM is going TROLOLOLOLOL.
Is there a more stable recovery for the TP or is my CWM isolated to just me?
Click to expand...
Click to collapse
Honestly sounds like you need to reflash with Acme or you have a hardware issue.
I personally use GooManager and TWRP with zero issues
Use search for more info please
Sent from my CM9 TouchPad using TapaTalk 2
what exactly is it doing? "it works when it feels like it" doesn't give much to go on? like someone mentioned I would try to reinstall with acme, if you're still having the same issues it's likely not the cwm image that is the problem.
Perhaps install Goomanager and use that to install TWRP. If that still has problems, then try reinstalling with Acme.
I think it's just you. I have never had an issue with CWM. Try reinstalling or give TWRP a whirl. I don't care for TWRP but there's a lot of people who love it. It's touch based and has a decent UI.
Allons-y
NapalmDawn said:
Is there a more stable recovery for me to use with my CM9 TP? I have CWM 5.026 and the thing is like a cat. It works when it feels like, mostly doesn't. Sometimes it reboots by itself, sometimes it won't do much of anything, sometimes it stops after backing up boot but before system starts. I honestly feel like this CWM is going TROLOLOLOLOL.
Is there a more stable recovery for the TP or is my CWM isolated to just me?
Click to expand...
Click to collapse
I haven't had a problem with cwm on my TP. I also use 5.0.2.6. I've had troubles with 5.0.2.8 on my phone, so much so, that I don't use it. I use titanium backup instead.
I just changed phones, and that was one of the reasons. My new phone (LG Motion 4g, metropcs) doesn't have cwm yet, but the devs are working on it.
Try setting your min cpu speed to 384, if you haven't done so yet. That could help.
Good luck.
Thanks for the replies. I'll try TWRP. Are my old backups from CWM not valid if I go with TWRP?
haxin said:
what exactly is it doing? "it works when it feels like it" doesn't give much to go on? like someone mentioned I would try to reinstall with acme, if you're still having the same issues it's likely not the cwm image that is the problem.
Click to expand...
Click to collapse
Basically it doesn't always give the expected results. Sometimes it starts a restore, hangs, reboots. Does the same thing for backing up. Sometimes you can even tell the TP to boot into recovery, look away and as it sits waiting for your input (no more than 2-3 minutes) it reboots itself. When you reboot, you'll see briefly in the startup text things like last boot=panic andlast boot=app crash.
NapalmDawn said:
Thanks for the replies. I'll try TWRP. Are my old backups from CWM not valid if I go with TWRP?
Click to expand...
Click to collapse
You are correct that the CWR backups dont work with TWRP. I have tried TWRP out and discovered this myself. And just my personal opinion, I didnt really like TWRP. CWR works perfectly for me.
Related
Hi guys,
Tried to upgrade from Darchdroid 2.6.5 to 2.7 today and am now stuck with an unusable phone.
I get a boot loop OR I get stuck on the HTC boot screen for 20+ min. I'm not sure why I get stuck on either one.
This advice was given to me today in the 2.7 thread:
hold down menu+back+power and do a hard reset.
then wipe everything. [EVERYTHING ext4, ect.]
then flash DD2.7
then flash GoogleBits.
good luck.
edit: this has the newest kernel.
__________________
Click to expand...
Click to collapse
The problem is, in order to complete a hard reset, you have to reboot the phone!(right?) But when I reboot, I just get stuck on the HTC boot screen. Is there wiping instructions (i.e. do I need to do certain things from adb instead of the phone?) that I'm missing out on?
Thanks so much. Really loved 2.6.5. Don't know why I keep getting suckered into updating
A hard reset is the same thing as doing a factory reset. So, go into recovery, go tinto the wipe list, and wipe everything on that list. Then, flash it and reboot.
HeroMeng said:
A hard reset is the same thing as doing a factory reset. So, go into recovery, go tinto the wipe list, and wipe everything on that list. Then, flash it and reboot.
Click to expand...
Click to collapse
Thx, Heromeng. Did exactly what you said - wiped everything possible in AmonRa 1.7 and now I'm back to a boot loop.
Some further info: When I was upgrading from 2.6.4 to 2.6.5, Darch said I should push the boot.img from 2.6.4 to make things work. That did the trick for the last update (although I don't know why!).
Is pushing the boot.img from 2.6.4 the way to get 2.7 to work on my phone?
Alright, I went ahead and pushed the boot.img from 2.6.4 and now it's working. I guess it's just like 2.6.5.
My question:
What am I sacrificing by using this boot.img instead of the one from 2.7? I'm not clear what the trade-off is.
Thanks again.
Back up your sd card, then repartition it.
Sometimes ramswapz corrupts the sd card, so you have to format it and repartition before being able to flash a new ROM.
---------------------------------------
There isn't enough of a difference between the kernel where your phone shouldn't boot.
Decad3nce said:
Back up your sd card, then repartition it.
Sometimes ramswapz corrupts the sd card, so you have to format it and repartition before being able to flash a new ROM.
---------------------------------------
There isn't enough of a difference between the kernel where your phone shouldn't boot.
Click to expand...
Click to collapse
Decad3nce: I've re-partitioned it 3 separate times and every time it's a boot loop! Would you tell me if I'm doing this all in the correct order?
-Wipe everything.
-Re-partition sd card
-Enable USB toggle
-Move 2.7 and Googleshits from computer to Phone
-Flash ROM
-Flash googleshits.
-Reboot.
note: I was able to boot into 2.7 with the (pushed) 2.6.4 boot.img but I wasn't able to start wi-fi. So I'm assuming the 2.6.4 boot.img had something to do with that and that's why I'm trying a "virgin" 2.7 flash again.
All I can say is I'm in the same boat. It seemed to me, in my earlier tinkerings, that my phone needed a boot.img that was slightly less overclocked. The few DarchDroid successes I've had were from lower-clocked boot.img's. Without it, I just look at the HTC logo forever.
bohiti said:
All I can say is I'm in the same boat. It seemed to me, in my earlier tinkerings, that my phone needed a boot.img that was slightly less overclocked. The few DarchDroid successes I've had were from lower-clocked boot.img's. Without it, I just look at the HTC logo forever.
Click to expand...
Click to collapse
That's really helpful info, Bohiti. I thought I was alone here!
I am in 2.7 now with the 2.6.4 boot.img but I'm unable to start wi-fi.
This is a dealbreaker for me.
Why would the boot.img affect wi-fi??
Well sorry, kind of. While what I said was true, I just now tried the hard reset suggested to you. (Menu+Back+Power). And then I wiped everything and flashed 2.7 and GoogleShits. And it booted fine, quickly. Only on HTC screen for 10 seconds maybe.
So I'm not in the same boat, though in the past I've had the same symptom with my phone. I haven't rebooted again, maybe I just got lucky.
Darch made changes to his kernel(so it boots at a higher frequency); your phone probably can't handle it then.
Bug him, jus10o, or me(tomorrow) about making a 710mhz bootable.
Decad3nce said:
Darch made changes to his kernel(so it boots at a higher frequency); your phone probably can't handle it then.
Bug him, jus10o, or me(tomorrow) about making a 710mhz bootable.
Click to expand...
Click to collapse
Thanks decad3nce. I will do just that! And thanks for the info, bohiti.
Finally some positive news!
sariamanascar said:
Thanks decad3nce. I will do just that! And thanks for the info, bohiti.
Finally some positive news!
Click to expand...
Click to collapse
I lied. it defaults at 710 on boot. But, try booting 2.6.7 with no sd card in your phone. (do a full wipe, I mean everything)
Decad3nce said:
I lied. it defaults at 710 on boot. But, try booting 2.6.7 with no sd card in your phone. (do a full wipe, I mean everything)
Click to expand...
Click to collapse
OK, just tried this two different times.
No boot loop(!) but now it just hangs on the HTC logo.
Any other ideas?
Bout to go ask Darch and jus10o for ideas....Btw, should I PM them or create a thread?
Thanks again for your help.
sariamanascar said:
OK, just tried this two different times.
No boot loop(!) but now it just hangs on the HTC logo.
Any other ideas?
Bout to go ask Darch and jus10o for ideas....Btw, should I PM them or create a thread?
Thanks again for your help.
Click to expand...
Click to collapse
already told jus10o, but feel free to pm him or Darcj anyways. one of us just needs to compile a kernel that defaults and limits itself under 710.
Decad3nce said:
already told jus10o, but feel free to pm him or Darcj anyways. one of us just needs to compile a kernel that defaults and limits itself under 710.
Click to expand...
Click to collapse
Just PM'd them myself. Thanks for the help, Dec.
Has this issue been addressed? I am having the exact same issue. I have flashed just about every rom on XDA and never had any issues, but I am having the same problem with 2.7 and Buffed2.0...both overclocked kernels. On 2.7 if I do a few battery pulls the phone somehow gets past the HTC logo but everytime I reboot i get the boot loop again.
I have never had any issues like this so I have never had to pull a log. If this would be helpful i would be glad to do it but would need directions on how to.
For all future visitors: Dec was kind enough to modify a kernel that got GPS and Wifi working for me - so thanks Dec. Problem was, GPS eventually started crapping out and I had a whole bunch of force closes over the past week. Including my phone app even crashing on me.
Today, I finally gave up on 2.7 and am on to PureHero which is largely AOSP and (for the non-OC'd version) a lot more stable. While I don't like the look as much, for those of us on weak phones, I think it's the best option.
I had the same issue, but flashed the uv kernel and it booted fine ever since. Couldn't run 2.7 till then.
stand corrected
I recently flashed the UV kernel and I have to say, everything works great. I stand corrected - no one told me the uv kernel was the same thing as "under clocking" a a kernel but I guess that's what it does. Thx.
Worked for me too
Hi just wanted to add that the UV kernel also solved my bootloop problems with DD 2.7.
A few times before the UV I was lucky, and after the 2nd or 3rd iteration of the bootloop it would get past the htc screen and boot. Happened enough times to get hooked on 2.7 haha But the last time I rebooted the phone it was very stubborn and stayed stuck no matter what I tried. That sent me searching back here. Glad I found your post, I assumed the UV kernel was only for those having battery issues, based on the main 2.7 thread.
Hello, this is my second post here though I visit this forum quite frequently.
I have a p990, and I have encountered a very strange problem with my phone:
Until yesterday, everything was normal, and every couple of weeks or so I installed a new/updated rom via CWM without any problem (usually).
Yesterday I installed the CM7 Kang from Ricardo, and this also worked well. However, when I tried to install my previous rom again (Gueste 3.1, after 3 wipes of course. The reason I didn't go back to a nandroid backup was because of problem in making the last backup) it got stuck on the 2ng LG screen. the buttons are lighted when I touch the screen, but even waiting 30 minutes doesn't change anything.
Since then, I tried to install many different roms (the latest CM7 nightly and some others), and all gave me the same problem. The only things that I've been able to do in order to boot successfully was to revert to an old backup that I had, or to install MIUI, which did work for some reason.
When I tried to install the same version of CM9 again, I always got a boot loop.
Any idea as to what could cause such a strange behavior and how can it be fixed?
Sorry for the long post, I just wanted to give as many details as possible, and I'll be happy to give more details if I can if there are things that I forgot.
Thanks,
Beorn
Beorn1 said:
Hello, this is my second post here though I visit this forum quite frequently.
I have a p990, and I have encountered a very strange problem with my phone:
Until yesterday, everything was normal, and every couple of weeks or so I installed a new/updated rom via CWM without any problem (usually).
Yesterday I installed the CM7 Kang from Ricardo, and this also worked well. However, when I tried to install my previous rom again (Gueste 3.1, after 3 wipes of course. The reason I didn't go back to a nandroid backup was because of problem in making the last backup) it got stuck on the 2ng LG screen. the buttons are lighted when I touch the screen, but even waiting 30 minutes doesn't change anything.
Since then, I tried to install many different roms (the latest CM7 nightly and some others), and all gave me the same problem. The only things that I've been able to do in order to boot successfully was to revert to an old backup that I had, or to install MIUI, which did work for some reason.
When I tried to install the same version of CM9 again, I always got a boot loop.
Any idea as to what could cause such a strange behavior and how can it be fixed?
Sorry for the long post, I just wanted to give as many details as possible, and I'll be happy to give more details if I can if there are things that I forgot.
Thanks,
Beorn
Click to expand...
Click to collapse
Try this: go to recovery > mounts and storage and wipe system, data and cache, and flash your rom.
If wiping system doesn't work neither, catch a logcat when the phone bootloops
markop90 said:
Try this: go to recovery > mounts and storage and wipe system, data and cache, and flash your rom.
If wiping system doesn't work neither, catch a logcat when the phone bootloops
Click to expand...
Click to collapse
This fixed the same issue for me.
Wiped everything and flashed CM9. Works great (but battery drain is incredible!!!)
Solved!
markop90 said:
Try this: go to recovery > mounts and storage and wipe system, data and cache, and flash your rom.
If wiping system doesn't work neither, catch a logcat when the phone bootloops
Click to expand...
Click to collapse
Thanks, I did this, and now I was able to boot again with Gueste 3.1 (I'd rather wait for a bit more stable and mature version of CM9).
Actually, I did this thing twice, and it still didn't help, and in the third time I tried to make a logcat (I'm rather new to this logcat thing), and while trying to boot and make a logcat at the same time it suddenly started workind
I just hope that it will stay good now, and that I won't have this problem again in future flashes...
Thanks!
hey guys, recently I have been experiencing a lot of crashes and other weird things.
sometimes the android gapps process or acore process would stop forcing me to reboot my phone.
the strange thing is, sometimes it will behave as if it was a first boot, so it would ask me to enter my details etc.
but after a battery pull and rebooting, it would boot normally.
however, it has also come to my knowledge that when i boot into CWM recovery, half the time it would say
"can't mount cache, etc etc etc" when it boots into it, and i cannot successfully flash on or wipe anything.
so it takes another few reboots to get it to finally work.
im on 2.02 blackrose running CWM 5.0.2.0
any ideas guys? cheers! :3
spazzy1912 said:
hey guys, recently I have been experiencing a lot of crashes and other weird things.
sometimes the android gapps process or acore process would stop forcing me to reboot my phone.
the strange thing is, sometimes it will behave as if it was a first boot, so it would ask me to enter my details etc.
but after a battery pull and rebooting, it would boot normally.
however, it has also come to my knowledge that when i boot into CWM recovery, half the time it would say
"can't mount cache, etc etc etc" when it boots into it, and i cannot successfully flash on or wipe anything.
so it takes another few reboots to get it to finally work.
im on 2.02 blackrose running CWM 5.0.2.0
any ideas guys? cheers! :3
Click to expand...
Click to collapse
My Nexus 7 just did that after I screwed around with everything in fastboot.
Try this:
\Change to 4EXT
Backup
Full wipe
Restore
My Incredible S doesn't see much screwing around any more and its still fine. I only had that problem after changing bootloaders to blackrose, then I wiped and the problem is gone
markj338 said:
My Nexus 7 just did that after I screwed around with everything in fastboot.
Try this:
\Change to 4EXT
Backup
Full wipe
Restore
My Incredible S doesn't see much screwing around any more and its still fine. I only had that problem after changing bootloaders to blackrose, then I wiped and the problem is gone
Click to expand...
Click to collapse
woops, i forgot to mention that i was on 4ext touch before and it still happened :S
it used to happen before, but not as frequently, so that is why i am a bit worried
when i get my pc back ill try reverting back to 1.13 bootloader :S
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:
hello
my phone used to work well, but after awhile, it suddenly won't boot properly (bootloop)
it's not a regular bootloop as it works very well only when on the dock and with the charger on, once i unplug the phone or the charger, it shuts off immediatly!
(no waiting, it just goes off)
I thought the battery was in fault but when I go into recovery the phone works normally without the dock
can you help?
Flash stock .ftf
dave_id said:
but after playing with some custom kernels it suddenly won't boot properly (bootloop)
Click to expand...
Click to collapse
So... you where "playing" with custom kernel, and now sadly phone doesnt work... That something really new on XDA! :]
To be honest only thing I would recommend is to revert default configuration and use backup via recovery... Because of course you made backup? Right? :]
You know, after all if you where "playing" with kernel you should have basic knowledge of "know-how" and you should know that kernel is not a puppy that you can "play with" :]
of course I made a backup! it's not the problem!
when I said "playing" it was just testing flashing kernels like zombie for exemple, nothing that special and I don't say it's the cause, it just happened after those tests.
(I'm not messing with any code in any way and I have a bit more than basic knowledge)
so I know what I''m doing, thanks for the lecture
backup or flashing a new rom doesn't help because I'm able to flash all roms that I want and install any kernel that I want, I'm even on the latest recovery.
there's something deeper happening, no matter what rom that I flash, the phone doesn't boot by itself without being on the dock(it works perfectly that way) or it can boot to recovery without the dock,
when not connected, i got bootloops, when I undock it it closes immediatly.. it's really a strange behaviour.
so I really need help on that problem!