Related
Have full Nand root with Clockwork recovery 1.8.2.1. Every time I try to do a nandroid back up, either from within rom manager or directly from recovery, it errors out. It says "E:Can't open /tmp/recovery.img" when doing directly from recovery. When doing from within rom manager, it'll boot into the recovery screen with the yellow triangle and the android, but sticks there.
Any ideas?
I got the same error earlier and didnt think anything of it til i went to recover and it failed at the md5 sum check. Good thing i still had another one from today.
Did you ever figure out what the problem was?
Nope i still cant seem to backup. Anyone else with full nand unlock unable to nandroid?
Anyone able to help us out? its kinda a big problem not to be able to backup..
Also when im in recovery I see that /tmp/recovery.log is not accessible, nor is it a file. I tried to create it but /tmp is read only.. I did the full nand unlock and can write to /system while android is running.
Can we get some acknowledgement of this issue? I really dont want to do anything until i can backup again, and its killing me
Mast3rpyr0 said:
Anyone able to help us out? its kinda a big problem not to be able to backup..
Also when im in recovery I see that /tmp/recovery.log is not accessible, nor is it a file. I tried to create it but /tmp is read only.. I did the full nand unlock and can write to /system while android is running.
Click to expand...
Click to collapse
This is a major issue. Not only can I not backup, but I can't seem to flash any new roms either. I am stuck with what I have. I haven't heard anything from any of the devs. Anyone? Bueller? Buelller? Bueller?
I just reflashed the root PC36IMG and started over, took out nand unlock. Im perfectly ok with rebooting to recovery to when i want to write to /system. kinda a fail safe i guess.
Works for me, but I use the actual nandroid and not clockwork nandroid.
warmthsound said:
Have full Nand root with Clockwork recovery 1.8.2.1. Every time I try to do a nandroid back up, either from within rom manager or directly from recovery, it errors out. It says "E:Can't open /tmp/recovery.img" when doing directly from recovery. When doing from within rom manager, it'll boot into the recovery screen with the yellow triangle and the android, but sticks there.
Any ideas?
Click to expand...
Click to collapse
Hey guys, thanks for the bug report. I'll fix this today!
Hi Koush,
I seem to still be getting this error, as well as "E:Can't make /tmp/update_binary" when I try to flash new kernels.
I can still apply new ROMs and some other updates without issue, other than the aforementioned recovery.log error.
This is on a HTC Desire using the latest version of ClockworkMod as installed by ROM Manager.
What version of Clockwork are you using?
I was using the newest version of Clockwork flashed from the newest version of Rom Manager and I was still getting this error in the recovery:
E:Can't open /tmp/recovery.log
I tried flashing back to an older version but it said the same thing.
I had to reflash the stock recovery img to get my Nandroid backup to work.
Dsmithjr said:
I was using the newest version of Clockwork flashed from the newest version of Rom Manager and I was still getting this error in the recovery:
E:Can't open /tmp/recovery.log
I tried flashing back to an older version but it said the same thing.
I had to reflash the stock recovery img to get my Nandroid backup to work.
Click to expand...
Click to collapse
Which version does it say in the recovery window I'm trying to figure out if the flash actually worked
Koush said:
Which version does it say in the recovery window I'm trying to figure out if the flash actually worked
Click to expand...
Click to collapse
Sorry Koush, I uninstalled it last night when I was having the issues and I can't remember the version numbers (it was pretty late). From what I can remember, the Rom Manager was version 2.0.0.5 I think, and the Recovery was 2.0.2.X maybe? I can't really remember. It did say the right number in the recovery window.
Last night I wiped and installed a new ROM on my phone, then installed Rom Manager from the market and flashed the newest recovery. It looked like everything was working but when I tried to flash a ROM, the phone would reboot into recovery, print a few lines of text on the screen, and then just reboot right away. So I rebooted to recovery from Rom Manager and it booted to your recovery, but it gave me the error at the bottom of the screen.
I flashed an older recovery (version 1.0.8.2 or something) and it did the same thing. Maybe I'll re dl it and try again today.
2.0.1.4, which is what ROM Manager 2.0.0.5 reports as the latest.
Just tried flashing 2.0.2.0 from the experimental section in ROM Manager, but when I rebooted to retest it seems ClockworkMod itself reports v1.8.2.1
I did this using unrEVOked 2 on a Mac, a few weeks back, which apparently should have installed ClockworkMod 2.0.1.0 - as ROM Manager reports 2.0.2.0 is present and gives no errors on flashing new versions, how can I resolve this?
Edit: Just rebooted into ClockworkMod v1.8.2.1 and tried to manually flash the 2.0.1.4 and the 2.0.2.0 recovery update zips but these too failed immediately with the "E:Can't make /tmp/update_binary" error.
Can you adb shell into your phone while in recovery and type "mount"?
I have the same problem,but I just can Backup~!I don't know why^^^
I flashed the most recent ClockworkMod to my phone using ROM manager so I could do a ROM backup, and now my phone will not go into recovery mode. When I get into the boot menu and try to go into recovery, it goes into the splash screen and stays there.
Has anyone else had this happen with ClockworkMod 3.0.0.3? It took my phone quite a while to boot after that, and it put me into panic mode for a good moment.
I'll be flashing Amon_RA now to do my backup/ROM flashing. The latest updates to ClockworkMod keep doing crazy, crazy things to my poor EVO. Has anyone else experienced this?
YES! I was flashing a rom earlier tonight with the latest clockwork from rom manager and it messed up everything. Tried a bunch of different things. Still hangs on splash screen. How long did you have to wait?
yes also nothing wanted to flash had to go back to clockwm.. 2.5.0 where everything was petfect lol
Sent from my PC36100 using XDA App
same here, went to flash a few zips and installations kept aborting. just flashed amon ra and no problems now. hopefully they fix whatever happened to clockworkmod before ppl go crazy lol
my evo is doing that as i type this, i will definitely be switching to amon ra (as soon as my evo stops freaking out) until it gets fixed.
Alfred F. Jones said:
I flashed the most recent ClockworkMod to my phone using ROM manager so I could do a ROM backup, and now my phone will not go into recovery mode. When I get into the boot menu and try to go into recovery, it goes into the splash screen and stays there.
Has anyone else had this happen with ClockworkMod 3.0.0.3? It took my phone quite a while to boot after that, and it put me into panic mode for a good moment.
I'll be flashing Amon_RA now to do my backup/ROM flashing. The latest updates to ClockworkMod keep doing crazy, crazy things to my poor EVO. Has anyone else experienced this?
Click to expand...
Click to collapse
same thing happened to me and I thought I bricked my phone-took a few hrs to sort out. very disappointing
how did you solve the issue? my phone is basically in a bricked state...
ricankng787 said:
how did you solve the issue? my phone is basically in a bricked state...
Click to expand...
Click to collapse
can you boot into HBOOT? if so flash back to an older version of ClockworkMod.
taintbad said:
can you boot into HBOOT? if so flash back to an older version of ClockworkMod.
Click to expand...
Click to collapse
yes I can boot into hboot, how would i push files onto the phone? and flash from there?
ricankng787 said:
yes I can boot into hboot, how would i push files onto the phone? and flash from there?
Click to expand...
Click to collapse
I used the ClockworkMod from unrevoked
http://unrevoked.com/rootwiki/doku.php/public/forever
place the appropriate file on the root of the sdcard using a card reader and boot into HBOOT.
I got out of it by crossing my fingers and doing a battery pull, then booting normally. Thankfully it worked, so I had the chance to use ROM Manager to flash Amon_RA, but I can't guarantee it would work for everyone's.
hope this helps some one I went to appmarket and romanager and uninstalled update then went to app to flash back to older version 2.5
Sent from my PC36100 using XDA App
I hope so too. At this point I'd probably recommend that everyone with trouble either go back to 2.5 or even suggest switching to Amon_RA... nothing but problems with 3.0. !
my just rooted my phone and attempted to flash a rom, wiping data and cache first. now i it gets stuck at boot screen! i do a battery pull and it goes back to recovery but i dont know what to do?!?
Let me guess, its an EXT4 Rom and you install clockworkmod 2.5.1.2 or 3.
the clockwork mod that came with the simple root. and yes it was ext4....
Then you aren't using an EXT4 compatible clockworkmod
okay then what do i do? i wiped data/cache/davlik and rebooted but it stays on the boot screen...
Odin back to stock and try again.
Beezer80 said:
Odin back to stock and try again.
Click to expand...
Click to collapse
Correction , odin to stock than install clockworkmod 3
wow! thats awesome! i just came from the Evo and we didnt have anything this cool. if you cant do anything from recovery then you were screwed. loving this phone. thank you so much for your help! sorry for my newb histeria!
f10g44 said:
wow! thats awesome! i just came from the Evo and we didnt have anything this cool. if you cant do anything from recovery then you were screwed. loving this phone. thank you so much for your help! sorry for my newb histeria!
Click to expand...
Click to collapse
Since I'm a bit of a grammar-nazi I can't help but say that it's HYSTERIA, that is all.
ugh lol now im just trying to find out how to use it... went to wiki but still kind of confused..
You load the Rom as PDA, the modem as Phone and boot into download mode on your phone by holding the power button and 1 on the hardware keyboard
Hey, I got a soft brick so I'm going to use the unroot method here but I just wanted to make sure it would work.
S-OFF, Hboot 2.1
Also, I'll still be able to root and go back to an old nandroid if this all works out, correct?
It should work. Yes, you will be able to re-root and restore a nandroid once you have completed everything again.
Might throw out your issue first, to see if someone can help you fix without having to go through all that work of unrooting and re-rooting again.
Let's hope so. I'm knocking on wood that I won't have to throw my EVO down some stairs and go get a new one.
Firstly, it is unclear (at least to me) what you mean by "soft brick". Secondly, the link you posted is to a thread that is outdated and was retired by the OP. Or did you mean this thread?
http://forum.xda-developers.com/showthread.php?t=838448
To answer your second question, with S-off you can just go into recovery, do a wipe and then restore your NAND back-up from there. Try just wiping the cache and dalvik cache before restoring. If your phone still gives you problems, you may need to do a full wipe and do a fresh install of your favorite rom.
Ok things are more complicated than I had originally implied.
I can't boot into recovery--still SOFF but when I try to get into recovery I'm getting the red triangle.
Should I try the fix broken recovery option?
tubazeppelin said:
Ok things are more complicated than I had originally implied.
I can't boot into recovery--still SOFF but when I try to get into recovery I'm getting the red triangle.
Should I try the fix broken recovery option?
Click to expand...
Click to collapse
Now we're getting somewhere. Yes, if you can get the recovery to work, it will make the process less difficult for you. Can you boot normally? If so, use ROM Manager to flash the recovery on it. If it doesn't boot into clockwork, try using ROM Manager to flash an alternate recovery (Amon RA) and then try booting into recovery.
If your phone doesn't boot at all, you're going to have to push the recovery image onto the phone via fastboot adb. Worse case scenario would be to run the RUU and start over.
rugedraw said:
Now we're getting somewhere. Yes, if you can get the recovery to work, it will make the process less difficult for you. Can you boot normally? If so, use ROM Manager to flash the recovery on it. If it doesn't boot into clockwork, try using ROM Manager to flash an alternate recovery (Amon RA) and then try booting into recovery.
If your phone doesn't boot at all, you're going to have to push the recovery image onto the phone via fastboot adb.
Click to expand...
Click to collapse
Yeah, no dice on getting it to boot. Stick on the HTC EVO 4G white screen and goes nowhere. I got into this mess trying to apply the GPS fix for CM7 and when i tried to nandroid back I got loopy loops.
So should I just use the recovery fix listed there or can I just download CM 3.0.0.5 and push that via fastboot? All my nandroids are via CM.
tubazeppelin said:
Yeah, no dice on getting it to boot. Stick on the HTC EVO 4G white screen and goes nowhere. I got into this mess trying to apply the GPS fix for CM7 and when i tried to nandroid back I got loopy loops.
So should I just use the recovery fix listed there or can I just download CM 3.0.0.5 and push that via fastboot? All my nandroids are via CM.
Click to expand...
Click to collapse
I would download Amon recovery and flash that via adb; I recommend staying away from clockwork - read about too many users running into issues with it, especially that 3.0.0.5 version.
tubazeppelin said:
Yeah, no dice on getting it to boot. Stick on the HTC EVO 4G white screen and goes nowhere. I got into this mess trying to apply the GPS fix for CM7 and when i tried to nandroid back I got loopy loops.
So should I just use the recovery fix listed there or can I just download CM 3.0.0.5 and push that via fastboot? All my nandroids are via CM.
Click to expand...
Click to collapse
I would suggest using Amon Ra recovery. I like it better, and personally have had far less issues with it. Attatched is a PC36IMG of Amon Ra 2.3. Put it on the main directory of your SD card, name it exactly PC36IMG, and boot to bootloader, and select yes to update. That should flash Amon Ra's V2.3 recovery for you. If it's successful, see if it works. The only problem with this, that I see, is you wouldn't be able to restore your previous clockwork backups. However, if that did go successful, and you were able to boot into a rom, you could use ROM manager to flash clockwork back, then you could restore your backups. Hope you get it booted up.
EDIT: If you do end up needing to unroot, just remember that if you initially used unrevoked to root, or used unrevoked forever at any time, you're not going to be able to turn S on without having a custom recovery. Becase as far as I know, you need to flash the Unrevoked S on tool in recovery if you used unrevoked to begin with. Otherwise S is permanently off.
tubazeppelin said:
Yeah, no dice on getting it to boot. Stick on the HTC EVO 4G white screen and goes nowhere. I got into this mess trying to apply the GPS fix for CM7 and when i tried to nandroid back I got loopy loops.
So should I just use the recovery fix listed there or can I just download CM 3.0.0.5 and push that via fastboot? All my nandroids are via CM.
Click to expand...
Click to collapse
Yea, try the recovery fix. If unsuccessful getting CW to flash, remember you can always try to flash Amor RA recovery just to be able to wipe and flash a working rom. Once you get the phone to boot, you can download ROM manager, flash clockwork and then restore to your CW NAND that is stored on your SD card. I've had to do this in the past.
Thanks EVERYONE! Come to the DC area and the beer is on me (or if you're a mobile dev and want a job, hit me up)
Worked like a charm.
PS I copied down the error message I got when it was trying to install, wondering if I should be worried about this:
Microp OK
Radio_v2 FAIL pu
everything else OK
Bootloader FAIL ic
I renamed my recovery file and everything loaded up fine, just wondering if I should be worried about any of that
tubazeppelin said:
Thanks EVERYONE! Come to the DC area and the beer is on me (or if you're a mobile dev and want a job, hit me up)
Worked like a charm.
PS I copied down the error message I got when it was trying to install, wondering if I should be worried about this:
Microp OK
Radio_v2 FAIL pu
everything else OK
Bootloader FAIL ic
I renamed my recovery file and everything loaded up fine, just wondering if I should be worried about any of that
Click to expand...
Click to collapse
Really not sure. That goes beyond my scope of trial and error knowledge.
Well thanks anyway.
Looks like booting back into CWM is no longer an option for me--everything defaults to Amon_RA (even when trying to switch through ROM manager). Guess I can't load my old nandroids so I'm stuck rebuilding.
Oh well...worse things could have happened.
tubazeppelin said:
Well thanks anyway.
Looks like booting back into CWM is no longer an option for me--everything defaults to Amon_RA (even when trying to switch through ROM manager). Guess I can't load my old nandroids so I'm stuck rebuilding.
Oh well...worse things could have happened.
Click to expand...
Click to collapse
So choosing 'flash clockworkmod recovery' from rom manager doesnt work for you? weird. Try letting it flash, and then instead of rebooting to recovery from within rom manager, boot to recovery manually, from teh bootloader. see if that works.
k2buckley said:
So choosing 'flash clockworkmod recovery' from rom manager doesnt work for you? weird. Try letting it flash, and then instead of rebooting to recovery from within rom manager, boot to recovery manually, from teh bootloader. see if that works.
Click to expand...
Click to collapse
Well I tried that the first time and nothing really worked out--got the same loops and had to do the whole dance again.
Tried it again after your post and it worked. Hot damn.
Getting rid of CWM as we speak and going back to RA, which was my first and only recovery for so long.
tubazeppelin said:
Well I tried that the first time and nothing really worked out--got the same loops and had to do the whole dance again.
Tried it again after your post and it worked. Hot damn.
Getting rid of CWM as we speak and going back to RA, which was my first and only recovery for so long.
Click to expand...
Click to collapse
So strange, but glad it worked for you. And yea, staying on RA will be your best bet.
k2buckley said:
So strange, but glad it worked for you. And yea, staying on RA will be your best bet.
Click to expand...
Click to collapse
Seemed to be an issue with ROM Manager. So weird--I'm so used to everyone over in Heroland swearing by CWM. I'm glad I'm back to a spot where RA is king.
Anyway I uninstalled ROM manager and am just not going to screw with it anymore. GB has a "reboot to recovery" option for a reason.
tubazeppelin said:
Seemed to be an issue with ROM Manager. So weird--I'm so used to everyone over in Heroland swearing by CWM. I'm glad I'm back to a spot where RA is king.
Anyway I uninstalled ROM manager and am just not going to screw with it anymore. GB has a "reboot to recovery" option for a reason.
Click to expand...
Click to collapse
Awesome. Thats the way to go, just manually flash everything using RA and you'll be good to go.
Can anyone tell me how to fix this, I made a backup before installation however can't access recovery. I can however still access everything else on my phone, hence how I'm able to post here...
ASMAteMe said:
Can anyone tell me how to fix this, I made a backup before installation however can't access recovery. I can however still access everything else on my phone, hence how I'm able to post here...
Click to expand...
Click to collapse
What recovery were you running? What happens when you try to boot to recovery, does it just hang at the splash screen? If you want to restore a backup, then you should re-flash whatever recovery you were using when you made the backups. If you can still boot into the phone, the easiest way to re flash your recovery is using ROM manager. If you were using Amon Ra, first you'd need to select 'flash clockwork mod recovery'. Then when it finishes, select, 'flash alternate recovery'. That will flash you to RA. That should work for ya. If not, there are other ways of flashing a recovery. Good luck.
I was able to flash RA so I was able to fix my problem, thank god!
ASMAteMe said:
I was able to flash RA so I was able to fix my problem, thank god!
Click to expand...
Click to collapse
glad you got it all worked out.