Hi there, long time reader, first post here
I've been running Myn's RLS4 with Clockwork 2.6 for a while, and have had no problems installing (flashing) zip files. Recently, I upgraded to RLS5 (still with Clockwork 2.6) and everything was still good to go (in reference to the Gingerbread keyboard, and Dark Coconut font zips in particular).
Well, I updated CWMod to 3.0 yesterday (after basically starting over with the phone... long story) and for some reason, the GB keyboard and Coconut fonts give an 'installation aborted' error now. The only thing that has changed was CWMod, but it just isn't making any sense. Before the abort, the recovery says something about the scripting being deprecated, and switching to Edify scripting (which it showed in the past when the flashing would work), but for some reason, with CW 3.0, it aborts the installation.
I've tried toggling script asserts and signature validation, to no avail. Is there something really simple I am missing, or I am going to have to find another zip to accommodate CW 3?
Thanks in advance for any insight!
I've been having that problem too, there are still a few things I can't flash, but it's the cw mod you're using. I haven't found the right one yet, but I've been flashing them from ROM manager... if anything goes through i'll let you know
vwgtiturbo said:
Hi there, long time reader, first post here
I've been running Myn's RLS4 with Clockwork 2.6 for a while, and have had no problems installing (flashing) zip files. Recently, I upgraded to RLS5 (still with Clockwork 2.6) and everything was still good to go (in reference to the Gingerbread keyboard, and Dark Coconut font zips in particular).
Well, I updated CWMod to 3.0 yesterday (after basically starting over with the phone... long story) and for some reason, the GB keyboard and Coconut fonts give an 'installation aborted' error now. The only thing that has changed was CWMod, but it just isn't making any sense. Before the abort, the recovery says something about the scripting being deprecated, and switching to Edify scripting (which it showed in the past when the flashing would work), but for some reason, with CW 3.0, it aborts the installation.
I've tried toggling script asserts and signature validation, to no avail. Is there something really simple I am missing, or I am going to have to find another zip to accommodate CW 3?
Thanks in advance for any insight!
Click to expand...
Click to collapse
Go back to CW 2.6. Everything will be back to normal. There were changes with the 3.0 update to CW. Anyway 2.6 works and this is the answer to your problem. Also the 2.6 version backs up Wimax.
I reverted back to 2.5.x from within ROM Manager, and all seems well. I think my nandroids were done with 2.6 (I remember seeing the system back up WIMAX during the process), so I should probably find a way to upgrade it 2.5.x to 2.6, right? I assume, if I did in fact have 2.6 before the update to 3.0, that my nandroid backups are worthless??
I switched to Amon Ra and haven't regretted it
ghost1227 said:
I switched to Amon Ra and haven't regretted it
Click to expand...
Click to collapse
I suppose now is as good of a time as any... I was avoiding it, because it's different (and CWM is pretty easy with ROM Manager) but I've had issues in the past with corrupt backups every now and then, so maybe this is the time to move. I don't think I've ever heard of issues with Amon Ra...
Well, I flashed Amon from ROM Manager, and upon reboot... well, it never rebooted. The screen just stayed black. It was completely dead until pulling the battery (which sucks, pulling the phone from this Ballistic case) but after reinstalling the battery, all is well. I just wish there was some sort of progress indicator during the backup (besides a seemingly endless line of dots).
Related
First off, thanks for all the help so far, this site is the best!
I just rooted my Evo using the unrevoked3. Had a little bit of trouble, nothing major, and overall it was a success. I also installed ROM Manager and Titanium Backup, based on suggestions found here.
The problem is, I'm not quite getting how to flash the roms... I downloaded one through ROM manager, and it seemed to work, but I didn't notice a single thing different. I tried to install CyanogenMod, and it downloaded, but it would always fail during the install.
I tried downloading on my computer, then moving the .zip file to my sdcard. Then I select "install rom from sdcard" and everything seems to go ok, I end up having to go into recovery and "rollback" my phone to the stock rom, because twice now I've almost bricked my phone.
Really, what I'm wanting is a setup like that "Kuma Style" one (without the animal), and a different bootscreen. I have spent a lot of time searching around, and it seems simple enough, I just seem to be missing some integral part of the proccess.....
Any help is appreciated!
Mark_Hardware said:
First off, thanks for all the help so far, this site is the best!
I just rooted my Evo using the unrevoked3. Had a little bit of trouble, nothing major, and overall it was a success. I also installed ROM Manager and Titanium Backup, based on suggestions found here.
The problem is, I'm not quite getting how to flash the roms... I downloaded one through ROM manager, and it seemed to work, but I didn't notice a single thing different. I tried to install CyanogenMod, and it downloaded, but it would always fail during the install.
I tried downloading on my computer, then moving the .zip file to my sdcard. Then I select "install rom from sdcard" and everything seems to go ok, I end up having to go into recovery and "rollback" my phone to the stock rom, because twice now I've almost bricked my phone.
Really, what I'm wanting is a setup like that "Kuma Style" one (without the animal), and a different bootscreen. I have spent a lot of time searching around, and it seems simple enough, I just seem to be missing some integral part of the proccess.....
Any help is appreciated!
Click to expand...
Click to collapse
I am not familiar with Unrevoked, but just running unrevoked doesn't completely root your phone. You need to do the second parts of rooting which unlocks nand.
Ah, so there is more to do. Maybe that's the problem then.... *off in search of how to unlock nand
Mark_Hardware said:
Ah, so there is more to do. Maybe that's the problem then.... *off in search of how to unlock nand
Click to expand...
Click to collapse
Unlocking nand just unlocks something so that you can save full image backups. That wouldn't lead to your phone not installing a ROM right, it's just something you'll want just in case things go wrong. So still finish the root and get nand. But that's not what you're missing here.
Possible error: Did you wipe settings &factory reset and wipe cache in ClockworkMod before flashing the ROM? I think that could lead to some problems.
Try flashing the alternative Amon Ra recovery through rom manager (will state that rom manager won't be fully functional unless clockworkmod is installed) and loading the roms onto the sd card then reboot into recovery. Amon Ra seems to work better imo than clockworkmod. When you're talking about something like "kuma style," those are themes that are usually flashable in recovery also. The boot animation could alse be flashable in recovery but if not, there are instructions on how to adb push custom ones onto your phone.
rugedraw said:
I am not familiar with Unrevoked, but just running unrevoked doesn't completely root your phone. You need to do the second parts of rooting which unlocks nand.
Click to expand...
Click to collapse
just fyi, the latest unrevoked (3.21) unlocks nand so u dont need to do it.
"unrevoked3 will permanently unlock NAND write protection by default on the following phones:
*
Sprint EVO 4G"
i'd link the wiki but i cant cuz i'm a new user lol
Gah! So I downloaded the enamored theme, moved it to the sd card, then went to ROM Manager and selected "Reboot into Recovery"and selected the enamored.zip. It said the install was a success, but when I rebooted, the phone stuck on the bootanimation. I tried restarting a couple times, but it always gets stuck in the same place.
I booted into recovery (if thats waht you call the hold the volume button down while pushing the power button trick), and selected recover, then nandroid, then a time under yesterdays date. Phone recovered fine.
WtH am I doing wrong? I realize I am way out of my league, but I'm not completely retarded. Again, GAH!
Are u wiping data and cache when flashing a ROM? I have been stuck at the CM6 boot animation when coming from a different Rom and not wiping.
Sent from my PC36100 using XDA App
Mark_Hardware said:
Gah! So I downloaded the enamored theme, moved it to the sd card, then went to ROM Manager and selected "Reboot into Recovery"and selected the enamored.zip. It said the install was a success, but when I rebooted, the phone stuck on the bootanimation. I tried restarting a couple times, but it always gets stuck in the same place.
I booted into recovery (if thats waht you call the hold the volume button down while pushing the power button trick), and selected recover, then nandroid, then a time under yesterdays date. Phone recovered fine.
WtH am I doing wrong? I realize I am way out of my league, but I'm not completely retarded. Again, GAH!
Click to expand...
Click to collapse
When you flash a theme, it could take up to 2-5 minutes to finish. This occurs during the boot animation. I flash themes all the time and I notice it's usually around 2-3 minutes wait. Maybe faster for others but that's just been my experience. If it's over 5 minutes than there's probably something wrong with your zip file or maybe clockworkmod recovery doesn't flash it properly. Also, it could be an issue with the kernel you're using...I noticed on kingklick cfs #10, I was stuck on boot animation for about 7 minutes and so I reverted back to the stock kernel and the theme was applied within 3 minutes.
ok, apparently I've been missing that step...
where do I do that again?
mizzos4 said:
When you flash a theme, it could take up to 2-5 minutes to finish. This occurs during the boot animation. I flash themes all the time and I notice it's usually around 2-3 minutes wait. Maybe faster for others but that's just been my experience. If it's over 5 minutes than there's probably something wrong with your zip file or maybe clockworkmod recovery doesn't flash it properly.
Click to expand...
Click to collapse
I waited a good long time. Am I at least headed in the right direction? Sorry to sound whiny, it's just that there's a few little things I want to do, and I'm intimidated as hell by actually doing any command line, so I'm hoping to avoid that- aka riding someone else's coattails
First, which rom are you using and is it stock or custom kernel? Are you using clockworkmod recovery? Try flashing the alternative amon ra recovery in rom manager then boot into recovery and apply your selected theme.
if you are using a stock rom it must say stock 2.2 deodexed
if it is not a deodexed rom.. of any kind.. then themes will say they flashed but they will either brick your phone or not work at all.
and stop using clockwork.... just use amon ra
Sent from my PC36100 using XDA App
I could be way off here, but I've seen some people who rooted using unrevoked, and run into trouble flashing things (or maybe I'm thinking of trouble with terminal commands) and it turned out they couldn't find flash_image anywhere in there SD card, Which should be installed (someone please correct me if I'm wrong).
I saw a lot of reports of this in chainsDDs superuser thread, if I remember correctly. They had to install flash_image.img (which is a file available on toasts part 2 root tutorial)
I obviously could be wrong about this, I've never used unrevoked, I rooted via toast, and his method included everything.
@ V_lestat
Thanks for the heads up about themes having the ability to brick your phone if not deodexed, I never knew that. I flash roms and kernels a lotbut never messed with themes much.
At OP, have a look at virus Rom thread. It's a great ROM, and he has built some different themes to go with it. Beautiful stuff, great ROM, great thread.
Good luck
Sent from my PC36100 using XDA App
See, some people say use clockwork, some people say Amon.
I looked around a lot beforehand, and people kept saying to use unrevoked, so I did. Now people say I should have used Toast?
Thanks for everybodies help so far, I am reading everything and taking it all in.
I Don't Mean to add any Confusion to your situation. I am new to this also.. I went with unrevoked also and when I booted into recovery with clockwork mod. I did a nand back up first to make sure if anything went wrong I could just boot back into recovery and load my backup. Then I wiped my Data & Davlick Cache all of the caches. Then I installed my Rom and it worked like a charm. I will add it did take about 5 to 7 mins to boot only on the first time though. I hope that helps some as to the process and what to do first don't give up XDA rocks with the smartest mind on the planet.
Mark_Hardware said:
ok, apparently I've been missing that step...
where do I do that again?
Click to expand...
Click to collapse
If you are using ROM Manager to "install zip from card" it presents you with a dialog with two unchecked check boxes. One of them is "wipe data + cache". make sure you check it before hitting ok on that dialog.
If you are manually booting into recovery then in the recovery choices you will see one that says wipe data and one thats says wipe davlik cache. first do a nandroid back up then wipe those data and davlik then install the rom. By the way are you just installing a theme or a full rom that might be the issue i am just wondering maybe a senior member can help on wether you can install a theme over a rooted stock theme or not?
Success!
I went into ROM Manager, backed up current ROM, went into recovery manually, wiped the cache, then installed from zip, and it worked! I tried a cool theme I found, and I like it, but it seemed old. I just installed fresh, and the enamored theme, and all is working great!
A couple more questions,
1) how do I get my contacts back?
2) How do I get my apps back onto my phone? I have them backed up on appbrain, but I haven't been able to find how to get them back to the phone.
So far, I've tried a couple of ROM's (and/or themes) and I've ended up flashing back to my own "safe" one, until I figure these two things out.
A tremendous thanks to everyones help! I seriously couldn't have done it without you guys
Edit; Oh yeah, one other thing. How do I delete the other nand backups? There's like 5, and I need to free up some memory. I tried going in and selecting one to see if it gave me the option to delete, but I didn't see anywhere that it did.... Got it. Search feature to the rescue
Ok, so I did unrevoked and have an unrooted phone. Started to get bored with the stock 2.2 and wanted better battery life.
My Dinc has an SLCD screen. So, when I go into the standard clockwork recovery, it goes to a black screen with white bars on the side. I had to do a custom flash recovery for my phone through unrevoked/flash. I then did a nand backup.
Tonight, I downloaded MIUI and attempted to install through the recovery flash. I ended up getting errors. So, I then thought that I needed to go through the ROM Manager app.... when I tried to flash the ROM, it automatically switched my recovery back to the Clockworks recovery..... then tried to go into the recovery portion of the ROM flash. Needless to say, I had to do a battery pull. Now when I try to do a normal boot, the phone freezes at the white screen that reads "HTC Incredible". If I boot into recovery... I can get to the hboot screen with the three droids at the bottom, but a script comes up on the screen and I think that it says something about no image... from there I can navigate around the recovery menue, but nothing works for me getting past this. If I go to recovery, it just keeps going to the black screen with the two white bars.
Is there anything that I can do. I am wondering if it is trying to flash the ROM everytime it comes on.... but this recovery method is not working on my phone.
Any help would be greatly appreaciated!
I believe you need a special clockwork recovery for SCLD screens. Not exactly sure where to find it on here, but it should be hanging around somewhere. I hope I helped ya out a bit, good luck.
Sent from my Droid Incredible running SkyRaider 3.3.2 with King Kernel BFS #5.
OK, so I was working a 24 hour shift yesterday when I posted this... unable to download any zip or exe file (damn firewalls)... This morning I was able to remove the miui zip from the root of the sd card via card reader. I then copied the PPB31IMG.zip to the root of my sd card. Then booted into recovery. I asked if I wanted to flash this file, I said yes and then it gave me the correct recovery menue. from there I was able to choose the recovery image that I had created yesterday. It seemed as though it was going to work, booted up to a stock rom that required manual setup (like on a new phone). Then I started to get FC's all over the place. I was able to find on my sd card two other nandroids that were saved in a different place than the only one that recovery allowed me to choose from. I moved the newly found recovery folders to the same location as the first and now I had those recovery options listed. I chose one from last week and thankfully my phone is restored and working.
I am not sure if this information will help anyone with an SLCD Dinc. There seems to be a huge difference in how these phones react to roms and tweaks. I am very hesitant to attempt any other ROMs at this time. On my eris, I flashed about 30 different ROMs and about 5 differnet radios. I am not new to this, but this SLCD Dinc has been a headache.
Any Aosp rom on an Slcd takes a different kernel. Get yourself the koush test#2 kernel and just keep it on your sd card. Flash it everytime you do a AOSP rom.
Sense based roms all seem to be ok as the kernel was built with Slcd in mind.
Well I'm glad you got it back up and running. I've heard about them not working well with some roms, I didn't know it was with all asop roms.
Sent from my Droid Incredible running SkyRaider 3.3.2 with King Kernel BFS #5.
doug piston said:
Any Aosp rom on an Slcd takes a different kernel. Get yourself the koush test#2 kernel and just keep it on your sd card. Flash it everytime you do a AOSP rom.
Sense based roms all seem to be ok as the kernel was built with Slcd in mind.
Click to expand...
Click to collapse
Thanks for the info on the AOSP roms. I did not know either. I wonder if there is a way to make the AOSP roms to support it by providing the new kernal in the flash or at least making a note on the AOSP ROM forum page that states the issues with SLCD Dinc's and what needs to be done to avoid problems. I would venture to say that anyone new to this stuff and was feeling brave would not be able to figure out how to restore there phone when it was acting the way mine was. Just my 2 cents.
Thanks again for the info.
Hey people, I've search far and wide, both on-forum and off-forum, and I cannot find a solution (it's quarter to 10pm EST and I've been searching since about noon EST... sigh)...
ISSUE:
- Had AuraxTSense running fine, but wanted to cook a custom using www.cookmyrom.se (recommended off of XDA-forums)
- Tried numerous times, using either AuraxT or Leedroid, cooked, downloaded and installed only to be reverted back to RelfexTSence, which I had BEFORE AuraxTSence. Odd, since Aurax was my most recent ROM, NOT Reflex... WEIRD, I KNOW!
- Ever since that, I cannot install any ROM. Install will fail, citing "Verification Signature Failed", "Installation Aborted".
THINGS I'VE TRIED:
-disabling verification (it's disabled by default, however, I enable it, then disable it just to make sure)
- Re-cooking, re-downloading, re-installing numerous, I stress, NUMEROUS times
- clearing all sorts of caches before AND after installs
- Wiping, re-formatting and re-partitioning SD Card (only thing I backed up was pictures and a kernel, but I didn't even restore because I couldn't get a ROM to work (re: issue above)
- tried installing via Rom Manager as opposed to via clockwork = still didn't work
SPECS/INFO:
- HBoot 0.83.xxx something
- Clockwork Recovery 0.2.5.7
- unbranded, rooted HTC Desire
- Last-running kernel was Coutts .975mV
- Last correctly running ROM was AuraxTSense (with new sense, apps2sd+ etc.)
- Second last correctly running ROM was ReflexTSense (yadda yadda)
- Third last correcetly running ROM was Leedroid (Can't remember the version, maybe d?)
But it keeps reverting to a half, slow, cheap install of ReflexTSense (no disrespect to the author of ReflexTSense, the ROM was great, it's my phone that makes it a crap experience)...
HELP! lol
Thanks a ton in advance!
Is the file verification enabled? If so disable it. If that doesn't work, make a Goldcard.
Thanks for the reply mate. I've read a bit about this "goldcard" business, but I can't seem to understand it.. have a link or anything, maybe a guide? I can't seem to pull anything useful up (sigh, after 10 hours or searching XDA + Google)...
Also, yes, verification was off :/
Gold card isn't needed to flash a custom ROM so don't worry about that. Chances are its the signature verification being turned on. Turn it off and it should work
It isn't but if disabling the signature verification in recovery isn't helping then making a Goldcard is the fastest way to go about it instead of farting around with a load of s**t.
Gold card only lets you flash a stock RUU from a different build then your original one. It does nothing for flashing custom ROMs
Have you tried switching from Clockwork Recovery 0.2.5.7 to AmonRa Recovery minimum 2.0.0? I don't know about Clocwork recovery options, as I used it only briefly, but the newer versions of amonra allow you to switch verification OFF. Give it a shot.
P.S. I use version 2.0.0 - the option is in the meniu -> other -> Toggle Signature Verify
Later edit: BTW, your version of Clockwork recovery is quite old - I've seen some 3.0 version talk here http://forum.xda-developers.com/showthread.php?t=897026
Thank you all for the replies. Clockwork DOES allow you to turn signature verification off, however as Stefen mentioned, it might be outdated. I'll first try to update clockwork since I'm familiar with it. If not, I'll try switching to AmonRa Recovery. Thank you all for the suggestions so far, I'll post back if solved!
Alright, so I cannot upgrade/downgrade my clockwork recovery, it just doesn't work. I've followed all steps (I AM technologically literate) to no avail...
What to do.......... ?
You need to either be S-OFF or re-run unrEVOked to update it. What have you tried to do?
EddyOS said:
You need to either be S-OFF or re-run unrEVOked to update it. What have you tried to do?
Click to expand...
Click to collapse
I have tried:
- disabling verification signature, then flashing
- wiping, literally, everything there is to wipe, then flashing
- updating recovery through HBoot (unsuccessful)
- updating recovery through ROM Manager (error on every version except current version I have)
- tried numerous ROMs that HAVE worked every time until recently (both verified through Desire Development threads, i.e. Leedroid, AuraxTSense etc., and custom cooked ROMs off of www.cookmyrom.se)
Specs:
- Desire AMOLED
- HBoot-0.83.0001
- Radio-4.08.00.09
- Current ROM: AuraxTSense (New Sense HD) -> It forces me on it
- Kernal: 2.26.32.26 [email protected] #34
- Recovery: Clockword Recovery 2.5.0.7
If I'm missing anything, ask me and I'll give you the info.
I mean you can ONLY update CWM by running unrEVOked again and pointing it to a newer version or do it once you've S-OFF - no other way will work
Oh ok, I understand now.. however, is updating my CWM the way to fix this issue?
I've read that CWM 3.0.0.0 and up only read Edify, meanwhile lots of ROMs are still zipped using the older-based script... So far, everyone reports 2.5.7.x to be working. Unfortunately, I'm stuck in a "no-flash-anything" zone :/
No idea, I use AmonRA
I'm going to try IntertCoin ROM, it's said to be zipped using Edify, which CWM 2.5.7.0 apparently supports... this way I'll know if it's CWM screwing me or not...
EDIT: Can't flash this one either. Still says verification signature failed even though I've disabled it, and the author of the ROM says it's signed.... like wtf man? All I've done is switch a few ROMs over a couple of months, nothing crazy, how could this happen???
BUMP..... I need help man... it's already rooted but I can't do ANYTHING! Can't flash, nothing...........
Go back to 100% stock, root again using AmonRA and flash another ROM
EddyOS said:
Go back to 100% stock, root again using AmonRA and flash another ROM
Click to expand...
Click to collapse
I've been searching on how to unroot.. can't find anything.. I found ONE tutorial on XDA and it looks complicated as hell.. I have OSX or windows 7... I originally rooted on Windows 7.
I've unrooted my phone, and have succesfully RE-rooted my phone only to end up with CWM 2.5.0.7 again, and sure enough, I cannot install ANY ROM again.
Since no one cares to help, I guess I'll just keep trying God knows what, and maybe I'll post results... thanks anyway...
How did you unroot? Did you run the original RUU for your phone?
Also, have you tried AMONRA recovery? You need to specify amonra when running unrevoked to flash it rather than clockworkmod.
Sent from my HTC Desire using Tapatalk
Is anyone else still having these problems?
I can't seem to ever complete a function in CWM3. I've flashed it through RM wiping any previous recoveries; I've installed from hboot, even tried using several different flash cards, but still no luck.
CWM3 will stop responding completely and the only way out is to yank the battery.
Anybody have any ideas?
I know one answer is "Use 2.5.x.x," but is there anything else?
Thanks for your help!
I had a lot of issues with CWM3.0.0.5 until I took someones advice and checked the "Erase Recovery" option in setting. Since then I have been running great, no issues.
Yea, I've done that too....still same errors.
Thanks for the suggestion though! I appreciate the help.
I personally never had any issues with CWM 3. But since so many other people have had a lot of trouble with it, I decided to install the Amon RA recovery for our devices. My favorite capability of it is installing zips from /emmc.
As for CWM 3, I have to ask when you installed it via HBOOT did you make sure to check the MD5 sum? At this point CWM 3 gives you no added functionality...maybe it is best to stick with 2.5.0.5 or 2.5.1.2 until 3 works well. Seems like it has a multitude of bugs at this point.
The new CWM is giving people fits because koush tweaked it to 'force?' developers to use an updated/different coding method in/for their ROMs, in anticipation of gingerbread. He noted this change on his twitter and his site.
Tremendous respect for koush - but this, imho, is hurting the user community more than forcing devs to adapt new methodoligies.
I'm staying on 2.x.
my $0.02
I'm also getting issues with CWM3 and have tried every suggestion I have read (install via HBOOT, check md5, set "erase recovery," install stock recovery then install CWM3 over it) and none of them have worked. I can get into CWM3 and navigate for a few seconds but it eventually completely freezes and requires a battery pull. One trigger I noticed for my CWM3 problems is that touching the optical trackpad while in recovery will occasionally cause my screen to briefly spazz (artifacting and diagonal white lines) and then my phone will reboot. 2.5.1.2 works fine but I would still like to upgrade for future edify scripts.
I have an S-off, amoled Dinc.
Edit: And I have tried updating to CWM3 with 3 different microSD cards (2 2gb Samsungs and a 1gb Sandisk)
Sterlic,.sounds like the exact same problems I'm having. Glad to know its not just me.
I might give Amon a try, does it use the edify script too? I don't know anything about that recovery or even where to look to find info on it.
Thanks everyone for your help.
Sent from my Droid Ostentatious...
I had quite a few problems with 3.0.0.5 initially. Lot's of cursing and hair pulling. Since then I have done a complete wipe and reinstall of CM7 RC1 up to #5 and CMR 3.0.0.5. Fingers crossed...everything seems to be working at the moment...
But I don't think I will be able to nandroid back to any of my older sense ROMs anymore. I believe I read this somewhere. I can't remember if there are any other limitations...
Hello everyone.
I enjoyed the noob video and also look forward to being pasted no doubt.
I have a wildfire running 2.2 android which I understand means I am running the latest firmware, which I also understand is going to make it difficult for me to root easily.
Never the less not being one to be beaten I have tried with EVO3, which no matter what I tried would not work, constantly asking if my firmware was too new. I even wiped it but no luck.
So I struck upon revolutionary, which yes I understand is beta.
This is perhaps where my lack of understanding comes in. Would I be right in thinking that custom roms require a specificly rooted device?
The thing is I have apparently been successfull with revolutionary. I can boot into it and I was able to instaly cryongena rom which worked OK until I installed google apps where by it constantaly showed the spinning blue arrow, round and round, rebooting and rebooting.
Thing is all other roms I have tried, everyone, has failed, with either script being old 'error 6' etc etc.
I found I needed a different kind of rom, which a few were offering however these also failed with error 6 which apparent was something to do with not being pure unix or something.
Sorry I am not up on the language, but I think I have tried all the popular ones, puzzle etc and none will install.
When I start up with the volume button pressed it shows the screen then says something about failing to load image, but goes away to quick to read pc4diag.img or something.
Is it possible I have not loaded revolutionary correctly, and have I gained 'root'
Thanks for reading, and please feel free to tear me a new one.
- Yes, I am sure you have Revolutionary installed correctly. You got a bootloop while installing GApps, in which case I would recommend performing a full wipe in Clockworkmod and try to install again. (Install the CM ROM first, then the GAPps Zip. Also, I hope you are using a filename called gapps-gb-2011xxxx.zip)
- If you want to install other ROMs, Sense and Android 2.2.1 ROMs require Clockworkmod 2.x. Attempting to flash them in Clockworkmod 3.x/4.x will give you the "Scripting not supported" error. The workaround to this is to download this attachment:
http://forum.xda-developers.com/attachment.php?attachmentid=662193&d=1311319218
Flash this in your new Clockworkmod Version, which will give you temporary 2.5, then proceed as normal.
- When you boot into the HBoot Mode, it will automatically perform a search for the files PC49IMG.diag and .nbh. It's normal, and theres nothing to worry about. After the search is over, and, it has not found the files, you can navigate properly again.
Oh, and I think you are being too paranoid about the video and everyone here trying to tear you a new one.
Good Luck
Thanks very much for your answer.
Honestly I spent 2 hours on google last night trying to get my head around it.
To be honest all I want is a quick phone, and I am not getting that with stock software on my wildfire, I get very frustrated when trying to scroll but it reads it as me tapping an app icon, and there are loads of them I don't want in here, footsteps and tweets and the likes, I am simply not interested and neither am I allowed to remove them. The cynogenmod looked amazing, but I can see even more processor intensive than the stock software.
I will have a look at what you have suggested and thanks for your help!
In that case, I think you might want to stick with the Stock ROM, and, get an app like 'Root Uninstaller' or 'Titanium Backup' which allows you to uninstall (Or, to be more correct - 'freeze') any apps you wish - Including System Apps.
Not trying to advertise Cyanogenmod here, since I understand ROM preference is a personal thing, but, I would recommend giving it one more try, after a full wipe. Also, go with the latest nightlies rather than the Stables. I have been using it since it was released back in January, and, honestly, I am never going back to Stock / Sense based ROMs.
Don't get me wrong it looks awesome. But the boot up time was just shy of 4 minutes (although I now understand it may have been because of first boot) and two attempts at install failed.
I shall look at how to fully wipe, but to be honest, being very new to hacking my phone I am quite happy having the back up there to revert too.
Well I tried to install anything but nothing works so I shall revert to my original back up and see about these tools for removing unwanted apps.
Thanks for the help, but something is not right. All roms either get as far as the twinkly noise on the HTC screen then do it again and again, and cynogen gets to the rotating arrow, then eventually an android zips across the screen and back to the arrow
Well I don't think I have root on this device. I tried to install busybox and titanium and both tell me my phone is not rooted.
Sigh.
If you are on the Stock ROM, you will have to flash this additionally:
http://bit.ly/su2361ef
This will install Superuser, which is what will give you "root". If you are on Custom ROMs, flashing this additional file is not required, since, they include the Superuser Binary already,. So, flash that, and then try installing Busybox / Ti Backup. (make sure you get a "superuser" icon in your app drawer after flashing that zip)
EDIT:
- Are you on Clockworkmod 3.0.0.6 incidentally? That version has caused bootloops for many users when installing ROM's.
- First boot time is extremely long (Upto 7-8 mins), and its normal.
Hello thanks for the info.
I am not confident I know what mod I am on, I just went to the revolutionary website and downloaded the latest beta.
When you say it can take 7-8mins to load up would this include the boot loops though? Thats all I get on all of them
I shall install the super user bit see if that helps.
No, not including bootloops. BTW, I am referring to the Clockworkmod Version, not Revolutionary,
When you enter the Recovery to flash something, at the bottom, you will "Clockworkmod Version x.x.x.x". It is that version I was asking.
Sadly I am not getting anywhere here, every single rom just goes round in circles in one way or another.
The version say revolutionary CWM v4.0.1.4
I was unable to get the standard revoked installed as I am runnning the latest android firmware and it just kept failing.
Something I am getting rather used to!
I cannot see a clockwork mod number anywhere, although it must be there as I have clockwork folder on the SD card.
Sorry, I am being a muppet here.