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!
Related
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!!!!
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...
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.
I have been using a CM 7 RC0 nightly since it came out with no problems. I have been updating about once a week. I had a single nightly on for the last week and I hadn't updated it because everything was working fine. I had my phone charging at my desk and out of nowhere it rebooted. I wasn't using it when it rebooted. On reboot it got stuck on the HTC Incredible screen. It will not boot to recovery or boot to the OS. I can get to HBoot and flash various updates but the phone still won't load. What are my next steps? Is it bricked/broke?
Thank you in advance for your help.
Have you tried going into recovery from hboot?
Also, have you tried flashing the stock ROM from hboot?
I have. When I go to recovery from hboot it does the same thing. Hangs on the HTC Incredible screen.
Flashing the stock ROM went through the flashing process (showed a progress bar and went through the steps) and appeared to succeed but the phone still did the same thing: displayed the white HTC Incredible screen...indefinitely.
if the screen has anything on it, its not bricked. dont worry - there is a sticky on the forum that should be able to help you. just get into recovery (if you cant, then flash recovery file in hboot first) then flash a stock rom.
brick is when you damage the radio or cant even get anything on the screen. everything else (pretty much) can be solved.
ducttapekz said:
I have. When I go to recovery from hboot it does the same thing. Hangs on the HTC Incredible screen.
Flashing the stock ROM went through the flashing process (showed a progress bar and went through the steps) and appeared to succeed but the phone still did the same thing: displayed the white HTC Incredible screen...indefinitely.
Click to expand...
Click to collapse
try flashing hboot .92, then cwr 2.5.1.2 (i am sure that works for both slcd and amoled screens - not sure which screen you have), then flash the stock rom. if that does not work then it might be something hardware related that might require some other fix.
be careful about flashing new hboot. pls read the stickies at the top.
Okay, I can flash hboot .92, at least I think I can. It does some work and then prompts me to reboot. When I reboot it goes back to the white screen. How do I put Clockwork on there? Unrevoked won't connect to the phone and I can't get into recovery to flash anything. Is there instructions for installing Clockwork without Unrevoked?
Have you tried flashing an RUU?
Sent from my ADR6300 using XDA App
I downloaded an RUU and it was an exe. How do I flash an RUU from hboot? I cannot get to recovery.
RUU
You actually run the RUU via your PC, it's installed like any other program. Hook your DINC up via usb and follow the on screen prompts.
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