Develop Bugs

Can't flash a new rom

Hi all
can't flash my desire hd anymore
and the phone boot only to the recovery.
after a full wipe,i try to flash a new rom, up to 80% and the progress bar does not move.... meaning that the flash does not complete:-(
my phone is s-off and root
I flashed different rom before and all worked
could someone help me please?
thx in advanced

Hi bassjam
bassjam said:
Hi all
can't flash my desire hd anymore
and the phone boot only to the recovery.
after a full wipe,i try to flash a new rom, up to 80% and the progress bar does not move.... meaning that the flash does not complete:-(
my phone is s-off and root
I flashed different rom before and all worked
could someone help me please?
thx in advanced
Click to expand...
Click to collapse
What Rom is it you are trying to install?
Is there any error message showing when it stops?
At a guess It sounds as if you are trying to install a Corrupt Rom, you need to check the MD5 Checksum that come with the Rom to make sure they are not corrupt on download, before you try to install them.
What you need to do is download the Rom again, check it's Checksum With this MD5 Check 2.1 tool.
Then delete the bad Rom that on your SD Card, and replace with the new download [Checked with MD5 Check] Rom, and flash it.
Take Care
TheQuest

Agree with I'm TheQuest. That's maybe because of bad download. redownload back the rom and put back to your SD card. Do the nandroid restore (but if you dont have nandroid backup before, this also can be done by taking out your sdcard and put into your laptop/card reader).

Thx for your answers
The problem appeared with the cynanogen RC4
this rom was installed since a week and i was on RC3 before
one day, I powered off the phone, then powered it on, and the phone boot only to the recovery.
I tried to flash the last leedroid but nothing
After that I knew it was not from the cyanogen rom.
For the moment, to solve the problem, i flashed (on bootloader) the last official WWE ruu(1.72), flash ok but the phone was very very sloooowwww
especially to install the sence, after unlocking simcard, I have a white screen with htc logo during 20 min. and only after that, I can start the configuration.
so i decided to back to ruu 1.32 to root / S-off the phone again
After that I try to install the cyanogen rom again
What do you think about that?

Hi bassjam
bassjam said:
Thx for your answers
The problem appeared with the cynanogen RC4
this rom was installed since a week and i was on RC3 before
one day, I powered off the phone, then powered it on, and the phone boot only to the recovery.
I tried to flash the last leedroid but nothing
After that I knew it was not from the cyanogen rom.
For the moment, to solve the problem, i flashed (on bootloader) the last official WWE ruu(1.72), flash ok but the phone was very very sloooowwww
especially to install the sence, after unlocking simcard, I have a white screen with htc logo during 20 min. and only after that, I can start the configuration.
so i decided to back to ruu 1.32 to root / S-off the phone again
After that I try to install the cyanogen rom again
What do you think about that?
Click to expand...
Click to collapse
If you Change ROM's you are always advised to do a FULL WIPE.
Moving to Cynanogen RC4 from RC3 should not have caused your problem, but even when Updating a Rom you are advised to wipe the Cache Partition and the Dalvik Cache
Take Care
TheQuest

My problem is not yet resolved
actually I download rommanager to get the recovery
my phone is so slooooowwwwwww...
after that I will try to flash new rom with a full wipe before ;-)
if it doesn't work --> the phone will go on "after sales service" :-(

Hi bassjam
bassjam said:
My problem is not yet resolved
actually I download rommanager to get the recovery
my phone is so slooooowwwwwww...
after that I will try to flash new rom with a full wipe before ;-)
if it doesn't work --> the phone will go on "after sales service" :-(
Click to expand...
Click to collapse
Yes do a full wipe, it should help with the speed, good luck.
Let us know how you get on please?
Take Care
TheQuest

is the first time such a problem that happens
I had a htc magic, hero, desire and windows mobile phone before
with each phone, I had at less similar problem
for the first time, I wonder if this is not a hardware problem like writing speed of the processor...
for the moment i finished radio s-off, eng-off, and i put the recovery with fastboot( problem to get recovery with rom manager)
It's time to full wipe, about 30 minutes to wait if not more...
edit: full wipe ok after 15 min, i'm going to wipe with fastboot to be sur!?
redit edit: flash the phone with cyanogen rc4...
thx

something in recvory or perhaps on i didn't see it before
I actually use CWM 2.5.1.2
i have in the recovery screen:
E: can't mount CACHE: recovery/command
E: can't mount CACHE: recovery/log
E: can't open CACHE: recovery/log
Could someone explain me what does it mean?
thx

Hi bassjam
bassjam said:
something in recvory or perhaps on i didn't see it before
I actually use CWM 2.5.1.2
i have in the recovery screen:
E: can't mount CACHE: recovery/command
E: can't mount CACHE: recovery/log
E: can't open CACHE: recovery/log
Could someone explain me what does it mean?
thx
Click to expand...
Click to collapse
You should try to updating CWM to 3.0.0.6, and that should clear that. [hopefully ]
Take Care
TheQuest

amazing!! it works!
flashed leedroid rom with CWM 2.5.1.2 and all is ok( it was impossible to flash cyano with this recovery)
i can now upgrade to cwm 3.0.0.6 and flash cyanogen rc4
very big thx
For those who have the same problem, read the previous post ;-)

Hi bassjam
bassjam said:
amazing!! it works!
flashed leedroid rom with CWM 2.5.1.2 and all is ok( it was impossible to flash cyano with this recovery)
i can now upgrade to cwm 3.0.0.6 and flash cyanogen rc4
very big thx
Click to expand...
Click to collapse
Glad to hear you have managed to get it fixed.
Take Care
TheQuest

bassjam said:
amazing!! it works!
flashed leedroid rom with CWM 2.5.1.2 and all is ok( it was impossible to flash cyano with this recovery)
i can now upgrade to cwm 3.0.0.6 and flash cyanogen rc4
very big thx
For those who have the same problem, read the previous post ;-)
Click to expand...
Click to collapse
Yes CWM 2.x can't write the ext4 partitions required by Gingerbread so you require cwm 3.x, you could have flashed this from Fastboot without first flashing a new ROM. If you didn't have CWM 3.x in the first place this was probably the source of your problems.

I don't believe it!
phone works during 5 five with cyanogen rom, I put the wifi on, and then bootloop( recognized problem on RC4)
i pull out the battery then restart the phone, and the phone has not started and the stay blocked to htc logo
PB: I have no recovery, impossible to to flash another rom. When I launch recovery, phone blocked on htc screen!
I tried to flash ruu 1.32 or 1.72 on fastboot mode... but phone still blocked on htc screen...
I don't know what to do
pls help
thx

[Q] reflashing the same rom

i wanted to start over again cuz i really mess up my dhd, i lost my bootscreen, phone is getting slower, tried some theme and now im stuck at bootloop.. so er.. if i reflash the same rom.. should i reflash everything again? those kernel patch, radio, and a2sd??.. & is it safe for me to format the sdcard?

LoVeRice said:
i wanted to start over again cuz i really mess up my dhd, i lost my bootscreen, phone is getting slower, tried some theme and now im stuck at bootloop.. so er.. if i reflash the same rom.. should i reflash everything again? those kernel patch, radio, and a2sd??.. & is it safe for me to format the sdcard?
Click to expand...
Click to collapse
few questions:
-before flashing your current rom yo did FULL WIPE?
-after flashing the rom you did WIPE BAT.STAT?
-WHAT YOU UNDERSTAND FOR BOOTSCREEN?maybe a bootanimation?
When you want to apply a theme on your OS you should clean the rom before flashing the theme.... if not.. you can enter in a boot loop
for solve it you can do various things:
1- restore nandroid backup if you did it before flash somethING.
2-or flash your rom again:
important you do FULL WIPE (FACT. RESET, CACHE, DALVIK) before anything.
then install your custom rom... and boot your device (for zipalign apk´s..etc)
(but no complete the htc sense questions that your device ask in the first boot)
and enter in recovery, flash your theme if you want and reboot...
then enter again into recovery (CWM) and flash kernel.. reboot...
later you can enter into CWM again for to flash the rest of things

your problem is solved???

er.. ye. actually i just figured out my self lol, well some of them. the only thing that keeps bugging me now is whenever i tried to flash this lockscreen and kernel i always get stock at boot animation, but i can lock & unlock the screen though. (i used cwm for flashing)

LoVeRice said:
er.. ye. actually i just figured out my self lol, well some of them. the only thing that keeps bugging me now is whenever i tried to flash this lockscreen and kernel i always get stock at boot animation, but i can lock & unlock the screen though. (i used cwm for flashing)
Click to expand...
Click to collapse
Mister Millagui says: small grains of sand do big mountains LOLOLOL
continue.... you will obtain it
In XDA we are always learning.....

Desire stays at why so serious, recovery available

I made a stupid mistake my phone was working great, but i decide to flash A HBOOT cm7/r2 via recovery which ended with brick. That thread.
http://forum.xda-developers.com/showthread.php?t=1147184
Now fastboot and recovery are available what can i do?
Ty

Cm7 hboot won't work with stock Rom.
If you have flashed the hboot correctly, just enter recovery and flash a Rom that supports cm7r2 hboot such as cool3d roms
Sent from my HTC Desire using XDA App

I had installed aurora v3 rom which support cm7/r2 hboot. Can I just install another hboot in these case bravostockhboot from thread I mentioned?
My hboot however says im on CM7/r2 hboot...

So you were using Aurora with stock hboot, then flashed cm7r2 hboot, now your phone stays at the splash screen?
If Aurora was working fine with stock hboot that means you had flashed "ROM converter" from the thread. Now that you've flashed a different hboot you'll have to reflash the rom because by flashing the "ROM converter" it is set up for stock hboot only.
Flash Aurora again but don't flash the "ROM converter" this time.

Correct. I flash aurora rom again but it the same. What should i do now?

How long are you giving it to boot? I've not tried Aurora myself but seen some people saying it can take up to 15/20 minutes for it to boot.

About 10 minutes... i will try to give it more.
My hboot version is 6.93.1002 is this correct one for cm7/r2?

Nope no changes still stays at why so serious screen. I will try aces rom and see if it works...
It works now! Thank god, thank you are for the help

Coolexe's ROM. http://forum.xda-developers.com/showthread.php?t=1040121
Suggestions...
1) Make sure you have all of the zips you want on your sd card before you begin. You'll need the ROM zip (obviously) also the weather pack zip.
You might also want any of the extra's available (second post on the thread)...Personally use "Dalvik.cache to SD EXT", "Usual UOT Jazzk% battery + flying windows animation & TP2W + TP2U" and "RC Team tweaks".
I would also flash a new kernel at this point but it's not essential (can be done later).
2) Reboot into recovery and full wipe. "wipe data/factory reset", "wipe cache partition" and then "advanced/wipe dalvik cache".
3) Install zip from sd card...
Flash ROM zip
Flash weather pack zip
Flash Dalvik.cache to SD EXT zip
Flash any extra's
(Flash kernel if you have a new one).
4) Reboot system now.
5) Go have a coffee, watch some tv etc... Give it time to do it's thing.
6) Enjoy
Let me know how it goes.
EDIT: Just saw you got it working. Enjoy.

wicked245 said:
Nope no changes still stays at why so serious screen. I will try aces rom and see if it works...
It works now! Thank god, thank you are for the help
Click to expand...
Click to collapse
Does it workes now refer to AceS ROM or Aurora? In principle, I have the same problem. Waited for 15 minutes!

Trying to install CM9 stable, stuck at boot logo.

My friend is currently running Arconium ICS on his Xperia, and now when I tried to install CM9 (Did full wipe > install CM > install gapps in CWM) it just gets stuck at the boot logo (SONY). After recovering the backup of Arconium in CWM it boots up fine again.
Since the boot logo didn't change, I'm thinking CM9 maybe didn't install a new kernel or something? Is there something I can do to make sure that CM9 fits as well as possible? If kernel switching is on the table I'd like to be able to do this from CWM.
Thank you!

bajsmumsaren said:
My friend is currently running Arconium ICS on his Xperia, and now when I tried to install CM9 (Did full wipe > install CM > install gapps in CWM) it just gets stuck at the boot logo (SONY). After recovering the backup of Arconium in CWM it boots up fine again.
Since the boot logo didn't change, I'm thinking CM9 maybe didn't install a new kernel or something? Is there something I can do to make sure that CM9 fits as well as possible? If kernel switching is on the table I'd like to be able to do this from CWM.
Thank you!
Click to expand...
Click to collapse
you must install the kernel "boot.img" through flashtool
is inside the zip file

krattos said:
you must install the kernel "boot.img" through flashtool
is inside the zip file
Click to expand...
Click to collapse
Do I have to do this via flashtool? No way to do it from inside CWM? Please excuse if this is a stupid question, I'm not still a 100 % sure what boot.img, recovery, kernel and all these are and how they fit together.

bajsmumsaren said:
Do I have to do this via flashtool? No way to do it from inside CWM? Please excuse if this is a stupid question, I'm not still a 100 % sure what boot.img, recovery, kernel and all these are and how they fit together.
Click to expand...
Click to collapse
Yes, through the FlashTool is safer.
For all your doubts see this link, is a little extended but very complete.
http://forum.xda-developers.com/showthread.php?t=1133650

bajsmumsaren said:
Do I have to do this via flashtool? No way to do it from inside CWM? Please excuse if this is a stupid question, I'm not still a 100 % sure what boot.img, recovery, kernel and all these are and how they fit together.
Click to expand...
Click to collapse
Boot.img is the kernel in a compiled file, which needs to be installed via fastboot. Flashtool includes fastboot aswell, so you can install the kernel(boot.img) using it.
Recovery is a certain 'program' used to install custom stuff, make full backups(Nandroid backup) and restore them, wipe/format partitions and some other stuff. Recovery can be included already inside the kernel, but there is also possibility to install it on /system partition for those who can't unlock bootloader and/or install custom kernel.
My recommendation - Don't do it if you don't understand anything. You should go and learn about the whole Android first, get yourself familiar with how to recover the phone(install stock firmware etc), what are the terms that we use, what is what etc, then come back. Else...you might get yourself a nice (temporary) brick and then you have another problem, how to get back the phone.

bajsmumsaren said:
My friend is currently running Arconium ICS on his Xperia, and now when I tried to install CM9 (Did full wipe > install CM > install gapps in CWM) it just gets stuck at the boot logo (SONY). After recovering the backup of Arconium in CWM it boots up fine again.
Since the boot logo didn't change, I'm thinking CM9 maybe didn't install a new kernel or something? Is there something I can do to make sure that CM9 fits as well as possible? If kernel switching is on the table I'd like to be able to do this from CWM.
Thank you!
Click to expand...
Click to collapse
Obviously you didnt flash the kernel..and before doing that u need to make sure if ur bootloader is unlocked..if it is unlocked then only you can proceed with flashing the kernel and then installing the ROM.

Same Here!!
but Nothin seems to b workin for me!! Ive Done everything as per da instructions!
I flashed the boot.img file which i unzipped from the cm9 nozomi.zip file!!
I formatted the data, the cache and the dalvik cache and then installed the cm9 and gapps files as well and then when i reboot my device from the recovery menu it just gets stuck at the boot screen of free xperia!!
(
pleasehelp!!

Assistere said:
Same Here!!
but Nothin seems to b workin for me!! Ive Done everything as per da instructions!
I flashed the boot.img file which i unzipped from the cm9 nozomi.zip file!!
I formatted the data, the cache and the dalvik cache and then installed the cm9 and gapps files as well and then when i reboot my device from the recovery menu it just gets stuck at the boot screen of free xperia!!
(
pleasehelp!!
Click to expand...
Click to collapse
Dude, nozomi is only for Xperia S device. You installed the wrong ROM!
Go check the supported devices list to find your device's codename.

Someguyfromhell said:
Dude, nozomi is only for Xperia S device. You installed the wrong ROM!
Go check the supported devices list to find your device's codename.
Click to expand...
Click to collapse
Dude mine is Xperia s is only!!
sorry i frgt to mention bout my phone earlier!!!

Assistere said:
Dude mine is Xperia s is only!!
sorry i frgt to mention bout my phone earlier!!!
Click to expand...
Click to collapse
Then you are at wrong forum.

[Q] Incredible 2 Bootloop and ROM Problems

Hey Guys Thank You For Taking A Look At My Thread.Lets Cut To The Chase.I Have A HUGE PROBLEM with my Replacement Incredible 2.I Rooted my phone with Tacoroot,and everything was fine.Flashed Condemed CM7.2 and started realizing i didn't like it as much,so i made a BACKUP just in case i wanted to return to the CM goodness.Went to TSMTrinity's Sense 2.1 Version 4.5 S,and here's where the problem started happening. After I set up everything on my Sense 2.1 ROM,i backed it up,the screen would get to the boot animation,get past the boot animation,id see my lock screen for 1 SECOND,and then it would start the bootup again.seeing as this was a problem,i WIPED All Cache and Factory Reset/Wipe Data on My Revolutionary Recovery.Then,I Restored the 2.1 Backup that i created and everything was fine again.Then again,i decided to Flash Mikrunny's Sense 3.5 ROM,which after i set up,worked fine,UNTIL YESTERDAY.I was driving in my car yesterday,listening to music on The STOCK HTC Music app on Sense 3.5,and the phone rebooted on its own.And it would not stop until i took the battery out.I got home,charged the battery for a bit,(shut down that is),then headed to recovery.I took out the SD card and rebooted the phone,but no luck.tried this rebooting process for an hour,until i decided to wipe cache and factory reset to my 2.1 ROM BACKUP.it works,but i just wanna know,am i doing something noobingly wrong when backing up and restoring roms? Also,i use Revolutionary's Backup,or I think its called Nandroid,to do backups and restores,and ROM MANAGER to edit their names and delete them.Also,an added side to his problem,when i boot to the Hboot screen,when it loads,for a few of the items it says,missing or wrong image.could that be the problem?? THANK YOU SO MUCH WHO REPLIES AND HELPS.:crying:

DroidUser_Wind said:
Hey Guys Thank You For Taking A Look At My Thread.Lets Cut To The Chase.I Have A HUGE PROBLEM with my Replacement Incredible 2.I Rooted my phone with Tacoroot,and everything was fine.Flashed Condemed CM7.2 and started realizing i didn't like it as much,so i made a BACKUP just in case i wanted to return to the CM goodness.Went to TSMTrinity's Sense 2.1 Version 4.5 S,and here's where the problem started happening. After I set up everything on my Sense 2.1 ROM,i backed it up,the screen would get to the boot animation,get past the boot animation,id see my lock screen for 1 SECOND,and then it would start the bootup again.seeing as this was a problem,i WIPED All Cache and Factory Reset/Wipe Data on My Revolutionary Recovery.Then,I Restored the 2.1 Backup that i created and everything was fine again.Then again,i decided to Flash Mikrunny's Sense 3.5 ROM,which after i set up,worked fine,UNTIL YESTERDAY.I was driving in my car yesterday,listening to music on The STOCK HTC Music app on Sense 3.5,and the phone rebooted on its own.And it would not stop until i took the battery out.I got home,charged the battery for a bit,(shut down that is),then headed to recovery.I took out the SD card and rebooted the phone,but no luck.tried this rebooting process for an hour,until i decided to wipe cache and factory reset to my 2.1 ROM BACKUP.it works,but i just wanna know,am i doing something noobingly wrong when backing up and restoring roms? Also,i use Revolutionary's Backup,or I think its called Nandroid,to do backups and restores,and ROM MANAGER to edit their names and delete them.Also,an added side to his problem,when i boot to the Hboot screen,when it loads,for a few of the items it says,missing or wrong image.could that be the problem?? THANK YOU SO MUCH WHO REPLIES AND HELPS.:crying:
Click to expand...
Click to collapse
1..update your recovery which is probly clockwork mod....i suggest you get your phone usable for a few minutes and go to 4ext.net and download and install that..its touch based recovery or also check out twrp if you want an alt if you dont like it
2....update your radio ...newest one can be found in the venom rom thread i think there are directions there http://forum.xda-developers.com/showthread.php?t=1953899
3.....wipe everything ....check out my wipe script in the dev section if you want max cleanification http://forum.xda-developers.com/showthread.php?t=2013242
4...flash what ever rom...if you like sense use viper i hear good things or check out my incredibly paranoid rom or all the other roms ..pick your poison

chillybean said:
1..update your recovery which is probly clockwork mod....i suggest you get your phone usable for a few minutes and go to 4ext.net and download and install that..its touch based recovery or also check out twrp if you want an alt if you dont like it
2....update your radio ...newest one can be found in the venom rom thread i think there are directions there http://forum.xda-developers.com/showthread.php?t=1953899
3.....wipe everything ....check out my wipe script in the dev section if you want max cleanification http://forum.xda-developers.com/showthread.php?t=2013242
4...flash what ever rom...if you like sense use viper i hear good things or check out my incredibly paranoid rom or all the other roms ..pick your poison
Click to expand...
Click to collapse
DUDE.THANK YOU so MUCH FOR REPLYING.Ill try what you told me tonight,and ill let you know how it goes down.thanks again chills.:good:

chillybean said:
1..update your recovery which is probly clockwork mod....i suggest you get your phone usable for a few minutes and go to 4ext.net and download and install that..its touch based recovery or also check out twrp if you want an alt if you dont like it
2....update your radio ...newest one can be found in the venom rom thread i think there are directions there http://forum.xda-developers.com/showthread.php?t=1953899
3.....wipe everything ....check out my wipe script in the dev section if you want max cleanification http://forum.xda-developers.com/showthread.php?t=2013242
4...flash what ever rom...if you like sense use viper i hear good things or check out my incredibly paranoid rom or all the other roms ..pick your poison
Click to expand...
Click to collapse
What OP wrote applies to me as well. I am looking for something better than aerovan's CM9 (which has been my DD), and thought I would give Viper a try. Without fail, bootlooping (which I could have guessed since I did tacoroot and this seems to be an issue with sense based roms).
That said, I tried steps 1 through 4 and the bootlooping stopped in Viper - it goes through startup and just shuts down before leaving the boot screen. One strange thing that I noticed is that the ICS Firmware/radio with Viper (which I loaded in CWM), wouldn't load in 4ext. Maybe I'll give paranoid a go if I can't resolve this bootlooping issue in Viper! I hope OP has better luck.

U don't flash radio in cwm..look for a how to.. can't explain I'm working sry
Sent from my Incredible 2 using xda app-developers app

I'm not as knowledgeable as Chilly, but a thought did occur to me. if the cm9 rom included a kernel on the flash and then you went to a sense based rom that didn't include a kernel that could cause a problem. I believe that I read that cm using a kernel that is asop based while sense roms use a different based kernel. You may check to see what kernel you have and then check for the recomended kernel for that rom and flash that kernel. don't forget to wipe.

Jasonp0 said:
I'm not as knowledgeable as Chilly, but a thought did occur to me. if the cm9 rom included a kernel on the flash and then you went to a sense based rom that didn't include a kernel that could cause a problem. I believe that I read that cm using a kernel that is asop based while sense roms use a different based kernel. You may check to see what kernel you have and then check for the recomended kernel for that rom and flash that kernel. don't forget to wipe.
Click to expand...
Click to collapse
All of the roms come with a kernel for our phone, but certainly, don't flash a sense kernel with aosp or vice versa after rom flash. Chilly is right. Flashing a newer radio should fix the problem and the radio is flashed with a PG32IMG.zip in the bootloader, not in the recovery.

gtdtm said:
All of the roms come with a kernel for our phone, but certainly, don't flash a sense kernel with aosp or vice versa after rom flash. Chilly is right. Flashing a newer radio should fix the problem and the radio is flashed with a PG32IMG.zip in the bootloader, not in the recovery.
Click to expand...
Click to collapse
Good call. When chilly said you don't flash kernels in recovery I hit my head. I flashed the radio, but now my challenge is getting back into recovery since I renamed the file and bootloader always finds it and wants to reboot or I load CM9 which stays on flash screen. I'll figure something out, maybe with adb. Thanks.

Power down, pop the sd out, boot to recovery, rename file, profit.

gtdtm said:
Power down, pop the sd out, boot to recovery, rename file, profit.
Click to expand...
Click to collapse
Didn't think of that. adb did the trick though. In business with VenomInc!
Thank you all.

digitalshepard said:
Didn't think of that. adb did the trick though. In business with VenomInc!
Thank you all.
Click to expand...
Click to collapse
good lucking going back to aosp lol

almost thesame problem
chillybean said:
U don't flash radio in cwm..look for a how to.. can't explain I'm working sry
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
i made a stupid mistake of flashing radio in recovery, in fact the radio is for Samsung at&t and now my phone vibrates it doesnt show htc quietly brilliant, only vibrates and orange light with black screen untill i pull out the battery... i was able to return to stuck and it can only boot if its connected to power, it doesn't read sd card while android is booted and in recovery to, only in bootloader it reads sd... error in mounting if i try to... i flashed RUU.exe 2.3.3 and 2 other RUUs for my droid inc 2 but it keeps vibrating... please help me!!! thanks

I made the same mistake when i first gained s-off for my dinc2. the thing with the venom rom tho is if you ever want to go back to aosp ull need to gets chill's anti-venom zip and flash it through recovery because doing a normal wipe wont do the trick. also a helpful trick that worked for me with roms if i ever start getting boot loops i go into recovery from the bootloader menu and i wipe the dalvik cache under advanced and then wipe the chache under mounts and storage and it always works like a charm for me. but ive also learned that you have to be careful which kernel you flash with the rom of your choice because not only will it cause lags if you happen to get past the boot animation to the main screen but in some cases it can cause breaks in your framework like your wifi data etc. im not an expert tho those are just suggestions that im familiar with because theyve already happened to me before. hope this helps in any way.