Database Users

Modaco ROM alternatives?

I'm just wondering what's so good about the Modaco ROMS... From what I was reading it's the best thing to ever happen to Hero but I've flashed it and it actually seems slower/laggier than my stock ROM... should this be?
My stock ROM was 2.73.XX but I can't remember the exact build number. I'm using Modaco 3.0... are there any other ROMS out there I should consider trying? I'm looking for the fastest and most responsive ROM out there. I do A LOT of multitasking so I'd like to have a ROM that can keep up.

If you did a complete data wipe/factory reset, while having the Modaco Rom, the Hero should be a lot more responsive and faster.
I like Modaco rather than stock rom because it removes some useless apps and allows for more customization. Btw, another alterative to the stock and Modaco is the [email protected] and the Clean ION Roms.
There are several different Roms, the differences is the types of apps removed/installed and the Android firmware.

i like modacos roms, because they work reliable and good. with pauls roms i am sure that he has tested them well, and i can use them as basis for my own modifications, or just can push them to my friends' heros without having them complain that something doesn't work. also in case you need support you can ask paul, he is really a nice guy.
there are some other roms, but imho mcr3.0 is by far the most evolved rom, esp. for everyday use. check the development section here for other roms, including the brandnew android 2.1 roms

Well here's the thing. I didn't wipe/factory reset before I Flashed the ROM. After flashing it went into a reboot loop, it would keep rebooting and when it got to the last boot animation, reboot again... I then did a wipe using the recovery boots wipe option and then it booted fine... Maybe I should do another wipe and flash again? It sucks though because now I've customized it back to the way I like it... I hate having to do that all over again. I guess I need to do the A2SD thing so I don't have to redownload my apps again... that was annoying when I had to do it after flashing Modaco's.... I couldn't even remember all that I had installed lol.

Anyone think reflashing might make it better?

I've been using MCR since about 2.2 so I can't speak for 3.0, but when I first flashed with 2.2 I didn't factory reset or format my SD card and it was a complete fail... apps force closing constantly, unable to recieve SMS, and other assorted weirdness.
So I factory resetted, reflashed and from that point MCR has run very smoothly and each update has gone OK (except for one where i had to format and repartition my SD card for A2SD, but didn't lose any settings).
So my advice would be that if you go to the effort of starting with a clean slate you'll get a much better user experience, which is what all us existing MCR users have...

streetdaddy is spot on. Do a clean wipe and then a rom flash.
I'm using MoDaCo 2.9. For my Hero, 3.0 ate up a lot of my phone's internal memory and kept saying I was running out of memory. The differences are minuscule and the speed improvement is about the same.

I started using Pauls ROM as soon as I got my Hero (which was a few days after release) because the stock ROM was toilet, and I've not looked back. The ROM itself is excellent and the support is first-class.
Make sure to wipe before installing. Once you've got it up and running you shouldn't have to wipe it when you upgrade next time.

constant reboots

Hello, I have had my evo for about a month and over the last week or two my phone constantly reboots and crashes. It sometimes gets stuck in boot loops and i haveto yank the battery. it seems to happen most frequently during the browser or market apps. I cannot figure why it is doing this!!!!
my phone is rooted and this has been happening on multiple ROMS including CM6, AVA froyo, baked snack, and fresh EVO.
I have wiped:
cashe
DATA
full factory reset
Dalvik Cache
battery stats adn rotate settings
I have triedmultiple batteries and SDcardsi have tried an 8GB and 16GB and reformatted both
any other ideas?

Which ROM and kernel are you using? Your description sounds like an overclock or under voltage issue. Do you get the same behaviour with the stock ROM & kernel?

Right now I am Ava froyo v7 I have used cyanogenmod Ava froyo v6 as well as baked snack 1.5-7 and fresh 3.0.1 and 3.2 same with all
I have use the stock kernel and still get rebooting with stock speeds and 400mhz

I had VERY similar problems to you (rooted, no matter what ROM I would use (even rooted stock) I would get reboots). Usually after yanking the battery I'd get a good 2 or 3 minutes, and then, particularly when using the browser, I would get a reboot. Then reboots would repeat in perpetuity. I even tried unrooting and going back to complete stock, no luck.
Note there is a thread about a code to fix some problems with GPS -- this didn't fix my problem, but it might fix yours.
So just today I took my Evo back to a Sprint store, convinced them it was a problem, they tried doing the complete RUU flash, and the reboots happened again (yay!)...and they gave me a "new refurb".
So I'm currently rooting the new refurb.
- Eckless

Could it possibly be that I am not reapplying the stock kernel before flashing a new rom how log did it take you to get a new phone?

First of all what root method did you use and did you root 2.2 or root 2.1 then upgrade to a prerooted 2.2 rom.
And if you are not following the rom install instructions to a T and are wondering why you are getting reboots then frankly wtf do you expect.
I said that because you said you were not flashing the stock **** before flashing the rom.
Typically this is not needed unless the rom creator SPECIFICALLY states it is needed.
First of all you are using some very nonstandard Rom's. Start by completely wiping and removing any custom sdcard formatting and reformat your sdcard on your pc.
It has been said and proven many times that a bad sdard can screw with your phone and make some crazy **** happen.
Then go back to the STOCK 2.2 ODEXED, not deodex, the point is to get as close to retail as possible without losing root.
Then see what happens.
Sent from my PC36100 using XDA App

Started with 2.1 1.47 OTA update and Jane followed all instructions to the dot and I have re reformated my sdcard several times with windows for both the 8 gb and the 16 gb which both work great on my droid ( which I did reformat between moving them to a new phone) I also tried using no sdcard and no difference ill try going back to stock rom but I have always been using ava froyo and baked snack but now I'm getting problems with any romI use

I am using swype so sorry for any wrong words. Any way I was also using clockwork recovery for a while and it was apparently not wiping dalvik etc. Correctly so I thought that was why it was crashing so I switched to amon Ra recovery and its still crashing so could it have caused permanent damage that can't be fixed by just wiping everything with amon Ra

Clockwork didn't cause damage...flash stock 2.2...flash stock kernel...do a factory reset...and report back...

help

folks, my a500 is overheating .. is getting too hot near the Dock Connector ...
is without overclocking, began in the ROM v10 ... already installed a four roms and the error still continues,
currently with honeyvillian, I leave with the original stock which is 3.0.1
I try the same way as was done to use mod 3.2, and does not work
... only shows the current version
well ..
current version: 1.0.1 Honey Villian ...
New Verson: N / A
I want to install the original version to send assistance to repair the high temperature

Verdeee said:
folks, my a500 is overheating .. is getting too hot near the Dock Connector ...
is without overclocking, began in the ROM v10 ... already installed a four roms and the error still continues,
currently with honeyvillian, I leave with the original stock which is 3.0.1
I try the same way as was done to use mod 3.2, and does not work
... only shows the current version
well ..
current version: 1.0.1 Honey Villian ...
New Verson: N / A
I want to install the original version to send assistance to repair the high temperature
Click to expand...
Click to collapse
You're not flashing your Rom correctly. I told you this in Thor's forum (at least the exact post was there also, so I suspect it's you, if it's not you, then accept my apologies ).
The reason it keeps telling you that a certain Rom/kernel is installed, is because it seems like you're just flashing one over the top of another without cleaning anything out. This is why your cpu overheats. You've got a corrupted OS.
Also, a Kernel image is not a Rom. And there are 2 types of kernels. 1 for a stock rom, and 1 for a cooked rom. You shouldn't mix the 2 or you may get problems depending on the rom. Another reason why your cpu overheats.
Do this. Put your SD in your PC's card reader, and format it to Fat32. Reason, is that I have absolutely no idea what you have on your sd. Update.zips, Kernels, Roms, etc.
Copy your VillainRom or Revolver Rom or Taboonay Rom (or whatever rom you want to use) to your SD, then put it back in your 500.
When you flash a new rom, you boot to CWM.
Wipe User Data
Wipe Cache Partition
Goto Advanced and Wipe Delvik
I like to do each a couple of times, just to be sure.
Then go back to the previous menu, and select "Install zip from sd"
Choose your rom and install it.
All three of the above roms come with a cooked kernel so you shouldn't have to mess with kernels.
Also, if you wish to install a different cooked kernel, you only need to wipe Delvik before installing.
Also, Install the rom first and let it run for awhile before installing a kernel. Never do both at the same time.
And the final rule, if you used a backup program like Titanium Backup or any of the others, Never Ever backup and restore system files to a different rom.
But, if you want to put it back to stock, the I suppose you can use the acer recovery tool to flash a stock acer rom and flash the stock recovery image. For more info, see this thread;
http://forum.xda-developers.com/showthread.php?t=1155664

Problems with checkrom or N.E.A.K installs IE bootloop or FC's

So i've have tried several times to install checkrom and have had some issues myself with boot loops, being a noob to andriod, (I just got the phone in january), first thing i wanted to do with my £400 handset was void the warranty and root the bugger.
OK, so i have managed to flash NEAK and checkrom and get my phone in such a nice sweet stable daily usage that i thought i would post this as i see many people have close to or the same problems i had flashing this rom and or kernal.
1) back up all your data using titanium or some other app that allows you to do this.
2) Transfer your data off your phone\SD card to PC IE pictures\music\videos\app back ups.
3) Once all the data you want saved is backed up to PC, you can proceed to format both SD and USB on the phone.
4) Reboot phone to recovery and wipe 'EVERYTHING' this means wipe cache partition\ wipe Dalvik cache \ wipe battery stats \ Factory reset.
5) Turn off phone
6) Boot into download mode IE odin mode
7) Flash via ODIN a rooted stock kernel
8) Boot into recovery again and wipe EVERYTHING
9) Flash checkrom V6
10) reboot into recovery and wipe 'EVERYTHING'
11) Flash N.E.A.K 1.3.3x
12) reboot phone and you should have a stable phone with checkrom as your rom and NEAK as your kernal
NOTE:
As a note i have also got JKAY deluxe setting app installed, i installed this separate which i found on the checkrom page and its working just fine.
Also uninstall the kitchen app that comes with checkrom BEFORE installing the new one from off the market, now i dont know if V6 comes with the new kitchen app as i had flashed V4 before hand then NEAK then to V6.
This took me many tries to get this just right and the key i think to it is the formatting of the USB and SD card.
Good luck to you people, and i hope you have the success i've had enjoying these wonderful tweaks i can now use on my phone.

Between the S1 and now the S2 I have flashed all sorts of roms and never had to format SD card/s. Btw I'm on Checkrom as well.
Sent from my GT-I9100T

Me too
I've had bootloops too. But i cleared a clean wipe of my data and flashed the stock rom and installed the ROM back. Now, it's working perfectly fine. I was thinking whether the N.E.A.K kernel was the one causing the problem. And now, after seeing that the others are having nearly the same problem with me, I am positive that there's some problem with the kernel and will not flash the same one again. Thanks!

cwh1996 said:
I've had bootloops too. But i cleared a clean wipe of my data and flashed the stock rom and installed the ROM back. Now, it's working perfectly fine. I was thinking whether the N.E.A.K kernel was the one causing the problem. And now, after seeing that the others are having nearly the same problem with me, I am positive that there's some problem with the kernel and will not flash the same one again. Thanks!
Click to expand...
Click to collapse
There is nothing wrong with the kernel. I also am on checkrom v6 and i have flashed that bugger so many times my tits are getting cold from the amount of times of flashing anyway it depends on the way you flash something and if you follow the proper procedures.
Sometimes it could be because of a bad download that sometimes you get bootloops or sometimes you just not flashed a file properly. But to blame a kernel or a rom in general 99% of times is a mistake as most bugs or errors are user inflicted. i still would recommend to flash NEAK as it is a sweet kernel and tomorrow their will be a new updated version. Anyway hope you guys enjoy checkrom and in general your android experience has a more enjoyable going

Pretty Weird Soft Brick

I wasnt sure where or even if I should post this I normally use V.5 as a daily driver but I wanted to try the latest Hydracore OC kernel with latest JB Paranoid Rom. Everything was cool on ParaJB, as it has been in other test drives, except that I kept losing root whenever I flashed Hydracore, and I know thats been reported many times but I couldnt fix it and I started thinking that it might have something to do with the way the PreRooted gb roms are rooted. No idea but anyway heres what I did:
I wasnt sure if I should flash try to SuperSu .96 from CWR to regain root (I think that I should have) so I started over and downgraded to gb via PC Odin using a pre rooted GB rom. I booted, confirmed root then flashed JB Paranoid 2.1 from recovery, booted and updated superuser in market and updated to latest binary in app.
So I try Hydracore again now that I updated the binary confirmed root GB to JB, but I lost root again with HydraCore so I was thinking, based on what i had read, that I probably messed up with Superuser but letting the market update it every time and that I should have downloaded and updated the binary with SuperSu instead. I really dont know why I didnt do that in the first place but I do that carelessness can get you into trouble.
So I flash the pre rooted GB again in PC Odin but this time I get into a bootloop and I cant even boot recovery...soft bricked? Tried to flash it in PC Odin a few more times, its flashing fine wo errors but no change no loop, its just stuck on N7000 logo.
I went back into download mode and did the standard download a stock gb rom, hope 4 the best procedure. This time it got further, it actually played the music, which I took as an encouraging sign that stock recovery would work & it did (I was a little nervous but I worrry 2 much) so I wiped cache, factory reset and finally booted, finally.
I still have no idea what happened and I still have to re-upgrade but I don't anticipate any issues with that. I guess this time I will try to install SuperSu from market before I flash HydraCore and/or flash .96 via CWR afterward I lost root and then Triangle Away.
...I must have flashed a thousand Roms, (counting other devices) but I cant remember ever losing the ability to charge. Only now do I realize why it always says have at least 50% charge, you really dont want to try flashing wo a lot of juice.

OC version of hydracore is not stable for all Notes. Try to reflash everything from Odin, use Speedmod
Sent from my GT-N7000 using Tapatalk 2

TopOfNewYork said:
I wasnt sure where or even if I should post this I normally use V.5 as a daily driver but I wanted to try the latest Hydracore OC kernel with latest JB Paranoid Rom. Everything was cool on ParaJB, as it has been in other test drives, except that I kept losing root whenever I flashed Hydracore, and I know thats been reported many times but I couldnt fix it and I started thinking that it might have something to do with the way the PreRooted gb roms are rooted. No idea but anyway heres what I did:
I wasnt sure if I should flash try to SuperSu .96 from CWR to regain root (I think that I should have) so I started over and downgraded to gb via PC Odin using a pre rooted GB rom. I booted, confirmed root then flashed JB Paranoid 2.1 from recovery, booted and updated superuser in market and updated to latest binary in app.
So I try Hydracore again now that I updated the binary confirmed root GB to JB, but I lost root again with HydraCore so I was thinking, based on what i had read, that I probably messed up with Superuser but letting the market update it every time and that I should have downloaded and updated the binary with SuperSu instead. I really dont know why I didnt do that in the first place but I do that carelessness can get you into trouble.
So I flash the pre rooted GB again in PC Odin but this time I get into a bootloop and I cant even boot recovery...soft bricked? Tried to flash it in PC Odin a few more times, its flashing fine wo errors but no change no loop, its just stuck on N7000 logo.
I went back into download mode and did the standard download a stock gb rom, hope 4 the best procedure. This time it got further, it actually played the music, which I took as an encouraging sign that stock recovery would work & it did (I was a little nervous but I worrry 2 much) so I wiped cache, factory reset and finally booted, finally.
I still have no idea what happened and I still have to re-upgrade but I don't anticipate any issues with that. I guess this time I will try to install SuperSu from market before I flash HydraCore and/or flash .96 via CWR afterward I lost root and then Triangle Away.
...I must have flashed a thousand Roms, (counting other devices) but I cant remember ever losing the ability to charge. Only now do I realize why it always says have at least 50% charge, you really dont want to try flashing wo a lot of juice.
Click to expand...
Click to collapse
Well I am glad that your phone is back to life. In your post I can not see that you have made a full wipe between flashes (GB and the custom rom). Maybe a wipe cache and dalvik could have helped. As you were already told, Hydracore OC version is not for all devices and might behave ramdonly so try to flash the Standard version of it.

iam pretty sure that I got tge wipes right but yea it wasnt a huge deal just strange
You don't want to wipe after you replace supersu either BC then you will lose it right and it will cause some sort of binary issue, is that even possible?
So I am pretty sure it was in fact an issue w supersu vs superuser
BC I am now once again using hydracore 3.4 OC group B wo issue (and its GREAT btw i love it) on paranoid v.5 w full root rights retained...but i dont think i csn factoryvl reset now wo losing root unless I first tell superuser to update ot bibary and retake control of root from Supersu then uninstall Supersu, or something like that, I haven't experimented enough to know what's what
So if u want to flash hydracore u just have to update supersu after you flash paranoid and probably any other Rom thats includes Superuser
From what I have gathered, if you download and update the binary from with SuperSu it replaces super user (as there can only be one at a time) I've found, at least on paranoid rooms, that if before you switch kernels you need to let supersu become the primary root binary and then flash hydracore you will retain root rights...messing around with the wrong binaries or perhaps having 2 might have messed up things when I went back to pre rooted GB and couldnt boot recovery, so I had to go back to stock
Hopefully this helps somebody who might have similar issues
Sent from my GT-N7000