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.
Related
Here's my issue: I wanted to start with a fresh "slate" for flashing a custom ROM (I originally had TRIGGER+OVERSTOCK). I backed up my apps/settings and the current ROM, disabled the Voodoo lagfix and unrooted the phone. Then, I ODIN'd back to JFD. At this point I downloaded TitaniumBackup and ROM Manager. When I tried to mount the Internal SD card, nothing happened...just the external card mounted. I went back and checked my ODIN settings an noticed that I had left the "Re-Partition" box checked. Freaking out at this point, I then went ahead and rooted the phone, and checked the file system through the Super Manager app. All my data was still there!!! So I went ahead and used ADB to "pull" the TB and ROM Manager data onto my computer just in case. My question is: how do I get the internal SD card to mount correctly?? Any help would be HUGE!!! Thanks in advance for everything!
Oryon007
I can't really tell by your post, are you trying to mount your external sd onto your phone or onto your computer?
I have Odin'ed to JFD with repartition checked many times, and have never had your problem. If I were you, I would just go through and Odin again using a different JFD image (maybe you just had a bad flash, what version of Odin were you using?) As long as whatever you are flashing with Odin contains all the essential bits, repartitioning should not do anything too deadly to your phone. (I learned this the hard way, do not try to Odin and repartition with JI6, for example, because JI6 has no dbdata image included).
If you just want to troubleshoot your current install, check the "/etc/vold.fstab" and "/etc/vold.conf". I can't actually tell you what those two files should look like as I am currently running a 2.2.1 rom (I think the files should differ between versions of the OS, but I'm not sure).
I am a pretty big Linux and Android noob, but I'm pretty sure that those two files are responsible for mounting both sdcards onto your phone, at least partially. (I would have no idea where to look to fix it if it isn't mounting onto your computer.)
Sorry if any of my advice is off, like I mentioned a little earlier, I am a pretty big noob, albeit very interested in Android.
Sorry for the confusion....I'm attempting to mount my internal SD to my computer. As far as ODIN is concerned, I'm using 1.7 with the flash files from this post:
http://forum.xda-developers.com/showthread.php?t=734475&highlight=stock+odin
I've used this ODIN flash before without any issues, so I'm still a bit stumped on why I can't mount my SD card. I can see the entire file system from within my phone as well as through ADB, but (for whatever reason) cannot mount it to my PC. I am leaning towards the issue of the SD card being partitioned wrong. Any thoughts? Any ideas on how to repartition the internal SD back to "stock"? Thanks again for any help provided!
-Oryon007
That's actually the same JFD image I use. I would just use Odin to flash JFD again with the repartition checkbox checked. I'm pretty sure that that will solve your problem.
Make sure you use the pit file too, without that you will have serious issues if you are repartitioning.
I'll try this again, just in case I missed something the first time...wish me luck!! I'll let you know how this turned out, too!
-Oryon007
Alright, good luck. Did you use the pit file when you originally flashed JFD and repartitioned? Not using that file may have been why you had this problem.
Ok...so, no change with the internal SD. When I attempt to mount the SD cards to my PC, the only one that shows up is the external one. After unmounting them, I can still see both cards with filesystems. Could the internal SD have been partitioned incorrectly? If so, how do I get it repartitioned right?
EDIT: I did use both original files from here...
Okay, I'm sorry but I have no clue how to help you. Are you sure its not just your computer? You may have to try and get help from somebody more knowledgeable than me. Have you tried flashing any other rom through Odin over JFD?
Not yet...I wanted to make sure that it wasn't something that I was doing incorrectly through ODIN. Again, my ultimate goal in all this was to have a "clean slate" to install a custom ROM on; the catch I'm running into is that I can't mount the internal SD card to place the files on to flash through CWM, even though I can see all the files through the phone and through ADB. *sigh* Thanks for your help though! It's always nice to have help when you run into these issues...
EDIT: After trying to ODIN JI2 files, I get the following error upon boot of the phone in Recovery:
E:Can't mount /dev/block/stl10
(Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
copy default media content failed.
Click to expand...
Click to collapse
Look at what I said at the end of the second paragraph, on the second post in the parentheses.
EDIT: Just flash a rom using Odin that does have a dbdata file. You probably checked repartition while flashing JI2.
Last night I was having a similar problem. While I wasnt flashing back to stock or anything, I could only get G: (external sd) to mount to my pc but not the F: (internal storage). Eventually I disabled USB Debugging, plugged in the USB cable from the pc, and it gives you 3 options for USB Mode: Kies, Media Player, Mass Storage. Once I selected mass storage, both internal and external sd cards mounted to the PC with no problem. Just remember to re-enable USB Debugging after.
Finally got it!!
Finally found the issue!! Only took me a week....lol
Going to manage my disk drives found that my PC wanted to assign a drive letter that was already assigned to a mapped network drive. *duh* Obviously not going to work. Reassigned the drive letter and voila!! I can mount my internal SD card!! w00t!!
That's really terrible and hilarious at the same time. Why wouldn't windows just pick another letter to map it to?
Hi everyone,
In my overzealous attempts to reformat an old 4gb external SD card through CW Recovery, I managed to reformat my internal SD card (I was using the Clockwork Recovery version 2.5). I thought that "format sd card" would reformat my external memory card and not leave me without a usable phone, but I guess I misunderstood.
I spent at least five hours going through all of the ODIN tutorials and trying them out, and found that using Eugene's 2.2 with 2E recovery ROM actually allows me to boot up (hooray! ), while the stock rom from this thread simply forces a bootloop on my poor phone, with occasional freezes. Even using AIO's "Flash to Stock" from Eugene's 2.2 doesn't work.
Further searching has lead to the thread about partitioning using parted, which has been hard for me to use effectively (I made a new partition, but I couldn't get it to mount properly).
I was really excited to come across this tutorial, but it didn't solve my problem. After getting through all of the steps, at step 5, ODIN3 versions 1.0, 1.7, and 1.81 (I tried all 3 on 3 different walk-throughs of the tutorial) never were actually capable of repartitioning the sdcard properly. Every time after the first time of using "parted" to reduce the card to a single partition, I found that that lone partition was always the only one there (15.5 gb /SYSTEM Fat32). No changes had been made to the sd card's partitions.
I don't know if it helps any, but the ROM I was running before I reformatted the card was Bi-Winning 3.0, and Voodoo had not been disabled at the time of the reformat, which may be why I can't flash new ROMs through the recovery as well.
As near as I can tell, ODIN can't actually return my vibrant's partitions to factory settings, so is there a way for me to do that manually? I think that would solve my problem.
Thanks,
-NewbieCube
My guide (you linked to) clearly states its not for this intent... if you read it, you would also see I linked to Eugenes froyo that does not brick. If you did it, THEN you did my guide ODIN to JFD, you are on a fully functional stock 2.1 JFD build.
If your intent was to just format the external sd, go to menu settings, sd card/phone storage, unmount the external and format it.
Right, I know that. In fact I read all through your thread and tried to flash to Eugene's first, and then to JFD, but JFD does not boot properly. It just gives me a black, unresponsive screen. I'll definitely go back through once more and try that again, though, as you clearly know what you're talking about.
I basically formatted the wrong storage (internal sd vs external sd), and would like to get that internal back to stock, so you are right that Eugenes -> JFD should work. I'll report back with results.
^ yeah, exactly... that should work with no issues. let me know if it does not.
Oddly enough, that didn't work for me either. Since my phone still can boot into Eugene's (albeit with 0.00B available to apps), I know this should work, just from reading through your guide. So once more, here's what I did:
1. Download mode -> ODIN 1.70: Flash Eugene_2E_JK2_Froyo.tar.md5, and s1_odin_20100512.pit (from Eugene) Re-Partition NOT checked (Eugene's thread says not to)
2. Boot up into Unbrickable Froyo, with no application space remaining Mount sdcard and move Update.zip (s15274n's) into the root folder without issue.
3. Download mode -> ODIN 1.70: Flash s1_odin_20100512.pit, and T959UVJFD.tar (s15274n's) with Re-Partition checked
4. Boots once automatically into recovery, saying something about a failed MBR checksum and failure to clear userdata
5. Bootloops that never get past the VIBRANT logo screen
6. Boot into recovery and try deleting user data and cache data manually and to reinstall packages, but bootloops continue.
I really don't know what I'm doing wrong here...
UPDATE:
I even used Heimdall on another computer and got the same result, so it isn't ODIN. Why is reformatting the internal SD card to stock so difficult to do?
delete my post
I FIGURED IT OUT!!! ...by random chance
For my problem, it was indeed the voodoo lagfix that was messing things up, and this post:
http://forum.xda-developers.com/showthread.php?t=888084
helped me out tremendously.
my tablet just turned itself of and when I wanted to turn it back on, it was stuck in a bootloop. I automatically enter CWM. adb parted says that the partition table is damaged. What am I supposed to do (already tried ot restore B&N firmware)
Did this occur after an attempt to repartition? Do you have CWM installed internally or on an SD? If this was after an attempt to repartition using the B&N method, did you still have CM7 installed when you tried? If you had CM7 installed there may be conflicting remnants of it... As noted, the B&N method flashes the stock ROM to your device.
I had problems during my experimentation with the B&N repartition image; The image that meghd00t worked out enabled me to reinstall the system. You could try that image, I've got it hosted for the time being.
Worst case you should be able to recover with AdamOutler's Ubuntu recovery.
Any updates?
it occured after repatitioning and making the internal SD card visible throught the build.prop edit on CM 7.2. I did the manual work with the repartitioning over parted, I wanted to have more internal sd storage then the standart .img file gives you which succeded at first. I was already searching for an answer to my problem, which apparentely more people have and I got this http://forum.xda-developers.com/showthread.php?t=1513583 the fix error method didn't work because fixed the 2 problems before that partition table defect occured. lavero.burgos that she found a method to fix that problem though, Ihope she'lll upload the steps tomorrow.....
Ok. I'm glad you're getting it sorted out. I was a little worried that it happened from trying the SD method. If you should need the file I PM'd you about I'll leave it up for a few days for you to download.
Not sure what kind of disaster I got my self into, but I mistakenly formated the EmmC. (****...) There goes 900+ photos, all my music, and other downloads.
But I can't install a new ROM, because it will no longer mount USB storage. Did I fry something here?
The error
"E:Unable to open ums lunfile (No such fi..."
(It goes beyond my screen and doesn't wrap so I cannot read the rest.)
What? What gives? I need to get the new rom file on their so I can start over like I was originally trying to.
I'm sorry if this is some "super" simple error I am missing. I did google some, but people said just flash a new recovery. Well...I tried ODIN with a another kernel, the first one I ever used. To no avail. I know how to flash with adb on HTC phones, but I can't figure it out with the Galaxy.
[Update] I figure out I can use an external SD card to move a rom over...but the EmmC is still unreadable. Did I blow it up? :/
[Update 2] I was able to recover, MOST, of my photos. It seems my phone decided to just start storing them all on the external card. Woot.
[Bad Update]
Can no longer mount the external SD to attempt to try another rom/kernel. Dammit
[Good update]
Was able to get the emmc to mount again! Yay! I am worried though...is there any chance of damage?
Formatting your internal storage is fine it does nothing at all to the system. Unless you're wiping with stock ics kernel installed. Which everyone who reads and searches before they flash knows not to do. So you should be good to go.
Sent from my SGH-I777 using Tapatalk 2
Good advice given to ya here bud. Glad you got things figured out (at least for the most part!)
Clay
Team Pirate
Sent from my PINK SGH-I777
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