guys....... how to reinstall amon ra 1.2.3 recovery image in hero?? my friend's hero is saying
E:can't read MISC:
(No space on device)
E:can't read MISC:
(No space on device)
E:can't read MISC:
(No space on device)
and cant do nandroid backup.
cheers
ReInstall? So its been erased/wiped? There are command prompts in Amon's recovery threads. It is possible to flash it but may be a bit tricky.
dying4004 said:
guys....... how to reinstall amon ra 1.2.3 recovery image in hero?? my friend's hero is saying
Click to expand...
Click to collapse
saying that when you try to do what? the more precise you ask the more precise we can answer. for this question i would give you this thread as an answer:
http://android.modaco.com/content/h...ed-recovery-image-on-your-device-permanently/
i installed amon ra 1.2.3 with flashrec in my friend's hero which got only1 fat32 partition. . then updated to modaco 2.8. but for some reason wifi wasnt working. did nandroid backup and tried some other roms. but wifi dint work. then i went into amonra custom recovery and deleted dalvik cache and did a reboot. then when i went in recovery again it was showing this error message--> E: cant read miscno space left on device). i tried to do a nandroid backup but i said could not run command. cant do nandroid restore. previous error mesage shows always.
i really need this custom recovery back. please guys. some help will be really appreciated. cheers
update......
i went into amon ra recovery mode and installed amon ra 1.2.2 with flash-recovery command with ADB and it installed. but this error message still remains and cant do nandroid back or restore.
E:can't read MISC:
(No space on device)
E:can't read MISC:
(No space on device)
E:can't read MISC:
(No space on device)
I am having this same issue were you ever able to recover????
See the posts towards the end of this thread. Let us know if it works for you.
Related
Hey Guys,
I need some major help in fixing my HTC Incredible S. Phone froze during a mass update using Market. Battery pull, now stuck on HTC boot screen.
- Tried to re-flash CyanogenMod 7.1.0 using ClockworkMod 5.0.2.0 but got this error:
E:Error in /sdcard/cmod/update-cm-7.1.0-IncS-signed.zip (Status 1)
Installation aborted.
- Also ClockworkMod on load gets error:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
-Tried to reformat cache via ClockworkMod but got error:
Error formatting /cache!
- Tried to re-flash ClockworkMod 5.0.2.0 through fastboot but freezes on "Writing ..."
- Tried to re-flash ClockworkMod using PD32img but freezes
- Tried factory reset through bootloader but freezes
- Trying RUU back to stock (Asia) but is currently stuck on "Rebooting to bootloader", it's been over 30 min.
Bootloader Info:
Revolutionary
VIVO PVT SHIP S-OFF RL
HBOOT-6.13.1002
RADIO-3805.04.03.27_M
eMMC-boot
Apr 1 2011,18:34:39
Does anybody know how to fix this? Any help would be greatly appreciated. Thanks!
If you have a Nand, you could just try to nand back.
Try use older version. 4.0 recovery.
Accidentally sent from my Google Nexus S using XDA Premium
I tried updating the recovery but it's not working.
Tried to update using fastboot flash but its stuck at writing 'recovery'...
Tried to update using PG32IMG.zip, it shows the first loading bar but the update prompt doesn't come up.
Also I don't have access to nandroid backup.
dorabeans said:
Also I don't have access to nandroid backup.
Click to expand...
Click to collapse
You don't have a Nand? Or you can't access it because of the way your device is acting? Because if you have a nand, you can Nand back using ADB.
TEAM MiK
Mik Roms Since 3/13/11
prboy1969 said:
You don't have a Nand? Or you can't access it because of the way your device is acting? Because if you have a nand, you can Nand back using ADB.
Click to expand...
Click to collapse
I cannot access adb since I cannot boot into Android. I can only access fastboot. Backup from recovery (clockworkmod) is not available even though I swear I made a backup a while back.
You can do Fastboot ADB. As long as you have it setup. Several threads here on XDA on how to setup Fastboot ADB.
TEAM MiK
Mik Roms Since 3/13/11
dorabeans said:
Hey Guys,
I need some major help in fixing my HTC Incredible S. Phone froze during a mass update using Market. Battery pull, now stuck on HTC boot screen.
- Tried to re-flash CyanogenMod 7.1.0 using ClockworkMod 5.0.2.0 but got this error:
E:Error in /sdcard/cmod/update-cm-7.1.0-IncS-signed.zip (Status 1)
Installation aborted.
- Also ClockworkMod on load gets error:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
-Tried to reformat cache via ClockworkMod but got error:
Error formatting /cache!
- Tried to re-flash ClockworkMod 5.0.2.0 through fastboot but freezes on "Writing ..."
- Tried to re-flash ClockworkMod using PD32img but freezes
- Tried factory reset through bootloader but freezes
- Trying RUU back to stock (Asia) but is currently stuck on "Rebooting to bootloader", it's been over 30 min.
Bootloader Info:
Revolutionary
VIVO PVT SHIP S-OFF RL
HBOOT-6.13.1002
RADIO-3805.04.03.27_M
eMMC-boot
Apr 1 2011,18:34:39
Does anybody know how to fix this? Any help would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
Hey there, I am encountering a similar problem, any luck on sorting it out?
Hi, I'm also having the same problem here with my dads IncS. Since the last post was over a month ago...is there a solution to this problem yet?
Here is the story....
My Desire HD was rooted & S-OFF
It stayed in HTC opening screen when I flashed another ROM
So I found a RUU and flashed it...
and it still can't open (stay in "HTC" screen)
The strange things was that my phone still had CWM ,but the phone became S-ON
and the CWM had errors below...
----------------------------------------------------------------
ClockworkMod Recovery v2.5.1.2 (MoDaCo r2)
E:Can't mount CACHE:recovery/cmmand
E:Can't mount CACHE:recvery/log
E:Can't open CHCHE:recovery/log
----------------------------------------------------------------
I flash another ROM & RUU
even flashed another CMW (flash update.zip)
it still doesn't work....
Please help me
thank you!!!
wantommy said:
Here is the story....
My Desire HD was rooted & S-OFF
It stayed in HTC opening screen when I flashed another ROM
So I found a RUU and flashed it...
and it still can't open (stay in "HTC" screen)
The strange things was that my phone still had CWM ,but the phone became S-ON
and the CWM had errors below...
----------------------------------------------------------------
ClockworkMod Recovery v2.5.1.2 (MoDaCo r2)
E:Can't mount CACHE:recovery/cmmand
E:Can't mount CACHE:recvery/log
E:Can't open CHCHE:recovery/log
----------------------------------------------------------------
I flash another ROM & RUU
even flashed another CMW (flash update.zip)
it still doesn't work....
Please help me
thank you!!!
Click to expand...
Click to collapse
I'd head over to http://forum.xda-developers.com/forumdisplay.php?f=885 and ask there.. probably better chance at getting a quick bit of help..
when switching through windows inside Recovery or trying to wipe cache i get
E: Can't mount /dev/block/mmcblk0p36
(File exists)
E: Can't mount CACHE:recovery/log
E: Can't open CACHE:recovery/log
E: Can't mount /dev/block/mmcblk0p36
(File exists)
im allways rooted/S-OFF
Recovery is Amon Ra 3.15
Ive tried to reflash the Latest RUU. and itll boot and i can use the stock rom but i usually use custom rom
but flashing the latest RUU didnt solve my problam
I am currently formatting my Internal_Sd and mt Sd card to Fat32 right now
ok im stuck on booting after nandroid restore
someone please help!
Stuck where? I would try flashing the kernel for the ROM in the nand and see if that does it.
Also, I've read conflicting info about whether you can restore a nand that was made before updating firmware with an RUU. If any resident experts can comment on this I'd appreciate it as I was going to post a thread asking this.
Did the RUU update yours or was it already running the same firmware?
Also, you were able to boot when on the RUU or no? If yes, you might just flash a ROM fresh rather than restore a nand.
feralicious said:
Stuck where? I would try flashing the kernel for the ROM in the nand and see if that does it.
If not, then give a little history on what you had on before your troubles and what you're trying to get back to, etc...
Click to expand...
Click to collapse
i fallowed this http://forum.xda-developers.com/showthread.php?t=1615969&page=3
im not getting the error inside the recovery anymore. im about to try a nandroid restore
Boot was completely successful. everything is fixed
(thread closed)
I have been trying to get to JB for the past couple of days, but I think I've screwed something up and I'm not sure how bad.. After some frustration with my PC giving me an error when sending the JB boot.img, (which magically decided to work 10 hours later with an ICS boot.img) I wanted to get my phone back to the 4.1 ICS rom I was using with NAND backup (Tron 1.2). I got it to show the correct bootscreen. I loaded the boot.img with fastboot and it stayed on the boot screen for 30 mins.
I found out that my Amon Ra was old and I used "fastboot flash recovery" to update 3.15. Between the NAND restore and the Amon Ra update, I noticed that when I accessed recovery it would and still does pop up with this immediately.
RA Revamped
Build : RA-VIGOR-v.3.15 - getitnowmarketing
E: Can't mount /dev/block/mmcblk0p36
(file exists)
E: Can't mount CACHE: recovery/command
E: Can't mount /dev/block/mmcblk0p36
(file exists)
E: Can't mount CACHE: recovery/log
E: Can't open CACHE: recovery/log
E: Can't mount /dev/block/mmcblk0p36
(file exists)
From what I've read with similar errors on other devices, the internal memory is screwed up and I need a new device. whomp whomp. Not a huge deal ultimately, but I would love to avoid that and continue with this device. Any ideas?
Here's some extra info:
2.25.0000
1.22.10.0421r/1.22.10.0424r
mainver 1.00.000.0
JayToTheMo said:
I have been trying to get to JB for the past couple of days, but I think I've screwed something up and I'm not sure how bad.. After some frustration with my PC giving me an error when sending the JB boot.img, (which magically decided to work 10 hours later with an ICS boot.img) I wanted to get my phone back to the 4.1 ICS rom I was using with NAND backup (Tron 1.2). I got it to show the correct bootscreen. I loaded the boot.img with fastboot and it stayed on the boot screen for 30 mins.
I found out that my Amon Ra was old and I used "fastboot flash recovery" to update 3.15. Between the NAND restore and the Amon Ra update, I noticed that when I accessed recovery it would and still does pop up with this immediately.
RA Revamped
Build : RA-VIGOR-v.3.15 - getitnowmarketing
E: Can't mount /dev/block/mmcblk0p36
(file exists)
E: Can't mount CACHE: recovery/command
E: Can't mount /dev/block/mmcblk0p36
(file exists)
E: Can't mount CACHE: recovery/log
E: Can't open CACHE: recovery/log
E: Can't mount /dev/block/mmcblk0p36
(file exists)
From what I've read with similar errors on other devices, the internal memory is screwed up and I need a new device. whomp whomp. Not a huge deal ultimately, but I would love to avoid that and continue with this device. Any ideas?
Here's some extra info:
2.25.0000
1.22.10.0421r/1.22.10.0424r
mainver 1.00.000.0
Click to expand...
Click to collapse
upgrade to amon ra 3.16 and see if it helps:
link
place zip on root of sd card
rename it PH98IMG.zip
boot into hboot
accept the install
reboot phone
(remember to remove zip when you are done)
synisterwolf said:
upgrade to amon ra 3.16 and see if it helps:
link
place zip on root of sd card
rename it PH98IMG.zip
boot into hboot
accept the install
reboot phone
(remember to remove zip when you are done)
Click to expand...
Click to collapse
Thanks for replying. I did the update and it's giving the same errors.
Try wiping it under mounts. Worked for me.
Flyhalf205 said:
Try wiping it under mounts. Worked for me.
Click to expand...
Click to collapse
I'm sorry, I'm not quite sure what you mean. Are you talking about choosing "Wipe" and wiping cache or doing something under "Mounts"? Because I don't have an option to wipe anything under "Mounts".
I tried to wipe cache earlier but I get the same error plus:
Error mounting /cache/!
Skipping format...
/cache wipe complete!
To go ahead and put this out there, I get failures with "Wipe ALL data/factory reset"
Formatting DATA:....
E: Can't mount /dev/block/mmcblk0p35
(File exists)
Error mounting /data/!
Skipping format....
Formatting SDCARD:.android_secure...
Formatting INTERNALSD:.android_secure...
E: Can't mount /dev/block/mmcblk037 (or /dev/block/mmcblk0p38)
(Invalid Argument)
Error mounting /internal_sdcard/.android_secure!
Skipping format...
Formatting CACHE:...
E: Can't mount /dev/block/mmcblk0p36
(File exists)
Error mounting /cache/!
Skipping format
Skipping format of /sd-ext
Userdata wipe complete!
Running the ruu should fix your problem
Sent from my Nexus 7 using Tapatalk HD
Go into the stock ROM than go to settings than storage and erase the SD card in there and it should fix those partitions.
Edit: also 3.16 version of the recovery is out if you want to update it
Sent from my ADR6425LVW using xda app-developers app
dottat said:
Running the ruu should fix your problem
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
That did it, I'm on 4.2.2 now! Thanks a ton!
Help!
JayToTheMo said:
That did it, I'm on 4.2.2 now! Thanks a ton!
Click to expand...
Click to collapse
I am having this issue. I have tried running the RUU from my computer and it is not solving the problem. It keeps giving me an "Error 155:Unknown"
Insydr4God said:
I am having this issue. I have tried running the RUU from my computer and it is not solving the problem. It keeps giving me an "Error 155:Unknown"
Click to expand...
Click to collapse
Can you download the 605.12 version in the PH98IMG format and then put that on your SD card and boot into hboot ?
Androidpolice has a link to the ph98img version of the ruu....that will take the PC out of the loop for you and let the phone take care of the update.
Sent from my Nexus 7 using Tapatalk HD
I have an unlocked bootloader. According to the Android Police article I found it will not flash with a locked bootloader. I think I also have Amon Ra installed as that is what I used to root in the first place.
Insydr4God said:
I have an unlocked bootloader. According to the Android Police article I found it will not flash with a locked bootloader. I think I also have Amon Ra installed as that is what I used to root in the first place.
Click to expand...
Click to collapse
so relock and flash it. have you tried yet?
For what it's worth.. i didn't relock my bootloader and simply flashed it. I then re-flashed recovery and used a ph98img file to change my hboot back to the modded 2.27 version (I am s-off so the phone simply doesn't care anymore).
Insydr4God said:
I have an unlocked bootloader. According to the Android Police article I found it will not flash with a locked bootloader. I think I also have Amon Ra installed as that is what I used to root in the first place.
Click to expand...
Click to collapse
It's the opposite of that. You need to be locked to run an RUU. Amon Ra won't matter to run an RUU, once you have run it you will have stock recovery and stock ROM. Then you can unlock again and flash Amon Ra or TWRP.
Also, be very patient when you run it. It should run through twice - it goes to a black screen for a bit then goes back to bootloader and goes through the updating process again. It will let you know when it's done, could take up to 15 min or so.
I tried relocking and flashing the build with the global update. I haven't had a chance to download the previous build to see if it works. The 4.0.x build told me that boot was older. Before trying to root again I had downloaded all the OTA updates. I am in so far over my head.. LOL
Insydr4God said:
I tried relocking and flashing the build with the global update. I haven't had a chance to download the previous build to see if it works. The 4.0.x build told me that boot was older. Before trying to root again I had downloaded all the OTA updates. I am in so far over my head.. LOL
Click to expand...
Click to collapse
If it makes you feel any better I'm in the same boat with the sd card, i've tried the ruu, the sd patch from other threads, formatted the card to fat32 on the pc and still no luck. The Infected 2.5 Rom runs great though just cant get the sd card to show up.
blueblazer96 said:
If it makes you feel any better I'm in the same boat with the sd card, i've tried the ruu, the sd patch from other threads, formatted the card to fat32 on the pc and still no luck. The Infected 2.5 Rom runs great though just cant get the sd card to show up.
Click to expand...
Click to collapse
Are you sure its not a hardware issue? Sorta sounds like it if hboot doesn't see the sdcard either. Did you try a different card?
Well...before I tried that I must have done something wrong while trying to fix that so now I can't get past the boot loader lol, so working on that now, just gonna try to get it all back to stock and start over.
Sent from my Nexus 7 using Tapatalk 2
I unlocked the bootloader on my HTC Desire x(Android 4.1.1.), install CWM recovery, and I get these error massages on the bottom of the recovery screen:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
I tried the TWRP, but the same errors appeared. Finally, I try to flash a ROM, but after the HTC logo, it shows a black screen. Before the flash, I took a backup, but the recovery can't restore it!! I took it a service and they fixed it. But in the recovery still the same errors. I can't install the supersu, too. It successfully flash the zip, I have got the superuser app, but haven't got root access!
Pls help me!
(sorry, if my English was wrong)
levi555 said:
I unlocked the bootloader on my HTC Desire x(Android 4.1.1.), install CWM recovery, and I get these error massages on the bottom of the recovery screen:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
I tried the TWRP, but the same errors appeared. Finally, I try to flash a ROM, but after the HTC logo, it shows a black screen. Before the flash, I took a backup, but the recovery can't restore it!! I took it a service and they fixed it. But in the recovery still the same errors. I can't install the supersu, too. It successfully flash the zip, I have got the superuser app, but haven't got root access!
Pls help me!
(sorry, if my English was wrong)
Click to expand...
Click to collapse
bro try to flash twrp recovery by ur pc and after that flash a rom of our device (htc desire x)
shyvam said:
bro try to flash twrp recovery by ur pc and after that flash a rom of our device (htc desire x)
Click to expand...
Click to collapse
The TWRP recovery is very buggy, and it give me the same error. I wrote, I ty to flash a rom from TWRP and CWM too, but I've got bootloop. It cant mount the cache, as a result, cant make full nandroid backups, or restore it. The ROM change isn't help
I solved the problem, I just installed the stock recovery, and than flash the TWRP for JB Hboot 5.0.0(thanks ckpv5 for the links), and the errors disappeared!! I installed SU, and I successfully got root access!
I can use root apps, and they works, but I cant uninstall system apps!
I try som apps from Geegle Play, but doesnt work. The System app remover uninstalls it perfectly, but when I reboot, the uninstalled apps coming back to the phone!! I try to uninstall the apks from the system/app, but the same result. Can I flash a ROM with theese problem? I dont want to brick my device, please help!