Database Develop

Having issues with overclocked ROMs

Any help on this would be greatly appreciated! I have flashed just about every single ROM on XDA and have never run into any issues, besides obvious bug within each of those ROM's. But since all of the .29 overclocked kernel ROM's have been popping up I have had nothing but problems with them. I have tried Darchdroid v2.7 and Buffed 2.0B and on each of those after flashing I either get stuck at the HTC screen or it gets stuck in an HTC screen boot loop. One thing I did notice was that after multiple battery pulls I can sometimes get Darch's ROM to boot, but every time I power off or reboot I get the same thing. I have done all the normal stuff that you guys tell all the n00bs, I have wiped EVERYTHING (Factory Reset, Dalvik, and EXT), I have tried booting up wih no SD card in, repartioned SD (with and without EXT), nothing seems to work. I have flashed back to DamagedControl and Fresh with no problems. Obviously there are people here using these ROM's on their Hero but for some reason mine does not like them, are there difference between Hero's based on when their purchased (different chipsets, ect.)?

Try using regawmod with darch's kernal for honeybun, that combo seems pretty awesome for me.
Just search the development forum for them.
Sent from my HERO200 using XDA App

neuro_genesis said:
Try using regawmod with darch's kernal for honeybun, that combo seems pretty awesome for me.
Click to expand...
Click to collapse
I am not a fan of the look of Regawmod, it looks to photoshoppy for me.

[Q] BACK From the cold lonley world without XDA

I recently traded my Sammy Moment for a HERO. I am rooted and flashed but found that some ROMS gave me trouble; Fresh being one of them. Looping boot screens and slow performance contrary to what I read about the roms I flash. Is there anything I may be missing? I rooted via ADB and did find an issue while the recovery was flashing it said: MD5 failure and no space; but recovery still flashed and works.
Last I was on XDA was with my G1 and Tilt. Anyone wanna hip me to what I have been missing? By the way I have succefully flashed the BUUF rom and and the Zen, darch booted with FC's and the others looped.
I wiped dalvik and system and reformated my SD.

Does your Hero have "With Google" branding?
Some of the older phones don't. And at that, some of the older chipset phones can't over clock as high, and OC'd roms will cause a boot loop.
That's the only thing I can think of that wil lbe causing the issue.
You should also try to Wipe everything under the wipe menu except maybe rotate and batt stats before you flash a rom. I always try to wipe clean before I flash.

What Kcarpenter said.
I got my Hero the first day out at BB. I can only clock to 710 otherwise phone starts blitzing.

Gorguts said:
...slow performance contrary to what I read about the roms I flash...
Click to expand...
Click to collapse
Yeah, this is just what most of us here have learned to deal with, as this phone model is nearly a year old and built with hardware that isn't quite powerful enough to smoothly handle the software stuff we try to put on it these days. We are still way ahead of regular HTC/Sprint stock though which is nice.

other than what the others have said...
other options to try...
have you tried the DamageControl ROMs? they are very stable.
if issues persist... maybe you have a bad memory card? there were a rash of them and can cause weird issues.
or you have a bad hero! was it new? warranty??
if so.. get warranty trade in. if you can show issues with phone that is not related to flashing and rooting!!!

Try froyo if you don't care about sense. I have yet to have a bootloop flashing nightlies. Flash a new bootloader, wipe dalvic, system and cache. I'd do each several times just to be sure. Use a new download and verify the checksum
Sent from my HERO200 using XDA App

Recovery Issue

Have posted this a number of places with no luck, including Rom Mgr thread:
If I flash a rom, set it up, then back up, Rom Mgr will not reboot to system. Goes to X and hangs. Sometimes after 3 tries or so it works or if I Restore the recent backup it works. Nothing consistent.
This started when I used amon 2.0 to increase ext to 1024mb for running eVil's desire rom. I had numerous issues where I could not even back up or restore. Seemed to always hang on android-secure part. Since then I reformatted sdcard with sdformatter, then used RM to create 1024 ext3. Flashed fresh eVil HD Gamma rom. All went well, but again after setting everything up and then tapping on reboot into system it hung again. It did not hang after initial flashing of rom and Circle Battery .zip. It booted into system fine.
When I got back to system and homescreens, I uninstalled RM and reinstalled. Although, I had done that before, but before I reformatted sdcard.
So, if this keeps up, only conclusion is RM even though I installed latest from Market, or this rom is messing things up. But, no mention of this issue anywhere else. I will try to boot into Clockwork thru Quick Boot (did that before also) to get to recovery and see how it goes.
Anyone have any idea for a solution to this nightmare, or had a similar experience. Running out of ideas. I am going to dl latest MIUI rom and see how it performs. And maybe load an earlier version of eVil's HD rom.
Thanks for any help, know this is weird,
Ken

Only thing I would suggest is to stop using ROM manager. There is really no need for it. Anything you can do in that, you can do either in recovery, or via a terminal.

efrant said:
Only thing I would suggest is to stop using ROM manager. There is really no need for it. Anything you can do in that, you can do either in recovery, or via a terminal.
Click to expand...
Click to collapse
+1
IMO, using an in-OS software to control the recovery is risky. I prefer having full control by manually flashing everything!

Thanks guys for replying,
I can try reboot recovery thru terminal and Quick Boot. Although, it did it right after repartitioning with Amon_Ra. So, thought it might not be Rom Mgr.
Really thought the reformat of sdcard would do it. May have two issues. Next step is to get the latest eVil rom off and go back to previous version and/or repartition back to 512mb sdext.
Just Frustrated and Confused
Ken

Just an update guys, since you were kind enough to reply to my post
I have kept the 1024 sdext made thru RM/CW removed both eVil's roms and relashed a fresh MIUI. No issues so far, time will tell. Will probably reflash a MicroMod rom too. Can't believe the larger HD rom was the cause. I loved the rom.
If I figure it out one way or the other I'll update. I can't even google my problem and find someone else with it.
Ken

id get rid of rom manager and clockwork. i flashed many many many things/times with amon ra recovery alone without issues, but all i hear are problems with rom manager/clockwork. i mean how easy is it to just go into recovery and flash? or just download something through the browser... my 2 cents

I've been doing this for 8 months and started with amon. Never had issues with either amon or rm/cw. Started using rm/cw just to try when doing a lot of nightlies with cyan.
But, I recently repartitioned to 1024 sdext3 with amon to run desire rom and amon hung too.
Still 1024 and no hanging with MIUI, using rm/cw. I don't have a preference one way or the other, as long as it works.
Don't think it is either amon or rm/cw, but the rom and my ext not working well together. Had no issues with the 512 ext and desire rom. But, I was getting windows warnings on errors on my sdcard and thought it time to reformat anyway.
Thanks for the advice all, I will run MIUI and Micro for awhile and maybe go back to 512 ext.
Did learn for anyone using Rom Mgr that it does now do 1024 ext3 partitioning. Many people thought, as I, it stopped at 512 and ext2. Maybe it use to. Verified the ext 3 thru Mini Partition Tool Wizard. Just FYI.
Ken

Well,
I appreciate all the advice and help, I need it sometimes. But, seems (I hope) that I forgot to reboot into recovery after repartitioning. This tip came from Amon_RA and seems to have fixed my "reboot into system from recovery" issue.
I am now back on eVil's great HD Desire rom and 1024 sdext3 working great.
Thanks,
Ken

[Q] All apps randomly close with any custom rom!!

Foremost, I apologize if this has been asked and answered before. I've been searching for weeks...maybe I'm a bad searcher.
My issue is that I have been experiencing random force closings on random apps, including random partial reboots when unlocking the Unlock screen (screen freeze then goes to Rom intialization screen). Sometimes Dolphin HD closes when loading pages, same with stock browser and Opera Mini, though sometimes the same page will load fine (both with JS on and off and with Flash turned off in Froyo ROMs). Swype (v.2.15) will sometimes close when typing in the search widget or an SMS message in both ChompSMS and stock messaging app. Titanium Backup and Astro sometimes close when scrolling down the app list. The only consistant factor that I can think of is available RAM or the processor overheating.
I have installed multiple ROMs thinking its ROM-specific, but the same behavior manifests in each one. I've tried Assonance 5.2, Cognition 3.04, Phoenix 4.5 and Serendipity 5-1.4.
With each new flashing I first use Odin to get back to stock, then use Odin to Master Clear, then root the phone, then install Clockwork, flash it's recovery app and then use Clockwork to flash the new ROM.
I did fresh installs of any apps I installed from the Market as I know user data from 2.1 will cause issues with 2.2.
Because I thought it was a RAM issue I installed Autokiller Memory and used the 'Optimum' preset.
After all this I still have the same issues with random apps closing and the phone doing ROM reboots when at random times I unlock the phone. Can anyone give me some guidance?

1. When restoring apps with TiBu, are u restoring system data too?
2. Do not restore data of non-system apps if moving between android 2.1 and 2.2.
3. Last ditch attempt, try flashing 5.5 version of the rom in my signature, and if the issue still persists.
4. Processor overheating can be reduced to some extent by turning 3G off, and getting on EDGE. This would reduce ur download speed though.

diablo009 said:
1. When restoring apps with TiBu, are u restoring system data too?
2. Do not restore data of non-system apps if moving between android 2.1 and 2.2.
3. Last ditch attempt, try flashing 5.5 version of the rom in my signature, and if the issue still persists.
4. Processor overheating can be reduced to some extent by turning 3G off, and getting on EDGE. This would reduce ur download speed though.
Click to expand...
Click to collapse
I'll give your ROM a shot.
Stupid question - Do all ROMs have kernels and modems cooked into them? I was just thinking that I've been flashing tons of ROMs lately and I'm not sure of the most stable kernels to have.

Yup they come all "pre-cooked" with kernels and modems... otherwise they wouldn't run
But you can flash different modems and even kernels (at your own peril). You can find them in the dev forum.. usually "update.zip" that you can use to flash under recovery.
But.. this sounds like maybe your internal RAM is corrupt?
Do these things persist if you were to stay at stock 2.1? I would run it "barebones" with just the restore and use the phone for a day or two to see if it continues to happen.
If the issues stop - your all good - just need to figure out what your doing or what your installing that is horking your phone. For me in the past its been due to overclocking without even knowing it (yay for Voltage Control) or it's been an application or bad flash causing the issue.
If the issues persist under the stock ROM - probably hardware related and you would need to warranty it for a different one.

avgjoegeek said:
Yup they come all "pre-cooked" with kernels and modems... otherwise they wouldn't run
But you can flash different modems and even kernels (at your own peril). You can find them in the dev forum.. usually "update.zip" that you can use to flash under recovery.
But.. this sounds like maybe your internal RAM is corrupt?
Do these things persist if you were to stay at stock 2.1? I would run it "barebones" with just the restore and use the phone for a day or two to see if it continues to happen.
If the issues stop - your all good - just need to figure out what your doing or what your installing that is horking your phone. For me in the past its been due to overclocking without even knowing it (yay for Voltage Control) or it's been an application or bad flash causing the issue.
If the issues persist under the stock ROM - probably hardware related and you would need to warranty it for a different one.
Click to expand...
Click to collapse
diablo009 - I ended up not using Tibu to restore anything because I feared that a backup was the cause of my force closings. I had done a clean flash of stock, rooted and then flashed a new ROM. The only apps I installed were dolphin, pandora, clockwork and Lookout.
Thanks avgjoegeek, I did kind of fear that it was bad RAM as this behavior mimics performance on a PC with bad RAM installed.
I did run it on stock for half a day because I wanted to verify and there were no force closings. I am going to run it on stock for the weekend and see what happens. If everything is all good then I will flash di11i's 5.5 and see what happens.
Could it be possible that some features of 2.2 just are not compatible with my captivate build?

DRoc740 said:
diablo009 - I ended up not using Tibu to restore anything because I feared that a backup was the cause of my force closings. I had done a clean flash of stock, rooted and then flashed a new ROM. The only apps I installed were dolphin, pandora, clockwork and Lookout.
Thanks avgjoegeek, I did kind of fear that it was bad RAM as this behavior mimics performance on a PC with bad RAM installed.
I did run it on stock for half a day because I wanted to verify and there were no force closings. I am going to run it on stock for the weekend and see what happens. If everything is all good then I will flash di11i's 5.5 and see what happens.
Could it be possible that some features of 2.2 just are not compatible with my captivate build?
Click to expand...
Click to collapse
When u restore to stock, format the internal SD from within windows. (Ok, I won't contest anyone's arguments on this, but I personally find it easier than doing a master clear and to wipe off even the basic folders android os format creates.)
And, I would recommend u download a fresh copy of 5.5, with a kernel that does not have any OC in it, to play safe. 5.5 is available in two versions - one with OC kernel, and one with non-OC kernel.
It could be a case of kernel too. Try swapping kernel and see if that helps. Not all kernels go well with all hardware. That's the reason I swapped to xcalibur kernel as soon as I loaded 5.5.
I think, personal opinion here, u could do away with clockwork recovery too. U cud download the cwm console update.zip and put it on ur sdcard root. And apply the update.zip with in console in stock to load up CWM console. This is the most non-intrusive way of going to CWM console as far as I know.

I've been running stock since yesterday with zero issues. My force closing issue usually appears within an hour of flashing a new ROM so this is a very good sign that its a flashing and not a hardware issue.
diablo009, you mention using the CWM console instead of clockwork recovery. Isn't this what the clockwork manager installs? Are you saying to install through the consol startup app instead of using the clockwork app when fully booted up? If so, this is what I have been doing.
Maybe its a kernel issue as I think i've exhausted all other options. I'll try xcaliburinhand's v2.3.2 01.31.2011 and see if it works.
Any other suggestions?

DRoc740 said:
diablo009, you mention using the CWM console instead of clockwork recovery. Isn't this what the clockwork manager installs? Are you saying to install through the consol startup app instead of using the clockwork app when fully booted up? If so, this is what I have been doing.
Click to expand...
Click to collapse
Yes. But instead of updating the system boot with this, it leaves the system as it is, and uses is as a standalone program.

diablo009 said:
Yes. But instead of updating the system boot with this, it leaves the system as it is, and uses is as a standalone program.
Click to expand...
Click to collapse
I searched around and couldn't find any download links for this. Do you happen to know where I can find it?

DRoc740 said:
I searched around and couldn't find any download links for this. Do you happen to know where I can find it?
Click to expand...
Click to collapse
Here you go.
1. Copy this to the root of ur sd card.
2. Go to recovery
3. Select "apply update.zip"
4. If u r doing this for the first time, u would need to step 3 again.
You would not now be in a green screen recovery console.
I would recommend storing this file in a safe place so u can copy it to sdcard root whenever u want to revert to stock before flashing a new rom.

diablo009 said:
Here you go.
1. Copy this to the root of ur sd card.
2. Go to recovery
3. Select "apply update.zip"
4. If u r doing this for the first time, u would need to step 3 again.
You would not be in a green screen recovery console.
I would recommend storing this file in a safe place so u can copy it to sdcard root whenever u want to revert to stock before flashing a new rom.
Click to expand...
Click to collapse
Awesome! Thanks!
From your description I think this is the update.zip I have but I'll try anything

DRoc740 said:
Awesome! Thanks!
From your description I think this is the update.zip I have but I'll try anything
Click to expand...
Click to collapse
welcome to the world of flashing. let me (us) know if u need any more help

diablo009 said:
welcome to the world of flashing. let me (us) know if u need any more help
Click to expand...
Click to collapse
Update:
I ran on stock ROM for 2 days without any force closings, no issues.
I just flashed di11i's 5.5 (no OC) ROM and within 10 minutes had numerous force closings and a ROM reboot.
I then flashed the I9000 reoriented ROM (from diablo009's signature link) and the issues persisted.
Is there something I'm doing wrong? Or any more ideas on what could be causing my issue?

DRoc740 said:
Update:
I ran on stock ROM for 2 days without any force closings, no issues.
I just flashed di11i's 5.5 (no OC) ROM and within 10 minutes had numerous force closings and a ROM reboot.
I then flashed the I9000 reoriented ROM (from diablo009's signature link) and the issues persisted.
Is there something I'm doing wrong? Or any more ideas on what could be causing my issue?
Click to expand...
Click to collapse
did you restore anything with titanium backup?

Pirateghost said:
did you restore anything with titanium backup?
Click to expand...
Click to collapse
No, didn't restore anything.
I flashed the update and had the force closings within a few minutes while I was typing an SMS using Swype.

Bumping
I have the same problem

[Q] Using MeDroid ICS 6.1 and experiencing REALLY big slowdowns

Hi guys, since i'm new i can't post on the development thread - [ROM] MeDroid ICS 4.0.3 CM9 V6.1 31/01/2012
Basically this has existed ever since version 5. The problem is if i open any app (say facebook, music, or even internet) things start to get really bogged down and stop responding for minutes. (I have to click "wait" like 4 or 5 times until it finally loads, especially facebook. Music stops randomely and becomes really laggy after 5 minutes of playing)
I know this must be a rom issue, because using a gingerbread rom alleviates all of these issues, heck even using a different ICS rom alleviates the issue but i REALLY like the MeDroid version (MIUI is too iPhoney and texasice just didn't tickle my pickle). Anyway, i'm seeing people in the thread saying "this is as fast as gingerbread!" and i'm like no way... the difference between a gingerbread build and this ics build for me is night and day, especially an oxygen build (that thing is lightning fast).
One thing i'm not sure of though, is i used an EXT4 partition for the A2SD. Now i can't remember if i experienced any slowdowns whilst this was here or not, i'm about to remove it and give it a shot, but i can't see how this lags the whole system out when i have about 3 apps installed.
I'm looking for any help regarding this though, thanks for anyone's time

Might be a bad sdcard.

Theshawty said:
Might be a bad sdcard.
Click to expand...
Click to collapse
Well, i've just taken the EXT partition off, and it's still seems the same to me, even with the SDCARD un-mounted it still acts so slow!
If i install a gingerbread rom though, it's as smooth as butter...maybe i should just wait for proper hardware accelleration before i commit to ICS as a daily

Steveyh22 said:
Well, i've just taken the EXT partition off, and it's still seems the same to me, even with the SDCARD un-mounted it still acts so slow!
If i install a gingerbread rom though, it's as smooth as butter...maybe i should just wait for proper hardware accelleration before i commit to ICS as a daily
Click to expand...
Click to collapse
Try the zkernel #21with Medroid v6.1. It works smoother than the existing kernel in ICS ROM

you need an sdext4, 1gb preferred and 0 swap
you need to have installed the custom hboot, (System/cache/data = 220/16/200)
per OP page. not just blackrose
verify correct hboot installed by checking your bootloader screen for it to be listed and s-off
you need to have wiped ALL 3x, including System
Go back over OP page and do all requirements--
if you prepared correctly, no reason it shouldn't work,
if not working after that, reformat sdcard with sdformatter

rugmankc said:
you need an sdext4, 1gb preferred and 0 swap
you need to have installed the custom hboot, (System/cache/data = 220/16/200)
per OP page. not just blackrose
verify correct hboot installed by checking your bootloader screen for it to be listed and s-off
you need to have wiped ALL 3x, including System
Click to expand...
Click to collapse
I've tried all this. I've even booted without an SDcard and it still acts the same. It's obviously not the SDcard...i've tried that zkernel and i got a very similar benchmark score to the guy that posted it.
I decided to flash the latest stable cyanogenmod and it's working flawlessly and is very fast in comparison... i'm tempted just to leave it for now, since even the browser hangs around for 20 seconds, and pages scroll awfully without the HW acceleration,
I must just be expecting too much from alpha roms, but something's obviously not right if others can use it "perfectly"

Steveyh22 said:
I've tried all this. I've even booted without an SDcard and it still acts the same. It's obviously not the SDcard...i've tried that zkernel and i got a very similar benchmark score to the guy that posted it.
I decided to flash the latest stable cyanogenmod and it's working flawlessly and is very fast in comparison... i'm tempted just to leave it for now, since even the browser hangs around for 20 seconds, and pages scroll awfully without the HW acceleration,
I must just be expecting too much from alpha roms, but something's obviously not right if others can use it "perfectly"
Click to expand...
Click to collapse
well, if you want to try again, you could still redo sd card with sdformatter and try amon_ra if not using it now
and as you said you did wipe system 3x
maybe too many bad blocks for this rom. although I don't know if that is a big issue with blackrose

I have Class 10 SD and ext4 part. It's very slow. ia2sd script not as good as a2sdx maybe. Frezes and reboot too much. Wipe dalvik and cache regularly but not help. I turned to cm7 too.
Sorry my English.
Sent from my Nexus One