Hi,
For some reason in rommanager I can only see up to #13 for the cyanogenmod nightlies?
Does anyone else have this problem?
The reason I bought the paid version was to get access to all of them.
Thanks
Paul
Well you got ripped off because Rom Manager is ****. Seriously, you should NEVER flash anything with Rom Manager or have it installed at that. Just download it from CyanogenMod, put it on your SD and install it via recovery.
Rom manager does what it is supposed to do and does it well.
The reason you do not see anymore nightlies is because there are no more. The nightlies got reset after RC1 was released. There isn't a new njghtly every night because sometimes there is no successful build.
Rom Manager does everything really poorly, seriously. It is useless and causes so many problems.
Meaple said:
Rom Manager does everything really poorly, seriously. It is useless and causes so many problems.
Click to expand...
Click to collapse
Care to elaborate?
Sent from my HTC Desire using Tapatalk
The main issue(s) is when you reboot. Say you flash a rom, when you reboot it tends to just reboot and not flash the rom or anything. It does stuff like that. Rom Manager tries to be the recovery but whilst booted up but fails. Fair enough, it works for some people but so many other people have problems with it. Ok, it has been developed for "noobs" and yes, I did kind of use it at first but then I found out from my own experience it didn't work too well. I think that people should forget about Rom Manager and just boot up into recovery and just use that since the recovery actually works, and only takes a reboot (depending on your rom) to get into it.
Why, do you like it?
I've noticed same issue with the nightly. I've tried manually flashing the newer ones, but get an error on the device check. So rom manager is correct 13 or RC2 are the latest that will install
Sent from my HTC Desire using XDA Premium App
Am a bit of a newbie to the custom rom world. So far rom manager has worked fine.
Am currently on cyanogen rc2 and have flashed my radio without problems. As a Java developer and a phone geek people think I am mad for mucking about with my phone so much.
The question was because I thought I had read there was a nightly 15.
Sent from my Desire HD using XDA App
I have had the same issue with Rom Manager. I had to download directly from the Cyanogenmod site
Just flashed 17 and it seems to be really fast!
http://mirror.kanged.net/nightly/bravo/
or directly to 17
http://mirror.kanged.net/nightly/bravo/cm_bravo_full-17.zip
Cheers
Which desire do you have GSM or cdma?
Sent from my HTC Desire using XDA Premium App
Uk desire HD gsm
Sent from my Desire HD using XDA App
That version worked for me thanks
Sent from my HTC Desire using XDA Premium App
Just realised, that is the bravo version, cyanogen points xemacs desires to bravoc. Still seems to be working fine
Sent from my HTC Desire using XDA Premium App
I don't know if it's related, but I had trouble with CM7 RC2 when installed through ROM Manager, but manually flashing the CM7 Nightly #17 worked just fine. I wiped the caches etc. on both tries (or rather, ROM Manager did on the RC2).
I've been using cm7 pretty much since I got my g2, but recent problems with gps caused me to look for other options.. so within the latest clockwork recovery I wiped data and cache for cm7 and flashed the latest miui rom. When I decided to go back to cm7 I wiped everything like before and flashed the rc2 rom. Even after repeated flashing I can not get the bootloops to stop. Right now I'm running cm6.1.1 with no problems.. but I would really like to find a way to bet back to 7.
Sent from my HTC Vision using XDA App
Yeah for some reason when I go yo use my camcorder it freezes. Is the there a fix for it. I'm running cm7 7.0.2.
Dinc
Upgrade to 7.0.3 or the newest nightly.
Sent from my ADR6300 using XDA App
7.3 better
Dinc
Do I have to do a full wipe to install the 7.0.3. If I'm on the 7.0.2.
Dinc
They say you don't have to when updating between versions of CM7 (whether it be stable releases or nightlys). I always make it a practice to do a full wipe data/cache/dalvik cache when switching ROMs. It's generally just a good practice to get yourself into to avoid having strange quirky issues like you're experiencing.
I have seen multiple users here and on Rootzwiki state that they can't run AOSP ROMS. All the users can run a Sense ROM with no problem, but as soon as they load an AOSP ROM they get freezes.
Edit:
In recovery, be sure to do a full wipe of data, cache, and dalvik cache. It is also recommended that you format your system partition as well. Then install ROM.
If you choose to format the SD card, be sure to back up your important files first.
If you still experience problems running AOSP ROMs (CM7, Liquid, OMFGB, Pool Party) share your results.
i was tested different rom's and i've never had an issue flashing AOSP roms. I flashed a few ruu and sense rom.
sjpritch25 said:
i was tested different rom's and i've never had an issue flashing AOSP roms. I flashed a few ruu and sense rom.
Click to expand...
Click to collapse
I haven't had the issue myself, but I've seen a handful that have. No one has figured it out yet.
Edit: if you experienced this it may help to figure it out
JAS_21 said:
I haven't had the issue myself, but I've seen a handful that have. No one has figured it out yet.
Click to expand...
Click to collapse
Its a myth.
I don't see a reason why it wouldn't work.
Sent from my Incredible 2 using xda premium
xHoLyx said:
Its a myth.
I don't see a reason why it wouldn't work.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
I've seen more than one user with the issue. One is a long time forum member.
xHoLyx said:
Its a myth.
I don't see a reason why it wouldn't work.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Definitely not a myth. I had issues with aosp roms not mounting data or cache properly. However, newest cyanogen fixed it. Were trying to figure out where the problem stemmed from
I am having this issue. I was actually running CM7 nightly (with Tiamat) when the problem started. I plugged my phone into my stereo before I went to bed and listened to an album. When I woke up, the screen would not turn on. I rebooted and was stuck in boot loop. I tried to wipe the caches, but got stuck in boot loop. I then upgraded to the most current nightly (with a full wipe), but the phone suffered from the sluggish performance and screen issue.
I have flashed just about every ROM listed in the dev section. Prior to having the issue, I was running MIUI. Prior to that, I was running Newts Incredible 2 HD.
I do NOT have this issue with TSM Pool Party or the past week or so of CM7 nightlies.
I do have this issue with the AOSP Liquid Rom, OMGB, OMFGB.
All sense ROMS work.
I was running andrev_oc when this happened. No overclocking, but did have screen on and screen off profiles.
I have attempted to flash with CWM and 4ext recoveries. Even when converted to ext4, I still have the issue.
Sorry for all the info. I just tried to give as much detail as possible.
Hope this helps,
Matt
Thank you. If anyone else is having, or had this issue let us know what ROM you noticed the issue on, and what you were running prior.
Also, if anyone has a fix it can be posted here.
I have seen this as well. It happened to me when I flash 9.30 MIUI because I was bored. The next morning I restored my cm7 backup and it worked just fine until the screen went off and I would have to pull the battery to boot it back up. Did this several times until I remembered seeing this issue. After several wipes and restores the problem stayed. I finially just flashed a nightly #91 believe I was on 87 before and it has worked fine since. Not sure what was the problem or why it worked flashing a different nightly but I was glad it did.
dch921 said:
I have seen this as well. It happened to me when I flash 9.30 MIUI because I was bored. The next morning I restored my cm7 backup and it worked just fine until the screen went off and I would have to pull the battery to boot it back up. Did this several times until I remembered seeing this issue. After several wipes and restores the problem stayed. I finially just flashed a nightly #91 believe I was on 87 before and it has worked fine since. Not sure what was the problem or why it worked flashing a different nightly but I was glad it did.
Click to expand...
Click to collapse
Were you running a sense ROM before Miui?
I switched from newts Inc hd to liquid, and I had all kinds of problems with the SD card not mounting properly. I ran miui a long time ago with no problems.
Sent from my mobile typewriter.
Went from newts hd to liquid as well, tried restoring my cm7 backup and ran into lockups, reboots, and data lose. Any possibility liquid rom is behind this somehow indirectly? No shot at liquid, just maybe some corrupt files?
Sent from my Incredible 2 HD using xda premium
ftmaniac948 said:
Went from newts hd to liquid as well, tried restoring my cm7 backup and ran into lockups, reboots, and data lose. Any possibility liquid rom is behind this somehow indirectly? No shot at liquid, just maybe some corrupt files?
Sent from my Incredible 2 HD using xda premium
Click to expand...
Click to collapse
No, other AOSP ROMs were having same problem. It seems that data and cache don't mount properly after running certain ROMS.
It's starting to look like everyone that had problems with AOSP lockups had been running Inc2 HD prior. I'm not saying Newts ROM caused the issue, since I don't know the cause, but hopefully this can help someone to figure out the problem
Is there a fix? I am running liquid now with no problem. If the system doesn't mount properly when I try to switch, can I just wipe or format system and try to restore a backup or load another rom?
stelv said:
Is there a fix? I am running liquid now with no problem. If the system doesn't mount properly when I try to switch, can I just wipe or format system and try to restore a backup or load another rom?
Click to expand...
Click to collapse
No, you should be fine.
Most people have no problems. This is for people experiencing random lockups and freezes, not just wit Liquid, but other AOSP ROMs also
JAS_21 said:
It's starting to look like everyone that had problems with AOSP lockups had been running Inc2 HD prior. I'm not saying Newts ROM caused the issue, since I don't know the cause, but hopefully this can help someone to figure out the problem
Click to expand...
Click to collapse
Iv been using newts hd rom for a long time now, and never experienced problems with it before
Sent from my Incredible 2 HD using xda premium
For me it was data and cache that didn't mount properly. But try the newest cyanogen and see, its the only one that worked for me
ftmaniac948 said:
Iv been using newts hd rom for a long time now, and never experienced problems with it before
Sent from my Incredible 2 HD using xda premium
Click to expand...
Click to collapse
I'm not saying that his ROM isn't running right, but it seems that people are having issues going from that ROM to an AOSP ROM.
Edit: There may be nothing wrong with his ROM, but maybe something is being left behind or not formatted after flashing the AOSP ROM.
Could Newts rom being formatted to Ext4 cause issues when flashing back to a Aosp rom? I've ran Newts Inc2HD and flashed back to Omfgb, but I've been using Ext4 for a while now for my system/data/cache file system (since switching to 4ext recovery). After flashing back, my Aosp rom ran fine. But my backup of Omfgb was already formatted to run on Ext4. Now if my backup was formatted to run on Ext3 for the data/cache, I would think this may cause issues if I don't reformat before flashing a new rom... Just a thought anyway.
I'm using preludedrews latest Ics rom (p3) and youtube is not on the gapps I flashed nor on the market. Anyone else have this issue? How can I get youtube back?
I'm running ics on my evo as well. No problems, but if you don't wipe your data, cache and dalvik before installing your gapps you will be missing important parts of your install like youtube.
Sent from my PC36100 using XDA Premium App
I see. I flashed calkulins format all before flashing the actual rom. But i always forget to flash gapps so after it booted i just went back and flashed it without wiping anything. So thanks ill try that
I think youtube does not work because it needs adobe flash and adobe flash does not support ics yet but it will soon.
Here's a good version of gapps includes latest everything
Edit:
http://db.tt/ojWqxSho
Sent from my PC36100 using XDA App