Develop Bugs

Can't Nandroid backup. eh?

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^^^

[FIXED] Help!Cant flash any recovery images

Ever since I updated to the last OTA I have lost clockworks recovery image. Thus now I am unable to install the latest froyo rom.
I have tried to install the latest clockworks recovery image and Amon_Ra recovery through Rom Manager. Each time it states it is installed but everytime I try to boot up to the recovery image it gives me the following error:
E: Can't open /cache/recovery/command
and it just gives me the Android System Recover <2e>
Any help would be appreciated....

It sounds like you are not rooted.
If you accepted the OTA from Sprint using your system update on your phone, you are no longer rooted and will not have a custom recovery/root permissions. You will be unable to flash any custom recovery/ROMS/delete any sprint apps/Other Root only things until someone comes up with a way to root 2.2.
Have a drink in hopes that a dev will come up with a way to Root 2.2 soon!

I didnt update over the phone
What happened is I installed a rooted verson of 1.47.651.1 but in doing that it got rid of the recovery image... it definetly a rooter version because i can run apps that require root.. such as wife tether titanium back etc...
any other suggestions...

coolguycarlos said:
I didnt update over the phone
What happened is I installed a rooted verson of 1.47.651.1 but in doing that it got rid of the recovery image... it definetly a rooter version because i can run apps that require root.. such as wife tether titanium back etc...
any other suggestions...
Click to expand...
Click to collapse
there's an update.zip around here somewhere that will allow you to boot into an early form of clockwork recovery.
so, assuming that you goofed something, but still have nand unlocked....
find that update.zip. put it and a .zip for a real recovery onto your sdcard. boot into hboot, let it run the update.zip, that will take you to koush's early clockwork recovery. use that recovery to flash a solid recovery.
done.
alternative method would be to use fastboot to erase the recovery partition, then put a new recovery in.

Here is the update.zip...Just extract Recovery.zip....Do this OR/AND what the Senior Member above said and you should be good

timothydonohue said:
there's an update.zip around here somewhere that will allow you to boot into an early form of clockwork recovery.
so, assuming that you goofed something, but still have nand unlocked....
find that update.zip. put it and a .zip for a real recovery onto your sdcard. boot into hboot, let it run the update.zip, that will take you to koush's early clockwork recovery. use that recovery to flash a solid recovery.
done.
alternative method would be to use fastboot to erase the recovery partition, then put a new recovery in.
Click to expand...
Click to collapse
I actually tried the update.zip one already and it doesnt install... it will stated that the signature cant be verified and it will about the installation... havent tried the fastboot approach... I guess I will need to find out how to do that now

so from the looks of it I am screwed... I have hboot .79 if that matters and from the looks of it the rooted rom i installed screwed up my nand unlock.. which is why i think i can install any recovery images... i tried alot of the nand unlock tutorials and most of them I eventually get to a point were i need to write to /data and i cant because permissions are denied... great... oh well i'll keep on trying... any suggestions are appreciated...

If you still have super user, try this...same thing happend to me.
http://forum.xda-developers.com/showthread.php?t=744621&page=4

I'm having a very similar problem also. My Hboot is 0.79.000 too & after trying clockworkmod recovery, a few RUU update attempts, and attempting to change ROMs completely (not in that order) I'm at a loss, no success anywhere. I can't even get in to recovery anymore. It just reverts back to Bootloader menu where my options are Reboot, Reboot Bootloader, or Power down (& I think there is one other option that i tried and sent me back to the aforementioned screen). However, I can still load my pre-existing ROM...
Does anyone have any ideas if there is anything I can do?
TIA

topdawgn8 said:
If you still have super user, try this...same thing happend to me.
http://forum.xda-developers.com/showthread.php?t=744621&page=4
Click to expand...
Click to collapse
I have a question bout this... I seen this before but the sdk that I downloaded for Windows 7 does not have the Su command... any ideas on how I can get it for Windows 7?
Sent from my PC36100 using XDA App

Nevermind I got the Su command to work
Sent from my PC36100 using XDA App

you can erase recovery from rom manager and try to reflash. i would recommend reinstalling rom manager just to make sure it installed correctly. it installed bad on me once and corrupted my recovery trying to update it, reinstalled and installed an old recovery then the newest one and it worked.

Thanks for the suggestions all. I followed the instructions from link you posted using terminal emulator. No such luck, still reading HBOOT 0.79.0000 and running same ROM.
I also tried reinstalling (several times) clockworkmod recovery images and it effects nothing.
Should I try to completely unroot my phone again? If the images i just flashed didn't do it what will?
Im totally at a loss here. ARG!

hit there jtwonbly.......are you also running the stock rooted 1.47.651.1?

Build number 1.47.651.1 CL195459 release-keys

yea same here......and what is it that your trying to do...go back to stock ROM?

I'd like to go to any other ROM. Its as if I'm no longer rooted anymore.
I think I may try to start all over again using NeckFaces old tutorial on unlocking NAND w/o adb. I'm just not sure if that will fix the HBOOT file because I can't get in to Recovery.

OK Guys thanks for all your help but I have been able to get it fixed now!!!
I pretty much had to redo all of Toast Root tutorial and NAND unlock to get it working. Both Part 1 and Part 2 even though I was already running a rooted rom.
The original problem I had is I kept getting told to just try the nand unlock in part 2 but the phone wasnt having it. It wouldnt like the engineering build of the pc36img.zip
So I started from Part 1. Downloaded the rooted rom pc36img.zip and what do you know it finally let me install it. By the time I was done with both parts 1 and 2 I was able to flash a recovery image, get back to hboot .76 and I am now another proud owner of an Evo running a rooted Froyo!!!!

[Q] Rooting gone wrong/ I've made a big mistake

Hi everyone, I'm hoping someone can help me out here because I've screwed up somehow and would like to un-do whatever it is I've done. I'm trying to think straight so I hope what I type out ends up making sense .
1. Right now, my phone works. I'm stuck on a rooted pre-OTA stock rom. I unrooted once, but was not able to flash the OTA update via the stock recovery. I still have a use-able phone so I'm doing better than some people in threads I've read about.
2. I tried to root it with gfree. I don't think it worked, and some errors came up during the process. I used the first method then skipped to 0.2 per the wiki. Using g-free verify tells me everything is alright. supercid, sim lock, etc.
3. I am s-off, but earlier I couldn't get gfree verify to work (my own error I'm certain) and assumed I screwed up. Rom manager and root explorer never gave me prompts for superuser permissions, but I was s-off. I didn't think I rooted correctly and used the rage against the cage method.
4. Right now, I'm apparently s-off and rooted. I can't flash any roms though. I use rom manager to flash the latest recovery, it says it works and then when I reboot to recovery it stays stuck on the HTC splash screen. Battery pull takes me back to the pre-OTA rom. Recovery only recently stopped working though.
Ultimately, I need to get recovery back somehow, and then I'd return my phone back to an unrooted state with the stock 2.2 rom since I can't seem to handle rooting to well. Since I have no clockwork mod recovery, not really sure what to do to get this process rolling. If someone can help me get recovery back, and then help me flash roms again I'd definitely appreciate it. I have noone to blame but myself here.
If it ends up mattering, I do have adb installed and can use that if need be, and like I said my phone still boots up. I don't have a brick but something crazy is going on.

tjmarchand said:
Hi everyone, I'm hoping someone can help me out here because I've screwed up somehow and would like to un-do whatever it is I've done. I'm trying to think straight so I hope what I type out ends up making sense .
1. Right now, my phone works. I'm stuck on a rooted pre-OTA stock rom. I unrooted once, but was not able to flash the OTA update via the stock recovery. I still have a use-able phone so I'm doing better than some people in threads I've read about.
2. I tried to root it with gfree. I don't think it worked, and some errors came up during the process. I used the first method then skipped to 0.2 per the wiki. Using g-free verify tells me everything is alright. supercid, sim lock, etc.
3. I am s-off, but earlier I couldn't get gfree verify to work (my own error I'm certain) and assumed I screwed up. Rom manager and root explorer never gave me prompts for superuser permissions, but I was s-off. I didn't think I rooted correctly and used the rage against the cage method.
4. Right now, I'm apparently s-off and rooted. I can't flash any roms though. I use rom manager to flash the latest recovery, it says it works and then when I reboot to recovery it stays stuck on the HTC splash screen. Battery pull takes me back to the pre-OTA rom. Recovery only recently stopped working though.
Ultimately, I need to get recovery back somehow, and then I'd return my phone back to an unrooted state with the stock 2.2 rom since I can't seem to handle rooting to well. Since I have no clockwork mod recovery, not really sure what to do to get this process rolling. If someone can help me get recovery back, and then help me flash roms again I'd definitely appreciate it. I have noone to blame but myself here.
If it ends up mattering, I do have adb installed and can use that if need be, and like I said my phone still boots up. I don't have a brick but something crazy is going on.
Click to expand...
Click to collapse
Download ClockworkMod Recovery straight from Koushik's page and put it on the root of your SD card. Open up Terminal Emulator on your phone and type in the following:
su
flash_image recovery recovery-clockwork-3.0.2.4-vision.img
reboot recovery
Click to expand...
Click to collapse
Post the results in here.

blackknightavalon said:
Download ClockworkMod Recovery straight from Koushik's page and put it on the root of your SD card. Open up Terminal Emulator on your phone and type in the following:
Post the results in here.
Click to expand...
Click to collapse
Hey thank you so much for a response! I tried this with two sd cards because I didn't have any luck. I tried that exact command and flash_image recovery /sdcard/recovery-clockwork-3.0.2.4-vision.img and each time it returns flash_image: not found
It definately is on my sd card.

tjmarchand said:
Hey thank you so much for a response! I tried this with two sd cards because I didn't have any luck. I tried that exact command and flash_image recovery /sdcard/recovery-clockwork-3.0.2.4-vision.img and each time it returns flash_image: not found
It definately is on my sd card.
Click to expand...
Click to collapse
Do you have the engineering bootloader? If not, you may have to try it with ADB.

blackknightavalon said:
Do you have the engineering bootloader? If not, you may have to try it with ADB.
Click to expand...
Click to collapse
Im fairly certain I had to flash it to root with the rage method, vol + pwr screen says "vision pvt eng s-off hboot 0.76.2000 (pc1010000)"
With adb it gives me the same error, but I used rom manager to flash 2.5.1.3 so I have a recovery again. I have one good nandroid of the rom im stuck on.
My next issue is that I tried to flash the stock rom with root from http://forum.xda-developers.com/showthread.php?t=836042 and something isn't right. I wipe data/cache and then go to install zip from sdcard (manual recovery) and select the rom. What happens after is it tells me the normal messages it gives when flashing and "welcome to vision" but when the flash is done instead of giving me the option of "reboot system now" it goes back to the install zip for sd card menu like the flash never happened (and it will not boot past the htc screen)

tjmarchand said:
Im fairly certain I had to flash it to root with the rage method, vol + pwr screen says "vision pvt eng s-off hboot 0.76.2000 (pc1010000)"
With adb it gives me the same error, but I used rom manager to flash 2.5.1.3 so I have a recovery again. I have one good nandroid of the rom im stuck on.
My next issue is that I tried to flash the stock rom with root from http://forum.xda-developers.com/showthread.php?t=836042 and something isn't right. I wipe data/cache and then go to install zip from sdcard (manual recovery) and select the rom. What happens after is it tells me the normal messages it gives when flashing and "welcome to vision" but when the flash is done instead of giving me the option of "reboot system now" it goes back to the install zip for sd card menu like the flash never happened (and it will not boot past the htc screen)
Click to expand...
Click to collapse
Maybe it's a bad recovery. You said you flashed 2.5.1.3, so ROM Manager should work. Try flashing 3.0.2.4 through there now. If not, I suggest downloading Fastboot.

tjmarchand said:
Hey thank you so much for a response! I tried this with two sd cards because I didn't have any luck. I tried that exact command and flash_image recovery /sdcard/recovery-clockwork-3.0.2.4-vision.img and each time it returns flash_image: not found
It definately is on my sd card.
Click to expand...
Click to collapse
flash_image isn't part of the stock ROM, I made a guide for using it: http://forum.xda-developers.com/showthread.php?t=902493

raitchison said:
flash_image isn't part of the stock ROM, I made a guide for using it: http://forum.xda-developers.com/showthread.php?t=902493
Click to expand...
Click to collapse
Thanks for the guide! I followed it with no issue, I rebooted into recovery; it first hung on the HTC screen, rebooted, vibrated and then booted back into the OS. So anyway, instead of 2.5.1.3, I'm on 3.0.0.5 now.
I went down to 2.5.1.3 and downloaded cm6.1 via rom manager. It told me this : E: can't open '/sdcard/..location (bad) installation aborted. tmp/recovery.log was copied to sdcard
I tried enom's froyo themed rom next, heres what recovery tells me:
Installing update...
Formatting cache
Copying files
Formatting SYSTEM
Copying files...
E Can't symlink /system/bin/su
E Failure at line 19:
symlink /system/xbin/su SYSTEM: bin/su
Installation aborted.
I also tried to download an updated superuser from the market, it says installation unsuccessful package file was not signed correctly.

Use Titanium to update your Superuser.apk
Sent from a Western Union telegram.

blackknightavalon said:
Use Titanium to update your Superuser.apk
Sent from a Western Union telegram.
Click to expand...
Click to collapse
That worked, so thank you. I ended up unrooting and putting s back on so I can retry. Now, I can't flash the OTA update via stock recovery. Any ideas for that one? Thank you so much for all the other help as well.
"E:Can't open /cache/recovery/command" -when I first enter recovery
--Install from sdcard...
Finding update pacakge...
Opening update pacakge...
Verifying update package...
E:failed to verify whole file signature
E: signature verification failed
Installation aborted. -after trying the OTA (named update.zip of course)

tjmarchand said:
That worked, so thank you. I ended up unrooting and putting s back on so I can retry. Now, I can't flash the OTA update via stock recovery. Any ideas for that one? Thank you so much for all the other help as well.
"E:Can't open /cache/recovery/command" -when I first enter recovery
--Install from sdcard...
Finding update pacakge...
Opening update pacakge...
Verifying update package...
E:failed to verify whole file signature
E: signature verification failed
Installation aborted. -after trying the OTA (named update.zip of course)
Click to expand...
Click to collapse
If this is the Gingerbread OTA, you'll need everything as stock. If it's the "OTA" with Superuser thrown in, you'll need CWM Recovery 3+ (2.5* formats the system in yaffs, 3+ formats it in EXT).

This is just the ota update with wifi calling still 2.2, Im unrooted and stock recovery again
Sent from my T-Mobile G2 using XDA Premium App

Rooting issues Desire!

Tried to root my Desire with unrevoked.
First i ran the rooting tool, got an message saying Failed to get root. Is your firmware too new? - Solved this with a factory reset of the phone. Then i ran the unrevoked software again.
Everything went smooth, til i booted up recovery.
I got this:
E:Can't find MISC:
E:Can't find mount CACHE :recovery/command
E:Can't find MISC:
E:Can't find mount CACHE : recovery/log
E:Can't find MISC:
Read around some and found out that it is due the clockwork is not compatible with PTV4(?) So I figured, i'll run the Unrevoked rooting procedure again, but this time with a custom recovery (RA Amon 2.0.1)
Unrevoked pushing recovery, reboots, Running root, bam! now i get this message on my Desire:
“the application zysploit (process com.unrevoked.zysploit) has stopped unexpectedly."
What do I do now?
What will happen if I do another Factory reset this time? as I got root rights now?

http://forum.xda-developers.com/showthread.php?t=913084
If u s-off The problem goes away.

Jakedude2011 said:
http://forum.xda-developers.com/showthread.php?t=913084
If u s-off The problem goes away.
Click to expand...
Click to collapse
So if I run the alpha s-OFF CWM will work? and I do not need to run the rooting procedure again? Or is there any other way to solve this without s-off?

In the link there is other solutions to, but S-OFF helped me. And u dont need to run the rooting procedure again.and Yes cwm will work with all features.

Jakedude2011 said:
In the link there is other solutions to, but S-OFF helped me. And u dont need to run the rooting procedure again.and Yes cwm will work with all features.
Click to expand...
Click to collapse
This can be done with the stock rom? The phone is rooted but I have not changed ROM, but it should work, right?

Yep. I to did it with a STOCK ROM.
Alpharev S-Off:
1. Download Alpha Rev.iso
2. Burn .iso image to CD with IMGburn
3. Boot from CD on your PC
4. Press enter when prompted
READ AND UNDERSTAND!! the warning, and plug in your turned on phone with usb cabel

Jakedude2011 said:
Yep.................
Click to expand...
Click to collapse
Looks like i got it to work, without S-OFF the phone. I Uninstalled the Zysploit app and ran the procedure again, but this time with RA Amon Recovery. Thanks for the help.

no poblem... glad it worked out for u.
But remember with S-OFF u have a lot more options,
but it can wait until one day u wanna do something that requires s-off.

Cant mount /devblock/mmcblklp2

Hello, I was in the middle of installing a new rom and my phone went into a boot loop. I took the battery out and then restarted the phone. When I did this Every time I go into recovery I get the message E: cant mount /dev/block/mmcblk0p2 (file exists).
I can get into recovery but every rom I try to load leaves the phone in a boot loop. I have searched the internet for a solution but I can find one and the one I did find I cant understand. I asks me to use the adb shell and I havent used this in over a year and cant really remember all the scripts to make it work.
I am running clockwork mod 2.5.1.2 i also did the unrevoked s-off. If anyone can walk me through a solution or point me in the direction of one that would be great. Also I wasnt sure where to post this so if Its in the wrong place just let me know and I can repost there.

I'm pretty sure anything before CWM 3.x uses update-script, while almost every rom now uses updater-script. Try updating CWM to 5.0.2.0 and then flashing a rom.
Sent from my ADR6300 using XDA App

This should be in the Q&A section, not developement.
That being said the above post by teerom is probably correct.

I tried loading the cwm 5.0.2.0 zip like I would any other zip and I got the same message. Am i doing something wrong?

bdolan said:
I tried loading the cwm 5.0.2.0 zip like I would any other zip and I got the same message. Am i doing something wrong?
Click to expand...
Click to collapse
Yeah. First download this file:
http://www.mediafire.com/?s7gyn7raxbs2lab
Rename it to PB31IMG.zip and place it on the root of your SD card. Boot your device into HBOOT (Power + Volume Up) and follow the instructions to install the new recovery. Then try flashing a ROM.

MY MANN!!! how you guys know how to fix these phones when they get all messed up is crazzy. Thank you sooo much for getting me back on my droid...Ive been working with my old palm pre plus... THanks again.

bdolan said:
MY MANN!!! how you guys know how to fix these phones when they get all messed up is crazzy. Thank you sooo much for getting me back on my droid...Ive been working with my old palm pre plus... THanks again.
Click to expand...
Click to collapse
Glad I could help
Sent from my ADR6300 using XDA App