Related
Guys, I need some help from you.
I already tried to search the tread but can't found the information I would like to get.
I tried to update my Desire rom following step on this page "(h)ttp://theunlockr.com/2010/06/07/how-to-load-a-custom-rom-on-the-htc-desire/" (note I already rooted my phone, and sorry I'm new member can't post the link correctly). Everything went well till step 7. Select Apply sdcard:update.zip.... then it fail to update. So, I rebooted my desire then it can't boot up to main screen (HTC Sense). So, I entered boot loader once again and selected Recovery mode. Now, it stuck at HTC white screen and doesn't go anywhere further than that.
I guess what cause this is "I didn't change the name of recovery package in step 1" so I might break some data? (please correct me if I'm wrong)
If this the case how should I fix it? Is there any suggestion?
Thank you in Advance
Now, I'm trying to flash RUU via fastboot. The process went well. However, after complete flash, it still can't boot to main screen. Will it help if I try to flash another RUU?
P.S. Phone shakes many time when I open it and then stuck on HTC white screen...
maybe this help you
http://forum.xda-developers.com/showthread.php?t=747775
Try unrEVOked, it will install a recovery image to your phone. Then enter recovery mode, it will be Clockworkmod then you choose install zip from SD card, browse until the .zip file and select it. Note that in clockworkmod you navigate with the trackball and select by pressing on the trackball.
Sent from my HTC Desire using XDA App
forelli said:
Try unrEVOked, it will install a recovery image to your phone. Then enter recovery mode, it will be Clockworkmod then you choose install zip from SD card, browse until the .zip file and select it. Note that in clockworkmod you navigate with the trackball and select by pressing on the trackball.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
I can confirm, that this should fix your problem.
I had the exact issue as you last night, but managed to finally fix it by using the unrevoked software to get recovery, then erasing cache, then flashing a new rom.
F0l3ert said:
I can confirm, that this should fix your problem.
I had the exact issue as you last night, but managed to finally fix it by using the unrevoked software to get recovery, then erasing cache, then flashing a new rom.
Click to expand...
Click to collapse
How can I use unrEVOked methode? I'm trying it and now stuck by the fact that I can't boot into Android right now. unrEVOked is asked me to enable USB debugging but I can't... Is there any way to perfrom unrEVOked without booting into Android?
Tried other RUU including Froyo one but still no hope...
i was going between ROMS trying out different versions. then i installed Vision BaconBits 0.3 on a Modaco DESIRE Z rom (i know, i know) & now the phone is stuck in a boot loop.
then i noticed i couldn't revert back to the stock ROM like i've done before. i wiped & tried again, but to no avail.
says MAIN VERSION is older or something like that.
i even tried the Modaco ROM again too, but nada. it fails.
oh yeah... and for some reason i got S-ON again. i'm like wtf?
so... did i brick my phone? or is there a way to get it going again?
btw, i did install ClockworkMod Recovery for G2 & did a back up before i tried out the DESIRE Z ROM.
DJ ELITE said:
i was going between ROMS trying out different versions. then i installed Vision BaconBits 0.3 on a Modaco DESIRE Z rom (i know, i know) & now the phone is stuck in a boot loop.
then i noticed i couldn't revert back to the stock ROM like i've done before. i wiped & tried again, but to no avail.
says MAIN VERSION is older or something like that.
i even tried the Modaco ROM again too, but nada. it fails.
oh yeah... and for some reason i got S-ON again. i'm like wtf?
so... did i brick my phone? or is there a way to get it going again?
Click to expand...
Click to collapse
it sounds like your phone is screwed!if there truly is no way to fix this return it for hinge issues or something,even pop the hinge if you have to lol
Try to get into clock work wipe if you can the system should try to reinstall stock , or see if you have adb access and then you can go from there . Good luck
Sent from my HTC Vision using XDA App
DJ ELITE said:
btw, i did install ClockworkMod Recovery for G2 & did a back up before i tried out the DESIRE Z ROM.
Click to expand...
Click to collapse
So your not able to Volume Down + Power and get into clockwork still? If so then why couldnt you just restore the backup you made.
thx for the expedient reponse...
bled82 said:
Try to get into clock work wipe if you can the system should try to reinstall stock , or see if you have adb access and then you can go from there . Good luck
Click to expand...
Click to collapse
the phone boot loops. how do i get in CWM?
userfriendlyme said:
So your not able to Volume Down + Power and get into clockwork still? If so then why couldnt you just restore the backup you made.
Click to expand...
Click to collapse
i can def do the Volume Down + Power. how does that get me in to CWM?
I'm still new to this so take my advice with a grain of salt but I think that "Main version is older issue" can be avoided by using the hex editor to change the build number on the ROM. Try changing the version with the hex editor as per this post:
http://forum.xda-developers.com/showthread.php?t=831398
and then try to flash it. Hopefully thats all you need to do.
pull the battery, wait a couple seconds and put back in. now hold the volume down button and press power. the phone will boot into fastboot. use volume down key to select recovery and hit the power button to confirm. if CW is still on your phone it will load, if you have s-on idk if it will load without su privilages or not im not a dev but try it.
edit: i have soft bricked my g1 like 10 times, the main thing to remember is backup, wipe wiPE WIPE! and follow instructions to a T.
DJ ELITE said:
i can def do the Volume Down + Power. how does that get me in to CWM?
Click to expand...
Click to collapse
If you can get vol dwn + pwr to work, then you can scroll to recovery. from there, you should be able to restore your backup from rom manager. If it's not in that one, then hold trackpad button + power and scroll to recovery.
if you can get into the clockwork recovery and can successfully get adb to recognize the phone, try the downgrade from OTA. it will restore your phone back to out of the box.
http://forum.xda-developers.com/showthread.php?t=831398
you might need a usb microsd reader to get the files onto and off of the sd card
thx for the reponses...
Azrael3123 said:
I'm still new to this so take my advice with a grain of salt but I think that "Main version is older issue" can be avoided by using the hex editor to change the build number on the ROM. Try changing the version with the hex editor as per this post:
http://forum.xda-developers.com/showthread.php?t=831398
and then try to flash it. Hopefully thats all you need to do.
Click to expand...
Click to collapse
yikes... sounds a lil too experimental to me. thx for chiming in tho. truly appreciated.
EdTeach1680 said:
pull the battery, wait a couple seconds and put back in. now hold the volume down button and press power. the phone will boot into fastboot. use volume down key to select recovery and hit the power button to confirm. if CW is still on your phone it will load, if you have s-on idk if it will load without su privilages or not im not a dev but try it.
edit: i have soft bricked my g1 like 10 times, the main thing to remember is backup, wipe wiPE WIPE! and follow instructions to a T.
Click to expand...
Click to collapse
yeah... i don't see CMW.
digikid said:
If you can get vol dwn + pwr to work, then you can scroll to recovery. from there, you should be able to restore your backup from rom manager. If it's not in that one, then hold trackpad button + power and scroll to recovery.
Click to expand...
Click to collapse
in RECOVERY i don't see ROM MANAGER. just the standard:
Rebooty system now
Apply sdcard:update.zip
Wipe data/factory reset
Wipe cache partition
thx for the response.
pr0naLd said:
if you can get into the clockwork recovery and can successfully get adb to recognize the phone, try the downgrade from OTA. it will restore your phone back to out of the box.
http://forum.xda-developers.com/showthread.php?t=831398
you might need a usb microsd reader to get the files onto and off of the sd card
Click to expand...
Click to collapse
i'm using my old HTC Rhodium to rename/transer files on the SD.
unfortunately... no CMW that i can see.
I can understand your hesitation but if you read through the post you will see that many people have tested it and it should work fine. At this point its the only way to downgrade to stock due to the "Main version is older" issue and, assuming you truly can't access clockwork recovery, I don't see what other method there is. Whats really got me twisted is the S-on part; I could've predicted some issue by flashing BB onto the Z rom but I wouldn't have seen that coming. Is it even possible to flash anything while S-on is enabled?
maybe you can use an offical update.zip that is signed. i dunno
DJ ELITE said:
in RECOVERY i don't see ROM MANAGER. just the standard:
Rebooty system now
Apply sdcard:update.zip
Wipe data/factory reset
Wipe cache partition
Click to expand...
Click to collapse
Hmmm...then you didn't install the CWM recovery. You should try to flash the rom that shipped with the phone. You can get it here. To do that, you need to get it onto your memory card as update.zip, then boot to recovery and choose "Apply sdcard:update.zip" and then you should have a bootable phone again.
thx for the reponses...
Azrael3123 said:
I can understand your hesitation but if you read through the post you will see that many people have tested it and it should work fine. At this point its the only way to downgrade to stock due to the "Main version is older" issue and, assuming you truly can't access clockwork recovery, I don't see what other method there is. Whats really got me twisted is the S-on part; I could've predicted some issue by flashing BB onto the Z rom but I wouldn't have seen that coming. Is it even possible to flash anything while S-on is enabled?
Click to expand...
Click to collapse
don't get me wrong, i feel u. i may have no choice but to try that. i'm getting desperate.
however, the current ROM loaded is the Modaco DESIRE Z w/the Vision BaconBits 0.3 updated to it... and after that, it kept boot looping. plus the fact that i have S-ON.
supergear said:
maybe you can use an offical update.zip that is signed. i dunno
Click to expand...
Click to collapse
have em. renamed em. tried em. (e.g.: PC10IMG.zip[, updated.zip)
oh that sucks
I was stuck in the same boat as you were. I had a stock rom permarooted and messed up editting on of the /system/ files. and got stuck with endless reboot. i then flashed this: [ROM] Desire Z Sense on the G2 (via HBOOT) because it was the only rom out at the time. It successfully loaded, but i wanted to go back to stock. i then flashed the OTB rom and got stuck with a desire z rom with s-on. No other rom would flash so i proceeded to temp-root and do the downgrade from OTA.
You lost root. Have to install the PC10.img and re-root.
Sent from my T-Mobile G2 using XDA App
But in order to edit the files necessary to flash down to the stock ROM, he needs to have at least temp root so he can pull and edit the misc.img (I think). If he has S-on and is stuck in a boot loop, how can he access visionary or terminal emulator in order to set up that temp root? I think that's the biggest issue unless I'm missing something.
Shouldn't the stock rom have everything that's needed? Plus it's signed so it should flash with s-on.
Guys i have a question regarding the htc splash screen. I rooted twice today just to test a few things.
When i rooted for the first time i used windows 7 + hboot drivers from unrevoked3 site and flashed/rooted my device (stock rom (froyo)). Everything worked fine but when i run clockwork recovery mode and select the backup option i get something strange.
My device is backing up and it says it's done, when i select the reboot option my device get stuck at the splash screen and reboots, hangs, reboots, hangs, reboots etc. I need to pull the batteries off to get back in recovery mode. This time i select restore and select the backup i created before all this happend. Now it's passing the htc splash screen.
Because i thought i got problems with the windows drivers i decided to root with linux, so i installed the official ruu update over my rooted rom and root it under linux to make sure i am a bit saver.
Now when i do a backup and reboot again i get the same thing ? it hangs at the splash screen. Is the unrevoked recovery tool bugged (clockworkmod) ??? because when i restore with the backup i created it is passing the htc splash screen again.
I don't understand.
(Sorry for my bad English)
PS: I used this rom to root. http://forum.xda-developers.com/showthread.php?t=828519
As far as i know you need to root only once..i guess rooting again n again may hav messed wid phone..nt sure though..wait for a reply from someone who is experienced..i hav been using android since past 3 months only
Sent from my HTC Desire using Tapatalk
What you could try is this.
Use unrevoked again, but in unrevoked select a alternative recovery image.
Then load this image http://forum.xda-developers.com/showthread.php?t=839621
This is the amon-ra recovery. And for the record, you can root with unrevoked as many times as you want
Btw, you are sure that you waited long enough? If you restored a nandbackup, booting the phone can take 5-10 minutes
Oo..i thght it is similiar to jail breaking tht needs to be done onl once...lolzz
Sent from my HTC Desire using Tapatalk
lordvoldemort said:
As far as i know you need to root only once..i guess rooting again n again may hav messed wid phone
Click to expand...
Click to collapse
You really didnt read well didnt you ? it already happend the first time i rooted . Secondly, if i root and install a official ruu update over it everything will get wiped and cleaned....so there would be no problems when i decide to root.
Lennyz1988 said:
Btw, you are sure that you waited long enough? If you restored a nandbackup, booting the phone can take 5-10 minutes
Click to expand...
Click to collapse
Yeah i am sure....after backup the phone showed me the menu screen that i could select options such as rebooting the phone. When i reboot after backup it doesnt get passed the splash screen and reboots (and those steps gets repeated). If i don't use recover....my phone is dead
- Flash a stock ruu (rom)
- Then root again and use amon ra.
Lennyz1988 said:
- Flash a stock ruu (rom)
- Then root again and use amon ra.
Click to expand...
Click to collapse
Already did that 1 minute ago....testing it now
Edit: Whooohooo.....works ... backed up files and rebooted now and i don't get stucked at htc splash screen.
Clockworkmod will never get on my device again.
MichelN said:
Already did that 1 minute ago....testing it now
Edit: Whooohooo.....works ... backed up files and rebooted now and i don't get stucked at htc splash screen.
Clockworkmod will never get on my device again.
Click to expand...
Click to collapse
This seems to be a documented problem with Unrevoked. The first reboot after rooting and backing up Nandroid seems to hang the system for some, and restoring the Nandroid fixes it. After restoring the Nandroid (as you did) there should be no further problems. And since you did that, your problem should have been fixed. And since you restored to a rooted copy, why did you have to try again with Linux? Your problem was already fixed by the Nandroid Restore..
unrEVOked isn't the issue, Clockwork Mod is...just use AmonRA instead
EddyOS said:
unrEVOked isn't the issue, Clockwork Mod is...just use AmonRA instead
Click to expand...
Click to collapse
Thought the 1st Nandroid Restore fixes it..Does Clockwork mod still pose probs?
Clockwork Mod is the issue - flash AmonRA from the start and you won't have this issue (or I never have anyway, use AmonRA as you can partition SD cards in it)
I have the same issue can't pass htc screen and with 2 black lines.
I will flash RUU then root by unrEVOked. My question is how to flash/install AmonRA, do i have to flash using Clockwork will it override my recovery? Sorry guys noob question...
protuger said:
I have the same issue can't pass htc screen and with 2 black lines.
I will flash RUU then root by unrEVOked. My question is how to flash/install AmonRA, do i have to flash using Clockwork will it override my recovery? Sorry guys noob question...
Click to expand...
Click to collapse
I didn't have 2 black lines, mine rebooted after it couldnt pass HTC splash...i needed to remove battery or it keeps rebooting.
What i did with clockworkmod is restore (the backup you created before rebooting)....this should fix the problem. If this is not the case then i don't know because i never rooted before. You should ask a expert.
Anyway because i needed to restore anytime i posted this topic, people said i should use AmonRA. So to do this i installed the latest official ruu (posted by EddyOS) (to make sure everything is clean and good again). Then i used linux to make sure it is saver.
When you downloaded the unrevoked3 tool open it and don't plug you phone yet, go to options and select custom recovery. Now select the AmonRA (latest version i used) to flash with unrevoked3. Now plug in your phone and relax.
The only thing i am scared off is to flash hboot to go s-off.
Actually the cause of this problem was when i have tried the method for s-off...sad...
When i run unrEVOked it says this thing....
Device "/sbin/sh:getprop: not found
"is not supported at this time.
protuger said:
When i run unrEVOked it says this thing....
Device "/sbin/sh:getprop: not found
"is not supported at this time.
Click to expand...
Click to collapse
Try flashing true Linux. Download Ubuntu and this way you can boot your pc in linux.
Could you please give me a step by step guide on how to this unrEVOked if i have already booted up to linux? Im not familiar with the codes.
protuger said:
Could you please give me a step by step guide on how to this unrEVOked if i have already booted up to linux? Im not familiar with the codes.
Click to expand...
Click to collapse
You need root rights in ubuntu, use google to find it
thanks hope google stops my sleepless nights...
I'm having issues with a bootloop on the incredible after rooting using unrevoked 3 and making the mistake of choosing cyanogenmod as the recovery because I'm incredibly new at this. Now granted this isn't an issue, I have root access now and I'm able to assign superuser and the phone boots to what looks like the stock rom. However, I wanted to flash cyanogen 7 rc2 and it's giving me a lot of issues when I try to access the clockworkmod recovery screen. I downloaded the rommanager from the market and flashed the recovery to clockworkmod 3.0.0.8 as per a wiki online and tried to boot to recovery. from there it hits the HTC incredible screen, then flashes every 3 seconds rather than showing the green text it's supposed to show.
I still have S-on and unrevoked won't run properly again. Tried running the factory reset and it's another bootloop. I tried going through the steps for a "manual recovery file flash via cyanogen's wiki, but I'm running into errors.
Summary:
unrevoked 3.32 completed successfully even using the cyanogenmod rom as the recovery file.
Have root access, S-on, radio version ~.7.28
Can't flash back to stock due to bootloop
Can't factory reset due to bootloop
Can't get to clockworkmod recovery screen due to bootloop
phone able to boot to main screen with original
Ideal solution: get to clockworkmod recovery screen and install C7RC2
Any help appreciated!
Why do you think using ClockworkMod was a mistake? It's one of the better AOSP ROMs out there.
It sounds to me like you're probably going to have to download one of the stock RUUs to completely revert your phone to stock. You might have a corrupted recovery. You can't flash ClockworkMod or an alternative recovery via RomManager?
oh don't get me wrong, my huge problem here is that I can't get into recovery, and I didn't load clockworkmod initally, but it is (as rom manager says) my recovery image and it's just not working at all.
I tried going with a RUU and it wouldn't get into bootloader properly (just shows HTC on the screen till the the ruu times out) I'll try on a 32 bit machine when I get home. I was originally able to flash on that and unrevoked was giving me issues till I did a 32 bit xp attempt. Thanks for the response!
whoops, forgot to address your last point. Tried another version of clockwork and the RA_GNM 1.8.1 and neither stopped it from bootlooping rather than recovery screen.
HTCP2newb said:
I'm having issues with a bootloop on the incredible after rooting using unrevoked 3 and making the mistake of choosing cyanogenmod as the recovery because I'm incredibly new at this. Now granted this isn't an issue, I have root access now and I'm able to assign superuser and the phone boots to what looks like the stock rom. However, I wanted to flash cyanogen 7 rc2 and it's giving me a lot of issues when I try to access the clockworkmod recovery screen. I downloaded the rommanager from the market and flashed the recovery to clockworkmod 3.0.0.8 as per a wiki online and tried to boot to recovery. from there it hits the HTC incredible screen, then flashes every 3 seconds rather than showing the green text it's supposed to show.
I still have S-on and unrevoked won't run properly again. Tried running the factory reset and it's another bootloop. I tried going through the steps for a "manual recovery file flash via cyanogen's wiki, but I'm running into errors.
Summary:
unrevoked 3.32 completed successfully even using the cyanogenmod rom as the recovery file.
Have root access, S-on, radio version ~.7.28
Can't flash back to stock due to bootloop
Can't factory reset due to bootloop
Can't get to clockworkmod recovery screen due to bootloop
phone able to boot to main screen with original
Ideal solution: get to clockworkmod recovery screen and install C7RC2
Any help appreciated!
Click to expand...
Click to collapse
Did you try getting to recovery manually power off the phone while its off press power and volume down at the same time you should be in hboot use the volume button to scroll down boot into recovery.....
Sent from my Incredible using XDA App
I don't think unrevoked finish all The way because you should be s-off did you wait until it said "done"..... or did you stop when it said "this is a triumph"
Sent from my Incredible using XDA App
Okay, from a 32 bit system has resolved the flashing back to a stock rom, I will update as to whether I can get into recovery and will wait until I am told "triumphant" this time around.
Will post an update in a bit if this was all that was necessary to fix the issue. Thank you all to have posted so far, please post if you think I'm missing something else.
HTCP2newb said:
Okay, from a 32 bit system has resolved the flashing back to a stock rom, I will update as to whether I can get into recovery and will wait until I am told "triumphant" this time around.
Will post an update in a bit if this was all that was necessary to fix the issue. Thank you all to have posted so far, please post if you think I'm missing something else.
Click to expand...
Click to collapse
No you need to wait till it says done sorry you misunderstood me......let it go till it says done and it stops completely..... because the last thing it does is flash the recovery
Sent from my Incredible using XDA App
Did you try flashing a recovery through hboot?
Sent from my ADR6300 using XDA App
Okay, problem totally resolved. basically what happened was that there was an incomplete unrevoked process for whatever reason or another. I repaired by downloading the RUU off the HTC website and flashing back to stock. That generated an error of "your firmware is too new" which is available elsewhere in XDA, basically solved by going into hboot and factory resetting.
Once I had the factory reset completed, I used a 32 bit system to unrevoke the phone (after setting debugging to on in applications > developer settings >debugging on) then I was able to properly boot into recovery. I recommend Clockworkmod update to 3.0.0.8 in Rom manager, but I used 2.5 and didn't have much of an issue. I backed up and the wiped the memory and cache and installed 7r2 without an issue.
The phone is WAY more stable now (thanks to all the hard work at Cyanogen! Thank you also to everyone who posted here!) Pandora doesn't randomly cut songs in half and battery life seems to have improved. Whether that was verizon's crap or I went market-crazy and had waaaay too many apps syncing... I can't say.
Thank you everyone again!
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