I really hope anyone can help me
atleast maybe just pointing me to the right guides or info would be really appreciated.
after flashing leedroid it said installation from sd card completed and i was back in recovery menu (rom manager 2.0.1.5) but when i pressed back btn i think it crashed, nothing more happend (i.e. i never got the reboot now menu option) so i took out the battery. Now it won't boot, stuck at white/green HTC logo.
When i go inte to recovery, instead of the clockworkmod custom recoveryscreen it's (blue text) Android system recovery 2e and i get error E:Can't open /cache/recovery/command and E:Can't open /data/data/recovery/log
I have working nandroid (via rom manger) backup that i would like to restore.
As i said help/pointers would be very appreciated. Maybe i can simply apply fake flash image again and try a different ROM? i just don't want to mess up the phone any more then i have already have
Desire 0.80 with latest radio
I had that last night, what I did was to re-root my phone then did a recovery from a backup I had.
Sent from my HTC Desire using XDA App
ribbox said:
I had that last night, what I did was to re-root my phone then did a recovery from a backup I had.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Thanks! what root method did you use? MoDaCo r6 riskfreeroot?
SOLVED
So i managed to solve this.
as i hadn't lost root i could simply copy fake flash update.zip and follow the fake flash instructions @ modaco here
so in recovery i ran update.zip which loaded the custom rom and allowed me to run a nandroid recovery
now Bob's my uncle
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
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.
I rooted my phone using ODIN. And tried to backup efs by using an app called efs backup.
the phone randomly restarted and kept reeboting..I went into the recovery and it said e:unable to mount /efs
I did a factory reset
Installed stock rom using odin
NOthing seems to be working..
What can I do?
raddums said:
I rooted my phone using ODIN. And tried to backup efs by using an app called efs backup.
the phone randomly restarted and kept reeboting..I went into the recovery and it said e:unable to mount /efs
I did a factory reset
Installed stock rom using odin
NOthing seems to be working..
What can I do?
Click to expand...
Click to collapse
DO you have a custom Recovery installed? If so, there might be a conflict between the stock ROM and I backup. Try going to recovery, wipe cache and then wipe data(factory reset) and reboot. The first boot takes A lot of time, so as long as the boot animation doesn't loop but does indeed stay n the Samsung text, you are OK
idealisti said:
DO you have a custom Recovery installed? If so, there might be a conflict between the stock ROM and I backup. Try going to recovery, wipe cache and then wipe data(factory reset) and reboot. The first boot takes A lot of time, so as long as the boot animation doesn't loop but does indeed stay n the Samsung text, you are OK
Click to expand...
Click to collapse
NO i had the stock recovery..
When I reflashed the stock rom it stayed on the samsung logo.. how much time does it take?
The stock recover shows the error in red E:unable to mount /efs (invalid argument)
Maybe something went wrong on your backup. So it had some residue instructions it was doing on boot up. I had a similar problem when triangle away crashed while hacking. I did a 'adb reboot' command which I think cleared any nasty commabd and let it reboot normally.
Think of these as those please reboot to apply chances updates on winfows
Sent from my GT-N7100 using XDA Premium 4 mobile app
raddums said:
NO i had the stock recovery..
When I reflashed the stock rom it stayed on the samsung logo.. how much time does it take?
The stock recover shows the error in red E:unable to mount /efs (invalid argument)
Click to expand...
Click to collapse
your solution lies here http://forum.xda-developers.com/showpost.php?p=39523753&postcount=4
but now since u dont have custom recovery i blv u need other way out rather flash the pit partition file first before flashing the stock rom post 4 has the pit file http://forum.xda-developers.com/showthread.php?t=1896696
shhbz said:
your solution lies here http://forum.xda-developers.com/showpost.php?p=39523753&postcount=4
but now since u dont have custom recovery i blv u need other way out rather flash the pit partition file first before flashing the stock rom post 4 has the pit file http://forum.xda-developers.com/showthread.php?t=1896696
Click to expand...
Click to collapse
It says the device should be rooted..I have reflashed the stock firmware..Its not rooted..
is my phone dead?
Any Solutions guys?? please
raddums said:
Any Solutions guys?? please
Click to expand...
Click to collapse
follow the other way out after flashing pit then the stock rom if u still cant just take it to sc instead screwing it more instead falling into any big isuues
Phone powers on gets to AT&T logo and stops.
Tried installing Clockworkmod but now when I hold power, home and volume up screen scrambles.
I canstill get into Download mode.
Before I installed Clockworkmod I got an E: failed to mount /efs (invalid argument) when clearing cache and wipe factory reset.
Rooted phone and thought I could just install a new mod like cyanogen but cannot get cwm to work now.
Help please. been going in circles looking for factory reset images etc paying for download sites etc.
Dbschall71 said:
Phone powers on gets to AT&T logo and stops.
Tried installing Clockworkmod but now when I hold power, home and volume up screen scrambles.
I canstill get into Download mode.
Before I installed Clockworkmod I got an E: failed to mount /efs (invalid argument) when clearing cache and wipe factory reset.
Rooted phone and thought I could just install a new mod like cyanogen but cannot get cwm to work now.
Help please. been going in circles looking for factory reset images etc paying for download sites etc.
Click to expand...
Click to collapse
Try using this method to get the phone working again then once your done and have the phone rooted then in odin flash the recovery in the pda or ap slot in odin and you'll be good to go
http://forum.xda-developers.com/showthread.php?t=2802189