[Q] Trying to recover from a data wiped SD card - Android Q&A, Help & Troubleshooting

Hi all.
I recently went about updating my tablet, and in the back of my mind I was under the impression that TWRP would backup the internal sdcard's files during the normal backup, so I thought nothing of wiping the internal sdcard. Whoops. It, of course, didn't, and now I find myself with a whole slew of stuff gone. Not much else was written to the internal sdcard (which is on an ext4 filesystem), so I suspect that a good bit of my stuff can still be sitting there in the data graveyard. Hopefully.
Since I'm on Linux and can't mount the sdcard directly (since for some odd reason Linux has issues with MTP), all I've been able to do was this:
I booted the tablet into recovery mode and opened up adb, and ran the following command through the adb shell:
Code:
~ # dd if=/dev/block/mmcblk0p8 of=/dev/block/mmcblk1p1
Where mmcblk0p8 is the internal sdcard with the lost data, and mmcblk1p1 is an external sdcard. I thought that by running that command, I could create a carbon copy of each and every little thing on the old sdcard, write it onto something my computer could read, and then go through the normal recovery process. In this case I planned to use a Linux tool called "extundelete."
Here's where I get stuck. The sdcard appeared to have cloned correctly, given that the entire thing is now filled up and reads as an ext4 filesystem on gparted (when it was previously fat32), but now I can't mount it. And if I can't mount it, I can't restore anything. Here's what I get when I try to mount it:
Code:
Error mounting /dev/sdb at /media/user/57f8f4bc-abf4-655f-bf67-946fc0f9f25b: Command-line `mount -t "ext4" -o "uhelper=udisks2,nodev,nosuid" "/dev/sdb" "/media/user/57f8f4bc-abf4-655f-bf67-946fc0f9f25b"' exited with non-zero exit status 32: mount: wrong fs type, bad option, bad superblock on /dev/sdb,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
So to sum it up, I accidentally wiped my tablet's internal sdcard using TWRP 2.3.3.0, and now I want to recover what was lost during the wipe. Not that it matters, my tablet is a Transformer Infinity in case anyone asks. Though I don't think that's really relevant here.
If anyone knows how to help me, or knows of a better way I should go about getting my data back, that would be, for a lack of better words, super awesome.
Thanks!

BJSerpas said:
Error mounting /dev/sdb
Click to expand...
Click to collapse
Seems you tried to mount /dev/sdb, not /dev/sdb1.
Also, did you make the SDcard partition the same size as the source partition? And what did dmesg say?

Also, http://forum.xda-developers.com/showthread.php?t=1994705 might be of some help..

kuisma said:
Seems you tried to mount /dev/sdb, not /dev/sdb1.
Also, did you make the SDcard partition the same size as the source partition? And what did dmesg say?
Click to expand...
Click to collapse
When I plugged it in, Linux automatically mounted it to sdb and not sdb1. And the external SD card was the same size as the internal one, 32gb. Currently not home so I can't run dmesg at the moment.
And thank you bodh, that looks very useful and is more or less what I was trying to do. I'll have to get on a windows PC it seems, but no issue there. In the meantime, is there a way to write protect the internal SD from the android terminal emulator until I get home? I don't want my old files accidentally overwritten. Or I could just not use the tablet if that's the better option here.
Thanks guys!

I'm not sure you could write protect the internal sd. I've tried changing permissions on it and get errors. You're best bet is probably to go without the tablet use for now.

BJSerpas said:
When I plugged it in, Linux automatically mounted it to sdb and not sdb1. And the external SD card was the same size as the internal one, 32gb. Currently not home so I can't run dmesg at the moment.
Click to expand...
Click to collapse
I'm talking about the number of blocks exactly, not "32gb" or so. And mount /dev/sdb1 manually, don't rely on Gnome failing to mount /dev/sdb.

Related

creating an ext2 partition on internal sd card

There are a few pages on how do do this on Android phones, but I'm having a hard time finding a solution tailored for the gtab. One page suggests using Cyanogen Recovery Image and ADB, however Cyanogen Recovery Image is not maintained anymore, and Clockwork is suggested. So I installed that, and I can boot into recovery mode on my gtab. But after connecting to the PC via usb, trying to use 'adb shell' returns a "device not found" error.
So what's the best way to create an ext2 partition on my Gtab's internal sd card?
Found out through #tegratab that this is not an option for the gtab. I hope to have better luck formatting a new micro sd card to ext2 with the goal of installing Debian on it. Will post my results later.
I hope to have better luck formatting a new micro sd card to ext2 with the goal of installing Debian on it. Will post my results later.
Click to expand...
Click to collapse
great idea -- keep us posted
My new micro SD card came with an mini SD card adapter, so it was no problem to insert it into my netbook running partedmagic and create an ext2 partition. Unfortunately the gtab says it's an unsupported file system. Something is crippled somewhere...
When I was attempting the same thing android wouldn't automount an ext2/3/4 sdcard for me but I could manually mount it through a terminal emulator.
So I downloaded Android Terminal Emulator from the market and typed
fdisk -l
to show the partition tables. Nothing happened. I then tried "su" to give the terminal superuser privileges, but that didn't help.
*sigh*
What am I doing wrong?
I'm using TnT-Enhanced v3.1.4b and have Clockworkmod installed. Perhaps my gtab is not "rooted" as it needs to be? I'm afraid I know little about how these things work...
IIRC all I had to do to mount the ext2 partition was type in mount /dev/block/platform/tegra-sdhci.2/mmcblk2p1 /mnt/sdcard
farmer bobathan said:
IIRC all I had to do to mount the ext2 partition was type in mount /dev/block/platform/tegra-sdhci.2/mmcblk2p1 /mnt/sdcard
Click to expand...
Click to collapse
That did nothing for me. Perhaps you could help me by explaining how you came up with that command - maybe I need to tailor it for my particulars.
I'm still troubled that fdisk -l does not show the partition table. If I type fdisk alone, terminal gives me a list of options I can use (including the -l).
(Sure hope another non-android based OS is developed soon that will run on the gtab.)
Which ROM are you using?
farmer bobathan said:
Which ROM are you using?
Click to expand...
Click to collapse
TnT-Enhanced v3.1.4b. I guess that's the stock ROM then... enhanced.
So do I need to install a different ROM for root access? I have superuser access, but not root?
Root and superuser are the same thing, I think you need a custom kernel such as pershoot's with ext support.

[Q] Tablet possibly bricked - how to get data

Hello, fellow gTablet users!
I'm kinda newbie here, so first of all my apologies to everyone if that was already asked, 'cause I did some research on the matter and couldn't find all the necessary info for solving my particular issue.
Ok, so here's the deal. I was using my gTab for about half-year now. When I received it, I installed VeganTab-7 Ginger Edition on it (thanks for the devs - very nice ROM!) and it worked flawlessly until yesterday. But then something not good happened and the tablet stopped booting. Now it starts from birds screen, goes on to G-Tabdevs screen, after which VeganTab GingerEd boot screen appears, it has flashing letters for a couple of seconds and then tablet goes black and tries to boot again. I guess it's a boot loop so it's kinda soft brick and I'll have to do wipe data/factory reset through CWM to solve the issue. So this isn't the biggest problem - I've already found all the instructions.
The real problem is that I didn't make backup of my data (guilty!), but I don't want to lose some of it, especially the browser data. I was using Opera Mobile, so I guess that its data should be on /data partition. So I'll need an advice on how I can dump the necessary data before doing factory reset!
I've already tried connecting to desktop, using guide from this (http://forum.xda-developers.com/showthread.php?t=1010943) thread (third method from it), but it didn't work, at least on my Win7 Pro x64 SP1: the tablet shows as removable disk, but I can't access it. I tried to mount /data or /sdcard partitions through CWM recovery menu, but it tells me that it can't find /dev/block/... - I guess that's block device, associated with those partitions. So what are my best options of backuping data?
And the last question: I'll probably install some other ROM just to try something different, but unfortunately I don't remember what loader I have. I'm nearly sure that I installed VeganTab for 1.1, 'cause I did it back in May 2011 and there wasn't one available for 1.2 yet. But just to make sure: how can I find my loader version before I do reset? Or maybe I just have to do the reset and look for it when back on stock ROM?
Seriously, guys, doesn't anybody know how to solve these problems?
Boot into CWM first, then try mounting both /data and /sdcard using the CWM menu. Note down the exact error message displayed in each case. Then connect the USB cable and run these ADB commands on your PC:
Code:
C:\> [B]adb shell dmesg >dmesg.txt[/B]
C:\> [B]adb shell fdisk -l /dev/block/mmcblk3 > fdisk.txt[/B]
C:\> [B]adb shell fdisk -l /dev/block/mmcblk2 >> fdisk.txt[/B]
Post the error messages and those 2 .txt files here.
Thank you for reply, rajeevvp.
When I'm trying to mount /data and /sdcard it says respectively:
Code:
E:Can't mount /dev/block/mmcblk3p2
(No such file or directory)
Error mounting DATA:!
E:Can't mount /dev/block/mmcblk3p1 (or /dev/block/mmcblk2p1)
(No such file or directory)
Error mounting SDCARD:!
Unfortunately I didn't have ADB installed. Now I'm trying to use the guide from here: http://forum.xda-developers.com/showthread.php?t=902860, but fail on step 4, cause there is nothing like "Nvidia harmony" appearing under other devices in my dev manager, just "Nvidia Tegra 2 USB Device" under Disk Drives and "USB Mass Storage Device" under Universal Serial Bus Controllers. I guess these devices are gTablet's internal memory presented as disk drive...
I'll try to install ADB and then write back how it worked.
Interesting error messages. Now I really have to see those text files.
If you're having problems installing ADB on Windows, try using Linux.
Ok, thanks you very much! I'll try that, but unfortunately tomorrow, as it's already too late here.
Btw, I read your post about linux - you're suggesting Knoppix Live CD there. Is it mandatory to use it? I mean I already have PartedMagic live CD burned, maybe I could use it instead...
anary said:
I mean I already have PartedMagic live CD burned, maybe I could use it instead...
Click to expand...
Click to collapse
If sudo and adb work, then no problem.
rajeevvp said:
Boot into CWM first, then try mounting both /data and /sdcard using the CWM menu. Note down the exact error message displayed in each case. Then connect the USB cable and run these ADB commands on your PC:
Code:
C:\> [B]adb shell dmesg >dmesg.txt[/B]
C:\> [B]adb shell fdisk -l /dev/block/mmcblk3 > fdisk.txt[/B]
C:\> [B]adb shell fdisk -l /dev/block/mmcblk2 >> fdisk.txt[/B]
Post the error messages and those 2 .txt files here.
Click to expand...
Click to collapse
Ok, I finally managed to do it. Sorry for the delay.
The files are attached. Did everything how you told me.
Actually I don't think that I understand too much in Android inner mechanics But having looked through these files, I thought that inner sdcard device (mmcblk3) doesn't seem to produce any strange behavior...
Btw, thanks a lot for your advice about using Knoppix - it's really very easy and handy!
anary said:
But having looked through these files, I thought that inner sdcard device (mmcblk3) doesn't seem to produce any strange behavior...
Click to expand...
Click to collapse
You have lost your /data partition altogether. You are supposed to have 2 partitions on that internal SD card: a 14GB FAT32 partition and a 2GB ext3 partition. You only have a single FAT32 partition spanning the entire SD card now.
I may be able to help you get both partitions back if you give me these details:
1. How and when did this happen?
2. Current ROM.
3. Current version of CWM.
4. Did you try to repartition the (internal) SD card recently?
5. Have you ever repartitioned the internal SD card? If yes, then using which version of CWM?
6. After you noticed the problem what steps did you take to fix the problem?
Yeah, I remember I was curious where it stores OS's kernel if all it has is FAT32 partition - now I get it...
Ok, here are the details:
1. I don't really know what has happened, but I guess that it happened when I tried to use tablet like cardreader for microsd card. During that I sort of formatted external sd - maybe that actually was internal memory? I checked through file manager though, and all the files seemed intact...
2. VeganTab GingerEd from this thread: http://forum.xda-developers.com/showthread.php?t=1031250. I'm pretty sure that I didn't install anything except for it.
3. Don't know. But it says ClockworkMod Recovery v2.5.1.1-bekit-0.8 in recovery menu, so I guess its version is maybe 0.8.
4. No I didn't, at least intentionally.
5. I think I did it just once, when installing the ROM. I'm pretty much sure that I used this instructions for repartitioning: http://viewsonic-gtablet-for-dummies.webs.com/repartition.htm (not exactly this, but I did the same as it's written there). To install the ROM I used the instructions from the ROM thread, mentioned above. I didn't whant to do a lot of modding, just wanted the device to work at least better than with stock ROM, so didn't try to change any other low-level things.
6. I just tried to mount partitions through CWM recovery and I tried wiping out cache partition and Dalvik cache. Nothing else.
anary said:
Yeah, I remember I was curious where it stores OS's kernel if all it has is FAT32 partition - now I get it...
Click to expand...
Click to collapse
The OS kernel is not stored on the SD cards. They're stored on a "boot" partition on the NAND flash. And, if the OS was messed up you would get hung up on the initial splash screen (the one with the 3 birds)--you wouldn't go into a boot loop.
1. I don't really know what has happened, but I guess that it happened when I tried to use tablet like cardreader for microsd card. During that I sort of formatted external sd - maybe that actually was internal memory?
Click to expand...
Click to collapse
That's what caused this problem. CWM-2.5.1.1-bekit-0.8 does not work on the external SD card (but, CWM-2.5.1.3 and CWM-4.0.1.5 do).
Did you format the internal SD card using CWM?
I checked through file manager though, and all the files seemed intact...
Click to expand...
Click to collapse
Files where? The internal SD card or the external one? And, how did you check this? After formatting the internal SD card, the very next boot into the ROM would've put you into a boot-loop because the /data partition is missing.
I think I may be able to get stuff from /data, but, everything on /sdcard is most likely gone. (Actually, the files are most likely all there, but, without direct access to the tablet, it's very difficult to get the retrieve any of them.) Just don't touch the tablet until I've figured out the commands you will have to use.
That's what caused this problem. CWM-2.5.1.1-bekit-0.8 does not work on the external SD card (but, CWM-2.5.1.3 and CWM-4.0.1.5 do).
Did you format the internal SD card using CWM?
Click to expand...
Click to collapse
No, I was going to format external SD card and I tried to do it through Android (or maybe VeganTab) menu. I think that doing this, I could accidentally format internal SD, but I'm not sure this could be done from within the OS. During the same logon session I checked files on internal SD with file manager and all of them were where they should have been. So I thought that all was ok. But when I rebooted next time, it wasn't booting... That's why I told you that maybe it was because of formatting.
And just to be clear: I didn't do anything using CWM after it stopped booting, apart from wiping system and Dalvik caches.
Do you have a large capacity micro SD card (anything larger than the maximum amount of data that's currently on the internal SD card) that you can use to save retrieved data into?
rajeevvp said:
Do you have a large capacity micro SD card (anything larger than the maximum amount of data that's currently on the internal SD card) that you can use to save retrieved data into?
Click to expand...
Click to collapse
Yep. Won't be any problem.
anary said:
Yep. Won't be any problem.
Click to expand...
Click to collapse
OK. Format that micro SD to contain a single DOS partition; then we'll proceed.
rajeevvp said:
OK. Format that micro SD to contain a single DOS partition; then we'll proceed.
Click to expand...
Click to collapse
Ok. That's done.
Boot into CWM, go into the "mounts and storage" menu, unmount all mounted partitions, connect the USB cable, and run these commands using ADB--do not back out of that "mounts and storage" menu while we're fixing this. We're trying to see if the data on the current /sdcard partition can be retrieved.
Code:
$ [B]adb shell[/B]
~ # [B]mount -r /dev/block/mmcblk3p1 /sdcard[/B]
~ # [B]ls -l /sdcard[/B]
If the ls listing looks OK, then we force a filesystem check before copying the data to the external micro SD card:
Code:
~ # [B]mount -r /system[/B]
~ # [B]umount /sdcard[/B]
~ # [B]/system/bin/fsck_msdos -f -y /dev/block/mmcblk3p1[/B]
If the listing doesn't look OK, then the data on /sdcard is lost.
Post the exact output of each command.
Ok, mount says this:
Code:
mount: mounting /dev/block/mmcblk3p1 on /sdcard failed: Invalid argument
and ls after that gives no output - I think it shouldn't give any, 'cause I didn't mount anything...
Does this mean I'm screwed?
Try this mount command:
Code:
~ # [B]mount -r -t vfat /dev/block/mmcblk3p1 /sdcard[/B]
The same result.

GP 5.0 need help for reformatting internal memory

Hello All,
I need help from experimented people because while trying to reformat my YP-GB70 - 5.0 korean version (internal memory went wreck after some bad manipulations in testing new roms)
Problem: partition14 is no more available, same for 15 and above and have to be reformatted through adb/fdisk.
Reformatting: OK but!
This is a normal operation I've done it 3 times already ,but the issue I am facing now is because Fdisk does not want to open the main /dev/block/mmcblk0 where the partitions are located and visible (excepted n°14 to 17 that are no more linux formated).
I am root access and I am able to access and reformat /dev/block/mmcblk1 that is my external SD card, so problem seems to be somewhere around fdisk instruction to open main memory .
Here attached the overall listing for verification.
Your suggestions are welcome, i need this issue solved for me, sure, but for any other people that can face the same behavior.
Anybody knows the trick? or any advice to help?
The most efficient way to do this is getting a full dd dump of another device. From adb in a working device:
Code:
mount /dev/block/mmcblk0p1 /sdcard
dd if=/dev/block/mmcblk0 of=/sdcard/image.img
Then dumping on your device:
Code:
mount /dev/block/mmcblk0p1 /sdcard
dd if=/sdcard/image.img of=/dev/block/mmcblk0
This command usually takes about 45 minutes or more to complete (you have 32gb internal storage).
Another way you can recover your device, but it's more risky:
DON'T DO IT UNLESS YOU HAVE THE OUTPUT OF A WORKING DEVICE (http://forum.xda-developers.com/showpost.php?p=21915742&postcount=3 )
Using fdisk /dev/block/mmcblk0
Recreate the partition table (if i'm not mistaken the command is o).
Then, you need to create p1 (primary), which is extended and uses all the device storage. The rest of partitions are logical (inside p1).
Make sure you replicate exactly the partition table. DON'T WRITE THE PARTITION TABLE UNLESS YOU'RE DONE. DON'T REBOOT THE DEVICE UNLESS YOU'RE DONE. If you do it --> hardbrick.
Many thanks for your prompt and precise answer.
I am going to ask for a GB70 dump with low confidence in getting it...
I will investigate the "hard" repartitionning way you suggest, I am not sure fdisk will allow me to modify anything because the main memory access is permanently denied.
(/dev/block/mmcblk0)
I already have my device partition table from previous issue I had in march.
regards
memory Issue under control
rumirand said:
The most efficient way to do this is getting a full dd dump of another device. From adb in a working device:
Code:
mount /dev/block/mmcblk0p1 /sdcard
dd if=/dev/block/mmcblk0 of=/sdcard/image.img
Then dumping on your device:
Code:
mount /dev/block/mmcblk0p1 /sdcard
dd if=/sdcard/image.img of=/dev/block/mmcblk0
This command usually takes about 45 minutes or more to complete (you have 32gb internal storage).
Another way you can recover your device, but it's more risky:
DON'T DO IT UNLESS YOU HAVE THE OUTPUT OF A WORKING DEVICE (http://forum.xda-developers.com/showpost.php?p=21915742&postcount=3 )
Using fdisk /dev/block/mmcblk0
Recreate the partition table (if i'm not mistaken the command is o).
Then, you need to create p1 (primary), which is extended and uses all the device storage. The rest of partitions are logical (inside p1).
Make sure you replicate exactly the partition table. DON'T WRITE THE PARTITION TABLE UNLESS YOU'RE DONE. DON'T REBOOT THE DEVICE UNLESS YOU'RE DONE. If you do it --> hardbrick.
Click to expand...
Click to collapse
PROBLEM SOLVED:
I have applied your guide lines and I finally succeeded turning back the device to life.
This was only possible because of the work you and Adamoutler's team have done.
Was mandatory your RJ14 kernel (V5.02.7)(- 2.8 also working ) and the "Unbrickeable resurrector" stuff .
Rebuilt the device 17 logical memory partitions and back to life again.
(see attachement)
Details for interested people under request.
More than many thanks again for your great help.

[Q] No Partitions Showing in Parted - Hardware Problem?

I have a Nook Tablet 16GB. It won't even power on to the "n" logo screen unless there is a CWM SD Boot card installed. I get mount errors once inside CWM.
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/
I've tried the Factory Restore (repart.img) and it runs through and tells me the device will shutdown in 5 seconds. (The other times I've used this it sits at a green check mark until I shut it down manually) This doesn't resolve the issue or make any changes at all.
I've tried Adam's Ubuntu method and the device boots to the SD card but sits at a blank screen after a few seconds and does nothing, even when left on over night. This doesn't resolve the issue or make any changes at all either.
I can connect to the device in ADB and the plan was to use parted to fix some partitions using Veronica's methods, but when I run the parted /dev/block/mmcblk0 print command no partitions are found at all on the device. I'm never prompted to fix any partitions either. The only thing it sees in the ext sd card partition. In the past when I've done this it shows 11 partitions with some details. This time it shows nothing. I am unable to find any information anywhere as to what to do next.
It is as though the internal SD Card (memory/hard drive whatever you call it) isn't working or detected by the system any longer.
Does anyone have any recommendations on what to try next? Please help!
I'd suggest burning a CM10.x pre-made SDcard image (e.g., cm_acclaim_10.1_21APR2013_HD_SDC_IMG.7z from Succulent's repo http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/) and see if your NT can successfully boot and run a ROM from SDcard. If it does then you can proceed to restoring stock ROM (or flashing CM10) internally on emmc.
Also, refrain from reformatting any partition (other than possibly /cache, /system, /data, if you have good reason to do so and know what you're doing), as you risk making the problem worse -- see http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31.
digixmax said:
I'd suggest burning a CM10.x pre-made SDcard image (e.g., cm_acclaim_10.1_21APR2013_HD_SDC_IMG.7z from Succulent's repo http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/) and see if your NT can successfully boot and run a ROM from SDcard. If it does then you can proceed to restoring stock ROM (or flashing CM10) internally on emmc.
Also, refrain from reformatting any partition (other than possibly /cache, /system, /data, if you have good reason to do so and know what you're doing), as you risk making the problem worse -- see http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31.
Click to expand...
Click to collapse
I made an SDCard using Succelent's repo and was able to boot to the Cyanoboot Bootloader but a few seconds later it just went to a blank screen. I rebooted and could get into recovery by holding the "n" button and selecting that. When I select to boot from SDC it just goes to Bootloader and then goes blank. It never boots into the OS.
I never mess around with partitions and I'm not sure how this thing got this way. I purchased it from eBay as a tablet for my daughter. It did say the device was bricked but that the hardware was okay. I've seen bricked devices in the past and the repart.img (Factory Reset) has always resolved the problem. I have a Nook Tablet that my son has been using so I've become pretty familiar with the basics of rooting, loading CWM, TWRP, Cyanogenmod, etc. But I've never seen it were I get mounting errors inside of CWM and am unable to flash anything. It won't even mount the external SDCard once inside CWM.
Not sure what to do and I hate to give up on this. Any help would be greatly appreciated.
Assuming that SD-based CWM is functional, you should try flashing flash_kernel_acclaim_30MAR2013_HD_SDC.zip under the heading "Flash this if your NT doesn’t boot newer kernel" in the SDC image section of http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/.
Also, you should try "wipe /cache" while in SD-based CWM recovery to see if that would take care of the /cache related mounting errors you encountered.
This happened to me last year. There is a post in development section about fixing partition table by So****e. It's the last resort, but worked for me.Also, Adam Outlers Ubuntu method loses your serial number, gone forever. Good luck
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
DEjaVu
Happened to my first nookT not to long ago....It died but the best advice I can give has already been given try not to erase more stuff. Digimax helped me not to long ago. Make sure you format your sdcards correctly and if you can flash a recovery or boot into it you should be able to use one of Succulents cards. Good luck
digixmax said:
Assuming that SD-based CWM is functional, you should try flashing flash_kernel_acclaim_30MAR2013_HD_SDC.zip under the heading "Flash this if your NT doesn’t boot newer kernel" in the SDC image section of http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/.
Also, you should try "wipe /cache" while in SD-based CWM recovery to see if that would take care of the /cache related mounting errors you encountered.
Click to expand...
Click to collapse
I tried to download the file you suggested, but the actual file isn't there any longer. When I click on the download link it takes me to GOO to download it, but said file can't be found. I also tried wiping my cache partition again from inside cwm, but no luck. Still getting the mount errors.
I believe the real issue is that my device doesn't see /dev/block/mmcblk0 (or rather is sees it as the external SD card). there is no /dev/block/mmcblk1 either. I thought perhaps the internal and external were swapped, but that doesn't appear to be the case. So since the device can't recognize the internal SD card I don't think I will be able to get anything to flash until I get that resolved first. I'm certain that is why Adam Ubuntu fix and Meg's reprt.img aren't working.
Probably the only way to do that, if it is even possible, is to do it through ADB. Veronica has a thread that shows how to recreate all of the partitions, but when I attempt to do that it doesn't see the internal storage at all so I can't even get started.
I really hate giving up on anything so I will keep trying as long as it takes if I know it is possible to fix this, but I'm not sure what steps to take next to try and get the internal storage recognized.
For all I know it could be a permission issue.
Do you know any commands I can run from ADB Shell to try and get the internal storage recognized?
When I run a list command from ADB shell I get the following:
~ # ls
ls
boot fstab.acclaim sd-ext
bootdata init sdcard
cache init.rc sys
data internal_sd system
datadata proc tmp
default.prop recovery ueventd.acclaim.rc
dev res ueventd.goldfish.rc
emmc rom ueventd.rc
etc root
external_sd sbin
~ #
So it looks like the internal storage is working after all and I can get into some of these directories and files and CAT or TAIL them. Perhaps the MBR is messed up or something?
skelnik said:
I tried to download the file you suggested, but the actual file isn't there any longer. When I click on the download link it takes me to GOO to download it, but said file can't be found.
...
Click to expand...
Click to collapse
You can try one of Succulent's more recent 10.2 builds listed at http://iamafanof.wordpress.com/2013...id-4-3-for-nook-tablet-imgsdc-boot-09aug2013/ which he uploaded onto Media Fire: "cm_acclaim_10.2.0-RC0_13OCT2013_HD_SDC_IMG.7z (mirror)".
You might also want to take a look at Succulent's recovery tools (in particular flash_stock_1.4.2.zip) at https://github.com/succulent/acclaim_recovery_sdcard.

can't mount internal sdcard exfat

I formatted my internal sdcard to exfat by mistake while trying to simply format it(for some reason windows defaulted to exfat instead of fat32) now my sdcard won't mount and I can't format it in windows and can't mount it, any way you guys think I could get it back to fat32 and working again.
KainXSS said:
I formatted my internal sdcard to exfat by mistake while trying to simply format it(for some reason windows defaulted to exfat instead of fat32) now my sdcard won't mount and I can't format it in windows and can't mount it, any way you guys think I could get it back to fat32 and working again.
Click to expand...
Click to collapse
I think you would have to fix it while in recovery - either with adb parted (example: http://mobilecon.info/how-to-partition-sdcard-using-parted-partition.html - don't use those commands, they will be specific to your device and what block the internal storage is located on) or possibly GParted in Linux?
What device do you have? Depending on what kind of storage set up, it might be possible to reformat everything by restocking it with the original firmware, but I am not positive on that.
es0tericcha0s said:
I think you would have to fix it while in recovery - either with adb parted (example: http://mobilecon.info/how-to-partition-sdcard-using-parted-partition.html - don't use those commands, they will be specific to your device and what block the internal storage is located on) or possibly GParted in Linux?
What device do you have? Depending on what kind of storage set up, it might be possible to reformat everything by restocking it with the original firmware, but I am not positive on that.
Click to expand...
Click to collapse
yup, I had to use parted and delete the sdcard block then recreate it as fat32
KainXSS said:
yup, I had to use parted and delete the sdcard block then recreate it as fat32
Click to expand...
Click to collapse
Right on. Mind posting what you had to do, for future reference? I'm curious and could come in handy if I find myself in that situation.
es0tericcha0s said:
Right on. Mind posting what you had to do, for future reference? I'm curious and could come in handy if I find myself in that situation.
Click to expand...
Click to collapse
what I did was go into cwm then run
adb shell
su
parted /dev/block/mmcblk0 (to see what block the sdcard is)
rm (block #) (remove entire block)
mkpartfs
-block name
-format type (I needed fat32)
-start
-end
then start creating block and waited till done.
KainXSS said:
what I did was go into cwm then run
adb shell
su
parted /dev/block/mmcblk0 (to see what block the sdcard is)
rm (block #) (remove entire block)
mkpartfs
-block name
-format type (I needed fat32)
-start
-end
then start creating block and waited till done.
Click to expand...
Click to collapse
Right on. Hope it doesn't come to that, but I fix people's phones for a living, so never know when someone will have an issue like this.

Categories

Resources