HI All,
I have waited and waited and............. waited for a standard Froyo Australian Optus ROM, I had not even thought about rooting the phone it was as standard as can be.
The ROM had finally come but I did my upgrade and the phone couldn't see the SIM. So I called Optus who passed me to Samsung who referred me to 2 different "service" centers hoping this was a standard issue with a standard fix. How foolishly trusting was I. so after getting off many phone calls it came to "send it in we will look at it". So I started my own research and ............... nothing (more than happy if someone knows where there is an answer and I just missed it)
So after this fail I was over it and so I loaded the DOC v9 JPO ROM rooting and all. Even after this the phone could still not see the SIM. =( I found the stock standard ROM loaded it and yes the SIM was fine so I tried once again the Optus release, FAIL, and then DOCs, FAIL. so I am back at the stock standard ROM and hoping not to have to send it away.
PLEASE HELP
Related
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.
Hi everyone,
I recently (3 weeks or so) bought a Rogers Captivate (Canada) and flashed the cognition froyo rom b6 onto it. everything was great. however, As I was traveling to India soon - i wanted to unlock it. So, I flashed the 2.1 AT&T rom, and did the nv_data.bin process where it doesn't ask for a unlock code anymore. I tried my bell canada sim card and it seemed to work fine. The network lock for OFF too.
Now, when I came to India and put an indian sim card (bsnl), it says (phone not allowed MM#6) and the IMEI is 'unknown'. I flashed 2.1 AT&T again and I got network but as soon as I switched the sim card, same problem. No network, with a phone not allowed error. I tried the Axura rom and same problem. Now, I am back to AT&T 2.1 and can't for the life of me, get a sim card to work!!!!!
I NEED to fix this, as I am traveling across india for 3-4 months and not having a phone, is a major problem!!!!!
please help.
I have access to a mac/PC and odin.
Maybe becouse you have flash att rom into it. And is rogers one, did you do a nandroid backup or anything of that sort before you loaded it with att or did anything?
rogers
I did have a Nandroid backup but that didn't help at all.
I have done the one-click downloader, flashed to stock JF6, Master clear, and still not luck
any suggestions?
bump...............................
Lot of info on Google but not much answers on how to make it work.
Basically the indian provider is locking out North American devices based on the imei. Buy a disposable phone.
Okay, I installed Darky's ROM 6.0 and its absolutely amazing, but I wanted my normal T-Mobile UK firmware back on my i9000 (the firmware I got my i9000 with) and I had updated to i9000XXJP3 using Kies on my T-Mobile UK i9000 from 2.1 and it had worked quite well. I wanted that firmware back so I downloaded it and flashed it using Odin, however nothing is working properly (very slow even after factory reset), it connects to Kies but when I go to firmware upgrade on Kies my phone does not show up and last of all it is not T-Mobile UK branded like it was when it came with the phone.
Please I do not want any more rubbish (Darky's ROM 6.0 is not rubbish for the record it is amazing), I would just like the T-Mobile UK firmware that came with my phone the first day I opened it and everything to be like on that firmware. I don't care if it is 2.1 (2.1 came with my phone) I just want that particular, branded, locked firmware back.
Please help.
no one knows what to do? no one can help?
Hi ,
My girlfriend has had her galaxy s for about 4 months i recently flashed darkys rom onto it, with no problems (excellent rom btw), but now the phone has started doing menu and back on its own randomly making it impossible to do anything on it for longer than a few minutes , its like the soft keys are being pressed (but they arent of course).
I've had a google and came to the conclusion its a hardware fault and not software (ive tried factory reset / re-flashing roms/ kernels) but now i have the problem i cant send the phone back to tmobile with a custom firmware so is there anywhere i can download tmobile firmware and stock kernel to make it like when she got it ?
Any help or advice would be greatly appreciated.
In the General chat, there is a link to all the stock roms. Select the one you want and install that one. I am on t mobile in the uk and my code is TMU so that will most likely be fine for you.
By the way - Its exactly what I did last month and they fixed it fine for me with no questions...
CtC
hi thanks for the quick response , ive already installed a stock firmware but when the phone boots up it doesnt do the tmobile logo now, plus the firmware i have installed, i'm not sure if thats ever been available on tmobile , which firmware did you send your phone back to them with if you dont mind me asking ?
Hi,
I used the JP1 stock rom here. I remember now that once I installed the stock one I used the Kies registry hack to put the latest t-mobile firmware on there. Then it was branded T-Mobile again. The only problem is that now kies has been updated the Registry hack may not work.
If I were to send you a nandroid backup of my original T-Mobile rom (I did that when I got a new one!) Would that help?
CtC
I would blame the rom before the hardware and want a wipe to a very clean phone and install a stock rom .
You cannot download TMobile firmware you need somebody to give it to you unless you backed up your original firmware .
The only way to get TMobiles firmware would be to downgrade your phone to stock Eclair then use Kies to update as normal to Froyo branded TMobile or if that failed use the registry patch .
Fix on a non stock rom is going to depend on the guy that picks the phone up and the problem .
jje
"If I were to send you a nandroid backup of my original T-Mobile rom (I did that when I got a new one!) Would that help? "
It would be brilliant if you could do that, how can you send it though ?
@ jjegan i have completely wiped the phone, changed the firmware to 2.1update1 same problem still exists with the soft keys randomly pressing themselves thanks anyway .
can any one give me some advice about making this phone look as stock uk tmobile as possible before i send it back ?
I tried to use ROM manager to update my rom to overstock, this did not work so well. It installed fine but then the battery refused to charge and all sorts of wierd problems so I used my backup to uninstall and that failed. I downloaded Odin3 v1.7 and downloaded the original stock firmware(eclair) and that failed. I then used UGJH2 and the phone will boot and see the galaxy s load but then the screen goes blank and vibrates periodically. in the recovery (3e) it says Can't mount /dev/block/st110. The last official firmware install was KC1 through kies but I can't find that anywhere is there any hope for this(sweating cause wife might find out)
I am also on sasktel and am an impulsive flasher (1-5 times daily) Heres an easy, fast fix. GO here:
http://www.darkyrom.com/community/index.php?threads/guide-installing-rc5-easy.2382/
go to section enabled "For GT-I9000 users only" and follow step by step. You can stop at step 2 if you want to leave your rom stock samsung or do last few steps to have darkys on there. EIther way once done you'll also have to enable the 850 band *#2263# then enable wcdma 850 option. Also you will have to manually enter your APN under network options. I use inet.stm.sk.ca for sasktel. Note that the Ficeto_JVB.zip download there includes all needed to flash (.pit file, rom, odin). THis is always my fail safe method after boot loops ( I always screw something up playing around lol).
ps: also depending how desperate you are and how trusting you are, I work at sasktels head office in the cornwall and if you wish I am sure I could take 15 mins out of my day tomorrow to do this for you, although you will not be able to get through security so you will have to trust me taking off with your phone lol. email me at [email protected] if needed.
trouble is I can't put things on SD card because I can't get it to load android
You won't be able to load eclair through Odin because JL2 installed a new SBL (secondary boot loader). Go to samfirmware.com, download JL2, and use odin to flash that. Once that's flashed it should fix your issues. Then, if you want a custom ROM, try the romkitchen (romkitchen.org).
problem solved!! turns out darkyrom did fix my phone, I couldn't push the zip file to my phone but their tar file got my phone working! Thanks for all the help
Dougustine said:
I tried to use ROM manager to update my rom to overstock, this did not work so well. It installed fine but then the battery refused to charge and all sorts of wierd problems so I used my backup to uninstall and that failed. I downloaded Odin3 v1.7 and downloaded the original stock firmware(eclair) and that failed. I then used UGJH2 and the phone will boot and see the galaxy s load but then the screen goes blank and vibrates periodically. in the recovery (3e) it says Can't mount /dev/block/st110. The last official firmware install was KC1 through kies but I can't find that anywhere is there any hope for this(sweating cause wife might find out)
Click to expand...
Click to collapse
I loled, I've been in the same boat, wife is always asking me why I always have to mess around with stuff. Shoulda seen her face after I soft bricked the phone the first time.
Just rooted my phone
I am new to this, I can do all kinda of things with my pc but with my phone a different story lol. I don't understand when you say "Eclair". Is that a different model or is that stock. I am too from sasktel.
Android 2.1 is Eclaire, 2.2 is Froyo and 2.3 is Gingerbread... Ice cream is next 4.0
hi guys, I know this is an old post but has anyone successfully unlocked their Sasktel i9000 vibrant without paying any unlock code service? has anyone tried anything like the SGS Unlock Pro that claimed to unlock all GSM galaxy S phones but did not list Sasktel? anyways, from the sound of it is Darky's rom currently the best for i9000's? I wanted to try CM9, so i did the super 1 click root and followed the CM wiki page to push clockwork recovery to the phone through Heimdall Suite but both times i tried failed and stuck in a boot loop so both times i ended up going through Odin to fix it. (super 1 click root didnt seem to stick b/c i lost superuser after fixing the phone w/ Odin, is that normal?)
anyways i had a very unique situation, originally had a Bell i9000m but died 1 week later tried to fix it numerous times for 7-8 months ( i live in U.S., and Sammy refuse to fix it b/c i dont have a canadian address they can send it back to b.s.) anyways finally landed myself a dead i9000m w/ broken screen, so i took both apart and put the working parts together. now 1 working phone with 3 problems: 1) so it seems that it's currently locked to Sasktel (it can be done but i'm curious if there is a cheaper way or even free) 2) CM wiki suggested Heimdall push CW recovery cause boot loop (some on xda suggested flashing the phone back to 2.2 (or 2.1??) first) 3) i was playing around and click on screen update and lose my touch keys ever since (ppl also suggest flashing it back to 2.1 and reupdate the keys, but will a bell i9000m 2.1 stock rom be compatible w/ the i9000m from Sasktel?)
anyways lots of questions there but if anyone can answer anyone of these would be greatly appreciated.
thanks in advance
Update: problem 1 is taken cared of. SGS Unlock Pro worked like a charm. tested, working. other 2 problem still unsolved.