Related
Hi guys,
I know some of you guys with a i9000M bell version are running the JP6 or JPM, can you please do a write up with details on how to do it via Odin.
Please include link to the files and what needs to be done before the flash on the stock JH2.
Thanks.
I just flashed JP6 using 512 no repartition right over stock UGJH2. It worked okay till today when after seeing a ton of FC's I had to power cycle the phone and when it came back it lost the CSC/Modem so I had to do a factory reset.
I went back to stock Bell firmware for now.. not sure what I'll do. I heard JM9 works good, but I really want a stable Froyo with voodoo
moophone said:
I just flashed JP6 using 512 no repartition right over stock UGJH2. It worked okay till today when after seeing a ton of FC's I had to power cycle the phone and when it came back it lost the CSC/Modem so I had to do a factory reset.
I went back to stock Bell firmware for now.. not sure what I'll do. I heard JM9 works good, but I really want a stable Froyo with voodoo
Click to expand...
Click to collapse
Same thing happened to me. Which stock firmware did u get ? my phone will not event boot right now. Im only getting passed the animation then a black screen.
At least my Download/recovery works but even if i flash I9000UGJH2 from samfirmwares, it just stays on the black screen .... Trying another fix. But i think my internal SD card is finished. Hope not
I upgraded using reghack and Kies, but now there's no 850 band, so if you are on Bell do not bother to update with the Nordic firmwares.
Hey, I got a Samsung Galaxy S Vibrant GT-I9000M a few months ago and have since tried a few ROMs. I was upgrading from Darky's 8.1 rom to v9.1 by downloading the app for adjusting the settings for the new rom. The phone restarted itself some time after the instillation of the application and was then unable to mount the internal or external sd cards. A few minutes later I restarted it and the phone would only boot to the Galaxy S screen and song before going blank. I've used several versional of Odin3 with several different firmwares, pit files, enabled/disabled re-partitioning, including trying to flash the original I9000UGJH2 firmware. Nothing has gotten my phone functional again past the Galaxy S boot screen.
Is there anyone who can give me some help?
I just tried the the JPC firmware and still no luck ... Does anyone have any info they can share?
try this:
JH2 with or without repartition. Phone won't boot just flashes initial start screen
flash JL2 without partition and you're back to stock JL2.
if what pr0cs suggested, does not get you back to running OS again, then your internal SD is toasted
It didn't work ...
I get this message:
E:Can't mount /dev/block/mmcblk0p2
(Invailid Argument)
E:copy_data_default_apk: Can't mount DBDATA:
I was getting the same message with a few other firmwares. If it is just a corrupted internal memory unit, why would it have failed to mount the external sd card aswell while the phone was half working? Something doesn't seem right. I hear there is a way to modify the phone to boot from a formatted micro sd card, but I'd rather not have to get that in depth. My friend has the exact same phone if it can help in anyway.
call samsung send it in for repair
or find your invoice and go to a Bell store
that error is a definite confirmation your internal SD is hosed
even if you get it to boot with another ROM, you will not be able to access your SD cards
My condolences.
But..
Welcome to the club. It's not exclusive .
Will they be able to tell the firmware has been swapped if I flash it back to I9000UGJH2? I think it voids the warranty ...
it will not void the warranty if ur flashing it to OFW
Techloid said:
Will they be able to tell the firmware has been swapped if I flash it back to I9000UGJH2? I think it voids the warranty ...
Click to expand...
Click to collapse
I had this problem and fixed it with I9000XXJPU.rar search samsunggalaxysforums.com
http://www.google.com/m/url?client=...gQFjAB&usg=AFQjCNGbNJgSCIx6HmVWl9Bm_P5niowAgA
Sent from my GT-I9000M using Tapatalk
http://samsunggalaxysforums.com/sho...CIAL-STOCK-FROYO-2.2.1-IS-OUT!!!!-(i9000XXJPU)
Sent from my GT-I9000M using Tapatalk
Techloid said:
Will they be able to tell the firmware has been swapped if I flash it back to I9000UGJH2? I think it voids the warranty ...
Click to expand...
Click to collapse
flash it to JH2, then flash it to JL2,
factory wipe it
then back again to JH2, make sure it hangs in a black screen during boot, or infinite boot loop
then send it in for warranty
Techloid said:
Hey, I got a Samsung Galaxy S Vibrant GT-I9000M a few months ago and have since tried a few ROMs. I was upgrading from Darky's 8.1 rom to v9.1 by downloading the app for adjusting the settings for the new rom. The phone restarted itself some time after the instillation of the application and was then unable to mount the internal or external sd cards. A few minutes later I restarted it and the phone would only boot to the Galaxy S screen and song before going blank. I've used several versional of Odin3 with several different firmwares, pit files, enabled/disabled re-partitioning, including trying to flash the original I9000UGJH2 firmware. Nothing has gotten my phone functional again past the Galaxy S boot screen.
Is there anyone who can give me some help?
Click to expand...
Click to collapse
I was having a similar problem with my Captivate, except it happened after re-applying a lagfix to stock 2.2. Flashing Rogers stock 2.1 and 2.2 didn't fix the problem, but I was able to get a full boot after flashing to AT&T stock. After that, I was able to flash back to Rogers stock and it was as good as new.
James Palm said:
I had this problem and fixed it with I9000XXJPU.rar search samsunggalaxysforums.com
http://www.google.com/m/url?client=...gQFjAB&usg=AFQjCNGbNJgSCIx6HmVWl9Bm_P5niowAgA
Sent from my GT-I9000M using Tapatalk
http://samsunggalaxysforums.com/sho...CIAL-STOCK-FROYO-2.2.1-IS-OUT!!!!-(i9000XXJPU)
Sent from my GT-I9000M using Tapatalk
Click to expand...
Click to collapse
Thanks James! It seems that the xxjpu firmware has a fix for internal-sd failure. I had the phone sent in the first time, but this worked for me when I tried it the second time my phone decided to die. It seems the problem is in not checking the bootloader update in odin when upgrading to the 2.2+ firmware. I'll try not to make that mistake again!
nzahorchak said:
I was having a similar problem with my Captivate, except it happened after re-applying a lagfix to stock 2.2. Flashing Rogers stock 2.1 and 2.2 didn't fix the problem, but I was able to get a full boot after flashing to AT&T stock. After that, I was able to flash back to Rogers stock and it was as good as new.
Click to expand...
Click to collapse
captivates are built slightly different... so this problem will not be the same, this fix won't work on the i9000
Hey guys, i just screwed up my galaxy s using odin. I was trying to upgrade my firmware from 2.2 to 2.2.1(in fact I recently upgraded from 2.1 to 2.2) when my phone went dead.
Now that i turn it on by holding down vol-up + home + power, all i get is this message:
RST_STAT =0x1
PMIC_IRQ1 =0x3c
PMIC_IRQ2 =0x0
PMIC_IRQ3 =0x0
PMIC_IRQ4 =0x0
PMIC_STATUS1 =0xc0
PMIC_STATUS2 =ox2c
*
I would appreciate your help and time spent in giving me some tips or better yet solutions to solve this issue. Thanks.
More info: Any customization ie. rooted, lagfixed, custom roms?
I used s1_odin_20100512.pit after that my phone turned off giving me the messages i just explained.
Not that familiar with 2.2.1, but I would make the assertion that you should not be using PIT files to ROM flash unless you need to change the partitions. You should be using PDA files. You will probably need to search for the proper PIT and PDA files for stock 2.1 or 2.2 and flash those. Are you able to see the phone via ODIN?
Exactly what kind of phone do you have. Is it a captivate or I9000?
Sent from my SGH-I897 using XDA Premium App
search odin 1 click
and go back to stock
you should still be able to get to DL mode
It doesn't even load on odin nor my computer can recognize the device.
i have a captivate I9000. I think the problem should have caused it that when i started odin i clicked the re-partition box.
capo503 said:
It doesn't even load on odin nor my computer can recognize the device.
i have a captivate I9000. I think the problem should have caused it that when i started odin i clicked the re-partition box.
Click to expand...
Click to collapse
Ok well the captivate is not an i9000 it is an i897, so you are in the wrong place. Also might be why if you used odin files set for the wrong device. I would look into getting a jig.
it is an i897. However, after upgrading to 2.2 and rebooting the phone, i would see a screen saying that it was an i9000. So what you think is that i installed the wrong adin files? great!!
what does a jig would do to my phone?
capo503 said:
it is an i897. However, after upgrading to 2.2 and rebooting the phone, i would see a screen saying that it was an i9000. So what you think is that i installed the wrong adin files? great!!
what does a jig would do to my phone?
Click to expand...
Click to collapse
How did you update to 2.2? if you used the new update you would not have gotten and i9000 screen unless it is a custom rom, A jig will force it into download mode.
If you can get a jig to get you into d/l mode, check out this thread to get you back to normal.
I'm sure you can find some sources for the jig in this thread, but if you prefer to try to make one, yourself, look here.
This may be a handy thread for you, too.
I got the update from Samsung Kies. I got that screen after rooting my phone.
i did three things: update from 2.1 to 2.2, root my phone, and attempted to upgrade to 2.2.1.
The third thing i did messed up my phone.
I will try getting a jig and see what happens. I hope it works fine again.
capo503 said:
I got the update from Samsung Kies. I got that screen after rooting my phone.
i did three things: update from 2.1 to 2.2, root my phone, and attempted to upgrade to 2.2.1.
The third thing i did messed up my phone.
I will try getting a jig and see what happens. I hope it works fine again.
Click to expand...
Click to collapse
Ok if Keis updated your phone to 2.2 with the i9000 screen then you dont have a i897 captivate. you have the i9000. mainly sense there is no keis upgrade for 2.2.1 for the captivate.
I was using odin to update to 2.2.1 and ended up bricking my phone!!
I had to use PDA instead of PIT as you said previously!!
Thanks!! there is also a tuturial about how to do a jig here
http://www.youtube.com/watch?v=Rdn5GoRjhn0
i might follow that one, seems helpful too.
capo503 said:
I was using odin to update to 2.2.1 and ended up bricking my phone!!
I had to use PDA instead of PIT as you said previously!!
Click to expand...
Click to collapse
I personally never said anything about PDA or the PIT file. What carrier are you on? ATT, Rogers?
OOOPS SORRY!! your right it wasn't you. Yes AT&T.
capo503 said:
OOOPS SORRY!! your right it wasn't you. Yes AT&T.
Click to expand...
Click to collapse
Ok then there is no way Keis updated you to the 2.2 with the i9000 screen, that comes from a custom rom. Get a jig and boot into download mode, if all the other methods have failed and flash back to stock with odin. Oh and all the 2.2.1 roms are custom roms normally used with CWM flashes. Might need to do a little be of research and spend a few hours reading up to make sure this doesnt happen again.
Thank you SO MUCH!!! I really appreciate the time you spent helping me.
And yeah i will do that definitely, that's the moral of the story.
Again, THANK YOU!
Ok I was trying to flash new rom...so I flashed to stock...but after the process finished in Odin...and it showed Reset....my phone should have rebooted right? But it didnt reboot...just got dead...I removed everything and tried to start it no use...even used jig...but its no responsive...I am not panicked (as it was my experimentation phone)...but trying to find what to do in that case...battery was full too....
I am in desperate need of help you guys! I screwed up so hard that I don't even know where to begin...
THE SITUATION:
-Right now when I go to turn on my phone, it will only stay on the current SAMSUNG GALAXY S I9000 screen (the very first screen when booting your phone) and it keeps flashing in and out.
Before trying to use Odin to put back the original Kernal on my phone, it was just stuck as the SAMSUNG GALAXY S I9000 screen, still wouldn't start. <I followed this website step by step>
http://www.samsunggalaxysforum.com/...-to-a-stock-rom-after-installing-darky's-rom/
BEFORE ALL OF THIS EVER HAPPENED:
I finally rooted my phone and manage to download Clockworkmod recovery on my phone and then used it to flash Darky's 10.2 custom ROM. Everything turned out great except at the beginning of the boot, the screen turned all rainbow coloured, completely distorted, and it continued to do that. I then tried to go back to Recovery mode to do the Voodoo lagfix but I couldn't even get into the recovery mode anymore, it either wouldn't let me, or it did but the screen didn't go to it properly (more likely the first one). I read somewhere that if you reflash your phone again, it should make all the tweeks go away. So I tried that from the Darky's tools menu and ever since then, I've been stuck with the Boot Screen this whole time...
I already bricked my phone once, and that was before the Flashing Boot Screen.
I really need help you guys, I would at least like to have my phone back to the original basis, at least! Your help would be greatly appreciated!
THANK YOU
P.S. (i'm not that great at all this phone tweeking, but I've succeeded in doing it up until yesterday)
Can you get into download mode (vol down+home+power while putting the battery in)?
If you can, just reflash a stock or custom rom in odin (like a darky odin rom) as guided by whatever rom you choose.
If you cannot get into download mode then we should know that too.
Edit: oh it looks like you could (and hopefully still can). Try a different rom or reflash. Sometime things do go wrong but as long as you can get to the download screen you should be fine in the end.
G
gfacer said:
Can you get into download mode (vol down+home+power while putting the battery in)?
If you can, just reflash a stock or custom rom in odin (like a darky odin rom) as guided by whatever rom you choose.
If you cannot get into download mode then we should know that too.
Edit: oh it looks like you could (and hopefully still can). Try a different rom or reflash. Sometime things do go wrong but as long as you can get to the download screen you should be fine in the end.
G
Click to expand...
Click to collapse
Yes, I can get into download mode! (thank you for reading my post).
If it's not too much to ask, could you maybe find the ROM that would be good for me to flash, considering my situation?
I want to be sure that it's what the top tech guys would recommend
A link would be appreciated
thank you again!
I'd start with a Darky rom - lots of users - active forum and odin editions for your situation. I have to go but you'll find the link on the first page of the development section.
G
gfacer said:
I'd start with a Darky rom - lots of users - active forum and odin editions for your situation. I have to go but you'll find the link on the first page of the development section.
G
Click to expand...
Click to collapse
So in essence all I have to do is flash the Darky ROM V10.2 with Odin using the Download mode on my phone and it should be okay?
Wait one caveat. Was it a gingerbread rom or froyo? Use a Darky rom of the same type...
Then yes it should be ok if you follow their guide. Cross fingers.
Sent from my GT-I9000M using XDA Premium App
gfacer said:
Wait one caveat. Was it a gingerbread rom or froyo? Use a Darky rom of the same type...
Then yes it should be ok if you follow their guide. Cross fingers.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
well...I did everything you said. The ROM is on there alright, it flashed and everything (And I know this because now when the boot screen STILL FLASHES, the darkcore & darky's rom logo are on it too).
THIS TIME AROUND:
The stock recovery seems to work...
any ideas??
Well we are sort of in long shot territory now... OK first try using a different odin version or ez odin and reflash.
If still not working??
Might be warranty time then but others are welcome to chime in.
Sent from my GT-I9000M using XDA Premium App
gfacer said:
Well we are sort of in long shot territory now... OK first try using a different odin version or ez odin and reflash.
If still not working??
Might be warranty time then but others are welcome to chime in.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
Alright I'll try and reflash the same one using a different version of odin the. I'll let you know what happened
gfacer said:
Well we are sort of in long shot territory now... OK first try using a different odin version or ez odin and reflash.
If still not working??
Might be warranty time then but others are welcome to chime in.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
tried ezodin, flashed it, and i still get the exact same thing I've exhausted every single possibility there is!!!
I really need help on this, my warranty is not gonna do anything because i have the phone rooted..
If you flash a stock rom with pit the root is gone. It won't boot but they can't prove it was you either and I don't think it was you.
But see my other post on your other thread for one last thought.
G
Sent from my GT-I9000M using XDA Premium App
gfacer said:
If you flash a stock rom with pit the root is gone. It won't boot but they can't prove it was you either and I don't think it was you.
But see my other post on your other thread for one last thought.
G
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
okay that could be useful data potentially (let's hope it won't have to be).
If you didn't see my reply from the other thread, here it is:
Once I rooted my phone, I automatically went from Stock Froyo to Darky's 10.2 extreme edition. It worked and everything except for that color disfiguration and the clockworkmod recovery not working.
It's weird because after I flashed my first darky's rom, i checked the phone and it said that the firmware version was 2.3.X (I believe X may have been 4). So from what you're saying, I don't exactly think it has anything to do with the fact that I went straight from froyo stock to GB darky ROM.
So are you saying that I should flash darky's 9.3 for Froyo and THEN flash the latest version?
No I think that you need froyo re edition then stock gb with bootloader (as the instructions say I thought) then a custom gb like 10.2.
Sent from my GT-I9000M using XDA Premium App
gfacer said:
No I think that you need froyo re edition then stock gb with bootloader (as the instructions say I thought) then a custom gb like 10.2.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
Ok, so just to be 100% on this
-I should flash Darky's 9.2 froyo onto my phone,
-then I should flash regular GB onto my phone (Not sure about the bootloader part though, if you could clarify that)(Also where would I get JUST a stock GB ROM?)
-then I can flash a custom GB ROM?
gfacer said:
No I think that you need froyo re edition then stock gb with bootloader (as the instructions say I thought) then a custom gb like 10.2.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
well i can safely say that flashing the 9.2 froyo rom was a fail. It's still doing the same old routine.
I just know that this problem can be fixed somehow without sending it in to bell or samsung or something.
roma17 said:
well i can safely say that flashing the 9.2 froyo rom was a fail. It's still doing the same old routine.
I just know that this problem can be fixed somehow without sending it in to bell or samsung or something.
Click to expand...
Click to collapse
I think you are right but other than trying again and again, which I've done before -though now I know why I had too - I am out of suggestions. Good Luck and if I have a brainwave I'll let you know.
Sent from my GT-I9000M using XDA Premium App
OK a few last brainwaves:
1) Try a fully complete stock rom with cache.rfs, dbdata.rfs, factoryfs.rfs, modem.bin, param.lfs, zImage, and sbl.bin (this was from JL2 rom for Bell - not sure if they all have the sbl.bin) and pit.
The key is to make sure it is complete. Try downloading the same rom from 2 different sources just to be sure its not a corrupt download (going overboard I know).
2) Can you get into recovery? Try to format partitions (not system) under advanced features (I think - I only have 3e right now as I am trying to diagnose other issues).
3) If you have a froyo rom on at one point, try to put a steam recovery kernel on. Its not really being developed anymore but I think that if you put a CWM packaged rom on to the external SD you could flash from there or at least move it to the internal and then flash it. Worth a shot. Or you might be able to transfer one in regular CWM recovery - can't recall as I have not had to try for about 8 months.
4) If you really want to try something completely different, and I am not sure I've got the balls if it was me but if you can get a file to flash from CWM or steam that you can get on from the external SD, you might try CM7. It uses a completely different file system so you'd have to go back to froyo via odin only (as a samsung based rom will not play well when flashed on top of the cm7 file system).
And calling it a day at this one...
gfacer said:
OK a few last brainwaves:
1) Try a fully complete stock rom with cache.rfs, dbdata.rfs, factoryfs.rfs, modem.bin, param.lfs, zImage, and sbl.bin (this was from JL2 rom for Bell - not sure if they all have the sbl.bin) and pit.
The key is to make sure it is complete. Try downloading the same rom from 2 different sources just to be sure its not a corrupt download (going overboard I know).
2) Can you get into recovery? Try to format partitions (not system) under advanced features (I think - I only have 3e right now as I am trying to diagnose other issues).
3) If you have a froyo rom on at one point, try to put a steam recovery kernel on. Its not really being developed anymore but I think that if you put a CWM packaged rom on to the external SD you could flash from there or at least move it to the internal and then flash it. Worth a shot. Or you might be able to transfer one in regular CWM recovery - can't recall as I have not had to try for about 8 months.
4) If you really want to try something completely different, and I am not sure I've got the balls if it was me but if you can get a file to flash from CWM or steam that you can get on from the external SD, you might try CM7. It uses a completely different file system so you'd have to go back to froyo via odin only (as a samsung based rom will not play well when flashed on top of the cm7 file system).
And calling it a day at this one...
Click to expand...
Click to collapse
Okay, basically at this point, I just want my phone to work I've tried what you said. I remember that before rooting my phone initially I was running Froyo 2.2.1. So I found the ROM for that ( http://www.samfirmware.com/WEBPROTECT-i9000.htm ) Just like you said. I downloaded from the *Provider Samsung Galaxy S i9000 heading and picked the I9000BOJS5 ## from February 2011 because I think somewhere around there I updated my phone to Froyo. Flashed it, did everything, still no luck.
I've had a recent hunch though. When the bootscreen boots up, it keeps saying i9000 only, when before it used to say i9000M at least for a little bit (yes my phone is i9000m). Is there a stock froyo rom that's specifically designed to go with the i9000m model? Or are they just all the same?
Never give up
-Thank you so much
I was just wondering I just recently bricked my last Captivate luckily At&t replaced it for free but im not sure how many more times thats going to work. My idea was that the brick occured from a suspicious looking 2.3 odin file but im not sure if that bricked it. Should I try flashing with the same computer but with a diferent 2.3 odin? I got a new one heres the link.
http://forum.xda-developers.com/showthread.php?t=1129821
Edit: forgot original package that bricked my phone.
http://forum.xda-developers.com/showthread.php?t=1232703
voldomart13 said:
I was just wondering I just recently bricked my last Captivate luckily At&t replaced it for free but im not sure how many more times thats going to work. My idea was that the brick occured from a suspicious looking 2.3 odin file but im not sure if that bricked it. Should I try flashing with the same computer but with a diferent 2.3 odin? I got a new one heres the link.
http://forum.xda-developers.com/showthread.php?t=1129821
Edit: forgot original package that bricked my phone.
http://forum.xda-developers.com/showthread.php?t=1232703
Click to expand...
Click to collapse
A hard brick occurs when you flash incompatible bootloaders. Make sure you flash the gingerbread bootloaders first (either the i9000 bootloaders or 2.3 captivate bootloaders) with odin then flash your gingerbread rom. There are odin packages that include just the bootloaders. Hope that helps.
Sent from my SGH-I897 using xda premium
Yeah it kinda helps im gonna wait though and buy a usb jig just so im ready if anything does manage to go wrong. Thanks though i didnt know that.
See with the package i used that bricked my phone it got stuck in a certain stage and wouldnt go anywhere so i tryed unpluging it and try to go back to 2.1 but after that attempted 2.3 flash it wouldnt accept any odins.
A hard brick not only happens with incompatible bootloaders, but with an incomplete bootloader flash, which is what happened, you say it stopped at a certain point, that is more than likely where it bricked. That package isn't "suspicious", if it were there would be a lot of reports about it.
The first link you posted is bootloaders only. It will not flash 2.3 firmware at all. Just the boots.
To make sure odin doesn't stall out, use a port on the back of the pc, right click odin and run as admin.
What studacris said. Keep in mind there is always a small risk on flashing that Odin fails. So once you flash Gingerbread bootloaders just don't flash any bootloaders again unless you really need to. OR Look in to the Unbrickable mod if you want that.
Just askin how long would ikt take to flash just the gb bootloaders?
Less than a second. Its a very small risk to begging with BUT a risk none the less.
ANother question is there any danger in downgrading bootloaders?
Same as upgrading. No reason to Downgrade except maybe AOSP specific kernels or warranty.
I had to right now because of a bootloop and a failed custom rom install and none of my backups worked and i couldnt install anything else. It said on clockworkmod that it couldnt read my cache folders. Did i have to go back to 2.1? Because thats what i did. Also thank you guys for answering my questions the captivate is so much more complex that the droid when it comes to custom roms and stuff like that.
voldomart13 said:
I had to right now because of a bootloop and a failed custom rom install and none of my backups worked and i couldnt install anything else. It said on clockworkmod that it couldnt read my cache folders. Did i have to go back to 2.1? Because thats what i did. Also thank you guys for answering my questions the captivate is so much more complex that the droid when it comes to custom roms and stuff like that.
Click to expand...
Click to collapse
No there are Odin packages that Do not include bootloaders, just saying. Same as there is GB packages without bootloaders as well (this goes for KF1 and KH3 to my knowledge). Once you flash GB bootloaders there is no reason to reflash bootloaders except for AOSP specific kernels and Warranty.