Unable to see internal memory. - Galaxy Tab General

As a side effect of trying one of the overclocked ROMs which stopped my tab booting, I've sorted it out by flashing back to a working zImage, but now the tab refuses to see the internal storage memory. It can see the external MicroSD in the recovery menu, but within the OS, it doesn't think it even _has_ internal memory.
Any idea how to reinstate the block device? I've tried doing a complete repartition and reflash of rotohammer's JMI firmware, but still nothing.
The likely block devices in /dev/block that I can see are:
mmcblk1
mmcblk1p1
mmcblk0
mmcblk0p1, 2 & 3
And in /dev/block/vold/ :
179:0, 1, 2, 3, 8 & 9
Any ideas?
EDIT:
I did another repartition and reflash of Rotohammer's JMI firmware and once it rebooted it seemed to sort itself out. Strange that it didn't do it the first time.

Related

Can I remove my secondary partition???

Ok, first off, I'm new to this, I've only had my android for about 1 1/2 months. I've read a million threads and posts to absorb information so I don't have to ask stupid questions like this. However, I've searched and tried several different methods, and none have worked. I apologize in advance because I'm sure the information is already somewhere in this forum, but I can't seem to find the specific information for my phone, Mt3G.
The problem I'm having is that last week I decided to partition my my sdcard so I could see how apps2sd worked. After some trial and error, I got it to work.
1. 64 mb swap
2. 512 mb ext
3 remainder on FAT32
After a couple of days, I started notices lags and also issues such as not being able to upload images to facebook, trouble downloading apps from the market, not being able to receive MMS messages or sending them, etc. Overall, it seems like partitions are causing my phone to lag, run slow and other small glitches, so I would like to remove all the partitions, format the sdcard, and just have one single FAT32 partition, as if it were stock. I no longer want apps2sd.
I've tried 'droid explorer', I've followed the cyanogen tutorial on how to uninstall apps2sd via terminal emulator, I've tried wiping, formatting, everything, nothing works. Every time I reboot my phone, the secondary partition still remains, although it says total space unavailable now, but its still there, and according to droid explorer, the apps are still there. I just want to get rid of everything because as of right now, most of my downloaded app icons don't appear, but when I go to download the apps at the market, they say they are already installed. I dont know, I'm about to just throw my phone at the wall.
Any help would be greatly appreciated. By the way, here is my current setup.
Phone: MT3G
ROM: Cyanogen 4.2.11.1 + Cyanogen recovery 1.4
Instead of Cyanogen's recovery, install Amon_RA's 1.5.2G
It will let you format your SD back to Fat32, or you can repartition it the the three, with just the click of a trackball.
In doing so, you will more than likely have to reflash the rom due to you losing all your apps and whatnot that's also on the ext partition, since you will be deleting it.
Backup all your stuff onto your computer first, as you will lose it all when it wipes the slate clean.
@tazz, hey, thanks for your reply. So let me elaborate, when I originally partitioned my card I had amon_ra on my phone. When I started noticing problems, I went back into recovery to see if there was any way to delete or repartition back to a single FAT32, but I couldn't find anything. I stated to back track and flashed CM recovery back on my phone, wiped, reflashed ROM, etc. Nothing...in fact, it caused even more force closes and still, my apps didn't appear in the app drawer, although according to market place and android explorer, they were installed.
Anyway, I took your advice, reflashed amon_ra recovery back on my phone, but I still do not see an option to partition with a single FAT32. All I'm seeing is the option to repartion the SD card, then it gives me the option to pick swap size, ext size, then the remainder on the fat32. Do I just set the swap and ext to 0? Also, do I wipe at all in this process?
yeah just put it to zero. i was thinking about his 1.2.3.
if you put them to zero, it should work out the same either way.
Hmmm....I must be doing something wrong. Went into recovery, selected 'partition sd', set swap to '0', set ext to '0', remainder to FAT32, flashed ROM, system reboot. Secondary partition still appears when I go into the sd storage under settings. Also, android explorer still showing apps in data folder, and marketplace still shows apps such as astro file manager still installed. I'm lost.
Update: Tazz, I followed your instructions, reflashed ROM, rebooted. Secondary partion still appeared. However, I noticed that the option for 'unmounting sdcard' was available. So, I unmounted and physically removed my sdcard to see if this was causing the problem or if it was something internal. After removing sdcard, I still had my applications showing that they were installed, but not showing in app drawer. I decided to try flashing an older CM ROM, just to see what happens. It worked! After flashing older ROM verision, I reflashed newer version and all my problems were solves.
Anyway, just wanted to say thanks for helping me get rid of my partitions.

[Q] Cannot Format /Data

Whenever I try to format /data through CWM 3.0.2.8, it returns the message.
error while formatting /data
Click to expand...
Click to collapse
Also when I try to restore a backup, CWM cannot format /data.
I've also tried to install CM7. It says it completed its install in CWM but when I reboot, it retains the OS (rooted stock 1.2) I was currently on.
Me too. I just updated to MR1 and I am trying to restore the /data directory and I can't.
There's one thing I noticed about this refurb'd nook color. The space available in the device info is 1GB. Shouldn't it be higher or did they change the file structure with the latest models?
Also, I went into ADB and mounted EMMC. The last modified date for the files in there is May 4th.
Edit
Not sure if this would help.
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
255 heads, 63 sectors/track, 965 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 9 72261 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p2 10 18 72292+ c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 965 7301542+ 5 Extended
/dev/block/mmcblk0p5 57 114 465853+ 83 Linux
/dev/block/mmcblk0p6 115 789 5421906 83 Linux
/dev/block/mmcblk0p7 790 834 361431 83 Linux
/dev/block/mmcblk0p8 835 965 1052226 c Win95 FAT32 (LB
A)
~ #
Click to expand...
Click to collapse
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC SEM08G (sd/mmc)
Disk /dev/block/mmcblk0: 7944MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 74.0MB 74.0MB primary fat32 boot, lba
2 74.0MB 148MB 74.0MB primary fat32 lba
3 148MB 461MB 313MB primary ext2
4 461MB 7937MB 7477MB extended
5 461MB 938MB 477MB logical ext2
6 938MB 6490MB 5552MB logical ext3
7 6490MB 6860MB 370MB logical ext3
8 6860MB 7937MB 1077MB logical fat32 lba
(parted)
Click to expand...
Click to collapse
Someone responded back to me on this forum.
http://androidforums.com/b-n-nookcolor/333668-format-internal-partition.html#post2672750
Barnes & Noble has started shipping new NOOK Color devices that are partitioned to allow only 1 GB of "user sideloaded" storage. The remaining 7 GB are partitioned for the OS, apps from the new B&N Apps store, and items downloaded directly from B&N. For the typical (non-rooted) device, the user would have to use the microSD slot for additional storage. I suspect you got one of the newly partitioned devices, which is why you are now seeing only 1 GB instead of the previous 5 GB of storage available.
Click to expand...
Click to collapse
Is there anyway to repartition the new devices or I'm stuck with this? If not, it's going to prevent me from dualbooting. This might also be the cause of my second problem, installing CM7 and still ending up with the original OS.
Oh man am I glad I found this thread. I was freakin' out when I couldn't load phiremod onto my newly purchased NC. Turns out I can only see 1GB of storage like the others in this thread. Hopefully some one will find a way to repartition the newer devices otherwise I am stuck with a rooted NC running the stock ROM with no way to return it.
You can just "Reset to factory default" and it'll remove the root. Then you can try to return it or exchange it. I'd probably say this if they ask for a reason...
"It's showing 1GB space as opposed to 8GB space as advertised"
Though I'm wondering why install CM7 doesn't change anything. After installation, it still boots up the stock OS.
jb7038 said:
You can just "Reset to factory default" and it'll remove the root. Then you can try to return it or exchange it. I'd probably say this if they ask for a reason...
"It's showing 1GB space as opposed to 8GB space as advertised"
Though I'm wondering why install CM7 doesn't change anything. After installation, it still boots up the stock OS.
Click to expand...
Click to collapse
Trying to load new ROMS fails because I can't do a data wipe as instructed.
I wonder if they made it so that outside sources can't write or modify /data now but it's still rootable with manualnooter.. I can format the other partitions through CWM and restore them easily.
EDIT
http://www.barnesandnoble.com/nookcolor/features/index.asp?cds2Pid=35583
*1GB = 1 billion bytes; Actual formatted capacity may be less. Approximately 5GB available to store content, of which up to 4GB may be reserved for content purchased from the Barnes & Noble NOOK Store.
I am not sure what kind of security they could have on the actual partitions, but the dual boot ROMS show that resizing the partitions should not be to hard, though it does mean you may lose data (possibly).
I don't mind losing my /data. I rather be able to install CM7 or something on the EMMC as opposed to running it on the SD.
I'd be grateful if someone could show me how to partition it so it's back to the original partition, 4gb/4gb as opposed to 7gb/1gb I think.
I hope something is figured out soon.
Here's the solution to anyone following this thread.
http://forum.xda-developers.com/showpost.php?p=13971291&postcount=110
I had this problem too.. bought a brand new nook color... this is what i did using CWM 3.0.2.8 to boot off SD...
1. used manual nooter 4.5.6
(after applying had all types of popup force close messages about /media this /media that)
2. changed my patitions to match this post
http://forum.xda-developers.com/showpost.php?p=13003431&postcount=166
(Note: Although it said that it didnt write the partitions it actually did)
3. did the 8 boot reset and nook button reset...
(This didn't reset the partitions actually and I had 5.sumthin GB free space not 1GB as before)
4. Manual nooted again then installed Phiremod 6.2 and Dalingrin's Kernel 042411 for cm7....
Sparks1641 said:
I had this problem too.. bought a brand new nook color... this is what i did using CWM 3.0.2.8 to boot off SD...
1. used manual nooter 4.5.6
(after applying had all types of popup force close messages about /media this /media that)
2. changed my patitions to match this post
http://forum.xda-developers.com/showpost.php?p=13003431&postcount=166
(Note: Although it said that it didnt write the partitions it actually did)
3. did the 8 boot reset and nook button reset...
(This didn't reset the partitions actually and I had 5.sumthin GB free space not 1GB as before)
4. Manual nooted again then installed Phiremod 6.2 and Dalingrin's Kernel 042411 for cm7....
Click to expand...
Click to collapse
I did this too and it scared the crap out of me when it kicked me out of fdisk. I thought I hosed it for good. Then when I did the 8 resets it kept going into CWM on the 8th reset. It wasn't until I rebooted it from CWM did it go and reflash itself.
Man that was scary. I thought I had a $250 paper weight.
I was a little freaked out when the fdisk said it didn't work... But reading around I seen that its almost impossible to break it as long as you don't mess with the first 3 partitions so what was the worse case I figured... This must be an issue with the CWR though.. Probably just updating the CWR to format different sizes of the partitions... A format with offset and length feature in an advanced menu... then we can change the sizes to what we want.. But going forward until CWR gets updated every new nook probably gonna have to do the partition change... Not like that's a big deal...
I bought a Nook Color used off craigslist cus they "bricked" it. I thought, no prob, through in the CWM uSD card, erase the data and system, and throw 1.2 on to root.
Can't erase the Data!
They said it was only a few weeks old. I'm guessing it was a refurb with new partition, they tried to root it somehow, and messed it up, then gave up.
Let's hope this fixes it!
Let us know if the partition thing works.. that would be cool.. GL.....
Sparks1641 said:
Let us know if the partition thing works.. that would be cool.. GL.....
Click to expand...
Click to collapse
I did the repartition here:
http://forum.xda-developers.com/showthread.php?t=1094371
and it worked like a charm - finally have CM7 on my 4th Nook!
Thanks to DeanGibson.

XDA + Google + Persistence saved my Phone! -or- How to pull emmc through adb

The Gist:
After much searching and reading and poking I found a way to pull my Titanium Backup data out after my Incredible started boot looping. This might be a no-brainer for most of you, but my linux skills are noob at best. Running ADB while in recovery did not show any /mnt/emmc or path to the internal storage. Relevant XDA threads pointed to the vold.fstab file for hints at where the internal storage lay, but repeating those commands in adb resulted only in errors:
Code:
# Mounts the first usable partition of the specified device
dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
dev_mount emmc /mnt/emmc 3 /devices/platform/msm_sdcc.3/mmc_host/mmc2
And poking around, I could not find any /devices/platform folder. But the "mmc" gave me a hint that it might be related to the things I found in /dev/block:
Code:
# ls
ls
loop0 loop4 mmcblk0 mmcblk1 mtdblock2 mtdblock6
loop1 loop5 mmcblk0p1 mmcblk1p1 mtdblock3 platform
loop2 loop6 mmcblk0p2 mtdblock0 mtdblock4 vold
loop3 loop7 mmcblk0p3 mtdblock1 mtdblock5
#
Some of these I saw were being used by the data, cache, and system partitions. So, I tried mounting emmc to some of the others, but kept getting "file does not exist", and "block device required" errors. But, with XDA, google, and persistance, I hit on the right combination. I unmounted the sdcard, and remounted that existing label to point to the partition where emmc should have been:
Code:
# umount sdcard
# mount -r -t vfat /dev/block/mmcblk0p3 sdcard
after that, I could see all my lost emmc files, and immediately pulled them through ADB.
The Phone:
Stock AMOLED Incredible, running Verizon OTA Froyo. Held off OTA Gingerbread until I had a chance to root it with unrevoked. I only made one small change to build.prop to prevent future OTA updates. I decided to keep Froyo running and used Titanium Backup to kill off some bloatware and make more room. Rebooted many times like this over the last few months, running trouble-free. Many thanks to you all.
INCREDIBLEC XC SHIP S-OFF
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.07.28
Jul 23 2010, 18:06:51
ClockworkMod Recovery v2.5.1.2
(I know - time to update ClockworkMod too...)
The Story:
Ok - so I keep my phone kind of full. The low memory bug plagued me but I kept it at bay by clearing some cache occasionally. The 750MB partition for apps, though, was always almost full. I also still had the original 2GB SDcard that came with the phone, and there was not enough room to make a nandroid backup. So, when I rooted the phone, I had the bright idea to move all the Titanium Backup data over to the 6GB of unused internal storage (emmc). That gave me plenty of room for clockworkmod to do its thing on the sdcard. But, foolishly, after getting a 32GB card, I never moved Titanium Backup back to the SDcard. Neither did I enable the sync to dropbox feature. After all, why back things up if its running perfectly? Well, I learned my lesson the hard way.
With Angry Birds RIO over and done I decided it was time to take a leap, back it up, and uninstall it to make some elbow room. Backup, Uninstall, No Problem. Next, I figure, why not try to restore it to make sure all my scores come back. Force Close, Reboot, No big deal. Hmmm... maybe it needs a little more room to expand the backup before it restores it. So, I uninstalled another large app (which had a minimal effect since it was actually on the sdcard), and tried restoring AB again. But this time everything started force closing all at once. I turned it off, and put it in my pocket since I was heading out. When I restarted it later, it bootlooped with a very loud "DROID!" every 30 seconds during the boot animation. (heh... This was, naturally, during a serious presentation in a quiet room filled with about 150 people... )
Every thread about boot looping suggests solving it by wiping the phone and trying a new or stock rom. That's when I got nervous. Because I could not see my internal storage when booting into recovery. And that's where all my backups were. I went nuts looking for a way, and stumbled on the right combination of commands to pull emmc though adb.
After that, I flashed jermaine151's Stock+ rom and it's been working great. (I should note that following his minimal wiping instructions kept my emmc intact after all, so all my fears were unfounded.) First thing I did was move all my backups to the SDcard and set up sync to dropbox. Next I think I'll try Warm2.3 or MikRunny 1.01 if I'm feeling brave.
Of course, a week later I found this XDA post with almost the exact command I used. That would have saved me about an hour and a half. Hopefully this might help someone else looking for their emmc data after a broken screen or whatever.
I contacted the Titanium Backup developer about the issue - boot looping after restoring on a nearly full device - but haven't heard back yet.
Thanks to all for this forum and your excellent work.

Can't write to internal EMMC

Hi,
I have a nook that I rooted and put a custom rom on back about a year and a half ago. I flashed the ROM to the internal EMMC and CWM 3.2.0.1 was flashed as recovery. If it makes any difference it was a CM9 ROM
Now here's where I'm at. I can run ROMs off the sd-card but they are not stable at all. I get a whole bunch of force closes and such.
When I try and flash a new ROM to the internal EMMC it says it completes, but nothing changes. It is still the previous ROM. When I try and format the /data and /system partitions with the EMMC recovery, it doesn't complete. It says there is an error. When I format with TWRP off an sd card, it says it completes but once again, the rom is not wiped.
I've tried the 8 reboot error method, and it never gets to the stock recovery screen. It keeps booting to the EMMC ROM.
I've tried repartioning the EMMC with leapinlar's zip files. It says it successfully completes, but once again nothing changes.
Ideally I'd like to get the emmc back to stock and try and run a rom off the sdcard.
I've read the threads that I thought were applicable to my issues, but nothing seemed to work. I'm completely out of ideas. Anyone have similar issues or can provide some guidance?
Thanks.
The problem you are having running a ROM from SD is the brand and speed of SD you are using. It needs to be SanDisk class 4.
The reason the 8 failed boot does not work is you replaced the stock recovery with CWM. It needs the stock recovery to be able to complete. See my NC tips thread linked in my signature and read item A12. Assuming you can get it to flash, I have a stock recovery zip there.
I don't understand why the ROMs are not flashing. You say it gives errors when you try to wipe with CWM. What do the errors say? You used the internal CWM and TWRP on SD, but none worked. Try my bootable CWM SD to see if that helps.
I don't understand why my partition zips did not work. I know the newest TWRP will not flash them without giving an error 2 message. Try my bootable CWM SD.
Sent from my Nook HD+ running CM10.1 on Hybrid SD
Thanks for the advice...
I've been using a Patriot class 10 micro sd to run the roms/attempt to flash new roms. Its worked fine before, but I'll try and pickup another one from someplace.
When I try and format /system and /data from the emmc CWM it says "Error formatting /system" or "error formatting /data" after working away for about 5 minutes
Here's what i did:
Created CWM 6.0.1.2 Bootable SD
- Flashed NookColor-emmc-stockrecovery.zip
- Message said successfull.
- tried to restart and old CWM recovery 3.2.0.1 was still installed
Booted into CWM 6.0.1.2 Bootable SD Recovery
- mounted /system and /data
- attempted to format
- Message "Done." for both
- attempted to flash stock 1.4.3 that you have modified for CWM
- install from sdcard complete
- reboot
- Old CynanogenMod bootscreen and old rom still installed.
Using same CWM 6.0.1.2 Bootable Sd Recovery
-flashed NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip and NookColor-emmc-format-partitions-5-6-7.zip
-said success
-attempted to flash stock 1.4.3
- nothing changed. Old rom still installed
One more thing I noticed:
Everytime I login to the currently flashed rom, any changes I make are never saved. For example, if i install an apk or uninstall an app, the next time i can successfully boot into the emmc ROM, those changes are reversed to the previous version. Could it be that the current rom is being stored somewhere and being reflashed when it tries to bootup?
I hate to say this, but it sounds like your internal embedded card has become read only. I have had this happen to SDs but not to emmc. The apps act like they are writing and if you leave the folder and come back, they are not there. It is like they are writing to a ramdisk instead of your SD. You might try booting to a ROM on SD and see if you can write to any of the internal partitions like /cache or /rom and see if they stick. If not, you may only be able to run off SD and maybe not even then. You might have to change your dalvik cache setting on SD so it uses /data instead of /cache.
Sent from my Galaxy Tab running Tapatalk
I tried copying a file to the emmc partition from twrp and it didn't persist after reboot... so it looks like the emmc is set to read only. I don't supposed I can change that using adb and/or software solutions right? It's a hardware issue?
Any guidance on how to change davlik cache to use /data instead of /cache? I'll be happy to get any sort of stable rom running off any SD card.
I was hoping to repurpose the nook as in in car tablet to tether a data connection to my phone and play music and such.
Thanks for your help. I appreciate you taking the time.
canjoe said:
I tried copying a file to the emmc partition from twrp and it didn't persist after reboot... so it looks like the emmc is set to read only. I don't supposed I can change that using adb and/or software solutions right? It's a hardware issue?
Any guidance on how to change davlik cache to use /data instead of /cache? I'll be happy to get any sort of stable rom running off any SD card.
I was hoping to repurpose the nook as in in car tablet to tether a data connection to my phone and play music and such.
Thanks for your help. I appreciate you taking the time.
Click to expand...
Click to collapse
I don't know of anything that can revive it. I never could revive my SD that that happened to.
To make your ROM on SD use /data for all of the dalvik cache, create a file in /data named local.prop. In that file put this line:
dalvik.vm.dexopt-data-only=1
Next time it boots the system file portion of dalvik cache will be on /data along with the installed app portion.
Sent from my stock Nook HD+ using XDA Premium
I now have a stable version of CM 7.2 running off the SD card. I put the davlik cache on the data partition and everything seems to be running pretty smooth.
I'll keep messing around seeing if there is anything to revive the internal emmc, but at least I can use the nook off the SD card again.
Thanks for helping me troubleshoot and figure this out. Cheers.

Lost 0.53 GB of internal storage after reflashing

I had some issues with my Galaxy S8 and I had to reflash the firmware, then TWRP, then Magisk. But there's a problem: I lost some storage space. Before that, my total internal storage space was 53.96 GB, and now it's just 53.53 GB. There's also a preload partition in TWRP's Wipe menu that wasn't there before. Is there any way to get the storage back without having to reflash everything again? Yes, I know it's just 0.53 GB, but I want it back anyway. Also, I'm not a developer or a hacker, just a particularly tech-savvy guy, and I don't know how an awful lot about terminal comands and things like that, so a step-by-step guide would be nice.

Categories

Resources