Alright...
So I tried to install voodoo on my phone which was running stock 2.1 Eclair, and somehow it amazingly ****ed everything up. I know it was likely more or less my error than not.
So I was researching how to correct my ****-up which seemed to be that my phone was soft bricked and stuck on the vibrant insignia on boot up. So I read further and decided best thing to do would be use odin to flash Eugenes 2.2 froyo
GREAT! Everything was working the 2.2 rom is on my phone, all lights are Green! BUT I tried to download something from Marketplace and now my phone is telling me there is no space left of Application Storage. So i thought that it might be weird and decided to go ahead and check it out in my SD Card and Phone Storage settings and sure enough, I have one Gig on my External SD available. 11 Gigs on my Internal SD available but NOTHING available in the way of Application storage space...which is a huge bummer...
Sadface - facepalm FAIL -
So then I read that sometimes when installing a lagfix they take up a significant amount of phone space to create databases. So I'm wondering if somewhere on my phone Voodoo is chillin' eating up all my application space...
Or what I should do now to correct the situation.
Any help would be greatly appreciated.
Cheers!
you flashed eugenes froyo right? havw you tried odin back to stock?
Sent from my SGH-T959 using XDA App
Yes, actually what I did, was flashed over to stock, original pit and tar files, and then when the phone booted it gave me an error, but that was expected saying it couldnt mount my SD card. I entered odin again and re-flashed back to eugene's 2.2 froyo and the appropriate pit file and BOOM. With Repartition checked it flashed back to eugene 2.2 with the filesystem cleared from my horrid attempt at voodoo and everything is perfect now. : -) All my application storage space is back!
that's nice.
Sent from my SGH-T959 using XDA App
Related
i'm on axura 2.1 and went to flash a new rom through clockwork and it says E:Can't open /sdcard/*********.zip (bad)
so i redownloaded the rom, put it on my sdcard, tried again, same thing. i then downloaded a different rom, put it on the sdcard, tried to flash, same thing. any ideas? is it odin time?
Did you save it on the internal card or the removable card? It needs to be on the internal to flash through CW.
it's in the right place. in fact, the axura21ve.zip is still on there and will flash fine, but no new zips will flash, so i'm thinking the fs got corrupted...?
I've had this happen on Axura 2.1 also with the mounting_fix_vibrant SD fix.
I can't copy anything from my PC to my internal SD card since flashing Axura 2.1
i thought that sombionix' sd mount fix was included in this rom. apparently not. which is weird because this issue never affected me in linux with previous roms that didn't have the fix. oh well. flashed the fix and am booting a new rom.
I am also unable to flash a different rom over Axura. Can you help me? I want to go back to Bionix but can't!!!!!
I was on axura 2.1 and changed to 2 new roms.
I an on another rom now, just fine.
I have been getting the android logo with exclamation mark a lot more recently though.
I smell ODIN with repartition checked.
Sent from my SGH-T959 using XDA App
Ive also run into this troublesome problem, even Odin back to JFD stock will not help me get the new roms on, wiped internal sd, external sd, cleared cache and everything. Was able to flash back to JFD and then Fusion 1.2 . Havent tried the repartition setting in Odin but I may have to go that route.. any input from you guys would be great, has anyone fixed this problem yet?
[FIXED]
What I did was odin back to JFD and select the "Re-partition" option, didnt delete any of my data and seems to have corrected the problem installing other roms, try that out.
I wanted to clear out my SD card so I used the setting in clockworkmod to repartition the SD card, but that apparently wiped out the system partition and after doing that my phone would not boot up. It would just get stuck at the Vibrant screen. After MANY attempts with ODIN, I finally was able to use Odin3 V1.7 along with Eugene_2E_JK2_Froyo to get a ROM on it and get my phone to boot back up, however now I can't update any apps or download new apps. When I look at the settings, it shows available app space as 0. There is plenty of system space and plenty of space on the SD card.
When I used Odin, the V1.7 version automatically checked the option to re-partition, but that doesn't seem to have changed the partition size. How can I get my Vibrant back to good working order? I can't install ClockworkMod again to try and flash a different ROM. Is there any way to change the available application storage space?
I'm pretty desperate at this point.
Thanks,
pamulli said:
I wanted to clear out my SD card so I used the setting in clockworkmod to repartition the SD card, but that apparently wiped out the system partition and after doing that my phone would not boot up. It would just get stuck at the Vibrant screen. After MANY attempts with ODIN, I finally was able to use Odin3 V1.7 along with Eugene_2E_JK2_Froyo to get a ROM on it and get my phone to boot back up, however now I can't update any apps or download new apps. When I look at the settings, it shows available app space as 0. There is plenty of system space and plenty of space on the SD card.
When I used Odin, the V1.7 version automatically checked the option to re-partition, but that doesn't seem to have changed the partition size. How can I get my Vibrant back to good working order? I can't install ClockworkMod again to try and flash a different ROM. Is there any way to change the available application storage space?
I'm pretty desperate at this point.
Thanks,
Click to expand...
Click to collapse
Can you Go into recovery & then into mount options & format data... worse case is to odin to stock then flash this over...
use the toolbox
http://forum.xda-developers.com/showthread.php?t=954509
No luck. If I use the toolbox and flash to stock Rom the phone doesn't fully boot. I get an error immediately after it reboots that says checksum error and then failed to wipe. I then see the Vibrant screen and the T-Mobile boot animation but then the phone goes completely black and does nothing. It seems that none of these processes are correcting the partition size problem that was created when I did the partition command in ClockworkMod. I'm just guessing, but if all of these are doing a format and not actually resizing the reserved application space partition then I'm never going to get a ROM to work.
I'm thinking that I may have to see if I can get it replaced under warranty since in it's current state T-Mobile shouldn't be able to tell that it was rooted. I hate to have to go through all of that though.
pamulli said:
No luck. If I use the toolbox and flash to stock Rom the phone doesn't fully boot. I get an error immediately after it reboots that says checksum error and then failed to wipe. I then see the Vibrant screen and the T-Mobile boot animation but then the phone goes completely black and does nothing. It seems that none of these processes are correcting the partition size problem that was created when I did the partition command in ClockworkMod. I'm just guessing, but if all of these are doing a format and not actually resizing the reserved application space partition then I'm never going to get a ROM to work.
I'm thinking that I may have to see if I can get it replaced under warranty since in it's current state T-Mobile shouldn't be able to tell that it was rooted. I hate to have to go through all of that though.
Click to expand...
Click to collapse
Do you have repartition in Odin checked?
I found several other posts regarding this exact same issue and everyone concluded there is no fix and it has to be replaced. Luckily I'm still under warranty and T-Mobile is sending me out a new one. Oh well...
So finally got my vibrant back up and going after i tried repartitioning the sd card through clockwork. Now that i installed the stock 2.2 it will not allow me to download any apps through the market because it says that i am low on space..??
I checked and i have plenty of space so whats the problem.
Any help out there would help.. THNKS
same problem.. lmk how u solve it pls!!
Do not use clockwork for repartition, use ODIN instead with JFD firmware(2.1) and .pit file. Then reinstall clockwork and install a 2.2 ROM of your choice.
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.
To start I dont mean ROM as in a custom ROM. I mean ROM(Read Only Memory)
I started to have this problem a while back but it never was that important. But now that I am trying to copy everything over for back-up it is.
Whenever I USB mass storage my phone, it randomly disconnects from my PC. I have tried different cables, ports, and also tried to wiggle the cable to see if there is a short. I can not make it happen, it just randomly does it. I do not have a problem connecting my GS2 so its not the PC. Maybe a corrupted ROM? How should I go about fixing that?
So I'm wondering if anyone else has had this problem.
Specs
T-959 3G ver
Running Bionix 3.1(I think)
It is possible its a corrupt install.. But the great thing about the vibrant is your internal and external sd cards are unmodified when flahing/odining. I recommend a simple backup using titanium backup (if it doesn't error out, then the memory itself is fine), then reflash your rom. If that fails, Odin back to stock. You can find information on how to do this in the newbie guide here: http://forum.xda-developers.com/showthread.php?t=849028
Good luck!
Using XDA premium, you should be too!
johnny12times said:
It is possible its a corrupt install.. But the great thing about the vibrant is your internal and external sd cards are unmodified when flahing/odining. I recommend a simple backup using titanium backup (if it doesn't error out, then the memory itself is fine), then reflash your rom. If that fails, Odin back to stock. You can find information on how to do this in the newbie guide here: http://forum.xda-developers.com/showthread.php?t=849028
Good luck!
Using XDA premium, you should be too!
Click to expand...
Click to collapse
The crazy part is I have done all of this. I have wiped, re-flashed, and Odined back to stock, I still have this issue. I have been using Bionix 1.3 for almost a year and didnt run into this problem until months after originaly flashing it.
Update: When I do get it connected to my PC, the PC detects a problem with the drive and wants to "Scan and Fix" it.
FYI: I'm not a noob to tech, I work in IT and am very exper in PC. Just letting that be known in hope for a more in-depth conversation.