Anyone out there have problems flashing back to Froyo ROM after using Evervolv gingerbread?
I can flash back to a Nandroid of Evervolv, but cant:
1. Fresh install Froyo Rom
2. Re-install Nandroid
This is of course all after wipe of everything.
Using Ra for wipe of dalvik, cache, battery, sd ext , factory reset.
ANY ADVICE.
when I try and flash any froyo rom or nandroid of a froyo rom I just get the white HTC evo 4g screen which stays (ive left it for an hour) until reset and flash back to evervolv.
So.......im stuck using ONLY evervolv and im kinda over the rom not working well yet. Its improving, but still too much not working consistently and reliably.
Does RA recovery need to be updated.......would that potentially fix the problem ??? or did something else cause the gingerbread only problem.
Sounds like you updated your radio and pri and are trying to flash to a rom still running the older HTC #17 kernel.
Download and flash one of the new roms based on the new ota 3.70 with the htc#15 kernel.
If it boots up there's the issue
sent from my evo.
Hi All,
I have a question about cmw's recovery and the rom manager. In the dev forum, theres cmw 3.1.0.1, which i've downloaded. However, rom manager keeps telling me the latest is 2.5.0.7. So im curious which one i should actually be using?
Reason I ask is because i've been getting a few odd problems flashing rcmix on my phone. Generally it will work properly (coming from a stock 2.2 rom), though from any other rom it wont. I know that if i flash something like insertcoin, reboot to recovery, wipe/reset, install rcmix it never works. Same goes for when i come from rcmix 1.5 to 1.6 (and 1.7). I assume its got something to do with the a2sd partition, but im not sure what or why cmw recovery is not wiping that jumping between versions of rcmix end with a total failure (stuck at boot logo forever). Quite often this happens with other roms too (like going from rcmix -> insertcoin or oxygen).
Mines a desire lcd, often running stock 2.2 at the moment (rooted, s-off'd) and the standard hboot.
Officially the Desire had the latest recovery version of 2.5.0.7 or what ever it is. 3.1.0.1 is a build built from the source unofficially. V3 has a new type of script and so might help with your issues.
Tbh I hate rom manager because it doesn't work well. Try manually flashing roms. It might help even more.
Swyped...
Same here. RomManager doesn't offer 3.x.x.x versions. You'll habe to flash it manually via Fastboot (for S-OFF) or with Unrevoked (for S-ON).
I actually dont use rom manager for flashing roms and the only reason i went to it was cause I couldnt find a consistent way of finding the lastest clockworkmod recovery image (theres alot of conflicting info out there).
Thanks for the info though, was handy to know. Interestingly, the version rom manager booted me into (boots off update.zip from the sdcard?) was older then the one i had.
Shihan said:
I actually dont use rom manager for flashing roms and the only reason i went to it was cause I couldnt find a consistent way of finding the lastest clockworkmod recovery image (theres alot of conflicting info out there).
Thanks for the info though, was handy to know. Interestingly, the version rom manager booted me into (boots off update.zip from the sdcard?) was older then the one i had.
Click to expand...
Click to collapse
I have always stuck with CWM 2.5.0.7 - it seems to be the latest version that nobody reports problems with. I don't think there's any good reason to update to the newer versions.
Hi guys I am having some issues flashing a rom to my buddies phone. Is there a different method to flash roms on phones that are rooted with revolutionary?
I ask because my phone was rooted a year or so ago with unrevoked. I have no problems flashing roms to it. But everytime I flash a rom to my buddies phone it is just bombarded with force closes left and right. I tried reformatting always clearing every cache etc?
Am I missing something? Should I be flashing different roms since it was already on OTA 2.3.3? Sorry for the noob questions but I figured once I got s-off that most roms would be compatible.
thanks
All roms will work with revolutionary what recovery are you using?
We are legion, for we are many.
On his phone I'm using the clockwork recovery. Same thing I have used on my phone. With newer rooted phones do I need to run a different recovery? Or flash the roms differently?
Like I said his was was already on android 2.3.3 and mikg, synergy and all other roms just force close like crazy. These are all installed through clockwork.
Any help would be great guys thanks
I use amon RA style supersonic recovery v3.11 some use amon RA, cwm and twrp both have issues wiping twro2.0 is known to brick phones, I'd recommend ARSSR v3.11 or Amon RA v2.3
We are legion, for we are many.
So I'm on froyo but trying to upgrade to gingerbread CleanGB Rom. I'm already rooted and I flashed clockwork mod from Rom manager. If i try to make a backup, or flash the rom, everything fails, soemthing about not mounting in clockwork mod. What's wrong? (Not experienced with Epic 4G). How can i get the recovery working normally?
Redo the one click and make your backup from a 3 finger salute into CWM. Sounds like ROM Manager is broken for you. Update from 3 finger into CWM and then you should be able to get ROM Manager working. There are things you have to do if you are going to MTD to get ROM Manager working. But first let's get you to Gingerbread.
You need cwm5. I would Odin to stock and retry.
Sent from my OG Epic running MIUI4 ICS powered by ShadowKernel
Maybe this is by design and I'm just missing something. I got a new e4gt and proceeded to root it using instructions found on epic4gtouchroot.com. Basically I used odin to flash a stock EL29 ROM and then install team Rogue's CWM.
All went well with this process so I proceeded to the next step, which was to download and install a custom ROM. I installed the VeNuM ICE 5.5 since I'm a comic book nerd as well as a computer geek.
This wasn't my first time rooting. I've been rooting my EVO for a year of so, and I've rooted my Wife's Nook Tablet too, so I was a bit shocked to see that the Team Rogue CWM recovery program went bye-bye after flashing the VeNuM ROM.
I downloaded ROM manager and tried to flash the latest CWM recovery program from there, but that dind't work. I haven't tried to download the touch recovery, but I was able to reinstall the Rogue CWM recovery program, which then hosed up my ROM. I actually thought I bricked my phone for a minute, but I was able to go back into Rogue Recovery and re-flash the VeNuM ROM.
All went well and I'm back into my phone, but now again when I reboot into recovery mode, I have "Android System Recovery <3e>" like an abridged version of CWM. I don't have near as many options and wonder what's going on.
I never lost my recovery mode before when flashing a ROM. Is there some sort of custom recovery included with this ROM, or am I doing something wrong?
hi. im pretty new at this also, but i think i know the answer to this. well. not really the answer, but i know how to get clockwork recovery back onto the venum rom you are using now. you need Odin3-v1.85 (just google it) and the clockwork recovery StockCWM-EL26.tar (google). Then you put your phone in odin mode, volume down and power from powered off state, run the program, check the PDA option and browse for the stockcwm file, plug in usb and hit start. That'll put the recovery back on your phone.
But as I've been reading, a lot of times, you cannot just download the rom onto the phone or sd card and flash new roms using the cwm recovery. something about the gingerbread and ics and different kernels. .... =D
Please read the "How not to brick your e4gt" or how ever it goes in general. You need to stay away from rom manager and any touch recoveries. To answer your question, rogue recovery went away because the Venum ICE rom has the stock recovery packed in because of all the custom recovery/bricking issues we've been having with ICS. So the Dev left out custom recovery included with his rom
Sent from my SPH-D710 using Tapatalk
I'm not sure what recovery Venum comes with but this might be by design since custom CWM recovery is not installed by design on most ICS roms.
First of all read through this thread: http://forum.xda-developers.com/showthread.php?t=1525495
You chose to flash ICS; if you had chosen Gingerbread this would not be an issue so please read on... ROM manager should NOT be used with ICS. Since you are new, the only CWM recovery you should be using is the stockcwm-el26 posted here: http://chris41g.devphone.org/index.php?dir=EpicTouch/Stock+Repack/EL26/
Lastly and most important:
Flashing ICS can be a very dangerous thing for your phone if done improperly. Even flashing back to Gingerbread from ICS can go wrong.
Please do not do any further flashing of ICS without reading and understanding the process of flashing ICS safely!
Also, please feel free to ask lots of questions until you are comfortable with the entire process. That is why we are here.
Edit: Sorry for the very strict tone throughout. You have a very nice WORKING phone and we see a lot of newbies flashing over to ICS without a full understanding of what can go horribly wrong. We also see users asking for help here daily because they have bricked their phone (many times with no hope for repair or recovery).
Maybe I'm just lucky?
Ok, so I read a little more (two straight days of XDA has left me a bit un-productive at work) and I see now the difference between the Samsung phone and the HTC phone I had before. Samsung does partitioning a bit different, or maybe it's just ICS, but either way as you explained in your post, the recovery has to be packed into the ROM. Makes sense now. I was thinking that the recovery was a different eeProm chip, therfore flashing a ROM shouldn't affect the recovery, now I know that's not the case.
After I read, a bit more, I actually did what it's been suggested not to do, and that's install ROM manager. From ROM manager I installed the custom recovery and have successfully booted to this several times without incident, and in fact have flashed both another ROM (VeNuM Anakonda), a Theme for this Rom, and the S Voice update 4 exe file. I don't seem to be having any trouble using Rom manager to boot into recovery mode.
Venum ICE was a bit much for me, way too many bells and whistles that I could potentially blow up my phone with which still could happen. Anyway, I like the Anakonda rom and will probably stick with it a while. I can't get s Voice to stabalize, but that seems to be the only problem I've got, so I'll live with that.
BBJon said:
Ok, so I read a little more (two straight days of XDA has left me a bit un-productive at work) and I see now the difference between the Samsung phone and the HTC phone I had before. Samsung does partitioning a bit different, or maybe it's just ICS, but either way as you explained in your post, the recovery has to be packed into the ROM. Makes sense now. I was thinking that the recovery was a different eeProm chip, therfore flashing a ROM shouldn't affect the recovery, now I know that's not the case.
After I read, a bit more, I actually did what it's been suggested not to do, and that's install ROM manager. From ROM manager I installed the custom recovery and have successfully booted to this several times without incident, and in fact have flashed both another ROM (VeNuM Anakonda), a Theme for this Rom, and the S Voice update 4 exe file. I don't seem to be having any trouble using Rom manager to boot into recovery mode.
Venum ICE was a bit much for me, way too many bells and whistles that I could potentially blow up my phone with which still could happen. Anyway, I like the Anakonda rom and will probably stick with it a while. I can't get s Voice to stabalize, but that seems to be the only problem I've got, so I'll live with that.
Click to expand...
Click to collapse
Coming in late to this thread but I would like to re-iterate what was said about ROM manager and pretty much everything tdunham said. Because you have been, so far lucky, does not mean that luck will continue. Best advice is to remove it and not use it. If you read through some more posts you will see that the bricking doesn't always happen on the first, second, third flash. It can all of a sudden appear. We've had VERY experienced developers brick their phones, so to think you won't just because you've been lucky is not wise.
But some of the comanailities are clear - using ICS recovery to wipe/restore and using ROM manager. Just thought I'd point that out.
If you're coming over from a different phone (HTC etc) check out Qbking77's videos. They are very informative too.
Good luck and have fun.
I'm glad that the op did some reading and had some extra help here. Our phones can be confusing but with extra reading it can be figured out. We try to list the kernel that's in the rom and these are all listed in the development section in some form or another with explanations of what they have, ie cwm or rogue recovery... In addition most of our roms list a change log that you can read that will tell what each version of the rom has in it in case you would rather use an older version. And we keep the older roms posted too... anyway happy flashing !
I've bricked my phone a few time messing around with different ICS roms and kernals. I go back and odin EL29 rooted...start all over from scratch. Try using new recovey kernals posted on ACS. I'm on FE22 with the ACS recovery and am having no issues with flashing zips and making backups as well restoring.
Sent from my SPH-D710 using xda premium
There are some repacked recoveries that Steady used to make for ICS before he disappeared. Those were never and still aren't safe for flashing ROMs though. It's safest to Odin/Mobile ODIN CWM EL26 tar whenever you need recovery and then flash whatever and then reflash an ICS kernel without recovery so that your phone boots
Sent from my SPH-D710 using XDA