Related
Okay, so after corrupting my SD card over 12 times and replacing my phone twice I think I have found the answer.
I strongly believe that the reason we get faced with the SD corruption (The ones where it is fixable by a software reset at the service center) on our i9000m's is because we repart while flashing.
The 512,513,903 pit files might be okay on international models, but I suspect that the Canadian version uses some other partition structure.
So to keep it short here is a successful method to install froyo on the i9000m. I have flashed to froyo using this method and have been using it for over 20 days now without issues.
Make sure you get a brand new phone before flashing. If you have reparted using odin this might be useless.
Installation Steps:
1. Make sure your phone is rooted (You can root via OCLF in the market)
2. Download Rom manager and install Clockworkmod recovery (Instructions can be found here - http://forum.xda-developers.com/showthread.php?t=734166&highlight=clockwork)
3. Install Doc's froyo rom from here ( http://forum.xda-developers.com/showthread.php?t=817703)
Once flashed it should work fine. When the phone starts make sure you first see the I9000M screen and then it switches to the I9000 screen and then the Galaxy and then into Froyo.
I have not tried just flashing froyo using ODIN without re-parting (Maintaining factory partitions). In theory it should work, if anyone tries it let us know.
P.S. I use Doc's rom as it allows to flash via clockwork. I am not endorsing this in any way.
I have personally flashed dozens of things through Odin with 512 and 803 pit, as well as tons of things through zip's like Doc's, with absolutely no problems on my Bell I9000M 16GB.
**Knocks on wood**
Do you lose your 850 Band doing it by this method. Please check by Activating WiFi while in your service menu (*#*#0011#*#*). You will see when you switch over from WiFi to 3G you Band should drop down to 850 from 1900.
Woolios said:
Do you lose your 850 Band doing it by this method. Please check by Activating WiFi while in your service menu (*#*#0011#*#*). You will see when you switch over from WiFi to 3G you Band should drop down to 850 from 1900.
Click to expand...
Click to collapse
WelCOME HOME OCRF's, Happy Flashing. http://forum.xda-developers.com/showthread.php?t=823702
rumy said:
I have not tried just flashing froyo using ODIN without re-parting (Maintaining factory partitions). In theory it should work, if anyone tries it let us know.
Click to expand...
Click to collapse
I've tried this one.. Never repartitioned yet still had a corrupt sd in the end.
cloudrainstar said:
I've tried this one.. Never repartitioned yet still had a corrupt sd in the end.
Click to expand...
Click to collapse
Can you give more information on what happened.
Original ROM?
Froyo Version tried to flash to?
Which SGS ei (gt-i9000m or gt-i9000)?
I've re-partitioned in ODIN by flashing back to JH2 (2.1), then use Doc's ROM to 2.2. What should I do to enable 850Mhz? I already added WCDMA850 in *#2263#
Woolios said:
Can you give more information on what happened.
Original ROM?
Froyo Version tried to flash to?
Which SGS ei (gt-i9000m or gt-i9000)?
Click to expand...
Click to collapse
1. UGJH2
2. I believe the one that it died on was XXJPM, after about 3 days. I've flashed XXJPH and XXJPK before that on that phone as well for a few days each, no pit/re-partition every time I flashed
3. GT-I9000M
killer23d said:
I've re-partitioned in ODIN by flashing back to JH2 (2.1), then use Doc's ROM to 2.2. What should I do to enable 850Mhz? I already added WCDMA850 in *#2263#
Click to expand...
Click to collapse
Does 850Mhz Band work for you? Could you check with the above method
Woolios said:
Can you give more information on what happened.
Original ROM?
Froyo Version tried to flash to?
Which SGS ei (gt-i9000m or gt-i9000)?
Click to expand...
Click to collapse
I am an Indian & have an Asian 16GB SGS. Every time & have this urge to FLASH, I just pick the pit file, nothing else, check re-partition, let the phone reboot, remove battery, re-insert, go back to download & re flash.
Me n 2 friends bought it together from same bell store 3 months ago.
Friend 1 :
On his 2nd sgs.
Got it replaced because internal sd got corrupted.
He was on jpk w/ repartition done
Friend 2 :
Still on his original sgs.
Stock + voodoo (aka never used odin)
Me:
On my 3rd sgs (if u count replacing the pcb as a new phone)
First one was stock + voodoo (stock was flashed using repartition through odin)
Second one was jpk w/ repartition
Third one im running with stock + voodoo (aka following friend #2's approach)
Hope tht helps :\
rumy said:
Okay, so after corrupting my SD card over 12 times and replacing my phone twice I think I have found the answer.
Click to expand...
Click to collapse
That's dedication right there.
ragin said:
I am an Indian & have an Asian 16GB SGS. Every time & have this urge to FLASH, I just pick the pit file, nothing else, check re-partition, let the phone reboot, remove battery, re-insert, go back to download & re flash.
Click to expand...
Click to collapse
Most of the time what I do is use Odin 1.3 Use an 803 PIT re-partition not checked at the same time select the PDA Phone and CSC since your 900MHz you should not have a problem using the GT-i9000-CSC-Multi-XXXXX.tar.md5 for CSC and the MODEM_i9000XXJPK.tar.md5 for Phone and your PDA will be JPM/JP6 or whatever rom you wish to install
cloudrainstar said:
1. UGJH2
2. I believe the one that it died on was XXJPM, after about 3 days. I've flashed XXJPH and XXJPK before that on that phone as well for a few days each, no pit/re-partition every time I flashed
3. GT-I9000M
Click to expand...
Click to collapse
Funny thing is I'm on 3rd SGS now too my first one I went crazy on Flashing everything as I had no problems with anything I did to it until JPM/JP6 I bought another SGS while I sent in the other one as a replacement for mine and as a gift for my wife after I get my SGS back from bell. The one I got for my wife died within 6 hours of flashing ROM's I use to have the 850MHz band on my original SGS throughout the whole flashing process but I couldn't repeat it with my wife's SGS. Now since I've buggered hers once already I'm now scared to do anything with this one. Although I still have the DOA warranty on it. I'm I crazy??? Probably more confused as I spent a lot of time reading on these forums and don't have an answer to what went wrong...
I have the Captivate and my girl has the I9000M. I am definitely not new in flashing, just find it very interesting that after flashing Doc's V6, the Bell APN still remained and the boot screen still has I9000M.
Did Bell do something to the phone to prevent people modding it?
So far, my gf didn't complain about corrupting SD. She got hers like 3 weeks ago and the battery production date is Oct 2010. The phone even has 3 button download mode working out of the box.
Okay so with all the excitement and multiple upgrades of docs rom I made a boo boo.
I flashed a wrong kernel (BLN) using CWM and the phone would not start and could not get into CWM. So I did a flash to UGJG8 and then restored to dock.
Things would work fine for a few hours and then I would get errors, my internal SD card was intact, however my internal available memory was 0. I repeated this process with the same issue, finally got fedup and reparteed with the 512 and it all worked for a few hours and then internal and external all said unavailable.
Now when I boot It goes to the 19000 screen and then shuts off.
However, when I load UGJG8 with my external SD it boots to android and none of the SD cards are available, but internal available says 1.85.
I am trying different things as I want to try and figure out whats going on, any suggestions?
P.S. I strongly believe it has something to do with odin and/or pit files, i.e. software fix.
rumy said:
Now when I boot It goes to the 19000 screen and then shuts off.
However, when I load UGJG8 with my external SD it boots to android and none of the SD cards are available, but internal available says 1.85.
Click to expand...
Click to collapse
Aren't those 2 the "Internal Sdcard Corruption" indicators ?
Boot into recovery. What do u see ?
Yup, I know it is the internal SD card corruption.
Ohh well.... back to the bell store
P.S. I want to highlight that all of this started once I used odin, till then I was using froyo for over a month without any issues. now it might be a coincidence but I dont think so!
I won't use odin if I don't have to. Il use cw instead
Sent from my GT-I9000m
I've flashed JPK for Phone, CSD and the other one. 512 Pit.
I did it on 2 i9000M and never had problem.
I used mine exclusively with 3G Data only though. No Calling plan attached.
Hello everyone!
Just wanted to show my depreciation of samsung products over the past few months...
It's the 4th GT-I9000M I get since august (in fact first exchange was done in october)
I got the phone 45 minutes ago by mail, it was probably a refurb (of course it was...). Inserted my sim inside (Phone was already unlocked as I didn't have to do it)....
Then I've started installing my apps and stuff than phone froze.....
Rebooted and.....
-----------------------------------------------------------------------------
Update Media, Please Wait
E:Can't mount /dev/block/stl10
(Invalid Argument)
E:copy_dbdata_media:Can't mount DBDATA:
You storage not prepared yet. please use UI menu for format and reboot action
-----------------------------------------------------------------------------
This is completely retarded.....aren't they testing the phone before shipping it to customers?
How could this be possible....
I don't know what to do between throwing the phone on the wall, crying, don't think about it and use an other phone or call them back.....maybe all of this once at a time.....
What enrage me the most is that currently there is absolutely no solutions to Dead Memory for the GT-I9000M.......I saw some for GT-I9000, tried it for my older buggy GT-I9000M but didn't get anything better thand "can't mount...."
Teranox said:
-----------------------------------------------------------------------------
Update Media, Please Wait
E:Can't mount /dev/block/stl10
(Invalid Argument)
E:copy_dbdata_media:Can't mount DBDATA:
You storage not prepared yet. please use UI menu for format and reboot action
-----------------------------------------------------------------------------
Click to expand...
Click to collapse
This is not the failed internal SD card error. I'm assuming this happened when you tried to flash a JP? rom with repartition checked in odin....
Flash the phone back to JH2 and then flash back to whatever 2.2 rom you were trying WITHOUT repartition rechecked.
Electroz said:
This is not the failed internal SD card error. I'm assuming this happened when you tried to flash a JP? rom with repartition checked in odin....
Flash the phone back to JH2 and then flash back to whatever 2.2 rom you were trying WITHOUT repartition rechecked.
Click to expand...
Click to collapse
+1
This happened to me in my earlier days of SGS flashing (albeit with the standard UK I9000) but my phone is fine now, you should be fine just flashing older firmware via Odin as quoted above.
Don't worry - all is not lost
Electroz said:
This is not the failed internal SD card error. I'm assuming this happened when you tried to flash a JP? rom with repartition checked in odin....
Flash the phone back to JH2 and then flash back to whatever 2.2 rom you were trying WITHOUT repartition rechecked.
Click to expand...
Click to collapse
correct that is just a corrupted internal SD partition message
it can be fixed, but flashing back to JH2 or JM8
then flash back to JL2
Electroz said:
This is not the failed internal SD card error. I'm assuming this happened when you tried to flash a JP? rom with repartition checked in odin....
Flash the phone back to JH2 and then flash back to whatever 2.2 rom you were trying WITHOUT repartition rechecked.
Click to expand...
Click to collapse
holly **** I LOVE YOU MAN!!!!
Phone is back to normal....
wanted to install Darky 8.0 as same as i did with previous phone. but then something went wrong
While installing 2.1 stock from bell with odin (to get 2e recovery working) something was different, phone logo was just flashing on/off so went back to 2.2 and error code was there....
So do you know what has caused 2.1 not running? first time i did it partition was cheked with previous phone and it worked
If I install speedmod kernel would I have to downgrade to apply darky 8 slim ROM
So do you know what has caused 2.1 not running? it was the same than
Teranox said:
holly **** I LOVE YOU MAN!!!!
Phone is back to normal....
wanted to install Darky 8.0 as same as i did with previous phone. but then something went wrong
While installing 2.1 stock from bell with odin (to get 2e recovery working) something was different, phone logo was just flashing on/off so went back to 2.2 and error code was there....
So do you know what has caused 2.1 not running? first time i did it partition was cheked with previous phone and it worked
If I install speedmod kernel would I have to downgrade to apply darky 8 slim ROM
So do you know what has caused 2.1 not running? it was the same than
Click to expand...
Click to collapse
Can't comment on the other queries but if you want to install SpeedMod kernel then make sure the Voodoo lagfix is disabled (do this by going into recovery and lagfix options) and then flash SpeedMod with ClockworkMod recovery
Teranox said:
holly **** I LOVE YOU MAN!!!!
Phone is back to normal....
wanted to install Darky 8.0 as same as i did with previous phone. but then something went wrong
While installing 2.1 stock from bell with odin (to get 2e recovery working) something was different, phone logo was just flashing on/off so went back to 2.2 and error code was there....
So do you know what has caused 2.1 not running? first time i did it partition was cheked with previous phone and it worked
If I install speedmod kernel would I have to downgrade to apply darky 8 slim ROM
So do you know what has caused 2.1 not running? it was the same than
Click to expand...
Click to collapse
Bell's UGJL2 rom has an updated bootloader that supposedly fixes the internal SD failures. This bootloader has compatibility issues with the 2.1 firmwares. There is a full version of JH2 going around that includes the old bootloader, but must be installed with the "Phone Bootloader Update" option checked in Odin. This will allow you to go back to 2.1
However, since you are aiming for a 2.2 rom, I suggest sticking with JL2, Flashing a custom Kernel that includes clockworkmod (ex. Speedmod or Voodoo) and installing Darky's with clockwork.
Electroz said:
Bell's UGJL2 rom has an updated bootloader that supposedly fixes the internal SD failures. This bootloader has compatibility issues with the 2.1 firmwares. There is a full version of JH2 going around that includes the old bootloader, but must be installed with the "Phone Bootloader Update" option checked in Odin. This will allow you to go back to 2.1
However, since you are aiming for a 2.2 rom, I suggest sticking with JL2, Flashing a custom Kernel that includes clockworkmod (ex. Speedmod or Voodoo) and installing Darky's with clockwork.
Click to expand...
Click to collapse
I'm now using Speedmod Kernel (the on that just got released today loll) so I can flash with this one.
I think before messing up again with everything i'll just let it like it is with speedmod (that claim to help the battery, increase speed, and have BLN enabled)....
Darky release rom so fast anyway loll that even i i install it today next week there gonna be 2-3 new relase loll
soooooooooooooo happy to get back my android device.....was using my old BB 9000 for a week.....needed a little more speed
Nice work Teranox.
"I got the phone 45 minutes ago by mail, it was probably a refurb (of course it was...). Inserted my sim inside (Phone was already unlocked as I didn't have to do it)....
Then I've started installing my apps and stuff than phone froze....."
It's bad enough you probably lie to Samsung/Bell about the situation surrounding the death of your phone, but lying to us here is sick.
Looks like your the one who actually messed up the phone on the first, second and third time. Conisder your self lucky that you still got a replacement.. Technically flashing those kernels and non samsung official release is already voiding your warranty.
It's one of the advantage of being a Samsung Mob!lers ;-) but the first one really died while never customised it. Second one same thing third one 3 days after normal.use under darky rom 7 with lagfix.
The one is just got (the fourth) crashed because i was not informed about the re-partion check/uncheck difference with the last firmware from bell.
Anyway, stock rom with speedmod is perfect from me since it is fast without lag and bln enabled. Will see in the coming weeks if Darky release something tempting enough to flash loll
Sent from my GT-I9000M using XDA App
So I tried flashing to XWJS3 in order to set my phone to PIT 803. As I understand i have to do this in order to flash it to XWJS5. After flashing with all 3 files i get this error in the recovery mode
How can I solve this?
Update: Flashing to I9000XXJPU replaced the DBDATA. The file from samfirmware.com did the trick! Thanks for a great forum
This should resolve any issues you have with the DBDATA since the I9000XXJPU-rom creates a new DBDATA.
Open Odin and select 512 .PIT, and CSC, PDA, MODEM-files. Check Re-partition and don't touch any other settings.
Turn off your phone and put it in download mode by holding VOL DOWN+MENU+POWER.
Now just flash the phone with your ROM of choice. See here for correct flashing procedures: Flash Firmware and kernels using Odin
AFAIK you should only repartition if you have a lowlevel/full rom. Make sure you use the correct PIT either way.
Click to expand...
Click to collapse
Update 2: After reading feedback from several forum members it seems like it may be wise to just stick with 512 PIT for the time being.
dbdata
nooryani84 said:
So I tried flashing to XWJS3 in order to set my phone to PIT 803. As I understand i have to do this in order to flash it to XWJS5. After flashing with all 3 files i get this error in the recovery mode
How can I solve this?
Click to expand...
Click to collapse
you need to download odin then you flash dbdata.rfs.tar in though odin to the sgs in recovery mode.files below
P.s press the thanks button =)
Thanks for the tip though as I find little documentation on that fix I think I'll flash to I9000XXJPU then XWJS3 with 803 => then XWJS5.... or can I skip the second step?
hehe sorry, I'm pretty new at this and have been reading a ton.
This is a fairly common issue. If you repartition your device (ie. run repartition with a new .PIT file) you change the partition sizes and therefore some of the old partitions become unavailable. In this case the partition that holds dbdata would have been changed and the old dbdata data was unavailable to the system. The fix is (a) flash a full ROM that contains all the components needed eg. JPU in this case, or (b) flash just the component you need eg. dbdata.rfs in this case. Either way would resolve the problem.
Hi,
i have the same Problem. After an unsuccessful flash (including a brain fart) with the JS5.
Flashing the I9000XXJPU with 512 pit and repart fixed the issue, i could start my phone again.
However, after that i flashed the JPY-PDA with 512 pit + repart i have the same "Can't mount DBDATA" error again :/
When i do a factory reset + reboot in this state, i get the Bootscreen with the Samsung S Logo, but then the screen just turns black and nothing happens.
Any suggestions how to fix this?
i had the same problem i would flash JPU with Repart and 512 all fixed then i would flash JS3 with repart and 803 and i get the same error then i went back to JPU then fixed then JS5 or JS3 i get the error back again. I do see dbdata.rfs being flashed as the last thing but still the error.
The only way i could get it to boot was when it showed the error i would scroll down the recovery console to wipe/clear data and then reboot and it worked fine booted to JS5. Hopefully thats works for you.
So in summary i flashed JS5 fine but had to do a wipe/clear data then reboot in the console but i dont know if it means there is still a problem but so far its working fine. My only issue is that i still have the old market and i cant see all the samsung apps like video editor etc.
Well, that is what i already tried. It starts into the samsung bootscreen after that but then it just force closes and i have to pull the battery.
I just flashed JPU again, the phone is in a working state atm. But i would like to upgrade it to the JPY, without the error obviously
//EDIT
Just tried it again, here is what i have done:
1. Flashed JPU with repart and 512 pit
2. Confirmed it was working.
3. Rebooted into recovery, did a factory reset + a wipe data
4. Rebooted again, confirmed its working
5. Flashed the JPY with repart and 512 pit
---> DBDATA error again :/
6. Factory reset + wipe cache
But after a reboot i only get force closes and a black screen.
Any suggestions?
Do i need to flash the JPY in a different way after i have successfully flashed the JPU?
//EDIT²
Well, after i did start to actually use my brain it did work
I did flashed with JPU(3 Files), repart and a pit file.
So there is no actual reason to flash the JPY and AGAIN use a pit file + repart.
Its what i did when i flashed the JPY the first time (i came from 2.2 back then).
My phone is booting without any issues now, and i have JPY-JPY-JPY again
which pit file did you use ofr JPU to work with repart?
i think we are in the same boat we both have been on pit 512 and need to somehow get to pit 803
Copacaba said:
//EDIT²
Well, after i did start to actually use my brain it did work
I did flashed with JPU(3 Files), repart and a pit file.
So there is no actual reason to flash the JPY and AGAIN use a pit file + repart.
Its what i did when i flashed the JPY the first time (i came from 2.2 back then).
My phone is booting without any issues now, and i have JPY-JPY-JPY again
Click to expand...
Click to collapse
I forgot to mention that I did NOT use flash it with another PIT-file after the initial JPU flash + PIT. When I tried that appoach i got the same DBDATA-error. However I plan on flashing it with this I9000_XEN_I9000XWJS5 which includes all 3 files.
Download I9000_XEN_I9000XWJS5, see first post.
I'm interested to know if anyone has success with this method. Are there any benefits of changing the PIT file?
I was stuck at DBData error! Wiped the Cache/User data. But only after seeing this thread I came to know that there is no necessity for that
So for the people who are reading this thread with the dbdata problem. Here's my experience NO NEED TO WIPE USER DATA FOR DBDATA PROBLEM. To solve the dbData problem, I went to Darky resurrection and now I'm in Darky 9.2, though its good, I'm far more comfortable with stock rom for some reason.
Now I'm Totally confused on how to flash to JS5.
What should I do now?
Flash XEN JS5(3 files) + 803pit + repart ?
emmarbee said:
I was stuck at DBData error! Wiped the Cache/User data. But only after seeing this thread I came to know that there is no necessity for that
So for the people who are reading this thread with the dbdata problem. Here's my experience NO NEED TO WIPE USER DATA FOR DBDATA PROBLEM. To solve the dbData problem, I went to Darky resurrection and now I'm in Darky 9.2, though its good, I'm far more comfortable with stock rom for some reason.
Now I'm Totally confused on how to flash to JS5.
What should I do now?
Flash XEN JS5(3 files) + 803pit + repart ?
Click to expand...
Click to collapse
If you follow the instructions in the first post you will have to re-partition with a full stock rom such as JPU. This will erase all your user data/cache. Afterwards you can flash JS5 with just the PDA.
You may be able to flash/re-partition JS5 with 3 files and 803 pit, though I can't confirm if this is a full rom like JPU. If it is a full rom then I think you may be able to skip flashing JPU all together.
Someone more knowledgable than me would have to confirm this before I can recommend it though. To be on the safe side just flash JPU(3files)+512 PIT w/re-part first, then JS5(1 file) without re-part.
well stop using pit 803.
use 512 or 513.
samfirmware have a love for pit 803 but its most useless of them.
this has been up for discussion 100+ times and the fact is that pit 803 really sucks.
**DamianGTO Steam kernel. 350MB Ram. 500HZ. all ext2. Steam Rom. Js5**
Really Damian? Because on some threads people are saying the opposite.. In truth, I haven't seen any evidence that anyone has actually analysed the PIT files well enough (except maybe the Heimdell developer), to know whats going on, and I don't really recall him saying what was going on.
Have a look at this :
http://forum.xda-developers.com/showthread.php?t=816449
The basic difference is the partition size of system and dbdata.
Auzy said:
Really Damian? Because on some threads people are saying the opposite.. In truth, I haven't seen any evidence that anyone has actually analysed the PIT files well enough (except maybe the Heimdell developer), to know whats going on, and I don't really recall him saying what was going on.
Click to expand...
Click to collapse
well i know it well. its looked into how it works.
the main thing is the different size of the partition. but many has different problem when using pit803.
it always works with pit 512, accept for one firmware. that need pit 513.
that's for the firmware is to big for pit 512.
**DamianGTO Ultimate kernel. 350MB Ram. 600HZ. all ext2. Steam Rom. Js5**
UFFF!
I can confirmed method on first post working, and very important is what write on gray:
If you're upgrading to a newer rom with 803 you must NOT re-partition again or you will end up with the same problem.
Thanks and Regards
miro666 said:
UFFF!
I can confirmed method on first post working, and very important is what write on gray:
If you're upgrading to a newer rom with 803 you must NOT re-partition again or you will end up with the same problem.
Thanks and Regards
Click to expand...
Click to collapse
Thanks for the feedback, I´ve updated the post. This problem annoyed the hell out of me, so I hope it saves people some of the frustration.
TechKidTarek said:
you need to download odin then you flash dbdata.rfs.tar in though odin to the sgs in recovery mode.files below
P.s press the thanks button =)
Click to expand...
Click to collapse
This unbricked my phone. Thank you sir.
The dbdata File was flashed in Recovery Mode? Not in Downloadmode?
Hello folks,
I posted here recently about an issue I had when I loaned my brother my Vibrant running 2.2, and he accidently installed Voodoo 2.1 on it. It made a big mess of my phone, and I wasn't able to even boot up.
Working with several members of a few different Android forums, I got myself working using Eugene's No Brick ROM. My phone seems to be working fine, except that now the phone thinks it's Application Storage is 0.00kb left, when I know I have over 11GB on the internal SD. The feeling I've got from several people is that my stock kernel I reflashed is only seeing the space it's installed on, and not all the reformatted space that Voodoo has altered.
A few of the guys I talked to said I probably need to reset my phone with a FULL ODIN package (that includes boot.bin. sbl.bin movinand.bin) to reset the phone's internal SD back to the original format.
Does anyone know where I can find that full ODIN package?
Or if anyone else has any other ideas, please let me know.
The bootloaders won't help...just increase the chance of a hard brick. You probably will benefit from odin with the pit and tar with repartition checked for jfd.
Edit: fyi this will wipe your entire internal sd, so backup.
I have the same problem. Can you please point me to the download links and name of the pit and tar? Thank you.
http://forum.xda-developers.com/showthread.php?t=771111
everything you need is in there. Good luck.
Sdobron said:
The bootloaders won't help...just increase the chance of a hard brick.
Click to expand...
Click to collapse
My phone is a brick right now if I don't install a ROM with a bootloader on it (Eugene's No Brick ROM). That's the only way I can get it to boot up.
kgbros said:
http://forum.xda-developers.com/showthread.php?t=771111
everything you need is in there. Good luck.
Click to expand...
Click to collapse
Thanks, I've been looking at all the various stickied threads, and can't find what I am looking for, which is why I was asking for some help.
I was hoping someone could point me right to what I need. None of the ROMS I found in there are the complete ODIN packages.
You don't need a bootloader to correct this problem
I'm going to echo everybody else's statements, you don't need to flash any new bootloaders.
No offense OP, but I'm pretty sure you don't know what bootloaders are.
The Wikipedia page on bootloaders
Use 512.pit file and check repartition.
Some good info here as well
http://forum.xda-developers.com/showthread.php?t=848737
Read my previous post. This WILL fix your problem.
Thanks for your responses everyone,
Several times I've tried reflashing the stock ROM and PIT file (and selecting partition), and each time I've ended up with the same result - I get the T-Mobile and Galaxy S boot screens, and then the phone goes black and stays there.
The only way I can get my phone to boot up is using Eugene's No Brick ROM.
You can read more about my initial problem here.
Any help you can offer would be greatly appreciated.
You're supposed to flash eugene's then jfd with repartition checked. I've had the same exact brick before (my only legitimate soft brick) and this is the solution.
Edit: Have you been able to check your partitions in adb shell? Check mount and see if they are rfs or ext4.
Thanks Sdobron - I've done that many times, and after doing jfd (T959UVJFD) with a re-partition, I get the soft brick again.
If I check adb, my partition is rfs.
This is why I am so confused. It's like my phone shows no signs of why there should be an issue, and everything I try doesn't work.
Dear all,
Before I started a new thread, I just wanted to tell you that I've been awake for over 14 hours Starting to fix issues with my phone and tried alot of things before resorting to starting a new thread,So Please excuse me for starting one
Here's the long one :
Got a Galaxy S as A Present, after an Iphone 3GS, phone is great .. was a branded vodafone one I think from Germany running Android 2.2.1 I think back then.
As am Egyptian I wanted to the phone to read arabic fonts,So I decided it to flash with the Official Android 2.3.3 Arabic version.
Flashing went perfect, everything is smooth and all is very cool started to love the phone.
I dont have an external SDcard this is the internal one btw.
after a few months, a Friend challenged me that he's blackberry would boot faster than an android.
I was intrigued ! So I turned off my phone, turned it back on (I think this was the first time I do it since I flashed it) the phone kept rebooting !
and after like rebooting 10-12 times ... it finally booted correctly (5-6 minutes)
I said something must be wrong with the Firmware I flashed, but Ignored it as the phone worked perfectly after this.
a few days ago it died on battery, charged it ... reboot loop !
I found a hundred of thousands of guides on how to fix that boot loop !
I was getting errors :
e:failed to mount /sdcard (file already exists)
e:copy_dbdata_media:can't mount /sdcard
your storage not prepared yet.please use ui menu for format and reboot actions
meida files copy failed.
after going into recovery mode and trying to wipe data, these above errors always showed.
So I found a guide that suggests flashing with a 3-file ROM (Phone/Modem/CSC) and re-partition would fix this.
So I flashed with the official 2.3.3 (unmodified) and the errors disappeared, phone works perfectly ! although everything is erased of course.
So after setting it up again I thought that I should test restarting it again..
so I did .... and there it goes .. went on Looping again !!!
I went into recovery mode ... same errors appeared again ...
Re flashed 3 files again ... works fine ... restart = loop !
although one time it looped a few times and it did boot at the end, the SDcard (internal one) can be formatted without errors, never had any writing issues so I dont think its corrupted or anything.
But now I can't let the phone reboot or die on battery without flashing it again .. as if its a TETHERED jb iphone !
any suggestions ?
Please try doing as follows:
1. Flash a Kernel with lag-fix support like Voodoo which I can recommend in this case.
2. After flashing the Kernel the phone should boot and the converting of the partitions from RFS to EXT4 will begin, let it be until the phone reboots to the user interface.
3. Turn the phone off and enter Download-mode and re-flash the device using the firmware of your choice and a different pit file of that that is used on your phone (use 512.pit if it's on 803.pit or 803 if it's on 512), you need to use pit and you need to check re-partition.
4. Do a factory reset from recovery after completing the first boot, you need to let the phone boot all the way to user interface then do a factory reset after turning it off.
I hope that this will fix the issue that you are having, good luck and let us know how it goes.
[Ramad] said:
Please try doing as follows:
1. Flash a Kernel with lag-fix support like Voodoo which I can recommend in this case.
2. After flashing the Kernel the phone should boot and the converting of the partitions from RFS to EXT4 will begin, let it be until the phone reboots to the user interface.
3. Turn the phone off and enter Download-mode and re-flash the device using the firmware of your choice and a different pit file of that that is used on your phone (use 512.pit if it's on 803.pit or 803 if it's on 512), you need to use pit and you need to check re-partition.
4. Do a factory reset from recovery after completing the first boot, you need to let the phone boot all the way to user interface then do a factory reset after turning it off.
I hope that this will fix the issue that you are having, good luck and let us know how it goes.
Click to expand...
Click to collapse
I will try it right away, Thanks a lot for your time.
Well I don't know what to do now!
before flashing the kernel you suggested, the phone died on battery so I had to charge it, opened it .. boot looop .. so I said am going to do the same thing I used to do the past few days .. flash with the official 2.3.3 (3 files flash) and repartition.
Apparetly that doesn't cut it anymore, I tried DarkysRom as well, I still get the same error now :
e:failed to mount /sdcard (file already exists)
e:copy_dbdata_media:can't mount /sdcard
your storage not prepared yet.please use ui menu for format and reboot actions
meida files copy failed.
Can't get past it, and of course the phone keeps on boot looping if I ignored it
Am I beyond repair ?
ok after a few reboots, the phone booted correctly, is there's anything to do after it booted ? its on the 2.3.3 now, should I try to update from sdcard thing ?
You don't have a problem with the SD-Card, the problem is with the Kernel not able to mount partitions /data and /dbdata it's why you get those loops, that can happen if there is errors on these spaces and there journals which are located on these partitions.
My advice regarding flashing a costume Kernel and converting to EXT4 is to format these partitions and wipe all these errors, then flashing back to a firmware using pit and reparation should give you a clean firmware install with no errors.
You can try to turn off the phone and power it up again and see if it boots as it should, if not then some of the partitions still does not mount correctly.
You don't have to worry about the device, flashing and re-flashing it will not break it, it's a very solid phone, just be careful and you will be fine.
Always flash when the device has enough battery power (50%-100%)
Ok I've got the voodoo fix but its for 2.2 not 2.3 .. (Vooodo 5.5 ) there's a beta (Voodoo 6.0) for 2.3
I tried flashing 5.5 this morning to the current rom, it still kept on rebooting but it took along time to do so .. (long time between reboots).
So I thought of getting a rom with voodoo built in .. so I got the DarkySrom Resurrection 10.2 and after flashing .. it still went into constant loops..
I have a few things that I didn't try yet, I will post with updates, thanks again for ur time.