Related
I am a bit confused about what to do now. First off.. I have the Evo rooted with OS 2.1 but recently I just found out that 2.2 has been rooted. So now I just need to know what to do to get rooted 2.2. I read on some searches I did that I can just flash a 2.2 rom and that would be fine but I am a little concern about doing it that way. I was wondering if I need to UNROOT then download the over the air update that sprint has to get 2.2 then start my root process from there or is there a guide that someone can link me to in order for me to proceed? Thanks for your input.
Just find a rooted stock rom in the Development forums (or experiment with a custom rom. There are several that don't lose any functionality these days). Do a nandroid backup, and a Titanium backup of your apps and data before since I think you will need to do a data and dalvik cache wipe.
The alternative you proposed would probably take you all day and it would still wipe!
Think of it this way. All of the 2.2 ROMS you flash is just like an upgrade from Sprint. If you flash the 2.2 OTA ROM its the same thing as getting from Sprint, but you don't lose root user access. Hope this clears it up a little. No need to jump through all the hoops you referenced.
So its has been a while since I did anything with my phone so I had to youtube how to flash a rom. When I get to the part where I select recovery it goes to a screen with a phone image with a red ! mark on it. What does that mean? Maybe I might just take path of unrooting this 2.1 and upgarding to 2.2 then root from there? Can someone direct me which steps to take? thanks
Whatever you do.....DON'T FLASH YOUR RADIO AND WIFI. You'll be screwed. Has taken me 24 hours + to get my ability to tether wirelessly back on my rooted 2.2 (I'm not complaining. the rooted 2.2 ROM is freagin awesomeness!)Just in case you do by accident there's lots of info out there on how to try to dig yourself back out.
Don't unroot your 2.1 dude.
ROM's are ROM's. It doesn't matter if it's 2.1 or 2.2, you can flash either one and flash back and forth between the two at your own leisure. Back before 2.2 was officially out for the evo, I used to flash back and forth between working 2.1 and experimental 2.2 on almost a daily basis. They always booted fine, my phone did not explode.
Reboot with volume key down, select recovery, wipe everything, flash the new rom, reboot.
You don't have a custom recovery installed, do you remember if your NAND is unlocked?
If you need to check turn off your phone and then turn it back on while holding the volume down button. At the top of the screen it should say either S-ON or S-OFF and below it an hBoot version. If it is S-OFF and ver .76 it should be simple for you to update it.
Thanks for the input guys. So I guess the final word is to not unroot my phone and just flash. Now to my problem with recovery mode.
Haus, it says S-ON and hboot is veryson 0.79.0000. Is this a problem? Can you guide me on what steps to take or what should i search for? thanks again.
still wasn't able to find information on this. anyone can link me? thanks
can anyone link me to where i should start?
well your going to want to make sure you have a custom recovery, when your in the bootloader scroll to recovery and click on it, if anywhere it says clockwork or amon ra, your set and then you only need to flash unrevoked forever to turn your s-off and then you can start flashing 2.2 roms from the htc evo android development section
if you do not have a custom recovery just head on over to unrevoked.com and download their latest for the evo, it will give a custom recovery and flash your s-off for you and youll be ready to roll
I tried and the problem I am having is when I select the recovery option it reboots and then shows a phone with the ! sign. Doesn't let me flash anything. This is where I am stuck now.
As mentioned before, you need to install a custom recovery on your phone. If you are rooted, then perhaps you can download ROM Manager and installed ClockworkMOD?? You can also change to Amon_RA as well through ROM Manager. Otherwise, in the unrevoked forever wiki, they do provide PC36IMG files that should install a custom recovery on your phone (take your pick of either ClockworkMOD or Amon_RA).
http://unrevoked.com/rootwiki/doku.php/public/forever#reinstalling_an_official_recovery
Scroll down to "Reinstalling an official recovery" section and you will see the links for the PC36IMGs.
Alright so I just remembered what that phone icon with the red ! meant. I plugged it back into my win7 machine and ran windowrecovery.bat and I somehow managed to flash it to s=off. So now all I have to do is select the rom I want to flash?
Rom manager
if you have a custom recovery, then yes download a rom from the development section and move it to the root of the sd card. Boot into recovery and wipe your dalvik and data. Go bac and choose install .zip from sd card. Find the file you downloaded and flash it. Wait for it to boot up and your good. Orrrrr download rom manager from the market and you can do all this from there.
Just finished rooting my phone now I want to know how to get gingerbread on it tried
Doing a couple of roms but none work any advices???
What roms did you try and why didn't they work? It will help if you give us some more details.
And welcome to the forums.
Sent from my T-Mobile G2
Search the market for Rom Manager. Please make sure your phone is fully rooted, (S-Off).
I hope this helps you bub.
kboogi said:
Please make sure your phone is fully rooted, (S-Off).
Click to expand...
Click to collapse
Yeah, you need to be rooted AND S-Off. If you don't know, you can verify S-Off by powering down, then holding the volume down button while pressing the power button. When the screen comes up, there will be some text, and one of the lines at the top will say S-Off or S-On.
Go to market and download ROM Manager to get ClockworkMOD recovery flashed on your phone. Go to the dev section and choose a GB ROM, I suggest RMK's Virtuous G-Lite 1.0.2 as it is overclockable via SetCPU to 1.5GHz and is AOSP GB.
As posted above, make sure you have root and S-OFF as this will ensure that you are set for flashing roms.
To flash is simple, not sure if you have flashed before so I will post this anyways.
Download the rom you want to try and place in the root of your sd card. Once you have CWM flashed, use ROM Manager to boot into recovery. Go to backup/restore and perform a backup of your current setup. Then go to wipe and wipe data, cache and battery stats. After, head to flash zip from sd and select the rom zip, let it do its thing and you should be in business! First boot is always longest and should always perform a cold boot after a flash to settle things down before you use it.
Have fun!
Sent from my T-Mobile G2 using XDA App
Hey guys,
So here's what happened and is happening:
1. I was running a custom ROM (Baked Snack 1.7) on Froyo (2.2). The phone was working fine but I wanted to try Gingerbread 2.3.3 out because I heard it had great battery life.
2. My phone would not update to 2.3.3 from Baked Snack. I thought it might have something to do with it being rooted. I used this method to unroot...and I think I only got through the first part:
http://www.thedroiddemos.com/2010/09/10/how-to-unroot-the-evo-in-2-steps/
I installed the S-On tool like he said to. Then I moved the "new updated version" of PC36IMG (I had the old version on my card already). He said something about the "S-Off" appearing on his phone but not the viewer's...well, mine says S-Off.
So fast forwarding, I got Sprint to push me the update for 2.3.3. It downloaded it, but then a voicemail error came up saying I had 2 voicemails. Then when I called voicemail, it said I had no messages. Sprint said a Sprint store would have to physically go into the phone to erase the error.
I also got a second update message that said there were minor enhancements to Gingerbread. I tried downloading them but the installation failed. Sprint told me to ignore the update, that there had been issues with Gingerbread (and the update) and that they were working on getting these resolved.
Somehow I managed to clear the phone and get back to 2.1. Here's what my system says when I look at the Phone Information:
Firmware Version: 2.1-update1
When I boot into the main bootloader/Recovery menu (Phone Off + Power Button + Volume Down), here's what it says:
Supersonic EVT2-2 ENG S-OFF
HBOOT-0.76.2000 (PC3610000)
If I click down to Recovery from this menu and press "Power" to enter it, NOW I get a picture of an EVO with a Red Triangle/Exclamation Point. This means I have to take my battery out and restart the phone.
Also, the OTA SimpleRoot procedure doesn't seem to work on the phone either. When I originally set it back, the procedure worked. Now it just goes through the motions on the computer but nothing happens with the phone (rebooting, skating Androids, etc.)
All I want to do is basically put it back 2.2 and re-run Baked Snack 1.7 which was giving me NO issues.
If someone could help me with this issue, I would be very grateful.
Well you have a simple fix. The error you got with the triangle and red ! is you booting into recovery, but no recovery is loaded [stock recovery]. Head over to the development section, and download the recovery of your choice. Personally I recommend in order: twrp [team win recovery project] , amon ra 2.3, cwm 3.0+. After you have your recovery installed, boot back into recovery and flash your baked snack rom. Also, don't manually take an OTA of 2.3.3 as it can't be rooted. if you want to try a gingerbread rom, simply download CM7, evervolv, deck's, ect rom and flash it like any other rom. Just backup your previous rom before flashing so you can go back.
teh roxxorz said:
Well you have a simple fix. The error you got with the triangle and red ! is you booting into recovery, but no recovery is loaded [stock recovery]. Head over to the development section, and download the recovery of your choice. Personally I recommend in order: twrp [team win recovery project] , amon ra 2.3, cwm 3.0+. After you have your recovery installed, boot back into recovery and flash your baked snack rom. Also, don't manually take an OTA of 2.3.3 as it can't be rooted. if you want to try a gingerbread rom, simply download CM7, evervolv, deck's, ect rom and flash it like any other rom. Just backup your previous rom before flashing so you can go back.
Click to expand...
Click to collapse
You like TWRP better??
I haven't tried it yet
HipKat said:
You like TWRP better??
I haven't tried it yet
Click to expand...
Click to collapse
Basically amon ra, but better. it has some additional options, such as the option to automatically reboot after a successful flash [good for doing a single flash, but if you're doing multiple, checked it at the last flash.] You have the option to compress backups to save space, though it takes a little bit longer, and they have some built in skins you can change at will. And MOAR.
I tried rooting using this method:
http://www.androidcentral.com/evo-4g-root-instructions
I put the PC36IMG on the root of my SD card and let the phone update in bootloader. It seemed to work fine, updated, rebooted the phone, etc.
Then I downloaded ROM Manager so I could let Clockwork install and then install Amon Ra....when ROM Manager tried installing Clockwork, it gave me the following message: "An error occurred while attempting to run privileged commands!"
It also will not let me flash an alternate recovery. I have the file "recovery-RA-supersonic-v2.3.img" on the root of my SD card right now.
What does this mean? Does this mean I'm not rooted? Or some other issue? I remember eons ago when I tried using this program I got the same message but I don't remember how I got around it. (obviously I did though)
Is there a different way I should install it?
nbakid2000 said:
I tried rooting using this method:
http://www.androidcentral.com/evo-4g-root-instructions
I put the PC36IMG on the root of my SD card and let the phone update in bootloader. It seemed to work fine, updated, rebooted the phone, etc.
Then I downloaded ROM Manager so I could let Clockwork install and then install Amon Ra....when ROM Manager tried installing Clockwork, it gave me the following message: "An error occurred while attempting to run privileged commands!"
It also will not let me flash an alternate recovery. I have the file "recovery-RA-supersonic-v2.3.img" on the root of my SD card right now.
What does this mean? Does this mean I'm not rooted? Or some other issue? I remember eons ago when I tried using this program I got the same message but I don't remember how I got around it. (obviously I did though)
Is there a different way I should install it?
Click to expand...
Click to collapse
That's a bit outdated; use unrevoked. I've already done the linking for you.
1. http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install <- Download and install the modified hboot drivers, follow the instructions.
2. On your phone, enable usb debugging from the applications > development, in settings
3. Connect your phone to your pc via usb cable, leave it on the home screen, no apps should be running; restart the phone just to be sure.
4. http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install <- download and run unrevoked
It'll take 3-5 minutes and reboot about 2 times, don't touch in the process, it'll say done at the end. Also, this will only work if on 2.2 still. if on 2.3.3, you're outta luck.
Okay, forget Rom Manager, forget "rooting" your phone - at least according to the normal use of the word.
Delete any PC36IMG files you may have on your SD card, then download this one of Amon Ra 2.3: http://db.tt/WP0beNa
Don't rename it, don't extract it... just put it on the root of your SD card. Then download whatever rom you want to use. Put it on the root of your SD card or in a folder that you'll remember. Amon Ra (and possibly other recoveries) can flash zips that are inside of folders. Just be sure that you know where it is because you'll need to navigate to it in recovery.
Then boot into the bootloader and let it flash the way you've done with other PC36IMG files. When it asks you to reboot just decline and then select recovery. I would make a backup just in case, then flash your rom.
Sent from my PC36100 using Tapatalk
Thank you guys, I will try these methods when I get back from work tonight. I really really appreciate it, I was about having a meltdown without my phone (the way I want it).
I'll report back either way. (and yes, I'm still on 2.1-update1)
nbakid2000 said:
Thank you guys, I will try these methods when I get back from work tonight. I really really appreciate it, I was about having a meltdown without my phone (the way I want it).
I'll report back either way. (and yes, I'm still on 2.1-update1)
Click to expand...
Click to collapse
Well between plainjane and myself, you'll be rooted before dinner time!
teh roxxorz said:
Well between plainjane and myself, you'll be rooted before dinner time!
Click to expand...
Click to collapse
OK, I forgot to mention this earlier...last time I was stuck in the Boot Sequence where it kept looping the Sprint and 4G logo....now that I'm rooted using plainjane's method (thank you) I'm stuck with the same thing.
I flashed the recovery, then flashed the Baked Snack ROM....now I'm in the Baked Snack bootload section....and it just keeps looping.
Is this an issue with my system that can be resolved?
EDIT: So weird. I went back into Recovery and wiped everything and set the phone back to original condition...and voila, Baked Snack comes up as the ROM! So now it appears it's for the most part back to normal and back to where I wanted it....thank you guys again.
Now can anyone point me in the direction of the latest radios, etc. that I can download and flash?
And why would it be giving me those looping problems, and then go back to normal when I cleared/wiped everything?
I mean, I'm happy this happened but I don't want the same things happening if I decide to flash another ROM at some point.
If this has been asked before then please forgive me...
I can not go back to any backup I had of CM7 or Gingerbread Sense ROM since upgrading to some Alpha ICS roms. I've tried wiping everything & started from scratch on these roms but I always get stuck at "failed to write boot partition from /tmp/boot.img" It doesn't matter what Gingerbread ROM I choose with the exception of MIUI rom (don't know why). I thought maybe I could use that as a stepping stone to go back from there but nogo. I've used RA's recovery & CWM with no success. Any ideas?
davidnjessicacruz said:
If this has been asked before then please forgive me...
I can not go back to any backup I had of CM7 or Gingerbread Sense ROM since upgrading to some Alpha ICS roms. I've tried wiping everything & started from scratch on these roms but I always get stuck at "failed to write boot partition from /tmp/boot.img" It doesn't matter what Gingerbread ROM I choose with the exception of MIUI rom (don't know why). I thought maybe I could use that as a stepping stone to go back from there but nogo. I've used RA's recovery & CWM with no success. Any ideas?
Click to expand...
Click to collapse
I would recommend tracking down calkulins format zip for the evo
1brainsurgeon said:
I would recommend tracking down calkulins format zip for the evo
Click to expand...
Click to collapse
Yeah... tried that already... Didn't fix it...
davidnjessicacruz said:
If this has been asked before then please forgive me...
I can not go back to any backup I had of CM7 or Gingerbread Sense ROM since upgrading to some Alpha ICS roms. I've tried wiping everything & started from scratch on these roms but I always get stuck at "failed to write boot partition from /tmp/boot.img" It doesn't matter what Gingerbread ROM I choose with the exception of MIUI rom (don't know why). I thought maybe I could use that as a stepping stone to go back from there but nogo. I've used RA's recovery & CWM with no success. Any ideas?
Click to expand...
Click to collapse
I can say with certainty that I don't have this problem. I've flashed every ROM from here to Timbuktu, AOKP, Deck's, Evervolv, and have had no problem restoring a nandroid of, or flashing MikG, Mik3D, MikRunny, The Express, or any other ROM I may have forgotten.
That boot partition error doesn't sound good, though. What HBOOT version do you use?
Captain_Throwback said:
I can say with certainty that I don't have this problem. I've flashed every ROM from here to Timbuktu, AOKP, Deck's, Evervolv, and have had no problem restoring a nandroid of, or flashing MikG, Mik3D, MikRunny, The Express, or any other ROM I may have forgotten.
That boot partition error doesn't sound good, though. What HBOOT version do you use?
Click to expand...
Click to collapse
HBOOT 0.97 is what I'm still using... never upgraded... should I & how do you recommend that I do so?
davidnjessicacruz said:
HBOOT 0.97 is what I'm still using... never upgraded... should I & how do you recommend that I do so?
Click to expand...
Click to collapse
No reason to upgrade - just wondering.
I'd recommend you flash a stock ROM in the bootloader - that should normalize everything, and then try those other ROMs again.
Captain_Throwback said:
No reason to upgrade - just wondering.
I'd recommend you flash a stock ROM in the bootloader - that should normalize everything, and then try those other ROMs again.
Click to expand...
Click to collapse
I assume your talking about in the recovery (aka amon ra/ clockworkmod), if so then I've tried that as well. Same issue.... This is not sounding good for me.
davidnjessicacruz said:
I assume your talking about in the recovery (aka amon ra/ clockworkmod), if so then I've tried that as well. Same issue.... This is not sounding good for me.
Click to expand...
Click to collapse
I believe he's talking about a RUU
Sent from my PC36100 using XDA App
evo4gnoob said:
I believe he's talking about a RUU
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
The stock one? Wow... don't even know how to flash that back.... hmm... I'll see if I can find it here, if not then I'll google it. I'll keep you informed.... hopefully bricking does not ensue.... any help here would be great as well
davidnjessicacruz said:
The stock one? Wow... don't even know how to flash that back.... hmm... I'll see if I can find it here, if not then I'll google it. I'll keep you informed.... hopefully bricking does not ensue.... any help here would be great as well
Click to expand...
Click to collapse
In the first "My Links" link in my sig, there are 3 of them.
They're PC36IMG files - you rename the file to exactly that - PC36IMG.zip - and put the file on the root of your sd card. Then you reboot your device into bootloader (HBOOT) mode. From a powered off state, hold the Volume down button and then press and hold the power button until you see the HBOOT screen. The file should be recognized and loaded, and after a minute or so it will ask you to update. Press Volume Up to accept, and then wait for a while.
NOTE: This will upgrade your HBOOT, but that's no big deal. The phone will reboot into the bootloader once near the beginning of the process by itself - that is also okay. Don't touch anything while it's updating.
At the end of the process, you'll need to find a PC36IMG for your preferred recovery (RA-supersonic-v2.3 recommended), which you will flash the same way as the ROM (in fact, you can replace the ROM file with the recovery file - unless you want to hold on to it, then you can just move or rename it).
Captain_Throwback said:
In the first "My Links" link in my sig, there are 3 of them.
They're PC36IMG files - you rename the file to exactly that - PC36IMG.zip - and put the file on the root of your sd card. Then you reboot your device into bootloader (HBOOT) mode. From a powered off state, hold the Volume down button and then press and hold the power button until you see the HBOOT screen. The file should be recognized and loaded, and after a minute or so it will ask you to update. Press Volume Up to accept, and then wait for a while.
NOTE: This will upgrade your HBOOT, but that's no big deal. The phone will reboot into the bootloader once near the beginning of the process by itself - that is also okay. Don't touch anything while it's updating.
At the end of the process, you'll need to find a PC36IMG for your preferred recovery (RA-supersonic-v2.3 recommended), which you will flash the same way as the ROM (in fact, you can replace the ROM file with the recovery file - unless you want to hold on to it, then you can just move or rename it).
Click to expand...
Click to collapse
Failed on #4 Boot.... it stated "failed - PU" "Partition failed" Fun times.... Now the phone is a brick (stuck at the white screen).... Where there is a will then there is a way so I'll find a way.... any help would be appreciated though....
Sooo... I was able to flash back my alternate recovery using a PC36IMG version of it. Thank god for the rooted community.... Restoring back my last backup. Funny though, that I still could not restore a rooted stock backup I had or a new upgraded .zip that I wanted to use. Common denominator in all this (even when trying to use the 4.24.651.1 version of the stock software PC36IMG), it can not write the boot.img Any one else had this problem? Next I will try to RUU which will technically make me lose root but I should be able to get it back, assuming I'm successful, since I still have S-OFF.
PS: My HBOOT now, btw, is 2.16.0001 so I know that the original attempt to get back to gingerbread was succesful
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.