I was running JPH on my i9000m when it lost signal, froze up, and wouldnt boot past the i9000 splash screen. So I flashed JH2 on it, It then came up with the error: "E:Can't/b mount /devlock/stl10". It will get past the galaxy s boot up video but will hang into black. Its just like my 1st i9000 that didnt have 3-button recovery at the time, I had it replaced. But this one had 3-button recovery out of the box. I am surprised I cannot fix it ATM. I flashed different froyo builds on it and they came up with: "E: can't mount /dev/block/mmcblk0p1". I have read that this has something to do with the filesystem of the phone being corrupt or something of that effect? Which makes sense, Since I did have a lagfix on it when It keeled over.
I hope someone can point me in the right direction
PS: I spent hours researching but I couldn't find anything that worked. I rarely post for help...buuuut, I'm kinda at a loss :S
PPS: I will be playing Dead Rising 2 early as I wait for responses
your phone is most likely toast, search around for similar problem, no one has been able to wipe or reset the internal sd card when this happens...its very frustrating, im on my second galaxy S because of this problem. the sooner you take it back the sooner you will have a new phone.
Flash jpc with 512 pit and reparation ticked.
Than you can go back to jph by flashing again without pit and without reparation.
Sent from my GT-I9000 using XDA App
omrij said:
Flash jpc with 512 pit and reparation ticked.
Than you can go back to jph by flashing again without pit and without reparation.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I'd love to hear if this actually works, i'm guessing it won't....I was told to try all kinds of different things including this....nothing worked. good luck.
omrij said:
Flash jpc with 512 pit and reparation ticked.
Than you can go back to jph by flashing again without pit and without reparation.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Ya-no.
This will not work with this error code. Although, It has worked in the past with other errors.
I have a feeling I'm gonna have to get ANOTHER replacement....It probably won't be a DOA instant switch like last time though..augh....Loner-Phone, Here I come! :'(
I wonder...
Does Clockwork Recovery have a button combo? Much like regular recovery?
Jordiharrison said:
I was running JPH on my i9000m when it lost signal, froze up, and wouldnt boot past the i9000 splash screen. So I flashed JH2 on it, It then came up with the error: "E:Can't/b mount /devlock/stl10". It will get past the galaxy s boot up video but will hang into black. Its just like my 1st i9000 that didnt have 3-button recovery at the time, I had it replaced. But this one had 3-button recovery out of the box. I am surprised I cannot fix it ATM. I flashed different froyo builds on it and they came up with: "E: can't mount /dev/block/mmcblk0p1". I have read that this has something to do with the filesystem of the phone being corrupt or something of that effect? Which makes sense, Since I did have a lagfix on it when It keeled over.
I hope someone can point me in the right direction
PS: I spent hours researching but I couldn't find anything that worked. I rarely post for help...buuuut, I'm kinda at a loss :S
PPS: I will be playing Dead Rising 2 early as I wait for responses
Click to expand...
Click to collapse
Hello
I had the same and i solved through the guide here:
http://briefmobile.com/how-to-android-2-2-on-galaxy-s
But i think the problem really was that i have make an ext2 partition on sd-card.
I removed the sd-card during flashing.
Works !!!!
omrij said:
Flash jpc with 512 pit and reparation ticked.
Than you can go back to jph by flashing again without pit and without reparation.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Worked like a charm for me. Cheers
omrij said:
Flash jpc with 512 pit and reparation ticked.
Than you can go back to jph by flashing again without pit and without reparation.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Worked for me too. Thanks!
omrij said:
Flash jpc with 512 pit and reparation ticked.
Than you can go back to jph by flashing again without pit and without reparation.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Ok so i used this method to get my phone running again and it worked, which is why i said thanks. But the problem now is that i dont want to flash to jph and it keeps giving me the same error if i flash any other firmware.
Anyone know the soloution for this? All help appreciated thanks.
P.s I've been trying to flash back to lower firmwares so that i can update to froyo officially through kies.
Update:
Nobody seems to be helpful around here when i ask for help but thought id share with the people who have this problem in the future.
Try using a different pit file when flashing, as there are two types of pit files. If you need more details just pm me.
Hi Riverriz , what's jpc stand for?
Flashing JPC with repartition using 512 pit works!
My Internal SD working again just after flashing JPC, now go back to Doc's rom. Thanks.
guys what is JPC and how do you falsh with it im stuck with same issue any links ??
update: did this and the phone gets tsuck in a reboot loop tried two 512 .pit
Is the JPC rom you're talking about the one available on samfirmware.com that unpacks to "I9000XXJPC_I9000OXAJPC With new .PIT and ODIN"?
I've been trying to flash various roms all afternoon with different versions of Odin and different .pits and invariably I get either an stl10 error, an stl11 and mmcblk0p1, or just an mmcblk0p1 error.
The mmcblk0p1 error seems to be pretty much finito as far as these phones are concerned but I was hoping that the fact that various roms would give me the stl10 error from which other people had been able to recover meant that there was still hope.
Is there a possibility for recovery from where I'm at?
I have problem like that on my galaxy tab. i didn't find answer on briefmobile,and i'm very afraid that i broke my device. so please, somebody, tell, how to solve this problem
Miggles said:
Is the JPC rom you're talking about the one available on samfirmware.com that unpacks to "I9000XXJPC_I9000OXAJPC With new .PIT and ODIN"?
I've been trying to flash various roms all afternoon with different versions of Odin and different .pits and invariably I get either an stl10 error, an stl11 and mmcblk0p1, or just an mmcblk0p1 error.
The mmcblk0p1 error seems to be pretty much finito as far as these phones are concerned but I was hoping that the fact that various roms would give me the stl10 error from which other people had been able to recover meant that there was still hope.
Is there a possibility for recovery from where I'm at?
Click to expand...
Click to collapse
I am in a similar situation. Does anyone have any ideas how to fix this? I tried to install Doc's JPU rom with the CWM JPU kernel and now I seem to be chasing partitions that can't mount etc.
Thanks,
David
I eventually gave up on this - it wasn't going to fix itself regardless of what I did.
JPC with the 512 PIT worked for me. Now my I9000 is flying again.
Related
Are there any problems flashing directly from JPK, On samfirmwares they recommend flashing to JM8 first.
I've seen people report there are no problems, but why do they recommend this?
Shocky2 said:
Are there any problems flashing directly from JPK, On samfirmwares they recommend flashing to JM8 first.
I've seen people report there are no problems, but why do they recommend this?
Click to expand...
Click to collapse
I struggled with JPC to JP6. I had to flash to JM1 before I could get it working.
SamFirmware seems like a bunch of n00bs.
I've installed every firmware without any repartition or PIT file. Just download the firmware and if you're using Odin to flash don't load any PIT file or select repartition. I just loaded the JPM stuff as PDA and flashed. No problems. Check the screenshot for a better idea if you don't understand what I'm saying.
Thanks for the help, I'll give that a try but first...
One more question, do I really need to remove the OCLF before flashing? Only it keeps failing to remove telling me theres not enough space.
Nevermind, got it working, but was it needed?
I flashed from JPK to JP6 with no problem. 803pit but I did not tick re-partition.
If you're not repartitioning then there is zero point to even bothering to load a PIT file.
I went straight from jpk to jpm without any hicups. I would recommend doing a factory data wipe once you have jpm. I did it from the phone settings then again from the bootloader to be sure.
Running well. I did have to install sgs tools and do a.market fix to get my paid app back from the market.
Sent from my GT-I9000 using XDA App
Many thanks, flash went well, rooted with lagfix.
Yep, did factory data wipe etc once it was flashed.
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
Hi everyone,
I own a captivate-i896 (rogers)
I have run into a very serious trouble
I tried to odin back to stock and now I am experiencing this problem. I get the following message:
update media. please wait
E:Can't mount /dev/block/st110
(Invalid argument)
E:copy_dbdata:media:Can't mount DBDATA:
copy default media content failed.
PLEASE HELP.
I tried delete all user data. reinstall packages. delete cache. EVERYTHING.
I even trying flashing again 3 times. No luck.
Can someone please help?
First thing is your phone isn't bricked if it still has power and you can see things on it. Second, what were you doing with Odin when it was flashing? Was it the full Odin or a one click version? Are you making sure you flash the proper firmware? What did you have on your phone before you tried going back to stock? Lots more detail is helpful because your phone works...just not like it should. Again its no brick and searching the forums will help with your issue.
This is my Captivate. There are many like it but this one is mine.
haroonazeem638 said:
Hi everyone,
I own a captivate-i896 (rogers)
I have run into a very serious trouble
I tried to odin back to stock and now I am experiencing this problem. I get the following message:
update media. please wait
E:Can't mount /dev/block/st110
(Invalid argument)
E:copy_dbdata:media:Can't mount DBDATA:
copy default media content failed.
PLEASE HELP.
I tried delete all user data. reinstall packages. delete cache. EVERYTHING.
I even trying flashing again 3 times. No luck.
Can someone please help?
Click to expand...
Click to collapse
You had a lagfix installed that you did not disable before you reflashed. Your internal partition is still on ext4 but the data is on efs. This is not a problem. You need the one-click version of odin. Search the threads for it and instructions on flashing. You will have the att boot logo but there are ways to work around it, but first do the one click.
Sent from my SAMSUNG-SGH-I896 using XDA App
clemmie said:
You had a lagfix installed that you did not disable before you reflashed. Your internal partition is still on ext4 but the data is on efs. This is not a problem. You need the one-click version of odin. Search the threads for it and instructions on flashing. You will have the att boot logo but there are ways to work around it, but first do the one click.
Sent from my SAMSUNG-SGH-I896 using XDA App
Click to expand...
Click to collapse
I thought Lagfix didn't need to be disabled if you were flashing to stock, just going from ROM to ROM. Besides that, I don't feel comfortable running 1-click for any reason as it bricked my first phone, just trying to flash.
What ROM were you running when you encountered this problem?
Stock, with a SpeedMod kernel. I wanted to go back to a stock kernel with voodoo. Trust me on this one, one-click will restore you to 2.1 if you follow the instructions.
See this thread:
http://forum.xda-developers.com/showthread.php?t=964749
Sent from my SAMSUNG-SGH-I896 using XDA App
The reason you have to disable the lagfix is because with a new ROM you are likely flashing an integrated kernel with a lagfix. Some are Captivate-based, some are i9000-based. Additionally, some use Supercurio's Voodoo Lagfix, some use Hardcore's SpeedMod. One or more of these elements might be incompatible going from one configuration to the new flash config. Without knowing more about what you had before and what you wanted to flash, this is the best explanation I can give.
If you are irked by the AT&T boot screen, I am also partial the this fellow's package, which I have used and works well. Read and make sure you have the Rogers version.
http://forum.xda-developers.com/showthread.php?t=944418
clemmie said:
Stock, with a SpeedMod kernel. I wanted to go back to a stock kernel with voodoo. Trust me on this one, one-click will restore you to 2.1 if you follow the instructions.
Click to expand...
Click to collapse
It has nothing to do with following the instructions - It has to do with the Batch version of the phone - 1010 and 1012 batch numbers do NOT play well with 1-click.
Dante04SRT said:
It has nothing to do with following the instructions - It has to do with the Batch version of the phone - 1010 and 1012 batch numbers do NOT play well with 1-click.
Click to expand...
Click to collapse
I'm well aware of that:
http://forum.xda-developers.com/showpost.php?p=11649620&postcount=5
What you might not be aware of is that Rogers Captivates are not prone to these failures as they are different build numbers. This is a fellow Rogers customer. I'd bet dollars to doughnuts that his build is 10.11.
Thanks everyone for all the responses.
Actually I had doc's rom installed on my phone and I believe I had the hardcore speedmod kernel OR the glitterball's kernel on my fone and also had the lagfix.
I was actually in process of flashing the cyanogen 7 gingerbread when this happened. I forgot to copy the actual flash file(that i was supposed to instal from speedmod kernel recovery) and so i just decided to odin back to stock and start the process all over again. But after doing that my phone never went past the rogers splash screen.
I use the ODIN 1 click software where u just load the PDA and PIT files and flash the fone. I have tried Odin back to stock for Rogers eclair 2.1 and froyo 2.2 without any luck. I also tried the at&t 1 click odin flash back to stock without any luck.
The best I was able to do was to reach the rogers splash screen and then the screen turned black and thats it.
I flashed many different kernels but nothing happened.
I even downloaded the giorgio armani firmware for the captivate and flashed that which got rid of the mounting error in the 2e recovery screen but after the splash screen, the phone just kept vibrating and nothing happened.
I have tried everything you guys asked me too.
Also, after flashing the I9010 rom(giorgio armani), my download mode 3 button combo changed. First, I used vol up and down plus USB to get into download mode but now its changed to vol down + power. This one is not a big deal as i can still get into download mode. But I am telling you all just to help.
I also read somewhere that we cannot repartition and flash using odin 1 click if we have a lagfix kernel installed. I might have done that too that might have caused the problem.
Someone here mentioned that the file system is changed from ext4 to efs or something like that. I don't know what the real problem is.
Please help
clemmie said:
I'm well aware of that:
http://forum.xda-developers.com/showpost.php?p=11649620&postcount=5
What you might not be aware of is that Rogers Captivates are not prone to these failures as they are different build numbers. This is a fellow Rogers customer. I'd bet dollars to doughnuts that his build is 10.11.
Click to expand...
Click to collapse
My build is 10.10
but I never had a problem with flashing with 1-click ODIN to stock before.
I have tried both AT&T and rogers versions through 1-click odin.
Hope that helps.
clemmie said:
Stock, with a SpeedMod kernel. I wanted to go back to a stock kernel with voodoo. Trust me on this one, one-click will restore you to 2.1 if you follow the instructions.
See this thread:
http://forum.xda-developers.com/showthread.php?t=964749
Sent from my SAMSUNG-SGH-I896 using XDA App
Click to expand...
Click to collapse
I am just going to try your method. I am downloading from here:
http://forum.xda-developers.com/showthread.php?t=731989
However, I cant do master clear because im stuck in recovery. Does it matter?
im going to try and see.
will update soon
clemmie said:
Stock, with a SpeedMod kernel. I wanted to go back to a stock kernel with voodoo. Trust me on this one, one-click will restore you to 2.1 if you follow the instructions.
See this thread:
http://forum.xda-developers.com/showthread.php?t=964749
Sent from my SAMSUNG-SGH-I896 using XDA App
Click to expand...
Click to collapse
I got it working. THANKS A LOT TO YOU.
YOU ARE THE MAN clemmie.
I didn't know that what I was using before wasn't a 1-click odin lol
it's fixed now. just have to install the rogers eclair or froyo now. Thanks a LOT!
haroonazeem638 said:
I got it working. THANKS A LOT TO YOU.
YOU ARE THE MAN clemmie.
I didn't know that what I was using before wasn't a 1-click odin lol
it's fixed now. just have to install the rogers eclair or froyo now. Thanks a LOT!
Click to expand...
Click to collapse
It can be pretty harrowing when you are in limbo like that, glad to be of assistance.
Clemmie, YOU rock!!! I haven't had this problem, but... your instructions were stated in a way that I could visualize the whole process! If I ever have issues, I'm looking for YOU!
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....
Just got a "new" captivate due to defect in the last one.
This new Captivate worked fine at 2.2 I was in the beginning stages of a prep for Continuum when this happened.
The boot loop seems to be attributed to the Odin One-Click to 2.1, seems almost like there is a different partition layout in the newer build versus the older one. Is that possible? I read something about pit files maybe?
What has been done:
1. Built a jig
2. can reboot into download mode reliably with jig
3. Tried to flash OCD to 2.1 around 10x before I gave up.
4. Flashed the Ursa minor kernel, just sits after stating "converting XX partition"
5. Flashed "back" to 2.1 with OCD again. Boot loop [confirmed]
6. Brought phone into work and tried the re-install of 2.1 [boot loop]
So now I am looking for stock 2.2 images I can flash with Odin, only thing is I can only find Rodgers....
Who has some ideas?
sounds like you have a later build phone that doesnt like odin one click...thats all your gonna get out of it is a bootloop
get into download mode and use this package:http://forum.xda-developers.com/showthread.php?t=995143
if you go to gingerbread and want to revert back to stock bootloaders you will have to use one click, even though you will end up in a bootloop and then use the package i posted to get it up and running completly sotck.
I tried that right after I posted and that didn't seem to work either, it actually froze up. In the end I had a true brick, even the jig couldn't get it into download mode anymore. It was just dead. I'm thinking the internal SD got corrupted.
I returned the phone and got another that I am not doing anything with until the GB update from Samsung comes out.
As a follow up it seems the only way to get back to stock reliably with a greater than 1010 build is to use the stock froyo from this thread:
http://forum.xda-developers.com/showthread.php?t=963403
IF the partitioning is fscked:
I'm still researching but I assume it's due to a param.lfs and pit issue. I may rip open the archive when I get a second to see if they are in there.
I haven't tried this! This is not the gospel! Do this at your own risk.
My phone is still stock at the moment and may very stay that way until hell freezes over or the ATT update to 2.3.4 comes along.
Partitioning is in the .pit in fact that's exactly what pit stands for.
P= partitioning
I= Information
T= table
dan_maran said:
My phone is still stock at the moment and may very stay that way until hell freezes over or the ATT update to 2.3.4 comes along.
Click to expand...
Click to collapse
Smart money is on hell freezing over!
studacris said:
Partitioning is in the .pit in fact that's exactly what pit stands for.
P= partitioning
I= Information
T= table
Click to expand...
Click to collapse
I did get that much, but I remember mine failing at the param.lfs(in Odin) then I heard rumblings about the pit being the culprit when taking a >= 1010 build down to 2.1
Just trying to get all the information in one spot for myself and anyone else who has has this happen. Like finding a pit file from a stock 2.2 build etc.
edit: I don't know when this will go through as I have to wait 5 minutes... (tick tock tick tock)
Here is a post that has all the needed information:
http://forum.xda-developers.com/showthread.php?t=1134443
Scroll down to "For Build 1010's [+] that CANNOT use Odin One Click and coming from GB Bootloaders"