I have a G2 rooted with the Desire Z HBOOT and clockworkmod recovery 5.0.2.7 and everything was working perfectly when randomly out of nowhere my backups no longer restored properly. It would either say md5 sum mismatch or it would restore and get stuck at HTC bootscreen. This happens with any rom i flash. I've tried wiping/factory reset/formatting sdcard/flashing older cwm/ and even removing and creating new md5 images. NOTHING works. This is important to me because I ususally flash back and forth between different roms and I like being able to back them up.
this happens whether i use ROM manager (4.8.0.2) to do the backup and/or restore; or if i use cwm recovery console to do the backup and/or restore. sometimes with ROM manager i get an error that says either it can't process the request or it says can't find SD card marker or something like that.
I recommend using an older version of CWM, like 2.xxx
i have tried using all the versions of the recovery. none work.
okay, randomly some of the backups will be good and some will be broken. I don't know why.
i feel like nobody is going to respond to my problem just because i am a fairly new member. I really can't stand this problem because i test different roms so often and if i dislike them i like being able to go back to my old one with all of my data still there and not having to start over. its been driving me nuts for all this time. I have tried everything and nothing works.
i had this same problem on my droid incredible. my fix was a fresh wipe (factory reset, system, boot, and dalvik cache) and a fresh install of rom manager from which i reflashed my recovery. (the option that says Flash Clockworkmod Recovery) my install was messed up initally. maybe yours is similar.
Sent from my ADR6300 using xda premium
what do you mean when you say boot? how do you wipe that?
SnapplerX said:
what do you mean when you say boot?
Click to expand...
Click to collapse
See here: http://www.addictivetips.com/mobile...plained-boot-system-recovery-data-cache-misc/.
SnapplerX said:
what do you mean when you say boot? how do you wipe that?
Click to expand...
Click to collapse
I also have the Vision and I would highly recommend you try 4EXT Recovery instead of ClockworkMod. It's based on CWM, but with more options and great support. See my signature for the thread link.
Sent from my HTC Vision using XDA App
in clickwork recovery select 'mounts/storage' then select 'format boot' same for system. you will only want to do this when youve already got your rom zip file on your phone. the inc might have a different option list, cause that was automatic on my og droid
Sent from my ADR6300 using xda premium
I had the same problem with clockwork, I just switched to Amon RA recovery! You will lose your clockwork backups, but Amon is so much nore "hassle free"
is Amon RA recovery supported in ROM Manager?
im going to try 4EXT and Amon Ra recovery ill see which works best for me
okay so apparently there is no amon ra for the g2/desire z. I tried ext4 recovery and i have the same problem. it is an md5 sum mismatch every time i create a back up the md5 sum is never a correct match no matter the recovery i use. I'm starting to think it might just be my sd card.
If anyone is still interested, I ended up buying a new sdcard and it works perfectly now. I am using 4EXT recovery and I recommend it to everyone.
Related
I know this problem is probably in other threads somewhere, but I've been looking and I haven't been able to find this same situation in any of them, sorry for being such a noob.
I was running aloysius v12, used clockwork mod to do a nandroid backup. I tried flashing a purehero ROM, and got stuck on the white startup (skateboard) screen for about 30 minutes. I pulled the battery, booted into recovery, and tried restoring the nandroid file, but every time I try it says "Error while flashing boot image!" and won't continue.
I have it plugged in, so it isn't low on battery. I still had 4 gb free on my sd card, so it's not low on memory. When I try to look at the files on my sd card on my computer, it won't recognize my phone at all. I also tried restoring my original stock rooted backup, but had the same problem. I'm not really sure where to go next, what do I do?
I don't use clockwork but in amon ra you can't put spaces in the file name if you rename it. If you can't access your sd card on your computer, maybe your sd card is corrupt.
I STRONGLY recommend you get rid of clockwork and install amon ra. I've read horror stories of bricked phones using clockwork. I do not know if clockwork recoveries will boot in amon ra, so it would probably be best to install amon and boot a fresh rom.
Sent from my Froyo Eris using XDA App
...you did turn enable usb when you plugged your phone into the computer right?
Sent from my Froyo Eris using XDA App
How do I do that from the recovery screen? That's all i can get to right now.
And i'm still really new to this whole rom/rooting thing, sorry to be so clueless, but once i can open my sd card on the computer, then i download a new rom to it and flash it right? do i need to get amon ra before i flash a new rom? is that even possible? maybe i shouldn't have done all this without completely understanding it haha
Edit:
I found how to mount USB mass storage device. Now do I just need to follow the instructions on installing amon ra, or will they work while I'm in recovery?
You should be able to select usb ms toggle from recovery (at least you can in amon ra) when the phone is connected to the computer and move files to your sd card. If not, power the phone off, eject the sd, insert it into your computer, and put the file on that way. Make sure you wipe data, dalvik, and ext partition (only necessary if you have a partitioned sd and you're using app2sd on a 2.1 rom). Then flash your new rom and enjoy.
There are a couple ways to change your recovery from clockwork to amon ra. There's a how to floating around xda somewhere for changing from clockwork to amon ra. I'd link it but it's late and i don't feel like searching for it. You could also use the RUU method to unroot your phone and then do the 1 click method to root it again. This would automatically install amon ra. I have not tried either method, so please read and fully understand them before you attempt it.
I'm just curious, which method did you use to root your phone and how are you getting into recovery?
Sent from my Froyo Eris using XDA App
I used the 1 click method. So apparently i already have amon ra... but i've been using rom manager, and the clockwork backup feature in there.
And i'm getting into recovery by holding the volume down and power buttons.
Thanks for the help, I'll try it out
When you you boot into recovery using power and vol up do you see anything on the screen about amon ra (I think it says amon ra 1.6.2)? I'm not the most advanced user but it seems to me that clockwork would replace amon ra if you installed it through rom manager. Maybe both recoveries are on your phone?
Sent from my Froyo Eris using XDA App
I tried flashing Ken's GB ROM today and for some reason it would just load the AT&T screen then restart. I flashed the zips through CWM, what might I have done wrong?
which recovery did you use? did you wipe? and try to re-download it. you may have gotten a damaged file. it happens. this is why we have MD5 sums
I used rom manager, I wiped after (maybe I should have done it before?), and what's an mds sum?
Sent from my MB860 using XDA App
I just used the new official CWM for Atrix (as opposed to tenfar's custom build) to flash navalynt's CherryBlur1.2 over my old 2.3.4HKTW ROM, which I had modified with navalynt's 1.8 rollup package.
I'm also bootlooping on the Atrix logo (instead of the Motorola logo; I think it was part of the theme included in the update package, and it'd be nice to be able to change it back to the stock somehow). I'd take your advice and try redownloading the .zip of the ROM, but, uh, I don't really know how to access my phone's internal storage without being able to boot it up.
Should I manually try flashing the .img files via fastboot interface, or what? I really picked a bad time to screw with my phone, because I'm expecting a call about a new job...
Obscene Topiary said:
I just used the new official CWM for Atrix (as opposed to tenfar's custom build) to flash navalynt's CherryBlur1.2 over my old 2.3.4HKTW ROM, which I had modified with navalynt's 1.8 rollup package.
I'm also bootlooping on the Atrix logo (instead of the Motorola logo; I think it was part of the theme included in the update package, and it'd be nice to be able to change it back to the stock somehow). I'd take your advice and try redownloading the .zip of the ROM, but, uh, I don't really know how to access my phone's internal storage without being able to boot it up.
Should I manually try flashing the .img files via fastboot interface, or what? I really picked a bad time to screw with my phone, because I'm expecting a call about a new job...
Click to expand...
Click to collapse
Yea, if you didn't make a nandroid backup, you need to flash the image files of your previous rom
Sent from my MB860 using XDA App
Well, this is very strange. I restored the backup I had made, although I got an error from CWM about being unable to wipe /data... nonetheless it booted properly. I loaded a new download of the .zip, flashed it in CWM with no apparent errors, and now instead of bootlooping on the custom Atrix animation, it's bootlooping on the Motorola "dual core technology" screen (not the actual bootloader screen with "unlocked" in the corner, but after that). I'm really confounded by all of this.
Forum is full of similar threads.
Rom Manager doesn't successfully wipe. You need to run a fastboot -w or reinstall tenfar's CWM and wipe, then reinstall your ROM. This will resolve your bootloop.
EDIT: You're seeing the same problem...bootlooping. The ROM's just have different boot animations: Atrix logo vs. Default Moto.
quicklyspent said:
Forum is full of similar threads.
Rom Manager doesn't successfully wipe. You need to run a fastboot -w or reinstall tenfar's CWM and wipe, then reinstall your ROM. This will resolve your bootloop.
EDIT: You're seeing the same problem...bootlooping. The ROM's just have different boot animations: Atrix logo vs. Default Moto.
Click to expand...
Click to collapse
Yes, I just used fastboot to reflash the stock HKTW images, and of course it's fine now. I'd just like to be able to get CherryBlur to work properly.
Edit: Got it. The .zip installed properly using tenfar's CWM. Ironically enough, tenfar's custom implementation of CWM works better than ROM Manager's, although obnoxiously it's unable to mount the phone's internal SD storage, so an external SD card must be used for installing .zips. ROM Manager's CWM can mount the internal storage, but has other issues. Lol, so convoluted.
Obscene Topiary said:
Yes, I just used fastboot to reflash the stock HKTW images, and of course it's fine now. I'd just like to be able to get CherryBlur to work properly.
Edit: Got it. The .zip installed properly using tenfar's CWM. Ironically enough, tenfar's custom implementation of CWM works better than ROM Manager's, although obnoxiously it's unable to mount the phone's internal SD storage, so an external SD card must be used for installing .zips. ROM Manager's CWM can mount the internal storage, but has other issues. Lol, so convoluted.
Click to expand...
Click to collapse
It's just a matter of time before rom managers cwm works properly
Sent from my MB860 using XDA App
I installed TWRP on my phone, and went into Bootloader an hit RECOVERY so I can get to the program (the first time I did this it brought me to the TMRWP program). THIS time, it completely wiped my friggin' phone... after I sat there like 4 hours re-setting up everything PERFECTLY how I wanted it.
What's weird is it kept ALL my apps that I converted to SYSTEM APPS, but all my user stuff is gone.
Lesson learned... Don't click recovery from Bootloader.
That has yet to happen to me with any recovery and 3 devices currently with twrp. Might be a step missed with the install or maybe you left a bootloader update zip and ran it when you rebooted? Or it can be a bug as going to recovery from bootloader via a cold start is how to get there traditionally. I would email teamwin and try to sort it out or redo the recovery install, making sure to check the md5 of the file after you download it.
Sent from my Transformer TF101 using Tapatalk 2
Your supposed to click recovery at bootloader. Thats where you do backup, restore and flash new roms.
HTC Sensation z710e
ICS 4.0.3
Sense version 4.0
Software Sense-o-maniac v1.3
Kernel. 3.0.30 Bricked
Radio 11.68.3504
That's what I thought too. If I'm not mistaking, I flashed the new firmware after I did the TWRP, so maybe that screwed it up somehow. I take it TWRP must be the LAST image you flash? Only flashes I remember doing were:
Customize bootloader screen
TWRP.
firmware update
Do I need to re-flash the new firmware before re-flashing TWRP, or is the firmware going to remain no matter what I do from this point on?
Just adb flash recovery. Put the recovery image in your platform tools folder. Adb reboot bootloader. when you are rebooted adb flash recovery recovery.img.
Or use one of the many tools made to do that on our forums
Sent from my ADR6425LVW using xda premium
Well I went ahead and used the GOO Manager to flash TWRP again, and this time it worked fine. I'm going to re-setup my phone again then before I customize it back like I had it, going to try to get to recovery and see if it works.
With it now being installed, does that mean I can't flash anything directly from SD Card or modify the bootloader anymore without it causing problems?
What I mean, moreso, is... if I ever put factory reset. will it reload the factory rom + keep the newest firmware I installed (etc.) or do I nee to back up the phone with TWRP and recover from that when I want to load it back?
Factory reset just puts things back to the way they were without the stuff in the data partition or any user apps or settings. This means that say you flash a custom rom, it will reset to as if that custom rom was freshly installed since the custom rom has replaced the factory rom in the /system/ parition and anything else related to it.
With that said it is usually a good practice after rooting a fresh device to do the nandroid and then transfer it to a computer before you do anything else. Note that while you probably won't be switching recoveries a lot, that nandroid backups generally work only with the recovery that generated them so don't get them mixed up.
I flashed twrp.img during unlock/root process. I have seen some mods/roms that say I should use CWR and not twrp to flash.
is it ok to install cwr even though I am running twrp already?
I fear conflicts like when I click reboot to recovery, wouldn't my device be confused which to use?
If you flash cwm it will replace twrp
Sent from my Droid DNA
jasonpascoe said:
I flashed twrp.img during unlock/root process. I have seen some mods/roms that say I should use CWR and not twrp to flash.
is it ok to install cwr even though I am running twrp already?
I fear conflicts like when I click reboot to recovery, wouldn't my device be confused which to use?
Click to expand...
Click to collapse
Go ahead and flash cwm youll be perfectly safe. the recovery.img's overwrite eachother so the phone will only boot to one or the other depending on what you have flashed most recently. TWRP has known errors, i've actually contacted the primary dev of twrp to resolve this but havent had time to follow up with him. Anyway CWM is much safer for now.
Don't forget that backups made with one recovery won't restore with a different recovery. So if you switch from TWRP to CWR, make a new backup
I would really like to see Amon Ra ported to the DNA. Anyone know how, or someone who could? It worked really nice on the Rezound.
{Possibly SOLVED}
Moved from Development Thread.
---
Installation errors.
--
What happens is when you get it all setup for the install, and you go and install it, it only wipes the system partition, (appears to anyway). and that is all it will do. I tried it on CWM first, then I saw that it said to use TWRP so I switched and it did the same thing. It did actually extract the files when I switched to TWRP the first time I tried to install it, then it was in a boot loop (I did flash the boot.img) and tried to re-install it. But it did the same thing it did in CWM.
I had the same issue. Both cwm and twrp would only wipe but not install. I got the Rom to install by flashing infernal kernal http://forum.xda-developers.com/showthread.php?p=39831357 first. It also contains the boot.IMG then flashed viperlte. I also verified md5's to before and after transfering to my sd card. Now I got it up and running with no issues.
Sent from my ADR6410LVW using xda app-developers app
Thanks, I'll try that and see what happens.
--
--
Watch out, TWRP wipes can wipe your internal SD card without warning. (When using the Factory Reset) unlike CWM recovery.)
--
EDIT: WORKS. Use infernal 4.1 kernel instead of stock kernel if your phone goes into a bootloop. And use TWRP 2.3.3.0.
Hey,
Is there any known reason that the newer TWRP (2.5) doesn't work?
Also, Because I am so new to XDA, I'm not able to suggest this in the development section but it seems to me that the step two on the second post of the thread concerning this rom (http://forum.xda-developers.com/showthread.php?t=1891202) could specify TWRP 2.3 i.e. instead of saying,
"2 Install a custom recovery. (twrp) "
It could say,
"2 Install a custom recovery. (twrp 2.3)"
Venom will only install on S-off with absolute stock ROM with root. If you have ever installed a JB rom, you cannot roll back to ICS with Venom. Download the stock RUU image, rename to PJ53DIAG.zip and initiate update. Reroot, reflash custom recovery, the bootloader will remain unchanged.
OR..the OBVIOUS & SIMPLEST method!
Restore from your ORIGINAL & first system nandroid. Then flash not just Viper but any ICS custom ROM using Aroma installer.
Sent from my Incredible 4G LTE using xda premium
Kienan said:
Hey,
Is there any known reason that the newer TWRP (2.5) doesn't work?
Also, Because I am so new to XDA, I'm not able to suggest this in the development section but it seems to me that the step two on the second post of the thread concerning this rom (http://forum.xda-developers.com/showthread.php?t=1891202) could specify TWRP 2.3 i.e. instead of saying,
"2 Install a custom recovery. (twrp) "
It could say,
"2 Install a custom recovery. (twrp 2.3)"
Click to expand...
Click to collapse
Twrp has aroma problems, mdmower posted the fix on venom thread and looks like nuts never updated, if you push mdmowers fix into venom zip it will work
Sent from my ADR6410LVW using xda app-developers app