[Q] Bell Canada Samsung Galaxy S Won't Boot OS - Galaxy S I9000 Q&A, Help & Troubleshooting

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

Related

[Q] Can't boot - E:Can't mount /dev/block/stl10

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.

Phone stuck in boot loop

Hi, I've been using Darky's Rom for over a week now and everything was fine. I woke up this morning, and my phone was off. I found this strange because it was left on the night before, and it was completely unresponsive. I pulled the battery and attempted to boot it, but it keeps flashing the GT-i9000M logo and rebooting. I have Download mode working, which is good and I've tried flashing the stock firmware back, and it's not working. I've tried the repartition option with both the 512mb .pit file and the one that came with odin, nothing's working. Anyone have any tips?
Call samsung its toast. Check out some of the i9000m posts in the general forum.
Sent from my GT-I9000M using XDA App
Dang. Is there any chance Bell will be able to replace it for me? I'm guessing my issue is the corrupt internal microsd. Also, since I was a running a custom rom would it be a good idea to flash the bell FroYo through Download Mode before taking it in? Thanks for the response. Also, should I mention to them that I upgraded to FroYo?
As it is you have no warranty as you messed with the firmware so yes be on the safe side and flash to stock bell firmware . You can always act ignorant and say it went bad after the Froyo update .
jje
JJEgan said:
As it is you have no warranty as you messed with the firmware so yes be on the safe side and flash to stock bell firmware . You can always act ignorant and say it went bad after the Froyo update .
jje
Click to expand...
Click to collapse
Alright, that's what I'll do. Thanks for the advice.
As bad as I feel about lying, it's a physical problem with the device and I feel that I deserve a replacement. I didn't really have second thoughts about installing a custom ROM because the Galaxy S is virtually unbrickable thanks to download mode.
edit: Does anyone know where I can find the jk4 froyo that's bricking our phones?
Found it! http://forum.xda-developers.com/showthread.php?t=867309

[Q] Galaxy S software screwed up. How to restore the stock?

Hello,
i've got a serious problem with my galaxy S.
Recently i updated my software of my SGS to 2.2.1 with kies. I was happy for a little while but then i saw darky's rom and i wanted also the Gingerbread look on my phone. I rooted my 2.2.1 using Odin and i installed Clockwork recovery Mod or something like it. After that i flashed Darky's rom on my phone.
It all worked perfectly. But then Yesterday suddenly when i tried to call home my phone wasnt working like it should. And it wouldnt call anybody.
So at home i searched up a stock firmware from samfirmware .com And i flashed it.
Now my phone is all **** because the software force closes and kies doenst work any more. I think i may should have first deinstalled Clockwork mod and unroot?
The only thing i want is to get back to 2.2 or 2.1 Im running vodafone and im from holland don't know if that makes a difference?
Anyways i really hope someone on this forum can help me please.
I just need the stock firmware and everything else like CWM and root of my phone although i cant see superusers anymore in my menu so i think its off?
first of all boot into recovery. do a factory reset/ wipe the cache and also try to format the internal sd card.
secondly boot into download mode and try to flash your stock rom again, do not use re-partition or pit unless you have 3 files (pda, modem, csc), if that completes, let me know what happens after the flash... or PM me if you want to.
Just to add, if you have these problems, you should flash with repartition to make sure that everything will be fixed, but as azzledazzle said, you need all the 3 files to do that.
you knw what a problem is i think ..that i'm not sure im using the right rom to flash with? could you maybe tell me what file i need to flash with? what is the stock for my phone and how can i see it?
http://forum.xda-developers.com/showthread.php?t=846913 this has all the stock firmwares you need. im not sure which ones come in 3 files. ideally you will be wanting one that also has dbdata... if you cant find it i would suggest flashing darkyys new 9.2
you can flash that thru odin, you can use 512 pit even tho it only has 1 pda file. and it also contains dbdata which will restore the old one incase of corruption or deletion (happened to me yesterday)
when i try to format the sd it says .
E:can't mound /dev/block/mmcblk0p1
(device or resource busy)
E:copy_dbdata_media: can't mount SDCARD:
do i need to do anything about this? is it bad?
i would try and flash a rom with dbdata if that doesnt work you could try this http://forum.xda-developers.com/showthread.php?t=905975 or this http://forum.xda-developers.com/showthread.php?t=563298
if that doesnt work i think it may need to go back to samsung i suspect it could be a corrupt sd card... (but i may be wrong)
yes yes YESSS i think it worked really thanks man for the fast help etc. now it boots i flashed it and there are no weird apps or force closes...Only one question left if i want to just root 2.2.1 is there an easy app for it? or do u have a file to just root stock with odin?
airdude13 said:
Hello,
i've got a serious problem with my galaxy S.
Recently i updated my software of my SGS to 2.2.1 with kies. I was happy for a little while but then i saw darky's rom and i wanted also the Gingerbread look on my phone. I rooted my 2.2.1 using Odin and i installed Clockwork recovery Mod or something like it. After that i flashed Darky's rom on my phone.
It all worked perfectly. But then Yesterday suddenly when i tried to call home my phone wasnt working like it should. And it wouldnt call anybody.
So at home i searched up a stock firmware from samfirmware .com And i flashed it.
Now my phone is all **** because the software force closes and kies doenst work any more. I think i may should have first deinstalled Clockwork mod and unroot?
The only thing i want is to get back to 2.2 or 2.1 Im running vodafone and im from holland don't know if that makes a difference?
Anyways i really hope someone on this forum can help me please.
I just need the stock firmware and everything else like CWM and root of my phone although i cant see superusers anymore in my menu so i think its off?
Click to expand...
Click to collapse
It's funny.. I did the exact same thing yesterday, and the same result happened to me. Now I'm dealing with how to unbrick my phone.
easiest way is to flash speedmod kernel thru odin, that gives you root and lagfix (if desired) also some extra tweaks to speed up the phone.
PS: Dont forget the thanks button ---------------------------------------------->>>>>
well maybe this can be some use to u it worked for me i guess only prob is i cannot connect to kies but that's just finding the right firmware
damn man it still is not the right firmware how can i see what firmware i need? the one i got now kies still says it cant update
damn man i still dont have the right firmware how can i see what firmware i need for my phone? its a dutch vodafone branded phone i want 2.2
http://forum.xda-developers.com/showthread.php?t=846913
select the firmware you want from there. dont listen to what kies tells you.

[q] need serious help. Phone bricked :(

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!

GT-P1000 Stock Rom SammMobile won''t flash only Overcome

Hello all, got a GT-P1000 Galaxy Tab1, it was previously ruined, and wouldn't boot anything but download mode, and wwhen charging the symbol would come up but never change.
So i decided to Reflash the FW with stock and that flashed fine the first time. But i was stuck on the samsung logo boot loop. As in Samsung logo would stay for 2 minutes, then disappear and reappear to do the exact same.
So i followed the overcome method - of flashing the SafeStockv5 Modem, and PIT. This booted straight into the OS of 2,3.3 and is booting fine.
My problem is that it starts up in italian, so need to select english, and there are a few Italian APPS, that can't be removed.
Anyone got any ideas on what FW i can flash to the tablet? If i try and do the 'stock' FW it hangs in oding on Hidden.rfs and won't budge. So forces me to reflash with Overcomes stock.
It's supposedly a UK Unbranded Galaxy Tab 1.
Any other info needed please ask.
Overcome gb stock safe v5 is Italian ROM. But it comes up only in English for me.
There are no Italian apps in there either.
Can you re flash it again?
Sent from my GT-N7100 using XDA Free mobile app
Hazeno said:
So i followed the overcome method - of flashing the SafeStockv5 Modem, and PIT. This booted straight into the OS of 2,3.3 and is booting fine
Click to expand...
Click to collapse
I have a P1000 that my daughter left out in the rain overnight. After stripping it down and drowning it in iso-pro alcohol I was able to get it to start and get to the download screen.
I've followed the Overcome method of restocking it (no errors) but also cannot get past the Samsung logo. Can you tell me where you got the files from that you used to restock please? I'm using the ones I've used previously but there must be some subtle difference because it refuses to start.
Could this be anything to do with the fact that I did manage to upgrade this thing to CM11 (before the rain incident), can I no longer downgrade to GB? I shouldn't need to revert to a different stage should I? Is far as I remember I've done this before all the way to GB then up to CM11, but I can't be certain.
Any thoughts on what to try next - be a shame to throw the thing out when it is so close to working again.

Categories

Resources