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^^^
Hiya all,
Just got my new Desire and rooted it right away of course.
Used unrevoked and all went well. Installed Rom Manager and it said I needed to install clockwork (even though it had already been installed by unrevoked) so I agreed.
Now when I run clockwork (2.5.0.7) it gives the following:
E:Can't find MISC:
E:Can't mount CACHE:recovery/command
E:Can't find MISC:
E:Can't mount CACHE:recovery/log
E:Can't find MISC:
I am unable to backup or restore. Backing up says:
Error while dumping boot image!
E:Can't mount CACHE:recovery/log
E:Can't find MISC:
Basically none of the commands in clockworkmod are working.
Next I tried using unrevoker to flash AmonRa but that just resulted in a black screen when I booted into recovery. So, once again, I used unrevoker and it reinstalled 2.5.0.7 with the same errors.
I have also tried using Rom Manger to download older versions of clockwork however, when I flash these using recovery it shows them as having installed at the time but, on reeboot, it switches back to 2.5.0.7 so the flash isn't working. The same applies if trying to change it in Rom Manager - it shows up as changed there, but is not on booting recovery.
Any help would be extremely gratefully received as I have been messing about with this most of the afternoon and I don't really know where to go next.
How about just using the phone first and see how it runs before jumping into rooting - I'd also recommend checking there is an RUU of your existing ROM so you can go back to stock should you need to
What is it with people rooting before even USING the phone??? Seriously...
introv said:
Hiya all,
Just got my new Desire and rooted it right away of course.
Used unrevoked and all went well. Installed Rom Manager and it said I needed to install clockwork (even though it had already been installed by unrevoked) so I agreed.
Now when I run clockwork (2.5.0.7) it gives the following:
E:Can't find MISC:
E:Can't mount CACHE:recovery/command
E:Can't find MISC:
E:Can't mount CACHE:recovery/log
E:Can't find MISC:
I am unable to backup or restore. Backing up says:
Error while dumping boot image!
E:Can't mount CACHE:recovery/log
E:Can't find MISC:
Basically none of the commands in clockworkmod are working.
Next I tried using unrevoker to flash AmonRa but that just resulted in a black screen when I booted into recovery. So, once again, I used unrevoker and it reinstalled 2.5.0.7 with the same errors.
I have also tried using Rom Manger to download older versions of clockwork however, when I flash these using recovery it shows them as having installed at the time but, on reeboot, it switches back to 2.5.0.7 so the flash isn't working. The same applies if trying to change it in Rom Manager - it shows up as changed there, but is not on booting recovery.
Any help would be extremely gratefully received as I have been messing about with this most of the afternoon and I don't really know where to go next.
Click to expand...
Click to collapse
How are you entering Recovery, via Rom-Manager? If so, it might be trying to load fake-flash.
What happens if you try and load using the bootloader (power off, hold back and press power).
StuMcBill said:
How are you entering Recovery, via Rom-Manager? If so, it might be trying to load fake-flash.
What happens if you try and load using the bootloader (power off, hold back and press power).
Click to expand...
Click to collapse
Same thing I'm afraid. Same errors and the same inability to overwrite the recovery image with a different version.
EddyOS said:
What is it with people rooting before even USING the phone??? Seriously...
Click to expand...
Click to collapse
Of course I used it. It sends texts, connects to the internet, has android on. Time to move on ...
I'm a software developer. I break and fix things for a living and I enjoy it so consider a new phone a new piece of kit to mess with above anything else.
What is it with people attempting to belittle others decisions??? Seriously ...
introv said:
Same thing I'm afraid. Same errors and the same inability to overwrite the recovery image with a different version.
Click to expand...
Click to collapse
I would go back to stock firmware and "re-unrevoked" it again and go from there.
I think Rom-Manager still installs fake-flash, and since unrevoked installs a permanent recovery, you don't really need to use it.
ROM Manager is a PITA - never used it as I prefer to do things myself from recovery. You get a lot more control over things
introv said:
Same thing I'm afraid. Same errors and the same inability to overwrite the recovery image with a different version.
Of course I used it. It sends texts, connects to the internet, has android on. Time to move on ...
I'm a software developer. I break and fix things for a living and I enjoy it so consider a new phone a new piece of kit to mess with above anything else.
What is it with people attempting to belittle others decisions??? Seriously ...
Click to expand...
Click to collapse
I'm not belittling anyone
There are FAR too many people who come on and are like
"So I just got my new phone from the shop and have rooted it and S-OFF - I'm so cool, look at me!!"
And they have NO idea what they've done or why. Your first post mentioned nothing of being a developer nor that you'd used the phone before. What does the phone not do that you need to root or are you rooting for the sake of rooting??
People don't think enough and just follow others like sheep
Baaaaaa..... lol!!
EddyOS said:
ROM Manager is a PITA - never used it as I prefer to do things myself from recovery. You get a lot more control over things
Click to expand...
Click to collapse
So it seems, and that's what I'm used to doing on my old G1.
Part of the issue here is that even in recovery, when booting directly to it, clockwork is not working correctly and is also not allowing me to flash over it. Worse than that though is that when I flash a different recovery on using unrevoker the phone black screens when booting into recovery.
Anyhoo ... unless anyone else has any brilliant ideas I guess I will reset it to stock tomorrow and try again.
I think the easiest thing to do is go back to stock and start afresh.
Also if you want to change recoveries often you should maybe look into AlphaRev (www.alpharev.nl) and get an S-Off HBOOT.
Do you have an AMOLED or an SLCD Desire?
Sent from my Amiga 500 using Workbench
same problem here, recovery doesn't work properly. Any ideas?
EDIT: I guess I should provide some details ;-)
I have a rather new (3 weeks old) SLCD Desire with a Vodafone branding on it.
Unrevoked 3.21 didn't work, so I had to use the older version which doesn't check the misc partition for the correct version.
Now rooting went fine, but if I try to boot into recovery, it can't mount any of the flash partitions (except for the sdcard), instead it shows the same error messages the OP got.
EDIT2: Got it fixed. The default recovery seems to be broken, everything worked after flashing the RA-desire-v2.0.0 Recovery.
Did find any solution to this problem plzzzzzzzzzzz help me
I should 1)backup? 2)s-off? 3)flash using the RA-desire-v2.0.0 Recovery?
then after that i shouldn't receive "E:Can't find MISC: ... "?
I'd like to know how to solve this problem too... It's pretty annoying not to able to flash or at least backup a ROM. How did you get it work ?
This works for me . . . .
I had exactly the same problem and had to install clockworkmod 3.0.0.5 in order to be able to create a nandroid backup.
Search the desire development thread for the latest clockworkmod, download the .img version and reflash the phone using unrevoked but before you start, go into unrevoked settings and tell it to use the .img you downloaded instead of the standard one. 3.0.0.5 will then be your standard recovery and will let you backup/flash etc.
Also,
Keep ROM Manager installed, because although It's generally **** and I'd never use it if I didn't have to, it has one use . .
Sometimes, you may try to flash a zip in Clockworkmod (CWM) 3.0.0.5 and it will tell you it can't flash it due to some edify scripting issue (or something like that!!)
As rare as it is, if this happens, reboot to android, run ROM Manager and ask it to install recovery. When it's done, ask it to reboot to recovery and it will install CWM 2.5.0.7 then boot into it, which will let you flash the zip which you couldn't flash before. Awesome!
The good thing is, once you leave recovery, 2.5.0.7 is gone and next time to reboot to recovery (not using ROM Manager) you will be back to 3.0.0.5.
Double awesome!!
What I've advised in the last 2 posts works well for me and has done for months, so hopefully it will work for you too.
Don't use ROM Manager for anything other than this though, cos apart from this it is rubbish!!
Hope this helps
EDIT: CWM is here by the way
http://forum.xda-developers.com/showthread.php?t=839640
Hi,
I used Unrevoked with the latest Clockwork recovery. Unfortunately, I got this error message : "Error, failed to get root. Is your firmware too new ?"
I think I must reset the phone though I don't want to... That'll do like I did the 1st time.
That sucks !
Here's a few suggestions for those who get "Error, failed to get root. Is your firmware too new ?"
http://androidforums.com/evo-4g-all-things-root/249730-unrevoked3-your-firmware-too-new.html
I Flashed KernelUpdater.zip with Merruks boot.img
then i had issues, sd card issues.
then i decided to flash back to my stock kernel.
when I reboot, my kernel is still Merruks.
What should I do??? HELP ME.
Flash the stock kernel by doky again. Follow the instructions correctly. Maybe you missed something.
And just follow original thread please.
I can't put the stock kernel by doky on my phone because im stuck at the android logo, how can I mount usb storage?
dennisaguilajr said:
I can't put the stock kernel by doky on my phone because im stuck at the android logo, how can I mount usb storage?
Click to expand...
Click to collapse
if you are able to go to download mode (press volume down + home button + power button all at the same time) then you are still ok, don't panic
go to this ---> thread
and flash the latest firmware for your country
leodasal2 said:
if you are able to go to download mode (press volume down + home button + power button all at the same time) then you are still ok, don't panic
go to this ---> thread
and flash the latest firmware for your country
Click to expand...
Click to collapse
Im now at download mode, it says Downloading.... Do not turn off target!!!
now what? i dont know what to do next?
dennisaguilajr said:
Im now at download mode, it says Downloading.... Do not turn off target!!!
now what? i dont know what to do next?
Click to expand...
Click to collapse
able to go to download mode (check) = your device is still good
just turn off your phone and go to the thread i posted a while ago
and download there the stock firmware for your country
the instructions on how to return to stock is already posted there
leodasal2 said:
able to go to download mode (check) = your device is still good
just turn off your phone and go to the thread i posted a while ago
and download there the stock firmware for your country
the instructions on how to return to stock is already posted there
Click to expand...
Click to collapse
wait, I flashed the stock kernel via odin. i think its successful, but im still stuck at samsung logo boot. should i still download the stock firmware for my country?
dennisaguilajr said:
wait, I flashed the stock kernel via odin. i think its successful, but im still stuck at samsung logo boot. should i still download the stock firmware for my country?
Click to expand...
Click to collapse
try to wait...
can you now go to recovery mode??
if still stuck, try flashing the whole firmware
after flashing do a "data wipe" + "cache wipe"
BRB ---> dota mode
leodasal2 said:
try to wait...
can you now go to recovery mode??
if still stuck, try flashing the whole firmware
Click to expand...
Click to collapse
yes, i can go to recovery mode, but under it it says
very/log
E:failed to mount /cache
(invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I cant reset my data, cant reset cache. and when I try to reboot, im stuck at Samsung logo.
dennisaguilajr said:
yes, i can go to recovery mode, but under it it says
very/log
E:failed to mount /cache
(invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I cant reset my data, cant reset cache. and when I try to reboot, im stuck at Samsung logo.
Click to expand...
Click to collapse
just flash the stock firmware via odin and it will all be fine
leodasal2 said:
just flash the stock firmware via odin and it will all be fine
Click to expand...
Click to collapse
thanks, it worked, uhh what kernel are you using? can you please share it with me?
dennisaguilajr said:
thanks, it worked, uhh what kernel are you using? can you please share it with me?
Click to expand...
Click to collapse
currently on a "search"
ps: you didn't even press the thanks button for helping you :/
Hey, Guys I had the CM10 Jelly Bean rom downloaded from Rom Manager (I know I shouldnt have used Rom Manager but too late). The rom was giving me problems of low call volume and mic, Losing signal and some other stuff so someone suggested me to use Dark Side Super Wipe and reinstall the rom. I did and Now the phone won't boot up it stays on the CM screen and the Nothing works in the recovery. I tried back and restore doesnt work, Tried installing super wipe again doesnt work. Reseting phone to factory doesnt work. So basically im stuck. I did my search couldnt find anything similar to my problem so I decided to post here. Next step I was going to take is put it on download mode and flash stock rom with ODIN but before I do that I wana get advice from you experts.
I made a short video describing the problem so please take a look to get a better idea of what im talking about. Unfortunately forums wont let me post the links because i have less than 10 posts so please type the title on youtube with my username
Title: Galaxy S2 wont boot up and nothing works in recovery
username: Lshmeet
I will edit and post the link when I have 10 posts to save the hassle.
Dark side wipe broke your recovery. Try installing a new one with Odin.
meekrawb said:
Dark side wipe broke your recovery. Try installing a new one with Odin.
Click to expand...
Click to collapse
Any CM recovery with Odin?
ishmeet10 said:
Any CM recovery with Odin?
Click to expand...
Click to collapse
Yes, but you will need the .tar version to use with Odin.
Edit: Make sure it is for the T989 Hercules.
meekrawb said:
Yes, but you will need the .tar version to use with Odin.
Edit: Make sure it is for the T989 Hercules.
Click to expand...
Click to collapse
Yes i just flashed the recovery-cmw-hercules.tar with Odin and went into recovery but I still see these errors in recovery.
E:Can't open /cache/recovery/log
E:Cant open /cache/recovery/log
E:Cant open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I haven't used cwm for awhile so I'm not sure what those errors mean. The next step is probably Odin to stock, unless anyone else has any ideas.
meekrawb said:
I haven't used cwm for awhile so I'm not sure what those errors mean. The next step is probably Odin to stock, unless anyone else has any ideas.
Click to expand...
Click to collapse
oh man, I got work in the morning and now im stuck with a non working phone How can I put it back to stock thru odin?
Try this:
http://galaxys2root.com/t-mobile-ga...-to-ics-stock-on-t-mobile-galaxy-s2-sgh-t989/
Be super careful and good luck!
Happened to me. Not sure why but the recovery got corrupted for whatever reason. What you need to do is reflash the recovery using ODIN, use the cwm image from the rooting guide.
Thankyou guys I fixed it. Reflashed recovery thru odin and reflashed stock rom. Still get the error in recovery but no issues so far..
For future reference when use the super wipe it wipes everything including your system partition
So basically there was no ROM installed on your phone
Sent from my SGH-T989 using xda app-developers app
Search up twrp odin recovery for sgh-t989
I suggest using this instead of cwm recovery like all the others said. Twrp doesnt have the errors that cwm does twrp is the better recovery
Went from the stock ICS on my cousins phone and updated him to the stock JB through Kies, and now on boot it just gets stuck on the 4g screen.
Also, when I do power+volume+ button it says "E:failed to mount /efs (invalid argument)" and E:Can't mount /efs/log/boot_cause and Can't open /efs/log/boot_cause
Any ideas guys?
Fabiofan said:
Went from the stock ICS on my cousins phone and updated him to the stock JB through Kies, and now on boot it just gets stuck on the 4g screen.
Also, when I do power+volume+ button it says "E:failed to mount /efs (invalid argument)" and E:Can't mount /efs/log/boot_cause and Can't open /efs/log/boot_cause
Any ideas guys?
Click to expand...
Click to collapse
Grab the GB27 odin build from the repository. Flash that. You should be good to go.
Sent from my SPH-D710 using xda premium
Trying to get a log with ADB
graydiggy said:
Grab the GB27 odin build from the repository. Flash that. You should be good to go.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Still no go for me after running rwilco12.com/Files/Devices/Samsung%20Galaxy%20S2%20%28Sprint%29%20%28SPH-D710%29/Stock%20ROMs/JB/GB27/No%20Data%20Restore/Rooted/SPH-D710_GB27_1014481_Rooted_Nodata.exe[/url]
I also tried tGA10_Agats Recovery.exe, wiped the dalvik cache, cache partition, and fixed permissions. Then I ran SPH-D710_GB27_1014481_Kernel.exe to get the stock kernel back.
adb devices
List of devices attached
try the restore, not the nodata
I've tried all of these methods and am having the same issues. I'm very close to just bricking it and calling it a wash. Is there anything at all I can do that will allow me to restore the missing info need for the phone to boot properly?
Could you flash FL24 (restore, NOT nodata) then get the OTA update? I didn't have any luck with flashing GB27.
As graydiggy mentioned try the One-click FULL RESTORE/RESET. Make sure you follow the directions from here. Also run the One-click 'as adminstrator' on your PC too.
Fabiofan said:
Went from the stock ICS on my cousins phone and updated him to the stock JB through Kies, and now on boot it just gets stuck on the 4g screen.
Also, when I do power+volume+ button it says "E:failed to mount /efs (invalid argument)" and E:Can't mount /efs/log/boot_cause and Can't open /efs/log/boot_cause
Any ideas guys?
Click to expand...
Click to collapse
Ok I had the same problem and found a solution! First to get off that bootloop go to rwilco.com and download fl22 and use odin to install it which is ICS, root your phone with the agat 0.6.8 then you go to the play store and download busybox free and gs2 repair. Run busybox do a smart install then open gs2 repair and on the second tab do the 1st and 2nd options only, restart your phone now you can upgrade to jellybean.