Related
Hi everyone I have a rooted Droid incredible, I don't believe I have an SLCD screen (b/c my clockwork mod recovery isn't black and white lines)
My phone is 2.2 rooted with unrevoked 3.22.
Everything was fine until I tried installing cyanogen mod 6.1 stable tonight.
I backed up with clockwork before I tried installing the zip but something went wrong, after installing the zip from clockwork mod all it said was "welcome to cyanogen mod" "install from zip complete" or something... I rebooted and hung up at white HTC incredible screen.
So I tried to recover from clockworkmod but it said MD5 mismatch so I attempted to do a factory reset, didn't work, I formatted system and such and that didn't work.
I searched for the MD5 solution and found this thread
http://forum.xda-developers.com/showthread.php?t=846280&highlight=mismatch with a solution of
adb shell
# cd /sdcard/clockworkmod/backup/2010-12-13.04.08.44
# rm nandroid.md5
# md5sum *img > nandroid.md5
after doing that my phone says
"checking md5 sums...
erasing boot before restore...
restoring boot image...
error while flashing boot image!"
it used to just say
"checking md5 sums...
md5 mismatch!"
so that fixed that... I think when I formatted I deleted a bunch of system files.
How can I use clockworkMod to flash the neccessary system files I need to get my phone back up and running?
Please help I can't return this phone I know its not a lost cause since I'm rooted and have the ability to run clockworkMod recovery still
Might be best to d/l the latest from shipped roms, flash it and start from scratch.
http://shipped-roms.com/index.php?category=android&model=Incredible
Problem Solved, (5 a.m. oh well)
I followed this thread.
incredible forum dot come /forum/htc-incredible-hacks/5723-how-get-back-complete-stock-s-off.html
1) Formatted my SD card to FAT 32, make sure you do that. SD cards usually come in regular FAT format. not 32
2) Turned S-On with unrevoked forever s-on.zip
3) Download the PB31IMG file he has listed, it is the current system img files and boot files and everything! Puts you back to complete stock
4) Ran unrevoked3 to get root back.
5) Ran cyanogenmod 6.1 stable zip from sd card from rom manager.
That's it, completely bricked phone back to right where I was trying to be 7 hours ago lol fully functioning and back in business (sorta).
(my cyanogen mod boot animation is in a continuous boot loop, lol wtf... i'm goin to bed ugh!)
Step 5 solution*
Running CyanogenMod 6.1 from SD card from Rom Manager app put me in a continuous boot animation loop.
Going into Hboot and running the zip from the sd root again re-installed it and it loaded properly. All is well.
Dont know if this is the correct forum to post but here it goes,
phone has MAGLDR 1.11
clockwork 1.1
originally flashed jdms 1.6 nand and was working perfectly
i tried to add the files from the updated clockwork 1.2 booted up clockwork as it normaly would, backed up my current system through through clockwork, i downloaded and put the updated version of jdms 1.7 beta and it would just bootloop, read that i needed a partition and i did it through clockwork, still bootlooped but it woped my sd card's contents with the partition, tried reformatting sd card added a new rom to start from scratch and it just satys at the htc logo or the android on rollerskates logo, tried putting the recovery image had back and it said it couldnt recognize md5 sum so it wouldnt do it. ive tried three bulds and all of them get stuck at the htc or cyanogen screen, i am doing all this from ubuntu, do i need to just start over and reflash through DAF? i dont have access to a windows machine so it will be a while, anybody have any suggestions? im phoneless at the moment, thanks in advance
Wipe cache after restore.
When bootloop, restart phone, start Clockwork mode - wipe cache.
Then restart phone.
Sent from my HD2 running Gingerbread
Tried that, didn't work still stuck on HTC quietly brilliant screen just flashed raidroid HD build
anyone has any advice?
Same Issue
I have the same issue of a bootloop... this seems to be the only place i could find with someone who is having a similar issue as i am.
Steps ive done:
Used Task29 w/radio 2.08.50.05 first.
Ive installed HSPL3
Ive also installed MAGLDR 1.13
Ive partitioned the SD to 13 gb FAT32 and 1 GB Ext3 --- both in primary
Ive flashed recovery 400
installed recovery files onto sd directly
I added the zipped CMYLXGOroms.stock.desire.HD.v1.1.5n.NAND.RMNET.NO-SQUASH-RAFPIGNA.1.7OC_CWM file directly to the SD card root.
then I install the CMYLXGOrom and it installs correctly, and then it boots up, and i see the android welcome screen for a second, and it starts its bootloop.
I've tried this with several differnt roms that are for the 1024 LEO but I get the same result each time.
Any help would be much appriciated!
Hi there. Thought I'd finally get around to rooting my Glacier, making progress but hit a roadblock.
ROM Manager app is stuck on "Error while downloading from server.", so I flashed clockwork recovery 3.0.2.4 with fastboot shell, ROM Manager still thinks recovery isn't installed and gives me the same download error when I try to manual override.
In recovery, attempting to start a backup gives me the error in the title, that is, "Error while backing up boot image!" and halts.
I could probably continue on to flashing cyanogenmod 7 and gapps, but I'm not comfortable doing that without a backup handy.
Android ver. 2.21, eng SPL (85.2007), 3.0.2.4 ClockworkMod recovery.
Can anyone help?
If it were me, I would download a fresh copy of CWM from here and flash it via fastboot. I bet then you'll be able to successfully make a Nandroid. If not, try formatting your SD card.
Downloaded that and re-flashed to no avail. Backed up SD card, formatted it, and for some reason it started working then.
Ah well, at least I have a backup. Thanks!
Had an odd error with the md5 checksums changing, too.. pushed them with adb, used md5sum, they were correct. Rebooted into recovery and they had changed again. Had to push and verify from recovery in order to install.
It ended up working though, so no complaints.
The easiest workaround I found to this problem was to boot into recovery mode using Quick Boot and follow these steps in the cwm boot screen: apply update from sdcard, install /sdcard/update.zip, reboot into recovery, backup and restore, and BACKUP. Worked for me and I didn't have to reformat my sd card, deleting everything on it.
Hi,
I would like to remind you that, CWM v3.x above are no longer support amend scripting which is used in Froyo ROM. Instead it used edify scripting which is used in Gingerbread ROM.
When you are on Froyo and try to use the latest CWM, it will not work, and you will encounter a problem just like you said.
My self, i use the CWM v.2.5.x, on my fascinate, and it can make backup successfully, although i never try the restore function yet.
I've flashed many roms and this has never happened to me before. I went to flash cm nightlies 73 and I get an E:Cant open /sdcard/cm_heroc_full-73.zip (bad) Installation aborted. I tried to download the rom again and flash it and it did the same thing again. I flashed to stock and then rooted my phone again and still got the same error. Ive looked online for a fix to this and couldn't come up with anything. Anybody know a fix for this? The recovery I used was clockworkmod 3.0.2.8, I thought it might have been the recovery so I went to an older clockwork recovery and the same thing happened.
ehusidic said:
I've flashed many roms and this has never happened to me before. I went to flash cm nightlies 73 and I get an E:Cant open /sdcard/cm_heroc_full-73.zip (bad) Installation aborted. I tried to download the rom again and flash it and it did the same thing again. I flashed to stock and then rooted my phone again and still got the same error. Ive looked online for a fix to this and couldn't come up with anything. Anybody know a fix for this? The recovery I used was clockworkmod 3.0.2.8, I thought it might have been the recovery so I went to an older clockwork recovery and the same thing happened.
Click to expand...
Click to collapse
I just D/l #73 and flashed ok for me,but I'm using darch's 1.7 amon Ra recovery so I don't know if it your recovery.Are you running Firerat's,If so you may have to resetit up from the instructions in the firerats thread.also if you are running firerats don't wipe your sd ext.,and make sure you have mtd partion setup with enuff room.Some one that knows more about it will speak up!
I know I had this happen to me a while back. My fix was that I had to download it from a computer, than transfer it over to my phone.
nm Saw you got it corrected over in the nightly thread. He formatted his SD card and it started working.
oohaylima said:
nm Saw you got it corrected over in the nightly thread. He formatted his SD card and it started working.
Click to expand...
Click to collapse
Yes sir everything is working great all I had to do was format my sdcard. I have no idea why the problem occurred but I guess that simple format fixed it. I copied most of the files that were on the sdcard and returned them after the flash and tested it again and its working still. Hopefully this information can help anyone who unfortunately will come across that problem.
I have looked and done searches for this problem with no matches. Phone stuck in bootloop after battery died. Pulled battery and went to recovery, tried to restore after wiping showed error message for data wipe
E:Can't mount /dev/block/mmcblk0p1.
(file exists)
When I tried to restore the attached results show up on the screen.
Any help with this situation would be greatly appreciated.
Try installing another rom. If that doesn't work, try flashing a new clockworkmod version.
Yes, I have tried three different roms and flashing a different recovery with the same type of results. The problem seems to be with data. Everything I try to do including wiping data ends up in an error message.
Hmm. Then you might try going back to stock from hboot and rerooting
Is sd full, or nearly full?
Sent from my ADR6300 using XDA Premium App
Id start with the newest version of clockworkmod and an new SD card.
Unrooted using the RUU with reverted HTC drivers. Process seemed to go fine but when it reboots it gets stuck in a bootloop with original droid bootscreen. I still have s-off and am wary of removing for fear of being stuck.
You could try flashing super vr wipe and do it that way.
sounds like the sdcard isn't mounting. i would back up the sdcard then reformat it and try again. or try another sdcard if you have one handy i usually keep a spare around just in case.
Look up five vibe fix ...
Sent from my ADR6300 using XDA App
This kind of thing frightens me to death about flashing a new ROM. I'm dying to get that 2.3 ROM that just posed but I'm afraid of bootloops, whitescreens and error messages etc.
It's really not that bad, as long as you dont touch it while its doing it's thing it works great. I just installed Ovo Community Mod Test RC5 and it is SICK!
You need to update your hboot to .92 first though.
kzoodroid said:
sounds like the sdcard isn't mounting. i would back up the sdcard then reformat it and try again. or try another sdcard if you have one handy i usually keep a spare around just in case.
Click to expand...
Click to collapse
Sounds like something isn't mounting, but I'm not sure if it's the SDcard. Those directories are on eMMC, aren't they? Not sure if this would help, but I'd check to see if it's mounted as read/write. Looks like it's read only.
RMarkwald said:
Dude, use Doug Piston's ROM Flashing Tutorial, here. It's easy.
After the screen shot showing Wiping Cache, also do:
Mounts and Storage - format /system, format /data, format /boot
Advanced - Wipe Dalvik
Then resume at the Install zip from SD Card screen shot...
Click to expand...
Click to collapse
I followed those directions and flashed the new 2.3.4 without any issues. I was originally on 2.2 rooted with unrevoked3
Much bigger problem. Now that I have run the RUU I no longer have clockwork recovery and cannot flash anything. When I reboot I get the droid bootscreen in bootloop. Frustration!
Have you tried just booting with the sd card removed? Issues with the sd card can stop it from booting
Also if you flashed the RUU your unrooted therefore have no cm recovery. You will need to root again for that.
Yes recovery was gone, attempted to flash clockwork again. When booting into recovery strange bar appeared and screen went black. After several tries with same results flashed Amon ra style recovery and now have this recovery but am still getting bootloops when flashing and having same E: can't mount /dev/block/mmcblk0p1 (file exisits) error messages. Confident there is a solution but have no idea how to get there. Determined though! Any help is greatly appreciated.
It is saying read only file system . E:Error in CACHE:recovery/log
This is at the bottom of the recovery screen.
Ok, I've said this a few times on here, but I don't see were you've mentioned that you've tried it. Remove your SD card and see if it boots!