Database Develop

looking for A 2.2 froyo rom , odin flashable

Guys need some help here,
I have a vibrant and there has been times that I have flashed a 2.2 froyo rom to repair the data partition on my internal sd card from a bad flash when a lag fix is applied.
I talked a friend into getting a captivate because he loved my vibrant so much. I had him running a stock rom, with unhelpful lax fix kernel and everything ewas gravy for two days until today. he said he got a sd card error, and the phone wont boot past the galaxy s logo, I tried one click odin from this forum, now the phone wont boot past the att logo, because it fails to wipe the data partition.
Can we use the vibrant fix for the captivate? I could try to lash that froyo thru odin and see if it helps, the phone doesnt need to boot up, I just need to flash and wipe the internal sd tru odin. any suggestions
Thanks in advance

Devin5277 said:
Guys need some help here,
I have a vibrant and there has been times that I have flashed a 2.2 froyo rom to repair the data partition on my internal sd card from a bad flash when a lag fix is applied.
I talked a friend into getting a captivate because he loved my vibrant so much. I had him running a stock rom, with unhelpful lax fix kernel and everything ewas gravy for two days until today. he said he got a sd card error, and the phone wont boot past the galaxy s logo, I tried one click odin from this forum, now the phone wont boot past the att logo, because it fails to wipe the data partition.
Can we use the vibrant fix for the captivate? I could try to lash that froyo thru odin and see if it helps, the phone doesnt need to boot up, I just need to flash and wipe the internal sd tru odin. any suggestions
Thanks in advance
Click to expand...
Click to collapse
Have you tried flashing in the plain voodoo kernel (atinms thread is around here somewhere) to see if you can get the thing to boot at least?

I have already tried to odin to stock, which didnt work and I knew that. The problem is I cant disable the lag fix, because the phone wont boot all the way up.
What we did in the vibrant forums was to flash a 2.2 thru odin. ( it automatically wipes internal sd and formats it back to original state.) then flash stock reroot and we are all happy again.
Is there anything like this for the captivate?
Unless i am missing something, which I could very well be flashing a kernel wont help the data partition problem will it?

what if you took the stock firmware from samfirmware.com and did a normal odin flash with the repartition selected?
I'm a noob but that seemed like a logical thing to try.

Devin5277 said:
I have already tried to odin to stock, which didnt work and I knew that. The problem is I cant disable the lag fix, because the phone wont boot all the way up.
What we did in the vibrant forums was to flash a 2.2 thru odin. ( it automatically wipes internal sd and formats it back to original state.) then flash stock reroot and we are all happy again.
Is there anything like this for the captivate?
Unless i am missing something, which I could very well be flashing a kernel wont help the data partition problem will it?
Click to expand...
Click to collapse
That doesn't really answer my question... I asked if you had tried booting it again with a plain voodoo kernel. Obviously the full flash didn't work for some reason, and now your internal SD isn't being detected... which is strange. You could conceivably try flashing pretty much anything you've used on the vibrant though to see if that helps.

Did you do the Master Clear before flashing with Odin?

nooomoto said:
Did you do the Master Clear before flashing with Odin?
Click to expand...
Click to collapse
no, my phone wont boot up to do a master clear. After doing some research it seems that the internal sd card got currupted. when I tried to clear data it failed on me, and gave me a cant mount data error in stock recovery

Devin5277 said:
no, my phone wont boot up to do a master clear. After doing some research it seems that the internal sd card got currupted. when I tried to clear data it failed on me, and gave me a cant mount data error in stock recovery
Click to expand...
Click to collapse
you can master clear with the one click odin. Its the big button to the right of start that says master clear

xetrev said:
you can master clear with the one click odin. Its the big button to the right of start that says master clear
Click to expand...
Click to collapse
I tried 3 times, It just hangs. I think the internal sd got unmounted somehow.

xetrev said:
you can master clear with the one click odin. Its the big button to the right of start that says master clear
Click to expand...
Click to collapse
You have to have the phone booted and in USB Debug mode for the odin master clear to work, this person can't get the phone to boot. Is there another way to put the phone in USB Debug mode when it will not boot?

So repartition doesn't work?
Sent from my SAMSUNG-SGH-I897 using XDA App

I'm having the same issue
h t t p:/ /forum.xda-developers. com/showthread.php?p=8340023#post8340023
I did try flashing in a voodoo complient kernal (although not atinm's) but it still won't boot...
Isn't there an i9000 2.2 rom that can be flashed to captivate?

Try the jpk tomorrow on the i9000 forum. I was able to go back from it to 2.1.
Sent from my GT-I9000 using XDA App

http://forum.xda-developers.com/showthread.php?t=790637
You may be able to just grab the 803 pit from samfirmware and then put it all back with the 512 when your done *shrug*
yadda yadda yadda not responsible for your phone blah blah blah
Sherpa

I did some experimenting on my friends captivate, only because he was going to take it back anyway . It was stuck in the bootloop because of the ota software update, then had a failed to mount error.
If you dont have a failed to mount error, your internal sd is not corrupted, it just needs to be repartitioned.
The way I was able to get my internal sd repartitioned, so I COULD flash back to original 2.1 stock was to odin flash a 2.2 rom, then odin the stock. So if you can find one that is ok for the captivate try it.
now let me make myself clear, you dont have to have the 2.2 reboot fully, you just need it to repartition the internal SD. As a matter of fact, the one in the vibrant forums doesnt even boot all the way at all, its just a tool for us to get back to 21. original firmware.
so try it out.
1. odin flash the 2.2 rom let odin do its business,
2. get back into downloader mode and odin flash back to stock.
it worked for me on my vibrant. I hope it can work for others.

flashed xxjpk and back to stock. Still get mount errors.

kakalaky said:
flashed xxjpk and back to stock. Still get mount errors.
Click to expand...
Click to collapse
http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/
this might shed some light on the failed to mount error. Its definately an SD card issue.

@devin5277 will the parted linked to in the post you linked to work with the captivate? If its just a generic linux partitioning tool thats run through adb i think it should.

parted works fine on the captivate. In my case it didn't help though. Rooted then tried ffdisk and parted. Both give I/O read errors on /dev/block/mmcblk0. Looks like the internal sdcard no longer works.

[Q] Stuck in Boot-Loop (Gingerbread,Juwe'sROM 4.0, CR-Root3.1, ext4)

Hi all,
I upgraded to Gingerbread and Juwe's ROM last night and all went well. That is until today when I ran the script to convert the filesystem to ext4. It rebooted into CWM and all seemed to go well except my phone is now stuck in a boot-loop. It gets as far as the initial "Galaxy S GT-I9000 Samsung" screen and then restarts to it every few seconds.
Background:
I followed the instructions as given in Juwes thread. Initially flashed XWJVB XEE firmware with bootloaders from this thread (this exact firmware I think) with re-partition,etc checked. After that I flashed CF-Root-XW_XEE_JVB-v3.1-CWM3RFS (no-repartition) and flashed ROM. ROM was working perfectly till I ran ext4.
Does anyone know of any way to fix this problem? I can boot into Download mode and CWM Recovery v3.0.0.5. I'm trying to avoid reflashing the ROM but if I can't get a solution soon I guess I'll just have to do that

Hmmm,
Are you able to get into recovery or download mode?
Edit: Just noticed you can.

Another question,
What did you use to convert to ext4?
Did you install Chainfire's ext4 addon?

electrotune1200 said:
Another question,
What did you use to convert to ext4?
Did you install Chainfire's ext4 addon?
Click to expand...
Click to collapse
Ya it's Chainfire's ext4 addon I used. Although it's just occurred to me that I think I used the one packaged with the ROM instead of the newest one from Chainfire's thread. Could it be an older version?

Yeah I really don't know about that. When we get the phone sorted, I would install his most recent addon to see if that's the issue.
As far as I know, you may only have 2 options.
First, you can try to do a factory reset in CWM.
If that fails, I'd start from the beginning, flashing with a 512 pit and re-partion.

electrotune1200 said:
Yeah I really don't know about that. When we get the phone sorted, I would install his most recent addon to see if that's the issue.
As far as I know, you may only have 2 options.
First, you can try to do a factory reset in CWM.
If that fails, I'd start from the beginning, flashing with a 512 pit and re-partion.
Click to expand...
Click to collapse
I was afraid you'd say that. Just got the phone setup as I wanted it
Just tried the factory reset in CWM and no joy. Guess I'll re-partition when I get home. Should probably be doing some work at the moment anyway

Sorry man,
Next time, set everything up after you convert it to ext4. Might save you another headache.
Also, make sure you have some free space on your internal sd card. I try to leave 1.5gb free for file system conversions.
Oh and,
get some work done already

Before you go and flash everything again.
Try flashing Chainfire's 3.1 kernal again. It might pull it out of the boot loop. Worth a shot though before starting all over.
Hopefully it works out for you without starting all over.

I tried reflashing the kernel but no joy. Just went with the complete reflash in the end. Was painless enough because I had everything set up to go from the night before
Thanks for all the help electrotune! Appreciate it

[Q] "Unavailable" SD card?

I was out today, minding my own business.
In the middle, my phone just shut off. Restarting it, it would not boot past the kernel boot screen, not even into CWM. When I got home, I oneclicked it to stock in an attempt to return to my nandroid CM7 from right before the full-9 package was released. I encountered an issue.
CWM3 said "Error: Can't mount /sdcard". Booted the phone up in JF6, and the storage menu shows both my External and internals reading with total and available space as "Unavailable", and both the mount and format options on both are greyed out. Internal phone storage is normal, however, and reads 1.73GB.
Don't ask me to flash Froyo or something. Standard 2e recovery does not allow me to use a ROM Manager flashable CWM2, thus I cannot flash Froyo or CM7's package. CM7's initial kernel returns the "Can't mount /sdcard" error, so that's also inadequate.
So, anyone have any idea what I'm dealing with here? How would I be able to go about fixing it? If it helps, my IMEI number and all that jazz is still present.
EDIT: I just realised a perplexing quality. The phone will ONLY boot with an external SD in it... Doesn't matter if I remove it after, it just needs an external in it to boot. Once the phone boots, it's dead weight. Funny, as I always flash without it in there...
EDIT2: Found some info from Supercurio on the Bell Vibrant while searching, I wonder if this is relevant...
supercurio said:
On #project-voodoo IRC I helped a user who had issues with his SDcard on a Bell I9000M
Turns out that his internal SD MoviNAND chip was dead!
The system automatically used his external SD as a backup for /data, as the "mmcblk1" device become "mmcblk0".
The internal SD was so dead that the Linux Kernel didn't detected any existence of it anymore.
The symptom that the phone was working (using the external SD) but he couldn't mount his SD card anywhere.
Eventually he had a replacement from Bell in a few days.
What killed the sdcard ? An old Ext2 lagfix when creating the giant 1GB+ loop files.
But it wasn't the lagfix fault. It just acted as accelerator.
Click to expand...
Click to collapse
But I've never used that lagfix. I've been on Speedmod then CM7 the entire time.

Maybe flash a kernel with CWM in it, such as speedmod with Odin though I'm clueless as to what happened to your phone. I guess do this, flash a new ROM go from there... Sorry this is my only idea.

emcnelly said:
Maybe flash a kernel with CWM in it, such as speedmod with Odin though I'm clueless as to what happened to your phone. I guess do this, flash a new ROM go from there... Sorry this is my only idea.
Click to expand...
Click to collapse
Already said, CWM returns "Can't mount /sdcard" in CM7's CWM3 from the initial kernel... I can't flash Froyo, so Speedmod is out of the question.

Thread moved.

I'd try flashing a full odin stock rom and a .pit with it with repartition checked. I heard someone else with this sort of problem, he used odin one click but still got the same thing, flashed stock gb with a .pit and it worked.

studacris said:
I'd try flashing a full odin stock rom and a .pit with it with repartition checked. I heard someone else with this sort of problem, he used odin one click but still got the same thing, flashed stock gb with a .pit and it worked.
Click to expand...
Click to collapse
Did not work; tried flashing JH7, KB1 and JF6, all 3 do not boot past the kernel screen. Only OCD JF6 gets the phone in a working way. I found some other threads, but it's looking worse and worse by the second.
ATT is probably getting a call tomorrow...

Same happened to me, I managed to get JI6 working somewhat. Flash the one click ODIN JI6, wait till bootanimation ends, ROM will not boot up completely so go back into download mode, then flashed speedmod with three button ODIN, let boot up complete then go into recovery and delete user data, wipe cache and dalvik cache.
Still don't have an mnt/sdcard but at least I can make a phone call.
Also, I lost data connection so I had to manually enter APN in settings, wireless and networks, mobile networks, Access point names and create a new APN, I just googled AT&T APN for the values.
Hope it works out as I'm probably going to contact AT&T as well.

I had that happen kinda with "cognadian bacon" it fried my sd card and I flashed odin one click then master cleared in odin. After that I booted up and got my format option back ..... If that doesn't work you could probably hook it to computer (windows) and go under device management and format from there but don't know if will support fat32.. Just a suggestion though.... That what I did for my external sd when it wouldn't recognize it
Sent from my GT-I9000 using XDA Premium App

Phone won't boot

Hello, i have had my galaxy note for a couple of weeks now.
bit of this and that, you know how it is, flashing a few roms, checking things out, keeping it safe and stuff.
idiotic of me, didn't do a backup.
now
everything was working perfectly fine.
'till i decided to put some music on my sdcard
so i shut the phone down, open it up, take out the battery, take the sdcard, put it in pc, put some music (music i had on it before, so the files could've somehow magically ****ed up the device) then but it back on.
ever since, my device won't boot, it will go to CWM recovery, it will go to download mode, but not like, properly boot. all it does is show the Samsung Galaxy Note N7000 thingie, then screen goes black, and back again to Samsung Galaxy Note N7000, then black again, over and over again.
i figured, it must be something wrong with the bootanimation, had a custom one put there, so i deleted it, cuz that way it goes back to stock.
did that, didn't help, same thing.
then, decided to flash the rom again, even tho it was working perfectly for a few days now, (stock 4.0.4 deodexed zipaligned with hydracore safe kernel)
reflashed, didn't help, nothing happened.
things were weird, i thought i should go back to a GB rom, that always...fixes the problem.
tried to flash with ODIN, stuck at factoryfs, when i pulled the cable out, it would tell me the thingummyjig with firmware update has encountered an issue please bla bla kies.
then, I EVEN TRIED the kies, it won't connect, even tho my drivers are right, and i used kies with it before.
NOW, i thought to myself, ****, the phone won't go to recovery anymore, won't boot normaly, just in download, well, download a speedmod kernel which is safe and flash it, that should give you a CWM and safe kernel to flash from
did that, worked.
flashed the stock 4.0.4 rom again, then flashed philz latest kernel for the rom, and i'm back to square one.
nothing changed, i still can't use my note.
WHAT. DO?

right, well, i tried flashing alliance rom, and it gets stuck at mounting partitions....
the blue bar goes on and on till it gets out of the designated loading space
i can't wipe cache, i can't wipe dalvik, it just gets stuck.

Etnoscope said:
... tried to flash with ODIN, stuck at factoryfs ...
Click to expand...
Click to collapse
I just quoted the bad line in your post. This is a strong indicator that you have a bricked device.
So you should try to install a different stock GB or ICS Rom with Odin again. If it stucks there again: bricked.
Then you can try to use the workaround described in hg42's thread with repartition. Or send your device for a motherboard replacement to Samsung.
hg42 has a partition scanner which allows to check for emmc problems. Try this.

ThaiDai said:
I just quoted the bad line in your post. This is a strong indicator that you have a bricked device.
So you should try to install a different stock GB or ICS Rom with Odin again. If it stucks there again: bricked.
Then you can try to use the workaround described in hg42's thread with repartition. Or send your device for a motherboard replacement to Samsung.
hg42 has a partition scanner which allows to check for emmc problems. Try this.
Click to expand...
Click to collapse
Thing is, phone worked flawlessly before, safe kernel,could flash anything,then this just happened....
Phone doesnt have warranty, sending it to some service would only have me end up with extra costs for putting the motherboard there, which i can do myself

right, welll
i tried flashing speedmod kernel with odin, it worked.
then i tried installing a GB rom via CWM
works well till it gets stuck at flashing modem.
what does this mean?

Etnoscope said:
...what does this mean?
Click to expand...
Click to collapse
As I wrote before: possibility that you have a bricked device.
Why don't you try the partition scanner or why don't you try to flash a stock GB and check if you get stuck again with factoryfs.img.
As long as you try different things without a "plan" what you want to test you'll get nothing in the end.

ThaiDai said:
As I wrote before: possibility that you have a bricked device.
Why don't you try the partition scanner or why don't you try to flash a stock GB and check if you get stuck again with factoryfs.img.
As long as you try different things without a "plan" what you want to test you'll get nothing in the end.
Click to expand...
Click to collapse
tried flashing a stock gb with odin (tried 1 file in pda before, now i tried with 3 files(modem, rom, csc), same thing happened.)
stuck at factoryfs again
i didn't want to get to the partition scanner yet, wanted to clear out any other possibility first, using the scanner as a last resort.
what about pit files?
***
also, i really wanna thank you for showing some interest in my issue, means a lot to me, just wanted to let you know i really appreciate it, and i acknowledge the fact that you're a good, helping member.
thanks bro, you're awesome.

If you have tried also with the correct original pit, then it's time for the scanners to do its job

nokiamodeln91 said:
If you have tried also with the correct original pit, then it's time for the scanners to do its job
Click to expand...
Click to collapse
right
so, i've checked out this thread, about the pit method, and after i opened the emmc_find_brick_start.zip, it started scanning normally, and it finished without being stuck anywhere, and then at the end it said scanned 15027 MiB = 15757 MB completed --> OK then the ---end thingie and done.
so the brick start isn't there, which i assume means my phone is NOT bricked, at least not by the emmc thingummyjig
but if so, what the hell am i to do? like really?
tried flashing gb with cwm, stuck at flashing modem
tried flashing gb with odin, stuck at factoryfs
what the ****?

Get the pit file from this thread
http://forum.xda-developers.com/showthread.php?t=1424997
Then flash the GB rom using pc odin. Make sure pit is selected and the repartition is ticked.
Also if you still have access to cwm try to install a CM10 rom first before trying out the above method.

SOOOOO
bit of an update.
right, after the whole emmc scanning brick mbs and stuff, decided to try and flash allianceROM 4.0.4 final
did it, worked, the flashing.
now i'm stuck at a non blinking, non changing non nothing, Smasung Galaxy Note GT-N7000 screen, with the yello jello triangle, same as before, but its not blinking now.

Ok. Try booting into recovery and performing a full wipe.

nokiamodeln91 said:
Ok. Try booting into recovery and performing a full wipe.
Click to expand...
Click to collapse
full wipe means:
factory reset
wipe cache
wipe dalvik
reboot.
right?
did that, as soon as i hit reboot, it got stuck again there, the frozen CWM screen.
battery in/out, back to square 1

Still try a cm rom as it's small in size and easier to download. CM10.1 flash from recovwey

nokiamodeln91 said:
Still try a cm rom as it's small in size and easier to download. CM10.1 flash from recovwey
Click to expand...
Click to collapse
official 4.2.1 will do?

Yeah

nokiamodeln91 said:
Yeah
Click to expand...
Click to collapse
any way we could talk via IM?
would be much better conversation-wise

We could but where I am, it's 4 am. And I will be off to sleep in a while. Hehe

nokiamodeln91 said:
We could but where I am, it's 4 am. And I will be off to sleep in a while. Hehe
Click to expand...
Click to collapse
i get status 7 error when i try to flash a CM rom btw, i know what to do, updating philz kernel as we speak
i want you to know i really appreciate this bro, couldn't have come so far without you. thanks a lot man.

right, well, i was using kangbang kernel, tried to install the cm rom, and it gets stuck at installing update...
been there for too long now,so i guess thats a safe bet.
gonna try with a different cm rom
right, well, apparently anything i try to flash gets stuck at installing update....
any solutions?

Cant mount /sdcard

Can someone help i was running cm9 for a year then i decided to update to jellybean(cm10.1) it was working fine for a few day then out of nowhere the phone turned off and would only boot into recovery so i tried to factory reset it passed but it still would'nt boot into rom so i tried to install cm9 back but that was a no go. i decided to flash back to jvu. after i did that it booted into recovery it said failed to mount /sdcard. can anyone help?
sorry for a lack of punctuation, im panicking.

original issue idk.
current issue : ics bootloaders with non ics rom.
go back to stock bootloader.

to the jvu bootloader?

http://www.youtube.com/watch?v=1RoZU5ZPMS4
try this see if it fixes it goodluck

Did you manage to fix this I have a second SGS like this too.
Seems the internal memory is unmounted the only way to get it to boot was to partition SDCard and boot from that.

Nope I'm just gonna buy a a SD card class 10 and use it

flash darky ROM 10.2 through odi will get it to boot worked for mine

Jesus, third person I've told this to tonight lol
Its not bootloader.
If it happened straight after you flashed back to gingerbread then all you need(ed) to do was flash dbdata.rfs in Odin as PDA and you're done... All good again... Reboot...
No need to go buying SD cards heh
Sent from my GT-I9000 using Tapatalk 2