Related
Seeing as I`m still a relatively noobish poster I`m unable to ask this question in the relevant thread. I`ve just debranded the phone following the 8 step guide but I had issues following step 8 where you change the CSC code. I couldnt quite figure it out so step 8 never got followed. As a result, despite losing the Three branding on the phone I now have a phone that displays the CSC as "unknown" and may well explain why Kies cannot pick up the firmware version on the phone. If I follow step 8 and key in *#272*<your IMEI># on my phone it then shows me a screen headed "Preconfig" with "Sales Code" underneath and "H3G" in the box to the right. Underneath is a radio button thats deselected. if I press to highlight it then press "install" at the bottom of the screen I keep getting an error saying "Must be THREE chars".
Can anyone shed any light on this and give me any hope of rectifying?
Will I need to manually input the Three APN settings once I successfuly change the CSC code?
Thanks in advance. I have spent ages scouring the web but there`s not a great deal of info out there about the CSC part of the debranding process.
id like some more info on how important the csc is too, im got told it hold some carrier information but i dont know if that is true or not.
the reason you cant pick on is probably as since debranding you havent flashed the csc you need, you could find the one you need for your firmware over in the dev section.
Cheers for the reply, interestingly i`ve just re-flashed the phone and this time it is showing my CSC as XEU. Even so, I still cannot follow step 8. When I input that code including my IMEI in it shows XEU but when I press "install" it gives me the same old error of "Must be THREE chars". So not sure whether its worked or not and what diference it makes. At least Kies now shows something in the firmware field, even if it doesnt show what I was expecting. Hopefully someone can assist with this at some point later.
RedAl said:
Cheers for the reply, interestingly i`ve just re-flashed the phone and this time it is showing my CSC as XEU. Even so, I still cannot follow step 8. When I input that code including my IMEI in it shows XEU but when I press "install" it gives me the same old error of "Must be THREE chars". So not sure whether its worked or not and what diference it makes. At least Kies now shows something in the firmware field, even if it doesnt show what I was expecting. Hopefully someone can assist with this at some point later.
Click to expand...
Click to collapse
Hi there
If it says XEU after inputting the imei then it's working fine. You're not supposed to have to press install at this stage. Also to make sure it's working fine, I always boot into recovery mode. If you look down the code as recovery is loading, it will say which csc is being used/implemented (xue etc). Always reset data in recovery after rom flash from (especially from different csc.
I've had issues in the past when I flashed back to T-Mobile (after originally flashing ke7 stock) and then back again to T-Mobile. When I re-flashed back to stock after this, I couldn't get it to change from tmu (t-mobile) csc back to xeu, no matter how I flashed it. In the end the only way I could revert csc back to xeu was using the jig I had purchased. Apart from resetting the customer binery counter, it seemed to reset other settings, as once I had done this, I was able to install stock ke7 with xeu csc.
redbullman said:
Hi there
If it says XEU after inputting the imei then it's working fine. You're not supposed to have to press install at this stage. Also to make sure it's working fine, I always boot into recovery mode. If you look down the code as recovery is loading, it will say which csc is being used/implemented (xue etc). Always reset data in recovery after rom flash from (especially from different csc.
I've had issues in the past when I flashed back to T-Mobile (after originally flashing ke7 stock) and then back again to T-Mobile. When I re-flashed back to stock after this, I couldn't get it to change from tmu (t-mobile) csc back to xeu, no matter how I flashed it. In the end the only way I could revert csc back to xeu was using the jig I had purchased. Apart from resetting the customer binery counter, it seemed to reset other settings, as once I had done this, I was able to install stock ke7 with xeu csc.
Click to expand...
Click to collapse
Cheers for that. I just did a recovery as you suggested and saw it was done using the Multi-CSC so hopefully that means its all sorted.
Does this mean I should now be able to see the latest Firmware update available in Kies?
RedAl said:
Cheers for that. I just did a recovery as you suggested and saw it was done using the Multi-CSC so hopefully that means its all sorted.
Does this mean I should now be able to see the latest Firmware update available in Kies?
Click to expand...
Click to collapse
Yes you should be able to see the latest available update for your csc via kies. Although kies seems much slower to get the updates. It's much easier to use Odin. Most people update by this method. It's really easy and pretty safe.
redbullman said:
Yes you should be able to see the latest available update for your csc via kies. Although kies seems much slower to get the updates. It's much easier to use Odin. Most people update by this method. It's really easy and pretty safe.
Click to expand...
Click to collapse
The csc will be sorted now. Also if you plug your phone into kies, this will confirm what csc you are using.
redbullman said:
The csc will be sorted now. Also if you plug your phone into kies, this will confirm what csc you are using.
Click to expand...
Click to collapse
Cheers Redbullman. I can get into Kies now but on the firmware information section it says "Current Firmware Version : PDA:KDD / PHONE:KDH / CSC:KD1 (H3G)"
Its not telling me there`s a firmware update available so I have a horrible feeling something`s still not quite right but I`ve flashed it twice now and done 2 factory resets.
Would it be easier to find the stock KE7 kernel (forgive me if I`m using the wrong words) in Odin to flash it that way? If I can manually do it then I`d rather do it that way. Only problem is I`ve not yet found any tutorials on doing that, unless its the same (mostly) as the tutorial for debranding, except using a different .tar file (KE7).
Ok, I have 2 problems,
1- Wifi Problems starting yesterday, It get stuck on -getting ip address--, now I can only connect with an Static IP Adress, and yeah i've tried on another routhers
2.- Can't get any adb shell command to work, all i get is
#chmod:not found
#ls:not found
Any way I know there are several post about my first problem, and some about my second one, but I think my background history could help
This is how i broke my phone (I think...) this past week
-I got my phone last week (I9100 Galaxy S II locked with Telcel Mexico).
-First I rooted with superonclick since I wanted to install Titanium backup, all good
-Then I wanted to unlock my phone, so I order a code, but they couldn't found one for me, so i came to the dark side.
-So I found de unlock by nv_data.bin by Odia, but the app didn't work(I still have my original nv_data.bin but coz problem 2 can't put it back in), then following other comments I tried Unlock Galaxy S by Helroz, didn't work.
-Then and this may be the problem, i uninstall busybox and galaxy S(yeah i use the restore option on the app before uninstall.
Any ideas of what to do would be much appreciated.
Factory reset
Or flash stock rom .
jje
Sent from my GT-I9100 using xda premium
JJEgan said:
Factory reset
Or flash stock rom .
jje
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
did it work for you cavaliere?
if your system is not running like you want go into recovery, wipe cache and dalvic cache => Flash via odin the new original Firmware, boot your device.
Then flash a kernel => cf root
go into recovery, wipe cache and dalvic cache and go into advanced => fixing permissions, and reboot
now it should work
factory reset
I tried the factory reset from the stock recovery mode, but didn't worked, I now can't root with superoneclick, it has the same problem, doesn't found any shell code.
I think i'll try to flash stock rom with odin, but yesterday Multiupload was down and couldn't get the roms
You haven't broke anything you just messed it
mod rom
do you think that if i'll try a mod rom could help? if so, what rom do you like?
you need a stock rom ill recommend you get them from this post
http://forum.xda-developers.com/showthread.php?t=1075278
get the KK5 version and after that flash a custom kernel so you have root
you can get the kernel from here, http://forum.xda-developers.com/showthread.php?t=1103399
pm if you need anything else amigo
First mark *#06# to make sure your IMEI number is still the same after messing around with nv-data files.If I where you after whats happened I wouldnt be to upset about paying to unlock it for saftey reasons.Then if its O.k. Id root with a CF-Root kernel which are always the safest to use as far as Im concerned.
http://forum.xda-developers.com/showthread.php?t=1103399
Once rooted make a backup of your EFS folder to make sure you dont screw-up your IMEI in the future and can get it back.Download "Release.zip"
http://forum.xda-developers.com/showthread.php?t=1308546
After that your choice of firmware and/or custom ROM.
the right rom
cooza said:
First mark *#06# to make sure your IMEI number is still the same after messing around with nv-data files.Then if its O.k. Id root with a CF-Root kernel which are always the safest to use as far as Im concerned.
http://forum.xda-developers.com/showthread.php?t=1103399
Once rooted make a backup of your EFS folder to make sure you dont screw-up your IMEI in the future and can get it back.Download "Release.zip"
http://forum.xda-developers.com/showthread.php?t=1308546
After that your choice of firmware and/or custom ROM.
Click to expand...
Click to collapse
the IMEI is the same, so I gess is good, but I'm a little confuse with all the Firmwares, and want to make sure i get the right one.
Keis tells me: PDA:KK1 / Phone:KK1 / CSC: KK1
*#1234#: PDA: UMKE1 / PHONE UHKD8 / CSC TCEKE1
RorixRebel said:
you need a stock rom ill recommend you get them from this post
http://forum.xda-developers.com/showthread.php?t=1075278
get the KK5 version and after that flash a custom kernel so you have root
you can get the kernel from here, http://forum.xda-developers.com/showthread.php?t=1103399
pm if you need anything else amigo
Click to expand...
Click to collapse
guess you should know my friend, but just to be sure, did you mean this:
XWKK5
Android 2.3.6
This package has: PDA: XWKK5| Modem/phone: XXKI3| CSC: XEUKH2
Download: http://www.multiupload.com/7FKGH0Y68X
XWKK5 Stock Kernel: http://www.multiupload.com/HK8G4YGXWJ
Password: [email protected]
KK5 is good and if you want it download it from here as multiloader doesnt work anymore,
http://hotfile.com/dl/146318866/aa937b4/I9100XWKK5_I9100OXXKJ3.zip.html
PASSWORD:samfirmware.com
Root with this CF_Root kernel,
http://download.chainfire.eu/54/CF-Root/SGS2/CF-Root-SGS2_XW_OXA_KK5-v5.0-CWM5.zip
I have read here on XDA that you shouldnt flash a phone if its not unlocked.Please be careful and unlock your phone first to make sure.
Keep in mind that your CSC will now change as its not a firmware for your country so you will need to flash a custom ROM which has a multi-CSC pack built-in.
Thanks for the mirror
cooza said:
I have read here on XDA that you shouldnt flash a phone if its not unlocked.Please be careful and unlock your phone first to make sure.
Keep in mind that your CSC will now change as its not a firmware for your country so you will need to flash a custom ROM which has a multi-CSC pack built-in.
Click to expand...
Click to collapse
Thanks for the Mirror on the KK5, but now i'm a little scared since I can't unlock my phone, as i said I tried Odia and Helroz method, and tried with gsmliberty.net and mobifreedom.net, this last one gave me a code for an Atrix, fortunately they gave me a refound.
Now my last option is an obscure method by dertys_ at the end of Odias thread that's seams to be working. Maybe I could wait a couple of days for the stock ICS update and see how it goes.
WI-FI seams to be fine
Thanks again to cooza and RorixRebel for the help.
Just wanted to tell you(maybe this could help to someone else) that I rooted with CF-root get busybox back, so i get my original nv_data.bin back and seams that wi-fi is ok, at least at home, I'll try some other routers tomorrow but I'm really happy
Kies will still work if you are rooted so you will get the update.With the original nv-data maybe you can unlock it now.Why dont you try this.Chainfire is the guy who made the root kernel you used so maybe you could use this to unlock.
https://market.android.com/details?...sImV1LmNoYWluZmlyZS5zZ3Myc2ltdW5sb2NrY29kZSJd
This ones a bit more tricky
https://market.android.com/details?...sMSwyLDEsImNvbS5oZWxyb3ouZ2FsYXh5c3VubG9jayJd
Alredy tried
cooza said:
Kies will still work if you are rooted so you will get the update.With the original nv-data maybe you can unlock it now.Why dont you try this.Chainfire is the guy who made the root kernel you used so maybe you could use this to unlock.
https://market.android.com/details?...sImV1LmNoYWluZmlyZS5zZ3Myc2ltdW5sb2NrY29kZSJd
This ones a bit more tricky
https://market.android.com/details?...sMSwyLDEsImNvbS5oZWxyb3ouZ2FsYXh5c3VubG9jayJd
Click to expand...
Click to collapse
I tried both again but same outcome, first one doesn't give code, second, says it unlocked but my other sim it just doesn't work, only Emergency calls
cavaliere06 said:
I tried both again but same outcome, first one doesn't give code, second, says it unlocked but my other sim it just doesn't work, only Emergency calls
Click to expand...
Click to collapse
I read that the helroz has a second step to it but the guy didnt explain what it was and he said that it worked.Dont know what he did though but he said the same thing happened to him at first.
I went to software update and there is a 197mb update on my phone then i started to download and it downloaded just fine but after rebooting it is failed always at 12% and meesage comes up " update through kies or contact samsung"... on kies there is no update.
My phone is not rooted.S II I9100 from KSA.
anyone?
This is what exactly going on
http://www.youtube.com/watch?v=gHkU_57zmlM&feature=player_embedded
Assuming you're running stock & have never messed with (rooted/run non stock firmware) the phone, try a factory reset/wipe in the first instance (boot into recovery), then try the update again.
You could flash a stock ICS rom manually with Odin, but be aware if you bork it in the process (very unlikely/small risk, but still a risk nonetheless), you'll likely not get it fixed under warranty. Get the PC version of Checkfus if you want to go down this route (search for it on here/Google), this will enable you to download the update manually, then flash it following the instructions here.
Ton need at least 40% to install an update.
MistahBungle said:
Assuming you're running stock & have never messed with (rooted/run non stock firmware) the phone, try a factory reset/wipe in the first instance (boot into recovery), then try the update again.
Click to expand...
Click to collapse
actually i have rooted my phone before 2 months but now it is not rooted... i just want to install official ICS using kies or through OTA ...don't want to root again.
Then take your pick. Do the reset & try it again (make sure you've got at least 40% battery; I think that's what JT meant), or do it manually with Odin. Or try the first option, then the 2nd one.
Up to you.
Also, if you can't find the firmware you need with Checkfus, search Samfirmware or here
Edit after your edit - In that case definitely the first option. If it doesn't work & you don't want to do it manually, take it to a Samsung service centre & ask them to put the latest firmware on it for you.
MistahBungle said:
Then take your pick. Do the reset & try it again (make sure you've got at least 40% battery; I think that's what JT meant), or do it manually with Odin. Or try the first option, then the 2nd one.
Up to you.
Also, if you can't find the firmware you need with Checkfus, search Samfirmware or here
Edit after your edit - In that case definitely the first option. If it doesn't work & you don't want to do it manually, take it to a Samsung service centre & ask them to put the latest firmware on it for you.
Click to expand...
Click to collapse
Ok, after reseting there is no update available on my phone when i try to update using phone.
OK. Have you ever flashed any other stock firmware on the phone ? I have two theories about this 'upgrade' - one; if you've flashed stock firmware for other regions on your phone, there's may be some issue with the CSC (even if you're currently running correct firmware for your region) preventing you from getting OTA updates successfully. Also, the update you saw may have been not for your region, because your CSC is messed up , it may have tried to pull an update for the region whose firmware you had on the phone previously. And when you did a reset it might have somehow fixed the issue with the CSC, and there is no update for your region. Conjecture, but hard to know exactly without knowing the history of the phone & exactly what you've done it.
Two; the size of the update sounds a bit strange. I would have thought it would be bigger than 197MB. Even zipped, I have a carrier branded ICS firmware and it's huge (>700MB). That you were able to download it, yet there was nothing on Kies is really strange.
Go into settings/about phone & tell me all the details you have in there. Also tell me everything you've done with the phone since you got it so far as rooting/flashing other firmware goes (details of kernels, roms, etc). And we'll see if we can shed a bit more light on things.
And one other thing, in your last post you say there's no update on the phone, have you checked Kies again. If not, have a look.
MistahBungle said:
it may have tried to pull an update for the region whose firmware you had on the phone previously. And when you did a reset it might have somehow fixed the issue with the CSC, and there is no update for your region. Conjecture
Click to expand...
Click to collapse
This might be true
Go into settings/about phone & tell me all the details you have in there
Click to expand...
Click to collapse
.
I bought S2 from Saudi Arabia.
baseband version: I9100XXKI4
Kernal Version: 2.6.35.7-I9100JPKJ2-CL655700 [email protected] #2
GBuild Number: GINGERBREAD.JPKJ2
]Also tell me everything you've done with the phone since you got it so far as rooting/flashing other firmware goes (details of kernels, roms, etc). And we'll see if we can shed a bit more light on things.
Click to expand...
Click to collapse
I have used this guide for rooting http://androidforums.com/galaxy-s2-...t/482994-rooting-galaxy-s2-dummies-guide.html
but after trying 5 or 6 custom ROMS i just unroot my phone.
And one other thing, in your last post you say there's no update on the phone, have you checked Kies again. If not, have a look.
Click to expand...
Click to collapse
no update on kies either.
I have also used this method toinstall official stock firmware http://www.technetinfo.in/mobile/mobile-software/stock-gingerbread.html
let me quote my own message while i was having problem with CSC.
k i did factory reset and wipe all data now it doesn't show "that device doest not support software upgrading via KIES" but firmware info is totally different now, it is suppose to be (KSA) not (XSG).
Click to expand...
Click to collapse
one thing more i would like to mention here is that before rooting....KIES showing
PDA:KJ2 / PHONE:KI4: / CSC KJ1 (KSA)
now it's showing
PDA:KJ2 / PHONE:KI4: / CSC KJ1 (XSG)
Click to expand...
Click to collapse
FIXED BY CHANGING CSC CODE
OK. Given all that, then it's obviously a CSC issue. Which means either it showed an update was available for the wrong region, and now that CSC issue has been resolved. Or there is an update for your region but your CSC is messed up so it can't get the update.
I've had a look at Checkfus, and the stock rom you're currently running is the latest for Saudi Arabia (GT-I9100LKAKSA -I9100JPKJ2/I9100OJPKJ1/I9100XXKI4/I9100JPKJ2) which was released on 25/10/2011.
So I'd say that update you saw was for another region, and the factory reset you did fixed whatever issue there was. There are no updates for your region, put it that way.
Edit - Unless it's some kind of minor carrier specific update ? That could explain the relatively small size of the one you saw. I guess you could find this out by contacting your carrier.
Thanks a lot MistahBungle, i really appreciate your help.
Now i have changed my CSC code from (KSA) to (JED) and now i'm getting official update from kies. Just curious about changing CSC, is there any negative effect on my phone in future by just changing CSC code?
Given you're getting OTA updates OK, probably not. Normally if you change your CSC to a different region, you often have problems getting OTA firmware updates. If it's working for you, it's obviously fine.
MistahBungle said:
Given you're getting OTA updates OK, probably not. Normally if you change your CSC to a different region, you often have problems getting OTA firmware updates. If it's working for you, it's obviously fine.
Click to expand...
Click to collapse
not sure about OTA but on KIES it is showing my firmware info correctly, i mean i can get updates through KIES without any issues.
suppose if i want to change my CSC back to original one (KSA) then what will happen?
As long as you can get it via Kies you're set. And even if you couldn't, it's simple to download the firmware with Checkfus & flash it via Odin. That's what I'd do if I were on rooted stock, for example (but I probably wouldn't be in any event).
I don't know. Try it & find out. Yes, I'm serious. I hate stock firmware, it's rubbish, and haven't run it since the first week I got my phone. So I honestly don't know.
Hi all....
I am an infrequent user of this site, the last time I pored over the information housed in here was a couple of years ago when I found the site and various threads invaluable for me when rooting my old and trusty HTC Desire.
I am now the owner of a fab and groovy galaxy S3 which I aquired in the UK from carphone warehouse.
I am using Vodafone as a carrier, but my understanding is that the stock phone was not tied in any way to a carrier.
It didn't take me long to root the phone, I only rooted the device because I wanted to get rid of various bits of samsung/bloatware, not in order to Flash a new rom to the phone.
I was more than happy with this until I received a notification that there was an OTA update, this I deemed to be the JB OS, which of course would not install due to the fact the phone was rooted and was using cwm etc.
After a week of cancelling the update and being reminded of it every three hours I decided that it was maybe time to update, I discovered that in order to do this I needed in effect to put the phone back to its factory state, soo I completed a factory reset on the phone and in no time at all I was up and running again with an unrooted S3....however, despite this in the last three weeks I have seen hide nor hair of the update that seemed to be banging at my door for so long!
My question therefore is:
is there something I am unaware of that is now stopping my phone from receiving the OTA update via settings/about device/software update/update(check for updates)?
To help those of you that know about this stuff here are the details from the phone that may help you to help me...and anyone else not in the know enough!
Device Status = Normal (while rooted this obviously showed as being modified)
Model Number GT-19300
Android version 4.0.4
baseband version - 19300XXLG8
kernel version - 3.0.15-928452-user [email protected] #1 SMP PREEMPT Thu Jul 26 12:06:08 KST 2012
Build Number IMM76D.19300XXBLGB
In addition prior to unrooting the phone the foillowing info was parsed and returned :
AP: 19300XXBLG8
CP: 19300XXLH1
CSC: 19300OXABLG8
Following unrooting and completing a factory reset.....the same process returns this information.....
AP: 19300XXBLG8
CP: 19300XXLG8
CSC: Unknown.
My apologies for the length of the post for what is probably a trivial matter, but as a Phone noob (but a systems pro) you can never have too much info!
many thanks in anticipation!
It's because your CSC was lost when you unrooted and hence OTA won't work. You would have been better off using the toolkit (see original development forum) to simply download and flash the JB ROM yourself, then no need to unroot etc.
You can still do this and you'll also get updates usually faster than OTA.
Regarding your bust CSC, try:
http://forum.xda-developers.com/showthread.php?t=1845103
Hmmm...well...
many thanks for the info re the cause of the issue, however, having looked at the following I still am having no joy.
1) downloaded a correct csc file and using odin flashed it to my phone, however, it is still showing the same information as before.
2) Found a stock Rom. the exact same Rom as that which is installed, that has been flashed using Odin and once again, upon reboot the information is exactly the same.
I'm not quite sure why you want to fix it, flashing jb yourself is much quicker, but a quick search found:
Q. I have flashed XXXX ROM and now my CSC is unknown?
A. Generally Speaking CSC does not make much of a difference. If you are really facing a problem which is related to CSC such as some specific apps not working, some language not there etc. Either:
Use
Type *#272*Device IMEI# at Phone dial pad.
Select the CSC that you want.
Click Install.
or Install CSC changer app from the Market and change the CSC
Both ways yopur device will be factory resetted.
Good luck.
I can....
...find all of that myself, It doesn't really help much if the person searching amongst the huge amount of disarticulated information liberally strewn around this forum is faced constantly with broken links or unhelpful replies and threads that vanish up their own orifice.
In order to decorticate that information it helps if some form of standardisation or common language is employed.
I have my reasons for asking the original question.
I am facing a problem and asking for advice and help in order to rectify the issue.
I have tried to flash the JB ROm myself, I am despite what you may consider not stupid, however, I am receiving errors when flashing the rom from the 'update' menu from the recovery menu within the phone.
Elsewhere on this forum I discover that it may be an issue with the csc being in an unknown state, hence my post in the first place, If I was able to follow the instructions and all was working as it should I would not bother anyone here or indeed waste my time doing so.
by querying the csc by using the dial pad it shows me that the correct one is still there, so installing it seems pointless, however, as stated at the very beginning of the question, when parsing the phone for detail info it tells me that the csc is 'UNKNOWN'
Greywolf907 said:
many thanks for the info re the cause of the issue, however, having looked at the following I still am having no joy.
1) downloaded a correct csc file and using odin flashed it to my phone, however, it is still showing the same information as before.
2) Found a stock Rom. the exact same Rom as that which is installed, that has been flashed using Odin and once again, upon reboot the information is exactly the same.
Click to expand...
Click to collapse
Try installing this from the Android Market
https://play.google.com/store/apps/details?id=com.manniakk.cscselector&
Run it and update your CSC to your correct one
EDIT :- Just looked at your phone info in post 1 again, this relates to UK unbranded version so your CSC should be BTU
You shouldn't normally have a problem updating a rooted phone to newer versions provided the base rom is still stock I have never had a problem with mine but everyone is different I guess, I did mine via Kies then just re-rooted afterwards.
...well...
ag4751 said:
Try installing this from the Android Market
Run it and update your CSC to your correct one
Click to expand...
Click to collapse
Hi and thank you also...however, I have checked the sales code and it is properly installed and shown as being BTU, which is correct, this is shown of course by typing into the dial pad...et al ad nausea....whatever, it is correctly displayed, the issue is that when typing into the dial pad *#1234# in order to retrieve the information contained there, it is returning CSC UNKNOWN.
Greywolf907 said:
Hi and thank you also...however, I have checked the sales code and it is properly installed and shown as being BTU, which is correct, this is shown of course by typing into the dial pad...et al ad nausea....whatever, it is correctly displayed, the issue is that when typing into the dial pad *#1234# in order to retrieve the information contained there, it is returning CSC UNKNOWN.
Click to expand...
Click to collapse
OK you wrote this while I was writing my edit in the previous post.
Have you tried just installing the latest 4.1.1 BTU version using Odin you can get it from the Sammobile web site its the PDA version I9300XXDLJ4
http://www.sammobile.com/firmware/?page=3&model=GT-I9300&pcode=BTU&os=1&type=1#firmware
......not
ag4751 said:
OK you wrote this while I was writing my edit in the previous post.
Have you tried just installing the latest 4.1.1 BTU version using Odin you can get it from the Sammobile web site its the PDA version I9300XXDLJ4
....that version no........I did d/l and try this version
United Kingdom 8 Sep 2012 4.1.1 I9300XXBLG8 I9300XXDLI4 283.2 MB Download
which seemed to be relevant to my original build, this is the one that I have been having issues with.
I am also somewhat confused as to how to install the zip file via Odin, I more or less think that the pda file needs to be a single tar/md5 file and of course these things are coming as zips...well..at least the last one I d/l'd did.....
I am as I type sucking the file you suggest down and as soon as hotfile finishes dribbling it into my machine I'll give it a bash and let you know what happens.....many many thanks for taking the time to help me and do it with such good grace and civility, it's refreshing.
Cheers for now!
PS: I tried Kies, on three different machines, two running XP and one running Seven, each time it just doesnt want to know that the phone is even connected...ie. it knows its there, but just doesnt want to actually connect to it...just whirrs and clicks until I get fed up and unplug it....hence the grief I am having one way or another trying to update the O/S...so I can root it again!
Click to expand...
Click to collapse
I am also somewhat confused as to how to install the zip file via Odin, I more or less think that the pda file needs to be a single tar/md5 file and of course these things are coming as zips...well..at least the last one I d/l'd did.....
Click to expand...
Click to collapse
You need to extract the file located inside the zip file, then start Odin, click the PDA button and find the extracted file, put your phone in download mode, connect to your PC, wait for Odin to connect then start the update.
mucho...
ag4751 said:
You need to extract the file located inside the zip file, then start Odin, click the PDA button and find the extracted file, put your phone in download mode, connect to your PC, wait for Odin to connect then start the update.
Click to expand...
Click to collapse
yes I understand all that bit, I didn't make myself clear maybe....The problem I had was that the file I had downloaded seemed to be a zip file containing the whole system, i.e a cloned image, it didn't work...however, the link you so very helpfully provided was just waht i was looking for and couldn't find myself, a single tar/md5 file which has been downloaded, installed and is up and running....I now have JB, but still the csc is classified as unknown...anyhow, that doesn't matter much until the next time I need to update.
My very best regards to you and huge thanks.
have a good 'un
:good:
Got there eventually, strange abut the CSC
If you want to root your phone use this thread, 3rd post if you don't already have it
http://forum.xda-developers.com/showthread.php?t=1957273
Then install this for easy access to recovery
http://forum.xda-developers.com/showthread.php?t=1768142
Hi All Below I occidentally posted in the Galxy SI900 instead of here< I got the usual replies but was grateful all the same. Maybe someone might help before I revert to stock...
Hi all, I know this has been done and dusted but I am having problems with connecting to kies after rooting. I am running standard jelly bean 4.1.2 and is an Australian GT-I9100. I installed the siyah kernal root system and now all I get on kies is "connecting" Windows 7 recognises and I can access the phone via explorer on the PC. The phone after a while comes up with a message that there is no compatible software on the PC, install kies...
I have tried all the so called fixes including formatting the internal SD and memory. The only thing I did before it stopped connecting was the root and running Triangle away (paid version). I have enabled / disabled USB debugging. The only things I haven't tried is a factory reset which I don't really want to do as I am always sceptical that the backup apps will work after to restore everything.
Any help appreciated
Click to expand...
Click to collapse
The thread is here: http://forum.xda-developers.com/showthread.php?p=45907982#post45907982
Hope someone can help...
Regards Ismael
Did you try another PC or reinstall Kies? To know if the problem is in the phone or in PC?
jiseuo said:
Did you try another PC or reinstall Kies? To know if the problem is in the phone or in PC?
Click to expand...
Click to collapse
Yes, Kies definitely sees the phone as it comes up with GTI9100 loading on the left top and in the centre it just sits saying connecting. I think the phone is not seeing kies as the message on my phone always comes up only when trying to connect to kies.
I have tried 3 computers/laptops same result. Different USB cables original plus other really high end ones also. No Joy. Looks like if I want to connect to kies I must revert back to stock kernal as the firmware I never changed it is the OTA from samsung 4.1.2 and rooted the S2 only...
Also Not knowing Samsung but in the about on my Motorola Tablet/phone even when rooted when you try to check for updates they say none available, the samsung actually says "Your device has been modified, no updates available"...
IsmaelJones said:
Yes, Kies definitely sees the phone as it comes up with GTI9100 loading on the left top and in the centre it just sits saying connecting. I think the phone is not seeing kies as the message on my phone always comes up only when trying to connect to kies.
I have tried 3 computers/laptops same result. Different USB cables original plus other really high end ones also. No Joy. Looks like if I want to connect to kies I must revert back to stock kernal as the firmware I never changed it is the OTA from samsung 4.1.2 and rooted the S2 only...
Also Not knowing Samsung but in the about on my Motorola Tablet/phone even when rooted when you try to check for updates they say none available, the samsung actually says "Your device has been modified, no updates available"...
Click to expand...
Click to collapse
Now I am not using KIES, because I use AOSP ROM (4.3 Slimbean), but in past, when i was using STOCK ROM (XWLSN, XWLSS) I used "PhilZ-cwm6 - Safe Stock Based Kernel" http://forum.xda-developers.com/showthread.php?t=1877270 to root my phone.
If I remember correctly, KIES was working with PhillZ, but it is few months ago ...
So you can try PhillZ and see If it will work.(If do not need any special feature from syiah kernel of course)
jiseuo said:
If I remember correctly, KIES was working with PhillZ, but it is few months ago ...
So you can try PhillZ and see If it will work.(If do not need any special feature from syiah kernel of course)
Click to expand...
Click to collapse
Okay had a look at this, thanks. I do have a question though, my Kernel (PDA) is XWLSH, I have downloaded the 2 files but I am wondering how to install? Do I use my CW recovery or do I have to revert back to stock? A little confusing as he dowsn't really give instructions and I am pretty much an amateur when it comes to some of these things? Also I am running JB 4.1.2 he only mentions ICS 4.0.4? Help appreciated here...
Actually just re-read the post and I think I know now what to do. Correct me if I am wrong but the 2 files I downloaded are for 2 different methods of installing, the Zip file via SD card and the MD5 file by odin. Is this correct?
IsmaelJones said:
Actually just re-read the post and I think I know now what to do. Correct me if I am wrong but the 2 files I downloaded are for 2 different methods of installing, the Zip file via SD card and the MD5 file by odin. Is this correct?
Click to expand...
Click to collapse
Yes. ZIP is for flashing from recovery and tar.md5 is for flashing from ODIN.
Maybe the best way will be to reflash your whole stock firmware to get correct previous state before you started flashing syiah. You can get it on Sammobile.com - (simple registration needed) and then use PhilZ recomended method - flash ZIP from stock recovery
What is your Country / operator, Try this http://www.sammobile.com/firmwares/2/ to find right and latest oficial firmware for your country / operator version for your phone.
edit: For XWLSH it may be GT-I9100LKJXSA - unbranded australia version, or GT-I9100LKJOPS - Australia OPTUS operator customized version.
jiseuo said:
Yes. ZIP is for flashing from recovery and tar.md5 is for flashing from ODIN.
Maybe the best way will be to reflash your whole stock firmware to get correct previous state before you started flashing syiah. You can get it on Sammobile.com - (simple registration needed) and then use PhilZ recomended method - flash ZIP from stock recovery
What is your Country / operator, Try this http://www.sammobile.com/firmwares/2/ to find right and latest oficial firmware for your country / operator version for your phone.
edit: For XWLSH it may be GT-I9100LKJXSA - unbranded australia version, or GT-I9100LKJOPS - Australia OPTUS operator customized version.
Click to expand...
Click to collapse
Hi Again, solved the problem... definitely the siyah root was the culprit. I used mobile Odin to install the stock kernel, once done checked and could connect in kies and was still rooted missing busybox only. After that I again used mobile odin to install philZ, again no problems and all seems fine now. Everything working.
Thanks a million for helping and also many thanks to mobile odin developers as this is a far better tool than most and saves connecting to the PC Odin. Also seems a lot safer...
:good: