I had originally run RegawMOD rooter on 1.13.651.1 and the phone ran great. Yesterday, I decided to do LazyPanda S-OFF and then try out some of the 1.22.651.3 ROMs. LazyPanda said everything completed successfully. I went into TWRP, wiped System/Cache/Dalvik, then went to install a ROM but it failed because it couldn't mount sdcard2. I read through the LazyPanda thread and noticed that there were sometimes data loss issues with the SD card - no biggie, I had all my data backed up. I didn't have an adapter on hand to hook up the SD card directly to the computer, so I went out and picked up a SD card + adapter combo.
Today, I put the brand new SD card into the device and boot into TWRP; however TWRP takes a long time to boot. I look at the console spew and there are a bunch of "E:failed to mount /sdcard (invalid argument)" errors and even a "E:failed to mount /cache (invalid argument)" one. Of course, this is the internal memory. I'm pretty sure I didn't see these errors last night, so I'm not sure what happened between then and now.
So my question is: how do I get back to a usable state? I don't care about losing any of the data (it's backed up elsewhere), I just need a working phone.
Trioculus said:
I had originally run RegawMOD rooter on 1.13.651.1 and the phone ran great. Yesterday, I decided to do LazyPanda S-OFF and then try out some of the 1.22.651.3 ROMs. LazyPanda said everything completed successfully. I went into TWRP, wiped System/Cache/Dalvik, then went to install a ROM but it failed because it couldn't mount sdcard2. I read through the LazyPanda thread and noticed that there were sometimes data loss issues with the SD card - no biggie, I had all my data backed up. I didn't have an adapter on hand to hook up the SD card directly to the computer, so I went out and picked up a SD card + adapter combo.
Today, I put the brand new SD card into the device and boot into TWRP; however TWRP takes a long time to boot. I look at the console spew and there are a bunch of "E:failed to mount /sdcard (invalid argument)" errors and even a "E:failed to mount /cache (invalid argument)" one. Of course, this is the internal memory. I'm pretty sure I didn't see these errors last night, so I'm not sure what happened between then and now.
So my question is: how do I get back to a usable state? I don't care about losing any of the data (it's backed up elsewhere), I just need a working phone.
Click to expand...
Click to collapse
I have had this problem before. It started when I booted twrp without my external ad card,then when I put it back in it recognizes it but it somehow got the sd ext mixed up with int sd so it tried to write roms to the ext sd,no matter how many times I reset it to recovery its still the same. The only solution I have found was to re-flash twrp I was using 2.18 or something now on 2.2 and I would recommend it. Here's how I fixed it easy. Downloaded evo 4g lte toolbox from the lte dev forum (not sure if its the orig forum or not),installed and opened toolbox,installed HTC drivers from toolbox,restart my phone in bootloader (vol-d+power) went into fastboot and clicked on push recovery from toolbox,reset into recovery and viola everything mounts properly. I am htcdev unlocked and I'm not sure if its different when your s-off. You should still be able to push recovery from fastboot. Let me know if this works
Sent from my EVO using xda premium
I wasn't able to find the toolbox you mentioned; however I was able to resolve the problem. I ended up running the RUU mentioned here to restore the internal memory to a installable state.
Trioculus said:
I wasn't able to find the toolbox you mentioned; however I was able to resolve the problem. I ended up running the RUU mentioned here to restore the internal memory to a installable state.
Click to expand...
Click to collapse
When in recovery touch mount and then touch external card so there is an x in the box then back out then touch the second choice thing with like two or three dots and select sdcard. that is what I did
PS: TOUCH SO THERE IS A DOT NEXT TO USING EXTERNAL SDCARD AT THE BOTTOM - THEN BACK OUT AND DO ABOVE.
No internal memory
Trioculus said:
I wasn't able to find the toolbox you mentioned; however I was able to resolve the problem. I ended up running the RUU mentioned here to restore the internal memory to a installable state.
Click to expand...
Click to collapse
So are you saying you completely unrooted your phone and went back to step one to fix this problem? I am trying to get my internal memory back myself.
if this happens again, there have been reports that mounting your phone to windows while in TWRP and formatting it will fix the issue. no need to RUU...but atleast it fixed your problem :victory:
Have same mounting issues with TWRP
bog3nator said:
if this happens again, there have been reports that mounting your phone to windows while in TWRP and formatting it will fix the issue. no need to RUU...but atleast it fixed your problem :victory:
Click to expand...
Click to collapse
I'm using samsung galaxy i9001. Have installed TWRP. But unable to access sd card on PC.
where can I find this format option?
Related
So I flashed the latest nightly 9-2-02 and I kept on getting the error in my camera app external device storage needed. I figured the problem was not with my sdcard, but with my internal sdcard folder. When I go to flash via recovery, it says e:/unable to mount internal sd card. Is there anyway to remount this card?
I have Hboot 1.15, s-on. I know some other people have been having this problem, anybody have any ideas?
midfieldmaestro said:
So I flashed the latest nightly 9-2-02 and I kept on getting the error in my camera app external device storage needed. I figured the problem was not with my sdcard, but with my internal sdcard folder. When I go to flash via recovery, it says e:/unable to mount internal sd card. Is there anyway to remount this card?
I have Hboot 1.15, s-on. I know some other people have been having this problem, anybody have any ideas?
Click to expand...
Click to collapse
it may some how have gotten corrupted. update twrp to the latest if you dont have it (2.2.2) and then boot into recovery and do a back up, go to advanced and install htc dumlock and reboot, i dont personally like dumlock but it is the most flexible solution barring a few extra steps, go into apps and launch dumlock, here it will write recovery to boot and then reboot directly into twrp because you technically no longer have a boot, it has been replaced by twrp, then go to advanced again and restore boot and go back to menu, go to wipe select internal, this will reformat it, then do the usual factory reset, wipe cache, dalvik, system and then flash cm10, gapps, and reboot, if all goes well you can go ahead and flash any extras you might have had prior
note: with dumlock there is no need to fastboot the kernel, with dumlock in boot it can write directly, the reason this method isnt the most ideal is that you are writing to boot multiple times but like i said i think it is the most flexible for newer users
om4 said:
it may some how have gotten corrupted. update twrp to the latest if you dont have it (2.2.2) and then boot into recovery and do a back up, go to advanced and install htc dumlock and reboot, i dont personally like dumlock but it is the most flexible solution barring a few extra steps, go into apps and launch dumlock, here it will write recovery to boot and then reboot directly into twrp because you technically no longer have a boot, it has been replaced by twrp, then go to advanced again and restore boot and go back to menu, go to wipe select internal, this will reformat it, then do the usual factory reset, wipe cache, dalvik, system and then flash cm10, gapps, and reboot, if all goes well you can go ahead and flash any extras you might have had prior
Click to expand...
Click to collapse
Thank you for this explanation, but I believe (thanks to a user from the CM10 thread) that it is indeed corrupted like you said. But instead of going through that, I went and mounted my internal drive via TWRP to my computer. So I have a macosx (ugh) and I reformatted it, but it had trouble doing it and it didn't work properly. Normally in windows it would do a much better job as you are able to set it FAT32 etc etc. So when my phone started up, the phone recognized it was a corrupted drive and repaired it itself, and voila, everything is working, I am able to side load apps and actually download things.
well i wrote those directions to give you the best chance at getting it to work, I always prefer a fresh start when possible. my instruction is also non reliant on a computer which to me is also a plus as windows/mac/and linux can interfere with usb. Glad to hear you got it working
Formatting work
I would like to thank everyone who posted, I rebooted my EVO to TWRP recovery, mounted the USB drive and connected to my windows PC. The USB drive popped up and windows asked if I wanted to fix it, I said yes and formatted as fat32 adn after unmounting and rebooting, the sdcard mounted perfectly!
Thanks you!
g_brownell said:
I would like to thank everyone who posted, I rebooted my EVO to TWRP recovery, mounted the USB drive and connected to my windows PC. The USB drive popped up and windows asked if I wanted to fix it, I said yes and formatted as fat32 adn after unmounting and rebooting, the sdcard mounted perfectly!
Thanks you!
Click to expand...
Click to collapse
So you got the internal to work.
Have you had any issues with mounting the external?
Hi guys,
My phone started to reboot itself every 5-10 minutes today. I rebooted into recovery and loaded a backup from a week ago. Now it loads and I get Unfortunately, the process com.android.phone has stopped and it repeats. I never get service.
I've wiped, put on a different ROM, same thing. When I try to wipe internal storage I get an error.
I'm s-off 1.12 hboot
radio 1.02.11.0423_2
I don't know what to do.. Do I have to relock, ruu, then re-root? If so, which RUU?
Any easier fixes?
Thanks
Mount internal storage to pc using twrp, it should say the internal needs to be formatted. You can also try fix permissions and clearing app data for any apps that force close.
om4 said:
Mount internal storage to pc using twrp, it should say the internal needs to be formatted. You can also try fix permissions and clearing app data for any apps that force close.
Click to expand...
Click to collapse
thanks but no dice.. i did that and now when i try to wipe in recovery it fails and isnt installing any zips (downloaded 2 new ones).
i get this:
Install /sdcard/stock w goodies.zip
finding update package..
opening update package..
installing update.
e: error in /sdcard/stock with... zip
above that i see
Using rm -rf of 'dev/block/mmcblk1p1'
e:tw_format_rmfr: unable to locate volume for device "dev/block/mmcblk1
and
e:tw_format_rmfr: unable to locate volume for device "dev/block/mmcblk0
that seems bad
phone hosed? should i try to ruu? i dont want to lose root so im not sure which one to use or what process
No no, mount storage to pc. Go to mount select internal card and hit mount storage and plug it into pc, and it will read as a flash drive. It will recognize it as a corrupt card and tell you that it needs to be formatted. Twrp will not recognize corrupted cards.
om4 said:
No no, mount storage to pc. Go to mount select internal card and hit mount storage and plug it into pc, and it will read as a flash drive and it will recognize it as a corrupt card and tell you that it needs to be formatted
Click to expand...
Click to collapse
i did.. and formatted.. and it didnt work. it formatted but now still no dice.. i stupidly tried to flash a rom and it failed so now i don't even have that..
I thought you were saying you tried to wipe inside of twrp. Ok that is odd
om4 said:
I thought you were saying you tried to wipe inside of twrp. Ok that is odd
Click to expand...
Click to collapse
i am.. thats when it says it fails and the error i posted..
but i had tried formatting in windows as you said. when i do that they both show up, clean
You can try ruu, it should wipe the phone and install everything factory
om4 said:
You can try ruu, it should wipe the phone and install everything factory
Click to expand...
Click to collapse
I just formatted again on both. Then I added a zip from my PC and it flashed without failing. It booted so we are good. Not sure why didnt work first time around or what caused it in first place.
Think it could have caused the reboots every few mintues earlier today? I hope thats fixed.. otherwise i got a phone dying lol.
THanks again!
It may have just been something simple like a kernel problem. Sometimes everything flashes and you boot android but it doesn't agree with the kernel and it reboots. Sometimes it's because something has been corrupted. Make back ups, keep a copy on pc and it would be handy to keep a wipe script in case you ever have to start over. It's easier to just flash a wipe script and then flash a rom
You should try getting a new sd. I've seen this happen with sd's that are starting to fail. Not saying this is your issue but its something to look into.
\Root-Hack_Mod*Always=LTE
I know there are a couple of other threads out there, but I want to make sure I get the right solution for my problem...
Hboot 1.12
S-ON
I've been running SuperLTE 2.0 for a few weeks, and when i plugged into the charger last night it started bootlooping. In TWRP I cleared both caches, but I am unable to mount the internal SD CARD and bootloops continued. I am able to mount the external SD just fine...
I've made no other changes while I ponder a solution. Looking at other threads, should I try reformatting the SD somehow, run an RUU (which one? never done that...), or run one of the twrp advanced menu apps like dumloc?
Solved, see third reply...
Well at least your not alone. I am running Stock rom with root, Hboot 1.12, and S-off (LazyPanda). On saturday my phone froze up, then rebooted. It immediately started boot looping and i could not get it back. Wiped cache, dalvik, nothing worked except a factory reset. I did make a backup of it to try and fix it but needed the phone back up ASAP. If anyone knows what is going on please help us.
Tried this three times and it did not work:
1. Remove external sd card
2. Boot into bootloader then recovery
3. Mount USB (to internal SD)
4. Windows recognized unformatted drive so I reformatted to fat32
5. Copied SuperLTE rom to SD card
5. Restarted and reinstalled ROM with full wipe
6. Boot to rom, everything seems to work
7. Shut down, insert external SD CARD, power on
8. Bootloops
looks like something besides the internal sd is FUBAR perhaps... The data seems to be good on the internal and external, so I'm left scratching my head
I think I finally fixed it by running the RUU:
(RUU_JEWEL_CLICS_40_S_Sprint_WWE-2.13.651.1_Radio_1.12.11.0809_NV_SPCS-2.45_003_release_277028_signed.exe)
I was reticent to do this because I had flashed radios and didn't want to upgrade my hboot, but it turns out that it was easy and didn't matter. Rerooting was via the stickied method instead of the old 1-click for 1.12 hboots, but that was easy enough.
1. Download the RUU
2. adb, fastboot oem lock
3. run RUU from fastboot usb
4. Reboot, then root via stickied post
5. Nandroid backup the stock rom for posterity
6. wiped, wiped, wiped til there were no brown stains
7. Changed format in twrp to rm-rf because on the superlte insructions it says to do so because of ext4 optimizations
8. wiped again
9. flashed superlte via the aroma installer
10. Yay
I should have bit the bullet and done the RUU yesterday... Everything is now up to date on the firmware side and re-rooting was easy. Hopefully it works good lasts long time.
So I just got back from a trip to Vegas, went to upgrade MeanROM from 6.3 to 6.5, and then my SD card would not mount and my internal storage is not showing. I've tried numerous things to try and fix this, by mounting SD and formatting it (Fat32, quick format off), unplugging and plugging in the SD Card, using a different one. No matter what I do, using TWRP 2.1.8 doesn't recognize the SD card and gives a repeated
E: failed to mount /sdcard (invalid argument).
E: Unable to mount /sdcard
Any tips?
Old Twrp ya got....use Goomanager and update...see if that might fix it
Can't even get GooManager to put anything in system cause it defaults to SD card
?? Goomanager install the recovery to the boot partition...you did click menu/ Install OpenRecoveryScript ???
Try flashing CWM recovery and seeing if that helps? My first guess would be to format your internal but since you've already done that I would default to blaming TWRP
tawnyoc said:
Try flashing CWM recovery and seeing if that helps? My first guess would be to format your internal but since you've already done that I would default to blaming TWRP
Click to expand...
Click to collapse
CMW is known to damage misc partitions
I just had a similar problem and the only lasting solution was to relock the bootloader, RUU, and reroot. It's easy and the newest RUU isn't difficult to reroot.
I was able to reformat in the internal SD a few times using a PC (before I ran the RUU that is) but it only lasted a reboot or two before re-corrupting. I wish I had just RUU'd from the beginning and not wasted effort with all the reformatting.
A while ago, I decided to work on my old legend and upgrading it with new custom roms.
After factory reset, I have flashed CM10 rom from here and discovered my Hboot version is 0.43 and not compatible with this rom.
So I found this rom instead and made 3 different partitions as instructed. But I have discovered that my phone have lost ability to go to recovery mode during the process and cannot recognize the zip files from SD card although its still in there. I have reformatted the SD card again with one fat32 to see if its problem with partitioning but it is still having same problem.
I can see the red triangle with ! in it and selected "Apply sdcard:update.zip" which keeps giving me error message "E:can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) Invalid argument"
Is there any solution to get out of this situation?
Thank you for your patience
Yhcho said:
A while ago, I decided to work on my old legend and upgrading it with new custom roms.
After factory reset, I have flashed CM10 rom from here and discovered my Hboot version is 0.43 and not compatible with this rom.
So I found this rom instead and made 3 different partitions as instructed. But I have discovered that my phone have lost ability to go to recovery mode during the process and cannot recognize the zip files from SD card although its still in there. I have reformatted the SD card again with one fat32 to see if its problem with partitioning but it is still having same problem.
I can see the red triangle with ! in it and selected "Apply sdcard:update.zip" which keeps giving me error message "E:can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) Invalid argument"
Is there any solution to get out of this situation?
Thank you for your patience
Click to expand...
Click to collapse
I have followed this thread and I got an error message saying failed due to low battery. I will just charge the phone for a while and see if it gives same error.
I have done the fastboot recovery method from here and its keep giving me "failed (remote: not allowed)" messages.
my Legend is already rooted and currently on S-off.
I have solved the problem.
It was memory card problem. my legend works after installing CM7 using different SD card.
I am suspecting if its because I have messed up something with memory card while dividing partitions to install a Jelllybean rom,
However the faulty memory card is still functioning well on my pc which made me think there is no problem with it.