Related
Damn near burst a vessel earlier, doods. I had downloaded the newest darchdroid, and was looking forward to some oc'd, jit-enabled, vanilla goodness. I booted into recovery, wiped everything, and tried to install. Ut oh! Got a bad download. No es bueno. But, imma careful sob, so I have like 4 nandroids sitting on my SD....2 from flipz' latest betas, 1 from the original fresh toast, and one from dc 2.0.8. And it was a damned good thing, too! The backups off the newest would NOT boot. They kept looping. I tried rewiping, nothing. No good. Finally, I tried one of the other nandroids, and It worked first try. Because I'm a curious person, I then immediately booted to recovery and tried my most recent nandroid (the first one that bootlooped). This time it worked like a charm. Consider this evidence that having more than one nandroid in storage is never a bad idea. Anyone with a clue about what might have happened, and why the nandroid wouldn't work...until suddenly it did?
dood, Nandroids are for pansies.
Maybe it has a bad temper, too.
-------------------------------------
Sent from your mom!
@Kcarpenter- Well, paint me pink and stick me in a pot! (i was gonna make a joke about your wife and my root, but in this current climate, it prolly would have gotten me banned for being off topic in my own thread)
@jerry- you're prolly right. I know it has my sense of humor, cause it keeps effing with me when I'm drunk....
Same experience
I tried to make a nand of darch and when it failed I tried to restore my last nand of my last rom and almost "oops_I_crapped_my_pants" when it failed too
Fortunately an older nand worked
So I just had to try darchdroid again and its nanding just fine . I probably wont stick with it fo eva but it is fast as crap after eating liquid dish soap.
btw, did you happen to see the very last stock wallpaper in darchdroid?? HOMINA HOMINA HOMINA. So hot, want to touch the hiney.. awwooooooo
phenicks said:
Same experience
I tried to make a nand of darch and when it failed I tried to restore my last nand of my last rom and almost "oops_I_crapped_my_pants" when it failed too
Fortunately an older nand worked
So I just had to try darchdroid again and its nanding just fine . I probably wont stick with it fo eva but it is fast as crap after eating liquid dish soap.
btw, did you happen to see the very last stock wallpaper in darchdroid?? HOMINA HOMINA HOMINA. So hot, want to touch the hiney.. awwooooooo
Click to expand...
Click to collapse
Na. I had a totally bad download. It never even finished installing. I'll try it again this afternoon, when I'm near a computer.
I am not sure if this will help, but I had a loop problem and I noticed it started when I installed an app. This was in my nandroid back up. If you boot, it will go into loop.
Through adb start removing programs in the /system/app/. I ended up removing the program (apk and/or odex) and it stopped the loop without rebooting. Not sure why it did this.
Once you find the program that may cause this, restore your nandroid and only remove that apk or odex.
Just try it and see if this works.
you should wipe and clear data before nandroiding back. probably why you had a boot loop. With recovery theres no reason why you cant take 5 seconds and wipe everything before nandroid. If you did do a wipe and clear data before hand then my sincere apologies.
Yeah, I rewiped MULTIPLE times (each time I tried to nandroid recover, so, like, 6 times or so). Thanks, though.
Hey I would have posted this on a different thread but i cant because i just made this account they want atleast 10 posts...
heres the deal... i have a rooted evo and running cm7 which i like, but i was dropping calls and where i live i should have good service. so i got the updated radio/wifi/ ect package and flashed it... it installed but did not help with the call issue... i heard many other having the same problem.
so i flashed the ota root update... which seemed like it did it really fast (wasnt watching the whole time) and the phone rebooted but gets stuck at the white htc evo screen, i let it sit there for 20 mins nothing, so right now i am recovering my old cm7... just wondering if anyone has that same problem or can help with getting better voice reception on cm7.. like i said i have tried the package for radio ect... and my prl was updated before i flashed to stable of cm7 so that should be in good standing i would imagine... thanks..
The obvious first question is, did you do a full and complete wipe of everything before you flashed the ROM?
As far as your signal, it may have been just in my area, but I know a few people that had problems texting and making calls, getting a "Network Is busy" error.
yea i did the wipe data/cache i wasnt dropping calls before the cm7 so im not sure right now im shootin to myns seeing how that is... cm7 was first flash i did
well as im trying to flash to the myns its looking like the samething... ill go through the steps...
have zip file in root of sd card
open up rom manager, have the newest clockwork thing installed
i goto flash from sd wipe data and cache are checked... i already have a backup so i skip that part
it installs.... says install is done and reboots itself... but seems to stay on that white bootscreen
if i take the battery out then i can reboot with recovery from the save file i have
blah i dont know... i got the ota installed... looked like it got a bit better reception.. i updated prl and came back to cm7 same probs... i dunno maybe ill just have to let go of cm7... really dont want to though its so sexy lol
I had the same weak signal issue with cm7 and had dropped calls and data dropping to 1x. I am on stock rooted 2.3.3 and reception is good again. Liked cm7 but need a phone I can use in the boonies.
Sent from my PC36100 using XDA Premium App
Dude, please, don't use ROM Manger.
Just boot to recovery, hopefully, you have Amon Ra, if not, search how to get it on your phone, it's not hard, do a FULL WIPE, full, wipe everything in recovery, then flash the ROM in recovery.
No offense to the Dev, I know he's a great guy, a smart guy, hard worker that makes a contribution, but Rom Manager is not the best way to do this.
Yea had to do it manually but nymph works now liking it so far
ok now i have different problem.... got the myn working liking it, but my market is completely different, not just the theme, but the apps i usually download... so tried to flash new market but it just open/closes quickly... any ideas for that?
Not sure by what you mean by the apps you usually d/l.
One thing about the Market in these newer ROMS is that sometimes, you just need to give it some time to fully sync before all your apps so up...
You should pull the market out of the zip file for the ROM and re-install that one, but you'll have to delete the one you have installed now, first.
umm usually download ninjump cant find that just some games that are usually on my phone the market on cm7 had them... ill give it a try though
look on the android market website
Check progress in DEV section http://forum.xda-developers.com/showthread.php?t=1562595
( I have posted less than 10 posts, so I can't write in the dev section. )
Stupid question : is it using Holo?
And, if it is based on CM9, it is rooted, isn't it?
If WiFi works, I'm SURELY going to try this!
I installed it yesterday. Wifi works, it uses Holo, hat root and performs better than I expected.
Thx.
I' ve put it on. It's really laggy, but it works!
It's a good start, but if this is the best performance the legend can give, I think I won't ever change definitevly to ICS. Maybe it can be optimizated for the Legend hardware to become smoother.
Thanks for testing, but it has not got hardware acceleration yet. For testing purpose, you could overclock it up to 787 MHZ safely, and the overall performance get better notably.
/=\lex said:
Thx.
I' ve put it on. It's really laggy, but it works!
It's a good start, but if this is the best performance the legend can give, I think I won't ever change definitevly to ICS. Maybe it can be optimizated for the Legend hardware to become smoother.
Click to expand...
Click to collapse
Yea is pretty smooth overall eventhough hardware aceleration is not working, this port looks really promising,
Tried it yesterday and in My view its the smoothest ics ROM ever tested.i had some fcs but will try Tor correct rights via rommanager.if GPS is working i will use this one.its a must Have for me.
Sent from my Legend using XDA
Thanks for testing, but it has not got hardware acceleration yet. For testing purpose, you could overclock it up to 787 MHZ safely, and the overall performance get better notably.
Click to expand...
Click to collapse
I'll try keeping it on for more time. By my first impression, it doesn't look so buggy, I think it is also quite stable. I'll tell you if I find anything.
Anyway, this is a great ROM, thanks for your work!
EDIT : Stupid question : to install GApps I have to flash the zip, right?
EDIT 2x : Yea, it was a very stupid question. Flashed from clockwork recovery. Works perfectly.
Its getting better and better. but still GPS not working. Hope you get it fixed soon.
Realy great job!!!!!
really good job. Just need GPS and Camera.
Hoping for 2.5 soon...also hoping based on Android 4.0.4.
How is work going?
Sent from my Legend using XDA
I have a problem with the latest 3.0 version.
After i flash gapps i keep getting boot loops.
If i dont flash it and just flash the rom it boots fine.
Dont know what the problem is. Can someone help me?
I have the exact same problem as DareFace, but I think zeubea is aware of the problem.
zeubea-cm-9.0.0-ALPHA3.0.1 and Google Apps
I tried install this ROM multiple times today, everything works until i install gapps (full or tiny). After that phone enters infinite boot-loop (HTC logo on white background).
Radio 7.13.35.05
Bootloader HBOOT-1.01 (S-ON)
ClockworkMod Recovery 5.0.2.0
Edited @ 08:31PM GMT+2
After installing gapps over gapps works as a charm. That's weird...
I had the same bootloop problem until I installed another kernel that Zeubea provided. It's till get some fc's, mainly for clock and email, but the email still works, clock is inaccessible atm.
It's even better than cm 7.2RC1, running oc'ed at 787mhz ! It's so smooth and beautiful. Let's hope that the gps and camera will get fixed soon. If I had capabilities to donate, I so would do it.
Thanks Zeubea! The Legend community loves you, keep up the wonderful work of making our ICS dreams come true when htc can't and won't deliver.
The reason for bootlooping is the clock issue.
The default clock in 3.0.0 is 806MHz - something every Legend doesn't handle, so it bootloops.
The 3.0.1 version has this "problem" fixed.
I faced another issue releted to sounds. I change both ring and notification sounds and after some time i realise that they are reverted to default!
I have this weird thing where the danish keyboard force-closes.
It's everytime i type the word "lige". It doesn't do it with the english keyboard
I've tried to turn off the spelling correction, since it's in english, and there isn't a danish one, but it doesn't help.
Other than that it's great
bootlooping after flashing cm9 gapps, possible fix
boots up normally after flashing the zip in CWM, but after flashing gapps it bootloops, and after awhile of countless flashing i discovered it bootloops even before flashing gapps, so i tried different step to flash it and finally it boots up normally, here's what i did :
1) full wipe, dalvik cache and cache partition, factory reset
2) flash the main cm9 zip
3) full wipe, dalvik cache and cache partition, factory reset (again)
4) flash gapps (not tiny version)
5) reboot, if it boots up normally thats great, if not its ok, continue to step 6
6) boot into CWM
7) dont wipe or anything*
8) flash the main cm9 zip
9) instead of rebooting device, continue by just flashing gapps (not tiny version)
this were the steps i did to fix the bootloops after flashing gapps, apparently the gapps tiny version is not compatible with cm9 on the htc legend thats why i stick to the normal gapps file, i hope this helps anyone of u experiencing the bootloops after flashing gapps
I have some kind of problem with wifi connection. If "Keep Wi-Fi on during sleep" is set to "Only when plugged in". After I wake up phone wifi is turned on it cannot find any networks.
EDIT: Logcat trimmed to "network|wifi|power|conectivity" http://pastebin.com/pdUAbfDy
And terminal emulator displays an error "Unfortunately, Terminal Emulator has stopped" when I try to open it.
EDIT: Logcat http://pastebin.com/ChRUu3jS
its been like that on my A500 since i installed Taboonay 3.01, and hasn't managed to fix itself even now i'm running the latest 4.1.1 CM10.
Everything else pretty much works. When i switch to camera, i just get green static with occasional pink horizontal stripes, then it just locks up and either the A500 resets, or i have to home-screen.
Any ideas on how to fix?
jnktechstuff said:
MOD : EDIT
try dleeting you who system, except your recovery , there should be a system whipe that should work, then reflash ur rom
Click to expand...
Click to collapse
hmm, i already dId a system wipe/reset from CWM recovery (all local data gone, just ext SD card remaining) when i applied CM10?
ps. One thing i noticed last night testing was that if i switch the camera to front-facing, it works. But rear-facing (main) no-go..
yeatsie said:
hmm, i already dId a system wipe/reset from CWM recovery (all local data gone, just ext SD card remaining) when i applied CM10?
ps. One thing i noticed last night testing was that if i switch the camera to front-facing, it works. But rear-facing (main) no-go..
Click to expand...
Click to collapse
check you camera connector. It may come lose from the motherboard. Try reseat the connector.
Sent from my A500 using Tapatalk
.
opened up the A500 last night - all looked good, all connectors in place, nothing obviously wrong?
Noticed the screen when i switch to the rear camera has artifacts from other screens in the background (ie Pulse app title heading etc) suggesting some kind of software glitch?
yeatsie said:
its been like that on my A500 since i installed Taboonay 3.01, and hasn't managed to fix itself even now i'm running the latest 4.1.1 CM10.
Everything else pretty much works. When i switch to camera, i just get green static with occasional pink horizontal stripes, then it just locks up and either the A500 resets, or i have to home-screen.
Any ideas on how to fix?
Click to expand...
Click to collapse
Known issue in the CM10 alpha test ROM. You should go to the one in general rather than making your own thread which WayDownSouth is unlikely to see.
http://forum.xda-developers.com/showthread.php?t=1789711
yeatsie said:
its been like that on my A500 since i installed Taboonay 3.01, and hasn't managed to fix itself even now i'm running the latest 4.1.1 CM10.
Everything else pretty much works. When i switch to camera, i just get green static with occasional pink horizontal stripes, then it just locks up and either the A500 resets, or i have to home-screen.
Any ideas on how to fix?
Click to expand...
Click to collapse
There.s really only 2 things it can be;
1. Dirty code.
2. Bad camera.
The camera is not like a radio, you can't update internal drivers like a firmware boot. So that only leaves the software side.
First off, which recovery system are you using? CWM, Public, TWP? And which specific version?
I will guess you are on ICS unlocked bootloader also? Version 4-8?
MD
Moscow Desire said:
There.s really only 2 things it can be;
1. Dirty code.
2. Bad camera.
The camera is not like a radio, you can't update internal drivers like a firmware boot. So that only leaves the software side.
First off, which recovery system are you using? CWM, Public, TWP? And which specific version?
I will guess you are on ICS unlocked bootloader also? Version 4-8?
MD
Click to expand...
Click to collapse
It started on ICS 4.03 (Taboonay) and its unlocked CWM bootloader (cant remember the version, maybe 3) and still present on latest CM 10 20120821 and unlocked ICS CWM v6 recovery bootloader.
yeatsie said:
It started on ICS 4.03 (Taboonay) and its unlocked CWM bootloader (cant remember the version, maybe 3) and still present on latest CM 10 20120821 and unlocked ICS CWM v6 recovery bootloader.
Click to expand...
Click to collapse
Well, maybe something with your recovery version (some of them were a little flakey) so you should boot to CWM and just check the version. Currently I use rev 1.7.2 of CWM. Some of the previous versions seemed didn't wipe data very well.
Bootloader version is Fine. Anything above ver4 is great.
Double check your CWM and if it needs updated, I would go ahead and do it. Just remember to make a new recovery backup after updating (just in case it doesn't read the older ones). I really don't think it's a hardware issue. If it is, it was just bad timing.
The camera drivers are pretty much the same more or less. They either work, or they don't, and it's not often cameras mess up. They do, but it's pretty rare I think.
When you install a rom, of course you should always do the following;
Wipes
a. User Data/Factory Reset
b. Cache
c. Dalvik Cache
d. Battery Stats (optional)
Mounts and Storage
a. Format System
b. Format Flexrom
This, with the newer CWM, should effectively clean the partitions of previous data.
Hope it takes care of the camera issue. Follow the above, re-install a rom. Try one of Civato's Flex roms. No camera issues reported there. Check it BEFORE installing any apps. And if you use Titanium Back-up, Check the camera FIRST BEFORE trying to restore any old data.
MD
Moscow Desire said:
Well, maybe something with your recovery version (some of them were a little flakey) so you should boot to CWM and just check the version. Currently I use rev 1.7.2 of CWM. Some of the previous versions seemed didn't wipe data very well.
Bootloader version is Fine. Anything above ver4 is great.
Double check your CWM and if it needs updated, I would go ahead and do it. Just remember to make a new recovery backup after updating (just in case it doesn't read the older ones). I really don't think it's a hardware issue. If it is, it was just bad timing.
The camera drivers are pretty much the same more or less. They either work, or they don't, and it's not often cameras mess up. They do, but it's pretty rare I think.
When you install a rom, of course you should always do the following;
Wipes
a. User Data/Factory Reset
b. Cache
c. Dalvik Cache
d. Battery Stats (optional)
Mounts and Storage
a. Format System
b. Format Flexrom
This, with the newer CWM, should effectively clean the partitions of previous data.
Hope it takes care of the camera issue. Follow the above, re-install a rom. Try one of Civato's Flex roms. No camera issues reported there. Check it BEFORE installing any apps. And if you use Titanium Back-up, Check the camera FIRST BEFORE trying to restore any old data.
MD
Click to expand...
Click to collapse
Cheers, i did as you listed with the wipes. Just checked, im on CWM 1.7.3. The bootloader is part of that right?
Will try the Flex ROM you mention and see if helps..
yeatsie said:
Cheers, i did as you listed with the wipes. Just checked, im on CWM 1.7.3. The bootloader is part of that right?
Will try the Flex ROM you mention and see if helps..
Click to expand...
Click to collapse
Boot loader is different from cwm recovery. When you boot, it should say in white text.
If in doubt, run Acer recovery installer from the market. It will tell you which version.
MD
ok, just installed the Acer app from market, it says bootloader is 0.03.14-MUL .
And when I boot up, it says Skrilaxcz boot loader v8.
Sent from my GT-I9100 using xda app-developers app
I have always had this intermittent problem on my a500. I have always used the stock ROM since I purchased it, and it's been the same since each OTA upgrade, so I doubt that it's a problem inherent to one custom ROM or the other.
A Dalvik cache clean has never worked for me, sometimes a restart has helped, but more often than not it doesn't help.
If someone discovers a set of steps that fixes this problem every time it occurs, I would be glad to hear of it.
yeatsie said:
ok, just installed the Acer app from market, it says bootloader is 0.03.14-MUL .
And when I boot up, it says Skrilaxcz boot loader v8.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Hi, What was your final solution to this problem? I'm trying to fix mine right now.
-Thanks-
No fix as yet, pretty much gave up trying to use the camera.
Sent from my Nexus 7 using Tapatalk 2
If anyone else's having this problem with ONE OF THE CAMERAS (Not both of them but frontal OR main) then this should be the solution:
Watch this video someone uploaded https://www.youtube.com/watch?v=Cjevl8I6rIA but HAVE THIS IN MIND:
That cord (FLEX) he's talking about is for the FRONTAL camera. Not related with the main or back camera. So that should fix the green trouble for the frontal one.
But, if the main camera shows green image or weird lines, that's likely because its connector is not correctly attached to the main board. That connector is NOT a flex, but it's a built in block in the board of the same camera unit. You need to remove or lift the main board, totally remove the main camera unit, clean the connector (both male and female) with alcohol and connect it again applying some pressure. If the trouble really was the connector not being correctly placed, that totally fixes it.
If it worked, let me know
That totally worked and fixed my green screen camera problem, thanks! (was a total pain to re-seat the camera but worth it)
I just bought a Nook Color and installed CM9 on it. The bottom where it displays the notification and wireless signal is gone. Also every 5 seconds is force closing everything. Apollo looks cool but I cant check it out mainly cause itll force close it. N i forgot to add it FREEZES! Can anyone tell me if I downloaded the wrong thing n have to re install or just forget it. N if i have to re flash please give me the WORKING links n directions THANKS!!!
BennyP86 said:
I just bought a Nook Color and installed CM9 on it. The bottom where it displays the notification and wireless signal is gone. Also every 5 seconds is force closing everything. Apollo looks cool but I cant check it out mainly cause itll force close it. N i forgot to add it FREEZES! Can anyone tell me if I downloaded the wrong thing n have to re install or just forget it. N if i have to re flash please give me the WORKING links n directions THANKS!!!
Click to expand...
Click to collapse
How did you install it? To SD or internal memory. And which version of CM9 are you using? Opengl or non-opengl?
If you installed to internal memory, did you factory reset via CWM first? You need to if coming from stock. You can still do it now.
If you installed to SD, what class SD card are you using? It should be a Sandisk class 4.
Your download isn't broken. CM9 on the NC is - it isn't really *done* yet on the Nook Color. Developers are working on it, but for now your best bet is CM7.2. I expect we might hear an announcement very soon, but for now, use CM7.2.
It's obvious that the installation of this person has problems.
CM9 DOESNT have this kind of problems. It might be a bit slower in hardware acceleration matters in comparison to CM7, but it sure works fine in all other matters.
It's quite mature by now.
Produced by NookColor at ICS AOKP 4.0.4
BennyP86 said:
I just bought a Nook Color and installed CM9 on it. The bottom where it displays the notification and wireless signal is gone. Also every 5 seconds is force closing everything. Apollo looks cool but I cant check it out mainly cause itll force close it. N i forgot to add it FREEZES! Can anyone tell me if I downloaded the wrong thing n have to re install or just forget it. N if i have to re flash please give me the WORKING links n directions THANKS!!!
Click to expand...
Click to collapse
What did you download?
Edit: Forget it. LeapinLar already asked all the pertinent questions.
I'm having similar issues as well. It's kind of sluggish and it has frozen a few times already. I downloaded the nightly by Eyeballer over at Techerrata: cm-9-encore-20120904-0700-unofficial.zip.
In the instructions over at Androidforums does say that it might be sluggish the first few days so I guess I will just have to wait it out. I did just install about roughly 12 hours ago.
I just installed today, over my CM7.2 install in internal memory. It seemed okay at first, though a bit sluggish. But then I re-booted it and now it is acting possessed. Apps are launching by themselves (Play Store, a notepad app I had installed, voice command window, etc.) Very odd. I've shut it down and re-booted, same thing. I am thinking of maybe doing a complete fresh install from a SD card, wiping out all my apps from 7.2 and see if that helps at all. Or, I made a backup of my 7.2 install from CWM before installing CM9, so can always go back to that.
Just to follow up on my previous post: My NC running CM9 (latest GL version) did stabilize quite a bit after a day or so. But it still is very sluggish at times, to respond to screen touches, opening apps, and even loading webpages. I ran the Quadrant benchmark tool and the results are slightly lower than I got with CM7.2, but not terribly so. I'm debating whether to go back to 7.2, or do a factory reset and try a fresh install of CM9 and see if that's any better? Is there any evidence that a fresh install will work better than updating over a installed 7.2?
It's total mistake to update CM9 over Cm7 or any other different system.
To be able to talk about how things should be, you need to do a clean install and then for sure things will be better.
Powered by my IceCold 8.6.1 DHD
RASTAVIPER said:
It's total mistake to update CM9 over Cm7 or any other different system.
To be able to talk about how things should be, you need to do a clean install and then for sure things will be better.
Powered by my IceCold 8.6.1 DHD
Click to expand...
Click to collapse
Wow, that made a world of difference! Thanks. I thought I'd read somewhere else that it was okay to update from CM7 to CM9.