Related
I was running calkulin's rom on my evo but I decided to give cyanogen a run for its money. I was successful in installing cyanogen 6.1, and when i went to go install the addons, they didn't install properly for whatever reason. I went back into recovery mode and did a wipe of the device and went to install a fresh install of culkulin .. but instead of selecting the item "install zip from sd card" i selected "install update.zip" even though I didn't have an update.zip on my device.
After it tried to do that, it asked me if i wanted to reboot, i selected yes, and now i can't get into recovery mode. I can get into fastboot, but when i try and select recovery, it goes to the white HTC EVO 4G screen, then it goes to the screen with the phone, a red triangle with the exclamation point. If i press vol up + power, it brings up the menu to install from update.zip, wipe cache, wipe data, and reboot. I've selected all the options, i'm LOST.
i'm on a 2010 macbook pro .. I have windows 7 installed via VMware but it doesn't want to recognize my phone.
I was able to install adb on my mac, but it still can't recognize the phone. Any help is much appreciated, i don't want a $300 paper weight. Thanks!
Somehow your recovery might have been overwritten. Download a recovery image, go into fastboot and run the following command:
fastboot flash recovery recovery.img
Where recovery.img equals the filename of the recovery image.
Amon_RA has a PC36IMG.zip of his recovery so you don't have to use command prompt at all, just go to bootloader and flash.
http://forum.xda-developers.com/showthread.php?t=705026
i don't have a way to access the commands via terminal or dos to my phone. my computer can't recognize my device .. i'd prefer to do this via OSX because W7 via vmware isn't stable on my machine.
where can i download a custom image .. i may be able to run it via unrevoked, but when i run unrevoked, it gives me the error Device "- exec'/system/bin/sh' failed: No such file or directory (2) -" is not supported at this time.
Sounds like recovery is corrupted, download pc36000.img fkr amon_ra 2.2.1, put it into your root folder of sd card and give it go from fastboot.
I am typing name of recovery from my memory, so it can be wrong.
I read other posts about typing fastboot recovery installation commands, but you have said your adb is not working, so give this a try.
Sent from my PC36100 using XDA App
I'm not sure how to get adb running on the mac but it should be fairly easy. I'd read up on getting your phone connected with adb/fastboot then get the custom recovery img file.
Then you'll do:
fastboot flash recovery recovery.img
(I'm not sure if amon has a readily available image file but you can get the img file for clockworkmod for the evo here: http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
Just click the evo link, copy it to your fastboot folder and rename it to recovery.img just to make it easier.
Edit, if you have an sdcard apater (or maybe put the card in a digital camera or something so you can access it) you can put this PC36IMG.zip file on it: http://www.mediafire.com/file/s3vsgfwcz5po8hs/PC36IMG.zip
then boot your phone with boot loader, it'll scan the file and hit volume up to apply the update.
Had issue yesterday, my phone would boot directly to fastboot. My issue was a corrupted SD card. I bought a new one and it did the same thing but was able to reformat and it works! Never had this issue until i start pushing dalvich cache to SD. Anyhow check your SD card, try another on see if you can boot a zip from fast boot.
i tried that and it works perfectly! I was able to get a custom rom loaded onto my device and boot up, then i re-ran unrevoked so i could get that custom recovery so i could reload one of my past back ups.
Worked like a charm!
dizzle247 said:
i tried that and it works perfectly! I was able to get a custom rom loaded onto my device and boot up, then i re-ran unrevoked so i could get that custom recovery so i could reload one of my past back ups.
Worked like a charm!
Click to expand...
Click to collapse
Glad to hear. Disaster averted
dizzle247 said:
i tried that and it works perfectly! I was able to get a custom rom loaded onto my device and boot up, then i re-ran unrevoked so i could get that custom recovery so i could reload one of my past back ups.
Worked like a charm!
Click to expand...
Click to collapse
He never said what worked. I am having the same issue and would like to know what worked.
Im actually stuck on the htc evo screen. I can access fastboot as well. Where do i go from there.
I'm having almost the exact same problem as dizzle247. I've tried to flash PC36.img and tried using a new recovery.img but it keeps on sending back to the beginning. I don't know if the fact that my phone is set to S-on has anything to do with it but if I try to switch it off it fails.
Please help
The same thing happened with my phone. How did you end up solving the problem?
If you're in that situation, gona have to run an RUU.
Any solution yet?
How would you run RUU when the phone doesn't boot?
I am having same issue.
I can access fastboot.
I can load a pc36img.zip from my root SD.
I can not access recovery.
Re-flashed amon multiple times, no change.
If I try to go into recovery, it just shows white evo 4g screen.
If I try to regular boot, just shows whit evo 4g screen.
Any thoughts?
GrooGrux said:
Any solution yet?
How would you run RUU when the phone doesn't boot?
I am having same issue.
I can access fastboot.
I can load a pc36img.zip from my root SD.
I can not access recovery.
Re-flashed amon multiple times, no change.
If I try to go into recovery, it just shows white evo 4g screen.
If I try to regular boot, just shows whit evo 4g screen.
Any thoughts?
Click to expand...
Click to collapse
Unfortunately, most people that had this problem were never able to get out of it. It happened mainly on AOSP based roms. I'm typing in past tense because it was a fairly common problem a few months ago, haven't heard much about it since.
You can try running an RUU. If it doesn't work and you have insurance, you may need to take it in and eat the $100 deductible.
Some people were flashing radios through hboot and pulling the battery until the device wouldn't even turn on, then taking it in.
However you want to handle it is up to you. I wish that someone had found a solution, but I'd try everything you can find before taking it in. Every phone is different, something may work for yours.
Sent from my PC36100 using Tapatalk
hmmm, can any1 shed some light as to WHAT worked? other ppl have same problem, it would help if they stated the actual solution lol.
tooill said:
hmmm, can any1 shed some light as to WHAT worked? other ppl have same problem, it would help if they stated the actual solution lol.
Click to expand...
Click to collapse
There is no solution most of the people that have had this happen got a replacement
Sent from my PC36100 using XDA App
ugh >.<, i wanna fix mines and sell it, i cant replace it.. i bought it and had it flashed for boost, but now it has that problem so idk what to do with it..
Same problem need help evo4g
GrooGrux said:
Any solution yet?
How would you run RUU when the phone doesn't boot?
I am having same issue.
I can access fastboot.
I can load a pc36img.zip from my root SD.
I can not access recovery.
Re-flashed amon multiple times, no change.
If I try to go into recovery, it just shows white evo 4g screen.
If I try to regular boot, just shows whit evo 4g screen.
Any thoughts?
Click to expand...
Click to collapse
I'm having the same issue need some help
Hi,
I hope this isn't a repeat, but I've searched here and Google to no avail. It may be I'm not searching the right things, because I'm not quite sure how to succinctly describe this problem.
I've rooted my DInc, with S-Off enabled. I'm running CyanogenMod 6.1 now, installed from ROM Manager, which is no version 3.0.0.7. I've got ClockworkMod 2.5.1.2 installed as well. When I first rooted my phone, etc. about a month ago, I made a nandroid backup, so I figure its time to make another one. Open ROM Manager, go to Make a New Backup, choose a file name, it reboots into Fastboot. If I then select "Reboot" by pressing the Power button, the phone boots back to Cyanogen and there is no (new) backup file in the clockworkmod/backup directory, where I expect it.
If I select "Bootloader" from the Fastboot menu, it takes me to the HBoot menu, with the options "Fastboot", "Recovery", etc. Then, an error message appears very quickly, about missing PB31IMG.zip files. I'm not sure about the exact text of the message since it disappears so quickly, but I've searched around and it seems to be because that file is missing from the root of my sd card (I checked on Windows, its not because the file is renamed to .zip.zip or something). Solutions such as formatting the sd card to FAT32 (it is, according to Windows) and reflashing ClockworkMod from ROM Manager do not help.
After the error message disappears, I am able to select "Recovery" from the HBoot menu, and the screen flashes the white with black text "HTC Incredible" startup screen before dropping me back into the Fastboot menu. At this point, I usually just give up and reboot and keep using the phone as normal.
Does anyone have any idea where the problem lies? Can someone link me to the proper PB31IMG.zip file for my phone/ROM/radio?
Radio: 2.15.00.07.28
HBOOT - 0.92.0000
Thanks!
Have you tried reflashing ClockworkMod from within ROM Manager?
Personally, I've never had this happen, sorry if reflashing doesn't help
dmbhaggis said:
Have you tried reflashing ClockworkMod from within ROM Manager?
Personally, I've never had this happen, sorry if reflashing doesn't help
Click to expand...
Click to collapse
Yeah, that's how I was reflashing ClockworkMod. Thanks anyways.
Try going into ROM Manager go all the way to the bottom to All clockworkmod recoveries and try flashing a different version of CWM Recovery...
jackbtha1 said:
Try going into ROM Manager go all the way to the bottom to All clockworkmod recoveries and try flashing a different version of CWM Recovery...
Click to expand...
Click to collapse
Flashing back to 2.5.1.1 appears to have worked...does anyone have any idea why 2.5.1.2 is apparently broken (probably just on my device)?
Thanks!
I've seen other people reporting problems with 2.5.1.1 & 2.5.1.2 on amoled devices. They've suggested going back to 2.5.0.5.
________________________________
Unrevoked forever
SkyRaider Sense 3.5
Radio 2.15.00.09.01
my bad didnt see last part
darthbith said:
Hi,
I hope this isn't a repeat, but I've searched here and Google to no avail. It may be I'm not searching the right things, because I'm not quite sure how to succinctly describe this problem.
I've rooted my DInc, with S-Off enabled. I'm running CyanogenMod 6.1 now, installed from ROM Manager, which is no version 3.0.0.7. I've got ClockworkMod 2.5.1.2 installed as well. When I first rooted my phone, etc. about a month ago, I made a nandroid backup, so I figure its time to make another one. Open ROM Manager, go to Make a New Backup, choose a file name, it reboots into Fastboot. If I then select "Reboot" by pressing the Power button, the phone boots back to Cyanogen and there is no (new) backup file in the clockworkmod/backup directory, where I expect it.
If I select "Bootloader" from the Fastboot menu, it takes me to the HBoot menu, with the options "Fastboot", "Recovery", etc. Then, an error message appears very quickly, about missing PB31IMG.zip files. I'm not sure about the exact text of the message since it disappears so quickly, but I've searched around and it seems to be because that file is missing from the root of my sd card (I checked on Windows, its not because the file is renamed to .zip.zip or something). Solutions such as formatting the sd card to FAT32 (it is, according to Windows) and reflashing ClockworkMod from ROM Manager do not help.
After the error message disappears, I am able to select "Recovery" from the HBoot menu, and the screen flashes the white with black text "HTC Incredible" startup screen before dropping me back into the Fastboot menu. At this point, I usually just give up and reboot and keep using the phone as normal.
Does anyone have any idea where the problem lies? Can someone link me to the proper PB31IMG.zip file for my phone/ROM/radio?
Radio: 2.15.00.07.28
HBOOT - 0.92.0000
Thanks!
Click to expand...
Click to collapse
I have the exact same problem, except my hboot reports as 0.78 I believe. Either way, the hboot menu is as far as I can get. Any other selection causes continual reboots. This started happening after a spontaneous reboot while driving down the road. I wasn't even using the phone. I do have the latest Clockwork on it, but it really doesn't matter because I can't get to the Clockwork menu anyway. Just the fastboot menu.
It says that USB is enabled in the hboot menu, but with it plugged into my PC, it won't show up in Windows. It's obviously not far enough into the boot cycle to do that.
Any suggestions would be awesome. I see about a dozen other topics started complaining about similar issues. If I leave it sit on the hboot menu, it'll sit there forever and is stable, so I don't believe it's a phone issues. It's almost like, if it were a PC, the boot sector is messed up and it needs an fdisk /mbr. I understand, that doesn't work, I'm just pointing out that I believe the behavior to be the same.
Thanks to anyone that can help!
I guess that, with no way to get into Clockwork and no way to replace Clockwork, I'm kind of stuck. Replacing Clockwork was an idea, but I'm not sure how to do that since hboot is all that's available and I can't choose any options without it rebooting continually. Is there a way to just plug the phone in and reflash Clockwork from my laptop with a Windows app on the laptop?
hackules said:
I guess that, with no way to get into Clockwork and no way to replace Clockwork, I'm kind of stuck. Replacing Clockwork was an idea, but I'm not sure how to do that since hboot is all that's available and I can't choose any options without it rebooting continually. Is there a way to just plug the phone in and reflash Clockwork from my laptop with a Windows app on the laptop?
Click to expand...
Click to collapse
Do you have Rom Manager installed on your phone? If you do you can always use the last option to install a different version of Clockwork. Give that a try...
I can't get past the "hold down and power" menu. That works fine, but anything I pick reboots the phone. I can't get into the OS at all because it just continually power cycles after I choose from the boot menu. I re-flashed Clockwork and no luck and I've re-flashed the entire phone to stock, same thing. It IS stable and the recovery menu you though. I can jump around in the menu, turn USB on and off, etc, just not boot into anything. It's literally like a computer that needs fdisk /mbr as all of the data seems to be where it should be.
I would try to flash any custom and see if that gets the phone to boot normally.
I took the stock build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000 and zipped it as PB31IMG.zip and when it boots, it'll take the images and flash them. It flashes all of the images in the zip and it takes a little bit to do that. Then it goes back to the menu and I restart it and it goes into the cycle again...
Hmmm. I would have used the unrooting guide to go back to stock just to get the phone back up and running and then unroot it again. If you do go that route DO NOT apply the 7.28 radio again because you will brick you phone being that you already have that radio flashed on your phone. What custom ROM or Kernel were you running before all this happened? I would try flashing that again but clear the data and cache first and see if that gets the phone up again.
I'm currently running the latest Senseless Revolution ROM and did upgrade to the latest ROM manager, but haven't flashed anything yet so no problems........yet!
Should I downgrade to CW 2.5.1.2 anyways since it was a bit sluggish when checking for MDsum?
I've read about some people having crazy problems and others actually not reporting anything bad......so what is the verdict? I'm trying to prepare myself first rather than finding out when my phone is stuck
I seem to be having some of the same problems. I upgraded ClockworkMod to 3.0.0.5 and was able to successfully boot into recovery. I installed CM 7 nightly, then ended up restoring to a backup of CM 6.1.
Now I can't access recovery, when I try I get stuck at the white droid incredible screen. My phone can still boot up so I tried downgrading ClockworkMod to 2.5.1.4, but it says an error occurred while flashing the recovery.
any ideas?
nate23 said:
I seem to be having some of the same problems. I upgraded ClockworkMod to 3.0.0.5 and was able to successfully boot into recovery. I installed CM 7 nightly, then ended up restoring to a backup of CM 6.1.
Now I can't access recovery, when I try I get stuck at the white droid incredible screen. My phone can still boot up so I tried downgrading ClockworkMod to 2.5.1.4, but it says an error occurred while flashing the recovery.
any ideas?
Click to expand...
Click to collapse
Are you renaming recovery to PB31IMG.ZIP and updating through hboot?
Sent from my ADR6300 using XDA App
pete_kowalski83 said:
Are you renaming recovery to PB31IMG.ZIP and updating through hboot?
Click to expand...
Click to collapse
thanks, that fixed it!
Hey,
I was wondering if anyone could help me out with this issue I have. I have a rooted Evo, with my latest ROM being Fresh Evo 4.0.0.4 Beta by flipzmode. I was having some issues with the rom, so I was attempting to reflash the rom, however its beta 3 (one update older) version, first. I went through ROM Manager and did a complete backup, then chose install from SD Card and checked the boxes for Wipe Dalvik cache and the other check for wipe cache / data (i forget exactly what it says). ROM manager took over from there, rebooting into recovery and installing the rom, atleast as i thought it as doing. Once it was said and done, I now am at my problem area. It will not boot past the white htc EVO 4G screen. I've given it anywhere from 20-40 minutes to load. I've tried pulling the battery as well. I've even attempted to get into recovery by going into my hboot bootloader. However there, i have ANOTHER problem...I can't pick any of the available options. Its as if my volume buttons just don't work. When I have my SD card loaded and I go into hboot, it does some kinda search which yields five results of No Image Found! it then returns to the main menu where again, I can't scroll up or down the list. It says s-off so I assume that means I'm still rooted. I'm not an expert by any means, and overall I'd say I'm a noob to this stuff, but I am trying to figure it all out. If anyone can help me out with what to do to get my phone running again, I'd appreciate it greatly.
Thanks!
Hmmmm, that's odd. You can try putting a PC36IMG of the RUU on the root of your SD card. If you used unrevoked, you'll stay s-off, so all you'll need to do is reflash recovery to flash a rom or restore from a backup. However, you need to use your volume buttons to agree to the flash in the bootloader. In the odd case that it just won't navigate the menu, but the volume buttons are fine, it may still receive the confirmation from the button that you want to flash the PC36IMG.
If that's the case , download this file: http://goo-inside.me/supersonic/sto...15.00.11.19_NV_1.90_release_161482_signed.zip and rename it to PC36IMG, don't add a zip to the end because it's already there. Put it on the root of your SD card and boot into the bootloader, when it asks you to update, *try* to agree with the volume up button. If it works, hopefully that'll fix your problem.
It's not the greatest fix, and the chance of it working isn't all that high, but it's all I've got.
Oh, and obviously your volume buttons are fine if you can get into the bootloader, unless a button is stuck.
(from... Evo/MIUI/Tapatalk)
And don't use ROM Manager.....
Thanks plainjane,
Just a couple more quick details before I try to do what you said, I'm not sure which root method was used for me. My cousin did it for me and with my phone mia, I have no way to find out. Does that effect anything? Also, i'm pretty sure i've used ClockWorkMod recovery, as i remember flashing it through ROM manager a few days ago. I've realized that the volume buttons do work, but only when to accept the update for the pc36img..I read about that before so I tried putting one that I believe was for ClockWorkMod recovery on my sd card, but I wasnt sure if that was the right pc36img file i need. So I can replace that with the one you have linked me with. Will running that cause any problems with the addtional details? I just don't want to end up permanently bricking my phone, so I'd rather cover all my bases.
Thanks again!
I would do 2 things: 1 flash a new recovery, specifically amon_RA and then I would flash a rooted ODEXED stock rom.
Click on the word "amon_RA" above and download the PC36IMG.zip file and place it on the root of your SD card (not in any folder). Make sure there is NO OTHER FILE with that same name on the root of your card. Turn off your device and then boot it to the bootloader screen. After a pause, the file should be autodetected and you should be prompted to install. follow the easy instructions to install. Afterwards, you should be able to go into recovery and flash a rom. Download the rooted stock rom by clicking on "rooted ODEXED stock rom" above. Afterwards, put it on your SD card and flash it from recovery. Once you've successfully flashed a rom and if you're set on re-using ClockWorkMod recovery, you can always download the ROM Manager app and have it install ClockWorkMod recovery for you, but I recommend you stay with amon_RA.
!
plainjane said:
If that's the case , download this file and rename it to PC36IMG, don't add a zip to the end because it's already there. Put it on the root of your SD card and boot into the bootloader, when it asks you to update, *try* to agree with the volume up button. If it works, hopefully that'll fix your problem.
Click to expand...
Click to collapse
Thank you, thank you, thank you plainjane! I decided to just go for it and try your method, it took care of my phone not being able to boot-up. I'm now at what seems like a stock rom.
dougjamal said:
I would do 2 things: 1 flash a new recovery, specifically amon_RA and then I would flash a rooted ODEXED stock rom.
Click to expand...
Click to collapse
Thanks for your suggestion dougjamal, I actually attempted your method first, but I still wasn't able to select the recovery option from the hboot bootloader main screen after running the PC36IMG, so I couldnt flash the rom.
So, I still have a couple of the same problems. I still can't choose the recovery option from the bootloader menu, I've tried multiple times to use a PC36IMG for ClockWorkMod recovery and Amon_ra. Also, while using the actual phone, my power button seems to not work. It doesnt turn of the screen, nor does longpressing it allow me to shut off the phone. If it helps to diagnose the problem, since i'm pretty sure up until today my power button still worked, whenever I pull my battery and put it back in, the phone boots automatically without me pressing the power button. Anyone have any suggestions?
Otherwise, is there anyway for me to just go back to complete stock again and attempt rooting the phone again, and starting completely from scratch?
Thanks again for everyone's help!
Boot into the bootloader screen and see if you're still rooted (S-OFF). If it displays S-ON then you will not be able to make changes to your device.
posting & replying via the XDA Premium app.
dougjamal said:
Boot into the bootloader screen and see if you're still rooted (S-OFF). If it displays S-ON then you will not be able to make changes to your device.
Click to expand...
Click to collapse
Yes, it still says S-OFF. I don't understand why I can't scroll through the menu nor turn off my screen though. Even when it times out, I can't turn the display back on. I have to plug in a charger.
I have posted a question about this a wile backwhen it was a white loading screen and someone told me to download the P----.ZIP file and I did and fixed my problem.
Now, this problem has reoccurred and I want to know how to get rid of it.
My HTC Droid Incredible was rooted and when the battery dies, and I charge it, and then start the phone up again, it just loads the screen again (using SKYRAIDER) and it doesn't go past that. I have once again, wiped the phone, installed the P-----.ZIP file(forgot the exact name), and then te phone worked. Once I rooted the phone again use revoked and installed the sky raider theme again, it just loads the loading screen. This always happens whenever my phone dies. Help?
we sort of need more info to work with here.
cvbcbcmv said:
yeah. Please tell us, EXACTLY what you do to flash it. One little thing could do the problem, all details please, it's all important.
Click to expand...
Click to collapse
yep, same, like did you use rom manager, did you do a nandroid backup, what kernal did you flash? did you try to flash a radio?
is said rom made for your phone?
Sorry if my details wasn't enough. Before my phone had died, it had the latest 4.2 Sky raider Rom installed. When the phone had died, this is what I did. I went into the clockwork recovery and wiped the phone completely, then I installed that PB31IMG.zip file to get the phone to unroot it. When that was finished, the phone was fine, everything bak to the way as it was manufactured, not rooted. Then I rooted it with unrevoked and went into recovery and installed the skyraider rom from a zip. Once that was finished, the phone would load up the loading screen and just continue it.. if there's anymore information you need, let me know. Thanks.
Guahan said:
Sorry if my details wasn't enough. Before my phone had died, it had the latest 4.2 Sky raider Rom installed. When the phone had died, this is what I did. I went into the clockwork recovery and wiped the phone completely, then I installed that PB31IMG.zip file to get the phone to unroot it. When that was finished, the phone was fine, everything bak to the way as it was manufactured, not rooted. Then I rooted it with unrevoked and went into recovery and installed the skyraider rom from a zip. Once that was finished, the phone would load up the loading screen and just continue it.. if there's anymore information you need, let me know. Thanks.
Click to expand...
Click to collapse
most roms should already be rooted, that may be what you did wrong
my suggestion, go back to stock, if you made a backup, then use the unrevoked method. then go into recovery, wipe it, reset, that good stuff, then install zip from sd card, then leave it be.
all you pretty much said in that post, sorry if i mis-read it, was that you instaled skyraider after you went to stock, did you load it via rom manager or booted it manually with clockwork mod? and is your phone SLCD or AMOLED. if it is AMOLED you eed to use cwm 3.0.0.7 if SLCD, then use 3.0.0.8
@Kiboe - that is exactly what I did until I got the loading screen. How do I check if my phone is SLCD or AMOLED? How to check it with my problem?
@cvbcbcmv - I installed Skyraider through the CWM, installed it using .zip.
Guahan said:
@Kiboe - that is exactly what I did until I got the loading screen. How do I check if my phone is SLCD or AMOLED? How to check it with my problem?
Click to expand...
Click to collapse
under your phone battery, there should be a SKU number, if the number ends in "VW3" then it's SLCD
if it ends in "VW2" then it's AMOLED
so, AMOLED would be "ADR6300VW2"
and SLCD would be "ADR6300VW3"
I'm only seeing ADR6300VW, not 2 or 3.
Guahan said:
I'm only seeing ADR6300VW, not 2 or 3.
Click to expand...
Click to collapse
It may be AMOLED then, mine is just ADR6300VW. My guess is an SLCD would be ADR6300VW2.
And in a sense ROM hardware version is 002 for AMOLED and 003 for SLCD, if you're on an Incredible ROM anyway, a lot of the Gingersense ROMS based on other phones report my AMOLED as 003. It is not, as I got it on Launch day, and it was manufactured April 2, 2010.
Currently having this problem as well...
I've tried flashing a couple of ROMs--specifically, Synergy RLS1 and Optimized Shift 2.4.1. I tried both the original download and the mirror download for Synergy. I'm flashing through ROM Manager 4.3.0.1 and wiping data, cache, and dalvik. Each time, the ROM will seem to install in CWM, but will be stuck at the white HTC Incredible screen when trying to boot. I know it may stay there for a while when flashing new ROMs, but it will sit there for over five minutes, at which point I just take out the battery and try again. I still get stuck at the same screen, so I just go into recovery and restore my last backup, which works. So I'm not bricked; I can return to a backup, but can't flash a new ROM. What should I try? I've flashed plenty of times before successfully, always the same way, never had this problem unless the download was corrupted.
I'd recommend not using rom manager. Try manually flashing in recovery and see if that doesn't help. I'm also assuming you're on the .92 hboot and 3.x.x.x recovery?
k_nivesout said:
I'd recommend not using rom manager. Try manually flashing in recovery and see if that doesn't help. I'm also assuming you're on the .92 hboot and 3.x.x.x recovery?
Click to expand...
Click to collapse
Worked--thanks! Odd I'd never had a problem with ROM Manager until now.
Hello all,
I'm sorry if this is the wrong place to post, but I thought I'd give it a try.
I own a Desire myself and the rooting / flashing a new ROM process was pretty easy so I thought I can help a friend out and put a custom ROM on his new Motorola Defy. Turns out I sucked at it. *ahem*
Right, the problem is as follows:
I got the brand new device, used SuperOneClick to root it, tried ROM Manager to install ClockworkMod CWM and it said Defy isnt supported in ROM Manager. So I google'd and it came up with this [german] (not allowed to post links), which basically gave me CWM.zip with an apk in it, which installed "System Recovery" and gave me the option to "Install System Recovery" and Reboot into Recovery - successfully bootet into CWM 2.5.1.8 , alright.
I did a nandroid backup and then wiped everything, selected the ROM on the sdcard to install MIUI 1.9.9 ROM, which worked fine. After it finished installing, I chose reboot system now.
Now what happens is:
I try to boot normally: I Only get the Motorola logo on screen and nothing ever happens
I boot into recovery like I used to know (Power + VolDown), I get a screen with a yellow exclamation mark and the android robot on it. Figured out that both volume keys take me to Android System Recovery Utility. I wiped everything again, that didn't help. I tried giving it the CWM.zip as an update.zip but it refuses that because it's apparently not properly signed. I can't do anything else in there. It also gives me a couple of errors "E: Can't moint CACHE:recovery/command" (/caller, /log)
Please, can anybody help me out? It seems I can't boot any ROM from it right now, nor do I know how to get CWM back in to at least even restore the nandroid backup (which I still have).
I would love to, at the end of the day, have a rooted device with CWM running and MIUI 1.9.9. If that doesn't work, at least can I restore the CWM backup somehow to have to stock ROM running?
I would really appreciate any help very much and realize I may be in over my head, it just seemed too easy on the Desire I previously used. Thanks a lot!