Related
Hi everyone.
I'm pretty new to android, but I'm quite good at following instructions. Basically I've tried doing a nandroid backup with ROM Manager and everytime it reboots to make a backup it goes to a black screen with a phone in the middle of the screen with a red warning sign next to it. I've always tried booting into recovery and I get the same result. I first found this out while trying to follow the instructions for replacing the status and battery icons. Has anyone else had this issue?
I'm using ROM Manager v3.0.0.1 on a stock HTC MySense ROM from TMO running Android v2.2.1.
Thanks in advance for anyone that knows what I'm apparently doing wrong.
when you opened ROM Manager did you select "Flash ClockworkMod Recovery"? if not try that, it's the only time mine has what your's is doing. I got a little excited to flash Iced-Glacier when I first got the phone and accidentally skipped that step and had same issue
Yeah I first clicked on Flash ClockworkMod Recovery and it currently says Current Recovery: ClockworkMod 2.5.1.2. I just redid the flash and tried to boot into recovery mode and I'm still getting that error picture upon reboot.
Is there a setting on the phone somewhere that would cause this?
I am not positive 100% but I think I know what you mean; and I had it once due to very low battery charge. See if it is the problem or not.
infraled said:
Yeah I first clicked on Flash ClockworkMod Recovery and it currently says Current Recovery: ClockworkMod 2.5.1.2. I just redid the flash and tried to boot into recovery mode and I'm still getting that error picture upon reboot.
Is there a setting on the phone somewhere that would cause this?
Click to expand...
Click to collapse
The phone with the triangle is the stock recovery image. Others have had to try flash the ClockworkMod Recovery several times. You may need to as well.
this is what i did, not sure if your doing the same thing or not. i clicked on Flash ClockworkMod Recovery, MY4G came up and i clicked that and then clicked on backup current rom.
Alright so I've tried it with a full battery and I had the same result. I also tried reflashing several times with the current version and rebooting. I even tried to load some of the older versions of clockwork through ROM Manager and everytime I tried it spits out an error. I don't understand how I could be having such a hard time with something everyone seems to be able to do effortlessly.
Sent from my HTC Glacier using XDA App
R u sure u r rooted with S-off? If u r then u may have to flash recovery from ADB. Some people have not been able to get recovery to stick through ROM manager. There is a thread in the development section that explains how to do this.
Sent from my HTC Glacier using XDA App
Really? I have not heard that...I'll have to check up on that. It seems that this problem would be more common, but I guess not as I have had little luck in finding information on my own about this problem.
Just in case anyone is following this thread with the same problem as me, this is the post that the previous poster was referring to:
http://forum.xda-developers.com/showthread.php?t=852905&highlight=recovery
UPDATE:
Ok I figured out what was wrong. Apparently although I had root access on my phone and able to run things like Titanium Pro and Adfree and others with root privileges it wasn't good enough.
I followed the instructions here on how to permaroot your phone by pushing gfree to it. Once I did that I attempted to manually flash clockworkmod, which I ended up running into other issues. On a lark I tried installing clockworkmod through ROM Manager after permarooting and it finally installed it properly!
I love doing stuff like this, thanks to everyone for their input as it guided me to finally solving this. I'm off to do a nandroid backup now.
krypto16 said:
R u sure u r rooted with S-off? If u r then u may have to flash recovery from ADB. Some people have not been able to get recovery to stick through ROM manager. There is a thread in the development section that explains how to do this.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
I have NEVER been able to flash Recovery with ROM manager. It says it does it but corrupts if everytime! Note: There has been some recent updates to ROM Manager and I haven't tried lately.
krypto16 said:
R u sure u r rooted with S-off? If u r then u may have to flash recovery from ADB. Some people have not been able to get recovery to stick through ROM manager. There is a thread in the development section that explains how to do this.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
IIRC the security protocol doesn't have to be off to flash clockwork ROM you do have to be rooted, VISONary.apk of course. I've turned my S=on just to make sure and it [clockworkROM] works pretty flawlessly.
Hey hey, it's great to see infraled out here! I am rooted/S=Off via the first VISIONary thread that was posted...
http://forum.xda-developers.com/showthread.php?t=834225
I installed Clockwork, flashed Clockwork Recovery and was expecting to have to do it twice, as outlined in this thread...
http://forum.xda-developers.com/showthread.php?t=858021
It only took one shot for me and it worked perfectly. The very first try, I powered off, powered on w/ vol down, went into Recovery and wham, there was Clockwork in its green glory. I figured I was just lucky and that once I rebooted, it would be lost and I'd have to flash again. Not so. Did a backup right away, worked flawlessly.
Looking forward to Iced Glacier, eVil and Cyanogen over the holiday break...
shlongwoodian said:
Looking forward to Iced Glacier, eVil and Cyanogen over the holiday break...
Click to expand...
Click to collapse
Cyanogen Gets my vote... But i've always loved T/DB's ROMS.
Recently rooted My new MyTouch 4G, downloaded the paid version of rom manager. I didn't understand why there are none of the current roms like the iced glacier, roms made by evil and several others listed as possible roms for flashing. The only roms are the cyanogenmod nightly builds. The cyanogenmod 6.1.2 RC2 isn't listed either. Do I need to do anything to get those listed or is that just the way it is???
Thank you,
Vinny
So the current iterations of cwm seem to have trouble working reliably with the newer froyo ROMs, and koush's recovery (although seeming to work correctly) is quite broken. So......
please find below a new recovery package that should work for any ROM for the fascinate, mesmerize, or showcase.
This is a "red" cwm recovery, and it will work with both voodoo and non-voodoo installations.
cwm-recovery-ALL.zip can be flashed via any cwm recovery.
if you are using odin, then use the cwm-recovery-ALL odin (.tar) package.
updated 3/29 - thanks to GizmoDroid for help with fixing fix_permissions script and root permissions typo that screwed up nandroid restores
updated 3/30 - fixed 'umount' typo - actually *fixed* fix_permissions this time - fixed odin/heimdall recovery attachment
Thanks, I just installed it. I'd rather not have a broken clockwork mod.
thanks, will give this a try!
ok, so I flashed this in the old cwm and it does come up red, but also says CwM Voodoo Lagfix Recovery, is that right?
In what ways is the old cm broken with froyo? I haven't noticed any problems.
Thanks! Good to have a fully working recovery again.
renf said:
In what ways is the old cm broken with froyo? I haven't noticed any problems.
Click to expand...
Click to collapse
Yeah, I'd like to 2nd this question. I have DL30 and CW worked for me in setting that up. Granted, I haven't tried anything else after that, but I'd like to know too.
Well I've had weird things happen when flashing stuff (I was using the "new-cwm.zip") , seemed like data being written where it shouldn't be? Just flashing theme files or own stuff I want to add, and I've had the following stuff happen:
Nuked my radio, had an unknown baseband and calls would never work, fortunately Radio Odin fixed it.
Had some /data apps disappear. Had some /data/data disappear. On reboot had Setup Wizard pop-up, even though I still had my Google account registered.
Hoping this new clockwork is completely safe. I suspected that clockwork was responsible for my weird happenings, so data-wiped and haven't flashed anything, so far fine functioning.
Using this is it easy to flash back to a prior set up, for me it would be back to dj05 w superdark and voodoo5?
Ive been holding off on froyo bc I need wireless tether, preferably unreported tether. But I really want to play around and see what the fuss is about. Ive downloaded every dl30 rom, havent installed one fearing I cant go back easily
Sent from my SCH-I500 using XDA App
/data on the fascinate is on /dev/block/mmcblk0p1
koush's recovery mounts /data as mmcblk0p2 (THIS IS OUR /DATA/FOTA. THAT'S BAAADDD)
under most circumstances this does not matter , because recovery.rc mounts data CORRECTLY before cwm gets to it, but there are circumstances where /data can be unmounted and then remounted, in which case cwm is gonna mount mmcblk0p2. If things get written there, at best you've got a **** load of FC's to deal with. At worst, a dead radio.
I've pointed this out to koush before, but was met with a "half-response", and to date it not been addressed (except for the recoveries that I've posted)
installed. When I go to do a backup, it gives the messages below. Backup seems to run fine though
E: missing bitmap progress_empty (code -1)
E: missing bitmap progress_fill (code -1)
Click to expand...
Click to collapse
Thanks, jt.
Copied to sdcard, booted into recovery, ran the program, keep coming back to green, no red.
ETA: Interesting. If I go to recovery from ROM mgr and try to load from sdcard, it does nothing, but if (while in ROM Mgr) I load from SDcard, it works. Got the blue screen, ran update, red appeared.
I likewise get the error message mentioned previously, but got it at install. Backup seemed to ahve run fine.
Installed like a charm, thanks jt!
sent from my fascinating XDA App
jackmei2 said:
thanks, will give this a try!
ok, so I flashed this in the old cwm and it does come up red, but also says CwM Voodoo Lagfix Recovery, is that right?
Click to expand...
Click to collapse
Yes, that is correct. It says in the OP. But it may have been edited since the time you posted and my response, so I'll let it slide
thank you JT!!!!! I thought it was just me, Ive had to start over again with my data about 6 times now becuase of Clockwork either not restoring my backups or my phone freaking out once I restored the backup. Thanks again!!!
beenz said:
Yes, that is correct. It says in the OP. But it may have been edited since the time you posted and my response, so I'll let it slide
Click to expand...
Click to collapse
haha thanks... but he said it will be red and that it is not for voodoo, so that's what I wanted to double check since it does have the voodoo menus and all.
superchunkwii said:
Yeah, I'd like to 2nd this question. I have DL30 and CW worked for me in setting that up. Granted, I haven't tried anything else after that, but I'd like to know too.
Click to expand...
Click to collapse
Lets see:
Broken mass storage function.
Broken data mounting function.
Couldn't wipe properly because of the above.
adrynalyne said:
Lets see:
Broken mass storage function.
Broken data mounting function.
Couldn't wipe properly because of the above.
Click to expand...
Click to collapse
The couldn't wipe properly bit me once already. Glad to have a proper recovery.
Sent from my SCH-I500 using XDA App
Thanks very much for addressing this issue.
For a while, I felt like a fresh n00blet, wondering what I was doing wrong. I tried flashing versions of supposedly compatible cwm's in different ways, always coming to the mounting errors.
Other than the errors from the missing graphics, this one works error free.
Scared to mess with this since i haven't experienced any problems with my current cwm stuff from pre dl09... Might just go ahead and do this tomorrow. For some reason I feel more comfortable using the odin method, so I can do all this over my Super Clean 1.0 with Neon GT theme and not have to do any data wiping or anything first?
So this makes no sense and I think its a weird coincident but as soon as I flashed this my beta version of swype started the force close loop..
EDIT: so weird, I had to uninstall the installer and swype itself using titanium backup and then download the installer and install again (had to do it all twice). Seems to be working again now tho..
Superclean 0.7.. aka Froyo.. Thanks devs!
Hey guys, i have the new CWR on the fascinate... only problem is when i go to make a backup it says "failed to backup boot.img" and bombs out. Anyone else having this problem?
I did a ODIN to the deodexed EB01. didn't add a google account or anything. Shut down, manually entered CWR and it worked.
Rebooted, loaded all my data, rebooted into CWR to make a backup of EB01 w/data and got the error message. Nothing was flashed in between backups. All i did was run Titanium...
Anyone else?
I had the same issue, I couldn't flash any roms either. Only after I replaced the update.zip with the one from jt1134's fix, did i finally get mine to work (i extracted it from the zip and copied replaced the one on my sdcard). Haven't tried a backup, but restore worked. Huh ope this helps.
ya i was going to do that if needed, but i wanted to see if there was a fix for the current recovery before going backwards. I was able to do one backup as I stated, but then it bombs out. not sure what the deal is.
I see to many issues with 3.0. I am gonna stay with the 2.5.x version until I am forced to do otherwise.
gotsflat4love said:
I see to many issues with 3.0. I am gonna stay with the 2.5.x version until I am forced to do otherwise.
Click to expand...
Click to collapse
I.wish I had
3.0 uses edify scripts which is lacking for the fascinate
boostedjti said:
3.0 uses edify scripts which is lacking for the fascinate
Click to expand...
Click to collapse
Yes, but I don't think we need edify scripts just yet. Nor does it work even if it says that it does...
Hey guys...I had the same issue -- but followed this, and all is right with the world again.
G/L!
boostedjti said:
3.0 uses edify scripts which is lacking for the fascinate
Click to expand...
Click to collapse
It is now with superclean 2.7, i deleted the clockworkmod folder and reflashed
recovery from RM, backup works. I have'nt tried restore yet.
Fix permission still does'nt work.
Im was trying to fix permissions as well with the orange cwr but no go . im 0n 2.7 patch btw
billhilt said:
Im was trying to fix permissions as well with the orange cwr but no go . im 0n 2.7 patch btw
Click to expand...
Click to collapse
Since your on 2.7 you can do it from terminal emulator, just type su then fxpms
once its done type reboot.
Birgertime has done a great job getting EDT ROMs available via Rom Manager (I may have bugged him a couple of times). I was a bit shocked when I was reading the thread and saw people were having issues when they updated using Rom Manager. I think the consensus was that Rom Manager was not properly wiping.
This is what I did:
I was on Trigger 2.9.3 *I try every ROM and I just felt like being old school.
I opened Rom Manager and downloaded the latest Trigger 3.2,
I used the KB1 Modem, KB5 kernel, I selected a few of the apps I wanted (bloater, titanium, maybe a couple others)
I told Rom Manger to wipe and do a backup by clicking the two boxes.
Once the download was completed I proceeded.
It went into CWR and it did a backup... immediately it did a wipe (it showed the steps in CWR like normal)... and then it flashed the ROM and it rebooted perfectly. I have had NO issues with the ROM. It's perfect in my opinion.
What I want to know, for those who had issues... what was different?
Did you get rebooted into the red voodoo recovery (I was at the normal CWR)? I don't understand how it can work perfectly for me, and not others. I would like to know exactly what went wrong so we can go to @koush and try and get both Rom Manager and Clockwork Recovery working better for us.
Between this, Fix Permissions, Partitions F'ing people, stats not working (for the dev's) I think our phone needs this amazing app to be better, and I know koush can do it.
** If there are other things wrong with Rom Manager/CWR, please post... it would be nice to have a list of things to work on.
I can put up a test version on rom manager. The current Trigger 3.2 up there will wipe regardless of what you tell ROM manager.
PS: who rated it 1 star?
birgertime said:
PS: who rated it 1 star?
Click to expand...
Click to collapse
Team Whiskey
EDIT, were you going to fix the prop so it showed 3.2, not 3.1? =)
Im confused. You said you used CWR to wipe and flash the ROM. What exactly did you use ROM Manager for?
s15274n said:
Team Whiskey
EDIT, were you going to fix the prop so it showed 3.2, not 3.1? =)
Click to expand...
Click to collapse
I think I did when I uploaded the vvm fixed version
androidmonkey said:
Im confused. You said you used CWR to wipe and flash the ROM. What exactly did you use ROM Manager for?
Click to expand...
Click to collapse
To download it
Sent from my SGH-T959 using XDA App
duboi97 said:
To download it
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Ah, ok. I dont see why downloading it with RomManager would make a difference, unless its not completely downloading. The safest is like birgertime says in the Trigger thread, download on PC and check Hash.
androidmonkey said:
Ah, ok. I dont see why downloading it with RomManager would make a difference, unless its not completely downloading. The safest is like birgertime says in the Trigger thread, download on PC and check Hash.
Click to expand...
Click to collapse
Rom Manager is the most convenient way to do this. it also checks the MD5 before it flashes the ROM. Trust me when I say I know the process...
I just want to know from those who had issues with using Rom Manager to download/wipe/flash, what went wrong?
I flashed it using Rom manager.
I chose KB5 modem and KB5 Kernel.
along with things like Bloater and swype.
it rebooted into red recovery and seemed to go fine from there.
when it first booted up it seemed ok at first, I let it sit for a while like usual.
and then rom manager force closed.
from there it was just force close after force close.
So I rebooted back into recovery and wiped data and dalvik.
then I rebooted.
and everything works just fine, with the exception of it never installed any of the extras I chose (swype,Bloater, etc...)
but I had those in titanium backup just in case anyways so it wasn't a big deal.
Its been running beautifully ever since.
Pretty much same thing happened to me, it went to red recovery and seemed to flash just fine. then when it rebooted i kept getting force closes everywhere. rebooted to clear cahce, dalvik, and fix permissions and has been fine ever since. it didnt wipe my apps which i found a bit odd
Alright, so as I expected... it sounds like it was
THE RED VOODOO RECOVERY AS THE PROBLEM.
Anyone able to prove that wrong?
I mean, it makes sense, it's not the recovery Rom Manager expects to see.
So, how do we fix it? This would not be koush now, I do not think.
Where did the red voodoo recovery initiate? I remember it just showed up one day. was it supercurio?
I installed BAMF 1.6.3 remix and I noticed that I don't have some of the features that were listed in his OP.
For ex. I still have my location icon in my status bar, when I press on the themed rosie button on the right it still opens up the personalize settings no matter what icon I chose to put there. I don't have the 6 bar signal strength. I don't have the power control settings in my pull down menu, but I do have the power control settings apk in my drawer. Don't have widget picker, Don't have the extra power options when the power button is pressed, reboot, hibernate, etc.... Also when a call is missed it doesn't show the number in my pulldown menu only that I had 3 missed calles from*86 and something about CDMA on the missed call icon.
These are the few that I noticed in the couple hours of it being on my phone. I am just wondering if this is normal or what I may have did wrong and how to get these working as I thought they were part of the ROM itself.
Thanks
Did you flash the rom in rom manager??? If so, thats most likely what created the missing issues.
You have to flash the rom thru CWR for you to get everything up and running fully.
Yeah I downloaded from the forum then installed using ROM manager. I will re-install using CWR. I will post my results. Thanks for the quick response. Oh yeah I noticed my post was at like 1:34 am? It's only 8:47 where im at?
So I re-flashed the ROm and everything seems to be like it should. I wonder why the differnece from Rom Mgr? It's not like I downloaded the file through RM, And It flashed using CWM? Oh well, I will know from now on to flash manually. I don't have the paid version, but if you can't fully flash a rom then what's the point of having/paying for Rom Mgr?
MomentFreak said:
Yeah I downloaded from the forum then installed using ROM manager. I will re-install using CWR. I will post my results. Thanks for the quick response. Oh yeah I noticed my post was at like 1:34 am? It's only 8:47 where im at?
So I re-flashed the ROm and everything seems to be like it should. I wonder why the differnece from Rom Mgr? It's not like I downloaded the file through RM, And It flashed using CWM? Oh well, I will know from now on to flash manually. I don't have the paid version, but if you can't fully flash a rom then what's the point of having/paying for Rom Mgr?
Click to expand...
Click to collapse
Sometimes it works, sometimes it doesn't. Full blown roms I will always try to do in CWR from now on. If its something small like a theme or extra or add on, Rom Manager usually works well.
Glad the reflash worked well thru CWR.
New here , just wanted to ask under this post.
Kind of the same topic.
I came from the dx used droidx bootstrap and dx2 bootstrap.
New the the TB I seen some post saying Rom manager.
So I installed Bamf 1.6 and 1.6.3 remix from Rom manager.
But I hit the flash Rom manager button, success.
Then hit boot into recovery.
Is that what you guys mean when you type. CWR.
Checking to make sure I am doing it correct.
Thank you
tanium said:
New here , just wanted to ask under this post.
Kind of the same topic.
I came from the dx used droidx bootstrap and dx2 bootstrap.
New the the TB I seen some post saying Rom manager.
So I installed Bamf 1.6 and 1.6.3 remix from Rom manager.
But I hit the flash Rom manager button, success.
Then hit boot into recovery.
Is that what you guys mean when you type. CWR.
Checking to make sure I am doing it correct.
Thank you
Click to expand...
Click to collapse
Well you need Rom Manager to Install CWR which stands for ClockworkMod Recovery, Which is where you can make what they call Nandroid backups, which is a backup of your current system and setup including apps and data. So it's always good do backup before making any changes ex, flashing rom's. But there are many things you can do with it and to me is one of the most important parts of having a rooted phone is having recovery. Hope this clears some stuff up.
Yes thank you.
But this is all done from inside Rom manager correct.
I mean I open Rom manager and clicked boot into recovery.
This is how I flashed Bamf 1.6 remix.
I installed no other program or app to get recovery.
Yes I see now , went and looked.
I was following instructions before.
I had to hit flash clockworkrecovery.
That is what installed that I guess.
See learning all the time.
I used droidx bootstrap before never new Rom manager was so cool.
That guy rocks.
I also had this problem. Installing from Rom manager doesn't seem to be enough. You seem to need to boot into recovery and install it manually from cwr.
Sent from my Verizon Wireless 4G LTE Thunderbolt
Definitely noticed that things can come up missing unless you wipe all three Data/Davlik/Cache and use clockwork to do it all. For some reason just flashing and wiping using ROM manager doesnt cut it.