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)
Related
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.
Hi peeps
(I've tried looking for related posts but nothing comes up with my stuff)
I have downloaded Rom Manager Premium and also downloaded clockwork recovery, how ever every time I reboot into recovery to install i get this
E:failed to verify whole-file signature
E:signature verification failed
I have flashed the file before using Odin but i get other stuff saying E: cant mount (random stuff)
My phone is rooted
What am i doing wrong?
Rom Manager & CWRecovery don't work together on the SGS2. It's one or the other. For example, if you have CWRecovery installed (as a result of rooting your phone with a CFRoot kernel, for example), using Rom Manager has a tendency to break CWRecovery and/or put your phone into a bootloop.
So you're going to have to decide what you want to use.
Also
I have noticed I have Clockwork recovery once and I flashed a new ROM and i was left with the stock recovery. Is that normal too?
Depends what you used/did to flash the new rom. If you flashed it in CWRecovery, then that's unusual for it to be broken purely by flashing a custom rom meant for a I9100/T. Not completely unheard of mind you, but not usual.
If you used Rom Manager to flash the rom when you already had CWRecovery installed, then as per my previous post, it's obvious CWRecovery was broken by Rom Manager.
Again as per my previous post, one or t'other. Up to you. But use both at your peril.
olster said:
Also
I have noticed I have Clockwork recovery once and I flashed a new ROM and i was left with the stock recovery. Is that normal too?
Click to expand...
Click to collapse
So would you recommend that I remove ROM manager and just flash CW Recovery?
I wouldn't recommend you do anything/use one over the other. I'm just saying that you run the risk of having major problems (bootloop/broken CWRecovery) if you have both on your phone/try to use both.
Personally speaking, I've never had a problem rebooting my phone into CWRecovery every/any time I want to flash a rom/kernel/backup/restore.
Up to you which you use.
olster said:
So would you recommend that I remove ROM manager and just flash CW Recovery?
Click to expand...
Click to collapse
It looks like Im having problems with my boot recovery as I try to use clockwork its saying cant mount, even trying to access SD CARD.
Is there a way of clearing every thing and starting again?
Also when I use clockwork recovery
Anything I try to do i get this
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
What rom/kernel are you running and how did you root your phone ?
You could try flashing a CFRoot kernel from here, if that doesn't work you should probably get your stock firmware from here and flash that in Odin. After that you can use a CFRoot kernel to root your phone.
That will give you a clean slate with CWRecovery working.
Edit to add - Yes, you're getting that in CWRecovery because Rom Manager obviously broke it as I've already said.
olster said:
It looks like Im having problems with my boot recovery as I try to use clockwork its saying cant mount, even trying to access SD CARD.
Is there a way of clearing every thing and starting again?
Click to expand...
Click to collapse
I am using 2.3.6 XWKK5 ROM with the CF-Root-SGS2_XW_OXA_KK5-v5.0-CWM5.tar
Then try my suggestions in my previous post.
Right, I have managed to start again and got it working again.
Thanks your help
NP. Glad you got it working
olster said:
Right, I have managed to start again and got it working again.
Thanks your help
Click to expand...
Click to collapse
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
Hello, All.
It seems I'm pretty close to bricking this thing so I thought I would ask you guys for help.
I'm not that experienced with this kind of stuff, but I was able to unlock my bootloader, and installed a custom recovery TWRP, using the Droid_Incredible_4G_LTE_All-In-One_Kit_v2.1 from hasoon2000,
It won't let me install a rom to the device. Been having some trouble with ADB as well. Seems like it won't recognize the phone when it's on the bootloader menu, but it will when it's in recovery mode. So using ADB i pushed a rom file to the device while in recovery and was able to get it on the sd card, but when I try to load the rom using TWRP it gives me an error msg. I thought that I might have to get rid of the old OS first before loading a new one so now I don't have an OS at all.
I feel like I'm missing something here, like I skipped a step or something... do i need to flash the kernel, or relock the bootloader? Confused as to why I can't load up a rom.
Thanks in advance for any help. Much appreciated.
Neon Samurai said:
Hello, All.
It seems I'm pretty close to bricking this thing so I thought I would ask you guys for help.
I'm not that experienced with this kind of stuff, but I was able to unlock my bootloader, and installed a custom recovery TWRP, using the Droid_Incredible_4G_LTE_All-In-One_Kit_v2.1 from hasoon2000,
It won't let me install a rom to the device. Been having some trouble with ADB as well. Seems like it won't recognize the phone when it's on the bootloader menu, but it will when it's in recovery mode. So using ADB i pushed a rom file to the device while in recovery and was able to get it on the sd card, but when I try to load the rom using TWRP it gives me an error msg. I thought that I might have to get rid of the old OS first before loading a new one so now I don't have an OS at all.
I feel like I'm missing something here, like I skipped a step or something... do i need to flash the kernel, or relock the bootloader? Confused as to why I can't load up a rom.
Thanks in advance for any help. Much appreciated.
Click to expand...
Click to collapse
before flashing a rom you should go into the wipe menu of twrp and wipe everything. Then install the rom zip. What error are you getting when try to flash the rom?
Sorry for the late response. I guess I don't really check my email without a smartphone.
Ok so in TWRP I go into wipe, and do Cache - Successful! Davik Cache - Successful! System: Successful! Factory Reset - Failed (and in the list it says:
updating partition detail...
unable to mount '/sdcard' a buncha times.
Then if i try to install a rom from the sd card it says
Failed
Installing 'external_sd/rom.zip'...
checking for MD5 file...
Skipping MD5 check: no MD5 file found.
assert failed: write_raw_image('tmp/boot.img". "boot"
E:Error in /external_sd/rom.zip
)Status 7)
Error flashing zip 'external_sd/rom.zip'
Updating partition details...
E:Unable to mount '/sdcard'
E:Unable to mount '/sdcard'
I guess what makes no sense to me is that it can't mount the sd card. Does it need to be on the internal "sdcard" instead of the mini sd I have the file on? IDK so confused...
Thanks for you help.
Bug...
Hi, Ok auto kill is good but i have a real problem... I like reminders app that Google Keep vs Evernote, but i don't can use. I set the reminder note for tomorrow and when time is coming, i don't have any notification/ remained... Help me please!
Hello,
Yesterday I unlocked my Galaxy S3 i9300, turned the Wifi on and soon after that my phone started to reboot.
This happened a few times before, but this time it got stuck on the "Galaxy S3" Screen.
So I booted in the Recovery Mode (TWRP 3.1.10) and was planning to wipe the cache partition, but I got the Error that the Recovery is unable to mount Any Partition..
So I cant do anything.
I wanted to ask, why my phone can not mount any Partitions anymore for example (system, efs, cache..).
What exatly is damaged and is it repairable?
I took a picture of the Error Message, but i dont know how to upload it. So I wrote it down.
Hope someone can help me and sorry for my bad english.
Kind Regards.
Error Message:
Updating partition details...
Failed to mount ´/efs´(invalid argument)
Failed to mount ´/cache`(invalid argument)
Failed to mount ´/system´(Invalid argmunent)
Failed to mount ´/data´(Invalid argmunent)
Failed to mount ´/preload´(Invalid argmunent)
Flash stock rom via Odin. Root it and try again.
ArdaCsknn said:
Flash stock rom via Odin. Root it and try again.
Click to expand...
Click to collapse
I am facing same errors. in these type of error i can't flash with odin, can't hard reset, can't install any recovery, i have tried many roms but all failed. i was thinking about to re-partition it but there is a file required for this .pit file. i have searched on google but i didn't find any .pit file for my Samsung S3 SHV-E210k. i have asked in thread but no response from anyone. so i am thinking to threw my phone away. :crying: :crying: :crying:
E30325i said:
Hello,
Yesterday I unlocked my Galaxy S3 i9300, turned the Wifi on and soon after that my phone started to reboot.
This happened a few times before, but this time it got stuck on the "Galaxy S3" Screen.
So I booted in the Recovery Mode (TWRP 3.1.10) and was planning to wipe the cache partition, but I got the Error that the Recovery is unable to mount Any Partition..
So I cant do anything.
I wanted to ask, why my phone can not mount any Partitions anymore for example (system, efs, cache..).
What exatly is damaged and is it repairable?
I took a picture of the Error Message, but i dont know how to upload it. So I wrote it down.
Hope someone can help me and sorry for my bad english.
Kind Regards.
Error Message:
Updating partition details...
Failed to mount ´/efs´(invalid argument)
Failed to mount ´/cache`(invalid argument)
Failed to mount ´/system´(Invalid argmunent)
Failed to mount ´/data´(Invalid argmunent)
Failed to mount ´/preload´(Invalid argmunent)
Click to expand...
Click to collapse
Try to find .pit file and flash it with odin. and then flash your stock rom.
My phone's model is SHV-E210K, i have searched on google but haven't found any .pit file related to my phone.
The sboot.bin file is the bootloader and it is not flashing because the bootloader in the phone is newer than than the bootloader in the ROM, the ROM is not for the phone, try a different USB cable, and/or try different USB ports.
The problem is recovery has gone crazy. Recovery mounts partitions. I've seen this problem a lot with twrp. When it happened to me I flashed the latest official cwmr via Odin. If you have a stock rom on the phone you can flash a stock recovery too. DO NOT FLASH A STOCK RECOVERY IF YOUR ROM ISN'T STOCK/ROOTED STOCK!!!
Beamed in by telepathy