Hello everybody, I hace a Galaxy S from Movistar (Spain) and I have tried to update to Froyo from its first beta version. I always get the same error. All works fine (maket, wifi, keyboard) but the SIM card is not detected. The phone starts and no ask me for PIN code.
Yesterday I tried the new froyo and got the same error.
Now I'm working fine with JM8 and JM4 modem (and of course the SAME SIM card).
When I updated to froyo first time with the beta version, I got an operator error code. I downgraded, all work fine and after taht I free my phone.
Could anyone help me to jump to froyo?
Kind regards
I doubt the operator thingy has got something to do with reading the actual card instead of just not recognizing his network. =/
Hardware- and softwarewise, you always get you pin verification, .. unless it's broken or you're missing a phone part?
I use the SAME SIM card with JM8 and other phones without any problem
I had this problem for the first time last night when I flashed to JP6. I finally got it working again by deleating the /efs/nv_data.bin and the /efs/nv_data.bin.md5 files (making sure the sim card is not in the phone when doing it)
I think the phone recreates those files from it's backup file. I'm a total noob at this and you might want to make sure this is correct before deleting anything. Is your product code correct?
macnessie said:
I had this problem for the first time last night when I flashed to JP6. I finally got it working again by deleating the /efs/nv_data.bin and the /efs/nv_data.bin.md5 files (making sure the sim card is not in the phone when doing it)
I think the phone recreates those files from it's backup file. I'm a total noob at this and you might want to make sure this is correct before deleting anything. Is your product code correct?
Click to expand...
Click to collapse
WATCH OUT WHEN DOING THAT.. You don't want to accidentally corrupt your IMEI (and I suspect doing that may cause that)
andrewluecke said:
WATCH OUT WHEN DOING THAT.. You don't want to accidentally corrupt your IMEI (and I suspect doing that may cause that)
Click to expand...
Click to collapse
Thanks for the warning. I managed to take a copy of everything before doing it. I made the mistake of not doing this at the very begining before flashing the JP6 update and have now lost the correct CSC info for the UK, but at least I kept my IMEI
The search continues
I will try at home this night
My SIM card is not readable on a JM1, coming from a JF3... im clueless
Hi, where do I find those files so that I can delete them. I am unable to get my SIM card recognised either! im on Vodafone UK
hey guys my i9000M sd died and am getting it replaced so far i have not done anything to it.
When i get my new replacement i was wondering if i should root it and put a ROM on such as Darky's V8.0 ROM
My only worry is the SD dying again on my and am screwed. Is there anyway bell would know my phone has had the ROM on and root if the SD card itself is corrupt?
Is the boot animation changed also because i think that would be something to hint i messed with the stock ROM (specifically for darky's because it looks awesome).
Read all the positive and negative posts bugs etc before you flash any rom .
Having a non standard rom invalidates your warranty .
It will all depend upon the Techie that picks the phone up to enter a report what they look at etc . Probably test to see if SD card is faulty that may entail booting up by some means .
jje
We know that the Canadian i9000M is basically the same as the international and European i9000, as well as the i9000B (Brazil). Their firmwares are mostly compatible with one another. Yet only the Canadian i9000M has massive reports of the deadly failure AKA the dead internal SD. The exact cause of the problem is unknown. We are not 100% sure what is killing it. It's widely accepted that the root of the problem is the faulty hardware used in certain batches of the i9000M. But there have been an alarming number of failures with latest hardware. What made the i9000M hardware so different from other i9000's? Weren't they manufactured at the same facility? No other i9000's used the same batch of the hardware? Can it be mainly firmware related?" Can there be some bugs or malicious codes in the canadian firmware, which leads to the failure of the hardware? I'm really intrigued.
Is there enough statistics on this issue?
Has anyone had his i9000M flashed with a stock ROM from another region (i9000, i9000B...), and it still died?
Have you flashed it fully or partially? (sbl, modem, etc...)
The same questions for those who flashed a custom ROM that is not based on a Canadian stock ROM.
We need more inputs to solve this annoying mystery once for all. It's freaking annoying knowing that you can't rely on your phone as it could just choke and die, and there's nothing you can do to prevent it.
Sorry for my English as it is not my primary lanuage. I hope I made it clear enough.
i flashed my phone with the european froyo when it first came out via the kies reg hack, and my phone had the internal sd card error within days. i never did rooting or lag fixes or anything.
It certainly is a Hardware issue from Samsung on Bell Galaxy S Vibrants. It is recognized and exists on all models prior to 10.12 (take out your battery and you will see this number directly below the UPC code) - mine was 10.07
Bell recognizes this and that is why they are offering:
* Expedited replacement
* $100 credit
* additional 2 year warranty on all models prior to 10.12
Tekky
tekkneak said:
It certainly is a Hardware issue from Samsung on Bell Galaxy S Vibrants. It is recognized and exists on all models prior to 10.12 (take out your battery and you will see this number directly below the UPC code) - mine was 10.07
Click to expand...
Click to collapse
So that there's no confusion... there's no evidence that any recent hardware dates result in fault-free phones. While the reports of failures on say 10.11 or 10.12 phones aren't substantial, they are definitely coming in. I'm a pessimist so I'm attributing the low numbers simply to there not being many of these phones in the market yet or to the simple fact that they haven't been in use for long (e.g. I have a 10.11 phone but only received it on Jan 4).
What about those that aren't on Bell's network but picked up one of their phones? Would I have to register to a pay-as-you-go Bell plan and then be eligible for the extended two year support?
My opinion: It was the secondary bootloader in the Canadian ROMs that killed our phones. This is basically what both Samsung and Bell have said as well; that flashing JL2 will fix the problem.
Yeah, there have been reports of phones running JL2 dying, but there have been much, much less people saying this compared to firmwares such as JK4. (Might be because JL2 is so new, but I don't think so.)
Received my repplacement dec 24th (10.12) flashed like crazy, filled the sd card many times, formattted lots of times and no slowdown or issue whatsoever am not on doc v8 from kitchen
that makes absolutely no sense a bootloader cannot kill the phone it doesnt do anything except during boot.. peoples phones were dieing while running.. and there is so reason you shouldnt be able to use any i9000 firmware.. it is just bad hardware.
seeARMS said:
My opinion: It was the secondary bootloader in the Canadian ROMs that killed our phones. This is basically what both Samsung and Bell have said as well; that flashing JL2 will fix the problem.
Yeah, there have been reports of phones running JL2 dying, but there have been much, much less people saying this compared to firmwares such as JK4. (Might be because JL2 is so new, but I don't think so.)
Click to expand...
Click to collapse
When I got my second phone it had JH2 (which doesn't have a sbl.bin).
I then flash JL2 (after removing the SBL.bin from the tar file). The phone died and I'm getting a new one from Bell.
Does this mean that removing the sbl killed my phone, as it never had one to begin with?
Thanks.
i think it's a hardware issue, because this phone is dying from numerous factors - it dies on multiple firmwares both custom and official rom. it dies on lagfix phones and non lagfix phones. therefore it is clear that this i9000m is a faulty product, and the issues has to do with samsung manufacturing process of this phone. And their official rom is not efficient as well. The GPS function is non existence, while u flash a custom rom it is working okay. which is ridiculous, because pushing a product like this into the market while promoting its gps feature that doesn't even work on majority of their phones is just disappointment.
tekkneak said:
It certainly is a Hardware issue from Samsung on Bell Galaxy S Vibrants. It is recognized and exists on all models prior to 10.12 (take out your battery and you will see this number directly below the UPC code) - mine was 10.07
Bell recognizes this and that is why they are offering:
* Expedited replacement
* $100 credit
* additional 2 year warranty on all models prior to 10.12
Tekky
Click to expand...
Click to collapse
Do you have a link to the extended warranty? I can't find anything on their website or via Google.
windraker said:
When I got my second phone it had JH2 (which doesn't have a sbl.bin).
I then flash JL2 (after removing the SBL.bin from the tar file). The phone died and I'm getting a new one from Bell.
Does this mean that removing the sbl killed my phone, as it never had one to begin with?
Thanks.
Click to expand...
Click to collapse
Why did you remove the Sbl.bin? The secondary boot loader apparently fixes this issue, so if anything you should flash it instead of removing it...
It had one to begin with, it's a boot loader so it must have had one. The JL2 version is just improved, so removing it wouldn't flash anything; you'd be stuck with your JH2 SBL.
lgkahn said:
that makes absolutely no sense a bootloader cannot kill the phone it doesnt do anything except during boot.. peoples phones were dieing while running.. and there is so reason you shouldnt be able to use any i9000 firmware.. it is just bad hardware.
Click to expand...
Click to collapse
The hardware is nearly identical to the i9000. I don't think it's a hardware issue.
Let's just wait the amount of phones dying (that run JL2) to match those dying that ran JK4. Then we can conclude the SBL didn't fix it.
seeARMS said:
Why did you remove the Sbl.bin? The secondary boot loader apparently fixes this issue, so if anything you should flash it instead of removing it...
It had one to begin with, it's a boot loader so it must have had one. The JL2 version is just improved, so removing it wouldn't flash anything; you'd be stuck with your JH2 SBL.
Click to expand...
Click to collapse
I removed it because on the phone before that after updating to JL2 I couldn't flash JH2 anymore because JH2 didn't have the bootloader. I asked some devs here and they said it would be ok to remove the SBL.BIN as it locks the phone somewhat, especially that post about the galaxy tab getting new boot/sbl files.
I want to be able to go back to a previous rom, and not have to fiddle around moving bootloaders between tar files.
I was planing on removing the sbl/boot from all future roms as well, so they don't do a checksum on the firmware
windraker said:
I removed it because on the phone before that after updating to JL2 I couldn't flash JH2 anymore because JH2 didn't have the bootloader. I asked some devs here and they said it would be ok to remove the SBL.BIN as it locks the phone somewhat, especially that post about the galaxy tab getting new boot/sbl files.
Click to expand...
Click to collapse
To get back to a previous ROM, just flash a previous ROM that contains a secondary boot loader, then you're able to flash anything. It locks the phone to some extent - until you just flash a different SBL.
seeARMS said:
To get back to a previous ROM, just flash a previous ROM that contains a secondary boot loader, then you're able to flash anything. It locks the phone to some extent - until you just flash a different SBL.
Click to expand...
Click to collapse
Not all roms have a secondary bootloader, even JS3/JPY didn't come with it, so I'm not sure why bells does
windraker said:
Not all roms have a secondary bootloader, even JS3/JPY didn't come with it, so I'm not sure why bells does
Click to expand...
Click to collapse
There isn't much known about it, but it'd make sense if the SBL of the older Bell firmwares killed the phone, so that's why Bell included an SBL in the newest JL2 firmware... There isn't a reason to actually install a SBL, so why else include one? To fix something.
seeARMS said:
My opinion: It was the secondary bootloader in the Canadian ROMs that killed our phones. This is basically what both Samsung and Bell have said as well; that flashing JL2 will fix the problem.
Yeah, there have been reports of phones running JL2 dying, but there have been much, much less people saying this compared to firmwares such as JK4. (Might be because JL2 is so new, but I don't think so.)
Click to expand...
Click to collapse
This is what I believe as well , I am on my second SGS now it's a 10.12 phone had it since Dec 23rd came with JH2 I installed JL2 on the 24th and then from there went to a custom rom/kernel that same night been flashed it 20+ times so far with no issues. First phone a 10.8 died within 2 weeks of flashing custom roms.
From my understanding the first batch of Bell i9000M's some of them were stuck without 3BR (3 button Recovery) due to a .SBL problem so they released a new .sbl with JH2?? to fix the issue so users could get a working 3BR. I believe they did not test it long enough and there was still an issue between the .SBL and the primary boot loader witch was some how killing internal SD cards this is why even some users phones died on JH2 as well. This is just my guess really as I'm no tech expert but just follow a lot of threads here on XDA about the I9000M. From what I can see there has been a huge decrease in dead internal SD's since the release of JL2 , I think it was about a week after it was released I read about the first one that died on it vs JK4 where there was 5+ people within the first day a few within the first few hours of it's release.
For those of you saying Bell/Samsung admitted a hardware problem I do not believe they did , Samsung blamed it on software and pulled JK4 from Kies if they honestly thought it was hardware they would of never removed JK4 from Kies.
Samdroid_G_S said:
This is what I believe as well , I have a 10.12 phone had it since Dec 23rd came with JH2 I installed JL2 on the 24th and then from there went to a custom rom/kernel that same night been flashed it 20+ times so far with no issues.
From my understanding the first batch of Bell i9000M's some of them were stuck without 3BR (3 button Recovery) due to a .SBL problem so they released a new .sbl with JH2?? to fix the issue so users could get a working 3BR. I believe they did not test it long enough and there was still an issue between the .SBL and the primary boot loader witch was some how killing internal SD cards this is why even some users phones died on JH2 as well. This is just my guess really as I'm no tech expert but just follow a lot of threads here on XDA about the I9000M. From what I can see there has been a huge decrease in dead internal SD's since the release of JL2 , I think it was about a week after it was released I read about the first one that died on it vs JK4 where there was 5+ people within the first day a few within the first few hours of it's release.
For those of you saying Bell/Samsung admitted a hardware problem I do not believe they did , Samsung blamed it on software and pulled JK4 from Kies if they honestly thought it was hardware they would of never removed JK4 from Kies.
Click to expand...
Click to collapse
Good post; exactly what I think. Samsung has indeed blamed it on software, not hardware: http://www.facebook.com/topic.php?uid=260085296049&topic=15210
seeARMS said:
My opinion: It was the secondary bootloader in the Canadian ROMs that killed our phones. This is basically what both Samsung and Bell have said as well; that flashing JL2 will fix the problem.
Yeah, there have been reports of phones running JL2 dying, but there have been much, much less people saying this compared to firmwares such as JK4. (Might be because JL2 is so new, but I don't think so.)
Click to expand...
Click to collapse
Thanks for your suggestion.
So flashing JL2 SBL is our best bet to prevent our phone from dying as we are running out of options...
Just use Odin to flash the phone with stock JL2 ROM? (with Phone Bootloader Update checked)
Will flashing another kernel (eg, Speedmod) overwrites the SBL, making the phone vulnerable again?
*Found the answers after more readings. Thanks.
kronomike said:
Thanks for your suggestion.
So flashing JL2 SBL is our best bet to prevent our phone from dying as we are running out of options...
Just use Odin to flash the phone with stock JL2 ROM? (with Phone Bootloader Update checked)
Will flashing another kernel (eg, Speedmod) overwrites the SBL, making the phone vulnerable again?
Click to expand...
Click to collapse
Correct me if im wrong but flashing a kernel does not override the SBL.