I nandroid to a sense rom and updated prl. Nandroid back to CM7 and then flashed Tiamat's latest kernel and Viperboy's aosp battery mod. Rom went into boot loop. I took out battery and went to recovery (using Amon-RA). However, in recovery, nothing shows up. I get a blank screen with just the build number of the recovery at the bottom of the screen.
Now my phone is useless and I need it as I am in clinical rotations in Akron and away from home. This is my only source for communication.
EDIT: I know this is the general section, but no one visits the Q/A section and I need immediate help.
jblazea50 said:
I nandroid to a sense rom and updated prl. Nandroid back to CM7 and then flashed Tiamat's latest kernel and Viperboy's aosp battery mod. Rom went into boot loop. I took out battery and went to recovery (using Amon-RA). However, in recovery, nothing shows up. I get a blank screen with just the build number of the recovery at the bottom of the screen.
Now my phone is useless and I need it as I am in clinical rotations in Akron and away from home. This is my only source for communication.
EDIT: I know this is the general section, but no one visits the Q/A section and I need immediate help.
Click to expand...
Click to collapse
Well if it were bricked it wouldnt even turn on so your ok. When u boot into recovery, let it sit for a minute. I've had this issue while on sense based roms. When I boot into recovey it takes a minute for the menu to actually show up. It's just black screen with the version of amon at the bottom. Don't know why it happens but give it a few minutes and see if it eventually shows up.
jblazea50 said:
I nandroid to a sense rom and updated prl. Nandroid back to CM7 and then flashed Tiamat's latest kernel and Viperboy's aosp battery mod. Rom went into boot loop. I took out battery and went to recovery (using Amon-RA). However, in recovery, nothing shows up. I get a blank screen with just the build number of the recovery at the bottom of the screen.
Now my phone is useless and I need it as I am in clinical rotations in Akron and away from home. This is my only source for communication.
EDIT: I know this is the general section, but no one visits the Q/A section and I need immediate help.
Click to expand...
Click to collapse
Is S-On in the bootloader? If not, reflash the recovery from the bootloader.
I flashed Amon 2.3 from 2.1 and that didn't help. Now I did PC36IMG.zip to stock, unrooted and it seems to work. I will root now.
jblazea50 said:
I flashed Amon 2.3 from 2.1 and that didn't help. Now I did PC36IMG.zip to stock, unrooted and it seems to work. I will root now.
Click to expand...
Click to collapse
I think you flashed the recovery image wrong lol. How are you rooting?
It wasn't flashed wrong because the version number changed from 2.1 to 2.3. When I originally rooted, it was during launch time. I'm using unrevoked now and everything is going smooth. I'm nandroiding back to CM7.
jblazea50 said:
I nandroid to a sense rom and updated prl. Nandroid back to CM7 and then flashed Tiamat's latest kernel and Viperboy's aosp battery mod. Rom went into boot loop. I took out battery and went to recovery (using Amon-RA). However, in recovery, nothing shows up. I get a blank screen with just the build number of the recovery at the bottom of the screen.
Now my phone is useless and I need it as I am in clinical rotations in Akron and away from home. This is my only source for communication.
EDIT: I know this is the general section, but no one visits the Q/A section and I need immediate help.
Click to expand...
Click to collapse
Go to www.shipped-roms.com and go to the SUPERSONIC section....choose an RUU to download....I recommend the newest one, unless you have a special reason for something different.....
run the RUU on your PC, (meaning not in your boot loader recovery, or from your SD card.)
If you have a mac...it will take extra steps....but is doable.
You should be able to flash with an RUU and get back to normal...afterwards, head over to www.unrevoked.com and re-root your phone...
jblazea50 said:
It wasn't flashed wrong because the version number changed from 2.1 to 2.3. When I originally rooted, it was during launch time. I'm using unrevoked now and everything is going smooth. I'm nandroiding back to CM7.
Click to expand...
Click to collapse
okay unrevoked is the best way to do it.
i've seen issues with CM7 losing root... I think it has more to do with ROM Manager and flashing the recovery image wrong. I've actually had it happen. I am working on an app to flash recoveries/roms, and it was working fine, but then i flashed clockwork recovery from rom manager and it turned security back on, disabled usb, and disabled sd... lol.
Thanks for all your help. I appreciate it. I am still not sure what caused the problem, but I went to stock, unrooted and now I'm back rooted and nandroid back to CM7. All is working fine at the moment.
derekwilkinson said:
okay unrevoked is the best way to do it.
i've seen issues with CM7 losing root... I think it has more to do with ROM Manager and flashing the recovery image wrong. I've actually had it happen. I am working on an app to flash recoveries/roms, and it was working fine, but then i flashed clockwork recovery from rom manager and it turned security back on, disabled usb, and disabled sd... lol.
Click to expand...
Click to collapse
Yup, unrevoked is super easy to do. My second time using it (1st time I did my dad's Evo after I unrooted to take it to Sprint store).
jblazea50 said:
Thanks for all your help. I appreciate it. I am still not sure what caused the problem, but I went to stock, unrooted and now I'm back rooted and nandroid back to CM7. All is working fine at the moment.
Click to expand...
Click to collapse
Great to hear
have fun!
I've lost recovery twice on this phone. Not a big deal to just reflash it. Glad you got it working
Related
I flashed the following: EVO_Radio_2.15.00.11.19_WiMAX_27167_R01_PRI_NV_1.90_003.zip
http://www.mediafire.com/?6jb1pee933ubsex
Pulled battery, wiped everything. Still stuck. Pulled battery, nandroid into backup, still stuck.
Any ideas?
your the third person tonight reporting that problem
to the sprint store for you!
NewZJ said:
your the third person tonight reporting that problem
to the sprint store for you!
Click to expand...
Click to collapse
Recovery work perfectly fine, let me try flashing some other rom.
Also, because this might be a bad radio flash, can reflashing radio hurt?
jerryparid said:
Recovery work perfectly fine, let me try flashing some other rom.
Also, because this might be a bad radio flash, can reflashing radio hurt?
Click to expand...
Click to collapse
ahh, missed that part, you could try downgrading or reinstalling
jerryparid said:
I flashed the following: EVO_Radio_2.15.00.11.19_WiMAX_27167_R01_PRI_NV_1.90_003.zip
http://www.mediafire.com/?6jb1pee933ubsex
Pulled battery, wiped everything. Still stuck. Pulled battery, nandroid into backup, still stuck.
Any ideas?
Click to expand...
Click to collapse
Could you give more information so I could be of help. Like what Rom, kernel, recovery anything specific...
Sent from my PC36100 using XDA App
I recommend you flash the previous version and then do a full wipe....next, flash a rom...then when that boots you can go back into recovery again and restore a nandroid if you would like....
Sent from my PC36100 using XDA App
Using Clockwork 2.5.1 (?, flashing right now) so I can't check.
Was on MYN RLS4. Flashed the bundled radio zip linked above, now in this situation. Currently, I'm flashing to RLS5 after a ADB push of the zip file. Edit: Was on BS#6 Kernel
If this doesn't work, I'll flash a deodexed stock 3.70.
Any more recommendations?
edit: Looks like I got past the HTC Evo 4G screen, just waiting for the MYN boot animation now.
edit2: I booted up, thanks for the help. At least I can rest knowing that my radio flash wasn't borked.
jerryparid said:
Using Clockwork 2.5.1 (?, flashing right now) so I can't check.
Was on MYN RLS4. Flashed the bundled radio zip linked above, now in this situation. Currently, I'm flashing to RLS5 after a ADB push of the zip file. Edit: Was on BS#6 Kernel
If this doesn't work, I'll flash a deodexed stock 3.70.
Any more recommendations?
edit: Looks like I got past the HTC Evo 4G screen, just waiting for the MYN boot animation now.
Click to expand...
Click to collapse
What happened after you flash the radio? Be specific..
Sent from my PC36100 using XDA App
Ive had the same problem today on two different evos, with two different recoveries! Both times I just booted into recovery and ran a full nandroid backup, then restarted and it stuck in white screen.
First was with amon_ra recovery. I pulled the battery after it stuck on white screen and it rebooted fine.
Second time was with clockwork. I just now pulled the battery and rebooted..... and it looks to be sticking again.
Both are running Fresh Rom. v3.5.01 I think.
Do you have the SDK installed and a usb cable? Hook up the evo, then do: "adb logcat", power on, and post the output. Note: it sounds like it is looping so watch carefully and when you see it looping hit "crtl+c" to stop logcat.
Do this! download this to you sd card http://www.megaupload.com/?d=PXIYUNSY than boot into bottloader, let the phone search for the file update and this should get you up and running. The problem doing what you did is that that works when a different kernel not htc kernel.
good lookin out
evolishesh said:
Do this! download this to you sd card http://www.megaupload.com/?d=PXIYUNSY than boot into bottloader, let the phone search for the file update and this should get you up and running. The problem doing what you did is that that works when a different kernel not htc kernel.
Click to expand...
Click to collapse
What's the purpose of doing this? Just like a RUU, right?
yes! But this should give you all that you are looking for, is much easier.trust me!
You will not Loose Root.
You lucky son of a gun, my old evo wouldn't even not into recovery. Just bootloader. After stressing out for hours trying to fix it I finally got a replacement
The same thing happened to me and your link worked like a charm. I was just wondering if after I did this would I still be able to try and flash a different rom? or am I stuck with this one? I am just wondering....as you can see Im pretty new to the rooting game.
Basically, if you update your radios, you have to also update your rom to 3.70 build otherwise the phone won't get pass the bootanimation screen. Normally, you would update the rom then update the radios. Also, to nandroid or flash back to 3.30 build, you have to downgrade the radios back to the version used for 3.30. I was stuck on bootloop with new radios if I flashed any rom below 3.70, but downgrading the radios to previous version allowed for 3.30 nandroid restores.
Ok thank you a bunch for the info!! you were a life saver lol
Same Questions
Ok so I did what you said above and loaded that file onto sd card and went into bootloader if worked and i managed to get into recovery and flashed fresh and got the phone booted all way but I want Warm two point two so i flashed that version 4 and it wont go past the white HTC screen what can I do
I just installed cyanogen 6.1.1 for my first time on my phone everything went correctly and then when it went to boot up its stuck at the boot screen. What do I do???
Someone plzzz help idk what to do???
Sinistah_ said:
I just installed cyanogen 6.1.1 for my first time on my phone everything went correctly and then when it went to boot up its stuck at the boot screen. What do I do???
Click to expand...
Click to collapse
Sinistah_ said:
So I just installed cyanogen 6.1.1. And its stuck at the boot up screen... what do I do????
Click to expand...
Click to collapse
Please do not start new threads when people are trying to help you. Wait patiently for an answer before starting a new one. You have started 4 threads already about rooting your phone and the problems you have. Invest some time in reading, learning and understanding the wikis. Thank you.
Sorry. I'm just paniking for the fact my phone is stuck on the boot screen and I'm jusst trying to get help asap. And actually the other thread was about if my phone was rooted so this thread is on another topic.
Are you still able to boot into recovery? And if so, what is displayed in your screen?
So I took the battery out, put it back in.. held power and the volume button it took me to where it says s-off n did a system recover. It worked!!! Haha... now I wanna try again but can u tell me what I did wrong??? I downloaded the cyanogen 6.1.1 and just started it up with the google stuff. It rebooted did its thing n stayed at the boot screen... am I supposed to clear something?? I read somethin like that when I was on google with my gfs phone. (I'm out somewhere... made me panik more since I don't have access to a computer atm)
Sent from my T-Mobile G2 using XDA App
Which version of ClockworkMod are you using?
Since you trie to flash a CM6.1. rom (which is froyo, android 2.2 based) you must use a ClockworkMod 2.5.x or below (or compatible).
And did you install Engineering HBoot? Sorry for asking, but it's unclear to me what you exactly have been doing already.
I did the visionary/gfree root last night without the hboot. And I tried the cyanogen 6.1.1 which was suggested by another user on here in one of my threads.
Sent from my T-Mobile G2 using XDA App
Btw my clockworkmod says 3.0.0.5
Whatever version that was on the market is the one I downloaded.
Sent from my T-Mobile G2 using XDA App
Apart from the fact that it seems to me that you skipped a step (hboot), which you have to perform , you are also trying to flash a 2.2 rom with the wrong recovery. Try with the 2.5 version in the thread http://forum.xda-developers.com/showthread.php?t=898151
HLeenders said:
Apart from the fact that it seems to me that you skipped a step (hboot), which you have to perform , you are also trying to flash a 2.2 rom with the wrong recovery. Try with the 2.5 version in the thread http://forum.xda-developers.com/showthread.php?t=898151
Click to expand...
Click to collapse
First of all, flashing the engineering HBOOT is not required unless you want to use fastboot on your computer. Also, if you used ROM Manager to flash ClockworkMod Recovery, that version is supposed to support both 2.2 and 2.3 ROMs. It was only the beta version of the recovery that was on this forum that only supported 2.3 and not 2.2---unfortunately, it was also labeled 3.0.0.5 and caused lots of confusion).
As far as why you are stuck at the boot screen, did you wipe data/cache when you flashed the ROM? Whenever you switch to a completely different ROM (as opposed to simply upgrading one), it's a good practice to. Also, the first time you start a new ROM, it'll take longer to boot up since the phone will be rebuilding its dalvik-cache (on CM6.1, it's be at a CM animation).
Ahh yeahhh okay good. So u cleared it all up for me n now my phone is running great
Sent from my HTC Vision using XDA App
I am having some issues. Don't know what is the problem. I nandroid to a sense rom and changed prl. Switched back to CM7 nightly 64 nandroid. Flashed tiamat's latest aosp kernel and did the viperboy's battery mod. Afterwards, my phone was stuck in boot loop. I went into recovery and there's nothing there. In the bottom of the screen, it says Build: RA-supersonic-v2.3, but the options aren't visible at all. And now, there's no way for me to boot the phone.
Any help would be greatly appreciated.
Can you not reflash amon RA via the bootloader?
posting & replying via the XDA Premium app.
jblazea50 said:
I am having some issues. Don't know what is the problem. I nandroid to a sense rom and changed prl. Switched back to CM7 nightly 64 nandroid. Flashed tiamat's latest aosp kernel and did the viperboy's battery mod. Afterwards, my phone was stuck in boot loop. I went into recovery and there's nothing there. In the bottom of the screen, it says Build: RA-supersonic-v2.3, but the options aren't visible at all. And now, there's no way for me to boot the phone.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Try pulling the battery, and reflashing your recovery, using a PC36IMG.
Sent from my PC36100 using XDA App
I was able to flash to Amon RA 2.3 (I was originally on 2.1). However, that didn't fix the issue. Now, I just did a PC36IMG.zip for a stock unrooted. Hopefully this works and I can get back to root.
jblazea50 said:
I was able to flash to Amon RA 2.3 (I was originally on 2.1). However, that didn't fix the issue. Now, I just did a PC36IMG.zip for a stock unrooted. Hopefully this works and I can get back to root.
Click to expand...
Click to collapse
It sounds like the recovery isn't being flashed correctly... are you sure that it is being flashed properly?
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.
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.