Related
well i am a little lost... i tried to update the kernel to the newest version of savaged zen. But got stuck on the white screen, so i went back and wiped both catches again, then i got to the boot animation and now thats looping.. okay so i made a backup before starting but now after wiping everything and restoring the backup is boot looping too. Any suggestions?
Try another kernel. I am using the BCblend kernel from november, it's awesome and very stable. Once you get it booted, go into your advanced wifi settings and set your sleep policy to never.
well... my backup boot loops too... wouldnt the backup have the old kernel?
It's possible your phone doesn't like that kernel either, mine didn't. How long were you running it before flashing the new kernel? I would try at least a couple more kernels and if you still can't get it booted then wipe and start over. What version of MIUI are you running?
In my opinion...if you have a good working kernel do not change it. From what ive seen every custom rom is based off a stock rom that comes with a kernel. Usually only custom kernels that match the rom version work well. So it could be the rom and the kernel dont work well together. One thing is nobody seems to list which kernel version is from which rom. So its hard to tell. Also I think your pri version will mess with compatability also. Basically newest rom versions should work with newest kernels. But if your on an older rom...the older kernels will probably work better. And usually kernels come out (it seems) before rom versions. Like new miui kernel supports 4g, but the rom does not support it yet. Also nandroid? backups should have the kernel also. Not sure bout miui backup. But wiping and installing it fresh usually works well. If not you know the deal..wipe everything..then flash the rom..and start over So.....find a good one...keep it=no issues
Evo - Myn 2.2 RLS 3 - Clockwork - HBoot .76
Hello, I could use some help with my Desire.
A few months ago I rooted my HTC Desire (Bravo, EU version) with Unrevoked3 and then tried a couple ROMS, like CM6 and MIUI. The installations all went fine without any problems and the ROMS worked as advertised.
I decided to go back to the stock 2.2 because of some app compatibility issues, using the backup I made from the recovery tool and have stayed with it since.
Now, whenever I try to install a newer ROM, like Aurora v04 or PyramidMod007, the installation never works, even though I always wipe/factory reset/wipe Dalvik cache before installing. The post-installation booting always freezes on the HTC logo screen for more than 20 minutes and I'm forced to remove the battery and restore my backup image.
The only ROM that I've tried and works is the latest MIUI.
Can anyone tell me what I'm doing wrong?
Are you wiping?
Are you downloading versions that fit in the stock hboot, NOT cm7 hboot?
Are you following ALL the instructions/requirements in the rom threads, including required partitions on SD card?
Hey folks,
Im new to the whole custom roms & kernel business but already experiencing the benefits and enjoyment behind tweaking my Arc S.
Ive managed to unlock my bootloader and get Jelly Sandwhich 5.0 running using the Lupus v5 kernel but decided to upgrade to the latest version of the kernel which is 5.2.
Carried out all the usual steps and reinstalled my custom rom only to find my phone hanging on the boot logo.
Luckily I had a backup so could easily restore but am wandering what it is I have done wrong as the last few times ive been messing around with it, it worked like a charm, am I supposed to re-flash to stock kernel before flashing to a new kernel?
Would ask in the developers thread itself but am stuck with my nooby post limit of 1 so cannot reply or give thanks to all those involved.
If you've reinstalled a different ROM then you should have cleared data and caches, if it's stuck on the updated kernel then it's possibly a kernel problem. And you don't need to flash the whole ROM if just updating the kernel.
No problems reported in the development thread so must have been an issue at my end. Noticed I was on an older flashtool version so will update
to latest version wipe everything and try again.
Any resolution to this problem? This has been reported in several threads (link 1, link 2, link 3, need I give more?)
I'm also experiencing the same problem. I installed Paranoid Android (per instructions here) and am now experiencing the same problem. After flashing, the phone continuously reboots. I am using an HTC One V (CDMA) from the US. I also flashed the JB 4.1.2 gapps with the ROM flash process.
When it boots, I receive two errors: "Unfortunately, android.process.acore has stopped working" and "Unfortunately, Contacts has stopped working". When I lock the screen, it reboots. When I try using it, it reboots after 30 seconds. If I just leave it alone, it reboots.
I have also tried several kernels with this same ROM (kernel that comes with the ROM, SuperSick [found here], and stock CM10) and they all just produced the same behavior.
I've looked all around. Some possibilities are: bad kernel, memory (RAM or otherwise) running out, bad install of ROM, or something no one has yet to define. I don't think its a bad kernel because this happens in 3 different ones. I don't think it's a memory issue because I lowered the CPU clockspeed and the phone has plenty of storage memory, and I've also flashed AOKP with the same results which rules out a bad ROM install.
I've wiped cache, system, data, and dalvik and followed all instructions as given to get a completely fresh installation. No avail. I realize that the One V isn't very popular, and there is only a limited amount of support for it but could anyone shed some light as to what the problem could be?? Perhaps some of the original devs who made the ROMs can help out us lowly fools who can't get it to work? I thank anyone in advance for being awesome and at least trying to help.
You may have to flash the old RUU. Look in the General subforum for a thread about phone rebooting after one minute.
sounds like you did the OTA update and have the new radio version, you need to RUU back to stock and dont get the OTA.
I'll try.
Thanks both of you! I will try flashing the RUU and I'll make sure to not install the OTA update. I'll post later with my results.
...
So... I flashed the RUU on the phone again. I again carefully followed instructions on how to flash ROMs (AOKP and Paranoid) and it simply doesn't boot. AOKP's ROM only starts up to a black screen. Paranoid boots to the boot screen animation and just hangs... I've used stock kernels, and tried the SuperSick kernel with both. No progress. Any other ideas?
Try the latest version of cm10 with the latest version super sick kennel. That's what I'm running. AOKP has a few versions that boot to a black screen. If you want AOKP use the latest stable version.
Awesome!
riggerman0421 said:
Try the latest version of cm10 with the latest version super sick kennel. That's what I'm running. AOKP has a few versions that boot to a black screen. If you want AOKP use the latest stable version.
Click to expand...
Click to collapse
Riggerman0421, thanks a ton for the suggestion!! It worked! Despite not being able to use the other roms, I think I can settle with using CM10.
htc one v
filoxo said:
Riggerman0421, thanks a ton for the suggestion!! It worked! Despite not being able to use the other roms, I think I can settle with using CM10.
Click to expand...
Click to collapse
Hey I am having the same problem as you with my htc one v. What did you do exactly to fix this?
lytesson said:
Hey I am having the same problem as you with my htc one v. What did you do exactly to fix this?
Click to expand...
Click to collapse
You have to RUU your device back to the original radio version; it was changed when you accepted the OTA update. That means that you're going to have to flash it to complete stock (no recovery, HTC Sense, booloader relocked, etc.) using the RUU. The forum I found that had all of the different RUUs was deleted unfortunately. You'll have to do careful research for the RUU for your specific device. I only know that Virgin Mobile in the U.S. uses the Sprint towers, so the RUU I used was titled "RUU_PRIMO_C_ICS_40A_Sprint_WWE_VM_1.08.652.6_Radio_1.00.00.0521_2_NV_VM_3.46_0503_PRL61008_release_262414_signed". Just a quick search on XDA and found this forum that has a download link to the RUU you would need for VM [CDMA] phone (read the comments); you can also look around yourself to make sure you have the right one.
You can find specific instructions on how to RUU your device at this awesome forum. It should only take, literally, 15-20 minutes.
After that is done, you will need to unlock your bootloader again and then you're ready to move on to bigger and better ROMs.
filoxo said:
You have to RUU your device back to the original radio version; it was changed when you accepted the OTA update. That means that you're going to have to flash it to complete stock (no recovery, HTC Sense, booloader relocked, etc.) using the RUU. The forum I found that had all of the different RUUs was deleted unfortunately. You'll have to do careful research for the RUU for your specific device. I only know that Virgin Mobile in the U.S. uses the Sprint towers, so the RUU I used was titled "RUU_PRIMO_C_ICS_40A_Sprint_WWE_VM_1.08.652.6_Radio_1.00.00.0521_2_NV_VM_3.46_0503_PRL61008_release_262414_signed". Just a quick search on XDA and found this forum that has a download link to the RUU you would need for VM [CDMA] phone (read the comments); you can also look around yourself to make sure you have the right one.
You can find specific instructions on how to RUU your device at this awesome forum. It should only take, literally, 15-20 minutes.
After that is done, you will need to unlock your bootloader again and then you're ready to move on to bigger and better ROMs.
Click to expand...
Click to collapse
So, this happend to my htc and I ruu'ed back to stock, after continunously trying to install roms with constant bootloops. I did the ota update again. So if I want to install a custom rom your saying DONT do the ota after ruu'ing then install one after rooting?
I've got a similar issue (virgin mobile HTC One V)
I currently have TWRP recovery installed, and I attempted to flash the jellybean CM10 as well as the AOKP rom, and I got as far as the unicorn and I actually manged to get the phone to boot to the main screen with all the icons, but it would constantly reboot after being on for maybe a minute
I tried flashing everything back to stock including restoring a backup I had previously taken with TWRP, but no luck
I also tried flashing the stock rom downloaded somewhere here on XDA and I even flashed the stock recovery, but all I got was constant rebooting.
it would get as far as the startup animation and then reboot indefinitely
I'm at a total loss here. I've seen a few links with some resources that look like they might have been helpful (like on this thread) but the links are dead, and I also read somewhere that HTC was putting the kibosh on a site that had some stock roms.
I'd prefer to get jellybean working on my phone, but ultimately, I just want a working phone.
I've followed the process of installing the rom - some instructions said to flash the boot img before flashing the rom, some say after
I've tried both methods
I went into recovery, mounted the usbmsd and copied the rom, and used recovery to install the rom after having cleared the cache, davlik cache and wiping the data (factory reset)
I also installed the gapps package after the rom, but I don't think that's critical to getting it to just boot.
The OTA update reboots were fixed in the latest 4.2 SickleKernels.
Sent from my One V using Tapatalk 2
bheadrick said:
I currently have TWRP recovery installed, and I attempted to flash the jellybean CM10 as well as the AOKP rom, and I got as far as the unicorn and I actually manged to get the phone to boot to the main screen with all the icons, but it would constantly reboot after being on for maybe a minute
I tried flashing everything back to stock including restoring a backup I had previously taken with TWRP, but no luck
I also tried flashing the stock rom downloaded somewhere here on XDA and I even flashed the stock recovery, but all I got was constant rebooting.
it would get as far as the startup animation and then reboot indefinitely
I'm at a total loss here. I've seen a few links with some resources that look like they might have been helpful (like on this thread) but the links are dead, and I also read somewhere that HTC was putting the kibosh on a site that had some stock roms.
I'd prefer to get jellybean working on my phone, but ultimately, I just want a working phone.
I've followed the process of installing the rom - some instructions said to flash the boot img before flashing the rom, some say after
I've tried both methods
I went into recovery, mounted the usbmsd and copied the rom, and used recovery to install the rom after having cleared the cache, davlik cache and wiping the data (factory reset)
I also installed the gapps package after the rom, but I don't think that's critical to getting it to just boot.
Click to expand...
Click to collapse
I think I'm having the same problem. The phone boots, gets as far as the "this build is for development purposes..." and then hangs for a few minutes and restarts, over and over. The flash with fastboot seemed to work fine and reported no errors.
EpicLordPhone said:
So, this happend to my htc and I ruu'ed back to stock, after continunously trying to install roms with constant bootloops. I did the ota update again. So if I want to install a custom rom your saying DONT do the ota after ruu'ing then install one after rooting?
Click to expand...
Click to collapse
Yes. Do NOT install the update if you want to flash another ROM onto your device. Use the RUU to get the device back to factory; this will restore the original radio version. Then go through the steps to unlock the bootloader, root, and flash your ROM as desired. There are other forums which explain the mentioned processes better.
BeyondExistence says that this is fixed with a "4.2 SickleKernel", but as far as I'm aware there are no JB 4.2 ROMs for the HTC One V. Maybe a little more information would be in order?
Bheadrick:
I'm not quite sure what you mean when you say you flashed the stock recovery. The One V doesn't have a recovery when everything is stock.
You will have to RUU your device back (have you read any of the posts in this and other forums??). The process will reinstall the stock rom, relock your bootloader, remove the recovery, etc.
I recommend that you use Paranoid android's rom with the latest SuperSick kernel. Its been my favorite and most stable build I've used.
Sent from my Nexus 7 using xda app-developers app
So I found what BeyondExistence might have been talking about (for those of you who care/are currently having the bootloop problem and would rather go with this route). Its called RhythmicRom. This is a 4.2.2 ROM and it has some cool things for users switching from Sense to a more-pure Android [Link here]. Its based off of CM10.1 for the One V and it includes the BeatsAudio app (which most ROMs don't, as far as I know).
The reason I think that this is worth mentioning is because whoever runs into this bootlooping problem can simply SKIP the RUU process and just move onto this ROM. Hit thanks if this helped!
Newest OTA update.
As some of you may have seen, there's an even newer OTA Update available through the stock ROM. As always, this will cause problems when you try to flash a different kernel, resulting in bootlooping (can anyone who has done the newest update confirm?). Anyway, I've also read that this update also updates your hboot (which, since I haven't and will not apply the update, don't know why it would impede you from flashing any other ROM/kernel but it does) and radio version.
I've looked for additional ROMs who try and make their builds compatible, but so far only RhythmicRom has done anything worthwhile (in my opinion). His latest v 1.3 build will be out soon, and I highly recommend it.
If you flashed both OTA updates, then please be sure to include that when making any post.
filoxo said:
As some of you may have seen, there's an even newer OTA Update available through the stock ROM. As always, this will cause problems when you try to flash a different kernel, resulting in bootlooping (can anyone who has done the newest update confirm?). Anyway, I've also read that this update also updates your hboot (which, since I haven't and will not apply the update, don't know why it would impede you from flashing any other ROM/kernel but it does) and radio version.
I've looked for additional ROMs who try and make their builds compatible, but so far only RhythmicRom has done anything worthwhile (in my opinion). His latest v 1.3 build will be out soon, and I highly recommend it.
If you flashed both OTA updates, then please be sure to include that when making any post.
Click to expand...
Click to collapse
I got my One V at the end of December and did the OTA update at the beginning of April. Last week, I decided to try messing with loading some different ROMs and have encountered all of the problems you've mentioned (e.g., boot-looping, inability to RUU back to stock). I have successfully gotten RhythmicRom to load using this OTA_support.zip (which has been incorporated into the regular release since I flashed it). I have also gotten the most recent version of PACman v22.1 to run (using the same kernel as RhythmicRom) without boot-looping, but the performance hasn't been great (browser crashes frequently and it seems like the launcher has to restart a lot). User demi_fiend has said that the PACman ROM will work using the CodefireX kernel from user BeyondExistence.
I had also tried to revert back to my stock CWM recovery, but it had the boot-loop problem too. However, demi_fiend has also informed me that you can revert to a stock backup by using the boot.img file that is located in the backup folder. I haven't had the chance to verify this, but I wouldn't be surprised if it were true.
It's a bit of a pickle being unable to revert back to previous radio versions, but there is hope that some of the devs will incorporate this issue into their new builds.
tallnproud said:
I got my One V at the end of December and did the OTA update at the beginning of April. Last week, I decided to try messing with loading some different ROMs and have encountered all of the problems you've mentioned (e.g., boot-looping, inability to RUU back to stock). I have successfully gotten RhythmicRom to load using this OTA_support.zip (which has been incorporated into the regular release since I flashed it). I have also gotten the most recent version of PACman v22.1 to run (using the same kernel as RhythmicRom) without boot-looping, but the performance hasn't been great (browser crashes frequently and it seems like the launcher has to restart a lot). User demi_fiend has said that the PACman ROM will work using the CodefireX kernel from user BeyondExistence.
I had also tried to revert back to my stock CWM recovery, but it had the boot-loop problem too. However, demi_fiend has also informed me that you can revert to a stock backup by using the boot.img file that is located in the backup folder. I haven't had the chance to verify this, but I wouldn't be surprised if it were true.
It's a bit of a pickle being unable to revert back to previous radio versions, but there is hope that some of the devs will incorporate this issue into their new builds.
Click to expand...
Click to collapse
Did you flash stock recovery and lock bootloader before running RUU?
Lsesp said:
Did you flash stock recovery and lock bootloader before running RUU?
Click to expand...
Click to collapse
I had flashed my stock recovery (although it was still boot-looping), and I did re-lock the bootloader before running the RUU.
I used the instructions found here.
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.