[Q] Q: Telstra ROM screen timeout will not come back on - Galaxy Tab Q&A, Help & Troubleshooting

I have a pre-release Galaxy Tab with slightly different hardware (no camera button). I have flashed the stock Telstra ROM and all works fine....EXCEPT...
Whenever the screen times out, or I manually press the power button to turn off the screen...it will not turn back on!
I always have to reboot.
I have tried re-flashing, and also flashed a different ROM then back to Telstra but it does not seem to matter.
Any ideas?
NOTE: I am VERY new to this flashing business so don’t get too technical on me.

As far as I know my galaxy tabs DON'T have camera buttons so I don't know of what tab you have...
If it was a Telstra tab, p1000t ( written on the back near the base) then it runs at 850mHz, if it was a tab from elsewhere then its probably a p1000 and runs at 900mHz.
If you flashed a straight Telstra rom where the modem.bin file hasn't been changed with one compatible to your radio this may cause problems but I wouldn't think it would stuff up the screen...
You need to clarify what have you done, is the tab rooted, is it a custom rotohammer copy of a Telstra rom, what type of tab you actually have... Then we might be able to help....

Ahhh, cool. Sorry for the confusion.
This is a GT-P1000
I am pretty sure it runs on 850 as it was a Telstra device.
It is NOT rooted and did not have anything else done to it. When I got it, it had a very vanilla Android build (didn't even have Gmail). Using ODIN 1.7 I flashed several different ROMs until I found one that worked.
I used gt-p1000_mr.pit
And then the Telstra moddem.bin and TelstraP1000TDVJJ3.tar ROM that I saw posted on this site. They all work except for this on/off issue
I only managed to get one other ROM to work (JHA.tar) but it keeps giving me the "Kernel Panic" error so is not stable. I have tried following the Overcome instructions but they do not work for this either.
Do I need to do something else on this machine to get the Telstra ROM working? Any ideas why it dies every time the screen times out?
Thanks

Related

SOLVED - Sasktel (bell) phone running Darky's ROM

Ok so I'm running Darky's 7.5 ROM just loaded it and it's flying . i'm having issues connecting to my carrier. I"m from canada and run on a network owned by Sasktel. We get our phones from Bell and our current release is JL2 I think. I was running this ROM fine but wanted to see what all the hype was about .
Now the only problem i'm having is I can't register on my network and thus my phone isn't working as a phone, lol. can someone help me set it up. here are the frequencies we run on.
SaskTel
GSM - N/A
UMTS/HSPA - 850/1900
I went into the APN and set that up so I should have data I just need to get registered. I can see the network Sasktel but it wont let me register. I get the exact message when clicking on it
"Registering on Sasktel......You SIM card does not allow a connection on this network"
any help would be great, thanks
I tried going in here *#2263# but didn't know what to pick so I left it to automatic
I don't know.
When you flash back to official firmware, everything works fine again ?
This may sound funny but try 'sim unlock' your phone.
after flashing, your phone might have reverted back it's original lock which is to BELL.
I agree with the other reply stating for you to have your phone unlocked.
xxgg said:
I don't know.
When you flash back to official firmware, everything works fine again ?
This may sound funny but try 'sim unlock' your phone.
Click to expand...
Click to collapse
I unlocked my phone a while back and it's unlocked still, Network lock = off. and yes flashing to other roms specifically for my phone will work fine on the network. Is this because Darky's ROM is based on a European ROM JPY and i'm supposed to be running a Canadian ROM JL2?
Hi. I have a SGS straight from Sasktel here in SK. I checked my setting under 2263, and it is automatic (top one). After I checked it, it lost cellular connection for about a minute, then eventually came back (phew!).
adamge said:
Hi. I have a SGS straight from Sasktel here in SK. I checked my setting under 2263, and it is automatic (top one). After I checked it, it lost cellular connection for about a minute, then eventually came back (phew!).
Click to expand...
Click to collapse
awesome what happens when you go back into 2263 and click on the wcdma band, which ones are stared in there?I have 2100, 1900 and 900 starred but 850 is not.....Also could you post your APN settings. those are in settings, wireless network, mobile networks, access point names and then click on the inet.stm.sk.ca one and if it's not too much for you could you post them up here along with the wcdma band settings. Thanks bud
can we actually install darkys rom on BELL vibranat i9000M
i would like to find out if darkys Rom works with Bell vibrant thats i9000M from canada ?
well his rom is up and running fine yes, I just have to get the right setting to run on my carrier....I own a i9000m it's a bell phone that my carrier gets supply from. So yes his rom works great on this phone, it's so fast, I might try flashing a modem for the canadian phones and see if that works i'll post back
SOLVED - Sasktel (Bell) running Darky's ROM
So I figured it out, I was running JL2 and then flashed speedmod kernel to get 2e. I then upgraded to Darky's 7.5 ROM, when that came up I was unable to get on the network. I was getting an error "Sim doesn't allow connection on the network" error when looking in providers. anyways, I just flashed the JK3 modem and i'm back on the network with Darky's rom
I grabbed the modem from here.
http://forum.xda-developers.com/showthread.php?t=846237
I used JK3 because they were having issues with JK4 bricking for some reason and didn't want to risk it. now to just get JL2 modem some how
There is a JL2 modem floating around somewhere.
I am also running jk3 modem with xxJPY, love my phone now.
No more bridling issues
BlackDino said:
There is a JL2 modem floating around somewhere.
I am also running jk3 modem with xxJPY, love my phone now.
No more bridling issues
Click to expand...
Click to collapse
Me too, so fast and smooth
If we could get jl2 modem with darkys
Is there a way to get jl2. Modem working with darkys then it would be perfect if u do find it let us know and make a step by step tutorial how it's done from the scratch for newbees canadiens thanks
notoriouspk said:
Is there a way to get jl2. Modem working with darkys then it would be perfect if u do find it let us know and make a step by step tutorial how it's done from the scratch for newbees canadiens thanks
Click to expand...
Click to collapse
It's very simple, TURN OFF ANY/ALL lag fixes!!!!! Back your **** up. then you can begin
You phone should be unlocked but might not have to be.....mine was, you can grab sgs unlocker form the app market also, You have to be running 2e recovery. so check on that first by powering your phone off, wait till it's actually off, froyo vibrates when it's shut down. After it's off, hold volume up, home button and power till you see the i9000m then let it go. it should boot into recovery. If you were running Froyo then you will have a 3e recovery, we need 2e. Also you should check and make sure you can get into download mode, by powering off, volume down, home and power key. If you can't get inot download mode you have to fix that first. if you can proceed:
So grab the recent stable speedmod kernel from hardcore here DON'T get the development version:
http://forum.xda-developers.com/showthread.php?t=822756&highlight=speedmod
depending on how you want to flash grab either the CWM or the other one which needs to be flashed via odin. Flash either or and your phone should boot with 2e. follow the instructions hardcore has posted and make sure you hit the thanks button for him .
After we have 2e installed you can grab Darky's ROM located here:
http://forum.xda-developers.com/showthread.php?t=814091
I used the non wipe one and didn't have issues, make sure you back your **** up before flashing anything. If you notice battery drain after you flash you could flash the wipe version just to make sure. anyways, Follow Darky's instructions to the T and dont forget to thank him
After his ROM boots, I grabbed a modem for our phones (bell, sasktel) I used JK3 because the search wasn't working last night but found this morning a link to JL2....i'm not sure if this is legit JL2 because I haven't used it but give it a shot if it doesn't work flash another on top (I can confirm JK3 works)
JL2: http://forum.xda-developers.com/atta...1&d=1293577837
Grabbed that from a link Samdroid_G_S posted so thank him for that.
JK3: was from docs link located here:
http://forum.xda-developers.com/showthread.php?t=846237&highlight=bell
you can thank him for that. I used JK3 because of the issues JK4 was causing. I wouldn't use JK4 but that' up to you.
again you can use either odin or CWM to flash the modem. once you flash the modem you should be able to register on the network. you might not have internet, so you will need to go in and edit your access point name. Located in your phone here:
Settings | wireless and network | Mobile Networks | access point names
If it is blank click the menu button and New APN, all you need for sasktel's is a name, can be whatever and APN, the APN should be "inet.stm.sk.ca" without the quotes. Leave everything else default and save it. you will have to click the bullet after you created it so it knows to use it. should be good after that. For bell just do a quick google search for bell apn or bell access point name, i'm sure someone has posted on xda also.
I am not responsible if you brick your phone, this is entirely on you if that happens.
Thanks man
That's what I have been looking for . A step by step tutorial how is the rom working for you I will give it a shot . I hope sd card Won't die on me again .I can deal with other problems but what could u do when sd card dies
on u .Thanks!
Hey no problem, by default the voodoo lag fix is disabled but honestly you won't need it.....
Sent from my GT-I9000 using XDA App
Nice, one of the great posts ever on xda. Is there any advantage to running darky's ROM? My SGS on JL2 has been good, and battery life seems awesome now that I turned off automated email checking.
adamge said:
Nice, one of the great posts ever on xda. Is there any advantage to running darky's ROM? My SGS on JL2 has been good, and battery life seems awesome now that I turned off automated email checking.
Click to expand...
Click to collapse
Pretty much preference I guess. I love Darky's ROM but JL2 was good, Darky's seems faster it's built upon 2.2.1 and I read Samsung did some kernel upgrades so that's why it's faster. If you do try it out just make sure you can get into recovery and download mode first.
i can confirm that Darkys rom works, I'm running 7.6 atm. I did notice that the APN settings in my original settings were missing ports numbers for data.
I tried this and it did not work, I still don't have data connection and I am on Bell canada.
Are u still getting text's? If so then you are registered on the network, all you have to do is go into your access point names and create an entry, then highlight it after it's saved. See my post above
Sent from my GT-I9000 using XDA App

[Q] Can i use official rom's on galaxy s with BOJF1 rom?How to?

I have samsung galaxy s(gt-i9000/it is not vibrant or...) which use this rom:
baseband version:i9000bojf1
build number:eclair.bojg3
I live in kuwait,but when i buy this phone it has one bag for used phone(T...MOBILE/UK),and in all user manual's i see t..mobile&samsung brand.
this version don't has arabic/persian lanuage&letter support,and i want use a JPJPG 2.2 rom to see arabic letters correctly/and all network lock is off on this phone and it's work correctly on kuwait's network...
can i use official rom's (froyo jpjpg 2.2) on this phone?
is this doing risky to brick my phone?
(i have no downloading problem)
is this a international version of galaxy s?
sorry for my bad english!
...
i have problem,help me,no one to answer me?
SOS
AliReza711 said:
I have samsung galaxy s(gt-i9000/it is not vibrant or...) which use this rom:
baseband version:i9000bojf1
build number:eclair.bojg3
I live in kuwait,but when i buy this phone it has one bag for used phone(T...MOBILE/UK),and in all user manual's i see t..mobile&samsung brand.
this version don't has arabic/persian lanuage&letter support,and i want use a JPJPG 2.2 rom to see arabic letters correctly/and all network lock is off on this phone and it's work correctly on kuwait's network...
can i use official rom's (froyo jpjpg 2.2) on this phone?
is this doing risky to brick my phone?
(i have no downloading problem)
is this a international version of galaxy s?
sorry for my bad english!
Click to expand...
Click to collapse
can i use jpjpg 2.2 official rom on this?how?
please guide me!
update via kies is risky?
i want an answer pls!...
If you have not had an answer to your multiple posts it usually means .
Nobody knows the answer or nobody understands your post .
jje
keep searching...
spark001uk said:
Originally Posted by jimsey View Post
my phone was on tmobiles BOJG3,
not sure it matter but i checked there tmobile hadn't re-enabled the sim-lock- which they hadn't
I flashed my phone using the rom I was using weeks ago: XWJM5 (using 512.pit, SERJM1 CSC and XXJM3 modem) all the files are in the JM5 download(single folder) from samfirmware.com
I used adb to get into download, then I selected repartition whilst flashing. ( not sure it's worth noting there's a sbl.bin file in the phone package that gets written to the device)
once i had JM5 up and running i checked whether the 3 button combo was working - it wasn't.
i then followed post 1 to the letter.( no .pit, select bootloader etc) - it takes just a second to run.
Now I just have to decide which ROM i want to try next -JPH awaits !
Well Jimsey, guess what.......... JOB DONE!!!!!
Did exactly what you said - except i added 1 step, (don't know if essential but i've heard reports that it saves some people needing to do a wipe/reset in recovery mode) :- i did a factory reset just prior to flashing of JM5. Other than that tho, i followed everything you did above TO THE LETTER!
Mind you, it wasn't good for my health i swear. It rebooted after flashing JM5, and a load of yellow writing came up saying all the little files it was initialising etc etc blah blah, and then... in RED writing it came up with - CANNOT ACCESS MULTI LOADER FROM TMU, or something like that.
Well, i felt the blood drain from my face. Then it booted up, damn that was scary!
You're right about the combo fix as well, when i flashed that it is as you say a dodgy two seconds, then a few more seconds on a black screen, i swear my heart didn't beat during that time!
Anyway there you go guys, i've just (narrowly avoiding a coronary) flashed my stock T-Mobile UK from BOJG3 to an unbranded, smooth as silk XWJM5, and on top of that flashed the standalone bootloader from post #1. And it works. I have the handset in front of me and it's all lit up on the home screen!
A big thankyou to Jimsey, for being the first pair of feet to jump!
Also to Richthofen for his bootloader fix, and his superb support in all this.
Well, don't know where next, JPC/JPH i suppose, but not yet, i need a drink to recover from this bit first!!
Click to expand...
Click to collapse
but few guy's in this forum do this work?!
theresee post 293
but my modem is different and it may cause some problem
pda:I9000BOJG3
PHONE:I9000BOJF1
CSC:I9000GTMUJG1
this csc and risk of this do is my problem my friend!?

[Q] trouble with my Sasktel Galaxy S

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.

Need some advice with i9000M

Hi guys, I know I need to make this short but I want it to be clear anyway. This is crazy I wanted nothing to do with smartphones 3-4 days ago because all the carriers rip us off with huge bills to get them. But low and behold when my cheap flip phone died after 3 years of loyal daily work a friend of mine offered me his Galaxy S i9000m for a good price. Started playing with the device and having a strong software/computer background started having a lot of fun with all the applications and was amazed with the possibilities (Networking, ipcam whatever) that just kept multiplying until I fell upon applications that needed something called gingerbread... Anyways I can tell you I learned a ****load in 48hours...
So I installed Samsung Kies, it found me the update and put it on for me.. (2.3.3 Gingerbread) then the nightmare started. The phone would boot, and would randomly reboot a random number of times until it could finally stay on and this could last from 2-30 minutes. So I thought, I'll just do a factory reset, to realise that its "STUCK" in 2.3.3 once its updated no going back to 2.1 or 2.2 easily.
Started looking around for ways to downgrade, and EVERY SINGLE LINK redirects to these 'mass download' sites that end up saying the firmwares were taken down for copyright issues. So desperate to find something, I fell upon a multiple CSC FROYO 2.2 firmware for the i9000 and was able to flash that in download mode the phone worked fine, except for me being very curious about the fact that I lost the "M" in my model description...
So started reading this thread(Mostly because I had already realised that with this non i9000m rom I had lost the 3 button DOWNLOAD MODE which i Had before) **** : http://androidforums.com/galaxy-s-a...flashing-darky-v9-gt-i9000m-minimal-risk.html
Got it rooted, got clockwork on, never managed to get the voodoo kernel working had errors in CWM.. so I was ready to give up until my eyes caught the
"*#*#2663#*#*
Then click Touch key FW update"
Which I thought would be neat to try.
NIGHTMARE, now BACK and MENU are dead, I understand that this is because I am running a non i9000m ROM and that updating the firmware rendered them unusable.
I came accross a post : http://forum.xda-developers.com/showthread.php?t=869492
Where this problem is adressed, I pretty much understand everything that should be done to get this back on its feet (right now the phone is still working I can use it at least 75% of its functions work except no back and menu)
Where I need your help : I'm not too sure how to attack this the right way, since I can't get into download mode I understand flashing is now more complicated to accomplish and now that I know that I need a i9000m firmware how can I find that...
Sorry for the long post I know I'm a noob here but I wanted to prove I had done all my homework to get where I'm at now seeking help from you guys!
Thanks a lot
Mat
By the way : Galaxy S GT i9000m currently on a 2.2 i9000 rom, my carrier is BELL. (Canada)
So there's no way of updating to 2.3.3 using Kies?
The only thing I can think of is getting a USB jig from ebay, which makes the i9000 go to download mode instantly. Good luck!
Alright, so I used CHECK FUS, and was able to get the i9000m stock BELL firmware YAY
now the help I need is to flash it correctly and find a way to get past the no download mode problem, would be very appreciated,
thanks guys
No, similar minds Sepharite, I also thought of redoing the Kies method, and then going back again if I needed to but now Samsung Kies says "Your device does not support firmware updates through Kies" Wow.. useful app, a samsung native app can't even detect it's own fricking hardware.
Thanks
UPdate : Was able to restore the 3 button "DOWNLOAD MODE" with a little tutorial online. Now I tried flashing my i9000m with ODIN, it flashed all the way and I get a i9000M logo now but it gets to the splash S logo and keeps rebooting never gets into the actual android setup is there something I did wrong?
In Odin all I put was the "BELL i19000m stock ROM" under PDA and wrote it. The device rebooted after flash but there still seems to be something I haven't done right.
Thanks guys
Please help guys, I know some of you out there have got this stuff nailed down!
Did you flash with a 1 file ROM or a 3 file ROM?
Using the UGKG3 ROM that you can fine here:
http://forum.xda-developers.com/showthread.php?t=1102881
Place the 3 files in their respective places (PDA, PHONE, CSC), for the PIT file, select the 512 pit file that should have come with ODIN, connect the phone, wait for ID:COM to turn yellow, and press Start.
That should get you going again. You may get apps that force close, so you'll need to delete the apps data and then reinstall them.
Hey thanks a lot man ya my flash was a SINGLE FILE, I bricked it yesterday trying to flash a different ROM since I had nothing to lose, I just got it working again on the old 9000 ****ty version that my back and menu keys don't work...
Now for some reason the USB JIG doesn'T work anymore after a couple of uses... could something have been damaged by doing it many times?
And your original roms section they are all unavailable due to copyright did you check the links before sending them?
When you say get the stock roms, I was able to get the UGKG3 file, but what about the versions? When I look at the north american section of the 2.2 version
UGKC1/UGKC1/BMCKC1/Sbl
UGJL2/UGJL2/BMCJL2/Sbl
UGJK3/UGJK3/BMCJK3
which one of the three suits me?
Thanks for your help, and if I get this running and go back and update my touch key firmwares with the right "Vibrant / 9000M" roms I should get them working again?
PS : I'm also very preoccupied by the fact that the USB JIG fix doesn'T seem to pop download mode anymore because this version of the ROM that I have has Download mode not working with the 3 button method. :S I wonder whats going on, but basically if I get your ROMS working the first time It'll fix everything but if it crashes then I lose the galaxy haha
Not sure why the USB jig doesn't work anymore. I have a couple and have only tested them on my phone to make sure they work, but they did not work on a Galaxy S II that I tried it on.
I just checked and the download link for the UGKG3 ROM at multiupload (downloading from multiupload), still works (you need to enter the captcha phrase).
The site megaupload was shut down by the US gov't, so that one won't work.
EDIT: UGKC1/UGKC1/BMCKC1/Sbl is the latest Froyo release from Bell. That's what mine and my wife's gt-i9000m phones came with.
She's still running it on hers.
Ok sorry for all these posts, basically when you said UGKG3 you want me to get the 2.3.3 ROM on ? Is that right? What if I Want to put on 2.2 to be sure I have no trouble with it since I'm in all this mess because the Kies update to Gingerbread had my phone in a bad state.
Thanks a lot by the way!
Sorry your post refreshed right after I did mine. Alright cool so I'll try the one you say your wife is running, I had made myself a JIG with a stock Samsung wire, it was working fine with a 300K resistor and I decided to solder it on and then it stopped working after that.... maybe the actual "usb plug" is damaged from the soldering heat I guess I'd have to try another wire, but anyway I'll try to download the 2.2 I just got the UGKG3 3 FILE rom downloaded one of the links did work!
But I'm a little worried about 2.3.3
I'll try to see if i can download the 2.2 first.
I mean basically... these roms shouldn't jam during transfer i Guess
One other thing I see different confusing information, is it important for me to click 'update bootloader" with these stock roms since these files contain an 'SBL' ? Because both times I bricked it was with an "update bootloader checked" firmware update trying to put the ARIES 3 button method fix as a boot.bin and sbl.bin
Fanks..
Files with SBL in the name already have the bootloader included in the PDA file, so "update bootloader" should NOT be checked.
That reassures me, because the only times it did jammed was when the bootloader was checked! THanks a lot blackrose i'll go out and buy another usb cable because I destroyed mine making my JIG. And I'll try yours out. I was reading a lot on another thread and found this one guy who flashed the JL2 one to save his keys instead of the C1 you said your wife was running, whats the main difference between those two and which one should I start with?
Update : I got a new wire, flashed the KC1 version of the firmware, everything goes fine, I did a repartition with the 512 PIT, it reboots the phone, loads all files in a prompt in yellow and there are no errors that appear, the phone reboots after writing 'successful update' and then goes to the galaxy logo and jams there and does the ONE vibrate, PAUSE, 2 vibrate on a black screen forever. The advantage of having successfully flashed a 9000M ROM allows me to have access to my DOWNLOAD MODE 3 button method, but ever since I flashed that 2.2 i9000 XXJP2 (seems its a euro version) off a torrent I found on the web (When I was desperate to find a functioning 2.2 working version) it seems as though it doesn'T want to boot with any other rom than that one, because all the 9000M roms that I've tried so far flash correctly, and the logo actually changed from i9000 to i9000M on the startup, but they just don't boot.. what could be missing it doesn't seem to be much???
Thanks Mat
If any of this can help, the device was rooted, I was following the darky's mod i9000M guide so I had previously installed the CLOCKWORK MOD and that's as far as I got because my eyes caught the FIRMWARE TOUCH KEY UPDATE which ruined my keys.
Could any of this have screwed something that stops my other roms from booting?
Thanks guys I really want to get this phone up and working again as I don't have much money and am afraid I'll have to cancel with my phone company if I just can'T get this running. I am also willing to make a significant donation to whoever can help me.
You in Canada right? Where abouts?
Sent from my GT-I9000 using xda premium
Quebec province
Alright, if this can help anybody my whole problme is solved.
I flashed the ****JL2**** the KC1 did not boot, the JL2 did.
Once inside JL2, I was able to update my TOUCH KEY FIRMWARE *#*#2663#*#* and everything went back to normal
I have no idea why the KC1 does not work, bugs me out.

[Q] Emergency Calls Only after CM install?

I've spent the last few days trying to figure this out without any luck. I have GT-S5830D (Canadian Koodo version) on stock firmware TLKI4, unlocked with SpeakOut sim (which operates on Rogers network).
Android Version: 2.3.4
Baseband Version: S5830DTLKI4
Kernel Version: 2.6.35.7-perf-CL568978 [email protected] #1
Build Number: GINGERBREAD.DTLKI4
PDA: S5830DTLKI4
PHONE: S5830DTLKI4
CSC: S5830DTLSKI4
In this stock firmware, I have no issues at all. Everything works fine, can place calls, WIFI, GPS, data all works. If I flash a new rom to the phone, I can see the networks still show up with signal strength showing okay, but the phone will not place calls. Just says Emergency Calls Only.
I've been reading about everything I can about this phone, and I just can't figure out what the problem is. I have flashed the modem with DDKQ7 and I was able to again place calls, however with this modem firmware, the connection was very unstable and would drop frequently.
Is there an issue with directly updating the stock rom to CM7 or CM9 that would cause problems with this baseband? I was under the impression that baseband wasn't really important. Interestingly enough, I have another phone that is the same make and model and is not experiencing this problem. I feel there must be something I am missing, if anyone can shed some light on this, I would appreciate it.
Thank you.
I have a feeling that I may be the only person that has experienced this issue. Continuing to search the internet for other answers, I've discovered that the baseband is the cause of this issue, but I still don't quite understands how it relates. My other phone is on the stock firmware (TLKI4) and is running CM7 without issue, on the same network even.
Do the APN settings have effect on voice calls too? Or is it strictly for data?
Also, I read a post on here that sounded like there was a limit to how many times you can perform a complete flash with Odin? Is that true? I'd love to keep experimenting, but each time to roll back the stock firmware, I need to use Odin and I'm hesitant due to the thought that will eventually brick the phone.
Thanks again.
tried to flash cm7 again??
Yes. I have installed cm-7.2.0-cooper.zip as well as some of the nightly's and still only get emergency calls only. I have another phone, exactly the same setup, and it works without issue. I even tryed GalaxyICS-latest and the same problem.
Now I did install a different modem firmware, and performed the upgrade and I don't have the issue anymore, however I have other issues, dropped service, 3g doesn't work properly, wifi and mobile data won't switch, gps is has extremely long lock time if it locks at all.
Does anyone here have the D version of this phone from Koodo? Which modem firmwares are you using? Anyone specifically using the phone on SpeakOut? Any hints would be helpful because I'm completely at a loss, will just have to keep it stock until I can figure it out.
I had the same problem as you, don't worry though because there is a solution. The Koodo Samsung Galaxy Ace only receives a signal when using the original Koodo baseband. (Basebands have to do with wireless signal, sometimes referred to as modems.) The good thing for you is that you can use any ROM or firmware you like, as long as after installing it you flash the original Koodo baseband (S5830DTLKI4) using Odin. I found a download link for the baseband in this thread: http://forum.xda-developers.com/showthread.php?t=1381595
After downloading, (I'm assuming you know how to use Odin, if not you can find a guide easily) open Odin, and in the "Phone" section browse to the file and select it. (You will have to extract the ZIP) Then press start and wait until it is finished downloading and that should do the trick. If you need any more help post back because I know what a pain it is to try and get this particular phone rooted and install a custom ROM.
ALSO MAKE SURE TO BACKUP IN CLOCKWORK MANAGER BEFORE FLASHING THIS
cause you never know what can happen.
If I flash CM7, it still shows my baseband being the same. It doesn't appear to have been changed. So what I need to do is flash CM7 and then just reflash the baseband with Odin and it should work? Even though the baseband shows the same? I'll give it a shot and let you know how it works out, but does anyone know why this would be required, to have to reflash the baseband even though it was never changed?
Is your current baseband S5830DTLKI4? Because in my experience that's the only way I could get service unless I was on the Koodo stock ROM.
Sent from my GT-S5830 using XDA
Yes, that is the firmware that I'm on. That firmware was installed with the stock rom that the phone came with and I have not changed it. Although I have changed it before, it fixed the issue with getting 'emergency calls only' in CM7 but the service was so flaky it wasn't worth keeping as a solution. If I leave the firmware from stock DTLKI4 and flash CM7 over it, I end up getting stuck with emergency calls only problem.
Is the current official CM7 not compatible with DTLKI4 firmware? Could that be the problem I'm having? I'm still really confused why this isn't working, but I will try to install CM7 again, and then use Odin to flash the DTLKI4 on top to see if the install is causing any issue with it. It doesn't really make sense.
Alright, interestingly enough, I just flashed it again and all is working as expected. I've flashed this phone about 10 times, using the same files and it would not work.
This time however, what I did differently is not root the phone. I've been using the universal_gb_root_v20.zip to root the phone previously, but I found that rooting before installing CM is waste of time as root is enabled in the CM7 rom already.
Also, when I flashed the stock rom with Odin, it usually used selected the KDO CSC automatically, last time I flashed it came up with TLS CSC and had the Telus branding. I don't know if that made any difference. All I know is that it worked and I am able to make calls and use data without any problems.
Thank you Dynamic_Apple, although your recommendation was not required, it did give me the motivation to try again and that was enough to get it working. I've never had so much difficulty modding a phone in my life, especially a model that I have messed with before.
Glad I was able to help, I had just as much trouble getting mine modded too, it makes me jealous of all the generic Galaxy Ace owners, but it's good to know that you can actually get past Koodo's sneaky limitations.

Categories

Resources