I think i've just got my head around ROMs and all the other millions of acronyms. I do like the look of the Oxygen ROM, only i'm not a fan of the green icons in the status bar, is the colour changeable, and does anyone suggest Oxygen as a good ROM to flash for a first timer?
I must add i love the dark bar and prefer having a dark background, so silver/bright etc task bars are a no no
Cheers.
Oxygen is a great ROM, but i would reccomend u go for a froyo rom first so u got more options with themes and such. but rly its a matter of taste and what u want .. stability or experimental.
Experimental: CyanogenMod 7
Stable: eMIUI, Oxygen 1.0.4
Sense roms?
Hmm im using Sense HD port now, since everything works. its stable¨
im using InsertCoin with my own tweaks and theme
u can allways check out my FroSTeD GingerBread theme for Oxygen 1.0.4^^
Rom and theme here
BUT, if u decide to go for a Android 2.3 Rom i rly recommend CM 7, Oxygen 2 RC7 is just as good but less theming options i think.
Heres a nice theme for CM7 Rom
Clicky
I tried the insert coin 1.8 and got caught in a never ending bootloop lol.
I have Leedroid 2.3d A2SD. It's slick and stable and had no issues with it.
grentuu said:
I tried the insert coin 1.8 and got caught in a never ending bootloop lol.
I have Leedroid 2.3d A2SD. It's slick and stable and had no issues with it.
Click to expand...
Click to collapse
then u did not do it right. read the whole first page. then u can complain if u did everything 100%. ive not had 1 single rom on bootloop. to get insertcoin to work u need EXT 4 partition with 1gb recommended. its not hard if u actually read what to do istead of just trying the easy way like Leedroid is. and leedroid was boring and old news
Well im now running on Oxygen 2.3.2 which is really nice.
However...i keep getting a message saying "The application settings (android.process.media) has stopped unexpectadly. Please try again"
This is ALWAYS the case when i choose the "sound" option from the settings menu.
Can anyone shed any light on this?
It means you didn't wipe properly before installing the rom. Boot in to recovery and wipe cache and dalvik cache (under advanced) start up and see if the problem persists, if yes you need to do a full wipe(data/factory reset, cache and dalvik cache).
Shall give it a go. Odd seeing as i did wipe it all before 0_0
Also, i assume if i factory reset, is that from the recovery menu, and then re install the ROM?
Yes, all wipes from recovery and then reflash the rom. Keep in mind all the data on the phone will be gone.
Exactly the same problem...i'm using Launcher Pro Plus if that's any help.
This is precisely why i've put off flashing ROMs for this long, to prevent naffing up my phone, and now
Well if you don't want any issues I don't understand why you would install a RC, also I'm pretty sure the fc is not a rom issue but a user issue.
If you did everything correctly you should have a normal functioning rom (except form the know issues), even with launcher pro plus cause i have the same setup.
Have you ever disabled signature verification? If yes there is a small chance your issues are caused by a corrupted zip file.
If you can't get oxygen to work and want a really stable custom rom use Leedroid. If you are done with rooting and custom rom's just run the latest RUU.
Thanks for the quick reply, where can i access the lastest RUUs to flash them from please? I may well try again at a later date, but it seems too much hassle currently with having to reset and change everything *sigh*
I've just reset to the last point using Nandroid before i flashed the ROM. I've still got root access which is good, but everything runs back to normal now.
A brief foray into the murky waters lol!
mrfish123,
Pretty sure I know what is causing your problem as I recently resolved this issue myself. If I'm right you did a full wipe before installing, but the issues started after restoring your apps (titanium backup?).
What I was doing was wiping and then restoring all apps with data. Lots of these are system settings/apps which come from the old ROM, so in effect you re restoring all the stuff you wiped in the first place.
What you need to do is:
Wipe (system wipe from recovery, and do the chache and dalvik cache too for good measure).
Install ROM
In Titanium select 'restore missing apps with data', but before you run it, go through the list and uncheck absolutely everything which is not obviously an app you have installed yourself, so anything HTC, system etc. You only want to restore your apps.
Once I did this I had no issue installing a custom ROM, and have had no problems running it for over a week.
auraxsense!
Redux-RC2.1 (Gingerbread 2.3.2) highly recommended - smooth and fast
http://forum.xda-developers.com/showthread.php?t=896213
running leedroid atm, so far everything seems nice
Related
For two months I have tried to install Cm6 and currently shadow rom. Every time after install from clockwork or nandroid I get the same bootloop splash htc screen. I have installed other roms with no problem....there must be a common issue with cm6 & shadowrom. I have wiped full, cache, davlik and even formated system cache etc. I have a 2.x radio kouche kernel and newest hboot. I've tried changing sd cards etc. No avail......any suggestions would be appreciated.
SamuraiXDroid
I would try wiping dalvik/cache before the flash, flashing, then wiping dalvik/cache again before the first boot of the new rom. I would also suggest trying kings kernel or koush's test kernel by flashing them from cwm recovery directly after the rom.
Aside from that, I could only guess that you might have a corrupt area preventing a full install of your rom/kernel which isn't too uncommon but which I have no experience with. I've heard there are ways to get around this by building the kernel manually or by restoring it from another nandroid (say king's on a ruby nandroid? though I'd venture to guess Ruby would have the same problem), but it seems fairly difficult.
I'm not a developer, but I hope my suggestions can hope point you in the right direction. I'm using the latest nightlies of CM6 and they are awesome. I hope you get the chance to try it.
Thanks jaguox for such a quick reply. So I tried this.method on both cm6 and shadowrom. Wiped full wiped cache wiped davlik. Installed rom and gapp and kernel. Tried koush and kingkernal....wiped davlik...cm6 boot loop.....shadowrom brings me to android touch screen initial setup. I try to touch screen but my phone dosnt respond....screen freeze. Sussesful installs I've had are sky raider virtuous most.sense roms...the only froyo I have that works is ruby...my fav right now. I would love to have cm 6....I've posted on this forum a few times as well as cyanogen forum. I hope im not the only one with this.issue.......
SamuraiXDroid
Here are some more ways to potentially solve your problem. Again, I am not a developer so I am just mentioning a few solutions that might work, I am not entirely sure what is wrong with your device. I'm just trying to help you hammer away from all sides.
Are you wiping data manually too? People have noted success before where they had none before by wiping data/dalvik/cache twice before flash and once after. Not sure why this would solve anything but it is worth a try.
Try installing cyanogen without GApps (I do this anyways with the nightlies since it seems to be corrupt for some reason) and then installing them later if it boots correctly.
I use the Paid rom manager for the ease of use for nightlies, but here is a web link to the nightlies which you can try if you don't have paid: http://mirror.teamdouche.net/?device=inc They are more up to date and stable at this point than 6.0.2 was (for me at least). I am using build 100 and have tried the packaged in kernel, koush test 6, and adrynalyne's, and all work well.
Adrynalyne has another kernel for AOSP roms you can try: http://adrynalyne.us/?p=79
You can also try using the phone to reformat one of your SD cards just to eliminate that potential pitfall, though I don't think you would be getting that far anyways if it was not formatted correctly (Menu>Settings>SD card). This will wipe any data currently on your SD card.
Now, I would wait for someone else to provide confirmation that this should work since I haven't done it personally, but you could also try restoring boot.img from a Ruby Nandroid with KK1/2 installed (Install Ruby, install KK, make nandroid backup, install CM6 w/o Gapps, nandroid>advanced restore>select ruby nandroid>Restore boot). This should restore a working AOSP kernel for CM6/shadow to use however I am unaware if there are any other consequences. I also suggest KK or adrynalyne since I do not know what Ruby uses and KK and adrynalyne have both worked for me on CM6. The reason I think the kernel is not installing correctly is because your touchscreen is not working and AOSP roms use a different driver than sense roms for it. I could be completely off base however.
Also, out of curiosity, which radio version exactly are you using?
Hi Jaguox,
Thanks again for the help here is what I tried. I do own the market app ClockworkMod Revovery v2.5.0.5/rom manager. I came from Ruby 1.1.1 with the newest kouch Kernal and radio 2.15.00.07.28. I then wiped data, cache and dalvik twice. I then installed cm nightley 96&98/shadowrom (two seperate installs of course for each rom). I then installed Adrynalyne/Kingkernal kernals and wiped dalvik cache once more. I did not install gapps and let the rom boot. Interesting enough the roms bypassed the intial setup and booted to the home screen. But both roms with both kernals still would not let me have touch access to the screen. So I could see the roms but I couldnt touch them...aaaahhhhhhh the irony. I also tried a reformatted sd card.....same outcome. One time out of the hundred I have tried in the past two months allowed me to initiate my account in a cm nightly and access apps. I rebooted after a fix permission and got a boot loop. That was the farthest I have ever made it. Its strange that both these two roms that share the same dna give my phone the same effect. I appreciate anyones help in solving this mystery.
Thanks in advance!
?
SamuraiXDroid
Same issue on my Dinc. I have.wiped, rewiped and.still.the same out come on 2.1. I did not have this issue when I installed the first release of SR a while back. I have no other issues with other ROM's. Help?
Sent from my ADR6300 using XDA App
So shadow rom first release woked for you? There must be some common denominater for why our phones cannot take certain aosp roms? Ruby works but not cm6 or shadow......very strange.
So I think shadow rom found the fix to the issue I was having....hopefully this thread helps anyone in the same vote as me.
http://forum.xda-developers.com/showthread.php?t=808972
Hi,
After having the Desire for a year now I finally decided to root and flash a rom. Got through the root pretty well but am now struggling with the rom.
I flashed Oxygen and all looked and felt great until i tried to add a shortcut and widget to my front screen as it never did anything when i chose the option. Then when I pressed the lock button the screen would not boot back up. The key pad lit up but no screen. I took the battery out and rebooted but still the same thing happened.
Ive now done a nadroid restore and back to the stock rom but like the simplicity of Oxygen. Any idea's what it could have been? Can you put widgets and shortcuts on roms?
Before installing i did a facory reset, are there any other resets i need to do?
Sorry for all the questions,
Thx
Hmmmm would seem something messed up. You can try reflashing it. That usually works with a rom (has done for me before). I don't know what launcher Oxygen comes with but you can try another launcher for free and see if that's any different.
When you change to a different rom, you should do a factory reset and wipe the Dalvik cache as well. If your upgrading a rom, you don't need to wipe anything.
To be honest, I am going to install Oxygen and see if there are any errors with it because a lot of people seem to be having issues with it.
**EDIT**
I installed Oxygen RC7 no problems at all. Did data wipe, cache wipe and Dalvik cache wipe then installed it. Added widgets, apps and shortcuts to the launcher.
I guess something messed up for you to wipe as I said above and flash it again.
Cheers for that, i'll give it another try later.
Is it worth updating my radio as there seems to be a lot of debate to weather you need to despite some roms requesting specific radios?
Just re flashed it and everything is working great thx.
Flashing a radio helps if your having problems with data connections on your current radio. To be honest, I just flash the current radio anyway just in case but it isn't necessary.
Hello all...I am currently running cm6....everything works great...mytouch slide 3g rooted, and s-off with alpha-rev
I downloaded the cm7 rc2 and the correct gapps as well...gb-20110307....I reboot into recovery, and select wipe data/factory reset etc....I clear cache etc....I then choose install from sd card....pick the cm7....it says installation complete, I then do the same for the gapps...says it installed....then I reboot phone....and it just sits at the s-off alpharev boot screen.....no cm android screen comes up.....ive tried like 5 times now and I wait like 20 minutes each time, but nothing evr happens.....Can someone give me some advice?...what the heck am I doing wrong?.....Thanks so much for your time.....DIrtylarry
Are you running the latest clockworkmod? No clue if it makes a difference, but an idea.
ummm....I think so?.....I guess I dont know for sure.....link maybe?....
Download Rom Manager from the market or make sure its updated if you already have it installed.
Open Rom Manager and hit "Flash ClockworkMod Recovery". Then try again.
Try the 0120 gb gapps, some people have had issues with the latest 0307 ones.
ok....so i reinstalled 6.0 cm and now want to go to 7.....so clockworkmod recovey.....then wipe etc....then 7.0 from sd card.....and then gapps?....what i find weird is that 6.0cm has a yellow status bar that goes across screen when installing, and neither of the 7.0 rc and rc2 have this, and neither will install.......make sense?,,ty
Do you have custom MTD partition sizes setup? If so, it's possible that your system partition isn't large enough..
Have you tried pulling a logcat while booting the phone?
JTB
Had a prob like this once b4 on mt3g and I fixed by putting latest radio....do u have the latest radio 7.15 cux cm7 have wifi calling and hotspot.....just putting in my 2 cent
thanks for the advice guys....after 6 hours of no solution i decided to go with a different rom....and EVERYTHING worked instantly...I'm sure all this has to do with a size constraint on the mtd?......Now....I need to research this and figure out how to get more space on the internal....as I am almost full again with even moving apps to sd........if I can figure this out...Ill be a happy androider....lol....
dirtylarry10 said:
thanks for the advice guys....after 6 hours of no solution i decided to go with a different rom....and EVERYTHING worked instantly...I'm sure all this has to do with a size constraint on the mtd?......Now....I need to research this and figure out how to get more space on the internal....as I am almost full again with even moving apps to sd........if I can figure this out...Ill be a happy androider....lol....
Click to expand...
Click to collapse
Do what I do and delete all the ringtones/notfications/alarms that you don't use. What radio are you on?
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
Hi,
I am currently running Android Revolution HD 5.1.7 on my DHD
I was just wondering with the new 6.1.1 version out, to upgrade to it,
do I simply download the file and just flash that to the device or must I first wipe my device? Or some other way?
Thanks for any help!
P.s Really sorry if this has already been asked but I had a quick search and couldn't see anything to this specific situation!
Back up all your data then flash the superwipe script, then flash the ROM, restore data
Sent from my HTC Desire HD using Tapatalk
Thanks alot,
Also once I have flashed the rom to the phone,
Can I remove the file from my SD Card to free up some space?
Its something I have been unsure about from the first time I flashed my phone,
But I should imagine you can??
**UPDATE**
I have succesfully installed Android Revolution HD 6.1.1
But I am getting an awful lot of Force Closes now,
1 in particularly when i try to go on "People" (contacts) it instantly force closes!
Another is SuperUser, and there are a few more than insantly FC as soon as I try to Open them!
Razza12003 said:
Can I remove the file from my SD Card to free up some space?
**UPDATE**
I have succesfully installed Android Revolution HD 6.1.1
But I am getting an awful lot of Force Closes now,
1 in particularly when i try to go on "People" (contacts) it instantly force closes!
Another is SuperUser, and there are a few more than insantly FC as soon as I try to Open them!
Click to expand...
Click to collapse
1. You can but I would recommend that you keep a copy of a stable ROM on your sd card just in case you have to reinstall for some reason.
2. It seems like the ROM is corrupted.
Did you superwipe before you installed the ROM?
If you have:Check the md5 checksum of the rom you downloaded. It should be the same as the one posted under the ROM download link in the ARHD thread. If its the same you can try superwiping and reinstalling the rom.
If you havent: Download the superwipe script from the first page in the ARHD thread, superwipe and reinstall the ROM.
Also make sure to backup your phone data before superwiping because everything will be lost. Also don't install any mods untill your device has completed the first boot after installing the ROM.
to be honest i had issues with arhd 6.1.1 when i flashed it too. not the same as yours but constant. not everybody seems to have them though and others say it has something to do with the overclock daemon. i believe there´s a patch for it though on the 6.1.1 developers thread.
i didnt bother though i just moved on to virtuous unity 2.39 and have had no problems, really smooth sense 3.0 rom. i´ve been planning to try out a non sense rom next but i really like this rom so i´ve been putting it off for a while now. i even put the beats audio patch on it a few days ago and i gotta say its pretty good even on stock htc headphones
planing to update to arhd6.1.1 too, but have ardh3.3 and clockwork 3.0.0.6. which clockwork is ok (mean which of the newest)?
I did use superwipe and i checked the md5 and it was all good!
I re-flashed the rom and now its ok
I have found out what was causing it!
It starts happening again every time I install google+ 2.0
The new version of the app that has recently been leaked on androidpolice
(Would include a link but im not allowed yet)
And the reason it did it straight from the start the first time is because, before
doing anything else, I restored all my app via Titanium Backup!
If anyone else has this issue or could try to install the app and see if it happens
to them or could figure out how to fix it, it would be great!
(Don't worry about installing it, uninstalling it stop the force closes straight away)
did you try just restoring just the app, but clean without the user data. i did that first time i flashed a rom and it caused all sorts of problems. so i reflashed and restored the apps one by one but just the app, no user data, and stopped having problems
Lewelynn said:
Also make sure to backup your phone data before superwiping because everything will be lost.
Click to expand...
Click to collapse
Hi,
My first post
Any idea does this superwiper clean the radio as well? Does the order matter - first wipe, then rom and finally radio?
ponk2k said:
did you try just restoring just the app, but clean without the user data. i did that first time i flashed a rom and it caused all sorts of problems. so i reflashed and restored the apps one by one but just the app, no user data, and stopped having problems
Click to expand...
Click to collapse
Yes i tried restoring just the app, that caused fc's too!
As did re-downloading the app!
jms-xda said:
Hi,
My first post
Any idea does this superwiper clean the radio as well? Does the order matter - first wipe, then rom and finally radio?
Click to expand...
Click to collapse
Superwipe doesn't effect the radio, and yeah that order you said is the way I went about it, but I also think you can do radio before rom too!
Update from 5.1 to 6.1
Maybe I haven't looked hard enough or maybe I am simply too tired...
Are there any specific steps from updating ARHD from 5.1 to 6.1? I can't seem to find any info about it.
Also, flashing the 6.1 over the 5.1 will it reset the way my screens/widgets are set while on 5.1?
Thanks.
Ok here it goes. my network service is off so i use my droin inc for games and such. running custom rom wildstang83 IceCream Scencless 1.0. im not sure what happened to my phone but i left for 3 days and come back to my phone being totally jacked up. It wot dl apps the google play reverted back to the old market icon. wont save my passwords for google sighn in. every time i go to youtube it says to re dl the google play services. im sure other stuff is messed up too. i have tried to flash another rom but when it gets loaded back up it keeps saying process. whatever failed and there a bunch of those that loop and i have to pull battery. when i try to factory reset it says everything was formatted but when i reboot phone its the sme as it was before apps and all. So is there anyone out there who can help me with this. Sorry if i posted in the wrong place or what not. i wasnt sure where to post it cuz its kinda an advanced question but not really a question just need help.
not a virus but it does sound like your phone might have exhausted all the space in the /data folder. I had a similar thing happen to me before I rooted and fixed my phone where i exhausted the space, itt went a factory reset and put the phone into an unusable state.
i don;t know anything about the rom you are running but are rooted and have CWM installed? if so, you should be able flash a new ROM to your device, GAPPS and optionally, the low space disk fix.
tekweezle said:
not a virus but it does sound like your phone might have exhausted all the space in the /data folder. I had a similar thing happen to me before I rooted and fixed my phone where i exhausted the space, itt went a factory reset and put the phone into an unusable state.
i don;t know anything about the rom you are running but are rooted and have CWM installed? if so, you should be able flash a new ROM to your device, GAPPS and optionally, the low space disk fix.
Click to expand...
Click to collapse
Yes i do have cwm but i tried to flash a new rom via the recovery section. after i choose the zip to flash everything goes as expected untill after the reboot and it goes into the setup part where u have to put gmail password and stuff in then it basically freezes up with unlimited process failures. but i will try again. cant hurt from where it is now.
if you are not doing so already, i would wipe cache and dalvik cache after flashing the rom. that may fix the FCs.
I would also suggest you run a newer jelly bean ROM like Tiny;s 5-16 with his version of GAPPS(4-05) version plus the low space disk fix so you can maintain parity with what is the latest.
I am currently using evervolve 6-25 and it is working well for me.
the reason I say that is these newer JB roms have the ability to let you skip the activation easily. I don;t know if it was some feature of GB roms but the activation wizard in the JB roms seem to be better my opinion.
When switching to a different ROM, it is crucial to wipe /system. This can be a source of FCs. Also, if switching, it is also a good idea to do factory reset.
tekweezle said:
if you are not doing so already, i would wipe cache and dalvik cache after flashing the rom. that may fix the FCs.
I would also suggest you run a newer jelly bean ROM like Tiny;s 5-16 with his version of GAPPS(4-05) version plus the low space disk fix so you can maintain parity with what is the latest.
I am currently using evervolve 6-25 and it is working well for me.
the reason I say that is these newer JB roms have the ability to let you skip the activation easily. I don;t know if it was some feature of GB roms but the activation wizard in the JB roms seem to be better my opinion.
Click to expand...
Click to collapse
I just flashed another rom i used in the past by the same dev and so this is my step by step. 1. choose zip from sd. 2. factory reset. 3. wipe dalvik cache. 4. wipe cache partition. If this doesnt work i will try jb roms but i would hate to have to dump the dev that im useing. there the most stabe roms i have come across so far
PonsAsinorem said:
When switching to a different ROM, it is crucial to wipe /system. This can be a source of FCs. Also, if switching, it is also a good idea to do factory reset.
Click to expand...
Click to collapse
what do u mean wipe /system. where do i find that. only reason i ask is cuz maybe ive never done that. but i have never had a problem withthe other 15 roms i have flashed before so thats why im so confused about what happened to my phone. all i did was shut it off and leave it home. nothing changed from my daily use before that and it was working top notch before i shut it off
im getting settings fc. youtube fc, my uploads fc, market fc, clock widget fc, internet fc, rss reader fc, htc sence fc, all those off of a fresh flash ad new sd card
Just lost my bckups that were saved on sd card so now i cant even get on it i dont get it. its not bricked but yet it i unstabe to run any rom but the preivious saved backup (now there deleted)
maybe the rom you downloaded is corrupt. worst case scenerio is that your phone is on it;s last legs.....
i would suggest you try downloading the JB rom and Gapps plus the low space fix.
http://forum.xda-developers.com/showthread.php?t=2050930
it;s kind of proven to work in my opinion. the 5-16 build is pretty stable.
what I do is flash the rom zip, gapps zip and low space zip, then wipe cache and dalvik. it probably should not make a difference but I am using TWRP as my recovery instead of CWM.
goodluck!
tekweezle said:
maybe the rom you downloaded is corrupt. worst case scenerio is that your phone is on it;s last legs.....
i would suggest you try downloading the JB rom and Gapps plus the low space fix.
http://forum.xda-developers.com/showthread.php?t=2050930
it;s kind of proven to work in my opinion. the 5-16 build is pretty stable.
what I do is flash the rom zip, gapps zip and low space zip, then wipe cache and dalvik. it probably should not make a difference but I am using TWRP as my recovery instead of CWM.
goodluck!
Click to expand...
Click to collapse
Thank u and its still not working. probably just takeing a dump on me now it is just bootlooping.
when i do a factory reset i get a wipe completed. but it says "no app2sd partition found. Skipping format of /sd-ext" could that be part of the issue?? ive never noticed that before
i don;t know if switching to TWRP might help you but it might be worth a try. maybe a coincidence but the last time I had a screw up on my Dinc installing a ROM, i was using CWM. I switch right after that. I think i did read something about TWRP specifically supporting the EXT4 Low space fix.
maybe someone more knowledgable can chime in.
tekweezle said:
i don;t know if switching to TWRP might help you but it might be worth a try. maybe a coincidence but the last time I had a screw up on my Dinc installing a ROM, i was using CWM. I switch right after that. I think i did read something about TWRP specifically supporting the EXT4 Low space fix.
maybe someone more knowledgable can chime in.
Click to expand...
Click to collapse
i will try it but it is doing the same thing on every rom i have tried to flash. ive tried 6 different roms so far and i have ran them all in the past so im incined to think its jacked. and is there a specific twrp for the different roms or can i just dl the latest version and it will work