ClockworkMod problem - G Tablet Android Development

When I tried to wipe user data, I got error message "E:Can't mount /dev/block/mmcblk3p2 (Invalid argument) Error mounting /data/!" and mount USB storage not working anymore. Now my gtab always in viewsonic/gtablet loop regardless which ROM I use. I was running TntLite 2.10 before crash.

In cwm, go to advanced and repartition the internal mem. That fixes the /data mount problem.

how much?
repartition it to what?
I see 6 options:
-128mb
-256mb
-512mb
-1042mb
-2048mb
-4096mb
not sure how much is needed or what the best option would be...

I ran into this problem as well. After going from stock to ZPad 2.2 then to TnT Lite 2.2.0. TnT Lite 2.2.0 was giving me problems so I decided to do a nandroid restore of my stock backup and got the same error you are getting.
Tried a bunch of different stuff, and nothing worked, so I "threw a hail mary", I had CM 6.1 RC4 on my external SD so I installed that from ClockworkMod, let it boot fully, then I shut it down and booted back into recovery and did a nandroid restore of my stock backup, this time the restore was successful.
Note: I am using ClockworkMod v2.5.1.2

Life in LA said:
repartition it to what?
I see 6 options:
-128mb
-256mb
-512mb
-1042mb
-2048mb
-4096mb
not sure how much is needed or what the best option would be...
Click to expand...
Click to collapse
I chose 4096 and then 64. No problems so far after the re-part. Hopefully you back up before doing this.

Thanks guys. Just to +1 this solution.

Related

error mounting /data- brick? LOL

I tried reflashing a sense 3.0 2.3.3 rom because of some minor issues. Now I may have nuked my /data partition. first it wouldn't format so I pulled battery numerous times. and Mounted it through mounts and storage menu, then I hit format, and it formatted, so I hit mount again and flashed the rom. and when I restarted the phone after splash screen the phone restarted and went into recovery
Tried everything including mounting /data again and it keeps saying error mounting /data. am I screwed?
I have .2007 eng bootloader btw. shoud I try the pd15img?
_ice_ said:
I tried reflashing a sense 3.0 2.3.3 rom because of some minor issues. Now I may have nuked my /data partition. first it wouldn't format so I pulled battery numerous times. and Mounted it through mounts and storage menu, then I hit format, and it formatted, so I hit mount again and flashed the rom. and when I restarted the phone after splash screen the phone restarted and went into recovery
Tried everything including mounting /data again and it keeps saying error mounting /data. am I screwed?
I have .2007 eng bootloader btw. shoud I try the pd15img?
Click to expand...
Click to collapse
I don't think you need to do that. You could do a fastboot erase, then go back into recovery and wipe data to reformat it /data, effectively starting from nothing.
jdkoren said:
I don't think you need to do that. You could do a fastboot erase, then go back into recovery and wipe data to reformat it /data, effectively starting from nothing.
Click to expand...
Click to collapse
Now I am getting mount /cache errors. aww man I think my phone is done....
edit: used the pd15img and I am back on stock :| s= off but I have the stock bootloader wtf.... how do I get my eng bootloader back?
this is how I fixed it:
I was on eng bootloader, but then I got reverted back to the stock bootloader.
This is how I encountered the problem. first of all I was having issues with raffy's fusion 3.0 rom, so I decided to reflash it, but it wouldn't flash or format /data, then I mounted it to through mounts and storage on the latest cwm 3.0.2.4 and hit format.
After that I tried reflashing his rom, it flashed but, after splashscreen I was redirected to my recovery instead. that's when I freaked because when I tried mounting data it said error cannot mount /data. so I fired up adb and did fastboot erase system -w and it erased it including cache.
then I popped up into recovery and BOOM started having cache mount errors experienced by a lot of people lately.
I thought I was SOL, but nope I downloaded the pd15img from http://www.megaupload.com/?d=V4NAODYZ
and put it on the root of my sd card and it worked....
so if anyone of you dudes are having similar problems try that ^

[SOLVED] Galaxy S I9000B not booting, no recovery mode

I rooted and installed CM7 on my SGS i9000B about 1 month ago. Everything was going fine and I was in love with my phone.
This afternoon, suddenly and with no apparent reason, it started giving me infinite "Force Close" messages to all apps I tried to open, making the phone pretty useless. Whe this happened I tried repairing permission from within Rom Maanger but the problem persisted. So I booted in recovery mode (Clockwork Mod Recovery) and tried fixing permissions there, but force closing problem was still there.
I had an Nand backup from the day I installed CM7. So I went to recovery mode again and tried restoring the backup, but it gave me an error (I believe it was somwthing related to disk space, but I'm not sure about that). So I did another backup (just in case) and tried to reboot the phone to try restoring backup again.
The problem is, now I can't get to recovery mode again. When I rebooted I was not able to go back to recovery mode anymore. I am still able to get to Download mode though. So I was thinking about flashing some rom/bootloader or something back in from Odin, but as I have no experience doing this, I believe it's safer to ask for help here before doing anything to the phone.
I believe it's not bricked yet, since I can still get to download mode.
Can anyone give me some detailed info about what I should do?
Do flash Kernel one more and,
Do root again and try that working.
If it happend again, wipe dalvik-cache and after your device is rebooted, try again in CWM.
evernet21 said:
Do flash Kernel one more and,
Do root again and try that working.
If it happend again, wipe dalvik-cache and after your device is rebooted, try again in CWM.
Click to expand...
Click to collapse
Sorry but I have very little experience with this and I want to be sure about what I'm supposed to do. What do you mean by flash kernel again? Is it flashing CyanogenMod 7 again via Odin?
I flashed the kernel again using Odin. Used the same file that I used before (when I fisrt rooted the phone a month ago - speedmod k13C). Now I can get into Recovery Mode.
But now I have a different problem. I tried to do a nandroid restore (backup and restore - restore ALL) but I have some errors related to mounting errors:
Code:
Checking MD5 sums...
Restoring system...
E:Can't mount /dev/block/st19 to /system with parameters auto llw.check=no
(File exists)
Error mounting /system/!
Skipping format...
E:Can't mount /dev/block/st19 to /system with parameters auto llw.check=no
(File exists)
Can't mount /system/!
I have no idea what that means.
Any help?
While searching for help on this error I found some people saying that flashing stock rom back intro phone could solve the problem. So this was what I did. Flashed stock samsung rom back i using Odin but when phone rebooted the following error appeared:
Android system recovery <3e>
Samsung Recovery Utils
- for BML -
[some recovery options]
update media, please wait
E:Can't mount /dev/block/st110
(Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
So I have a very similar error - "can't mount /dev/block/SOMEFILE". It looks to me like a problem with the internal sd card. What do you guys think?
Solved
I could solve the problem using the method described in this thread.
http://forum.xda-developers.com/showthread.php?p=14732179#post14732179

[Q] Cache and Data mount issues

So I've been using various JB ROM's on my Defy for the past couple of years, but this time I made the mistake of using the factory reset within the stock recovery. I found a thread that mentioned using the "ultimate wipe" for defy and then reflashing my ROM of choice would fix issue, but when I use the wipe the custom recovery still tells me it is unable to mount /cache or /data on my phone.
My phones internal storage is also showing as 0, so I am unable to install any apps etc.
I'm completely stumped right now, so any help at all would be greatly appreciated. I'll provide any further information I can if its needed, thanks in advance
DSpartox said:
So I've been using various JB ROM's on my Defy for the past couple of years, but this time I made the mistake of using the factory reset within the stock recovery. I found a thread that mentioned using the "ultimate wipe" for defy and then reflashing my ROM of choice would fix issue, but when I use the wipe the custom recovery still tells me it is unable to mount /cache or /data on my phone.
My phones internal storage is also showing as 0, so I am unable to install any apps etc.
I'm completely stumped right now, so any help at all would be greatly appreciated. I'll provide any further information I can if its needed, thanks in advance
Click to expand...
Click to collapse
I think you need to start over from SBF.
Sent from my Nexus 7 using Tapatalk
DSpartox said:
So I've been using various JB ROM's on my Defy for the past couple of years, but this time I made the mistake of using the factory reset within the stock recovery. I found a thread that mentioned using the "ultimate wipe" for defy and then reflashing my ROM of choice would fix issue, but when I use the wipe the custom recovery still tells me it is unable to mount /cache or /data on my phone.
My phones internal storage is also showing as 0, so I am unable to install any apps etc.
I'm completely stumped right now, so any help at all would be greatly appreciated. I'll provide any further information I can if its needed, thanks in advance
Click to expand...
Click to collapse
Your partitions might have a problem and the wipe script doesn't format them, it just deletes their contents. In the bootmenu you can format your /data and /cache partitions (ext4); if that doesn't work, then yes, gotta start over from SBF.
Antiga Prime said:
Your partitions might have a problem and the wipe script doesn't format them, it just deletes their contents. In the bootmenu you can format your /data and /cache partitions (ext4); if that doesn't work, then yes, gotta start over from SBF.
Click to expand...
Click to collapse
Thank you heaps for the help. I just decided to go ahead and reflash SBF. That all went fine, RSDlite gave a pass. I then went into the stock recovery in order to do the factory reset again before I root, and Data now formats, but Cache throws up the error "E:Can't mount CACHE:recovery/log".
The actual phone seems to work fine if I boot it up, but that error just makes me wonder as I'm not sure how much of a problem it really is

Gt i9506 10 gb used by system after flashing.

hello there!
some months ago i tried a custom firmware on my 9506 (i think that was the first version of arya mod) but i didnt kinda like it so i downloaded again the stock fw and flashed it back.
i did my typicall "download the basic apps" routine and on the 4th app an "insufficient storage available" message appeared on my screen and i was like "lol whats wrong?" i checked on and i found that 10.6Gb was used by system.
Well i thought that i downloaded maybe a bugged stock rom and i didnt have the free time at the time to check whats wrong so i decided to live with it till i find some spare time to check it again.
Yesterday i downloaded and flashed the lineage os fw and i was sure that this would fix the problem...but...well it didnt..still 10.6 used by system.
i tried wipe EVERYTHING (dalvik/cache/system/internal) and reflashed again but still nothing,i flashed again the stock rom,still nothing, i searched online but i didnt find a solution, i downloaded diskusage app to see where are those 10gbs but i couldnt figure out where they where.
So if anyone knows anything or had the same or similar problem it would be great if he/she write here and give a solution or some tips.
Thanks in advance
Try format data from recovery.
Pwnycorn said:
Try format data from recovery.
Click to expand...
Click to collapse
Thanks for your reply!
You mean the wipe option or am i missing something?
I did wipe everything via twpr recovery from the "advanced wipe option" and checked everything except my sdcard and still nothing.
is there any other way to completly format it ? if so,then how i can do it?
bakos360 said:
Thanks for your reply!
You mean the wipe option or am i missing something?
I did wipe everything via twpr recovery from the "advanced wipe option"
Click to expand...
Click to collapse
There's a format data option there too.
Pwnycorn said:
There's a format data option there too.
Click to expand...
Click to collapse
lol i didnt see it and it was in front of my eyes!
i tried that too today but here is what is happening
Updating partition details...
...done
Full SELinux support is present.
Running boot script...
Done.
MTP enabled
E:unable to wipe '/data' -- unknown file system ' auto enable to format to remove encryption.
Mount media patd for recreate TWRP settings. /data/media/o
TWRP settings saved
Updating partition details...
...done..
for some reason it seems that its enable to format '/data'
any other option ? =/
bakos360 said:
lol i didnt see it and it was in front of my eyes!
i tried that too today but here is what is happening
Updating partition details...
...done
Full SELinux support is present.
Running boot script...
Done.
MTP enabled
E:unable to wipe '/data' -- unknown file system ' auto enable to format to remove encryption.
Mount media patd for recreate TWRP settings. /data/media/o
TWRP settings saved
Updating partition details...
...done..
for some reason it seems that its enable to format '/data'
any other option ? =/
Click to expand...
Click to collapse
Try flashing the stock ROM together with a PIT file
i fixed it guys
i flashed again cwm recovery and i formated EVERYTHING from there and then reflashed again the rom and gapps and that fixed the problem.
Thanks for your help !
For the record, CWM's incremental backup feature was what I believe was stealing your space. If you still have CWM on that device, make sure to set the default nandroid backup format to ".tar" instead of ".dup", clear out your nandroid backups, clear all the allocated space, and then upgrade to the latest version of TWRP.
CWM hasn't been updated in a few years now and has difficulty installing modern ROMs.
you are right i think.
if i recall corectly when i flashed that rom back then before the problem appeared, i used cwm recovery so yeah maybe thats the main reason that this happened.
i allready set the default backup to .tar and cleared out all the nandroid backups and i allready use TWRP now.
thanks for the tip mate!

S8 TWRP Error

Hi all,
Yesterday I managed to root my phone all fine with TWRP and SuperSU. Then after incorrectly uninstalling the security log agent and getting a million errors I foolishly deleted the stock OS.
I have download the correct version for my phone and location but now TWRP fails to launch.
I get the follows errors when booting to the recovery.
Failed to mount /data (invalid argument)
Unable to recreate /data/media folder
Unable to mount storage
Unable to mount /data/media/TWRP/.twrps
I have googled a millions things and am still stuck.
Interestingly tho, If i install the Indian version of the OS, it loads and roots no problems (I'm from New Zealand).
Any help greatly appreciated.
VacantLot said:
Hi all,
Yesterday I managed to root my phone all fine with TWRP and SuperSU. Then after incorrectly uninstalling the security log agent and getting a million errors I foolishly deleted the stock OS.
I have download the correct version for my phone and location but now TWRP fails to launch.
I get the follows errors when booting to the recovery.
Failed to mount /data (invalid argument)
Unable to recreate /data/media folder
Unable to mount storage
Unable to mount /data/media/TWRP/.twrps
I have googled a millions things and am still stuck.
Interestingly tho, If i install the Indian version of the OS, it loads and roots no problems (I'm from New Zealand).
Any help greatly appreciated.
Click to expand...
Click to collapse
Hi
Your internal memory now corrupt you have to format it.
Use twrp wipe option select internal memory then format to fat32 after that again do same thing. This time choose its original format type.
drparvez said:
Hi
Your internal memory now corrupt you have to format it.
Use twrp wipe option select internal memory then format to fat32 after that again do same thing. This time choose its original format type.
Click to expand...
Click to collapse
Hi, thanks for the fast reply.
Iv'e tried this option, I installed the Indian OS which works with TWRP, formatted the Data drive to FAT (Fat32 isn't an option) and then back to EXT4. I then used Odin to Install the carrier firmware I want to run and the same errors occurred. Could it be a problem with the actual OS?
Edit** When I install the Carrier firmware I can't get TWRP to open, these errors occur as soon as it opens, and then it crashes and reboots
VacantLot said:
Hi, thanks for the fast reply.
Iv'e tried this option, I installed the Indian OS which works with TWRP, formatted the Data drive to FAT (Fat32 isn't an option) and then back to EXT4. I then used Odin to Install the carrier firmware I want to run and the same errors occurred. Could it be a problem with the actual OS?
Edit** When I install the Carrier firmware I can't get TWRP to open, these errors occur as soon as it opens, and then it crashes and reboots
Click to expand...
Click to collapse
Try reflashing twrp
Acoustichayes said:
Try reflashing twrp
Click to expand...
Click to collapse
Hi hi, tried that several times. Would still like to find out what is causing the issue but have now installed Nemisis and all is working perfrctly which makes me think it's the OS as opposed to my file system, considering I have installed multiple other versions and ran TWRP no problems.
Got same problem here. Installed TWRP to flash a custom rom, TWRP can't mount /data.
Google doesn't give me any solutions
This fixed it for me:
- download stock firmware from sammobile & flash with Odin
- go into stock recovery
- wipe data and cache partitions
- flash twrp using odin
After that, TWRP was able to mount /data and function normally again

Categories

Resources