Database Develop

Rogers Dream questions

I realize there are numerous threads about the phone, but I have several questions and I don't think they fit into any single thread. Merge this if necessary.
First of all, the phone in question ran on Dwang's rom using EBI0 root hack. After the 911 bug thing with Rogers, they disabled the internet and the phone did not have data and sms. I found out about Cyanogen's radio update trick and proceeded to try it. I flashed the latest Cyanogen rom first, then did the radio update with the EBI1 kernel patch. The phone boot up normally.
Several days later (haven't used the phone), I realized another problem. Data and sms came back, but now I can't call or receive. Has anyone any idea about this problem?
[edit] Realized it is a temporary issue (one of many) with Rogers as other people I know can't call either.
I also pulled the battery out for some reason and noticed it was bloated/fatter/expanded/etc. Went to Rogers store and they were going to replace whole phone instead of just the battery. They're probably doing that to ensure I get a phone with the unrootable update.
Question is: Will Rogers realize if I send the new phone back with the old battery?

yingjai said:
Question is: Will Rogers realize if I send the new phone back with the old battery?
Click to expand...
Click to collapse
Yes due to IMEI, but if they ask just say you didnt need the phone.

[Q] SIM - What role, if any, does it play...

Does anyone have any information or insight in to what role, if any, the SIM might play in preventing restoral to 100% stock. The question, of course, assumes the SIM is left in when mod the phone with another ROM, kernal, etc.

over at the i9000 forum they say when flashing or restoring if you dont remove the sim it will lock the phone.

tjsooley said:
over at the i9000 forum they say when flashing or restoring if you dont remove the sim it will lock the phone.
Click to expand...
Click to collapse
I did have that happen to me on my first try of an I9000 Froyo ROM (forgot to take it out). Since then, I've done a lot of flashing and not had that happen again (left it in cause the directions for the ROM's I was flashing said nothing about taking the SIM out).

gps, usb, ota problems

Hi all,
I've purchased a samsung captivate from United States and bring it to italy where I'm using with Wind operator.
I'm starting thinking that it was the worst purchase that i've never made.
First of all, I've unlocked at&t sim restriction and it was the only think went fine.
In italy I had time to test the phone and I've noticed the full unworking gps feature: position was never catched and just 1 or 2 satellites was found with low signal.
I'm trying to use samsung kies to upgrade the firmware before install a custom rom but samsung kies doesn't found the phone! (on win 7 or xp the fault is the same.. Mtp driver not installed correctly or kies says that phone is not supported!)
Moreover, updates by OTA don't work because the updated tool fails to connect to at&t server!
I'm really sick for all of that.. The last think I can do is to root the phone and install a custom ROM but I'm afraid that gps still doesn't work.
What do you think about this?
​

You don't need to update to install a custom rom. So I wouldn't stress too much about it. Make sure you back up the folder which contains the unlock information!! I made that mistake.
Many roms out there try to fix gps issues. For now, many of us (including me) have awful gps capabilities.
Edit, I should say that many roms vastly improve the GPS, so after you've read up on flashing and want to give it a try, it's probably your best bet.
Sent from Captivate, sorry for the brevity.

I don't know if your experience with the original firmware is the same that i have but my gps is not working at all. I can't understand how they can sell a phone with this buggy behaviour.
However, if it does not work also with the new firmware may I flash back original firmware for at&t / samsung assistance? I don't think so but maybe you are more informed than me.

Have you tried installing the gpsjm9 files with clockwork? Makes even stock gps better.
Sent from a phone somewhere in the universe

cappysw10 said:
Have you tried installing the gpsjm9 files with clockwork? Makes even stock gps better.
Sent from a phone somewhere in the universe
Click to expand...
Click to collapse
i see its from/for an i9000. will it be fine with the captivate?

chasesavestheday said:
i see its from/for an i9000. will it be fine with the captivate?
Click to expand...
Click to collapse
yes...and you can flash from stock to a custom.
you can flash back to stock via odin 1-click.
my best gps performance (build 1007)
have been with
Doc's, Chronus, and Assonance.

[Q] [i9000M] What really killed our phones? Faulty hardware or Canadian stock ROM's?

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.

Note re-locked again??!!

Hi, folks...
After a long time, I have a problem with my Note...
Many, many weeks ago I rooted and unlocked my Note, and all was going well... It is just in the recent day, or two that I noticed that suddenly I don't have access to SMS service, calls, or Internet... I thought it was provider's fault, but after inserting other network's SIM card I got the same problem...
I think I might have re-locked itself somehow... I tried again using Galaxy S unlock method, but it changes nothing... is it possible that the phone unrooted itself, or that some update (no ICS, I am not touching that yet! ) messed up something?
Awaiting for your helpful response...

cmick30 said:
Hi, folks...
After a long time, I have a problem with my Note...
Many, many weeks ago I rooted and unlocked my Note, and all was going well... It is just in the recent day, or two that I noticed that suddenly I don't have access to SMS service, calls, or Internet... I thought it was provider's fault, but after inserting other network's SIM card I got the same problem...
I think I might have re-locked itself somehow... I tried again using Galaxy S unlock method, but it changes nothing... is it possible that the phone unrooted itself, or that some update (no ICS, I am not touching that yet! ) messed up something?
Awaiting for your helpful response...
Click to expand...
Click to collapse
Unlocked means? Unlocked from what? Service provider?
Sent from my GT-N7000 using XDA Premium App

I don't think it may have auto locked.
You are on GB ROM then try
-Factory reset
still dont work, then
-Reflash ROM
This shud work, if still doesn't work then reason to believe it has been locked.

Is your IMEI still showing correctly?
Sent from my GT-N7000 using xda app-developers app

Locked, as in SIM locked.
Will try factory reset in the evening (London) and see what happens...
What do you mean if my IMEI is still showing correctly? How should I know what is wrongly showing of IMEI?

He mean you can see IMEI as digit or just written 'unknown'

dr.ketan said:
He mean you can see IMEI as digit or just written 'unknown'
Click to expand...
Click to collapse
yeah, full number is there, no anomalies of any kind in that regard....
thanks...

I am having the same problem or at least similar. The phone was running fine on both paranoid android and chracks rom. I flashed Crash v7 yesterday, still fine. I decided to go back to Chrack since there was an update. When I did that, safely, the first pop-up I got was "enter network unlock code key" message. I tried the galaxy_s unlock, didn't work. The only backup that I had left was the Crashv7 so I restored that. I got the same message now but galaxy_s unlock DOES work on it. Though, I never had to use it before. I have been at this trying to figure it out for over 8 hours. I believe it has something to do with the new roms and the CSC regions. I have been searching the forums all night and now today I see more people experiencing problems.
I would like to ask a few question here,
Why do we need to change the CSC regions? Other than Kies updating, what difference does it make? I have not found the answer anywhere. I am in the US and have never had to deal with this b.s. before. Web searches I have seen seem to all refer these to Samsung phones. Are they the only company that does this?
My N7000 is from Sweden, NEE(XEE) csc. The rom that is working for me now has a csc of: EUR. I was under the impression that with custom roms it didn't matter what the csc but now I am starting to doubt that.
Any true help out there? Anyone in the states or anywhere else suffering from the same problem? I just think it strange that the phone would re-lock itself but only stay locked on newer roms(any after July 25th) and the unlock app only works on the older roms. :shrug:
Sorry for this long post.
Edit: When the sim unlock app doesn't work, imei says "unknown"
Edit 2: Looking at other threads it looks like this isn't isolated. I guess there is a problem with the new lrk or whatever it is. It's re-locking units and galaxy_s unlock isn't working.

Yeah, I would also say that some time around middle of this week, this issue became apparent to me... I really didn't use the Note much for the last two weeks, so when I wanted to send an SMS, I thought it was the network playing up (2, or 3 times a year it has problems with service, which is ok with me, since they give a great deal for £10, and I don't need a non-stop connectivity...
I am knackered after today's ride, so I will try and deal with the issue tomorrow...

Oh... I did factory restore and rooting and flashing and the whole procedure of installing busybox and galaxy s unlock app and doing everything I remember doing the first time I unlocked my Note, but unfortunately it keeps saying "Network not available."
Has anybody got any idea why some Note re-SIMlock themselves, even though this method of SIM unlock is supposed to be permanent...
What should I do now? Install other stokk GB firmware, or risk it with some custom ROMs?
I am so sad...

cmick30 said:
Oh... I did factory restore and rooting and flashing and the whole procedure of installing busybox and galaxy s unlock app and doing everything I remember doing the first time I unlocked my Note, but unfortunately it keeps saying "Network not available."
Has anybody got any idea why some Note re-SIMlock themselves, even though this method of SIM unlock is supposed to be permanent...
What should I do now? Install other stokk GB firmware, or risk it with some custom ROMs?
I am so sad...
Click to expand...
Click to collapse
I have found that any custom rom built on the LRI/LRK radios do not work for us users with sim-relock. Best to stay on older roms that aren't built from those sources. Sucks, I know. :crying:

cmick30 said:
Oh... I did factory restore and rooting and flashing and the whole procedure of installing busybox and galaxy s unlock app and doing everything I remember doing the first time I unlocked my Note, but unfortunately it keeps saying "Network not available."
Has anybody got any idea why some Note re-SIMlock themselves, even though this method of SIM unlock is supposed to be permanent...
What should I do now? Install other stokk GB firmware, or risk it with some custom ROMs?
I am so sad...
Click to expand...
Click to collapse
Reflashing a GB ROM WORTH A SHOT.
Sent from my GT-N7000 using xda app-developers app

AND WHAT DO YOU KNOW.....
A week and a bit back I had this sim lock problem with the Note, tried stuff in this thread, nothing worked, just fo find it today, when I picked it up to go and try flashing God knows what I'd pick, and turn it on, and IT IS UNLOCKED!!!
I was like a small pig when you give it some corn...
Phew, that is a stone off my heart...
But, how? Is it possible that maybe some Kies update, or some other app update brought about the re-locking of the NOTE?
Still, what made it work now, after so much time and failures?