Hey, I have a problem with my Vibrant:
First I had the "Low internal storage w/ CM10, Slimbean, Hellybean due to Partition Error" and did the fix shown on XDA. However when I boot my phone it automatically goes into Android system recovery and the following in yellow letters shows:
-- Movi_check Start..!!
checksum confirmation need_checksum[1301305579]
MBR_ChkSum in header : 4.1
MBR checksum: 00A35E062CE062CE4230BC72D52C175496072
MBR Checksum Error
Movinand Checksum Confirmation Fail
-- movi_checking done!...
# MANUAL MODE #
-- Applying Multi-CSC...
Installing Multi-CSC
Then when i try to do 'reinstall packages' to install CWM, this pops up in red font:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(Invalid argument)
E:Can't mount SDCARD:update.zip
Installation aborted.
What does kinda unbrick my phone is flashing Eugene_2E_JK2_Froyo (PDA), Vibrant_Froyo.tar (BOOTLOADER) and s1_odin_20100512 (PIT) and ticking re-partition on ODIN. This let's me go back to the stock rom, but a pop up shows that my 'Internal Memory is Damaged' and I cannot access or view the stats for my internal memory at all. And when I try to install Rom Manager I get 'Not enough space'.
I'm really stuck and would appreciate any help! Thanks!
Which "fix" did you use for low storage issue? Was it this thread http://forum.xda-developers.com/showthread.php?p=32346116
IIRC, the update.zip doesn't work in froyo. There is a work around but you need figure out the int SD card issue first.
Do you have any way of analyzing the internal SD card? Like storage analyser app or something like that?
I am Jack's inflamed sense of rejection.
i dont know this can works but you can try
here is the link
forum.xda-developers.com/showpost.php?p=26285877&postcount=12
Hi OP, I probably have very unfortunate news for you. What you are experiencing is exactly the same thing that happened to our old pal Dan_Brutal's first vibe.
He ended up sending it to me, and I could never fix it. The only thing that would boot it, was Eugene's JK2, and it had the exact same messages when attempting to flash in the stock recovery. I could never get the EU fix to work either, it seems to he a deeper problem than that.
I went as far as using the reparted method, since I could successfully connect to the phone via adb and adb shell, and rebuilt the partition table via shell, and still, nothing would work, internal sd was lost and all it would ever boot from was an Odin flash of JK2, and that sd error never went away.
After about six months of trying different fixes, we decided it was a lost cause, and a severely corrupted internal sd. That was in fact the phone that was parted out in an attempt to get Woody a USB port replacement.
I say try the EU fix/workaround, it's gonna be your best bet at getting a running phone again. I could never get it to take when I was in your shoes, but I wish you better luck than I had.
Sent from the ICZen Experience
Br1cK'd said:
Hi OP, I probably have very unfortunate news for you. What you are experiencing is exactly the same thing that happened to our old pal Dan_Brutal's first vibe.
He ended up sending it to me, and I could never fix it. The only thing that would boot it, was Eugene's JK2, and it had the exact same messages when attempting to flash in the stock recovery. I could never get the EU fix to work either, it seems to he a deeper problem than that.
I went as far as using the reparted method, since I could successfully connect to the phone via adb and adb shell, and rebuilt the partition table via shell, and still, nothing would work, internal sd was lost and all it would ever boot from was an Odin flash of JK2, and that sd error never went away.
After about six months of trying different fixes, we decided it was a lost cause, and a severely corrupted internal sd. That was in fact the phone that was parted out in an attempt to get Woody a USB port replacement.
I say try the EU fix/workaround, it's gonna be your best bet at getting a running phone again. I could never get it to take when I was in your shoes, but I wish you better luck than I had.
Sent from the ICZen Experience
Click to expand...
Click to collapse
Thanks! I decided to just give up and get a new one lol
Related
It all started out with a simple root, flashing of recovery, and a flash of Megatron to my friend's Optimus T. It was great, the rom was fast, snappy, and much smoother than before. No problems......until my friend switched SD cards.
I am aware that messes up the ext4 partition of apps on the phone. Well, my friend switched back to the regular SD card, and it still didn't work. Soon, he started to get weird issues, such as the the boot animation switching back to the stock Android one from the sketch animation in Megatron. I told him to wipe data and cache, and told me that it didn't work. So, I have his phone right now, including a bit of headache.
The problem: The SD card refuses to mount on his phone. His phone boots up and all, but force closes after finishing the Setup Wizard with the message "The application 'Setup Wizard' closed unexpectantly" or something like that. And there was a black screen after that with nothing able to be accessed. The status bar still displayed, with the notification "SD Card is removed" or something along those lines. I suspected at first a data/cache/dalvik wipe would fix it, but to no prevail. In the recovery (using RA-thunderg-1.1.0-GNM), whenever I try to flash a zip, the following error appears:
E:Can't mount /dev/blocl/mmcblk0 p1 (or /dev/block/mmcblk0)(No such file or directory)
E: Can't mount SDCARD:
Also, when partitioning the SD card, the recovery says that it has succeded, but in reality, it hasn't. Also, converting ext2 to ext3 does not work and displays:
Error : Run 'fs ext3' via adb!
and for ext3 to ext4:
Error : Run 'fs ext4' via adb!
To add, the USB-MS option doesn't work either, as the Removable Disk does not show up in Windows.
I've also tried using a blank SD card that was freshly formatted: didn't work.
So it all boils down to the SD card not mounting.
Any solutions? I'm kinda responsible for this as I told my friend to do this, but I never expected such a problem. I am an experienced Android user as I've flashed, rooted, adb, and etc on a Droid Eris, Droid, Droid X, Samsung Continuim, and currently the Samsung Fascinate. The hardest problem I've encountered is dealing with Samsung's RFS issue, but I've gotten over that now. This is beyond anything I've seen.
Hopefully the community around here can help me as I've been trying to solve this for a few days now. Thanks for enduring through such a long post!
(P.S. All SD card's used are the stock Samsung Class 2 2GB that comes with the phone.)
Change the sd or try fresh format and reflash.
As said before, even with different SD cards, the card will not mount, and therefore I'm unable to flash anything from the SD card.
Rockin' DJ05, Liberty Gingerbread, Clocked at 1.2ghz Voodoo
-----------------------------------
Yes, still on 2.1, waiting on some Gingerbread goodness, but might flash Vanilla Froyo.
-----------------------------------
DD username: TheSonicEmerald
only possible reason for what's,happening would be that you didnt follow the procedures correctly, I recomend u reflash stock rom and do all the procedures for flashing a custom rom correctly this time..
I flashed the rom correctly, and it worked perfectly until my friend switched SD cards, so I'm pretty sure I followed the procedures correctly.
Edit: Would you mind linking me to a stock reflash of the phone? Can't seem to find it....
Hello!
So, this is a problem I've had for a while, I just haven't had the chance to take care of it, but it appears that my vibrant is missing a large chunk of its internal storage. When I mount the phone's storage, I can only see and access two partitions; one is my sd card, and the other is a portion of my internal storage (2.19 gigs).
I feel like this might have occurred a while back after flashing one of the earlier 2.2 roms. I used to be able to see 3 partitions, the two formerly mentioned, and also a large (14gig was it?) partition as well.
I've done some searches already, but I haven't been able to get any definitive answers. Has anyone else experienced this and if so is there a fix for it?
Thanks in advanced! :]
Sounds like a mounting problem. There is a fix for this I think it was called sd mounting fix. Jelette, Whitehawxx, sombionix, one them If I remember correctly did the fix. Look in the general sticky or the development sticky
Should be seeing a 2 internal, 14 internal, and whatever you have in the external
Stock KA6 out of the box... weird intermittent mounting issue
So I got my new phone... back to hacking away at it...
it came as 2.2 KA6
1. Rooted it with SuperOneClick
2. Got the modded 3e recovery
3. When I go to install.. I get a E: Can't mount /dev/block/mmcblk0 (or /dev/block/mmblk0p1 (Device or resource busy)
E:Can't mount /sdcard
4. I reboot and everything is fine, all is mounting...
5. Can I not install any roms?
I had an old update.zip... downloaded a new one from clockwork mod... working great bionix 1.3
Alright so here's the backstory. I bought a Vibrant off of ebay that was stuck in a bootloop. I thought to myself, hey I could just shove this thing into download mode and be on my merry way!
Well, I attempted to flash JFD with a jig that I had. Went fine, Odin gave it a PASS.
Still boot looped.
So I then try Eugene's no brick, and after finally getting the right version, it booted up. Then tried to flash to JFD again.
No dice.
Following the directions here I was able to finally get 2.1 to boot, now here is the problem that I'm currently stuck on.
I can't get the internal sd (onboard flash) to mount in the system. If I am at the shell I can browse to /mnt/sdcard and see everything on the phone and on the sd (external_sd).
But when I go into the settings, all I see is space unavailable and the format is grayed out.
The culprit I believe lies in the partition on the internal memory that creates this MBR checksum error every recovery.
Thoughts? Opinions? I know this can be fixed, I've come this far!
Below I've attached some of the voodoo logs, it seems that when trying to make the ext4 partitions, it can't find it. (I was trying this so I could in the end disable it)
Does anyone know what might be going on? Any tips at all?
The only thing that I can figure now is that there might be damage or the internal storage. When looking in /dev/block, there is no reference to mmc anything, like the internal storage isn't even there. Is the flash chip soldered on the motherboard? I'm guessif that it is, which means it would be a difficult fix.
Only other "solution" that I could thing of is if I mod the fstab to mount a microsd as the internal storage. Would this mod be affected by a flashing rom or odining back to stock?
Also is this the right board for this? If not can anyone direct me to the best spot to ask this question?
Thanks a bunch!
Please find my guide on the developers thread and follow it,
You will be bak at no sweat.
Any problems post there.
Hi guys i have problem with a phone thats friends gives me to repair and this is the problem.
Phone was dead so i put in download mode and flashed with "T959UVJFD" , and the phone stucks on GALAXY S logo and then the 4 lights of the down of the phone on and the screen was black so i tried differents combinations of roms, pits files , etc.
The phone finaly booted propely when i flashed a kernel "Bali_1.8.8UV-zImage" with heimdall .
After the phone booted i was happy but i checked and internal 16gb was not recognized and also when i inserted sd card also no detected.
Finaly i was searching solution also when tried to flash with RIFF BOX BY jtag and still same , phone only boots when i flash with kernel "Bali_1.8.8UV-zImage" but still no internal or external storage .
Also in recovery mode messages like
"can't mount /dev/block/mmcblk0 (or /dev/block/mmcblk0p1)"
Anybody can help me?
I need to work one of them storages
Did you ever find a solution to this? I have an old Vibrant laying around that has this same problem....both the external and internal memories are unavailable no matter what I do.
rikimaer said:
... Also in recovery mode messages like
"can't mount /dev/block/mmcblk0 (or /dev/block/mmcblk0p1)"
Click to expand...
Click to collapse
a) When you see this message in recovery, what happens if you simply select "Reboot phone" and hit the Power button? Does it then boot up?
b) mmcblk0 = Internal sdcard. I hate to say it, but it sounds very likely your friend's phone could have been hit by the Encyption Unsuccessful bug (refer to Merio90's thread).
As a test, you could follow Merio90's OP steps and use the updated CWM recovery (via update.zip) to re-partition your external sdcard. Note: all data will get wiped (so backup first). When you "reinstall packages" in recovery, you may get that "can't mount ... emmcblk0" error again. Just "reinstall packages" again. Then see if you get int / ext sdcard detection at that point.
If still not detected, proceed to flash a CM7 v7.2.0-vibrantmtd rom. Flash it twice (1st flash updates recovery; 2nd flash converts to mtd partitioning and flashes rom). Merio90's thead is geared towards ending up at an ICS rom, but keep in mind essentially all of the Vibrant EU occurences have been on ICS rom's. This is why I suggest using that stable CM7 build as a test. For kicks, see if you get sdcard detection (probably not). If not, do the vold.fstab emmc/sdcard swap, which works the same and uses the same syntax on GB & ICS (ie. refer to Merio90's OP for vold.fstab syntax). Flash CM7, edit your vold.fstab, & reboot (for swap to take place).
If you're good to go ... you can always proceed onto a JB rom from there. Read through the last discussions re. JB rom flashing issues and kernel compabitibility - ie. to save you the trial & error.
If you still don't get sdcard detection at this point, maybe this is something different altogether. But, my hunch is that you'll get detection on CM7 (after the vold.fstab swap).
Edit: I think i fixed it by "cleaning" with diskpart and using an sd card to copy a rom and flash it, then booting up android and letting it format the internal storage. Will report back if any problems occur! Check post # 6 on this page for the solution. Also, sorry for the erratic writing, it's 4:55AM here and i need to be up at 9AM!
AtrICS rom did a random reboot and was saying something about encryption failed. Strange, i've never used that setting (i don't even have a screen lock). I rebooted the phone and it wouldn't get to the ROM, so i went into recovery and tried restoring a backup. After a few seconds it aborted. Strange. I mounted usb so i could copy a fresh rom.zip to flash, but after a few MB, it was throwing a "cannot read from source disk" error. Internal storage was corrupted.
I can read data from the partition, but after a while it'll lock up. I cannot write to it at all. I also get an error in CWM "unable to write to ums lunfile (no such file or directory)".
How can i fix this? I was thinking full sbf flash, but is that too risky? I'm in the UK (t-mobile), came with stock froyo, unlocked bootloader and flashed gingerbread onwards. Is it safe for me to flash back to froyo or something, or will my unlocked bootloader get me bricked? How can i fully clean this pesky corrupted partition any other way?
Thanks.
coolnow said:
AtrICS rom did a random reboot and was saying something about encryption failed. Strange, i've never used that setting (i don't even have a screen lock). I rebooted the phone and it wouldn't get to the ROM, so i went into recovery and tried restoring a backup. After a few seconds it aborted. Strange. I mounted usb so i could copy a fresh rom.zip to flash, but after a few MB, it was throwing a "cannot read from source disk" error. Internal storage was corrupted.
I can read data from the partition, but after a while it'll lock up. I cannot write to it at all. I also get an error in CWM "unable to write to ums lunfile (no such file or directory)".
How can i fix this? I was thinking full sbf flash, but is that too risky? I'm in the UK (t-mobile), came with stock froyo, unlocked bootloader and flashed gingerbread onwards. Is it safe for me to flash back to froyo or something, or will my unlocked bootloader get me bricked? How can i fully clean this pesky corrupted partition any other way?
Thanks.
Click to expand...
Click to collapse
Sound like the same issue myself and some others are having. I was using the atrics rom and icsrom as well before my phone went to heck. We cannot delete stuff from sd card or flash any other rom..
boonemeat said:
Sound like the same issue myself and some others are having. I was using the atrics rom and icsrom as well before my phone went to heck. We cannot delete stuff from sd card or flash any other rom..
Click to expand...
Click to collapse
Did you mess with the encryption settings? I know i didn't. Whatsapp was throwing errors so i rebooting the phone and now all this has happened. Can't even moto-fastboot flash system because it always gives an error :crying:
coolnow said:
Did you mess with the encryption settings? I know i didn't. Whatsapp was throwing errors so i rebooting the phone and now all this has happened. Can't even moto-fastboot flash system because it always gives an error :crying:
Click to expand...
Click to collapse
Sure did not mess with encryption. Rsd flashing did nothing, fastboot does nothing for me. Now the rom I'm stuck on is getting errors and fc's like crazy and the touch screen is beginning to fail.
boonemeat said:
Sure did not mess with encryption. Rsd flashing did nothing, fastboot does nothing for me. Now the rom I'm stuck on is getting errors and fc's like crazy and the touch screen is beginning to fail.
Click to expand...
Click to collapse
Damn. I would have thought RSD would be the last resort...
I think i've made some progress. I have to be up in 5 hours so i'll be making this short. You will need an SD card.
I was sick of the lockups created by the corrupted /emmc/ partition, so i rebooted my phone, went back into recovery (it would never mount any filesystem after mounting emmc once, so a reboot was needed every time) and mounted emmc. Showed up on my computer, and gave me a chance to copy my photos and all that. Thank you!
I started CMD as an admin and typed in
diskpart
Click to expand...
Click to collapse
When it loaded up, i typed
list disk
Click to expand...
Click to collapse
I saw a 10GB partition as disk 2 so i then
select disk 2
Click to expand...
Click to collapse
then i did
list partition
Click to expand...
Click to collapse
and saw only 1 partition, as partition 1, so
select partition 1
Click to expand...
Click to collapse
then
clean
Click to expand...
Click to collapse
Went into Disk Management and right clicked the black bar "unallocated space" and made a new simple volume, formatted as fat32 and that's that.
I then copied a rom onto my sd card and flashed via cwm. Everything seemed to go well, i could boot up (remember, because of the failed encryption, i was wiping my /system/, /data/ etc to try to get a fresh start so i had no rom to get on.
Will report back any problems. Just had one, i booted up fine but realised my usb cable was still plugged in so sd and internal storage were unmounted. Unplugged USB and phone froze (due to corrupted partition?). I recognise that freeze, i had it earlier on today (is that when the partition got corrupted?). It's rebooting right now, no usb cable plugged in. Wish me luck.
Android gave me a "your internal storage is corrupted" notification and offered to format. I allowed it and everything seems to be well! I will be filling it up right now before going to bed to see if it will lock up, but i think i fixed it!
Well congrats I'm glad you had such luck! It seems our problems are a bit different unfortunately because it goes a little deeper on my end. Thank you so much for the help.
Here is my struggle with the same problem. I have no solution, but maybe something here will help you?
http://forum.xda-developers.com/showthread.php?t=1967620