I'll try to be brief...
Background: I bought a used Samsung Galaxy Tab knowing full well that there was something wrong with the internal 2GB memory. The previous owner had installed CM10.1 nightlies on the SD card and was booting the tablet from the external SD card, totally bypassing the internal memory.
The goal: to recover the internal memory
Steps I've taken:
1. Removed external SD card so it doesn't boot from SD card
2. Successfully used Heimdall to re-flash to stock (VZW 2.3.5 Stock Root) - after the flash the tablet attempted to reboot. It went to the VerizonWireless screen and I think went into a bootloop.
3. Turned off the tablet and booted into the stock recovery. From the recovery menu I tried to reboot the system, which gave me the following error:
"failed to mount data"
4. Turned off the tablet and booted into stock recovery. I wiped the cache partition. Then I tried to wipe data/factory reset and got the following error:
"E:failed to mount /data (Invalid Argument)
E:install_application_for_customer: Can't mount /data
your storage not prepared yet. please use UI menu for format and reboot actions"
5. Using Heimdall I successfully flashed ClockworkMOD recovery, and booted into CM recovery.
6. I attempted to reboot system now and the tablet just hangs at the Samsung logo, doesn't even go to the Verizon screen.
So obviously there seems to be a problem with the /data partition. I'm not sure exactly what to try at this point. How do I mount /data? Can this be done from within CM recovery?
Any advice or things to try would be greatly appreciated.
Related
Just got my color nook today.
Trying to get my nook color up and running on a custom rom. But I am lost, there appears to be quiet a few ways to start and I am not sure the best and most updated method.
So as of now I am not rooted, pretty much pulled it out and charged it, I checked and its running 1.1.0 out of the box.
I'm going for the Phiremod rom, and I want to boot from internal memory not SD card.
Would really appreciate some links to what I need.
Thanks
lost just lost
so i ended up using autonooter
then made a sd card with clockworkmod on it
installed clockwork mod, installed a zip just like i would on a phone
and .... no go it wont boot to android just back to clockworkmod, what am i doing wrong?
also getting an error in clockwork
"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"
hd2brick said:
so i ended up using autonooter
then made a sd card with clockworkmod on it
installed clockwork mod, installed a zip just like i would on a phone
and .... no go it wont boot to android just back to clockworkmod, what am i doing wrong?
also getting an error in clockwork
"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"
Click to expand...
Click to collapse
The errors are normal; since you don't have any cache or its not mounted.
You burned a CWM image on a SD card and installed the Phiremod rom from his Zip file in CWM?
Then you only have to remove the sd-card while in CWM and then choose 'reboot device' (first option in main menu) (sometimes you get back in CWM but reboot a couple of times and it should boot Phiremod CM7 off the emmc.)
(if the Nook finds a bootloader on the SD card, it'll load that instead of the internal emmc memory. )
too used to phones
hey thanks so much for the reply
that would have solved the problem, but i was running cwm on internal and using a different sd card
found out what was wrong, i was doing the wipes like you would on the phone
i.e. wipe data/factory reset and cache there
(instead of from inside mounts and storage)
finally up and running after 4 hours haha
thanks again
Just flashed a new 1.1.0 to CM7; no need for autonooter if you're going custom ROM straight off.
1. Download the SDCard-bootable CWM. Burn to MicroSD with WinDiskImage32 (needs to be run as Admin for block-level access if you get write errors)
2. Drop on your ROM .zip of choice.
3. Drop on the gapps .zip
4. Eject, insert into Nook, boot up.
5. TAKE A BACKUP. This is your 'oh crap' restore point.
6. Install zip from SD; install ROM. Do the same, install gapps. Wipe cache and data.
7. Remove MicroSD, boot NC. If it works, format the MicroSD card in your computer as FAT32 (after copying off your backup, under the clockworkmod directory), insert into NC, good to go. If it bombs out, redo step 4-7, skipping 5.
If you can't get it to load, boot from MicroSD and restore your backup. No harm, no foul. Keep a copy of this 'gold' backup on your computer. I forgot to do this and ended up blowing my original away when I reformatted my MicroSD.
Update your kernel
Keep up to date with Dalingrin's latest kernel, he keeps pushing the overclocking to new heights every few days it seems
http://forum.xda-developers.com/showthread.php?t=925451
He due to release a kernel sometime soon that can run at 1.3Ghz...
i was running my salsa rooted with CWR and data-2-sd_ext3 done exactly the same way as given in bigbear's noob guide everything was running smooth used it for almost 2 months,but yesterday when i started my device after it was powered off due to empty battery(nothing new happens to me all he time) it was stuck in a bootloop. so this what i did to get out off it
1 i went into recovery mode and tried to restart the device from there,but was stuck in the same bootloop
2 i had backups in my sd card so decided to do a restore,but during the tripple wipe in the wipe data/format there was some problem with mounting sd card so the commands came like error mounting sd card, skipping format,data wiped.i ignored and went forward to wipe cache and dalvic and both was successful. then when i selected restore in backup and restore menu it failed and the command came like E: cant mount /sd
3 after trying to restore a few times with no use i chose to reboot the device but when i rebooted from recovery it gave me the same bootloops(even after the triple wipes)
4 after that i removed the memory card out of the device and then powered on and it booted normally.i also have the superuser and the fb button which i revamped using button rewamper is doing what i made it to do (use as a power button).all my phone data is gone(i don't care)
Now i am confused as what should i do next
should i format the sd card and will the format also delete the partition which i made,if yes after the format when i will make the partition again and put the sd card again in the device will i have to flash the data-2-sd ext3 again (i think it should be there because the root and the F button rewamp is there(not the app but the function))
plzz guys help,i am confused
xdajiar said:
i was running my salsa rooted with CWR and data-2-sd_ext3 done exactly the same way as given in bigbear's noob guide everything was running smooth used it for almost 2 months,but yesterday when i started my device after it was powered off due to empty battery(nothing new happens to me all he time) it was stuck in a bootloop. so this what i did to get out off it
1 i went into recovery mode and tried to restart the device from there,but was stuck in the same bootloop
2 i had backups in my sd card so decided to do a restore,but during the tripple wipe in the wipe data/format there was some problem with mounting sd card so the commands came like error mounting sd card, skipping format,data wiped.i ignored and went forward to wipe cache and dalvic and both was successful. then when i selected restore in backup and restore menu it failed and the command came like E: cant mount /sd
3 after trying to restore a few times with no use i chose to reboot the device but when i rebooted from recovery it gave me the same bootloops(even after the triple wipes)
4 after that i removed the memory card out of the device and then powered on and it booted normally.i also have the superuser and the fb button which i revamped using button rewamper is doing what i made it to do (use as a power button).all my phone data is gone(i don't care)
Now i am confused as what should i do next
should i format the sd card and will the format also delete the partition which i made,if yes after the format when i will make the partition again and put the sd card again in the device will i have to flash the data-2-sd ext3 again (i think it should be there because the root and the F button rewamp is there(not the app but the function))
plzz guys help,i am confused
Click to expand...
Click to collapse
Try reflashing stock ROM with triple wipe
Sent from my Galaxy Nexus using Tapatalk 2
how can i flash ROM when there is a problem mounting sd card? and i wanted to know if someting wrong with the sd card can cause bootloops,as the phone booted fine without it. I think i will format the sd card make the partition again put it back in and flash data-2sd ext3 (which i am not sure off ),my questions are
1 will the sd card format remove the partition which i made earlier?
2 will i have to flash the data-2-sd ext3 again after popping in the sd card?
1.YES, if you format it would remove the EXT3 Partition
2.You would have to make FAT32 Primary Partition and EXT3 Primary Partition Secondary in Mini-tool
2.Yes, flash the script after setting up the partition
Done guys
did the sd card format using minitool partition wizard removed all the partitions,then made it again.then installed bussybox version 1.18,got the data-2-sd ext3 into the sd card flashed it using CWR,and rebooted using CWR and done.
srry BB i should have given it a shot before harassing you ,TY anyways:victory:
Lol I did kinda tell u but hey ho its done
BigBearEvo is using Xparent Tapatalk ICS on CM10
I tried to flash the ROM Nitrogen [Android UnChained] yesterday, and since I had a ext3 partition on my SD-Card i used his tool to convert it.
After that the ROM was working fine but wasn't recognizing my SDCard. Long story short, I ended up today making a full flash, Stock ROM 2.3.6 with ODIN because my phone was stuck in a bootloop for the recovery.
Now I flashed the CWM with Odin but phone does not boot the ROM.
I removed my SDCard and tried to make a Factory Reset in Recovery and when it tries to format /sd-ext I got the message: "E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p2"
When I insert the SDCard and try to make the Factory Reset the Recovery just go back to the initial screen.
When I try to mound sd-ext it just says: Error mounting /sd-ext! If i choose in "mounts and storage" > "format /sd-ext" it goes back to initial screen, like rebooting the Recovery.
Please help me with that. I think the /sd-ext partition is messed up after I used the tool to convert it "PSN's Ext4 conversion tool".
Also my computer is Windows 8, couldn't recognize phone in download mode, used my friends Windows 7 computer to flash Stock ROM and CWM with ODIN.
And now I formated my SDCard and I have the primary partition as FAT32 and the second partition as EXT3, logical, with MiniTool.
TL;DR
Phone doesnt boot ROM, can't mount sd-ext!
edit:
Format the SDCard and recreated the partition with CWM, now I can format without a problem. Will try to flash another ROM now.
It's weird, when I flash the Stock ROM with Odin, and on the first boot it says: Updating package, and suddenly there's an error mounting /data
edit:
Fixed after creating the sd-ext as EXT4 with minitool and as Primary. Reinstalled the Nitrogen ROM and now my sd works. Phone is back
I am trying to get my Son's Captivate back up and running.. while it has no phone service, he uses it all day long. It was running Cyanogen Mod 10 .. he sat it down to eat.. when he came back the screen was black with the buttons lit up and no response.
He did a battery pull to restart it and it came back looping Error to mount /SDcard and a count down.
I got it into recovery and am not able to mount /data or /emmc. And it is failing to install a ROM from zip.
I tried using "I897UCKK4 Stock, Wipe, with options to install Bootloaders, Param,and Re-partition-One-Click" and it runs through the process.. flashing Kernal, Modem, FactoryFS, DBDataFS and CACHE successfully.. then the device reboots and goes through a few things on screen, and fails on Formatting /data ( E:format_volume: rfs format failed on /dev/block/mmcblk0p2 ) but everything else says success. Hitting "reboot system now" says that it cant copy the log because of failure to mount /emmc.. then reboots to the same recovery and does the copy of Media and Appling Multi-CSC (their spelling mistake not mine) over again.
Flashing back to a CWM 6 recovery and still no mounting of /data or /emmc. And it just boots right into the recovery.
I tried --repartition with Heimdall and it said it uploaded the S1JE4.pit fine. Same things..
So is there anything I can to to test the internal storage to KNOW if it is faulty or is there anything else I can do?
I would really like to get this thing working again for my little dude.. he is so sad as all heck to not have his Android Buddy. :crying:
Seems likely internal sd may be dead, particularly if someone ran ICS on it at some point. If you have an external sd card, at least 8GB, this thread may help-
http://forum.xda-developers.com/showthread.php?p=21439417
you could use cm10.1 instead of the ICS rom mentioned in the thread.
Sent via Monty Pythons Flying Circus
Perhaps someone can help. I've read a lot of the great content here but I've hit a wall.
A few weeks ago my ovation device was running cm11+cwm but began random rebooting. Clearing the cache+dalvik only helped briefly.
I tried an upgrade with a twrp 3.0.0.0 (using the amazing multiboot recovery SD), but it hung formatting the cache partition (I waited about an hour). Tried again, same thing.
I used adb shell to fix a blank file system type on the cache partition but was only successful in creating an ext2 partition there. I got cm13 booting but it trebuchet kept crashing. I tried twrp again and flashing a different image and tried a factory reset. Big mistake.
Now when I try to boot any recovery SD it doesn't boot all the way. Using adb shell, my dmesg shows that umount is hanging. No emmc partitions seem to be mounted. The partition data exists in dmesg but calls to parted hang. Mkfs.ext4 also hangs (naturally).
So I've lost the ability to fully boot recovery SDs (they are probably hanging when they try to mount the emmc partitions). As such I can't flash a recovery. I have a clockwork backup that has a system.ext.tar file in it, but I don't know how to use it at this point.
I can't mount /rom so I'm worried.
Is my emmc shot? Is there any way to tell?
Thanks!
Would a noEMMC SD be safe?
I guess what I was hoping to do was use adb to completely wipe and restore the device to a sane state, which would include repartitioning and formatting the emmc partitions. Is that possible? Maybe not at this point.
I guess another question would be: if my NookHd+ emmc is technically working but currently unrecoverable, is it possible for me to safely use a NOemmc SD card? There seem to be some warnings about those wrecking emmc but I can't find any technical explanation as to why.
Based on further diagnostics, my emmc is one of the faulty Samsung models and so I think the crashes and ultimate recovery failures were the failure of the emmc.
I've successfully installed 10.1 noEMMC on one microsd. Runs Okay but a lot of apps I am interested in don't work on android from this vintage.
I tried to install 4.4.4/CM11 noEMMC but it can't mount the necessary partitions as per the install process on the iamafanof Wordpress page. I also see SELinux errors in the twrp recovery log. Does anyone know how to overcome this mount issue that apparently impacts some people.
Assuming there are others out there who find this useful, I have some updates.
I was determined to figure out why the CM11 NoEMMC was not working for me but CM10.2 noEMMC works fine. I get the error that many others get: unable to mount /boot, /data, /system.
I used adb shell to connect to the twrp 2.8.0.0 that runs when you boot the CM11 noEMMC SD boot/install image and compared the Linux system differences between that and the system you can see connected to the cwm 6.0.4.? That runs when you boot the CM10.2 noEMMC SD boot/instal image.
First things first: cm10 noEMMC remaps the internal emmc as /dev/block/emcblk1 and the external microsd card slot as blk0 (this is swapped from the norm and correct for a situation where you want to install to the SD as though it were the internal device).
CM11 noEMMC does not do this. I think that the author assumed that if your emmc is bricked then the system won't see your /dev/block/emmcblk0 at all so your external sdcard will take over that number. Clearly that's true for some, but it's not true for me.
I also began poking around the post boot script (in /sbin) to see how the cm11 noEMMC prepares the partitions on the Sd card and to see what Command it uses to create the data partition
Here's the kicker. I was able to mount my emmc rom partition and copy off all that data with an adb pull. I was able to initialize the cache partition (9) as a blank ext4 partition. I was even able to initialize the user partition (10) as ext4... Though I'm not sure that's right. I began mounting partitions and got greedy and tried to mount the whole partition map and it failed.
So, there's something wrong with (at least) one of my partitions. When recovery tries to mount the partitions, mount hangs and recovery fails to fully load. The noEMMC sd card got me around this because it doesn't try to mount any of the emmc partitions let alone all of them.
So, does anyone know if I can make new file systems on every partition and if by luck I'm able to get a twrp or cwm to fully load, will flashing a stock recovery put data on all those partitions?
Thanks
Sorry to resurrect this thread, But it exactly speaks to my issue. You mention that the blk0 and blk1 devices need to be switched for cm11 image to mount partitions properly. Does anyone know specifically where this might be done. Can files of the existing nov4 cm11 image be altered to reverse these two devices?
CalculonsTalent said:
Assuming there are others out there who find this useful, I have some updates.
I was determined to figure out why the CM11 NoEMMC was not working for me but CM10.2 noEMMC works fine. I get the error that many others get: unable to mount /boot, /data, /system.
I used adb shell to connect to the twrp 2.8.0.0 that runs when you boot the CM11 noEMMC SD boot/install image and compared the Linux system differences between that and the system you can see connected to the cwm 6.0.4.? That runs when you boot the CM10.2 noEMMC SD boot/instal image.
First things first: cm10 noEMMC remaps the internal emmc as /dev/block/emcblk1 and the external microsd card slot as blk0 (this is swapped from the norm and correct for a situation where you want to install to the SD as though it were the internal device).
CM11 noEMMC does not do this. I think that the author assumed that if your emmc is bricked then the system won't see your /dev/block/emmcblk0 at all so your external sdcard will take over that number. Clearly that's true for some, but it's not true for me.
I also began poking around the post boot script (in /sbin) to see how the cm11 noEMMC prepares the partitions on the Sd card and to see what Command it uses to create the data partition
Here's the kicker. I was able to mount my emmc rom partition and copy off all that data with an adb pull. I was able to initialize the cache partition (9) as a blank ext4 partition. I was even able to initialize the user partition (10) as ext4... Though I'm not sure that's right. I began mounting partitions and got greedy and tried to mount the whole partition map and it failed.
So, there's something wrong with (at least) one of my partitions. When recovery tries to mount the partitions, mount hangs and recovery fails to fully load. The noEMMC sd card got me around this because it doesn't try to mount any of the emmc partitions let alone all of them.
So, does anyone know if I can make new file systems on every partition and if by luck I'm able to get a twrp or cwm to fully load, will flashing a stock recovery put data on all those partitions?
Thanks
Click to expand...
Click to collapse
Could you please teach me how to mount EMMC partitions and retrieve data specially /factory partition with ADB?
I can only boot my Nook HD+ with with bootable SD card with TWRP or CWM.
Thanks.