I have a rather confusing problem that requires knowledgeable folks.I will lay out the entire situation to the best of my ability. Please, read through to the end. A few things that should be clarified: I am a 48 year old adult who is fairly skilled with tech. Linux, however is a bit of a weak point. I am pretty intelligent, methodical, and thorough. I researched my phone project well, and was operating from clear instructions. I met several problems along the way, and spent about 30 hours reading, researching, and attempting things before i exhausted my resources and posted here. I point these things out from the start because I abhor taking the time to write a detailed post requesting information, only to get one line answers telling me to "look it up." That being said, here is the situation.
Equipment
T-Mobile Samsung Galaxy S (SGH-T959V)
Stock USB data transfer cable
Desktop computer running Windows 8.1 64 bit
Software Used/Available
Android SDK
Odin 3 v1.85
Heimdall v1.4rc1 win32
Heimdall v1.4rc2 win32
Semaphore 2.7.4
CyanogenMod 10.1.3 galaxysmtd
CyanogenMod 10.2.0 galaxysmtd
Procedure
I began by following the procedure detailed on the CynaogenMod site (wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd) It instructed me to download Semaphore's ClockworkRecovery Mod and Heimdall, boot into download mode, and flash the kernel, which I did, though it was not trouble free. Heimdall had trouble sending the data, but after fiddling a bit with drivers and cables, it completed.
Continuing on their instructions, I downloaded CyanogenMod 10.2.0 and placed it on the root of the sdcard using adb (adb push cm-10.2.0-galaxysmtd.zip /sdcard/) I then booted to recovery mode and performed the following actions in this order:
Select and execute the option to wipe data/factory reset.
Select install zip from sdcard.
Select choose zip from sdcard.
Select the CyanogenMod file you placed on the sdcard.
Optional: Install any additional packages you wish using the same method.
Once the installation finished, returned back to the main menu, and selected the reboot system now option.
At this point, the device should have booted into CyanogenMod.
Instead, It started to load cyanogen, but stalled at "Waiting for /sdcard to mount", counted down from 20 to 0, and then rebooted, ad infinitum.
Current Status
Now, it boots into CWM-based Recovery v6.0.4.5, and the following printout under the command list:
E: failed to find "cache" partition to mount at "/cache"
E: failed to find "cache" partition to mount at "/cache"
E: Can't mount /cache/recovery/command
E: failed to find "cache" partition to mount at "/cache"
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: failed to find "cache" partition to mount at "/cache"
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: failed to find "cache" partition to mount at "/cache"
E: failed to find "cache" partition to mount at "/cache"
Error mounting /cache!
I can't boot into download mode. I cannot mount /cache, /datadata, /system, or /data. I cannot format them, either. I have tried a few times from badly worded instruction posts to push the file again and install from zip, but heimdall fails saying "Is a directory." I dont understand sideloading sufficiently to use it, but I suspect it wouldn't help until i can resolve the mounting issue.
Things I Have Tried, and why they didn't work
In googling "cant mount /sdcard" issues, I have seen many posts suggesting to "Use Odin and revert to stock." Currently, when my phone is plugged into USB, my computer recognizes only two disk drives, both classed as "Linux File - CD Gadget USB Device" Odin doesn't see it at all, and I suspect that it is because it isn't in download mode, and the compter doesnt see it as a phone. If there is a way around this, i would be grateful to hear it.
I have also seen a few posts suggesting to "reflash cwm_mod." I assume this is suggesting that by reverting to just a clean system and CWM, I could try to install the mod, or a stock rom, again. I do not know how this is possible when I cant mount /sdcard. It seems that this single issue is the crux of the matter.
Request For Help
I am totally stumped. I am willing to work with anyone who can either walk me through some steps or point me to a well written resource. I have looked up many guides, but frankly, a lot of them are so poorly written as to be nearly incomprehensible. All siggestions are humbly accepted, and greatly appreciated. I will be home all day, and in front of the computer waiting.
Thank you for reading.
If you can get into download mode try this.
http://forum.xda-developers.com/showthread.php?t=2258628
☞Sent from here☜
Hey I was in the same boat as you, try this and it will take you back to gingerbread but you will be able to reflash newer updates and mods.
just click the download link in the thread and open it after you download.
Then put your phone into download mode to connect with heimdall and once it says connected click the flash button and once its done you'll be back to stock gingerbread.
I was stumped for a few days because I thought I had to use odin but its very simple heres the link to the thread.
http://forum.xda-developers.com/showthread.php?t=1358498
baseballfanz said:
If you can get into download mode try this.
http://forum.xda-developers.com/showthread.php?t=2258628
☞Sent from here☜
Click to expand...
Click to collapse
You did like me; I didn't realize this post is referring to a Galaxy S 4G, not the Galaxy S4. I don't believe you'd want to follow that particular bit of advice being that it's not the same model.
Related
Hi there,
I used Cyanogenmod 1.1 beta for a while and while I was pretty happy about it, it did have some issues i wasn't very fond of. So I decided to to perform a nandroid restore of my stock rom and succeeded. My stock rom kept crashing when trying to use internet (synchronising, browsing etc). While messing a little with the settings (like no account syncing etc) my phone crashed and it went into an infinite bootloop. I went into recovery, did the neccesary wipes and performed a nandroid recovery to my Cyanogenmod again. It errored while doing so (can't remember exactly what the line was, but was something like unable to format...something).
Now when I boot into recovery it displays the following information:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Any idea's? I know there is a lot to find about this on the internet and this forum but they're all guides from other devices and don't know if it would be wise to follow them
Help would be appreciated!
Clockworkmod v4.0.1.4
Eisken said:
Hi there,
I used Cyanogenmod 1.1 beta for a while and while I was pretty happy about it, it did have some issues i wasn't very fond of. So I decided to to perform a nandroid restore of my stock rom and succeeded. My stock rom kept crashing when trying to use internet (synchronising, browsing etc). While messing a little with the settings (like no account syncing etc) my phone crashed and it went into an infinite bootloop. I went into recovery, did the neccesary wipes and performed a nandroid recovery to my Cyanogenmod again. It errored while doing so (can't remember exactly what the line was, but was something like unable to format...something).
Now when I boot into recovery it displays the following information:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Any idea's? I know there is a lot to find about this on the internet and this forum but they're all guides from other devices and don't know if it would be wise to follow them
Help would be appreciated!
Clockworkmod v4.0.1.4
Click to expand...
Click to collapse
What happens when you attempt to enter RECOVERY and format CACHE?
Did you at any point in this boot loop process pull the battery?
ben_pyett said:
What happens when you attempt to enter RECOVERY and format CACHE?
Did you at any point in this boot loop process pull the battery?
Click to expand...
Click to collapse
When doing cache wipe:
Formatting /cache...
Cache wipe complete.
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I did not pull the battery out except for the infinite bootloop I mentioned earlier.
Eisken said:
When doing cache wipe:
Formatting /cache...
Cache wipe complete.
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I did not pull the battery out except for the infinite bootloop I mentioned earlier.
Click to expand...
Click to collapse
Sorry, I'm afraid that I must be the bearer of bad news ....I believe that by pulling out the battery you have ruined the eMMC chip in the device, this appears to be a flaw or defect with a selection of recent HTC devices.
I believe that the only thing you can do is to return the device for warranty or to attempt to get the chip replaced.
Here are a selection of similar threads, within this forum which also cover this problem and I believe that you should be able to find others......
http://forum.xda-developers.com/showthread.php?t=1165304
http://forum.xda-developers.com/showthread.php?t=1150917
http://forum.xda-developers.com/showthread.php?t=1226849
Thanks for your reply!
Too bad there is nothing to do about it. I'll just send it in for repair then.
having the same problem.. so should i try to wipe the cache and see what happens?
I fixed that by going into recovery and wiping the cache. It still says that it is unable to mount but re-flashing the ROM fixed all that.
I've tried that quite a few times, but it always failed to flash the rom. Did you get errors when flashing the rom?
What errors do you get when you're installing the ROM?
If you are still able to go into recovery then....
Do you have EXT4 recovery installed?
If not 1) Download this FILE which is EXT4 recovery 2) then copy it onto your SD card 3) enter recovery and flash the EXT4 ZIP file 4) Reboot Recovery
Then look at what format the existing CACHE partition is in?
OK i seem to be the next one with this Problem.
But for now it isn't a real problem, the following happended:
Used Hydrogen for some weeks, but wanted to try the new Virtuous Unity. So i did a backup of my apps with titanium, booted into recovery, flashed the Virtuous Rom, Install was complete and after that it says the known E: cant't mount ... and so on.
After that i pressed restart now in ext4 recovery and the Rom booted as it should. I restored my apps, everything is ok. But now i'm a little scared what will happen next
So is this the normal "way" it goes, or did i just have luck? I'm thinking about going back to s-on and stock, if this is possible.
Btw i didn't pull out the battery ever, cause i knew this could brick my ds, and i never had a bootloop or something like that.
Hope someone can give me some tips.
Cheers
EbiEre said:
OK i seem to be the next one with this Problem.
But for now it isn't a real problem, the following happended:
Used Hydrogen for some weeks, but wanted to try the new Virtuous Unity. So i did a backup of my apps with titanium, booted into recovery, flashed the Virtuous Rom, Install was complete and after that it says the known E: cant't mount ... and so on.
After that i pressed restart now in ext4 recovery and the Rom booted as it should. I restored my apps, everything is ok. But now i'm a little scared what will happen next
So is this the normal "way" it goes, or did i just have luck? I'm thinking about going back to s-on and stock, if this is possible.
Btw i didn't pull out the battery ever, cause i knew this could brick my ds, and i never had a bootloop or something like that.
Hope someone can give me some tips.
Cheers
Click to expand...
Click to collapse
The good news here is that you recovered from this problem and also that you didn't pull battery, so we can rule that out as being the cause in your case.
Between the Installation/flashing of the second ROM did you perform the necessary WIPES?
You may well have done, but, just in case, I'd always recommend that you take a full Nandroid backup of an existing system ROM before moving and flashing another (just to have a fall back position in case)?
@ EbiEre
I got scared after reading those lines too. Nothing to worry about. Just keep flashing roms as usual . Just a cache error. If you didnt pull out the battery, and if the rom booted, then everything is ok.
Yeah but I'm scared because I think it could brick "really".
I don't think it is sure that it only happen if i pull out the battery isn't it?
For now I'm back at the stock tom, it's OK but to be honest I love to root my phone and flash rims, and so maybe I will root again
Thx for your answers
EbiEre said:
Yeah but I'm scared because I think it could brick "really".
I don't think it is sure that it only happen if i pull out the battery isn't it?
For now I'm back at the stock tom, it's OK but to be honest I love to root my phone and flash rims, and so maybe I will root again
Thx for your answers
Click to expand...
Click to collapse
Can only echo the comments of @.sh4d0w.
We all take a minor risk of bricking our devices with the majority of commands and flashes that we do.....but we still do them because that's half the fun...
Did you ever examine the format types ie EXT3/EXT4 of each partition using the EXT4 recovery?
Alright guys, I've got a question. I have my brothers nexus s that has had CM9 A11 on it and we decided to move to the latest CM9. Long story short, I am no longer able to boot the phone up, but can only access CWM Recovery and Bootloader/Fastboot mode. Trying to boot results in a bootloop. I need help getting this thing back to stock however I can. I've tried to flash recovery.img via fastboot but cannot get my computer to recognize the phone in order to do what I need. He would like his phone back ASAP and I hate to tell him its bricked for a few days. Thanks!
Download full OTA ROM from the link in my signature. Boot into CWM, mount USB storage, and transfer the file to SD card. Flash it. Done.
Just make sure you download the correct ROM for your phone model.
Sent from my Nexus S using xda premium
Video on that page will show you how to install drivers on a windows-based machine to recognise the phone for fastboot, and provide files to do so.
Also, can't you go into CWM --> mounts and storage --> mount usb storage (while plugged into the computer) then copy over any files you need, then flash through recovery.
I forgot to mention that I am getting this when trying to format cache:
E:Can't find misc
E:failed to find "cache" partition to mount at "/cache"
E:Can't mount /cache/recovery/command
E:Can't find misc
E:failed to find "cache" partition to mount at "/cache"
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to find "cache" partition to mount at "/cache"
E:Can't mount /cache/recovery/latest_log
E:Can't open /cache/recovery/latest_log
E:Can't find misc
E:failed to find "cache" partition to mount at "/cache"
I tried to install the OTA update like you said but got the following:
assert failed: write_raw_image("/tmp/boot.img".
"boot")
E:Error in /sdcard/(OTA file name here)
(status 7)
Installation aborted.
Maybe the internal SD card is bad? Any thoughts?
When you get the drivers installed, download the latest 5.0.2.0 CWM from here.
Alright, so I got fastboot to recognize the phone, but am having another problem. It gave me an error when I gave the command to flash the new CWM. I tried to install pdanet for the drivers, and the phone says at the bottom "FASTBOOT STATUS - FAILInvalid Command". I really think something has been corrupted, any ideas on how to fix it/restore it? Thanks for all the help guys.
Fastboot status is not a command.
Fastboot devices is the command you use to test if it sees the device . The serial number will show.
uh oh sounds like someone flashed brickROM V1
Sent from my Nexus S 4G using XDA App. Developer of brickROM, and OP of XDA Thread of The Year 2011.
So, I have a Sprint HTC One (M7) that I tried to root following this guide:
http://www.xda-developers.com/how-to-root-the-htc-one-m7-and-install-recovery-xda-developer-tv/
Custom Recovery was flashed successfully (I tried both TWRP 2.5 and CWM 6.0.4.6), and I immediately got the following errors:
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
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
I can't access /cache, in short. So, I tried to find my SD card, but my phone doesn't have a slot for one, and I couldn't figure out how to write to the virtual one inside the phone, so I passed SuperSU-v2.46.zip through sideload, and it failed when it couldn't access cache. I was then rather foolish, and tried to just flash a ROM from Android Revolution HD, found on this thread:
http://forum.xda-developers.com/showthread.php?t=2265618 (I used this particular ROM:Android_Revolution_HD-One_92.0_4a9d05.zip).
Again, I passed it using sideload because I don't have an SD card. The install formatted my partitions, then at 30% (when it began to copy files), it failed. Thus, I was left with an empty phone, but an unlocked bootloader. I tried a few more things, to no avail.
I think if I could figure out how to put something in the virtual SD inside, that might get me there, since I'm guessing that it's formatting over the location of the installer/image. Also, I found that if I use the "Wipe /cache" from CWM, I don't get those errors, but then I can't reboot into the recovery again, so I'm guessing that it's saving it in the /cache partition. I use the command "fastboot flash recovery CWM_image.img" to put my recovery in there.
Anyway, any ideas or help would be nice. I know enough to be dangerous, but clearly not enough to get myself out of this mess. Any help would be appreciated.
Hi there
You'd be best served asking for help from the experts who own your device, here
So you came at XDA-Developers to find help? (Beginners Thread)
Good luck
So, I have a Sprint HTC One (M7) that I tried to root following this guide:
http://www.xda-developers.com/how-to...-developer-tv/
Custom Recovery was flashed successfully (I tried both TWRP 2.5 and CWM 6.0.4.6), and I immediately got the following errors:
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
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
I can't access /cache, in short. So, I tried to find my SD card, but my phone doesn't have a slot for one, and I couldn't figure out how to write to the virtual one inside the phone, so I selected "Install zip" option in CWM and passed SuperSU-v2.46.zip through sideload, and it failed when it couldn't access cache. I was then rather foolish, and tried to just flash a ROM from Android Revolution HD, found on this thread:
http://forum.xda-developers.com/show....php?t=2265618 (I used this particular ROM:Android_Revolution_HD-One_92.0_4a9d05.zip).
Again, I passed it using sideload because I don't have an SD card. The install formatted my partitions, then at 30% (when it began to copy files), it failed. Thus, I was left with an empty phone, but an unlocked bootloader. I tried a few more things, to no avail.
I think if I could figure out how to put something in the virtual SD inside, or somehow protect the install files from being overwritten during the install, that might get me there, since I'm guessing that it's formatting over the location of the installer/image. Also, I found that if I use the "Wipe /cache" from CWM, I don't get those access cache errors, but then I can't reboot into the recovery without flashing it again, so I'm guessing that it's saving it in the /cache partition. I use the command "fastboot flash recovery CWM_image.img" to put my recovery in there, which may be a part of the problem.
Anyway, any ideas or help would be nice. I know enough to be dangerous, but clearly not enough to get myself out of this mess. Any help would be appreciated, and at this point, it would just be nice to have any OS on my phone. All HTC recovery software fails because they require a locked bootloader, but my computer won't detect a phone with no OS and a locked bootloader...
Duplicate.
http://forum.xda-developers.com/general/xda-assist/odd-problems-trying-to-root-htc-one-m7-t3164965
I am totally new to rooting, not sure what I've done wrong.
I started trying to root my SM-J727P by installing TWRP with Odin. This works fine, then I added the superSU v2.82 file to the device's microSD card. I went to install tab in TWRP recovery mode->select storage->Micro SD card->superSU.
Then when I try to flash it, a red message appears saying "Could not mount /data and unable to find crypto footer. Failed to mount /data (Invalid Argument). At the bottom it says "Failed to mount /system (Device or Resource Busy). Failed to mount /data (Invalid Argument.)
After this I read that I need to format storage.
I went to wipe->format data->typed yes and the same message appears, "Failed to mount /system (device or resource busy).
I'm extremely new to this so I don't really know what I'm talking about but do I need to disable dm-verity?
Any help would be greatly appreciated.
ColoPhone said:
I am totally new to rooting, not sure what I've done wrong.
I started trying to root my SM-J727P by installing TWRP with Odin. This works fine, then I added the superSU v2.82 file to the device's microSD card. I went to install tab in TWRP recovery mode->select storage->Micro SD card->superSU.
Then when I try to flash it, a red message appears saying "Could not mount /data and unable to find crypto footer. Failed to mount /data (Invalid Argument). At the bottom it says "Failed to mount /system (Device or Resource Busy). Failed to mount /data (Invalid Argument.)
After this I read that I need to format storage.
I went to wipe->format data->typed yes and the same message appears, "Failed to mount /system (device or resource busy).
I'm extremely new to this so I don't really know what I'm talking about but do I need to disable dm-verity?
Any help would be greatly appreciated.
Click to expand...
Click to collapse
I now have manually mounted system and no errors showed, after tapping reboot system, the phone entered a bootloop. Not sure if this is supposed to happen or not and if it is, how long does it take?
ColoPhone said:
I now have manually mounted system and no errors showed, after tapping reboot system, the phone entered a bootloop. Not sure if this is supposed to happen or not and if it is, how long does it take?
Click to expand...
Click to collapse
This happened to me when I was doing my first root with samsung. What I did was completely start over with a new stock ROM and TWRP. Be sure you have all the right things ticked on Odin. What I had to do with my sm-j700p was un-tick auto-restart when done, and when the TWRP was done flashing, I had to remove the battery instead of wait for it to shut down. Then QUICKLY go into recovery mode by pressing the buttons after you turn it back on. Flash ROM. If I remember correctly, I was so good from there, but the timing with samsung when pushing the buttons apparently is EVERYTHING.
And making sure it is the correct TWRP file. I also made the mistake of picking the wrong TWRP file. Same model and carrier...different year of phone. Software version number is where it's at to get the best info.
Good luck!