Hi there, I seem to have messed up my mounting partitions while trying to deodex Stock JB Central Europe. I basically used xultimate to pull the files and deodex then tried using adb shell to mount the system partition and copy them over. After I rebooted the phone, it would get stuck on unlocked bootloader warning or on the motorola logo. I hard reset into recovery and restored a nandroid backup and once booted into android found so many folders under the Storage folder such as "asec", "obb", rfs0" and so on. Now, when I try to wipe dalvik-cache in recovery, i get the following error: "E: unknown volume for path [/sd-ext]". Also, when i try flashing custom rom's and reboot, it gets stuck on the unlocked bootloader warning and wont load - while in recovery after flashing, i also get another error something like this: "E: cant load /cache/recovery.log" or similar. I also sometimes have issues mounting system, cache partitions, data and internal storage, all depending on which custom recovery i am using. I read on another site that downgrading to ics might solve mounting problems so I forced a downgrade to ics but that didnt work either and am still on ics.
Is there a way to restore the partitions correctly or are they stuck this way? Would mounting and remounting solve this problem? Any help would be much appreciated and would very much appreciate it if someone could upload their mount point info so i could use to try and fix it.
Many thanks in advance.
EDIT: Managed to flash Slim Bean 4.3 Official using OUDHS recovery without wiping cache and dalvik-cache at first. After reboot, it would bootloop so went to recovery and wiped cache and dalvik-cache then it worked. Still no sd-ext and some apps can't write or backup to external memory such as Go Backup & Restore Pro so what remains is to mount/unmount the partitions correctly.
I am relatively new to the world of rooting and ROMs, but I have successfully installed CM10 on a previous Samsung phone, so I am decently literate.
I am currently attempting to install CM10.1 on my Verizon Galaxy S III (following the instructions on the Install CM for d2vzw page on the CM wiki), but I have reached an impasse at step 7. I was not aware that I had to put the VRALE6.bootloader.zip file on the SD card before starting this process, so I am now attempting to get that file onto my SD card either by sideloading through CWM or by pushing it to the SD card through adb. The issue is that CWM gives me an error (can't mount SD card) and adb doesn't recognize my device (I have tried installing and reinstalling various drivers for the past few hours). I enabled USB Debugging mode before starting the process, but I am only able to get into Download and CWM modes right now (if I don't do the Download Mode or Recovery Mode key combination, I am stuck on the Galaxy S III screen). Am I bricked at this point, or is there a way to get VRALE6.bootloader.zip onto my phone and continue with the ROM process?
It is important to note that I formatted the SD card before starting this process because I wanted enough space to put the Cyanogenmod file on it. However, I think I may have formatted it generically rather than into FAT-32. Could this be the issue?
I am going to pick up a microSD card reader today in order to flash the SD card to FAT-32 and put the CyanogenMod file on it.
I am getting 5 errors upon startup of CWM (E: Can't mount /cache/recovery/command, can't mount /cache/recovery/log, etc.). When I try to mount the SD card or external SD card, I get E: Can't mount /sdcard/
Same issue with sd card not mounting.
I'm having somewhat of the same issue. I've tried both Clockwork recovery and TWRP and have the same issue.
Should have mentioned that i still have access to the stock rom and can use my phone just fine.
I some how got Clockwork mod recovery to work using the Rom Manager pro App.
I wish i had been paying better attention to what i was doing but i know i updated CWMrecovery from in rom manager and chose to install my chosen rom with that.
My suggestion is to start over completely. There is a much easier way to do this.
My suggestion is to flash one of the rooted stock ROMs through Odin. There's a thread in android development that has rooted stock. Then when that's done boot up your phone. If it bootloops wipe data. Then use Ez-Unlock 1.2 app to unlock your bootloader. Make sure it's 1.2. Now use GooManager to flash TWRP. You are done! This is probably the easiest way to do this.
Thread: http://forum.xda-developers.com/showthread.php?p=33948598
Sent from my SCH-I535 using Tapatalk
Sent from my SCH-I535 using Tapatalk
Sandman-007 said:
My suggestion is to start over completely. There is a much easier way to do this.
My suggestion is to flash one of the rooted stock ROMs through Odin. There's a thread in android development that has rooted stock. Then when that's done boot up your phone. If it bootloops wipe data. Then use Ez-Unlock 1.2 app to unlock your bootloader. Make sure it's 1.2. Now use GooManager to flash TWRP. You are done! This is probably the easiest way to do this.
Thread: http://forum.xda-developers.com/showthread.php?p=33948598
Sent from my SCH-I535 using Tapatalk
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I am not familiar with TWRP, so is the process the same for flashing CM (putting CM zip file on sd card and going to install from SD card in TWRP)? Are there any additional steps beyond this?
I am following the directions in the thread linked above to root and install TWRP. So far, I have the rooted stock ROM running fine, but I can't get TWRP to work. I downloaded Goomanager and attempted to get TWRP using the Install Openrecovery Script option. However, it said that it couldn't find a recovery for my device. I also tried to use the adb method, but nothing happened after I put in the commands. I even tried to flash the latest TWRP .tar file from their website using Odin, but it keeps failing. Is there any way to get TWRP on my phone?
EDIT:Whoops, I skipped over the EZ-Unlock step. Now everything works. Thanks for the help, Sandman!
mikestrong19 said:
I am following the directions in the thread linked above to root and install TWRP. So far, I have the rooted stock ROM running fine, but I can't get TWRP to work. I downloaded Goomanager and attempted to get TWRP using the Install Openrecovery Script option. However, it said that it couldn't find a recovery for my device. I also tried to use the adb method, but nothing happened after I put in the commands. I even tried to flash the latest TWRP .tar file from their website using Odin, but it keeps failing. Is there any way to get TWRP on my phone?
EDIT:Whoops, I skipped over the EZ-Unlock step. Now everything works. Thanks for the help, Sandman!
Click to expand...
Click to collapse
No problem bro. Glad you are all fixed up
Sent from my SCH-I535 using Tapatalk
Sandman-007 said:
No problem bro. Glad you are all fixed up
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Alright, maybe I'm not quite fixed up yet. I have TWRP installed and I can go between TWRP, download mode, and the normal stock rooted ROM fine. However, I cannot get to the SD Card in TWRP in order to install CM. TWRP gives me the following errors upon booting into recovery:
E: Unable to find parition size for '/boot'
E: Unable to find parition size for '/data'
E: Unable to find parition size for '/recovery'
Updating partition details:
E: Unable to mount '/system'
E: Unable to mount '/cache'
E: Unable to mount '/cache'
E: TWFunc: :Copy_Log - - Can't open destination log
E: Unable to mount '/cache'
Upon trying to go to Install, I am unable to select the external SD card, and an additional error appears when I attempt to touch Micro SD Card (E: Unable to mount '/external_sd').
I guess I could try to sideload the CM zip file through adb, but I would rather fix the SD card for future use. I have been researching and working on the SD card for the better part of today, to no avail. I am pretty sure the issue is in the formatting of the SD card (it appears to be RAW rather than the required FAT32 for CM), but I cannot format the SD card into FAT-32 no matter what I try (both Windows and 3rd party formatting tools). They all say that the SD card is either write-protected (I have already checked the read/write switch on the side of the SD card adapter) and/or the format cannot be completed. I have tried both my old SD card that I have kept for a few phones (an 8GB Samsung microSD card) and a brand new Sandisk 8GB microSD card, both of which will not work.
I am able to transfer files to the SD card with no issue (with both ADB and through dragging/dropping in Windows), but I cannot install from SD in recovery.
Does anyone have a solution to allow me to install CM on my phone?
Download root checker from the play store. Make sure you are rooted
Sent from my SCH-I535 using Tapatalk
Sandman-007 said:
Download root checker from the play store. Make sure you are rooted
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Yes, I do have root access. I think the problem lies somewhere in my SD card.
mikestrong19 said:
Yes, I do have root access. I think the problem lies somewhere in my SD card.
Click to expand...
Click to collapse
Do you have another computer to try formatting the sdcard with? And you said that you receive the same errors when trying to reformat the new 8 GB sdcard as with your other sdcard which is formatted to RAW?
SlimSnoopOS said:
Do you have another computer to try formatting the sdcard with? And you said that you receive the same errors when trying to reformat the new 8 GB sdcard as with your other sdcard which is formatted to RAW?
Click to expand...
Click to collapse
I do have access to another computer, but I ran out of time and patience yesterday. I will try it when I get home later today. And yes, both cards are RAW (even the new one) and I can't get either one to format or work in TWRP.
So it appears the the issue with formatting was due to my computer's drivers (even though I installed the latest Samsung USB drivers) and not the SD card. I was able to format the SD card to FAT32 on another computer and put CM and GAPPS onto it. When booted normally into TouchWiz, the phone sees the SD card fine. However, I still get the same "Can't mount external SD card" error as well as the others previously listed when I attempt to install a zip from recovery. I even tried to sideload the ROM from ADB, but it still didn't work.
mikestrong19 said:
So it appears the the issue with formatting was due to my computer's drivers (even though I installed the latest Samsung USB drivers) and not the SD card. I was able to format the SD card to FAT32 on another computer and put CM and GAPPS onto it. When booted normally into TouchWiz, the phone sees the SD card fine. However, I still get the same "Can't mount external SD card" error as well as the others previously listed when I attempt to install a zip from recovery. I even tried to sideload the ROM from ADB, but it still didn't work.
Click to expand...
Click to collapse
Which version of CWM and also TWRP are you using?
And the problems keep rolling in. I was able to mount my SD card and get rid of the TWRP errors by installing a modded TWRP 2.6.0.0 from this thread (http://forum.xda-developers.com/showthread.php?p=44277901). However, when I go to install CM (cm-10.1.3-d2vzw.zip), I get the following error:
assert failed: getprop("ro.product.device") ==
E: Error executing updater binary in zip '/external_sd/cm-10.1.3-d2vzw.zip'
Error flashing zip '/external_sd/cm-10.1.3-d2vzw.zip'
Updating partition details
I did a factory reset before attempting to install this, but I did not format data or do anything else.
mikestrong19 said:
And the problems keep rolling in. I was able to mount my SD card and get rid of the TWRP errors by installing a modded TWRP 2.6.0.0 from this thread (http://forum.xda-developers.com/showthread.php?p=44277901). However, when I go to install CM (cm-10.1.3-d2vzw.zip), I get the following error:
assert failed: getprop("ro.product.device") ==
E: Error executing updater binary in zip '/external_sd/cm-10.1.3-d2vzw.zip'
Error flashing zip '/external_sd/cm-10.1.3-d2vzw.zip'
Updating partition details
I did a factory reset before attempting to install this, but I did not format data or do anything else.
Click to expand...
Click to collapse
Well, that is for the Sprint S3 my friend. We can't interchange recoveries between the different S3 models to flash roms. You may want to ask Kennyglass123 or any of those other guys if they can make a change for the VZW S3 for you to test it out.
SlimSnoopOS said:
Well, that is for the Sprint S3 my friend. We can't interchange recoveries between the different S3 models to flash roms. You may want to ask Kennyglass123 or any of those other guys if they can make a change for the VZW S3 for you to test it out.
Click to expand...
Click to collapse
Sounds good. I think the problem has been isolated to being something with needing a modded TWRP. I tried using an older, non-modded TWRP (2.5.0.0), which didn't work.
mikestrong19 said:
Sounds good. I think the problem has been isolated to being something with needing a modded TWRP. I tried using an older, non-modded TWRP (2.5.0.0), which didn't work.
Click to expand...
Click to collapse
Would you mind trying this soft brick fix? If I'm not mistaken, I believe you're experiencing this same issue--excluding the Sprint TWRP issue you just mentioned. You will need to flash your VZW custom recovery either through GooManager, Rom Manager, or Odin btw.
SlimSnoopOS said:
Would you mind trying this soft brick fix? If I'm not mistaken, I believe you're experiencing this same issue--excluding the Sprint TWRP issue you just mentioned. You will need to flash your VZW custom recovery either through GooManager, Rom Manager, or Odin btw.
Click to expand...
Click to collapse
I can still get between the stock rooted ROM, download mode, and recovery mode fine, so does that mean I am still soft-bricked and should try this?
mikestrong19 said:
I can still get between the stock rooted ROM, download mode, and recovery mode fine, so does that mean I am still soft-bricked and should try this?
Click to expand...
Click to collapse
Yea, because you are still receiving these errors right?
E: Unable to find parition size for '/boot'
E: Unable to find parition size for '/data'
E: Unable to find parition size for '/recovery'
Updating partition details:
E: Unable to mount '/system'
E: Unable to mount '/cache'
E: Unable to mount '/cache'
E: TWFunc: :Copy_Log - - Can't open destination log
E: Unable to mount '/cache'
Click to expand...
Click to collapse
This soft brick fix is an attempt to correct the /system and /data errors.
Edit: Oh great, none of the links work. I'll see about finding alternate links.
I am not new to ROM's I have dabbled here and there with my phones and the xoom. I followed the directions to a t for the Omni 4.4.2. I did the first part for putting bigPart TWRP on my xoom. I have the recovery on there and I can find my SD card with the rom and other files on there needed but it will not load after I install everything. The internal storage still shows at 0. I get the Omni bootloader and then a message from google pops up saying encryption unsuccessful and I need to perform a factory reset. When I try that it just brings me back to recovery. I don't know what I did wrong but the only thing that works is recovery. It's like nothing at all is on the internal storage of the xoom. I have tried to copy the files from my sd card over to internal and install, same thing. When I go back to check the files I copied to internal they are gone. The files I have on the sd card are there but it won't load the files on the internal storage to set up android on there. I can't even go back to an old restore cause I was using cwm recovery and the those restore files aren't recognized. I'm at a loss, any help would be greatly appreciated. I can't even get my computer to see so I can push the files over to it and I am pretty rusty with ADB to try and set that up.
I just tried to push the original twrp 2630 through adb and it flashed, I tried to reboot into recovery and it just staid at the twrp screen. Ughhh I'm getting so frustrated cause I had the xoom working perfectly on JB before I started messing around. Any help would be great, Even getting me back to stock and I can take it from there.
update
at0msplat said:
I am not new to ROM's I have dabbled here and there with my phones and the xoom. I followed the directions to a t for the Omni 4.4.2. I did the first part for putting bigPart TWRP on my xoom. I have the recovery on there and I can find my SD card with the rom and other files on there needed but it will not load after I install everything. The internal storage still shows at 0. I get the Omni bootloader and then a message from google pops up saying encryption unsuccessful and I need to perform a factory reset. When I try that it just brings me back to recovery. I don't know what I did wrong but the only thing that works is recovery. It's like nothing at all is on the internal storage of the xoom. I have tried to copy the files from my sd card over to internal and install, same thing. When I go back to check the files I copied to internal they are gone. The files I have on the sd card are there but it won't load the files on the internal storage to set up android on there. I can't even go back to an old restore cause I was using cwm recovery and the those restore files aren't recognized. I'm at a loss, any help would be greatly appreciated. I can't even get my computer to see so I can push the files over to it and I am pretty rusty with ADB to try and set that up.
I just tried to push the original twrp 2630 through adb and it flashed, I tried to reboot into recovery and it just staid at the twrp screen. Ughhh I'm getting so frustrated cause I had the xoom working perfectly on JB before I started messing around. Any help would be great, Even getting me back to stock and I can take it from there.
Click to expand...
Click to collapse
trying to give as much info as I can. I got the original twrp 2630 running, flash twrp big part, followed next step to to wipe everything except sdcard, this is what I got:
Updating partition details...
E:unable to mount '/system'
E:unable to mount '/cache'
E:failed to wipe dalvik
updating partition details...
E:unable to mount '/system'
E:unable to mount '/cache'
Hello, i am quite panicked about this problem so i will cut to the chase.:crying: I will write down stuff i did in numerical orders.
1. Using TWRP 2.8.6.1, I was curious to try to go to Wipe>Advanced>full wipe (wiping everything). After i did and tried to reboot, it said there is no OS. So i tried flashing my flashable stock rom 4.4.4 in zip form but it didn't boot.
2. So i flashed to stock in fastboot. (For flashing to stock, i used this instructions http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/). After finish flashing, i went to stock recovery and wiped dalvik cache and data.
3. After that, i rebooted and... that when it didn't seem right. Nexus 5 COULD connect to my PC but it only showed "Internal Storage" and nothing else. If i tried to move something to the storage, it would immediately say i can't move it there.
4. So i thought this was because the full wipe i did before and that the system partition got totally wiped. So i used TWRP again but to restore my old nandroid backup.
5. After i flashed my nandroid backup, twrp said this one line that goes in red "unable to mount /firmware. I ignored and rebooted. It still had the problem where i couldn't move anything to my storage by MTP but also adb push. It even couldn't save screenshots and download anything from internet like apk or some sort. When i went into the app called "Zipper", it said 'no sdcard'.
6. I searched through the internet to fix this but i kept failing to solve it. I tried going to TWRP and doing chmod, chmod 755, using these instructions (http://forum.xda-developers.com/google-nexus-5/general/sdcard-problems-upgrading-android-t2938749)
TL;DR : I did a full wipe in TWRP and lost all permissions to read or write. Nandroid backup didn't help. Whatever i flash in twrp, it says "unable to mount /firmware" at the end.
metallikoh said:
Hello, i am quite panicked about this problem so i will cut to the chase.:crying: I will write down stuff i did in numerical orders.
1. Using TWRP 2.8.6.1, I was curious to try to go to Wipe>Advanced>full wipe (wiping everything). After i did and tried to reboot, it said there is no OS. So i tried flashing my flashable stock rom 4.4.4 in zip form but it didn't boot.
2. So i flashed to stock in fastboot. (For flashing to stock, i used this instructions http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/). After finish flashing, i went to stock recovery and wiped dalvik cache and data.
3. After that, i rebooted and... that when it didn't seem right. Nexus 5 COULD connect to my PC but it only showed "Internal Storage" and nothing else. If i tried to move something to the storage, it would immediately say i can't move it there.
4. So i thought this was because the full wipe i did before and that the system partition got totally wiped. So i used TWRP again but to restore my old nandroid backup.
5. After i flashed my nandroid backup, twrp said this one line that goes in red "unable to mount /firmware. I ignored and rebooted. It still had the problem where i couldn't move anything to my storage by MTP but also adb push. It even couldn't save screenshots and download anything from internet like apk or some sort. When i went into the app called "Zipper", it said 'no sdcard'.
6. I searched through the internet to fix this but i kept failing to solve it. I tried going to TWRP and doing chmod, chmod 755, using these instructions (http://forum.xda-developers.com/google-nexus-5/general/sdcard-problems-upgrading-android-t2938749)
TL;DR : I did a full wipe in TWRP and lost all permissions to read or write. Nandroid backup didn't help. Whatever i flash in twrp, it says "unable to mount /firmware" at the end.
Click to expand...
Click to collapse
EDIT: alright i did a mess up. When i flashed the stock, i didn't rename the radio from radio-hammerhead-m8974a-2.0.50.1.16 to radio.img.