Manually Wiping Data Partition - Vibrant Q&A, Help & Troubleshooting

My phone did the whole failed encryption bull shhhh. Figured that the issue is either located in the Vibrants DATA Partition or the SDCARD Partition (internal memory). I have attempted to ODIN back to stock but when it goes through the wipe data factory reset stage at the very end, the Data Partition fails.
I'd like to know of a way to manually get into the phone and format this partition clean. Then maybe odin will work.
Can it be done with ADB?
I got an old REcovery put back on trying things out from step one when I first got the phone a year ago.
Boot and Data partitions wont format. Boot just fails and I doubt thats where the issue is. But Data gives me this error:
Formatting DATA:...
E:Can't mount /dev/block/mmcblk0p2
(File exists)
Error mounting /data/!
Skipping format...
Done.
So anyone got any pearls of wisdom here? Or is this thing truly bricked?

nFiniti said:
My phone did the whole failed encryption bull shhhh. Figured that the issue is either located in the Vibrants DATA Partition or the SDCARD Partition (internal memory). I have attempted to ODIN back to stock but when it goes through the wipe data factory reset stage at the very end, the Data Partition fails.
I'd like to know of a way to manually get into the phone and format this partition clean. Then maybe odin will work.
Can it be done with ADB?
I got an old REcovery put back on trying things out from step one when I first got the phone a year ago.
Boot and Data partitions wont format. Boot just fails and I doubt thats where the issue is. But Data gives me this error:
Formatting DATA:...
E:Can't mount /dev/block/mmcblk0p2
(File exists)
Error mounting /data/!
Skipping format...
Done.
So anyone got any pearls of wisdom here? Or is this thing truly bricked?
Click to expand...
Click to collapse
Read this, http://forum.xda-developers.com/showthread.php?t=1580902 . There is no known fix just a work around, good luck. That bug made me go back to GB ROMS, it's ICS related unfortunately.
Sent from my T959 using XDA Premium App

iTz KeeFy is correct. There is no "fix" for the ICS bug. Only a work around that requires the use of your external sdcard.
Odin >> Heimdall >> JTAG will not fix it.

Related

Bell Galaxy S dead (unable to mount /sdcard) -> LAGFIX Problem?

Hi Guys.
I have a Galaxy S on bell's network, running JPK.
I looked at my phone last night and there was an orange "!" caution icon in the notification area. Said something about the internal sdcard not unmounting properly. So I rebooted the phone and now its booting to a black screen.
I have Ryan's OCLF from the market installed. I'm not sure if this is what is causing the problem (may be confused about ext2?)
I can boot into recovery, but no access to su from there. I can get into download mode. I tried re-flashing JPK, which flashed ok but I still have the same problem.
The error I'm seeing in recovery is:
E:Can't mount /dev/block/mmcblk0p1 (No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:
I tried flash sdcard from recovery but didnt work.
Can anyone help me get my phone back? I heard flashing stock 2.1 Bell firmware may fix my issue, but I don't have that firmware. Please help!
This should help.
http://forum.xda-developers.com/showthread.php?t=739091
this will work for you
this is the erro that comes up
E: Can't mount /dev/block/mmcblk0p2
(File exists)
Error mounting /data/!
Skipping format...
Copying files...
E: Can't mount /dev/block/mmcblk0p2
(File exists)
E: Can't mount DATA:
E: Failure at line 372:
copy_dir PACKAGE:data DATA:
Installation aborted.
this is the way you fix the problem.
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Download the 'True stock 2.1 firmware for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine
You might be better off sticking to the i9000 forums in the future, given that your Bell Vibrant resembles our T-Mobile Vibrant in name only. It's far more similar to the international i9000.
alcangel64, will this work with the GT-i9000? I also see the caution about don't do it if you've flashed JP3.. should I ignore that warning?
alcangel64 said:
this will work for you
this is the erro that comes up
E: Can't mount /dev/block/mmcblk0p2
(File exists)
Error mounting /data/!
Skipping format...
Copying files...
E: Can't mount /dev/block/mmcblk0p2
(File exists)
E: Can't mount DATA:
E: Failure at line 372:
copy_dir PACKAGE:data DATA:
Installation aborted.
this is the way you fix the problem.
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Download the 'True stock 2.1 firmware for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine
Click to expand...
Click to collapse
while in recovery mode, if you have adb installed u can adb reboot download and it'll take u to download mode. Then you'll be able to restore through odin. But I warn u, if it has something to do with the filesystem (ext2, ext4) ur in for a long ride. Other day I spent all day trying to get my phone to boot after flashing like 20+ times in odin due to an error in my filesystem
I think the title is bit misleading. It was likely not JPK that broke but rather the EXT2 loopback created by the lag fix. You might consider changing the title of the thread to something else.
If you get it working again, I wouldn't suggest applying the OCLF again. When the internal SD mounted improperly, it was likely corrupted. This can happen at anytime since the EXT2 is not journaled like Samsung's RFS or EXT4. You might be able to fix the file system corruption if you can run fsck on it through ADB.
Selecting the repartition option in ODIN may get you past any file corruption issues with the SD but it will wipe your internal SD. So, just restore from backup.
I agree. I think it was the lagfix, ultimately. I think the problem now is that I can't reflash because none of these PDA firmwares know anything about ext2.
Are there any releases with ext2 enabled right in the firmware? That might let me re-mount /sdcard at least, or at least remove the symbolic links?
epakrat75 said:
I think the title is bit misleading. It was likely not JPK that broke but rather the EXT2 loopback created by the lag fix. You might consider changing the title of the thread to something else.
If you get it working again, I wouldn't suggest applying the OCLF again. When the internal SD mounted improperly, it was likely corrupted. This can happen at anytime since the EXT2 is not journaled like Samsung's RFS or EXT4. You might be able to fix the file system corruption if you can run fsck on it through ADB.
Selecting the repartition option in ODIN may get you past any file corruption issues with the SD but it will wipe your internal SD. So, just restore from backup.
Click to expand...
Click to collapse
What did you do to fix it? Problem is I can't su in recovery mode. If I could I could at least remove the ext2 symbolic links and continue.
jroid said:
while in recovery mode, if you have adb installed u can adb reboot download and it'll take u to download mode. Then you'll be able to restore through odin. But I warn u, if it has something to do with the filesystem (ext2, ext4) ur in for a long ride. Other day I spent all day trying to get my phone to boot after flashing like 20+ times in odin due to an error in my filesystem
Click to expand...
Click to collapse
moophone said:
Are there any releases with ext2 enabled right in the firmware? That might let me re-mount /sdcard at least, or at least remove the symbolic links?
Click to expand...
Click to collapse
The stock 2.1 / 2.2 kernel should already support EXT2 however it won't mount a corrupted / damaged partition. You should try flashing back to 2.1 with the repartition option checked through ODIN. Once the internal SD is formatted by the repartition, it should then finally mount. It will also return everything back to RFS.
What kernel exactly? I tried flashing i9000_Kernel.tar, and then I9000XXJPH_KERNEL.tar from JPH. I tried JPC. I don't have a stock Bell kernel but none of those did anything.
Could you refer me to a specific kernel that will restore the /sdcard partition?
Thanks,
Greg
epakrat75 said:
The stock 2.1 / 2.2 kernel should already support EXT2 however it won't mount a corrupted / damaged partition. You should try flashing back to 2.1 with the repartition option checked through ODIN. Once the internal SD is formatted by the repartition, it should then finally mount. It will also return everything back to RFS.
Click to expand...
Click to collapse
moophone said:
What kernel exactly? I tried flashing i9000_Kernel.tar, and then I9000XXJPH_KERNEL.tar from JPH. I tried JPC. I don't have a stock Bell kernel but none of those did anything.
Could you refer me to a specific kernel that will restore the /sdcard partition?
Thanks,
Greg
Click to expand...
Click to collapse
After about 30 tries I was able to boot my phone with UGJH2. The funy part is for it to work and boot OK .. I have to leave my external SD card in it. It will error saying that it can't mount it once booted and both my internal 16G sd or my external 8G sd can't be mounted. All the rest of the phone works perfectly. If there was just a way for format or repartition the internal SD card from in the OS or ADB it would be fine. At least my phone now works until I can get a replacement phone from bell.
I tried to remove the external SDcard and the phone crashed. If I leave it in there , it works fine ??
Having this problem after flashing jp6 on my Bell i9000m. It worked great for like 2 days but suddenly it stopped working and i can't boot anymore. I did apply a lagfix but i removed it soon after because i did not see any speed improvements. Downloading the roms suggested in this thread right now... hope it works
Flashing again doesn't help*
I've flashed back to stock rom and used wipe factory and cache, but it still doesn't fix the issue.
I've read something about using adb to fix it, however adb doesn't even reconize my damn phone. Odin does on the other hand.
If adb reconize your phone, you should be able to push some files,and follow some other procedures to fix the internal sd card then flash it again with odin.
The other solution is changing your internal sd card, don't know how though people have sent back their device to their carrier or went to phone shop, i heard it costs one guy around 80$ to change it.

[Q] Unable to mount preinstall, Is this normal?

So during my battles trying to get JB on my atrix I performed a fastboot wipe on just about everything, including preinstall. Now anytime I flash something I get the error "unable to mount preinstall" is this bad or normal? I just searched quite a bit and found no one mentioning it.
Where are you getting this message? In the recovery?
If you wiped everything, that's perfectly normal. You can't mount a non-existent filesystem. You'll need to create a filesystem first before you (or a script) can mount it.

Unable to Mount Internal Storage

Hello all,
I have run in to some issues with my phone today, and have spent several hours trying out different things, and reading through the forums.
My phone is unlocked, s-on, and have had no problem loading multiple different ROMs in the past. The most recent ROM I was using was Carbon 1.7. It had been working well for the most part, periodically the phone would restart itself, but I didn't really consider that an issue.
Today though, I was taking a photo with the phone, and it restarted itself. Upon the restart, it became stuck at the HTC boot logo. Once I got home I investigated it some more, and figured I'd try and just wipe the cache/dalvik, and this is where I came to realize I might be in a big mess than originally thought.
I'm not able to wipe the cache, dalvik, system, or anything. I try to flash a ROM, and it seems to work, and since i'm S-On, I try to load the boot image with Hasoon's All in One Kit, but still stuck at the boot logo. I try to do a full wipe from within the ROM when install, and also tried a full wipe with Super Wipe, but no luck.
This is what I'm seeing (I've tried using TWRP, CWM, EXT, and all come up with something similar):
E: Unable to mount '/cache'
E: Unable to mount '/data'
E: Unable to mount '/system'
E: Unable to mount '/devlog'
E: Unable to mount '/emmc'
E: Unable to mount '/emmc'
E: Unable to mount internal storage
I've racked my brain as much as I possibly can. I consider myself a noob when it comes to most of this stuff still, so any help would be greatly appreciated.
Thanks so much
I recently sold my amaze to a coworker and over the weekend if started doing the same thing i spent all night trying to figure it out... I did a full wipe except sd and it wouldn't recognize the sd card. It was running cm10.1
Sent from my SGH-M919 using Tapatalk 4 Beta
S-Off your amaze. Then apply a stock RUU. I had to downgrade to GB to recover my phone. Android 4.1.x and 4.2.x roms tend to have this bug of partition corruption with our phones.
Fix internal storage error
If you wipe or factory reset it from the bootloader, it may kill the internal storage partition. Just connect USB, go into recovery, unmount and remount USB storage, it will recognize the internal storage and say its unformatted. Then format it as fat32. Then you can do a wipe and reimage. Thanks to OM4 from XDA for posting this. Worked for me!!
http://forum.xda-developers.com/show....php?t=1975989
heyliddle said:
Hello all,
I have run in to some issues with my phone today, and have spent several hours trying out different things, and reading through the forums.
My phone is unlocked, s-on, and have had no problem loading multiple different ROMs in the past. The most recent ROM I was using was Carbon 1.7. It had been working well for the most part, periodically the phone would restart itself, but I didn't really consider that an issue.
Today though, I was taking a photo with the phone, and it restarted itself. Upon the restart, it became stuck at the HTC boot logo. Once I got home I investigated it some more, and figured I'd try and just wipe the cache/dalvik, and this is where I came to realize I might be in a big mess than originally thought.
I'm not able to wipe the cache, dalvik, system, or anything. I try to flash a ROM, and it seems to work, and since i'm S-On, I try to load the boot image with Hasoon's All in One Kit, but still stuck at the boot logo. I try to do a full wipe from within the ROM when install, and also tried a full wipe with Super Wipe, but no luck.
This is what I'm seeing (I've tried using TWRP, CWM, EXT, and all come up with something similar):
E: Unable to mount '/cache'
E: Unable to mount '/data'
E: Unable to mount '/system'
E: Unable to mount '/devlog'
E: Unable to mount '/emmc'
E: Unable to mount '/emmc'
E: Unable to mount internal storage
I've racked my brain as much as I possibly can. I consider myself a noob when it comes to most of this stuff still, so any help would be greatly appreciated.
Thanks so much
Click to expand...
Click to collapse

[Q] error when trying to format

total noob here...
managed to get CM 10 up and running...
been working great..
then i let me friend touch it...
he seen something that said update and he ran it putting me at RC4 ( or some such thing )
anyway..
it went bad...he must have shut it off or something because now i cant do anything.
i have tried wiping cache / dalvik cache
tried booting into recovery and reinstalling the rom.
im pretty sure this was not a good plan. as now i get the cyanoboot logo ( the spinning one as it boots )
spins around maybe once...crashes and powers down the unit.
when trying to format i did get a error.
screen looks like this..
--wiping data ..
formatting /data...
formatting /cache...
formatting /sd-ext...
e:format_volume: make_extf4fs failed on /dev/block/mmcblk1p2
error mounting /sdcard/,android_secure
skipping format
data wipe complete
i dont want to loose the data on the sd card that was on it...do i have to put it in there for a wipe to actualy work?
internal install btw..i do not run the os off the sd...if that matters..
bigbudz said:
total noob here...
managed to get CM 10 up and running...
been working great..
then i let me friend touch it...
he seen something that said update and he ran it putting me at RC4 ( or some such thing )
anyway..
it went bad...he must have shut it off or something because now i cant do anything.
i have tried wiping cache / dalvik cache
tried booting into recovery and reinstalling the rom.
im pretty sure this was not a good plan. as now i get the cyanoboot logo ( the spinning one as it boots )
spins around maybe once...crashes and powers down the unit.
when trying to format i did get a error.
screen looks like this..
--wiping data ..
formatting /data...
formatting /cache...
formatting /sd-ext...
e:format_volume: make_extf4fs failed on /dev/block/mmcblk1p2
error mounting /sdcard/,android_secure
skipping format
data wipe complete
i dont want to loose the data on the sd card that was on it...do i have to put it in there for a wipe to actualy work?
internal install btw..i do not run the os off the sd...if that matters..
Click to expand...
Click to collapse
ok so forget this..
gave up..
reset nook back to b&n stock..
and now i have no touchscreen...
trying to create a bootable sd card with cm10 on it now so i can run the touchscreen flash thingy...
resetting it back to 2 touch..
so i can then re install cm 10 internal...
anyway to flash the touchscreen firmware without making this card?
bigbudz said:
ok so forget this..
gave up..
reset nook back to b&n stock..
and now i have no touchscreen...
trying to create a bootable sd card with cm10 on it now so i can run the touchscreen flash thingy...
resetting it back to 2 touch..
so i can then re install cm 10 internal...
anyway to flash the touchscreen firmware without making this card?
Click to expand...
Click to collapse
No. But you can get a pre-made CM10.1 SD image from http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/.

Help! I tried to encrypt phone but get "Encryption Failed" no matter what I do.

Help! I tried to encrypt phone but get "Encryption Failed" no matter what I do.
I have TWRP recovery.
This happened after a power outage.
I have LInk2sd with apps linked to /data/sdext2
1. I've formatted /data, using both regular and the -rf option
2a. I've repaired data without 2nd sdcard in phone successfully
2b. When I try to repair with the 2nd sdcard inserted, I get the following:
E:/sbin/e2fsck -fp /dev/block/mmcblk0p25 process ended with ERROR=1
E:Unable to repair '/data'
E:Error repairing file system
3. I've reformatted data a couple of times using EXT4
4. I've restored from backup
5. I've booted with 2nd sdcard in and without
I still get Encryption Failed and its suggestion to reset to factory does not work.
Any ideas as to how I can fix this? I'm going to stick my head in the sand in the meantime....
I'm going to answer my own question - seems you run into problems when encrypting a rooted phone. I unrooted and was able to encrypt thereafter. On first try however, it doesn't seem to accept my encryption password when I boot... strange. I redid it and then it was encrypted.
For giggles I thought I would test decrypting but it fails and hangs on the open chest Android picture. This is my next problem.

Categories

Resources