Develop Bugs

[FIXED] Help!Cant flash any recovery images

Ever since I updated to the last OTA I have lost clockworks recovery image. Thus now I am unable to install the latest froyo rom.
I have tried to install the latest clockworks recovery image and Amon_Ra recovery through Rom Manager. Each time it states it is installed but everytime I try to boot up to the recovery image it gives me the following error:
E: Can't open /cache/recovery/command
and it just gives me the Android System Recover <2e>
Any help would be appreciated....

It sounds like you are not rooted.
If you accepted the OTA from Sprint using your system update on your phone, you are no longer rooted and will not have a custom recovery/root permissions. You will be unable to flash any custom recovery/ROMS/delete any sprint apps/Other Root only things until someone comes up with a way to root 2.2.
Have a drink in hopes that a dev will come up with a way to Root 2.2 soon!

I didnt update over the phone
What happened is I installed a rooted verson of 1.47.651.1 but in doing that it got rid of the recovery image... it definetly a rooter version because i can run apps that require root.. such as wife tether titanium back etc...
any other suggestions...

coolguycarlos said:
I didnt update over the phone
What happened is I installed a rooted verson of 1.47.651.1 but in doing that it got rid of the recovery image... it definetly a rooter version because i can run apps that require root.. such as wife tether titanium back etc...
any other suggestions...
Click to expand...
Click to collapse
there's an update.zip around here somewhere that will allow you to boot into an early form of clockwork recovery.
so, assuming that you goofed something, but still have nand unlocked....
find that update.zip. put it and a .zip for a real recovery onto your sdcard. boot into hboot, let it run the update.zip, that will take you to koush's early clockwork recovery. use that recovery to flash a solid recovery.
done.
alternative method would be to use fastboot to erase the recovery partition, then put a new recovery in.

Here is the update.zip...Just extract Recovery.zip....Do this OR/AND what the Senior Member above said and you should be good

timothydonohue said:
there's an update.zip around here somewhere that will allow you to boot into an early form of clockwork recovery.
so, assuming that you goofed something, but still have nand unlocked....
find that update.zip. put it and a .zip for a real recovery onto your sdcard. boot into hboot, let it run the update.zip, that will take you to koush's early clockwork recovery. use that recovery to flash a solid recovery.
done.
alternative method would be to use fastboot to erase the recovery partition, then put a new recovery in.
Click to expand...
Click to collapse
I actually tried the update.zip one already and it doesnt install... it will stated that the signature cant be verified and it will about the installation... havent tried the fastboot approach... I guess I will need to find out how to do that now

so from the looks of it I am screwed... I have hboot .79 if that matters and from the looks of it the rooted rom i installed screwed up my nand unlock.. which is why i think i can install any recovery images... i tried alot of the nand unlock tutorials and most of them I eventually get to a point were i need to write to /data and i cant because permissions are denied... great... oh well i'll keep on trying... any suggestions are appreciated...

If you still have super user, try this...same thing happend to me.
http://forum.xda-developers.com/showthread.php?t=744621&page=4

I'm having a very similar problem also. My Hboot is 0.79.000 too & after trying clockworkmod recovery, a few RUU update attempts, and attempting to change ROMs completely (not in that order) I'm at a loss, no success anywhere. I can't even get in to recovery anymore. It just reverts back to Bootloader menu where my options are Reboot, Reboot Bootloader, or Power down (& I think there is one other option that i tried and sent me back to the aforementioned screen). However, I can still load my pre-existing ROM...
Does anyone have any ideas if there is anything I can do?
TIA

topdawgn8 said:
If you still have super user, try this...same thing happend to me.
http://forum.xda-developers.com/showthread.php?t=744621&page=4
Click to expand...
Click to collapse
I have a question bout this... I seen this before but the sdk that I downloaded for Windows 7 does not have the Su command... any ideas on how I can get it for Windows 7?
Sent from my PC36100 using XDA App

Nevermind I got the Su command to work
Sent from my PC36100 using XDA App

you can erase recovery from rom manager and try to reflash. i would recommend reinstalling rom manager just to make sure it installed correctly. it installed bad on me once and corrupted my recovery trying to update it, reinstalled and installed an old recovery then the newest one and it worked.

Thanks for the suggestions all. I followed the instructions from link you posted using terminal emulator. No such luck, still reading HBOOT 0.79.0000 and running same ROM.
I also tried reinstalling (several times) clockworkmod recovery images and it effects nothing.
Should I try to completely unroot my phone again? If the images i just flashed didn't do it what will?
Im totally at a loss here. ARG!

hit there jtwonbly.......are you also running the stock rooted 1.47.651.1?

Build number 1.47.651.1 CL195459 release-keys

yea same here......and what is it that your trying to do...go back to stock ROM?

I'd like to go to any other ROM. Its as if I'm no longer rooted anymore.
I think I may try to start all over again using NeckFaces old tutorial on unlocking NAND w/o adb. I'm just not sure if that will fix the HBOOT file because I can't get in to Recovery.

OK Guys thanks for all your help but I have been able to get it fixed now!!!
I pretty much had to redo all of Toast Root tutorial and NAND unlock to get it working. Both Part 1 and Part 2 even though I was already running a rooted rom.
The original problem I had is I kept getting told to just try the nand unlock in part 2 but the phone wasnt having it. It wouldnt like the engineering build of the pc36img.zip
So I started from Part 1. Downloaded the rooted rom pc36img.zip and what do you know it finally let me install it. By the time I was done with both parts 1 and 2 I was able to flash a recovery image, get back to hboot .76 and I am now another proud owner of an Evo running a rooted Froyo!!!!

[Q] Rom manager, rom backup and red exclamation point

Hi
I am trying to backup my current rom from my rooted Tmo G2(just for trying because i could get the original rom from the xda wiki.
When i click on the backup rom, my phone reboots and tries to go onto recovery mode, but then i get that black phone and the red exclamation point. after that i cannot do anything.
I have to remove the battery to reboot the phone.
What am i doing wrong here?
thanks

The red exclamation means your still in stock recovery. Reboot the phone, go into ROM Manager and flash the recovery TWICE. I had this same problem and flashing it a second time solved it
Sent from my T-Mobile G2 using XDA App

you are a genius.
I did update the recovery before trying, but this time, i did it twice in a row and that did the trick
thanks again

Same problem but flashing it twice still doesn't fix it?
pretty much what i said above... I have the same exact problem so when i =read this i flashed it twice and still get the red ! arrow when i backup it restarts? any other ideas?

If you get this image, just hit Vol (+) and Power. This will continue you to recovery and you can see whether you are still stock or CW Recovery. I am CW, but I will sometimes get the triangle image.

I think you have to flash twice because of root permissions.
My G2 did not ask me for superuser permission until after it had already downloaded the recovery and was in the process of installing it.
The second time you flash it, ROM manager will already have the superuser permission it needs to successfully install it.
I think that the initial (unsuccessful) installation of recovery is what gets ROM manager to ask for superuser access.
So if you have a way to grant ROM manager su permission before installing, it SHOULD work the first time. I don't really know how to test this theory yet though.

I temp rooted + flashed the recovery part 4 times now, "successful" each time, but on "ROM Backup", the red exclamation mark is the only thing that works..
DesireHD

AlCapone said:
I temp rooted + flashed the recovery part 4 times now, "successful" each time, but on "ROM Backup", the red exclamation mark is the only thing that works..
DesireHD
Click to expand...
Click to collapse
Do you have Desire HD ? If so, you are in the wrong forum, this is the Vision forum (G2/Desire Z).
If you do have a Vision, then I suspect the problem is that you don't have S-OFF. Temp root is enough to run ROM Manager, but not enough to flash a custom recovery.

ok, thanks that might be it - still ..strange that it detects the recovery software as installed after boot - maybe it's just saving the information and fakes it. ?
yes, I am in wrong forum - just searched for this issue, and it seems like it is just the same.
Thanks.

AlCapone said:
ok, thanks that might be it - still ..strange that it detects the recovery software as installed after boot - maybe it's just saving the information and fakes it. ?
yes, I am in wrong forum - just searched for this issue, and it seems like it is just the same.
Click to expand...
Click to collapse
If you don't have S-OFF, then your recovery partition (plus others) is write-protected in hardware. So the software thinks it's writing to it, but the data is just being held in cache. When you reboot the cache is lost so you see the old image (i.e. stock recovery) again.

Remember to have "USB Debugging" enabled, i've just spend over 2hrs tbefore i've figured it out...

I just perm rooted my G2 using the Visonary + gfree (No ADB) method, and it worked on the 1st try. I am also trying to backup my stock rom, and was wondering about the steps. I have ROM Manager, and I know that I need to flas ClockWorkMod Recovery, But do I do it before I attempt to backup my current ROM, or after? Do I need to erase recovery before flashing ClockWork?

omarsalmin said:
The red exclamation means your still in stock recovery. Reboot the phone, go into ROM Manager and flash the recovery TWICE. I had this same problem and flashing it a second time solved it
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
This worked perfectly for me. Thank you!

Stuck on boot screen! Help!

Hi!
I bought a Desire HD a week ago and today I decided to try one of the custom roms. I rooted it with Visionary+, turned s-off with the one-click tool found in another thread, installed Rom Manager and Clockwork mod and then flashed it with a custom rom from the recovery/boot screen without wiping anything.
The problem is, when I later tried to install another rom, it wouldn't boot, it's stuck on the HTC boot screen. I've tried reflashing it, wiping everything there is to wipe and I even tried RUU but it won't recognize the phone. Can anyone help me how to restore to the normal stock rom?! I can bring up the Clockworkmod recovery menu if I take out the battery and put it back in.
I would be very grateful if someone could help me with this! Consider that I'm a noob though so try to write the instructions as simply as possible

Hi, I'm basically in the same boat (I take it you tried one of the stable CM6 builds?).
Digged through an awful lot of stuff, found something about downgrading clockwork.
Maybe this'll help you, I'm still having trouble.
I've found an older clockwork recovery image, gathered all the SDK bits and pieces, got my USB drivers set up after even more digging - now this:
D:\android-sdk-windows\tools>fastboot boot recovery.img
downloading 'boot.img'... OKAY
booting... FAILED (remote: not allowed)
It's rooted, S-OFF, all that good jazz. Halp. :<

enectrixx said:
Hi!
I bought a Desire HD a week ago and today I decided to try one of the custom roms. I rooted it with Visionary+, turned s-off with the one-click tool found in another thread, installed Rom Manager and Clockwork mod and then flashed it with a custom rom from the recovery/boot screen without wiping anything.
The problem is, when I later tried to install another rom, it wouldn't boot, it's stuck on the HTC boot screen. I've tried reflashing it, wiping everything there is to wipe and I even tried RUU but it won't recognize the phone. Can anyone help me how to restore to the normal stock rom?! I can bring up the Clockworkmod recovery menu if I take out the battery and put it back in.
I would be very grateful if someone could help me with this! Consider that I'm a noob though so try to write the instructions as simply as possible
Click to expand...
Click to collapse
Which version clockwork mod are you using? And what is the ROM you tried to flash?
Sometimes custom ROMs can take 5 minutes to boot...so give it some more time and see if that helps.

Headwoünd said:
Hi, I'm basically in the same boat.
Digged through an awful lot of stuff, found something about downgrading clockwork.
Maybe this'll help you, I'm still having trouble.
I've found an older clockwork recovery image, gathered all the SDK bits and pieces, got my USB drivers set up after even more digging - now this:
D:\android-sdk-windows\tools>fastboot boot recovery.img
downloading 'boot.img'... OKAY
booting--- FAILED (remote: not allowed)
It's rooted, S-OFF, all that good jazz. Halp. :<
Click to expand...
Click to collapse
seems like your pc is not recognizing your phone. And should not you flash the recovery first and then boot?

I did flash the recovery via Rom Manager, which gave me Clockwork Recovery version 3.0.0.5.
Then I had Rom Manager download CM6, it rebooted the phone, phone gets stuck in HTC splash screen.
According to the thread I linked above, I needed to downgrade Clockwork Recovery, hence flashing 2.5.x.x via command prompt.
The drivers are installed correctly, I'm at least sure of that.
Recovering my previously backed up stock ROM won't get me further than the splash screen either, same with wiping everything that can be wiped before that.

Headwoünd said:
I did flash the recovery via Rom Manager, which gave me Clockwork Recovery version 3.0.0.5.
Then I had Rom Manager download CM6, it rebooted the phone, phone gets stuck in HTC splash screen.
According to the thread I linked above, I needed to downgrade Clockwork Recovery, hence flashing 2.5.x.x via command prompt.
The drivers are installed correctly, I'm at least sure of that.
Recovering my previously backed up stock ROM won't get me further than the splash screen either, same with wiping everything that can be wiped before that.
Click to expand...
Click to collapse
Then use ROM manager to downgrade the CWM to 2.x. You can do it under the option "All recoveries" in ROM manager. People are reporting problems with the latest version of CWM. Check if you get the same if you wipe everything and install another custom ROM.

Can't find a way to even get past the first splash screen - only thing I can properly access is the Bootloader.

Same here. When I boot I just see the initial "HTC" logo, nothing else.
I had Mike's Revolution HD ROM installed and working just fine, and then I tried to install another mod, which got me to this situation.
I have CWM 3.0.0.5 and I have a nandroid backup of the working system from before installing the last mod.
I tried recovering the nandroid, which goes smoothly (including the MD5 validation of the backup) but it still doesn't boot afterwards. I wiped the boot, system and data partitions and tried restoring again - same result.
I assume my next step is to flash a new ROM but unfortunately I don't have any ROMs on my SDCARD, so I need a way to push it there. I tried with fastboot but it doesn't recognize a partition called "sdcard". I believe adb should work while I'm in CWM but it just says "error: device not found".
Any suggestions?

sphuyal said:
Which version clockwork mod are you using? And what is the ROM you tried to flash?
Sometimes custom ROMs can take 5 minutes to boot...so give it some more time and see if that helps.
Click to expand...
Click to collapse
Sorry, no idea which version, but it's the default that comes with Rom Manager. I downloaded Rom Manager yesterday so I guess it's the most recent Clockwork mod.
Left it for 15 minutes, still nothing. I used Android Revolution HD 2.0.11 for the first flash which worked and then when I tried to install Pays-ROM HD Sparta 1.0 I got stuck on the boot screen. I've tried recovering from the previous backup I made on the recovery screen with no result.

Just got mine back alive
Flashed CWM 2.5.1.3 and restored the nandroid with it.
Spending the last few hours searching the forums my best advice is to avoid 3.0.0.5

Went a different approach - finally figured out that you could mount the sdcard via Clockwork Recovery, threw newest CM7 nightly on there and installed it with Clockwork as well.
CHRIST that was a pain in the ass... and I thought downgrading the stock ROM was annoying.

as a rule i have found out cwm3 is for flashing gingerbread and cwm2 is for froyo

Headwoünd said:
Went a different approach - finally figured out that you could mount the sdcard via Clockwork Recovery, threw newest CM7 nightly on there and installed it with Clockwork as well.
CHRIST that was a pain in the ass... and I thought downgrading the stock ROM was annoying.
Click to expand...
Click to collapse
Thanks for the advice! It worked for my DHD too Except that I, after flashing ut with CM7, restored it to stock with RUU! Thanks to everyone here who tried to help

erank said:
Just got mine back alive
Flashed CWM 2.5.1.3 and restored the nandroid with it.
Spending the last few hours searching the forums my best advice is to avoid 3.0.0.5
Click to expand...
Click to collapse
how do I get 2.5.1.3 onto the device when I can't even get the darn thing to load?

encrypshun said:
how do I get 2.5.1.3 onto the device when I can't even get the darn thing to load?
Click to expand...
Click to collapse
Read here: http://forum.xda-developers.com/showthread.php?t=855490&page=132 (jump to page 132 #1312)...
Take your battery off, then put it back in. Hold power button and volume down button at the same time. You come to recovery...or alternately you can use adb.

sphuyal said:
Read here: http://forum.xda-developers.com/showthread.php?t=855490&page=132 (jump to page 132 #1312)...
Take your battery off, then put it back in. Hold power button and volume down button at the same time. You come to recovery...or alternately you can use adb.
Click to expand...
Click to collapse
mate you're a STAR. I actually downloaded a recovery image (from post 1315) in the same thread but it kept saying "connecting to device". When I downloaded the recovery image from 1312 and ran "fastboot flash recovery recovery.img" it say's
sending recovery ... OK
writing recover ... OKAY
What do I do next? Just reboot the device?

oh mother looks like I got somewhere. I did a format device and it went into the CWM 2.3.XX screen as below, reloaded Cyanogen 6.1.3 and boom I'm in. Man I though the device was a goner....I'm almost feeling brave enough to install Cyanogen 7.X

encrypshun said:
oh mother looks like I got somewhere. I did a format device and it went into the CWM 2.3.XX screen as below, reloaded Cyanogen 6.1 and boom I'm in. Man I though the device was a goner....
Click to expand...
Click to collapse
So you are happy with your device now?

Well not really, I went back to HTC Sense because Internet Pass Through wasn't available on Cyanogen and now I cannot get the phone to login and create my google account no matter what

Headwoünd said:
Can't find a way to even get past the first splash screen - only thing I can properly access is the Bootloader.
Click to expand...
Click to collapse
the REMOTE NOT ALLOWED error means you only have radio s-off, so you cannot issue fastboot commands to your device.

can someone please help me with my problem i have

hello everyone i ran into a little bit of a problem last night. here it is, i was messing around with a new rom i got and i was using setcpu and i overclocked then i went back to make it normal again and it said it didn't have root access so i couldn't put it back to normal. so then i tried to go into superuser and it would automatically FC. so then i thought it would be a smart idea to reboot and now im stuck at the white boot screen and i cant enter recovery, i can go into bootloader and when i do it says that i have s-on but i know that it was off before i messed it up. ive tried to flash new recoveries and no luck anyone have any ideas? any help is appreciated

Could see if somebody has a stock rom that you could flash to get it back to factory state. On the bionic someone compiled a desktop app that does it once booted into fastboot. Not sure if any this helps but could be a start?
Sent from my DROID BIONIC using xda premium

i would say try to reinstall super user, and go from there, or maybe search the market for busybox, and install/reinstall that

Active_Matrix said:
i would say try to reinstall super user, and go from there, or maybe search the market for busybox, and install/reinstall that
Click to expand...
Click to collapse
i cant even boot up the rom i get stuck on the white evo slash screen.

RUU back to stock or find the newest PC36IMG.zip and update through fastboot. I don't have the link handy, just search for the newest one. You already lost s-off somehow, so you won't be able to flash anything but a signed HTC rom anyway. Once you get it booting again just reroot and off you go.

[Q] Upgrading to cyanogenmod 7.1 issues

Phone: HTC Desire GSM
I have Cyanogen 7.0.3 and want to upgrade to 7.1, mainly to keep up to date but also because since I got a market update a couple of months ago I keep getting force closes whenever I try to update or download a new app. This also force closes when it tries to update the superuser app, as it says binary outdated and won't let me use it, then tries to download the new one and FC's.
When I try to go into recovery, I get the red triangle. How can I get a custom recovery like clockworkmod on there? I also noticed from the bootloader menu that I still have S_ON, how can I fix this? The suggestion from the cyanogen wiki is to use Revolutionary, but when filling out the form for the beta key, my HBOOT version is not on there. Mine is 0.75, the only two options are 0.93 and 1.02.
What are my options for getting cyanogen 7.1 on my phone, or at least fixing this awful force close thing that leaves my market unusable. I've tried a few fixes for it but none have worked.

Pryomancer said:
Phone: HTC Desire GSM
I have Cyanogen 7.0.3 and want to upgrade to 7.1, mainly to keep up to date but also because since I got a market update a couple of months ago I keep getting force closes whenever I try to update or download a new app. This also force closes when it tries to update the superuser app, as it says binary outdated and won't let me use it, then tries to download the new one and FC's.
When I try to go into recovery, I get the red triangle. How can I get a custom recovery like clockworkmod on there? I also noticed from the bootloader menu that I still have S_ON, how can I fix this? The suggestion from the cyanogen wiki is to use Revolutionary, but when filling out the form for the beta key, my HBOOT version is not on there. Mine is 0.75, the only two options are 0.93 and 1.02.
What are my options for getting cyanogen 7.1 on my phone, or at least fixing this awful force close thing that leaves my market unusable. I've tried a few fixes for it but none have worked.
Click to expand...
Click to collapse
jheeze theres a troubleshooting guide for you stickied.. so it's the first thing you see when you go into Q&A and yet you still post a new thread.. come on man that's what its there for! Just check it out and you can get a solution there

Uninstall updates on superuser
Try setting language to US English for market.
Assume you used Rom manager to flash before?
Also sounds like you rooted pre unrevoked?
At the red triangle, press vol.up plus power. Does it say HTC recovery 2.0e? If so this is the.leaked engineering recovery we started with.
If you used Rom manager, you probably have update.zip on your sd card to boot into cwm fake flash.
If not, here it is: http://db.tt/s6MoApxB
Put it on the root of sd and boot into the engineering recovery. Apply update from there then take a nandroid backup.
If its true alpharev doesn't work with 0.75 (have you tried? I don't know) best bet is probably to RUU. But in order to use alpharev, not sure if cm7 is compatible so flash teppic74 rooted stock Froyo. You can also do this via fake flash cwm. Run alpharev to test.
Like I said, if not, probably easier to RUU then root with unrevoked or s-off with revolutionary
Sent from my HTC Desire using XDA App

bortak said:
jheeze theres a troubleshooting guide for you stickied.. so it's the first thing you see when you go into Q&A and yet you still post a new thread.. come on man that's what its there for! Just check it out and you can get a solution there
Click to expand...
Click to collapse
It's the first thing I went to, but my situation seems to meld two or three of the problems addressed in that guide.
I'm rooted, with S_ON, going to recovery brings up the red triangle, my HBOOT is 0.75. I'm wondering if anyone can suggest some specific actions for me to take. It's a lot of things to consider and is somewhat overwhelming. I don't know where to begin.

rootSU said:
Uninstall updates on superuser
I did this, it seemed to work, I can get superuser access on a terminal with su now. Before it would crash. But I tried following some instructions to create a market-download-cache folder but I didn't have permission to do it.
Try setting language to US English for market.
I tried that before, it didn't work.
Assume you used Rom manager to flash before?
Yes, I put cyanogen 7.1 on my sd card and went to flash through rom manager, but it went to the red triangle screen. If you mean did I use rom manager to get my current version of cyanogenmod on my phone, then yes I did do that. However that was on my computer before I upgraded to Win7. I had this .bat file that I ran and it pushed a load of files to my phone over usb which fixed the red triangle and took it to a recovery menu. I can't find that again. Would it work if I did have it?
Also sounds like you rooted pre unrevoked?
I suppose so. I got my Desire a few days after it came out, rooted it probably 2-3 months later.
At the red triangle, press vol.up plus power. Does it say HTC recovery 2.0e? If so this is the.leaked engineering recovery we started with.
Yes, it says 'Android system recovery <2e>, in blue text. I also have a small menu consisting of Reboot system now, Apply sdcard:update.zip(I assume that's from rom manager?), wipe data/factory reset, and wipe cache partition. It also says below all that in yellow text, 'E:Can't open /cache/recovery/command
If you used Rom manager, you probably have update.zip on your sd card to boot into cwm fake flash.
If not, here it is: http://db.tt/s6MoApxB
I heard Rom Manager is not good anymore as of some recent updates to it. It can mess up installations. Is this true?
Put it on the root of sd and boot into the engineering recovery. Apply update from there then take a nandroid backup.
If its true alpharev doesn't work with 0.75 (have you tried? I don't know) best bet is probably to RUU. But in order to use alpharev, not sure if cm7 is compatible so flash teppic74 rooted stock Froyo. You can also do this via fake flash cwm. Run alpharev to test.
Like I said, if not, probably easier to RUU then root with unrevoked or s-off with revolutionary
Click to expand...
Click to collapse
Thank you for that. Is my situation bad, is it salvagable? So I should apply the update.zip from that recovery screen? What happens after that?
In fact, maybe I should revise what I actually want to do. I just want cyanogen 7.1, so do I even need to gain S_OFF? What do I need to do to be able to get into recovery and flash it? Is it that simple or do I need to do other things?

You doo if you want to use CM7 HBOOT. Some root apps also requires S-OFF.

Pryomancer said:
Thank you for that. Is my situation bad, is it salvagable? So I should apply the update.zip from that recovery screen? What happens after that?
In fact, maybe I should revise what I actually want to do. I just want cyanogen 7.1, so do I even need to gain S_OFF? What do I need to do to be able to get into recovery and flash it? Is it that simple or do I need to do other things?
Click to expand...
Click to collapse
you need s-off to replace the engineering recovery with cwm true flashed recovery as the engineering one is hugely limited. Please confirm you have this
Sent from my HTC Desire using XDA App

As beautiful n functional cynogen mod is,I couldn't get it to work properly on my phone,it had something to do with force close Android.phone looping continuously as soonm as my phone air get network it air lose it...tried the 2g,3g network change n still didn't work

leoaamro said:
As beautiful n functional cynogen mod is,I couldn't get it to work properly on my phone,it had something to do with force close Android.phone looping continuously as soonm as my phone air get network it air lose it...tried the 2g,3g network change n still didn't work
Click to expand...
Click to collapse
did you do a full wipe before you installed CM? if you didn't go to mounts and storage and format everything apart from the sdcard and then flash it again.
---------- Post added at 06:02 PM ---------- Previous post was at 05:58 PM ----------
Pryomancer said:
Phone: HTC Desire GSM
I have Cyanogen 7.0.3 and want to upgrade to 7.1, mainly to keep up to date but also because since I got a market update a couple of months ago I keep getting force closes whenever I try to update or download a new app. This also force closes when it tries to update the superuser app, as it says binary outdated and won't let me use it, then tries to download the new one and FC's.
When I try to go into recovery, I get the red triangle. How can I get a custom recovery like clockworkmod on there? I also noticed from the bootloader menu that I still have S_ON, how can I fix this? The suggestion from the cyanogen wiki is to use Revolutionary, but when filling out the form for the beta key, my HBOOT version is not on there. Mine is 0.75, the only two options are 0.93 and 1.02.
What are my options for getting cyanogen 7.1 on my phone, or at least fixing this awful force close thing that leaves my market unusable. I've tried a few fixes for it but none have worked.
Click to expand...
Click to collapse
What I would do:
Use alpharev 1.8 to S-OFF
Download recovery
Do a full wipe (mounts & storage, format boot, syste, data, cache, sd-ext)
Flash ROM
---------- Post added at 06:09 PM ---------- Previous post was at 06:02 PM ----------
also @RootSU - I swear you can't flash anything from the stock recovery? I tried before and it didn't let me.. otherwise what would be the point of rooting and flashing custom recovery if it was that easy?
also im pretty sure Alpharev works on that version, it's revolutionary that doesn't.

No not stock. Before unrevoked we all had to push an engineering HTC recovery (used by HTC engineers) not stock. It's the one.that says 2.0(e) at the top. You can apply update.zip only
Sent from my HTC Desire using XDA App

rootSU said:
No not stock. Before unrevoked we all had to push an engineering HTC recovery (used by HTC engineers) not stock. It's the one.that says 2.0(e) at the top. You can apply update.zip only
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
oh, I thought that was the stock one, and yeah I tried applying update.zip through that recovery once but it didn't work for me. I've only tried to use it once so I guess you know about it more than me

bortak said:
oh, I thought that was the stock one, and yeah I tried applying update.zip through that recovery once but it didn't work for me. I've only tried to use it once so I guess you know about it more than me
Click to expand...
Click to collapse
The update.zip I used to apply regularly was the fakeflash cwm. I often forgot back in those days that the reboot into recovery from the power button took me to the Triangle unlike RM which took me to CWM.
The huge downfall of this setup is that sometimes if your FS is already a little corrupt, CWM decides to "wipe" the sd card, taking with it the update.zip for cwm.
Thats why I RUU's and rooted with unrevoked when it came out.

rootSU said:
The update.zip I used to apply regularly was the fakeflash cwm. I often forgot back in those days that the reboot into recovery from the power button took me to the Triangle unlike RM which took me to CWM.
The huge downfall of this setup is that sometimes if your FS is already a little corrupt, CWM decides to "wipe" the sd card, taking with it the update.zip for cwm.
Thats why I RUU's and rooted with unrevoked when it came out.
Click to expand...
Click to collapse
Ahh right, I never knew that.. I only rooted my phone about 6 months after I got it so I used unrevoked from the start

rootSU said:
you need s-off to replace the engineering recovery with cwm true flashed recovery as the engineering one is hugely limited. Please confirm you have this
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
It says <2e> at the top of the recovery when I do power+vol.up at the red triangle screen. From what you've said this seems to indicate I do have the engineering recovery.

Pryomancer said:
It says <2e> at the top of the recovery when I do power+vol.up at the red triangle screen. From what you've said this seems to indicate I do have the engineering recovery.
Click to expand...
Click to collapse
search your clockworkmod folder for a "update.zip"
place it in the root of your sdcard
when you boot the engineering reocvery, press VOLUME UP and POWER together.. it may take several attempts before you get anything.. sometimes you don't press it at exactly the same time or whatever
choose "apply update.zip"
When the new recovery is booted
flash a rom

bortak said:
search your clockworkmod folder for a "update.zip"
place it in the root of your sdcard
when you boot the engineering reocvery, press VOLUME UP and POWER together.. it may take several attempts before you get anything.. sometimes you don't press it at exactly the same time or whatever
choose "apply update.zip"
When the new recovery is booted
flash a rom
Click to expand...
Click to collapse
Ive been in this situation and it can be a nightmare if the SD fails so personally rather than flashing a rom using cwm fake flash, I would simply nandroid backup.
Then RUU and start from scratch. As unique as the 2e is, its better to have a decent recovery flashed.
Update.zip should be on the root of sd anyway. If not, here it is:http://dl.dropbox.com/u/20471345/SUroot/Tools/Android/Recovery/CWM2.5.0.7 fakeflash/update.zip

thanks for the reply bortak, i will try when I get bored of the current rom - Aurora....
I've read it in quite a few places of users experiences the force close phone.android error inspite of the wipes (not format's)
check here - http://forum.xda-developers.com/showthread.php?t=968501

leoaamro said:
thanks for the reply bortak, i will try when I get bored of the current rom - Aurora....absence of smart dialling was putting me off..
Click to expand...
Click to collapse
you can always download a different dialer app from market